Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
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.
Originally posted by bostonben You probably get this because your kernel is built with CONFIG_MODVERSIONS, and the driver is not. This
build option adds a checksum to the end of every external symbol name in the kernel:
Google for "CONFIG_MODVERSIONS" to find out more about why this is done.
However, it really shouldn't matter to you, "insmod" will still load the driver. The "depmod" messages are annoying
(which is why I didn't install the driver into /lib/modules), but shouldn't affect the operation of the driver.
Hello bostonben:
Thanks a lot for your reply, and I tried again, then got
the following result, do you have any suggestion:
insmod -f rtl8180_24x.o
Warning: loading rtl8180_24x.o will taint the kernel: forced load
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
rtl8180_24x.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
# dmesg | tail -10
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
******** RTL8180 Wireless Lan Driver 2003-06-11 loaded********
rtl8180: No devices found, RTL8180 Wireless Lan Driver 2003-06-11 unregistered
******** RTL8180 Wireless Lan Driver 2003-06-11 loaded********
rtl8180: No devices found, RTL8180 Wireless Lan Driver 2003-06-11 unregistered
Whew, okay I fiddled with both drivers most of Monday, drank Tuesday, and decided to give it another go on Wednesday... what can I say, I'm a slacker, on the second day Finegan slacks off.
I've been staying relatively quiet until I had room to talk.
Now... I got this kid to work with the newest driver package, now the only one available direct from the realtek site, (well, two, I used the gcc 3.xx version). A few things...
priv_part.o is the binary library file for the driver, its actually incoporated into rtl8180_24x.o at the end of the make. It also comes precompiled for you, hence the different gcc stuff.
There is no need to insmod it seperately, if you take a look, its listed as "unused"
I never got anything out of the earlier versions on this laptop:
Make certain the kernel source path and your kernel version match, note to the guys running RH where you kernel source may be stock yet you've upgraded your kernel a few times with up2date... get the newer include headers... although this shouldn't matter, this driver does childish things (don't ever type the command: "more /proc/rtl8180/status" for instance, unless you like oopses )
make
insmod rtl8180_24x.o
ifconfig wlan0 up (voodoo step, probably unnecessary)
iwpriv wlan0 wlan_para wepmod=off
iwpriv wlan0 wlan_para networktype=infra
iwpriv wlan0 wlan_para ssid2scan=(some vulgar synonym for copulation)junk
iwpriv wlan0 enable
Wham, there's a scan in dmesg:
Code:
RTL8180: Select a BSS and Join it at channel 3.
RTL8180: ----------------------------------------------------------
RTL8180: wlan0 Link status:
RTL8180: Channel number = 3
RTL8180: beacon period = 100
RTL8180: BSSID = 0x00:0x03:0x2f:0x01:0xd6:0x97
RTL8180: SSID = (something lewd)junk
RTL8180: Capability = 0x01
RTL8180: AID = 0x03
RTL8180: Operational rate = 0x0F <bit 0~3 = 1~11 Mbps>
RTL8180: ----------------------------------------------------------
ifconfig, route, or dhcpcd or (for the Hatters), dhclient from there...
Originally posted by pijulius I have used Your script just i have changed the wep to OFF, but i get just blinking Link on the card, nothing works.
Hi Julius, did you also set authtype=opensystem ?
I disabled WEP on my network, only changed wepmode=off and I get similar behaviour. If I also change authtype=opensystem it works fine.
Originally posted by dannylin
...
rtl8180_24x.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
# dmesg | tail -10
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
******** RTL8180 Wireless Lan Driver 2003-06-11 loaded********
rtl8180: No devices found, RTL8180 Wireless Lan Driver 2003-06-11 unregistered
This means the driver can't find the card. Assuming it's actually plugged in, what do these commands show:
# /sbin/cardctl ident
# /sbin/lspci -v
They should at least show a Realtek network device.
Incidentally, I'm still running the older version (2003-5-22) of the driver, since the new one won't work for me: I get a "unable to handle kernel paging request" oops in one of the driver's internal functions when I "insmod" it. Sigh.
More interesting is the output of "#insmod -f rtl8180_24x.o" in /var/log/messages:
-----------------------
PCI: No IRQ known for interrupt pin A of device. Please try using pci=biosirq.
PCI: Setting latency timer of deviceto 64
unregistered_netdevice: device wlan%%d/cld2ec00 never registered
RTL8180: region #0 not a PIO resource, aborting
RTL8180: wlan driver load failed
rtl8180: No devices found, RTL8180 Werless Lan Driver Version 1.1 <2003-05-22> unregistered.
-------------------------
What is the dealy here - I'd really like to get past this part, since the rest seems dooable - however, im not a code guy and I really need help trying to find out what is going on with these scripts.
i have bought a pci card with the realtek chipset and i want to run it in my router, which runs under debian linux
i have the kernel version 2.4.18-bf2.4
so i changed this in Makefile, the other parameters i left untouched. it compiled without any special warnings, but when i run the insmod command "insmod -f rtl8180_24x.o" i get this:
Quote:
Warning: kernel-module version mismatch
rtl8180_24x.o was compiled for kernel version 2.4.19
while this kernel is version 2.4.18-bf2.4
rtl8180_24x.o: unresolved symbol __out_of_line_bug
in one of the first posts in the thread someone said he changed something, but what did u change???
sorry i am a little bit new to compiling, i hope u can help... thx.
edit: i have solved the kernel mismatch but i have still the rtl8180_24x.o: unresolved symbol __out_of_line_bug problem
Originally posted by halifax
-----------------------
PCI: No IRQ known for interrupt pin A of device. Please try using pci=biosirq.
PCI: Setting latency timer of deviceto 64
unregistered_netdevice: device wlan%%d/cld2ec00 never registered
RTL8180: region #0 not a PIO resource, aborting
RTL8180: wlan driver load failed
rtl8180: No devices found, RTL8180 Werless Lan Driver Version 1.1 <2003-05-22> unregistered.
-------------------------
There is no IRQ for the card, you have to add an append line to lilo or grub. In lilo its as simple as sticking this line somewhere near the top:
append="pci=biosirq"
if you have multiple ones in there, just stick them in the " " in order:
append="pci=biosirq hdd=ide-scsi" (for example)
Then re-run /sbin/lilo
For grub, its all in the kernel statement, for instance:
Code:
title Red Hat Linux (2.4.18-3)
root (hd0,1)
kernel /boot/vmlinuz-2.4.18-3 ro root=/dev/hda2 hdc=ide-scsi pci=biosirq
Don't worry about the wrong ident in pcmcia, its a cardbus card so it doesn't bother with ident up against /etc/pcmcia/config and the like, if hotplugging is enable and you run a depmod -a after copying the module into /lib/modules/2.4.XX/kernel/drivers/net/wireless (or anywhere in there really), hotplugging will load that module on a card hotload or at boot.
Side note, I had some issues last night with some oops'es until I played around with /etc/pcmcia/config and allowed for some more memory ranges... it first started when I hot-yanked the card. Anyone else had this behavior?
@finegan
if u meant me, it wasn't successfully, i get
----
# insmod -f rtl8180_24x.o
Warning: kernel-module version mismatch
rtl8180_24x.o was compiled for kernel version 2.4.20
while this kernel is version 2.4.18-bf2.4
rtl8180_24x.o: unresolved symbol __out_of_line_bug
---
when i change the kernel version in /usr/include/linux/version.h from 2.4.20 into 2.4.18-bf2.4 the kernel mismatch message disappears. but this f***** out of line bug still is there, i don't know where to search...
just for fun i tested the precompiled driver in the suse82 (knowing that i have debian) package from realtek, but there is the out of line bug too...
help would be great, otherwise i have to change my router from debian to windows, and i dont want to do that
Which source version of the driver are you using? 1.1 or 1.2?
You're changing the version number on the source header of the kernel? You're compiling against the wrong source tree for your running kernel... its going to continue to bug... you need the source tree for 2.4.18 patched with whatever the -bf2.4 patch is, and then you need to run a make dep in there. Or, just grab a vanilla 2.4.21, compile it from scratch, run that and compile the rtl module against it, but the wrong tree is just going to keep bugging.
@finegran
sorry for being a little bit like a newbie, but i never compiled anything before...
so the cause why i have this kernel is that a friend suggested it to me as i was installing it.
i downloaded the version with rh73 at the end (version 1.2, there is no other at the download page at the moment) because a gcc -v said that i am having 2.9 something
so i understand u right i have 2 possibilities:
i compile a new kernel to the system (why vanilla 2.4.21, described in a howto i have found a kernel version 2.5.0?)
or
i search the right source code for the kernel, throw it on the system, give the makefile the location of it and try again?
thx for ur help so far and sorry for bad english, i am from germany
The 2.5.x series is development, a lot of things are broken... the 2.4.x is the stable tree for us normal people.
Downloading and compiling a raw 2.4.21 may be a lot simpler then getting the 2.4.18 source, and finding that patch set that was applied to it, or it might not... I don't use Debian all that much... maybe its apt-gettable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.