From None Date: None From: Subject: [palinux-palo] bug#74: Palo ramdisk problems X-PA-RISC Linux-PR-Message: report 74 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by bugs@bugs.parisc-linux.org id=B.98417675614170 (code B ref -1); Fri, 09 Mar 2001 22:33:01 GMT Date: Fri, 9 Mar 2001 17:26:41 -0500 From: "Paul J.Y. Lahaie" To: submit@bugs.parisc-linux.org Message-ID: <20010309172641.B30872@achilles.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Package: palo Version: 0.86 I've done a cvs update right before, so this should be the latest and greatest(?) palo. When you use a ramdisk with palo, the ramdisk does not seem to be found. Here is the palo command line: ../palo/palo/palo -b ../palo/iplboot -k vmlinux -r ~/root.bin -c "0/vmlinux initrd=0/ramdisk console=ttyS0 root=/dev/ram0 HOME=/ TERM=linux" -s a180 Here is what PALO writes on bootup: palo ipl pjlahaie@ljudfisk Fri Mar 9 17:07:49 EST 2001 0/vmlinux 2611079 bytes @ 0x6800 0/palo-cmdline '0/vmlinux initrd=0/ramdisk console=ttyS0 root=/dev/ram0 HOME=/ TERM=linux' 0/ramdisk 6553600 bytes @ 0x283f87 Kernel: partition 0 file /vmlinux ELF32 executable Entry 00100000 first 00100000 n 5 Segment 0 load 00100000 size 1512872 mediaptr 0x1000 Segment 1 load 00272000 size 184264 mediaptr 0x173000 Segment 2 load 002a0000 size 221536 mediaptr 0x1a0000 Segment 3 load 002d8000 size 8192 mediaptr 0x1d7000 Segment 4 load 00306608 size 76256 mediaptr 0x1d9608 branching to kernel entry point 0x00100000 Here is what the kernel says: PALO command line: 'initrd=0/ramdisk console=ttyS0 root=/dev/ram0 HOME=/ TERM=linux' PALO initrd 0-0 Total Memory: 128 Mb initrd: 00000000-00000000 From None Date: None From: Subject: bug#74: [palinux-palo] bug#74: Palo ramdisk problems X-PA-RISC Linux-PR-Message: report 74 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by 74-bugs@bugs.parisc-linux.org id=B74.9845067177865 (code B ref 74); Tue, 13 Mar 2001 18:18:01 GMT To: "Paul J.Y. Lahaie" , 74@bugs.parisc-linux.org In-Reply-To: Your message of "Fri, 09 Mar 2001 15:33:03 MST." <200103092233.PAA29171@hpfcla.fc.hp.com> References: <200103092233.PAA29171@hpfcla.fc.hp.com> Date: Tue, 13 Mar 2001 11:05:15 -0700 From: Paul Bame Message-Id: This is either in late palo pre-boot code or early kernel boot code so I'll take a look at it. -P From None Date: None From: Subject: [palinux-palo] bug#74: palinux-palo] bug#74: Palo ramdisk problems X-PA-RISC Linux-PR-Message: report 74 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by 74-bugs@bugs.parisc-linux.org id=B74.9845140419125 (code B ref 74); Tue, 13 Mar 2001 20:18:01 GMT To: 74@bugs.parisc-linux.org In-Reply-To: Your message of "Tue, 13 Mar 2001 11:18:04 MST." <200103131818.LAA06165@hpfcla.fc.hp.com> References: <200103131818.LAA06165@hpfcla.fc.hp.com> Date: Tue, 13 Mar 2001 13:05:24 -0700 From: Paul Bame Message-Id: Fixed in CVS. If that's inconvenient, change the kernel commandline so that 'initrd=' isn't the first arg after the kernel name. From daniel_frazier@hp.com Tue, 13 Mar 2001 13:18:02 -0700 (MST) Date: Tue, 13 Mar 2001 13:18:02 -0700 (MST) From: PA-RISC Linux bug Tracking System daniel_frazier@hp.com Subject: [palinux-palo] Processed: your mail Processing commands for control@bugs.parisc-linux.org: > close 74 bug#74: Palo ramdisk problems bug closed, send any further explanations to "Paul J.Y. Lahaie" > End of message, stopping processing here. Please contact me if you need assistance. dann frazier (administrator, PA-RISC Linux bugs database) From None Date: None From: Subject: [palinux-palo] bug#87: palo ipl entry point must be at start of executable X-PA-RISC Linux-PR-Message: report 87 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by bugs@bugs.parisc-linux.org id=B.9851989041760 (code B ref -1); Wed, 21 Mar 2001 18:33:01 GMT Message-Id: Date: Wed, 21 Mar 2001 11:20:59 -0700 (MST) To: submit@bugs.parisc-linux.org From: bame@debian.org Cc: bame@debian.org Sender: www-data@bame.riverrock.org Package: palo Version: 20Mar2001 Severity: grave recently the palo ipl entry point, $ (in crt0.S), started being moved to 0x60010 rather than 0x60000 where the text segment is relocated. This is due to linker stubs being inserted at the beginning of the segment. Fix is to use .init instead. From None Date: None From: Subject: [palinux-palo] bug#89: get rid of "warning block sizes other than 1k may fail" message X-PA-RISC Linux-PR-Message: report 89 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by bugs@bugs.parisc-linux.org id=B.9852057443325 (code B ref -1); Wed, 21 Mar 2001 20:18:02 GMT Message-Id: Date: Wed, 21 Mar 2001 13:15:08 -0700 (MST) To: submit@bugs.parisc-linux.org From: bame@debian.org Cc: bame@debian.org Sender: www-data@bame.riverrock.org Package: palo Version: 20Mar2001 Severity: wishlist From daniel_frazier@hp.com Wed, 21 Mar 2001 13:18:03 -0700 (MST) Date: Wed, 21 Mar 2001 13:18:03 -0700 (MST) From: PA-RISC Linux bug Tracking System daniel_frazier@hp.com Subject: [palinux-palo] Processed: your mail Processing commands for control@bugs.parisc-linux.org: > close 87 bug#87: palo ipl entry point must be at start of executable bug closed, send any further explanations to bame@debian.org > End of message, stopping processing here. Please contact me if you need assistance. dann frazier (administrator, PA-RISC Linux bugs database) From None Date: None From: Subject: [palinux-palo] bug#90: palo should allow booting kernels and ramdisks from ext2 partitions past 2Gbytes X-PA-RISC Linux-PR-Message: report 90 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by bugs@bugs.parisc-linux.org id=B.9852059613430 (code B ref -1); Wed, 21 Mar 2001 20:33:01 GMT Message-Id: Date: Wed, 21 Mar 2001 13:18:49 -0700 (MST) To: submit@bugs.parisc-linux.org From: bame@debian.org Cc: bame@debian.org Sender: www-data@bame.riverrock.org Package: palo Version: 20Mar2001 Severity: wishlist Later PDC firmware has an alternate disk I/O interface which allows access to large disks, so the current palo limitation that it must boot from an ext2 partition which ends within the first 2Gbytes can be eliminated on certain systems. From None Date: None From: Subject: [palinux-palo] bug#92: Won't boot after editing entries X-PA-RISC Linux-PR-Message: report 92 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by bugs@bugs.parisc-linux.org id=B.9852376629192 (code B ref -1); Thu, 22 Mar 2001 05:18:02 GMT Date: Thu, 22 Mar 2001 05:07:39 +0000 From: Matthew Wilcox To: submit@bugs.parisc-linux.org Message-ID: <20010322050739.O5491@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: Package: palo Version: Unsure After interacting with IPL and editing the load options, I frequently get a hang as demonstrated by the following boot log: Main Menu: Enter command > bo lan Interact with IPL (Y, N, Q)?> y INI C740: initialize other path Booting... Network Station Address 001083-357d75 System IP Address 15.1.51.80 Server IP Address 15.1.50.190 Boot IO Dependent Code (IODC) revision 2 INI C780: load IPL other path INI C30C: monarch slave check INI CC41: CPU1 memory rendezvous INI CC43: CPU3 memory rendezvous INI CC42: CPU2 memory rendezvous INI 10CA: CPU0 initialize system bus arbitration HARD Booted. INI C7FF: launch IPL other palo ipl willy@chrysl Sat Feb 17 02:25:19 MST 2001 0/vmlinux 2564549 bytes @ 0x6800 0/palo-cmdline '0/vmlinux HOME=/ TERM=linux root=/dev/sda1 console=ttyS0 init=/bin/sh' Current command line: 0/vmlinux HOME=/ TERM=linux root=/dev/sda1 console=ttyS0 init=/bin/sh 0: 0/vmlinux 1: HOME=/ 2: TERM=linux 3: root=/dev/sda1 4: console=ttyS0 5: init=/bin/sh Edit which field? (or 'b' to boot with this command line)? 3 root=/dev/nfs nfsroot=15.1.50.190 Current command line: 0/vmlinux HOME=/ TERM=linux root=/dev/nfs nfsroot=15.1.50.190 console=ttyS0 init=/bin/sh 0: 0/vmlinux 1: HOME=/ 2: TERM=linux 3: root=/dev/nfs 4: nfsroot=15.1.50.190 5: console=ttyS0 6: init=/bin/sh Edit which field? (or 'b' to boot with this command line)? b Kernel: partition 0 file /vmlinux (hangs for long time, then): ERROR: Read from boot device failed (status = -3). byteio_read: seekread() returned -1 expected 2048 ERROR: Read from boot device failed (status = -3). byteio_read: seekread() returned -1 expected 2048 ERROR: Read from boot device failed (status = -3). byteio_read: seekread() returned -1 expected 2048 Couldn't grok your kernel executable format failed to load kernel This palo may be somewhat out of date. To help, we have: willy@chrysl:~/parisc/palo$ cvs -n up C Makefile U ipl/Makefile U ipl/crt0.S U ipl/ipl.c U ipl/pdc_misc.c $ cat ipl/CVS/Entries /Makefile/1.14/Mon Feb 12 22:16:03 2001// /ipl.c/1.13/Mon Feb 12 22:16:03 2001// /pdc_misc.c/1.6/Tue Sep 5 16:04:15 2000// /crt0.S/1.11/Sat Feb 17 09:22:24 2001// i hope this helps you tell whether this bug has been fixed already. -- Revolutions do not require corporate support.