so what do i do with this now?
What we are trying to do, is figure out why your 5300 AGN wireless does not work. I believe it is due to one of three reasons:
- the subversion of an Intel 5300 AGN that your PC has does not yet work with openSUSE, or
- you are too new to openSUSE to figure out what needs to be done to setup the wireless, given openSUSE’s quirks, and given in the default KDE4 wireless application is still a bit buggy.
- your router is not configured to work with this wireless device, and you may need to try it with a different router
I think what would be useful, is to do what I suggested above, which is to check what 5300AGN subversion you have on your PC. I tried to explain HOW to do that above.
It appears you do not understand my advice.
Let me try again. Start by typing
/sbin/lspci | grep 5300
on my PC this gives:
04:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection
and on your PC this gives:
07:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection
Note the** 07:00.0.** That is important to be able to navigate the larger file we may have to produce next.
/sbin/lspci -vv | grep Intel
and look for the line with 07:00.0 in it. What does the line below it say? On my PC, if I type “/sbin/lspci -vv | grep Intel”, the line below 04:00.0 (because I have to use 04:00.0 instead of 07:00.0) gives me:
04:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection Subsystem: Intel Corporation Device 1121
which tells me my Dell Studio 1537 laptop’s Intel PRO/Wireless 5300 AGN is of the version 1121.
So what is yours?
Alternatively, you can type:
/sbin/lspci -vv > list-pci-devices.txt
and then open up list-pci-devices.txt with a text editor, and look for the section associated with 07:00.0. On my PC, if I type that, and if I look for 04:00.0, I find:
04:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection Subsystem: Intel Corporation Device 1121 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 217 Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=8] Capabilities: <access denied> Kernel driver in use: iwlagn Kernel modules: iwlagn
again, what do you get?
That is as basic as I can explain this. If you find that too complex, then I’ll bow out of this thread now and quit, because our knowledge differences are simply too big, and I can’t figure out how to make it more simple. And I suspect there are others who can explain much better than I.[/size]
Once you know what your 5300 AGN version is, go to this URL and look it up.
I gave you link to a thread, where there was discussion on these different 5300 AGN versions:
OpenSolaris Forums : Wifi Link 5300 Wireless Adapter, iwh, …
Look there to see what they say about your version.
For example, one thing I noted was this URL on that page:
Wifi Link 5300 and 5100 Series [LWN.net]
That took me to an Intel announcement, where I noted my 5300 AGN was listed, giving me
confidence mine would work (and mine does work).
In that Intel announcement, is your 5300 AGN listed? In case you can not find that URL
From: “Tomas Winkler” <firstname.lastname@example.org>
To: linux-wireless <email@example.com>, LKML <firstname.lastname@example.org>, email@example.com, “Zhu Yi” <firstname.lastname@example.org>
Subject: [ANNOUNCE] Wifi Link 5300 and 5100 Series
Date: Thu, 14 Aug 2008 00:11:24 +0300
Intel would like to announce Linux support for Wifi Link 5000 and 5100 Series Adapters under iwlwifi driver (iwlagn.ko)
The Intel(R) WiFi Link 5100 Series and 5300 is a families of IEEE 802.11a/b/g/Draft-N1 wireless network adapters that operate in both the 2.4 GHz and 5.0 GHz spectra. These adapters, available in both PCIe* Mini Card and Half Mini Card form factor
5100 1x2 MIMO up to 300Mbps
5300 3x3 MIMO up to 450Mbps
… snipped …
pci.ids were already sent to The PCI ID Repository
8086 Intel Corporation
4232 Wifi Link 5100 Wireless Adapter
[INDENT] 8086 1201 5100ABGN Mini Card
8086 1205 5100BG Mini Card
8086 1206 5100ABG Mini Card
8086 1301 5100ABGN Half Mini Card
8086 1305 5100BG Half Mini Card
8086 1306 5100ABG Half Mini Card
8086 1321 5100ABGN Half Mini Card Dell
8086 1326 5100ABG Half Mini Card Dell[/INDENT]
4235 Wifi Link 5300 Wireless Adapter
[INDENT] 8086 1001 5300ABGN Mini Card
8086 1101 5300ABGN Half Mini Card
8086 1121 5300ABGN Half Mini Card Dell[/INDENT]
4236 Wifi Link 5300 Wireless Adapter
[INDENT] 8086 1011 5300ABGN Mini Card Lenovo[/INDENT]
4237 Wifi Link 5100 Wireless Adapter
[INDENT] 8086 1211 5100ABGN Mini Card Lenovo
8086 1216 5100ABG Mini Card Lenovo[/INDENT]
In case this being new to openSUSE is the reason, I have added below the content of what I sent to a friend in an email. I don’t know yet if this advice has helped them, but I offer this to you, in case it might help you. Apologies if you find this insulting, … I do not know the state of your knowledge, and this is being offered up in the case that it might help.
… You could use the “traditional ifup” or instead use wicd (I
have both instructions for the traditional, and also a link below about
KNetworkManager: Some details:
The state of wireless management in KDE4 is still not as good as that of KDE3, although progress is being made, and is almost there. I note these links: [list]
[li] KNetworkManager: KNetworkManager - openSUSE
[/li]> [li] KDE4.2 progress report on KNetworkmanager:
[/li]> KDE 4.2 Progress, New NetworkManager Plasmoid Coming
[li] KDE4 networkmanager plans: [ vizZzion.org :: Networkmanager in KDE4. ]
In my case, both of my laptop’s have Intel wireless, with support right in the kernel.
But although the hardware network wireless driver is already in place when I was testing the openSUSE-11.1 KDE-4.3. liveCD, and also testing the openSUSE-11.2 milestone-6 liveCD with KDE-4.3, I noted Network Manager in the lower right corner did not work well with wireless.
In both cases I ended up going to YaST > Network Devices > Network Settings and
 acknowledge the warning about NetworkManagement controlling the Network
 under Global Options Tab select the “Traditional method with ifup”
 disable ipv6 (it will ask for a reboot, don’t do that now)
 Overview Tab - select your wireless card and select edit. Go for the default settings except as I noted below
 while in Edit Select “next”
 Under Network Name ESSID select scan network, and then in drop down list select your SSID
 Select your authentication mode (in our case it is WPA-PSK)
 Enter your passphrase
 Select Next
 Select OK
 You may get a notification from Network Management that it is disabled.
And wireless then works. Also, next time you reboot ipv6 will be disabled but hopefully you do not need to rush that reboot. Disabling ipv6 is just a performance tuning measure.
But as noted, you may prefer to install wicd.
Until KNetworkManager is sufficiently mature for KDE4, many wireless “gurus” are recommending one instead use “wicd” for openSUSE. There is guidance here: Wicd - openSUSE
Wireless in General
Note when it comes to getting wireless to work with openSUSE, there is a Hardware Compatibility List here:
HCL/Network Adapters (Wireless) - openSUSE
On our forum, we recommend new users go here and read the “stickies” at the top of the page: Wireless - openSUSE Forums
We have experts on the forum who know way way more than I about wireless. If you post asking for help, please read the stickies first, and then when posting tell them your openSUSE version, your deskop version (ie KDE-4.3), your wireless hardware (as obtained from “/sbin/lspci” ).
With trepidation, I’m entering this thread. Normally, I don’t do Intel
wireless devices, but I’m making a special case here.
I have reread the entire thread and have the following comments:
First of all to dzuchowski: (1) Do you have a problem answering
questions? In several postings, oldcpu asked for simple information
that he never got. (2) This forum is not the place to tell people how
to make Windows work. We simply do not care. The only reason to
mention that other OS (sic) is to indicate that the hardware is
functional. (3) You really started badly by berating the list when no
one answered your original post. As was stated, the 5300 AGN cards
just plain work.
To oldcpu: You are probably correct in your assessment of the OP’s
capabilities, and I know how hard it is to not make that kind of
response, but please just walk away.
Now to the problem:
Does the card send and receive information? The quickest way to tell
is to use the following command:
sudo /usr/sbin/iwlist scan
Please post the output from that command.
Note: If you fail to provide answers to my questions, I’ll simply go away.
donald@linux-l8bw:~> sudo /usr/sbin/iwlist s
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
sudo /usr/sbin/iwlist scan
> donald@linux-l8bw:~> sudo /usr/sbin/iwlist s
> lo Interface doesn’t support scanning.
> eth0 Interface doesn’t support scanning.
You do not have any wireless device created. Now we need to find out why.
What do the commands below show?
lsmod | grep iwl dmesg | grep iwl
For: lsmod | grep iwl
iwlagn 98956 0
iwlcore 94612 1 iwlagn
rfkill 11044 1 iwlcore
mac80211 242320 2 iwlagn,iwlcore
led_class 5008 2 iwlcore,asus_laptop
cfg80211 28200 3 iwlagn,iwlcore,mac80211
For: dmesg | grep iwl
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:07:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 5300AGN REV=0x24
iwlagn: Unsuported EEPROM VER=0x114 < 0x11a CALIB=0x3 < 0x4
iwlagn 0000:07:00.0: PCI INT A disabled
iwlagn: probe of 0000:07:00.0 failed with error -22
Thanks for the help. I am new to linux but an expierenced windows person and want to figure out some of this stuff. I just learned of the opensuse kde admin file manager which makes copying files easier to the root areas…
> iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
> iwlagn: Copyright(c) 2003-2008 Intel Corporation
> iwlagn 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwlagn 0000:07:00.0: setting latency timer to 64
> iwlagn: Detected Intel Wireless WiFi Link 5300AGN REV=0x24
> iwlagn: Unsuported EEPROM VER=0x114 < 0x11a CALIB=0x3 < 0x4
> iwlagn 0000:07:00.0: PCI INT A disabled
> iwlagn: probe of 0000:07:00.0 failed with error -22
Where did you get this card? Please see the thread at
FYI, Comment #6 is from the head of the Intel driver development team
working on Linux drivers.
I purchased it off of ebay: New Intel WiFi Link 5300 300M 11n Mini PCI-E Card USA - eBay (item 290335478970 end time Aug-29-09 14:19:11 PDT)
I have also bought the intel 5350 with wimax that should arrive this week just incase their is somethig wrong with the current card. As i understand it both cards the 5300 and 5350 use the same drivers…
Intel 5350 i just ordered: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=400052510578&ssPageName=STRK:MEWNX:IT
> I purchased it off of ebay: ‘New Intel WiFi Link 5300 300M 11n Mini
> PCI-E Card USA - eBay (item 290335478970 end time Aug-29-09 14:19:11
> PDT)’ (http://tinyurl.com/mwclvl)
> I have also bought the intel 5350 with wimax that should arrive this
> week just incase their is somethig wrong with the current card. As i
> understand it both cards the 5300 and 5350 use the same drivers…
> Intel 5350 i just ordered: http://tinyurl.com/lmv3o6
It appears as though you were sold an illicit board. I wrote Reinette
about your problem and CC’d the wireless mailing list. Perhaps he has
some new ideas. You might want to explore the possibility of getting
your money back.
thanks, they have a 100% money back for 30 days minus shipping. I will contact them. What do you think of the intel 5350 one that i posted a link to. It sounds as if it is not a energing sample so it should be oem. Do you that that one is ok, it has wimax. I only ordered it since i may want it for future usage in a year or so…
> thanks, they have a 100% money back for 30 days minus shipping. I will
> contact them. What do you think of the intel 5350 one that i posted a
> link to. It sounds as if it is not a energing sample so it should be
> oem. Do you that that one is ok, it has wimax. I only ordered it since i
> may want it for future usage in a year or so…
The only cards I know about are those made by Broadcom, so I could not
answer that question. I will report what the Intel guys have to say.
lwfinger, thank you for coming back into this thread to help out. As noted, my wireless has always “just worked” and as a result, if something always works, one does not learn much, … and indeed I have not learned much about wireless.
lwfinger I know you know, but In case anyone else is curious as to what the commands you had dzuchowski should give on a functional 5300AGN, I offer the following from my Dell Studio 1537’s Intel Pro Wireless 5300AGN running openSUSE-11.1 (32-bit):
oldcpu@studio15:~> sudo /usr/sbin/iwlist scan root's password: lo Interface doesn't support scanning. eth0 Interface doesn't support scanning. wmaster0 Interface doesn't support scanning. wlan0 Scan completed ............. snipped ....... ............. a big list of the various ESSID's in range ........
oldcpu@studio15:~> lsmod | grep iwl iwlagn 86804 0 iwlcore 83376 1 iwlagn rfkill 8576 2 iwlcore led_class 3896 1 iwlcore mac80211 199864 2 iwlagn,iwlcore cfg80211 23380 3 iwlagn,iwlcore,mac80211
oldcpu@studio15:~> dmesg | grep iwl iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks iwlagn: Copyright(c) 2003-2008 Intel Corporation iwlagn 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn 0000:04:00.0: setting latency timer to 64 iwlagn: Detected Intel Wireless WiFi Link 5300AGN REV=0x24 iwlagn: Tunable channels: 13 802.11bg, 24 802.11a channels phy0: Selected rate control algorithm 'iwl-agn-rs' firmware: requesting iwlwifi-5000-1.ucode Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX
dzuchowski , sorry to read in the end it did not work, but at least part of the mystery was solved (only to open up a new mystery).
Just as a side note, I am running opensuse 11.1 64bit version…
Thanks, I recall that.
In post#4 above, I provided the results of my testing openSUSE-11.2 64-bit milestone-6 with my Dell Studio 1537 laptop (with the Intel 5300AGN) and that wireless worked on my Dell.
If you think it helpful, I can boot an openSUSE-11.1 64-bit live CD on my Dell, and see if the Intel 5300AGN wireless works with that, … I suspect it will (albeit I will likely need to go to YaST to configure).
I note from the Intel sites that they claim the Intel 5350 works with Linux, but I do not recall any openSUSE users claiming success yet. I do recall reading some Ubuntu users claiming success. I checked the openSUSE HCL, and there is no mention of the 5350 in that list: HCL/Network Adapters (Wireless) - openSUSE However that does not mean much, as not everyone checks the list to ensure it is up to date. … On 23-Nov-2008 I was the one to input the Intel 5300 AGN entry into that HCL list.
I note that in this current thread, in post#16 above, I missed your 21:12 edit to your 21:06 post (where you added the “lspci -vv” information). My reply was at 21:10, and I did not go back and re-read your post for subsequent edits. In hindsight, I should have. … although when seeking support, often its better to simply reply to one’s own post, as opposed to putting in an edit.
Anyway, I do not know much about wireless, and I’ll leave this thread to the pro’s. Good luck in your efforts.
Correction to my post. … Searching for 5350 on our forum I note one user reports getting the Intel 5350 working with openSUSE 11.1 and SLED 11 :
- IBM T400: Getting Wireless to work - openSUSE-11.1 Forums (however its not clear if they are using a 32-bit or 64-bit openSUSE).
> Correction to my post. … Searching for 5350 on our forum I note one
> user reports getting the Intel 5350 working with openSUSE 11.1 and SLED
> 11 :
> - ‘IBM T400: Getting Wireless to work - openSUSE-11.1 Forums’
> (http://tinyurl.com/lz9jk4) (however its not clear if they are using
> a 32-bit or 64-bit openSUSE).
I don’t have any statistics, but only my experiences. I heavily test
new kernels in the merge phase between the release of 2.6.X and
2.6.X+1-rc1, which is when one finds the majority of problems. The
results are that there are more glitches on my i386 machines than on
x86_64. My conclusion is that more developers use x86_64 than i386. In
any case, the 64-bit version of Linux is very well tested.
As to the 5300, it is supported as long as the EEPROM is flashed to
the correct level. Unfortunately, flashing in the field is not supported.
I got the following answer from Reinette:
“All production cards are supported by the driver. I thus do not know
how an unsupported card can be obtained from a reputable dealer. Would
it be possible to obtain images of both sides of this card showing all
numbers clearly? You can send this to me off list and I can see if it
is possible to determine what type of card we are dealing with here.”
If possible, could you photograph the card and send the pictures to
Larry dot Finger at lwfinger dot net.
Thanks for the help. I recieved my intel 5350 wifi/wimax card this week and I installed it on both vista/ windows 7 / and OpenSuse 11.1. It worked right out the box only on opensuse 11.1 However this is one common problem amoung windows vista/7/opensuse 11.1 I am using a Linksys wrt600n and when i connect to opensuse 11.1 or windows vista or open suse 11.1 all 64bit I only get about 700k downloads and I have a 15mb cable connection. I place backin the orginal intel 5300 and i get my speeds back up to normal but the 5300 i have does not work with linux as we have seen in the previous posts. The weird thing withthe 5350 and windows vista or windows 7 is that the drivers dont work well if i install the windows drivers for 5350 then the wifi does not show enabled in windows device manger, if i install the drivers for 5300 then the wimax portion for windows does not show enabled in device manager… their is something with this card. i think… got it off ebay and all…