I used the stock FC4 kernel with the same command line as you used. My autoboot was just hdb1:/linux_2.6.16.elf (I have a CD-ROM as hda)
Good luck,
Myles
-----Original Message----- From: linuxbios-bounces@linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Per Mellander Sent: Wednesday, May 31, 2006 6:53 AM To: myles@mouselemur.cs.byu.edu Cc: linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie )
Now I get so far that the kernel is identified and loaded but then it breaks :(
I created an elf with mkelfImage:
# mkelfImage --kernel=/vmlinuz-2.6.16-1.2111_FC5 --output=/vmlinuz.elf --initrd=/initrd-2.6.16-1.2111_FC5.img --command-line="ro root=LABEL=/ rhgb quiet console=ttyS0 console=ttyS0,115200"
----8<-------------------------------------------------------------
Jumping to boot code at 0x109ad4 FILO version 0.5 (root@mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 Press <Enter> for default boot, or <Esc> for boot prompt... timed out boot: hda1:/vmlinuz.elf find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8a find_ide_controller: primary channel: compatibility mode find_ide_controller: cmd_base=0x1f0 ctrl_base=0x3f4 ide_software_reset: Waiting for ide0 to become ready for reset... ok init_drive: Testing for hda init_drive: Probing for hda init_drive: LBA mode, sectors=268435455 init_drive: LBA48 mode, sectors=321672960 init_drive: Init device params... ok hda: LBA48 164GB: HDS722516VLAT80 Mounted ext2fs Loading Linux version 2.6.16-1.2111_FC5 (bhcompile@hs20-bc1-3.build.redhat.com) #1 Thu May 4 21:16:58 EDT 2006... Jumping to entry point... 0
LinuxBIOS-1.1.8.0Fallback Wed May 31 13:15:25 CEST 2006 starting... Enabling mainboard devices Enabling shadow ram
----8<-------------------------------------------------------------
I get the same result when I try,
AUTOBOOT_FILE = "hda1:/vmlinuz initrd=/initrd.img root=/dev/hda1 console=tty0 console=ttyS0,115200"
so the problem is not in the elf image.
Could you please send me a snippet from your AUTOBOOT or similar?
Btw. Do I have to make a 'special' kernel to make this work or should the stock FC5 work?
/Per
On Tue, 30 May 2006 08:38:53 -0600, Myles Watson wrote
Did you try using mkelfImage from ftp://ftp.lnxi.com/pub/mkelfImage ? It combines the vmlinuz & initrd files into one.
To get my machine to boot I used the same kernel parameters as I found in grub, set up by Fedora.
I don't know if I'm stupid or what, but it just won't work for me :(
First of. I can't have my harddisk connected as hdb1 and my cdrom as hda1, ( which is out of the box for my setup ) because the IDE-disk will not be recognized by LB if its secondary. ( ??? )
So I put the hd as hda1 and create my LinuxBIOS as follows:
Get a proper vga-bios
# dd if=/dev/mem of=video.bios.bin bs=1 count=65536 skip=786432
Get the filo-0.5 change Config
Remove grub stuff set AUTOBOOT_FILE = "hda1:/vmlinuz.elf"
make copy filo.elf to /
# svn co svn://openbios.org/repos/trunk/LinuxBIOSv2 # cd LinuxBIOSv2/targets # ./buildtarget via/epia-m # cd via/epia-m/epia-m/ # vi Makefile
edit so video.bios.bin is cat'ed before linuxbios.rom
# make
create a kernel/initrd with
# mkelfImage --kernel=/vmlinuz-2.6.16-1.2111_FC5 \ --output=/vmlinuz.elf \ --initrd=/initrd-2.6.16-1.2111_FC5.img \ --command-line="ro root=LABEL=/ rhgb quiet console=tty0 console=ttyS0,115200"
flash the BIOS verify the BIOS
repeat above until verify
reboot
logged startup follows:
---8<--------------------------------------------------------------
0
LinuxBIOS-1.1.8.0Fallback Wed May 31 13:15:25 CEST 2006 starting... Enabling mainboard devices Enabling shadow ram vt8623 init starting Detecting Memory Number of Banks 04 Number of Rows 0d Priamry DRAM width08 No Columns 0a MA type e0 Bank 0 (*16 Mb) 10 No Physical Banks 02 Total Memory (*16 Mb) 20 CAS Supported 2 2.5 Cycle time at CL X (nS)75 Cycle time at CL X-0.5 (nS)a0 Cycle time at CL X-1 (nS)00 Starting at CAS 2.5 tRP 50 tRCD 50 tRAS 30 Low Bond 04 High Bondd7 Setting DQS delay90vt8623 done 00:06 11 23 31 06 00 30 22 00 00 00 06 00 00 00 00 10:08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30:00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40:00 18 88 80 82 44 00 00 18 99 88 80 82 44 00 00 50:c8 de cf 88 e0 07 00 00 e0 00 10 20 20 20 00 00 60:02 ff 00 30 e6 32 01 20 42 2d 43 58 84 55 00 00 70:82 48 00 01 01 08 50 00 01 00 00 00 00 00 02 12 80:0f 64 00 00 80 00 00 00 02 00 00 00 00 00 00 00 90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0:02 c0 20 00 07 02 00 1f 04 00 00 00 2f 02 04 00 b0:00 00 00 00 c0 00 00 00 c8 00 00 04 00 00 00 00 c0:01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0:00 dd 00 01 00 00 01 00 40 00 00 00 00 00 00 00 f0:00 00 00 00 00 00 12 13 00 00 00 00 00 00 00 00 AGP Doing MTRR init. Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.8.0Fallback Wed May 31 13:44:49 CEST 2006 booting... clocks_per_usec: 2412 Enumerating buses... Finding PCI configuration type. PCI: Using configuration type 1 PCI_DOMAIN: 0000 enabled APIC_CLUSTER: 0 enabled PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [1106/3123] enabled PCI: 00:01.0 [1106/b091] enabled PCI: 00:0a.0 [1180/0476] enabled PCI: 00:0a.1 [1180/0476] enabled PCI: 00:0d.0 [1106/3044] enabled In vt8235_enable 1106 3038. PCI: 00:10.0 [1106/3038] enabled In vt8235_enable 1106 3038. PCI: 00:10.1 [1106/3038] enabled In vt8235_enable 1106 3038. PCI: 00:10.2 [1106/3038] enabled In vt8235_enable 1106 3104. PCI: 00:10.3 [1106/3104] enabled In vt8235_enable 1106 3177. Initialising Devices PCI: 00:11.0 [1106/3177] enabled In vt8235_enable 1106 0571. PCI: 00:11.1 [1106/0571] enabled In vt8235_enable 1106 3059. PCI: 00:11.5 [1106/3059] enabled In vt8235_enable ffff ffff. In vt8235_enable 1106 3065. PCI: 00:12.0 [1106/3065] enabled PCI: pci_scan_bus for bus 1 PCI: 01:00.0 [1106/3122] enabled PCI: pci_scan_bus returning with max=01 PCI: pci_scan_bus for bus 2 PCI: pci_scan_bus returning with max=02 PCI: pci_scan_bus for bus 3 PCI: pci_scan_bus returning with max=03 vt1211 enabling PNP devices. PNP: 002e.0 enabled vt1211 enabling PNP devices. PNP: 002e.1 enabled vt1211 enabling PNP devices. PNP: 002e.2 enabled vt1211 enabling PNP devices. PNP: 002e.3 enabled vt1211 enabling PNP devices. PNP: 002e.b enabled PCI: pci_scan_bus returning with max=03 done Allocating resources... Reading resources... Done reading resources. Setting resources... I would set ram size to 0x80000 Kbytes PCI: 00:0a.0 In set resources PCI: 00:0a.0 10 <- [0x00febfa000 - 0x00febfafff] mem PCI: 00:0a.0 2c <- [0x00000018f0 - 0x00000028ef] io PCI: 00:0a.0 34 <- [0x00000028f0 - 0x00000038ef] io PCI: 00:0a.0 1c <- [0x00f6bfa000 - 0x00f8bf9fff] prefmem PCI: 00:0a.0 24 <- [0x00f8bfa000 - 0x00fabf9fff] mem PCI: 00:0a.1 In set resources PCI: 00:0a.1 1 ==> febfb000 PCI: 00:0a.1 10 <- [0x00febfc000 - 0x00febfcfff] mem PCI: 00:0a.1 2c <- [0x00000038f0 - 0x00000048ef] io PCI: 00:0a.1 34 <- [0x00000048f0 - 0x00000058ef] io PCI: 00:0a.1 1c <- [0x00fabfa000 - 0x00fcbf9fff] prefmem PCI: 00:0a.1 24 <- [0x00fcbfa000 - 0x00febf9fff] mem PCI: 00:0d.0 10 <- [0x00febfd000 - 0x00febfd7ff] mem PCI: 00:0d.0 14 <- [0x0000001800 - 0x000000187f] io PCI: 00:10.0 20 <- [0x0000001880 - 0x000000189f] io PCI: 00:10.1 20 <- [0x00000018a0 - 0x00000018bf] io PCI: 00:10.2 20 <- [0x00000018c0 - 0x00000018df] io PCI: 00:10.3 10 <- [0x00febfe000 - 0x00febfe0ff] mem PNP: 002e.0 60 <- [0x00000003f0 - 0x00000003f7] io PNP: 002e.0 70 <- [0x0000000006 - 0x0000000006] irq PNP: 002e.0 74 <- [0x0000000002 - 0x0000000002] drq PNP: 002e.1 60 <- [0x0000000378 - 0x000000037f] io PNP: 002e.1 70 <- [0x0000000007 - 0x0000000007] irq PNP: 002e.1 74 <- [0x0000000003 - 0x0000000003] drq PNP: 002e.2 60 <- [0x00000003f8 - 0x00000003ff] io PNP: 002e.2 70 <- [0x0000000004 - 0x0000000004] irq PNP: 002e.3 60 <- [0x00000002f8 - 0x00000002ff] io PNP: 002e.3 70 <- [0x0000000003 - 0x0000000003] irq PNP: 002e.b 60 <- [0x000000ec00 - 0x000000ecff] io PCI: 00:11.1 20 <- [0x00000018e0 - 0x00000018ef] io PCI: 00:11.5 10 <- [0x0000001000 - 0x00000010ff] io PCI: 00:12.0 10 <- [0x0000001400 - 0x00000014ff] io PCI: 00:12.0 14 <- [0x00febff000 - 0x00febff0ff] mem Done setting resources. Done allocating resources. Enabling resources... PCI: 00:00.0 cmd <- 146 PCI: 00:01.0 bridge ctrl <- 000f PCI: 00:01.0 cmd <- 147 PCI: 01:00.0 cmd <- 140 PCI: 00:0a.0 bridge ctrl <- 0503 PCI: 00:0a.0 cmd <- 143 PCI: 00:0a.1 bridge ctrl <- 0503 PCI: 00:0a.1 cmd <- 143 PCI: 00:0d.0 cmd <- 1c3 PCI: 00:10.0 subsystem <- 00/00 PCI: 00:10.0 cmd <- 141 PCI: 00:10.1 subsystem <- 00/00 PCI: 00:10.1 cmd <- 141 PCI: 00:10.2 subsystem <- 00/00 PCI: 00:10.2 cmd <- 141 PCI: 00:10.3 subsystem <- 00/00 PCI: 00:10.3 cmd <- 142 PCI: 00:11.0 cmd <- 147 PNP: 002e.0 - enabling PNP: 002e.1 - enabling PNP: 002e.2 - enabling PNP: 002e.3 - enabling PNP: 002e.b - enabling PCI: 00:11.1 cmd <- 147 PCI: 00:11.5 subsystem <- 00/00 PCI: 00:11.5 cmd <- 141 PCI: 00:12.0 cmd <- 1c3 done. Initializing devices... Root Device init PCI: 00:10.0 init PCI: 00:10.1 init PCI: 00:10.2 init PCI: 00:10.3 init PCI: 00:11.0 init vt8235 init RTC Init Invalid CMOS LB checksum pci_routing_fixup: dev is 000102a0 setting firewire Assigning IRQ 9 to 0:d.0 Readback = 9 setting usb Assigning IRQ 5 to 0:10.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:10.1 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:10.2 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 5 to 0:10.3 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting vt8235 Assigning IRQ 5 to 0:11.1 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 9 to 0:11.5 Readback = 9 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting ethernet Assigning IRQ 5 to 0:12.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting vga Assigning IRQ 5 to 1:0.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting pci slot setting cardbus slot Assigning IRQ 5 to 0:a.0 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 Assigning IRQ 5 to 0:a.1 Readback = 5 pci_level_irq: lower order bits are wrong: want 0x0, got 0x20 setting riser slot PNP: 002e.0 init PNP: 002e.1 init PNP: 002e.2 init PNP: 002e.3 init PNP: 002e.b init PCI: 00:11.1 init Enabling VIA IDE. ide_init: enabling compatibility IDE addresses enables in reg 0x42 0x0 enables in reg 0x42 read back as 0x0 enables in reg 0x40 0x13 enables in reg 0x40 read back as 0x13 enables in reg 0x9 0x8a enables in reg 0x9 read back as 0x8a command in reg 0x4 0x7 command in reg 0x4 reads back as 0x7 PCI: 00:11.5 init PCI: 00:12.0 init Configuring VIA Rhine LAN PCI: 00:0a.0 init rl5c476 init CF Base = febfb000 PCI: 00:0a.1 init rl5c476 init CF Base = febfb000 CF Config = ff APIC_CLUSTER: 0 init Initializing CPU #0 CPU: vendor Centaur device 698 Enabling cache
Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB Setting fixed MTRRs(24-88) Type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 256MB, type WB Setting variable MTRR 1, base: 256MB, range: 128MB, type WB Setting variable MTRR 2, base: 384MB, range: 64MB, type WB Setting variable MTRR 3, base: 448MB, range: 32MB, type WB DONE variable MTRRs Clear out the extra MTRR's
MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled
Disabling local apic...done. CPU #0 Initialized PCI: 00:00.0 init VT8623 random fixup ... Frame buffer at d0000000 PCI: 00:01.0 init VT8623 AGP random fixup ... PCI: 00:0d.0 init PCI: 01:00.0 init VGA random fixup ... INSTALL REAL-MODE IDT DO THE VGA BIOS found VGA: vid=1106, did=3122 rom base, size: fffc0000 write_protect_vgabios bus/devfn = 0x100 biosint: INT# 0x15 biosint: eax 0x5f00 ebx 0x187d4 ecx 0x17fa0 edx 0xa biosint: ebp 0x17f70 esp 0xff2 edi 0xed30 esi 0x187d4 biosint: ip 0x641c cs 0xc000 flags 0x46 biosint: INT# 0x1a biosint: eax 0xb108 ebx 0x10000 ecx 0x10000 edx 0x3d5 biosint: ebp 0x17f70 esp 0xfcc edi 0xf6 esi 0x1c01b biosint: ip 0x40f0 cs 0xc000 flags 0x46 0xb108: bus 0 devfn 0x0 reg 0xf6 val 0x12 biosint: INT# 0x15 biosint: eax 0x5f02 ebx 0x187d4 ecx 0x7f01 edx 0x3d5 biosint: ebp 0x17f70 esp 0xfdc edi 0x44 esi 0x1c01b biosint: ip 0x6468 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x401 edx 0x112 biosint: ebp 0x17f70 esp 0xfa4 edi 0x44 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x401 edx 0x112 biosint: ebp 0x17f70 esp 0xfa4 edi 0x44 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x401 edx 0x112 biosint: ebp 0x17f70 esp 0xf92 edi 0x44 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f02 ebx 0x10002 ecx 0x401 edx 0x0 biosint: ebp 0x17f70 esp 0xfb8 edi 0x44 esi 0x1c01b biosint: ip 0x6468 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f02 ebx 0x10002 ecx 0x401 edx 0x0 biosint: ebp 0x17f70 esp 0xfb8 edi 0x44 esi 0x1c01b biosint: ip 0x6468 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f02 ebx 0x10002 ecx 0x401 edx 0x0 biosint: ebp 0x17f70 esp 0xfb8 edi 0x44 esi 0x1c01b biosint: ip 0x6468 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f0f ebx 0x187d4 ecx 0x7fa0 edx 0x3d5 biosint: ebp 0x17f70 esp 0xfee edi 0x44 esi 0x187d4 biosint: ip 0x651b cs 0xc000 flags 0x6 biosint: INT# 0x15 biosint: eax 0x5f02 ebx 0x187d4 ecx 0x7f01 edx 0x3d5 biosint: ebp 0x17f70 esp 0xfdc edi 0x44 esi 0x187d4 biosint: ip 0x6468 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x700 edx 0x112 biosint: ebp 0x10fca esp 0xf8e edi 0xac51 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x700 edx 0x112 biosint: ebp 0x10fca esp 0xf7e edi 0xb880 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x101 edx 0x112 biosint: ebp 0x10fca esp 0xf7e edi 0xb880 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x7a0 edx 0x112 biosint: ebp 0x10fca esp 0xf88 edi 0xb880 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x700 edx 0x112 biosint: ebp 0x10fca esp 0xf7e edi 0xb880 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x700 edx 0x112 biosint: ebp 0x10fca esp 0xf90 edi 0xb880 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x701 edx 0x112 biosint: ebp 0x10fca esp 0xf90 edi 0xb880 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f18 ebx 0x187d4 ecx 0x7f01 edx 0x3d5 biosint: ebp 0x17f70 esp 0xfde edi 0x44 esi 0x187d4 biosint: ip 0x6533 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x300 edx 0x112 biosint: ebp 0x10fc8 esp 0xf8c edi 0xac49 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x46 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x300 edx 0x112 biosint: ebp 0x10fc8 esp 0xf7c edi 0xb840 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x101 edx 0x112 biosint: ebp 0x10fc8 esp 0xf7c edi 0xb840 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x3a0 edx 0x112 biosint: ebp 0x10fc8 esp 0xf86 edi 0xb840 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x300 edx 0x112 biosint: ebp 0x10fc8 esp 0xf7c edi 0xb840 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x300 edx 0x112 biosint: ebp 0x10fc8 esp 0xf8e edi 0xb840 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0xc01 ecx 0x301 edx 0x112 biosint: ebp 0x10fc8 esp 0xf8e edi 0xb840 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f06 ebx 0x18001 ecx 0x80010001 edx 0x0 biosint: ebp 0x10fd6 esp 0xfb4 edi 0x0 esi 0x146a7 biosint: ip 0x6479 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010000 edx 0x112 biosint: ebp 0x10fd6 esp 0xf88 edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010000 edx 0x112 biosint: ebp 0x10fd6 esp 0xf78 edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010101 edx 0x112 biosint: ebp 0x10fd6 esp 0xf78 edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010001 edx 0x112 biosint: ebp 0x10fd6 esp 0xf82 edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010000 edx 0x112 biosint: ebp 0x10fd6 esp 0xf78 edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010000 edx 0x112 biosint: ebp 0x10fd6 esp 0xf8a edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f01 ebx 0x10c01 ecx 0x80010001 edx 0x112 biosint: ebp 0x10fd6 esp 0xf8a edi 0x0 esi 0x1aacd biosint: ip 0x6448 cs 0xc000 flags 0x246 biosint: INT# 0x15 biosint: eax 0x5f08 ebx 0x18001 ecx 0x80010001 edx 0x0 biosint: ebp 0x10fd6 esp 0xfb4 edi 0x0 esi 0x146a7 biosint: ip 0x6485 cs 0xc000 flags 0x202 Devices initialized Copying IRQ routing tables to 0xf0000...done. Verifing copy of IRQ routing tables at 0xf0000...done Checking IRQ routing table consistency... check_pirq_routing_table() - irq_routing_table located at: 0x000f0000 done. ACPI: Writing ACPI tables at f0400... ACPI: * FACS ACPI: * DSDT @ 000f049e Length 3f0 ACPI: * FADT ACPI: added table 1/5 Length now 40 ACPI: done. Moving GDT to 0x500...ok Wrote linuxbios table at: 00000530 - 00000b70 checksum 5477
Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3
rom_stream: 0xfffd0000 - 0xfffeffff Found ELF candiate at offset 0 New segment addr 0x100000 size 0x31080 offset 0xc0 filesize 0xbde8 (cleaned up) New segment addr 0x100000 size 0x31080 offset 0xc0 filesize 0xbde8 New segment addr 0x131080 size 0x48 offset 0xbec0 filesize 0x48 (cleaned up) New segment addr 0x131080 size 0x48 offset 0xbec0 filesize 0x48 Dropping non PT_LOAD segment Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000031080 filesz: 0x000000000000bde8 Clearing Segment: addr: 0x000000000010bde8 memsz: 0x0000000000025298 Loading Segment: addr: 0x0000000000131080 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x109ad4 FILO version 0.5 (root@mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 Press <Enter> for default boot, or <Esc> for boot prompt... boot: hda1:/vmlinuz-FC5.elf find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8a find_ide_controller: primary channel: compatibility mode find_ide_controller: cmd_base=0x1f0 ctrl_base=0x3f4 ide_software_reset: Waiting for ide0 to become ready for reset... ok init_drive: Testing for hda init_drive: Probing for hda init_drive: LBA mode, sectors=268435455 init_drive: LBA48 mode, sectors=321672960 init_drive: Init device params... ok hda: LBA48 164GB: HDS722516VLAT80 Mounted ext2fs Loading Linux version 2.6.16-1.2111_FC5 (bhcompile@hs20-bc1-3.build.redhat.com) #1 Thu May 4 21:16:58 EDT 2006... Jumping to entry point... 0
LinuxBIOS-1.1.8.0Fallback Wed May 31 13:15:25 CEST 2006 starting... Enabling mainboard devices Enabling shadow ram vt8623 init starting ---8<--------------------------------------------------------------
Then it keeps restarting ???
Any hints someone??
Per
n Wed, 31 May 2006 07:56:44 -0600, Myles Watson wrote
I used the stock FC4 kernel with the same command line as you used. My autoboot was just hdb1:/linux_2.6.16.elf (I have a CD-ROM as hda)
Good luck,
Myles
-----Original Message----- From: linuxbios-bounces@linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Per Mellander Sent: Wednesday, May 31, 2006 6:53 AM To: myles@mouselemur.cs.byu.edu Cc: linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie )
Now I get so far that the kernel is identified and loaded but then it breaks :(
I created an elf with mkelfImage:
# mkelfImage --kernel=/vmlinuz-2.6.16-1.2111_FC5 --output=/vmlinuz.elf --initrd=/initrd-2.6.16-1.2111_FC5.img --command-line="ro root=LABEL=/ rhgb quiet console=ttyS0 console=ttyS0,115200"
----8<-------------------------------------------------------------
Jumping to boot code at 0x109ad4 FILO version 0.5 (root@mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 Press <Enter> for default boot, or <Esc> for boot prompt... timed out boot: hda1:/vmlinuz.elf find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8a find_ide_controller: primary channel: compatibility mode find_ide_controller: cmd_base=0x1f0 ctrl_base=0x3f4 ide_software_reset: Waiting for ide0 to become ready for reset... ok init_drive: Testing for hda init_drive: Probing for hda init_drive: LBA mode, sectors=268435455 init_drive: LBA48 mode, sectors=321672960 init_drive: Init device params... ok hda: LBA48 164GB: HDS722516VLAT80 Mounted ext2fs Loading Linux version 2.6.16-1.2111_FC5 (bhcompile@hs20-bc1-3.build.redhat.com) #1 Thu May 4 21:16:58 EDT 2006... Jumping to entry point... 0
LinuxBIOS-1.1.8.0Fallback Wed May 31 13:15:25 CEST 2006 starting... Enabling mainboard devices Enabling shadow ram
----8<-------------------------------------------------------------
I get the same result when I try,
AUTOBOOT_FILE = "hda1:/vmlinuz initrd=/initrd.img root=/dev/hda1 console=tty0 console=ttyS0,115200"
so the problem is not in the elf image.
Could you please send me a snippet from your AUTOBOOT or similar?
Btw. Do I have to make a 'special' kernel to make this work or should the stock FC5 work?
/Per
On Tue, 30 May 2006 08:38:53 -0600, Myles Watson wrote
Did you try using mkelfImage from ftp://ftp.lnxi.com/pub/mkelfImage ? It combines the vmlinuz & initrd files into one.
To get my machine to boot I used the same kernel parameters as I found in grub, set up by Fedora.
-- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
-- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
* Per Mellander per@mellander.org [060601 11:32]:
I don't know if I'm stupid or what, but it just won't work for me :(
First of. I can't have my harddisk connected as hdb1 and my cdrom as hda1, ( which is out of the box for my setup ) because the IDE-disk will not be recognized by LB if its secondary. ( ??? )
Then it keeps restarting ???
Any hints someone??
Hi Per,
- is your kernel compiled for any K7 or newer CPUs? I remember I had problems with the default SUSE kernel because it assumed CPU features that an Epia-M 10000 did not have.
- Can you run memtest as a payload before proceeding with filo? http://www.memtest86.com/ or http://www.memtest.org/ (not sure which one of them supports LinuxBIOS)
http://www.memtest86.com/ or http://www.memtest.org/ (not sure which one of them supports LinuxBIOS)
www.memtest86.com. But you need to make sure the serial port ui is enabled.
On Fri, 2 Jun 2006 00:16:41 +0200, Stefan Reinauer wrote
- is your kernel compiled for any K7 or newer CPUs? I remember I had problems with the default SUSE kernel because it assumed CPU features that an Epia-M 10000 did not have.
I did a quick test getting a vanilla kernel and compiled it for C3. Same (bad) result. BTW. I'm running an EPIA-M2 12000.
- Can you run memtest as a payload before proceeding with filo? http://www.memtest86.com/ or http://www.memtest.org/ (not sure which one of them supports LinuxBIOS)
Yes I can. Both serial and VGA output :)
I did not test with both memtest and filo as payload, only memtest. Do you know why I'm getting all those errors from memtest? Is that my problem?
Per
----8<--------------------------------------------------------------------------
Memtest-86 v3.2 | Pass 0% VIA C3 Nehemiah 1200 Mhz | Test 52% #################### L1 Cache: 64 4896MB/s | Test #1 [Address test, own address] L2 Cache: 64K 1464MB/s | Testing: 104K - 480M 480M Memory : 480M 251MB/s | Pattern: Chipset : VIA CLE266
WallTime Cached RsvdMem MemMap Cache ECC Test Pass Errors ECC Errs --------- ------ ------- -------- ----- --- ---- ---- ------ -------- 0:00:06 480M 0K LinuxBIOS on off Std 0 827 0 ----------------------------------------------------------------------------- Tst Pass Failing Address Good Bad Err-Bits Count Chan --- ---- ----------------------- -------- -------- -------- ----- ---- 1 0 000000c0cc4 - 0.0MB 000c0cc4 26ff3205 26f33ec1 1 1 0 000000c0cc8 - 0.0MB 000c0cc8 e8c30188 e8cf0d40 1 1 0 000000c0ccc - 0.0MB 000c0ccc f08a104e f0861c82 1 1 0 000000c0cd0 - 0.0MB 000c0cd0 e0d3c422 e0dfc8f2 1 1 0 000000c0cd4 - 0.0MB 000c0cd4 7580c6f6 758cca22 1 1 0 000000c0cd8 - 0.0MB 000c0cd8 26d4f610 26d8fac8 1 1 0 000000c0cdc - 0.0MB 000c0cdc 08262420 082a28fc 1 1 0 000000c0ce0 - 0.0MB 000c0ce0 8ae58a04 8ae986e4 1 1 0 000000c0ce4 - 0.0MB 000c0ce4 1c4689c6 1c4a8522 1 1 0 000000c0ce4 - 0.0MB 000c0ce4 1c4689c6 1c4a8522 1 (ESC)exit (c)configuration (SP)scroll_lock (CR)scroll_unlock
----8<--------------------------------------------------------------------------
* Per Mellander per@mellander.org [060605 14:35]:
On Fri, 2 Jun 2006 00:16:41 +0200, Stefan Reinauer wrote
- Can you run memtest as a payload before proceeding with filo? http://www.memtest86.com/ or http://www.memtest.org/ (not sure which one of them supports LinuxBIOS)
Yes I can. Both serial and VGA output :)
I did not test with both memtest and filo as payload, only memtest. Do you know why I'm getting all those errors from memtest? Is that my problem?
Per
Are they all in the c0000 segment? If so, its not a problem, as thats the vga bios area which is not writable..
Otherwise, something is wrong.
----8<--------------------------------------------------------------------------
Memtest-86 v3.2 | Pass 0%VIA C3 Nehemiah 1200 Mhz | Test 52% #################### L1 Cache: 64 4896MB/s | Test #1 [Address test, own address] L2 Cache: 64K 1464MB/s | Testing: 104K - 480M 480M Memory : 480M 251MB/s | Pattern: Chipset : VIA CLE266
WallTime Cached RsvdMem MemMap Cache ECC Test Pass Errors ECC Errs
0:00:06 480M 0K LinuxBIOS on off Std 0 827 0
Tst Pass Failing Address Good Bad Err-Bits Count Chan
1 0 000000c0cc4 - 0.0MB 000c0cc4 26ff3205 26f33ec1 1 1 0 000000c0cc8 - 0.0MB 000c0cc8 e8c30188 e8cf0d40 1 1 0 000000c0ccc - 0.0MB 000c0ccc f08a104e f0861c82 1 1 0 000000c0cd0 - 0.0MB 000c0cd0 e0d3c422 e0dfc8f2 1 1 0 000000c0cd4 - 0.0MB 000c0cd4 7580c6f6 758cca22 1 1 0 000000c0cd8 - 0.0MB 000c0cd8 26d4f610 26d8fac8 1 1 0 000000c0cdc - 0.0MB 000c0cdc 08262420 082a28fc 1 1 0 000000c0ce0 - 0.0MB 000c0ce0 8ae58a04 8ae986e4 1 1 0 000000c0ce4 - 0.0MB 000c0ce4 1c4689c6 1c4a8522 1 1 0 000000c0ce4 - 0.0MB 000c0ce4 1c4689c6 1c4a8522 1 (ESC)exit (c)configuration (SP)scroll_lock (CR)scroll_unlock
----8<--------------------------------------------------------------------------
On Mon, 5 Jun 2006 18:02:20 +0200, Stefan Reinauer wrote
Are they all in the c0000 segment? If so, its not a problem, as thats the vga bios area which is not writable..
Yes they're all in that segment.
You don't have any clue why my kernel loads but then LB restarts as mentioned in my previous posting?
I've tested with plain kernel ( several different ones ), kernel and initrd, kernel+initrd with mkelfImage and a lot of different settings for kernel params. etc. Nothing helps, it keeps on restarting after kernel is loaded. Is there any more debug that I can switch on to se whats causing the error?
I'm not sure how to make a LB without VGA-bios for my EPIA. Can anyone explain which settings that need to be changed in Config.lb and/or Makefile(s) so I can test my board with serial only output?
Per
On Tue, 6 Jun 2006, Per Mellander wrote:
On Mon, 5 Jun 2006 18:02:20 +0200, Stefan Reinauer wrote
Are they all in the c0000 segment? If so, its not a problem, as thats the vga bios area which is not writable..
Yes they're all in that segment.
You don't have any clue why my kernel loads but then LB restarts as mentioned in my previous posting?
I've tested with plain kernel ( several different ones ), kernel and initrd, kernel+initrd with mkelfImage and a lot of different settings for kernel params. etc. Nothing helps, it keeps on restarting after kernel is loaded. Is there any more debug that I can switch on to se whats causing the error?
Bought a via PD6000 about two weeks ago. Using factory bios until I get everything else just right. One of the first thing i discovered the via box kept restarting, so I moved the hd to a tyan mb and tried booting. The tyan stopped with a kernel panic.
Got the via working and then built several versions of a 2.6.19 kernel. The one that seems to work the best is where the cpu is called a "k6". If interested, will email copy of the config file. (Or, if there's enough interest will post it).
russ
* Per Mellander per@mellander.org [060606 08:57]:
You don't have any clue why my kernel loads but then LB restarts as mentioned in my previous posting?
sorry, not yet. :(
I've tested with plain kernel ( several different ones ), kernel and initrd, kernel+initrd with mkelfImage and a lot of different settings for kernel params. etc. Nothing helps, it keeps on restarting after kernel is loaded. Is there any more debug that I can switch on to se whats causing the error?
Have you been using filo all the time? Can you switch on the DEBUG_ config variables? Can you try other payloads? (etherboot)
What compiler have you been using? What Linux distribution?
I'm not sure how to make a LB without VGA-bios for my EPIA. Can anyone explain which settings that need to be changed in Config.lb and/or Makefile(s) so I can test my board with serial only output?
If you built the Epia from an unchanged source tree, it should be without VGA bios..
On Tue, 6 Jun 2006, Stefan Reinauer wrote:
- Per Mellander per@mellander.org [060606 08:57]:
You don't have any clue why my kernel loads but then LB restarts as mentioned in my previous posting?
sorry, not yet. :(
I can think of 3:
1. The kernel (and root) is on a vfat fs but vfat support is not compiled into the kernel. Same for other file system mismatches.
2. Booting from an ide-hd or ide-cd is so commonplace that it is easy to overlook needed hardware support in the kernel if you boot from some- thing else.
3. Incompatable cpu support in the kernel. If you are using a generic 486 there should be no problem. But a pentium II or even the via offered in the kernel menu doesn't work. (The via only works for one model via chip).
Hope this helps, russ
On Tue, 6 Jun 2006 13:45:48 +0200, Stefan Reinauer wrote
Have you been using filo all the time? Can you switch on the DEBUG_ config variables? Can you try other payloads? (etherboot)
Yes, I've been using filo all the time. Tried to compile etherboot but it wouldn't compile. Probably because of my gcc 4.1.0 that does not support memcpy (?).
I've only ran it with DEBUG_IDE when I had problems with get it to load kernel from hdb. It kept complaining about "Drive 1 missing" so I did a dd to another drive and hooked that up. ( Easier than pulling the drive out and move the switches to make it master. Very tight 1U chassie ;) ) Will try a more extensive debug later.
I have on the other hand succeeded with memtest as mentioned before.
What compiler have you been using? What Linux distribution?
gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3) Fedora Core 5
If you built the Epia from an unchanged source tree, it should be without VGA bios..
Well I tried that aswell but I didn't get the BIOS to boot then. Perhaps I've missed something. I'll make another try today.
Per
* Per Mellander per@mellander.org [060607 08:58]:
On Tue, 6 Jun 2006 13:45:48 +0200, Stefan Reinauer wrote
Have you been using filo all the time? Can you switch on the DEBUG_ config variables? Can you try other payloads? (etherboot)
Yes, I've been using filo all the time. Tried to compile etherboot but it wouldn't compile. Probably because of my gcc 4.1.0 that does not support memcpy (?).
Hm, weird. YhLu?
I was reading the other day about VIA's PadLock Hardware Security Suite on the C5P die. Does this one need some special initialization?
Can you try to enable early_printk in your kernel and see whether it says anything?
On Thu, 1 Jun 2006, Per Mellander wrote:
I don't know if I'm stupid or what, but it just won't work for me :(
First of. I can't have my harddisk connected as hdb1 and my cdrom as hda1, ( which is out of the box for my setup ) because the IDE-disk will not be recognized by LB if its secondary. ( ??? )
So far it looks like we've covered almost everything except ide-cabling.
The older 40-wire cables, the controller shook hands with the master, the master shook hands with the slave. The jumpers on the drives decided which was which. The master on the primary bus is hda, on the secondary bus it's hdc. On a single drive system you cannot have a hdb. And you really should jumper it as a single drive.
The 80-wire cables are cable-select. Which means all the drives can be jumpered as single drives. I found out the hard way if you have only one drive on a cable it *must* be in the end connector. (cd's and dvd's don't count and will work in either connector).
One more little problem: no matter which drive you're booting from it must agree with the info in /etc/fstab. Once you get the box to boot you can read dmesg to find out where it thinks the cd is.
Hope this helps, russ
The 80-wire cables are cable-select. Which means all the drives can be jumpered as single drives. I found out the hard way if you have only one drive on a cable it *must* be in the end connector. (cd's and dvd's don't count and will work in either connector).
This is really a per drive/ per setup thing. I've used 80-pin cables with HD's in both connectors when I set the drive up as signle or master.
IIRC on an 80p cable the PDIAG signal is still connected between the drives just like a 40pin but its broken between the drives at the host at the connector where it becomes 40/80 select.
The spec recommends that for an 80pin setup you allways attach the drive at the outmost connector. This keeps the extra connector from acting as an unterminated stub. So depending on your cable and setup you could get a case where and 80pin driver in >= ATA100 mode would not work on an inside connector.
CDROM's never really push the speed limit on the IDE bus so thats why they would work well on either connctor.
I'm just reading this thread in more detail. Sorry for this latecomer message.
A few tips for that very first time you boot linux on a linuxbios machine: 1) when booting linuxbios on a new machine, ALWAYS configure the kernel as an i386. It's just safer that way. Turn off everything you can. make sure what you're doing would work on a 1990-era PC. 2) always enable serial and, before you try linuxbios, run minicom on the machine and make sure serial REALLY works. This is also a good cable test. Take nothing for granted. 3) If it's legal where you live, always burn a copy of the fuctory bios and boot with that, to ensure your burn path is totally working. Again, if it is legal where you live, keep a spare copy of fuctory bios around for that inevitable time when you screw up and flash over it. 4) never try VGA on the first time around. It adds too much variation 5) use earlyprintk! earlyprintk=ttyS0,115200,keep 6) learn to use initramfs, and have it boot a simple shell (I'm just getting the hang of this, but it's very useful) (you can write a shell in surprisingly small space) 7) spontaneous reboots almost always mean that you have the wrong cpu type. See note (1) above. very quick reboots are a good hint that memory is getting errors. Lockups are a sign of bad memory programming (you wouldn't believe some of the failures I've seen) or you've got an old VIA chipset with a bug :-) For any but the worst reboots, earlyprintk is a big help.
thanks
ron
On Sat, 10 Jun 2006 10:11:28 -0600, ron minnich wrote
- when booting linuxbios on a new machine, ALWAYS configure the kernel as an i386. It's just safer that way. Turn off everything you
can. make sure what you're doing would work on a 1990-era PC.
Tried with a pure i386-kernel, same result :(
- always enable serial and, before you try linuxbios, run minicom on the machine and make sure serial REALLY works. This is also a good cable test. Take nothing for granted.
It works alright! Has been running it from day one ;)
- If it's legal where you live, always burn a copy of the fuctory bios and boot with that, to ensure your burn path is totally working. Again, if it is legal where you live, keep a spare copy of fuctory bios around for that inevitable time when you screw up and flash over it.
I've got a BIOS-savior, and I run the BIOS in that. I don't think it will make any difference pulling the savior out and place LB in the original socket.
- never try VGA on the first time around. It adds too much variation
I'm not quite sure how to manage that. Everytime I've tried just leaving out the "cat /root/113mem.bin fallback/linuxbios.rom > ./linuxbios.rom" I end up with a nonbootable prom. Is there any other changes to be done to make it work?
- use earlyprintk! earlyprintk=ttyS0,115200,keep
Tried that, no special output at all. ( See below. ) What I did was to make sure kernel is compiled with CONFIG_EARLY_PRINTK=y and adding the above line to my commandline:
mkelfImage --kernel=/boot/vmlinuz-2.6.16.19-i386 \ --output=/vmlinuz-i386-ep.elf \ --initrd=/boot/initrd-2.6.16.19-i386.img \ --command-line="ro root=LABEL=/ rhgb quiet console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200,keep"
--8<-----------------------------
Jumping to boot code at 0x109ad4 FILO version 0.5 (root@mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 Press <Enter> for default boot, or <Esc> for boot prompt... boot: hda1:/vmlinuz-i386-ep.elf find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8a find_ide_controller: primary channel: compatibility mode find_ide_controller: cmd_base=0x1f0 ctrl_base=0x3f4 ide_software_reset: Waiting for ide0 to become ready for reset... ok init_drive: Testing for hda init_drive: Probing for hda init_drive: LBA mode, sectors=268435455 init_drive: LBA48 mode, sectors=321672960 init_drive: Init device params... ok hda: LBA48 164GB: HDS722516VLAT80 Mounted ext2fs Loading Linux version 2.6.16.19-i386 (root@mm.int.mmtab.se) #4 Mon Jun 12 10:46:16 CEST 2006... Jumping to entry point... 0
--8<-----------------------------
- learn to use initramfs, and have it boot a simple shell (I'm just getting the hang of this, but it's very useful) (you can write a shell in surprisingly small space)
I'd love to, as soon as I can get the kernel to load at all.
- spontaneous reboots almost always mean that you have the wrong cpu type. See note (1) above. very quick reboots are a good hint that memory is getting errors. Lockups are a sign of bad memory programming (you wouldn't believe some of the failures I've seen) or you've got an old VIA chipset with a bug :-) For any but the worst reboots, earlyprintk is a big help.
[root@mm linux-2.6.16.19]# lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 82) 00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 82) 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03)
[root@mm linux-2.6.16.19]# cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 9 model name : VIA Nehemiah stepping : 8 cpu MHz : 1199.924 cache size : 64 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr cx8 mtrr pge cmov pat mmx fxsr sse rng rng_en ace ace_en bogomips : 2403.34
/Per
So I did some new testing today!
I created a kernel with serial console, tested it with my factory BIOS and it worked alright.
Then I recompiled filo-0.5 with DEBUG_ALL=1
Did a new mkelfImage with the new kernel and same params as in the first test. ( earlyprintk etc.
When I boot my machine with the latest BIOS this is what happens:
[Initial logging snipped for clarity] Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3
rom_stream: 0xfffd0000 - 0xfffeffff Found ELF candiate at offset 0 New segment addr 0x100000 size 0x359c0 offset 0xc0 filesize 0x10728 (cleaned up) New segment addr 0x100000 size 0x359c0 offset 0xc0 filesize 0x10728 New segment addr 0x1359c0 size 0x48 offset 0x10800 filesize 0x48 (cleaned up) New segment addr 0x1359c0 size 0x48 offset 0x10800 filesize 0x48 Dropping non PT_LOAD segment Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000359c0 filesz: 0x0000000000010728 Clearing Segment: addr: 0x0000000000110728 memsz: 0x0000000000025298 Loading Segment: addr: 0x00000000001359c0 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x10c4b4 FILO version 0.5 (root@mm.int.mmtab.se) Tue Jun 13 14:30:12 CEST 2006 collect_sys_info: boot eax = 0xe1fb007 collect_sys_info: boot ebx = 0x1dff6940 collect_sys_info: boot arg = 0x1dff6940 malloc_diag: alloc: 0 bytes (0 blocks), free: 16376 bytes (1 blocks) malloc_diag: alloc: 24 bytes (1 blocks), free: 16352 bytes (1 blocks) collect_elfboot_info: Bootloader: elfboot collect_elfboot_info: Version: 1.3 malloc_diag: alloc: 40 bytes (2 blocks), free: 16336 bytes (1 blocks) collect_linuxbios_info: Searching for LinuxBIOS tables... find_lb_table: Found canidate at: 00000530 find_lb_table: header checksum o.k. find_lb_table: table checksum o.k. find_lb_table: record count o.k. collect_linuxbios_info: Found LinuxBIOS table at: 00000530 malloc_diag: alloc: 128 bytes (3 blocks), free: 16248 bytes (1 blocks) convert_memmap: 0x00000000000000 0x00000000000bd8 16 convert_memmap: 0x00000000000bd8 0x0000000009f428 1 convert_memmap: 0x000000000c0000 0x00000000030000 1 convert_memmap: 0x000000000f0000 0x00000000000c00 16 convert_memmap: 0x000000000f0c00 0x0000001df0f400 1 collect_sys_info: 0000000000000bd8-00000000000a0000 collect_sys_info: 00000000000c0000-00000000000f0000 collect_sys_info: 00000000000f0c00-000000001e000000 collect_sys_info: RAM 480 MB relocate: Current location: 0x100000-0x135a07 relocate: Relocating to 0x1dfca5f0-0x1dfffff7... ok setup_timers: CPU 1200 MHz pci_init: Scanning PCI: found 14 devices malloc_diag: alloc: 304 bytes (4 blocks), free: 16072 bytes (1 blocks) pci_init: 00:00.0 1106:3123 0600 00 pci_init: 00:01.0 1106:b091 0604 00 pci_init: 00:0a.0 1180:0476 0607 00 pci_init: 00:0a.1 1180:0476 0607 00 pci_init: 00:0d.0 1106:3044 0c00 10 pci_init: 00:10.0 1106:3038 0c03 00 pci_init: 00:10.1 1106:3038 0c03 00 pci_init: 00:10.2 1106:3038 0c03 00 pci_init: 00:10.3 1106:3104 0c03 20 pci_init: 00:11.0 1106:3177 0601 00 pci_init: 00:11.1 1106:0571 0101 8a pci_init: 00:11.5 1106:3059 0401 00 pci_init: 00:12.0 1106:3065 0200 00 pci_init: 01:00.0 1106:3122 0300 00 Press <Enter> for default boot, or <Esc> for boot prompt... boot: hda1:/vmlinuz.elf malloc_diag: alloc: 336 bytes (5 blocks), free: 16040 bytes (1 blocks) malloc_diag: alloc: 352 bytes (6 blocks), free: 16024 bytes (1 blocks) file_open: dev=hda1, path=/vmlinuz.elf find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8a find_ide_controller: primary channel: compatibility mode find_ide_controller: cmd_base=0x1f0 ctrl_base=0x3f4 ide_software_reset: Waiting for ide0 to become ready for reset... ok init_drive: Testing for hda init_drive: Probing for hda init_drive: LBA mode, sectors=268435455 init_drive: LBA48 mode, sectors=321672960 init_drive: Init device params... ok hda: LBA48 164GB: HDS722516VLAT80 devopen: Partition 1 start 63 length 76180167 Mounted ext2fs malloc_diag: alloc: 336 bytes (5 blocks), free: 16040 bytes (1 blocks) malloc_diag: alloc: 504 bytes (6 blocks), free: 15872 bytes (1 blocks) malloc_diag: alloc: 664 bytes (7 blocks), free: 15712 bytes (1 blocks) malloc_diag: alloc: 680 bytes (8 blocks), free: 15696 bytes (1 blocks) malloc_diag: alloc: 768 bytes (9 blocks), free: 15608 bytes (1 blocks) process_image_notes: Image checksum: 0x7c4a malloc_diag: alloc: 608 bytes (8 blocks), free: 15768 bytes (2 blocks) Loading Linux version 2.6.16.19-i386-serial (root@mm.int.mmtab.se) #6 Tue Jun 13 11:40:32 CEST 2006... load_segments: segment 1 addr:0x10000 file:0x11bc mem:0x12264 loading... clearing... ok load_segments: segment 2 addr:0x20000 file:0x0 mem:0x1070 loading... clearing... ok load_segments: segment 3 addr:0x100000 file:0x19067e mem:0x700000 loading... clearing... ok load_segments: segment 4 addr:0x800000 file:0xcc4d9 mem:0xcc4d9 loading... clearing... ok load_segments: Loaded 2481427 bytes in 15457ms (160KB/s) malloc_diag: alloc: 872 bytes (9 blocks), free: 15504 bytes (2 blocks) elf_load: current time: 317476 elf_load: entry point is 0x10000 Jumping to entry point... 0
And here it reboots... :(
I tried with:
boot: hda1:/boot/vmlinuz-2.6.16.19-i386-serial earlyprintk=ttyS0,115200,keep
which is my 'plain' kernel, but with same result.
Please anyone!
Still I can't get a LinuxBIOS without the additional video-bios cat'ed at the beginning of my LB to boot at all. That is I can't manufacture a BIOS that won't initialize the VGA. How to do a LinuxBIOS without the VGA-portion in it???
/Per
Still I can't get a LinuxBIOS without the additional video-bios
cat'ed at the beginning
of my LB to boot at all. That is I can't manufacture a BIOS that won't initialize the VGA. How to do a LinuxBIOS without the VGA-portion in it???
Sounds like your rom size or location info is is wrong. I don't see your config.lb posted anywhere in this thread.
post up your config.lb please.
What size is your flash?
You can do a quick check by just pre-pending a 64k file of 0xffs rather than a video bios. And see if it boots.
I don't remember if we ever patched the expansion rom code so that it verifies signatures before running the code. If not then it will crash when it runs the video bios but then you can just disable that option in your config and it should run.
On Tue, 13 Jun 2006 09:41:35 -0500, Richard Smith wrote
Sounds like your rom size or location info is is wrong. I don't see your config.lb posted anywhere in this thread.
It's a plain vanilla Config.lb that's generated by "./buildtarget via/epia-m". You'll find it attached.
What size is your flash?
256M
You can do a quick check by just pre-pending a 64k file of 0xffs rather than a video bios. And see if it boots.
I'll try that today.
I don't remember if we ever patched the expansion rom code so that it verifies signatures before running the code. If not then it will crash when it runs the video bios but then you can just disable that option in your config and it should run.
Where can I find info about each option i.e which option affects the VGA init?
Thanks for your help,
Per
-
Myles Watson -
Per Mellander -
Richard Smith -
ron minnich -
Russell Whitaker -
Stefan Reinauer