|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
So as suggested before, bring back xorg.conf and use "vesa", beyond fiddling with s3virge driver options and getting lucky.. there really isn't anything else we can do for you.
Try the mailing lists, or a snapshot. |
|
|||
mfaridi, the purpose of quoting previous posts is to point out to readers what specific point(s) are being addressed in your response. Simply quoting the entire message leads to confusion (What was cut out, or why include the whole thing?) & ultimately is nothing more than noise.
|
|
|||
mfaridi, if you have truly tried X's vesa driver (as originally suggested by BSDfan666...), & this has not worked, there is little else anyone will be able to suggest.
However, I do have questions, some which have been raised by others, & I will mention these again. Whether you want to experiment further is up to you as none of us are there to observe firsthand this hardware or what you have done.
Can this old system be used for OpenBSD? It appears that you have enough disk space & the memory is good. Before writing off the entire experience as a failure, I personally would install again, but this time be smart about the process. |
|
|||
Quote:
Following my theme of simplicity, you should verify that X works locally first where you have a monitor, keyboard, & mouse attached. Then start startx here. It's starting to look like you were trying to tunnel X through SSH to a remote system without doing any configuration. It doesn't work that way. Has a monitor, keyboard, & mouse always been connected to this Pentium I system? |
|
|||
You can set the Driver option in the Device section to "vesa", this will be an unaccelerated framebuffer.
If you do this, VendorName/BoardName/BusID and most other options can be commented out or removed.. except for Identifier & Driver, of course. Other choices like trying a snapshot have been given before, have you considered doing that? |
|
||||
Thanks
All guys I replace s3virge with vesa in xorg.conf and reboot system after that I run this command Code:
echo "exec fluxbox" >.xinitrc and after that I have fluxbox . but I have some problem 1-I read this link http://www.openbsd.org/faq/faq11.html#amd64i386 and do everything I see in this page, but resolution of monitor is not good and I do not have good resolution 2- I install many package like opera and thunderbird but I do have them in main menu how add new packages to main menu and use them it is my first experience with fluxbox , all time I use Gnome and KDE. |
|
|||
VESA capabilities are fairly limited, there is a select list of predefined modes in the video BIOS, X may default at lower resolution (800x600).. you can try choosing another by one listed in xrandr output, i.e: xrandr -s 1024x768.
Based on the Xorg.0.log output on the first page, replacing your Monitor section with the following MIGHT help if no other modes are listed in xrandr output. Code:
Section "Monitor" Identifier "FLATRON 775FT" DisplaySize 310 230 VertRefresh 50-160 HorizSync 30-70 Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync EndSection Good luck. |
|
||||
Here is a link to a VESA 1024x768, 24-bit color, 8MB video RAM xorg.conf:
http://www.daemonforums.org/showpost...41&postcount=2 Note the very first line in that xorg.conf file. It mentions a program you can use to create your own xorg.conf files. Quote:
|
|
||||
Quote:
|
|
||||
Your screen is a "FLATRON 775FT" according to xorg.log, which is a 17" CRT screen according to google.
For most 17" CRT (4:3 ratio) screens 1280x1024 @ 60 hertz is the highest supported resulotion, although 1024x768 should also work fine (In fact, many people prefer this). You can try replacing "1024x768" with "1280x1024" and see if that works better. You may need to manually adjust the stretch/location with the controls on your screen though. CRT screens are not able to do this automatically as LCD screens can (Because it's an analogue electron stream and not digital pixels).
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
||||
According to wikipedia, the S3 ViRGE is capable of "1600x1200 with 16.7M colors at 80 Hz refresh (VX), 1280x1024 with 256 colors at 75 Hz refresh, 1024x768 with 64K colors at 75 Hz refresh, 800x600 16.7M colors at 75 Hz refresh."
According to this specification I found online at a store for the LG Flatron 775FT: Code:
Max: 1280 x 1024 @ 60 Hz Recommended: 1024 x 768 @ 85 Hz Dot Pitch 0.24 MM Stripe Pitch Misc. Features ~ Horizontal Scan Range 30 - 70 kHz, Vertical Scan Range 50 - 160 Hz ~ 110 Mhz Video Input Bandwidth |
|
||||
Quote:
Code:
I believe that mfaridi now has sufficient information to either use xorgconfig, or to give up |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Fluxbox don't start | Artur | FreeBSD General | 4 | 3rd September 2009 01:04 PM |
fluxbox crash? HELP | bsdnewbie999 | OpenBSD General | 9 | 2nd April 2009 04:35 AM |
HOWTO: Fluxbox from GIT | vermaden | Guides | 6 | 3rd November 2008 12:13 PM |
OpenBSD 4.3, XDM + FluxBox | WeakSauceIII | General software and network | 2 | 19th May 2008 08:34 PM |
gtk themes for fluxbox | rex | FreeBSD General | 0 | 18th May 2008 03:24 AM |