Please keep the old IDE chipset drivers so that external CD writers can work

[Rick Knight]

Wenzhuo Zhang wrote:
> Rick Knight wrote:
>   
>> Wenzhuo Zhang wrote:
>>     
>>> Hi,
>>>
>>> Starting from Gutsy, the old IDE chipset drivers are no longer included in the kernel package. 
>>>       
>> Could this be my problem? See post "Help with Gutsy upgrade" in this 
>> list. After an upgrade from Feisty to Gutsy the new kernel will not load 
>> my hard drive. When I upgraded from Dapper to Feisty, the upgrade set my 
>> drives up as /dev/sdx (in GRUB and /etc/fstab) and I could not boot. I 
>>     
>
> Nowadays the standard way of identifying filesystems is by UUIDs. You should
> use the vol_id command to find out the UUIDs of your filesystems, e.g.
>
>     $ sudo vol_id /dev/hda1
>
> and replace the occurrences of "/dev/[sh]dx?" in /etc/fstab and /boot/grub/menu.lst to "UUID=xxxxxxxx", where "xxxxxxxx" is the corresponding UUID of each filesystem.
>   
I've done that. I've verified the UUIDs of all partitions with blkid and 
vol_id and and compared those results with what's in /boot/grub/menu.lst 
and /etc/fstab. They are the same.
>  
>   
>> changed the drives back to /dev/hdx and that solved the problem. Gutsy 
>> does not seem able to deal with /dev/hdx so, could this be why I can't 
>> boot the 2.6.22.14-generic kernel? I have a 4 year old Soyo motherboard 
>> with Via chipset. Can I rebuild the kernel to get this older IDE 
>> support? I can still boot into my Feisty kernel.
>>     
>
> If you have added the old IDE driver modules to /etc/initramfs-tools/modules
> before, you should remove them fist, and run the following command for each kernel
> version:
>
>     $ sudo update-initramfs -u -k <version>
>   
I've removed the changes made to /etc/initramfs-tools/modules and I've 
re-run

$ sudo update-initramfs -u -k 2.6.22-14-generic
> If you have not modifiled /etc/initramfs-tools/modules before, probably your IDE chipset is not supported by libata yet.
How can I determine if my chipset isn't supported by libata? These 
modules load for both the working kernel (2.6.20-16-generic) and the non 
working kernel (2.6.22-14-generic)

ata_generic
libata
sg
st
scsi_mod
ide_cd
ide_disk

> You may want to file a separate bug report at launchpad, attaching the result of "lspci -vvn", "dmesg" of a running kernel, and a screenshot (by a camera) of the boot failure of Gutsy.
>
> Wenzhuo
>   
I'll file the bug report as you, suggest, tonight or this weekend. But 
until I hear a respones to the bug report, is there anyway to force the 
newer kernel to setup drives by path with hdxn instead of sdxn? Also, if 
I do rebuild the kernel, which module(s) do I need to activate?

Thanks again,
Rick