Re: Megatrends Bootable ?

Re: Megatrends Bootable ?

[Andrew B. Cramer]

Hi Glenn,
	I have read, and have been compiling kernels for quite some time. I 
mirror the HOWTO's and will go back and re-check again.

On 16 Mar 2003 at 16:59, -Glenn- wrote:

> andrew.cramer@cramer-ts.com wrote:
> > Good evening,
> >     I'm using Slackware 8.1 w/ the raid.s boot disk, I install Linux 
> > 2.4.18 and when I reboot the screen fills with '40' all over the 
> > place. If I boot from a disk and mount root=/dev/sda ro it boots but 
> > from the kernel on the floppy. Any advice would be greatly 
> > appreciated.
> > 
> 
> Installing a kernel isn't like installing an app.  A kernel needs to be 
> compiled for your system.  Your boot device, LILO/GRUB, is still looking 
> for the old kernel configuration, hence the success in booting from the 
> floppy & the bogus 40's pattern on your screen while trying from your HDD.
> 
> Hop on over to www.linux.org & check out the docs, HOW-TO's, tutorials 
> on how to compile a kernel.  It sure helped me 'cause I did the same 
> thing & it drove me nuts for 2 days to the point that I had to 
> re-install & then I went to the docs, etc.
> 
> I guess I'm too much of a man 'cause I never ask for directions - ROTFL!!
> 
> Good Luck  .  .  .
> 
>                     Sincerely,
> 
>                             -Glenn-
> 
> -- 
> The advantage of exercising every day is that you die healthier.
> ========
> Registered Linux User No. 306834
> 

Megatrends Bootable ?

[Andrew B. Cramer]

Good evening,
	I'm using Slackware 8.1 w/ the raid.s boot disk, I install Linux 
2.4.18 and when I reboot the screen fills with '40' all over the 
place. If I boot from a disk and mount root=/dev/sda ro it boots but 
from the kernel on the floppy. Any advice would be greatly 
appreciated.

Cheers - Andrew

Re: Megatrends Bootable ?

[The ServSwitch]

	It appears to be a missing device in lilo.conf. Is your lilo
configuration ok?

On Sun, 2003-03-16 at 02:22, Andrew B. Cramer wrote:
> Good evening,
> 	I'm using Slackware 8.1 w/ the raid.s boot disk, I install Linux 
> 2.4.18 and when I reboot the screen fills with '40' all over the 
> place. If I boot from a disk and mount root=/dev/sda ro it boots but 
> from the kernel on the floppy. Any advice would be greatly 
> appreciated.
> 
> Cheers - Andrew
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

_______________________________________________________________________
Busca Yahoo!
O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
http://br.busca.yahoo.com/

Re: Megatrends Bootable ?

[Andrew B. Cramer]

Seems to be. If you have done this, could you send me a clip of what 
I may need to add?

On 16 Mar 2003 at 10:14, The ServSwitch wrote:

> 	It appears to be a missing device in lilo.conf. Is your lilo
> configuration ok?
> 
> On Sun, 2003-03-16 at 02:22, Andrew B. Cramer wrote:
> > Good evening,
> > 	I'm using Slackware 8.1 w/ the raid.s boot disk, I install Linux 
> > 2.4.18 and when I reboot the screen fills with '40' all over the 
> > place. If I boot from a disk and mount root=/dev/sda ro it boots but 
> > from the kernel on the floppy. Any advice would be greatly 
> > appreciated.
> > 
> > Cheers - Andrew
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> _______________________________________________________________________
> Busca Yahoo!
> O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> http://br.busca.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Megatrends Bootable ?

[Andrew B. Cramer]

HI ServSwitch,
	Here is my lilo.conf

Thanks - Andrew

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Linux
  read-only
# Linux bootable partition config ends

Re: Megatrends Bootable ?

[The ServSwitch]

	Humm... Your lilo.conf is great. So the problem could be when lilo
writes informations at mbr. What is the model of your megatrends
controler? What is the model of your hard drive? Have you tried boot
with a floppy disk and execute "# lilo" as root? A error message could
show the problem.

On Sun, 2003-03-16 at 15:13, Andrew B. Cramer wrote:
> HI ServSwitch,
> 	Here is my lilo.conf
> 
> Thanks - Andrew
> 
> # LILO configuration file
> # generated by 'liloconfig'
> #
> # Start LILO global section
> boot = /dev/sda
> message = /boot/boot_message.txt
> prompt
> timeout = 1200
> # Override dangerous defaults that rewrite the partition table:
> change-rules
>   reset
> # Normal VGA console
> vga = normal
> # VESA framebuffer console @ 1024x768x64k
> # vga=791
> # VESA framebuffer console @ 1024x768x32k
> # vga=790
> # VESA framebuffer console @ 1024x768x256
> # vga=773
> # VESA framebuffer console @ 800x600x64k
> # vga=788
> # VESA framebuffer console @ 800x600x32k
> # vga=787
> # VESA framebuffer console @ 800x600x256
> # vga=771
> # VESA framebuffer console @ 640x480x64k
> # vga=785
> # VESA framebuffer console @ 640x480x32k
> # vga=784
> # VESA framebuffer console @ 640x480x256
> # vga=769
> # End LILO global section
> # Linux bootable partition config begins
> image = /boot/vmlinuz
>   root = /dev/sda1
>   label = Linux
>   read-only
> # Linux bootable partition config ends
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

_______________________________________________________________________
Busca Yahoo!
O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
http://br.busca.yahoo.com/

Re: Megatrends Bootable ?

[Andrew B. Cramer]

Hi,
	Thanks. #lilo and # lilo comes back without anything. It's a 928 
controler with a Seagate 73gig ultra/wide drive. I am able to get, 
and I'm afraid to say it, but Dos-6.22, Win95, Win98, WinNT, and 
Win2000. It boots fine with those. I wonder if Linux is seeing the 
drive as a striped single unit?

On 16 Mar 2003 at 18:08, The ServSwitch wrote:

> 	Humm... Your lilo.conf is great. So the problem could be when lilo
> writes informations at mbr. What is the model of your megatrends
> controler? What is the model of your hard drive? Have you tried boot
> with a floppy disk and execute "# lilo" as root? A error message could
> show the problem.
> 
> On Sun, 2003-03-16 at 15:13, Andrew B. Cramer wrote:
> > HI ServSwitch,
> > 	Here is my lilo.conf
> > 
> > Thanks - Andrew
> > 
> > # LILO configuration file
> > # generated by 'liloconfig'
> > #
> > # Start LILO global section
> > boot = /dev/sda
> > message = /boot/boot_message.txt
> > prompt
> > timeout = 1200
> > # Override dangerous defaults that rewrite the partition table:
> > change-rules
> >   reset
> > # Normal VGA console
> > vga = normal
> > # VESA framebuffer console @ 1024x768x64k
> > # vga=791
> > # VESA framebuffer console @ 1024x768x32k
> > # vga=790
> > # VESA framebuffer console @ 1024x768x256
> > # vga=773
> > # VESA framebuffer console @ 800x600x64k
> > # vga=788
> > # VESA framebuffer console @ 800x600x32k
> > # vga=787
> > # VESA framebuffer console @ 800x600x256
> > # vga=771
> > # VESA framebuffer console @ 640x480x64k
> > # vga=785
> > # VESA framebuffer console @ 640x480x32k
> > # vga=784
> > # VESA framebuffer console @ 640x480x256
> > # vga=769
> > # End LILO global section
> > # Linux bootable partition config begins
> > image = /boot/vmlinuz
> >   root = /dev/sda1
> >   label = Linux
> >   read-only
> > # Linux bootable partition config ends
> > 
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> _______________________________________________________________________
> Busca Yahoo!
> O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> http://br.busca.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Megatrends Bootable ?

[The ServSwitch]

	Is your scsi board made by american megatrends? I cannot find any
specifications about it. Do me a favor execute a /sbin/lspci and cut and
paste the result please. Do you know how scsi driver linux are using in
your system to control that scsi board?

