Couple of devices gone walk-about

[Mike Klinke]

Regards, Mike Klinke

Seems that somewhere between kernel-2.6.7-1.517 and 
kernel-2.6.8-1.526 I seem to have lost the ability to use the 
cdrom/dvd player on my VAIO laptop. The /dev/cdrom and /dev/sr0 
files which were created under the 517 kernel are no longer created 
under the 526 kernel.  If I go back to the 517 kernel as is well. 
Is this a known problem or does it need to be investigated further?

Regards, Mike Klinke

[Mike Klinke]

>  Seems that somewhere between kernel-2.6.7-1.517 and
>  kernel-2.6.8-1.526 I seem to have lost the ability to use the
>  cdrom/dvd player on my VAIO laptop. The /dev/cdrom and /dev/sr0
>  files which were created under the 517 kernel are no longer
>  created under the 526 kernel.  If I go back to the 517 kernel as
>  is well. Is this a known problem or does it need to be
>  investigated further? 
 

OK, narrowing it down a bit, everything seems to have gone haywire 
between kernel-2.6.8-1.524 and kernel-2.6.8-1.525.  I suspect it 
has something to do with:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130746

but since English is my native language I'm not sure what's going on 
there but I get the sense that something's gone haywire with 
autoloading of modules and sure enough, a diff of "lsmod" between 
the 524 and 525 kernels shows there definitely a problem here:

23:31:03 # diff 524-Modules.txt 525-Modules.txt
2,13d1
< snd_mixer_oss          14017  2
< snd_intel8x0           30829  3
< snd_ac97_codec         58693  1 snd_intel8x0
< snd_pcm                82377  1 snd_intel8x0
< snd_timer              25029  1 snd_pcm
< snd_page_alloc          8137  2 snd_intel8x0,snd_pcm
< gameport                3777  1 snd_intel8x0
< snd_mpu401_uart         7232  1 snd_intel8x0
< snd_rawmidi            21605  1 snd_mpu401_uart
< snd_seq_device          6345  1 snd_rawmidi
< snd                    44453  10 
snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
< soundcore               7457  3 snd
16,19d3
< parport_pc             21249  1
< lp                      9133  0
< parport                35337  2 parport_pc,lp
< usbserial              22057  0
32,34d15
< floppy                 53873  0
< sg                     28257  0
< sr_mod                 14181  0
43c24
< ext3                   92585  2
---
>  ext3                   95401  2 
49c30
< scsi_mod              103953  5 sg,sr_mod,usb_storage,sbp2,sd_mod
---
>  scsi_mod              103953  3 usb_storage,sbp2,sd_mod

[Jef Spaleta]

On Wed, 25 Aug 2004 23:42:17 -0500, Mike Klinke <lsomike(a)futzin.com&gt; wrote:
>  OK, narrowing it down a bit, everything seems to have gone haywire
>  between kernel-2.6.8-1.524 and kernel-2.6.8-1.525.  I suspect it
>  has something to do with:
>  
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130746 
udev... have you followed the instructions in comment #7 of that bug report?
update to udev-030-7 and rerun mkinitrd

specifically what you want to do is make sure you have udev-030-7 installed
then you want to recreate the initrd for the kernel you are running.
example for 2.6.8-1.526:
  backup the old initrd image
mv /boot/initrd-2.6.8-1.526.img  /boot/initrd-2.6.8-1.526.img.bak
  create new initrd image for  2.6.8-1.526
mkinitrd /boot/initrd-2.6.8-1.526.img 2.6.8-1.526
reboot into .6.8-1.526

Make sure you have a kernel to fall back to before you do that
example. Or make sure you know how to edit your grub menu to use the
backup initrd...just in case something goes wrong with the new initrd.

Since initrd images on your system are created when you install the
kernel package, you
have to recreate the initrd image being used to take advantage of the
udev fixes that were created in udev-030-7 package.


-jef


>  
>  but since English is my native language I'm not sure what's going on
>  there but I get the sense that something's gone haywire with
>  autoloading of modules and sure enough, a diff of "lsmod" between
>  the 524 and 525 kernels shows there definitely a problem here:
>  
>  23:31:03 # diff 524-Modules.txt 525-Modules.txt
>  2,13d1
>  < snd_mixer_oss          14017  2
>  < snd_intel8x0           30829  3
>  < snd_ac97_codec         58693  1 snd_intel8x0
>  < snd_pcm                82377  1 snd_intel8x0
>  < snd_timer              25029  1 snd_pcm
>  < snd_page_alloc          8137  2 snd_intel8x0,snd_pcm
>  < gameport                3777  1 snd_intel8x0
>  < snd_mpu401_uart         7232  1 snd_intel8x0
>  < snd_rawmidi            21605  1 snd_mpu401_uart
>  < snd_seq_device          6345  1 snd_rawmidi
>  < snd                    44453  10
>
> snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
>  < soundcore               7457  3 snd
>  16,19d3
>  < parport_pc             21249  1
>  < lp                      9133  0
>  < parport                35337  2 parport_pc,lp
>  < usbserial              22057  0
>  32,34d15
>  < floppy                 53873  0
>  < sg                     28257  0
>  < sr_mod                 14181  0
>  43c24
>  < ext3                   92585  2
>  ---
>  > ext3                   95401  2
>  49c30
>  < scsi_mod              103953  5 sg,sr_mod,usb_storage,sbp2,sd_mod
>  ---
>  > scsi_mod              103953  3 usb_storage,sbp2,sd_mod
>  
>  
>  
>  
>  --
>  fedora-test-list mailing list
>  fedora-test-list(a)redhat.com
>  To unsubscribe:
>  http://www.redhat.com/mailman/listinfo/fedora-test-list
>

[Mike Klinke]

On Thursday 26 August 2004 11:03, you wrote:
 
>  udev... have you followed the instructions in comment #7 of that
>  bug report? update to udev-030-7 and rerun mkinitrd
>
>  specifically what you want to do is make sure you have udev-030-7
>  installed then you want to recreate the initrd for the kernel you
>  are running. example for 2.6.8-1.526: .... 
No I hadn't really tried to digest that bugzilla yet as it appeared 
to quickly turn into "developer-speak" on subjects I'm not familiar 
with.  Thank-you for taking the time to give a quick translation as 
it's quite helpful and I'll revisit this again tonight.

Regards, Mike Klinke

[Alexandre Strube]

Em Qui, 2004-08-26 às 01:01, Mike Klinke escreveu:

>  Seems that somewhere between kernel-2.6.7-1.517 and 
>  kernel-2.6.8-1.526 I seem to have lost the ability to use the 
>  cdrom/dvd player on my VAIO laptop. The /dev/cdrom and /dev/sr0 
>  files which were created under the 517 kernel are no longer created 
>  under the 526 kernel.  If I go back to the 517 kernel as is well. 
>  Is this a known problem or does it need to be investigated further? 
That's odd... I have three or four machines whose cd recorders are no
longer working with fedora2.

[Per Bjornsson]

On Thu, 2004-08-26 at 07:53, Alexandre Strube wrote:
>  That's odd... I have three or four machines whose cd recorders
> are no
>  longer working with fedora2.  
Are you sure about that? It might just be that you updated to kernel
2.6.8 (the 2.6.8-1.521 update RPM) which does SCSI command filtering
unless the user has the capability CAP_SYS_RAWIO. This was put in in
order to prevent ordinary users who happen to have direct access - even
read access - to a drive, e.g. a CD drive, from doing dangerous things
like uploading new firmware. It was tossed in rather shortly before the
release of the 2.6.8 kernel and it has been discovered that the command
list that was allowed was not long enough to e.g. allow CD burning.
Check LKML, work is going on to figure out how to do this sanely.

Try burning a CD as root. If that works, it's in all likelihood the
command filtering that has bitten you. The only quick solution I know of
is to roll back to an earlier kernel version or patch out the filtering
in a custom kernel (both of which of course expose the security hole
that this was supposed to fix).

Cheers,
Per

-- 
Per Bjornsson <perbj(a)stanford.edu&gt;
Ph.D. Candidate, Department of Applied Physics, Stanford University