Netgear MA111 problem

[Paul F. Johnson]

Hi,

I'm following the instructions for getting the Netgear MA111 from
http://www.linuxquestions.org/questions/history/89893.

I am up to the part where I have to enter the path to the kernel source.
When I enter /usr/src/linux-2.6.6-1.435, the config script fails
complaining that while the kernel sources are where I say they are, they
are incomplete and advising me obtain the sources from the likes of
kernel.org

Is there anything missing from the current source tree or am I safe to
download the 2.6.7 tree from kernel org and point the script to that?

TTFN

Paul

[Philip Balister]

I just went through this ordeal. I made it work by rebuilding the kernel
rpm.

Install the kernel source rpm.

Edit the spec file so it doesn't build the smp kernel.

touch /etc/beehive (look up name in the spec file) so the kernel doesn't
add the username to the kernel version.

rpmbuild -qb <spec-file>

Then tell linux-wlan-ng the kernel source is in
/usr/src/redhat/BUILD/...

The above is from memory, you will need to double check commands etc and
read the spec file carefully. I am pretty annoyed at the pain level
required to build this driver, however I felt I gained some insight into
how to rebuild rpm's which offset the pain some :)

Email me of list if you have anymore questions.

Philip

On Thu, 2004-06-17 at 06:13, PFJ wrote:
> Hi,
>
> I'm following the instructions for getting the Netgear MA111 from
> http://www.linuxquestions.org/questions/history/89893.
>
> I am up to the part where I have to enter the path to the kernel source.
> When I enter /usr/src/linux-2.6.6-1.435, the config script fails
> complaining that while the kernel sources are where I say they are, they
> are incomplete and advising me obtain the sources from the likes of
> kernel.org
>
> Is there anything missing from the current source tree or am I safe to
> download the 2.6.7 tree from kernel org and point the script to that?
>
> TTFN
>
> Paul

[Arjan van de Ven]

On Thu, 2004-06-17 at 12:13, PFJ wrote:
> Hi,
>
> I'm following the instructions for getting the Netgear MA111 from
> http://www.linuxquestions.org/questions/history/89893.
>
> I am up to the part where I have to enter the path to the kernel source.
> When I enter /usr/src/linux-2.6.6-1.435, the config script fails

that is the wrong location; the right location is

/lib/modules/2.6.6-1.435/build

[Philip Balister]

Apparently these drivers have a great desire to see a built kernel
source tree. Google for "fedora linux-wlan".

Philip

On Thu, 2004-06-17 at 08:30, Arjan van de Ven wrote:
> On Thu, 2004-06-17 at 12:13, PFJ wrote:
> > Hi,
> >
> > I'm following the instructions for getting the Netgear MA111 from
> > http://www.linuxquestions.org/questions/history/89893.
> >
> > I am up to the part where I have to enter the path to the kernel source.
> > When I enter /usr/src/linux-2.6.6-1.435, the config script fails
>
> that is the wrong location; the right location is
>
> /lib/modules/2.6.6-1.435/build
>
> -- 
> fedora-test-list mailing list
> [e-mail]
> To unsubscribe: 
> http://www.redhat.com/mailman/listinfo/fedora-test-list

[Arjan van de Ven]

On Thu, Jun 17, 2004 at 08:45:59AM -0400, Philip Balister wrote:
> Apparently these drivers have a great desire to see a built kernel
> source tree. Google for "fedora linux-wlan".

actually these drivers have a really broken set of makefiles (well broken
for 2.6 kernels)... since these don't seem to be adjusted for 2.6 I doubt
the code itself is... dangerous drivers thus.

[Camilo Mesias]

Arjan
> actually these drivers have a really broken set of makefiles (well broken
> for 2.6 kernels)... since these don't seem to be adjusted for 2.6 I doubt
> the code itself is... dangerous drivers thus.

With respect, that's a little harsh. I have compiled the wlan-ng drivers 
against the FC2 2.6 kernel with little effort. I now have a server at 
home whose only connection to the net is through the MA111. It works 
very well for me (WEP included).

I wonder what it would take to get the FC2 drivers to work with the 
MA111 (from what I remember, it only took a one-line change to allow the 
MA111 to be detected in wlan-ng)

-Cam

[Paul F. Johnson]

Hi,
> I wonder what it would take to get the FC2 drivers to work with the 
> MA111 (from what I remember, it only took a one-line change to allow the 
> MA111 to be detected in wlan-ng)

It's compiled, it's installed and won't work as the modules are in the
"incorrect format".

Any way to fix it?

TTFN

Paul

[Camilo Mesias]

Paul
> > I wonder what it would take to get the FC2 drivers to work with the 
> > MA111 (from what I remember, it only took a one-line change to allow the 
> > MA111 to be detected in wlan-ng)
>
> It's compiled, it's installed and won't work as the modules are in the
> "incorrect format".
>
> Any way to fix it?

What specific errors do you get?

I don't recall exactly what I did but it would have been something like:

* install the FC2 kernel sources RPM
* cd into /usr/src/linux...
* copy the relevant config from the configs subdirectory into .config
* make oldconfig
* make
* make install
* reboot to test the 'custom' kernel

then install the wlan-ng sources, configure them to compile only the usb 
driver and point them at the kernel sources built in the previous step.

Configuration is a bit of a pain, I used the text config files not the 
system-config-* GUI. But it does work.

-Cam

[Paul F. Johnson]

Hi,
> > It's compiled, it's installed and won't work as the modules are in the
> > "incorrect format".
> >
> > Any way to fix it?
>
> What specific errors do you get?

system-config-network:

The ethernet card could not be initialised. Please verify your settings
and try again.

WARNING: Error inserting p80211 (/lib/modules/2.6.6-1.435/linux-wlan-ng/
p80211.ko): Invalid module format
FATAL: Error inserting prism2_usb (/lib/modules/2.6.6-1.435/linux-wlan-
ng/prism2_usb.ko): Invalid module format

I did as Arjan suggested and pointed the Configure script to the correct
place. Other than having to make one directory, the compilation went
without a hitch.

I did a yum install kernel-sourcecode which placed the source in /usr/
src. What config files do I need to copy into .config? I would have
thought that compiling using the path indicated by Arjan would have
worked.

TTFN

Paul

[Camilo Mesias]

PFJ
> I did a yum install kernel-sourcecode which placed the source in /usr/
> src. What config files do I need to copy into .config? I would have
> thought that compiling using the path indicated by Arjan would have
> worked.

OK a quick followup, here's what I did.

I installed the kernel-source-2.6.5-1.358

ln -s /usr/src/linux-2.6.5-1.358/ /usr/src/linux
cp /usr/src/linux/configs/kernel-2.6.5-i586.config /usr/src/linux/.config
make oldconfig
make
make modules_install
make install

(reboot)

wget -nd 
ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/linux-wlan-ng-0.2.1pre21.tar.bz2
tar jxvf linux-wlan-ng-0.2.1pre21.tar.bz2
cd linux-wlan-ng-0.2.1pre21
less README
make config
make
make all
make install
cd /etc/wlan/
less wlancfg-DEFAULT

(probably edited the file)

mv wlancfg-DEFAULT wlancfg-myESSIDhere

ln -s /home/X86/linux-wlan-ng-0.2.1pre21/etc/rc.wlan /etc/rc.d/init.d/
cd /etc/rc.d/init.d/
./rc.wlan status
./rc.wlan start

chkconfig rc.wlan --add

...

The above is pieced together from my bash history, hope it helps. Use it 
for clues rather than as a recipe.

-Cam

[Philip Balister]

Look in /var/log/messages and I bet you see the versions don't quite
match. If you built the kernel from the rpm, try touching /etc/beehive
(look up the real file name in the spec file) to fool it into not adding
a username to the kernel version string.

Philip

On Thu, 2004-06-17 at 09:51, PFJ wrote:
> Hi,
> > I wonder what it would take to get the FC2 drivers to work with the 
> > MA111 (from what I remember, it only took a one-line change to allow the 
> > MA111 to be detected in wlan-ng)
>
> It's compiled, it's installed and won't work as the modules are in the
> "incorrect format".
>
> Any way to fix it?
>
> TTFN
>
> Paul