View previous topic :: View next topic |
Author |
Message |
cwr Veteran

Joined: 17 Dec 2005 Posts: 1969
|
Posted: Sat Jun 20, 2009 9:57 am Post subject: Kernel 2.6.30 and CDROM/PATA? [Solved] |
|
|
I've upgraded to 2.6.30, which broke the entire sound system: I've managed
to fix most of it, but the system now locks solid with a kernel oops 0000 when
I load an audio or data CDROM (Null pointer dereference at 00000024). I
suspect the problem is actuall with the PATA interface - the main HD is SATA,
but the CDROM is on a (standard Intel onboard) PATA bus.
Everything worked in 2.6.28 (well, everything that usually works) and I've double-
checked the configuration changes; has anyone seen any similar problem?
Thanks - Will
Last edited by cwr on Sun Jun 21, 2009 1:38 pm; edited 1 time in total |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55200 Location: 56N 3W
|
Posted: Sat Jun 20, 2009 2:27 pm Post subject: |
|
|
cwr,
Do you use both the old IDE and SATA kernel branches or have you migrated to the PATA drivers under libata?
The PATA driver in libata works for my AMD/nvidia PATA chip set. The device appears as /dev/sr0 _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
hielvc Advocate

Joined: 19 Apr 2002 Posts: 2805 Location: Oceanside, Ca
|
Posted: Sat Jun 20, 2009 4:17 pm Post subject: |
|
|
After upgrading from 2.6.28 to 2.6.29-r2 then r3 which broke X and sound. Now that things have settled, yesterday, my /dev/ pointers had changed to cdrom1 and so forth. Did yours ? _________________ An A-Z Index of the Linux BASH command line |
|
Back to top |
|
 |
RedSquirrel Guru


Joined: 22 Apr 2008 Posts: 336
|
Posted: Sat Jun 20, 2009 4:39 pm Post subject: |
|
|
2.6.30 with libata (pata_via) works well for me (VIA IDE interface).
hielvc wrote: | After upgrading from 2.6.28 to 2.6.29-r2 then r3 which broke X and sound. Now that things have settled, yesterday, my /dev/ pointers had changed to cdrom1 and so forth. Did yours ? |
See /etc/udev/rules.d/70-persistent-cd.rules. |
|
Back to top |
|
 |
cwr Veteran

Joined: 17 Dec 2005 Posts: 1969
|
Posted: Sun Jun 21, 2009 1:37 pm Post subject: |
|
|
I had a couple of the CMD640 chipset flags set, since it's used on another machine.
They haven't been a problem before, but apparently they are now; I turned them
off, and the CDROM worked.
Thanks for the ideas - Will |
|
Back to top |
|
 |
|