From: "Takis Diakoumis" <takisd@alphalink.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11 AC patch CD/DVD issues
Date: Tue, 22 Mar 2005 11:14:15 +1100 [thread overview]
Message-ID: <423f6357.2ce4.0@alphalink.com.au> (raw)
thanks for responding.
>> other ata controllers which then report errors as they can't be unloaded
>> - though i read somewhere on this list that this was by design???).
>
>IDE is designed to be compiled in. There is a lot to do to fix that. -ac
>has hackish unload support in test but the right solution is refcounting
>and driver model based and is in Bartlomiej's dev tree.
should i compile all 'offending' modules into the kernel?
>> all cd ripping/reading tools for audio/multimedia cds report unable to
>> initialize /dev/cdrom (a link to cdrom device).
>
>Are you sure it points to the right device. I've seen similar reports
>where
>/dev/cdrom ended up pointing at the hard disk when the it8212 is added.
>Seems
>some distributions get confused when an IDE controller decides it wants
>to be first.
sorry, i should have been clearer. i am actually changing the link
depending on whether the it8212 controller is enabled in the bios. if
enabled, cdrom is /dev/hdh (dvd is /dev/hdg). if not enabled, cdrom/dvd is
/dev/hdc and hdd. the links are correct, and like i mentioned in the
initial post, i can mount data cds/dvds with no issues whether the
controller is enabled or not. it almost sounds like it thinks the cd and
dvd drives are hard drives and treating them as such. is there perhaps some
additional parameter that should be passed to the kernel on boot, perhaps
with ide-cdrom or similar??
thanks again for responding.
Takis
next reply other threads:[~2005-03-22 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 0:14 Takis Diakoumis [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-20 15:27 2.6.11 AC patch CD/DVD issues Takis Diakoumis
2005-03-21 14:43 ` Alan Cox
2005-03-22 16:35 ` Takis Diakoumis
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=423f6357.2ce4.0@alphalink.com.au \
--to=takisd@alphalink.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox