Hi,
I have some improvement on my TUSL2-C board (intel 82815ep chipset). The ram initialization is successful . However, it boots neither etherboot elf nor adlo payload. It hangs after the following messages from serial port . I put the tagged bzImage (not elf) on hda using : dd if=bzImage.ether of=/dev/hda bs=4096 skip=1 as suggested by ron but it does not seem to be recognized by linuxbios . I am using sis900.ebi as ide etherboot. Any idea ? Thanks.
LinuxBIOS-1.0.0 Tue May 13 12:12:08 EDT 2003 starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 Ram Enable 5 Ram4 Ram5 Ram6
Testing SDRAM : 00000000-0009ffff SDRAM fill: 00000000 00010000 00020000
LinuxBIOS-1.0.0 Tue May 13 12:12:08 EDT 2003 starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 Ram Enable 5 Ram4 Ram5 Ram6
Testing SDRAM : 00000000-0009ffff SDRAM fill: 00000000 00010000 00020000 00030000 00040000 00050000 00060000 00070000 00080000 00090000 0009ffff
SDRAM verify: 00000000 00010000 00020000 00030000 00040000 00050000 00060000 00070000 00080000 00090000 0009ffff Done.
Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.0.0 Tue May 13 12:12:08 EDT 2003 booting... Finding PCI configuration type. PCI: Using configuration type 1 Scanning PCI bus...PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [8086/1130] PCI: 00:01.0 [8086/1131] PCI: 00:1e.0 [8086/244e] PCI: 00:1f.0 [8086/2440] PCI: 00:1f.1 [8086/244b] PCI: 00:1f.2 [8086/2442] PCI: 00:1f.3 [8086/2443] PCI: 00:1f.4 [8086/2444] PCI: 00:1f.5 [8086/2445] PCI: 00:1f.6 [8086/2446] PCI: pci_scan_bus for bus 1 PCI: 01:00.0 [1002/5144] PCI: pci_scan_bus returning with max=01 PCI: pci_scan_bus for bus 2 PCI: 02:07.0 [13f6/0111] PCI: 02:0a.0 [10b7/9055] PCI: pci_scan_bus returning with max=02 PCI: pci_scan_bus returning with max=02 done
Allocating PCI resources... ASSIGN RESOURCES, bus 0 PCI: 00:00.0 10 <- [0xf8000000 - 0xfbffffff] prefmem PCI: 00:01.0 1c <- [0x00001000 - 0x00001fff] bus 1 io PCI: 00:01.0 24 <- [0xf0000000 - 0xf7ffffff] bus 1 prefmem PCI: 00:01.0 20 <- [0xfc000000 - 0xfc0fffff] bus 1 mem ASSIGN RESOURCES, bus 1 PCI: 01:00.0 10 <- [0xf0000000 - 0xf7ffffff] prefmem PCI: 01:00.0 14 <- [0x00001000 - 0x000010ff] io PCI: 01:00.0 18 <- [0xfc000000 - 0xfc07ffff] mem ASSIGNED RESOURCES, bus 1 PCI: 00:1e.0 1c <- [0x00002000 - 0x00002fff] bus 2 io PCI: 00:1e.0 24 <- [0xfc200000 - 0xfc1fffff] bus 2 prefmem PCI: 00:1e.0 20 <- [0xfc100000 - 0xfc1fffff] bus 2 mem ASSIGN RESOURCES, bus 2 PCI: 02:07.0 10 <- [0x00002000 - 0x000020ff] io PCI: 02:0a.0 10 <- [0x00002400 - 0x0000247f] io PCI: 02:0a.0 14 <- [0xfc100000 - 0xfc10007f] mem ASSIGNED RESOURCES, bus 2 PCI: 00:1f.1 20 <- [0x00003c00 - 0x00003c0f] io PCI: 00:1f.2 20 <- [0x000038c0 - 0x000038df] io PCI: 00:1f.3 20 <- [0x00003c10 - 0x00003c1f] io PCI: 00:1f.4 20 <- [0x000038e0 - 0x000038ff] io PCI: 00:1f.5 10 <- [0x00003000 - 0x000030ff] io PCI: 00:1f.5 14 <- [0x00003880 - 0x000038bf] io PCI: 00:1f.6 10 <- [0x00003400 - 0x000034ff] io PCI: 00:1f.6 14 <- [0x00003800 - 0x0000387f] io ASSIGNED RESOURCES, bus 0 Allocating VGA resource done.
Enabling PCI resourcess...PCI: 00:00.0 cmd <- 06 PCI: 00:01.0 cmd <- 07 PCI: 00:1e.0 cmd <- 07 PCI: 00:1f.0 cmd <- 0f PCI: 00:1f.1 cmd <- 01 PCI: 00:1f.2 cmd <- 01 PCI: 00:1f.3 cmd <- 01 PCI: 00:1f.4 cmd <- 01 PCI: 00:1f.5 cmd <- 01 PCI: 00:1f.6 cmd <- 01 PCI: 01:00.0 cmd <- 83 PCI: 02:07.0 cmd <- 81 PCI: 02:0a.0 cmd <- 03 done.
Initializing PCI devices... PCI devices initialized DRP0 = 0xc DIMM0 - size = 256M DIMM1 - size = 0M DRP1 = 0x0 DIMM2 - size = 0M totalram: 256M Initializing CPU #0 Updating microcode microcode_info: sig = 0x000006b1 pf=0x00000010 rev = 0x00000000 Enabling cache... Setting fixed MTRRs(0-88) type: UC inside set_fixed_mtrrs going out set_fixed_mtrrs Setting fixed MTRRs(0-16) type: WB inside set_fixed_mtrrs going out set_fixed_mtrrs DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 256MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs done.
Max cpuid index : 2 Vendor ID : GenuineIntel Processor Type : 0x00 Processor Family : 0x06 Processor Model : 0x0b Processor Mask : 0x00 Processor Stepping : 0x01 Feature flags : 0x0383fbff Cache/TLB descriptor values: 1 reads required Desc 0x01 : Instr TLB: 4KB pages, 4-way set assoc, 32 entries Desc 0x02 : Instr TLB: 4MB pages, fully assoc, 2 entries Desc 0x03 : Data TLB: 4KB pages, 4-way set assoc, 64 entries Desc 0x00 : null Desc 0x00 : null Desc 0x00 : null Desc 0x00 : null Desc 0x00 : null Desc 0x00 : null Desc 0x00 : null Desc 0x00 : null Desc 0x82 : L2 Unified cache: 256K bytes, 8-way set assoc, 32 byte line size Desc 0x08 : Inst cache: 16K bytes, 4-way set assoc, 32 byte line size Desc 0x04 : Data TLB: 4MB pages, 4-way set assoc, 8 entries Desc 0x0c : Data cache: 16K bytes, 2-way or 4-way set assoc, 32 byte line size MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled Configuring L2 cache...CPU signature of 6b0 so no L2 cache configuration Enable Cache done.
Disabling local apic...done. CPU #0 Initialized Please turn on nvram Copying IRQ routing tables to 0xf0000...done. Verifing priq routing tables copy at 0xf0000...failed Wrote linuxbios table at: 00000500 - 00000660 checksum 393b
Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 203:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Searching for 16 byte tags 64:rom_read_bytes() - overflowed source buffer. max_block = 15 init_bytes found 0 tags Found ELF candiate at offset 0 New segment addr 0x7c00 size 0x20400 offset 0x100 filesize 0x20400 (cleaned up) New segment addr 0x7c00 size 0x20400 offset 0x100 filesize 0x20400 Loading Segment: addr: 0x000000000ff667e8 memsz: 0x0000000000020400 filesz: 0x0000000000020400 Jumping to boot code at 0x7c00
regards, eehuey
_________________________________________________________________ Download ringtones, logos and picture messages from MSN Malaysia http://www.msn.com.my/mobile/ringtones/default.asp
* Yap Ee Huey yapeehuey@hotmail.com [030513 13:46]:
The ram initialization is successful . However, it boots neither etherboot elf nor adlo payload. It hangs after the following messages from serial port . I put the tagged bzImage (not elf) on hda using : dd if=bzImage.ether of=/dev/hda bs=4096 skip=1 as suggested by ron but it does not seem to be recognized by linuxbios . I am using sis900.ebi as ide etherboot. Any idea ? Thanks.
I never got ADLO to say something either, when I tried it the last time. But etherboot works nicely here. Have you changed the etherboot config not to use legacy PC-BIOS cruft? When I forgot to do so, I got the same result on AMD64
Best regards, Stefan Reinauer
- Yap Ee Huey yapeehuey@hotmail.com [030513 13:46]:
The ram initialization is successful . However, it boots neither etherboot elf nor adlo payload. It hangs after the following messages from serial port . I put the tagged bzImage (not elf) on hda using : dd if=bzImage.ether of=/dev/hda bs=4096 skip=1 as suggested by ron but it does not seem to be recognized by linuxbios . I am using sis900.ebi as ide etherboot. Any idea ? Thanks.
I never got ADLO to say something either, when I tried it the last time.
* did you adjust loader.s file to your system as needed?
* did you try to use serial console path for ADLO posted by Heechul Yun
* Adam Sulmicki adam@cfar.umd.edu [030513 14:56]:
I never got ADLO to say something either, when I tried it the last time.
- did you adjust loader.s file to your system as needed?
I did, but i might have overseen something. Especially I'm not sure whether i did the shadow enable thing right. Is there more that I need to get it talking?
- did you try to use serial console path for ADLO posted by Heechul Yun
no, this was before Heechul did this great job. I'll retry working on this as soon as I find some time.
Stefan
I never got ADLO to say something either, when I tried it the last time.
- did you adjust loader.s file to your system as needed?
I did, but i might have overseen something. Especially I'm not sure whether i did the shadow enable thing right. Is there more that I need to get it talking?
Usually no. However the whole shadow thing is the key and if it does not work right ADLO will not work at all.
- did you try to use serial console path for ADLO posted by Heechul Yun
no, this was before Heechul did this great job. I'll retry working on this as soon as I find some time.
cool.
On Tue, 13 May 2003, Yap Ee Huey wrote:
Hi,
I have some improvement on my TUSL2-C board (intel 82815ep chipset). The ram initialization is successful . However, it boots neither etherboot elf nor adlo payload. It hangs after the following messages from serial port .
Your problem is that etherboot and adlo are not coming up.
Are you sure that you built etherboot so that it only uses serial and does not require BIOS interrupts?
I think that may be the problem.
congratulations on getting this working -- it will be very useful.
ron
* Yap Ee Huey yapeehuey@hotmail.com [030513 13:46]:
I put the tagged bzImage (not elf) on hda using : dd if=bzImage.ether of=/dev/hda bs=4096 skip=1
^^^^^^ This has to be seek=1, not skip=1. Otherwise you overwrite your partition table with an incomplete elf file instead of leaving your partition table there and writing the complete file.
Stefan
On Tue, 13 May 2003, Stefan Reinauer wrote:
This has to be seek=1, not skip=1. Otherwise you overwrite your partition table with an incomplete elf file instead of leaving your partition table there and writing the complete file.
I am going to regret that particular typo of mine for a long time.
Sorry.
I think the solution of using sfdisk to build a /dev/hda1 that starts at sector 1 is better. Fixing etherboot to scan 64k in each direction is best. I tried that but it still didn't find the elfimage.
ron
-
Adam Sulmicki -
ron minnich -
Stefan Reinauer -
Yap Ee Huey