[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: lilo config is busted, need help fixing it



On Thu, 23 Sep 2010 23:20:45 -0500
Stan Hoeppner <stan@hardwarefreak.com> wrote:

> briand@aracnet.com put forth on 9/23/2010 10:50 PM:
> 
> > Boot image: /boot/vmlinuz-2.6.32-5-amd64
> > Device 0x0802: BIOS drive 0x80, 255 heads, 30515 cylinders,
> >                63 sectors. Partition offset: 120583890 sectors.
> > Using Volume ID 5879D4A8 on bios 80
> > Setup length is 27 sectors.
> > Mapped 4708 sectors.
> > Mapping RAM disk /boot/initrd.img-2.6.32-5-amd64
> > Device 0x0802: BIOS drive 0x80, 255 heads, 30515 cylinders,
> >                63 sectors. Partition offset: 120583890 sectors.
> > Using Volume ID 5879D4A8 on bios 80
> > RAM disk: 9407 sectors.
> > Added Lin_2.6.32img5
> >     <dev=0xe0,hd=227,cyl=57,sct=204>
> >     "ro root=802"
> > 
> > I immediately noticed that dev=0xe0
> 
> > shouldn't dev=0x82 !!??
> 
> No, that's normal.  What had you changed on the system immediately
> prior to this boot problem occurring?

apt-get dist-upgrade, natch.

it's very odd, because it runs just fine. and it boots fine as long as
I supply the root=/dev/sda2 

aaargh.  I've never had so much trouble in my entire
linux/debian/life.  I have had a smooth boot or bootloader upgrade on
this computer since I fired it up.  other one works good, though. but
really, 1/2 _is_ bad.


Brian


Reply to: