Jump to content
Posted 12 May 2013 - 17:50
Posted 12 May 2013 - 17:58
Posted 12 May 2013 - 18:26
Oh and would you look at that, downgraded back to 3.8 and all my sound options comes back.
I'm not even blaming the arch team for this, now it seems the kernel team are incompetant.
Getting so tired or actual idiots 'fixing' or 'improving' things when they haven't got a clue and they just break everything, gonna format this and install debian stable later I think.
For anyone else on arch that needs a fix, go to the arch linux release mirror thing and find linux-3.8.11, pacman -U <package name>, reboot and all will be fine again.
Posted 12 May 2013 - 19:02
Sadly this is true. All Archlinux seems to be anymore is a fanboy's toy.
Debian Stable is a blast. I would highly recommend it.
Posted 12 May 2013 - 19:53
Posted 12 May 2013 - 20:42
Posted 12 May 2013 - 21:40
If you've got arch, and have upgraded it without ever having problems then you are doing something wrong unless you do a brand new install every so often.
Posted 12 May 2013 - 21:46
*sigh* don't blame the distro or the kernel maintainers. Blame yourself, what chipset is the audio card you have, have you read the changelog for kernel 3.9 have you read Arch documentation before upgrading to 3.9? Did you try loading the needed kernel modules after the upgrade?
The kernel maintainers are strict with their releases, its not their fault. As for Arch im an Arch user and have had no problems with any upgrades because i don't upgrade blind, with rolling release distros you need to read things first before you upgrade to ensure that things wont break and if they do you will then know how to reconfigure them correctly.
did you try recompiling a custom 3.9 kernel to ensure you have the correct modules loaded?
Posted 12 May 2013 - 22:38
Yeah that's right they fully documented that when they first switched to systemd, it wasn't actually complete and lots of things didn't work... OH NO WAIT, they didn't!
I would say they are actually reading the change notes and not indiscriminately applying all updates, also known as doing it right.
Posted 12 May 2013 - 22:52
So I had a pretty much fine arch linux 64 bit install with KDE, I had pulseaudio and using alsamixer I could see the full range of my card's audio devices, master, front, left, side, mic, line, etc. and all was great...
I've been looking just now though and alsamixer's sound has been reduced to what I will consider utter garbage that makes it pretty much unusable. Master, headphone (there is no headphone slot), speaker (there is no internal speaker), PCM, Mic Boost, Beep, Auto+Mute Mode, Independant HP...
Now, I've no idea what auto+mute is nor what independant HP is, but what's really ****ed me off is I can no longer get mic or line or play either out through my speakers. I frantically removed pulseaudio and reinstalled it a few times thinking I'd somehow messed that up but it wasn't that, looking through the pacman upgrade log the only thing I see that has anything to do with sound is upgrading from kernel 3.8 to 3.9 earlier...
So does this mean it's the doing of the 3.9 kernel or what? Has the kernel been bastardised now so that it's just a pile of garbage? And most importantly, how the hell do I go about getting back a usable sound system instead of this unworkable system?
Posted 12 May 2013 - 22:58
Posted 13 May 2013 - 15:19
He should blame himself for something that should work but doesn't? Yeah, somehow that doesn't make sense. I only run Linux in a VM and this is an example why that makes more sense. I feel for some of you troopers that have to go all through this pain to get stuff to work.
Should I waste my life away and my time away on just getting basic things to work or should I just get work done that needs to get done? hmmmm.
Posted 13 May 2013 - 20:02
I think you're getting a bit confused between using the normal arch linux repos and the TESTING arch linux repos.
He's using a bleeding edge rolling-release power-user focused distro, if you use a bleeding edge distro you will run into regressions from time to time after updates, its simply the nature of running cutting-edge software. And if you run cutting edge software you should be prepared to report bugs instead of freaking out every time you encounter one. Most distros do not do major kernel updates in between releases (only smaller security and bugfix updates), so this type of thing is much more rare.
From the threads I've seen from him lately, he should blame himself for choosing a distro that clearly does not fit his needs.
Posted 13 May 2013 - 20:10
Posted 13 May 2013 - 20:25
Never use testing apps or OS (beta or public preview release) on your primary system... you will need a backup system for testing to make sure they work... if so, you can upgrade or fresh install on your primary.