On 28.11.2016 19:05, Helge Deller wrote: > On 28.11.2016 19:37, Meelis Roos wrote: >>>>>>> Command line for kernel: 'root=/dev/sda3 console=ttyS0 >>>>>>> palo_kernel=2/vmlinux' >>>>>>> Selected kernel: /vmlinux from partition 2 >>>>>> >>>>>> I'm missing here the information of the various sections >>>>>> in the vmlinux file which the boot loader usually prints >>>>>> here. >>>>> >>>>> Well, I did not leave anything out AFAIK? >>>> >>>> It seems palo can't read the vmlinux file (aka get's confused with the contents >>>> and doesn't print the ELF section list). >>>> >>>> Did you maybe used a recent binutils package? >> >> Old binutils, but here is my vmlinux that does not boot (slightly larger >> than vmlinux-4.8.0): >> >> http://kodu.ut.ee/~mroos/vmlinux-4.9.0-rc6-00240-gd8e435f > > This kernel boots nicely for me on my c3000 machine: > > Main Menu: Enter command > bo pri > Interact with IPL (Y, N, Q)?> y > > Booting... > Boot IO Dependent Code (IODC) revision 0 > > > HARD Booted. > palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31 +0100 > Skipping extended partition 6 - beyond reach of IPL > > Partition Start(MB) End(MB) Id Type > 1 2 33 f0 Palo > 2 34 157 83 ext2 > 5 159 134887 83 ext2 > > PALO(F0) partition contains: > 0/vmlinux64 17631904(0) bytes @ 0x140000 > > Information: No console specified on kernel command line. This is normal. > PALO will choose the console currently used by firmware (serial).Current command line: > 2/vmlinux root=LABEL=ROOT rootfstype=ext4 initrd=2/initrd.img HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102 The only differences I currently see between your and my setup are: 1. My palo partition contains a vmlinux file (you need to add a vmlinux file to your /etc/palo.conf file and rerun "palo -v"). 2. In my setup I didn't added "console=ttyS0". palo does that by itself if you run via serial console. I'm not confident that those are the problem, but you may try... Helge > ... > Current command line: > 2/vmlinux-4.9.0-rc6-00240-gd8e435f root=LABEL=ROOT rootfstype=ext4 HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102 > 0: 2/vmlinux-4.9.0-rc6-00240-gd8e435f > 1: root=LABEL=ROOT > 2: rootfstype=ext4 > 3: HOME=/ > 4: panic_timeout=60 > 5: panic=-1 > 6: console=ttyS0 > 7: TERM=vt102 > > <#> edit the numbered field > 'b' boot with this command line > 'r' restore command line > 'l' list dir > 'x' reset and reboot machine > ? b > > Command line for kernel: 'root=LABEL=ROOT rootfstype=ext4 HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux-4.9.0-rc6-' > Selected kernel: /vmlinux-4.9.0-rc6-00240-gd8e435f from partition 2 > ELF64 executable > Entry 00100000 first 00100000 n 5 > Segment 0 load 00100000 size 134688 mediaptr 0x1000 > Segment 1 load 00121000 size 22272 mediaptr 0x22000 > Segment 2 load 00200000 size 4456864 mediaptr 0x28000 > Segment 3 load 00641000 size 1387492 mediaptr 0x469000 > Segment 4 load 00800000 size 1084600 mediaptr 0x5bc000 > Branching to kernel entry point 0x00100000. If this is the last > message you see, you may need to switch your console. This is > a common symptom -- search the FAQ and mailing list at parisc-linux.org > > Linux version 4.9.0-rc6-00240-gd8e435f (mroos@a500) (gcc version 5.4.0 (Gentoo 5.4.0 p1.0) ) #104 Sun Nov 27 16:30:20 EET 2016 > unwind_init: start = 0x4075a444, end = 0x40793be4, entries = 14714 > FP[0] enabled: Rev 1 Model 19 > The 64-bit Kernel has started... > Kernel default page size is 4 KB. Huge pages enabled with 1 MB physical and 2 MB virtual size. > bootconsole [ttyB0] enabled > Initialized PDC Console for debugging. > Determining PDC firmware type: System Map. > model 00005dc0 00000481 00000000 00000002 777c3e84 100000f0 00000008 000000b2 000000b2 > vers 00000301 > CPUID vers 19 rev 11 (0x0000026b) > capabilities 0x7 > model 9000/785/C3700 > ... > > Helge > -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
