09-27-2007
Quote:
Originally Posted by
vntiger
And I have no idea about my Graphic Adapter. How can I check that?
Can you open the box and see what it says on the board?
I'm sure there is an elegant way to find out whats on the PCI bus, does the "dmesg" output give any clues?
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. 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
3. 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
4. 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
5. Solaris
I have a Sun Ultra 45 that was working perfectly until i upgraded it to Update 9 with a zfs filesystem. The box is sparc based and has an internal video card. When i boot it up, i receive an X server error and, while checking /var/dt/Xerrors, the following message is displayed
Fatal server... (9 Replies)
Discussion started by: goose25
9 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. AIX
If I login to one of our AIX 6.1 servers using SSH via PuTTY and I issue the who -a or w command I cannot see my session, although if I login via TELNET I can.
Why is this?
SSH:
root#> who
root#> w
08:06PM up 40 days, 27 mins, 0 users, load average: 0.05, 0.12, 0.14
User tty login@ idle... (1 Reply)
Discussion started by: deepinsight
1 Replies
8. 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
9. 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
10. 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
LEARN ABOUT NETBSD
pci_devinfo
PCI(3) BSD Library Functions Manual PCI(3)
NAME
pci -- library interface for PCI bus access
LIBRARY
PCI Bus Access Library (libpci, -lpci)
SYNOPSIS
#include <pci.h>
int
pcibus_conf_read(int pcifd, u_int bus, u_int dev, u_int func, u_int reg, pcireg_t *valp);
int
pcibus_conf_write(int pcifd, u_int bus, u_int dev, u_int func, u_int reg, pcireg_t val);
int
pcidev_conf_read(int devfd, u_int reg, pcireg_t *valp);
int
pcidev_conf_write(int devfd, u_int reg, pcireg_t val);
char *
pci_findvendor(pcireg_t id_reg);
void
pci_devinfo(pcireg_t id_reg, pcireg_t class_reg, char *devinfo, size_t len);
void
pci_conf_print(int pcifd, u_int bus, u_int dev, u_int func);
DESCRIPTION
The pci library provides support for accessing the PCI bus by user programs.
These functions are available in the libpci library. Programs should be linked with -lpci.
CONFIGURATION SPACE FUNCTIONS
The following functions are used to access PCI configuration space:
pcibus_conf_read()
Access the PCI configuration register reg on the device located at bus, dev, func, and place the result in *valp. pcifd must be an
open file descriptor to a PCI bus within the target PCI domain.
pcibus_conf_write()
Write the value specified by val into the PCI configuration register reg on the device located at bus, dev, func. pcifd must be an
open file descriptor to a PCI bus within the target PCI domain.
pcidev_conf_read()
Access the PCI configuration register reg on the device associated with the open file descriptor devfd and place the result in *valp.
pcidev_conf_write()
Write the value specified by val into the PCI configuration register reg on the device associated with the open file descriptor devfd.
MISCELLANEOUS FUNCTIONS
The following miscellaneous functions are available:
pci_findvendor()
Return an ASCII description of the PCI vendor in the PCI ID register id_reg.
pci_devinfo()
Return an ASCII description of the PCI vendor, PCI product, and PCI class specified by the PCI ID register id_reg and PCI class ID reg-
ister class_reg. The description is placed into the buffer pointed to by devinfo; the size of that buffer is specified in len.
pci_conf_print()
Print the PCI configuration information for the device located at bus, dev, func. pcifd must be an open file descriptor to a PCI bus
within the target PCI domain.
RETURN VALUES
The pcibus_conf_read(), pcibus_conf_write(), pcidev_conf_read(), and pcidev_conf_write() functions return 0 on success and -1 on failure.
The pci_findvendor() function returns NULL if the PCI vendor description cannot be found.
SEE ALSO
pci(4)
HISTORY
The pcibus_conf_read(), pcibus_conf_write(), pcidev_conf_read(), pcidev_conf_write(), pci_findvendor(), pci_devinfo(), and pci_conf_print()
functions first appeared in NetBSD 1.6.
BSD
April 24, 2004 BSD