Hi,
I was able to boot Fiasco on a PIII 450 Mhz, 128MB. However, I have tried the same procedure on a Pentium IV 2.5GHz, 1GB RAM and it does not work. I get to this point in the boot process and it stops:
|RMGR: Stage1 | loading /boot/sigma0 | loading kernel /boot/main -nokdb -nowait | kernel at 00300000-0039d624 | detected new-style DD-L4(v2)/Fiasco | configuring sigma0: 00090000-00095000, start: 00090000 | reserve modules memory range: 00223000-0022d175 | starting kernel /boot/main -nokdb -nowait proto=0x101fa0 @ 0x00300aa0 | |Loading ELF image (kernel) at 0x303140 [entry 0xf0001000]
I used all the defaults when building L4, rmgr, sigm0, and hello. Is there anything special I need to do when booting on an PIV? I also created a floppy disk and booted it on both the PIII and the PIV. It boots on the PIII but not on the PIV. Anyone have any ideas as to what my problem is?
Here is my grub configuration:
|title hello world | root (hd1,0) | kernel (/boot/rmgr -sigma0) | module /boot/main -nokdb -nowait | module /boot/sigma0 | module /boot/hello
Anything else I can provide that would be useful?
Thanks!
-Julian
Hi,
On Tue Nov 09, 2004 at 14:47:07 -0500, Julian Grizzard wrote:
I was able to boot Fiasco on a PIII 450 Mhz, 128MB. However, I have tried the same procedure on a Pentium IV 2.5GHz, 1GB RAM and it does not work. I get to this point in the boot process and it stops:
|RMGR: Stage1 | loading /boot/sigma0 | loading kernel /boot/main -nokdb -nowait | kernel at 00300000-0039d624 | detected new-style DD-L4(v2)/Fiasco | configuring sigma0: 00090000-00095000, start: 00090000 | reserve modules memory range: 00223000-0022d175 | starting kernel /boot/main -nokdb -nowait proto=0x101fa0 @ 0x00300aa0 | |Loading ELF image (kernel) at 0x303140 [entry 0xf0001000]
I used all the defaults when building L4, rmgr, sigm0, and hello. Is there anything special I need to do when booting on an PIV? I also created a floppy disk and booted it on both the PIII and the PIV. It boots on the PIII but not on the PIV. Anyone have any ideas as to what my problem is?
Here is my grub configuration:
|title hello world | root (hd1,0) | kernel (/boot/rmgr -sigma0) | module /boot/main -nokdb -nowait | module /boot/sigma0 | module /boot/hello
Anything else I can provide that would be useful?
Just a guess right now, try adding "-noserial" to the Fiasco kernel command line. (By any chance, has the P4 serial ports? If, how many?)
Adam
Adam,
On Tue, 9 Nov 2004 21:22:29 +0100, Adam Lackorzynski adam@os.inf.tu-dresden.de wrote:
Hi,
On Tue Nov 09, 2004 at 14:47:07 -0500, Julian Grizzard wrote:
I was able to boot Fiasco on a PIII 450 Mhz, 128MB. However, I have tried the same procedure on a Pentium IV 2.5GHz, 1GB RAM and it does not work. I get to this point in the boot process and it stops:
|RMGR: Stage1 | loading /boot/sigma0 | loading kernel /boot/main -nokdb -nowait | kernel at 00300000-0039d624 | detected new-style DD-L4(v2)/Fiasco | configuring sigma0: 00090000-00095000, start: 00090000 | reserve modules memory range: 00223000-0022d175 | starting kernel /boot/main -nokdb -nowait proto=0x101fa0 @ 0x00300aa0 | |Loading ELF image (kernel) at 0x303140 [entry 0xf0001000]
I used all the defaults when building L4, rmgr, sigm0, and hello. Is there anything special I need to do when booting on an PIV? I also created a floppy disk and booted it on both the PIII and the PIV. It boots on the PIII but not on the PIV. Anyone have any ideas as to what my problem is?
Here is my grub configuration:
|title hello world | root (hd1,0) | kernel (/boot/rmgr -sigma0) | module /boot/main -nokdb -nowait | module /boot/sigma0 | module /boot/hello
Anything else I can provide that would be useful?
Just a guess right now, try adding "-noserial" to the Fiasco kernel command line. (By any chance, has the P4 serial ports? If, how many?)
Interesting. That made it a bit farther, but brings me to a new problem. Here's what I've got beyond the previous point
|... |Welcome to Fiasco(ia32)! |DD-L4(v2)/x86 microkernel (C) 1998-2004 TU Dresden |Rev: Tue Nov 9 12:01:14 2004 compiled with gcc 3.3.4 for Intel Pentium 4 |Performance-critical config options(s) detected: | CONFIG_NDEBUG is off | CONFIG_NO_FRAME_PTR is off | |Enabling fully special nested mode for pic |Panic: Too much kernel memory reserved |Shutting down... | |Press any key to reboot
Guessing that has something to do with having 1GB of memory?
-Julian
On Tue, 9 Nov 2004 16:23:55 -0500, Julian Grizzard grizzard@gmail.com wrote:
Adam,
On Tue, 9 Nov 2004 21:22:29 +0100, Adam Lackorzynski adam@os.inf.tu-dresden.de wrote:
Hi,
On Tue Nov 09, 2004 at 14:47:07 -0500, Julian Grizzard wrote:
I was able to boot Fiasco on a PIII 450 Mhz, 128MB. However, I have tried the same procedure on a Pentium IV 2.5GHz, 1GB RAM and it does not work. I get to this point in the boot process and it stops:
|RMGR: Stage1 | loading /boot/sigma0 | loading kernel /boot/main -nokdb -nowait | kernel at 00300000-0039d624 | detected new-style DD-L4(v2)/Fiasco | configuring sigma0: 00090000-00095000, start: 00090000 | reserve modules memory range: 00223000-0022d175 | starting kernel /boot/main -nokdb -nowait proto=0x101fa0 @ 0x00300aa0 | |Loading ELF image (kernel) at 0x303140 [entry 0xf0001000]
I used all the defaults when building L4, rmgr, sigm0, and hello. Is there anything special I need to do when booting on an PIV? I also created a floppy disk and booted it on both the PIII and the PIV. It boots on the PIII but not on the PIV. Anyone have any ideas as to what my problem is?
Here is my grub configuration:
|title hello world | root (hd1,0) | kernel (/boot/rmgr -sigma0) | module /boot/main -nokdb -nowait | module /boot/sigma0 | module /boot/hello
Anything else I can provide that would be useful?
Just a guess right now, try adding "-noserial" to the Fiasco kernel command line. (By any chance, has the P4 serial ports? If, how many?)
Interesting. That made it a bit farther, but brings me to a new problem. Here's what I've got beyond the previous point
|... |Welcome to Fiasco(ia32)! |DD-L4(v2)/x86 microkernel (C) 1998-2004 TU Dresden |Rev: Tue Nov 9 12:01:14 2004 compiled with gcc 3.3.4 for Intel Pentium 4 |Performance-critical config options(s) detected: | CONFIG_NDEBUG is off | CONFIG_NO_FRAME_PTR is off | |Enabling fully special nested mode for pic |Panic: Too much kernel memory reserved |Shutting down... | |Press any key to reboot
Guessing that has something to do with having 1GB of memory?
-Julian
The p4 has one serial port by the way.
-Julian
On Tue Nov 09, 2004 at 16:24:39 -0500, Julian Grizzard wrote:
The p4 has one serial port by the way.
Thanks for the info, this confirms my presumption.
Adam
On Tue Nov 09, 2004 at 16:23:55 -0500, Julian Grizzard wrote:
Interesting. That made it a bit farther, but brings me to a new problem. Here's what I've got beyond the previous point
|... |Welcome to Fiasco(ia32)! |DD-L4(v2)/x86 microkernel (C) 1998-2004 TU Dresden |Rev: Tue Nov 9 12:01:14 2004 compiled with gcc 3.3.4 for Intel Pentium 4 |Performance-critical config options(s) detected: | CONFIG_NDEBUG is off | CONFIG_NO_FRAME_PTR is off | |Enabling fully special nested mode for pic |Panic: Too much kernel memory reserved |Shutting down... | |Press any key to reboot
Guessing that has something to do with having 1GB of memory?
Yeah but I'd declare this a bug ;)
If you want to fix that now, go to l4/kernel/fiasco/src/kern/config.cpp and decrease kernel_mem_per_cent (2nd occurance) appropriately, e.g. to something like 4.
Adam
Guessing that has something to do with having 1GB of memory?
Yeah but I'd declare this a bug ;)
If you want to fix that now, go to l4/kernel/fiasco/src/kern/config.cpp and decrease kernel_mem_per_cent (2nd occurance) appropriately, e.g. to something like 4.
Well at least that is an easy patch, solved the problem. Thanks for the help!
-Julian
On Wednesday 10 November 2004 00:01, Julian Grizzard wrote:
Guessing that has something to do with having 1GB of memory?
Yeah but I'd declare this a bug ;)
If you want to fix that now, go to l4/kernel/fiasco/src/kern/config.cpp and decrease kernel_mem_per_cent (2nd occurance) appropriately, e.g. to something like 4.
Well at least that is an easy patch, solved the problem. Thanks for the help!
Fixed in CVS.
Frank
l4-hackers@os.inf.tu-dresden.de