public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Radeonfb problem
@ 2004-02-17 19:08 Sergio Vergata
  2004-02-17 20:36 ` Kronos
  0 siblings, 1 reply; 12+ messages in thread
From: Sergio Vergata @ 2004-02-17 19:08 UTC (permalink / raw)
  To: Linux Kernel list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
I'v 2.6.3-rc3-mm1 up and running on an t40p.
ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02)
The problem i observe was that reset won't clean my display just draw the new 
commandline on the upper left. The screen still old display. 

Don't know if anyone can aprove that.

Cu Sergio 

- -- 
Microsoft is to operating systems & security ....
             .... what McDonalds is to gourmet cooking

PGP-Key http://vergata.it/GPG/F17FDB2F.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAMma0VP5w5vF/2y8RAqJLAJ9Ca4B/Et/foy+b620B1udvg5E8HgCgyCWN
YyjSsPf8nLzd6lLph+gzWZY=
=JcF9
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 19:08 Radeonfb problem Sergio Vergata
@ 2004-02-17 20:36 ` Kronos
  2004-02-17 21:11   ` Damian Kolkowski
  0 siblings, 1 reply; 12+ messages in thread
From: Kronos @ 2004-02-17 20:36 UTC (permalink / raw)
  To: linux-kernel; +Cc: Sergio Vergata

Sergio Vergata <vergata@stud.fbi.fh-darmstadt.de> ha scritto:
> I'v 2.6.3-rc3-mm1 up and running on an t40p.
> ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02)
> The problem i observe was that reset won't clean my display just draw the new 
> commandline on the upper left. The screen still old display. 

Are you running X? This is a known problem, it's X fiddling with accel
registers. BenH is working on a fix, for now you can boot with "noaccel"
to disable hw acceleration.

Btw, how does 2.6.3-rc4 work?

Luca
-- 
Home: http://kronoz.cjb.net
Ligabue canta: "Tutti vogliono viaggiare in primaaaa..."
Io ci ho provato e dopo un chilometro ho fuso il motore e bruciato
la frizione...

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 20:36 ` Kronos
@ 2004-02-17 21:11   ` Damian Kolkowski
  2004-02-17 21:34     ` Kronos
  0 siblings, 1 reply; 12+ messages in thread
From: Damian Kolkowski @ 2004-02-17 21:11 UTC (permalink / raw)
  To: Kronos; +Cc: linux-kernel, Sergio Vergata

* Kronos <kronos@kronoz.cjb.net> [2004-02-17 21:53]:
> Sergio Vergata <vergata@stud.fbi.fh-darmstadt.de> ha scritto:
> > I'v 2.6.3-rc3-mm1 up and running on an t40p.
> > ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02)
> > The problem i observe was that reset won't clean my display just draw the new 
> > commandline on the upper left. The screen still old display. 
> 
> Are you running X? This is a known problem, it's X fiddling with accel
> registers. BenH is working on a fix, for now you can boot with "noaccel"
> to disable hw acceleration.
> 
> Btw, how does 2.6.3-rc4 work?

2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for radeonfb
wont work.

P.S. I have rv250if.

-- 
# Damian *dEiMoS* Kołkowski # http://kolkowski.no-ip.org/ #

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 21:11   ` Damian Kolkowski
@ 2004-02-17 21:34     ` Kronos
  2004-02-17 21:57       ` Damian Kolkowski
  0 siblings, 1 reply; 12+ messages in thread
From: Kronos @ 2004-02-17 21:34 UTC (permalink / raw)
  To: linux-kernel, Sergio Vergata

Il Tue, Feb 17, 2004 at 10:11:20PM +0100, Damian Kolkowski ha scritto: 
> > Btw, how does 2.6.3-rc4 work?
> 
> 2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for radeonfb
> wont work.

What do you mean? What are passing to the kernel?

Luca
-- 
Home: http://kronoz.cjb.net
42

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 21:34     ` Kronos
@ 2004-02-17 21:57       ` Damian Kolkowski
  2004-02-17 22:22         ` Benjamin Herrenschmidt
  0 siblings, 1 reply; 12+ messages in thread
From: Damian Kolkowski @ 2004-02-17 21:57 UTC (permalink / raw)
  To: Kronos; +Cc: linux-kernel, Sergio Vergata

