On a new installation on a old raspberry (the very first version) There is no wlan device, even after inserting a usb wifi device. Ifconfig shows only eth0 en lo. How to create the device? Shouldn't it created automatically when the device is inserted? Many thanks in advances
Try rebooting. Is the WiFi device listed as being supported by that hardware and software?
-- Cheers, David Web: http://www.satsignal.eu
It should be, yes, if the right software is installed.
Possibly you need to upgrade to the lastest version that will run on that hardware. But I am out of my comfort zone on that.
-- "Women actually are capable of being far more than the feminists will let them."
I did, inserting the device before booting. I dont know for shure bute believe it's a D-link..
Fresh install and updated RASPIAN latest.
Right, I am out of my comfort zone then!
It is imporatant to know what chipset it uses so you should do an lsusb to see what actual dongle it is
should then be looked at to see what operating system versions support that chipset and what firmware, if needs be, needs to be installed.
In particular:
" D-Link ( DWA-131 (rev. B1) ) - Works now on Raspbian's kernel 3.6.11+ or with DLink firmware:
DWL-G132 - In archlinux it is recognized - lsusb: 2001:3a03 D-Link Corp. DWL-G132 (no firmware) [Atheros AR5523] - but no wlan0 device is created - perhaps it needs the firmware to be loaded"
It would seem that D-LINK dongles are not well supported at all. If you want a quick fix buy a dongle from a raspberryPi vendor that is known to 'just work' with whatever versions of OS you are running
-- All political activity makes complete sense once the proposition that all government is basically a self-legalising protection racket, is fully understood.
I think 'the very first v.' has wireless. Raspbian has inxi by default which script shows lots of hardware info.
However, on RPi, the inxi reports are incomplete, including the wifi part of the report.
Normally, on a 'conventional' machine w/ both ethernet and wifi connectivity, inxi -N would show the ethernet and the wifi and their drivers, but not on my RPi. Here's inxi -N w/ only the wifi connected, no ethernet.
$ inxi -N Network: Card: Standard Microsystems SMSC9512/9514 Fast Ethernet Adapter
I can show more w/ inxi, which shows up the wlan0; and I will munge my WAN IP.
$ inxi -Nni Network: Card: Standard Microsystems SMSC9512/9514 Fast Ethernet Adapter IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A WAN IP: (munged) IF: eth0 ip-v4: N/A IF: wlan0 ip-v4: 192.168.1.135
My ifconfig shows the wifi as wlan0, but I'm reading some msgs from
2014 in which the wifi was ra0 instead.My lsusb also shows that SMSC9512/9514 device, which is the only thing inxi sees in its network survey.
Posted from my RPi model B accessing via wifi.
-- Mike Easter
No. The Pi 1 & 2 did NOT have wifi.
That was posted from a 3B.
-- Mike Easter
This is a conventional laptop w/ ethernet & wifi; inxi gives a good report on the hardware & drivers:
$ inxi -N Network: Device-1: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: bcma-pci-bridge Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
What does lsusb say?
-- Mike Easter
The inxi developer is developing pinxi for ARM.
It looks like the network hardware is the same for both ethernet & wifi (but there are 2 MACs) and there is only one driver:
$ pinxi -n Network: Device-1: Standard Microsystems SMSC9512/9514 Fast Ethernet Adapter type: USB driver: smsc95xx IF: eth0 state: down mac: b8:27:eb:ca:56:1a IF-ID-1: wlan0 state: up mac: b8:27:eb:9f:03:4f
-- Mike Easter
What's written to /var/log/messages when the USB wifi dongle is plugged in?
Hint: having "sudo tail -f /var/log/messages" running on another terminal session when you plug it in helps a lot. It should show you what the USB device announces itself as.
More informations. Many thanks
lsusb -v -d 2001:3319 root@raspi:~# lsusb -v -d2001:3319
Bus 001 Device 007: ID 2001:3319 D-Link Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x2001 D-Link Corp. idProduct 0x3319 bcdDevice 2.00 iManufacturer 1 Realtek iProduct 2 802.11n WLAN Adapter iSerial 3 (error) bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0035 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 5 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 2 802.11n WLAN Adapter Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x87 EP 7 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x08 EP 8 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x000c bNumDeviceCaps 1 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x00000002 HIRD Link Power Management (LPM) Supported can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0001 Self Powered root@raspi:~#
---- /var/log/messages: Aug 21 09:27:54 raspi kernel: [ 307.194765] usb 1-1.3: new high-speed USB device number 7 using dwc_otg Aug 21 09:27:54 raspi kernel: [ 307.327814] usb 1-1.3: New USB device found, idVendor=2001, idProduct=3319, bcdDevice= 2.00 Aug 21 09:27:54 raspi kernel: [ 307.327841] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 21 09:27:54 raspi kernel: [ 307.327855] usb 1-1.3: Product: 802.11n WLAN Adapter Aug 21 09:27:54 raspi kernel: [ 307.327865] usb 1-1.3: Manufacturer: Realtek Aug 21 09:27:54 raspi mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.3" Aug 21 09:27:54 raspi mtp-probe: bus: 1, device: 7 was not an MTP device Aug 21 09:27:54 raspi mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.3" Aug 21 09:27:54 raspi mtp-probe: bus: 1, device: 7 was not an MTP device
root@raspi:~# uname -a Linux raspi 4.19.58+ #1245 Fri Jul 12 17:20:08 BST 2019 armv6l GNU/Linux
Apparently an "MTP device" is a protocol handler for transferring files to and from an Android phone.
Your RPi knows that your wifi dongle is a Realtech 802.11n WLAN Adapter but apparently doesn't have the drivers for it installed. Use apt to search the Raspbian package repository for a suitable driver and install that.
-- Martin | martin at Gregorie | gregorie dot org
That is a DLINK DW131 adapter
Linux support is not good
suggests there is a pi driver out there, but you need the one that matches your kernel
-- "Socialist governments traditionally do make a financial mess. They always run out of other people's money. It's quite a characteristic of them" Margaret Thatcher
it might lack Linux drivers, particularly on ARM [especially if it's a broadcom device].
I suggest using 'lsusb' to determine whether or not it's even being recognized. I've tried wireless USB devices (wifi and bluetooth) on RPi original model B before and had no problems with it, other than that the old legacy bluez bluetooth support broke after wheezy... (and as far as I can tell, was never fixed)
but that's a side issue, not really related here. Point is, if there's a Linux USB driver for it you should be able to use it just fine.
And 'lsusb' should tell ya.
-- (aka 'Bombastic Bob' in case you wondered) 'Feeling with my fingers, and thinking with my brain' - me 'your story is so touching, but it sounds just like a lie' "Straighten up and fly right"
what really helped is apt-get update apt-get upgrade
and:
# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored.
i2c-dev rtl8192cu rtl_usb rtl8192c_common rtlwifi mac80211
--
root@raspi:~# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev
update_config=1
country=BE
network={
ssid="SSID"
psk="PASS"
key_mgmt=WPA-PSK
}
network={
ssid="SSID"
psk=.... generated
}
many thanks to all.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.