-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi!
Today I installed grml 0.9 (two times) to HD with grm2hd. If I boot with the CD the autoconf detects eth0 (e1000) and eth1 (ipw3945) from my T60 laptop. After install on HD and reboot the system just recognize eth0. After rmmod ipw3945 /modprobe ipw3945 (and for some test another /etc/init.d/ipw3945d restart) I get a eth1 but with a dhclient eth1 I can?t get a IP.
While booting from the live CD I just need to wait a few sec and retry dhclient eth1 and the LED for the WLAN activity is enlighten and blinks. With boot from HD it is most time dark, just a part of second enlightent.
Oh, I use grml-network with WPA supplicant options.
Anyone has a idea? Is ipw3945 buggy?
Yes, it is a clean install, an now the (hopeful) exact steps: boot from CD: boot with standard option grml-network (enter correct SSID, standard options, WPA, enter correct Key), wait, break fist dhclient wait some sec dhclient eth1 *ipw3945 is active, WLAN LED is active and I got net access*
HD install: - -grml2hd - -chroot, install grub - -reboot - -apt-get update, apt-get upgrade (NO grml, kenrel oder ipw3945 update!) - -grml-network (same as with CD boot) - -reboot - - after boot no eth1 present - - rmmod ipw3945 - - modprobe ipw3945 - - ifconfig - no eth1 - - ifconfig eth1 - eth1 shows up with correct MAC ID, no IP - - dhclient eth1 - WLAN HD is dark, some flickering and NO IP..
MfG, Lars Schimmer - -- - ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
* Lars Schimmer l.schimmer@cgv.tugraz.at [20061211 00:15]:
Today I installed grml 0.9 (two times) to HD with grm2hd. If I boot with the CD the autoconf detects eth0 (e1000) and eth1 (ipw3945) from my T60 laptop. After install on HD and reboot the system just recognize eth0.
[...]
Ok, today I found the time to take a closer look at the problem at Lars' hardware (thanks for the coffee, Lars :-)).
JFTR: ipw3945 definitely has some race condition problems. To fix this problem on your Debian/grml system just take a look at my howto:
################################################################################ We want to avoid autoloading of the ipw3945 module at boottime, so we blacklist the module:
# cat /etc/modprobe.d/grml blacklist ipw3945
Now create a new initscript which loads the driver:
# cat /etc/init.d/ipwfix #!/bin/sh grep -q ipw3945 /proc/modules && rmmod ipw3945 modprobe ipw3945
Then make sure the initscript is used before /etc/init.d/networking is running:
# update-rc.d ipwfix start 34 S .
Notice a problem with /etc/resolv.conf? I couldn't debug it in detail due to lack of time but the problem definitely goes away if you do not use the package resolvconf, so just run:
# apt-get --purge remove resolvconf
We want to have persistent interface names so we bind ipw3945 to interface name wlan0 via udev (see 'grml-tips udev' for details):
# INTERFACE=wlan0 /lib/udev/write_net_rules 00:13:02:aa:bb:cc
Finally configure your WLAN device as usual via /etc/network/interface (and make sure you have CONFIG_DHCP=no in /etc/grml/autoconfig on your grml-system), for example it might look like the following for a WPA setup:
# cat /etc/network/interfaces auto lo wlan0 iface lo inet loopback
iface wlan0 inet dhcp wireless-mode Managed wireless-essid secret pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B down killall wpa_supplicant ################################################################################
regards, -mika-
* Michael Prokop wrote [14.12.06 15:19]: Hi,
Notice a problem with /etc/resolv.conf? I couldn't debug it in detail due to lack of time but the problem definitely goes away if you do not use the package resolvconf, so just run:
# apt-get --purge remove resolvconf
Hm, no, please :)
Just issue the command ,---- | resolvconf -d $INTERFACE `----
The problem is when you use dhclient or something like that which modifies resolv.conf with resolvconf it generates an entry in /etc/resolvconf/run/interfaces/$INTERFACE but ifup/ifdown generates an entry named $INTERFACE.inet $INTERFACE.dhcp so $INTERFACE will never be overwritten.
A solution is to have an entry in /etc/network/interfaces
,----[ /etc/network/interfaces ] | iface dhcp inet dhcp `----
and use ifup $INTERFACE=dhcp
regards, -mika-
Uli
* Ulrich Dangel schula@grml.org [20061214 17:15]:
- Michael Prokop wrote [14.12.06 15:19]:
Notice a problem with /etc/resolv.conf? I couldn't debug it in detail due to lack of time but the problem definitely goes away if you do not use the package resolvconf, so just run:
# apt-get --purge remove resolvconf
Hm, no, please :)
Just issue the command ,---- | resolvconf -d $INTERFACE `----
The problem is when you use dhclient or something like that which modifies resolv.conf with resolvconf it generates an entry in /etc/resolvconf/run/interfaces/$INTERFACE but ifup/ifdown generates an entry named $INTERFACE.inet $INTERFACE.dhcp so $INTERFACE will never be overwritten.
[...]
Ah! I wasn't aware of this fact, thanks for the pointer. :)
regards, -mika-
Teilnehmer (3)
-
Lars Schimmer -
Michael Prokop -
Ulrich Dangel