Nichtskönner
Anmeldungsdatum: 30. August 2014
Beiträge: 22
|
Hallo
ich habe das Problem das mein Ubuntu kein ethernet Port erkennt also habe ich die nötigen Treiber von der Asus website heruntergeladen und sie probiert zu installieren (im Terminal mir root rechte gemacht (sudo su) dann die tar.gz datei mit cd eingefügt und make install eingegeben) doch ich bekomme immer den Fehler "No such file or directory #include <linux/config.h>" (hier das ganze noch einmal ausführlich: user@NAS:~$ sudo su
[sudo] password for user:
root@NAS:/home/user# cd /home/user/Schreibtisch/driver/tg3-3.58b
root@NAS:/home/user/Schreibtisch/driver/tg3-3.58b# make install
gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -I/lib/modules/3.13.0-32-generic/build/include -DOLD_NETIF -mno-red-zone -mcmodel=kernel -pipe -finline-limit=2000 -O2 -c -o tg3.o tg3.c
tg3.c:18:26: fatal error: linux/config.h: No such file or directory
#include <linux/config.h>
^
compilation terminated.
make: *** [tg3.o] Error 1
root@NAS:/home/user/Schreibtisch/driver/tg3-3.58b#) ich hoffe ihr könnt mir weiter helfen
(Treiber: http://www.asus.com/Commercial_Servers_Workstations/P5M2/HelpDesk_Download/ )
meine hardware: Asus P5m2, xeon 3060 2.40GHz, 4GB ECC kingston RAM
|
archy
Anmeldungsdatum: 24. November 2009
Beiträge: 1920
|
hallo, also als Anfänger gleich einen Netzwerktreiber selbst kompilieren und installiere zu wollen halte ich für sehr mutig. Und wie du siehst ging es auch komplett schief. Aber der tg3 ist der Treiber für Broadcom Chips und selbstverständlich hat Ubuntu den mit an Bord. Sieh mal da: /lib/modules/3.13.0-35-generic/kernel/drivers/net/ethernet/broadcom/ Dynamisch werden Treibermodule mit den Befehlen "insmod" und "modprobe" geladen. Mehr dazu sagt dir "man modprobe" in der Konsole.
Zuerst aber solltest du mit "lsmod" in der Konsole prüfen welche Treiber wirklich geladen sind. gruß archy
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13938
|
Nichtskönner schrieb: tg3.c:18:26: fatal error: linux/config.h: No such file or directory
#include <linux/config.h>
I. d. R. wird "config.h" vom "./configure"-Script erzeugt. Poste mal aus dem Verzeichnis "/home/user/Schreibtisch/driver/tg3-3.58b", die Ausgaben von:
ls -la | grep -iE 'configure|makefile'
./configure --help
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Hallo und willkommen bei uu.de. Der Treiber tg3 ist bereits im System drin:
modinfo tg3 Wird er geladen? sudo modprobe -v tg3
lsmod
ifconfig -a
cat /etc/resolv.conf Übrigens ist der User "root" nicht nötig, siehe sudo 😉
|
Nichtskönner
(Themenstarter)
Anmeldungsdatum: 30. August 2014
Beiträge: 22
|
vielen dank für die schnelle Antwort Ich habe die Befehle in die Konsole eingegeben hier sind die ausgaben : M odule Size Used by
rfcomm 69160 0
bnep 19624 2
bluetooth 391196 10 bnep,rfcomm
coretemp 13435 0
kvm_intel 143060 0
kvm 451511 1 kvm_intel
lpc_ich 21080 0
radeon 1522422 2
serio_raw 13462 0
ttm 85115 1 radeon
drm_kms_helper 53081 1 radeon
i3000_edac 12906 0
drm 303102 4 ttm,drm_kms_helper,radeon
i2c_algo_bit 13413 1 radeon
edac_core 62291 2 i3000_edac
shpchp 37032 0
mac_hid 13205 0
parport_pc 32701 1
ppdev 17671 0
lp 17759 0
parport 42348 3 lp,ppdev,parport_pc
hid_logitech_dj 18581 0
usbhid 52570 0
hid 106148 3 usbhid,hid_logitech_dj
ahci 25819 2
libahci 32560 1 ahci
root@NAS:/home/user/Schreibtisch/driver/tg3-3.58b# ls -la
total 560
drwxrwxr-x 2 user user 4096 Aug 30 13:48 .
drwxrwxr-x 5 user user 4096 Aug 30 13:25 ..
-rw-r--r-- 1 user user 83696 Mai 19 2006 ChangeLog
-rw-r--r-- 1 user user 15153 Mai 19 2006 LICENSE
-rw-r--r-- 1 user user 2480 Mai 19 2006 Makefile
-rw-r--r-- 1 user user 9301 Mai 19 2006 README.TXT
-rw-r--r-- 1 user user 3130 Mai 19 2006 tg3.4
-rw-r--r-- 1 user user 344865 Mai 19 2006 tg3.c
-rw-r--r-- 1 user user 93616 Mai 19 2006 tg3.h
root@NAS:/home/user/Schreibtisch/driver/tg3-3.58b# grep -iE
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
root@NAS:/home/user/Schreibtisch/driver/tg3-3.58b# ./configure --help
bash: ./configure: No such file or directory
der Befehl auf das broadcom Verzeichnis wurde durch den Befehl nicht gefunden
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
sudo modprobe -v tg3 war fehlerhaft? Prüfe
lspci -nnk | grep -iA2 net
grep tg3 /etc/modprobe.d/*
locate tg3.ko | grep lib
uname -a
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13938
|
Nichtskönner schrieb: root@NAS:/home/user/Schreibtisch/driver/tg3-3.58b# ls -la
total 560
drwxrwxr-x 2 user user 4096 Aug 30 13:48 .
drwxrwxr-x 5 user user 4096 Aug 30 13:25 ..
-rw-r--r-- 1 user user 83696 Mai 19 2006 ChangeLog
-rw-r--r-- 1 user user 15153 Mai 19 2006 LICENSE
-rw-r--r-- 1 user user 2480 Mai 19 2006 Makefile
-rw-r--r-- 1 user user 9301 Mai 19 2006 README.TXT
-rw-r--r-- 1 user user 3130 Mai 19 2006 tg3.4
-rw-r--r-- 1 user user 344865 Mai 19 2006 tg3.c
-rw-r--r-- 1 user user 93616 Mai 19 2006 tg3.h
OK, "Makefile" ist schon vorhanden, d. h. "./configure" wird nicht benötigt. Gib mal nur als Test, Folgendes (ohne "make install" !!) ein:
make
und poste die Ausgabe von:
ls -la linux/config.h
|
Nichtskönner
(Themenstarter)
Anmeldungsdatum: 30. August 2014
Beiträge: 22
|
user@NAS:~$ lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation E7230/3000/3010 Memory Controller Hub [8086:2778] (rev c0)
Subsystem: ASUSTeK Computer Inc. Device [1043:820c]
Kernel driver in use: i3000_edac
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 01)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: lpc_ich
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: ata_piix
00:1f.2 SATA controller [0106]: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] [8086:27c1] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8190]
01:00.0 PCI bridge [0604]: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A [8086:032c] (rev 09)
03:02.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:81de]
Kernel driver in use: radeon
user@NAS:~$ grep tg3 /etc/modprobe.d/*
user@NAS:~$ tg3.ko
tg3.ko: command not found
user@NAS:~$ grep lib
uname -a
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Dir Karte wird gar nicht erkannt. Prüfe im BIOS, ob sie dort aktiv(ierbar) ist.
|
Nichtskönner
(Themenstarter)
Anmeldungsdatum: 30. August 2014
Beiträge: 22
|
user@NAS:~$ make
make: *** No targets specified and no makefile found. Stop.
user@NAS:~$ cd /home/user/Schreibtisch/driver/tg3-3.58b
user@NAS:~/Schreibtisch/driver/tg3-3.58b$ make
gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -I/lib/modules/3.13.0-32-generic/build/include -DOLD_NETIF -mno-red-zone -mcmodel=kernel -pipe -finline-limit=2000 -O2 -c -o tg3.o tg3.c
tg3.c:18:26: fatal error: linux/config.h: No such file or directory
#include <linux/config.h>
^
compilation terminated.
make: *** [tg3.o] Error 1
user@NAS:~/Schreibtisch/driver/tg3-3.58b$ ls -la linux/config.h
ls: cannot access linux/config.h: No such file or directory
user@NAS:~/Schreibtisch/driver/tg3-3.58b$
(für lubux)
|
Nichtskönner
(Themenstarter)
Anmeldungsdatum: 30. August 2014
Beiträge: 22
|
Im BIOS habe ich keinen Einstellungspunkt gefunden
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Dann versuche einen BIOS-Reset auf Werkseinstellungen
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13938
|
Nichtskönner schrieb: tg3.c:18:26: fatal error: linux/config.h: No such file or directory
#include <linux/config.h>
Da ist dann eine "allgemeine" linux/config.h-Datei (außerhalb des source code) gemeint. Poste mal die Ausgabe von:
cat README.TXT
|
Nichtskönner
(Themenstarter)
Anmeldungsdatum: 30. August 2014
Beiträge: 22
|
BIOS ist zurückgesetzt und hier ist die readme Datei
user@NAS:~$ cd /home/user/Schreibtisch/driver/tg3-3.58b
user@NAS:~/Schreibtisch/driver/tg3-3.58b$ cat README.TXT
Installation Notes
Broadcom tg3 Linux Driver
Version 3.57b
04/28/2006
Broadcom Corporation
16215 Alton Parkway,
Irvine, CA 92619-7013
Copyright (c) 2004, 2005, 2006 Broadcom Corporation
All rights reserved
Table of Contents
=================
Introduction
Limitations
Packaging
Installing Source RPM Package
Building Driver From TAR File
Driver Settings
Driver Defaults
Unloading and Removing Driver
Driver Messages
Introduction
============
This file describes the tg3 Linux driver for the Broadcom NetXtreme
10/100/1000 Mbps PCI/PCI-X/PCI Express Ethernet Network Controllers.
The latest driver is in the latest 2.6 Linux kernel. It can also be
downloaded from http://www.broadcom.com as a source package, but is
generally not necessary to do so if you are using the latest 2.6
upstream kernel from http://www.kernel.org or one of the latest
vendor kernels from Red Hat, SuSE, or others.
The tg3 driver from the Broadcom package is almost identical to the
tg3 driver in the latest 2.6 upstream Linux kernel. It includes some
additional kernel compatible code to allow it to compile on older 2.6
and some 2.4 kernels. The version number is also similar but generally
has a one letter suffix at the end, (e.g. 3.55b) to distinguish it from
the in-kernel tg3 driver.
The next few sections on packaging, compiling, and installation apply
mostly to the Broadcom driver package only.
Limitations
===========
The current version of the driver has been tested on 2.4.x kernels starting
from 2.4.24 and all 2.6.x kernels. The driver may not compile on kernels
older than 2.4.24. Testing is concentrated on i386 and x86_64 architectures.
Only limited testing has been done on some other architectures such as
powerpc and sparc64.
Minor changes to some source files and Makefile may be needed on some
kernels.
Packaging
=========
To replace an older previously installed or in-kernel tg3 driver, follow
the instructions below.
The driver package from http://www.broadcom.com is released in two packaging
formats: source RPM and compressed tar formats. The file names for the two
packages are tg3-<version>.src.rpm and tg3-<version>.tar.gz respectively.
Identical source files to build the driver are included in both packages.
Installing Source RPM Package
=============================
The following are general guidelines for installing the driver.
1. Install the source RPM package:
rpm -ivh tg3-<version>.src.rpm
2. CD to the RPM path and build the binary driver for your kernel:
cd /usr/src/{redhat,OpenLinux,turbo,packages,rpm ..}
rpm -bb SPECS/tg3.spec
or
rpmbuild -bb SPECS/tg3.spec (for RPM version 4.x.x)
Note that the RPM path is different for different Linux distributions.
3. Install the newly built package (driver and man page):
rpm -ivh RPMS/<arch>/tg3-<version>.<arch>.rpm
<arch> is the architecture of the machine, e.g. i386:
rpm -ivh RPMS/i386/tg3-<version>.i386.rpm
Note that the --force option may be needed on some Linux distributions
if conflicts are reported.
The driver will be installed in the following path:
2.4.x kernels:
/lib/modules/<kernel_version>/kernel/drivers/net/tg3.o
2.6.x kernels:
/lib/modules/<kernel_version>/kernel/drivers/net/tg3.ko
4. Load the driver:
insmod tg3.o
or
insmod tg3.ko (on 2.6.x kernels)
or
modprobe tg3
5. To configure network protocol and address, refer to various Linux
documentations.
Building Driver From TAR File
=============================
The following are general guidelines for installing the driver.
1. Create a directory and extract the files:
tar xvzf tg3-<version>.tar.gz
2. Build the driver tg3.o (or tg3.ko) as a loadable module for the
running kernel:
cd src
make
3. Test the driver by loading it:
insmod tg3.o
or
insmod tg3.ko (on 2.6.x kernels)
or
insmod tg3
4. Install the driver:
make install
See RPM instructions above for the location of the installed driver.
5. To configure network protocol and address, refer to various Linux
documentations.
Driver Settings
===============
This and the rest of the sections below apply to both the in-kernel tg3
driver and the tg3 driver package from Broadcom.
Driver settings can be queried and changed using ethtool. The latest ethtool
can be downloaded from http://sourceforge.net/projects/gkernel if it is not
already installed. The following are some common examples on how to use
ethtool. See the ethtool man page for more information. ethtool settings do
not persist across reboot or module reload. The ethtool commands can be put
in a startup script such as /etc/rc.local to preserve the settings across a
reboot.
1. Show current speed, duplex, and link status:
ethtool eth0
2. Change speed, duplex, autoneg:
Example: 100Mbps half duplex, no autonegotiation:
ethtool -s eth0 speed 100 duplex half autoneg off
Example: Autonegotiation with full advertisement:
ethtool -s eth0 autoneg on
Example: Autonegotiation with 100Mbps full duplex advertisement only:
ethtool -s eth0 speed 100 duplex full autoneg on
3. Show flow control settings:
ethtool -a eth0
4. Change flow control settings:
Example: Turn off flow control
ethtool -A eth0 autoneg off rx off tx off
Example: Turn flow control autonegotiation on with tx and rx advertisement:
ethtool -A eth0 autoneg on rx on tx on
Note that this is only valid if speed is set to autonegotiation.
5. Show offload settings:
ethtool -k eth0
6. Change offload settings:
Example: Turn off TSO (TCP segmentation offload)
ethtool -K eth0 tso off
7. Get statistics:
ethtool -S eth0
8. Perform self-test:
ethtool -t eth0
Note that the interface (eth0) must be up to do all tests.
9. See ethtool man page for more options.
Driver Defaults
===============
Speed : Autonegotiation with all speeds advertised
Flow control : Autonegotiation with rx and tx advertised
MTU : 1500 (range 46 - 9000)
Some chips do not support jumbo MTUs bigger than
1500
Rx Ring Size : 200 (range 0 - 511)
Some chips are fixed at 64
Rx Jumbo Ring Size : 100 (range 0 - 255)
Not all chips support the jumbo ring, and some
chips that support jumbo frames do not use the
jumbo ring.
Tx Ring Size : 511 (range (MAX_SKB_FRAGS+1) - 511)
MAX_SKB_FRAGS varies on different kernels and
different architectures. On a 2.6 kernel for
x86, MAX_SKB_FRAGS is 18.
Coalesce rx usecs : 20 (range 0 - 1023)
Coalesce rx usecs irq : 20 (range 0 - 255)
Coalesce rx frames : 5 (range 0 - 1023)
Coalesce rx frames irq : 5 (range 0 - 255)
Coalesce tx usecs : 72 (range 0 - 1023)
Coalesce tx usecs irq : 20 (range 0 - 255)
Coalesce tx frames : 53 (range 0 - 1023)
Coalesce tx frames irq : 5 (range 0 - 255)
Coalesce stats usecs : 1000000 (aprox. 1 sec.)
Some coalescing parameters are not used or have
different defaults on some chips
MSI : Enabled (if supported by the chip and passed
the interrupt test)
TSO : Enabled on newer chips that support TCP segmentation
offload in hardware.
Unloading and Removing Driver
=============================
To unload the driver, use ifconfig to bring down all eth# interfaces opened
by the driver, then do the following:
rmmod tg3
Note that on 2.6 kernels, it is not necessary to bring down the eth#
interfaces before unloading the driver module.
If the driver was installed using rpm, do the following to remove it:
rpm -e tg3
If the driver was installed using make install from the tar file, the driver
tg3.o (or tg3.ko) has to be manually deleted from the system. Refer
to the section "Installing Source RPM Package" for the location of the
installed driver.
Driver Messages
===============
The following are the most common sample messages that may be logged in the file
/var/log/messages. Use dmesg -n <level> to control the level at which messages
will appear on the console. Most systems are set to level 6 by default. To see
all messages, set the level higher.
Driver signon:
-------------
tg3.c:v3.53c (Mar 13, 2006)
NIC detected:
------------
eth0: Tigon3 [partno(BCM95704CA40) rev 2002 PHY(5704)] (PCI:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:10:18:04:3e:64
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[763f0000] dma_mask[64-bit]
Link up and speed indication:
----------------------------
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
Link down indication:
--------------------
tg3: eth0: Link is down.
user@NAS:~/Schreibtisch/driver/tg3-3.58b$
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13938
|
Nichtskönner schrieb: Building Driver From TAR File
=============================
cd src
make
Zum Kompilieren hast Du kein src-Verzeichnis nach dem Entpacken. Hast Du das Richtige downloadet? BTW: Ich weiß nicht ob der kompilierte Treiber, für dein Ubuntu 14.04 brauchbar ist.
|