Does it work fine if you boot first into MacOS and then launch BootX?
If so, then check the archives. I have had this problem ever since I
Linux'd my OldWorld 8500 back in 2000.
As I recall, direct booting required some specific firmware
settings--and an external TTY (or emulator) was
Greetings to you all,
I tried to use kernel-images but I couldn't even boot it (kernel panic).
Obviously, as you already know, oldworld macs use BootX, so I even tried with
different arguments (with initrd and without initrd, ie) but it wouldn't boot.
I decided to compile 2.6.8.1 (as I had done
Jens Schmalzing ([EMAIL PROTECTED]) wrote:
Hi,
Mauricio Hernandez Z. writes:
I tried to use kernel-images but I couldn't even boot it (kernel
panic). Obviously, as you already know, oldworld macs use BootX, so
I even tried with different arguments (with initrd and without
initrd, ie)
Hi,
Mauricio Hernandez Z. writes:
I tried to use kernel-images but I couldn't even boot it (kernel
panic). Obviously, as you already know, oldworld macs use BootX, so
I even tried with different arguments (with initrd and without
initrd, ie) but it wouldn't boot.
BootX booting works fine
Hi,
Mauricio Hernandez Z. writes:
That was my 1st thought too but I had already set it.
CONFIG_FRAMEBUFFER_CONSOLE=y
Then it is possible that for some reason the console is showing you
black text on black background.
I have attached my .config just in case.
Build the accelerated driver
5 matches
Mail list logo
