The install script looked for a directory indicated by `uname -r`, so I
symlinked the -4 directory from the installation tarball to -7 which got
'make config' and to work and then did 'make install' (basically, the script
then copied the rt2500.ko and rt2500.ko.gz supplied for 2.6.3-4mdk instead
of -7).
The I then tried to '/sbin/insmod rt2500.ko' but get
insmod: error inserting 'rt2500.ko': -l Invalid module format
Is this what I should expect from hacking the version number?
What is the -4 version? Can I get Madk 10 to work with that?
Realteks drivers are hopelessly broken (unless things have changed
very recently). But the card works under ndiswrapper (free) or the
linuxant driver (non-free).
> to work under mdk 10.0. The driver (from Ralink's web
> site) expects uname -r = 2.6.3-4mdk whereas my system has 2.6.3-7mdk. What
> difference does the -x number (-4 v. -7) indicate?
Not sure what driver that is, but then I wouldn't touch a mandrake
package with a bargepole.
> then copied the rt2500.ko and rt2500.ko.gz supplied for 2.6.3-4mdk instead
Pardon? .ko sounds more like a FreeBSD module than Linux!
> The I then tried to '/sbin/insmod rt2500.ko' but get
> insmod: error inserting 'rt2500.ko': -l Invalid module format
Erm, yes. What does "file rt2500.ko" tell you?
--
Nick Kew
Hmmm. " Mandrake 10 has the [ndis]wrapper as part of their kernel listed
under 3rd party drivers " (from http://www.linuxelectrons.com/).
But where's the list?!
> > to work under mdk 10.0. The driver (from Ralink's web
> > site) expects uname -r = 2.6.3-4mdk whereas my system has 2.6.3-7mdk.
What
> > difference does the -x number (-4 v. -7) indicate?
>
> Not sure what driver that is, but then I wouldn't touch a mandrake
> package with a bargepole.
I guess I don't have much choice if I'm running Mandrake though, do I? :-)
(I'm not religiously converted to Mandrake mind - I'd be happy to install
any other Linux that (a) installed, (b) worked in graphics mode (c) worked
with my network card. I just tried Mdk because I'd heard some good things
about it being easy to install & use, and had had a bad time trying to get
anywhere with Debian.)
> > then copied the rt2500.ko and rt2500.ko.gz supplied for 2.6.3-4mdk
instead
>
> Pardon? .ko sounds more like a FreeBSD module than Linux!
Seems to be what they call them for 2.6.x kernels (on Mdk at least)
> > The I then tried to '/sbin/insmod rt2500.ko' but get
> > insmod: error inserting 'rt2500.ko': -l Invalid module format
>
> Erm, yes. What does "file rt2500.ko" tell you?
ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped
I think I understood the 'Intel' bit :-)
Ralink Tech, not realtek.
I am using the ralink tech rt2400 module, works just fine.
> very recently). But the card works under ndiswrapper (free) or the
> linuxant driver (non-free).
>
>>to work under mdk 10.0. The driver (from Ralink's web
>> site) expects uname -r = 2.6.3-4mdk whereas my system has 2.6.3-7mdk.
>> What difference does the -x number (-4 v. -7) indicate?
Get the source code and compile it yourself.
http://www.ralinktech.com/supp-1.htm
> Not sure what driver that is, but then I wouldn't touch a mandrake
> package with a bargepole.
>
>> then copied the rt2500.ko and rt2500.ko.gz supplied for 2.6.3-4mdk
>> instead
>
> Pardon? .ko sounds more like a FreeBSD module than Linux!
It is the 2.6 naming convention for linux kernel modules.
Eric
D'oh! Didn't think of that (getting weenified by this packages business -
when I used Solaris I used to have to compile everything myself, and often
to faff around with the order of compilers in $PATH to get it to do the
right thing :-)
Unfortunately 'make all' throws up errors, starting with
'/usr/src/linux-2.6.3-7mdk/include/linux/modversions.h: No such file ...'
The README says the source has been verified for 'Linux versions after
RedHat Linux 7.1' so maybe modversions.h is a RH thing?
include/linux/modversions.h is in 2.4 kernels source.
include/config/modversions.h is in 2.6 kernels source.
To build a 2.6 kernel, the simple procedure is:
make xconfig
make && make modules_install && make install
That's it :)
--
,,,
(._.)
/|\+\\
\|/ @u(==-
Ha! "weenified", that's pretty funny.
> when I used Solaris I used to have to compile everything myself, and often
> to faff around with the order of compilers in $PATH to get it to do the
> right thing :-)
Really? I remember in SunOS days (prior to and up to Solaris 1.1.1) I used
to build a bunch of freeware from tarballs. That usually worked quite well
actually. I suspect most freeware was being developed on SunOS.
These days I usually find freeware for Solaris (2.x+) on:
www.sunfreeware.com
www.blastwave.org
> Unfortunately 'make all' throws up errors, starting with
> '/usr/src/linux-2.6.3-7mdk/include/linux/modversions.h: No such file ...'
> The README says the source has been verified for 'Linux versions after
> RedHat Linux 7.1' so maybe modversions.h is a RH thing?
Yeah, I find most (but not all) application packages can be "ported" to
another distro quite easily. Kernel patches and/or drivers can be messy.
They should be more independent of distro, but they're still messy.
BTW, I have this header on SuSE 8.2:
rpm -qal | grep modversions.h
/usr/src/linux-2.4.20.SuSE/include/linux/modversions.h
p.s. I'm trying to work up the courage to implement wireless LAN 802.11g
on Linux. I guess I'm hoping someone else will have blazed a trail.
--
Juhan Leemet
Logicognosis, Inc.