From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Rakhesh Sasidharan <rakhesh@rakhesh.com>
Cc: Ismail Donmez <ismail@pardus.org.tr>,
Alan <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: VCD not readable under 2.6.18
Date: Sun, 10 Dec 2006 01:19:14 +0200 [thread overview]
Message-ID: <200612100119.15498.caglar@pardus.org.tr> (raw)
In-Reply-To: <20061209172332.2915.qmail@web57808.mail.re3.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
09 Ara 2006 Cts 19:23 tarihinde, Rakhesh Sasidharan şunları yazmıştı:
> Infact, just inserting a CD is enough. No need for a media player to try
> and access the files. :)
>
> The backend must be polling and trying to mount the disc upon insertion.
> Kernel 2.6.16 and before did that fine, but kernel 2.6.17 and above don't
> and give error messages. Which explains why downgrading the kernel solves
> the problem. (If it were a HAL or KDE/ GNOME problem then shouldn't
> downgrading the kernel *not* help?) Just thinking aloud ...
But i cannot reproduce the problem that way, in my case dmesg flooded as soon
as somebody trying to _access_ to VCD. I disabled hal and closed KDE to test
and that problem no longer reproducible for me. So its really seems a
userspace problem and i think all of them (KDE's cdpolling backend, hal,
mplayer and xine-lib) has problems with kernels >= 2.6.17
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-09 23:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 17:23 VCD not readable under 2.6.18 Rakhesh Sasidharan
2006-12-09 19:46 ` Bill Davidsen
2006-12-10 0:50 ` Alan
2006-12-09 23:19 ` S.Çağlar Onur [this message]
2006-12-10 0:44 ` Alan
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 19:21 Rakhesh Sasidharan
2006-12-11 17:58 Rakhesh Sasidharan
2006-12-10 4:33 Rakhesh Sasidharan
2006-12-10 4:27 Rakhesh Sasidharan
2006-12-09 13:33 Rakhesh Sasidharan
2006-12-09 8:48 Rakhesh Sasidharan
2006-12-09 6:06 Rakhesh Sasidharan
2006-12-09 8:14 ` Ismail Donmez
2006-12-09 13:21 ` Alan
2006-12-09 14:15 ` Ismail Donmez
2006-12-09 14:36 ` Alan
2006-12-09 14:31 ` Ismail Donmez
2006-12-09 16:09 ` S.Çağlar Onur
2006-10-16 18:53 wixor
2006-10-16 23:12 ` Alan Cox
2006-10-17 18:16 ` wixor
2006-10-17 22:38 ` Alan Cox
2006-10-17 22:21 ` Prakash Punnoor
2006-10-17 22:45 ` Olivier Galibert
2006-10-19 16:35 ` wixor
2006-10-19 16:42 ` Alan Cox
2006-10-19 17:39 ` wixor
2006-10-20 13:05 ` Alan Cox
2006-10-24 16:06 ` wixor
2006-10-29 19:23 ` S.Çağlar Onur
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=200612100119.15498.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ismail@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=rakhesh@rakhesh.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.