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 voltage, temperature, and fan sensor SYNOPSIS
aibs* at acpi? DESCRIPTION
The aibs driver provides support for voltage, temperature, and fan sensors available as an ACPI device on ASUSTeK motherboards. 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 whether each sen- sor is within the specifications as defined by the motherboard manufacturer through ACPI. The aibs driver supports envsys(4) sensor states as follows: o Voltage sensors can have a state of 'valid', 'critunder', or 'critover'; temperature sensors can have a state of 'valid', 'warnover', 'critover', or 'invalid'; and fan sensors can have a state of 'valid', 'warnunder', or 'warnover'. o Temperature sensors that have a reading of 0 are marked 'invalid', whereas all other sensors are always assumed valid. o Voltage sensors have a lower and an upper limit, 'critunder' and 'critover', temperature sensors have two upper limits, 'warnover' and 'critover', whereas fan sensors may either have only the lower limit 'warnunder', or, depending on the vendor's ACPI implementation, one lower and one upper limit, 'warnunder' and 'warnover'. Sensor values and limits are made available through the envsys(4) interface, and can be monitored with envstat(8). For example, on an ASUS V3-P5G965 barebone: $ envstat -d aibs0 Current CritMax WarnMax WarnMin CritMin Unit Vcore Voltage: 1.152 1.600 0.850 V +3.3 Voltage: 3.312 3.630 2.970 V +5 Voltage: 5.017 5.500 4.500 V +12 Voltage: 12.302 13.800 10.200 V CPU Temperature: 27.000 95.000 80.000 degC MB Temperature: 58.000 95.000 60.000 degC CPU FAN Speed: 878 7200 600 RPM CHASSIS FAN Speed: 0 7200 700 RPM Generally, sensors provided by the aibs driver may also be supported by a variety of other drivers, such as lm(4) or itesio(4). The precise collection of aibs sensors is comprised of the sensors specifically utilised in the motherboard design, which may be supported through a com- bination of one or more physical hardware monitoring chips. The aibs driver, however, provides the following advantages when compared to the native hardware monitoring drivers: 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 states are supported by aibs. The state is reported based on the acceptable range of values for each individual sensor as sug- gested 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. As a result, sensor readings from the actual native hardware monitoring drivers are redundant when aibs is present, and may be ignored as appropriate. Whereas on some supported operating systems the native drivers may have to be specifically disabled should their presence be judged unnecessary, on others the drivers like lm(4) are not probed provided that acpi(4) is configured and the system potentially supports the hardware monitoring chip through ACPI. SEE ALSO
acpi(4), envsys(4), envstat(8) HISTORY
The aibs driver first appeared in OpenBSD 4.7, DragonFly 2.4.1 and NetBSD 6.0. An earlier version of the driver, named aiboost, first appeared in FreeBSD 7.0 and NetBSD 5.0. AUTHORS
The aibs driver was written for OpenBSD, DragonFly BSD, and NetBSD by Constantine A. Murenin <http://cnst.su/>, Raouf Boutaba Research Group, David R. Cheriton School of Computer Science, University of Waterloo. Jukka Ruohonen <jruohonen@iki.fi> later reworked and adjusted the driver to support new ASUSTeK motherboards. The earlier version of the driver, aiboost, was written for FreeBSD by Takanori Watanabe and adapted to NetBSD by Juan Romero Pardines. BSD
June 12, 2011 BSD
All times are GMT -4. The time now is 07:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy