I followed the instructions in post #85, made backups of the 2 files
before I modified them for easy reversal if needed...  Here's what I
did...

1. Add "blacklist pata_ali" to /etc/modprobe.d/blacklist
2. Run "sudo update-initramfs -u"
3. Add "ata_generic.all_generic_ide=1" to the GRUB_CMDLINE_LINUX line in 
/etc/default/grub
4. Run "sudo update-grub"
5. Reboot (preferably using the recovery option so that you can see the verbose 
boot information).

I booted into recovery mode...then when a MS-DOS style windows with ANSI
came up, I selected the first option, to continue booting normally.

I did not notice any errors...but then again, I couldnt scroll the
display to backtrace...but everything seemed fine...albeit with no
GUI...so I shutdown and restarted this time NOT using recovery
mode...and I am in Ubuntu Karmic now...everything appears to be the
same, unchanged, no difference...

First thing I did is to see if my drives are /dev/sdX or /dev/hdX, and
they are still /dev/sdX...so did a

canada_...@home:~$ sudo hdparm /dev/hda
/dev/hda: No such file or directory
canada_...@home:~$ sudo hdparm /dev/sda

/dev/sda:
 multcount     = 16 (on)
 IO_support    =  0 (default) 
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 48641/255/63, sectors = 781422768, start = 0
l...@home:~$ sudo hdparm -c1 /dev/sda

/dev/sda:
 setting 32-bit IO_support flag to 1
 HDIO_SET_32BIT failed: Invalid argument
 IO_support    =  0 (default) 


So, is there anything I need to do to make my system change the drives from 
/dev/sdX to /dev/hdX?

Also, right this second, which is being used right this second?
ata_generic or pata_ali?  How can I verify which is in use right now?

Also, if any updates happen, with they wipe out this change I am trying
to make?  And will I have to do this change everytime a certain thing
gets updated?

I dont know if this matters, but I am using Prelink and Preload.

Anyone have any suggestions?

Laters.

-- 
[HARDY-LUCID] No DMA nor 32bits IO support
https://bugs.launchpad.net/bugs/228302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to