From: Parag Warudkar <warudkar@vsnl.net>
To: nsouch@free.fr
Cc: geert@linux-m68k.org, jsimmons@infradead.org,
linux-fbdev-devel@lists.sourceforge.net, jochen@panix.com
Subject: Re: 2.5.70 - Blank Screen with VESA VGA Framebuffer
Date: Sat, 14 Jun 2003 09:20:16 +0530 [thread overview]
Message-ID: <002201c33228$12566b80$016f41db@Lappy> (raw)
Sorry - Last time I sent the message encoded/html which appeared garbled
on the list.. Thanx to Jochen Roth for pointing it out.
Original Message...>
Yeah, exact same card. I will try the LCD patch, does X work with it?
For me the reason for using FB is X, it wont work otherwise. Why? I don't
know..
Will take this up with X-Pert..!
P
-----Original Message-----
From: Nicolas Souchu [mailto:nsouch@free.fr]
Sent: Sat 6/14/2003 04:55
To: Parag Warudkar
Cc: Geert Uytterhoeven; James Simmons; Linux Frame Buffer Device
Development
Subject: Re: [Linux-fbdev-devel] 2.5.70 - Blank Screen with VESA VGA
Framebuffer
On Fri, Jun 13, 2003 at 02:06:56PM +0530, Parag Warudkar wrote:
> No. Atyfb hasn't worked for me in 2.4.20. If I use video=atyfb, I get a
> corrupted white screen which is beyond my capabilities to describe!! :)
My experience is almost the same with the following board:
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M
AGP 2x
+(rev 64) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Mobility P/M AGP 2x
Flags: bus master, stepping, medium devsel, latency 64, IRQ 9
Memory at e4000000 (32-bit, non-prefetchable) [size=16M]
I/O ports at c000 [size=256]
Memory at e6000000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 1.0
Capabilities: [5c] Power Management version 1
The PCI id is Ox4d4c, and you?
e.g. I got the famous encrypted white screen with at least 2.4.9 but
now with 2.5.69 + LCD patch posted recently, it's much better. I get
half the screen duplicated verticaly but with correct resolution.
I guess this is a modesetting problem?
> The graphics chip is ATI RAGE Mobility M1(LT) AGP2X - a MACH64 Derivate
> with 8Mb RAM.. For X, 3D acceleration (DRI, direct rendering) works
> with a Mach64 branch of XFree86.
> (http://dri.sourceforge.net/snapshots/bleeding-edge/mach64*-*)
You should try the 2.5.69+patch...
Note that I had to disable everything else but the ATY driver (VESA,
VGA16,
framebuffer virtual).
Nicholas
--
Nicholas Souchu - nsouch@free.fr - nsouch@FreeBSD.org
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
next reply other threads:[~2003-06-14 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 3:50 Parag Warudkar [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 9:04 2.5.70 - Blank Screen with VESA VGA Framebuffer Parag Warudkar
2003-06-13 9:24 ` Geert Uytterhoeven
2003-06-13 22:06 ` Alexander Kern
2003-06-13 8:36 Parag Warudkar
2003-06-13 8:54 ` Geert Uytterhoeven
2003-06-13 2:32 Parag Warudkar
2003-06-13 8:06 ` Geert Uytterhoeven
2003-06-10 9:36 Parag Warudkar
2003-06-12 18:57 ` James Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002201c33228$12566b80$016f41db@Lappy' \
--to=warudkar@vsnl.net \
--cc=geert@linux-m68k.org \
--cc=jochen@panix.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=nsouch@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.