I’m missing something. The USB wireless card shows in YaST under Hardware Info, and lsusb give this:
Bus 001 Device 003: ID: 13b1:002f Linksys AS1000v1 802.11n [Ralink RT3572]
iwconfig shows that there is no connections (don’t have the output for that handy, I only have internet at work, Linux is on my home PC).
Misc. Info:
OpenSuse 12.1 64 bit
wireless card is plugged in to the extension cable that came with it, not sure if that’s relevant
no blinking lights on USB card itself
strong wireless signal is present, as my wireless router is broadcasting, and is only 10 ft. away (iPad can surf through wireless network w/o issues)
same wireless card and computer worked fine on Win 7 64bit, in same location as it is now, in same USB port on the computer, has not been re-seated (though I will try this tonight)
using ifup
My attempts to fix: I’ve tried ndiswrapper, but later read that native Linux drivers are best, where possible. Verified Linux is seeing the card in Hardware Info in YaST, lsusb shows the card, tried to activate wireless services but can’t find correct commands
I’m reading through these pages, but not sure how to proceed. Link 1 and Link 2
My question: How do I turn on OpenSuse’s wireless service and get the card to pick up a signal? Can I get a hint as to the next step?
Thank you for any attention you’re able to give.
On 02/24/2012 09:26 AM, niero wrote:
>
> My question: How do I turn on OpenSuse’s wireless service and get the
> card to pick up a signal? Can I get a hint as to the next step?
> Thank you for any attention you’re able to give.
Just for the record, you never want to use ndiswrapper unless there is no Linux
driver for a device. The reason is that ndiswrapper exposes the kernel to the
Windows driver with absolutely no checks. If it has bugs (what software does
not), you end up with the Linux equivalent of the Blue Screen of Death.
Furhtermore, as Linux and windows use memory very differently, there may be bugs
that are harmless in the Windows environment, but deadly under Linux.
That card is handled by driver rt2800usb. As you have a device listed in
iwconfig (actual output is preferred), the driver is likely loaded.
Have you installed the kernel-firmware package? The necessary file is
/lib/firmware/rt2870.bin.
What does ‘sudo /usr/sbin/iwlist scan’ show?
Finally, any configuration steps are completely different with Gnome that for
KDE or any other desktop. Please tell us which one you use.
Thanks for your reply. That’s good to know, I hadn’t heard that about ndiswrapper.
I’m running KDE, the latest version.
I will try the “iwlist scan” suggestion tonight after work and let you know. I may not be able to post again until Monday (no internet at home).
Thanks again.
On 02/24/2012 12:46 PM, niero wrote:
>
> Hi lwfinger,
>
> Thanks for your reply. That’s good to know, I hadn’t heard that about
> ndiswrapper.
Yes, it runs the Windows driver in the inner-most ring of the OS. No prior
protection against any kind of error. Some only generate a kernel oops, but
others such a a page fault in interrupt code will panic the kernel. All you see
is the console lights blinking at 1 Hz.
> I’m running KDE, the latest version.
>
> I will try the “iwlist scan” suggestion tonight after work and let you
> know. I may not be able to post again until Monday (no internet at
> home).
I didn’t get my output from iwlist yet. Forgot to bring it to work. I was busy with some hard drive issues this weekend.
However, I do have another question.
I’m reading quite a few pages and forum posts on wireless issues, but things are still a hodge-podge in my mind; Meaning, I’m not understanding the overall picture. What are the basic steps for hooking up wireless internet on Linux?
Please correct this if wrong:
Wireless Card Walkthrough
Attach wireless device
Check to see if Linux sees device. Command is: hwinfo
If device is seen, get info for device. Command is: lsusb or lspci
Get driver. Go to Google with info from lsusb or lspci
Load driver. Command is: _____ ? modprobe??
Wireless should now work.
Write driver info to config file. In Opensuse this file is: ______ ?
If anyone has a moment to add even one bit of info, it would be most appreciated. I’d like to have a guide as I’ll be doing this all again with my laptop later on.
Any attention you’re able to give is most appreciated. Thank you.
On 02/27/2012 10:46 AM, niero wrote:
> Wireless_Card_Walkthrough
> 1. Attach wireless device
> 2. Check to see if Linux sees device. Command is: hwinfo
> 3. If device is seen, get info for device. Command is: lsusb or
> lspci
> 4. Get driver. Go to Google with info from lsusb or lspci
> 5. Load driver. Command is: _____ ? modprobe??
> 6. Wireless should now work.
> 7. Write driver info to config file. In Opensuse this file is: ______
I think you are overthinking the problem. I recommend the following:
From YaST => Network Devices => Network Settings, select the Global Options tab
and make certain that the “User Controlled with NetworkManager” button is selected.
After exit from YaST, make certain that the wireless applet is running. The
steps needed to this are different for KDE and Gnome.
Launch the applet and check to see if a wireless option is available. If it is,
and it is not grayed out, then do the configuration. If you use WEP, then enter
the hexadecimal key. Using a passphrase is unlikely to work.
If no wireless connection is found, does ‘/usr/sbin/iwconfig’ show your device?
If not, then check dmesg to see why. If the device shows up, then try to scan
for APs with ‘sudo /usr/sbin/iwlist scan’. If you cannot scan due to the network
being down, then check for something blocking the radio. Use ‘/usr/sbin/rfkill
list’ to see. You will likely need to install the rfkill package. If you see a
“hard” block, turn your wireless switch on. If there is a “soft” block, check if
‘sudo /usr/sbin/rfkill unblock all’ to see if it clears the problem. If it does,
then you will be ready to go. If not, post the output of ‘/usr/sbin/rfkill list’
here.
I will give those things a try tonight or tomorrow evening. I know iwconfig lists the device.
I’m using WPA, I believe. It is a long passphrase, not a hexadecimal key. Will that not work? I’ve been reading that WEP isn’t nearly as secure. Thus, I’d like to stay with WPA if possible.
Thanks again for your assistance w/ this. It is most appreciated.
The problems with (non hexadecimal) passphrases/encryption keys/representations of keys exist only “If” you would use the old WEP (The second sentence I cited from Larry Finger is probably related to the sentence before it and so only to WEP.).
And in addition: WEP is very insecure - see Wired Equivalent Privacy - Wikipedia, the free encyclopedia .
So if you are using WPA there is probably no reason to use WEP instead (but maybe WPA2 for more security).
On 02/28/2012 08:46 AM, niero wrote:
>
> Cool, thanks, pstazienfresser. Good to know.
Just to reemphasize, WEP should never be used unless you have a really old AP
that does not support WPA. WEP can be cracked in less than 5 minutes. Using WEP
is better than no encryption, but not by much.
It is also possible to crack WPA, but that is a lot harder. To my knowledge, no
one has ever cracked WPA2 unless a trivial passphrase is used. All such schemes
are susceptible to dictionary lookup cracking, but if your phrase is not in a
dictionary, and of sufficient length, then it is quite secure. My WPA2 secret is
28 characters and is full of special characters, yet it is easily remembered.
From your iwlist output, I doubt that the device shows up in iwconfig. I
suspect that you have a problem with missing firmware. Did you check for the
firmware file that I mentioned earlier?
I did, and YAST said that module was installed. Forgot to mention that, sorry.
Although I didn’t find that particular file in the file system. What does that tell me? Does it mean it’s there but in a different location? Or that I need an updated version? (I installed off of the full 12.1, 4.3 GB DVD that I downloaded within the last six weeks.
On 02/28/2012 11:06 AM, niero wrote:
>
> lwfinger;2444255 Wrote:
>>
>> From your iwlist output, I doubt that the device shows up in iwconfig.
>> I
>> suspect that you have a problem with missing firmware. Did you check
>> for the
>> firmware file that I mentioned earlier?
>
> I did, and YAST said that module was installed. Forgot to mention that,
> sorry.
> Although I didn’t find that particular file in the file system. What
> does that tell me? Does it mean it’s there but in a different location?
> Or that I need an updated version? (I installed off of the full 12.1,
> 4.3 GB DVD that I downloaded within the last six weeks.
No, it is not in a different location - it means that you do not have the
firmware installed. Run the command
sudo zypper install kernel-firmware
Depending on the state of your repos, you will either need the DVD or a wired
connection.
I will give this a try tonight.
Incidentally, I tried to get a wired connection going last weekend, but to no avail. I thought wired connections were pretty much plug and play. I wonder if it’s the fact that KNetworkManager isn’t handling things. I’ll do some research.
On 03/01/2012 07:16 AM, niero wrote:
>
> I will give this a try tonight.
> Incidentally, I tried to get a wired connection going last weekend, but
> to no avail. I thought wired connections were pretty much plug and play.
> I wonder if it’s the fact that KNetworkManager isn’t handling things.
> I’ll do some research.
Connections with a wire are usually attained without much difficulty, but there
are corner cases. If you have trouble with that, then download the following
file by any means possible (including Windows):
Thank you, I’ll throw this on my PC tonight and try to connect via cable. Incidentally, is this also the package that would install the rt wireless driver you mentioned?
On 03/01/2012 04:06 PM, niero wrote:
>
> Thank you, I’ll throw this on my PC tonight and try to connect via
> cable. Incidentally, is this also the package that would install the rt
> wireless driver you mentioned?
You don’t need that package for wired. Nearly all Ethernet devices have their
firmware hard coded. That package is primarily needed for other kinds of
interfaces. The driver that you need for wireless is already in the kernel. What
you are lacking is the code for the CPU on the card - in other words “firmware”.
Once that rpm is installed, your wireless should come to life.
When I tried to install the rpm, it said it was already installed, and that one of the files conflicted with another package that was installed. But it wasn’t the driver file. I forgot to include the print out for it.
So I did a little exploring w/ commands I saw in other posts about wireless issues. Hopefully this information helps.
I also brought up KNetworkManager, but it doesn’t see anything. At all. No wired or wireless.
I’m going to do some research this morning and see what I can find.
Any ideas?
Thank you for any attention you’re able to give.
ifconfig
eth0 Link encap:Ethernet HWaddr 00:1A:4D:70:74:88
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)
Interrupt:16
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:2006 errors:0 dropped:0 overruns:0 frame:0
TX packets:2006 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:159677 (155.9 Kb) TX bytes:159677 (155.9 Kb)v
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 13b1:002f Linksys AE1000 v1 802.11n [Ralink RT3572]
Bus 001 Device 004: ID 1058:1021 Western Digital Technologies, Inc. Elements 2TB
Bus 003 Device 002: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device
Bus 007 Device 002: ID 046d:c068 Logitech, Inc. G500 Laser Mouse
Bus 007 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 005: ID 1516:1603 CompUSA Flash Drive
dhcpcd eth0
err, eth0: timed out
warn, eth0: using IPV4LL address 169.254.13.133
ifconfig eth0 up
linux-gpbe:/home/thedude # ps -A | grep dhcp
11524 ? 00:00:00 dhcpcd
linux-gpbe:/home/thedude # kill 11524
linux-gpbe:/home/thedude # dhcpcd eth0
err, eth0: timed out
warn, eth0: using IPV4LL address 169.254.13.133linux-gpbe:/home/thedude # ps -A | grep dhcp
11524 ? 00:00:00 dhcpcd
linux-gpbe:/home/thedude # kill 11524
linux-gpbe:/home/thedude # dhcpcd eth0
err, eth0: timed out
warn, eth0: using IPV4LL address 169.254.13.133
linux-gpbe:/home/thedude # lsmod
Module Size Used by
af_packet 35338 2
ip6t_LOG 17095 5
xt_tcpudp 12924 2
xt_pkttype 12504 3
ipt_LOG 13040 5
xt_limit 12711 10
tun 22987 0
nls_iso8859_1 12713 3
nls_cp437 16991 3
vfat 17535 3
fat 65607 1 vfat
vboxpci 27384 0
vboxnetadp 13382 0
vboxnetflt 23882 0
vboxdrv 300157 3 vboxpci,vboxnetadp,vboxnetflt
vmsync 13068 0
vmblock 22807 1
ip6t_REJECT 12974 3
nf_conntrack_ipv6 14349 3
nf_defrag_ipv6 18438 1 nf_conntrack_ipv6
ip6table_raw 12683 1
xt_NOTRACK 12504 4
ipt_REJECT 12576 3
iptable_raw 12678 1 10
10
tun 22987 0 tun 22987 0
iptable_filter 12810 1
ip6table_mangle 12740 0
nf_conntrack_netbios_ns 12665 0
nf_conntrack_broadcast 12589 1 nf_conntrack_netbios_ns
nf_conntrack_ipv4 14783 3
nf_defrag_ipv4 12729 1 nf_conntrack_ipv4
ip_tables 27717 2 iptable_raw,iptable_filter
xt_conntrack 12760 6
nf_conntrack 96202 6 nf_conntrack_ipv6,xt_NOTRACK,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack
ip6table_filter 12815 1
ip6_tables 27864 4 ip6t_LOG,ip6table_raw,ip6table_mangle,ip6table_filter
x_tables 34102 16 ip6t_LOG,xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,ip6table_raw,xt_NOTRACK,ipt_REJECT,iptable_raw,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables
cpufreq_conservative 13821 0
cpufreq_userspace 13162 0
cpufreq_powersave 12618 0
acpi_cpufreq 18766 1
mperf 12667 1 acpi_cpufreq
microcode 35758 0
fuse 87950 7
dm_mod 92333 0
joydev 17606 0
snd_usb_audio 134896 3
snd_usbmidi_lib 25256 1 snd_usb_audio
snd_rawmidi 34844 1 snd_usbmidi_lib
snd_seq_device 14540 1 snd_rawmidi
ppdev 17718 0
kvm_intel 141431 0
kvm 434774 1 kvm_intel
sr_mod 22464 0
cdrom 47994 1 sr_mod
floppy 74461 0
parport_pc 37537 0
parport 46528 2 ppdev,parport_pc
pcspkr 12702 0
i2c_i801 18013 0
sg 36561 0
snd_hda_codec_realtek 338028 1
sky2 62935 0
iTCO_wdt 17863 0
iTCO_vendor_support 13718 1 iTCO_wdt
snd_hda_intel 33441 2
snd_hda_codec 118874 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13613 2 snd_usb_audio,snd_hda_codec
snd_pcm 109594 4 snd_usb_audio,snd_hda_intel,snd_hda_codec
snd_timer 34086 1 snd_pcm
snd 86602 19 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 15091 1 snd
snd_page_alloc 18572 2 snd_hda_intel,snd_pcm
autofs4 43290 2
nouveau 778194 3
ttm 80953 1 nouveau
drm_kms_helper 42489 1 nouveau
drm 252967 5 nouveau,ttm,drm_kms_helper
i2c_algo_bit 13423 1 nouveau
mxm_wmi 12979 1 nouveau
wmi 19256 1 mxm_wmi
video 19653 1 nouveau
processor 45192 1 acpi_cpufreq
thermal_sys 25017 2 video,processor
button 13949 1 nouveau
ata_generic 12937 0
sata_sil 13539 0
pata_jmicron 12747 0
linux-gpbe:/home/thedude # ifup eth0
Sorry, there is already an instance of ifplugd for eth0 running.
eth0 device: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
eth0 is controlled by ifplugd
I was reading on Welcome - Linux Wireless and saw this posting on the main page, regarding changes to the 3.0 kernel.
With a little delay, Linus released 3.0. Besides numbering change, this version contains some interesting wireless changes
ar9170usb: remove driver (replaced by carl9170)
ath6kl: add support for AR6003 v2.1.1
ath9k_htc: add AP and P2P modes
ath9k_hw: support for AR9340
b43: fix DMA problems on some LP-PHY cards
iwlagn: fix performance regression since 2.6.35 (use cts-to-self protection)
iwlagn: support for new 105 series devices
rt2860sta: remove driver (replaced by mainline rt2800pci)
**rt2870sta: remove driver (replaced by mainline rt2800usb)**
rt2x00: Initial support for RT5370 USB devices
rt2x00: Enable support for RT53xx PCI devices by default
rt2x00: RT33xx device support is no longer experimental
rtlwifi: support for RTL8192SE chips added
Is the rt2870sta driver above the same as the “regular” rt2870 driver? I wonder if I just have the wrong driver loaded.
On 03/02/2012 08:26 AM, niero wrote:
>
> I was reading on ‘Welcome - Linux Wireless’ (http://linuxwireless.org/)
> and saw this posting on the main page, regarding changes to the 3.0
> kernel.
>
>> With a little delay, Linus released 3.0. Besides numbering change, this
>> version contains some interesting wireless changes
>>
>> ar9170usb: remove driver (replaced by carl9170)
>> ath6kl: add support for AR6003 v2.1.1
>> ath9k_htc: add AP and P2P modes
>> ath9k_hw: support for AR9340
>> b43: fix DMA problems on some LP-PHY cards
>> iwlagn: fix performance regression since 2.6.35 (use cts-to-self
>> protection)
>> iwlagn: support for new 105 series devices
>> rt2860sta: remove driver (replaced by mainline rt2800pci)
>> rt2870sta: remove driver (replaced by mainline rt2800usb)
>> rt2x00: Initial support for RT5370 USB devices
>> rt2x00: Enable support for RT53xx PCI devices by default
>> rt2x00: RT33xx device support is no longer experimental
>> rtlwifi: support for RTL8192SE chips added
>
> Is the rt2870sta driver above the same as the “regular” rt2870 driver?
> I wonder if I just have the wrong driver loaded.
The rt2870sta driver was obsoleted by rt2800usb. The kernel is smart enough to
load the proper driver based on the USB IDs. Your problem is that the
configuration variable CONFIG_RT2800USB_RT35XX is not enabled, thus the kernel
does not recognize your device. I will have that fixed.
In the meantime, I will create a new configuration with the device enabled,
build a new rpm, and upload it to a place you can reach. That will take a while
as I never build an rpm and I’ll have to learn how to do that.
