[newbie] lilo v21.5
I've now discovered that my lilo problem is probably down to the fact that I have an olde version of lilo. Can some one point me in the right direction of how to obtain lilo v.21.5, and also where I might find out the process by which I upgrade lilo.
RE: [newbie] lilo config problems
> Hi Sean > > Change the default setting to "windows" minus the quotes of course giving > you a line that reads: > default =windows That what i have been attempting to do using the emacs editor, but every time I run /sbin/lilo to get lilo to accept the edited changes I get the cylinder error message I spoke of. > as for the cylinder error. I had a similar error when I disabled > lba during > installation. I take it windows on your system has something like the 1st > 8gig of the HD? If so, look for where you are asked about lba > suuport during > installation. I can't recall exactly where it was now, but I suspect that > may solve the prob. Windows ME actually takes up the first 4 gb of my HD and Mandrake the remaining 4GB, am I going to have to reinstall again? > James > > - Original Message - > From: "Sean Kenny" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 19, 2001 8:52 AM > Subject: [newbie] lilo config problems > > > > Here's my lilo.conf file and below is the problem I'm having > > > > boot=/dev/hda > > map=/boot/map > > install=/boot/boot.b > > default=linux > > keytable=/boot/uk.klt > > lba32 > > prompt > > timeout=50 > > message=/boot/message > > image=/boot/vmlinuz > > label=linux > > root=/dev/hda7 > > append=" hdb=ide-scsi" > > read-only > > image=/boot/vmlinuz > > label=failsafe > > root=/dev/hda7 > > append=" hdb=ide-scsi failsafe" > > read-only > > other=/dev/hda1 > > label=windows > > table=/dev/hda > > other=/dev/fd0 > > label=floppy > > unsafe > > > > I want to change this to boot into Windows by default, while I'm > familairising > > myself with Mandrake, and because the kids insist, but whether I do this > in > > Klilo or edit it myself in emacs and run /sbin/lilo I get the following > error > > message > > > > warning: device 0x0307 exceeds 1204 cylinder limit > > Fatal: geo_comp_addr: Cylinder number is too big (2991 > 1023) > > > > Wgat does this mean and how can I get around it? > > >
[newbie] test
Apolgies test newbie list - I've posted acouple of times from kmail and they haven't appeared, although other stuff seems to get through.
[newbie] lilo config problems
Here's my lilo.conf file and below is the problem I'm having boot=/dev/hda map=/boot/map install=/boot/boot.b default=linux keytable=/boot/uk.klt lba32 prompt timeout=50 message=/boot/message image=/boot/vmlinuz label=linux root=/dev/hda7 append=" hdb=ide-scsi" read-only image=/boot/vmlinuz label=failsafe root=/dev/hda7 append=" hdb=ide-scsi failsafe" read-only other=/dev/hda1 label=windows table=/dev/hda other=/dev/fd0 label=floppy unsafe I want to change this to boot into Windows by default, while I'm familairising myself with Mandrake, and because the kids insist, but whether I do this in Klilo or edit it myself in emacs and run /sbin/lilo I get the following error message warning: device 0x0307 exceeds 1204 cylinder limit Fatal: geo_comp_addr: Cylinder number is too big (2991 > 1023) Wgat does this mean and how can I get around it?
[newbie] lilo config problems
Here's my lilo.conf file and below is the problem I'm having boot=/dev/hda map=/boot/map install=/boot/boot.b default=linux keytable=/boot/uk.klt lba32 prompt timeout=50 message=/boot/message image=/boot/vmlinuz label=linux root=/dev/hda7 append=" hdb=ide-scsi" read-only image=/boot/vmlinuz label=failsafe root=/dev/hda7 append=" hdb=ide-scsi failsafe" read-only other=/dev/hda1 label=windows table=/dev/hda other=/dev/fd0 label=floppy unsafe I want to change this to boot into Windows by default, while I'm familairising myself with Mandrake, and because the kids insist, but whether I do this in Klilo or edit it myself in emacs and run /sbin/lilo I get the following error message warning: device 0x0307 exceeds 1204 cylinder limit Fatal: geo_comp_addr: Cylinder number is too big (2991 > 1023) What does this mean and how can I get around it?
RE: [newbie] configuring LILO.
> make it /dev/hda1 or /dev/hda? .. and being a real newbie, what exactly am I changing to the above ... and how? > Op maandag 15 januari 2001 18:57, schreef u: > > > > Klilo keeps telling me my Hd is too big for it to > reconfigure the boot > > > > sequence, and although I've edited lilo.conf I still can't get > > > > > > my machine to > > > > > > > boot into the win partition by default, lilo seems to be > > > > > > ignoring the edit > > > > > > > I've done. Have I missed something? > > > > > > Here's the first bit of lilo.conf: > > > > > > boot = /dev/hda > > > map = /boot/map > > > timeout = 50 > > > prompt > > > message = /boot/message > > > default = linux > > > > > > That last line should read whatever you've name your Windows > > > partition in /etc/fstab. If you've done that, & it's still not > > > working, try editing the file again, but this time, as root, run: > > > > > > # /sbin/lilo > > > > > > That, instead of using klilo, should do it. > > > > .. and so I thought too. Unfortunatly I'm getting the same error message > > that I got from lilo about > > the HDD being too big. Any other ideas? > > -- > Luk Vermeylen > Putse Baan 84 > 2040 Antwerpen 4 > 03/295.00.12 > [EMAIL PROTECTED] > linux counter: #186539 >
[newbie] META - how the list works
For every post I make I get a bounce, but the same post turns up on the list anyway, anyone know why this might be?
RE: [newbie] configuring LILO.
> > Klilo keeps telling me my Hd is too big for it to reconfigure the boot > > sequence, and although I've edited lilo.conf I still can't get > my machine to > > boot into the win partition by default, lilo seems to be > ignoring the edit > > I've done. Have I missed something? > > Here's the first bit of lilo.conf: > > boot = /dev/hda > map = /boot/map > timeout = 50 > prompt > message = /boot/message > default = linux > > That last line should read whatever you've name your Windows > partition in /etc/fstab. If you've done that, & it's still not > working, try editing the file again, but this time, as root, run: > > # /sbin/lilo > > That, instead of using klilo, should do it. .. and so I thought too. Unfortunatly I'm getting the same error message that I got from lilo about the HDD being too big. Any other ideas?
[newbie] configuring LILO.
Klilo keeps telling me my Hd is too big for it to reconfigure the boot sequence, and although I've edited lilo.conf I still can't get my machine to boot into the win partition by default, lilo seems to be ignoring the edit I've done. Have I missed something? Sean
[newbie] test
test