On Sun, 2003-03-16 at 18:24, Andrew B. Cramer wrote:
> Hi,
> 	Thanks. #lilo and # lilo comes back without anything. It's a 928 
> controler with a Seagate 73gig ultra/wide drive. I am able to get, 
> and I'm afraid to say it, but Dos-6.22, Win95, Win98, WinNT, and 
> Win2000. It boots fine with those. I wonder if Linux is seeing the 
> drive as a striped single unit?
> 
> On 16 Mar 2003 at 18:08, The ServSwitch wrote:
> 
> > 	Humm... Your lilo.conf is great. So the problem could be when lilo
> > writes informations at mbr. What is the model of your megatrends
> > controler? What is the model of your hard drive? Have you tried boot
> > with a floppy disk and execute "# lilo" as root? A error message could
> > show the problem.
> > 
> > On Sun, 2003-03-16 at 15:13, Andrew B. Cramer wrote:
> > > HI ServSwitch,
> > > 	Here is my lilo.conf
> > > 
> > > Thanks - Andrew
> > > 
> > > # LILO configuration file
> > > # generated by 'liloconfig'
> > > #
> > > # Start LILO global section
> > > boot = /dev/sda
> > > message = /boot/boot_message.txt
> > > prompt
> > > timeout = 1200
> > > # Override dangerous defaults that rewrite the partition table:
> > > change-rules
> > >   reset
> > > # Normal VGA console
> > > vga = normal
> > > # VESA framebuffer console @ 1024x768x64k
> > > # vga=791
> > > # VESA framebuffer console @ 1024x768x32k
> > > # vga=790
> > > # VESA framebuffer console @ 1024x768x256
> > > # vga=773
> > > # VESA framebuffer console @ 800x600x64k
> > > # vga=788
> > > # VESA framebuffer console @ 800x600x32k
> > > # vga=787
> > > # VESA framebuffer console @ 800x600x256
> > > # vga=771
> > > # VESA framebuffer console @ 640x480x64k
> > > # vga=785
> > > # VESA framebuffer console @ 640x480x32k
> > > # vga=784
> > > # VESA framebuffer console @ 640x480x256
> > > # vga=769
> > > # End LILO global section
> > > # Linux bootable partition config begins
> > > image = /boot/vmlinuz
> > >   root = /dev/sda1
> > >   label = Linux
> > >   read-only
> > > # Linux bootable partition config ends
> > > 
> > > 
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> > _______________________________________________________________________
> > Busca Yahoo!
> > O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> > http://br.busca.yahoo.com/
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 
> 

_______________________________________________________________________
Busca Yahoo!
O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
http://br.busca.yahoo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Megatrends Bootable ?

[p niemandt]

hiya:

Just FYI: I used to get this problem, {of 40's flooding the screen when
trying to install), when I tried to install Linux (RedHat, in my case),
on a hard drive with a previous FAT32 partition: Can't remember the
exact cause or solution, but it basically came down to the MBR (Master
Boot Record) of the disk that was screwed. 

What you can try, and this might be a dangerous route to follow, is just
to update your mbr, {in DOS, I did this using fdisk /mbr: This clears
the mbr, but does not damage any partition information.) Maybe do some
google on it.

I haven't had the problem in ages: but if I remember correctly it
usually was when I tried to install Linux on a partition which had the
FAT32/16 on, not when the FAT32 was on another partition.)

hope this helps, or gives some direction.
Paul



On Sun, 2003-03-16 at 21:47, The ServSwitch wrote:
> 	Is your scsi board made by american megatrends? I cannot find any
> specifications about it. Do me a favor execute a /sbin/lspci and cut and
> paste the result please. Do you know how scsi driver linux are using in
> your system to control that scsi board?
> 
> On Sun, 2003-03-16 at 18:24, Andrew B. Cramer wrote:
> > Hi,
> > 	Thanks. #lilo and # lilo comes back without anything. It's a 928 
> > controler with a Seagate 73gig ultra/wide drive. I am able to get, 
> > and I'm afraid to say it, but Dos-6.22, Win95, Win98, WinNT, and 
> > Win2000. It boots fine with those. I wonder if Linux is seeing the 
> > drive as a striped single unit?
> > 
> > On 16 Mar 2003 at 18:08, The ServSwitch wrote:
> > 
> > > 	Humm... Your lilo.conf is great. So the problem could be when lilo
> > > writes informations at mbr. What is the model of your megatrends
> > > controler? What is the model of your hard drive? Have you tried boot
> > > with a floppy disk and execute "# lilo" as root? A error message could
> > > show the problem.
> > > 
> > > On Sun, 2003-03-16 at 15:13, Andrew B. Cramer wrote:
> > > > HI ServSwitch,
> > > > 	Here is my lilo.conf
> > > > 
> > > > Thanks - Andrew
> > > > 
> > > > # LILO configuration file
> > > > # generated by 'liloconfig'
> > > > #
> > > > # Start LILO global section
> > > > boot = /dev/sda
> > > > message = /boot/boot_message.txt
> > > > prompt
> > > > timeout = 1200
> > > > # Override dangerous defaults that rewrite the partition table:
> > > > change-rules
> > > >   reset
> > > > # Normal VGA console
> > > > vga = normal
> > > > # VESA framebuffer console @ 1024x768x64k
> > > > # vga=791
> > > > # VESA framebuffer console @ 1024x768x32k
> > > > # vga=790
> > > > # VESA framebuffer console @ 1024x768x256
> > > > # vga=773
> > > > # VESA framebuffer console @ 800x600x64k
> > > > # vga=788
> > > > # VESA framebuffer console @ 800x600x32k
> > > > # vga=787
> > > > # VESA framebuffer console @ 800x600x256
> > > > # vga=771
> > > > # VESA framebuffer console @ 640x480x64k
> > > > # vga=785
> > > > # VESA framebuffer console @ 640x480x32k
> > > > # vga=784
> > > > # VESA framebuffer console @ 640x480x256
> > > > # vga=769
> > > > # End LILO global section
> > > > # Linux bootable partition config begins
> > > > image = /boot/vmlinuz
> > > >   root = /dev/sda1
> > > >   label = Linux
> > > >   read-only
> > > > # Linux bootable partition config ends
> > > > 
> > > > 
> > > > -
> > > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > > the body of a message to majordomo@vger.kernel.org
> > > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > 
> > > _______________________________________________________________________
> > > Busca Yahoo!
> > > O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> > > http://br.busca.yahoo.com/
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > 
> > 
> > 
> 
> _______________________________________________________________________
> Busca Yahoo!
> O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> http://br.busca.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
p niemandt <maudib@acesurfer.co.za>

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Megatrends Bootable ?

[Andrew B. Cramer]

Thanks Paul, did that first. Low-leveled the drive. Tried all the 
normal things, but no luck. I do have a current mirror of the HOWTO's 
and will have a look.

On 16 Mar 2003 at 22:04, p niemandt wrote:

