Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Tino
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

Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Ralph Giles
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

Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Tino Keitel
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! > >

Re: [Mactel-linux-users] naive question: read linux partion from OSX

2006-11-27 Thread Tobi Gschwendtner
did you try the force mount option ? without i have the same behavior. tobi Ralph Giles wrote: > On Sat, Nov 25, 2006 at 02:04:41PM -0800, Jay Lewis wrote: > > >> I have rebooted to verify, and for the record, kernel 2.6.17.13 (and >> later I assume) *is* able to write to journaled HFS+ file

Re: [Mactel-linux-users] naive question: read linux partion from OSX

2006-11-27 Thread Ralph Giles
On Sat, Nov 25, 2006 at 02:04:41PM -0800, Jay Lewis wrote: > I have rebooted to verify, and for the record, kernel 2.6.17.13 (and > later I assume) *is* able to write to journaled HFS+ filessytems. Odd, it still doesn't work for me now that I've got 2.6.18.3 working (but the built-in isight work

Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Ralph Giles
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 ---

Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread gimli
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

Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Ralph Giles
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

Re: [Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Jay Lewis
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

[Mactel-linux-users] boot problems with 2.6.18

2006-11-27 Thread Ralph Giles
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

Re: [Mactel-linux-users] naive question: read linux partion from OSX

2006-11-27 Thread Ralph Giles
On Sat, Nov 25, 2006 at 02:04:41PM -0800, Jay Lewis wrote: > I have rebooted to verify, and for the record, kernel 2.6.17.13 (and > later I assume) *is* able to write to journaled HFS+ filessytems. Yay, thanks for confirming. I was still on 2.6.17.6, where writing doesn't appear to work, even wh