> > Awesome! Eyes must have glazed over when I got to
> that
> > part.
>
> Does this mean it helped?
Yes, thanks a lot.
Maxim
Ready
for the edge of your seat?
Check out tonight's top picks on Yahoo! T
Am Samstag, 12. Mai 2007 schrieb maxim wexler:
> > Maybe you should try adding OPTIONS+="last_rule" to
> > stop device node
> > generations for CD/DVD devices after your rules.
>
> Awesome! Eyes must have glazed over when I got to that
> part.
Does this mean it helped?
> > > udev-104-r12
> >
> >
--- Dirk Heinrichs <[EMAIL PROTECTED]> wrote:
> Am Freitag, 11. Mai 2007 schrieb maxim wexler:
> > > Can you post the relevant lines from
> 10.local.rules.
> >
> > [EMAIL PROTECTED] ~ $ cat /etc/udev/rules.d/10*
> > BUS=="ide", KERNEL=="hdc", SYMLINK+="cdrom",
> > GROUP="cdrom"
> > BUS=="ide",
Am Freitag, 11. Mai 2007 schrieb maxim wexler:
> > Can you post the relevant lines from 10.local.rules.
>
> [EMAIL PROTECTED] ~ $ cat /etc/udev/rules.d/10*
> BUS=="ide", KERNEL=="hdc", SYMLINK+="cdrom",
> GROUP="cdrom"
> BUS=="ide", KERNEL=="hdd", SYMLINK+="dvd",
> GROUP="cdrom"
> [EMAIL PROTECTE
> Can you post the relevant lines from 10.local.rules.
[EMAIL PROTECTED] ~ $ cat /etc/udev/rules.d/10*
BUS=="ide", KERNEL=="hdc", SYMLINK+="cdrom",
GROUP="cdrom"
BUS=="ide", KERNEL=="hdd", SYMLINK+="dvd",
GROUP="cdrom"
[EMAIL PROTECTED] ~ $
see http://www.reactivated.net/writing_udev_rules
Am Freitag, 11. Mai 2007 schrieb maxim wexler:
> Problem is persistent-CD.rules that keeps getting
> re-written every boot.
Hmm that's strange. Doesn't happen on my system(s).
> I've already written a
> 10-local.rules to handle my _one_ CD, /dev/cdrom->
> /dev/hdc and _one_ DVD, /dev/dvd-> /dev
> And if you use the new one, you have to be aware
> that it is attached to the
> SCSI subsystem now. This means that you have to
> enable SCSI as well as
> support for SCSI disks (CONFIG_BLK_DEV_SD=y) and
> SCSI cdroms
> (CONFIG_BLK_DEV_SR=m => sr_mod.ko), just as you
> would do with SATA.
Tha
Am Freitag, 11. Mai 2007 schrieb ext Dan Farrell:
> 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 bu
> 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.
What I did was write a 10-local.rules file follo
On Thu, 10 May 2007 08:50:34 -0700 (PDT)
maxim wexler <[EMAIL PROTECTED]> wrote:
>
> --- Alan McKinnon <[EMAIL PROTECTED]> wrote:
>
> > On Wednesday 09 May 2007, maxim wexler wrote:
> > > lrwxrwxrwx 1 rootroot 3 May 9 08:25
> > > cdrom -> hdc
> > > lrwxrwxrwx 1 rootroot
--- Alan McKinnon <[EMAIL PROTECTED]> wrote:
> On Wednesday 09 May 2007, maxim wexler wrote:
> > lrwxrwxrwx 1 rootroot 3 May 9 08:25
> > cdrom -> hdc
> > lrwxrwxrwx 1 rootroot 3 May 9 08:25
> > cdrom1 -> hdd
> > lrwxrwxrwx 1 rootroot 3 May 9 08:25
> cdrw
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
>
> appear since loading ide-generic.ko
>
> [EMAIL P
> > CONFIG_M586=y
> Nothing to do with your disks, but why this setting?
> You seem to have a 64bit Opteron, not a MkI pentium
CPU is an AMD product, sempron3100, 32bit. It's based
on the 3200 64bit.
> > CONFIG_IDE_GENERIC=m
>
> is this module loaded?
Overlooked this one. I loaded it and the
13 matches
Mail list logo
