FW: 2.4 -> 2.6
Well, I tried 2.6.8-2-32-smp "out of the box" and got nowhere again. When I booted with root=/dev/sda3 it didn't find it, so I changed to root=/dev/sdb3 and it still didn't find it. Could I please hear from someone who has upgraded from 2.4 to 2.6 to let me know what they did STEP BY STEP. Thanks -Original Message- From: Harry Cochran [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 2:28 PM To: Thibaut VARENE Cc: debian-hppa@lists.debian.org Subject: 2.4 -> 2.6 Thanks Thibaut, I double checked the kernel output from my last attempt (attached) and I don't see anywhere where it tells me that sda under 2.4 has become sdb under 2.6 except that it does tell me my root is not on sda, so that doesn't leave too many other choices. One final question. My palo.conf says --command-line=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --recoverykernel=1/vmlinux.old --init-partitioned=/dev/sda (vmlinux->vmlinux-2.6.8-2-32-smp and vmlinux.old->vmlinux-2.4.17-32) What I hear you saying is that I should reboot with this palo.conf and if I get the root problem again I should change root=/dev/sda3 to root/dev/sdb3 and reboot again. I note that after the first reboot it's too late to change init-partitioned=/dev/sda to /dev/sdb, but I guess that's okay (all I can find on init-partitioned is that it tells palo to initialize the palo boot parameters on the drive rather than preserving any existing parameters). Thanks again for your help. If I get through this I will commit to trying to write down the baby steps so that no one goes through what I went through no matter how uninitiated to Debian hppa Linux they are. Cheers, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 1:42 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: [parisc-linux] NIC & "searching for devices" On Fri, 25 Feb 2005 11:16:52 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Thanks Thibaut, > > However, I have been unable to upgrade to 2.6. The image in > unstable, > 2.6.8-2-32-smp requires initrd. Fair enough, but nothing I have tried > works. I get tripped up on the root= statement (I have sent mail on > this). I've been searching for days now for a simple cookbook on > upgrading from 2.4 to 2.6 and I can't find one. If you could please > point me to a document that goes through the process of upgrading from > 2.4 to 2.6, I would really appreciate it. I don't understand your problem. apt-get install kernel-image-2.6.8-2-32-smp should work out of the box. the root issue is just a matter of having your root device name that has changed. look in the kernel output while booting, you'll see where your HD lives. For instance, on a machine of mine, /dev/sda became /dev/sdb. HTH Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ 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.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 Partition Start(MB) End(MB) Id Type 1 1 31 f0 Palo 2 321008 82 swap 31009 17366 83 ext2 PALO(F0) partition contains: 0/vmlinux32 4968722 bytes @ 0x44000 Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial).Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=/initrd.img console=ttyS0 TERM=vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? 03 initrd=1/boot/initrd.img Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=1/boot/initrd.img console=ttyS0 TERM =vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=1/boot/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? b Command line for kernel: 'root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_ke rnel=1/boot/vmlinux' Selected kernel: /boot/vmlinux from partition 1 Selected ramdisk: /boot/initrd.img from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable Entry 0010 first 0010 n 3 Segment 0 load 0010 size 2832408 mediaptr 0x1000 Segment 1 load 003b4000 size 705472 mediaptr 0x2b5000 Segment 2 load 00464000 size 397328 mediaptr 0x362000 ERROR: failed to load ramdisk - proceeding anywayBranching to kernel entry point 0x0010. 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 2.6.8-2-32-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian
RE: FW: 2.4 -> 2.6
Dear Grant, Kyle and Thibaut: Thank you all very much! I now have a running 2.6.8-2-32-smp on my J6000. I repartitioned sda to have the root right next to the f0 partition (and the swap at the end) per Grant, modified /etc/mkinitrd/modules per Kyle and added Kyle's patch to mkinitrd just for luck, rebooted and everything just worked. sda did not become sdb. I will write this up to point out the pitfalls newbies like me can hit, but I'm afraid I'm out of time to figure out if, for instance, it works without Kyle's mods. It's great to be back among the living Debian hppa users! This J6000 is going into production in China to run Web and mail services for my company there. Cheers, Harry -Original Message- From: Grant Grundler [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 1:30 AM To: Harry Cochran Cc: Thibaut VARENE; debian-hppa@lists.debian.org Subject: Re: 2.4 -> 2.6 On Fri, Feb 25, 2005 at 02:27:52PM -0500, Harry Cochran wrote: > HARD Booted. > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 This is an invalid partition scheme. It's just luck that it worked with 2.4 kernel. I'm assuming partition 3 is the root partition. Re-read http://en.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html. In particular "4.3.3. Making a bootable partition". grant -Original Message- From: Kyle McMartin [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 11:27 PM To: Harry Cochran Subject: Re: FW: 2.4 -> 2.6 On Fri, Feb 25, 2005 at 10:20:28PM -0500, Harry Cochran wrote: > Well, I tried 2.6.8-2-32-smp "out of the box" and got nowhere again. When I > booted with root=/dev/sda3 it didn't find it, so I changed to root=/dev/sdb3 > and it still didn't find it. Could I please hear from someone who has > upgraded from 2.4 to 2.6 to let me know what they did STEP BY STEP. > The problem is 2.4 sucks, and with 2.6 we moved to doing things exactly like the other architectures Debian supports. One last thing to try that I can think of, is to add "sym53c8xx" to /etc/mkinitrd/modules. This is how it looks on my C3000: % cat /etc/mkinitrd/modules # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 tulip sym53c8xx Hope this helps, Regards, Kyle M. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FW: 2.4 -> 2.6
On Sat, Feb 26, 2005 at 12:17:26PM -0500, Harry Cochran wrote: > Thank you all very much! I now have a running 2.6.8-2-32-smp on my > J6000. I repartitioned sda to have the root right next to the f0 > partition (and the swap at the end) per Grant, No, that isn't what Grant said... The Boot HOWTO explains that the kernel image must be located within the first 2GB of the disk. The only sensible way to ensure this is to have a dedicated /boot partition, which is contained entirely within the first 2GB. This needn't be large -- a 64MB partition should be ample. In your case, it doesn't matter whether this is before or after the 1GB swap partition, but it must come before the large root (/) partition. AFAICS, although your new partition scheme may appear to be working, it may cease to work whenever the kernel is upgraded. (By swapping the partitions you are effectively doubling the amount of disk space from the first 2GB which is used for the root partition.) Hope that helps, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: FW: 2.4 -> 2.6
Thanks Stuart, When I started this whole process, I had a nice f0 /boot partition of 100MB that occupied the beginning sectors of my disk. When I did the reinstall, I couldn't get the installer to let me mount the f0 partition as /boot. Grant just told me about -e2. Onwards and upwards. Cheers, Harry -Original Message- From: Stuart Brady [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 5:55 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: FW: 2.4 -> 2.6 On Sat, Feb 26, 2005 at 12:17:26PM -0500, Harry Cochran wrote: > Thank you all very much! I now have a running 2.6.8-2-32-smp on my > J6000. I repartitioned sda to have the root right next to the f0 > partition (and the swap at the end) per Grant, No, that isn't what Grant said... The Boot HOWTO explains that the kernel image must be located within the first 2GB of the disk. The only sensible way to ensure this is to have a dedicated /boot partition, which is contained entirely within the first 2GB. This needn't be large -- a 64MB partition should be ample. In your case, it doesn't matter whether this is before or after the 1GB swap partition, but it must come before the large root (/) partition. AFAICS, although your new partition scheme may appear to be working, it may cease to work whenever the kernel is upgraded. (By swapping the partitions you are effectively doubling the amount of disk space from the first 2GB which is used for the root partition.) Hope that helps, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FW: 2.4 -> 2.6
On Sat, Feb 26, 2005 at 08:11:37PM -0500, Harry Cochran wrote: > Are you saying that I need an f0 partition and then another partition of > 64MB that I mount as /boot? That's what I was saying, but it's the old way of dealing with the problem. > I've never seen this in any of the examples, but the installer won't let > me mount an f0 partition at all and I have to say I don't understand > Grants -e2 hint. If I've understood correctly, the new approach is to format the Palo (f0) partition as ext2 (using the -e2 option to palo) and then use that as /boot, instead of having an extra partition. I haven't tried this, so I'm not the best person to ask about it. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
