Hi Grub command is fine, what is your problem about filo? send the log if you can
Wang Qing Pei Mail: wangqingpei@gmail.com Phone:86+013426369984
----- Reply message ----- 发件人: "Joop Boonen" joop_boonen@web.de 日期: 周三, 5 月 19 日, 2010 年 07:09 主题: [coreboot] Advice how to install Linux to get it working with FILO 收件人: coreboot@coreboot.org
Hello All,
I want to get FILO working on my system (arima/hdama). As I want to rule out my Linux installation I have a few questions. I've installed openSuSE 11.2 x86_64 on a SATA disk connected to the on board SIL3114 controller.
I have the follwoing partitioning. 1) /boot about 128 MB 2) swap about 2 GB 3) /root about 60GB 4) /home about 20GB
Is this OK or is there also a track maximum for FILO like existed for LILO? Is it best to configure FILO with grub commands?
Regards,
Joop.
On Wed, May 19, 2010 1:46 am, wangqingpei@gmail.com wrote:
Hi Grub command is fine, what is your problem about filo? send the log if you can
The problem is that I see the follwoing in the log:
<quote> Jumping to entry point...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET... </quote>
I've also attached the log.
Wang Qing Pei Mail: wangqingpei@gmail.com Phone:86+013426369984
----- Reply message ----- åä»¶äººï¼ "Joop Boonen" joop_boonen@web.de æ¥æï¼ å¨ä¸, 5 æ 19 æ¥, 2010 å¹´ 07:09 主é¢ï¼ [coreboot] Advice how to install Linux to get it working with FILO æ¶ä»¶äººï¼ coreboot@coreboot.org
Hello All,
I want to get FILO working on my system (arima/hdama). As I want to rule out my Linux installation I have a few questions. I've installed openSuSE 11.2 x86_64 on a SATA disk connected to the on board SIL3114 controller.
I have the follwoing partitioning.
- /boot about 128 MB
- swap about 2 GB
- /root about 60GB
- /home about 20GB
Is this OK or is there also a track maximum for FILO like existed for LILO? Is it best to configure FILO with grub commands?
Regards,
Joop.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it crashed, how about try to disable acpi?
On Wed, May 19, 2010 at 2:11 PM, Joop Boonen joop_boonen@web.de wrote:
On Wed, May 19, 2010 1:46 am, wangqingpei@gmail.com wrote:
Hi Grub command is fine, what is your problem about filo? send the log if you can
The problem is that I see the follwoing in the log:
<quote> Jumping to entry point...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
</quote>
I've also attached the log.
Wang Qing Pei Mail: wangqingpei@gmail.com Phone:86+013426369984
----- Reply message ----- 发件人: "Joop Boonen" joop_boonen@web.de 日期: 周三, 5 月 19 日, 2010 年 07:09 主题: [coreboot] Advice how to install Linux to get it working with FILO 收件人: coreboot@coreboot.org
Hello All,
I want to get FILO working on my system (arima/hdama). As I want to rule out my Linux installation I have a few questions. I've installed openSuSE 11.2 x86_64 on a SATA disk connected to the on board SIL3114 controller.
I have the follwoing partitioning.
- /boot about 128 MB
- swap about 2 GB
- /root about 60GB
- /home about 20GB
Is this OK or is there also a track maximum for FILO like existed for LILO? Is it best to configure FILO with grub commands?
Regards,
Joop.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Wed, May 19, 2010 8:52 am, Qing Pei Wang wrote:
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it crashed, how about try to disable acpi?
Hi Qing Pei,
Thank you very much, for you help.
I'll try to boot without acpi later.
On Wed, May 19, 2010 at 2:11 PM, Joop Boonen joop_boonen@web.de wrote:
On Wed, May 19, 2010 1:46 am, wangqingpei@gmail.com wrote:
Hi Grub command is fine, what is your problem about filo? send the log
if
you can
The problem is that I see the follwoing in the log:
<quote> Jumping to entry point...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
</quote>
I've also attached the log.
Wang Qing Pei Mail: wangqingpei@gmail.com Phone:86+013426369984
----- Reply message ----- åä»¶äººï¼ "Joop Boonen" joop_boonen@web.de æ¥æï¼ å¨ä¸, 5 æ 19 æ¥, 2010 å¹´ 07:09 主é¢ï¼ [coreboot] Advice how to install Linux to get it working
with
FILO æ¶ä»¶äººï¼ coreboot@coreboot.org
Hello All,
I want to get FILO working on my system (arima/hdama). As I want to rule out my Linux installation I have a few questions. I've installed openSuSE 11.2 x86_64 on a SATA disk connected to the on board SIL3114 controller.
I have the follwoing partitioning.
- /boot about 128 MB
- swap about 2 GB
- /root about 60GB
- /home about 20GB
Is this OK or is there also a track maximum for FILO like existed for LILO? Is it best to configure FILO with grub commands?
Regards,
Joop.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
-- Wang Qing Pei MSN:wangqingpei@hotmail.com MSN%3Awangqingpei@hotmail.com Gmail:wangqingpei@gmail.com Gmail%3Awangqingpei@gmail.com Phone:86+13426369984
On Wed, May 19, 2010 8:52 am, Qing Pei Wang wrote:
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it crashed, how about try to disable acpi?
I don't think it gets that far. There's no kernel output from the serial port. It looks like FILO thinks it loads the kernel correctly, then jumps to invalid code (or the wrong address).
<quote> Jumping to entry point...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
</quote>
Thanks, Myles
On Wed, May 19, 2010 3:54 pm, Myles Watson wrote:
On Wed, May 19, 2010 8:52 am, Qing Pei Wang wrote:
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it
crashed,
how about try to disable acpi?
I don't think it gets that far. There's no kernel output from the serial port. It looks like FILO thinks it loads the kernel correctly, then jumps to invalid code (or the wrong address).
Is there a way I can troubleshoot this?
<quote> Jumping to entry point...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
</quote>
Thanks, Myles
On Wed, May 19, 2010 at 8:31 AM, Joop Boonen joop_boonen@web.de wrote:
On Wed, May 19, 2010 3:54 pm, Myles Watson wrote:
On Wed, May 19, 2010 8:52 am, Qing Pei Wang wrote:
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it
crashed,
how about try to disable acpi?
I don't think it gets that far. There's no kernel output from the serial port. It looks like FILO thinks it loads the kernel correctly, then jumps to invalid code (or the wrong address).
Is there a way I can troubleshoot this?
Here are a couple of ways. I'm not sure which is easiest: 1. Try it in a simulator (SimNOW or Qemu) 2. Print out the memory at the entry point to see if it looks like good code 3. Move FILO to an address that isn't the same as the kernel (they both use 0x100000) 4. Use FILO to load some other payload
Sorry it's pretty generic. Any FILO experts care to weigh in?
Good luck, Myles
<quote> Jumping to entry point...
INIT detected from --- { APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
</quote>
On 5/19/10 4:31 PM, Joop Boonen wrote:
On Wed, May 19, 2010 3:54 pm, Myles Watson wrote:
On Wed, May 19, 2010 8:52 am, Qing Pei Wang wrote:
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it
crashed,
how about try to disable acpi?
I don't think it gets that far. There's no kernel output from the serial port. It looks like FILO thinks it loads the kernel correctly, then jumps to invalid code (or the wrong address).
Is there a way I can troubleshoot this?
Which Linux version is that again? 2.6.31+ by any chance? If so: FILO needs the same fix that Eric posted for mkelfImage earlier today.
Stefan
On Wed, May 19, 2010 4:59 pm, Stefan Reinauer wrote:
On 5/19/10 4:31 PM, Joop Boonen wrote:
On Wed, May 19, 2010 3:54 pm, Myles Watson wrote:
On Wed, May 19, 2010 8:52 am, Qing Pei Wang wrote:
hi Joop, From the log, the filo worked fine. it can detect the hard disk,load kernel. But the kernel crashes. i do not not much about why it
crashed,
how about try to disable acpi?
I don't think it gets that far. There's no kernel output from the serial port. It looks like FILO thinks it loads the kernel correctly, then jumps to invalid code (or the wrong address).
Is there a way I can troubleshoot this?
Which Linux version is that again? 2.6.31+ by any chance? If so: FILO needs the same fix that Eric posted for mkelfImage earlier today.
It's openSUSE 11.2 it uses kernel 2.6.31 . I presume it needs the same fix, is the it already included in the current FILO code?
Stefan
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
(Recommend looking into utf-8, guys.)
Joop Boonen wrote:
the same fix, is the it already included in the current FILO code?
It was posted by Eric as a patch to mkelfImage today. There is no patch for FILO. Feel free to help adapt the mkelfImage patch!
//Peter
On Wed, May 19, 2010 7:02 pm, Peter Stuge wrote:
(Recommend looking into utf-8, guys.)
Joop Boonen wrote:
the same fix, is the it already included in the current FILO code?
It was posted by Eric as a patch to mkelfImage today. There is no patch for FILO. Feel free to help adapt the mkelfImage patch!
I'm trying to implement the patch in filo. I think a part is done see diff.
<diff> svn diff Index: i386/linux_load.c =================================================================== --- i386/linux_load.c (revision 131) +++ i386/linux_load.c (working copy) @@ -82,6 +82,10 @@ u32 cmd_line_ptr; /* 0x228 */ /* 2.03+ */ u32 initrd_addr_max; /* 0x22c */ + /* 2.05+ */ + u32 kernel_alignment; /* 0x230 */ + u8 relocateable_kernel; /* 0x234 */ + u8 reserved15[0x2d0 - 0x235]; /* 0x235 */ } __attribute__ ((packed));
/* Paramters passed to 32-bit part of Linux @@ -161,6 +165,9 @@ u8 reserved12_5[8]; /* 0x220 */ u32 cmd_line_ptr; /* 0x228 */ u8 reserved13[164]; /* 0x22c */ + u32 kernel_alignment; /* 0x230 */ + u8 relocateable_kernel; /* 0x234 */ + u8 reserved15[0x2d0 - 0x235]; /* 0x235 */ struct e820entry e820_map[E820MAX]; /* 0x2d0 */ u8 reserved16[688]; /* 0x550 */ #define COMMAND_LINE_SIZE 256 </diff>
I don't have a clue where to put this part
@@ -1503,6 +1506,9 @@ void initialize_linux_params(struct para
/* No loader flags */ info->real_mode->loader_flags = 0; + + /* Set it to 16M instead of 4G */ + info->real_mode->kernel_alignment = 16*1024*1024;
/* Ramdisk address and size ... */ info->real_mode->initrd_start = 0;
//Peter
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Wed, May 19, 2010 at 1:16 PM, Joop Boonen joop_boonen@web.de wrote:
On Wed, May 19, 2010 7:02 pm, Peter Stuge wrote:
(Recommend looking into utf-8, guys.)
Joop Boonen wrote:
the same fix, is the it already included in the current FILO code?
It was posted by Eric as a patch to mkelfImage today. There is no patch for FILO. Feel free to help adapt the mkelfImage patch!
I'm trying to implement the patch in filo. I think a part is done see diff.
I've attached my attempt at porting the patch.
Signed-off-by: Myles Watson mylesgw@gmail.com
Thanks, Myles