From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mws <mws@twisted-brains.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11-rc5
Date: Sat, 26 Feb 2005 11:50:43 +1100 [thread overview]
Message-ID: <1109379043.14993.93.camel@gaston> (raw)
In-Reply-To: <200502251430.16860.mws@twisted-brains.org>
On Fri, 2005-02-25 at 14:30 +0100, Mws wrote:
> hi,
>
> i also have problems with 2.6.11-rc5 and radeon:
>
> i am using a ATI Radeon X600 PciExpress.
>
> a) now the console framebuffer seems to bee working, thx benjamin :)
> b) when bootup seq ist completed and i want to start X (xorg-x11) with ati-drivers
> x is freezing - not your problem, but the console is not correctly restored :/ the only way
> out is to reset the machine :/
> 2.6.11-rc3 was running fine in this case
Hrm, the binary drivers ? oh well... some users had them freezing vs.
radeonfb before and not now. I don't know what they do and don't have
access to a machine with them (there are no ppc versions) so it will be
difficult to track. I suspect they completely reconfigure the chip and
don't restore it properly tho.
What exactly is happening. Does X launches at all ? When does it
freeze ? On X launch or when exiting it ? Have you tried disabling
dynamic clock tweaking ? (radeonfb.default_dynclk=-1 or 0 on the
cmdline, first one means "don't touch the registers", secoond one means
"disable dynamic clocks").
> i have attached my lspci -vv & lspci -tv output and following a small seq of the dmesg output
> when initializing the radeon fb.
>
> if i can provide/assit you with testing, i am available to do so, also if you need more information
> on my system.
>
> i am subscribed to lkml, but i would like to be included into cc seprately, thx.
>
>
> radeonfb_pci_register BEGIN
> ACPI: PCI interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> radeonfb (0000:05:00.0): Found 131072k of DDR 128 bits wide videoram
> radeonfb (0000:05:00.0): mapped 16384k videoram
> radeonfb: Found Intel x86 BIOS ROM Image
> radeonfb: Retreived PLL infos from BIOS
> radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=400.00 Mhz, System=300.00 MHz
> radeonfb: PLL min 20000 max 40000
> 1 chips in connector info
> - chip 1 has 2 connectors
> * connector 0 of type 2 (CRT) : 2300
> * connector 1 of type 3 (DVI-I) : 3221
> Starting monitor auto detection...
> radeonfb: I2C (port 1) ... not found
> radeonfb: I2C (port 2) ... not found
> radeonfb: I2C (port 3) ... found CRT display
> radeonfb: I2C (port 4) ... not found
> radeonfb: I2C (port 2) ... not found
> radeonfb: I2C (port 4) ... not found
> radeonfb: I2C (port 3) ... found CRT display
> radeonfb: Monitor 1 type CRT found
> radeonfb: EDID probed
> radeonfb: Monitor 2 type no found
> Display is GTF capable
> hStart = 1344, hEnd = 1504, hTotal = 1728
> vStart = 1025, vEnd = 1028, vTotal = 1072
> h_total_disp = 0x9f00d7 hsync_strt_wid = 0x14054a
> v_total_disp = 0x3ff042f vsync_strt_wid = 0x30400
> pixclock = 6349
> freq = 15750
> freq = 15750, PLL min = 20000, PLL max = 40000
> ref_div = 12, ref_clk = 2700, output_freq = 31500
> ref_div = 12, ref_clk = 2700, output_freq = 31500
> post div = 0x1
> fb_div = 0x8c
> ppll_div_3 = 0x1008c
> Console: switching to colour frame buffer device 160x64
> radeonfb (0000:05:00.0): ATI Radeon [b
> radeonfb_pci_register END
>
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2005-02-26 0:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 4:18 2.6.11-rc5 Linus Torvalds
2005-02-24 6:24 ` 2.6.11-rc5 Michael Neuffer
2005-02-24 15:49 ` 2.6.11-rc5 Linus Torvalds
2005-02-24 6:29 ` 2.6.11-rc5 Matt Mackall
2005-02-24 12:49 ` 2.6.11-rc5 Matthias-Christian Ott
2005-02-24 14:25 ` 2.6.11-rc5 Steven Rostedt
2005-02-24 14:57 ` 2.6.11-rc5 M.Baris Demiray
2005-02-24 15:39 ` 2.6.11-rc5 Sergey Vlasov
2005-02-24 15:57 ` 2.6.11-rc5 Steven Rostedt
2005-02-24 15:53 ` 2.6.11-rc5 Gabriel Paubert
2005-02-24 14:50 ` 2.6.11-rc5 Olaf Hering
2005-02-24 17:14 ` 2.6.11-rc5 Olaf Hering
2005-02-24 23:28 ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-25 7:08 ` 2.6.11-rc5 Olaf Hering
2005-02-25 7:29 ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-25 13:30 ` 2.6.11-rc5 Mws
2005-02-26 0:50 ` Benjamin Herrenschmidt [this message]
2005-03-01 11:36 ` 2.6.11-rc5 Mws
2005-03-01 14:36 ` 2.6.11-rc5 Helge Hafting
2005-03-01 14:39 ` 2.6.11-rc5 Mws
2005-03-01 21:38 ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-03-01 22:01 ` 2.6.11-rc5 Mws
2005-02-25 17:29 ` 2.6.11-rc5 Olaf Hering
2005-02-25 17:59 ` [Linux-fbdev-devel] 2.6.11-rc5 James Simmons
2005-02-25 20:24 ` Olaf Hering
2005-02-25 21:21 ` Olaf Hering
2005-02-25 23:30 ` Olaf Hering
2005-02-26 1:01 ` Benjamin Herrenschmidt
2005-02-26 9:52 ` Giuseppe Bilotta
2005-02-26 0:58 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-02-26 0:57 ` Benjamin Herrenschmidt
2005-02-26 0:54 ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-26 0:41 ` 2.6.11-rc5 Olaf Hering
2005-02-26 0:49 ` 2.6.11-rc5 Linus Torvalds
2005-02-26 0:53 ` 2.6.11-rc5 Olaf Hering
2005-02-26 1:04 ` 2.6.11-rc5 Linus Torvalds
2005-02-26 1:08 ` [Linux-fbdev-devel] 2.6.11-rc5 Buttchereit, Axel (XL)
2005-02-26 1:17 ` Benjamin Herrenschmidt
2005-02-26 1:13 ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-26 7:41 ` [Linux-fbdev-devel] 2.6.11-rc5 Antonino A. Daplas
2005-02-27 8:07 ` 2.6.11-rc5 Geert Uytterhoeven
2005-02-24 15:57 ` 2.6.11-rc5 (compile stats) John Cherry
2005-02-24 16:30 ` 2.6.11-rc5 Brian Gerst
2005-02-24 17:00 ` 2.6.11-rc5 Linus Torvalds
2005-02-25 21:47 ` 2.6.11-rc5 Bill Davidsen
2005-02-25 21:50 ` 2.6.11-rc5 Lee Revell
2005-02-26 5:03 ` 2.6.11-rc5 Bill Davidsen
2005-02-27 20:32 ` 2.6.11-rc5, rivafb i2c oops, bogus error handling Olaf Hering
2005-02-28 14:41 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-03-01 12:02 ` Olaf Hering
2005-03-01 20:58 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2005-02-24 6:23 2.6.11-rc5 Voluspa
[not found] <3BjgD-5iu-7@gated-at.bofh.it>
2005-02-25 16:28 ` 2.6.11-rc5 Vincent C Jones
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=1109379043.14993.93.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mws@twisted-brains.org \
/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