What you have there is a source rpm. You do not really need to use that for your kernel.

Here is what you need...

kernel-2.4.20-8.rpm
kernel-source-2.4.20-8.rpm


To use a .src.rpm you have to build it with rpmbuild.The default folder where the build tales place is not writable to normal users by default. That's why you can't install any src.rpm file as a normal user.


The kernel-2.4.20-8.rpm will install the kernel, the kernel-source file will install the kernel source in /usr/src/linux-2.4.20-8

If your building the kernel from the source you do not really need the kernel-2.4.20-8.rpm file, you are going to build a custom kernel anyway. However it won't hurt to test the default kernel for problems.

Shouldn't that be kernel-source-2.4.20-8... ?

WMCrazyOne, are you installing the packages as root? That error msg sounds like you are trying without being root.

Yeah, its kernel 2.4.20-8... Sorry. And , yeah im set up as root. Also, I can only find , at rpmfind.net is 2.4.20-8.i686.rpm and kernel-source-2.4.20-8.i386.rpm and similar ones, like those. Not , just 2.4.20-8.rpm and kernel-source-2.4.20-8.rpm. Am I looking in the wrong place? Sorry , just want to make sure, I'm doing it the right way, and not messing up my box. Thanks , for all the help.

That's the right files, I just did not have the exact name. There are different targets for the same kernel sometimes. Basically i386 should run on any x86 pc. You see what I mean though right?

The .src.rpm needs to be built with rpmbuild, where the i386.rpm files can be installed with rpm.

The linksys card works with the current redhat 9 kernel, I am using it right now.

[david@zeus david]$ rpm -q kernel kernel-source
kernel-2.4.20-20.9
kernel-source-2.4.20-20.9

[david@zeus david]$ /sbin/lsmod | grep rtl
rtl8180_24x 224876 1

[david@zeus david]$ cat /proc/rtl8180/status
---------------------------------------
Driver status
---------------------------------------

rtl8180_pci_driver version 1.4 loaded.
The Network is configured as Infrastructure mode.
MacAddr = 00:xx:xx:xx:xx:xx
ioaddr = 0x4000
irq = 5


---------------------------------------
Wireless Link status
---------------------------------------

Link Success!

Channel number = 1
beacon period = 100
BSSID = 0xxx 0xxx 0xxx 0xxx 0xxx 0xxx
SSID = Days_Inn_1_GreatBend
Capability = 0x01
AID = 0x07
Operational rates = <1><2><5.5><11>Mbps
Current TX operational rates = <11>Mbps

Heres what I get when I try to insmod..........oot@localhost release]# /sbin/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

Is this right? Says something like tainting a kernel. Did I do something wrong? Any help would be greatly appreciated. Oh, I went back to RH9.0 . Updated kernel to 2.4.20-20.9 , Downloaded the Realtek drivers, the one for RH9. And followed all the processess up to here. Looks like I did something wrong. But , I don't know for sure.......

Sigh. I'm still banging my head on this in my spare time. Here's where I'm at:

0) System: laptop running RH9, kernel 2.4.20-20.9

1) Downloaded v1.4 of the driver, got it to compile

2) Can 'insmod rtl8180_24x.o' with no complaints

3) I try running provided 'wlanup' script and run into all sorts of trouble. A lot of this is
due to my complete ignorance of wireless terminology/lingo. If someone is patient enough to break this down for me, I'd be much obliged.

I'm trying to connect to an Apple Airport at work. I have some instructions for Mac users which are as follows:

Apple OS9:

Select AirPort from the Apple menu
Under Settings, click in the box labeled:

"Allow selection of closed networks"

Under AirPort Network, select "Other" from the pull-down list
Enter "XXX" as the Name and "YYY" as the Password
Close the AirPort utility

I suspect, though don't know for certain, that it is providing DHCP. I have no idea about this WEP business, one way or the other.

So. Do I want to run 'wlanup' with ap, infra or adhoc as an argument? For other fellow
lunkheads, could someone spell out what these refer to? More aggressive googling would no doubt yield the info, but it would be nice to have it documented here.

There are a mess of 'wlan_para' parameters that may or may not need to be set. It would also be fantastic if someone could spell out which always need to get set and which others are need in particular cases. It would also be great to get some advice on how the average user tracks down the necessary info.

Thanks to everyone for posting. At least it's good to know that I'm not suffering alone...

Some time back I posted about geting a message from iwpriv saying: "no private ioctls", well I've just solved the problem and wanted to share my findings. Maybe what I found is really obvious to everyone else, but since this is the first time I compile a driver, to me is something else.

I have LindowsOS 4.0 (Debian based) installed on a Toshiba Satellite Laptop with the Linksys WPC11v4 card, my kernel version is 2.4.20, so I downloaded the file for RH9.0, since it is the same kernel version. In the Realtek site said that this was for gcc 3.2 (or this is what I understood), so I compiled it with gcc 3.2 and here was the problem. After looking for the nth time through dmesg, I noticed that my kernel was compiled with gcc 2.95, so I thought that maybe I needed to build the driver with the same compiler as the one used to build the kernel. I built it again, now with gcc 2.95, ran the wlanup script and voila!, I am posting this through my wireless card.

In conclusion:

1. You need to download from realtek the file that matches your kernel version:
---> gcc 2.96 / RH7.3 for kernel 2.4.18 or
---> gcc 3.2 / RH9.0 for kernel 2.4.20;
2. You need to build the driver using the same version of gcc that was used to build the kernel.

I want to thank everyone for all the help and for a great thread, this is one of the reasons Linux is so great.

WMCrazyOne

No problem, the warnings are just that. The driver is not signed.



argh

I ran into the DHCP problem as well, if that's what it is in your case. I suspect that it has something to do with the server config. probably a windows machine runnnig half-assed software.


Anyway I just setup mine manually with ifconfig. Then I used iptraf to listen for traffic and found the server..

UDP (72 bytes) from 192.168.0.1:520 to 192.168.0.255:520 on wlan0

From this I was able to determine what I can use for an ip address and the default route.


I then set my ip address to 192.168.0.211 and default route to 192.168.0.1

If some windows machine had the same ip it would likely crash and then they should get a new address on reboot.

Not a glamorous solution but it works. In my case it's temporary setup that works great.

Hi,

I'm having a similar problem to argh, above. I cannot get my Netgear MA521 to connect to my Apple Airport (Dual ethernet/Snow model). I posted a seperate thread, but perhaps I should post here since it seems to get more traffic for issues with this chipset.

Here's the post I made yesterday afternoon:

http://www.linuxquestions.org/questi...hreadid=119220

The main issue is that the join request for the SSID times out. I grepped for the error message in all the files included with the driver from realtek and only priv_part.o matches. I think my issue might be that I have that module loaded. Would that matter?

Or does anyone have any other idea what I might be missing?

Distribution: Red Hat 9.0
Kernel: 2.4.20-20.9 (precompiled from RH updates)
RealTek driver: r14
Knowledge level of user: I have extensive experience with Linux networking, but this is my first adventure into wireless .

Thank you.

I just joined this board to see if there is an easy way to get linux(redhat or mandrake) to recognize my desktop linksys 54g pci card. This wireless stuff drove me back to xp. As soon as there is an easy way to get my desktop to recognize my linksys 54g pci card I will reinstall linux. This is too much work and too litlle productivity. Very frustrating. This should be basic. Let me double click or run a program so that my wireless card is recognized. yikes!
baimo

Why don't you ask Linksys?

They told me the 2.6 kernel driver for my Wireless card will be released soon.

Maybe they could make you a special program where everything is automagically setup. Just let them know what you need.

Ok, heres what I get when I run----[root@localhost william]# /sbin/iwpriv wlan0 enable
wlan0 no private ioctls.
Does anyone one know what this means. Have been looking for info , on this and have been unsuccessful. Any help would be greatly appreciated. Thanks, William.

Ok Thanks

The only way I can get that error is if I run it with wlan1 which does not exist.

what do these show?

ifconfig -a

lsmod


I was looking at your recent post again and see that it looks like the module may not have loaded.

be sure you built the module for your current kernel, then copy the driver to your modules folder

cp rtl8180_24x.o /lib/modules/`uname -r`/kernel/drivers/net/wireless/

then run these

depmod -ae
modprobe rtl81880_24x

ifconfig -a