-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, On Apr 15, 2009, at 8:57 AM, T. M. Pederson wrote:
Morning, On Fri, 10 Apr 2009 20:46:47 -0400 Michael <macallan%netbsd.org@localhost> wrote: [...]Please try radeonfb just to see if it makes any difference.Okay. I'll likely be compiling that later today.I have another idea. Please run pcictl pci0 dump -d <whatever device number your radeon is on, pcictl pci0 list should tell you> beforestarting X, then start X like before, just with an xterm, run the samecommand and look for differences in the BARs. If the Xserver feels like messing with the BARs then whatever console driver we use would cause a panic immediately when trying to write video memory. I don't really see evidence of this but who knows.Okay. I gave this a shot, and the diffs are in the "Common header" < 0x00: 0x59621002 0x02b00006 0x03000001 0x0000ff08 ---0x00: 0x59621002 0x02b00007 0x03000001 0x0000ff08And: < Command register: 0x0006 < I/O space accesses: off ---Command register: 0x0007 I/O space accesses: on
Oh for crying out loud. I/O access: on is the case that works?
Also, I set wscons=YES for this run, and tapping the vt switching key combo got: Failed to switch consoles (Inappropriate ioctl for device)
Not surprising if you don't have virtual consoles configured.
And when exiting the xterm, that was followed by: finished PLL2
That comes from the radeon driver. have fun Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQEVAwUBSeYGzMpnzkX8Yg2nAQLMNAf+JlYs2iop4c9KHsWxRgO2gvzaIiDqmcYh TegSp22yU5CmYvRLpYOaqmu6HSwPBNxDqSoCsZqt+lXUz2Rq6rQdu0MVNpGu+ysw H0D4MhP1l5/b1lGnRXs1fNvfsPCxkse68rI8jkFR7zbDScyufZdby2w/uMLGYK1G 0/Z0fjZYxcFe7jKjKdOob+Eh0oQwSQCoRQS3SIrrmBGFGUfQM0Lv689tsL29gS7u KTL4USVyD9rVRDW02UC5NJ61+qeTSVbSzjQno9NVnaoNozY73ldFpDjaVUCvAO21 vuiiXlxuqORPY9EAkTO40y2HU1VPVgHBxxxVedeh3fE+GCKbPBoTPg== =RU8K -----END PGP SIGNATURE-----