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 manual
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
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.
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
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.
> &
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
Man
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
> 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 approp
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
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
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
[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.
>
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
>
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 p
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 wor
nounce
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
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
>
>cdu3
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]
-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 n
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 mana
-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
> 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
-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
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
es 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
kerne
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
> 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
> > "cd
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 g
>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 w
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
> > voluntee
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]
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, n
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 o
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"
s information? I was used to the old
"cdu31a=0xPORT,IRQ" syntax from the boot prompt, or as an "append=..." line
in /etc/lilo.conf
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 & Go
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 m
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
38 matches
Mail list logo
