Ralink Wireless LAN card v2 not working in Fedora 7
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Ralink Wireless LAN card v2 not working in Fedora 7
I have recently installed Fedora 7 on the second partition of my Packard Bell EasyNote MZ36-U-001 (1,60 GHz, IntelŪ PentiumŪ dual-core Processor T2060, 533 MHz, 1 GB DDR2, 120 GB )
Two things I havent been able to fix:
Not recognizing my Ralink Wireless LAN card v2 hardware (although it does recognize the Realtek RTL8139/810x Family Fast Ethernet NIC)
My Realtek HD audio isnt working at sll when I test it.
Im not concerned about the audio as much as I am about my wireless connectivity.
Can someone please guide me through what I need to do?
I couldnt find a code for the Ralink Wireless LAN card v2. Other sites have things like "rt2400" devices but in windows I cant find anything like that.
You need to find out what chipset the wireless card has (rt2400 is an example of one). After booting up the laptop, post the output of the command dmesg (must be run as root / superuser). There should be some info on the card there.
please note, if I come across as annoyed or frustrated, it because this whole affair has been nothing but that
Quote:
Originally Posted by farslayer
What distribution ?
well, so far I've tried on:
redhat 4 (2.6.9)
ubuntu 8.04.1
fedora 9
all with no success at being able to get either my Motherboard NIC going, or indeed the card I subsequently bought (and posted this comment about) going.
I've spend whole working days at this no just some evenings at home with the TV on in the background. Also, I did not take lightly the move from redhat 4 as I'm needing that to then install Oracle 10g which requires the redhat 4
Quote:
Originally Posted by farslayer
in Debian it was drop dead simple.. (ubuntu should be the same)
yes, well that's the thing that Linux people keep telling me. However Since 1994 I've made 3 attempts to get a usable system operating at home using Linux (of various flavours) going and at no time have I ever been able to get my underlying hardware (lets not even start with peripherals like printers or scanners) going properly. I started playing on Apple IIe, BBC's, Amiga, IBM compatible since the 80's. Now, while I'm not claiming to be an expert on Linux systems if I can't do this then how is the ordinary mum and dad out there supposed to?
right now as it happens I'm looking at an error message in Fedora telling me to enable IOMMU in my bios (nothing like that seems to be there). Of course I then can't do much with Fedora as while the installer seems to be happy with my system (well, it crashes if I ask it to detect my network card) and seems to display X, when booting it just leaves my screen black. I assume that its starting in some video mode that my system can't utilize.
Then edit the /etc/network/interfaces file to add the entry for the wireless adapter..
sorry, but I have no idea what what that command does (and didn't even know of its existence till you mentioned it and I googled it).
if you think that's drop dead easy, why don't you try working with a windows platform some day? Over there I've found everything simply works, and if its not on the 'list' when installing then it gives me a "have disk" option to provide it and put it where it needs to go.
Linux may be many things, but simple - straight forward - anyone can do it are not among the lists.
10 years later I'm finding that its still the nightmare of frustration that it ever was.
Can't make sense of what exactly you are trying to put across, but you can save yourself headaches by buying Linux compatible hardware (just like you would do with Windows) if you want to save yourself frustration. I personally use ralink based wireless cards (the drivers are included in new kernels, so you don't need to install them on your own) and basic realtek or via rhine wired cards and things just work out of the box on most distros.
Can't make sense of what exactly you are trying to put across
that its not helpful when people say "its simple" when its not always simple.
Quote:
Originally Posted by reddazz
if you want to save yourself frustration. I personally use ralink based wireless cards (the drivers are included in new kernels, so you don't need to install them on your own) and basic realtek or via rhine wired cards and things just work out of the box on most distros.
ok, which is why I then went and bought a card which I understood was compatible (specifically the RT-2561T card mentioned), which then seems not to be supported in the latest distro's which I mentioned (Fedora 9 and Ubuntu 8.04.1
if there is a wireless card that you can recommend will work please feel free to recommend it as quite frankly a server with no network card isn't much of a server.
if on the other hand you (or anyone else) would be so kind as to make some suggestions on how to:
after re-installing redhat (over my non usable fedora) I now find that when compiling things from the serialmonkey driver set, that stuff seems to be working better now.
compile warnings:
Code:
Building modules, stage 2.
MODPOST
CC /tmp/rt61-cvs-2008071005/Module/rt61.mod.o
LD [M] /tmp/rt61-cvs-2008071005/Module/rt61.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
!!! WARNING: Module file much too big (>1MB)
!!! Check your kernel settings or use 'strip'
*** Module rt61.ko built successfully
[root@localhost Module]#
-- now, after doing step 4 modprobe returns nothing
-- I don't know if this is significant
-- so I then installed ...
Code:
[root@localhost Module]# make install
*** Install module in /lib/modules/2.6.9-22.ELsmp/extra ...
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
INSTALL /tmp/rt61-cvs-2008071005/Module/rt61.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
/sbin/depmod -a
*** Update /etc/modprobe.d/ralink alias for wlan*
*** Config dir /etc/modprobe.d not found
*** Install firmware in /lib/firmware ...
*** Check old config ...
-- checking with modprobe still gives nothing
Code:
[root@localhost Module]# modprobe rt61
-- but when just typing in the commands (with fingers crossed)
Granted what I called simple, is only simple if you know the commands. as for working with Windows, yes that's what I do for a living. I find it relaxing and fun to work with a stable Linux platform after dealing with Windows issues all day.
I can take two identical PC's install Linux on one and have everything work immediately after the install with actual applications to use, install Windows on the other and have no sound, no network, crappy video, etc.. until I locate and manually install drivers for everything on the windows box, rebooting a dozen times or so.
Yes if you are very familiar with windows it seems easier, but if you have no experience in either OS then I would say they are equally as difficult to use.
Glad you finally got something working there on your wireless.
Have you tried using NDISWrapper? that's how I got my RaLink RT2561/RT61 working in all my distros...
well, I'm not sure if I've done something wrong, of if there is a lack of source code with my distro. Well, anyway the first stage of make failed. I've bolded a few areas which I can't change or don't know if I could / should change.
Here is the output of [root@localhost ndiswrapper-1.53]# make
Code:
make -C driver
make[1]: Entering directory `/tmp/ndiswrapper-1.53/driver'
*** WARNING: This kernel uses 4K stack size option
(CONFIG_4KSTACKS); many Windows drivers will not work
with this option enabled. Disable CONFIG_4KSTACKS
in kernel's .config file, recompile and install kernel
make -C /usr/src/kernels/2.6.9-22.EL-smp-i686 M=/tmp/ndiswrapper-1.53/driver
make[2]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
LD /tmp/ndiswrapper-1.53/driver/built-in.o
MKEXPORT /tmp/ndiswrapper-1.53/driver/crt_exports.h
MKEXPORT /tmp/ndiswrapper-1.53/driver/hal_exports.h
MKEXPORT /tmp/ndiswrapper-1.53/driver/ndis_exports.h
MKEXPORT /tmp/ndiswrapper-1.53/driver/ntoskernel_exports.h
MKEXPORT /tmp/ndiswrapper-1.53/driver/ntoskernel_io_exports.h
MKEXPORT /tmp/ndiswrapper-1.53/driver/rtl_exports.h
MKEXPORT /tmp/ndiswrapper-1.53/driver/usb_exports.h
CC [M] /tmp/ndiswrapper-1.53/driver/crt.o
In file included from /tmp/ndiswrapper-1.53/driver/crt.c:16:
/tmp/ndiswrapper-1.53/driver/ntoskernel.h:649: error: field `lock' has incomplete type
/tmp/ndiswrapper-1.53/driver/ntoskernel.h: In function `raise_irql':
/tmp/ndiswrapper-1.53/driver/ntoskernel.h:686: warning: implicit declaration of function `mutex_lock'
/tmp/ndiswrapper-1.53/driver/ntoskernel.h: In function `lower_irql':
/tmp/ndiswrapper-1.53/driver/ntoskernel.h:708: warning: implicit declaration of function `mutex_unlock'
make[3]: *** [/tmp/ndiswrapper-1.53/driver/crt.o] Error 1
make[2]: *** [_module_/tmp/ndiswrapper-1.53/driver] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/tmp/ndiswrapper-1.53/driver'
make: *** [all] Error 2
[root@localhost ndiswrapper-1.53]#
I don't know if I can just comment out things ... either way this is (again) not a straight forward solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.