Sponsored Content
Special Forums Hardware Atheros AR8151 LAN not working Post 302550318 by cbstryker on Thursday 25th of August 2011 09:58:07 AM
Old 08-25-2011
Atheros AR8151 LAN not working

Hi Everyone,

First time here on Unix.com forums. I've been trying to install Nexenta on a new server machine that I built. The MotherBoard is a Gigabit GA-G41MT-S2P and the LAN chip is an AR8151.

I understand that the AR8151 isn't natively supported by the Solaris kernel, but I'm wondering if there's another way of getting it to work. I have a few old USB to Ethernet adapters that I can plug in to get a network connection, but they are only 10/100. But with using the adapter is it possible to download something to enable the on-board LAN controller?
 

9 More Discussions You Might Find Interesting

1. Solaris

How to configure private LAN and coporate LAN on the same machine-Solaris10

Hi , I am trying to configure a private LAN and corporate LAN on the same machien on Solaris 10. How can I achieve this? Thanks (1 Reply)
Discussion started by: deedee
1 Replies

2. Linux

lan help

iam using open suse 10.3 in dual boot with windows internet is through Lan(ethernet) in windows by entering below data in Lan properties net is coming the information is bellow ip 10.2.45.67 subnet 255.255.0.0 default gate way 10.1.1.4... (3 Replies)
Discussion started by: seshumohan
3 Replies

3. IP Networking

Local Lan, no-ip directed DNS forward, surf within lan

Hi, We have a website running on a local centos 5.4 surfer, static IP. The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server. My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine. However, we cannot see... (3 Replies)
Discussion started by: lawstudent
3 Replies

4. Red Hat

Different hostnames with reboot while lan cable, no lan cable

I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable Reboot with lan cable: The hostname is ubunut Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies

5. Ubuntu

Ubuntu 10.10 LAN connection stopped working...

Well this is weird. I restarted my dual boot Win7/Ubuntu 10.10 from ubuntu to windows. Everything was working fine and windows is always connecting properly to my lan. After restarting back into Ubuntu, all of a sudden I can't connect to my network. It looks as if its trying to connect through... (15 Replies)
Discussion started by: zixzix01
15 Replies

6. IP Networking

lan

how can i make lan between two or more computers having linux fedora as os...? (1 Reply)
Discussion started by: Ravi Kumar Mish
1 Replies

7. Fedora

about lan

how can i lan between two or more computers having linux fedora as os? (1 Reply)
Discussion started by: Ravi Kumar Mish
1 Replies

8. IP Networking

Talk Not Working over LAN or on one computer

I have talk installed: yum install talk talk-server And I have /etc/xinetd.d/talk set to disabled and /etc/xinetd.d/ntalk set to enabled I also have opened port 518/udp on server and laptop and enabled xinetd.service sudo systemctl enable xinetd.service sudo systemctl start... (4 Replies)
Discussion started by: Benji Wiebe
4 Replies

9. Hardware

Atheros AR9271

Hi!! It's possible instal the Atheros AR9271 on Solaris? I never find the driver to Linux or Unix. (1 Reply)
Discussion started by: _rehad_
1 Replies
TL(4)							   BSD Kernel Interfaces Manual 						     TL(4)

NAME
tl -- Texas Instruments ThunderLAN Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device tl Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_tl_load="YES" DESCRIPTION
The tl driver provides support for PCI Ethernet adapters based on the Texas Instruments ThunderLAN Ethernet controller chip. The ThunderLAN controller has a standard MII interface that supports up to 32 physical interface devices (PHYs). It also has a built-in 10baseT PHY hardwired at MII address 31, which may be used in some 10Mbps-only hardware configurations. In 100Mbps configurations, a National Semiconductor DP83840A or other MII-compliant PHY may be attached to the ThunderLAN's MII bus. If a DP83840A or equivalent is available, the ThunderLAN chip can operate at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes. The ThunderLAN's built-in PHY and the DP83840A also support autonegotiation. The tl driver supports the following media types: autoselect Enable autoselection of the media type and options. Note that this option is only available on those PHYs that support autonegotiation. Also, the PHY will not advertise those modes that have been explicitly disabled using the following media options. 10baseT/UTP Set 10Mbps operation 100baseTX Set 100Mbps (Fast Ethernet) operation 10base5/AUI Enable AUI/BNC interface (useful only with the built-in PHY). The tl driver supports the following media options: full-duplex Force full duplex operation half-duplex Force half duplex operation. hw-loopback Enable hardware loopback mode. Note that the 100baseTX media type is only available if supported by the PHY. For more information on configuring this device, see ifconfig(8). HARDWARE
The tl driver supports Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large number of Compaq PCI Ethernet adapters. Also supported are: o Olicom OC-2135/2138 10/100 TX UTP adapter o Olicom OC-2325/OC-2326 10/100 TX UTP adapter o Racore 8148 10baseT/100baseTX/100baseFX adapter o Racore 8165 10/100baseTX adapter The tl driver also supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq Deskpro desktop machines including: o Compaq Netelligent 10 o Compaq Netelligent 10 T PCI UTP/Coax o Compaq Netelligent 10/100 o Compaq Netelligent 10/100 Dual-Port o Compaq Netelligent 10/100 Proliant o Compaq Netelligent 10/100 TX Embedded UTP o Compaq Netelligent 10/100 TX UTP o Compaq NetFlex 3P o Compaq NetFlex 3P Integrated o Compaq NetFlex 3P w/BNC DIAGNOSTICS
tl%d: couldn't map memory A fatal initialization error has occurred. tl%d: couldn't map interrupt A fatal initialization error has occurred. tl%d: device timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). tl%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring. tl%d: no memory for tx list The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. SEE ALSO
arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8) HISTORY
The tl device driver first appeared in FreeBSD 2.2. AUTHORS
The tl driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BSD
July 16, 2005 BSD
All times are GMT -4. The time now is 08:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy