From: "Décio Luiz Gazzoni Filho" <decio@revistapcs.com.br>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Dual Athlon crashing with VESAfb and Rivafb
Date: Tue, 23 Jul 2002 00:14:46 -0300 [thread overview]
Message-ID: <200207230014.52689.decio@revistapcs.com.br> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have put together a dual Athlon machine (K7D Master mobo with the AMD 760MPX
chipset) and GeForce4 Ti4400 video card, and my only grip with it so far is
the inability to run my display with a framebuffer device. VESAfb locks my
machine hard, while Rivafb leaves me staring at a blank screen (though the
system keeps loading). That happened on 2.4.19-pre2 with the RML's preempt
patch (configured for SMP, preemption enabled, VESAfb and Rivafb built-in
into the kernel). Now I have updated to 2.4.19-rc3, and VESAfb keeps locking
the machine hard, but I can't load Rivafb any longer, passing the boot-time
parameter video=riva:1024x768-32@60 still loads with a plain text console,
and `dmesg | grep riva' doesn't show up anything.
Is this a known problem? Any ideas on how to fix it? If more information is
needed, let me know and I will provide it.
Thanks
Décio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj08yiwACgkQZ4XkjV48x2dddwCcDWDSL7dvt0aS/OXv5WPCuTtJ
KQIAni61GQ+XO5aBszskX8jAxtLJG9fy
=Vw/p
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
reply other threads:[~2002-07-23 3:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200207230014.52689.decio@revistapcs.com.br \
--to=decio@revistapcs.com.br \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).