Sponsored Content
Full Discussion: OI 151 e1000g NIC problem
Operating Systems Solaris OI 151 e1000g NIC problem Post 302753203 by DustinT on Tuesday 8th of January 2013 08:56:47 AM
Old 01-08-2013
Can you post the make and model of your motherboard. If the NIC is on an addin card, can you post the details of that as well?

Unless your motherboard manufacturer is no longer in existence, it's likely you can find a BIOS update. Perhaps we can help you do that.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SuSE 8.1 NIC problem

i have just installed suse 8.1 on a third computer which has an Asus p4s8x with onboard NIC and sound. now, on install suse detected everything automatically with no probelm, however upon reboot the sound failed to load as well as the network card. /dev/eth* doesnt exist. i looked in the bios and... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

2. Solaris

Dual NIC problem

Hi, I have a problem with a server disconnecting from the network. This is a SUN box with dual NIC's running Solaris 8. We have a Nokia router that routes traffic but it's virtual address doesn't respond to pings. When the SUN box sends out a ping, if nothing comes back it will shut down... (5 Replies)
Discussion started by: m_smith
5 Replies

3. UNIX for Dummies Questions & Answers

nic problem

hello friends i am using x86 pc i can install solaris o/s but nic card is not deceting. i am not able see in file called /etc/path_to_inst. i did /touch reconfigu and devfsadm also. i used external nic card also realtech 8169d am using gigabyte mother board 775. (0 Replies)
Discussion started by: manoj123
0 Replies

4. IP Networking

Problem configuring NIC in DGUX

Old DG box Aviion PentiumPro running R4.20Mu06 being used to try to recreate Ingres db from backup tapes so machine has not been operational before and some of original files in /etc may have ben overwritten Unable to get NIC working Any pointers on how to go about configuring NIC :rolleyes: (0 Replies)
Discussion started by: lindab
0 Replies

5. Solaris

IPMP. Is this a NIC problem!!?

-- IPMP Groups -- Node Name Group Status Adapter Status --------- ----- ------ ------- ------ IPMP Group: hostname1.xx-xxxx.xxxi sc_ipmp1 Online ce5 Online IPMP Group: hostname1.xx-xxxx.xxxi ipmpgrp01... (2 Replies)
Discussion started by: FeNiCrC_Neil
2 Replies

6. Solaris

NIC problem

can anyone help me fix this? what command should I use to bring them back to "TRUE"? Interface Speed Duplex Autoneg --------- ----- ------ ------- ce0 100 Mbit/s FULL FALSE ce5 100 Mbit/s FULL ... (3 Replies)
Discussion started by: uuontario
3 Replies

7. Solaris

NIC detection problem in solaris

Hi, Hardware: Mother board: Asus P5G4IC-M LX On board NIC: PCIe Gigabite LAN Kernel Ver.: SunOS 5.10 Generic_141445-09 I've NIC detection problem in Solaris 10. When I was trying to install in x86 machine, it was not asking for any Network settings which means it couldn't find NIC. But... (7 Replies)
Discussion started by: vicky86ind
7 Replies

8. Solaris

e1000g.conf

Hi guys Beginning to get my hands dirty in the world of Solaris11. I've encountered a bump that I cannot seem to overcome with a server NIC interface? So I installed a VM Solaris11 machine at home to play with. Sun OS Solaris11 5.11 11.0 i86pc i386 My question is - is it enough to modify... (4 Replies)
Discussion started by: ru4n1
4 Replies

9. Red Hat

I want to tune NIC's rps, rfs and xps value. which NIC device should I modify.

Dear All I want tune my NIC's rps, rfs and xps value. In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1). Here is the question? Which device should I modify ? eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0) Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies

10. AIX

LPAR NIC Problem

On all our lpars we have our main interface set up and a backup network interface. On a number of our lpars those connections go to a down state for no apparent reason. They are still attached but they show up as "*en1" in netstat. Has anyone else come across this issue or know why an... (4 Replies)
Discussion started by: bsewen
4 Replies
AIBS(4) 						   BSD Kernel Interfaces Manual 						   AIBS(4)

NAME
aibs -- ASUSTeK AI Booster ACPI ATK0110 voltage, temperature and fan sensor SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device acpi device aibs Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5): acpi_load="YES" aibs_load="YES" DESCRIPTION
The aibs driver provides support for the voltage, temperature and fan sensors available through the ATK0110 ASOC ACPI device on ASUSTeK moth- erboards. The number of sensors of each type, as well as the description of each sensor, varies according to the motherboard. The driver supports an arbitrary set of sensors, provides descriptions regarding what each sensor is used for, and reports the current values as well as the supposed range specifications of each sensor's input as defined by the motherboard manufacturer through ACPI. The range specifications are as follows: o Voltage sensors have a lower and an upper range specification. o Temperature sensors have two upper specifications. o Fan sensors may either have only the lower specification, or, depending on the DSDT, one lower and one upper specification. Sensor readings and the range specifications are made available through the sysctl(3) interface, and can be monitored with sysctl(8). For example, on an ASUS V3-P5G965 barebone: > sysctl dev.aibs.0.{volt,temp,fan} dev.aibs.0.volt.0: 1192 850 1600 dev.aibs.0.volt.1: 3312 2970 3630 dev.aibs.0.volt.2: 5017 4500 5500 dev.aibs.0.volt.3: 12302 10200 13800 dev.aibs.0.temp.0: 28.0C 80.0C 95.0C dev.aibs.0.temp.1: 55.0C 60.0C 95.0C dev.aibs.0.fan.0: 878 600 7200 dev.aibs.0.fan.1: 0 700 7200 > sysctl -d dev.aibs.0.{volt,temp,fan} dev.aibs.0.volt: dev.aibs.0.volt.0: Vcore Voltage dev.aibs.0.volt.1: +3.3 Voltage dev.aibs.0.volt.2: +5 Voltage dev.aibs.0.volt.3: +12 Voltage dev.aibs.0.temp: dev.aibs.0.temp.0: CPU Temperature dev.aibs.0.temp.1: MB Temperature dev.aibs.0.fan: dev.aibs.0.fan.0: CPU FAN Speed dev.aibs.0.fan.1: CHASSIS FAN Speed Generally, sensors provided by the aibs driver may also be supported by certain other drivers or utilities that access the ISA / LPC or I2C / SMBus devices directly. The precise collection of aibs sensors is comprised of the sensors specifically utilised in the motherboard design, which may be supported through a combination of one or more physical hardware monitoring chips. The aibs driver, however, provides the following advantages when compared to the native hardware monitoring drivers or other utilities: o Sensor values from aibs are expected to be more reliable. For example, voltage sensors in many hardware monitoring chips can only sense voltage from 0 to 2 or 4 volts, and the excessive voltage is removed by the resistors, which may vary with the motherboard and with the voltage that is being sensed. In aibs, the required resistor factors are provided by the motherboard manufacturer through ACPI; in the native drivers, the resistor factors are encoded into the driver based on the chip manufacturer's recommendations. In essence, sensor values from aibs are very likely to be identical to the readings from the Hardware Monitor screen in the BIOS. o Sensor descriptions from aibs are more likely to match the markings on the motherboard. o Sensor range specifications are supported by aibs. The range specification is reported for each individual sensor as suggested by the motherboard manufacturer. For example, the threshold for the CPU temperature sensor is likely to be significantly higher than that for the chassis temperature sensor. o Support for newer chips in aibs. Newer chips may miss a native driver, but should be supported through aibs regardless. SEE ALSO
sysctl(3), acpi(4), sysctl(8) HISTORY
The aibs driver first appeared in OpenBSD 4.7, DragonFly 2.5, NetBSD 6.0 and FreeBSD 9.0. An earlier version of the driver, acpi_aiboost, first appeared in FreeBSD 7.0 and NetBSD 5.0. AUTHORS
The aibs driver was written for OpenBSD, DragonFly, NetBSD and FreeBSD by Constantine A. Murenin <cnst@FreeBSD.org>, Raouf Boutaba Research Group, David R. Cheriton School of Computer Science, University of Waterloo. An earlier version of the driver, named acpi_aiboost, was written for FreeBSD by Takanori Watanabe. BSD
April 4, 2010 BSD
All times are GMT -4. The time now is 02:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy