02-11-2011
and a patch update with latest patch cluster didn't fix the problem?
10 More Discussions You Might Find Interesting
1. SCO
Can i change the password on the SCO GUI interface login page and if so how?
When I try to login it just goes right back to the login screen. If anyone has any suggestions, please reply. :confused: (3 Replies)
Discussion started by: qphillips
3 Replies
2. Solaris
Hi experts,
I've installed Solaris 8 to Sunfire V480. After installation I only could login to the server using CLI command. Can you show me how to start the login GUI? I use standard SUN graphic monitor and keyboard.
Thanks in advanced.
VN (26 Replies)
Discussion started by: vntiger
26 Replies
3. Linux
hi
iam installed mandriva spring 2009
iam unble to login into gui using root
how to enable it
where the settings are stored (5 Replies)
Discussion started by: seshumohan
5 Replies
4. Solaris
I have 2 queries:
1.how do we monitor failed GUI logins...? I think the /var/adm/loginlog will log
only failed logins happened at /dev/console and virtual terminals..
2.How to use cron scheduler to display a message when a user is working in GUI Terminal window irrespective of in which... (1 Reply)
Discussion started by: saagar
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
When I installed Ubuntu on my laptop, I had chosen "automatic login" . So i was not asked ofr username and password everytime I switched on. I later wanted to change the settings. So I went to systems-->administration-->login window-->security. There I disabled automatic login and I reboot the... (3 Replies)
Discussion started by: vishwamitra
3 Replies
6. Fedora
Hi all,
I am able to login via putty to a fedora 10 workstation.
But when i try to login via physical screen connected to workstation, it just gives me a blank screen and i cant see any options to enter username and passwd. How do i get the physical GUI to work.
$ who -r
... (4 Replies)
Discussion started by: lramsb4u
4 Replies
7. Solaris
Solaris machine is at # prompt not able to login in GUI mode :
I want to login solaris server in GUI mode from # prompt.
---------- Post updated 12-30-11 at 11:36 AM ---------- Previous update was 12-29-11 at 02:23 PM ----------
Hi,
Please send me some guidelines regarding this....
as... (2 Replies)
Discussion started by: sunray
2 Replies
8. UNIX for Dummies Questions & Answers
I am not too new with linux. Since I installed a new version (2011) of Mandriva, I am unable to login via the gui (I'm currently using the live version of the same dvd free with Linux Format mag). I can login from a console as it has picked up the previous version's /home, but when I try to login... (2 Replies)
Discussion started by: richardmellersh
2 Replies
9. Shell Programming and Scripting
hii all,
I am unable to login into GUI mode in solaris 10. It is only prompting me to command mode credentials not going further to GUI mode.. Please help..
Thanks & regards,
Bhagi (3 Replies)
Discussion started by: bhargav90
3 Replies
10. Solaris
I just got moved to a new office building, and as I was unpacking my stuff I saw an odd tower PC in the nearby recycling heap. It turned out to be a Sun Ultra 10 Elite3D workstation, complete with keyboard, mouse, and monster-sized CRT with the wacky Sun video cable.
I just set everything up and... (4 Replies)
Discussion started by: wowbobwow
4 Replies
ISP(4) BSD Kernel Interfaces Manual ISP(4)
NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters
SYNOPSIS
isp* at pci? dev? function? (PCI)
isp* at sbus? slot ? offset ? (SBus)
scsibus* at isp?
DESCRIPTION
This driver provides access to SCSI or FibreChannel devices.
SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, and LVD (for the ISP1080 and ISP1280),
Fibre Channel support uses FCP SCSI profile for FibreChannel. and uses Class 3 connections only. Support is available for Public and Pri-
vate loops. Command tagging is supported for all (in fact, FibreChannel requires tagging).
CONFIGURATION
An optional flags 0x80 appended to the above isp* declarations will disable the download of driver firmware, which means you use whatever
firmware is running on the card. If no firmware is running on the card, the driver cannot operate the card.
An optional flags 0x40 appended to the above isp* declarations (can be OR'd in with the other config flags option) will keep the driver from
looking at device or bus NVRAM settings (this is in case NVRAM is just wrong and you have the card in a platform where it is inconvenient to
change NVRAM settings on the card).
HARDWARE
Supported cards include:
ISP1000
SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards.
PTI SBS440
Performance Technology ISP1000 variants.
ISP1020
Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards.
ISP1040
Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards.
PTI SBS450
Performance Technology ISP1040 variants.
Qlogic 1240
Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards.
Qlogic 1080
Qlogic 1280 LVD Ultra2 Wide PCI cards.
Qlogic 1280
Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards.
Qlogic 2100
Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop
Qlogic 2102
Qlogic Dual Loop 2100A Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2200
Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2202
Qlogic 2200 Dual Bus Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2204
Qlogic 2200 Quad Bus Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2300
Qlogic 2300 2-Gigabit Optical Fibre Channel PCI cards.
Qlogic 2312
Qlogic 2300 2-Gigabit Dual Channel Optical Fibre Channel PCI cards.
PTI SBS470
Performance Technology ISP2100 variants.
Antares P-0033
Antares Microsystems ISP2100 variants.
Qlogic 2400
Qlogic 2400 4-Gigabit Optical Fibre Channel PCI cards.
Qlogic 2500
Qlogic 2500 8-Gigabit Optical Fibre Channel PCI cards.
SEE ALSO
cd(4), intro(4), scsi(4), sd(4), st(4)
AUTHORS
The isp driver was written by Matthew Jacob for NASA/Ames Research Center.
BUGS
The driver currently ignores some NVRAM settings.
The driver currently doesn't do error recovery for timed out commands very gracefully.
Sometimes, when booting, the driver gets stuck waiting for the Fibre Channel firmware to tell it that the loop port database is ready. In
this case you'll see an announcement that the loop state has a value of 0x1. To unwedge the system, unplug and replug the fibre channel con-
nection, or otherwise cause a LIP (Loop Initialization Primitive sequence) - this will kick the firmware into getting unstuck.
BSD
June 24, 2009 BSD