[ltp] tp 600E + sound: HELP!!!

[Mauro Maroni]

Put cs46xx and snd-cs46xx on your /etc/hotplug/blacklist to avoid loading 
those modules.

On Wed, 1 Jan 2003, davide wrote:

> Great! googling in the web I found what was my error: I still had the Quick Boot enabled in the bios.
> After disabling this I had to re-initialize the bios but now I can hear sounds!!
> I still have a problem with mp3s:
> ALSA lib pcm_hw.c:1057:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy
> but I hope to fix it up.
> 
> By the way, I've seen in dmesg these lines
> 
> Yenta ISA IRQ mask 0x0298, PCI irq 11
> Socket status: 30000006
> Yenta ISA IRQ mask 0x0298, PCI irq 11
> Socket status: 30000020
> cs: cb_alloc(bus 5): vendor 0x10ec, device 0x8139
> PCI: Enabling device 05:00.0 (0000 -> 0003)
> cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
> cs: IO port probe 0x0800-0x08ff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> ALSA ../../alsa-kernel/pci/cs46xx/cs46xx_lib.c:3943: hack for Thinkpad 600E (unsupported) enabled
> ALSA ../../alsa-kernel/pci/cs46xx/cs46xx_lib.c:3166: create - never read codec ready from AC'97
> ALSA ../../alsa-kernel/pci/cs46xx/cs46xx_lib.c:3167: it is not probably bug, try to use CS4236 driver
> Sound Fusion CS46xx soundcard not found or device busy
> CS461x PCI: 50100000[8192]
> gameport0: CS461x Gameport speed 1420 kHz
> 
> first I  have to say to ALSA not to use the snd-cs46xx ...
> but I'm a bit worried for the line
> 
> cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x388-0x38f 0x3b8-0x3df 0x4d0-0x4d7
> 
> what does it mean? 0x220 and 0x388 are both used by the soundcard!
> 
> 
> > >/ It seems the kernel can only find the pci accelerator (as win95 call 
> /> >/ it) and it can only insmod the gameport (cs461x + gameport).
> /
> > I don't don't think you want to do this, you only have a physical 
> > joystick port if you have a dock. 
> 
> well, I just tried compiling every driver could be attached to this card in hope for hints for getting sound working
> 
> > What version of ALSA do you have?
> 
> I have the 1.0.4
> 
> > I don't need the isapnp=0 because when I compile ALSA I have ISA PNP 
> > support configured out.  If you are using a vendor kernal and modules 
> > you probably need it.
> 
> since I'm doing experiments I've left it: at least I have "ignoring isapnp=0..."
>  
> > If it's panicing you have other problems.  If your options line is 
> > incorrect it should merely fail to find the card and not load the 
> > module.  Try it from a fresh boot with no other modules loaded, if 
> > possible.   The oops is written to the console, not standard error, so 
> > that's why you can't redirect it.  Does it not show up in 
> > /var/log/kern.log or /var/log/messages? 
> 
> in slackware there's no kern.log, in messages there's nothing.
> Since I resetted the bios I haven't had more panics... let's hope!
> 
> //> Make sure your ALSA modules are built for the kernel 
> > you are running, if you are not building modules and kernel yourself.  
> 
> yes, I am.
> 
> > Bert Haskins wrote:
> > Now, after reloading ALSA (the easy way is to just reboot ;-))
> 
> in the alsa-driver-1.0.4 there is a script (utils/alsasound) to load-unload alsa drivers.
> I've attached it.
> 
> davide
> 
> 
> 
>