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

[wes schreiner]

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!!


Ah yes, Quick boot must be disabled, PCIbuspower must be on, etc., like 
all the TP600[EX] FAQs say. 

> 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.


On this hardware the sound devices are single open, that means only one 
program can use the sound hardware at any one time.  If a second program 
tries to open a sound device then you get errors like the above.  Make 
sure there isn't any other program using the sound devices.  
Alternately, if your setup has a sound daemon running (arts, esound) 
then you might want to only use programs that work with your sound 
daemon, or else you need to stop the sound daemon before running a 
program that wants to access the sound devices itself.

> 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!


That's OK,  that line says that the driver that monitors your PC-Card 
slots will not probe those addresses.  That's what you want because your 
sound hardware is already using them.

>> >/ 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


For a 600E that's not the right way to go about it.  There are several 
drivers that will work or almost work with the sound hardware, and if 
you don't get the right one you will either have no sound (like with the 
cs4610 driver) or you won't be able to access the full capabilities of 
the hardware.  You're OK now.

>
>> 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.


Hey, Bert didn't write that, I did.  And the smiley face means I know 
that it is possible to unload modules without rebooting, but I was lazy 
so I just rebooted.


It sounds like you have it working now, you just need to sort out your 
sound-using programs.

wes