Re: no cd/dvd devices detected after kernel change

2008-07-29 Thread Joe Hickey
  Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected
  as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work
  perfectly. When I boot 2.6.25-2-686-bigmem, no entries for these
  devices appear in /dev.

snip dmesg and lsmod output

 I'm not sure this is relevant but when I modinfo on ide_cd_mod it 
 shows : 
 
 filename:   /lib/modules/2.6.25-2-686/kernel/drivers/ide/ide-cd_mod.ko
 license:GPL
 alias:  ide-cd
 alias:  ide:*m-cdrom*
 description:ATAPI CD-ROM Driver
 depends:ide-core,cdrom
 vermagic:   2.6.25-2-686 SMP mod_unload 686
 parm:   ignore:charp
 
 Note the description : *ATAPI* CD-ROM Driver. In the dmesg of your 
 bigmem kernel your drivers seems to be recognize as SATA, not ATAPI.
 
 There's nothing about GSA-H55L in your dmesg ? Because on your normal 
 kernel there is the name of the drives, not in the bigmem kernel. Is 
 the lspci output the same for both kernels ?

 Thomas Preud'homme

Thanks for your reply. GSA-H55L doesn't appear in dmesg for the bigmem kernel, 
nor do any
references to DVD drives. Both appear when booting 2.6.4-1-686. 

Comparing outputs of lspci for the two kernels, there is a difference
for the following device:
03:00.0 IDE interface [0101]: Marvell Technology Group Ltd. 8
Subsystem: ASUSTeK Computer Inc. Device [1043:82a2]

In the standard issue kernel, lspci reports:
Kernel driver in use: pata_marvell
Kernel modules: pata_marvell

But the bigmem kernel:
Kernel driver in use: ahci
Kernel modules: ahci, pata_marvell

Might this be the issue? I tried adding ahci to /etc/modprobe.d/blacklist and 
rebooting the bigmem kernel, but the dvd devices are still not detected.

-- 
Joe Hickey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: no cd/dvd devices detected after kernel change

2008-07-29 Thread Joe Hickey
On Tue, Jul 29, 2008 at 07:51:04PM +0100, Joe Hickey wrote:
   Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected as
   /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work perfectly.
   When I boot 2.6.25-2-686-bigmem, no entries for these devices appear in
   /dev.
 
 snip dmesg and lsmod output
 
  I'm not sure this is relevant but when I modinfo on ide_cd_mod it shows : 
  
  filename:   /lib/modules/2.6.25-2-686/kernel/drivers/ide/ide-cd_mod.ko
  license:GPL alias:  ide-cd alias:  ide:*m-cdrom*
  description:ATAPI CD-ROM Driver depends:ide-core,cdrom vermagic:
  2.6.25-2-686 SMP mod_unload 686 parm:   ignore:charp
  
  Note the description : *ATAPI* CD-ROM Driver. In the dmesg of your bigmem
  kernel your drivers seems to be recognize as SATA, not ATAPI.
  
  There's nothing about GSA-H55L in your dmesg ? Because on your normal kernel
  there is the name of the drives, not in the bigmem kernel. Is the lspci
  output the same for both kernels ?
 
  Thomas Preud'homme
 
 Thanks for your reply. GSA-H55L doesn't appear in dmesg for the bigmem kernel,
 nor do any references to DVD drives. Both appear when booting 2.6.4-1-686. 
 
 Comparing outputs of lspci for the two kernels, there is a difference for the
 following device: 03:00.0 IDE interface [0101]: Marvell Technology Group Ltd.
 8 Subsystem: ASUSTeK Computer Inc. Device [1043:82a2]
 
 In the standard issue kernel, lspci reports: Kernel driver in use:
 pata_marvell Kernel modules: pata_marvell
 
 But the bigmem kernel: Kernel driver in use: ahci Kernel modules: ahci,
 pata_marvell
 
 Might this be the issue? I tried adding ahci to /etc/modprobe.d/blacklist and
 rebooting the bigmem kernel, but the dvd devices are still not detected.
 

I solved this problem by adding 'pata_marvell' to /etc/initramfs-tools/modules
and then rebuilding the initial boot image by typing 'sudo update-initramfs -u'.

My guess is that pata_marvell wasn't being loaded early enough. Is
this behaviour a bug/regression in the kernel, or just a quirk of my setup? 

-- 
Joe Hickey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: no cd/dvd devices detected after kernel change

2008-07-29 Thread Thomas Preud'homme
Le mardi 29 juillet 2008, Joe Hickey a écrit :
 On Tue, Jul 29, 2008 at 07:51:04PM +0100, Joe Hickey wrote:
Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are
detected as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and
cdrom1, and work perfectly. When I boot 2.6.25-2-686-bigmem, no
entries for these devices appear in /dev.
 
  snip dmesg and lsmod output
 
   I'm not sure this is relevant but when I modinfo on ide_cd_mod it
   shows :
  
   filename:  
   /lib/modules/2.6.25-2-686/kernel/drivers/ide/ide-cd_mod.ko
   license:GPL alias:  ide-cd alias: 
   ide:*m-cdrom* description:ATAPI CD-ROM Driver depends:   
   ide-core,cdrom vermagic: 2.6.25-2-686 SMP mod_unload 686 parm:   
  ignore:charp
  
   Note the description : *ATAPI* CD-ROM Driver. In the dmesg of
   your bigmem kernel your drivers seems to be recognize as SATA,
   not ATAPI.
  
   There's nothing about GSA-H55L in your dmesg ? Because on your
   normal kernel there is the name of the drives, not in the bigmem
   kernel. Is the lspci output the same for both kernels ?
  
   Thomas Preud'homme
 
  Thanks for your reply. GSA-H55L doesn't appear in dmesg for the
  bigmem kernel, nor do any references to DVD drives. Both appear
  when booting 2.6.4-1-686.
 
  Comparing outputs of lspci for the two kernels, there is a
  difference for the following device: 03:00.0 IDE interface [0101]:
  Marvell Technology Group Ltd. 8 Subsystem: ASUSTeK Computer Inc.
  Device [1043:82a2]
 
  In the standard issue kernel, lspci reports: Kernel driver in use:
  pata_marvell Kernel modules: pata_marvell
 
  But the bigmem kernel: Kernel driver in use: ahci Kernel modules:
  ahci, pata_marvell
 
  Might this be the issue? I tried adding ahci to
  /etc/modprobe.d/blacklist and rebooting the bigmem kernel, but the
  dvd devices are still not detected.

 I solved this problem by adding 'pata_marvell' to
 /etc/initramfs-tools/modules and then rebuilding the initial boot
 image by typing 'sudo update-initramfs -u'.

 My guess is that pata_marvell wasn't being loaded early enough. Is
 this behaviour a bug/regression in the kernel, or just a quirk of my
 setup?

I don't think so. Did you try to load this module at the end of the 
boot ? This module isn't necessary to boot thus you can boot correctly 
so it should be able to be loaded (is that still correct english ???) 
at any moment. The problem is more that the module isn't being loaded 
automatically, with the same conf for both kernels.

Sorry not being able to help you more and I'm glad you finally manage to 
make it works with your bigmem kernel.


 --
 Joe Hickey



-- 
Thomas Preud'homme

Why Debian : http://www.debian.org/intro/why_debian


signature.asc
Description: This is a digitally signed message part.


Re: no cd/dvd devices detected after kernel change

2008-07-21 Thread Thomas Preud'homme
Le dimanche 20 juillet 2008, Joe Hickey a écrit :
 Hello,

 Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected
 as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work
 perfectly. When I boot 2.6.25-2-686-bigmem, no entries for these
 devices appear in /dev.

 With the working kernel, the relevant part of dmesg is:

 scsi7 : SCSI emulation for USB Mass Storage devices
 usb-storage: device found at 2
 usb-storage: waiting for device to settle before scanning
 ata5.00: ATAPI: HL-DT-STDVD-RAM GSA-H55L, 1.05, max UDMA/66
 ata5.01: ATAPI: HL-DT-ST DVD-ROM GDR-H30N, 1.00, max UDMA/33
 usb 7-2: new low speed USB device using uhci_hcd and address 2
 ata5.00: configured for UDMA/66
 usb 7-2: configuration #1 chosen from 1 choice
 ata5.01: configured for UDMA/33
 BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00
 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00

 With the bigmem kernel, what looks like the corresponding part of
 dmesg:

 [0.812202] PCI: Setting latency timer of device :03:00.0 to
 64 [0.812281] scsi5 : ahci
 [0.812455] scsi6 : ahci
 [0.812583] scsi7 : ahci
 [0.812645] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED] port
 0xfeaffd00 irq 16
 [0.812705] ata6: SATA max UDMA/133 abar [EMAIL PROTECTED] port
 0xfeaffd80 irq 16
 [0.812765] ata7: DUMMY
 [0.874732] usb 7-1: configuration #1 chosen from 1 choice
 [0.875046] scsi8 : SCSI emulation for USB Mass Storage devices
 [0.875218] usb 7-1: New USB device found, idVendor=04b4,
 idProduct=6830

 There are no error messages referring to the DVD drives elsewhere in
 dmesg.

 There's a slight difference in the output of lsmod | grep ide between
 the two kernels. For the working kernel:

 ide_cd 36224  0
 cdrom  32512  2 ide_cd,sr_mod
 ide_core  108292  2 ide_cd,generic

 For the bigmem kernel that doesn't detect the drives:

 ide_cd_mod 33632  0
 cdrom  32640  2 sr_mod,ide_cd_mod
 ide_pci_generic 4996  0 [permanent]
 ide_core  101624  2 ide_cd_mod,ide_pci_generic

 I have ide-core, ide-cd, cdrom and sr_mod listed in /etc/modules to
 try to ensure relevant stuff gets loaded at boot.

 I'd appreciate any advice about next steps for tracking down the
 problem.

 Best,
 --
 Joe Hickey

I'm not sure this is relevant but when I modinfo on ide_cd_mod it 
shows : 

filename:   /lib/modules/2.6.25-2-686/kernel/drivers/ide/ide-cd_mod.ko
license:GPL
alias:  ide-cd
alias:  ide:*m-cdrom*
description:ATAPI CD-ROM Driver
depends:ide-core,cdrom
vermagic:   2.6.25-2-686 SMP mod_unload 686
parm:   ignore:charp

Note the description : *ATAPI* CD-ROM Driver. In the dmesg of your 
bigmem kernel your drivers seems to be recognize as SATA, not ATAPI.

There's nothing about GSA-H55L in your dmesg ? Because on your normal 
kernel there is the name of the drives, not in the bigmem kernel. Is 
the lspci output the same for both kernels ?

Hope this help

-- 
Thomas Preud'homme

Why Debian : http://www.debian.org/intro/why_debian


signature.asc
Description: This is a digitally signed message part.


no cd/dvd devices detected after kernel change

2008-07-20 Thread Joe Hickey
Hello,

Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected as
/dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work
perfectly. When I boot 2.6.25-2-686-bigmem, no entries for these
devices appear in /dev.

With the working kernel, the relevant part of dmesg is:

scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
ata5.00: ATAPI: HL-DT-STDVD-RAM GSA-H55L, 1.05, max UDMA/66
ata5.01: ATAPI: HL-DT-ST DVD-ROM GDR-H30N, 1.00, max UDMA/33
usb 7-2: new low speed USB device using uhci_hcd and address 2
ata5.00: configured for UDMA/66
usb 7-2: configuration #1 chosen from 1 choice
ata5.01: configured for UDMA/33
BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00
0B:00 0C:07 0D:00 0E:00 0F:00 

With the bigmem kernel, what looks like the corresponding part of
dmesg:

[0.812202] PCI: Setting latency timer of device :03:00.0 to 64
[0.812281] scsi5 : ahci
[0.812455] scsi6 : ahci
[0.812583] scsi7 : ahci
[0.812645] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED] port
0xfeaffd00 irq 16
[0.812705] ata6: SATA max UDMA/133 abar [EMAIL PROTECTED] port
0xfeaffd80 irq 16
[0.812765] ata7: DUMMY
[0.874732] usb 7-1: configuration #1 chosen from 1 choice
[0.875046] scsi8 : SCSI emulation for USB Mass Storage devices
[0.875218] usb 7-1: New USB device found, idVendor=04b4,
idProduct=6830

There are no error messages referring to the DVD drives elsewhere in
dmesg.

There's a slight difference in the output of lsmod | grep ide between
the two kernels. For the working kernel:

ide_cd 36224  0 
cdrom  32512  2 ide_cd,sr_mod
ide_core  108292  2 ide_cd,generic

For the bigmem kernel that doesn't detect the drives:

ide_cd_mod 33632  0 
cdrom  32640  2 sr_mod,ide_cd_mod
ide_pci_generic 4996  0 [permanent]
ide_core  101624  2 ide_cd_mod,ide_pci_generic

I have ide-core, ide-cd, cdrom and sr_mod listed in /etc/modules to
try to ensure relevant stuff gets loaded at boot.

I'd appreciate any advice about next steps for tracking down the
problem.

Best,
-- 
Joe Hickey


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]