From: Martin Sieper <msi@ngi-box.de>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Computer with 1GB and radeonfb
Date: Fri, 30 May 2003 22:13:54 +0200 [thread overview]
Message-ID: <elmo105432563416005480015305@arbeitspferd> (raw)
Hello developers,
I have a P4 computer with 1GB of RAM and a Radeon 9100 and I'm
using linux 2.4.20.
I had try the vesafb but it's failed. OK I've found a
patch for big memory on this list and now vasafb works fine.
The radeonfb doesn't work. OK I've found these patch
radeonfb-041103-2.4.20.diff also on this list but the
radeonfb doesn't work:
May 30 13:22:22 arbeitspferd kernel: radeonfb_pci_register BEGIN
May 30 13:22:22 arbeitspferd kernel: radeonfb: ref_clk=2700, ref_div=12, xclk=20000 from BIOS
May 30 13:22:22 arbeitspferd kernel: radeonfb: probed DDR SGRAM 131072k videoram
May 30 13:22:22 arbeitspferd kernel: BIOS 4 scratch = 2000002
May 30 13:22:22 arbeitspferd kernel: FP_GEN_CNTL: 0, FP2_GEN_CNTL: 8
May 30 13:22:22 arbeitspferd kernel: TMDS_TRANSMITTER_CNTL: 10000082, TMDS_CNTL: 1000000, LVDS_GEN_CNTL: 0
May 30 13:22:22 arbeitspferd kernel: DAC_CNTL: ff604002, DAC_CNTL2: 0, CRTC_GEN_CNTL: 2000200
May 30 13:22:22 arbeitspferd kernel: radeonfb: cannot map FB
I think it's also a big memory problem like the vesafb.
I'm not a kernel hacker, can someone help me please?
Thanks
Martin
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
next reply other threads:[~2003-05-30 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 20:13 Martin Sieper [this message]
2003-05-31 5:42 ` Computer with 1GB and radeonfb Jurriaan
2003-06-05 12:06 ` Martin Sieper
2003-06-05 19:04 ` Jurriaan
2003-06-10 10:56 ` Martin Sieper
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=elmo105432563416005480015305@arbeitspferd \
--to=msi@ngi-box.de \
--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).