Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
SiS 7018 + ALSA
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Tue Jan 27, 2004 10:31 pm    Post subject: SiS 7018 + ALSA Reply with quote

Hi all,

kernel 2.6.1(gentoo-dev-sources) is mostly running fine on my laptop; except for sound. I did the same procedure on my desktop and it worked right away. For my laptop I compiled:
Code:
<*> Sound Card Support
<*> Advanced Linux Sound Architecture
<*> Sequencer Support
<*> OSS API emulation
<*> OSS mixer API
<*> OSS PCM (digital audio) API
<*> Trident 4D-Wave DX/NX; SiS 7018

I also enabled
Code:
<*> Gameport support

because I heard this might be needed.
This should be correct, but ALSA reports
Code:
No soundcards found

The "Trident 4D-Wave DX/NX; SiS 7018" as a modules is called snd_trident, which I used for my 2.4.22 kernel (and it worked, of course).
I even tried to enable all sound cards in the kernel, but the ALSA message was the same.
Any ideas what could be wrong here?
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Wed Jan 28, 2004 4:01 pm    Post subject: Reply with quote

By the way, I have tried to compile everything as modules, too. But that did not help it.
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Thu Jan 29, 2004 6:13 pm    Post subject: Reply with quote

Doesn't anyone have an idea? I mean, SiS chipset is quite common...
Back to top
View user's profile Send private message
twstd3bc
Apprentice
Apprentice


Joined: 07 Feb 2003
Posts: 289
Location: Los Angeles, USA

PostPosted: Mon Feb 02, 2004 3:39 am    Post subject: no clue here either Reply with quote

I don't know of anyone who got snd_trident working in kernel 2.6. I'll go look at the alsa mailing list and see...
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Tue Feb 03, 2004 8:12 am    Post subject: Reply with quote

Really? I posted, because I did not find anyone with the same problem. Please post again, if you find any information regarding this subject. Thank you.
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Tue Feb 03, 2004 5:28 pm    Post subject: Possible solution Reply with quote

Hi there.

I have an Amilo laptop with a SiS7012 soundcard, which worked perfectly with 2.4x kernels, and gave a lot of problems with the new 2.6.1...

I've done everything exactly has you did, and it behaved has bad has yours..

But, the solution was rather weird...

rebuild your kernel without MIDI support. :D

I know this sound very very strange, but here are the steps i took:

Code:
emerge alsa-driver && emerge alsa-lib && emerge alsa-utils


if alsa-driver fails to compile with the 2.6.x kernel, read below for a solution i've found, changing the original .ebuild file

Code:
-> Go to the kernel "menuconfig" and de-select [b]everything[/b] related with midi, and all other sound cards


This sounds very strange to me, but the thing is: IT WORKED :D

Maybe the 2.6.x kernel's ALSA, loaded at boot, must have the main sound device loaded at "#0", instead of #1, since #0 was the MIDI device!!

Code:
Compile the kernel and reboot


You should then notice quite a different ALSA report at boot..

Go on, try it, i hope that works for you!

Good luck,
Artur Martins (aka Phk)
---------------------------------------------------

About that alsa-driver problem with the 2.6x kernels:

- edit /usr/portage/media-sound/alsa-driver/alsa-driver-0.9.8.ebuild
- in function src_unpack(), add the following 3 lines (cp command) AFTER the line:
Code:
 epatch ${FILESFIR}/makefile.patch


so that it looks like this:

Code:
 epatch ${FILESFIR}/makefile.patch
cp /usr/src/linux/include/config/modversions.h /var/tmp/portage/alsa-drver-0.9.8/work/alsa-driver-0.9.8/

cp /usr/src/linux/include/config/modversions.h /var/tmp/portage/alsa-drver-0.9.8/work/alsa-driver-0.9.8/include/linux

cp /usr/src/linux/include/config/modversions.h /var/tmp/portage/alsa-drver-0.9.8/work/alsa-driver-0.9.8/linux


I know this is a lousy work-around, but it solves the "modversions.h" problem!

See us around!
Phracker
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Tue Feb 03, 2004 5:29 pm    Post subject: Possible solution for u (worked for me!) Reply with quote

Hi there.

I have an Amilo laptop with a SiS7012 soundcard, which worked perfectly with 2.4x kernels, and gave a lot of problems with the new 2.6.1...

I've done everything exactly has you did, and it behaved has bad has yours..

But, the solution was rather weird...

rebuild your kernel without MIDI support. :D

I know this sound very very strange, but here are the steps i took:

Code:
emerge alsa-driver && emerge alsa-lib && emerge alsa-utils


if alsa-driver fails to compile with the 2.6.x kernel, read below for a solution i've found, changing the original .ebuild file

Code:
-> Go to the kernel "menuconfig" and de-select [b]everything[/b] related with midi, and all other sound cards


This sounds very strange to me, but the thing is: IT WORKED :D

Maybe the 2.6.x kernel's ALSA, loaded at boot, must have the main sound device loaded at "#0", instead of #1, since #0 was the MIDI device!!

Code:
Compile the kernel and reboot


You should then notice quite a different ALSA report at boot..

Go on, try it, i hope that works for you!

Good luck,
Artur Martins (aka Phk)
---------------------------------------------------

About that alsa-driver problem with the 2.6x kernels:

- edit /usr/portage/media-sound/alsa-driver/alsa-driver-0.9.8.ebuild
- in function src_unpack(), add the following 3 lines (cp command) AFTER the line:
Code:
 epatch ${FILESFIR}/makefile.patch


so that it looks like this:

Code:
 epatch ${FILESFIR}/makefile.patch
cp /usr/src/linux/include/config/modversions.h /var/tmp/portage/alsa-drver-0.9.8/work/alsa-driver-0.9.8/
cp /usr/src/linux/include/config/modversions.h /var/tmp/portage/alsa-drver-0.9.8/work/alsa-driver-0.9.8/include/linux
cp /usr/src/linux/include/config/modversions.h /var/tmp/portage/alsa-drver-0.9.8/work/alsa-driver-0.9.8/linux


I know this is a lousy work-around, but it solves the "modversions.h" problem!

See us around!
Phracker
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Tue Feb 03, 2004 5:30 pm    Post subject: (sorry for the repeated post!) Reply with quote

___
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Fri Feb 06, 2004 8:20 pm    Post subject: Reply with quote

@Phx

Good, that it worked for you. Unfortunately, I have a SiS 7018 (not 7012) soundcard.
One question: Why did you compile alsa-DRIVERS??? This support should be given by the kernel or with kernel modules. Have you tried to get your card to work without the alsa-drivers (only libs and utils)?
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Sun Feb 08, 2004 11:01 pm    Post subject: Gentoooooooooooooooooooooooooooooooooo Reply with quote

Why? Cause the kernel drivers didn't work! Now i don't know which ones are working, since the kernel says exactly the same thing before....

Well, at least it works now ;) And yours should works too, the difference of 7018 and 1012 is minimum.....

You should try the MIDI thing, made my speakers sing.. :D
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
ryszardzonk
Apprentice
Apprentice


Joined: 18 Dec 2003
Posts: 225
Location: Rzeszów, POLAND

PostPosted: Mon Feb 09, 2004 10:05 am    Post subject: sis 7018 Reply with quote

i have sis 7018 just like You on te laptoop and I didnt have any problems with it with any 2.6 kernel version. presently i have 2.6.2-mm1 and it worls like a charm

what You shoud do is UNINSTALL alsa-drivers as they are not needed and provided by the kernel sources. what you still need is alsa-libs and alsa-utils. Utils are neesesery for you to get alsamixer which is needed to get any sound from alsa. The mixer is MUTED by default.

anyway what you need to do

1) have every alsa stuff in kernel setup as module ( no defference really, but makes your kernel more stable in case sound so going to get screwed up - that is why everything that is NOT NEEDED for boot should be as module)
2 OPTIONAL)
A --- if your soundcard is not recognized it my be that You need to go back to your PCI settings and check the "CONFIG_PCI_GO_ANY=y" option so it can get access to all PCI resources for probing purposes
B --- other option to chceck is "CONFIG_PCI_NAMES=y"
This should solve yours NO SOUND CARDS FOUND problem

3) after You reboot your new kernel start "alsaconf" which should setup your card properly

4) here you my have to edit modules file by
# nano "/etc/modules.d/alsa" and put Your sound card there which in our case is "snd-trident"
5) then start "alsamixer" (from alsautils) to setup your volume on the sound card
6) last is "rc-update add alsasound boot" without this You wold not get the sound after reboot, becouse with alsa it has to be restored everytime after rebbot and that is what this script does

7) GOOD LUCK :)
_________________
Sky is not the limit...
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Wed Feb 11, 2004 2:14 pm    Post subject: Reply with quote

@ ryszardzonk

Thank you for the cool guide. Unfortunately it did not work for me. "CONFIG_PCI_GOANY=y" (it is not "..GO_ANY=y") and "CONFIG_PCI_NAMES=y" were enabled already. I even tried mm-sources. No success.
I know there is something very strange going on with my notebook. I would be very glad if anybody had other ideas how to fix this for me.

Thanks again, ryszardzonk
Back to top
View user's profile Send private message
jhr0771
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2003
Posts: 90

PostPosted: Wed Feb 11, 2004 7:15 pm    Post subject: Reply with quote

I have and ARM computer with SiS 7018 and it worked with gentoo-dev-sources 2.6.1.
My only problem ( very weird ) is that the sound settings get reseted with every new song I play in XMMS or rhytmbox.
To make it work:
1) emerge -C alsa-driver, alsa-oss . I kept alsa-util and alsa-lib
2) activate the alsa stuff in the kernel as modules
3) reboot and it worked !
Back to top
View user's profile Send private message
ryszardzonk
Apprentice
Apprentice


Joined: 18 Dec 2003
Posts: 225
Location: Rzeszów, POLAND

PostPosted: Wed Feb 11, 2004 9:03 pm    Post subject: hmmm Reply with quote

I have looked at your post again and there is not much more I can help in that matter. I am supprised that it doesnt work, sinse it was the easiest thing for me to set-up and that is basicly wat I did.
Of couse every computer is different and as many users there is there would be that many problems. Myself I am struggling with ACPI FAN & LM_sensors. It doesnt work for me...

I hope you find the solution
_________________
Sky is not the limit...
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Thu Feb 12, 2004 1:29 am    Post subject: Reply with quote

Yeah, it might be my specific notebook. On my other PC it was very easy to set ALSA up, as you already said.
Regarding your ACPI problem: I had a problem with that too. The main reason was that my BIOS was too old. I solved the problem with simply adding
Code:
acpi=force

to my kernel options in grub.conf. After that everything acpi related worked fine.
By the way: I compiled all ACPI stuff into the kernel, not as modules.
Good luck with your ACPI problem.
Back to top
View user's profile Send private message
Smoka
n00b
n00b


Joined: 12 Feb 2004
Posts: 4

PostPosted: Thu Feb 12, 2004 11:47 pm    Post subject: Reply with quote

Had the same Problem.

Could only solve it by choosing an other Kernel (Vanilla 2.6.2).
Used the same .config and it simply worked.
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Fri Feb 13, 2004 2:11 pm    Post subject: Reply with quote

I haven't found your sources in portage. Only vanilla 2.4.24, vanilla prepatch 2.4.25 and vanilla tiny sources 2.6.2 (masked). Did you install the tiny sources?
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Mon Feb 16, 2004 10:40 am    Post subject: Reply with quote

Maybe this helps tracking down the problem:
Code:
Advanced Linux Sound Architecture Driver Version 1.0.2c (Thu Feb 05 15:41:49 2004 UTC).
Trident4DWaveAudio: probe of 0000:00:01.4 failed with error -16
ALSA device list:
  No soundcards found.

This is the part from dmesg that causes the problem.
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Mon Feb 16, 2004 12:33 pm    Post subject: Reply with quote

I think I have come a bit closer. In my opinion ACPI is somehow messing around with the PCI IRQ routing. Adding
Code:
pci=noacpi

to the kernel options gives me:
Code:
Advanced Linux Sound Architecture Driver Version 1.0.2c (Thu Feb 05 15:41:49 2004 UTC).
PCI: Found IRQ 11 for device 0000:00:01.4
PCI: Sharing IRQ 11 with 0000:00:03.0
Trident4DWaveAudio: probe of 0000:00:01.4 failed with error -16
ALSA device list:
  No soundcards found.

while the device which the IRQ is shared with is
Code:
Yenta: CardBus bridge found at 0000:00:03.0 [1584:3000]

This was with mm-sources.

With gentoo-dev-sources and with all PCMCIA stuff disabled I get:
Code:
Advanced Linux Sound Architecture Driver Version 1.0.0rc2.
request_module: failed /sbin/modprobe -- snd-card-0. error = -16
PCI: Assigned IRQ 11 for device 0000:00:01.4
PCI: Sharing IRQ 11 with 0000:00:03.0
Trident4DWaveAudio: probe of 0000:00:01.4 failed with error -16
ALSA device list:
  No soundcards found.

Anyway, I mainly switched to 2.6 because my PCMCIA wireless card was working correctly. So disabling PCMCIA would not be a solution for me.

Any idea on the one?
Back to top
View user's profile Send private message
R!tman
Veteran
Veteran


Joined: 18 Dec 2003
Posts: 1303
Location: Zurich, Switzerland

PostPosted: Fri Mar 12, 2004 12:19 pm    Post subject: Reply with quote

It works flawlessly with mm-sources-2.6.4-r1 :D.

But now bootsplash does not work :(. [edit]And PCMCIA does not seem to work to.[\edit]

I think I will have to wait for gentoo-dev-sources-2.6.4.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum