-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
On Sat, Sep 23, 2006 at 11:35:28PM +0300, Eddy Petrişor wrote:
On 23/09/06, Attilio Fiandrotti [EMAIL PROTECTED] wrote:
Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attilio Fiandrotti wrote:
Eddy Petrişor wrote:
On 25/09/06, Eddy Petrişor [EMAIL PROTECTED] wrote:
Eddy, do you have the chance to test if forcing off DFB's HW
acceleration makes g-i run on your Mac?
At Sven's suggestion, I have ran the
OK,
I booted from the CD with install DEBIAN_FRONTEND=newt
switched to the F2 console when the choose language screen came up.
The hardware info you wanted is:
~# cat /proc/cpuinfo | grep motherboard
Motherboard: PowerMac3,5 MacRISC2 MacRISC Power Macintosh
~# cat /proc/fb
0 ATI Radeon QW
OK,
I booted from the CD with install DEBIAN_FRONTEND=newt
switched to the F2 console when the choose language screen came up.
Then I did:
~# echo disable-module=radeon /etc/directfbrc
~# echo no-hardware /etc/directfbrc
~# export DEBIAN_FRONTEND=gtk
~# debian-installer
It crashed when it
On Sep 27, 2006, at 7:03 PM, Rick Thomas wrote:
(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and
current mode not supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0,
8/0, 0/0 (8bit)
For what it's worth, there is no file /etc/fb.modes in the
Rick Thomas wrote:
OK,
I booted from the CD with install DEBIAN_FRONTEND=newt
switched to the F2 console when the choose language screen came up.
The hardware info you wanted is:
~# cat /proc/cpuinfo | grep motherboard
Motherboard: PowerMac3,5 MacRISC2 MacRISC Power Macintosh
~# cat /proc/fb
On 25/09/06, Eddy Petrişor [EMAIL PROTECTED] wrote:
A round of PPC tests would be useful, especially it happens to find
owners of ATI or NVIDIA boards.
Got one.
Eddy, do you have the chance to test if forcing off DFB's HW
acceleration makes g-i run on your Mac?
I did, (Sven knows),
Eddy Petrişor wrote:
On 25/09/06, Eddy Petrişor [EMAIL PROTECTED] wrote:
A round of PPC tests would be useful, especially it happens to find
owners of ATI or NVIDIA boards.
Got one.
Eddy, do you have the chance to test if forcing off DFB's HW
acceleration makes g-i run on your
On Sep 24, 2006, at 5:52 AM, Sven Luther wrote:
On Sun, Sep 24, 2006 at 04:17:58AM -0400, Rick Thomas wrote:
On Sep 23, 2006, at 6:13 AM, Sven Luther wrote:
Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc
On Tue, Sep 26, 2006 at 04:01:15PM -0400, Rick Thomas wrote:
On Sep 24, 2006, at 5:52 AM, Sven Luther wrote:
On Sun, Sep 24, 2006 at 04:17:58AM -0400, Rick Thomas wrote:
On Sep 23, 2006, at 6:13 AM, Sven Luther wrote:
Also, about the console font corruption with radeonfb, i would be
On Tue, Sep 26, 2006 at 04:48:51PM -0400, Rick Thomas wrote:
On Sep 26, 2006, at 4:04 PM, Sven Luther wrote:
On Tue, Sep 26, 2006 at 04:01:15PM -0400, Rick Thomas wrote:
OK. I have a G4 PowerMac with
:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon
RV200 QW [Radeon
On Sep 26, 2006, at 4:04 PM, Sven Luther wrote:
On Tue, Sep 26, 2006 at 04:01:15PM -0400, Rick Thomas wrote:
OK. I have a G4 PowerMac with
:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon
RV200 QW [Radeon 7500]
Should work flawlessly with the current daily-builds.
On 23/09/06, Attilio Fiandrotti [EMAIL PROTECTED] wrote:
Eddy Petrişor wrote:
snip/
A round of PPC tests would be useful, especially it happens to find
owners of ATI or NVIDIA boards.
Got one.
Eddy, do you have the chance to test if forcing off DFB's HW
acceleration makes g-i run on your
On Sep 23, 2006, at 6:13 AM, Sven Luther wrote:
Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc stuff ?
No idea, i on no radeon boards :(
Someone else ?
I might have a NewWorld Mac with a radeon board...
On Sunday 24 September 2006 10:17, Rick Thomas wrote:
Is there an iso I can burn with the necessary stuff on it? I'm not
set up to do netbooting at this moment.
There is only an iso. Look for gtk-miniiso under powerpc/powerpc64:
http://people.debian.org/~wouter/d-i/powerpc/daily/
On Sun, Sep 24, 2006 at 04:17:58AM -0400, Rick Thomas wrote:
On Sep 23, 2006, at 6:13 AM, Sven Luther wrote:
Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc stuff ?
No idea, i on no radeon boards :(
Sven Luther wrote:
On Fri, Sep 22, 2006 at 10:40:34PM +0200, Frans Pop wrote:
On Friday 22 September 2006 21:32, Sven Luther wrote:
We did never implement the thingy which disables the acceleration in
the directfbrc, right ?
I've committed a patch now that always disables it for ppc.
On Sat, Sep 23, 2006 at 10:53:56AM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
On Fri, Sep 22, 2006 at 10:40:34PM +0200, Frans Pop wrote:
On Friday 22 September 2006 21:32, Sven Luther wrote:
We did never implement the thingy which disables the acceleration in
the directfbrc,
On Sat, Sep 23, 2006 at 12:07:45PM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
snip/
I belive disabling hw acceleration on PPC machines is a good choice, as
we're interested in stability, not performance, and i also belive
performance drop won't be even detectable in the case of
Sven Luther wrote:
snip/
I belive disabling hw acceleration on PPC machines is a good choice, as
we're interested in stability, not performance, and i also belive
performance drop won't be even detectable in the case of a simple DFB
application like our GTK frontend.
By the way, i think
Sven Luther wrote:
/snip
That's a good idea.
I also wonder if kernels shipped in d-i include or not modules for
hardware specific framebuffer devices, or generic drivers (like vesafb
on i386) only.
CONFIG_FB_CIRRUS=m
CONFIG_FB_OF=y
CONFIG_FB_CONTROL=y
CONFIG_FB_PLATINUM=y
Sven Luther wrote:
snip/
Yes, i saw the vanished lines in your screenshots and i belive this may
be #385026, which is GTKDFB 2.8.x related and affects all HW platforms.
As Frans said, this is a quite annoying bug and i'll try to see if i can
fix it in GTKDFB 2.8.20 with a small patch (but
On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:
looking at DFB's supported-hardware page
http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics
i can see some of those fb modules may allow DFB to run in hw
accelerated mode, but for many of them no
On Sat, Sep 23, 2006 at 01:56:40PM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
snip/
Yes, i saw the vanished lines in your screenshots and i belive this may
be #385026, which is GTKDFB 2.8.x related and affects all HW platforms.
As Frans said, this is a quite annoying bug and
Mmm,
nogo on the xgi card, since 2.6.16/17 have the sisfb framebuffer device not
builtin, but modular.
Is there some place where we can do some kind of framebuffer device detection,
and loading of the appropriate modules ? Where is it done for vesafb, which if
i am not wrong, is modular on x86 ?
On Saturday 23 September 2006 16:17, Sven Luther wrote:
Is there some place where we can do some kind of framebuffer device
detection, and loading of the appropriate modules ? Where is it done
for vesafb, which if i am not wrong, is modular on x86 ?
That should also be an issue for the newt
On Saturday 23 September 2006 12:45, Attilio Fiandrotti wrote:
Speaking generically, i don't know how much is safe having DFB running
in accelerated mode using fb module X on architecture Y.
An extensive set of tests to detect bad X,Y couples looks dificlut to
be performed, so to be sure the
On Sat, Sep 23, 2006 at 05:09:15PM +0200, Frans Pop wrote:
On Saturday 23 September 2006 16:17, Sven Luther wrote:
Is there some place where we can do some kind of framebuffer device
detection, and loading of the appropriate modules ? Where is it done
for vesafb, which if i am not wrong, is
Frans Pop wrote:
On Saturday 23 September 2006 12:45, Attilio Fiandrotti wrote:
Speaking generically, i don't know how much is safe having DFB running
in accelerated mode using fb module X on architecture Y.
An extensive set of tests to detect bad X,Y couples looks dificlut to
be performed, so
On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:
looking at DFB's supported-hardware page
http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics
Well, ...
I did some try with my xgi card, and even though i disabled hardware
acceleration, this is a nogo. I ended
On 23/09/06, Attilio Fiandrotti [EMAIL PROTECTED] wrote:
Also, about the console font corruption with radeonfb, i would be interested
in feedback of if it is a powerpc only issue, or ppc stuff ?
No idea, i on no radeon boards :(
$ lspci | grep ATI
:00:10.0 VGA compatible controller:
On Sat, Sep 23, 2006 at 10:13:10PM +0200, Sven Luther wrote:
On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:
looking at DFB's supported-hardware page
http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics
Well, ...
I did some try with my xgi card, and
On Sat, Sep 23, 2006 at 11:35:28PM +0300, Eddy Petrişor wrote:
On 23/09/06, Attilio Fiandrotti [EMAIL PROTECTED] wrote:
Also, about the console font corruption with radeonfb, i would be
interested
in feedback of if it is a powerpc only issue, or ppc stuff ?
No idea, i on no radeon boards
Sven Luther wrote:
On Sat, Sep 23, 2006 at 10:13:10PM +0200, Sven Luther wrote:
On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:
looking at DFB's supported-hardware page
http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics
Well, ...
I did some try with my
Sven Luther wrote:
On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:
looking at DFB's supported-hardware page
http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics
Well, ...
I did some try with my xgi card, and even though i disabled hardware
acceleration,
Eddy Petrişor wrote:
snip/
A round of PPC tests would be useful, especially it happens to find
owners of ATI or NVIDIA boards.
Got one.
Eddy, do you have the chance to test if forcing off DFB's HW
acceleration makes g-i run on your Mac?
On Sat, Sep 23, 2006 at 10:50:37PM +0200, Attilio Fiandrotti wrote:
IIUC, you loaded the per-card (SiS) fb device, but DFB ran unaccelerated
because it didn't recognize the board and furthermore acceleration was
forced off, right?
No, i didn't even get into gtk-di, i ended up in a somewhat
On Sat, Sep 23, 2006 at 10:46:05PM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:
looking at DFB's supported-hardware page
http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics
Well, ...
I did some
Sven Luther wrote:
On Thu, Sep 21, 2006 at 03:32:28PM +0200, Frans Pop wrote:
severity 342053 important
thanks
Lowering the severity of this bug to important.
This issue is the main reason that g-i is only provided as experimental
mini.iso for powerpc. However, that does not make RC for the
On Fri, Sep 22, 2006 at 09:37:28AM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
On Thu, Sep 21, 2006 at 03:32:28PM +0200, Frans Pop wrote:
severity 342053 important
thanks
Lowering the severity of this bug to important.
This issue is the main reason that g-i is only provided as
Sven Luther wrote:
snip/
Last times the g-i was tested on PPC, it turned tout that
Known good : radeonfb, vesafb (or whatever x86 uses).
vesafb is not built on powerpc, and the laptop we had in extremadura used a
radeon chipset, altough of the R300 variety.
isn't fbonly the PPC equivalent
On Fri, Sep 22, 2006 at 02:52:24PM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
snip/
Last times the g-i was tested on PPC, it turned tout that
Known good : radeonfb, vesafb (or whatever x86 uses).
vesafb is not built on powerpc, and the laptop we had in extremadura used a
Well,
My first naive test with the unstable g-i, gives just a blue screen. I can
alt-ctr-f2 away, and check a bit.
We did never implement the thingy which disables the acceleration in the
directfbrc, right ?
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Sven Luther wrote:
On Fri, Sep 22, 2006 at 02:52:24PM +0200, Attilio Fiandrotti wrote:
Sven Luther wrote:
snip/
Last times the g-i was tested on PPC, it turned tout that
Known good : radeonfb, vesafb (or whatever x86 uses).
vesafb is not built on powerpc, and the laptop we had in
On Friday 22 September 2006 21:32, Sven Luther wrote:
We did never implement the thingy which disables the acceleration in
the directfbrc, right ?
I've committed a patch now that always disables it for ppc.
pgpu2hF2ZnaR2.pgp
Description: PGP signature
On Fri, Sep 22, 2006 at 09:37:28AM +0200, Attilio Fiandrotti wrote:
Last times the g-i was tested on PPC, it turned tout that
Known good : radeonfb, vesafb (or whatever x86 uses).
Known bad : atyfb, nvidiafb
when acceleration was enabled.
But that was with GTKDFB 2.0.9 and DFB 0.9.22,
On Fri, Sep 22, 2006 at 10:40:34PM +0200, Frans Pop wrote:
On Friday 22 September 2006 21:32, Sven Luther wrote:
We did never implement the thingy which disables the acceleration in
the directfbrc, right ?
I've committed a patch now that always disables it for ppc.
Thanks,
Friendly,
Processing commands for [EMAIL PROTECTED]:
severity 342053 important
Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers
are used
Severity set to `important' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
severity 342053 important
thanks
Lowering the severity of this bug to important.
This issue is the main reason that g-i is only provided as experimental
mini.iso for powerpc. However, that does not make RC for the package as a
whole.
pgputmxClUlr0.pgp
Description: PGP signature
On Thu, Sep 21, 2006 at 03:32:28PM +0200, Frans Pop wrote:
severity 342053 important
thanks
Lowering the severity of this bug to important.
This issue is the main reason that g-i is only provided as experimental
mini.iso for powerpc. However, that does not make RC for the package as a
50 matches
Mail list logo