From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew B. Cramer" Subject: Re: Megatrends Bootable ? Date: Sun, 16 Mar 2003 16:57:30 -0600 Sender: linux-admin-owner@vger.kernel.org Message-ID: <3E74ACFA.13214.8E44225@localhost> References: <1047851245.478.15.camel@feanor.dimarino.nom.br> Reply-To: andrew.cramer@cramer-ts.com Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-reply-to: <1047852287.932.4.camel@quark> Content-description: Mail message body List-Id: Content-Type: text/plain; charset="iso-8859-1" To: p niemandt Cc: linux-admin Thanks Paul, did that first. Low-leveled the drive. Tried all the=20 normal things, but no luck. I do have a current mirror of the HOWTO's=20 and will have a look. On 16 Mar 2003 at 22:04, p niemandt wrote: > hiya: >=20 > Just FYI: I used to get this problem, {of 40's flooding the screen wh= en > 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 (Maste= r > Boot Record) of the disk that was screwed.=20 >=20 > What you can try, and this might be a dangerous route to follow, is j= ust > 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 som= e > google on it. >=20 > 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 th= e > FAT32/16 on, not when the FAT32 was on another partition.) >=20 > hope this helps, or gives some direction. > Paul >=20 >=20 >=20 > 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 cu= t and > > paste the result please. Do you know how scsi driver linux are usin= g in > > your system to control that scsi board? > >=20 > > 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= =20 > > > controler with a Seagate 73gig ultra/wide drive. I am able to get= ,=20 > > > and I'm afraid to say it, but Dos-6.22, Win95, Win98, WinNT, and=20 > > > Win2000. It boots fine with those. I wonder if Linux is seeing th= e=20 > > > drive as a striped single unit? > > >=20 > > > On 16 Mar 2003 at 18:08, The ServSwitch wrote: > > >=20 > > > > Humm... Your lilo.conf is great. So the problem could be when = lilo > > > > writes informations at mbr. What is the model of your megatrend= s > > > > controler? What is the model of your hard drive? Have you tried= boot > > > > with a floppy disk and execute "# lilo" as root? A error messag= e could > > > > show the problem. > > > >=20 > > > > On Sun, 2003-03-16 at 15:13, Andrew B. Cramer wrote: > > > > > HI ServSwitch, > > > > > Here is my lilo.conf > > > > >=20 > > > > > Thanks - Andrew > > > > >=20 > > > > > # LILO configuration file > > > > > # generated by 'liloconfig' > > > > > # > > > > > # Start LILO global section > > > > > boot =3D /dev/sda > > > > > message =3D /boot/boot_message.txt > > > > > prompt > > > > > timeout =3D 1200 > > > > > # Override dangerous defaults that rewrite the partition tabl= e: > > > > > change-rules > > > > > reset > > > > > # Normal VGA console > > > > > vga =3D normal > > > > > # VESA framebuffer console @ 1024x768x64k > > > > > # vga=3D791 > > > > > # VESA framebuffer console @ 1024x768x32k > > > > > # vga=3D790 > > > > > # VESA framebuffer console @ 1024x768x256 > > > > > # vga=3D773 > > > > > # VESA framebuffer console @ 800x600x64k > > > > > # vga=3D788 > > > > > # VESA framebuffer console @ 800x600x32k > > > > > # vga=3D787 > > > > > # VESA framebuffer console @ 800x600x256 > > > > > # vga=3D771 > > > > > # VESA framebuffer console @ 640x480x64k > > > > > # vga=3D785 > > > > > # VESA framebuffer console @ 640x480x32k > > > > > # vga=3D784 > > > > > # VESA framebuffer console @ 640x480x256 > > > > > # vga=3D769 > > > > > # End LILO global section > > > > > # Linux bootable partition config begins > > > > > image =3D /boot/vmlinuz > > > > > root =3D /dev/sda1 > > > > > label =3D Linux > > > > > read-only > > > > > # Linux bootable partition config ends > > > > >=20 > > > > >=20 > > > > > - > > > > > To unsubscribe from this list: send the line "unsubscribe lin= ux-admin" in > > > > > the body of a message to majordomo@vger.kernel.org > > > > > More majordomo info at http://vger.kernel.org/majordomo-info= =2Ehtml > > > >=20 > > > > _______________________________________________________________= ________ > > > > Busca Yahoo! > > > > O servi=E7o de busca mais completo da Internet. O que voc=EA pe= nsar 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.h= tml > > > >=20 > > >=20 > > >=20 > >=20 > > ___________________________________________________________________= ____ > > Busca Yahoo! > > O servi=E7o de busca mais completo da Internet. O que voc=EA pensar= o Yahoo! encontra. > > http://br.busca.yahoo.com/ > > - > > To unsubscribe from this list: send the line "unsubscribe linux-adm= in" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > --=20 > p niemandt >=20 > - > 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 >=20 - 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