Vista + 802.11n PCMCIA + AEBS Giga = 300Mbps connection

With this combination, I managed to get a reported 300Mbps connection from my windows Vista laptop to a AEBS N:
Buffalo Wireless-N Nfiniti Dual-Band Notebook Adapter (WLI-CB-AG300N).
Latest vista driver downloaded from Buffalo website.
Airport Extreme Base Station (Gigabyte version) with latest s/w update.
Allow only N client on 5Ghz.
Authentication Type WPA2-PSK.
Both windows and the Buffalo client s/w reports 300Mbps a connection.
Copying a 4GB file, windows reported average speed of 3.2MB/Sec.
Is this correct for a claimed 300Mbps connection?
Only just got this today, so not sure about long term stability.
Peter

Just to follow up, running the same test with my macbook boot camp vista connected wirelessly at 300Mbps, windows reported a speed of 6.1MB/sec. This is nearly twice as fast as the windows laptop & pcmcia card. Maybe the bottleneck is with the pcmcia card, or maybe the drivers need to be tweaked further.
Peter

Similar Messages

Vista and 802.11n on AEBS

Hi,
I've been scratching my head over why I can't connect Vista to my new Extreme network.
I'm running a '802.11n only' network on 5ghz as it seems the best performing setup for my MBP.
Having installed Vista as a 'might need it ocasionally' thing using Bootcamp1.2 ( easy install and no problems) I tried to get onto my 'n' network.
Vista ses the network and prompts for password etc to connect (WPA2) but then says 'unable to connect to network' and diverts me to the usual highly helpful Help pages
The only clue I have to my problems is that Vista reports the network as a 802.11a network.
Does Vista on MBP actually have drivers for 802.11n ?
Any ideas people ?
Thanks
Pete
Macbok Pro C2D Mac OS X (10.4.9)

Vista reports the network as a 802.11a network.
That is probably because you have specified 802.11n only which operates on the same 5GHz band used by 802.11a.
Others have reported joy getting Vista (under Bootcamp) to operate, however I don't recall if they used the 5GHz band. I suspect not.

AirPort Extreme 802.11n Wi-Fi doesn't connect to printer

So, I got the AirPort Extreme 802.11N Wi-Fi connected and working to my cable modem (good times), but now neither computer (PC or Mac) can connect through it to the printer (HP C4280 Aii-in-One) that we connected to the USB port on the back of it.
Any idea what we're doing wrong here? Is there something that needs to be configured within the software of the router?

Work your way through the Apple Troubleshooting Guide to see if that will help get the printer going.
Bear in mind that only the print function will be supported when your device is connected to the USB port on the AirPort Extreme. Scan, copy, fax, maintenance etc. are not supported, so if you need these functions, you will need to connect your all-in-one directly to the computer.
The PC will need to have Bonjour for Windows installed. It's on the CD that came with the AirPort Extreme.

Time Capsule & Vista - 802.11n drivers?

I've set-up the TC to use the wireless-n only on the 5ghz spectrum. Everything is running fine under the Mac OS -- but booting Vista in the boot camp partition and using the wireless-n network is very slow and the signal is very weak.
Do I need load new Vista drivers, or reload the Broadcom drivers from the Mac OS disk in Vista? Any help is appreciated.

I've run into this same issue with a new MacBook Pro. The wifi drivers on my Leopard install disc don't work in Vista on this new machine, so I'm stuck without wifi for now.
From what I've seen so far, we might have to just wait for Apple to release a Boot Camp update to create new drivers for these machines. In the past, this typically means burning a new CD of drivers with the Boot Camp utility in Mac OS X (or dumping them onto a USB drive), then switching over to Windows and installing.
Vista tells me the actual manufacturer of the 802.11n hardware, so I'll try checking their site later this weekend to see if they have a newer driver version themselves that could work.

802.11n Airport Express won't connect to Internet

Hi,
I have recently purchased a new 802.11n Airport Express which works fine with the Airport Utility, but will not connect to the internet through the Ethernet.
It is plugged directly from the cable model into the 802.11n via Ethernet.
I know that it is not the modem/internet service provider because when I pop my old 802.11b/g (model A1084) everything works fine, and I connect no problem.
The settings appear the same, but with the old model I get internet, with the 802.11n I get the flashing amber light. If I set it up manually, and input the same IP, Subnet Mask, and Router number that is working for the 802.11b/g model, I get the solid green light, but no internet.
Originally, I assumed I'd just picked up a lemon, so I exchanged it and I am getting the exact same results so I must be doing something wrong.
Any ideas?
I wanted to extend my network, but use the 802.11n as the internet input so I could take advantage of the faster speeds.

Welcome to the discussions!
You mentioned that you had a cable modem. Although the ISP will claim otherwise, in many cases it will take 20-30 minutes for a modem to completely reset. The reset is needed whenever you change the device that is directly connected to the modem.
Power down the modem and pull the battery if it has one. Power down the rest of the system as well.
Power up the modem first and let it run for 5-10 minutes, then the Express for a few minutes, then your computers.
Once you get things going, we can look into the next puzzle of extending the network. Please post back when you have the "green" light and internet.

Can't join "802.11n only 5Ghz" but can connect to "802.11n only 2.4 GHz"

Using an airport extreme and two MacBook C2D's, I'd like to have the airport create an "802.11n only 5 GHz" network using WPA2 Personal security. For some reason, I can create an 802.11n only 2.4 GHz network and join it, but am unable to join the exact same network using 5 GHz.
Can anyone help me solve this?
I live in an urban environment with TONS of competing networks / microwaves / sonos / cell phones / cordless phones ... on the 2.4Ghz bandwidth and want to use 5 Ghz. What could be causing this problem?

Me reporting back again - I may have narrowed down the problem, on my system at least. I bought a new Airport express with 802.11n capability and I set it up as a separate network to my stereo, broadcasting at 5GHz. It worked fine, and in fact it eliminated the interference problem I was having. Since my computer manages at 5 GHz, as well as the new Airport Express, it means that the problems I have been having broadcasting at 5GHz originate from the Airport Extreme base station. Could be that others are having that problem as well? I'm only sorry that the base station is beyond the warranty period, so I can't return it.

Macbook Pro with Vista does NOT connect to 802.11n

I have a Macbook Pro running Vista and a wifi Linksys WRT350 access point/router, which does 802.11b/g/n. The Macbook Pro only connect to the access point at 802.11g 54Mbps the access point is set to mix-mode. If I set the access point to only 802.11n, the Macbook Pro cannot connect to the access point. If I use bootcamp to load the Mac OS X, the Mac OS X is able to connect to 802.11n. The signal level is pretty good on Vista ad Mac OS X.
Any ideas?

Usually when connecting a camera only the SD card is mounted, so it is normal to see only the SD card mounted on the Desktop. The camera is not actually the device, rather the SD card (and interface) is. Apparently System Information does report correctly on the camera itself.
Be sure to check at Epson's support site for an updated driver compatible with Lion. You can also download the latest drivers package from Apple: Epson Printer Drivers v2.9 OS X.
Of importance is if the scanner is working. If it is working, then it really doesn't matter, except cosmetically, that the device is reported as a printer. You can report that to Apple via Apple Feedback.

WRT160NL and AirPort Express 802.11n Connection

I have a Linksys WRT160NL that is currently connected to 2 Apple AirPort Express 802.11n via WiFi.
The connections are Cable Model via ethernet to WRT160NL
WRT160NL ethernet to PCs running XP and Vista
WRT160NL WiFi to laptops at 802.11g
WRT160NL ethernet to DirecTV HD Box
WRT160NL WiFi to Airport Express to ethernet connection of DirecTV HD Boxes (2 connections) (802.11g)
This current setup works. The hard wired components work as expected and the wifi to the AirPort Expresses work as well. The only issue I have is that the AirPort Expresses are only connecting to the the WRT160NL via WiFi at 802.11g speeds. I want to be able to conenct the AirPort Expresses at 802.11n speeds as I am having some streamin issues for High Def video. I verfied in the DHCP Client Table of the router that the AirPort Exresses are connected via "Wireless-G" to the routers. The AirPort Expresses are running the lastest firmware from Apple and I am running Firmware Version: 1.00.01 B17 on the router.
Any help/ideas on how I can connect the Apple Airport Express to the WRT160NL at 802.11n speeds? Are these 2 devices just not compatible with each other?

Thanks for the reply Scrooge. I have verified that the Apple Airport Express is 802.11n complaint:
http://store.apple.com/us/product/MB321LL/A/AirPort-Express-AirTunes?fnode=MTY1NDA0Mg&mco=MTA4NTc4MTE
I have also checked to make sure tha the router is set to Mixed mode:
Mode:     Mixed
Network Name (SSID):     xxxxxxxxx
Channel Width:    Standard - 20MHz Channel
Wide Channel:    N/A
Standard Channel:    2
Security:    WPA2 Personal
SSID Broadcast:    Enabled
The airport expresses are still connected at 802.11g according to the DHCP Client Table from the router. Is there any way to force the Airport Expresses to connect at 802.11n?
TIA

How can I tell if the connection us 802.11g or 802.11n?

G'day people
I bought a new Time Capsule today and just installed it. Both my iMac and MacBook are backing-up with Time Machine to the Time Capsule; that's great.
I also have an AppleTV and a TiVo set-top-box connected. I want to confirm that the iMac, MacBook and AppleTV are connected to the Time Capsule via 802.11n and the TiVo is connected as 802.11g.
Is there anything I can look up on both computers to confirm 802.11n connection?
Thanks
Al

Just got home from Sydney - Love it there, Mate!
Hold "option" and click the airport icon in
the toolbar. If the rate is over 54, it is n. If 54 or less it could be either, so make sure you are closer to the TC when you do it.
s

New Base Airport Extreme 802.11n .....bugs

Well,
I have just read tens of posts in many forums, included this one.
It seems that the Base Airport Extreme 802.11n has severe problems of connections to internet.
That's is also my case.
This is my config.
1. Modem NetGear DM111P <--> WAN Base Airport Extreme 802.11n
2. LAN Base Airport Extreme 802.1n <--> Ethernet iMac 24"
3. LAN iMac as DHCP auto IP
4. Base Airport set for PPPoE
There is no way to get into Internet.
If I connect the Modem DM111P directly to the iMac 24" LAN the Internet is on, fast, fluid.
With the Airport in betwwen....no way...
Any help ?
I am seriously thinking Apple has distributed a product full of bugs.
Read other forums with same problem.
Beppe
iMac 24" Mac OS X (10.4.8) Base Airprt Extreme + 2 x Airport Express

James,
Confirmed: the NetGear <--> AEBS <--> iMac does not work.
I have set the Bridge Mode as you suggest, but nothing, no internet !
Othe 3 hours of tests in setting tens of conigurations. No one works.
All the leds of the NetGear Modem as the one in the AEBS are solid green.
I will return back the NetGear modem to the retailer.
I am now running with my old Pirelli Modem from Alice Service (Telecom Italia Net) that - even if slower - at least it works.
I am concluding that the Airport Extreme has seriuos problems of compatibility with the open market modems.
Apple should check the SW+HW before selling such difficult items as the the Airport Extreme base.
Just a question: which model/type of modem(s) is(are) effectively compatible with the AEBS ?
If the retailer will permit me this, I will replace the NetGear (a very good modem...what a pity) with a compatible one with this strange base.
Thaks for your help.
Beppe

Manual Static LAN IP address for 802.11n Base Station when using PPPoE

We have a network of about 75 machines. We want to replace our main router with the new Airport Extreme 802.11n base station. WAN connection is PPPoE so we'd use the NAT function. All IP addresses of our machines on the LAN are statically assigned.
Problem is our machines are assigned to find the router at a specific address: 192.168.0.254. The default base station IP in that subnet is 192.168.0.1. Is there any way to change the IP of the base station to 192.168.0.254 from the default of 192.168.0.1? We can do it if we have it join our existing LAN in bridge mode, but we want it to provide the main NAT functions AND connect to our ISP's PPPoE server WITHOUT having to change all our LAN devices to find it at 192.168.0.1. Possible?

The HH will only show devices which use DHCP in the list of devices, unless you've set the device to use a static IP in the HH Home Network page. It's a bit of a silly idea and IMO the software on the router is terrible, but you do it like this...
- Set the printer to use DHCP to get an IP address.
- Log in to the HomeHub 5 and browse to the Home Network page (http://192.168.1.254/index.cgi?active_page=9130)
- Find the printer in the list of devices and click on it.
- Click on 'Yes' next to the "Always use this IP address" option.
- Set the IP address on the printer statically and update your devices to use the new IP address of the printer (if it changed from what it was before).
That will ensure that the DHCP server in the HH5 doesn't lease the same IP to another device. This will also allow you to see the printer in the list of devices.

IOS6 and Appletv 5.1 wifi working as 802.11g instead 802.11n

Both upgrades are making my devices to operate as 802.11g instead 802.11n, at my home wifi connections.
The devices which I haven't updated are still working as 802.11n.
This could be another issue in the new upgrades. I hope that a possible iOS6.0.1 fix that up!
Thanks everyone
Chris

Is anyone having the same problem?

Extremely basic 802.11n questions

I just replaced an older AirPort hub with a Time Capsule, and I'm puzzled about the status of 802.11n networking.
I only connect wirelessly to the Time Capsule with two core2duo machines (a MacBook and a MacBook Pro). The one older machine in the house with a pre-extreme AirPort card, a G5 iMac, is connected directly via ethernet. I had been under the impression that the MacBooks needed to be enabled for 802.11n use, but the Time Capsule disk does not appear to contain the 802.11n enabler (although this IS referenced in the opening ReadMe). Is there an enabler somewhere that I need to apply to these two machines? Is this automatically part of Leopard (as some things I've read have implied) or of something else? How can I determine that the machines really are enabled for 802.11n use?
And then, how do I determine whether the network is actually running at 802.11n speed (and range)? My understanding is that connecting any non-n device (presumably including my iPhone) to the network will cause it to revert to b/g; how do I determine that this has happened? And does it revert back to n immediately after the non-n device disconnects?
Thanks for any information, or for pointers to something more comprehensive on this than what I've found so far.

James A. Weston wrote:
I don't know how to test the so-called "speed" of a wireless network other than to use a stopwatch, but my understanding is that a mixed n/g/b network is only slowed down when a b or g client is actually using the network.
And one g client using the network would slow down n-client users but not all the way down to g speeds. In other words, the n network does not revert to a g network.
Assuming your understanding is correct, that answers the basic question I was asking. It also suggests that there's no reason for me to carefully turn off wireless networking on my iPhone whenever I'm home: it won't slow down network backups to Time Capsule unless I'm actually doing something significant on it.
Thanks.

Packet loss / pausing when using 802.11N (Intel 6300)

Hi,
Previously, I had posted a thread involving the Intel 6250, and lack of detection of N WiFi on that card. Some time later, I bit the bullet and got an Intel 6300 card off eBay. After receiving it today, I popped it into my Thinkpad X220, and it worked.... sort of. I can definitely see wireless N support, and can associate with my 2.4 GHz mixed-mode B/G/N network at 130 Mbps, and my 5 GHz N-only router at around 243 - 270 Mbps. However, right off the bat, it seems the number of "Tx Excessive Retries" in iwconfig climb up to several thousand within ~ 15 - 20 minutes of connecting. Also right off the bat, pings are rather inconsistent (typically at least 2 ms greater than when the card is forced to work in G-only mode, and with pauses and spikes up to 800 - 2000 ms, and packet loss from 5 - 10%)
From what I have gathered so far, there has been a bug in the iwlwifi kernel tree that affects N wireless users, and this bug has been around since around 2010 or even earlier. However, I was under the impression that some sort of fix has been merged into the mainline Kernel at this point (I'm on 3.5.3-1-ARCH BTW), and my symptoms are somewhat less aggressive than the ones others described (basic web browsing works reasonably well, though there is often noticeable lag in the response times, but anything latency/packet loss-sensitive will suffer in a major way.) Has anyone managed to get wireless N to actually work reasonably well on Arch (or for that matter, ANY linux distro)? As I understand it, the matter is one of relation to the kernel module itself, so distro-distro variations of userspace apps shouldn't be as much a factor anyway. I am using WICD for my network manager, and am happy to say that it does its job admirably well (assuming the card is set to G-only mode, but the connection itself is actually maintained quite stably even in N mode.)
While I understand that the 11n_disable=1 "fix" allows most people to get on with their lives, I am rather alarmed that this is being considered a long-term solution. Many laptop owners (ThinkPad owners like myself for example) are essentially locked into Intel WiFi cards, unless we are willing to take an expensive risk and flash our BIOS to one that that doesn't have a "whitelist" of approved cards (something that can void the warranty or worse, brick a laptop.) All the while, Intel is still claiming Linux support for a card whose major capabilities are essentially neutered purely based on the OS a user chooses to run (yes, I do consider N to be a major capability, considering 300 Mbps N WiFi is basically old news, with many manufacturers coming out with full 450 Mbps routers. Also, chipsets like Atheros seem to have no problems with offering both performance and stability under Linux... my desktop rig using an Atheros card manages perfectly fine on a full-rate wireless-N network with essentially no packet loss or latency spikes.)
Below is some information that might be useful:
iwconfig (802.11g, ~ 1 hour after connection and running a few speedtests, browsing, ping testing):
wlan0 IEEE 802.11abg ESSID:"dd-wrt"
Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:359 Missed beacon:0
iwconfig (802.11n, 5GHz after ~10 minutes browsing/ping testing):
wlan0 IEEE 802.11abgn ESSID:"net2"
Mode:Managed Frequency:5.745 GHz Access Point: XXXXXX
Bit Rate=243 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=55/70 Signal level=-55 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:860 Invalid misc:50 Missed beacon:0
iwconfig (802.11n, 2.4 GHz after connecting and running a speedtest):
wlan0 IEEE 802.11abgn ESSID:"dd-wrt"
Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
Bit Rate=117 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:974 Invalid misc:59 Missed beacon:0
dmesg | grep iwl :
[12011.488089] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[12011.488092] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
[12011.488269] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[12011.488271] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050f8000
[12011.488273] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
[12011.488585] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
[12011.491862] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
[12011.492112] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[12011.492114] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[12011.492116] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[12011.492117] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
[12011.492119] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
[12011.492121] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[12011.492206] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12011.502925] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[12011.502928] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
[12011.502930] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
[12011.502946] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[12011.503105] ieee80211 phy8: Selected rate control algorithm 'iwl-agn-rs'
[12011.503456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12011.503661] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12011.745631] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12011.745868] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12073.651471] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[12073.651474] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
[12073.651660] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[12073.651661] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050b8000
[12073.651663] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
[12073.652241] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
[12073.655662] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
[12073.655887] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[12073.655890] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
[12073.655892] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
[12073.655894] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[12073.655975] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12073.666587] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[12073.666593] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
[12073.666595] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
[12073.666618] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[12073.667056] ieee80211 phy9: Selected rate control algorithm 'iwl-agn-rs'
[12073.667456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12073.667659] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12073.908411] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12073.908632] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.261869] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.262090] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.487757] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.488010] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.699574] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.699781] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12087.837322] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12087.837526] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12097.329577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12097.329832] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12097.797748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12097.797970] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12098.016220] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12098.016458] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.458762] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.459006] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.608769] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.609021] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.764093] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.764341] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12100.979029] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12100.979228] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[12101.159987] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[12101.160208] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
lshw | less :
*-network
description: Wireless interface
product: Centrino Ultimate-N 6300
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 35
serial: 00:24:d7:be:9e:74
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet phy
sical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.5.3-
1-ARCH firmware=9.221.4.1 build 25532 ip=192.168.1.145 latency=0 link=yes multic
ast=yes wireless=IEEE 802.11abgn
resources: irq:50 memory:f2500000-f2501fff
Thanks,
- A.G.

