You are not logged in.
Hi all
Within this last update that merged /bin and friends to /usr/bin, the oss package was also updated and it broke the osscore module.
Now, when typing soundon I get
modprobe: ERROR: could not insert 'osscore' : Invalid argument
Loading the osscore module failed
Looking at dmesg, I can see
osscore: no symbol version for memmove
osscore: Unknown symbol memmove (err -22)
I tried building the package myself, it didn't complain and finished successfully only to realise that it had the same problem. I then thought that my system/install was somehow screwed up so I fired up virtualbox, installed the image that I had (archlinux-2013.04.01), updated it completely and tried installing oss there. Again it failed with the same error.
Thank god for pacman cache as I tried downgrading to oss-4.2_2007-2 and it worked. I was relieved to hear my system play music again and that I did not have to go back to alsa.
Did anyone else experience this problem and did you solve it and how? Should I open a bug report on arch bug tracker?
I'm on x86_64 btw...I don't think other specs are that important as it happened on both native and virtual machine (native-custom compiled kernel and vbox stock).I did not check if the problem persisted when on i686 as I had only installed x64 arch in vbox to test, but I'll install it later tonight in vbox just to check it.
Last edited by klothius (2013-06-05 20:29:50)
Offline
I wager 5 tacos that `uname -a` and `pacman -Qi linux` give different version numbers.
If so, a reboot will fix it, and the tacos can be compressed and sent via email.
Last edited by Trilby (2013-06-05 22:45:49)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Did anyone else experience this problem and did you solve it and how?
Same problem here, same workaround (downgrade).
Should I open a bug report on arch bug tracker?
After you, Alphonse.
Sorry Trilby, no tacos for you. 3.9.4-1 consistently. Thanks for playing, though.
Offline
Oh well, sorry.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Did anyone else experience this problem and did you solve it and how?
I get the same problem and is going to downgrade the oss package in order to get back my music. Do you guys think that oss-4.2_2007-3 is a better choice for downgrading?
Vox populi, vox Dei
Offline
Well the task has been set up on arch bug tracker, you can vote up/comment to confirm it https://bugs.archlinux.org/task/35672
I get the same problem and is going to downgrade the oss package in order to get back my music. Do you guys think that oss-4.2_2007-3 is a better choice for downgrading?
No, the *-3 package was just a pkg release number change according to the changelog.
Last edited by klothius (2013-06-06 08:55:29)
Offline
O...... Thanks Klothius.
Vox populi, vox Dei
Offline
Well, I have the same problem, but I was stupid enough to do "pacman -Scc" after the latest update (since my root partition is rather small ...) so now I don't have the oss-4.2_2007-2 package any more. Any idea where I can still get it so I can downgrade? Otherwise I'm stuck with "beep", "beep".
Last edited by unhappy (2013-06-08 07:46:33)
Offline
You can roll back to a previous package via ARM (Arch Rollback Machine).
http://arm.konnichi.com/2013/03/15/community/os/ go here, then choose your OS (i686 or x64), and search for oss-4
Btw the task on the bug tracker still isn't confirmed and thus assigned
Offline
You can roll back to a previous package via ARM (Arch Rollback Machine).
http://arm.konnichi.com/2013/03/15/community/os/ go here, then choose your OS (i686 or x64), and search for oss-4
Btw the task on the bug tracker still isn't confirmed and thus assigned
thx for link. I use Linux Fumofuu 3.9.4-1-ARCH kernel, oss (4.2_2007-2) starting sloooowly, but he working.
Offline