From: "J.A. Magallón" <jamagallon@ono.com>
To: "Linux-Kernel, " <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [2.6.18-rc2-mm1] libata cdroms not automounted
Date: Thu, 3 Aug 2006 01:16:33 +0200 [thread overview]
Message-ID: <20060803011633.13338417@werewolf.auna.net> (raw)
Hi...
Following with my switch to libata for everything...
After latest patches, my burner and dvd work ok, apart from the fact that
they do not get auto-mounted in gnome environment.
udevmonitor shows nothing when a CD is inserted.
More:
- USB sticks work
- IDE ZIP drive works:
UEVENT[1154559818.714967] add@/block/sda/sda1
UEVENT[1154559820.046948] mount@/block/sda/sda1
- cdroms work under the old IDE driver (not tested in the same box, but
with the same software)
- srX cdroms generated by libata do not automount (tested in 2 boxes)
As software is the same in the 3 boxes, and some things work, I suspect
the kernel is not generating the correct events ?
Or is the combo udev+dbus+hal userspace what fails ?
But as udevmonitor shows events for zip drive but none for cdrom, I would
vote against the kernel :)
Someone with a real SCSI cdrom can check if it works ?
Software:
- Linux 2.6.18-rc2-mm1+scsi-media-detection-patch [1]
- udev-096
- dbus-0.91
- hal-0.5.7.1
(mandriva cooker)
More info on demand.
TIA
[1] http://marc.theaimsgroup.com/?l=linux-kernel&m=115412002912837&w=2
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2007.0 (Cooker) for i586
Linux 2.6.17-jam05 (gcc 4.1.1 20060724 (prerelease) (4.1.1-3mdk)) #1 SMP PREEMPT
next reply other threads:[~2006-08-02 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 23:16 J.A. Magallón [this message]
2006-08-04 7:29 ` Tejun Heo
2006-08-04 14:05 ` Mark Lord
2006-08-04 23:05 ` Jiri Slaby
2006-08-05 3:41 ` Tejun Heo
[not found] <fa.0fapZpsbPNwCajbQ53nT7FIKF1k@ifi.uio.no>
2006-08-03 2:37 ` Robert Hancock
2006-08-07 7:51 ` Robert Hancock
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=20060803011633.13338417@werewolf.auna.net \
--to=jamagallon@ono.com \
--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
Powered by JetHome