LinuxAnswers DiscussionThis forum is to discuss articles posted to LinuxAnswers.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[root@localhost dpiepgrass]# /etc/init.d/wlan start
Starting WLAN Devices: FATAL: Error inserting prism2_usb (/lib/modules/2.6.5-1.358/linux-wlan-ng/prism2_usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
[root@localhost dpiepgrass]# [ OK ]
What's dmesg? Anyway, I figured I'd reboot to see if the init procedure would happen on startup. During bootup, a different error message came out, which was approximately:
usb_prism2 device wlan0 does not seem to be present. Delaying initialization.
That's IIRC. Is there a bootup log file with this message in it (and hopefully more information)?
Well, that didn't fix it (but I haven't rebooted yet)
I looked through dmesg's output and found
usb 1-1: new full speed USB device using address 2
prism2_usb: Unknown symbol usb_kill_urb
The latter message,
prism2_usb: Unknown symbol usb_kill_urb
appears several times in the file, but only once adjacent to that usb1-1 message, which seems to indicate the device is recognized (there is only one usb device attached, and that is the wireless thingie)
well, you got me there, I would guess a usb option you need is not compile dinto your kernel, but if it compiled the driver it should be.... if it still fails after a reboot then I am not sure where to go from there, it is at that point that I would recompile my kernel, something you would want to go find a detailed tutorial for.
dmesg only contains kernel messages, not system messages, so most of what you see on boot will nto be shown, only driver related stuff.
depmod will resolve module dependancies put them int here place, and while I am not clear exactly what the inner workings and preccesses are I do know this: it makes new modules usable :-D
I was wondering if anybody could help me here. I have a Netgear MA111 USB Card, and I just got Linux on the computer I use it on.
I would really like internet on it... but I have no idea how to use Linux to build these drivers, and I have SuSE, not RedHat...
so if somebody would please help me, I would appreciate it. Even just pointing me to a tutorial or something. In the mean time, I guess I'll just keep looking around.
I am trying to use a Netgear MA111 on a Linux machine. I have a link for the driver (I assume get the latest one).
I am told I have to have the source code for my Linux. I am hazy as to where to get that. I downloaded Red Hat 9 from linuxiso org.
I got Version: 9 (shrike) Release: 2003-04-07
Does linuxiso have the source? I can't see it, but maybe I am not looking for the right thing.
I just went through all this setup, config, etc. Apparently,
Netgear changed the chipset used in MA111, but didn't
change the product name or id. If your MA111 box has
a tiny little "v2" on the side, then you probably have the
new chipset, and the standard MA111 (v1) drivers will
not recognize the device. I'm returning mine to the
store now.
Originally posted by Qwertie But if they put it in, and I don't need it, but they offered no explanation about it, then where would I be? I would be in a state of confusion, of course, as you can see.
I'm using Fedora which is one of the 3 redhat distros the author said he was using.
Thanks, I'll try that.
But, er, what programs? By the way, I see neither prism2_usb nor wlan0 in /dev. Will one of those automatically appear in /dev when the driver starts working? Should there be a file in /dev representing the device before the device driver starts working?
I have Red Hat 9
I got through compiling and installing, the only problem i ran into when I booted up and it tried to load my device it said it was unexistant..... http://www.linuxquestions.org/questi...ighlight=ma111
I am with u this is very frustrating I bought SUSE 9.2 and everything went fine except that I cant get the netgear ma111 to work the howto does not work past the make config source kernel step "Linux source directory" it automaticlly finds it but then says it is not complete or missing, this has stoped me now for 1 week so far it has taken me 3 weeks to just try to get this ma111 working this situation is not good, if I ever figure it out I will make a howto that is complete that is every step will be explained nothing assumed for us newbies. Any help please at all coz i need to get on with my life.
What version of gcc are you guys using? I've 3.3 and kernel 2.6.10 and I can't get a mac address on my adapter. I also get all kinds of warnings compiling with 3.3. Code version 0.2.1pre25.
lnxreq_hostWEPEncrypt=true # true|false
lnxreq_hostWEPDecrypt=true # true|false
dot11PrivacyInvoked=true # true|false
dot11WEPDefaultKeyID=0 # 0|1|2|3
dot11ExcludeUnencrypted=true # true|false, in AP this means WEP is required.
dot11WEPDefaultKey0=52:62:66:47:15
IS_ADHOC=n
AuthType="opensystem"
The rest are basically the default values.
Couldn't find /etc/modprobe.conf, so I put "alias wlan0 prism2_usb" in /etc/modules.conf
Here are some of the commands I tried.
Code:
collin@debian:~$ sudo modprobe wlan0
collin@debian:~$ lsmod|grep wlan0
collin@debian:~$ sudo /etc/init.d/wlan start
Starting WLAN Devices:
collin@debian:~$
collin@debian:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:29:26:9B:E7
inet addr:192.168.2.39 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1075 errors:0 dropped:0 overruns:0 frame:0
TX packets:1131 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:523179 (510.9 KiB) TX bytes:176918 (172.7 KiB)
Interrupt:10 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6936 (6.7 KiB) TX bytes:6936 (6.7 KiB)
collin@debian:~$
collin@debian:~$ sudo /etc/init.d/networking restart
SIOCSIFFLAGS: No such device
Listening on LPF/wlan0/00:00:00:00:00:00
Sending on LPF/wlan0/00:00:00:00:00:00
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
I have also added the following to /etc/network/interfaces
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.