10-04-2001
log file
How do I know which log file it is I got this error(below) out of one of them there are three xfree86 log files .0 .8 .9 Does it change and replace the log file everytime i load x do i need to load x through init 5 then when it hangs reboot the machine and check the log from the console?? let me know please because i loaded then i went into x and checked the file so i may need to do it again
Symbol cfb24_32ScreenInit from module /usr/X11R6/lib/modules/drivers/vesa_drv.o
is unresolved!
Symbol cfb24_32ScreenInit from module /usr/X11R6/lib/modules/drivers/vesa_drv.o
is unresolved!
7 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hello guys , i have a big big problem.
At the company that i work for there are like 4 pcs that are sending and recieving a lot of packets to the point that the network is down.
we think that it might be a virus, we run all the antivirus that you could posible think of and nothing so far.
... (2 Replies)
Discussion started by: josramon
2 Replies
2. Debian
Hi. I have problems sometimes going to "My Network Places" in the Windows Explorer. Sometimes works OK and sometimes appears an Explorer.exe Application Popup:
<<The instruction at "0x10004160" referenced memory at "0x10004160". The memory could not be "read">>
and the Explorer go out or is... (0 Replies)
Discussion started by: luisben
0 Replies
3. IP Networking
Hi. I have problems sometimes going to "My Network Places" in the Windows Explorer. Sometimes works OK and sometimes appears an Explorer.exe Application Popup:
<<The instruction at "0x10004160" referenced memory at "0x10004160". The memory could not be "read">> (Event ID: 26 at the Windows... (0 Replies)
Discussion started by: luisben
0 Replies
4. UNIX for Dummies Questions & Answers
After i login i try to start X windows by using the "startx" command. All it does is return "startx: Command not found". Any help would be great.:), By the way I'm using freeBSD. (1 Reply)
Discussion started by: spacebizall
1 Replies
5. UNIX for Advanced & Expert Users
Hello all,
I have encountered a strange question. I installed a Ubuntu 8.10 in the VMware in the XP, and use putty to connect to ubuntu. Everything is fun except I can't use the wget in putty, neither does command "sudo apt-get ***". But they are OK in the VM.
Can someone help me out? Thank... (2 Replies)
Discussion started by: tpltp
2 Replies
6. UNIX for Advanced & Expert Users
Hi I have an issue with a client. He was able to use his mounted Samba share for a long time. However, a couple of days ago, he wasn't able to access all of his files all of a sudden. He still see's the share and majority of the files, but not some that he needs.
I checked with Secure CRT on... (1 Reply)
Discussion started by: zixzix01
1 Replies
7. Solaris
Hi. I'm new here and new at using Solaris and I've been having some problems with file sharing between Windows Server 2012 and Solaris 10. I will really appreciate your help.
So my Windows Server (WS) 2012 has just three activated services: DNS, DHCP and Active Directory. Solaris too three... (1 Reply)
Discussion started by: LauraKtz
1 Replies
VESA(4) Kernel Interfaces Manual VESA(4)
NAME
vesa - Generic VESA video driver
SYNOPSIS
Section "Device"
Identifier "devname"
Driver "vesa"
...
EndSection
DESCRIPTION
vesa is an Xorg driver for generic VESA video cards. It can drive most VESA-compatible video cards, but only makes use of the basic stan-
dard VESA core that is common to these cards. The driver supports depths 8, 15 16 and 24.
SUPPORTED HARDWARE
The vesa driver supports most VESA-compatible video cards. There are some known exceptions, and those should be listed here.
CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.
The driver auto-detects the presence of VESA-compatible hardware. The ChipSet name may optionally be specified in the config file "Device"
section, and will override the auto-detection:
"vesa"
The following driver Options are supported:
Option "ShadowFB" "boolean"
Enable or disable use of the shadow framebuffer layer. Default: on.
This option is recommended for performance reasons.
Option "ModeSetClearScreen" "boolean"
Clear the screen on mode set. Some BIOSes seem to be broken in the sense that the newly set video mode is bogus if they are asked to
clear the screen during mode setting. If you experience problems try to turn this option off. Default: on.
SEE ALSO
Xorg(1), xorg.conf(5), Xserver(1), X(7)
AUTHORS
Authors include: Paulo Ce'sar Pereira de Andrade.
X Version 11 xf86-video-vesa 2.3.1 VESA(4)