public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] no CD or DVD but "rules" seem correct-FIXED-or, not
Date: Thu, 10 May 2007 17:12:36 -0500	[thread overview]
Message-ID: <20070510171236.416c40fa@pascal.spore.ath.cx> (raw)
In-Reply-To: <643461.72977.qm@web31701.mail.mud.yahoo.com>

On Thu, 10 May 2007 08:50:34 -0700 (PDT)
maxim wexler <blissfix@yahoo.com> wrote:

> 
> --- Alan McKinnon <alan@linuxholdings.co.za> wrote:
> 
> > On Wednesday 09 May 2007, maxim wexler wrote:
> > > lrwxrwxrwx  1 root    root         3 May  9 08:25
> > > cdrom -> hdc
> > > lrwxrwxrwx  1 root    root         3 May  9 08:25
> > > cdrom1 -> hdd
> > > lrwxrwxrwx  1 root    root         3 May  9 08:25
> > cdrw
> > > -> hdc
> > > [ /dev device nodes for cdroms ]
> > > appear since loading ide-generic.ko
> > >
For one thing, generic IDE support is certainly less appropriate than
support for your IDE card.  Hardware-specific options cna be enabled
and you might gain DMA if your hardware is really unusual.  I can say
from experience that generic ide support doesn't provide anything that
drivers specific to your hardware fails to provide, unless I
misunderstand greatly. It's not a question of increased functionality
necessarily, but one of performance, and possibly less overhead for the
CPU.  

Secondly, in addition to some kind of driver for IDE, either generic or
specific, you need the cdrom driver (module: cdrom.ko) for cdrom
support.  

My guess is, you upgraded the kernel and fell into the commonly
experienced PATA driver burn -- there's two driver sets now, an
experimental one and the old ones, and you have to make sure to get the
right one for your configuration.  

Dont forget, you'll also need to have the ISO9660 and possibly UDF
filesysem supported.  
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-10 22:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  2:36 [gentoo-user] no CD or DVD but "rules" seem correct maxim wexler
2007-05-09  6:03 ` Dirk Heinrichs
2007-05-09  7:44 ` Alan McKinnon
2007-05-09 14:44   ` maxim wexler
2007-05-09 15:49     ` Alan McKinnon
2007-05-09 19:48       ` [gentoo-user] no CD or DVD but "rules" seem correct-FIXED maxim wexler
2007-05-10  7:22         ` Alan McKinnon
2007-05-10 15:50           ` [gentoo-user] no CD or DVD but "rules" seem correct-FIXED-or, not maxim wexler
2007-05-10 22:12             ` Dan Farrell [this message]
2007-05-11  1:36               ` maxim wexler
2007-05-11  6:01               ` Dirk Heinrichs
2007-05-11 16:08                 ` maxim wexler
2007-05-11 18:17                   ` Dirk Heinrichs
2007-05-11 19:52                     ` maxim wexler
2007-05-12  6:41                       ` Dirk Heinrichs
2007-05-12 17:34                         ` [gentoo-user] no CD or DVD but "rules" seem correct-FIXED-no, really maxim wexler
2007-05-12 18:45                           ` Dirk Heinrichs
2007-05-12 20:22                             ` maxim wexler
2007-05-09 14:25 ` [gentoo-user] no CD or DVD but "rules" seem correct gummnmi-live

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=20070510171236.416c40fa@pascal.spore.ath.cx \
    --to=dan@spore.ath.cx \
    --cc=gentoo-user@lists.gentoo.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