(please don't drop linux-ide, use reply-to-all)
Gavin Cameron wrote:
Tejun Heo wrote:
quoted
Hmmm... looks like configuration went well but media presence polling is
causing the problem. "hal-disable-polling /dev/sr0" will disable the
polling. Can you please do that and see whether the drive is usable?
[root@picard ~]# hal-disable-polling --device /dev/sr0
Polling for drive /dev/sr0 have been disabled. The fdi file written was
/etc/hal/fdi/information/media-check-disable-storage_model_DVD_A__DH20A3P.fdi
Okay.
Inserted CD into drive: drive light came on for about 20 seconds, but
nothing happened.
Checked /var/log/messages and nothing there.
Left it sitting there for 5 minutes or so and checked /var/log/messages
again and still nothing there.
As media presence polling is disabled, the system won't notice whether
the media has changed or not.
Mounted the CD as root:
[root@picard ~]# mkdir /mnt/cdrom
[root@picard ~]# mount -t iso9660 /dev/sr0 /mnt/cdrom/
mount: block device /dev/sr0 is write-protected, mounting read-only
The command took about 1 minute to complete. I was then able to browse
the CD, however each change of directory took approximately 10 seconds
to read.
Hmmm...
I then ejected the CD:
[root@picard ~]# eject /dev/sr0
again, this took about 20 seconds to eject the CD.
After the eject, still nothing in /var/log/messages.
Tried inserting and ejecting another couple of times.
I verified that the CD was readable in my external CD drive and then put
the CD back into the main drive and started writing up the results so far.
As I've been typing, the drive has been spinning up and down several
times and this time when I checked /var/log/messages I found what is
attached.
Is there anything else I can provide in order for you to find the problem?
Can you please try kernel parameter "libata.force=2.00:udma33" and then
"libata.force=2.00:pio4"? Depending on which distro you're on and
whether libata is built into the kernel or not, you'll need to use
different method to actually get the parameter passed to libata.
Thanks.
--
tejun
Hi,
Thanks again for following up on this and sorry for the delay in
responding as I've not been at home for about a week.
Anyway, I did as you ask ...
Tejun Heo wrote:
(please don't drop linux-ide, use reply-to-all)
Gavin Cameron wrote:
quoted
Tejun Heo wrote:
quoted
Hmmm... looks like configuration went well but media presence polling is
causing the problem. "hal-disable-polling /dev/sr0" will disable the
polling. Can you please do that and see whether the drive is usable?
[root@picard ~]# hal-disable-polling --device /dev/sr0
Polling for drive /dev/sr0 have been disabled. The fdi file written was
/etc/hal/fdi/information/media-check-disable-storage_model_DVD_A__DH20A3P.fdi
Okay.
quoted
Inserted CD into drive: drive light came on for about 20 seconds, but
nothing happened.
Checked /var/log/messages and nothing there.
Left it sitting there for 5 minutes or so and checked /var/log/messages
again and still nothing there.
As media presence polling is disabled, the system won't notice whether
the media has changed or not.
I re-enabled hal on the CD drive by changing the file:
/etc/hal/fdi/information/media-check-disable-storage_model_DVD_A__DH20A3P.fdi
so that it read:
<merge key="storage.media_check_enabled" type="bool">true</merge>
quoted
Mounted the CD as root:
[root@picard ~]# mkdir /mnt/cdrom
[root@picard ~]# mount -t iso9660 /dev/sr0 /mnt/cdrom/
mount: block device /dev/sr0 is write-protected, mounting read-only
The command took about 1 minute to complete. I was then able to browse
the CD, however each change of directory took approximately 10 seconds
to read.
Hmmm...
quoted
I then ejected the CD:
[root@picard ~]# eject /dev/sr0
again, this took about 20 seconds to eject the CD.
After the eject, still nothing in /var/log/messages.
Tried inserting and ejecting another couple of times.
I verified that the CD was readable in my external CD drive and then put
the CD back into the main drive and started writing up the results so far.
As I've been typing, the drive has been spinning up and down several
times and this time when I checked /var/log/messages I found what is
attached.
Is there anything else I can provide in order for you to find the problem?
Can you please try kernel parameter "libata.force=2.00:udma33" and then
"libata.force=2.00:pio4"? Depending on which distro you're on and
whether libata is built into the kernel or not, you'll need to use
different method to actually get the parameter passed to libata.
Thanks.
List of modules currently loaded are in the attached file.
You'll find the attached /var/log/messages output from both experiments.
What I ended up doing (not sure if it's right, but I can't see any error
messages) was to add the lines to /etc/stsctl.conf which appears to be
the way that Fedora 9 takes care of parameters like that. I've also
attached that file too. However, I didn't see any file called
/proc/sys/libata/force so I'm not entirely sure that it worked. Perhaps
I need "kernel." or something before libata? (I'm not a kernel
developer, so forgive my lack of knowledge on this matter)
What happened both times was that the disc was read initially ok - I'm
sure I recall it doing this before, but only if a CD is inserted very
quickly after booting up and loggin on.
Anyway, when I removed the CD and waited a while before inserting it
again, the same thing happened as before.
Both experiments were with kernel 2.6.25.14 which is the latest one on
the Fedora 9 distribution. I chose this as 2.6.26.1 didn't do anything
different last time, but it also didn't have a lot of modules that my
machine requires.
Anyway, I eagerly await your response.
Best regards,
Gavin.