9600gt works fine with envy ng -> install drivers manualy and select the newest driver
9600gt works fine with envy ng -> install drivers manualy and select the newest driver
Even on the 2.6.27-rc2? Tried it without luck, but maybe I did somehting wrong.
edit: The 9600m gt or the 9600 gt?
Last edited by KimOlsen; August 14th, 2008 at 01:29 PM.
Got it working with a patched 177.13 driver described in this thread. Patch is in post #23, but please read the entire thread.
So now I have an Intel Wifi Link 5100 and Nvidia 9600m gt working.
Last edited by KimOlsen; August 14th, 2008 at 03:08 PM. Reason: Added post # for the patch
KimOlsen, thanks for blazing a trail for Ubuntu users looking to use
the Intel 5100! Pardon the newbie question, but what steps were involved in using the 2.6.27-RC2 kernel with Ubuntu hardy? I ask because I'm about to get a new laptop with the Intel 5100 wireless and would like to put Ubuntu on it. I'm willing to compile a kernel, but haven't done it before. Many thanks for any pointers!
I've just bought a new Compal JHL90 (resold as PowerPro P 12:15 by powernotebooks.com), which comes with an Intel WiFi Link 5100AGN wireless adapter and an nvidia GeForce 9600M GT.
The video adapter worked with using the proprietary "nvidia" driver, which I had to set in the /etc/X11/xorg.conf. This was quick.
The WiFi Link 51000 is giving me more headaches. Anecdotal forum reports say that the 2.6.26 has out of the box support, but I would really like to use the Ubuntu Hardy 8.04 64 bit stock kernel.
I came across this post by Intel in which they announce native support for the 5100 adapter. Kernels >= 2.6.24 can use the new support via the compat-wireless project.
I've gotten a bit further, but I seem to be stuck at the rfkill problem that's been described elsewhere.
Here are the steps I took, to get from a totally unrecognized device to a recognized device under stock Ubuntu 8.04 without a new kernel compilation:
- Download compat-wireless from http://linuxwireless.org/download/co...ss-2.6.tar.bz2
- Untar somewhere (I'm choosing /usr/src/) and I'm doing everything as root from here on:Code:sudo su cd /usr/src tar xjf compat-wireless-2.6.tar.bz2 cd compat-wireless-2008-08-06
- Note, as of this writing (8/24/08), the most recent compat wireless package available was dated 8/6/08, but it does contain support for the 5100 card.
- Edit the config.mk file and add the following lines at the end to turn on support for the 5100 card and also for the rfkill switch:
- Download the firmware iwlwifi-5000-ucode-5.4.A.11.tar.gz
- Code:tar xzf iwlwifi-5000-ucode-5.4.A.11.tar.gz sudo cp iwlwifi-5000-1.ucode /lib/firmware/2.6.24-19-generic/
- This will add support for the 5100 card to the iwl4965 kernel module. This is probably temporary and from what I read the 2.6.26 kernels already have an iwl5000 module...Code:make make install make load
- Code:lshw -C network *-network DISABLED description: Wireless interface product: Intel Corporation vendor: Intel Corporation physical id: 0 bus info: pci@0000:0e:00.0 logical name: wmaster0 version: 00 serial: 00:16:ea:73:64:e0 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless configuration: broadcast=yes driver=iwl4965 latency=0 module=iwl4965 multicast=yes wireless=IEEE 802.11abgn *-network description: Ethernet interface product: RTL8111/8168B PCI Express Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:14:00.0 logical name: eth0 version: 02 serial: 00:1e:ec:55:88:02 size: 100MB/s capacity: 1GB/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=full ip=192.168.1.8 latency=0 link=yes module=r8169 multicast=yes port=twisted pair speed=100MB/s
- And this is where I get stuck. The wlan0 device is not enabled. I think this is related somehow to the hardware RF Kill switch (airplane switch) that disables wireless. This machine has a hardware switch and a software Fn+F2 option. Neither combination has worked for me. Toggling the hardware switch generates errors in the syslog:
Code:Aug 24 16:29:38 wta-mobile kernel: [ 1576.686265] atkbd.c: Unknown key pressed (translated set 2, code 0xf1 on isa0060/serio0). Aug 24 16:29:38 wta-mobile kernel: [ 1576.686275] atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
- This thread talks about the rfkill switch, but none of the suggestions have worked for me.
Any help with this is appreciated. I haven't tried compiling a 2.6.26 kernel yet, and I'd rather not if there are other options.
Last edited by wolframarnold; August 25th, 2008 at 12:40 AM.
Thank you so much wolframarnold!
Thanks to you ive got my wireless 5100 working with hardy!
Oke so I followed your steps.
Indeed after that the device was finally reconized.
But it was still disabled.
This was because it could not load the driver
So by simply copying iwlwifi-5000-1.ucode from /lib/firmware/2.6.24-19-generic/iwlwifi-5000-ucode-5.4.A.11/ to /lib/firmware and reloading the driver it finally worked!Code:Aug 25 21:43:06 slipie-vaio kernel: [ 342.149093] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Aug 25 21:43:06 slipie-vaio kernel: [ 342.149170] PM: Writing back config space on device 0000:05:00.0 at offset 1 (was 100002, writing 100006) Aug 25 21:43:06 slipie-vaio firmware_helper: main: error loading '/lib/firmware/iwlwifi-5000-1.ucode' for device '/devices/pci0000:00/0000:00:1c.2/0000:05:00.0/firmware/0000:05:00.0' with driver '(unknown)'
Thnx a lot!
Glad this worked for you, Slipie. I don't see the firmware load error in my syslog.
What I get is:
Why is the Network Manager deactivating the device???Code:Aug 25 14:25:22 wta-mobile kernel: [ 569.035589] iwl4965: START_ALIVE timeout after 4000ms. Aug 25 14:25:24 wta-mobile NetworkManager: <info> wlan0: Device is fully-supported using driver 'iwl4965'. Aug 25 14:25:24 wta-mobile NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Aug 25 14:25:24 wta-mobile NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Aug 25 14:25:24 wta-mobile NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Aug 25 14:25:24 wta-mobile NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'. Aug 25 14:25:24 wta-mobile NetworkManager: <info> Deactivating device wlan0. Aug 25 14:25:24 wta-mobile NetworkManager: <debug> [1219699524.444013] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/net_00_16_ea_73_64_e0_0'). Aug 25 14:25:25 wta-mobile kernel: [ 571.649370] ACPI: PCI Interrupt 0000:0e:00.0[A] -> GSI 18 (level, low) -> IRQ 18
wolframarnold: did you try without your cat5e plugged in?
I still can't get mine to work. Asus G50V. lshw -C network shows it as disabled every time I boot up, cat5e or not. What's interesting, though, is that it works just fine in single user mode.
Code:iwconfig wlan0 essid my-essid dhclient wlan0After that, I tried init 2. No go. Doesn't show disabled, so I guess that's a step in the right direction.Code:[ 46.535286] wlan0: authenticate with AP 00:1d:7e:39:##:## [ 46.537649] wlan0: authenticated [ 46.537649] wlan0: associate with AP 00:1d:7e:39:##:## [ 46.539833] wlan0: RX AssocResp from 00:1d:7e:39:##:## (capab=0x401 status=0 aid=4) [ 46.539833] wlan0: associated
Another thing I've noticed is that the LED turns on ~13 seconds (at which you would be in single), and turns off at 29 (some time during the last few messages before, or maybe even while KDM loads up). Any suggestions would be welcome.Code:[ 306.372128] iwl4965: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -5 [ 306.372108] iwl4965: Radio Frequency Kill Switch is On: [ 306.372108] Kill switch must be turned off for wireless networking to work.
Edit: when lshw does show disabled, then dmesg has a different message:
Edit 2: renaming everything 1 by 1 in /etc/rc2.d came up with the problem (for myself): S99acpi-support (renamed to K01acpi-support). There probably is a better way, but it works. For now.Code:[ 28.985671] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17 [ 28.985748] PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 100002, writing 100006) [ 28.985891] firmware: requesting iwlwifi-5000-1.ucode [ 30.871205] iwl4965: Radio disabled by HW RF Kill switch [ 30.871484] ACPI: PCI interrupt for device 0000:03:00.0 disabled
Last edited by Thalanix; August 26th, 2008 at 06:11 AM.
KernelCheck that automates most of the process. Remember to select Development under the "New Kernel Patch Options" to get the 2.6.27-rc4 (at the moment).
When the config gui starts. Remember to select the iwl options (think it is under device drivers -> wireless). Think it is at least iwlcore and iwl5000, will need to check when I get to my laptop later. And also, for sound it seems like most laptops need to check the alsa option and intel hd (even if not intel, because you get more choices when you select that).