cdrom cdu31a y kernel 2.4
Tengo un lector de cdrom de sony cdu31a que no es atapi sino que necesita una tarjeta de interface particular, Me funcionaba perfectamente en linux pero... recientemente he instalado la versión 2.4.9 del kernel y la unidad de cdrom me ha dejado de funcionar. Realmente puedo montar discos e incluso ver los directorios pero al acceder a un fichero, por ejemplo para mostrarlo en pantalla con less, da un error de segment fault llegando a veces a bloquear completamente al ordenador. ¿Donde me aconsejáis que pida/busque ayuda? (Parece ser que no hay actualmente un mantenedor activo para ese driver) gracias...
Re: cdu31a
Thanks for the hints! The problem is that my controller is a SC400 ( card shown in commented text in cdu31a.c ) but the ports suggested are not working I get a resource busy message from kernel even if I specify explicitly cdy31a_port=0x634 which should be my port! ( as reported in card manuals ) Why? On other computer I got similar problem on modular ppa, but resolved problem with correct module dependencies! But in this case a `depmod -a` not resolved the problem. Thanx, Andrea!
cdu31a
Hi to all! I have an old sony cdu33a 2x cd! The problem is that no docs are provided about which io_port I should use. The DOS driver don't tell me the values! The manifacturer of the audio card / controller have retired ( was Reveal ) and all the hints in cdu31a.c don't work! I'm using kernel 2.2.1 on hamm. What can I do? Thanks!!! Andrea
Re: cdu31a
Hello Andrea, The kernel sources list the following as possible addresses: { 0x340, 0 },/* Standard configuration Sony Interface */ { 0x1f88,0 },/* Fusion CD-16 */ { 0x230, 0 },/* SoundBlaster 16 card */ { 0x360, 0 },/* Secondary standard Sony Interface */ { 0x320, 0 },/* Secondary standard Sony Interface */ { 0x330, 0 },/* Secondary standard Sony Interface */ { 0x634, 0 },/* Sound FX SC400 */ { 0x654, 0 },/* Sound FX SC400 */ In my experience, I found it often at 0x330 or 0x300, or 0x2c0 (not all of those are listed.) If all else fails, try each of those and see if you get it to work. Hint: compile it as a module and specify it on the command line so you don't have to compile and reboot so many times. Andrea Novara [EMAIL PROTECTED] writes: Hi to all! I have an old sony cdu33a 2x cd! The problem is that no docs are provided about which io_port I should use. The DOS driver don't tell me the values! The manifacturer of the audio card / controller have retired ( was Reveal ) and all the hints in cdu31a.c don't work! I'm using kernel 2.2.1 on hamm. What can I do? Thanks!!! Andrea -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Sony CDU31A CD on SB16
Hello, I installed the Debian distribution base floppies and everything went OK except for one thing. I was not able to setup the CD drive and this prevents me from going on with installing other portions from the distribution CD. My system is a 486 and has a Sony CD type CDU31A-2 connected to a Sound Blaster 16 (the type that supports 3 kinds of CD drives - Sony, Mitsumi and NEC). I know this is a very old CD drive but this is what I have at the moment for this system. I could not find in the list of drivers one that will work with my configration. I tried the one that is for a Sony CDU31A and I tried the one for SB Pro. Does Linux support this configuration? Is there a different driver? Does anybody know what is the base address for the CD port on the SB16 (there is a jumper to set the IRQ but no setup that I can see for the base address - is it the same base address as the SB itself, and only a different IRQ?) I am new to this list, can it be recieved in digest form once or twice a day, or only as separate messages? Thanks, Gilad -- -- Gilad Barak Fruitonics Ltd. Product Manager P.O.B 2358, Rehovot 76123, Israel Tel: +972-8-947-7088 [EMAIL PROTECTED] Fax: +972-8-947-7099 --
/dev entry for cdu31a device
Hello all, What is the proper /dev entry for a Sony proprietary cdu31a device? I don't see a cdu31a device in dev and don't know how to access it otherwise. Thanks in advance. Martin Jackson: [EMAIL PROTECTED] === Information Science Major Mankato State University === -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /dev entry for cdu31a device
On Sun, Mar 01, 1998 at 09:05:57AM +0100, Paul Seelig wrote: [EMAIL PROTECTED] (Martin Jackson) writes: What is the proper /dev entry for a Sony proprietary cdu31a device? I don't see a cdu31a device in dev and don't know how to access it otherwise. Thanks in advance. This should be /dev/sonycd if i'm not severely mistaken. At least this used to work with my own cdu33a CD-ROM drive. The kernel's Documentation/devices.txt says /dev/sonycd is correct for cdu31a and cdu33a devices. hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Sony cdu31a problem
On Mon, 13 Jan 1997, Matt Lawrence wrote: I'm trying to install Debian 1.2 off of the Dec. InfoMagic CDs. After typing in cdu31a=0x340 at the boot prompt, the kernel recognizes the CD drive, but there isn't an entry in /dev. It's easy enough to create one, but I don't know the appropriate major and minor device numbers. Any suggestions? By the way, the drive is hooked to a Sony controller. -- Matt Matt, I think the /dev entry you want is /dev/sonycd I have the same kind of drive, and I didn't need to create the device. Off the wall wild guess, I think the major number was 15. I can't be sure right now since my Debian machine is down with a dead power supply, but that is my vague memory... Since you probably only have one, the minor should be 0 Anyway check out http://sunsite.unc.edu/mdw/HOWTO/CDROM-HOWTO-4.html, it has a section on the cdu31a. Hope this helps. - Don - Don Prezioso Ashland University Phone: (419) 289-5015 System Programmer/Analyst 401 College Avenue E-mail: [EMAIL PROTECTED] Administrative Computing Ashland, OH 44805 http://www.ashland.edu/~dprez -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Sony cdu31a problem
At 05:08 PM 1/13/97 -0500, Don Prezioso wrote: I think the /dev entry you want is /dev/sonycd I have the same kind of drive, and I didn't need to create the device. Off the wall wild guess, I think the major number was 15. I can't be sure right now since my Debian machine is down with a dead power supply, but that is my vague memory... Since you probably only have one, the minor should be 0 Anyway check out http://sunsite.unc.edu/mdw/HOWTO/CDROM-HOWTO-4.html, it has a section on the cdu31a. It really was a major number of 15. Thanks for the help. So far, only the Slackware installation has actually been able to talk to the CD, Red Hat and Debian failed. Now I'll be able to finish installing Debian. Minor rant: It wasn't that long ago that the CDU31A was one of the few CDs supported by Linux. Now, it seems that it's considered old technology and ignored. Considering that I'm running on a 33MHz 386, I think that older machines still have a lot of life left in them, particularly with Linux. -- Matt -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Sony cdu31a problem
I'm trying to install Debian 1.2 off of the Dec. InfoMagic CDs. After typing in cdu31a=0x340 at the boot prompt, the kernel recognizes the CD drive, but there isn't an entry in /dev. It's easy enough to create one, but I don't know the appropriate major and minor device numbers. Any suggestions? By the way, the drive is hooked to a Sony controller. Here's the entry for your reference: brw-r--r-- 1 root root 15, 0 Dec 27 18:23 /dev/sonycd -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] | -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Sony cdu31a problem
Hmm, I have installed Debian from a machine with both a CDU31A and a CDU33A (the 33A is functionally identical to the 31A). Neither gave me any problems with Debian, although RedHat did have some problems. It really was a major number of 15. Thanks for the help. So far, only the Slackware installation has actually been able to talk to the CD, Red Hat and Debian failed. Now I'll be able to finish installing Debian. Minor rant: It wasn't that long ago that the CDU31A was one of the few CDs supported by Linux. Now, it seems that it's considered old technology and ignored. Considering that I'm running on a 33MHz 386, I think that older machines still have a lot of life left in them, particularly with Linux. -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] | -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Sony cdu31a problem
I'm trying to install Debian 1.2 off of the Dec. InfoMagic CDs. After typing in cdu31a=0x340 at the boot prompt, the kernel recognizes the CD drive, but there isn't an entry in /dev. It's easy enough to create one, but I don't know the appropriate major and minor device numbers. Any suggestions? By the way, the drive is hooked to a Sony controller. -- Matt -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cdu31a
On 14 Nov 1996 [EMAIL PROTECTED] wrote: A friend is trying to convert to Debian from Slakware. He's using buzz-fixed off an Info Magic cdrom, and can't get the installation boot disk to recognize his cdu31a. At the lilo prompt, he's type linux cdu31a=0x230,0 This lilo parameter worked fine under slakware. Any suggestions? This gave me the hardest time of installation too and i lost two days being without a reasonably working system trying to find this out and reinstalling numerous times until Bruce gave me the right advice: Try: modprobe cdu31a cdu31a_port=0x340 cdu31a_irq=5 If you use modconf (the module configuration menu) use the arguments cdu31a_port=0x340 cdu31a_irq=5 Adapt as needed. It's all stated in the kernel documentation included with the sources which are not present upon the stage of the base system installation. And the information *present* during installation time is somewhat misleading because the old scheme of passing parameters to LILO doesn't work with the new 2.0.xx kernels. This should be revised in the setup configuration. Or is it already for Debian-1.2 release? P. *8^) -- Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cdu31a
[EMAIL PROTECTED] wrote: Package: disks-i386 Version: 1996-07-14 A friend is trying to convert to Debian from Slakware. He's using buzz-fixed off an Info Magic cdrom, and can't get the installation boot disk to recognize his cdu31a. At the lilo prompt, he's type linux cdu31a=0x230,0 This lilo parameter worked fine under slakware. Any suggestions? Thanks, -- Raul -- The easiest way is to install cdu31a as a module during setup. Use 'cdu31a_port=0x230' as the parameter. You should get a success message. If not ask for more help. Michael -- This message was distributed manually by [EMAIL PROTECTED] after the list initially failed to distribute it.
cdu31a
Package: disks-i386 Version: 1996-07-14 A friend is trying to convert to Debian from Slakware. He's using buzz-fixed off an Info Magic cdrom, and can't get the installation boot disk to recognize his cdu31a. At the lilo prompt, he's type linux cdu31a=0x230,0 This lilo parameter worked fine under slakware. Any suggestions? Thanks, -- Raul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Can't install cdu31a
Hi. I am trying to install debian, but not having much luck getting it to recognize my sony cd-rom. I am using 'linux cdu31a=0x340' at the boot prompt. When I get to the device driver configuration menu and try to install 'cdu31a' it says it can't initialize. It works fine under Win 3.1 and Win95. Now what? Robin --- RD in Internet video and speech recogition using C++ and Java http://jumpsite.com San Diego, CA 619-457-1159 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Fix for CDU31A driver in 2.0.23 and 2.1.5 (fwd)
Something went wrong with my posting which was supposed to include this message from c.o.l.a., so here it is again! P. *8^) -- Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -- Forwarded message -- Date: 30 Oct 1996 11:21:23 GMT From: Corey Minyard [EMAIL PROTECTED] Newsgroups: comp.os.linux.announce Subject: Fix for CDU31A driver in 2.0.23 and 2.1.5 Followup-To: comp.os.linux.development.system -BEGIN PGP SIGNED MESSAGE- Well, I managed to screw up the CDU31A driver. I couldn't test the patch I sent Linus because my interface board is broken; it looked right (my daughter has been waking me up at 5:00 every morning and everything looks right when you are tired :-), so I applied it. Well, it was wrong. The following fix has been tested and does seem to work. Sorry for the problem. - -- Corey Minyard Internet: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] UUCP: [EMAIL PROTECTED] - --- linux/drivers/cdrom/cdu31a.c.old Sun Oct 20 22:25:06 1996 +++ linux/drivers/cdrom/cdu31a.cSun Oct 20 22:30:31 1996 @@ -1915,7 +1915,9 @@ int num_tracks; - - num_tracks = sony_toc.last_track_num - sony_toc.first_track_num + 1; + num_tracks = ( bcd_to_int(sony_toc.last_track_num) + - bcd_to_int(sony_toc.first_track_num) ++ 1); for (i = 0; i num_tracks; i++) { if (sony_toc.tracks[i].track == track) @@ -2486,8 +2488,8 @@ i=verify_area(VERIFY_WRITE, hdr, sizeof(*hdr)); if(i0) return i; - - loc_hdr.cdth_trk0 = sony_toc.first_track_num; - - loc_hdr.cdth_trk1 = sony_toc.last_track_num; + loc_hdr.cdth_trk0 = bcd_to_int(sony_toc.first_track_num); + loc_hdr.cdth_trk1 = bcd_to_int(sony_toc.last_track_num); memcpy_tofs(hdr, loc_hdr, sizeof(*hdr)); } return 0; @@ -2567,8 +2569,8 @@ return i; memcpy_fromfs(ti, (char *) arg, sizeof(ti)); - - if ( (ti.cdti_trk0 sony_toc.first_track_num) - - || (ti.cdti_trk0 sony_toc.last_track_num) + if ( (ti.cdti_trk0 bcd_to_int(sony_toc.first_track_num)) + || (ti.cdti_trk0 bcd_to_int(sony_toc.last_track_num)) || (ti.cdti_trk1 ti.cdti_trk0)) { return -EINVAL; @@ -2587,7 +2589,7 @@ * If we want to stop after the last track, use the lead-out * MSF to do that. */ - - if (ti.cdti_trk1 = sony_toc.last_track_num) + if (ti.cdti_trk1 = bcd_to_int(sony_toc.last_track_num)) { log_to_msf(msf_to_log(sony_toc.lead_out_start_msf)-1, (params[4])); -BEGIN PGP SIGNATURE- Version: 2.6.3i Charset: noconv iQCVAwUBMnc5vYQRll5MupLRAQFuWwQA0yV7RepUXhf+NibP/b1BrALkA+okYjkx VLXA5IaldTC4yu0otZijXnNdVm7PuVyCrBrcNtHzDJPYzB6cJ62ded/bDaRY6fkg DN1UGTrhm2raZAfJNU3aWT7ErFrplRLScdmV66sw8WR0uHCZiuioDgnu/yPhZi6I VRz9zk9EtH0= =T8EF -END PGP SIGNATURE- -- This article has been digitally signed by the moderator, using PGP. http://www.iki.fi/liw/lars-public-key.asc has PGP key for validating signature. Send submissions for comp.os.linux.announce to: [EMAIL PROTECTED] PLEASE remember a short description of the software and the LOCATION. This group is archived at http://www.iki.fi/liw/linux/cola.html -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
need help from someone who has gotten their SONY cdu31a working
Would someone who has gotten their SONY cdu31a working please walk through the process with this user? Thanks Bruce From: The Darter [EMAIL PROTECTED] Hi Bruce! A friend of send me this: Run the module configuration, and add the arguments cdu31_port=3D0x cdu31a_irq=3DX Fill in your I/O port address and IRQ as appropriate. Bruce I have make this, but it will don't run with it. :( This is my hardware-configuration: CD-ROM Sony cdu33a direct connected with a Soundblaster 16 ASP MultiCD (Hardware-IRQ on card 10) This is the Error-Message: not detected the cdrom-format (at every cd's) Please, help me. Your Detlef Zober -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
cdu31a
Run the module configuration, and add the arguments cdu31_port=0x cdu31a_irq=X Fill in your I/O port address and IRQ as appropriate. Bruce -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Sony CDU31A not recognized at all!?
-BEGIN PGP SIGNED MESSAGE- Try: modprobe cdu31a cdu31a_port=0x340 cdu31a_irq=5 If you use modconf (the module configuration menu) use the arguments cdu31a_port=0x340 cdu31a_irq=5 Yeah, wow! This did the trick! But why is it not documented in the help text which is accessible at boot up of the installation disks by pressing the key F4? It wrongly suggests to add as parameter cdu31a=0x3XX,X or something like that. This even sounds rather plausible if you know this already from other more or less broken distributions! This is definitely a bug in the installation routine! What a pity that i lost so much time trying to find it out... Well, i think it's time to compose some kind of an Debian-Installation-FAQ just for these kind of cases. An FAQ of this kind would have saved me and probably others lots of time and frustration. Anybody interested in contributing to such an FAQ? Let's see if i can manage to maintain it and learn from it! BTW, i didn't succeed installation anyway. :-( After my CD drive was recognized and the bad-links-fix package from i-Connect (i received a broken Debian-1.1.5 CD from them) was installed as described in their README i could use dselect to select my packages and everything. (This 'dselect' is to my mind a rather awkward program and i didn't enjoy installation with it very much...) But after completion of all selections when i started 'Install' i just got following error message (i wrote it down at home and went to our institute for mailing it): - -cut-here-- Running dpkg -iGROEB /tmp/Debian-1.1.6/stable/binary-i386 find: /tmp/Debian-1.1.6/stable/binary-i386/admin/sudo_1.4.4-2.deb: No such file or directory find: /tmp/Debian-1.1.6/stable/binary-i386/base/mount_2.5l-1.deb: No such file or directory dpkg: subprocess find returned error exit status 1 installation script returned error exit status 1. Press RETURN to continue. - -cut-here-- Well, i tried continuation and repeated everything various times. The files which are not found by find are definetely there right in the place as reported in the error message. They are just there waiting for 'find' and this damn 'find' just chooses to ignore them for whatever reason there is!? Can't 'find' handle symbolic links on a CD ROM? At this point i just had to give in. Looks like a case for i-Connect anyway... I think this is just incredible! When i was a complete clueless newbie who didn't even know how to pronounce UNIX or Linux and was a complete Windoze addict one and a half year ago i managed to setup a Slackware based system due to proper documentation in little more than a day. And up to this moment i barely managed to install a Debian-1.1 base system since friday evening being stuck again on monday morning... This ain't no good! I'd really wish it to be easier for a non informatics guy like me! Maybe i should switch to Redhat, but i like the idea behind Debian and GNU and actually want to install it on two Linux boxes which i am maintaining at our institute. But these frustrating experiences with my testdrive at my private box give me something to think about... Well, now it is almost 2:30 in the middle of the night and i am tired, pretty desillusioned and rather frustrated about my Debian experiences so far. I'll go home to sleep now and hope to get my Debian system up and running some time really soon. I depend on a Linux box and i definitely want it to be a GNU/Debian machine in any case! Good night, Paul *8^) __ Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: latin1 Comment: 'finger -l [EMAIL PROTECTED]' for public key iQCVAwUBMjNjgOgqiw1XE3/lAQGh2QP+PSfedWmjKLv9NAO7R23BvYS5QMK3aaeN 3CLK7WJKV/VsMpgtW8UqVsMuVN7LFVIZLyblvBslSDMQHlF/bSUWz6VPMd+50Clk 9fhfcxXxAjTIWzA0ExtWdQxk8g0i5QNY+/hDsQSrX7KgI5dtKJucFr97JdvPpbl0 RK4ihDYbCRc= =MOGv -END PGP SIGNATURE-
Re: Sony CDU31A not recognized at all!?
Hi Paul -- You said: Well, i think it's time to compose some kind of an Debian-Installation-FAQ just for these kind of cases. An FAQ of this kind would have saved me and probably others lots of time and frustration. Anybody interested in contributing to such an FAQ? Let's see if i can manage to maintain it and learn from it! Have you found the FAQ (published on any Debian site in the directory doc/FAQ) to be inadequate? If so, can you suggest some changes? (This is not meant tongue-in-cheek. I don't know if you missed it, or if it just didn't help.) Susan Kleinmann
Re: Sony CDU31A not recognized at all!?
-BEGIN PGP SIGNED MESSAGE- Hi Susan! Have you found the FAQ (published on any Debian site in the directory doc/FAQ) to be inadequate? If so, can you suggest some changes? The FAQ you mention is great for a general overview regarding Debian. Actually i downloaded the old and the new version of the FAQ prior to nuking my old Linux setup and read it. Not every line of it but at least the stuff that was important to my mind. Right now at this moment i got my Debian system at least running with X and PPP, so that i can at least access the net. At last! Dselect was so nice as not to install the software after selection as described before but i tried installation from the command line using dpkg and switching back to dselect for choosing what i wanted to be installed. This dselect may be a great invention technically but for easy installation by a newbie it definitely is a nuisance! Sorry if i hurt somebody's feelings... The kind of FAQ i was suggesting would be supposed to cover more specific installation topics and traps like the one i escaped with Bruce's tips after a too long period of anger trying to get it running. You know, there are these small details which make a debuting Debian user get stuck already upon installation and i'd propose to cover these topics in an Debian-Installation.FAQ. Thanks a lot, Paul *8^) __ Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: latin1 Comment: 'finger -l [EMAIL PROTECTED]' for public key iQCVAwUBMjQ+5ugqiw1XE3/lAQEbTQQAi5b7p2qeZTk2K81LuutWg4UxVwiVFBXb uqczbAWjI0+x3Vvle6/uP8jgQVlRtb5gOsVQWsO8KCEgWIiLI0zImEmMy59ysE+q lEDlP6NuYTbH5GIi/ffI6QUjjTyKUQ6QtzpofEpuToNipCOhtFPcqX/WXBobG1UZ B2g3V2ximdE= =rw51 -END PGP SIGNATURE-
Re: Sony CDU31A not recognized at all!?
You may be giving the module the wrong argument (for that version, at least). Try modprobe cdu31 cdu31a=0x340,5 . Also, add ,PAS to that if you are using the CD connector on a Pro Audio Spectrum card. Thanks Bruce
Re: Sony CDU31A not recognized at all!?
-BEGIN PGP SIGNED MESSAGE- On Sat, 7 Sep 1996, Bruce Perens wrote: You may be giving the module the wrong argument (for that version, at least). Try modprobe cdu31 cdu31a=0x340,5 . Also, add ,PAS to that if you are using the CD connector on a Pro Audio Spectrum card. Until now i tried installation maybe 8 or 9 times, maybe more (i didn't count). Everything went fine but the cdu31a doesn't become recognized in no way whatever i do. I tried so far: 1.) At booting of the install boot disk: Adding parameter as cdu31a=0x340,5, naturally without the `' and as i don't have a PAS i didn't pass any information about one to the kernel. As a variation i put a few times cdu31a=0x340,05 but this was not very succesful either. 2.) After installation of the base system via the setup screen as offered by the debian install: I choose CDU-31-A as CD drive module and tried to install it with the parameters 0x340,5. Output: Initialisation of cdu31a failed. 3.) After reboot of the system with the newly installed kernel from a custom boot disk: I tried installion of the module with insmod cdu31a but again the only output was just Initialisation of cdu31a failed. In /dev there is no entry cdu31a to be found and trying to execute ./MAKEDEV cdu31a yields a Don't know how to make /dev/cdu31a or something similar (I'm not at home right now to check the exact strings). I don't understand this by no means. I'll try the way you wrote, Bruce, but i suspect there is a typo in your prescription? Shouldn't it better be modprobe cdu31a cdu31a=0x340,5? ^^^ I don't have a PAS and use the interface card provided by Sony. Maybe i should tell the kernel definitely that there is no PAS at all with something like PAS=0? Thank you, Paul *8^) __ Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: latin1 Comment: 'finger -l [EMAIL PROTECTED]' for public key iQCVAwUBMjMLc+gqiw1XE3/lAQGLdQP/UMwpsBvFf086z7FfuWseUy2Ytttq4J6y AlpvIRpuDiBT9gnP37WO6cxMQ98jHADo2ul2s3LsFTnlCLnXVOFBAQeArhqfhjhI cFc2Xpfv/TiRXGGdtuiCGSA5jvpFmaCBoq4Kap+jTCU2USLjZSgi9IS3v9gYRgkD DGI9bXmvia8= =Gc1a -END PGP SIGNATURE-
Re: Sony CDU31A not recognized at all!?
I choose CDU-31-A as CD drive module and tried to install it with the parameters 0x340,5. Oh darn. I gave the wrong advice. Try: modprobe cdu31a cdu31a_port=0x340 cdu31a_irq=5 If you use modconf (the module configuration menu) use the arguments cdu31a_port=0x340 cdu31a_irq=5 Thanks Bruce
Sony CDU31A not recognized at all!?
-BEGIN PGP SIGNED MESSAGE- Hi all! Yesterday evening i started installation of Debian-1.1.5 being well aware about the need to use the bad_links_fix_1.1.5.tgz for fixing some troubles related with the spoiled CD-ROM which i received like a few others too. Using the 1,44 diskimages in buzz/disks-i386/current/ i managed without any major problem to partition my harddrive and install a base system. BTW, this is a well designed setup procedure to my mind. But here installation is over for me. My Sony CD-ROM drive CDU31A doesn't get recognized at all by the debian kernel, whereas there never was any problem with this for one year and a half with a Slackware-based setup. Also Win95 has no problems with this drive. Trying to install a loadable module via insmod or the Debian installation routines just yields a Initialization of cdu31a failed. When giving the kernel the proper I/O adress and IRQ like it worked before (0x340,5) has no impact at all. In /dev there is not even mention made of a 'cdu31a' although there exists a 'cdu31a.o' in the place where all modules are to be found. My machine is a Vesa Local Bus 486DX-33 with 20MB RAM, two harddrives and the CDU31A on a ISA CD-ROM controller by Sony. This is my first encounter with Debian as well as with the 2.xx generation of the Linux kernel. I tried pretty everything to find out why the drive is not recognized. I even read the documentation provided on the CD-ROM by I-Connect and on the Debian WWW server. Regrettably the man pages are still not accesible with the barebones base installation. Right now i'm checking the Debian mailing list archives at http://www.debian.org/Lists-Archives; but i didn't find any hint so far... Well, i can't proceed with the installation and i am pretty disappointed up to this point that i'm so helpless right now. I need Linux for my everyday work and really need to have a working system ASAP. I'd really hope it is some dumb error of myself which prevents initialization of the CD drive but i just can't figure this out. Do you need more information or is this sufficient for having an idea about what is possibly a solution? TIA, Paul *8^) __ Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: latin1 Comment: 'finger -l [EMAIL PROTECTED]' for public key iQCVAwUBMjGfUOgqiw1XE3/lAQGfZwP/SgDKq6KUaubacHilpFXjYwUrxL28QtNZ bUyOFIPXLv7aaxXZwcA9SQmknrxlxQjJMG98Pr6nZDSEn5ZwQ0CNCSGtlVH5N2vi 7px+rr8eJQeKvVaSwg3+BVFnWyE7do0b4Wds6TqFx6YM35e1KHCfUv/gs1nhRCRV Afo67e151yU= =nRUM -END PGP SIGNATURE-
Re: module cdu31a fails on insert
From: [EMAIL PROTECTED] (renald loignon) May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf I don't see that it is documented at all outside of the kernel source. And if you think that this is a serious problem in Debian, it is. And it's not going to be helped unless more people like you volunteer to work on the documentation. Is there any chance you have checked the bootparm-howto? http://sunsite.unc.edu/mdw ?? If it is not in there, I would suggest that would be the best place for it. -- Todd Fries .. [EMAIL PROTECTED]
Re: module cdu31a fails on insert
Todd Is there any chance you have checked the bootparm-howto? Todd Todd http://sunsite.unc.edu/mdw ?? If you install Debian's doc-linux package, they are also at /usr/doc/HOWTO/* As the doc-linux package is updated monthly with the upstream HOWTOs, you should always look for the newest one in unstable/binary-all/doc. Safe to install on any system as it's only text. Hard to put a bug into that :-) -- Dirk Eddelbuttel http://qed.econ.queensu.ca/~edd
Re: module cdu31a fails on insert
Susan: I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments to document the arguments that can be given to a module when it is activated? I don't think the cdu31a information is in there - we must have missed it when we created modconf. Also, not everyone uses modconf, which is the only thing that displays the module_help files. We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. Thanks Bruce
Re: module cdu31a fails on insert
Bruce Perens: We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. Ilucius ([EMAIL PROTECTED]) took it from me, but I'm not sure if we bothered to tell anyone. (Ilucius, perhaps you can confirm this.) -- Rural sizes win [EMAIL PROTECTED] http://www.iki.fi/liw/ Please don't Cc: me when replying to my message on a mailing list. pgpQLHOsAAaAZ.pgp Description: PGP signature
Re: module cdu31a fails on insert
On Tue, 20 Aug 1996, Lars Wirzenius wrote: Bruce Perens: We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. Ilucius ([EMAIL PROTECTED]) took it from me, but I'm not sure if we bothered to tell anyone. (Ilucius, perhaps you can confirm this.) Yep, your right. I neglected to inform anyone. (face red in shame) I've been playing around with this architecture independence stuff that I COMPLETELY forgot about it. But, since I'll be without a modem for a few days, I'll take the time to scan the kernel source for any additions/differences. Leland __ Y_ a_ m_ b_ o_ | The leanest, meanest, fightinest sweet tater on Earth! oo o oo o o | o o o | [EMAIL PROTECTED] o ooo o | -- -- -- -- -- -- | http://www.millcomm.com/~llucius (maybe one day)
Re: module cdu31a fails on insert
Susan: I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments to document the arguments that can be given to a module when it is activated? I don't think the cdu31a information is in there - we must have missed it when we created modconf. Also, not everyone uses modconf, which is the only thing that displays the module_help files. We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. I hear you Bruce. I most certainly do not wish to put down the fine efforts that you and the rest of the Debian group are putting in. Also, I consider it quite likely that I will eventually get involved (again) in some non-profit group or other having to do with computer software and/or the Internet. (In fact, been there, done that, if you will give some consideration to some 5 years of involvement in Fidonet at many levels). Honesty, whether I join the Linux camp or another will depend on the success of my current efforts to bootstrap myself into this community. For now, most of my on-line interactions are done with Eudora for Windows (email), Free Agent (news) , WsFTP and Netscape for Windows. Thus, as a example of obstacle to my progression, I cannot easily grab a set of HTMLized FAQs from the Net for local perusal because they use long filenames. Also, I am constrained to getting the msdos-i386 branch of the distribution sites, even though dselect seems to be somewhat reluctant to use these DOS filenames... And if I start seriously considering the purchase of a CD copy of the distribution, to give dselect the long filenames it prefers, I have to face a non-documented module argument... taking on the whining voice of Gilda Radner's Roseanne Roseannadanna When it's not one thing, it's another... ;-))) Hey, don't let me spoil your fun. Whenever I point out a flaw in the Debian distribution, I do it in the spirit of providing useful feedback, and with no malice whatsoever. Consider it my first level of contribution to your fine work. Hopefully, in the fullness of time I will feel confident and knowledgeable enough to participate in more significant ways. In the meantime, I'm still here, so despite my setbacks, I haven't given up Regards, renald
Re: module cdu31a fails on insert
Lars: Ilucius ([EMAIL PROTECTED]) took it from me From: llucius [EMAIL PROTECTED] Yep, your right. I neglected to inform anyone. (face red in shame) I've been playing around with this architecture independence stuff that I COMPLETELY forgot about it. Leland, of course I'm happy to get any work you do on this now. You are also one of the lead programmers on the 68k port, and you are a lead programmer on the issue of architecture independence for Debian. One of our problems is that a few key volunteers do a _lot_ of stuff, and tasks should be distributed better so that those key people can continue to have lives and health :-) So I won't frown if you eventually find someone else to take on the job of tracking modules. Thanks Bruce
Re: module cdu31a fails on insert
From: [EMAIL PROTECTED] (renald loignon) May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf I don't see that it is documented at all outside of the kernel source. And if you think that this is a serious problem in Debian, it is. And it's not going to be helped unless more people like you volunteer to work on the documentation. Thanks Bruce -- Clinton isn't perfect, but I like him a lot more than Dole. Please register to vote, and vote for Democrats. Bruce Perens AB6YM [EMAIL PROTECTED]http://www.hams.com/
Re: module cdu31a fails on insert
Bruce Perens wrote: From: [EMAIL PROTECTED] (renald loignon) May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf I don't see that it is documented at all outside of the kernel source. I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments to document the arguments that can be given to a module when it is activated? ?, Susan Kleinmann
module cdu31a fails on insert
I am installing debian 1.1.1 from the August Pacific Hi Tech CD on my Gateway 200 PS-60. Things go OK until I try to add the cdu31a module to support the CDU33A CDROM drive in the Gateway: it fails to insert. The drive is defaulted onto 0x340; when I try to add a parameter to the module insertion it either fails the same way or gives me an invalid parameter message. So perhaps I am providing the parameter in the wrong format (could not find any documentation with the distribution on the format of module parameters) - or something else is wrong. Everything works OK using Slackware 3.0 kernel 1.2.13 with cdu31a support in the kernel. Thanks, Michael Laing
Re: module cdu31a fails on insert
From: [EMAIL PROTECTED] Things go OK until I try to add the cdu31a module to support the CDU33A CDROM drive in the Gateway: it fails to insert. The drive is defaulted onto 0x340; when I try to add a parameter to the module insertion it either fails the same way or gives me an invalid parameter message. Use the argument cdu31a_port=0x340 when you install the module. It also understands cdu31a_irx=N. Bruce -- Clinton isn't perfect, but I like him a lot more than Dole. Please register to vote, and vote for Democrats. Bruce Perens AB6YM [EMAIL PROTECTED]http://www.hams.com/
Re: module cdu31a fails on insert
Hi Michael! On Sun, 18 Aug 1996 [EMAIL PROTECTED] wrote: The drive is defaulted onto 0x340; when I try to add a parameter to the module insertion it either fails the same way or gives me an invalid parameter message. Have you tried with the following parameter? cdu31a_port=0x340 Bye Good Luck! Pablo B.
Re: module cdu31a fails on insert
Use the argument cdu31a_port=0x340 when you install the module. It also understands cdu31a_irx=N. May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf