My P6 server is with dual vio servers. From the below output we could see that cd devices(cd0 and cd1) has been mapped to the vio client named prdsapfi1.
When we execute "lsdev -Cc cdrom" in prdsapfi1 there are 2 cd devices named cd0 and cd1 showing up in available state.
My question is how to find out if cd0 showing up in prdsapfi1 has been coming from vioprd01p or vioprd01i?
Hi,
I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160).
During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Trying to get my unix system to recognize an optical drive, it was delivered to us, so we assumed it worked, in the 2 years since no one ever has used it, we want to now. However, even running probe-scsi-all doesn't bring up that drive. It's a scsi address of 3, at the end of the chain, all... (1 Reply)
hi folks here is my case
Storage XP24K
Business copy setup
OS Solaris 10
Verital 4.1
Business copy is running between a production server and backup server using xp24k
when the disk groups are imported back on backup server after BC from the prduction server
following error is reported... (0 Replies)
Hi guys,
I have not connected optical cable to the Dual port HBA before. My integrator used to do that for me all the time. Can someone explain to me how can I physically connect optical cable to the HBA port in P570.
The optical cable has two connectors and right now the HBA port has just a... (7 Replies)
Not really a newbie, but I have a strange problem and I'm not sure how to further troubleshoot it.
I have to log out of a virtual terminal by typing exit, then exit again as in:
woodnt@toshiba-laptop ~ $ exit
logout
woodnt@toshiba-laptop ~ $ exit
logout
I DON'T have to do this when I'm... (1 Reply)
hello,
someone gave me a set of electronic gadgets 'Brookstone' which has mini optical mouse. This mouse label doesn't have model or etc. Mouse does not work properly i.e. pointer is moving right but left/right buttons work opposite and not always could open or close controls.
I suggest it might... (3 Replies)
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Hi All,
Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines?
Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies
LEARN ABOUT DEBIAN
lsdev
LSDEV(8) Linux System Manual LSDEV(8)NAME
lsdev - display information about installed hardware
SYNOPSIS
lsdev
DESCRIPTION
lsdev gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.
OPTIONS
None.
FILES
/proc/interrupts
IRQ channels.
/proc/ioports
I/O memory addresses.
/proc/dma
DMA channels.
BUGS
lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files sometimes use
different names for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
`keyboard' in /proc/interrupts. This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).
The program does however try to match lines by stripping anything after a space or open parenthesis from the name, so that e.g. the
`serial' lines from /proc/interrupts match the `serial(set)' lines from /proc/ioports. This attempt at DWIM might be considered a bug in
itself.
This program only shows the kernel's idea of what hardware is present, not what's actually physically available.
SEE ALSO procinfo(8).
AUTHOR
Sander van Malssen <svm@kozmix.cistron.nl>
3rd Release 1998-05-31 LSDEV(8)