> hiya:
> 
> Just FYI: I used to get this problem, {of 40's flooding the screen when
> trying to install), when I tried to install Linux (RedHat, in my case),
> on a hard drive with a previous FAT32 partition: Can't remember the
> exact cause or solution, but it basically came down to the MBR (Master
> Boot Record) of the disk that was screwed. 
> 
> What you can try, and this might be a dangerous route to follow, is just
> to update your mbr, {in DOS, I did this using fdisk /mbr: This clears
> the mbr, but does not damage any partition information.) Maybe do some
> google on it.
> 
> I haven't had the problem in ages: but if I remember correctly it
> usually was when I tried to install Linux on a partition which had the
> FAT32/16 on, not when the FAT32 was on another partition.)
> 
> hope this helps, or gives some direction.
> Paul
> 
> 
> 
> On Sun, 2003-03-16 at 21:47, The ServSwitch wrote:
> > 	Is your scsi board made by american megatrends? I cannot find any
> > specifications about it. Do me a favor execute a /sbin/lspci and cut and
> > paste the result please. Do you know how scsi driver linux are using in
> > your system to control that scsi board?
> > 
> > On Sun, 2003-03-16 at 18:24, Andrew B. Cramer wrote:
> > > Hi,
> > > 	Thanks. #lilo and # lilo comes back without anything. It's a 928 
> > > controler with a Seagate 73gig ultra/wide drive. I am able to get, 
> > > and I'm afraid to say it, but Dos-6.22, Win95, Win98, WinNT, and 
> > > Win2000. It boots fine with those. I wonder if Linux is seeing the 
> > > drive as a striped single unit?
> > > 
> > > On 16 Mar 2003 at 18:08, The ServSwitch wrote:
> > > 
> > > > 	Humm... Your lilo.conf is great. So the problem could be when lilo
> > > > writes informations at mbr. What is the model of your megatrends
> > > > controler? What is the model of your hard drive? Have you tried boot
> > > > with a floppy disk and execute "# lilo" as root? A error message could
> > > > show the problem.
> > > > 
> > > > On Sun, 2003-03-16 at 15:13, Andrew B. Cramer wrote:
> > > > > HI ServSwitch,
> > > > > 	Here is my lilo.conf
> > > > > 
> > > > > Thanks - Andrew
> > > > > 
> > > > > # LILO configuration file
> > > > > # generated by 'liloconfig'
> > > > > #
> > > > > # Start LILO global section
> > > > > boot = /dev/sda
> > > > > message = /boot/boot_message.txt
> > > > > prompt
> > > > > timeout = 1200
> > > > > # Override dangerous defaults that rewrite the partition table:
> > > > > change-rules
> > > > >   reset
> > > > > # Normal VGA console
> > > > > vga = normal
> > > > > # VESA framebuffer console @ 1024x768x64k
> > > > > # vga=791
> > > > > # VESA framebuffer console @ 1024x768x32k
> > > > > # vga=790
> > > > > # VESA framebuffer console @ 1024x768x256
> > > > > # vga=773
> > > > > # VESA framebuffer console @ 800x600x64k
> > > > > # vga=788
> > > > > # VESA framebuffer console @ 800x600x32k
> > > > > # vga=787
> > > > > # VESA framebuffer console @ 800x600x256
> > > > > # vga=771
> > > > > # VESA framebuffer console @ 640x480x64k
> > > > > # vga=785
> > > > > # VESA framebuffer console @ 640x480x32k
> > > > > # vga=784
> > > > > # VESA framebuffer console @ 640x480x256
> > > > > # vga=769
> > > > > # End LILO global section
> > > > > # Linux bootable partition config begins
> > > > > image = /boot/vmlinuz
> > > > >   root = /dev/sda1
> > > > >   label = Linux
> > > > >   read-only
> > > > > # Linux bootable partition config ends
> > > > > 
> > > > > 
> > > > > -
> > > > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > > > the body of a message to majordomo@vger.kernel.org
> > > > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > > 
> > > > _______________________________________________________________________
> > > > Busca Yahoo!
> > > > O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> > > > http://br.busca.yahoo.com/
> > > > -
> > > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > > the body of a message to majordomo@vger.kernel.org
> > > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > > 
> > > 
> > > 
> > 
> > _______________________________________________________________________
> > Busca Yahoo!
> > O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
> > http://br.busca.yahoo.com/
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> -- 
> p niemandt <maudib@acesurfer.co.za>
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Megatrends Bootable ?

[Andrew B. Cramer]

One thing I forgot to list was:

Warning: LBA32 addressing assumed
Added Linux *

Is what I get when I run 'lilo' after the system has booted from the 
floppy w/ mount root=/dev/sda1 ro and login.

Best - Andrew

Re: Megatrends Bootable ?

[Paul Furness]

I haven't had this exact problem, but it rang some bells so I read
around a bit.

You could try taking a look at some of the options in lilo relating to
parition tables - specifically "lba32" "geometric" "ignore-table" and
"fix-table".

Looking at the man page for lilo.conf, "fix-table" looks like it might
be worth a try.

Incidentally, to run lilo from the command line you need to do "lilo"
not "# lilo". "#" means comment - anything after it is ignored when you
type it on the line. When "#" is the prompt, it's not part of what you
type and simply informs you that you are root.

Paul.

On Mon, 2003-03-17 at 00:36, Andrew B. Cramer wrote:
> One thing I forgot to list was:
> 
> Warning: LBA32 addressing assumed
> Added Linux *
> 
> Is what I get when I run 'lilo' after the system has booted from the 
> floppy w/ mount root=/dev/sda1 ro and login.
> 
> Best - Andrew
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Paul Furness

Systems Manager
Visual Information Lab
Mitsubsihi Electric ITE BV
Guildford, UK

Steepness is an illusion caused by flat things leaning over.

Re: Megatrends Bootable ?

[Andrew B. Cramer]

Hi all helpers!
	I put a 9gig drive in. It is working fine. It seems the AMI 
Megatrends 928 is too old to support a 73gig drive as bootable. It 
does work as a second though. Thanks again!

Cheers - Andrew