PDA

View Full Version : Screen resolution


carlos
03-31-2008, 03:52 AM
PCU: Athlon 64 3200+
MB: Asus A8N-E
Chipset: nForce4
Mem: 1024 MB
Video Card: Ati - Asus Extreme AX5500 (PCI)
Monitor: HP f2105 set to 1680x1050 (32bit)on Windows XPSP2 and on KUBUNTU 7.10

Previously installed FreeSpire 2.0.3 (installation went well but monitor resolution was at best 1600x1200 (24bit) and could not be corrected. Text was OK but somewhat blurry.

PCBSD 1.5 on 320MB SATA HD
PCBSD installs harmoniously (font is beautiful), after reboot a frozen scrambled screen.

New to Linux.

wmjodea
03-31-2008, 04:03 AM
Will will need to correct the xorg.conf file. Looks like the horizontal and vertical frequency rate are not right. Find the specs on the monitor then enter them manually.

Oko
03-31-2008, 06:48 AM
PCU: Athlon 64 3200+
MB: Asus A8N-E
Chipset: nForce4
Mem: 1024 MB
Video Card: Ati - Asus Extreme AX5500 (PCI)
Monitor: HP f2105 set to 1680x1050 (32bit)on Windows XPSP2 and on KUBUNTU 7.10

Previously installed FreeSpire 2.0.3 (installation went well but monitor resolution was at best 1600x1200 (24bit) and could not be corrected. Text was OK but somewhat blurry.

PCBSD 1.5 on 320MB SATA HD
PCBSD installs harmoniously (font is beautiful), after reboot a frozen scrambled screen.

New to Linux.

Well I never got to use Linux in my life either.

Configuring X window in Unix is simple. You drop to console run X -configure in supper user mode and then inspect your
/var/log/xorg.log file. Then you need to edit xorg.conf and probe it
with x -config /root/xorg.conf.new if it is stable.

I disagree with the above comment that you have a problem with Vert and Horz sync rates. Actually you are better of erasing them all together as they should be specified on modern hardware only in couple of instances.

I would be guessing your troubles without reading the log file but you can try to specify DefaultDepth in ScreenSection to something like 24 or even better to 16 and probe X server.

carlos
03-31-2008, 06:56 PM
Installed in VESA.
None of the screen resolutions offered -not even the 800x600 in 16 bit-worked.
Cancel.
Sys:"Reboot to default"
That worked. It is a low resolution, slightly distorted screen.
The monitor was correctly detected as HP f2105 (it is a wide screen monitor 1680x1050 and is working properly in KUBUNTU and Windows XP environment)

Following up your recommendation.
Console> sudo X -config
Password: (did not work) neither the user nor the administrator.
Console> su X -config
Sys: Sorry

By the way, at first tried to enter safe (or any other) mode during the boot up. That did not work. It would just go ahead and do its thing.

Have no Internet connection either on PCBSD. I have to change back and forth between a Window/KUBUNTU and PCBSD HD.

wmjodea
03-31-2008, 08:14 PM
Is VESA your only choice? Do you have Xorg? In Xorg you would type Xorg -config. Enter as root try su (enter) then password (enter) then xorg (space) config. You may have to edit the xorg.conf file which should be at /etc/X11. Look under screen0 for the resolution settings. You may have to add the one you want if it is not listed. Check the Horizontal and Vertical Sync setting to make sure their are correct for your monitor.

Oko
03-31-2008, 08:54 PM
Is VESA your only choice? Do you have Xorg? In Xorg you would type Xorg -config. Enter as root try su (enter) then password (enter) then xorg (space) config. You may have to edit the xorg.conf file which should be at /etc/X11. Look under screen0 for the resolution settings. You may have to add the one you want if it is not listed. Check the Horizontal and Vertical Sync setting to make sure their are correct for your monitor.

Do not be ridiculous. Xorg -configure and X -configure do the same thing.
Read man pages.

NO, I am repeating he needs to erase Horz and Vert sync. X server is very smart and will do better without those rates.

Please do not answer question if you do not know what are you talking about.


To original question:

Seems that I am dealing with an Ubuntu user.

You need to go to su mode. Unless you set up sudo account you can not use it.

su -
password

then

#whatever is your command

The easiest way is to completely kill the X before you go to su mode
In vanilla FreeBSD which doesn't run XDM it is simply
alt+ctrl+backspace.

I am not using PC-BSD so I do not know what is the fastest way to drop
in console mode on PC.

wmjodea
03-31-2008, 10:07 PM
I did what Oko suggested and removed the HorizSync and VertRefresh from my xorg.conf file. Now I have only one resolution option,800x680. After adding the HorizSync and VertRefresh settings under Monitor my 1024x768 setting came back. Please go to http://www.freebsd.org/doc/en/books/han ... onfig.html (http://www.freebsd.org/doc/en/books/handbook/x-config.html) and read X11 Configuration. The information I posting to help you came from the FreeBSD Handbook Chapter 5 :The X Window System. which is on Freebsd.org. I do not know if what works for Freebsd will work for sure on PC-BSD ; but this is what I did when I had problems with screen resolution on my FreeBSD system. I also use PC-BSD ; but I have had no problems with PC-BSD so far. I would think when you installed PC-BSD it did an X -configure as part of the set up. Some times editing the xorg.conf is require for certain sysytems.

http://www.freebsd.org/doc/en/books/han ... onfig.html (http://www.freebsd.org/doc/en/books/handbook/x-config.html)

Or just Google X11 Configuration

Oko
03-31-2008, 10:18 PM
I did what Oko suggested and removed the HorizSync and VertRefresh from my xorg.conf file. Now I have only one resolution option,800x680. After adding the HorizSync and VertRefresh settings under Monitor my 1024x768 setting came back. Please go to http://www.freebsd.org/doc/en/books/han ... onfig.html (http://www.freebsd.org/doc/en/books/handbook/x-config.html) and read X11 Configuration. The information I posting to help you came from the FreeBSD Handbook Chapter 5 :The X Window System. which is on Freebsd.org. I do not know if what works for Freebsd will work for sure on PC-BSD ; but this is what I did when I had problems with screen resolution on my FreeBSD system. I also use PC-BSD ; but I have had no problems with PC-BSD so far. I would think when you installed PC-BSD it did an X -configure as part of the set up. Some times editing the xorg.conf is require for certain sysytems.

http://www.freebsd.org/doc/books/handbook/x-config.html

Or just Google X11 Configuration


The Handbook Chapter 5 about configuration of X window system is badly outdated!

Vert and Horz syn rates are harmless if you know exactly your hardware.
Look now the Section Screen and in particular SubSection Display. If your DefaultDepth is let say 24 try to add something like


Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24

SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
EndSection


and some other even better resolutions.
X server will try to launch with the first one and if it fails will try
to use the next one resolution in the line Mode.

So specify the first one that you want and then a few alternatives.

The resolution is also driver and depth specific. There is a very complicated formula that can tell you what is the best resolution you
can get with the certain Depth (Colors) on the particular driver.

I would imagine that VESA will try to do 800x600 if not forced by Mode lines to do better. VESA should be your last choice for the video driver anyway.

Cheers,


P. S.
I also forgot that you can use


xrandr


to adjust the resolution on the fly. You need to refresh the
X server after you do that.

This is an up to date how to for X server.

http://www.openbsd.org/faq/faq11.html#amd64i386


but the readings howtos is not a substitution for reading books and
Xorg manuals.



OKO

wmjodea
03-31-2008, 11:09 PM
The FreeBSD handbook maybe out dated ; but the information in it worked for me. My Subsection is also set with Depth And Mode setting.

SubSection "screen"
Depth 24
Modes "1024x786"
EndSubSection

All I did was remove the HorizSync and the VertRefresh.

Yes I agree. I have Absolute FreeBSD 2nd Edition by Micheal W. Lucas which I use for information also. Do you have any other books to suggest?

carlos
03-31-2008, 11:11 PM
Not an KUBUNTU "user". It is installed only for Internet use.

Back to your rec. It worked.
Su
Password
Commands

Of course it was done in the Konsole while X(abr.for graphical interface?)running.
cd unto /var/ was OK. That's it. There is no /log/ file to go on.

Do you have to shut down X before make changes in the xorg.log file?
Ctr+Alt+Del brings up a screen in "X" with computer stats or something like that.
Where is this xorg.log file to modify.

Oko
04-01-2008, 12:18 AM
NO. When you probe the X server it will generate the file

/root/xorg.conf.new Which you can test it with X -config /root/xorg.conf.new. Then if it doesn't die you copy
xorg.conf.new into /etc/X11/xorg.conf

You do edit xorg.conf file and play with it.

Your log file should be in /var/log/ directory.

Good Luck,
OKO

Oko
04-01-2008, 12:25 AM
The FreeBSD handbook maybe out dated ; but the information in it worked for me. My Subsection is also set with Depth And Mode setting.

SubSection "screen"
Depth 24
Modes "1024x786"
EndSubSection

All I did was remove the HorizSync and the VertRefresh.

Yes I agree. I have Absolute FreeBSD 2nd Edition by Micheal W. Lucas which I use for information also. Do you have any other books to suggest?


The only up to date book on the market about XOrg is
X power tools

http://www.oreilly.com/catalog/9780596101954/toc.html

You can see my harsh review of the book on Amazon.com (From Russia with the Love). It will give you systematic introduction and be good base for reading man pages.

There are some classics about X window system

http://www.oreilly.com/catalog/v8/toc.html

I like it but bare in mind that so many things has happened with Xorg
since 2000 so the book is outdated big time. For instance xrandr
is only half a year ago included in Xorg.
It is wider in scope than the first one and goes through x applications in much greater detail.

Bottom line you need foundations and then jump into reading
man pages for Xorg. They are huge but in all honestly X is not
too well documented at least not as good as OpenBSD or FreeBSD for instance.

Cheers,
OKO

wmjodea
04-01-2008, 01:18 AM
Thank You Oko for the information. I went to the Xorg man pages for FreeBSD 6.3 and found under Monitor that if no HorizSync or VertRefrsh is stated in the xorg.conf file ; then Xorg will default to 28-33kHz and the VertRefresh will default to 43-72HZ.

According to the HP manual for thef2105 ; which carlos is using the HorizSync is 30-94kHz and the VertRefresh is 48-85.

Max resolution 1920x1200 Horiz is 74.0 kHz Vert is 60 Hz
1680x1050 Horiz is 65.3 Vert is 60
1600x1200 Horiz is 75.0 Vert is 60
1280x1024 Horiz is 91.2 Vert is 85

So if by default Xorg is 28-33 (horiz) and 43-72 (vert) then to use the higher resolution on the monitor would put it out of range based on the default settings.

Could this not be why carlos can not access the higher resolutions?
When I changed those setting on my system I was limited to only the lower setting

Oko
04-01-2008, 01:47 AM
Thank You Oko for the information. I went to the Xorg man pages for FreeBSD 6.3 and found under Monitor that if no HorizSync or VertRefrsh is stated in the xorg.conf file ; then Xorg will default to 28-33kHz and the VertRefresh will default to 43-72HZ.

According to the HP manual for thef2105 ; which carlos is using the HorizSync is 30-94kHz and the VertRefresh is 48-85.

Max resolution 1920x1200 Horiz is 74.0 kHz Vert is 60 Hz
1680x1050 Horiz is 65.3 Vert is 60
1600x1200 Horiz is 75.0 Vert is 60
1280x1024 Horiz is 91.2 Vert is 85

So if by default Xorg is 28-33 (horiz) and 43-72 (vert) then to use the higher resolution on the monitor would put it out of range based on the default settings.

Could this not be why carlos can not access the higher resolutions?
When I changed those setting on my system I was limited to only the lower setting

You are most definitely right. Bare in mind also that relationship between Depth (colors), Vert and Horz sync rates, Modes, and Drivers is extremely complex so we would really have to sit down and do lots of computing to be able to figure out why his X server is not using the
appropriate resolution.

We also have not talked about the type of the monitor he uses. CRT monitors and LCD monitors work on very different physical principles
which also affects the X server. In essence you produce the picture on LCD monitor by altering the current through the liquid crystal which is much more sensitive process than shooting electrons onto the screen of the CRT monitor.
There is a big science behind it but I am happy if he can get his X to work.

Kind Regards,
OKO

carlos
04-01-2008, 02:12 AM
The monitor is LCD type.

Questions:
Probe the X server -- (how?)
How do you go to /var/log/ -- previous attempt to cd to it was unsuccessful.
It went into /var/ and no further on.

wmjodea
04-01-2008, 03:38 AM
Carlos as root try cd /var/log [enter] then type ls -a (list all) to see the files on /var/log.

TerryP
04-01-2008, 07:30 AM
Many people give directions using the command line, because it is either necessary at times (X -configure for example) or because that is what they tend to use. It's not some thing that I like about forums.pcbsd.org but can't blame any one for it, I do likewise.


If you are uncomfortable with using the command prompt to navigate around folders (e.g. cd, ls, etc) you can use Konqueror for those parts.

On PC-BSD /var/log/Xorg.0.log and /var/log/Xorg.0.log.old should be world readable and you would probably prefer looking at the file in kedit or kwrite rather then at the command line (more filename or less filename).

Konqueror also has the ability to launch a terminal (command prompt window) in the current directory through it's tools menu, from which you could always use to run other commands as necessary.



Oko can some times be a difficult person to follow directions from (especially if you've never touched a command prompt in your life or techy-things and manpages content sound like bable), but he is also one of the knowledgeable patrons of this forum.

wmjodea
04-01-2008, 03:29 PM
carlos: Did you try using the Display Setup Wizard at boot up? On the Boot Menu --Welcome to PC-BSD-- Try option #6 Display Setup Wizard. Hit the space key to pause the menu if it starts the boot up process to fast to read the menu. Enter #6 then check the display settings. On the advanced menu check monitor settings to see if the Horizontal Sync and the Vertical Refresh setting match your monitor settings(check your monitor manual for correct specs). This will show you if your monitor is being properly detected.