Re: G4 widescreen powerbook

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

Hello,

On Jul 12, 2007, at 05:53, Andreas Moschos wrote:

>>
>> > it seems like a modeline issue to me but after
using:
>> > ModeLine "1440x900" 96.2 1440 1504
1536 1760 900 903 906 912
>> > had the same results.
>> > iBookHacks is enabled.
>>  
>> Well it was not a modeline issue.
>>
>> Unfortunately the radeon driver heavily depends on
reading pll
>> parameters from the firmware ROM which currently
doesn't work on 
>> macppc
>> ( not sure why - either the driver doesn't like
OpenFirmware or it
>> doesn't find the ROM )
>> As an ugly workaround you can use the wsfb driver -
that will be stuck
>> in whatever the console used and won't have
acceleration but it should
>> at least work.
>>  
> using a section "Device" with wsfb did not
work for me.Log file said:
> (II) wsfb: driver for wsdisplay framebuffer: wsfb
> (II) Primary Device is: PCI 00:10:0
> (EE) No devices detected
>  
> Note that BusID is "PCI:0:16:0" for radeon in
the config file
> Maybe a misconfiguration from me?

What does your device section look like? wsfb doesn't need
any 
additional parameters ( no bus ID or anything like that - it
doesn't 
know or care about buses, instead it will try to use
whatever can be 
mapped via ttyE0 )
And you can easily check if your BusID is right - pcictl
pci0 dump will 
list all PCI devices that can be found on the 1st PCI host
bridge, on 
Macs that's usually the AGP port. On the other hand, if the
BusID was 
wrong the radeon driver would have complained too instead of
messing 
with the chip.

>> >  i thought of using a current kernel but i
only get coredumps of 
>> XFree
>> > with black screens.
>>
>> That's weird - where and how does it crash?
>>  
> Let me rephrase.It actuall lives me with a blank screen
and i find a 
> coredump of XFree.I did not try a remote session on
this one.

Even weirder - either XFree86 crashed very early or very
late, by 
default it will install a signal handler to catch events
leading to 
coredumps and does its own little dance instead of dumping
core which 
leads to annoying deadlocks sometimes ( if the signal
handler 
crashes... )

> But it finally worked! I stopped the wsmoused from
running and X 
> started succesfully, note that it works with both the
manually 
> configured Mode and without it 

I had a lot of trouble with wsmoused on macppc, for some
reason it 
doesn't seem to like bitmapped wsdisplays even though it
shouldn't know 
or care about the difference, or it's a bug I introduced
with machfb 
which got cargo-culted to all the others ;)

> So it does understand the widescreen format.

Nice 
For the records - please post your dmesg and XF86Config
along with an 
exact model name so the next guy in this situation can
easily google up 
your solution.

> One minor issue is that at the areas where i can see
garbage under 
> wscons i see something like "snow" under X
but if i use an xterm at 
> that area and issue a top or a clear it goes away and
comes back 
> gradually after a few moments!

That looks like a misdetected framebuffer memory size or
something 
messes in fb memory where it shouldn't. Could you send me
your 
XFree86.0.log in a private message?
And - does the garbage show up in screenshots? If it does
please send 
me one, to understand the problem I need to see it.

>> >  i also have issues with the output of the
wscons using the curret
>> > kernel.The first 20 lines (counting from the
top of the panel) are 
>> so
>> > meshed up i can see nothing (on all the
screens).
>>
>> Radeonfb has trouble on R3xx and newer,
unfortunately nobody with
>> access to such hardware did any debugging work that
I'm aware of so 
>> far
>> ( all I have is the RV280 in my iBook G4 which
works fine )
>>  
> if you think a debugging procedure could be started by
asking me some 
> data which i could get back to you please let me
now.Don't pick 
> lemons.

Ok, please mail me the following things privately:
- - dmesg output
- - your XF86Config
- - your XFree86.0.log
- - ofctl -p output
that should give me a pretty good idea of what your hardware
is like 
and what X and radeonfb are trying to do with it.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRpYlkMpnzkX8Yg2nAQJKawf/aMbvcHMs86vYbpF+eOoFANMFSFoz
JH9U
WzmlXJXW8987345v5pt/MTlviPGsj7xRJHLqBVmELtGRnRnPj783LrwaTalT
n8KC
4urBnzhPC4naeFa6qrTH0XQ2vruOJJVwiG/ZD73R6l99redClHn/owBT4EeZ
+8Fv
W5j+MtgvQQ0DMHycpio2DsBgqwx1NOtIanv6/NBwMJykv41v7HWw1+rcLkr7
rQZs
Ak0Y5Bygq+afOBehvh2teyA9yZ23gkdiXK/JfaW5yHhDYfBW+5YeIPyXDy+m
yxMb
pa9wqcHe0nZfY5r/kX9qCfR/Aybpccay0anPHZqiB3d7ZgwPkV53CQ==
=d5pg
-----END PGP SIGNATURE-----