[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Sarge: Falscher CD-Treiber haelt Rechner fuer 1 Minute an.



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hallo,

bei meinem PC mit Debian Sarge haelt ein CD-Treiber (insmod versucht auf 
einmal den Treiber zu laden) den Rechner alle 2 - 3 Stunden fuer ca. eine 
Minute an (selbst die Uhr bleibt stehen).

Im Rechner sind zwei IDE CD/DVD Laufwerke eingebaut 
  LG GSA 40801B	DVD-Brenner
  LG GCC 4520B	CD/DVD Combo Laufwerk
Beide Laufwerke werden ueber den ide-scsi Treiber angesprochen. 

Bei den Treibern die Probleme machen scheint es sich aber um Treiber fuer alte 
CD-Rom Laufwerke zu handeln (mit extra Schnittstellenkarte).
Auch mit den Kernel pc2004 2.4.24-1-686 oder pc2004 2.4.25-1-686 gab es die 
Probleme.

Wieso versucht insmod auf einmal Treiber zu laden?
Ich bin fuer jeden Tipp dankbar.

Vielen Dank und Gruss Rupert Wenzel
 


Ausgabe von uname -a:
Linux pc2004 2.4.26-1-686 #1 Sat May 1 18:04:05 EST 2004 i686 GNU/Linux


Ausgabe von cat /etc/modules:

# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a "#", and everything on the line after them are ignored.

usb-uhci
input
usbkbd
keybdev
8139too
apm
soundcore
ide-scsi
ohci1394
agpgart
usb-storage
msdos
vfat
floppy
loop
radeon
usbmouse


Ausgabe von dmesg (zum Zeitpunkt als der Rechner nicht reagierte, ca, 1 Stunde 
nach dem booten ):

ide_setup: hda=ide-scsi
ide_setup: hdc=ide-scsi
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
hda: HL-DT-ST DVDRAM GSA-4081B, ATAPI CD/DVD-ROM drive
hdc: HL-DT-ST RW/DVD GCC-4520B, ATAPI CD/DVD-ROM drive
hda: attached ide-scsi driver.
hdc: attached ide-scsi driver.
...
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
sr0: scsi3-mmc drive: 32x/32x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Sony CDU-535: probing base address 340
Did not find a Sony CDU-535 drive
sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed 
Jul 26 04:24:10 EDT 2000
sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
sbpcd-0 [04]:  No drive found.
sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed 
Jul 26 04:24:10 EDT 2000
sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
sbpcd-0 [04]:  No drive found.
sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed 
Jul 26 04:24:10 EDT 2000
sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
sbpcd-0 [04]:  No drive found.
sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed 
Jul 26 04:24:10 EDT 2000
sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
sbpcd-0 [04]:  No drive found.
sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed 
Jul 26 04:24:10 EDT 2000
sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
sbpcd-0 [04]:  No drive found.
mcd: initialisation failed - No mcd device at 0x300 irq 11
SJCD: Sanyo CDR-H94A cdrom driver version 1.7.
SJCD: Resetting: .......... reset failed, no drive found.
Trying to free nonexistent resource <00000340-00000343>
optcd: unknown drive detected; aborting


Ausgabe in /var/log/syslog (nur die Zeilen zum Treiber Problem):

Jul 11 12:52:26 pc2004 kernel: sbpcd-0 [04]:  No drive found.
Jul 11 12:52:26 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/sbpcd.o: init_module: 
Input/output error
Jul 11 12:52:26 pc2004 insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more information in syslog or the output from dmesg
Jul 11 12:52:26 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/sbpcd.o: insmod 
block-major-25 failed
Jul 11 12:52:26 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/cdu31a.o: init_module: 
Input/output error
Jul 11 12:52:26 pc2004 insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more information in syslog or the output from dmesg
Jul 11 12:52:26 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/cdu31a.o: insmod 
block-major-15 failed

Jul 11 12:52:31 pc2004 kernel: mcd: initialisation failed - No mcd device at 
0x300 irq 11
Jul 11 12:52:31 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/mcd.o: init_module: 
Input/output error
Jul 11 12:52:31 pc2004 insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more information in syslog or the output from dmesg
Jul 11 12:52:31 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/mcd.o: insmod 
block-major-23 failed
Jul 11 12:52:41 pc2004 kernel: SJCD: Sanyo CDR-H94A cdrom driver version 1.7.
Jul 11 12:52:41 pc2004 kernel: SJCD: Resetting: .......... reset failed, no 
drive found.
Jul 11 12:52:41 pc2004 kernel: Trying to free nonexistent resource 
<00000340-00000343>

Jul 11 12:52:42 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/sjcd.o: init_module: 
Input/output error
Jul 11 12:52:42 pc2004 insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more information in syslog or the output from dmesg
Jul 11 12:52:42 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/sjcd.o: insmod 
block-major-18 failed
Jul 11 12:52:54 pc2004 kernel: optcd: unknown drive detected; aborting
Jul 11 12:52:54 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/optcd.o: init_module: 
Input/output error
Jul 11 12:52:54 pc2004 insmod: Hint: insmod errors can be caused by incorrect 
module parameters, including invalid IO or IRQ parameters.       You may find 
more information in syslog or the output from dmesg
Jul 11 12:52:54 pc2004 
insmod: /lib/modules/2.4.26-1-686/kernel/drivers/cdrom/optcd.o: insmod 
block-major-17 failed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA8SbCnkv8DVU91lMRAqGtAJ9otpJLK5TU2DxJLaUmLPaTUrxBoQCgmSfm
ax34OD9mvIET3auOMoXi9Rg=
=njlC
-----END PGP SIGNATURE-----



Reply to: