From: Mark Lord <lkml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ioan Ionita <opslynx@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
htejun@gmail.com
Subject: Re: More JMicron troubles with 2.6.21
Date: Wed, 02 May 2007 17:49:53 -0400 [thread overview]
Message-ID: <46390781.10507@rtr.ca> (raw)
In-Reply-To: <20070502201511.4c8085e9@the-village.bc.nu>
Alan Cox wrote:
>> I have an Asus Commando Mobo with one of those dreadful JMicron
>> controllers (JMicron 20360/20363 AHCI Controller (rev 02). I have a
>
> The Jmicron controllers get a lot of testing so should run smoothly.
>
>> I can't get my CD-RW to work. have tried the pata_jmicron driver and
>> the JMicron ide driver, no success.
>
> This is almost certainly a problem outside of the IDE handling in that
> case. The jmicron controllers are smart, there is basically no code to
> the IDE driver to go wrong (especially in the case of using the old IDE
> for the PATA port where you basically use zero code that hasn't been
> tested for years).
The old IDE driver for JMicron didn't work well for me either,
running on Kubuntu Edgy 2.6.17. It would find the PATA DVD drive,
and work okay for the first half of a DVD movie playback, and then go bonkers.
I eventually gave up on it and installed a pure SATA DVD drive on ICH7(8?)
and just disabled the JMicron completely.
Kernel upgrades are not currenly a viable option for this box
(too many other things would need to be fiddled with).
Cheers
next prev parent reply other threads:[~2007-05-02 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 17:37 More JMicron troubles with 2.6.21 Ioan Ionita
2007-05-02 19:15 ` Alan Cox
2007-05-02 19:29 ` Ioan Ionita
2007-05-02 21:49 ` Mark Lord [this message]
2007-05-02 22:58 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46390781.10507@rtr.ca \
--to=lkml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=opslynx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.