* Kronos <kronos@kronoz.cjb.net> [2004-02-17 22:51]:
> > 2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for radeonfb
> > wont work.
> 
> What do you mean? What are passing to the kernel?

For example:

append = "video=radeon:1024x768-32@100" works for 2.4.x
append = "video=radeonfb:1024x768-32@100 works for 2.6.x

but for new radeonfb _radeonfb_ in append won't work, my screean start with
small res on 36 Hz ;-) So I need to use fbset.

Besides don't use 2.6.x even on desktop, that was only a test with new
radeonfb from Ben H.

-- 
# Damian *dEiMoS* Kołkowski # http://kolkowski.no-ip.org/ #

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 21:57       ` Damian Kolkowski
@ 2004-02-17 22:22         ` Benjamin Herrenschmidt
  2004-02-18  0:02           ` Sergio Vergata
                             ` (3 more replies)
  0 siblings, 4 replies; 12+ messages in thread
From: Benjamin Herrenschmidt @ 2004-02-17 22:22 UTC (permalink / raw)
  To: Damian Kolkowski; +Cc: Kronos, Linux Kernel list, Sergio Vergata

On Wed, 2004-02-18 at 08:57, Damian Kolkowski wrote:
> * Kronos <kronos@kronoz.cjb.net> [2004-02-17 22:51]:
> > > 2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for radeonfb
> > > wont work.
> > 
> > What do you mean? What are passing to the kernel?
> 
> For example:
> 
> append = "video=radeon:1024x768-32@100" works for 2.4.x
> append = "video=radeonfb:1024x768-32@100 works for 2.6.x
> 
> but for new radeonfb _radeonfb_ in append won't work, my screean start with
> small res on 36 Hz ;-) So I need to use fbset.
> 
> Besides don't use 2.6.x even on desktop, that was only a test with new
> radeonfb from Ben H.

Ugh ? Send me a dmesg log at boot please without any command
line. radeonfb should set your display to the native panel size
by default

Ben.



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 22:22         ` Benjamin Herrenschmidt
@ 2004-02-18  0:02           ` Sergio Vergata
  2004-02-18  0:11             ` Benjamin Herrenschmidt
  2004-02-18 10:26           ` Damian Kolkowski
                             ` (2 subsequent siblings)
  3 siblings, 1 reply; 12+ messages in thread
From: Sergio Vergata @ 2004-02-18  0:02 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: Damian Kolkowski, Kronos, Linux Kernel list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, just build 2.6.3-rc4 and the problem still exists.

I tried also booting with commandline parameter and reduced the size to 
1280x1024 and 1024x768 both works fine for me 

The dmesg output, from booting without any parameter,  autodetection of the 
displaysize works fine.

Sergio

....
radeonfb_pci_register BEGIN
PCI: Found IRQ 6 for device 0000:01:00.0
PCI: Sharing IRQ 6 with 0000:00:1d.0
PCI: Sharing IRQ 6 with 0000:02:00.0
PCI: Sharing IRQ 6 with 0000:02:01.0
radeonfb: probed DDR SGRAM 65536k videoram
radeonfb: mapped 16384k videoram
radeonfb: Invalid ROM signature 0 should be 0xaa55
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=252.00 Mhz, System=200.00 MHz
1 chips in connector info
 - chip 1 has 2 connectors
  * connector 0 of type 2 (CRT) : 2300
  * connector 1 of type 4 (DVI-D) : 4201
Starting monitor auto detection...
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: SXGA+ Single (85MHz)    
radeonfb: detected LVDS panel size from BIOS: 1400x1050
BIOS provided panel power delay: 1000
radeondb: BIOS provided dividers will be used
ref_divider = 6
post_divider = 2
fbk_divider = 4c
Scanning BIOS table ...
 320 x 350
 320 x 400
 320 x 400
 320 x 480
 400 x 600
 512 x 384
 640 x 350
 640 x 400
 640 x 475
 640 x 480
 800 x 600
 1024 x 768
 1152 x 864
 1280 x 1024
 1400 x 1050
Found panel in BIOS table:
  hblank: 200
  hOver_plus: 72
  hSync_width: 40
  vblank: 12
  vOver_plus: 2
  vSync_width: 1
  clock: 8496
Setting up default mode based on panel info
radeonfb: Power Management enabled for Mobility chipsets
radeonfb: ATI Radeon Lf  DDR SGRAM 64 MB
radeonfb_pci_register END
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
speedstep-centrino: found "Intel(R) Pentium(R) M processor 1600MHz": max 
frequency: 1600000kHz
ikconfig 0.7 with /proc/config*
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
hStart = 1472, hEnd = 1512, hTotal = 1600
vStart = 1052, vEnd = 1053, vTotal = 1062
h_total_disp = 0xae00c7	   hsync_strt_wid = 0x505ba
v_total_disp = 0x4190425	   vsync_strt_wid = 0x1041b
pixclock = 11770
freq = 8496
lvds_gen_cntl: 003dffa1
Console: switching to colour frame buffer device 175x65
...

On Tuesday 17 February 2004 23:22, Benjamin Herrenschmidt wrote:
> On Wed, 2004-02-18 at 08:57, Damian Kolkowski wrote:
> > * Kronos <kronos@kronoz.cjb.net> [2004-02-17 22:51]:
> > > > 2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for
> > > > radeonfb wont work.
> > >
> > > What do you mean? What are passing to the kernel?
> >
> > For example:
> >
> > append = "video=radeon:1024x768-32@100" works for 2.4.x
> > append = "video=radeonfb:1024x768-32@100 works for 2.6.x
> >
> > but for new radeonfb _radeonfb_ in append won't work, my screean start
> > with small res on 36 Hz ;-) So I need to use fbset.
> >
> > Besides don't use 2.6.x even on desktop, that was only a test with new
> > radeonfb from Ben H.
>
> Ugh ? Send me a dmesg log at boot please without any command
> line. radeonfb should set your display to the native panel size
> by default
>
> Ben.

- --
Microsoft is to operating systems & security ....
             .... what McDonalds is to gourmet cooking

PGP-Key http://vergata.it/GPG/F17FDB2F.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAMqueVP5w5vF/2y8RAl1cAKDbvE0+Rw5IlzaLBIQOTbFdhtN+cACgxvYi
NagkT2Buid3GhhQQdyNwfk4=
=veYH
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-18  0:02           ` Sergio Vergata
@ 2004-02-18  0:11             ` Benjamin Herrenschmidt
  0 siblings, 0 replies; 12+ messages in thread
From: Benjamin Herrenschmidt @ 2004-02-18  0:11 UTC (permalink / raw)
  To: Sergio Vergata; +Cc: Damian Kolkowski, Kronos, Linux Kernel list

On Wed, 2004-02-18 at 11:02, Sergio Vergata wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Well, just build 2.6.3-rc4 and the problem still exists.
> 
> I tried also booting with commandline parameter and reduced the size to 
> 1280x1024 and 1024x768 both works fine for me 
> 
> The dmesg output, from booting without any parameter,  autodetection of the 
> displaysize works fine.

I'm getting mixed up in all the reports, especially since you are
replying to Damian, but I don't think you have the same problem.

So please, do a short summary of the problem, include full context
information in your email.

> Sergio
> 
> ....
> radeonfb_pci_register BEGIN
> PCI: Found IRQ 6 for device 0000:01:00.0
> PCI: Sharing IRQ 6 with 0000:00:1d.0
> PCI: Sharing IRQ 6 with 0000:02:00.0
> PCI: Sharing IRQ 6 with 0000:02:01.0
> radeonfb: probed DDR SGRAM 65536k videoram
> radeonfb: mapped 16384k videoram
> radeonfb: Invalid ROM signature 0 should be 0xaa55
> radeonfb: Retreived PLL infos from BIOS
> radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=252.00 Mhz, System=200.00 MHz
> 1 chips in connector info
>  - chip 1 has 2 connectors
>   * connector 0 of type 2 (CRT) : 2300
>   * connector 1 of type 4 (DVI-D) : 4201
> Starting monitor auto detection...
> Non-DDC laptop panel detected
> radeonfb: Monitor 1 type LCD found
> radeonfb: Monitor 2 type no found
> radeonfb: panel ID string: SXGA+ Single (85MHz)    
> radeonfb: detected LVDS panel size from BIOS: 1400x1050
> BIOS provided panel power delay: 1000
> radeondb: BIOS provided dividers will be used
> ref_divider = 6
> post_divider = 2
> fbk_divider = 4c
> Scanning BIOS table ...
>  320 x 350
>  320 x 400
>  320 x 400
>  320 x 480
>  400 x 600
>  512 x 384
>  640 x 350
>  640 x 400
>  640 x 475
>  640 x 480
>  800 x 600
>  1024 x 768
>  1152 x 864
>  1280 x 1024
>  1400 x 1050
> Found panel in BIOS table:
>   hblank: 200
>   hOver_plus: 72
>   hSync_width: 40
>   vblank: 12
>   vOver_plus: 2
>   vSync_width: 1
>   clock: 8496
> Setting up default mode based on panel info
> radeonfb: Power Management enabled for Mobility chipsets
> radeonfb: ATI Radeon Lf  DDR SGRAM 64 MB
> radeonfb_pci_register END
> SBF: Simple Boot Flag extension found and enabled.
> SBF: Setting boot flags 0x1
> Machine check exception polling timer started.
> speedstep-centrino: found "Intel(R) Pentium(R) M processor 1600MHz": max 
> frequency: 1600000kHz
> ikconfig 0.7 with /proc/config*
> Initializing Cryptographic API
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> hStart = 1472, hEnd = 1512, hTotal = 1600
> vStart = 1052, vEnd = 1053, vTotal = 1062
> h_total_disp = 0xae00c7	   hsync_strt_wid = 0x505ba
> v_total_disp = 0x4190425	   vsync_strt_wid = 0x1041b
> pixclock = 11770
> freq = 8496
> lvds_gen_cntl: 003dffa1
> Console: switching to colour frame buffer device 175x65
> ...
> 
> On Tuesday 17 February 2004 23:22, Benjamin Herrenschmidt wrote:
> > On Wed, 2004-02-18 at 08:57, Damian Kolkowski wrote:
> > > * Kronos <kronos@kronoz.cjb.net> [2004-02-17 22:51]:
> > > > > 2.6.3-rc4 with new radeonfb looks better, but in lilo.con append for
> > > > > radeonfb wont work.
> > > >
> > > > What do you mean? What are passing to the kernel?
> > >
> > > For example:
> > >
> > > append = "video=radeon:1024x768-32@100" works for 2.4.x
> > > append = "video=radeonfb:1024x768-32@100 works for 2.6.x
> > >
> > > but for new radeonfb _radeonfb_ in append won't work, my screean start
> > > with small res on 36 Hz ;-) So I need to use fbset.
> > >
> > > Besides don't use 2.6.x even on desktop, that was only a test with new
> > > radeonfb from Ben H.
> >
> > Ugh ? Send me a dmesg log at boot please without any command
> > line. radeonfb should set your display to the native panel size
> > by default
> >
> > Ben.
> 
> - --
> Microsoft is to operating systems & security ....
>              .... what McDonalds is to gourmet cooking
> 
> PGP-Key http://vergata.it/GPG/F17FDB2F.asc
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFAMqueVP5w5vF/2y8RAl1cAKDbvE0+Rw5IlzaLBIQOTbFdhtN+cACgxvYi
> NagkT2Buid3GhhQQdyNwfk4=
> =veYH
> -----END PGP SIGNATURE-----
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 22:22         ` Benjamin Herrenschmidt
  2004-02-18  0:02           ` Sergio Vergata
@ 2004-02-18 10:26           ` Damian Kolkowski
  2004-02-18 11:01             ` Benjamin Herrenschmidt
  2004-02-18 10:33           ` Damian Kolkowski
  2004-02-19 23:21           ` Joshua Kwan
  3 siblings, 1 reply; 12+ messages in thread
From: Damian Kolkowski @ 2004-02-18 10:26 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: Kronos, Linux Kernel list, Sergio Vergata

* Benjamin Herrenschmidt <benh@kernel.crashing.org> [2004-02-18 00:02]:
> Ugh ? Send me a dmesg log at boot please without any command
> line. radeonfb should set your display to the native panel size
> by default

Now I compiled 2.6.3-mm1 with new radeonfb. Clean boot without radeonfb append
sets 640x480 in 60 Hz, ok thats fine.

But..,

if I use fbset like this:

	fbset -fb /dev/fb0 -a -depth 32 1024x768-100

my CRT monitor MAG 786FD looks like ths:

|------------|
|     |      |
|  a  |      |
|     |      |
|-----|      |
|       b    |
|            |
|------------|

Where "a" is the visual screan after using fbset and "b" is my monitor.

So something is worng, besides when using higher resolution "a" fieald is
smaller then "b".

P.S. Using video=radeon:1024x768-32@100 in append is _NOT_ working for my
rv250if (radeon 9000 pro).

PP.S. Cursor is working fine on text terminal, but in graphics it's hangs when
protocol option is set to auto :-) Using "IMPS/2" works, but xterm is not
starting :-)

PPP.S. Ben please if you know tell me if fglrx works with new radeonfb without
hanging text terminal as it was in old radeonfb.

-- 
# Damian *dEiMoS* Kołkowski # http://kolkowski.no-ip.org/ #

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 22:22         ` Benjamin Herrenschmidt
  2004-02-18  0:02           ` Sergio Vergata
  2004-02-18 10:26           ` Damian Kolkowski
@ 2004-02-18 10:33           ` Damian Kolkowski
  2004-02-19 23:21           ` Joshua Kwan
  3 siblings, 0 replies; 12+ messages in thread
From: Damian Kolkowski @ 2004-02-18 10:33 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: Kronos, Linux Kernel list, Sergio Vergata

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

* Benjamin Herrenschmidt <benh@kernel.crashing.org> [2004-02-18 00:02]:
> Ugh ? Send me a dmesg log at boot please without any command
> line. radeonfb should set your display to the native panel size
> by default

Ups.., I forget too attache dmesg.

-- 
# Damian *dEiMoS* Kołkowski # http://kolkowski.no-ip.org/ #

[-- Attachment #2: dmesg_263mm1.txt --]
[-- Type: text/plain, Size: 13302 bytes --]

Linux version 2.6.3-mm1 (root@uran) (gcc version 3.3.3) #1 Wed Feb 18 10:52:03 CET 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
 BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
 BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
found SMP MP-table at 000f55b0
zapping low mappings.
On node 0 totalpages: 65520
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 61424 pages, LIFO batch:14
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.2 present.
ACPI: RSDP (v000 VKT400                                    ) @ 0x000f7070
ACPI: RSDT (v001 VKT400 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff3000
ACPI: FADT (v001 VKT400 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff3040
ACPI: MADT (v001 VKT400 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff6f80
ACPI: DSDT (v001 VKT400 AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 16
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, IRQ 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 dfl dfl)
ACPI BALANCE SET
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists
Initializing CPU#0
Kernel command line: BOOT_IMAGE=Slackware-NEW ro root=305 hdc=ide-scsi mem=nopentium
ide_setup: hdc=ide-scsi
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 1795.740 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 255816k/262080k available (1680k kernel code, 5528k reserved, 509k data, 332k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 3538.94 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:     After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU:     After all inits, caps: 0383fbf7 c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2200+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=-1
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1794.0545 MHz.
..... host bus clock speed is 265.0858 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040211
IOAPIC[0]: Set PCI routing entry (2-9 -> 0x71 -> IRQ 9 Mode:1 Active:1)
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [ALKA] (IRQs 20)
ACPI: PCI Interrupt Link [ALKB] (IRQs 21)
ACPI: PCI Interrupt Link [ALKC] (IRQs 22)
ACPI: PCI Interrupt Link [ALKD] (IRQs 23)
SCSI subsystem initialized
IOAPIC[0]: Set PCI routing entry (2-16 -> 0xa9 -> IRQ 16 Mode:1 Active:1)
00:00:08[A] -> 2-16 -> IRQ 16
IOAPIC[0]: Set PCI routing entry (2-17 -> 0xb1 -> IRQ 17 Mode:1 Active:1)
00:00:08[B] -> 2-17 -> IRQ 17
IOAPIC[0]: Set PCI routing entry (2-18 -> 0xb9 -> IRQ 18 Mode:1 Active:1)
00:00:08[C] -> 2-18 -> IRQ 18
IOAPIC[0]: Set PCI routing entry (2-19 -> 0xc1 -> IRQ 19 Mode:1 Active:1)
00:00:08[D] -> 2-19 -> IRQ 19
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
_CRS returns NULL! Using IRQ 21 fordevice (PCI Interrupt Link [ALKB]).
ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
IOAPIC[0]: Set PCI routing entry (2-21 -> 0xc9 -> IRQ 21 Mode:1 Active:1)
00:00:10[A] -> 2-21 -> IRQ 21
Pin 2-21 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
_CRS returns NULL! Using IRQ 20 fordevice (PCI Interrupt Link [ALKA]).
ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
IOAPIC[0]: Set PCI routing entry (2-20 -> 0xd1 -> IRQ 20 Mode:1 Active:1)
00:00:11[A] -> 2-20 -> IRQ 20
Pin 2-21 already programmed
_CRS returns NULL! Using IRQ 22 fordevice (PCI Interrupt Link [ALKC]).
ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
IOAPIC[0]: Set PCI routing entry (2-22 -> 0xd9 -> IRQ 22 Mode:1 Active:1)
00:00:11[C] -> 2-22 -> IRQ 22
_CRS returns NULL! Using IRQ 23 fordevice (PCI Interrupt Link [ALKD]).
ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 23
IOAPIC[0]: Set PCI routing entry (2-23 -> 0xe1 -> IRQ 23 Mode:1 Active:1)
00:00:11[D] -> 2-23 -> IRQ 23
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-23 already programmed
Pin 2-23 already programmed
Pin 2-23 already programmed
Pin 2-23 already programmed
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00178003
.......     : max redirection entries: 0017
.......     : PRQ implemented: 1
.......     : IO APIC version: 0003
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 001 01  0    0    0   0   0    1    1    39
 02 001 01  0    0    0   0   0    1    1    31
 03 001 01  0    0    0   0   0    1    1    41
 04 001 01  0    0    0   0   0    1    1    49
 05 001 01  0    0    0   0   0    1    1    51
 06 001 01  0    0    0   0   0    1    1    59
 07 001 01  0    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 001 01  0    1    0   1   0    1    1    71
 0a 001 01  0    0    0   0   0    1    1    79
 0b 001 01  0    0    0   0   0    1    1    81
 0c 001 01  0    0    0   0   0    1    1    89
 0d 001 01  0    0    0   0   0    1    1    91
 0e 001 01  0    0    0   0   0    1    1    99
 0f 001 01  0    0    0   0   0    1    1    A1
 10 001 01  1    1    0   1   0    1    1    A9
 11 001 01  1    1    0   1   0    1    1    B1
 12 001 01  1    1    0   1   0    1    1    B9
 13 001 01  1    1    0   1   0    1    1    C1
 14 001 01  1    1    0   1   0    1    1    D1
 15 001 01  1    1    0   1   0    1    1    C9
 16 001 01  1    1    0   1   0    1    1    D9
 17 001 01  1    1    0   1   0    1    1    E1
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9-> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ18 -> 0:18
IRQ19 -> 0:19
IRQ20 -> 0:20
IRQ21 -> 0:21
IRQ22 -> 0:22
IRQ23 -> 0:23
.................................... done.
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=250.00 Mhz, System=200.00 MHz
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
Monitor Operating Limits: From EDID
     H: 30-86KHz V: 50-160Hz DCLK: 180MHz
radeonfb: ATI Radeon If  DDR SGRAM 64 MB
Machine check exception polling timer started.
Initializing Cryptographic API
PCI: Via IRQ fixup for 0000:00:10.0, from 11 to 5
PCI: Via IRQ fixup for 0000:00:10.1, from 11 to 5
PCI: Via IRQ fixup for 0000:00:10.2, from 10 to 5
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Fan [FAN] (on)
ACPI: Processor [CPU0] (supports C1 C2)
ACPI: Thermal Zone [THRM] (40 C)
Console: switching to colour frame buffer device 80x30
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: AGP aperture is 128M @ 0xd0000000
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xdc00-0xdc07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 6E040L0, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: HL-DT-ST GCE-8480B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
 hda: hda1 hda2 < hda5 hda6 >
Console: switching to colour frame buffer device 80x30
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
i2c /dev entries driver
oprofile: using NMI interrupt.
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
BIOS EDD facility v0.12 2004-Jan-26, 1 devices found
Please report your BIOS at http://linux.dell.com/edd/results.html
ACPI: (supports S0 S1 S4 S5)
found reiserfs format "3.6" with standard journal
Reiserfs journal params: device hda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda5) for (hda5)
Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 332k freed
Adding 248968k swap on /dev/hda6.  Priority:-1 extents:1
blk: queue c13a0400, I/O limit 4095Mb (mask 0xffffffff)
via-rhine.c:v1.10-LK1.1.19-2.5  July-12-2003  Written by Donald Becker
  http://www.scyld.com/network/via-rhine.html
eth0: VIA VT6102 Rhine-II at 0xe800, 00:0a:e6:3e:7e:13, IRQ 23.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: HL-DT-ST  Model: CD-RW GCE-8480B   Rev: 1.03
  Type:   CD-ROM                             ANSI SCSI revision: 02
[drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon If R250 9000
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: irq 21, pci mem d1928000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
Via 686a/8233/8235 audio driver 1.9.1-ac4-2.5
via82cxxx: Six channel audio available
PCI: Setting latency timer of device 0000:00:11.5 to 64
ac97_codec: AC97 Audio codec, id: VIA97 (Unknown)
via82cxxx: board #1 at 0xE000, IRQ 22
eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
smbfs: Unrecognized mount option noexec

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-18 10:26           ` Damian Kolkowski
@ 2004-02-18 11:01             ` Benjamin Herrenschmidt
  0 siblings, 0 replies; 12+ messages in thread
From: Benjamin Herrenschmidt @ 2004-02-18 11:01 UTC (permalink / raw)
  To: Damian Kolkowski; +Cc: Kronos, Linux Kernel list, Sergio Vergata


> if I use fbset like this:
> 
> 	fbset -fb /dev/fb0 -a -depth 32 1024x768-100
> 
> my CRT monitor MAG 786FD looks like ths:
> 
> |------------|
> |     |      |
> |  a  |      |
> |     |      |
> |-----|      |
> |       b    |
> |            |
> |------------|
> 
> Where "a" is the visual screan after using fbset and "b" is my monitor.

Ok, I see what you mean. This is not a radeonfb problem at this point.

The problem is in the fbcon layer in 2.6 which doesn't adapt to
resolution changes. I have done some work to fix this but it's
not completely right yet. I'll submit something to Andrew & Linus
once I'm happy with it.

The append= you need is radeonfb=, not radeon=

I don't think the cursor issue is related at all. And I don't know
what's up with the firegl binary drivers.

Ben.


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Radeonfb problem
  2004-02-17 22:22         ` Benjamin Herrenschmidt
                             ` (2 preceding siblings ...)
  2004-02-18 10:33           ` Damian Kolkowski
@ 2004-02-19 23:21           ` Joshua Kwan
  3 siblings, 0 replies; 12+ messages in thread
From: Joshua Kwan @ 2004-02-19 23:21 UTC (permalink / raw)
  To: Linux Kernel list

On Wed, Feb 18, 2004 at 09:22:12AM +1100, Benjamin Herrenschmidt wrote:
> Ugh ? Send me a dmesg log at boot please without any command
> line. radeonfb should set your display to the native panel size
> by default

Hmm, this is a bit offtopic, Ben, but do you know why my flat panel
using radeonfb spews half a screenful of junk onto the screen when
switching to FB mode at boot time, which later scrolls away?

It's been a problem since as far back as 2.5.59.

My Mobility Radeon is a M6 LY. If you need any other information such as
kernel config and dmesg, sorry, I'm without my laptop right now as I'm
across the country visiting Carnegie Mellon... you'd have to wait until
Saturday. Just wanted to let you know of the issue.

-- 
Joshua Kwan

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2004-02-19 23:27 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-17 19:08 Radeonfb problem Sergio Vergata
2004-02-17 20:36 ` Kronos
2004-02-17 21:11   ` Damian Kolkowski
2004-02-17 21:34     ` Kronos
2004-02-17 21:57       ` Damian Kolkowski
2004-02-17 22:22         ` Benjamin Herrenschmidt
2004-02-18  0:02           ` Sergio Vergata
2004-02-18  0:11             ` Benjamin Herrenschmidt
2004-02-18 10:26           ` Damian Kolkowski
2004-02-18 11:01             ` Benjamin Herrenschmidt
2004-02-18 10:33           ` Damian Kolkowski
2004-02-19 23:21           ` Joshua Kwan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox