Re: No 1028x786 resolution on HP M50 Monitor On Sarge
Angelina Carlton wrote:
On Sat, Jun 04, 2005 at 07:59:04AM +0000, Leonard Chatagnier wrote:
Also read the link you provided and came to
conclusion r128 doesn't
apply to my video card. Doesn't seem to hurt anything though and I know
that is was
loaded before when all resolutions were working.
Well you need to find the correct module to load, google for the exact
model of your card. At this point I would also look at the logs.
/var/log/XFree86.0.log will contain lots of information about what
fails to load, what will load but with warnings and hopefully
something about why it wont do 1024x786.
I find this related to 1028x786:
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device ???
(--) Chipset vesa found
(II) VESA(0): Not using mode "1028x786" (no mode of this name) ???
(II) VESA(0): Not using built-in mode "1024x768" (width too large for
virtual size) ???
(II) VESA(0): VESA VBE OEM Product: MACH64GT (my card driver, I believe)
(WW) VESA(0): Option "UseFBDev" is not used
lspci -vv give for my card:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro
AGP 1X/2X (rev 5c) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Pro Turbo AGP 2X
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 66 (2000ns min), Cache Line Size: 0x08 (32 bytes)
Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at 9000 [size=256]
Region 2: Memory at f4100000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] AGP version 1.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=<none>
ChatagnierL-Home:~#
Also, googling for linux drivers for my card gave lots of hits, no
solutions that I could implement, mention of bugs
in Debian and strong indication that Mach64 is the proper driver for my
card. Perhaps the above date means something to you. I don't know what
to make of it. I had this same problem with X when I first installed woody
but can't remember the solution. If you want to continue, I'll try any
suggestions you or any body else has and thanks for everybody's help. I
did pick up on a few new commands for me to use.
You also don't need to reboot the computer each time,
ctrl+alt+backspace will kill the xserver for you and you can make some
changes and try again.
Thanks for this, too.
Leonard Chatagnier
Reply to: