Also have AR8152 problems

[Nanoscienceguy]

Hi, I've recently installed Fedora 13 64-bit on a Dell N7010. There is no Ethernet driver installed same as the originator of this thread described. I have tried both installing the Atheros driver and the compat-wireless-2.6 on the link to the Ubuntu forum with different problems for each described below. This really puts me in a quandary, as w/o internet connectivity this Linux partition isn't very useful (e.g. there are no developer tools like gcc available right now, so doing make's are difficult, such as installing the Broadcom wireless driver. ) So, are there any suggestions from those far more adept at Linux than me?

Some particulars:
[Ron@localhost ~]$ uname -r
2.6.33.3-85.fc13.x86_64

[Ron@localhost ~]$ lsusb
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 413c:8160 Dell Computer Corp.
Bus 001 Device 006: ID 413c:8162 Dell Computer Corp.
Bus 001 Device 005: ID 413c:8161 Dell Computer Corp.
Bus 001 Device 004: ID 0c45:641d Microdia
Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Ron@localhost ~]$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 1
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 1
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 01)
04:00.0 Ethernet controller: Atheros Communications AR8152 v1.1 Fast Ethernet (rev c1)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
[Ron@localhost ~]$

When I try to extract the tarball AR81Family-linux-v1.0.1.13.tar.gz obtained from
website partner dot atheros dot com/Drivers dot aspx, the following error message occurs:

[Ron@localhost EthernetDriver]$ tar xvf AR81Family-linux-v1.0.1.13.tar.gz
./atl1e.7
./atl1e.spec
./at_osdep.h
./copying
./dkms.conf
./ldistrib.txt
./Makefile
./pci.updates
./readme
./release_note.txt
./src/
./src/atl1c.h
./src/atl1c_ethtool.c
./src/atl1c_hw.c
./src/atl1c_hw.h
./src/atl1c_main.c
./src/atl1c_param.c
./src/atl1e.h
./src/atl1e_ethtool.c
./src/atl1e_hw.c
./src/atl1e_hw.h
./src/atl1e_main.c
./src/atl1e_param.c
./src/at_common.h
./src/at_common_main.c
./src/at_osdep.h
./src/kcompat.c
./src/kcompat.h
./src/kcompat_ethtool.c

gzip: stdin: decompression OK, trailing garbage ignored
./src/Makefile
./src/Module.markers
./src/Module.symvers
./src/modules.order
tar: Child returned status 2
tar: Exiting with failure status due to previous errors
[Ron@localhost EthernetDriver]$

Trying to do a make anyway results in:

[Ron@localhost EthernetDriver]$ make
make -C ./src
make[1]: Entering directory `/home/Ron/EthernetDriver/src'
Makefile:61: *** Linux kernel source not found. Stop.
make[1]: Leaving directory `/home/Ron/EthernetDriver/src'
make: *** [all] Error 2

And finally, trying to do a make for compat-wireless-2.6 (the linked Ubuntu forum path) results in the error:

[root@localhost compat-wireless-2010-10-23]# make
/home/Ron/ETD/compat-wireless-2010-10-23/config.mk:196: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."
./scripts/gen-compat-autoconf.sh config.mk > include/linux/compat_autoconf.h
make -C /lib/modules/2.6.33.3-85.fc13.x86_64/build M=/home/Ron/ETD/compat-wireless-2010-10-23 modules
make: *** /lib/modules/2.6.33.3-85.fc13.x86_64/build: No such file or directory. Stop.
make: *** [modules] Error 2

Any suggestions *most* appreciated!!!

Thank you,

Ron

[MikeTbob]

Hello and Welcome.
Click the wireless link in my signature, it has a lot of good info on getting started with networking. If we can get the wired connection going, the wireless should be fairly easier.

[Nanoscienceguy]

Hi MikeTbob,

Thanks for the answer... I've started a new thread titled "Dell N7010 Ethernet connectivity (Fedora 13 x86_64)" per your wireless setup link hints.

Ron

[oz]

Thanks for the answer... I've started a new thread titled "Dell N7010 Ethernet connectivity (Fedora 13 x86_64)" per your wireless setup link hints.

Hello and welcome to the forums, Ron!

I'm locking this one because it becomes overly confusing to those that try to help when we have two active threads running concerning the same issue. Good luck with it.