Sponsored Content
Operating Systems SCO Set NIC correctly , but the network does not work Post 302875555 by jgt on Tuesday 19th of November 2013 08:24:51 PM
Old 11-19-2013
If you have a valid serial number and activation key, you can/should upgrade to 5.0.6. You can do this before making the image file and as an update install so no data should be lost.
When Intel introduced the Pentium 4, they moved control of the processor temperature from the CMOS/microcode to the operating system. SCO did not incorporate this change into any releases older than 5.0.6.
In 5.0.4 SCO made a change to the custom file format. Any VOL.000.000 files that work with 5.0.4 and newer will not work with 5.0.0 thru 5.0.3. This fact will make finding drivers much more difficult.
This User Gave Thanks to jgt For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

why the PATH can not be set correctly?

I'm using Linux-Mandrake 8.0 in my laptop. After I logged in as a "root", I added a new path in my .bashrc file (I use bash shell). Then I can observe it has been set correctly by typing echo $PATH. But, when I log in again as a personal account, not "root", then I open my bash shell, and type... (5 Replies)
Discussion started by: yishen
5 Replies

2. UNIX for Dummies Questions & Answers

Couldn't set locale correctly

When a user connects via ssh to one of out Sun V120 boxes the following message is displayed. "couldn't set locale correctly" The .profile has the following line # @(#)local.profile 1.6 98/02/06 SMI stty istrip stty erase ^H So I put a set -x in the .profile and re sourced it and... (1 Reply)
Discussion started by: mattd
1 Replies

3. SuSE

vsft doesn't work correctly

I install vsftpd server on 2 SUSE 10.2 servers. The first works perfectly, but the second doesn't work how I expect. The second works only over local network and doesn't over internet. The vsftpd.conf and ../xinetd.d/vsftpd are the same in 2 servers. The only different was when I threw to log in... (1 Reply)
Discussion started by: zhivko.neychev
1 Replies

4. Solaris

Couldn't set locale correctly

hi All, I'm using sun OS 5.10. All locales are set to en_US.ISO8859-1 in /etc/profile/init file. I'm using one functional user.When I tried to "sesu - functionalUser",its giving me error like "Couldn't set locale correctly".In functional user profile i'm tring to set locales to en_US.After... (1 Reply)
Discussion started by: Kathraji
1 Replies

5. Solaris

Couldn't set locale correctly

Hello, I have a recently configured machine that when log into it as a user or remotely as root it displays "Couldn't set locale correctly" When I type locale it displays the below which is wrong compared to other machines LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C"... (7 Replies)
Discussion started by: Mr Pink
7 Replies

6. Programming

Cannot get dbx to work correctly with a running process

Hi everyone, I've been struggling with this for a few weeks now. I'm trying to debug a running process with dbx on an AIX box. The command I'm using is 'dbx -a <pid> core' There is a function I can perform in my application that crashes this process, but it does not show up as crashed in... (0 Replies)
Discussion started by: ctote
0 Replies

7. Solaris

LC_ALL & LANG are set OK, but others couldn't set locale correctly.

Hi, I have a Solaris (SunOS 5.10) installed, by default with the en_AU.UTF-8 locale. I want to change it to en_US.UTF-8 With AU, I have no issues whatsoever, so I installed the language package and now locale -a shows "en_US.UTF-8". Problem is even with LC_ALL set in etc/default/init, the... (2 Replies)
Discussion started by: asdfg
2 Replies

8. UNIX for Advanced & Expert Users

Libvirt does not work correctly anymore on my gentoo

Hi, Since a year my libvirtd does not work anymore on my Gentoodesktop. In the meantime a used virtualbox. But I would like to have back libvirt. The problem was after libvirt should not only work with root privileges. I deinstalled all things with libvirt an kvm. I removed all things from /var... (4 Replies)
Discussion started by: darktux
4 Replies

9. Gentoo

LDAP-Auth does not work correctly with systemd

Hi, since the upgrade to Gnome 3.6 (now i have 3.8) the authentication over LDAP stops working. The whole machine does not start anymore. The machine boot, but no gdm and no X. I can login, with root, but then the tty hangs. When i look at ttyF12 i see a lot of systemd service the runs random,... (1 Reply)
Discussion started by: darktux
1 Replies

10. Shell Programming and Scripting

Why does this awk script not work correctly?

I have a large database with English on the left hand side and Indic words on the left hand. It so happens that since the Indic words have been entered by hand, there are duplicates in the entries. The structure is as under: English headword=Indic gloss,Indic gloss A small sample will... (6 Replies)
Discussion started by: gimley
6 Replies
PCN(4)							   BSD Kernel Interfaces Manual 						    PCN(4)

NAME
pcn -- AMD PCnet/PCI Fast Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device pcn Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_pcn_load="YES" DESCRIPTION
The pcn driver provides support for PCI Ethernet adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Ethernet controller chips. Supported NIC's include the Allied Telesyn AT-2700 family. The PCnet/PCI chips include a 100Mbps Ethernet MAC and support both a serial and MII-compliant transceiver interface. They use a bus master DMA and a scatter/gather descriptor scheme. The AMD chips provide a mechanism for zero-copy receive, providing good performance in server environments. Receive address filtering is provided using a single perfect filter entry for the station address and a 64-bit multicast hash table. The pcn driver supports the following media types: autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to rc.conf(5). 10baseT/UTP Set 10Mbps operation. The ifconfig(8) mediaopt option can also be used to select either 'full-duplex' or 'half-duplex' modes. 100baseTX Set 100Mbps (Fast Ethernet) operation. The ifconfig(8) mediaopt option can also be used to select either 'full-duplex' or 'half-duplex' modes. The pcn driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The pcn driver supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips: o AMD Am79C971 PCnet-FAST o AMD Am79C972 PCnet-FAST+ o AMD Am79C973/Am79C975 PCnet-FAST III o AMD Am79C976 PCnet-PRO o AMD Am79C978 PCnet-Home o Allied-Telesis LA-PCI DIAGNOSTICS
pcn%d: couldn't map ports/memory A fatal initialization error has occurred. pcn%d: couldn't map interrupt A fatal initialization error has occurred. pcn%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (e.g. a cable fault). pcn%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring. pcn%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. pcn%d: chip is in D3 power state -- setting to D0 This message applies only to adapters which support power management. Some operating sys- tems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configur- ing it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a warm boot to have the device properly configured. Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting FreeBSD, the card should be configured correctly. SEE ALSO
arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8) AMD PCnet/FAST, PCnet/FAST+ and PCnet/Home datasheets, http://www.amd.com. HISTORY
The pcn device driver first appeared in FreeBSD 4.3. AUTHORS
The pcn driver was written by Bill Paul <wpaul@osd.bsdi.com>. BSD
January 31, 2006 BSD
All times are GMT -4. The time now is 07:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy