Sign in to follow this  
Followers 0
hacnslash

slack sound

16 posts in this topic

I have an integrated VIA VT8235 sound card, and I have installed all the drivers and all that shit, the modules load on startup.....but when I start kde the sound server cant start cuz it cant find /dev/dsp....and I have no idea what to do, there is a dev/dsp file but it has 0 bytes, should there be something in it???

0

Share this post


Link to post
Share on other sites

It isn't a really file, it is a device. If you are trying to use it as a user other than root then you might not have permissions to that device.

If that is the problem a nice chmod 666 /dev/dsp would solve that.

If it complains device not found then there probably is a problem with the drivers.

Another thing, I highly advise against using artsd if you don't need it. It often causes more problems than it solves. Check ps -ax also to see if artsd is automatically being loaded, a very common problem with sound cards which only allow one process to access the dsp at once.

0

Share this post


Link to post
Share on other sites

kay, thanks, ill check the drivers again, and yeah I am logged in as root, I havent gotten to setting up a seond account (ill do it soon)

0

Share this post


Link to post
Share on other sites

well, it was the drivers, I tried alsa again, but no luck, then I tried oss, and it did work, it thinks i have a vt8233 but thats fine with me as long as I can hear shit out o my speakers, speaking of speakers im using a pair I havent used in like 2 years and damn, they sound like shit man, tinny and very raw, kind of a preproduction feel.......

dammit I just now figured out that oss is comercial, dammit, 20 bucks, they can shove it!!!!!!

0

Share this post


Link to post
Share on other sites

And remember that the defualts for sound is MUTED.. so open kmix or gmix if your in X and turn everythign up, then just control your volume through your speakers.. thats what I do.

Also is always upgrading, i would really check them out.. I had a yamaha-dx based card that was crappy and wouldnt work.. alsa got it up and blasting ICP within the hour.

0

Share this post


Link to post
Share on other sites

The funny think is I have a fear of clowns due to being beaten by one at a young age.. thankfully its only visualy induced. :)

0

Share this post


Link to post
Share on other sites

BTW, I still can't get the sound up and running in slack9, I installed some alsa drivers, but now it loads up this shitload of modules, that are not used by anything, damn, I have to rtfm...........

w00t, im listetning to nirvana right now!!!!!!!alsa kicks ass

0

Share this post


Link to post
Share on other sites

ok, im stumped, I reinstalled slackware and I cannot get the same fukking alsa version to install, that I had on my previous install!!!! at the end of make install it gives me these errors about a pcmcia module, and its a pc so I dont have a fukkin pcmcia port! what is goin on here?? and another question, before on my previous install I had installed alsa, but then could not get mplayer to compile, now I have gotten mplayer to compile and install but cant do alsa!!! is there any beef goin on between them?

ok, here is the error part:

make[2]: Entering directory `/root/downloads/alsa/2/alsa-driver-0.9.2/pcmcia/vx'

gcc -D__KERNEL__ -DMODULE=1 -I/root/downloads/alsa/2/alsa-driver-0.9.2/include -I/usr/include -O2 -mpreferred-stack-boundary=2 -march=i486 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -DKBUILD_BASENAME=vxpocket -c -o vxpocket.o vxpocket.c

vxpocket.c:35:28: pcmcia/version.h: No such file or directory

In file included from vxpocket.c:36:

vxpocket.h:26:29: pcmcia/cs_types.h: No such file or directory

vxpocket.h:27:23: pcmcia/cs.h: No such file or directory

vxpocket.h:28:27: pcmcia/cistpl.h: No such file or directory

vxpocket.h:29:23: pcmcia/ds.h: No such file or directory

In file included from vxpocket.c:36:

vxpocket.h:32: parse error before "dev_info_t"

vxpocket.h:32: warning: no semicolon at end of struct or union

vxpocket.h:48: parse error before '*' token

vxpocket.h:48: warning: type defaults to `int' in declaration of `dev_list'

vxpocket.h:48: warning: data definition has no type or storage class

vxpocket.h:49: parse error before '}' token

vxpocket.h:66: parse error before "dev_link_t"

vxpocket.h:66: warning: no semicolon at end of struct or union

vxpocket.h:67: warning: type defaults to `int' in declaration of `node'

vxpocket.h:67: warning: data definition has no type or storage class

vxpocket.h:78: parse error before '*' token

vxpocket.h:78: warning: type defaults to `int' in declaration of `snd_vxpocket_attach'

vxpocket.h:78: warning: data definition has no type or storage class

vxpocket.h:79: parse error before "dev_link_t"

vxpocket.h:79: warning: function declaration isn't a prototype

vxpocket.c:59: conflicting types for `irq_list'

vxpocket.h:39: previous declaration of `irq_list'

vxpocket.c:60: conflicting types for `ibl'

vxpocket.h:40: previous declaration of `ibl'

vxpocket.c:97: parse error before "dev_info"

vxpocket.c:97: warning: type defaults to `int' in declaration of `dev_info'

vxpocket.c:97: warning: initialization makes integer from pointer without a cast

vxpocket.c:97: warning: data definition has no type or storage class

vxpocket.c:121: variable `hw_entry' has initializer but incomplete type

vxpocket.c:122: unknown field `dev_info' specified in initializer

vxpocket.c:122: warning: excess elements in struct initializer

vxpocket.c:122: warning: (near initialization for `hw_entry')

vxpocket.c:125: unknown field `index_table' specified in initializer

vxpocket.c:125: warning: excess elements in struct initializer

vxpocket.c:125: warning: (near initialization for `hw_entry')

vxpocket.c:126: unknown field `id_table' specified in initializer

vxpocket.c:126: warning: excess elements in struct initializer

vxpocket.c:126: warning: (near initialization for `hw_entry')

vxpocket.c:127: unknown field `enable_table' specified in initializer

vxpocket.c:127: warning: excess elements in struct initializer

vxpocket.c:127: warning: (near initialization for `hw_entry')

vxpocket.c:128: unknown field `irq_mask_p' specified in initializer

vxpocket.c:128: warning: excess elements in struct initializer

vxpocket.c:128: warning: (near initialization for `hw_entry')

vxpocket.c:129: unknown field `irq_list' specified in initializer

vxpocket.c:129: warning: excess elements in struct initializer

vxpocket.c:129: warning: (near initialization for `hw_entry')

vxpocket.c:130: unknown field `ibl' specified in initializer

vxpocket.c:130: warning: excess elements in struct initializer

vxpocket.c:130: warning: (near initialization for `hw_entry')

vxpocket.c:133: unknown field `hardware' specified in initializer

vxpocket.c:133: warning: excess elements in struct initializer

vxpocket.c:133: warning: (near initialization for `hw_entry')

vxpocket.c:134: unknown field `ops' specified in initializer

vxpocket.c:134: warning: excess elements in struct initializer

vxpocket.c:134: warning: (near initialization for `hw_entry')

vxpocket.c:139: parse error before '*' token

vxpocket.c:140: warning: return type defaults to `int'

vxpocket.c:144: parse error before '*' token

vxpocket.c:145: warning: function declaration isn't a prototype

vxpocket.c: In function `vxp_detach':

vxpocket.c:146: `link' undeclared (first use in this function)

vxpocket.c:146: (Each undeclared identifier is reported only once

vxpocket.c:146: for each function it appears in.)

vxpocket.c: In function `init_vxpocket':

vxpocket.c:156: `servinfo_t' undeclared (first use in this function)

vxpocket.c:156: parse error before "serv"

vxpocket.c:158: warning: implicit declaration of function `CardServices'

vxpocket.c:158: `GetCardServicesInfo' undeclared (first use in this function)

vxpocket.c:158: `serv' undeclared (first use in this function)

vxpocket.c:159: `CS_RELEASE_CODE' undeclared (first use in this function)

vxpocket.c:163: warning: implicit declaration of function `register_pccard_driver'

vxpocket.c: In function `exit_vxpocket':

vxpocket.c:169: warning: implicit declaration of function `unregister_pccard_driver'

vxpocket.c: At top level:

vxpocket.c:121: storage size of `hw_entry' isn't known

make[2]: *** [vxpocket.o] Error 1

make[2]: Leaving directory `/root/downloads/alsa/2/alsa-driver-0.9.2/pcmcia/vx'

make[1]: *** [_modsubdir_vx] Error 2

make[1]: Leaving directory `/root/downloads/alsa/2/alsa-driver-0.9.2/pcmcia'

make: *** [compile] Error 1

0

Share this post


Link to post
Share on other sites

Check your paths, your compiler version (new compilers add stricker restraints to code styles that some people just hate following) and such.... and check the Alsa docs ;)

0

Share this post


Link to post
Share on other sites

im usin gcc 3.2.2 and it works for everythin else.......

apparently not even commercial oss can install on my system, it tells me that the snddshield module can't be compiled for my kernel.........this sucks!!!!!

are there no alternatives to alsa and oss?? or should I try upgrading my kernel to 2.5 series, i heard it has alsa built in.

I just tried installing alsa 0.9.1 (0.9.2 is the latest) and I used the --with-card=via82xx option, and it worked ok (0.9.2 did not know what via82xx was!!). Then I edited my modules.conf file, and still at startup it couldn't load the module, and I looked everywhere and there is no via82xx.o file installed on this computer!!! does anyone knoe why this might happen??

0

Share this post


Link to post
Share on other sites

GCC version 3.2.X adds ALLOT of restrainst to code styles that allot of peopel just dont like or cant cope with.. so some code that compiles in a earlyer version of GCC may not compile in the newer version, my suggestion is to install a older version alongside your current version for just these cases.

As for your missing file, i would make sure it was included and compiled.. you cant compile something that is not there or goes by a different name.

Im sure it did know what you card was, perhaps they changed it into a more standard driver for that base.. iSome of the newer driver sets are being intergreted into one large file thats just been hacked down to one tiny thing for several chipsets that are the same, I would check and make sure.

0

Share this post


Link to post
Share on other sites

ok, I got it to work, well apparently the set of instructions that I had said to do a make install right after the ./configure and it doesn't work (go figure!) I just did a ./configure make make install, and surprise surprise it works, and it works well. Too bad ppl screw up when makin instructions.....

0

Share this post


Link to post
Share on other sites

I would send a complaint to the people/person who wrote the docs you where going by.. Im sure your not the only one affected.

0

Share this post


Link to post
Share on other sites

well, I was goin by info on a forum board, so I cant really say anything, I just checked the official alsa docs, and indeed it says make&&make install, so I can't really say anything. BTW if you want to check out the forum I was goin thru with this it was:

www.linux.ro

it's in romanian so, it prolly won't be of much help for a lot of ppl......

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0