Hi Wawrzek Very annoying! It may be related to similar random behaviour in whether eth0 is the wireless or ethernet connection. (and random behaviour of console fullscreen or not at bootup.) Sometimes it seems to be affected by use of Windows between bootups, but not really consistently. Hope someone has an answer. clare Not Windows at my machine, so this another problem. I partly resolve my problem. In Amarok you point directly to device not to 'number'[1]. I also write udev rules creating symlinks to my devices, so I always I have /dev/mixer-intel and /dev/mixer-ens1370. But some programs [skype] point to alsa device 0, alsa device 1. Wawrzek [1] http://amarok.kde.org/wiki/FAQ#How_can_I_change_where_the_audio_is_output_to... -- Wawrzyniec Niewodniczański WWW: http://larryn.blogspot.com/ vel LarryN E-MAIL: wawrzyniec.niewodniczanski[na]pwr.wroc.pl PhD student @ JID: larryn@chrome.pl Wroclaw University of Technology TEL: +48(071)320-2894
Not Windows at my machine, so this another problem.
I partly resolve my problem. In Amarok you point directly to device not to 'number'[1]. I also write udev rules creating symlinks to my devices, so I always I have /dev/mixer-intel and /dev/mixer-ens1370. But some programs [skype] point to alsa device 0, alsa device 1.
Wawrzek
[1] http://amarok.kde.org/wiki/FAQ#How_can_I_change_where_the_audio_is_output_to...
the problem is the fact that udev tries to load all modules at the same time. I came across this "fix" earlier: KERNEL=="eth*", DRIVER=="3c59x", NAME="eth0" KERNEL=="eth*", DRIVER=="e1000", NAME="eth1" i've not yet tried the above fix yet, but in case it fails this should atleast do the trick: Comment out the ACTION=="add", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe $env{MODALIAS}" line in /etc/udev/rules.d/26-modprobe.rules. -- Fredrik Rinnestam
participants (2)
-
Fredrik Rinnestam
-
Wawrzyniec Niewodniczański