> Everyone, I tried rebuilding 2.6.22-rc2 last night with CONFIG_IDE > disabled, but it still produces the same problem. The relevant config > options: > > # CONFIG_IDE is not set > CONFIG_ATA=y > CONFIG_ATA_ACPI=y > CONFIG_SATA_AHCI=y > CONFIG_ATA_PIIX=y > CONFIG_PATA_JMICRON=y > > Ethan, you mention that this is a known issue.. I can't find any link > to this problem. This is happening on a cleanly rebuilt kernel, so I'm > not sure if this has to do with Debian 4.0r0 probing the module > incorrectly. I already have the OS installed, and I figured a newer > kernel would have resolved this issue. Unlike the bug report I linked > to, I am not seeing the driver detect JMB363 & JMB361 in the same boot > log. Even when everything works, it only detects a JMB361. I've tried to reproduce this issue under GA-965P-DQ6. JMB363 works fine in 2.6.22-rc2. The dmesg log is attached. It will not show any device name in pata_jmicron. > A working boot looks like this: > > JMB361: IDE controller at PCI slot 0000:04:00.1 > ACPI: PCI Interrupt 0000:04:00.1[B] -> GSI 18 (level, low) -> IRQ 58 > JMB361: chipset revision 2 > JMB361: 100% native mode on irq 58 > ide0: BM-DMA at 0xa000-0xa007, BIOS settings: hda:pio, hdb:pio > ide1: BM-DMA at 0xa008-0xa00f, BIOS settings: hdc:DMA, hdd:DMA If you disabled the entire old-IDE driver, this message should not be existed. It should be like this: ACPI: PCI Interrupt 0000:03:00.1[B] -> GSI 18 (level, low) -> IRQ 19 PCI: Setting latency timer of device 0000:03:00.1 to 64 scsi6 : pata_jmicron scsi7 : pata_jmicron ata7: PATA max UDMA/100 cmd 0x0001a000 ctl 0x0001a402 bmdma 0x0001b000 irq 0 ata8: PATA max UDMA/100 cmd 0x0001a800 ctl 0x0001ac02 bmdma 0x0001b008 irq 0 > No use of acpi=off, noapic, nolapic seems to affect the JMB361 from > being detected properly or not. > > Any next steps? Ethan, do you have more information about this > particular issue with the DQ6 motherboard? > > Thanks -Andrew
Attachment:
dmesg.log
Description: Binary data
