Arch Linux

axper

Member

Registered: 2013-01-25

Posts: 115

[SOLVED] modprobe: ERROR: could not insert 'osscore': Invalid argument

I am trying to install oss by following the oss wiki, but #soundon throws this into terminal:

modprobe: ERROR: could not insert 'osscore': Invalid argument
Loading the osscore module failed

There's a yet unsolved bug report for oss 4.2_2007-4, which mentions the same error message. I have downgraded to oss 4.2_2007-2, but I am still getting the same error.

pacman -Qs alsa|grep local/

local/alsa-lib 1.0.27.1-1
local/alsa-plugins 1.0.27-1
local/alsa-utils 1.0.27.1-2
local/lib32-alsa-lib 1.0.27.1-1
local/lib32-alsa-plugins 1.0.27-1

pacman -Qs oss|grep local/|grep oss (I know, crazy cmd skillz:D)

local/oss 4.2_2007-2

cat /etc/modprobe.d/alsa_blacklist.conf

install soundcore /bin/false

cat /etc/group|grep audio

audio:x:92:<my user>

When running #soundon without deleting /usr/lib/oss/starting (that is, when oss has previously crashed) I get messages like

Previous start of OSS crashed the system
Please resolve the situation and remove file
"/usr/lib/oss/starting". Then start OSS by
running soundon again.

When running #soundon after deleting /usr/lib/oss/starting it waits for about 60 seconds, then throws this:

#soundon

modprobe: ERROR: could not insert 'osscore': Invalid argument
Loading the osscore module failed

Output of commands after deleting /usr/lib/oss/starting

#systemctl status oss

oss.service - Open Sound System v4
   Loaded: loaded (/usr/lib/systemd/system/oss.service; enabled)
   Active: failed (Result: exit-code) since Mon 2013-06-24 14:09:14 AMT; 8s ago
  Process: 20142 ExecStart=/usr/sbin/soundon (code=exited, status=60)

Jun 24 14:08:42 desktop systemd[1]: Starting Open Sound System v4...
Jun 24 14:09:14 desktop soundon[20142]: modprobe: ERROR: could not insert 'osscore': Invalid argument
Jun 24 14:09:14 desktop soundon[20142]: Loading the osscore module failed
Jun 24 14:09:14 desktop systemd[1]: oss.service: main process exited, code=exited, status=60/n/a
Jun 24 14:09:14 desktop systemd[1]: Failed to start Open Sound System v4.
Jun 24 14:09:14 desktop systemd[1]: Unit oss.service entered failed state.

#journalctl -xn

-- Logs begin at Sat 2013-04-13 20:29:15 AMT, end at Mon 2013-06-24 14:13:28 AMT. --
Jun 24 14:13:19 desktop soundon[26382]: modprobe: ERROR: could not insert 'osscore': Invalid argument
Jun 24 14:13:19 desktop soundon[26382]: Loading the osscore module failed
Jun 24 14:13:19 desktop kernel: osscore: no symbol version for memmove
Jun 24 14:13:19 desktop systemd[1]: oss.service: main process exited, code=exited, status=60/n/a
Jun 24 14:13:19 desktop systemd[1]: Failed to start Open Sound System v4.
-- Subject: Unit oss.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit oss.service has failed.
-- 
-- The result is failed.
Jun 24 14:13:19 desktop systemd[1]: Unit oss.service entered failed state.
Jun 24 14:13:19 desktop sudo[26379]: pam_unix(sudo:session): session closed for user root
Jun 24 14:13:19 desktop kernel: osscore: Unknown symbol memmove (err -22)
Jun 24 14:13:28 desktop sudo[32542]: void2 : TTY=pts/0 ; PWD=/home/void2 ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Jun 24 14:13:28 desktop sudo[32542]: pam_unix(sudo:session): session opened for user root by (uid=0)

#dmesg

...
[  607.753263] osscore: no symbol version for memmove
[  607.753270] osscore: Unknown symbol memmove (err -22)

#ossmix

/dev/mixer: No such file or directory

#osstest

/dev/mixer: No such file or directory

Tried reinstalling 4.2_2007-2.
Rebooted after operations when resanable.

Have seen pages:
https://wiki.archlinux.org/index.php/Open_Sound_System
https://bugs.archlinux.org/task/35672
https://bbs.archlinux.org/viewtopic.php?id=165268
https://bbs.archlinux.org/viewtopic.php?id=164656
https://bbs.archlinux.org/viewtopic.php?id=164713
https://bbs.archlinux.org/viewtopic.php?id=164827

Any help appreciated.

Last edited by axper (2013-06-28 12:48:43)

klothius

Member

From: Beograd, Serbia

Registered: 2013-06-05

Posts: 18

Re: [SOLVED] modprobe: ERROR: could not insert 'osscore': Invalid argument

I don't have a clue why it's failing for you even with oss-*-2 package, but you might want to try out the newest 2008 build available in AUR (it says nonfree as it contains some proprietary drivers for some cards) - https://aur.archlinux.org/packages/oss-nonfree   

As the 2008 build is official on 4front servers, I have already flagged the official package out of date, but it seems the maintainer isn't active so much as he has yet to answer to the bug related to the latest 2007 build (oss-*-4).

If you don't want any proprietary drivers in your system you can go ahead and build your own build 2008 from the official source.

axper

Member

Registered: 2013-01-25

Posts: 115

Re: [SOLVED] modprobe: ERROR: could not insert 'osscore': Invalid argument

Ok this is really strange. I installed oss-nonfree from AUR, it worked, but some apps gave errors. Then I tried installing 4.2_2007-2 again and now it works flawlessly! I have no idea what has changed. Thanks for reply anyway.

Seems like same thing as https://bbs.archlinux.org/viewtopic.php … 9#p1287629

sonoran

Member

From: sonoran desert

Registered: 2009-01-12

Posts: 192

Re: [SOLVED] modprobe: ERROR: could not insert 'osscore': Invalid argument

I don't have a clue why it's failing for you even with oss-*-2 package, but you might want to try out the newest 2008 build available in AUR (it says nonfree as it contains some proprietary drivers for some cards) - https://aur.archlinux.org/packages/oss-nonfree   

As the 2008 build is official on 4front servers, I have already flagged the official package out of date, but it seems the maintainer isn't active so much as he has yet to answer to the bug related to the latest 2007 build (oss-*-4).

If you don't want any proprietary drivers in your system you can go ahead and build your own build 2008 from the official source.

Thanks for the link to the new OSS version in the AUR - it works fine here, after a reboot.

In an older OSS bug report the maintainer mentioned that he would have to wait until he had access to the box he has OSS installed on, so the delay with FS#35672 is understandable.