Rene Herman a écrit : > Hulin Thibaud wrote: > >> I have now the Ubutu version Dapper 6.06 (related 1st june 2006), >> with the kernel Linux 2.6.15-23-386. I have the same errors with my >> old kernel 2.6.12-10 : pnpdump and alsaconf don't fall the soundcard. > > Well, it's rather amazing, seeing as how your computer (a Pentium 1 > laptop) isn't exactly new but I'm looking at 2.6.15 here now and it > indeed also has no (PnP-BIOS) support for your onboard CS4236. That > support is new to 2.6.16.
It's a pentium 1 MMX, 233 Mhz... > Look at it this way -- your computer is still so advanced it needs the > very latest Linux kernel to function completely. Great isn't it? Of course, that's great ! > I asked around, and it appears that Ubuntu does not yet have a 2.6.16 > kernel available either. Them releasing with 2.6.15 is in fact a bit > strange but nothing I can do about that. I'm really quite reluctant to > make you compile a new kernel (or ALSA) yourself though. The added bit > in 2.6.16 is just the "works magically" PnP-BIOS support so let's try if > we can just enable the thing manually (if needed) and then tell the > driver to not use pnp. > > Your Crystal PNPBIOS devices were 00:0f and 00:10. In the directories: > > /sys/devices/pnp0/00:0f > > and > > /sys/devices/pnp0/00:10 > > there should be files named "resources". If you do a: > > cat /sys/devices/pnp0/00:0f/resources I obtain : state = active io 0x210-0x217 > does it say "state = disabled" and nothing more? If so, try a: > > echo auto >/sys/devices/pnp0/00:0f/resources I obtain nothing in sudo mode, or, in user mode : -bash: /sys/devices/pnp0/00:0f/resources: Permission denied > It should now look something like (that cat again): > > state = disabled > io 0x534-0x537 > io 0x388-0x38b > io 0x220-0x22f > irq 5 > dma 1 > dma 0 > > Then, do a: > > echo activate >/sys/devices/pnp0/00:0f/resources Idem for the both mode > after which that "state = disabled" should have been changed to "state = > active". Ie, you should now have something like > > state = active > io 0x534-0x537 *1 > io 0x388-0x38b *2 > io 0x220-0x22f *3 > irq 5 *4 > dma 1 *5 > dma 0 *6 > > If it already looked like this before you echoed anything into the > resource file, all the better! Good ! > For 00:10 (the CTRL port) you should, possibly again after echoing that > "auto" and "activate" into the resource file, you should have: > > cat /sys/devices/pnp0/00:10/resources > state = active > io 0x538-0x53f *7 OK, I actived that and I obtain with the cat command : state = active io 0x530-0x537 io 0x388-0x38b io 0x220-0x22f irq 5 dma 1 dma 0 > All still well? If so, we can try loading the driver. I already made you > try this with the values as given here, so I'm hoping your values are > different and it will work this time. Try: > > modprobe snd-cs4236 isapnp=0 port=*1 cport=*7 irq=*4 dma1=*5 dma2=*6 > > substituting the *N items with the values from the resources files as > numbered. I supose this is a question about io numbers, but which choose ? I used sudo modprobe snd-cs4236 isapnp=0 port=0x530 cport=0x388 irq=5 dma1=1 dma2=0 I obtained this : CS4232+ soundcard not found or device busy FATAL: Error inserting snd_cs4236 (/lib/modules/2.6.15-23-386/kernel/sound/isa/cs423x/snd-cs4236.ko): No such device > Did it work? Please? Aaaaah? And with snd-cs4232 and those same Aaaah...! And with snd-cs4232 : ALSA /home/hulin/alsa-driver-1.0.11rc5/isa/cs423x/../../alsa-kernel/isa/cs423x/cs4236.x:294: CS4232 WSS PnP manual resources are invalid, using auto config CS4232 WSS PnP configure failed for WSS (out of resources ?) PnP BIOS detection failed for CS4232 CS4232 soundcard not found or device busy FATAL: Error inserting snd_cs4232 (/lib/modules/2.6.15-23-386/kernel/sound/isa/cs423x/snd-cs4232.ko): No such device > If it did work, you'd need to do that same echoing into that resource > file that you did on every boot -- you could do this from your > "rc.local" startup file if needed. If you didn't need any echoing (ie, > your BIOS already actived everything, as is likely) you can just always > load the driver with those parameters. To just need a "modprobe > snd-cs4236", you can say in /etc/modprobe.d/alsa-base (I believe that's > where ubuntu puts it but I'm not an ubuntu or debian user) > > options snd-cs4236 isapnp=0 port=*1 cport=*7 irq=*4 dma1=*5 dma2=*6 > >>> And a last resort for now: >>> >>> modprobe snd-sb8 port=0x220 irq=5 dma8=1 >> Hey ! No error ! >> With xmms, I have music ! >> But sound is very bad... How can I improve that ? > > Well, you could play a bit with volumes in ALSA mixer to see if it > improves but this is the wrong driver anyway. It's just that the Crystal > chip _has_ a soundblaster compatible part so it can be used, but the > chrystal driver should be preferred. It is good to know that it does > work since that will mean that at least your BIOS has enabled that part > of the chip. > > I'm hoping that with the above things will work. I can imagine it all > looks a bit clumsy if you're a new Linux user but due to some weird > reason the PnP-BIOS support for your chip was only added very recently > and due to some other weird reason Ubuntu is not using 2.6.16 but > 2.6.15. As indicated, on 2.6.16 "modprobe snd-cs4232" should be all you > need, and alsaconf should be able to figure that all out as well. > > Rene. New after using alsaconf 1.0.11cr : The soundcard selection found two cards on my system : cs4232 snd-cs4232 legacy Probe legacy ISA (non-PnP) chips It modify /etc/modprobe.d/sound and /etc/modprobe.conf In the first, I read alias snd-card-0 snd-cs4232 and alias sound-slot-0 snd-cs4232 The second don't exist. And no information about io ! I continu with alsa conf. I obtain : "OK, sound driver is configured".. for adjustements volume, use your favorite mixer So, I type alsamixer, and I see : alsamixer: function snd_ctl_open failed for default: No such device And XMMS don't work. Ahhhh ! Near of the goal ? _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
