Re: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
On Sat, Mar 05, 2005 at 06:52:57PM -0500, Harry Cochran wrote: d. Assuming your f0 partition is on sda1, mount /dev/sda1 mnt This should have been /mnt. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
Thanks Stuart, Got it. Either mount /dev/sda1 /mnt or cd / and then mount /dev/sda1 mnt obviously do it, but rather than fixing my mistake with a cd, it's certainly better to just mount /dev/sda1 /mnt. Cheers, Harry -Original Message- From: Stuart Brady [mailto:[EMAIL PROTECTED] Sent: Sunday, March 06, 2005 6:32 AM To: debian-hppa@lists.debian.org Subject: Re: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6 On Sat, Mar 05, 2005 at 06:52:57PM -0500, Harry Cochran wrote: d. Assuming your f0 partition is on sda1, mount /dev/sda1 mnt This should have been /mnt. -- 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]
PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
Hi, I'm sure you're way beyond my rough scrawl, but I found one small baby step that I left out (8.3 c) and I want to make sure that whatever goes out is complete to the lowest level of detail. Thanks, Harry 8. Upgrading from a Debian hppa 2.4 Kernel to a 2.6 kernel 8.1 Check your 2.4 partition scheme 8.2 First Steps 8.3 Set up f0 as /boot if necessary 8.4 Edit /etc/palo.conf 8.5 Before you reboot 8.6 Conclusion 8.1 Check your 2.4 partition scheme It is relatively easy to set up a partition scheme that will work for a while, but then stop working when root starts to fill up. For example: 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 root Don't despair. There is a way to tell palo to format your f0 partition, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot (See 8.3). Here's an example that works: Disk /dev/sda: 73.4 GB, 73407865856 bytes 255 heads, 63 sectors/track, 8924 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 *1 24 192748+ f0 Linux/PA-RISC boot /dev/sda2 25 148 996030 82 Linux swap /dev/sda3 149 214016000740 83 Linux /dev/sda4 2141 892454492480 83 Linux and here's the palo.conf that goes with it: --commandline=0/vmlinux-2.6.11-rc2-pa3-UP root=/dev/sda3 panic=5 console=ttyS1 --update-partitioned=/dev/sda 8.2 First steps I'm the conservative type, so I don't load from unstable. At the time of this writing, the 2.6 kernels in testing are 2.6.8-2-32, 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. Step 1 For example, apt-get install kernel-image-2.6.8-2-32-smp. When you get near the end of the install, you will get messages telling you that this is an initrd kernel and asking you if you want to abort. At this point say, Yes. Now it's time for: Step 2 you need to add sym53c8xx to /etc/mkinitrd/modules. modules is created from /etc/mkinitrd/modules.dpkg-new. This is how it looks after editing: % cat /etc/mkinitrd/modules.dpkg-new # /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 Okay. Now we are ready for: Step 3 apt-get install kernel-image-2.6.8-2-32-smp again, but this time when asked if you want to abort, say, No. Step 4 Run apt-get upgrade Step 5 Run palo -? and make sure your palo has -format-as=type 8.3 Set up f0 as /boot if necessary One of the weaknesses of the current hppa installer is that it won't let you mount the f0 partition as /boot. If you created a small (50MB-200MB) ext2 partition and mounted it as /boot during the install process, you can skip this section and go to 8.4. If not, and you have a / that goes out beyond 2GB from the beginning of your disk, here is your salvation. Of course, if you're starting from scratch, you can set up an f0 and an ext2 partition that you mount as /boot, but the preferred partitioning scheme is to just set up one f0 partition during installation (at least 50MB for a production system and say 200MB for a development system) and then use palo to format it, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot. Here's what to do: a. Edit /etc/palo.conf, on the --commandline change your pointer to vmlinux to 1/vmlinux and insert initrd=1/initrd.img. Add a line that says --format-as=2 Leave the line that says --init-partitioned=/dev/sda (or similar) Remove the line that says --recoverykernel=/boot/vmlinux.old (or similar) b. Now run palo. This will format your f0 partition. c. cd / d. Assuming your f0 partition is on sda1, mount /dev/sda1 mnt e. cp /boot/* /mnt f. edit /etc/fstab so that /dev/sda1 is mounted as /boot by adding this line: # file system mount point type optionsdump pass /dev/sda1 /boot ext2defaults 0 2 g. Edit /etc/palo.conf and remove the --format-as=2 line and change the --init-partitioned=/dev/sda to --update-partitioned=dev/sda. h. Now run palo. i. Reboot. If this fails, look at 8.4, go back over the steps above and try again. If it works, j. Run /etc/init.d/klogd stop (if you dont stop klogd, youll get device is busy when you try to umount /boot in the next step) k. umount /boot l. rm /boot/* m. mount /boot If you get through step m., you're done. 8.4 Edit /etc/palo.conf Edit /etc/palo.conf and insert on the --commandline
Re: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
--- On Sun, Feb 27, 2005 at 02:05:45PM -0500, Harry Cochran wrote: 8.1 Check your 2.4 partition scheme It is relatively easy to set up a partition scheme that will work for a while, but then stop working when root starts to fill up. For example: This was due to using an incorrect partition scheme in the first place. I'm not sure that this belongs in a HOWTO that explains how to upgrade from 2.4 to 2.6. That issue is clearly mentionned in the PA-RISC/Linux Boot HOWTO already (maybe with a poor wording though, I'll fix that in the next release): http://www.pateam.org/parisc-linux-boot/PA-RISC-Linux-Boot-HOWTO/paloa ppusage.html#bootablepartition Beware ! Your vmlinux has also to be located within the first 2GB of the hard disk. We strongly recommend to create a separated /boot partition at the front of the disk if your '/' is bigger than that, because if ever your vmlinux goes above the first 2GB of the disk (like when filling up '/' with data), the box won't boot anymore. As for the upgrade from 2.4 to 2.6, it doesn't belong to that howto per se if you are only considering the Debian kernels. This HOWTO is not a Use Debian On A PA-RISC Machine HOWTO. That said, there are a few things that could be interesting to have in the howto wrt kernel upgrade (especially the SCSI disks naming change, and a few new features) that I'll probably add somewhere in appendix. Documentation explaining how to use the palo partition as the /boot partition seems worth having, but it's surely a separate issue. I'm the conservative type, so I don't load from testing. At the time of this writing, the 2.6 kernels in unstable are 2.6.8-2-32, 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. I don't get this -- testing is safer than unstable. Yeah. Maybe someone needs to RTFM: http://www.debian.org/releases/testing/ HTH Thibaut VARENE PA/Linux ESIEE Team http://www.pateam.org/
Re: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
--- Documentation explaining how to use the palo partition as the /boot partition seems worth having, but it's surely a separate issue. In /usr/share/doc/palo/README perhaps? Indeed, this should be updated. In any case, since palo usage is already documented in the howto, I'll add whatever is suitable to detail -e[2|3] use. HTH Thibaut VARENE PA/Linux ESIEE Team http://www.pateam.org/
PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
On Sun, Feb 27, 2005 at 02:05:45PM -0500, Harry Cochran wrote: 8.1 Check your 2.4 partition scheme It is relatively easy to set up a partition scheme that will work for a while, but then stop working when root starts to fill up. For example: This was due to using an incorrect partition scheme in the first place. I'm not sure that this belongs in a HOWTO that explains how to upgrade from 2.4 to 2.6. Documentation explaining how to use the palo partition as the /boot partition seems worth having, but it's surely a separate issue. I'm the conservative type, so I don't load from testing. At the time of this writing, the 2.6 kernels in unstable are 2.6.8-2-32, 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. I don't get this -- testing is safer than unstable. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
On Mon, Feb 28, 2005 at 12:36:50AM +, Stuart Brady wrote: On Sun, Feb 27, 2005 at 02:05:45PM -0500, Harry Cochran wrote: 8.1 Check your 2.4 partition scheme It is relatively easy to set up a partition scheme that will work for a while, but then stop working when root starts to fill up. For example: This was due to using an incorrect partition scheme in the first place. I'm not sure that this belongs in a HOWTO that explains how to upgrade from 2.4 to 2.6. I agree. Maybe we need a FAQ for I upgraded my kernel and now it doesn't work? Documentation explaining how to use the palo partition as the /boot partition seems worth having, but it's surely a separate issue. In /usr/share/doc/palo/README perhaps? -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
On Sun, Feb 27, 2005 at 02:05:45PM -0500, Harry Cochran wrote: 8.1 Check your 2.4 partition scheme It is relatively easy to set up a partition scheme that will work for a while, but then stop working when root starts to fill up. For example: On Sun, Feb 27, 2005 at 07:36:45PM -0500, Stuart Brady wrote: This was due to using an incorrect partition scheme in the first place. I'm not sure that this belongs in a HOWTO that explains how to upgrade from 2.4 to 2.6. Documentation explaining how to use the palo partition as the /boot partition seems worth having, but it's surely a separate issue. From a newbie point of view, I think it's important to know that you might have a partition scheme where you are booting something like 3/boot/vmlinux that might just stop working if root starts to fill up and because of format-as=2 you have a chance to fix it on a 2.6 upgrade. I'm the conservative type, so I don't load from testing. At the time of this writing, the 2.6 kernels in unstable are 2.6.8-2-32, 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. I don't get this -- testing is safer than unstable. Thanks Stuart, I finally sat down and read the explanation of unstable and testing. Someone else told me that unstable was more reliable that testing which clearly isn't the case. Sorry for putting my misunderstanding in the document. Regards, Harry -- 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]
