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

Re: 3.2.0-0.bpo.2 ate my dvd drive

On Mon, 2012-04-23 at 18:02 +0200, Jim MacBaine wrote:
> Hi,
> I recently upgraded my desktop to kernel version
> 3.2.0-0.bpo.2-686-pae from debian-backports.

From what?

> Starting with this
> version, I can no longer access my dvd drive. It is an IDE drive
> connected to a JMicronJMB362 Controller:
> $ lspci | grep ^03
> 03:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial
> ATA Controller (rev 02)
> 03:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial
> ATA Controller (rev 02)
> $ lspci -n | grep ^03
> 03:00.0 0106: 197b:2363 (rev
> 03:00.1 0101: 197b:2363 (rev 02)

I think these devices should be handled by ahci and pata_jmicron

> $ dmidecode -s system-manufacturer
> Gigabyte Technology Co., Ltd.
> $ dmidecode -s system-product-name
> P35-DS3
> So far, I have found out, that IDE support has been completely
> disabled between 3.2.0-0.bpo.1 and 3.2.0-0.bpo.2 and,
> unfortunately, my IDE controller seems not to be supported by
> this kernel's pata drivers. Using 3.2.0-0.bpo.1 I can access my
> dvd drive just fine.

Yes, but we replaced jmicron with pata_jmicron years ago (in 2.6.30-1).
The recent change just finished off the transition (aside from a very
few controllers with no new driver).

> I grepped through the kernel sources for the pci id of my
> controller and the only match is in the ide tree:
> $ grep 0x2363 include/linux/pci_ids.h
> #define PCI_DEVICE_ID_JMICRON_JMB363	0x2363
> drivers/ide/jmicron.c:  { PCI_VDEVICE(JMICRON, PCI_DEVICE_ID_JMICRON_JMB363) },
> drivers/pci/quirks.c:   case PCI_DEVICE_ID_JMICRON_JMB363:
> PCI_DEVICE_ID_JMICRON_JMB363, quirk_jmicron_ata);
> PCI_DEVICE_ID_JMICRON_JMB363, quirk_jmicron_ata);
> include/linux/pci_ids.h:#define PCI_DEVICE_ID_JMICRON_JMB363    0x2363

Not all PCI devices are matched by device ID.  They can also be matched
by class code (as the abovementioned drivers do).

> So it seems the controller is not supported at all by the pata
> drivers and I cannot use the drive with 3.2.0-0.bpo.2 at all.

Well, I believe it's mean to be supported by pata_jmicron.  Is that
driver being loaded?   What error or other messages does it log?


Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: