Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Wireless Card on Compaq Evo n800c
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Schnacki
Tux's lil' helper
Tux's lil' helper


Joined: 19 Feb 2003
Posts: 105

PostPosted: Sat Aug 21, 2004 10:37 pm    Post subject: Reply with quote

Thanks to the tips by "otaci" I just got my W200 loading, too. Can't test it right now, but at least the LED is on now.

To sum up his steps:


  • IMPORTANT:

    • go to the directory where your running kernel-sources are installed (/usr/src/linux for me)
    • Run "make menuconfig".
    • Go to "Device Drivers --->".
    • Go to "Generic Driver Options --->".
    • Add "Select only drivers that don't need compile-time external firmware".
    • Add "Hotplug firmware loading support" (either as module or compiled in).
    • Save your kernel-config.
    • Compile and install your kernel. For this I mount "/boot", run
      Code:
      Make all modules_install install

      and make sure I have sections for the new and old symlinks (added by make install) in my grub.conf.
    • reboot!!!

  • download the orinoco from cvs from http://savannah.nongnu.org/projects/orinoco/
  • change into the new directory
  • run make
  • copy the ".ko"-files to your kernel-directory ("/lib/modules/2.6.8-gentoo/kernel/drivers/net/wireless/" in my case)
  • go to http://orinoco-usb.alioth.debian.org/ to download the old "orinoco-usb" drivers version 0.2.2. You can find them directly at http://alioth.debian.org/download.php/356/orinoco-usb-0.2.2.tar.bz2
  • unpack the file and change into the new directory
  • you'll find several subdirectories
  • change into the "firmware"-directory
  • run "make" (you _need_ webaccess for this)
  • create the directory "/usr/lib/hotplug/firmware" (if it's not present already)
  • run "cp orinoco_ezusb_fw /usr/lib/hotplug/firmware/"
  • activate the W200 by pressing Fn-F2 until the LED turns on (wait a few seconds after each press, the driver needs a moment)

Now the WLAN-card is running. Try to figure out how to configure it yourself. ;) I still have to do that myself.

I really think this could/should be a HowTo. Took me quite a while to find this thread.

[edit] added info to compile the kernel correctly[/edit]


Last edited by Schnacki on Mon Aug 23, 2004 5:37 am; edited 1 time in total
Back to top
View user's profile Send private message
spazegun
n00b
n00b


Joined: 23 Sep 2003
Posts: 31

PostPosted: Mon Aug 23, 2004 4:44 am    Post subject: Reply with quote

I also have an Evo with the orinoco wireless card. I tried all of the downloading and installing, and this still happens

Code:

Aug 23 00:42:14 mobile atkbd.c: Use 'setkeycodes e078 <keycode>' to make it known.
Aug 23 00:42:14 mobile ohci_hcd 0000:02:0e.0: wakeup
Aug 23 00:42:15 mobile usb 2-3: new full speed USB device using address 4
Aug 23 00:42:15 mobile usb 2-3: config 1 has an invalid interface number: 1 but max is 0
Aug 23 00:42:15 mobile usb 2-3: config 1 has no interface number 0
Aug 23 00:42:15 mobile prism_usb_hard_reset - dummy
Aug 23 00:42:15 mobile prism_usb_init - dummy
Aug 23 00:42:15 mobile prism_usb_init - dummy
Aug 23 00:42:15 mobile prism_usb_allocate - dummy
Aug 23 00:42:15 mobile prism_usb_read_ltv - dummy
Aug 23 00:42:15 mobile eth1: Cannot read hardware identity: error -95
Aug 23 00:42:15 mobile eth1: Incompatible firmware, aborting
Aug 23 00:42:15 mobile prism_usb: Cannot register network device
Aug 23 00:42:15 mobile prism_usb: probe of 2-3:1.1 failed with error -95


I have the ezusb in the /usr/lib/hotplug/firmware

thanks
Back to top
View user's profile Send private message
Schnacki
Tux's lil' helper
Tux's lil' helper


Joined: 19 Feb 2003
Posts: 105

PostPosted: Mon Aug 23, 2004 5:28 am    Post subject: Reply with quote

Hi

spazegun wrote:
I also have an Evo with the orinoco wireless card. I tried all of the downloading and installing, and this still happens

Code:

[...]
Aug 23 00:42:15 mobile prism_usb_hard_reset - dummy
Aug 23 00:42:15 mobile prism_usb_init - dummy
Aug 23 00:42:15 mobile prism_usb_init - dummy
[...]


I have the ezusb in the /usr/lib/hotplug/firmware


Ok, the first (and maybe only) Problem is, that you do not run "orinoco_usb" but "prism_usb". That's the wrong driver.

Did you compile the Kernel with Firmware-loading and USB support? Without it, the Makefile just skips the orinoco_usb. And in the "non-cvs"-Version of orionoco it's not even included.

This is what I get when plugging it in:

Code:

orinoco 0.15rc2HEAD (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
orinoco_usb 0.15rc2HEAD (Manuel Estrada Sainz <ranty@debian.org>)
eth1: Hardware identity 0008:0003:0001:0000
eth1: Station identity  001f:0001:0008:003a
eth1: Firmware determined as Lucent/Agere 8.58
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
[...]


Ciao, Jan
Back to top
View user's profile Send private message
spazegun
n00b
n00b


Joined: 23 Sep 2003
Posts: 31

PostPosted: Tue Aug 24, 2004 1:41 am    Post subject: Reply with quote

Code:


bash-2.05b# lsmod
Module                  Size  Used by
prism_usb               9344  0
orinoco                52496  1 prism_usb


here is what happens when i hit fn-f2

Code:

Aug 23 21:38:17 mobile ohci_hcd 0000:02:0e.0: wakeup
Aug 23 21:38:17 mobile usb 2-3: new full speed USB device using address 4
Aug 23 21:38:17 mobile usb 2-3: config 1 has an invalid interface number: 1 but max is 0
Aug 23 21:38:17 mobile usb 2-3: config 1 has no interface number 0
Aug 23 21:38:17 mobile prism_usb_hard_reset - dummy
Aug 23 21:38:17 mobile prism_usb_init - dummy
Aug 23 21:38:17 mobile prism_usb_init - dummy
Aug 23 21:38:17 mobile prism_usb_allocate - dummy
Aug 23 21:38:17 mobile prism_usb_read_ltv - dummy
Aug 23 21:38:17 mobile eth1: Cannot read hardware identity: error -95
Aug 23 21:38:17 mobile eth1: Incompatible firmware, aborting
Aug 23 21:38:17 mobile prism_usb: Cannot register network device
Aug 23 21:38:17 mobile prism_usb: probe of 2-3:1.1 failed with error -95


i do load the prism_usb module... but still it errors

and where is firmware-loading? I have usb support and hotplug all going, but i cant seem to find firmware-loading.
Back to top
View user's profile Send private message
spazegun
n00b
n00b


Joined: 23 Sep 2003
Posts: 31

PostPosted: Tue Aug 24, 2004 3:23 am    Post subject: Reply with quote

ok, i enabled all the kernel options that were in the former posts. And i still have the same problem. Also when i make the orinoco module, they are fine. If i reboot, the prism_usb.ko is gone. I have to remake it.

thanks
Back to top
View user's profile Send private message
Schnacki
Tux's lil' helper
Tux's lil' helper


Joined: 19 Feb 2003
Posts: 105

PostPosted: Tue Aug 24, 2004 8:55 am    Post subject: Reply with quote

Hi

spazegun wrote:
ok, i enabled all the kernel options that were in the former posts. And i still have the same problem. Also when i make the orinoco module, they are fine. If i reboot, the prism_usb.ko is gone. I have to remake it.


You misunderstood me:

You do NOT need "prism_usb".

You DO need "orinoco_usb". I have no idea, why your computer tries to load prism_usb, mine does not. But maybe it only does if "orinoco_usb" is not present.
Back to top
View user's profile Send private message
spazegun
n00b
n00b


Joined: 23 Sep 2003
Posts: 31

PostPosted: Tue Aug 24, 2004 12:30 pm    Post subject: Reply with quote

well, i though i had the prism chipset because mine says wireless lan on the side and not W200. Also Even if both modules are loaded, (or either one for that matter) i still get that incompatable firmware error.
Back to top
View user's profile Send private message
Schnacki
Tux's lil' helper
Tux's lil' helper


Joined: 19 Feb 2003
Posts: 105

PostPosted: Tue Aug 24, 2004 12:35 pm    Post subject: Reply with quote

spazegun wrote:
well, i though i had the prism chipset because mine says wireless lan on the side and not W200.


Oh, sorry, I didn't get that from your postings. Then I don't have any idea where to look for the error.
Back to top
View user's profile Send private message
daktak
Tux's lil' helper
Tux's lil' helper


Joined: 18 Oct 2002
Posts: 142
Location: Melbourne, Victoria

PostPosted: Wed Jan 05, 2005 9:22 am    Post subject: Reply with quote

I had heaps of troubles till i realised that /usr/lib/hotplug/firware is now /lib/firmware!
Back to top
View user's profile Send private message
greatguru
n00b
n00b


Joined: 01 Apr 2003
Posts: 6

PostPosted: Thu Jan 20, 2005 2:28 pm    Post subject: Thanks for the help! Reply with quote

Thanks to the steps outlined by Schnacki (and by extension otaci), I just got mine working. I have a Compaq Evo N610c with the W200 and its working fabulously. However, a note: I followed the steps outlined above, but when I would turn on the card (with Fn-F2), in dmesg it would say:

usb 2-3: new high speed USB device using ohci_hcd and address 2
usb 2-3: khubd timed out on ep0in
usb 2-3: device descriptor read/64, error -110

I tried a few things without luck, including switching the firmware loader to /lib/firmware as the poster above me pointed out. This had no effect. I then rebooted my laptop and added 'acpi=off' to the kernel params and loaded it up. Then, when I hit Fn-F2, it started up correctly, putting in an interface eth1!!

I was excited because I had hence narrowed this down to a acpi problem, but upon rebooting normally (with acpi enabled), it worked again! It's been working fine since, even after a few reboots, so that might have just done the trick...

On a side note, for anyone considering this laptop or who owns one, the overheating problems are horrendous. Booting with acpi=off is especially dangerous as this laptop doesn't know how to turn the fan on unless you update the DSDT (which is another project I've recently completed, see a post on these forums about common acpi problems). I have got this laptop in July of '03 to start college with, and I have sent it in twice to be repaired since then, which I believe has been directly related to overheating issues (both times they replaced the main board under warranty). Just a note...

Good luck to the rest of you! If you have any questions, email me b/c I don't check these forums much unless I'm looking for help...

bmschell_AT_benschell.dyndns.org
Back to top
View user's profile Send private message
rdcapasso
n00b
n00b


Joined: 13 Mar 2005
Posts: 3
Location: Madison, WI

PostPosted: Tue Mar 15, 2005 1:59 am    Post subject: Reply with quote

I have a Compaq N600c and I am having the same problem that spazegum is having :(. orinoco_usb loads fine on boot but tail shows this in /var/log/messages when I hit fn-f2:

Code:
Mar 15 01:54:50 ed209 usb 3-2: new full speed USB device using uhci_hcd and address 6
Mar 15 01:54:50 ed209 usb 3-2: config 1 has an invalid interface number: 1 but max is 0
Mar 15 01:54:50 ed209 usb 3-2: config 1 has no interface number 0
Mar 15 01:54:50 ed209 prism_usb_hard_reset - dummy
Mar 15 01:54:50 ed209 prism_usb_init - dummy
Mar 15 01:54:50 ed209 prism_usb_init - dummy
Mar 15 01:54:50 ed209 prism_usb_allocate - dummy
Mar 15 01:54:50 ed209 prism_usb_read_ltv - dummy
Mar 15 01:54:50 ed209 eth1: Cannot read hardware identity: error -95
Mar 15 01:54:50 ed209 eth1: Incompatible firmware, aborting
Mar 15 01:54:50 ed209 prism_usb: Cannot register network device
Mar 15 01:54:50 ed209 prism_usb: probe of 3-2:1.1 failed with error -95


I'm guessing that there must be a firmware file for the prism_usb that's missing. My multiport adapter says 'Wireless LAN' on the side, as well.
Back to top
View user's profile Send private message
vtowel
n00b
n00b


Joined: 28 Jun 2002
Posts: 22
Location: Ontario, Canada

PostPosted: Wed Mar 16, 2005 7:36 pm    Post subject: Reply with quote

I also have a Compaq N600c, and this behaviour is exactly the same here. So I'm led to believe that our card is NOT a W200 card. When I do "lsusb" with the card activated, the device is listed as:

Code:
Bus 003 Device 012: ID 049f:0033 Compaq Computer Corp. 801.11b Adapter [orinoco]


Notice that the product ID is 0033. According to Oystein Olsen's orinoco-usb page, the product ID of the HP/Compaq W200 is 0076. So we N600c folks must be dealing with a different wireless card altogether.

But since "lsusb" states "orinoco", you'd think that the orinoco drivers would still work with our card, right? Maybe they orinoco developers just haven't gotten around to supporting it/recognizing the firmware... :?:
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent

PostPosted: Wed Mar 16, 2005 9:04 pm    Post subject: Reply with quote

vtowel wrote:
I also have a Compaq N600c, and this behaviour is exactly the same here. So I'm led to believe that our card is NOT a W200 card. When I do "lsusb" with the card activated, the device is listed as:

Code:
Bus 003 Device 012: ID 049f:0033 Compaq Computer Corp. 801.11b Adapter [orinoco]


Notice that the product ID is 0033. According to Oystein Olsen's orinoco-usb page, the product ID of the HP/Compaq W200 is 0076. So we N600c folks must be dealing with a different wireless card altogether.

But since "lsusb" states "orinoco", you'd think that the orinoco drivers would still work with our card, right? Maybe they orinoco developers just haven't gotten around to supporting it/recognizing the firmware... :?:

049f:0033 is a W100 card -- I was using this model before it broke, w/ the linux-wlan-ng drivers.
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Mon Nov 07, 2005 5:30 am    Post subject: Reply with quote

So, I'm not really sure if anyone is still working on this, but I was recently trying to get it to work with no luck. I have a N800c with a W200 card, but I'm not sure if it's the new or the old one. I'm 99% sure I have everything enabled in my kernel.

First off, I always get the following message in my dmesg when I hit FN-F2 (even before I tried to set up the wireless card):
Code:

usb 2-3: new full speed USB device using ohci_hcd and address 2
usb 2-3: config 1 has an invalid interface number: 1 but max is 0
usb 2-3: config 1 has no interface number 0

Anyway, don't know if that's important or not.

My lsusb output is:
Code:

Bus 003 Device 001: ID 0000:0000 
Bus 002 Device 002: ID 049f:0033 Compaq Computer Corp. 801.11b Adapter [orinoco]
Bus 002 Device 001: ID 0000:0000 
Bus 001 Device 001: ID 0000:0000 


I followed all of the steps is Schnacki's synopsis, and now when I try to FN-F2 to get the card up, I get various output on my dmesg from time to time. Once I got a kernel bug message and my system started acting really funny and I had to reboot. Currently, this is what I get:
Code:

usb 2-3: new full speed USB device using ohci_hcd and address 4
usb 2-3: config 1 has an invalid interface number: 1 but max is 0
usb 2-3: config 1 has no interface number 0
prism_usb_hard_reset - dummy
prism_usb_init - dummy
prism_usb_init - dummy
prism_usb_allocate - dummy
prism_usb_read_ltv - dummy
eth1: Cannot read hardware identity: error -95
eth1: Incompatible firmware, aborting
prism_usb: Cannot register network device
prism_usb: probe of 2-3:1.1 failed with error -95

No LED flashing, no wlan0 device...

So at this point I tried to modprobe orinoco_usb, and I got this on my dmesg:
Code:

orinoco_usb: Unknown symbol release_firmware
orinoco_usb: Unknown symbol request_firmware
orinoco_usb: Unknown symbol register_firmware

I do have the firmware file in /usr/lib/hotplug/firmware...

Anyway, it's a big mess, but thought I'd just contribute my problems and see if anyone can help me or maybe my issues can help someone else.

laters,
appleshampoo
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Mon Nov 07, 2005 5:55 am    Post subject: Reply with quote

So, I'm a retard and was using the wrong kernel (the un-configured one) when I posted that last post, hence why all the error messages were different than how I remembered them. Here's what happens on my dmesg when I'm using the right kernel and hit Fn-F2:
Code:

kobject_register failed for orinoco (-17)
 [<c01f5349>] kobject_register+0x49/0x80
 [<c012e2c1>] mod_sysfs_setup+0x51/0xc0
 [<c012f3e1>] load_module+0x7a1/0xa70
 [<c012f74a>] sys_init_module+0x6a/0x1f0
 [<c0102c25>] syscall_call+0x7/0xb
prism_usb 0.15rc2HEAD (Pavel Roskin <proski@gnu.org>)
prism_usb_hard_reset - dummy
prism_usb_init - dummy
------------[ cut here ]------------
kernel BUG at lib/iomap.c:85!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: prism_usb parport_pc lp
CPU:    0
EIP:    0060:[<c01fa634>]    Not tainted VLI
EFLAGS: 00010287   (2.6.12-gentoo-r6)
EIP is at iowrite16+0x24/0x40
eax: 00000000   ebx: 00000064   ecx: 00000000   edx: 00000032
esi: 00000001   edi: cba51ae8   ebp: cba51800   esp: ca081dfc
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 7026, threadinfo=ca080000 task=cf2160a0)
Stack: c02a2d1b c0139090 c114fee0 00000000 cba51a20 00000001 cba51800 cba51800
       c029fa41 cba51ae8 0000000a ca081ea3 00000002 ca081eaf c01f87f6 ca081ea3
       ca081eaf 00000001 cba51ae8 0000000a ffffffff 00000000 00000002 ca080000
Call Trace:
 [<c02a2d1b>] hermes_init+0x2b/0x1d0
 [<c0139090>] prep_new_page+0x60/0x70
 [<c029fa41>] orinoco_init+0x31/0x670
 [<c01f87f6>] vsnprintf+0x256/0x4d0
 [<c0110af7>] __wake_up_locked+0x27/0x30
 [<c034262b>] register_netdevice+0x5b/0x320
 [<c029cf60>] orinoco_stop+0x0/0x60
 [<c0342947>] register_netdev+0x57/0x90
 [<d086b568>] prism_usb_probe+0x2d8/0x3e0 [prism_usb]
 [<c02d2200>] usb_probe_interface+0x70/0x90
 [<c027470f>] driver_probe_device+0x2f/0x80
 [<c027485c>] driver_attach+0x5c/0xa0
 [<c0274dcd>] bus_add_driver+0x9d/0xd0
 [<c02d22fc>] usb_register+0x4c/0xb0
 [<c01144c7>] printk+0x17/0x20
 [<d086e028>] prism_usb_module_init+0x28/0x4c [prism_usb]
 [<c012f828>] sys_init_module+0x148/0x1f0
 [<c0102c25>] syscall_call+0x7/0xb
Code: 8d bc 27 00 00 00 00 81 fa ff ff 03 00 0f b7 c8 77 25 89 d0 25 00 00 ff ff 3d 00 00 01 00 75 0b 81 e2
ff ff 00 00 89 c8 66 ef c3 <0f> 0b 55 00 cd d0 3b c0 eb eb 89 f6 66 89 0a c3 8d b6 00 00 00

So, yeah, who really knows what's going on there...
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent

PostPosted: Mon Nov 07, 2005 7:00 am    Post subject: Reply with quote

I'm not sure about your particular bug, but I can confirm that the latest CVS orinoco_usb code works well with vanilla kernel 2.6.13 for W200.
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Mon Nov 07, 2005 8:11 am    Post subject: Reply with quote

Hmmm...so that's just emerge vanilla-sources and the configure the kernel like usual, right? I might have to try that.
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Tue Nov 08, 2005 5:38 am    Post subject: Reply with quote

I tried the 2.6.12.5 and the 2.6.13 vanilla kernels. I didn't get the kernel error from above, but it still didn't work. dmesg after Fn-F2:
Code:

usb 2-3: new full speed USB device using ohci_hcd and address 3
usb 2-3: config 1 has an invalid interface number: 1 but max is 0
usb 2-3: config 1 has no interface number 0
prism_usb_hard_reset - dummy
prism_usb_init - dummy
prism_usb_init - dummy
prism_usb_allocate - dummy
prism_usb_read_ltv - dummy
eth1: Cannot read hardware identity: error -95
eth1: Incompatible firmware, aborting
prism_usb: Cannot register network device
prism_usb: probe of 2-3:1.1 failed with error -95

It doesn't seem that orincoro_usb is being loaded automatically. I did a modprobe orinoco_usb and got this on dmesg:
Code:

usbcore: registered new driver prism_usb
orinoco_usb 0.15rc2HEAD (Manuel Estrada Sainz)
usbcore: registered new driver orinoco_usb

which doesn't look too bad, but still no LED or wlan0 device. I think I'm going to give up on this for a while.
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent

PostPosted: Tue Nov 08, 2005 5:44 am    Post subject: Reply with quote

The device ID for my USB W200 is 049f:0076

What's yours? (Use "lsusb")
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Tue Nov 08, 2005 5:57 am    Post subject: Reply with quote

lsusb output:
Code:

Bus 003 Device 001: ID 0000:0000 
Bus 002 Device 004: ID 049f:0033 Compaq Computer Corp. 801.11b Adapter [orinoco]
Bus 002 Device 001: ID 0000:0000 
Bus 001 Device 001: ID 0000:0000 


Also, I think I figured out why I was getting the kernel error above. In my kernel config Device Drivers--->Networking Support---->Wireless LAN----> I was enabling "Hermes Chipset 802.11b support (Orinoco/Prism2/Symbol)" and also the three options under it, which I'm pretty sure you don't need with the external orinoco modules. After disabling these, I get the same output as above (2.6.13 vanilla) with the 2.6.12-gentoo-r6 kernel.
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent

PostPosted: Tue Nov 08, 2005 6:01 am    Post subject: Reply with quote

I think you have a W100. I could only get my old 0033 to work using linux-wlan-ng; orinoco is for Prism 2.x chipsets, such as in the W200.
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Tue Nov 08, 2005 6:31 am    Post subject: Reply with quote

Hypnos wrote:
I think you have a W100. I could only get my old 0033 to work using linux-wlan-ng; orinoco is for Prism 2.x chipsets, such as in the W200.

That's entirely possible, there were 2 versions of the card that went out with my class's laptots. The writing on the side has since rubbed off though, so I can't tell that way. So you actually got your W100 to work with linux-wlan-ng? Is there a HOWTO out there for that method? I see the package in portage, but I'm guessing it's a little more complicated than that.


Last edited by appleshampoo on Tue Nov 08, 2005 6:43 am; edited 1 time in total
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2889
Location: Omnipresent

PostPosted: Tue Nov 08, 2005 6:39 am    Post subject: Reply with quote

The version in Portage is a recent release, and should Just Work (tm). Play it by ear, I guess ...
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Tue Nov 08, 2005 6:49 am    Post subject: Reply with quote

Hypnos wrote:
The version in Portage is a recent release, and should Just Work (tm). Play it by ear, I guess ...

Trying to emerge linux-wlan-ng-0.2.0 gave me an error during the merge that it wouldn't work with 2.6 kernel and that I needed to use >=linux-wlan-ng-0.2.1_pre17, which required me to add ~x86 for net-wireless/linux-wlan-ng, net-wireless/linux-wlan-ng-modules, net-wireless/linux-wlan-ng-utils, and net-wireless/linux-wlan-ng-firmware. Lol, I wish I could post a vidcap of me during this process it went something like this:

Me: {after adding linux-wlan-ng ~x86 to package.keywords} emerge -av linux-wlan-ng
Portage: linux-wlan-ng-modules is still masked, failed dependency
Me: {add linux-wlan-ng-modules ~x86 to package.keywords} emerge -av linux-wlan-ng
Portage: linux-wlan-ng-utils is still maksed, failed dependency
Me: {add linux-wlan-ng-utils ~x86 to package.keywords} emerge -av linux-wlan-ng
Portage: linux-wlan-ng-firmware is still maksed, failed dependency
Me: {add linux-wlan-ng-firmware ~x86 to package.keywords} emerge -av linux-wlan-ng
Protage: Okay, I've made you jump through enough hoops, I guess I'll go ahead and merge them all now...
Back to top
View user's profile Send private message
appleshampoo
Tux's lil' helper
Tux's lil' helper


Joined: 26 Sep 2004
Posts: 116

PostPosted: Tue Nov 08, 2005 7:16 am    Post subject: Reply with quote

Hokay, so after all the BS above, it seems I am getting somewhere. Now when I toggle the wireless with Fn-F2, I see a "wlan0" device that appears in the output of iwconfig. I really have no idea where I'm going from here, so if anyone has any pointers, it would be much appreciated. Right now if I try to do /etc/init.d/wlan, I get some errors:
Code:
root@hashbrown-lappy /home/appleshampoo # /etc/init.d/wlan start
 * Starting WLAN devices ...
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.12-gentoo-r6/misc/ndiswrapper.ko): Operation not permitted
message=lnxreq_ifstate
  ifstate=fwload
  resultcode=implementation_failure
prism2dl: No such device
load_cardpda failed, exiting.
Unknown prism2 hardware type  (), assuming SSF
Processing PDR file: /tmp/prism2_ssf.pda
prism2dl: No such device
Couldn't fetch PRI-SUP info
Warning: RAM load only, PDA changes will NOT be written to flash.
Reading S-record file /lib/firmware/prism2_pm.hex...
NIC ID: 0 v0.0.0
MFI ID: 0 v0 0->0
CFI ID: 0 v0 0->0
PRI ID: 0 v0 0->0
Version:  ID 0x15 1.1.2
Compat: Role 0 Id 0x3 v2 4->4
Compat: Role 0x1 Id 0x2 v2 1->1
Seq: 0
Platform:  ID 0x800e 1.0.0
Platform:  ID 0x8015 1.0.0
Platform:  ID 0x8019 1.0.0
Platform:  ID 0x801d 1.0.0
Platform:  ID 0x8024 1.0.0
prism2dl: warning: Failed to find PDR for plugrec 0x0003.
prism2dl: warning: Failed to find PDR for plugrec 0x0005.
prism2dl: warning: Failed to find PDR for plugrec 0x0006.
prism2dl: warning: Failed to find PDR for plugrec 0x0007.
prism2dl: warning: Failed to find PDR for plugrec 0x0008.
prism2dl: warning: Failed to find PDR for plugrec 0x0402.
prism2dl: warning: Failed to find PDR for plugrec 0x0403.
prism2dl: warning: Failed to find PDR for plugrec 0x0404.
prism2dl: warning: Failed to find PDR for plugrec 0x0408.
prism2dl: warning: Failed to find PDR for plugrec 0x0001.
prism2dl: No such device
prism2dl: writeimage()->do_ioctl() failed w/ result=19, aborting download
prism2dl: Failed to ramwrite image data for /lib/firmware/prism2_pm.hex, exiting.
prism2dl: No such device
load_cardpda failed, exiting.
Firmware failed to load for device wlan0
wlanctl-ng: No such device
error: Autojoin indicated failure!                                                        [ ok ]


Does ndiswrapper play a role in all of this? I do have it emerged, but don't really know what I'm supposed to do with it.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 4 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum