stardotstar
l33t
Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU
|
 Posted: Tue Sep 09, 2008 2:58 am Post subject: (solved) udev help and solution for a wifi and finger secur |
 |
|
Hi all,
I have got my Thinkpad working first of all with the iwl4965 module and wpa_supplicant so that I can up and down my wifi associations.
Then I got thinkfinger sorted out allowing me to log in and unlock the screen and su and so on using the finger print scanner.
So far so good.
But after adding the thinkfinger pam stuff I found that my wifi stopped working.
dmesg reporting that the link is never ready:
| Code: |
ADDRCONF(NETDEV_UP): wlan0: link is not ready
|
It is detected on startup:
| Code: | iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.17kds
iwl4965: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:03:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
|
and I have modprobed -r and reprobed it as well as tried the killswitch on the front but although the module is seen in lsmod I am not getting the link ready:
| Code: |
geko rules.d # lsmod
Module Size Used by
snd_seq_dummy 6532 0
snd_seq_oss 29952 0
snd_seq_midi_event 9600 1 snd_seq_oss
snd_seq 44880 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 9868 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37280 0
snd_mixer_oss 16640 1 snd_pcm_oss
vboxdrv 59032 0
snd_hda_intel 272928 2
snd_pcm 64644 2 snd_pcm_oss,snd_hda_intel
snd_timer 20484 2 snd_seq,snd_pcm
snd 42980 12 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
soundcore 9824 1 snd
snd_page_alloc 11144 2 snd_hda_intel,snd_pcm
iwl4965 180584 0
nvidia 7093380 38
geko rules.d # modprobe -r iwl4965
geko rules.d # ifconfig wlan0
wlan0: error fetching interface information: Device not found
geko rules.d # modprobe iwl4965
geko rules.d # ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:1D:E0:90:CE:59
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
geko rules.d # /etc/init.d/net.wlan0 start
* WARNING: net.wlan0 has already been started.
geko rules.d # /etc/init.d/net.wlan0 restart
* Stopping wlan0
* Bringing down wlan0
* Shutting down wlan0 ... [ ok ]
* Stopping wpa_cli on wlan0 ... [ ok ]
* Stopping wpa_supplicant on wlan0 ... [ ok ]
* Starting wlan0
* Starting wpa_supplicant on wlan0 ...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported [ ok ]th param 5 value 0x1 -
* Starting wpa_cli on wlan0 ... [ ok ]
* Backgrounding ...
geko rules.d # ifconfig iwlan0
iwlan0: error fetching interface information: Device not found
geko rules.d # ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:1D:E0:90:CE:59
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
|
| Code: |
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.17kds
iwl4965: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:03:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy1: Selected rate control algorithm 'iwl-4965-rs'
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
|
So from what I see the device is there and configured exactly the same way as earlier this morning (prior to thinkfingering) and yet never becoming ready.
All I did otherwise was according to the wiki so this sort of thing:
| Code: |
stardotstar@geko /opt/VirtualBox-2.0.0 $ su
Password or swipe finger:
geko VirtualBox-2.0.0 # cd /etc/udev/rules.d/
geko rules.d # ls
30-kernel-compat.rules 60-persistent-input.rules 61-persistent-storage-edd.rules 75-persistent-net-generator.rules
40-alsa.rules 60-persistent-storage-tape.rules 64-device-mapper.rules 80-drivers.rules
40-gentoo.rules 60-persistent-storage.rules 65-permissions.rules 90-hal.rules
40-video.rules 60-vboxdrv.rules 70-persistent-cd.rules 90-network.rules
50-udev-default.rules 60-virtualbox.rules 70-persistent-net.rules 95-udev-late.rules
60-cdrom_id.rules 60-vmware.rules 75-cd-aliases-generator.rules _-thinkfinger.rules
geko rules.d # mv _-thinkfinger.rules 60-thinkfinger.rules
geko rules.d # cat 60-thinkfinger.rules
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#
# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"
# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"
|
ie added a 60- rule for thinkfinger and set up permissions as group thinkfinger and amended the pam system-auth as follows:
| Code: |
geko pam.d # cat system-auth
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass likeauth nullok
account required pam_unix.so
password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 try_first_pass retry=3
password required pam_unix.so try_first_pass use_authtok nullok md5 shadow
session required pam_limits.so
session required pam_env.so
session required pam_unix.so
|
If anyone can follow my logic and see my error I would appreciate the input. Google does come back with some links on the link not ready but so far to no avail.
Much gratitude to any who deigns to help me 
Will
Turned out to be invisibility mode on the access point . I am sure I managed to associate with it since turning it to invisible but when I finally tried to solve the prob by making ti broadcast again it associated straight away.
So nothing to do with the thinkpad usb device (of course) but another factor altogether.
please delete me.
_________________
]8P |
|
Kernel & Hardware
