Sponsored Content
Full Discussion: second tape drive on SCO 505
Top Forums UNIX for Dummies Questions & Answers second tape drive on SCO 505 Post 52306 by franruiz on Tuesday 15th of June 2004 01:11:46 PM
Old 06-15-2004
If no one has an answer or encoutered the same problem, can someone suggest a back up device with capacity for 20 gig that will work on a Compaq proliant 1600r runing SCO 505.
 

8 More Discussions You Might Find Interesting

1. IP Networking

Roteamento No Sco 505

Right now, i have an SCO 505 with IP, GATEWAY e MASK configured. I have one router that is my gateway. The SCO is able to connect to all of the local computers, including the router. However, i´m not unable to ping anything that is not local with SCO. I believe I tried setting the... (1 Reply)
Discussion started by: Danielnr
1 Replies

2. UNIX for Advanced & Expert Users

Tape Drive SCO 5.0.7

Hi guys I had a system running 5.0.6 , we upgraded it to 5.0.7 everything was fine till i try to do a test backup. The error was cannot open (cannot open /dev/xct0 no such file or directory)what i did was, removed the tape , reboot the system and the try to install it again, but its... (2 Replies)
Discussion started by: josramon
2 Replies

3. UNIX for Dummies Questions & Answers

vncserver on SCo 505

I have installed vnc on my SCO 505 box. its running fin, but when I start a session and connect to it from my win machine I do get an Xsession but I only get an xterm and thats it. I know my settings are in my //.vnc/xstartup file but what exactly am I supposed to see there. will some one send... (3 Replies)
Discussion started by: franruiz
3 Replies

4. SCO

Tape drive issues with SCO 5.0.5!!!

Hi Don't know if anyone will be able to help, but we're currently having problems with our external tape drive on our SCO server. If I try the following command for instance, "tar cvf /dev/rStp0", the tape drive jumps into action for a while, then comes back with the error "tar: cannot open:... (3 Replies)
Discussion started by: mattingg
3 Replies

5. UNIX for Dummies Questions & Answers

SCO 5.0.5 Tape Drive errors

hi guys, I.m trying to remove and add a new tape drive by using the mkdev tape command and when i try to update the Kernel this is what i'm getting, i386ld: Symbol Sdsk_no_tag in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/blad/s pace.o is multiply defined. First defined in... (0 Replies)
Discussion started by: josramon
0 Replies

6. SCO

SCO hard drive with data - No SCO computer

Situation - i have an IDE hard drive from server apparently running SCO last used in 2003. No access to computer it was formerly in. I need to access the drive to pull off data files from a billing/scheduling program. I have no SCO machine or access to one atm. Have some limited Linux... (3 Replies)
Discussion started by: lordlars1
3 Replies

7. SCO

SCO Openserver Release 5 and HP VS160 Tape Drive

Hi, Does anyone know if a HP VS160 Tape drive will work with SCO Openserver Release 5? If so what driver would it use? alad, cha? Thanks John (3 Replies)
Discussion started by: jfd7000
3 Replies

8. SCO

SCO 5.0.7 Tape Drive swap

Our tape drive died and I installed a newer Quantum DAT72 drive in it's place with the same SCSI ID. It still works, but with one major flaw, the system will lock up if I try to upgrade BackupEDGE or view NFS settings in scoadmin. I get a Transition to ready failure on ha=0* message when the... (4 Replies)
Discussion started by: psytropic
4 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 01:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy