On Tue, Nov 28, 2006 at 08:37:26AM +0100, [EMAIL PROTECTED] wrote:
> Well, this has nothing to do with i810. With fbdev, you have no video
> overlay, no hardware GL accelleration, not even 2D accelleration,
> right?
Correct. Maybe I'm old school, but I didn't notice much of a problem as
long as
On Mon, Nov 27, 2006 at 23:06:18 -0800, Ralph Giles wrote:
> On Tue, Nov 28, 2006 at 07:46:32AM +0100, Tino Keitel wrote:
>
> > Not only for the proprietary video drivers. The i810 Xorg driver
> > (needed in minis and macbooks) needs na VESA BIOS, too. Or has that
> > changed recently?
>
> I've b
On Tue, Nov 28, 2006 at 07:46:32AM +0100, Tino Keitel wrote:
> Not only for the proprietary video drivers. The i810 Xorg driver
> (needed in minis and macbooks) needs na VESA BIOS, too. Or has that
> changed recently?
I've been using the fbdev driver. It's been painful since the ShadowFB
stride
On Mon, Nov 27, 2006 at 13:55:44 -0800, Ralph Giles wrote:
> On Mon, Nov 27, 2006 at 01:38:06PM -0800, Jay Lewis wrote:
>
> > I am inherently suspect of the legacy boot stuff. I suppose those who
> > use it have their reasons, but I'm all for moving ahead and leaving the
> > old bios behind!
>
>
On Mon, Nov 27, 2006 at 11:27:29PM +0100, gimli wrote:
> I have added a missing patch to 2.6.18 for booting using elilo.
> It was broken from 2.6.17 to 2.6.18.
Thanks! That fixed the problem. I guess most people are using the legacy
bios then?
-r
---
I have added a missing patch to 2.6.18 for booting using elilo.
It was broken from 2.6.17 to 2.6.18.
cu
Edgar (gimli) Hucek
Ralph Giles schrieb:
> On Mon, Nov 27, 2006 at 01:38:06PM -0800, Jay Lewis wrote:
>
>> I am inherently suspect of the legacy boot stuff. I suppose those who
>> use it have
On Mon, Nov 27, 2006 at 01:38:06PM -0800, Jay Lewis wrote:
> I am inherently suspect of the legacy boot stuff. I suppose those who
> use it have their reasons, but I'm all for moving ahead and leaving the
> old bios behind!
Well, me too, but it's occasionally useful for the proprietary video
dr
Have you tried updating your firmware?
I am inherently suspect of the legacy boot stuff. I suppose those who
use it have their reasons, but I'm all for moving ahead and leaving the
old bios behind!
The legacy boot option has always failed with my refit configuration
(same error as yours) but it
Speaking of using 2.6.17.6, I've not had any luck updating to 2.6.18.
All of the builds I've tried, with 18, 18.1, 18.3 plus the then-current
mactel-linux patch set have hung on boot. In efi, before changing the
screen from the refit menu, and with the legacy bios boot through I
get a "Hard Dis
