Mailinglist Archive: opensuse-factory (592 mails)

< Previous Next >
[opensuse-factory] Hardware Support: JMicron JMB363 (w/ Intel P965 Chipset)
  • From: Randall R Schulz <rschulz@xxxxxxxxx>
  • Date: Sun, 15 Oct 2006 08:08:59 -0700
  • Message-id: <200610150808.59326.rschulz@xxxxxxxxx>

I have a nice new Asus P5B mainboard (please, no chastising me for
choosing a board from a Linux-hostile vendor) that is, for the most
part, running 10.2a5 successfully. However, that's so only because I had
the brilliant, though completely serendipitous, idea to put one IDE
optical drive and one SATA optical drive in my system. Fortunately, the
SATA drive made installation possible while the JMicron-controlled
IDE/ATA bus with its lonely optical drive remains shut out.

And that is the subject my question. How do I get access to the IDE bus?

My on-line research indicates that the 2.6.18 kernel should be able to
access this device (see the very long thread in the Ubuntu bug forum at
and the Linux kernel commit log entry at
Apparently there was a bug in an earlier kernel that rendered the
JMicron controller inaccessible when it was paired with the Intel P965
chipset (which itself includes no legacy IDE support at all, only SATA).

One thing I find odd is that this device shows up and is properly
identified in the output of "lspci -vv":

03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc. Unknown device 81e4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Interrupt: pin A routed to IRQ 169
Region 0: I/O ports at ac00 [size=8]
Region 1: I/O ports at a880 [size=4]
Region 2: I/O ports at a800 [size=8]
Region 3: I/O ports at a480 [size=4]
Region 4: I/O ports at a400 [size=16]
Region 5: Memory at fe1fe000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at fe1e0000 [disabled] [size=64K]
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Express Legacy Endpoint IRQ 1
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <64ns, L1 <1us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 1
Link: Latency L0s <1us, L1 <16us
Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1

Does anyone know if the JMicron JMB363 controller is actually supported
by the kernel and driver complement of 10.2a5? If so, what must I do to
render it operable?


Randall Schulz
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups