#1 permalink Just Joined!
Join Date: Nov 2008
Posts: 14
D-Link WUA-1340 USB Wireless on Fedora 9
Hello All,
I am struggling to get this USB wireless nic (D-Link WUA-1340) working on Fedora 9. It seems to work when I boot into Gnome but it does not work when I boot up to the console which I where I spent most of my time.
I see this odd wmaster0 entry when I run ifconfig so I think there is some problem.
Any help is appreciated! Here is the output:
/sbin/ifconfig
Code:
eth0 Link encap:Ethernet HWaddr 00:40:F4:7F:34:B3
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::240:f4ff:fe7f:34b3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:473350 errors:0 dropped:0 overruns:0 frame:0
TX packets:241166 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:710673895 (677.7 MiB) TX bytes:16615783 (15.8 MiB)
Interrupt:10 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2121 errors:0 dropped:0 overruns:0 frame:0
TX packets:2121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:108346 (105.8 KiB) TX bytes:108346 (105.8 KiB)
wlan0 Link encap:Ethernet HWaddr 00:1E:58:9E:37:02
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)
wmaster0 Link encap:UNSPEC HWaddr 00-1E-58-9E-37-02-F4-FF-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING 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)
/sbin/iwconfig
Code:
lo no wireless extensions.
eth0 no wireless extensions.
pan0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=22 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
/sbin/lsusb
Code:
Bus 001 Device 004: ID 07d1:3c04 D-Link System WUA-1340
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
/sbin/lsmod
Code:
Module Size Used by
bridge 46104 0
bnep 14464 2
rfcomm 34576 4
l2cap 22272 16 bnep,rfcomm
bluetooth 47588 5 bnep,rfcomm,l2cap
fuse 41116 3
sunrpc 151412 3
loop 16772 0
dm_multipath 18056 0
ipv6 221660 12
ppdev 10244 0
snd_emu10k1_synth 10240 0
snd_emux_synth 33920 1 snd_emu10k1_synth
snd_seq_virmidi 8960 1 snd_emux_synth
snd_seq_midi_emul 9088 1 snd_emux_synth
snd_emu10k1 125828 4 snd_emu10k1_synth
snd_rawmidi 22400 2 snd_seq_virmidi,snd_emu10k1
snd_ac97_codec 94368 1 snd_emu10k1
ac97_bus 5504 1 snd_ac97_codec
snd_seq_dummy 6660 0
snd_seq_oss 30364 0
snd_seq_midi_event 9600 2 snd_seq_virmidi,snd_seq_oss
snd_seq 48448 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 42496 0
arc4 5760 2
snd_mixer_oss 16768 1 snd_pcm_oss
parport_pc 25364 0
parport 32084 2 ppdev,parport_pc
ecb 6528 2
snd_pcm 67076 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
crypto_blkcipher 17924 1 ecb
snd_seq_device 10124 7 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer 21640 3 snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc 11400 2 snd_emu10k1,snd_pcm
snd_util_mem 7552 2 snd_emux_synth,snd_emu10k1
snd_hwdep 10500 2 snd_emux_synth,snd_emu10k1
snd 48312 23 snd_emu10k1_synth,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_seq_dummy,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_util_mem,snd_hwdep
floppy 52084 0
pcspkr 6272 0
8139too 23936 0
soundcore 9288 1 snd
8139cp 20864 0
emu10k1_gp 6656 0
mii 8192 2 8139too,8139cp
gameport 13708 2 emu10k1_gp
rt73usb 26880 0
crc_itu_t 5760 1 rt73usb
rt2x00usb 12544 1 rt73usb
rt2x00lib 31744 2 rt73usb,rt2x00usb
rfkill 9108 1 rt2x00lib
input_polldev 7176 1 rt2x00lib
mac80211 185184 2 rt2x00usb,rt2x00lib
cfg80211 24712 2 rt2x00lib,mac80211
i2c_viapro 10644 0
i2c_core 20628 1 i2c_viapro
button 10000 0
sg 31028 0
sr_mod 17064 0
cdrom 32796 1 sr_mod
dm_snapshot 18468 0
dm_zero 5632 0
dm_mirror 26116 0
dm_mod 48980 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
ata_generic 8964 0
pata_via 11524 2
pata_acpi 8192 0
libata 126688 3 ata_generic,pata_via,pata_acpi
sd_mod 25624 3
scsi_mod 120820 4 sg,sr_mod,libata,sd_mod
ext3 108424 2
jbd 40852 1 ext3
mbcache 10116 1 ext3
uhci_hcd 22928 0
ohci_hcd 22276 0
ehci_hcd 32268 0
dmesg
Code:
sr 1:0:1:0: Attached scsi generic sg3 type 5
input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
ACPI: Power Button (CM) [PWRB]
phy0: Selected rate control algorithm 'pid'
gameport: EMU10K1 is pci0000:00:12.1/gameport0, io 0xe000, speed 1242kHz
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
8139cp 0000:00:13.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp 0000:00:13.0: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt 0000:00:13.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
input: PC Speaker as /devices/platform/pcspkr/input/input5
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
parport_pc 00:09: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
eth0: RealTek RTL8139 at 0xd293c000, 00:40:f4:7f:34:b3, IRQ 10
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
Registered led device: rt73usb-phy0:radio
Registered led device: rt73usb-phy0:assoc
Registered led device: rt73usb-phy0:quality
usbcore: registered new interface driver rt73usb
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
ALSA sound/pci/emu10k1/emu10k1_main.c:1747: vendor=0x1102, device=0x2, subsystem_vendor_id=0x80271102, subsystem_id=0x8027
ALSA sound/pci/emu10k1/emu10k1_main.c:1772: Sound card name=SBLive! Value [CT4832]
ppdev: user-space parallel port driver
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
device-mapper: multipath: version 1.0.5 loaded
loop: module loaded
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sdb1, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Adding 589816k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:589816k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
ip6_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (5120 buckets, 20480 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
fuse init (API version 7.9)
SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bridge firewalling registered
pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
ADDRCONF(NETDEV_UP): wlan0: link is not ready
eth0: no IPv6 routers present
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
usb 1-1: USB disconnect, address 2
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
usb 1-1: new full speed USB device using uhci_hcd and address 3
usb 1-1: configuration #1 chosen from 1 choice
phy1: Selected rate control algorithm 'pid'
Registered led device: rt73usb-phy1:radio
Registered led device: rt73usb-phy1:assoc
Registered led device: rt73usb-phy1:quality
usb 1-1: New USB device found, idVendor=07d1, idProduct=3c04
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: 802.11 bg WLAN
usb 1-1: Manufacturer: Ralink
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Any help or suggestions please?
#2 permalink Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
If you spend most of the time without a desktop environment, then you don't want a gui handling your network devices.
Open this program.
Code:
system-config-network
Click on the network card, and click Edit. Make sure that the box next to "Controlled By NetworkManager" is unchecked. You may want to do this for all network devices.
Now you can control the wireless through terminal commands. Here are some.
ifup
ifdown
iwconfig
iwlist
You bring to device online with ifup wlan0, and down with ifdown wlan0. You use iwconfig to set the connection specifics. Use these commands for more info on using it.
You can use iwlist to check for available networks.
Also run help and man commands for more info on this.
If you are connection to a WPA encrypted network, you will need to install and configure wpa_supplicant. This is not needed with NetworkManager, but if you're not using NetworkManager, it is needed for secure connections.
__________________
#3 permalink Just Joined!
Join Date: Nov 2008
Posts: 14
Thanks for this info, I have read and tested the commands. I still cannot connect when I ping the router, I get a network unreachable error.
This is my error when try to run the
iwup wlan0
Code:
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device wlan0 ; Invalid argument.
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.
Determining IP information for wlan0... failed.
#4 permalink Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
Try this:
Code:
iwconfig wlan0 rate auto
__________________
#5 permalink Just Joined!
Join Date: Nov 2008
Posts: 14
Quote:
Originally Posted by
waterhead Try this:
Code:
iwconfig wlan0 rate auto
After reading the man page that is the first thing that came to my mind. I have tried this and still no luck.
I also get this additional line in the error every a few tries (not each time:
Code:
Determining IP information for wlan0...dhclient(2486) is already running - exiting.
I am so confused...
#6 permalink Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
You may need to bring the device down and up again with the ifdown/ifup commands.
dhclient is also a command, something like this:
__________________
#7 permalink Just Joined!
Join Date: Nov 2008
Posts: 14
Quote:
Originally Posted by
waterhead You may need to bring the device down and up again with the ifdown/ifup commands.
dhclient is also a command, something like this:
Ok, this works if I add this in /etc/rc.local
Code:
/bin/sleep 3
/sbin/dhclient wlan0
apparently there is a bug and this is the work around.
What are your thoughts on using a STATIC IP for this wireless connection to avoid dhclient completly?
#8 permalink Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
As long as your router/access point is OK with a static IP, there should be no problem.
__________________
#9 permalink Just Joined!
Join Date: Nov 2008
Posts: 14
Quote:
Originally Posted by
waterhead As long as your router/access point is OK with a static IP, there should be no problem.
Yes indeed the router is ok with it but I wonder if you can tell me how ir where I make these changes?
I am thinking I need to edit the /etc/sysconfig/network-scripts/ifcfg-wlan0
is this correct? and what specifically do I need to change?
thanks.
#10 permalink Trusted Penguin
Join Date: Jul 2004
Location: Franklin, Wisconsin
Posts: 3,957
I would use the file in the /etc/sysconfig/networking/devices. But the files there are identical to the ones in the network-scripts folder.
Change whatever you feel needs changing.
BOOTPROTO=static
NETMASK=255.255.255.0
IPADDR=<Put your static IP address here>
ESSID=<your wireless network name>
NM_CONTROLLED=no
__________________
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools Display Modes Linear Mode
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
Wireless Internet Anything related to getting wireless set up in Linux. WLAN, WiFi, etc.
Submit Your Article
Latest Articles
Editor's Choice
Article Categories
Join Linux Forums Today
Win Great Prizes
Linear Mode