I have an ASUS UX32VD-DB71 which has the Intel Centrino 6235 wifi card. I've been having this laptop for more than 6 months and I've tried different solutions to fix the issue with Wireless-N but none of them were stable other than disabling N completely using 11n_disable=1
I've tried different kernels all the way from 3.2 to the latest 3.7 series of kernels (both in the openSUSE tree as well as mainline) with no luck whasoever. I also tried installing the compat-drivers from 2013-01-23-1-u version onto my 3.6 kernel which provided the same results too. I see packet loss with N and the G speeds are just too slow. I have a workstation in my network and I can only transfer effectively at 1.5 MB /s max over G whereas an old laptop from 2007 which has an 1x1 MIMO antenna (again Intel though) can connect at 144 Mbps to my router and transfer files at least 3-4 times faster (if not more).
It is totally unacceptable for Intel to not just fix this issue for Linux.
Last edited by Tuxdude (2013-02-17 01:38:59)

Laserjet 1505 connected to AEB 802.11n via USB keeps timing out after print

I have a HP Laserjet 1505 connected on my AEB 802.11n via USB and shared on my network, on my network are two macs connected via wifi and 3 WinXP PC connected via wire. I have Bonjour and WinXP laserjet drivers installed on all Win PC. Everytime I print from any of the computers, it will print the first time, but when I try printing again from any of the machines, the macs and winxp pc's cannot detect the printer. When I go to airport utility, the printer cannot be detected anymore. I have to hard reset the AEB for it to detect the laserjet printer again. But the same thing happens again after I print out another document. Has anybody encountered this kind of problem. Can anyone help me resolve this?

Here is what I got from HP support :
The driver for the Laserjet P1006 is not available yet for Os 10.5...we are hoping it will be release in the next week or so...please click on the link below to sign up for an email update as soon as it is available..As a workaround, some people have been able to use the 10.4 driver from the cd, but this is not guaranteed to work in all applications therefore the only solution is to wait and install the 10.5 driver.
So we wait.
Yves

Vista + 802.11n PCMCIA + AEBS Giga = 300Mbps connection

Similar Messages

Maybe you are looking for