From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Giuliano Pochini <pochini@shiny.it>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Radeon problems
Date: 22 Jul 2003 23:27:29 +0200 [thread overview]
Message-ID: <1058909248.535.0.camel@gaston> (raw)
In-Reply-To: <20030722212344.11c895f1.pochini@shiny.it>
On Tue, 2003-07-22 at 23:23, Giuliano Pochini wrote:
> >> Problem #1: Radeonfb sets a video mode that isn't supported by my LCD
> >> monitor. I have to blindly type "/usr/sbin/fbset -a 1280x1024-60 -depth 16"
> >> at the root console every time (*if* it boots, because I make the box
> >> crash quite often :( ). Is there a boot option to set the right video mode ?
> >
> > Can you send me a dmesg dump (with the wrong video mode) and
> > a dump of /proc/device-tree/pci@f0000000 ?
>
> Yes, these are the relevant lines:
>
> ----
> Kernel command line: ro video=radeonfb:1024x768-8@75
> Console: colour dummy device 80x25
> radeonfb: ref_clk=2700, ref_div=12, xclk=24975 from OF
> Console: switching to colour frame buffer device 80x30
> radeonfb: ATI Radeon 9000 If DDR SGRAM 64 MB
> radeonfb: DVI port no monitor connected
> radeonfb: CRT port CRT monitor connected
> ----
>
> Hmm, I just noticed that it believes I connected a CRT monitor. It's wrong,
> I have an non-Apple LCD display connected to the DVI port. 80x30 means the
> resolution is still 640x480.
Tried booting with video=radeon:dfp to force flat panel detection ?
> This a dir of /proc/device-tree/pci@f0000000, but I don't see how can it be
> useful. Is there a tool to extract more info ?
Just tarball that dir, it contains some useful stuffs, beleive me :)
> [Giu@Jay pci@f0000000]$ dir
> total 0
> dr-xr-xr-x 4 root root 0 lug 22 21:09 .
> dr-xr-xr-x 21 root root 0 lug 22 21:09 ..
> lrwxrwxrwx 1 root root 20 lug 22 21:13 @10 -> ATY,PheonixParent@10
> -r--r--r-- 1 root root 4 lug 22 21:13 #address-cells
> lrwxrwxrwx 1 root root 20 lug 22 21:13 ATY,PheonixParent -> ATY,PheonixParent@10
> dr-xr-xr-x 4 root root 0 lug 22 21:13 ATY,PheonixParent@10
> lrwxrwxrwx 1 root root 15 lug 22 21:13 @b -> uni-north-agp@b
> -r--r--r-- 1 root root 10 lug 22 21:13 built-in-names
> -r--r--r-- 1 root root 8 lug 22 21:13 bus-range
> -r--r--r-- 1 root root 4 lug 22 21:13 clock-frequency
> -r--r--r-- 1 root root 10 lug 22 21:13 compatible
> -r--r--r-- 1 root root 4 lug 22 21:13 device_type
> -r--r--r-- 1 root root 4 lug 22 21:13 #interrupt-cells
> -r--r--r-- 1 root root 28 lug 22 21:13 interrupt-map
> -r--r--r-- 1 root root 16 lug 22 21:13 interrupt-map-mask
> -r--r--r-- 1 root root 4 lug 22 21:13 interrupt-parent
> -r--r--r-- 1 root root 8 lug 22 21:13 interrupts
> -r--r--r-- 1 root root 4 lug 22 21:13 linux,phandle
> -r--r--r-- 1 root root 14 lug 22 21:13 model
> -r--r--r-- 1 root root 4 lug 22 21:13 name
> -r--r--r-- 1 root root 72 lug 22 21:13 ranges
> -r--r--r-- 1 root root 8 lug 22 21:13 reg
> -r--r--r-- 1 root root 4 lug 22 21:13 #size-cells
> -r--r--r-- 1 root root 11 lug 22 21:13 slot-names
> lrwxrwxrwx 1 root root 15 lug 22 21:13 uni-north-agp -> uni-north-agp@b
> dr-xr-xr-x 2 root root 0 lug 22 21:13 uni-north-agp@b
> -r--r--r-- 1 root root 0 lug 22 21:13 write-combining
>
>
> --
> Bye.
> Giuliano.
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-22 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 21:23 Radeon problems Giuliano Pochini
2003-07-22 21:27 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-19 14:55 Giuliano Pochini
2003-07-19 16:20 ` Calum Selkirk
2003-07-20 15:54 ` Giuliano Pochini
2003-07-21 12:53 ` Paul Mackerras
2003-07-21 23:15 ` Michel Dänzer
2003-07-24 7:28 ` Giuliano Pochini
2003-07-21 18:54 ` Benjamin Herrenschmidt
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=1058909248.535.0.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
/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).