| View previous topic :: View next topic |
| Author |
Message |
NuMPTy
Tux's lil' helper
Joined: 04 Mar 2012
Posts: 78
|
 Posted: Sat Jul 21, 2012 2:42 am Post subject: oss-devel not working |
 |
|
Hi everyone,
I've given up on the in-kernel drivers for my X-Fi card, and have moved onto OSS, which does have drivers I can actually load. Unfortunately, OSS itself seems to be broken within oss-devel from layman (the links for oss itself are broken in the overlay)
Currently:
| Code: | # lsmod
Module Size Used by
oss_sbxfi 29679 0
osscore 542995 1 oss_sbxfi
|
| Code: | | Kernel driver in use: oss_sbxfi |
However, when I try to run actual oss commands:
| Code: | # osstest
/dev/mixer: No such file or directory
# soundoff
/dev/mixer: No such file or directory
/dev/mixer: No such file or directory
#soundon
#ossdetect -d -v
mknod /dev/sndstat c 249 0 -m 20666
mknod /dev/midi c 249 1 -m 20666
mknod /dev/mixer c 249 2 -m 20666
mknod /dev/oss/oss_sbxfi0/mix0 c 248 3 -m 20666
mknod /dev/oss/oss_sbxfi0/pcm0 c 248 4 -m 20666
mknod /dev/oss/oss_sbxfi0/pcmin0 c 248 6 -m 20666 |
What should I be doing? |
|
| Back to top |
|
 |
NuMPTy
Tux's lil' helper
Joined: 04 Mar 2012
Posts: 78
|
| Posted: Sat Jul 21, 2012 2:43 am Post subject: |
|
|
Also:
| Code: | # cat /usr/src/linux/.config | grep -i 'oss\|alsa'
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_CROSS_COMPILE=""
# CONFIG_CHR_DEV_OSST is not set
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_BCMA_POSSIBLE=y
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
|
Thanks in advance! |
|
| Back to top |
|
|
tclover
Guru
Joined: 10 Apr 2011
Posts: 516
|
| Posted: Sat Jul 21, 2012 2:51 am Post subject: |
|
|
that ebuild is not really maintained so i'd advise to make yours or get other from an overlay, check my sig for that. the live version does not get updates that often moreover cloning from their mercurial repo is not always possible, so just grab something with 4.200x something to get going.
_________________
home/:mkinitramfs-ll/:supervision/:e-gtk-theme/:overlay/ |
|
| Back to top |
|
|
NuMPTy
Tux's lil' helper
Joined: 04 Mar 2012
Posts: 78
|
| Posted: Sat Jul 21, 2012 3:46 am Post subject: |
|
|
| tclover wrote: | | that ebuild is not really maintained so i'd advise to make yours or get other from an overlay, check my sig for that. the live version does not get updates that often moreover cloning from their mercurial repo is not always possible, so just grab something with 4.200x something to get going. |
Thanks for the reply. I had a generic build of 4.2 (can't remember the version) on here before I found the devel ebuild, but I suppose I can try it again.
What would be the "steps" involved in doing this without generating any conflicts
emerge --unmerge oss-devel (obviously)
reboot
install new?
reboot?
or is it more complicated than that?
Cheers, |
|
| Back to top |
|
|
tclover
Guru
Joined: 10 Apr 2011
Posts: 516
|
| Posted: Wed Jul 25, 2012 11:25 pm Post subject: |
|
|
No need to reboot whatsoever, just stop alsasound init service and remove ALSA kernel modules (good luck because this can be very annoying). And then start oss init service. You may need a soundon.user to meet specific needs.
Anyway, I've commited three commits which fix oss-4.2.2006 ebuild and added USE flags so now one can only compile and merge specified drv by USE flags.
_________________
home/:mkinitramfs-ll/:supervision/:e-gtk-theme/:overlay/ |
|
| Back to top |
|
|
|
Multimedia
