[arch-general] Problems with ifplugd and net-auto-wired
Hi, I've two problems with ifplugd and net-auto-wired. When ifplugd is started during boot my speakers make a weird and very loud "moep" sound. When started from a console after boot no such sound occurs. The second problem I have is if net-auto-wired starts during boot time it will not detect any networks. I have to restart net-auto-wired by hand after boot to get a connection. /etc/rc.conf(just the important lines) MODULES=(acpi_cpufreq cpufreq_ondemand coretemp lib80211_crypt_tkip !ssb !b43 fglrx wl usblp !pcspkr !snd_pcsp vboxdrv vboxnetflt fuse) INTERFACES=() WIRED_INTERFACE="eth0" WIRELESS_INTERFACE="wlan0" DAEMONS=(syslog-ng hal ifplugd @net-auto-wired @net-auto-wireless @alsa @mpd @crond @ntpd @alsa @lastfmsubmitd @lastmp @cpufreq @sensors @tor @privoxy) /etc/network.d/dhcp CONNECTION="ethernet" DESCRIPTION="dhcp" INTERFACE="eth0" IP="dhcp" As far as I can tell my configuration is correct but I'm open to any suggestion Sebastian -- The best thing about a boolean is even if you are wrong, you are only off by a bit.
On Sun, 21 Feb 2010 05:57:36 +0100, Sebastian Köhler <sebkoehler@whoami.org.uk> wrote:
I've two problems with ifplugd and net-auto-wired. When ifplugd is started during boot my speakers make a weird and very loud "moep" sound. When started from a console after boot no such sound occurs.
Intel and via sound chips have a tendency to make noise in some conditions like acpi wakeup, or sudden power drop in weak laptops. Try to blacklist your sound driver and load it after whatever causes the noise. Never read about anything but a "plop" noise, so not sure if that's related.
On Sun, Feb 21, 2010 at 06:04:24AM +0100, Arvid Picciani wrote:
Intel and via sound chips have a tendency to make noise in some conditions like acpi wakeup, or sudden power drop in weak laptops. Try to blacklist your sound driver and load it after whatever causes the noise. Never read about anything but a "plop" noise, so not sure if that's related.
Ok blacklisting snd-hda-intel definitely helped. But after loading the module with modprobe my sound went crazy and my laptop reapeated the "moep" sound over an over again. But now that I know where to look I can experiment a little until I find a solution. Sebastian -- The best thing about a boolean is even if you are wrong, you are only off by a bit.
On Sun, Feb 21, 2010 at 05:57:36AM +0100, Sebastian Köhler wrote:
Hi,
I've two problems with ifplugd and net-auto-wired. When ifplugd is started during boot my speakers make a weird and very loud "moep" sound. When started from a console after boot no such sound occurs.
The second problem I have is if net-auto-wired starts during boot time it will not detect any networks. I have to restart net-auto-wired by hand after boot to get a connection.
/etc/rc.conf(just the important lines) MODULES=(acpi_cpufreq cpufreq_ondemand coretemp lib80211_crypt_tkip !ssb !b43 fglrx wl usblp !pcspkr !snd_pcsp vboxdrv vboxnetflt fuse) INTERFACES=() WIRED_INTERFACE="eth0" WIRELESS_INTERFACE="wlan0" DAEMONS=(syslog-ng hal ifplugd @net-auto-wired @net-auto-wireless @alsa @mpd @crond @ntpd @alsa @lastfmsubmitd @lastmp @cpufreq @sensors @tor @privoxy)
/etc/network.d/dhcp CONNECTION="ethernet" DESCRIPTION="dhcp" INTERFACE="eth0" IP="dhcp"
Grml, I forgot to send the logs created during startup. Here they are(): Feb 21 05:14:14 laptop ifplugd(eth0)[3955]: ifplugd 0.28 initializing. Feb 21 05:14:15 laptop ifplugd(eth0)[3955]: Using interface eth0/00:22:19:E7:02:25 with driver <tg3> (version: 3.102) Feb 21 05:14:15 laptop ifplugd(eth0)[3955]: Using detection mode:SIOCETHTOOL Feb 21 05:14:15 laptop ifplugd(eth0)[3955]: Initialization complete, link beat not detected. Feb 21 05:14:15 laptop ifplugd(eth0)[3955]: Using detection mode: SIOCETHTOOL Feb 21 05:14:15 laptop ifplugd(eth0)[3955]: Initialization complete, link beat not detected. Feb 21 05:14:18 laptop ifplugd(eth0)[3955]: Link beat detected. Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: up: error fetching interface information: Device not found Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: eth0 Link encap:Ethernet HWaddr 00:22:19:E7:02:25 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: RX packets:4 errors:0 dropped:0 overruns:0 frame:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: collisions:0 txqueuelen:1000 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: RX bytes:523 (523.0 b) TX bytes:0 (0.0 b) Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: Interrupt:17 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: lo Link encap:Local Loopback Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: inet addr:127.0.0.1 Mask:255.0.0.0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: UP LOOPBACK RUNNING MTU:16436 Metric:1 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: RX packets:0 errors:0 dropped:0 overruns:0 frame:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: collisions:0 txqueuelen:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: wlan0 Link encap:Ethernet HWaddr 00:22:5F:82:20:53 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: UP BROADCAST MULTICAST MTU:1500 Metric:1 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: RX packets:0 errors:0 dropped:0 overruns:0 frame:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: collisions:0 txqueuelen:1000 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: Interrupt:17 Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: Usage: inet_route [-vF] del {-host|-net} Target[/prefix] [gw Gw] [metric M] [[dev] If] Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: inet_route [-vF] add {-host|-net} Target[/prefix] [gw Gw] [metric M] Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: [netmask N] [mss Mss] [window W] [irtt I] Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: [mod] [dyn] [reinstate] [[dev] If] Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: inet_route [-vF] add {-host|-net} Target[/prefix] [metric M] reject Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: client: inet_route [-FC] flush NOT supported Feb 21 05:14:19 laptop ifplugd(eth0)[3955]: Program execution failed, return value is 1. Although eth0 is clearly there ifplugd says "Device Not Found" :/ -- The best thing about a boolean is even if you are wrong, you are only off by a bit.
participants (2)
-
Arvid Picciani
-
Sebastian Köhler