From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe58.law3.hotmail.com [209.185.240.58]) by dsl2.external.hp.com (Postfix) with ESMTP id 85EFC482A for ; Wed, 7 Aug 2002 02:33:42 -0600 (MDT) From: "Alex Green" To: Date: Wed, 7 Aug 2002 10:33:31 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BF_01C23DFD.E0080F40" Message-ID: Subject: [parisc-linux] palo issues Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_01BF_01C23DFD.E0080F40 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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 =3D -7: Nonexistent device >>Some Hex Entries<< Failed to initialize What is this... did I do something wrong? AG ------=_NextPart_000_01BF_01C23DFD.E0080F40 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hi,

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

ENTRY_INIT failed, status =3D = -7: Nonexistent=20 device

>>Some Hex=20 Entries<<

Failed to = initialize

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

------=_NextPart_000_01BF_01C23DFD.E0080F40-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe22.law3.hotmail.com [209.185.240.15]) by dsl2.external.hp.com (Postfix) with ESMTP id D4380482A for ; Wed, 7 Aug 2002 04:56:13 -0600 (MDT) From: "Alex Green" To: Date: Wed, 7 Aug 2002 12:56:11 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0290_01C23E11.CE09F380" Message-ID: Subject: [parisc-linux] palo issues Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_0290_01C23E11.CE09F380 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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 =3D -7: Nonexistent device >>Some Hex Entries<< Failed to initialize What is this... did I do something wrong? AG ------=_NextPart_000_0290_01C23E11.CE09F380 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hi,

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

ENTRY_INIT failed, status =3D = -7: Nonexistent=20 device

>>Some Hex=20 Entries<<

Failed to = initialize

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

------=_NextPart_000_0290_01C23E11.CE09F380-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from systemhalted (CPE0080c82c70ca.cpe.net.cable.rogers.com [24.112.140.233]) by dsl2.external.hp.com (Postfix) with ESMTP id 3D38E482A for ; Wed, 7 Aug 2002 06:39:33 -0600 (MDT) Date: Wed, 7 Aug 2002 08:38:07 -0400 From: Carlos O'Donell To: Alex Green Cc: parisc-linux@lists.parisc-linux.org Subject: Re: [parisc-linux] palo issues Message-ID: <20020807123807.GB9966@systemhalted> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: > 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe50.law3.hotmail.com [209.185.240.218]) by dsl2.external.hp.com (Postfix) with ESMTP id 451A3482A for ; Wed, 7 Aug 2002 08:38:51 -0600 (MDT) From: "Alex Green" To: "Carlos O'Donell" Cc: References: <20020807123807.GB9966@systemhalted> Subject: Re: [parisc-linux] palo issues Date: Wed, 7 Aug 2002 16:38:48 +0200 Message-ID: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: 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" To: "Alex Green" Cc: 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe62.law3.hotmail.com [209.185.240.63]) by dsl2.external.hp.com (Postfix) with ESMTP id 92A66482A for ; Wed, 7 Aug 2002 09:23:29 -0600 (MDT) From: "Alex Green" To: "Paul Bame" Cc: References: <20020807123807.GB9966@systemhalted>

Subject: Re: [parisc-linux] palo issues Date: Wed, 7 Aug 2002 17:23:26 +0200 Message-ID: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: ok the file was build using make bzImage... surely this would produce a proper image..... or not? ----- Original Message ----- From: "Paul Bame" To: "Alex Green" 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe21.law3.hotmail.com [209.185.240.125]) by dsl2.external.hp.com (Postfix) with ESMTP id 83722482A for ; Wed, 7 Aug 2002 09:28:23 -0600 (MDT) From: "Alex Green" To: "Paul Bame" Cc: References: <20020807123807.GB9966@systemhalted>

Subject: Re: [parisc-linux] palo issues Date: Wed, 7 Aug 2002 17:28:20 +0200 Message-ID: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: I ran file against my new kernel and the output is the same as the currently booting kernel. ----- Original Message ----- From: "Paul Bame" To: "Alex Green" 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from systemhalted (CPE0080c82c70ca.cpe.net.cable.rogers.com [24.112.140.233]) by dsl2.external.hp.com (Postfix) with ESMTP id 9298C482A for ; Wed, 7 Aug 2002 09:38:21 -0600 (MDT) Date: Wed, 7 Aug 2002 11:36:47 -0400 From: Carlos O'Donell To: Alex Green Cc: Paul Bame , parisc-linux@lists.parisc-linux.org Subject: Re: [parisc-linux] palo issues Message-ID: <20020807153647.GD12856@systemhalted> References: <20020807123807.GB9966@systemhalted>

Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe54.law3.hotmail.com [209.185.240.54]) by dsl2.external.hp.com (Postfix) with ESMTP id 898BE4831 for ; Wed, 7 Aug 2002 09:40:34 -0600 (MDT) From: "Alex Green" To: "Carlos O'Donell" Cc: "Paul Bame" , References: <20020807123807.GB9966@systemhalted>

<20020807153647.GD12856@systemhalted> Subject: Re: [parisc-linux] palo issues Date: Wed, 7 Aug 2002 17:40:32 +0200 Message-ID: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: 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" To: "Alex Green" Cc: "Paul Bame" ; 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. > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hotmail.com (oe66.law3.hotmail.com [209.185.240.82]) by dsl2.external.hp.com (Postfix) with ESMTP id 519A1482A for ; Wed, 7 Aug 2002 10:06:19 -0600 (MDT) From: "Alex Green" To: "Paul Bame" Cc: "Carlos O'Donell" , References: <20020807123807.GB9966@systemhalted>

Subject: Re: [parisc-linux] palo issues Date: Wed, 7 Aug 2002 18:05:54 +0200 Message-ID: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: > > > > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from atlrel6.hp.com (atlrel6.hp.com [156.153.255.205]) by dsl2.external.hp.com (Postfix) with ESMTP id 0EA13482A for ; Wed, 7 Aug 2002 10:29:36 -0600 (MDT) To: "Alex Green" Cc: "Carlos O'Donell" , parisc-linux@lists.parisc-linux.org Subject: Re: [parisc-linux] palo issues In-Reply-To: Your message of "Wed, 07 Aug 2002 18:05:54 +0200." References: <20020807123807.GB9966@systemhalted>

Date: Wed, 07 Aug 2002 10:29:32 -0600 From: Paul Bame Message-Id: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: **** 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from systemhalted (CPE0080c82c70ca.cpe.net.cable.rogers.com [24.112.140.233]) by dsl2.external.hp.com (Postfix) with ESMTP id 4FE43482A for ; Wed, 7 Aug 2002 10:39:33 -0600 (MDT) Date: Wed, 7 Aug 2002 12:37:57 -0400 From: Carlos O'Donell To: Paul Bame Cc: Alex Green , parisc-linux@lists.parisc-linux.org Subject: Re: [parisc-linux] palo issues Message-ID: <20020807163757.GF13287@systemhalted> References: <20020807123807.GB9966@systemhalted>

Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: > > --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.