Re: Booting 2.3.48 (devel) kernel problems?

Re: Booting 2.3.48 (devel) kernel problems?

[Benjamin Herrenschmidt]

On Wed, Mar 8, 2000, Michael Schmitz
<schmitz@opal.biophys.uni-duesseldorf.de> wrote:

>So the framebuffer got mapped from OF but not from BootX.

I think it worked with OF because we inherit from OF SDR1 and, by luck,
OF page tables are high enough in memory to not have been damaged by the
kernel. When booting via BootX, that's not the case.

We should not try to access the framebuffer from identify_machine() and
MMU_Init() unless it was mapped with a BAT in head.S (for debugging
purposes). In normal cases, it will get mapped via map_bootx_text called
from setup_arch() and can be used beyond that point.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Booting 2.3.48 (devel) kernel problems?

[enneper]

 Benjamin Herrenschmidt }  I think it worked with OF because we inherit from OF SDR1 and, by luck,
 Benjamin Herrenschmidt }  OF page tables are high enough in memory to not have been damaged by the

yes, 2.3.48 works with 3400-OF

there are three things so far:
-OF complains past the standart
	ok
	copying OF device tree ...done
 about:
	Initialising fake screen
	Failed to get address
 but lets linux make its way

-in something like mutt in aterm, colours and fonts scramble for their rights at the bottom of the window with a very useless result, a bit annoying.

-pcmcia compiles with:
i82365.c:110: warning: `do_scan' defined but not used
i82365.c:553: warning: `test_irq' defined but not used
i82365.c:737: warning: `add_socket' defined but not used
i82365.c:748: warning: `add_pcic' defined but not used
i82365.c:1499: warning: `init_i82365' defined but not used
i82365.c:1543: warning: `exit_i82365' defined but not used
but gets massive pci problems, so no driver is loaded.

greetings
Claus

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Booting 2.3.48 (devel) kernel problems?

[Michael Schmitz]

> >So the framebuffer got mapped from OF but not from BootX.
>
> I think it worked with OF because we inherit from OF SDR1 and, by luck,
> OF page tables are high enough in memory to not have been damaged by the
> kernel. When booting via BootX, that's not the case.
>
> We should not try to access the framebuffer from identify_machine() and
> MMU_Init() unless it was mapped with a BAT in head.S (for debugging
> purposes). In normal cases, it will get mapped via map_bootx_text called
> from setup_arch() and can be used beyond that point.

In his own words :-)

------------------------------------8<-----------------------------------
 - make sure setting the display BAT in arch/ppc/mm/init.c (MMU_Init) is
commented out, this is a hack and need some alignement tricks to work in
all cases. It should already be in #if 0/#endif

 - in arch/ppc/kernel/pmac_setup.c, comment out the content of the
function pmac_progress. (Or change pmac_init() so that it sets
ppc_md.progress to NULL, and set it to pmac_progress only
pmac_setup_arch()).

The problem is that pmac_progress will try to print to the framebuffer at
a time where it's not mapped (MMU_Init).
------------------------------------8<-----------------------------------

Or, in a diff:

--- arch/ppc/kernel/pmac_setup.c.org	Wed Mar  8 16:41:53 2000
+++ arch/ppc/kernel/pmac_setup.c	Wed Mar  8 16:41:12 2000
@@ -229,6 +229,10 @@
 	struct device_node *cpu;
 	int *fp;

+#ifdef CONFIG_BOOTX_TEXT
+	ppc_md.progress = pmac_progress;
+#endif
+
 	/* Set loops_per_sec to a half-way reasonable value,
 	   for use until calibrate_delay gets called. */
 	cpu = find_type_devices("cpu");
@@ -687,7 +691,7 @@
         ppc_ide_md.io_base = _IO_BASE;	/* actually too early for this :-(
*/
 #endif
 #ifdef CONFIG_BOOTX_TEXT
-	ppc_md.progress = pmac_progress;
+	ppc_md.progress = NULL;
 #endif
 	if (ppc_md.progress) ppc_md.progress("pmac_init(): exit", 0);

Just unconfiguring BOOTX_TEXT would have done the same trick I guess.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Booting 2.3.48 (devel) kernel problems?

[Robert Shaw]

I have a PowerBook G3 (1997) that I'm trying to get the latest devel kernel
compiled and booting on (2.3.48). However, no matter what I try, it always
hangs at the "booting..." screen.

I've tried using the default ".config" from the rsync, I've tried the default
pmac_config config, and I've tried the config from a booting stable
2.2.15pre11 kernel. None of them seem to work.

Can anyone help? Does anyone have the 2.3.x series kernel booting on this
older PowerBook G3 (3400 form factor, first PBG3 made)? If so, please email me
with details.

Thanks!!

-Robert
 mailto:rshaw@linuxppc.org
 http://www.linuxppc.org/BlueG3/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Booting 2.3.48 (devel) kernel problems?

[enneper]

 Robert Shaw }  I have a PowerBook G3 (1997) that I'm trying to get the latest devel kernel
 Robert Shaw }  compiled and booting on (2.3.48). However, no matter what I try, it always
 Robert Shaw }  hangs at the "booting..." screen.
probably CONFIG_DEVFS_FS = y ????
first try /usr/scr/linux/Documentation/filesystems/devfs/README
greetings
Claus

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Booting 2.3.48 (devel) kernel problems?

[Michael Schmitz]

>  Robert Shaw }  I have a PowerBook G3 (1997) that I'm trying to get the latest devel kernel
>  Robert Shaw }  compiled and booting on (2.3.48). However, no matter what I try, it always
>  Robert Shaw }  hangs at the "booting..." screen.
> probably CONFIG_DEVFS_FS = y ????
> first try /usr/scr/linux/Documentation/filesystems/devfs/README

That, plus a few patches related to BootX text console output happening
before the framebuffer is mapped. I'll dig out a patch if necessary.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Booting 2.3.48 (devel) kernel problems?

[enneper]

 Michael Schmitz }  That, plus a few patches related to BootX text console output happening
 Michael Schmitz }  before the framebuffer is mapped. I'll dig out a patch if necessary.

PB3500 as mentioned could be booted via OF.
greetings.
Claus

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Booting 2.3.48 (devel) kernel problems?

[Michael Schmitz]

>  Michael Schmitz }  That, plus a few patches related to BootX text console output happening
>  Michael Schmitz }  before the framebuffer is mapped. I'll dig out a patch if necessary.
>
> PB3500 as mentioned could be booted via OF.

So the framebuffer got mapped from OF but not from BootX.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/