Re: What does the output of prtconf mean

From: Morten Larsen (nospam_at_blackhat.dk)
Date: 02/12/05 

Date: Sat, 12 Feb 2005 01:06:32 +0100

1. If you want to find out what kind of adapter you have, try the
prtdiag command.

2. Try using the format command to find out if it can see any
disks/LUN's (other than the "local" disks), you may have to run devfsadm
first.

3. From the prtconf man page:
The driver not attached message means that no driver is
currently attached to that instance of the device. In gen-
eral, drivers are loaded and installed (and attached to
hardware instances) on demand, and when needed, and may be
uninstalled and unloaded when the device is not in use.

Shashank Khanvilkar wrote:
>
>
> Hi,
> Any help is appreciated.
> We have a sun4800 server and it has this Fiber channel adater card,
> which is used to connect to a storage server.
> 1. How do i find out the make and model of the Fiber channel adapter
> card, without opening the sun box.
>
> 2. How do i make sure that it is working as expected.
>
> 3. Why does the prtconf output shows "driver not attached"?
>
> Thanks Shashank
>
>
>
> # prtconf
> System Configuration: Sun Microsystems sun4u
> Memory size: 8192 Megabytes
> System Peripherals (Software Nodes):
>
> SUNW,Sun-Fire
> openprom (driver not attached)
> client-services (driver not attached)
> aliases (driver not attached)
> options, instance #0
> chosen (driver not attached)
> packages (driver not attached)
> deblocker (driver not attached)
> disk-label (driver not attached)
> terminal-emulator (driver not attached)
> obp-tftp (driver not attached)
> SUNW,builtin-drivers (driver not attached)
> ufs-file-system (driver not attached)
> memory (driver not attached)
> virtual-memory (driver not attached)
> failsafe (driver not attached)
> sgcn, instance #0
> todsg (driver not attached)
> ssm, instance #0
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #0
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #1
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #2
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #3
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #4
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #5
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #6
> SUNW,UltraSPARC-III+ (driver not attached)
> memory-controller, instance #7
> pci, instance #0
> bootbus-controller, instance #0
> pci, instance #0
> pci108e,1000 (driver not attached)
> SUNW,hme, instance #0
> SUNW,isptwo, instance #0
> sd (driver not attached)
> st (driver not attached)
> sd, instance #0
> sd, instance #1 (driver not attached)
> sd, instance #2 (driver not attached)
> sd, instance #3 (driver not attached)
> sd, instance #4 (driver not attached)
> sd, instance #5 (driver not attached)
> sd, instance #6 (driver not attached)
> sd, instance #7 (driver not attached)
> sd, instance #8 (driver not attached)
> sd, instance #9 (driver not attached)
> sd, instance #10 (driver not attached)
> sd, instance #11 (driver not attached)
> sd, instance #12 (driver not attached)
> sd, instance #13 (driver not attached)
> sd, instance #14 (driver not attached)
> pci, instance #1
> SUNW,qlc (driver not attached)
> fp (driver not attached)
> disk (driver not attached)
> pci, instance #2
> pci, instance #3
> pci, instance #4
> bootbus-controller, instance #1
> pci, instance #1
> pci108e,1000 (driver not attached)
> SUNW,hme, instance #1
> SUNW,isptwo, instance #1
> sd (driver not attached)
> st (driver not attached)
> sd, instance #15
> sd, instance #16 (driver not attached)
> sd, instance #17 (driver not attached)
> sd, instance #18 (driver not attached)
> sd, instance #19 (driver not attached)
> sd, instance #20 (driver not attached)
> sd, instance #21
> sd, instance #22 (driver not attached)
> sd, instance #23 (driver not attached)
> sd, instance #24 (driver not attached)
> sd, instance #25 (driver not attached)
> sd, instance #26 (driver not attached)
> sd, instance #27 (driver not attached)
> sd, instance #28 (driver not attached)
> sd, instance #29 (driver not attached)
> pci, instance #5
> SUNW,qlc (driver not attached)
> fp (driver not attached)
> disk (driver not attached)
> pci, instance #6
> pci, instance #7
> pseudo, instance #0 

-- 
Morten Larsen (nospam@blackhat.dk)
*** Quantum Mechanics: The Dreams of Which Stuff is Made ***

Relevant Pages

  • PATCH: docs for updated sk98 from vendor
    ... +Marvell Yukon/SysKonnect SK-98xx Gigabit Ethernet Adapter family driver for LINUX ... the driver is integrated in the linux kernel source. ... both link partners are allowed to send PAUSE frames ...
    (Linux-Kernel)
  • Re: [RFC][PATCH] SPI subsystem
    ... Are you expecting the adapter ... > driver to handle the fact that its transfer routine could be called ... > a message or another CS line which is really a GPO pin used for register ... For example a char LCD with SPI interface ...
    (Linux-Kernel)
  • Re: Ataptec SCSI card problem
    ... I tried to install this card debian 4.0, ubuntu 7.10, Fedora Core 8, ... Slackware 12 and I have always the same message from scsi card. ... what it looks like to me, the problem is to be found in the driver, rather ... SCSI adapter family, which means that they can be used in two modes, i.e. ...
    (comp.os.linux.hardware)
  • [PATCH 2/10] cxgb3 - main source file
    ... the Chelsio T3 network adapter driver. ... * This file is part of the Chelsio T3 Ethernet driver for Linux. ... * ones for any additional queues. ... +static int init_smt ...
    (Linux-Kernel)
  • Re: Wifi key ?
    ... In fact we can't redesign our hardware and we already give the possibility to get an USB key for our customer! ... The only way i can use is to find an other stick with windows CE driver. ... If not, forget USB and look for another method of connecting the WiFi to your hardware, SDIO might be possible, although the only SDIO adapter that I was aware of went away, too. ...
    (microsoft.public.windowsce.embedded.vc)
Loading