Here is one for the real Solaris aficionados on the site;
I have a T5240 and have to create an I/O domain with access to the serial port, in this case /dev/term/a and although I have been through the documentation I'm having some issues in identifying the device to assign.
What I have is;
The T5240 is on the older side having 2*6 Core CPU's each with 8 threads per core, where I have an issue - is that I don't actually see the serial device as assigned to either PCI bus. Of course it might just be that I'm being dumb!
Howto check if a ethernet interface is up?
It's impossible to determine via the ipaddress i have learned, or?
Can someone please give me a hint on howto do?
Environment == Linux x86 GNU GCC.
:D
regards
Esaia (2 Replies)
Given the interfaces on a firewall:
eth0 Link encap:Ethernet HWaddr 02:40:67:34:F5:47
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
eth1 Link encap:Ethernet HWaddr 86:23:98:45:35:56
inet addr:123.45.240.69 Bcast:255.255.255.255 ... (2 Replies)
Given a new Solaris box, with a fresh, unconfigured install on it, how does one figure out what kind of network interface it has (bge,le, hme, etc)? (8 Replies)
Hello,
I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
This is my situation
DOS pc serial cable (sl0) Linux Pc eth1
192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router)
I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface.
... (3 Replies)
Hi,
I´ve given only this info to configure a network interface : "port 1 PCI 4"
I´ve been searching for any kind of relationship in the system which allow me to find the etc that must be configured...
Please, could anybody help me?
rhxx:#/root# lspci |grep -i "PCI BRIDGE"
00:01.0 PCI... (0 Replies)
Hi
Had an old ML590 with RS232 serial card that stopped working (spindle that advance ribbon broke) so I purchased a working used on ebay.
Printer powers up and seems fine. Put serial board from old printer in working ebay unit but no printing happens.
Does anyone know if there are any... (0 Replies)
Hi
Had an old ML590 with RS232 serial card that stopped working (spindle that advance ribbon broke) so I purchased a working used on ebay.
Printer powers up and seems fine. Put serial board from old printer in working ebay unit but no printing happens.
Does anyone know if there are any... (3 Replies)
Hey guys, I want to use a a quick bash script/command to determine what network interface is connected to the internet so I can pipe it out to become a variable, in order so the user does not have to manually type it in each time or have to 'hardcode' the variable into the script.
I know about... (6 Replies)
I'm looking for driver for SunSAI/P 3.0 (Serial Asynchronous Interface) card X2156A for Solaris. It used to be on sun-solve, but I fail to find it on the Oracle site. Any help would be very appreciated! (1 Reply)
Discussion started by: Ira28
1 Replies
LEARN ABOUT NETBSD
hptide
HPTIDE(4) BSD Kernel Interfaces Manual HPTIDE(4)NAME
hptide -- Triones/Highpoint IDE disk controllers driver
SYNOPSIS
hptide* at pci? dev ? function ? flags 0x0000
DESCRIPTION
The hptide driver supports the Triones/Highpoint HPT366, HPT370, HPT370A, HPT372 and HPT374 IDE controllers, and provides the interface with
the hardware for the ata(4) driver.
The 0x0002 flag forces the hptide driver to disable DMA on chipsets for which DMA would normally be enabled. This can be used as a debugging
aid, or to work around problems where the IDE controller is wired up to the system incorrectly.
SEE ALSO ata(4), atapi(4), intro(4), pci(4), pciide(4), wd(4), wdc(4)BUGS
The timings used for the PIO and DMA modes for controllers listed above are for a PCI bus running at 30 or 33 MHz. This driver may not work
properly on overclocked systems.
BSD October 8, 2003 BSD