Re: 2.34 Kernel Won't Boot
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Aug 2010 03:13:50 -0500
David Baron put forth on 8/20/2010 2:04 AM:
I built this kernel for first time with new PATA rather than the old
deprecated drivers. These are compiled-in, no initrd. Get cannot find block
error, [2,22] or something like that.
Possibilities:
1. Need to compile in VIA's driver as well. Not doing this prevented DMA
access using deprecated drivers a while back. I am doing this kernel for a
new MB, not VIA chipset. Module is built.
2. New drivers assign different dev names. Need to change to newer name scheme
in lilo.conf. If so, this will wait for new machine since this will render
older kernel builds unusable. Current MB is an older IDE-based machine. The
new MB will be SATA but has an IDE as well (and there are those adapters that
plug in to the old disks to make them work like SATA).
3. Do not use 2.6.34. Has apparently been abandoned?
Can anyone tell me what to do? (I hope the older kernels will boot on the new
MB.) Thanks in advance.
It would help tremendously if you told us exactly which IDE chip(s) you have,
or your exact motherboard make/model#.
--
Stan
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Archive: http://lists.debian.org/4C6E393E.1000401@xxxxxxxxxxxxxxxxx
- References:
- 2.34 Kernel Won't Boot
- From: David Baron
- 2.34 Kernel Won't Boot
- Prev by Date: Re: disable sleep mode hdd usb
- Next by Date: Re: Unidentified subject!
- Previous by thread: 2.34 Kernel Won't Boot
- Next by thread: Re: 2.34 Kernel Won't Boot
- Index(es):
Relevant Pages
|
