Re: 1900x1200 console

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As far as I know you can't use a 16:9 resolution. You have to use a 4:5 resolution. If you are fine with that write vga=*** to your boot parameters.

Exchange *** with the value of the table:

Color depth       | 640x480 800x600 1024x768 1280x1024
256 (8bit)        | 769     771     773      775
32000 (15bit)     | 784     787     790      793
65000 (16bit)     | 785     788     791      794
16.7 Mill.(24bit) | 786     789     792      795


On 2/17/07, Bob Barrett < bobbrrtt@xxxxxxxxxxxxx> wrote:
I recently set up a new computer with the following hardware:

Tyan S2865ANRF
AMD Athlon 64 X2 4600+ Dual-Core
4 GB Corsair (CMX1024-3200)
PNY Quadro FX 1500 256 MB
Acer AL2423W


I had no trouble getting X to run at 1920x1200. Gnome first started at
1280x1024. I went to System > Preferences > Screen Resolution.
1920x1200 was available. I set it, and that was that. Now, I'd like to
set 1680x1050 as my resolution in the console. I haven't been able to
get it to work.

I have searched the list archives for "console" back two years and found
nothing
on this particular problem.


Some commands and output:

[]# dmesg | grep -i vesa
vesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 5120k,
total 262144k
vesafb: mode is 1280x1024x16, linelength=2560, pages=1
vesafb: protected mode interface info at c000:cb60
vesafb: pmi: set display start = c00ccb96, set palette = c00ccc00
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce
3cf 3d0
3d1 3d2 3d3 3d4 3d5 3da
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device

[]#  grep -i vesa /boot/config-2.6.18-1.2200.fc5smp

CONFIG_FB_VESA=y


[]# cat /proc/fb

"0 VESA VGA", so, vesafb is working.

[]$ gtf 1920 1200 60 && gtf 1920 1200 60 -f

# 1920x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 193.16 MHz
  Modeline "1920x1200_60.00"   193.16  1920 2048 2256 2592  1200 1201
1204 1242 \
  -HSync +Vsync

mode "1920x1200 60.00Hz 32bit (GTF)"
    # PCLK: 193.16 MHz, H: 74.52 kHz, V: 60.00 Hz
    geometry 1920 1200 1920 1200 32
    timings 5177 336 128 38 1 208 3
    hsync low
    vsync high
endmode

[]$ gtf 1680 1050 70 && gtf 1680 1050 70 -f

  # 1680x1050 @ 70.00 Hz (GTF) hsync: 76.51 kHz; pclk: 173.83 MHz
  Modeline "1680x1050_70.00"   173.83  1680 1792 1976 2272  1050 1051
1054 1093 \
  -HSync +Vsync

mode "1680x1050 70.00Hz 32bit (GTF)"
    # PCLK: 173.83 MHz, H: 76.51 kHz, V: 70.00 Hz
    geometry 1680 1050 1680 1050 32
    timings 5753 296 112 39 1 184 3
    hsync low
    vsync high
endmode

ddcprobe output:        # When running X on the nvidia driver

Videocard autoprobe results
Description:  NVIDIA Corporation G71 Board - q455h501
Memory (MB):  256

Monitor autoprobe results
ID: ACR0977
Name: AL2423W
Horizontal Sync (kHZ): 31-81
Vertical Sync (HZ)  : 56-75
Width (mm): 520
Height(mm): 320


xvidtune output:

Vendor: Monitor Vendor, Model: AL2423W
Num hsync: 0, Num vsync: 0

"1920x1200"   193.16   1920 2048 2256 2592   1200 1201 1204 1242 -hsync
+vsync

"1680x1050"   173.83   1680 1792 1976 2272   1050 1051 1054 1093 -hsync
+vsync

"1440x900"    106.50   1440 1520 1672 1904    900  903  909  934 -hsync
+vsync

(I've read that xvidtune reported clock values are inaccurate.)

Xorg.0.log (II) VESA(0):
Ranges: V min: 56  V max: 75 Hz, H min: 31  H max: 81 kHz, PixClock max
170 MHz

(II) NV(0): Supported additional Video Mode:
clock: 154.0 MHz   Image Size:  518 x 324 mm
h_active: 1920  h_sync: 1968  h_sync_end 2000 h_blank_end 2080 h_border: 0
v_active: 1200  v_sync: 1203  v_sync_end 1209 v_blanking: 1235 v_border: 0
Ranges: V min: 56  V max: 75 Hz, H min: 31  H max: 81 kHz, PixClock max
170 MHz
Monitor name: AL2423W
ACER

I am currently running at vga=0x31A (16 bit) and have run it at
vga=0x317 and
vga=0x31B, but the letter "x" is wider than it is tall. I would rather
run at
1680x1050 or 1900x1200.

I have searched the internet and found the most information here:

http://en.tldp.org/HOWTO/Framebuffer-HOWTO.html    (v1.2, 27 Feb 2000)

This information is seven years old, but using instructions found here on
converting XFree86 mode-lines into framebuffer device timings, I have
come up
with these added to "kernel /boot/vmlinuz- 2.6.19-1.2895.fc6 ro
root=LABEL=/1 \
rhgb quiet" line in GRUB:

video=vesa:xres:\
1680,yres:1050,depth:24,left:296,right:112,hslen:184,upper:39,lower:1,vslen:3

I have also tried:

video=vesa:xres:\
1680,yres:1050,depth:32,left:296,right:112,hslen:184,upper:39,lower:1,vslen:3

which matches the info above from the gtf output.

And I have tried:

video=vesa:xres:\
1920,yres:1200,depth:24,left:336,right:128,hslen:208,upper:38,lower:1,vslen:3

I have tried both of these using "video=vesafb...", and with both the "nv"
driver and the "nvidia" driver. When using the "nv" driver, the "nvidia"
driver was turned off with "chmod 644 etc/rc.d/init.d/nvidia*".

I'm concentrating on 24bit depth because that's what X is using. I get an
error when I try 32bit in xorg.conf. I guess I don't have enough video RAM.
I wanted a CAD video card (and this is), but those with more RAM are quite
expensive.

This has been tried in Fedora C5 & C6 and in Slackware with the "append"
line
in Lilo. It doesn't work there either. Does this not work with newer
kernels?
I don't mind recompiling the kernel, but the above information looks like it
shouldn't be necessary.

Sorry this is so long, but I have covered everything I can think of.

Thanks,

Bob

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux