Re: installing kernel-image
Ionut Georgescu [EMAIL PROTECTED] writes: boot dka0 -flags 0 There is also an environment variable with which one can set the default flags. IIRC, it is called bootdef_flags; in any case, show boot* ought to display it.
installing kernel-image
Hi, I'm first trying again the kernel-image of 2.4.21. I did a apt-get for the kernel-image, and got told to configure my bootloader. It already happened to me when trying to install a kernel-image, that the machine wouldn't come up again (I have no root I want to scream). So before rebooting I want to be sure to have everything correct ;) What I find a bit confusing, is that I now have a link /initrd.img that points to a initrd in /boot. So far so good, but I can't find any reference to that initrd.img elsewhere. I think at boot time the bootloader needs to know what initrd to load? My /etc/abbot.conf just looks like this: 0:2/vmlinuz ro root=/dev/rd/c0d0p2 is that enough? On my last install try I think my problem was that initrd.img was not loaded... Lars
RE: installing kernel-image
What I find a bit confusing, is that I now have a link /initrd.img that points to a initrd in /boot. So far so good, but I can't find any reference to that initrd.img elsewhere. I think at boot time the bootloader needs to know what initrd to load? My /etc/abbot.conf just looks like this: what I forgot: I also have an empty directory /initrd Lars
Re: installing kernel-image
You have to pass the path to the initrd image. aboot.conf here: 0:1/boot/vmlinuz-2.4.20 ro root=/dev/sda1 initrd=/boot/initrd-2.4.20 1:1/boot/vmlinuz-2.4.18 ro root=/dev/sda1 initrd=/boot/initrd-2.4.18 Ionut On Tue, Jul 15, 2003 at 01:16:39PM +0200, [EMAIL PROTECTED] wrote: Hi, I'm first trying again the kernel-image of 2.4.21. I did a apt-get for the kernel-image, and got told to configure my bootloader. It already happened to me when trying to install a kernel-image, that the machine wouldn't come up again (I have no root I want to scream). So before rebooting I want to be sure to have everything correct ;) What I find a bit confusing, is that I now have a link /initrd.img that points to a initrd in /boot. So far so good, but I can't find any reference to that initrd.img elsewhere. I think at boot time the bootloader needs to know what initrd to load? My /etc/abbot.conf just looks like this: 0:2/vmlinuz ro root=/dev/rd/c0d0p2 is that enough? On my last install try I think my problem was that initrd.img was not loaded... Lars -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- *** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * In Windows you can do everything Microsoft wants you to do; in Unix you *can do anything the computer is able to do.
RE: installing kernel-image
You have to pass the path to the initrd image. aboot.conf here: ok, I think I'm understanding the boot process more now. Just in case, I want to make a second boot configuration with the old kernel. While I have vmlinuz-2.2.20-generic in /boot, I can't find any initrd but the new ones. Did 2.2.20 not use an initrd? Or did it get deleted while installing the new kernel-image? Another question is, how can I select another boot-configuration at boot time? I configured aboot to automatically boot vmlinuz... Lars
Re: installing kernel-image
Debian did not use initrd per default with 2.2.x. Was it possible ? Actually you cannot define a default boot configuration with aboot.conf. You just define several boot scenarios, identified by the first number in the line: 0, 1, 2 etc. You choose a specific scenario at the SRM console: boot dka0 -flags 0 or boot dka0 -flags 1 or boot dka0 -flags l The flags are passed over to aboot. So -flags l will let aboot display the configured scenarios and give you a command line. Ionut On Tue, Jul 15, 2003 at 01:28:13PM +0200, [EMAIL PROTECTED] wrote: You have to pass the path to the initrd image. aboot.conf here: ok, I think I'm understanding the boot process more now. Just in case, I want to make a second boot configuration with the old kernel. While I have vmlinuz-2.2.20-generic in /boot, I can't find any initrd but the new ones. Did 2.2.20 not use an initrd? Or did it get deleted while installing the new kernel-image? Another question is, how can I select another boot-configuration at boot time? I configured aboot to automatically boot vmlinuz... Lars -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- *** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * In Windows you can do everything Microsoft wants you to do; in Unix you *can do anything the computer is able to do.
AW: installing kernel-image
hm, what I feared happened, the machine doesn't boot that kernel. A bit of thinking would have made that obvious to me, I have root=/dev/rd/c0d0p2 in aboot, but without DAC960 support in the kernel, it can't be mounted at boot time. A boot drb0 -flags 1 (which points to my 2.2.20 kernel) doesn't work correct, since aboot tells me it doesn't know what to do with the first partition (swap) fortunately, I could get up again with p 2 (pointing to partition 2) and 1 (using aboot config 1) in aboot. Seems I really have to compile that kernel ;) Lars
Re: AW: installing kernel-image
A boot drb0 -flags 1 (which points to my 2.2.20 kernel) doesn't work correct, since aboot tells me it doesn't know what to do with the first partition (swap) fortunately, I could get up again with p 2 (pointing to partition 2) and 1 (using aboot config 1) in aboot. Seems I really have to compile that kernel ;) Sounds like you must have installed a new copy of aboot at some time on the front of your drive (i.e. did a 'swriteboot /dec/sda bootlx' -- bootlx is built with the Alpha kernel and contains the aboot image). If you were doing repartitioning, etc, make sure you left space at the front of the drive for aboot (the swriteboot man page advises you leave 512 sectors). Otherwise there will be problems once Linux starts using that swap partition. :) In any event, the problem is that your newly installed aboot is configured by default to look for your /etc/aboot.conf file on the first partition. Use 'abootconf /dev/sda 2' to change that to the second partition. You will have to change the /dev/sda bit to your correct boot device. -T -- Tyson Whitehead ([EMAIL PROTECTED] -- WSC-) Computer Engineer Dept. of Applied Mathematics, Graduate Student- Applied Mathematics University of Western Ontario, GnuPG Key ID# 0x8A2AB5D8 London, Ontario, Canada
Re: AW: installing kernel-image
Am Dienstag, 15. Juli 2003 15:14 schrieb Tyson Whitehead: Sounds like you must have installed a new copy of aboot at some time on the front of your drive (i.e. did a 'swriteboot /dec/sda bootlx' -- bootlx is built with the Alpha kernel and contains the aboot image). hm, I installed aboot when installing woody. If you were doing repartitioning, etc, make sure you left space at the front of the drive for aboot (the swriteboot man page advises you leave 512 sectors). Otherwise there will be problems once Linux starts using that swap partition. :) I left that space back then... Until now, Linux seems not to have a problem using that swap partition. In any event, the problem is that your newly installed aboot is configured by default to look for your /etc/aboot.conf file on the first partition. Use 'abootconf /dev/sda 2' to change that to the second partition. I guess a 'abootconf /dev/c0d0p2' will do the correct thing for me, since I boot from a raid? You will have to change the /dev/sda bit to your correct boot device. uh, what? Lars
Re: AW: installing kernel-image
On Tuesday 15 July 2003 09:24, Lars Oeschey wrote: I guess a 'abootconf /dev/c0d0p2' will do the correct thing for me, since I boot from a raid? That is: abootconf device num device- The linux device representing the drive on which /etc/aboot.conf is stored. num- The partition number on which /etc/aboot.conf is stored. For my machine it would be 'abootconf /dev/sda 1' because /etc/aboot.conf is on the first SCSI drive (/dev/sda), partition 1. -T PS: Note that the device is the drive (i.e. /dev/sda) not the partition on the drive (i.e. /dev/sda1). The parition number is given as the second paramater. The program modifies the configuration info in the aboot image that resides on the first several sectors of the drive. -- Tyson Whitehead ([EMAIL PROTECTED] -- WSC-) Computer EngineerDept. of Applied Mathematics, Graduate Student- Applied MathematicsUniversity of Western Ontario, GnuPG Key ID# 0x8A2AB5D8 London, Ontario, Canada
