[parisc-linux] palo issues

[parisc-linux] palo issues

[Alex Green]

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

Hi,

I've just build 2.4.19-pa2 on my c3600 and then I ran palo * I've updated to 1.1 * afterwards, after booting I got an error reporting:

ENTRY_INIT failed, status = -7: Nonexistent device

>>Some Hex Entries<<

Failed to initialize

What is this... did I do something wrong?



AG

[-- Attachment #2: Type: text/html, Size: 1448 bytes --]

Re: [parisc-linux] palo issues

[Carlos O'Donell]

> Hi,
> I've just build 2.4.19-pa2 on my c3600 and then I ran palo * I've updated to 1.1 * afterwards, after booting I got an error reporting:
> ENTRY_INIT failed, status = -7: Nonexistent device
> >>Some Hex Entries<<
> Failed to initialize
> What is this... did I do something wrong?
> AG

Yes. Possibly specifying the wrong device.

To quote HP IT Resources:
The device address supplied to ENTRY_INIT is valid, but, 
the target controller or device is not installed or is not responding
ENTRY_INIT -7 Causes:
- Booting from the wrong path or non-existent device.
- Trying to boot from a device that is not responding.

Stop the machine at bootup and try to search for bootable
devices... and see what it returns.

c.

Re: [parisc-linux] palo issues

[Alex Green]

ok, well i got the PALO to start however it now crashes with the following
error:

Couldn't grok your kernel executable formatERROR: failed to load kernel.

What does this mean?

ag

----- Original Message -----
From: "Carlos O'Donell" <carlos@baldric.uwo.ca>
To: "Alex Green" <alexdgreen@hotmail.com>
Cc: <parisc-linux@lists.parisc-linux.org>
Sent: Wednesday, August 07, 2002 2:38 PM
Subject: Re: [parisc-linux] palo issues


> > Hi,
> > I've just build 2.4.19-pa2 on my c3600 and then I ran palo * I've
updated to 1.1 * afterwards, after booting I got an error reporting:
> > ENTRY_INIT failed, status = -7: Nonexistent device
> > >>Some Hex Entries<<
> > Failed to initialize
> > What is this... did I do something wrong?
> > AG
>
> Yes. Possibly specifying the wrong device.
>
> To quote HP IT Resources:
> The device address supplied to ENTRY_INIT is valid, but,
> the target controller or device is not installed or is not responding
> ENTRY_INIT -7 Causes:
> - Booting from the wrong path or non-existent device.
> - Trying to boot from a device that is not responding.
>
> Stop the machine at bootup and try to search for bootable
> devices... and see what it returns.
>
> c.
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>

Re: [parisc-linux] palo issues

[Alex Green]

ok the file was build using make bzImage... surely this would produce a
proper image..... or not?

----- Original Message -----
From: "Paul Bame" <bame@fc.hp.com>
To: "Alex Green" <alexdgreen@hotmail.com>
Sent: Wednesday, August 07, 2002 5:14 PM
Subject: Re: [parisc-linux] palo issues


> > ok, well i got the PALO to start however it now crashes with the
following
> > error:
> >
> > Couldn't grok your kernel executable formatERROR: failed to load kernel.
> >
> > What does this mean?
>
> The normal reason for this error is that the file isn't an elf32
> or elf64 executable.  Common mistakes are using a lifimage instead
> of a 'vmlinux' (e.g., elf kernel).  Once someone used a tarball
> (of the pre-built kernels on ftp.parisc-linux.org/kernels/32) without
> unpacking it first.
>
> Run 'file' on what you're telling palo to load.
>
> -P
>

Re: [parisc-linux] palo issues

[Alex Green]

> > > > ok the file was build using make bzImage... surely this would
produce a
> > > > proper image..... or not?
> > >
> > > Nope.  Just use 'make'.  the file 'vmlinux' is what you want
>
> Something doesn't compute yet for me, sorry for asking stupid
> questions:
>
>     So you made 'vmlinux' and then copied it to /boot or something right?

Yep I copied to /boot/vmlinux-64

>
>     'file vmlinux' says something about ELF 32 right?

nope I built it with 64bit gcc, as I wanted a 64bit kernel, so the file is
ELF64 :).

>
>     The partition where palo expects to find 'vmlinux' _ends_ within the
>     first 2G of the disk?

Yep, the f0 partition is the first 75mb of the disk:


Disk /dev/sda: 64 heads, 32 sectors, 17366 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1   *         1        72     73712   f0  Linux/PA-RISC boot
/dev/sda2            73       560    499712   82  Linux swap
/dev/sda3           561      1048    499712   82  Linux swap
/dev/sda4          1049     17366  16709632   83  Linux


mount
/dev/sda4 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/proc/bus/usb on /proc/bus/usb type usbdevfs (rw)


cat /etc/palo.conf
--commandline=4/boot/vmlinux-64 root=/dev/sda4 HOME=/
--recoverykernel=/boot/vmlinux
--init-partitioned=/dev/sda


ls -l
total 11912
-rw-r--r--    1 root     root       881069 Aug  7 10:23 System.map-2.4.18-64
-rw-r--r--    1 root     root       900165 Aug  7 18:04 System.map-64
-rw-r--r--    1 root     root         4711 Aug  7 10:23 config-2.4.18-64
lrwxrwxrwx    1 root     root           17 Aug  7 10:26 vmlinux ->
vmlinux-2.4.18-64
-rw-r--r--    1 root     root      5139673 Aug  7 10:23 vmlinux-2.4.18-64
-rwxr-xr-x    1 root     root      5227388 Aug  7 18:04 vmlinux-64


palo
palo version 1.1 bame@c3k Tue Aug  6 09:40:01 MDT 2002
ELF64 executable
Partition Start(MB) End(MB) Id Type
1               1      72   f0 Palo
2              73     560   82 swap
3             561    1048   82 swap
4            1049   17366   83 ext2
ipl: addr 16384 size 30720 entry 0x0
 ko 0x0 ksz 0 k64o 0x0 k64sz 0 rdo 0 rdsz 0
<4/boot/vmlinux-64 root=/dev/sda4 HOME=/>
ipl: addr 16384 size 30720 entry 0x0
 ko 0x0 ksz 0 k64o 0x44000 k64sz 5139673 rdo 0 rdsz 0
<4/boot/vmlinux-64 root=/dev/sda4 HOME=/>


file vmlinux-64
vmlinux-64: ELF 64-bit MSB executable, PA-RISC 2.0 (LP64) version 1
(GNU/Linux), dynamically linked (uses shared libs), not stripped
mohawk:/boot# file vmlinux-2.4.18-64
vmlinux-2.4.18-64: ELF 64-bit MSB executable, PA-RISC 2.0 (LP64) version 1
(GNU/Linux), dynamically linked (uses shared libs), not stripped
mohawk:/boot#


Does this shed any light ??

Thanks
AG

Re: [parisc-linux] palo issues

[Paul Bame]

	**** BOTH THE F0 PARTITION AND THE EXT2 PARTITION	****
	**** WHERE PALO IS TOLD TO FIND THE KERNEL _MUST_ BE	****
	**** CONTAINED WITHIN THE FIRST 2G OF THE DISK		****
	http://parisc-linux.org/software/install.html

> >     The partition where palo expects to find 'vmlinux' _ends_ within the
> >     first 2G of the disk?

In your case (thanks for all the info!) palo is being asked to load the
kernel from partition 4.

> --commandline=4/boot/vmlinux-64 root=/dev/sda4 HOME=/

Partition 4 is _NOT_ contained within the first 2G.

> /dev/sda4          1049     17366  16709632   83  Linux

Sorry my question wasn't clearer.  Perhaps you can turn sda2 or 3 into
a /boot partition, or something more drastic...

> Yep, the f0 partition is the first 75mb of the disk:
> 
> 
> Disk /dev/sda: 64 heads, 32 sectors, 17366 cylinders
> Units = cylinders of 2048 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/sda1   *         1        72     73712   f0  Linux/PA-RISC boot
> /dev/sda2            73       560    499712   82  Linux swap
> /dev/sda3           561      1048    499712   82  Linux swap
> /dev/sda4          1049     17366  16709632   83  Linux
> 
> 
> mount
> /dev/sda4 on / type ext3 (rw,errors=remount-ro)
> proc on /proc type proc (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> /proc/bus/usb on /proc/bus/usb type usbdevfs (rw)
> 
> 
> cat /etc/palo.conf
> --commandline=4/boot/vmlinux-64 root=/dev/sda4 HOME=/
> --recoverykernel=/boot/vmlinux
> --init-partitioned=/dev/sda
> 
> 
> ls -l
> total 11912
> -rw-r--r--    1 root     root       881069 Aug  7 10:23 System.map-2.4.18-64
> -rw-r--r--    1 root     root       900165 Aug  7 18:04 System.map-64
> -rw-r--r--    1 root     root         4711 Aug  7 10:23 config-2.4.18-64
> lrwxrwxrwx    1 root     root           17 Aug  7 10:26 vmlinux ->
> vmlinux-2.4.18-64
> -rw-r--r--    1 root     root      5139673 Aug  7 10:23 vmlinux-2.4.18-64
> -rwxr-xr-x    1 root     root      5227388 Aug  7 18:04 vmlinux-64
> 
> 
> palo
> palo version 1.1 bame@c3k Tue Aug  6 09:40:01 MDT 2002
> ELF64 executable
> Partition Start(MB) End(MB) Id Type
> 1               1      72   f0 Palo
> 2              73     560   82 swap
> 3             561    1048   82 swap
> 4            1049   17366   83 ext2
> ipl: addr 16384 size 30720 entry 0x0
>  ko 0x0 ksz 0 k64o 0x0 k64sz 0 rdo 0 rdsz 0
> <4/boot/vmlinux-64 root=/dev/sda4 HOME=/>
> ipl: addr 16384 size 30720 entry 0x0
>  ko 0x0 ksz 0 k64o 0x44000 k64sz 5139673 rdo 0 rdsz 0
> <4/boot/vmlinux-64 root=/dev/sda4 HOME=/>
> 
> 
> file vmlinux-64
> vmlinux-64: ELF 64-bit MSB executable, PA-RISC 2.0 (LP64) version 1
> (GNU/Linux), dynamically linked (uses shared libs), not stripped
> mohawk:/boot# file vmlinux-2.4.18-64
> vmlinux-2.4.18-64: ELF 64-bit MSB executable, PA-RISC 2.0 (LP64) version 1
> (GNU/Linux), dynamically linked (uses shared libs), not stripped
> mohawk:/boot#
> 
> 
> Does this shed any light ??
> 
> Thanks
> AG
> 
> 
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] palo issues

[Carlos O'Donell]

> > --commandline=4/boot/vmlinux-64 root=/dev/sda4 HOME=/
> 
> Partition 4 is _NOT_ contained within the first 2G.
> 
> > /dev/sda4          1049     17366  16709632   83  Linux
> 
> Sorry my question wasn't clearer.  Perhaps you can turn sda2 or 3 into
> a /boot partition, or something more drastic...
> 
> > Yep, the f0 partition is the first 75mb of the disk:

Or you could set --commandline=0/vmlinux and have palo copy the
kernel into f0. Though you'll need to do this for every new kernel
you want to use. Very much like a normal lilo setup on x86. Though
if you muck it up... you can't recover.

c.

Re: [parisc-linux] palo issues

[Alex Green]

I ran file against my new kernel and the output is the same as the currently
booting kernel.


----- Original Message -----
From: "Paul Bame" <bame@fc.hp.com>
To: "Alex Green" <alexdgreen@hotmail.com>
Sent: Wednesday, August 07, 2002 5:14 PM
Subject: Re: [parisc-linux] palo issues


> > ok, well i got the PALO to start however it now crashes with the
following
> > error:
> >
> > Couldn't grok your kernel executable formatERROR: failed to load kernel.
> >
> > What does this mean?
>
> The normal reason for this error is that the file isn't an elf32
> or elf64 executable.  Common mistakes are using a lifimage instead
> of a 'vmlinux' (e.g., elf kernel).  Once someone used a tarball
> (of the pre-built kernels on ftp.parisc-linux.org/kernels/32) without
> unpacking it first.
>
> Run 'file' on what you're telling palo to load.
>
> -P
>

Re: [parisc-linux] palo issues

[Carlos O'Donell]

On Wed, Aug 07, 2002 at 05:28:20PM +0200, Alex Green wrote:
> I ran file against my new kernel and the output is the same as the currently
> booting kernel.
> 
> 

I was decidedly wrong. While 'make bzImage' will produce the
right vmlinux for you to use... you cannot use the actual bzImage
because we don't support compressed kernel images in palo.

Using the vmlinux in /usr/src/linux (or where your tree is) will
get you to the right place :)

c.

Re: [parisc-linux] palo issues

[Alex Green]

I've rebuilt using make vmlinux, to remove all options for the wrong image
being built, however, even after reloading palo, it still has the same
error.

I'm now going back to look at the kernel build to check if I can anything
there.

----- Original Message -----
From: "Carlos O'Donell" <carlos@baldric.uwo.ca>
To: "Alex Green" <alexdgreen@hotmail.com>
Cc: "Paul Bame" <bame@fc.hp.com>; <parisc-linux@lists.parisc-linux.org>
Sent: Wednesday, August 07, 2002 5:36 PM
Subject: Re: [parisc-linux] palo issues


> On Wed, Aug 07, 2002 at 05:28:20PM +0200, Alex Green wrote:
> > I ran file against my new kernel and the output is the same as the
currently
> > booting kernel.
> >
> >
>
> I was decidedly wrong. While 'make bzImage' will produce the
> right vmlinux for you to use... you cannot use the actual bzImage
> because we don't support compressed kernel images in palo.
>
> Using the vmlinux in /usr/src/linux (or where your tree is) will
> get you to the right place :)
>
> c.
>

[parisc-linux] palo issues

[Alex Green]

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

Hi,

I've just build 2.4.19-pa2 on my c3600 and then I ran palo * I've updated to 1.1 * afterwards, after booting I got an error reporting:

ENTRY_INIT failed, status = -7: Nonexistent device

>>Some Hex Entries<<

Failed to initialize

What is this... did I do something wrong?



AG

[-- Attachment #2: Type: text/html, Size: 1396 bytes --]