Pages

Showing posts with label alsa. Show all posts
Showing posts with label alsa. Show all posts

2014-08-07

Crux 3.1, install and so on

# Install is mostly the same as 3.0
- There were slight differences in installable apps - some of them important, see release notes. Also, see Handbook - surprisingly enough, it is corrected for new release (simply, such kind of care is not so common).
So, let's note here some diffrences from 3.0 install:
- fstab (but you still have to fill it out, mostly)
- kernel pre-made conf is more complite/generally-usable.
- network has been split to lo and net scripts, AND those files are already functional.

# Later stuff
. See this and this of Crux 3.0 - a lot went the same way.
What differs:
- prt-get sysup. One update was xorg-server. Dependency 'libepoxy' was not noted and compile failed (but I think it's already fixed). Also, after update xorg-server needs drivers reinstalled (I picked libevdev, evdev, vesa, libva and got X started ok).
- Kernel, as a cautionary tale: Despite I was very eagle-eyed when in kernels' make menuconfig, I still missed my sound driver somehow... doh.
So I thought that I create it as a module. Downloaded alsa-driver (and alsa firmware) packages for make&kmod ... and spent an hour with googling/fixing 'configure' (version.h in wrong folder). And then - it still erred (some ioctl stuff) when 'making'. Fuck. So I went and recompiled the kernel. Took me less than 5 minutes... One reboot, alsactl init and sound appeared. What a waste of time - but superbly educational. Maybe.
- dbus is not installed out of box. Now, I didn't have that problem in 3.0 - which might simply mean that I got it at early stages as dependency... Whatever - it needs to be installed now.
- xdotool. Used Pkgfile this time... and got libxdo also installed.
- man: This time, it worked for root OK, BUT, still not for user (error was different of 3.0). prt-get depinst most - and man started up, colors and all ... for a user, BUT not for root. Strange. | Missing export PAGER="most" in root .bashrc, nothing else :) |
- jdk - version in Pkgfile is wrong, fix it.
- gegl (for gimp), footprint mismatch = delete footprint. And Gimp installed without whining despite threatening text in readme. Check URL in Gimps' Pkgfile - at some point of time it is/was incorrect.
- qpdfview, qbittorrent. Neither could make package (bsdtar: *: Cannot stat: No such file or directory). I couldn't find any reasonable lead for fixing that... As I didn't have such a message with any other (NOT-QT) apps, I tend to guess that it had something to do with QT. But finally, I went for simple 'make' and they installed with no fuss.
- fbreader. Missing libpng15.so.15 , ln -s from ver 16 helped.
About libpng - this new one craps pointless wrong-srgb warning messages to everywhere. Very bloody annoying.
- smplayer not recognising mplayer version-and-stuff. It started but didn't play a thing, no video, no audio. I reinstalled mplayer, installed docutils... did something ... and smplayer started to function. Oh good - but, I really don't know what that was about.

That's it for now. I'm sure there will be more. I haven't finished with apps, and I also have some unresolved errors... like 'cannot ioremap fb base' (nvidiafb) at startup...

All-in-all, I am a bit dissappointed - not sure if more in myself or in nature of Crux. Means, I hoped it goes easier second time around. It didn't.
Summary: My level of Linux plus Crux means that it will remain as my second distro after Slackware. I simply don't have multitude of hours to spade-work in google-piles. The perspective of continuous fixing of results of updates makes me ...depressed.
But - as I really like Cruxs' ideas and choices - it's a keeper without question.

2014-02-25

Alsa problem on new Wheezy

I just did Wheezy netinstall to really old box. Athlon64, sound through nforce chipset. Wheezy called the working sound (mostly) 'Nvidia CK804'.
Alsa was installed as per usual:
alsa-base, alsa-utils, alsa-tools, libsound, alsamixer, (and dependencies) and lastly volumeicon (started from Openbox autostart file).

alsactl init did the trick and everything seemed dandy.
Unfortunately, the sound worked alright only to first reboot. Then it didn't anymore, and volumeicon also disappeared (and refused to start from terminal with quite a lengthy fail-message).

I tried various stuff to diagnose and fix:
The simple alsactl init again, and heavier alsa force-reload.
Pried from terminal with:
lspci | grep audio
aplay -l
aplay -L 

and even with hwinfo (install from repo)...
Visited alsas' home for information and for possible source download.
Peeked into files:
cat /proc/asound/cards
cat /proc/asound/modules
cat ~.config/volumeicon/volumeicon
cat /etc/modprobe.d/alsa-base.conf


Conclusion:
1. Nvidia or no, the drivers are:
snd-hda-intel => card0 (default), and not working for me,
snd-intel8x0 => card1, and working when manually chosen.
2. Solution is that the second one should be the first, default choice. And then there wouldn't be also need to change the last block in volumeicon file:
[Alsa]
card=default


sudo nano /etc/modprobe.d/alsa-base.conf
After lines of 'install' and before 'options' I added two lines:
options snd-intel8x0 index=0
options snd-hda-intel index=1


sudo alsa force-reload
And there was sound! And it still is - also after reboot.
That's it.