mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rakhesh Sasidharan <rakheshster@yahoo.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VCD not readable under 2.6.18
Date: Sat, 9 Dec 2006 05:33:26 -0800 (PST)	[thread overview]
Message-ID: <20061209133326.69944.qmail@web57808.mail.re3.yahoo.com> (raw)

Slackware 11 (2.6.18 kernel) didn't have GNOME installed. So if it is a GNOME thing, how come Slackware too was giving the same error? 

Also, if previously the kernel wasn't reporting errors when asked to do stuff like this with VCDs, how come it was still able to mount the VCDs and allow playback/ copying of the files in it? Its ok if the kernel reports more errors than before, as long as it allows playback/ copying ... 

Regards,
Rakhesh

ps. Please do cc me on replies to thread. 

----- Original Message ----
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Rakhesh Sasidharan <rakhesh@rakhesh.com>
Cc: rakheshster@yahoo.com; linux-kernel@vger.kernel.org
Sent: Saturday, December 9, 2006 5:21:20 PM
Subject: Re: VCD not readable under 2.6.18


Your system tried to read a Video data block. The usual cure for this
problem is to remove Gnome, or at least kill all the Gnome stuff and flip
to init level 3 then mount the cd from the command line. 

The kernel is correctly reporting it was asked to do something stupid.
Older kernels would fail to report many of these errors due to a bug in
the ide-cd reporting logic.






 
____________________________________________________________________________________
Any questions? Get answers on any topic at www.Answers.yahoo.com.  Try it now.

             reply	other threads:[~2006-12-09 13:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 13:33 Rakhesh Sasidharan [this message]
  -- 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 17:23 Rakhesh Sasidharan
2006-12-09 19:46 ` Bill Davidsen
2006-12-10  0:50   ` Alan
2006-12-09 23:19 ` S.Çağlar Onur
2006-12-10  0:44 ` Alan
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=20061209133326.69944.qmail@web57808.mail.re3.yahoo.com \
    --to=rakheshster@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®