Hi,

When I can't compile my Attansic network card, because of this error:

CFLAGS was changed in "home/test/Attansic/src/Makefile". Fix it to use EXTRA_CFLAGS. Stop.

the kernel is kernel 2.6.24.

Any help is appreciated

thanks a lot

Try setting the variable
KBUILD_NOPEDANTIC
to 1 before running make

1 members found this post helpful.

Where is that located at???
In what file???
What is the path to the file where I will need to change that???
The kernel is 2.6.26 (Flavor = Mepis)
Thanks in advance...

Love is very patient and kind, never jealous or envious, never boastful or proud, never haughty or selfish or rude. Love does not demand its own way. 1 Corinthians 13:4 - 8, 13 The greatest ........ is LOVE.
"A firsthand account of discrimination (racial, sex, orientation, disability) in Federal Civil Service: Glass Ceilings" - Buy my book: http://www.authorhouse.com/BookStore...kid~50452.aspx

You don't need to set it in a file. Just, instead of running

make

in a terminal, type

KBUILD_NOPEDANTIC=1 make

Or, type

export KBUILD_NOPEDANTIC=1
make

I tried that... and here's what I got...

I ran... KBUILD_NOPEDANTIC=1 make ... in a console...

root@somecomputer:/# KBUILD_NOPEDANTIC=1 make
make: *** No targets specified and no makefile found. Stop.

What file is that setting found in???
I would appreciate any help that you can offer with this...

You need to run make from the directory that contains the Makefile for your module or application. Usually, it's located in the top-level directory of the source tree. So, you should cd to /home/test/Attansic/src/ or something like that and run it from there.

Okay... I'll do make for each and everyone of them... thanks...

I tried... but they are still failing... here's what they say when I try to run ./configure and/or make them...
Alsa
/usr/bin/make -C /usr/src/linux-headers-2.6.26 SUBDIRS=/usr/src/modules/alsa-driver O=/usr/src/linux-headers-2.6.26 CPP="gcc-4.1 -E" CC="gcc-4.1" modules
make[3]: Entering directory `/usr/src/linux-headers-2.6.26'
/usr/src/linux-headers-2.6.26/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.26/arch/x86/Makefile_32.cpu: No such file or directory
and cdfs
make -C /usr/src/linux-headers-2.6.26 SUBDIRS=/usr/src/modules/cdfs/2.6 modules
make[3]: Entering directory `/usr/src/linux-headers-2.6.26'
/usr/src/linux-headers-2.6.26/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.26/arch/x86/Makefile_32.cpu: No such file or directory
make[3]: *** No rule to make target `/usr/src/linux-headers-2.6.26/arch/x86/Makefile_32.cpu'. Stop.
and OV511
Building OVCam drivers for 2.6 kernel.
/usr/bin/make -C /usr/src/linux-headers-2.6.26 SUBDIRS=/usr/src/modules/ov511 modules
make[3]: Entering directory `/usr/src/linux-headers-2.6.26'
/usr/src/linux-headers-2.6.26/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.26/arch/x86/Makefile_32.cpu: No such file or directory
make[3]: *** No rule to make target `/usr/src/linux-headers-2.6.26/arch/x86/Makefile_32.cpu'. Stop.

Hi all,
Someone else might end up in this thread because the problem is quite common. The first answer given was the right info, but just missed one crucial thing that a newbie would not perhaps pick up on.

I had the exact same problem, and managed to work it out, so here is the full solution:

Asus P5Q motherboard, needs atl1e driver for Attansic/Atheros LAN, kernel 2.6.24 fc8.

The easist answer is to upgrade the kernel to 2.2.26, but without a LAN that might be tricky. In my case I'm using a packaged distro (mythdora5), and want to keep that as standard as possible, so need the harder approach.
Please note that this solution does not build a custom kernel, it simply builds the required kernel module (driver file) against the installed kernel. The info says that it's good for 2.6.24 and 2.6.26
If not done already get the driver here (on some other working internet machine):

http://dlsvr04.asus.com/pub/ASUS/mb/...nuxDrivers.zip

This archive has both sound and LAN drivers, use winrar to open it (see why in a minute), navigate to "L1e_LAN", and open the winrar archive (that's why), extract the files to a USB stick.

insert the usb stick into the fc8 box. Now, on mythdora5 it automounts for me, but this may not happen in your fc8, you're on your own there sorry. Once you get the USB stick mounted in fc8, copy the files into the suggested directory

/usr/local/src/atl1e

Check that you have in that location at least the file

atl1e.7

and a dir called

src
(then as root, don't type the #, that's the root prompt...)
#cd /usr/local/src/atl1e
#KBUILD_NOPEDANTIC=1 make install

the result will be a driver file called atl1e.ko loaded into

/lib/modules/<KVER>/kernel/drivers/net/atl1e

where <KVER> is your kernel version. Check this with:

#find / -name atl1e.ko

Two locations should show up, one in /lib/modules and one where the driver was built.

The driver file will be automatically 'probed' by the system, the build process will automatically install

alias eth0 atl1e

into the system setup file /etc/modprobe.conf
(note there's no action required by you here, but this explains how it works....)

Now reboot
#init 6

And then enjoy my friends...

Funny how life works, I found my way back to my own post, with the same problem, this time I've got FC10 on the same P5Q motherboard, and for some strange reason the NIC does not start up on boot. The interface can be brought up from a terminal once the machine is up, and seems to work ok:

ifup eth0

FC10 is a bit different than FC8, for example modules.conf has been replaced by /etc/modprobe.d/modprobe.conf.dist and has lots of stuff in it. I tried doing the work above to install manually, but still no good. The atl1e module is actually loaded (lsmod), but dmesg has no record of starting the NIC until ifup is run manually once the machine is running.

The driver file reports version 1.0.0.7 using
ethtool -i eth0

yum update and new kernel etc still don't fix this problem, so I have taken the very lazy approach of putting a line in my rc.local file:

/sbin/ifup eth0

dmesg shows a weird thing (weird to me anyway)
---
ATL1E 0000:02:00.0: ATL1E: eth0 NIC Link is Up<100 Mbps Full Duplex>
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
---

Is this link not ready the reason why it won't come up when the machine starts?

Just a further note here, I have seen comments that FC11 has a bad/broken driver for this NIC, not sure on the current status of that.

I see there is v1.0.1.0 of the driver source available, but I have no source on my mythdora10.21 (packaged distro again), so can't be bothered getting all that on board to try it.

Pleased to hear if anyone knows the 'proper' way to fix this (my method above is only a 'hack' the way I see it...)