CD-RW installation problems
SuSE 7.3 2.4.16-4GB kernel I have a Mitsumi CR-480ATE CD-RW drive. I've followed the directions in the CD-Writing HOWTO, but it does not work. My /etc/modules.conf file has these lines: alias char-major-21 sg # cd writer options ide-cd ignore=hdc alias scd0 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd In my lilo.conf file I have this: image = /boot/vmlinuz root = /dev/hda3 label = linux append = "hdc=ide-scsi" I get these complaints in my logfile: May 24 16:26:29 bi165 modprobe: modprobe: pre-install sg failed May 24 16:26:29 bi165 modprobe: modprobe: insmod char-major-21 failed ...those two lines repeated twenty times... May 24 16:26:30 bi165 kernel: paride: version 1.06 installed (parport) May 24 16:26:30 bi165 kernel: pg: pg version 1.02, major 97 May 24 16:26:31 bi165 modprobe: modprobe: Can't locate module paride_protocol May 24 16:26:31 bi165 kernel: pg0: Autoprobe failed May 24 16:26:31 bi165 kernel: pg: No ATAPI device detected May 24 16:26:31 bi165 insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted May 24 16:26:31 bi165 insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters May 24 16:26:31 bi165 insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed I haven't a clue what's wrong, and I'd be grateful for some suggestions. /john -- inet: john@wilkes.com | addr: 321 High School Rd. NE #367 | "The man who views the world at 50 the city: Bainbridge Island, Washington | same as he did at 20 has wasted 30 code: 98110-1697 | years of his life." icbm: 47 37 48 N / 122 29 52 W | - Muhammad Ali
John, I am sorry to alert you to the fact that Mitsumi cdrw drives don't work so well with Linux! I don't know if you have checked the hardware database yet for this model, but I am guessing it will not be listed as a working model. I tried a couple different models of Mitsumi drives a few months back and could not get either of them to work and Mitsumi tech support just flat out say they don't support Linux! I gave up on them and returned the units for an Acer model, that works the best I have seen/used. I am sure some others here can give you details on their working models too. Patrick --------------------------- On Friday 24 May 2002 20:21, John Wilkes wrote:
SuSE 7.3 2.4.16-4GB kernel
I have a Mitsumi CR-480ATE CD-RW drive. I've followed the directions in the CD-Writing HOWTO, but it does not work.
My /etc/modules.conf file has these lines:
alias char-major-21 sg # cd writer options ide-cd ignore=hdc alias scd0 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd
In my lilo.conf file I have this:
image = /boot/vmlinuz root = /dev/hda3 label = linux append = "hdc=ide-scsi"
I get these complaints in my logfile:
May 24 16:26:29 bi165 modprobe: modprobe: pre-install sg failed May 24 16:26:29 bi165 modprobe: modprobe: insmod char-major-21 failed ...those two lines repeated twenty times... May 24 16:26:30 bi165 kernel: paride: version 1.06 installed (parport) May 24 16:26:30 bi165 kernel: pg: pg version 1.02, major 97 May 24 16:26:31 bi165 modprobe: modprobe: Can't locate module paride_protocol May 24 16:26:31 bi165 kernel: pg0: Autoprobe failed May 24 16:26:31 bi165 kernel: pg: No ATAPI device detected May 24 16:26:31 bi165 insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted May 24 16:26:31 bi165 insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters May 24 16:26:31 bi165 insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed
I haven't a clue what's wrong, and I'd be grateful for some suggestions.
/john
-- --- KMail v1.4 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
My CD-RW is a Mitsumi CR-4804TE and so far it works fine under SuSE 7.3 and 8.0, so John's problem may not be the brand of CD writer. On my machine it is /dev/sr0 after ide-scsi emulation assigned that device to what is actually /dev/hdd. The pertinent lines of my /etc/lilo.conf that (among other things) appends the ide-scsi emulation kernel parameter at boot time: image = /boot/vmlinuz label = linux root = /dev/hda2 vga = 791 initrd = /boot/initrd append = " hdd=ide-scsi" --- --- --- On Friday 24 May 2002 19:58, Patrick wrote:
John, I am sorry to alert you to the fact that Mitsumi cdrw drives don't work so well with Linux! [...]
Patrick --------------------------- On Friday 24 May 2002 20:21, John Wilkes wrote:
SuSE 7.3 2.4.16-4GB kernel
I have a Mitsumi CR-480ATE CD-RW drive. I've followed the directions in the CD-Writing HOWTO, but it does not work.
---
On Fri, 24 May 2002, Patrick wrote:
I am sorry to alert you to the fact that Mitsumi cdrw drives don't work so well with Linux! I don't know if you have checked the hardware database yet for this model, but I am guessing it will not be listed as a working model.
If I don't enable hdc=ide-scsi in my lilo.config file, I can mount the Mitsumi drive in the usual fashion with no problem, so as a cdrom device on the ide bus, it works. However, the CR-480ATE is not listed as a working model at lhd.datapower.com. It's a relatively new model 32x12x40x drive, and other similar sounding models are listed as supported in the CD-Writing HOWTO: CR-2401-TS, CR-2600 TE, CR-2801 TE, CR-4801 TE, CR-4802 TE, and CR-4804 TE. My problem seems to be in the ide-scsi setup. It appears that the Mitsumi drive is not seen or recognized. How can I get more information about the failure? The logfile doesn't say much other than it didn't work: May 24 16:26:29 bi165 modprobe: modprobe: pre-install sg failed May 24 16:26:29 bi165 modprobe: modprobe: insmod char-major-21 failed This looks like the driver itself fails to load. I've set things up according to the CD-Writing HOWTO, but I wonder if it is completely up to date. The only one I've seen refers to kernel versions 2.0.x and 2.2.y, but I'm running 2.4.16. Is the setup different for 2.4.x kernels? /jw -- inet: john@wilkes.com | addr: 321 High School Rd. NE #367 | "The man who views the world at 50 the city: Bainbridge Island, Washington | same as he did at 20 has wasted 30 code: 98110-1697 | years of his life." icbm: 47 37 48 N / 122 29 52 W | - Muhammad Ali
I have reloaded SuSE 8.0 several times, first I had to get past a video conflict, then a mouse problem ... OK there but now it always brings me to a command line/prompt rather than X-windows. When I type kde I get a slew of errors. xsetroot: unable to open display ' ' xdpyinfo: unable to open display " " . etc ..... What might be the source of this problem and the solution, please? Thanks! doc
Snip.. startx ? -- ICQ# 55846749 Registered Linux user #191829 A Cherokee Prayer: Oh Great Spirit, Help me always to speak the truth quietly, to listen with an open mind when others speak and to remember the peace that may be found in silence.
Snip..
startx ?
Thanks but unfortunately no ... startx triggers a bazillion errors. "Symbol VBESetVBEMode from module /usr/X11R6/lib/modules/drivers/sis_drv.o is unresolved!" "Fatal server error: Caught signal 11. Server aborting." "XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining." Thanks! doc
startx ?
Thanks but unfortunately no ... startx triggers a bazillion errors.
Just tried "startx | less" so I could look at the error log and saw "/etc/X11/XF86Config" as the source file that triggered the error and "(EE) SIS(0): No valid modes found" Thanks! doc
On Sat, 2002-05-25 at 20:36, doc wrote:
Snip..
startx ?
Thanks but unfortunately no ... startx triggers a bazillion errors.
"Symbol VBESetVBEMode from module /usr/X11R6/lib/modules/drivers/sis_drv.o is unresolved!"
"Fatal server error: Caught signal 11. Server aborting."
"XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining."
Thanks! doc
Sounds like your X server is not configured correctly and that your default runlevel is wrong. 1) Fix X server config by running sax2 If that fails, you can try XF86Setup. This should get your X server running and when you type startx, it should work. 2) Seems like your machine is set up to start in runlevel 3 (Multiuser without graphics) If you want the machine to boot in graphics mode, you need to boot in runlevel 5 (Multiuser with Graphics) YAST should have a setting soemwhere to change this (I am not sure exactly where - maybe somebody else can tell you) You can go and edit a file to change the setting manually: Edit /etc/inittab (NB!! Make sure to make a backup copy first) THere is a line that should look like this: id:3:initdefault: Change the 3 to a 5 Then you system will boot in graphics mode. HTH -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
** Reply to message from John Wilkes <john@wilkes.com> on Sat, 25 May 2002 10:48:35 -0700 (PDT) # This looks like the driver itself fails to load. I've set things up # according to the CD-Writing HOWTO, but I wonder if it is completely up # to date. The only one I've seen refers to kernel versions 2.0.x and # 2.2.y, but I'm running 2.4.16. Is the setup different for 2.4.x # kernels? This guy seems to have the facts: http://www.linuxgaxette.com/issue57/stoddard.html Ed Harrison, broadcasting on ----/ / ---/ / (_) __ __ _ _ _ __ --/ /__ / // \/ // /_/ /\ \/ / -/___//_//_/\_//__,_/ /_/\_\ by SuSE(8.0), Kernel 2.4.18, X 4.2 or Windows98 (running in vmware 3.1 for fun) PolarBarMailer 1.22prev3 with IBM JDK 1.3.1
The "pre-install" lines in modules.conf (as described in Winfried Tr�mper's CD-Writing HOWTO) do not work properly and were the cause of the problem. I found an alternate CD-Writing Mini HOWTO at: http://www.linuxgazette.com/issue57/stoddard.html Its configuration description works. My lilo.conf looks like this: image = /boot/vmlinuz root = /dev/hda3 label = linux append = "hdc=ide-scsi" My modules.conf has these lines: alias scsi_hostadapter ide-scsi options ide-cd ignore=hdc alias scd0 srmod And "cdrecord -scanbus" reports: Cdrecord 1.11a05 (i686-suse-linux) Copyright (C) 1995-2001 J�rg Schilling Linux sg driver version: 3.1.20 Using libscg version 'schily-0.5' scsibus0: 0,0,0 0) 'MITSUMI ' 'CR-48XATE ' '1.0C' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * Finally, KOnCD recognizes the Mitsumi CD Writer. /jw -- inet: john@wilkes.com | addr: 321 High School Rd. NE #367 | "The man who views the world at 50 the city: Bainbridge Island, Washington | same as he did at 20 has wasted 30 code: 98110-1697 | years of his life." icbm: 47 37 48 N / 122 29 52 W | - Muhammad Ali On Fri, 24 May 2002, John Wilkes wrote:
SuSE 7.3 2.4.16-4GB kernel
I have a Mitsumi CR-480ATE CD-RW drive. I've followed the directions in the CD-Writing HOWTO, but it does not work.
My /etc/modules.conf file has these lines:
alias char-major-21 sg # cd writer options ide-cd ignore=hdc alias scd0 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd
In my lilo.conf file I have this:
image = /boot/vmlinuz root = /dev/hda3 label = linux append = "hdc=ide-scsi"
I get these complaints in my logfile:
May 24 16:26:29 bi165 modprobe: modprobe: pre-install sg failed May 24 16:26:29 bi165 modprobe: modprobe: insmod char-major-21 failed ...those two lines repeated twenty times... May 24 16:26:30 bi165 kernel: paride: version 1.06 installed (parport) May 24 16:26:30 bi165 kernel: pg: pg version 1.02, major 97 May 24 16:26:31 bi165 modprobe: modprobe: Can't locate module paride_protocol May 24 16:26:31 bi165 kernel: pg0: Autoprobe failed May 24 16:26:31 bi165 kernel: pg: No ATAPI device detected May 24 16:26:31 bi165 insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted May 24 16:26:31 bi165 insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters May 24 16:26:31 bi165 insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed
I haven't a clue what's wrong, and I'd be grateful for some suggestions.
/john
participants (7)
-
Andre Truter -
Dale Kosan -
doc -
Ed Harrison -
John Wilkes -
Patrick -
Steve D