Did a new install on my home box this evening and it worked like a charm save for two issue, which are the display of 3 floppy drives - I only have one 3.5 / 5.25 combo - and an extra CD-ROM plus a failed boot disk. As I didn't want to disturb my current SuSE 7.1 setup, and as I was installing to a third HD, I elected the boot floppy option vice the mbr approach. All seemed to have worked as advertised and YaST said the boot floppy was properly made. So I finished the setup and tried booting from the floppy. ALL I get from the floppy boot attempt is a screen of scrolling alternating ones and zeros. Not a major problem in and of itself as my intention was to add the new system to my current lilo and have the 8.0 as one menu option along with 7.1, windows, and memtest. Only I'm unsure as to how I properly write the section in lilo.conf. Current lilo.conf looks like this although I'm leaving out a lot of stuff (the section below is the default bootup): boot = /dev/sda . . . . image = /boot/vmlinuz_24 label = linux_2.4 root = /dev/sdb3 initrd = /boot/initrd_24 optional . . . Now, if I want to add a section to offer the new install as an option, I was thinking of a section that looks like the following. Please let me know if this is the correct approach or where I am in error. This new install is on the 3rd of 4 SCSI drives hence the sdc. . . . image = /boot/vmlinuz_24 label = SuSE_8.0 root = /dev/sdc3 initrd = /boot/initrd_24 optional I'm guessing that the first and fourth lines as written above are not correct but I don't know what else to put there. Any help greatly appreciated. I want to leave the 7.1 version as my default boot up. tia, dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
Well the root device is ok - but you are trying to boot the same kernel "image = /boot/vmlinuz_24" Your new install has its own kernel -as does the old. Copies of both these should be in /boot (/dev/sda) as that is where lilo is saying they are going to be. This way you do not have to worry about the floppy. Brian Marr image = /boot/vmlinuz.old label = Suse 7.1 root = /dev/sdb3 #initrd = /boot/initrd_24 optional image = /boot/vmlinuz_24 label = SuSE_8.0 root = /dev/sdc3 initrd = /boot/initrd optional On Sunday 28 July 2002 11:16, you wrote:
Did a new install on my home box this evening and it worked like a charm save for two issue, which are the display of 3 floppy drives - I only have one 3.5 / 5.25 combo - and an extra CD-ROM plus a failed boot disk.
As I didn't want to disturb my current SuSE 7.1 setup, and as I was installing to a third HD, I elected the boot floppy option vice the mbr approach. All seemed to have worked as advertised and YaST said the boot floppy was properly made. So I finished the setup and tried booting from the floppy. ALL I get from the floppy boot attempt is a screen of scrolling alternating ones and zeros. Not a major problem in and of itself as my intention was to add the new system to my current lilo and have the 8.0 as one menu option along with 7.1, windows, and memtest. Only I'm unsure as to how I properly write the section in lilo.conf.
Current lilo.conf looks like this although I'm leaving out a lot of stuff (the section below is the default bootup):
boot = /dev/sda . . . . image = /boot/vmlinuz_24 label = linux_2.4 root = /dev/sdb3 initrd = /boot/initrd_24 optional . . .
Now, if I want to add a section to offer the new install as an option, I was thinking of a section that looks like the following. Please let me know if this is the correct approach or where I am in error. This new install is on the 3rd of 4 SCSI drives hence the sdc.
. . .
image = /boot/vmlinuz_24 label = SuSE_8.0 root = /dev/sdc3 initrd = /boot/initrd_24 optional
I'm guessing that the first and fourth lines as written above are not correct but I don't know what else to put there. Any help greatly appreciated. I want to leave the 7.1 version as my default boot up.
tia,
dave
Hello I have been trying to get ACPI power management to work in linux. In all my research, I have found on my particular laptop it may be beneficial to install ACPI as modules in the kernel. My only problem is I do not know how to load them into the running kernel. I know to use insmod then the name but I do not know the names! Can anybody assist me in locating the names of these modules or know them off the top of their head? Thanks for Your Help!
Hi there, Well you can see what modules were built for your kernel by looking in: /lib/modules/`uname -r`/kernel/drivers/acpi Kind regards, Simon A.MAINS wrote:
Hello
I have been trying to get ACPI power management to work in linux. In all my research, I have found on my particular laptop it may be beneficial to install ACPI as modules in the kernel.
My only problem is I do not know how to load them into the running kernel. I know to use insmod then the name but I do not know the names!
Can anybody assist me in locating the names of these modules or know them off the top of their head?
Thanks for Your Help!
participants (4)
-
A.MAINS -
Brian Marr -
David Johanson -
Simon Heaton