My Pi has finally seen some action over the Christmas break. The remarkable projects going on here are clearly out of my league. I can't even get WiFi working.
My Hardware
RasPi Model B, Rev 1
SD Card: Samsung 8 GB Class 10
Dongle is D-Link DWL-G122 (B1)
On the latter,
Code: Select all
lsusbCode: Select all
Bus 001 Device 005: ID 2001:3c00 D-Link Corp. AirPlus G DWL-G122 Wireless Adapter(rev.B1) [Ralink RT2571]Since it's the latest install is based on wheezy, I added the wheezy non-free source rather than the squeeze source. Some key errors on apt-get update were fixed using the guidance here: http://www.raspberrypi.org/phpBB3/viewt ... 28&t=19075
After installing the ralink firmware (which at least references the relevant chipset), I plug in the dongle and I get some activity on the dongle's little LEDs, but that's where the fun ends. It doesn't return any hosts on the issue of "nmcli dev wifi list". And if I run "sudo ifup wlan0" I get no DHCP offers.
If it's of any interest, the wlan0 entry does appear in ifconfig, but after that is run, the "sudo ifup wlan0" command now gives extra errors:
Code: Select all
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
...
Some bumph here about Internet Systems Consortium
...
RTNETLINK answers: Input/output error
Listening on LPF/wlan0/MY:MA:CA:DD:RE:SS
Sending on LPF/wlan0/MY:MA:CA:DD:RE:SS
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
receive_packed failed on wlan0: Network is down
...
More like the above, different intervals, and no "receive_packet" lines until ..
...
No DHCPOFFERS received.
Unable to obtain a lease on first try. Exiting.
Failed to bring up wlan0.Some of the pages my frantic searching have turned up seem to be suggesting issues like this could be power supply related. In case of differing power consumption, I've tried the set up using both wired and wireless keyboards, and no keyboard but ssh (I might try the latter again), but it's made no difference so far. I don't own a powered USB hub, perhaps it's time I did, but I'd be reluctant to go the powered hub route for the "final" set up.
I'll replace the power supply if my current one turns out to be substandard. I do own a multimeter ... is there anything I can do to check if power is the problem? Or if anyone has other suggestions, they'd be gratefully recevied. It's been driving me mad.