LinuxQuestions.org - [SOLVED] Problem compiling a RT73 module in Slack 64 13.1

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Problem compiling a RT73 module in Slack 64 13.1 (https://www.linuxquestions.org/questions/slackware-14/problem-compiling-a-rt73-module-in-slack-64-13-1-a-834808/)

Problem compiling a RT73 module in Slack 64 13.1

Hello:

Actually, I have posted this problem here but I don´t know if is best to ask it here.

The problem is that I have upgraded my OS to Slackware 13.1 64 bits, and now, I can´t compile the module RT73 from serialmonkey

There are a lot of similar tutorials explaining the steps for a succesfully installation. I had followed any of them before, and I had no problem never.

But now, I get this error:

Code:

make[1]:Entering directory "/usr/src/linux-2.6.33.4"

 Building modules, stage 2

 MODPOST 0 modules

make [1]: Leaving directory "/usr/src/linux-2.6.33.4"

rt73.ko failed to build!

make:*** [module] Error 1

On the other hand, in the serialmonkey page they said that the driver was included into the kernel yet, but I don´t know how can I now if I have the driver installed. The true is that my usb doesn´t work.

It´s is a USB D-Link System AirPlus G DWL-G122 Wireless Adapter (rec.C1) [Ralink RT73]

Thank you

First of all, you shouldn't post questions in other topics like the one you linked to. All new questions in their own topics.

Second, according to the output of lsmod (which you posted in the other topic, but not this one, by the way), the proper module is already loaded for your hardware. In that case, what exactly seems to be the problem? Does the interface not show up?

What is the output of "iwconfig"?

Hello:

Thx for your answer.
It wasn´t a good idea not open a new thread, definitively.

Well, lsmod shows: rt73usb, rt2x000usb and rt2x00lib

The problem is that my usb device doesn´t work. It has 2 leds, and both of them are switch off. Usually, the "Link" led is always on, and the "Act" led is flicking when there are traffic.

Until now, I have always followed one of the hundreds of similar tutorials for run this device. The stes are:

* Remove the similar modules that don´s work (rt73usb, rt2x000usb and rt2x00lib) and put them in the blacklist.

* Download the driver from serialmonkey page and compile and install the module

* Optionally install RutilT for manage it.

Even in Slackware 13.0 I followed this way (when the kernel had included the modules for my device) and all it was ok.

But now I get the error when I compile.

On the other hand, maybe it has no sense to try to compile a old module when the newer kernels have included the drivers into them, but It was the way I always followed and It always was ok. I have no very experience into Linux, and it´s dificult to me to change the few ways I know to solve the problems.

Ufff, sorry for my english again!

P.S. I installed a Ubuntu version and my usb device work perfectly

Quote:

Originally Posted by davidehm (Post 4110693)

On the other hand, maybe it has no sense to try to compile a old module when the newer kernels have included the drivers into them, but It was the way I always followed and It always was ok. I have no very experience into Linux, and it´s dificult to me to change the few ways I know to solve the problems.

I have a couple of rt73 devices that have worked out of the box since Slackware 13.0 was released. Prior to Slackware 13.0 I did have to use an upstream driver for better performance. Though, IIRC, I did use a newer kernel than that which shipped with Slackware 13.0. I do know for a fact, our rt73 usb wireless sticks work out of the box with Slackware 13.1 and it's default kernel.

Quote:

Usually, the "Link" led is always on, and the "Act" led is flicking when there are traffic.

The "Link" led will not be on until you obtain an IP address / associate with a router. When you first plug in the device, no led will be lit. Perhaps you have not setup / ran Wicd correctly?

Well, I'm more stupid I thought.

Actually, in my first try, I had a problem with Wicd and RutilT, because they couldn't found the device, but I had made any wrong things before...

Now, I have try to configure it manually, with ifconfig and iwconfig and it works.

Very very thank you. Sometimes I forget to back over my steps and reconsider the options.