From per at mellander.org Thu Jun 1 11:32:46 2006 From: per at mellander.org (Per Mellander) Date: Thu, 1 Jun 2006 11:32:46 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> Message-ID: <20060601091409.M98965@mellander.org> 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 at mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 Press for default boot, or 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 at 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 at linuxbios.org > [mailto:linuxbios-bounces at linuxbios.org] On Behalf Of Per Mellander > Sent: Wednesday, May 31, 2006 6:53 AM > To: myles at mouselemur.cs.byu.edu > Cc: linuxbios at 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 at mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 > Press for default boot, or 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 at 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 at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Thu Jun 1 16:09:49 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Thu, 01 Jun 2006 08:09:49 -0600 Subject: [LinuxBIOS] a slight change to startup and elf images Message-ID: <447EF52D.2080204@lanl.gov> Right now, we use mkelfimage to set up parameter blocks for linux. There is a lot of code to do this, and I am running out of room on OLPC. I need to build tiny elf images with on executable code in them (other than your kernel, of course). I have modified mkelfimage so that it produces an elfimage with only 3 segments: command line, kernel, initrd. With this option, you can build a very simple elfimage with just those three things. There is the issue of setting up %esi for 386 linux. I am considering the following convention: architecture-independent part (src/boot/) For the first PT_LOAD elf segment, assume it is the command line. Set a variable, command_line, to the load address of this segment. architecture-dependent, e.g. 386 (src/cpu/boot.c) set %esi to command_line. If you are using normal mkelfimage, this is a no-op: esi setting is ignored. If you are using mkelfimage with my option (e.g. OLPC), this address will be used as the command line pointer. I can't see a problem, any comments? thanks ron From stepan at coresystems.de Fri Jun 2 00:16:41 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 2 Jun 2006 00:16:41 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060601091409.M98965@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> Message-ID: <20060601221641.GA11315@coresystems.de> * Per Mellander [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) -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From smithbone at gmail.com Fri Jun 2 00:25:07 2006 From: smithbone at gmail.com (Richard Smith) Date: Thu, 1 Jun 2006 17:25:07 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060601221641.GA11315@coresystems.de> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> Message-ID: <8a0c36780606011525q57ebf656qd6e9fd299cd1c059@mail.gmail.com> > 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. -- Richard A. Smith From smithbone at gmail.com Fri Jun 2 00:32:46 2006 From: smithbone at gmail.com (Richard Smith) Date: Thu, 1 Jun 2006 17:32:46 -0500 Subject: [LinuxBIOS] OLPC (One Laptop Per Child) Developer's program. In-Reply-To: <1149025377.30703.141.camel@localhost.localdomain> References: <1149025377.30703.141.camel@localhost.localdomain> Message-ID: <8a0c36780606011532lc1d6253t51a2173af9c432be@mail.gmail.com> On 5/30/06, Jim Gettys wrote: > As you know, we've said we were going to have a developer's program. You > can find more information, including how to apply for boards at: Ron: how many of these are sort of ear marked for LB developers? I would like to apply for one of these but if LB allready has enough then I don't want to hog one. -- Richard A. Smith From jg at laptop.org Fri Jun 2 21:36:48 2006 From: jg at laptop.org (Jim Gettys) Date: Fri, 02 Jun 2006 15:36:48 -0400 Subject: [LinuxBIOS] linuxbios Digest, Vol 16, Issue 2 In-Reply-To: References: Message-ID: <1149277008.6309.43.camel@localhost.localdomain> > Date: Thu, 1 Jun 2006 17:32:46 -0500 > From: "Richard Smith" > Subject: Re: [LinuxBIOS] OLPC (One Laptop Per Child) Developer's > program. > To: LinuxBIOS > Cc: jg at laptop.org > Message-ID: > <8a0c36780606011532lc1d6253t51a2173af9c432be at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 5/30/06, Jim Gettys wrote: > > > As you know, we've said we were going to have a developer's program. You > > can find more information, including how to apply for boards at: > > Ron: how many of these are sort of ear marked for LB developers? I > would like to apply for one of these but if LB allready has enough > then I don't want to hog one. > This is my headache to deal with. I don't want to discourage people to apply, and we're ending up with more hardware than expected, and I haven't revisited my spreadsheet to reflect that. What I have down now for LinuxBIOS development is certainly significantly more than the number currently in people's hands. Regards, - Jim -- Jim Gettys One Laptop Per Child From adi.coman at gmail.com Mon Jun 5 13:59:40 2006 From: adi.coman at gmail.com (Adrian Coman) Date: Mon, 5 Jun 2006 13:59:40 +0200 Subject: [LinuxBIOS] Is my hardware supported? Message-ID: <2f06b8970606050459t4fc87e73w82a1917a7a2c7dea@mail.gmail.com> Hi, I have the following lspci output, please let me know if this hw it's supported. Thanks, Adrian 00:00.0 Host bridge: Intel Corporation 955X Memory Controller Hub Subsystem: Dell: Unknown device 01a8 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge: Intel Corporation 955X PCI Express Graphics Port (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: 00:1b.0 Class 0403: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) Subsystem: Dell: Unknown device 01a8 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: 00:1c.4 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: 00:1c.5 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01) (prog-if 00 [UHCI]) Subsystem: Dell: Unknown device 01a8 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: Dell: Unknown device 01a8 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Region 1: I/O ports at Region 2: I/O ports at Region 3: I/O ports at Region 4: I/O ports at ffa0 [size=16] 00:1f.2 Class 0106: Intel Corporation 82801GR/GH (ICH7 Family) Serial ATA Storage Controllers cc=AHCI (rev 01) (prog-if 01) Subsystem: Dell: Unknown device 01a8 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) Subsystem: Dell: Unknown device 01a8 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) Subsystem: Dell: Unknown device 01a8 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- From per at mellander.org Mon Jun 5 14:35:21 2006 From: per at mellander.org (Per Mellander) Date: Mon, 5 Jun 2006 14:35:21 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060601221641.GA11315@coresystems.de> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> Message-ID: <20060605122738.M78729@mellander.org> 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<-------------------------------------------------------------------------- From rminnich at lanl.gov Mon Jun 5 16:47:40 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Mon, 05 Jun 2006 08:47:40 -0600 Subject: [LinuxBIOS] Is my hardware supported? In-Reply-To: <2f06b8970606050459t4fc87e73w82a1917a7a2c7dea@mail.gmail.com> References: <2f06b8970606050459t4fc87e73w82a1917a7a2c7dea@mail.gmail.com> Message-ID: <4484440C.1060609@lanl.gov> Adrian Coman wrote: > Hi, > > I have the following lspci output, please let me know if this hw it's supported. > > Thanks, > Adrian > > 00:00.0 Host bridge: Intel Corporation 955X Memory Controller Hub > Subsystem: Dell: Unknown device 01a8 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > SERR- Latency: 0 > Capabilities: no, i'm sorry, it's not. This is intel chipset, and intel is not a linuxbios-friendly company any more. thanks ron From stepan at coresystems.de Mon Jun 5 18:02:20 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Mon, 5 Jun 2006 18:02:20 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060605122738.M78729@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> Message-ID: <20060605160220.GA18023@coresystems.de> * Per Mellander [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<-------------------------------------------------------------------------- > -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From per at mellander.org Tue Jun 6 08:57:03 2006 From: per at mellander.org (Per Mellander) Date: Tue, 6 Jun 2006 08:57:03 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060605160220.GA18023@coresystems.de> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> <20060605160220.GA18023@coresystems.de> Message-ID: <20060606064645.M73489@mellander.org> 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 From russ at ashlandhome.net Tue Jun 6 10:33:04 2006 From: russ at ashlandhome.net (Russell Whitaker) Date: Tue, 6 Jun 2006 01:33:04 -0700 (PDT) Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060606064645.M73489@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> <20060605160220.GA18023@coresystems.de> <20060606064645.M73489@mellander.org> Message-ID: 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 From stepan at coresystems.de Tue Jun 6 13:45:48 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Tue, 6 Jun 2006 13:45:48 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060606064645.M73489@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> <20060605160220.GA18023@coresystems.de> <20060606064645.M73489@mellander.org> Message-ID: <20060606114548.GA20687@coresystems.de> * Per Mellander [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.. -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From russ at ashlandhome.net Tue Jun 6 20:23:53 2006 From: russ at ashlandhome.net (Russell Whitaker) Date: Tue, 6 Jun 2006 11:23:53 -0700 (PDT) Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060606114548.GA20687@coresystems.de> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> <20060605160220.GA18023@coresystems.de> <20060606064645.M73489@mellander.org> <20060606114548.GA20687@coresystems.de> Message-ID: On Tue, 6 Jun 2006, Stefan Reinauer wrote: > * Per Mellander [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 From per at mellander.org Wed Jun 7 08:58:43 2006 From: per at mellander.org (Per Mellander) Date: Wed, 7 Jun 2006 08:58:43 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060606114548.GA20687@coresystems.de> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> <20060605160220.GA18023@coresystems.de> <20060606064645.M73489@mellander.org> <20060606114548.GA20687@coresystems.de> Message-ID: <20060607064759.M97696@mellander.org> 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 From patrick at xentech.nl Wed Jun 7 14:09:40 2006 From: patrick at xentech.nl (Patrick (Xentech)) Date: Wed, 07 Jun 2006 14:09:40 +0200 Subject: [LinuxBIOS] Overclocking with LinuxBIOS Message-ID: <20060607120940.672357fe@f89199.upc-f.chello.nl> Hi, Would it be possible to do some overclocking with LinuxBIOS? -------------- next part -------------- An HTML attachment was scrubbed... URL: From stepan at coresystems.de Wed Jun 7 14:17:01 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Wed, 7 Jun 2006 14:17:01 +0200 Subject: [LinuxBIOS] Overclocking with LinuxBIOS In-Reply-To: <20060607120940.672357fe@f89199.upc-f.chello.nl> References: <20060607120940.672357fe@f89199.upc-f.chello.nl> Message-ID: <20060607121701.GA5622@coresystems.de> * Patrick (Xentech) [060607 14:09]: > Hi, > > Would it be possible to do some overclocking with LinuxBIOS? In theory, yes. If the chipset/cpu "supports" it and the specs are available to this. Stefan -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From rminnich at lanl.gov Wed Jun 7 16:35:40 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Wed, 07 Jun 2006 08:35:40 -0600 Subject: [LinuxBIOS] Overclocking with LinuxBIOS In-Reply-To: <20060607120940.672357fe@f89199.upc-f.chello.nl> References: <20060607120940.672357fe@f89199.upc-f.chello.nl> Message-ID: <4486E43C.4080008@lanl.gov> Patrick (Xentech) wrote: > Hi, > > Would it be possible to do some overclocking with LinuxBIOS? > yes, years ago we did work with this. We just had a linux command that set the overclocking. ron From tylerapohl at gmail.com Wed Jun 7 18:09:18 2006 From: tylerapohl at gmail.com (Tyler Pohl) Date: Wed, 7 Jun 2006 09:09:18 -0700 Subject: [LinuxBIOS] bios addressing Message-ID: <503ab0210606070909k729788dbr37f86f4384aa962c@mail.gmail.com> What is the first instructions address in a 2Mb bios chip ? I'm not very familiar with i386 processors obviously because i assumed the first instruction on power up was 0h but i don't think thats the case now. Is there a good flow chart somewhere on the web I don't know about ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From stuge-linuxbios at cdy.org Wed Jun 7 19:41:55 2006 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Wed, 7 Jun 2006 19:41:55 +0200 Subject: [LinuxBIOS] bios addressing In-Reply-To: <503ab0210606070909k729788dbr37f86f4384aa962c@mail.gmail.com> References: <503ab0210606070909k729788dbr37f86f4384aa962c@mail.gmail.com> Message-ID: <20060607174156.19413.qmail@cdy.org> On Wed, Jun 07, 2006 at 09:09:18AM -0700, Tyler Pohl wrote: > What is the first instructions address in a 2Mb bios chip ? I'm not very > familiar with i386 processors obviously because i assumed the first > instruction on power up was 0h but i don't think thats the case now. Is > there a good flow chart somewhere on the web I don't know about ? x86 always boot at 0xfffffff0 and BIOS ROM ends at 4GB with very few exceptions, if any. For a 2Mbit BIOS chip (256kbyte) that means the BIOS ROM is at 0xfffc0000 and x86 will boot from 0x3fff0 in the chip. //Peter From rminnich at lanl.gov Wed Jun 7 20:48:00 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Wed, 07 Jun 2006 12:48:00 -0600 Subject: [LinuxBIOS] bios addressing In-Reply-To: <20060607174156.19413.qmail@cdy.org> References: <503ab0210606070909k729788dbr37f86f4384aa962c@mail.gmail.com> <20060607174156.19413.qmail@cdy.org> Message-ID: <44871F60.9090701@lanl.gov> Peter Stuge wrote: > On Wed, Jun 07, 2006 at 09:09:18AM -0700, Tyler Pohl wrote: > >>What is the first instructions address in a 2Mb bios chip ? I'm not very >>familiar with i386 processors obviously because i assumed the first >>instruction on power up was 0h but i don't think thats the case now. Is >>there a good flow chart somewhere on the web I don't know about ? > > > x86 always boot at 0xfffffff0 and BIOS ROM ends at 4GB with very few > exceptions, if any. > > For a 2Mbit BIOS chip (256kbyte) that means the BIOS ROM is at > 0xfffc0000 and x86 will boot from 0x3fff0 in the chip. um. .... it's a bit more complext. We still put the ROMCC payload at the top, and GCC payload right ahead of it. Also, we maintain high addressing, so romcc will address high mem in 4G. It's quite odd, due to the x86 (I need a nickel for every time I've said that). jmp 0xf000:something, then go to 32-bit mode at 0xffffabcd, then copy gcc to low memory, and jump to low memory. ack. ron From arturo.mann at gmail.com Thu Jun 8 02:16:41 2006 From: arturo.mann at gmail.com (Arturo Mann) Date: Wed, 7 Jun 2006 19:16:41 -0500 Subject: [LinuxBIOS] Tyan ThunderK8SRE Message-ID: <601d22e40606071716v72894d29o5e28099f0894f574@mail.gmail.com> Hello there, I'm building a new server, based around a Tyan Thunder K8SRE (S2891). The specs claim it's using an 8MiB flash chip for Phoneix Bios. I would very much like to use LinuxBios to make the booting much easier for me. (After the initial turmoil) So, my question is, does anyone know which BiosSaviour will work with such a Flash /Bios / Mainboard combo? Thanks, Cheers, -- ------------------------ Arturo Mann, arturo.mann at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhendrix at google.com Thu Jun 8 03:22:48 2006 From: dhendrix at google.com (David Hendricks) Date: Wed, 7 Jun 2006 18:22:48 -0700 Subject: [LinuxBIOS] Overclocking with LinuxBIOS In-Reply-To: <20060607120940.672357fe@f89199.upc-f.chello.nl> References: <20060607120940.672357fe@f89199.upc-f.chello.nl> Message-ID: (On a tangent) For that matter, I wonder if there are any userland apps that can do this in Linux... Does anyone have insight on the utilities motherboard vendors typically bundle for overclocking in Windows and if they require BIOS interaction at all? On 6/7/06, Patrick (Xentech) wrote: > > Hi, > > Would it be possible to do some overclocking with LinuxBIOS? > > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Thu Jun 8 03:23:51 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Wed, 7 Jun 2006 18:23:51 -0700 Subject: [LinuxBIOS] Tyan ThunderK8SRE Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FBE@ssvlexmb2.amd.com> The BIOSSavior only have 512k. So you need to make sure the linuxbios image is 512k. YH ________________________________ From: linuxbios-bounces at linuxbios.org [mailto:linuxbios-bounces at linuxbios.org] On Behalf Of Arturo Mann Sent: Wednesday, June 07, 2006 5:17 PM To: linuxbios at linuxbios.org Subject: [LinuxBIOS] Tyan ThunderK8SRE Hello there, I'm building a new server, based around a Tyan Thunder K8SRE (S2891). The specs claim it's using an 8MiB flash chip for Phoneix Bios. I would very much like to use LinuxBios to make the booting much easier for me. (After the initial turmoil) So, my question is, does anyone know which BiosSaviour will work with such a Flash /Bios / Mainboard combo? Thanks, Cheers, -- ------------------------ Arturo Mann, arturo.mann at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ward at pong.be Thu Jun 8 13:45:39 2006 From: ward at pong.be (Ward Vandewege) Date: Thu, 8 Jun 2006 07:45:39 -0400 Subject: [LinuxBIOS] Tyan ThunderK8SRE In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FBE@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FBE@ssvlexmb2.amd.com> Message-ID: <20060608114539.GA16526@localdomain> On Wed, Jun 07, 2006 at 06:23:51PM -0700, Lu, Yinghai wrote: > The BIOSSavior only have 512k. So you need to make sure the linuxbios image is > 512k. Just to clarify, that is 512 KB (kilybytes), as in 4Mbit. I think there was a report to the list a while back that the mainboard *does* work with LinuxBIOS. Ward. -- Pong.be -( Writing software is more fun than working. )- Virtual hosting -( )- http://pong.be -( )- GnuPG public key: http://gpg.dtype.org From rminnich at lanl.gov Thu Jun 8 16:30:29 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Thu, 08 Jun 2006 08:30:29 -0600 Subject: [LinuxBIOS] Tyan ThunderK8SRE In-Reply-To: <20060608114539.GA16526@localdomain> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FBE@ssvlexmb2.amd.com> <20060608114539.GA16526@localdomain> Message-ID: <44883485.80601@lanl.gov> Ward Vandewege wrote: > On Wed, Jun 07, 2006 at 06:23:51PM -0700, Lu, Yinghai wrote: > >>The BIOSSavior only have 512k. So you need to make sure the linuxbios image is >>512k. > > > Just to clarify, that is 512 KB (kilybytes), as in 4Mbit. > > I think there was a report to the list a while back that the mainboard *does* > work with LinuxBIOS. if somebody wants to send an lspci we can see what it is similar to. ron From dhendrix at google.com Thu Jun 8 18:48:03 2006 From: dhendrix at google.com (David Hendricks) Date: Thu, 8 Jun 2006 09:48:03 -0700 Subject: [LinuxBIOS] Tyan ThunderK8SRE In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FBE@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FBE@ssvlexmb2.amd.com> Message-ID: Can he use the 8Mbit ROM that comes with the motherboard with a BIOS Savior? Or will he need to purchase another 4Mbit ROM separately? I've never mixed ROMs of different size with a BIOS Savior... On 6/7/06, Lu, Yinghai wrote: > > The BIOSSavior only have 512k. So you need to make sure the linuxbios > image is 512k. > > > > YH > ------------------------------ > > *From:* linuxbios-bounces at linuxbios.org [mailto: > linuxbios-bounces at linuxbios.org] *On Behalf Of *Arturo Mann > *Sent:* Wednesday, June 07, 2006 5:17 PM > *To:* linuxbios at linuxbios.org > *Subject:* [LinuxBIOS] Tyan ThunderK8SRE > > > > Hello there, > I'm building a new server, based around a Tyan Thunder K8SRE (S2891). The > specs claim it's using > an 8MiB flash chip for Phoneix Bios. > I would very much like to use LinuxBios to make the booting much easier > for me. (After the initial turmoil) > So, my question is, does anyone know which BiosSaviour will work with such > a Flash /Bios / Mainboard combo? > > Thanks, > Cheers, > > > -- > ------------------------ > Arturo Mann, arturo.mann at gmail.com > > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Thu Jun 8 19:29:26 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Thu, 8 Jun 2006 10:29:26 -0700 Subject: [LinuxBIOS] Tyan ThunderK8SRE Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FC2@ssvlexmb2.amd.com> Yes. he can. But for safe he could get extra PMB 512Kbytes flash. YH ________________________________ From: linuxbios-bounces at linuxbios.org [mailto:linuxbios-bounces at linuxbios.org] On Behalf Of David Hendricks Sent: Thursday, June 08, 2006 9:48 AM To: linuxbios at linuxbios.org Subject: Re: [LinuxBIOS] Tyan ThunderK8SRE Can he use the 8Mbit ROM that comes with the motherboard with a BIOS Savior? Or will he need to purchase another 4Mbit ROM separately? I've never mixed ROMs of different size with a BIOS Savior... On 6/7/06, Lu, Yinghai wrote: The BIOSSavior only have 512k. So you need to make sure the linuxbios image is 512k. YH ________________________________ From: linuxbios-bounces at linuxbios.org [mailto: linuxbios-bounces at linuxbios.org ] On Behalf Of Arturo Mann Sent: Wednesday, June 07, 2006 5:17 PM To: linuxbios at linuxbios.org Subject: [LinuxBIOS] Tyan ThunderK8SRE Hello there, I'm building a new server, based around a Tyan Thunder K8SRE (S2891). The specs claim it's using an 8MiB flash chip for Phoneix Bios. I would very much like to use LinuxBios to make the booting much easier for me. (After the initial turmoil) So, my question is, does anyone know which BiosSaviour will work with such a Flash /Bios / Mainboard combo? Thanks, Cheers, -- ------------------------ Arturo Mann, arturo.mann at gmail.com -- linuxbios mailing list linuxbios at linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: From russ at ashlandhome.net Fri Jun 9 06:36:56 2006 From: russ at ashlandhome.net (Russell Whitaker) Date: Thu, 8 Jun 2006 21:36:56 -0700 (PDT) Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060601091409.M98965@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> Message-ID: 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 From stepan at coresystems.de Fri Jun 9 11:47:10 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 9 Jun 2006 11:47:10 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060607064759.M97696@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <20060601221641.GA11315@coresystems.de> <20060605122738.M78729@mellander.org> <20060605160220.GA18023@coresystems.de> <20060606064645.M73489@mellander.org> <20060606114548.GA20687@coresystems.de> <20060607064759.M97696@mellander.org> Message-ID: <20060609094710.GA13797@coresystems.de> * Per Mellander [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? -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From smithbone at gmail.com Fri Jun 9 16:46:47 2006 From: smithbone at gmail.com (Richard Smith) Date: Fri, 9 Jun 2006 09:46:47 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> Message-ID: <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> > 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. -- Richard A. Smith From rminnich at gmail.com Sat Jun 10 18:11:28 2006 From: rminnich at gmail.com (ron minnich) Date: Sat, 10 Jun 2006 10:11:28 -0600 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> Message-ID: <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tylerapohl at gmail.com Mon Jun 12 09:45:00 2006 From: tylerapohl at gmail.com (Tyler Pohl) Date: Mon, 12 Jun 2006 00:45:00 -0700 Subject: [LinuxBIOS] bochs and qemu Message-ID: <503ab0210606120045h7cc7e791i3a26f9b6d85edbc0@mail.gmail.com> Where could i download a linuxbios.bin file that runs with qemu? Maybe even find some documentation on how to compie the linuxbios to run under qemu. Thanks Again :) Tyler -------------- next part -------------- An HTML attachment was scrubbed... URL: From per at mellander.org Mon Jun 12 13:55:41 2006 From: per at mellander.org (Per Mellander) Date: Mon, 12 Jun 2006 13:55:41 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> Message-ID: <20060612114421.M22682@mellander.org> On Sat, 10 Jun 2006 10:11:28 -0600, ron minnich wrote > 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. Tried with a pure i386-kernel, same result :( > 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. It works alright! Has been running it from day one ;) > 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. 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. > 4) 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? > 5) 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 at mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006 Press for default boot, or 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 at mm.int.mmtab.se) #4 Mon Jun 12 10:46:16 CEST 2006... Jumping to entry point... 0 --8<----------------------------- > 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) I'd love to, as soon as I can get the kernel to load at all. > 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. [root at 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 at 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 From fourstar10_2000 at yahoo.com Mon Jun 12 17:34:07 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Mon, 12 Jun 2006 08:34:07 -0700 (PDT) Subject: [LinuxBIOS] INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} Message-ID: <20060612153407.9550.qmail@web38910.mail.mud.yahoo.com> Reset... reset... where am I going wrong? Any Ideas? ----------------------------------------------------------------- boot: hda1:/boot/memtest86/memtest.bin malloc_diag: alloc: 424 bytes (5 blocks), free: 15952 bytes (1 blocks) malloc_diag: alloc: 440 bytes (6 blocks), free: 15936 bytes (1 blocks) file_open: dev=hda1, path=/boot/memtest86/memtest.bin devopen: already open malloc_diag: alloc: 424 bytes (5 blocks), free: 15952 bytes (1 blocks) elf_load: Not a bootable ELF image malloc_diag: alloc: 440 bytes (6 blocks), free: 15936 bytes (1 blocks) file_open: dev=hda1, path=/boot/memtest86/memtest.bin devopen: already open malloc_diag: alloc: 424 bytes (5 blocks), free: 15952 bytes (1 blocks) Possible very old Linux (protocol 0x0) zImage or Image. init_linux_params: Setting up paramters at 0x90000 set_memory_size: 0000000000000e10 - 00000000000a0000 set_memory_size: 00000000000c0000 - 00000000000f0000 set_memory_size: 00000000000f0400 - 0000000040000000 set_memory_size: ramtop=0x40000000 set_memory_size: ext_mem_k=64512, alt_mem_k=1047552 load_linux_kernel: offset=0xa00 addr=0x1000 size=0x156b4 Loading kernel... ok start_linux: eip=0x1000 Jumping to entry point... INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} --- Issuing SOFT_RESET... -------------------------------------------------------------------------------------------- hda1:/boot/memtest86/memtest.bin console=tty0 console=ttyS0,115200 = SAME -------------------------------------------------------------------------------------------- hda1:/boot/vmlinuz console=tty0 console=ttyS0,115200n8 = SAME -------------------------------------------------------------------------------------------- vmlinuz has "serial console" built in memory is detected OK all devices seem to be detected OK ----- FULL PRINTOUT FOLLOWS ------------------------------------------- LinuxBIOS-1.1.8_mb06047_Fallback Mon Jun 12 11:13:35 EDT 2006 starting... 01 nodes initialized. SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfd44 testx = 5a5a5a5a Copying data from cache to ram -- switching to use ram as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to ram. src=fffe0004 dst=00004000 linxbios_ram.bin length = 000225d0 Jumping to LinuxBIOS. LinuxBIOS-1.1.8_mb06047_Fallback Mon Jun 12 11:13:35 EDT 2006 booting... ----------------->Enumerating buses... APIC_CLUSTER: 0 enabled PCI_DOMAIN: 0000 enabled PCI: 00:18.3 siblings=1 CPU: APIC: 00 enabled CPU: APIC: 01 enabled PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] enabled PCI: 00:00.0 [10de/005e] enabled PCI: 00:00.0 [10de/005e] enabled next_unitid: 000f PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [10de/005e] enabled PCI: 00:01.0 [10de/0051] enabled PCI: 00:01.1 [10de/0052] enabled PCI: 00:02.0 [10de/005a] enabled PCI: 00:02.1 [10de/005b] enabled PCI: 00:04.0 [10de/0059] disabled PCI: 00:04.1 [10de/0058] disabled PCI: 00:06.0 [10de/0053] enabled PCI: 00:07.0 [10de/0054] enabled PCI: 00:08.0 [10de/0055] enabled PCI: 00:09.0 [10de/005c] enabled PCI: 00:0a.0 [10de/0056] enabled PCI: 00:0b.0 [10de/005d] enabled PCI: 00:0c.0 [10de/005d] enabled PCI: 00:0d.0 [10de/005d] enabled PCI: 00:0e.0 [10de/005d] enabled PNP: 002e.0 disabled PNP: 002e.1 disabled PNP: 002e.2 enabled PNP: 002e.3 disabled PNP: 002e.5 enabled PNP: 002e.6 disabled PNP: 002e.7 disabled PNP: 002e.8 enabled PNP: 002e.9 enabled PNP: 002e.a enabled PNP: 002e.b enabled smbus: PCI: 00:01.1[0]->I2C: 01:50 enabled smbus: PCI: 00:01.1[0]->I2C: 01:51 enabled smbus: PCI: 00:01.1[0]->I2C: 01:52 enabled smbus: PCI: 00:01.1[0]->I2C: 01:53 enabled smbus: PCI: 00:01.1[0]->I2C: 01:54 enabled smbus: PCI: 00:01.1[0]->I2C: 01:55 enabled smbus: PCI: 00:01.1[0]->I2C: 01:56 enabled smbus: PCI: 00:01.1[0]->I2C: 01:57 enabled ck804_pci_scan_bridge PCI: pci_scan_bus for bus 1 PCI: 01:06.0 [126f/0720] 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 PCI: pci_scan_bus for bus 4 PCI: 04:00.0 [11ab/4360] enabled PCI: pci_scan_bus returning with max=04 PCI: pci_scan_bus for bus 5 PCI: pci_scan_bus returning with max=05 PCI: pci_scan_bus returning with max=05 PCI: pci_scan_bus returning with max=05 done ---->Analyzing resources... -------->Reading resources... PNP: 002e.8 missing read_resources PNP: 002e.9 missing read_resources PCI: 00:09.0 1c <- [0x000000f000 - 0x000000efff] bus 1 io PCI: 00:09.0 24 <- [0x00fff00000 - 0x00ffefffff] bus 1 prefmem PCI: 00:0b.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 2 io PCI: 00:0b.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 2 prefmem PCI: 00:0b.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 2 mem PCI: 00:0c.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 3 io PCI: 00:0c.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 3 prefmem PCI: 00:0c.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 3 mem PCI: 00:0d.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 4 prefmem PCI: 00:0e.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 5 io PCI: 00:0e.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 5 prefmem PCI: 00:0e.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 5 mem <--------Done reading resources. PCI: 01:06.0 <---- VGA PCI: 00:09.0 <-------- Setting PCI_BRIDGE_CTL_VGA PCI: 00:18.0 <-------- Setting PCI_BRIDGE_CTL_VGA PCI_DOMAIN: 0000 <-------- Setting PCI_BRIDGE_CTL_VGA Root Device <-------- Setting PCI_BRIDGE_CTL_VGA PCI: 01:06.0 <----VGA END ------------>Setting resources... VGA: PCI: 00:18.0 (aka node 0) link 0 has VGA device PCI: 00:18.0 1d8 <- [0x0000001000 - 0x0000003fff] io PCI: 00:18.0 1b8 <- [0x00fc000000 - 0x00fbffffff] prefmem PCI: 00:18.0 1b0 <- [0x00f0000000 - 0x00f41fffff] mem PCI: 00:01.0 10 <- [0x0000002c00 - 0x0000002c7f] io PCI: 00:01.0 14 <- [0x00f4100000 - 0x00f4100fff] mem PCI: 00:01.0 60 <- [0x0000002000 - 0x00000020ff] io PCI: 00:01.0 64 <- [0x0000002400 - 0x00000024ff] io PCI: 00:01.0 68 <- [0x0000002800 - 0x00000028ff] io PNP: 002e.2 60 <- [0x00000003f8 - 0x00000003ff] io PNP: 002e.2 70 <- [0x0000000004 - 0x0000000004] irq PNP: 002e.5 60 <- [0x0000000060 - 0x0000000060] io PNP: 002e.5 62 <- [0x0000000064 - 0x0000000064] io PNP: 002e.5 70 <- [0x0000000001 - 0x0000000001] irq PNP: 002e.5 72 <- [0x000000000c - 0x000000000c] irq ERROR: PNP: 002e.a 70 irq size: 0x0000000001 not assigned PNP: 002e.b 60 <- [0x0000000290 - 0x0000000297] io PNP: 002e.b 70 <- [0x0000000005 - 0x0000000005] irq PCI: 00:01.1 10 <- [0x0000003000 - 0x000000301f] io PCI: 00:01.1 20 <- [0x0000002c80 - 0x0000002cbf] io PCI: 00:01.1 24 <- [0x0000002cc0 - 0x0000002cff] io PCI: 00:02.0 10 <- [0x00f4101000 - 0x00f4101fff] mem PCI: 00:02.1 10 <- [0x00f4105000 - 0x00f41050ff] mem PCI: 00:06.0 20 <- [0x0000003020 - 0x000000302f] io PCI: 00:07.0 10 <- [0x0000003050 - 0x0000003057] io PCI: 00:07.0 14 <- [0x00000030a0 - 0x00000030a3] io PCI: 00:07.0 18 <- [0x0000003060 - 0x0000003067] io PCI: 00:07.0 1c <- [0x00000030b0 - 0x00000030b3] io PCI: 00:07.0 20 <- [0x0000003030 - 0x000000303f] io PCI: 00:07.0 24 <- [0x00f4102000 - 0x00f4102fff] mem PCI: 00:08.0 10 <- [0x0000003070 - 0x0000003077] io PCI: 00:08.0 14 <- [0x00000030c0 - 0x00000030c3] io PCI: 00:08.0 18 <- [0x0000003080 - 0x0000003087] io PCI: 00:08.0 1c <- [0x00000030d0 - 0x00000030d3] io PCI: 00:08.0 20 <- [0x0000003040 - 0x000000304f] io PCI: 00:08.0 24 <- [0x00f4103000 - 0x00f4103fff] mem PCI: 00:09.0 20 <- [0x00f0000000 - 0x00f3ffffff] bus 1 mem PCI: 01:06.0 10 <- [0x00f0000000 - 0x00f3ffffff] mem PCI: 00:0a.0 10 <- [0x00f4104000 - 0x00f4104fff] mem PCI: 00:0a.0 14 <- [0x0000003090 - 0x0000003097] io PCI: 00:0d.0 1c <- [0x0000001000 - 0x0000001fff] bus 4 io PCI: 00:0d.0 20 <- [0x00f4000000 - 0x00f40fffff] bus 4 mem PCI: 04:00.0 10 <- [0x00f4020000 - 0x00f4023fff] mem64 PCI: 04:00.0 18 <- [0x0000001000 - 0x00000010ff] io PCI: 04:00.0 30 <- [0x00f4000000 - 0x00f401ffff] romem PCI: 00:18.3 94 <- [0x00f8000000 - 0x00fbffffff] mem <------------Done setting resources. <----Done allocating resources. ---->Enabling resources... PCI: 00:18.0 cmd <- 140 PCI: 00:00.0 cmd <- 146 PCI: 00:01.0 cmd <- 14f ck804 lpc decode:PNP: 002e.2, base=0x000003f8, end=0x000003ff ck804 lpc decode:PNP: 002e.5, base=0x00000060, end=0x00000060 ck804 lpc decode:PNP: 002e.5, base=0x00000064, end=0x00000064 PNP: 002e.8 missing enable_resources PNP: 002e.9 missing enable_resources ck804 lpc decode:PNP: 002e.b, base=0x00000290, end=0x00000297 PCI: 00:01.1 cmd <- 141 PCI: 00:02.0 cmd <- 142 PCI: 00:02.1 cmd <- 142 PCI: 00:06.0 cmd <- 141 PCI: 00:07.0 cmd <- 143 PCI: 00:08.0 cmd <- 143 PCI: 00:09.0 bridge ctrl <- 000b PCI: 00:09.0 cmd <- 147 PCI: 01:06.0 cmd <- 143 PCI: 00:0a.0 cmd <- 143 PCI: 00:0b.0 bridge ctrl <- 0003 PCI: 00:0b.0 cmd <- 140 PCI: 00:0c.0 bridge ctrl <- 0003 PCI: 00:0c.0 cmd <- 140 PCI: 00:0d.0 bridge ctrl <- 0003 PCI: 00:0d.0 cmd <- 147 PCI: 04:00.0 cmd <- 143 PCI: 00:0e.0 bridge ctrl <- 0003 PCI: 00:0e.0 cmd <- 140 PCI: 00:18.1 cmd <- 140 PCI: 00:18.2 cmd <- 140 PCI: 00:18.3 cmd <- 140 <----Done Enabling Resources. ---->Initializing devices... Root Device init APIC_CLUSTER: 0 init Initializing CPU #0 CPU: vendor AMD device 20f12 Enabling cache Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB, RdMEM, WrMEM Setting fixed MTRRs(24-88) Type: WB, RdMEM, WrMEM DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 1024MB, type WB DONE variable MTRRs Clear out the extra MTRR's MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled microcode: equivalent processor rev id = 0x0210, patch id = 0x00000000 microcode: patch id that want to apply= 0x0000004d microcode: updated to patch id = 0x0000004d success Setting up local apic... apic_id: 0 done. Clearing memory 2048K - 1048576K: --------------- done CPU #0 Initialized start_eip=0x00019000 Initializing CPU #1 Waiting for 1 CPUS to stop CPU: vendor AMD device 20f12 Enabling cache Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB, RdMEM, WrMEM Setting fixed MTRRs(24-88) Type: WB, RdMEM, WrMEM DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 1024MB, type WB DONE variable MTRRs Clear out the extra MTRR's MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled microcode: equivalent processor rev id = 0x0210, patch id = 0x00000000 microcode: patch id that want to apply= 0x0000004d microcode: updated to patch id = 0x0000004d success Setting up local apic... apic_id: 1 done. CPU #1 Initialized All AP CPUs stopped PCI: 00:18.0 init PCI: 00:01.0 init set power on after power fail RTC Init Invalid CMOS LB checksum PNP: 002e.2 init PNP: 002e.5 init PNP: 002e.a init PNP: 002e.b init PCI: 00:02.1 init PCI: 00:06.0 init IDE0 PCI: 00:07.0 init SATA S SATA P PCI: 00:08.0 init SATA S SATA P PCI: 00:09.0 init dev_root mem base = 0x00f0000000 [0x50] <-- 0xf0000000 PCI: 00:0a.0 init PCI: 00:0b.0 init PCI: 00:0c.0 init PCI: 00:0d.0 init PCI: 00:0e.0 init PCI: 00:18.1 init PCI: 00:18.2 init PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 01:06.0 init PCI: 04:00.0 init rom address for PCI: 04:00.0 = f4000000 Incorrect Expansion ROM Header Signature ffff <----Done initializing resources Writing IRQ routing tables to 0xf0000...done. Wrote the mp table end at: 00000020 - 000001b4 Moving GDT to 0x500...ok Wrote linuxbios table at: 00000530 - 00000dbc checksum 6b88 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 32:stream_init() - rom_stream: 0xfffc0000 - 0xfffdffff Found ELF candiate at offset 0 New segment addr 0x100000 size 0x41e00 offset 0xe0 filesize 0x17fe8 (cleaned up) New segment addr 0x100000 size 0x41e00 offset 0xe0 filesize 0x17fe8 New segment addr 0x141e00 size 0x48 offset 0x180e0 filesize 0x48 (cleaned up) New segment addr 0x141e00 size 0x48 offset 0x180e0 filesize 0x48 Dropping non PT_LOAD segment Dropping non PT_LOAD segment Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000041e00 filesz: 0x0000000000017fe8 Clearing Segment: addr: 0x0000000000117fe8 memsz: 0x0000000000029e18 Loading Segment: addr: 0x0000000000141e00 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x1112d0 FILO version 0.5 (root at localhost) Fri Jun 9 14:38:13 EDT 2006 collect_sys_info: boot eax = 0xe1fb007 collect_sys_info: boot ebx = 0x3ffef640 collect_sys_info: boot arg = 0x3ffef640 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 0x00000000000e10 16 convert_memmap: 0x00000000000e10 0x0000000009f1f0 1 convert_memmap: 0x000000000c0000 0x00000000030000 1 convert_memmap: 0x000000000f0000 0x00000000000400 16 convert_memmap: 0x000000000f0400 0x0000003ff0fc00 1 collect_sys_info: 0000000000000e10-00000000000a0000 collect_sys_info: 00000000000c0000-00000000000f0000 collect_sys_info: 00000000000f0400-0000000040000000 collect_sys_info: RAM 1024 MB relocate: Current location: 0x100000-0x141e47 relocate: Relocating to 0x3ffbe1b0-0x3ffffff7... ok setup_timers: CPU 1809 MHz pci_init: Scanning PCI: found 20 devices malloc_diag: alloc: 376 bytes (4 blocks), free: 16000 bytes (1 blocks) pci_init: 00:00.0 10de:005e 0580 00 pci_init: 00:01.0 10de:0051 0601 00 pci_init: 00:01.1 10de:0052 0c05 00 pci_init: 00:02.0 10de:005a 0c03 10 pci_init: 00:02.1 10de:005b 0c03 20 pci_init: 00:06.0 10de:0053 0101 8a pci_init: 00:07.0 10de:0054 0101 85 pci_init: 00:08.0 10de:0055 0101 85 pci_init: 00:09.0 10de:005c 0604 01 pci_init: 00:0a.0 10de:0056 0200 00 pci_init: 00:0b.0 10de:005d 0604 00 pci_init: 00:0c.0 10de:005d 0604 00 pci_init: 00:0d.0 10de:005d 0604 00 pci_init: 00:0e.0 10de:005d 0604 00 pci_init: 00:18.0 1022:1100 0600 00 pci_init: 00:18.1 1022:1101 0600 00 pci_init: 00:18.2 1022:1102 0600 00 pci_init: 00:18.3 1022:1103 0600 00 pci_init: 01:06.0 126f:0720 0300 00 pci_init: 04:00.0 11ab:4360 0200 00 boot: hda1:/boot/vmlinuz console=tty0 console=ttyS0,115200n8 malloc_diag: alloc: 440 bytes (5 blocks), free: 15936 bytes (1 blocks) malloc_diag: alloc: 456 bytes (6 blocks), free: 15920 bytes (1 blocks) file_open: dev=hda1, path=/boot/vmlinuz find_ide_controller: found PCI IDE controller 10de:0053 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=1019088 init_drive: Init device params... ok hda: LBA 521MB: SILICONSYSTEMS INC 512MB init_drive: Testing for hdb init_drive: Testing for hdb devopen: Partition 1 start 59 length 1018989 Mounted ext2fs malloc_diag: alloc: 440 bytes (5 blocks), free: 15936 bytes (1 blocks) elf_load: Not a bootable ELF image malloc_diag: alloc: 456 bytes (6 blocks), free: 15920 bytes (1 blocks) file_open: dev=hda1, path=/boot/vmlinuz devopen: already open malloc_diag: alloc: 440 bytes (5 blocks), free: 15936 bytes (1 blocks) Found Linux version 2.6.15-gentoo-r7 (root at localhost) #4 SMP PREEMPT Thu May 25 07:32:06 EDT 2006 (protocol 0x204) (loadflags 0x1) bzImage. init_linux_params: Setting up paramters at 0x90000 set_memory_size: 0000000000000e10 - 00000000000a0000 set_memory_size: 00000000000c0000 - 00000000000f0000 set_memory_size: 00000000000f0400 - 0000000040000000 set_memory_size: ramtop=0x40000000 set_memory_size: ext_mem_k=64512, alt_mem_k=1047552 parse_command_line: original command line: "console=tty0 console=ttyS0,115200n8" parse_command_line: kernel command line at 0x91000 parse_command_line: kernel command line (35 bytes): "console=tty0 console=ttyS0,115200n8" load_linux_kernel: offset=0x1e00 addr=0x100000 size=0x1c37fa Loading kernel... ok start_linux: eip=0x100000 Jumping to entry point... INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} --- Thank You. Steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From per at mellander.org Mon Jun 12 19:53:17 2006 From: per at mellander.org (Per Mellander) Date: Mon, 12 Jun 2006 19:53:17 +0200 Subject: [LinuxBIOS] INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} In-Reply-To: <20060612153407.9550.qmail@web38910.mail.mud.yahoo.com> References: <20060612153407.9550.qmail@web38910.mail.mud.yahoo.com> Message-ID: <20060612175137.M86698@mellander.org> On Mon, 12 Jun 2006 08:34:07 -0700 (PDT), steve yannalfo wrote > Reset... reset... where am I going wrong? Any Ideas? > > ----------------------------------------------------------------- > boot: hda1:/boot/memtest86/memtest.bin > malloc_diag: alloc: 424 bytes (5 blocks), free: 15952 bytes (1 blocks) > malloc_diag: alloc: 440 bytes (6 blocks), free: 15936 bytes (1 blocks) > file_open: dev=hda1, path=/boot/memtest86/memtest.bin > devopen: already open > malloc_diag: alloc: 424 bytes (5 blocks), free: 15952 bytes (1 blocks) > elf_load: Not a bootable ELF image Use the 'memtest' ELF binary instead of memtest.bin /Per From fourstar10_2000 at yahoo.com Mon Jun 12 21:24:13 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Mon, 12 Jun 2006 12:24:13 -0700 (PDT) Subject: [LinuxBIOS] INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} Message-ID: <20060612192414.36921.qmail@web38908.mail.mud.yahoo.com> SAME Thanks for you help though... still working on this. The Docs say FILO can boot a regular kernel, bzImage, memtest, elf images etc... So I don't know why it was complaining about it not being an ELF. I just thought that was the default. Still same err though. ---------------------------------------------- boot: hda1:/boot/memtest86/memtest.elf console=tty0 console=ttyS0,115200n8 malloc_diag: alloc: 456 bytes (5 blocks), free: 15920 bytes (1 blocks) malloc_diag: alloc: 472 bytes (6 blocks), free: 15904 bytes (1 blocks) file_open: dev=hda1, path=/boot/memtest86/memtest.elf find_ide_controller: found PCI IDE controller 10de:0053 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=1019088 init_drive: Init device params... ok hda: LBA 521MB: SILICONSYSTEMS INC 512MB init_drive: Testing for hdb init_drive: Testing for hdb devopen: Partition 1 start 59 length 1018989 Mounted ext2fs malloc_diag: alloc: 456 bytes (5 blocks), free: 15920 bytes (1 blocks) malloc_diag: alloc: 528 bytes (6 blocks), free: 15848 bytes (1 blocks) Loading image... load_segments: segment 0 addr:0x10000 file:0x155f4 mem:0x155f4 loading... clearing... ok load_segments: Loaded 87540 bytes in 568ms (154KB/s) malloc_diag: alloc: 792 bytes (7 blocks), free: 15584 bytes (1 blocks) elf_load: current time: 36403 elf_load: entry point is 0x10000 Jumping to entry point... INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} --- Issuing SOFT_RESET... ------------------------------------------ Thank you steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Mon Jun 12 22:23:03 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Mon, 12 Jun 2006 14:23:03 -0600 Subject: [LinuxBIOS] bochs and qemu In-Reply-To: <503ab0210606120045h7cc7e791i3a26f9b6d85edbc0@mail.gmail.com> References: <503ab0210606120045h7cc7e791i3a26f9b6d85edbc0@mail.gmail.com> Message-ID: <448DCD27.80104@lanl.gov> Tyler Pohl wrote: > Where could i download a linuxbios.bin file that runs with qemu? Maybe > even find some documentation on how to compie the linuxbios to run under > qemu. Thanks Again :) > > Tyler > I believe qemu is a 440bx chipset emulation. I doubt you need to program memory timings much if at all ... should be pretty straightforward. thanks ron From smithbone at gmail.com Mon Jun 12 22:29:33 2006 From: smithbone at gmail.com (Richard Smith) Date: Mon, 12 Jun 2006 15:29:33 -0500 Subject: [LinuxBIOS] bochs and qemu In-Reply-To: <448DCD27.80104@lanl.gov> References: <503ab0210606120045h7cc7e791i3a26f9b6d85edbc0@mail.gmail.com> <448DCD27.80104@lanl.gov> Message-ID: <8a0c36780606121329n63764822y784e2c368cc900e3@mail.gmail.com> On 6/12/06, Ronald G Minnich wrote: > Tyler Pohl wrote: > > Where could i download a linuxbios.bin file that runs with qemu? Maybe > > even find some documentation on how to compie the linuxbios to run under > > qemu. Thanks Again :) > > > > Tyler > > > > I believe qemu is a 440bx chipset emulation. I doubt you need to program > memory timings much if at all ... should be pretty straightforward. > Yeah. Too bad the 440bx maintainer never got the 440bx stuff to work with V2. What a slacker. -- Richard A. Smith From stepan at coresystems.de Mon Jun 12 22:55:46 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Mon, 12 Jun 2006 22:55:46 +0200 Subject: [LinuxBIOS] bochs and qemu In-Reply-To: <448DCD27.80104@lanl.gov> References: <503ab0210606120045h7cc7e791i3a26f9b6d85edbc0@mail.gmail.com> <448DCD27.80104@lanl.gov> Message-ID: <20060612205545.GA7520@coresystems.de> * Ronald G Minnich [060612 22:23]: > Tyler Pohl wrote: > > Where could i download a linuxbios.bin file that runs with qemu? Maybe > > even find some documentation on how to compie the linuxbios to run under > > qemu. Thanks Again :) > > > > Tyler > > > > I believe qemu is a 440bx chipset emulation. I doubt you need to program > memory timings much if at all ... should be pretty straightforward. For x86/x86_64 there's a special target. Build LinuxBIOS for the emulation/qemu-i386 "mainboard". On qemu/sparc you should use OpenBIOS instead -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From scott at lubetech.com.au Tue Jun 13 03:05:10 2006 From: scott at lubetech.com.au (Scott) Date: Tue, 13 Jun 2006 11:05:10 +1000 Subject: [LinuxBIOS] EPIA-V8000 Message-ID: <000001c68e85$6b6789e0$2e0a800a@scottbedf9e644> Hi All, Is anyone aware of a rom image of V2 that is available for the Via EPIA-V8000 or an updated Tutorial on setting up V2 on this board? Thanks. From stepan at coresystems.de Tue Jun 13 03:55:12 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Tue, 13 Jun 2006 03:55:12 +0200 Subject: [LinuxBIOS] EPIA-V8000 In-Reply-To: <000001c68e85$6b6789e0$2e0a800a@scottbedf9e644> References: <000001c68e85$6b6789e0$2e0a800a@scottbedf9e644> Message-ID: <20060613015512.GA9557@coresystems.de> * Scott [060613 03:05]: > > Hi All, > Is anyone aware of a rom image of V2 that is available for the Via > EPIA-V8000 or an updated Tutorial on setting up V2 on this board? You should use the via/epia mainboard for this one. It features a PLE133 northbridge (which is the VT8601), and a VT8231 southbridge. You might find http://www.linuxbios.org/data/lbdoc/ or http://www.linuxbios.org/index.php/The_EPIA-M/MII useful, though both are for the Epia-M, not the Epia-V. We are very interested in getting a Howto (http://www.linuxbios.org/index.php/Documentation) So if you go down the road of trying LinuxBIOS on this board, please document what you do, while you do it (as people tend to forget what they did afterwards, which is why there are not many howtos) We're working on a method of providing precompiled, verified-working LinuxBIOS images on the LinuxBIOS website, but it's still in development. Important: Get yourself a serial null modem cable and a backup flash chip before starting, so you don't have to erase your factory bios before you make sure everything is working correctly. Stefan -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From wojciech.kromer at dgt.com.pl Tue Jun 13 09:04:01 2006 From: wojciech.kromer at dgt.com.pl (Wojciech Kromer) Date: Tue, 13 Jun 2006 09:04:01 +0200 Subject: [LinuxBIOS] VIA EPIA MII6000E Message-ID: <448E6361.9020600@dgt.com.pl> I've followed instuctions in EPIA-M-howto, but can't boot anything. How could I boot from cdrom now??? What is correct syntax in command line grub (filo-grub) LinuxBIOS-1.1.8.0Fallback pon cze 12 12:33:20 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 01 Total Memory (*16 Mb) 10 CAS Supported 2 2.5 3 Cycle time at CL X (nS)50 Cycle time at CL X-0.5 (nS)60 Cycle time at CL X-1 (nS)75 Starting at CAS 3 We can do CAS 2.5 We can do CAS 2 tRP 3c tRCD 3c tRAS 28 Low Bond 06 High Bondd0 Setting DQS delay8cvt8623 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 10 10 10 00 00 60:02 ff 00 30 52 32 01 20 42 2d 43 58 00 44 00 00 70:82 48 00 01 01 08 50 00 01 00 00 00 00 00 02 02 80:0f 61 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 80 00 00 00 a8 00 00 00 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 00 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 pon cze 12 12:33:20 CEST 2006 booting... clocks_per_usec: 941 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 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 0x40000 Kbytes PCI: 00:0a.0 In set resources PCI: 00:0a.0 10 <- [0x00febfb000 - 0x00febfbfff] mem PCI: 00:0a.0 2c <- [0x0000001870 - 0x000000286f] io PCI: 00:0a.0 34 <- [0x0000002870 - 0x000000386f] io PCI: 00:0a.0 1c <- [0x00f6bfb000 - 0x00f8bfafff] prefmem PCI: 00:0a.0 24 <- [0x00f8bfb000 - 0x00fabfafff] mem PCI: 00:0a.1 In set resources PCI: 00:0a.1 1 ==> febfc000 PCI: 00:0a.1 10 <- [0x00febfd000 - 0x00febfdfff] mem PCI: 00:0a.1 2c <- [0x0000003870 - 0x000000486f] io PCI: 00:0a.1 34 <- [0x0000004870 - 0x000000586f] io PCI: 00:0a.1 1c <- [0x00fabfb000 - 0x00fcbfafff] prefmem PCI: 00:0a.1 24 <- [0x00fcbfb000 - 0x00febfafff] mem PCI: 00:10.0 20 <- [0x0000001800 - 0x000000181f] io PCI: 00:10.1 20 <- [0x0000001820 - 0x000000183f] io PCI: 00:10.2 20 <- [0x0000001840 - 0x000000185f] 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 <- [0x0000001860 - 0x000000186f] 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: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 000111a0 setting firewire 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 ^^^^ why? any missconfiguration? 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 ^^^^ is it wrong ???? PCI: 00:11.5 init PCI: 00:12.0 init Configuring VIA Rhine LAN PCI: 00:0a.0 init rl5c476 init CF Base = febfc000 PCI: 00:0a.1 init rl5c476 init CF Base = febfc000 CF Config = 0 APIC_CLUSTER: 0 init Initializing CPU #0 CPU: vendor Centaur device 673 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: 128MB, type WB Setting variable MTRR 1, base: 128MB, range: 64MB, type WB Setting variable MTRR 2, base: 192MB, 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: 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 BAD SIGNATURE 0xb4 0x0 ^^^^^ why? I grab vide.bios.rom just as in howto, and changed everything... biosint: INT# 0x10 biosint: eax 0x4f14 ebx 0x18003 ecx 0x1 edx 0x0 biosint: ebp 0x17fa8 esp 0xffa edi 0x0 esi 0xffff7063 biosint: ip 0xbb85 cs 0x0 flags 0x46 BIOSINT: Unsupport int #0x10 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 3245 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 0x3ca40 offset 0xc0 filesize 0x12c48 (cleaned up) New segment addr 0x100000 size 0x3ca40 offset 0xc0 filesize 0x12c48New segment addr 0x13ca40 size 0x48 offset 0x12d20 filesize 0x48 (cleaned up) New segment addr 0x13ca40 size 0x48 offset 0x12d20 filesize 0x48 Dropping non PT_LOAD segment Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x000000000003ca40 filesz: 0x00Clearing Segment: addr: 0x0000000000112c48 memsz: 0x0000000000029df8 Loading Segment: addr: 0x000000000013ca40 memsz: 0x0000000000000048 filesz: 0x00Jumping to boot code at 0x10e408 FILO version 0.5 (krom at krom.bkir.dgt) pon cze 12 10:55:25 CEST 2006 menu: hda3:/boot/filo/menu.lst ^^^ this is my mistake, should be hde1:/boot/filo/menu.lst for CF but i want to boot anything now.... hda: ATAPI: HL-DT-ST DVDRAM GSA-4167B Waiting for drive to detect the medium... 50MB medium detected El-Torito entries other than Initial/Default is not supported Press any key to continue. ...... From per at mellander.org Tue Jun 13 15:12:38 2006 From: per at mellander.org (Per Mellander) Date: Tue, 13 Jun 2006 15:12:38 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060612114421.M22682@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> Message-ID: <20060613125600.M11621@mellander.org> 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 at 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 for default boot, or 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 at 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 From smithbone at gmail.com Tue Jun 13 16:41:35 2006 From: smithbone at gmail.com (Richard Smith) Date: Tue, 13 Jun 2006 09:41:35 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060613125600.M11621@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> Message-ID: <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> > 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. -- Richard A. Smith From fourstar10_2000 at yahoo.com Tue Jun 13 20:18:35 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Tue, 13 Jun 2006 11:18:35 -0700 (PDT) Subject: [LinuxBIOS] etherboot fails to compile for FILO Message-ID: <20060613181835.31205.qmail@web38907.mail.mud.yahoo.com> ld -m elf_i386 -N -T arch/i386/core/etherboot.lds -o bin/filo.elf.rt bin/elfprefix.exit.o bin/filo.rt.o bin/filo.rt.o: In function `install_pxe_stack': : undefined reference to `allot_base_memory' bin/filo.rt.o: In function `install_pxe_stack': : undefined reference to `e820mangler_size' bin/filo.rt.o: In function `install_pxe_stack': : undefined reference to `install_rm_callback_interface' bin/filo.rt.o: In function `install_pxe_stack': : undefined reference to `install_e820mangler' bin/filo.rt.o: In function `use_undi_ds_for_rm_stack': : undefined reference to `forget_real_mode_stack' bin/filo.rt.o: In function `hook_pxe_stack': : undefined reference to `hide_etherboot' bin/filo.rt.o: In function `unhook_pxe_stack': : undefined reference to `unhide_etherboot' bin/filo.rt.o: In function `remove_pxe_stack': : undefined reference to `forget_base_memory' bin/filo.rt.o: In function `pxenv_restart_tftp': : undefined reference to `get_free_base_memory' make: *** [bin/filo.elf.rt] Error 1 rm bin/elfprefix.entry.o bin/filo.rt.o bin/elfprefix.exit.o bin/filo.o ---------------------------------------------------------------------------------------------------- src/Config # Select which buses etherboot should support CFLAGS+= -DCONFIG_PCI CFLAGS+= -DCONFIG_ISA # CFLAGS+= -DCONFIG_PCMCIA # For prompting and default on timeout CFLAGS+= -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC # If you would like to attempt to boot from other devices as well as the network. # CFLAGS+= -DBOOT_SECOND=BOOT_FLOPPY # CFLAGS+= -DBOOT_THIRD=BOOT_DISK # CFLAGS+= -DBOOT_INDEX=0 # If you prefer the old style rotating bar progress display # CFLAGS+= -DBAR_PROGRESS # Show size indicator # CFLAGS+= -DSIZEINDICATOR # Enabling this creates non-standard images which use ports 1067 and 1068 # for DHCP/BOOTP # CFLAGS+= -DALTERNATE_DHCP_PORTS_1067_1068 # Enabling this makes the boot ROM require a Vendor Class Identifier # of "Etherboot" in the Vendor Encapsulated Options # This can be used to reject replies from servers other than the one # we want to give out addresses to us, but it will prevent Etherboot # from getting an IP lease until you have configured DHCPD correctly # CFLAGS+= -DREQUIRE_VCI_ETHERBOOT # EXPERIMENTAL! Set DHCP_CLIENT_ID to create a Client Identifier (DHCP # option 61, see RFC2132 section 9.14) when Etherboot sends the DHCP # DISCOVER and REQUEST packets. This ID must UNIQUELY identify each # client on your local network. Set DHCP_CLIENT_ID_TYPE to the # appropriate hardware type as described in RFC2132 / RFC1700; this # almost certainly means using '1' if the Client ID is an Ethernet MAC # address and '0' otherwise. Set DHCP_CLIENT_ID_LEN to the length of # the Client ID in octets (this is not a null terminated C string, do # NOT add 1 for a terminator and do NOT add an extra 1 for the # hardware type octet). Note that to identify your client using the # normal default MAC address of your NIC, you do NOT need to set this # option, as the MAC address is automatically used in the # hwtype/chaddr field; note also that this field only sets the DHCP # option: it does NOT change the MAC address used by the client. # CFLAGS+= -DDHCP_CLIENT_ID="'C','L','I','E','N','T','0','0','1'" \ # -DDHCP_CLIENT_ID_LEN=9 -DDHCP_CLIENT_ID_TYPE=0 # CFLAGS+= -DDHCP_CLIENT_ID="0xDE,0xAD,0xBE,0xEF,0xDE,0xAD" \ # -DDHCP_CLIENT_ID_LEN=6 -DDHCP_CLIENT_ID_TYPE=1 # EXPERIMENTAL! Set DHCP_USER_CLASS to create a User Class option (see # RFC3004) when Etherboot sends the DHCP DISCOVER and REQUEST packets. # This can be used for classification of clients, typically so that a # DHCP server can send an appropriately tailored reply. Normally, a # string identifies a class of to which this client instance belongs # which is useful in your network, such as a department ('FINANCE' or # 'MARKETING') or hardware type ('THINCLIENT' or 'KIOSK'). Set # DHCP_USER_CLASS_LEN to the length of DHCP_USER_CLASS in octets. # This is NOT a null terminated C string, do NOT add 1 for a # terminator. RFC3004 advises how to lay out multiple User Class # options by using an octet for the length of each string, as in this # example. It is, of course, up to the server to parse this. # CFLAGS+= -DDHCP_USER_CLASS="'T','E','S','T','C','L','A','S','S'" \ # -DDHCP_USER_CLASS_LEN=9 # CFLAGS+= -DDHCP_USER_CLASS="5,'A','L','P','H','A',4,'B','E','T','A'" \ # -DDHCP_USER_CLASS_LEN=11 # for btext console support # CFLAGS+= -DCONSOLE_BTEXT # for direct PC kbd support # CFLAGS+= -DCONSOLE_PC_KBD # Set to enable FILO support # for FILO support it will make main call pci_init INCLUDE_FILO=y ifdef INCLUDE_FILO CFLAGS+= -DCONFIG_FILO endif # Enabling this causes Etherboot to ignore Etherboot-specific options # that are not within an Etherboot encapsulated options field. # This option should be enabled unless you have a legacy DHCP server # configuration from the bad old days before the use of # encapsulated Etherboot options. CFLAGS+= -DALLOW_ONLY_ENCAPSULATED # Disable DHCP support # CFLAGS+= -DNO_DHCP_SUPPORT # Set to enable static boot information # CFLAGS+= -DUSE_STATIC_BOOT_INFO # Specify the static boot values # All must be specified, if -DUSE_STATIC_BOOT_INFO is defined # CFLAGS+= -DSTATIC_CLIENT_IP=\"192.168.25.25\" # CFLAGS+= -DSTATIC_SUBNET_MASK=\"255.255.255.0\" # CFLAGS+= -DSTATIC_SERVER_IP=\"192.168.25.101\" # CFLAGS+= -DSTATIC_GATEWAY_IP=\"192.168.25.1\" # CFLAGS+= -DSTATIC_BOOTFILE=\"tftp://192.168.25.101/pxelinux.0\" # Specify a default bootfile to be used if the DHCP server does not # provide the information. If you do not specify this option, then # DHCP offers that do not contain bootfiles will be ignored. # CFLAGS+= -DDEFAULT_BOOTFILE=\"tftp://192.168.1.254/lts/pxelinux.0\" # Exit if there is an error loading the boot file # CFLAGS+= -DEXIT_ON_FILE_LOAD_ERROR # Limit the delay on packet loss/congestion to a more bearable value. See # description above. If unset, do not limit the delay between resend. CFLAGS+= -DBACKOFF_LIMIT=7 -DCONGESTED # More optional features # CFLAGS+= -DTRY_FLOPPY_FIRST=4 # CFLAGS+= -DEXIT_IF_NO_OFFER # For a serial console, which can run in parallel with FIRMWARE console # CFLAGS+= -DCONSOLE_DUAL -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 # Enable tagged image, generic ELF, Multiboot ELF # or FreeBSD ELF/a.out boot image support CFLAGS+= -DTAGGED_IMAGE -DELF_IMAGE # CFLAGS+= -DAOUT_IMAGE -DIMAGE_MULTIBOOT -DIMAGE_FREEBSD # CFLAGS+= -DAOUT_IMAGE -DAOUT_LYNX_KDI # CFLAGS+= -DCOFF_IMAGE # CFLAGS+= -DRAW_IMAGE # Download files via TFTP CFLAGS+= -DDOWNLOAD_PROTO_TFTP # FSP support # CFLAGS+= -DDOWNLOAD_PROTO_FSP -DDEFAULT_PROTO_FSP # Change download protocol to NFS, default is TFTP # CFLAGS+= -DDOWNLOAD_PROTO_NFS # Change download protocol to HTTP, default is TFTP # CFLAGS+= -DDOWNLOAD_PROTO_HTTP # Change default protocol to NFS # CFLAGS+= -DDEFAULT_PROTO_NFS # Support to resolve hostnames in boot filename # CFLAGS+= -DDNS_RESOLVER # Multicast Support # CFLAGS+= -DALLMULTI -DMULTICAST_LEVEL1 -DMULTICAST_LEVEL2 -DDOWNLOAD_PROTO_TFTM # Etherboot as a PXE network protocol ROM # (Requires TFTP protocol support) CFLAGS+= -DPXE_IMAGE -DPXE_EXPORT # Etherboot stricter as a PXE network protocol ROM # CFLAGS+= -DPXE_DHCP_STRICT # Support for PXE emulation. Works only with FreeBSD to load the kernel # via pxeboot, use only with DOWNLOAD_PROTO_NFS # CFLAGS+= -DFREEBSD_PXEEMU # Include an auto-incrementing build serial number and optional build # ID string # CFLAGS+= -DBUILD_SERIAL # CFLAGS+= -DBUILD_SERIAL -DBUILD_ID=\"testing\" # Do not relocate # core/relocate.c should really be moved to an arch specific directory # but this is here for archs that don't support relocation # CFLAGS+= -DNORELOCATE # you should normally not need to change these HOST_CC= gcc CPP= gcc -E -Wp,-Wall RM= rm -f TOUCH= touch PERL= /usr/bin/perl CC= gcc AS= as LD= ld SIZE= size AR= ar RANLIB= ranlib OBJCOPY= objcopy CFLAGS+= -Os -ffreestanding CFLAGS+= -Wall -W -Wno-format CFLAGS+= $(EXTRA_CFLAGS) ASFLAGS+= $(EXTRA_ASFLAGS) LDFLAGS+= $(EXTRA_LDFLAGS) # For debugging # LDFLAGS+= -Map $@.map # Location to place generated binaries, and files BIN=bin ----------------------------------------------------------------------------- arch/i386/Confi # BIOS select don't change unless you know what you are doing #CFLAGS+= -DPCBIOS # Compile in k8/hammer support CFLAGS+= -DCONFIG_X86_64 # Options to make a version of Etherboot that will work under linuxBIOS. CFLAGS+= -DLINUXBIOS CFLAGS+= -DCONFIG_TSC_CURRTICKS CFLAGS+= -DCONSOLE_SERIAL CFLAGS+= -DCOMCONSOLE=0x3f8 CFLAGS+= -DCOMPRESERVE CFLAGS+= -DCONFIG_PCI_DIRECT CFLAGS+= -DELF_IMAGE CFLAGS+= -DCONSOLE_DIRECT_VGA # These options affect the loader that is prepended to the Etherboot image # LCONFIG+= -DBBS_BUT_NOT_PNP_COMPLIANT # LCONFIG+= -DBOOT_INT18H # Produce code that will work inside the Bochs emulator. The pnic # driver is probably the best one to try. CFLAGS+= -DCONFIG_PCI_DIRECT # Produce code that will work with OpenBSD's pxeboot #CFLAGS+= -DFLATTEN_REAL_MODE CFLAGS+= -fstrength-reduce -fomit-frame-pointer -march=i386 # Squeeze the code in as little space as possible. # gcc3 needs a different syntax to gcc2 if you want to avoid spurious warnings. GCC_VERSION = $(subst ., ,$(shell $(CC) -dumpversion)) GCC_MAJORVERSION = $(firstword $(GCC_VERSION)) ifeq ($(GCC_MAJORVERSION),2) CFLAGS+= -malign-jumps=1 -malign-loops=1 -malign-functions=1 else CFLAGS+= -falign-jumps=1 -falign-loops=1 -falign-functions=1 endif GCC_MINORVERSION = $(word 2, $(GCC_VERSION)) ifneq ($(GCC_MINORVERSION),4) CFLAGS+= -march=i386 endif LDFLAGS+= -N ifeq "$(shell uname -s)" "FreeBSD" CFLAGS+= -DIMAGE_FREEBSD -DELF_IMAGE -DAOUT_IMAGE endif # An alternate location for isolinux.bin can be set here # ISOLINUX_BIN=/path/to/isolinux.bin ----------------------------------------------------------------------------------- filo/Config #AUTOBOOT_FILE = "hda3:/boot/vmlinuz root=/dev/hda3 console=tty0 console=ttyS0,115200" AUTOBOOT_FILE = "hda2:/boot/vmlinuz initrd=/boot/initrd pci=noacpi ro root=/dev/hda2 console=tty0 console=ttyS0,115200" #AUTOBOOT_FILE = "mem at 0xfff80000" #AUTOBOOT_FILE = "hde1 at 0" #AUTOBOOT_FILE = "uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf" #AUTOBOOT_FILE = "hda5:/boot/vmlinuz initrd=/boot/initrd ro root=/dev/hda7 console=tty0 console=ttyS0,115200" # Time in second before booting AUTOBOOT_FILE AUTOBOOT_DELAY = 2 # Driver for hard disk, CompactFlash, and CD-ROM on IDE bus IDE_DISK = 1 # Driver for USB disk USB_DISK = 1 # Filesystems # To make filo.zelf < 32 k, You may not enable JFS, MINIX, XFS # Is anyone still using these file system? BY LYH FSYS_EXT2FS = 1 FSYS_FAT = 1 #FSYS_JFS = 1 #FSYS_MINIX = 1 FSYS_REISERFS = 1 #FSYS_XFS = 1 FSYS_ISO9660 = 1 # Support for boot disk image in bootable CD-ROM (El Torito) ELTORITO = 1 # PCI support SUPPORT_PCI = 1 # Debugging #DEBUG_ALL = 1 #DEBUG_ELFBOOT = 1 #DEBUG_ELFNOTE = 1 #DEBUG_LINUXBIOS = 1 #DEBUG_MALLOC = 1 #DEBUG_MULTIBOOT = 1 #DEBUG_SEGMENT = 1 #DEBUG_SYS_INFO = 1 #DEBUG_TIMER = 1 #DEBUG_BLOCKDEV = 1 #DEBUG_PCI = 1 #DEBUG_LINUXLOAD = 1 #DEBUG_IDE = 1 #DEBUG_USB = 1 #DEBUG_ELTORITO = 1 # i386 options # Loader for standard Linux kernel image, a.k.a. /vmlinuz LINUX_LOADER = 1 # Boot FILO from Multiboot loader (eg. GRUB) # You need to modify i386/multiboot.c to use it. change mmrange to e820entries. # By LYH #MULTIBOOT_IMAGE = 1 # Use PCI Configuration Mechanism #1 (most boards) PCI_CONFIG_1 = 1 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From stepan at coresystems.de Tue Jun 13 20:29:37 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Tue, 13 Jun 2006 20:29:37 +0200 Subject: [LinuxBIOS] etherboot fails to compile for FILO In-Reply-To: <20060613181835.31205.qmail@web38907.mail.mud.yahoo.com> References: <20060613181835.31205.qmail@web38907.mail.mud.yahoo.com> Message-ID: <20060613182937.GA10538@coresystems.de> * steve yannalfo [060613 20:18]: > ld -m elf_i386 -N -T arch/i386/core/etherboot.lds -o bin/filo.elf.rt bin/ > elfprefix.exit.o bin/filo.rt.o > bin/filo.rt.o: In function `install_pxe_stack': > : undefined reference to `allot_base_memory' > bin/filo.rt.o: In function `install_pxe_stack': > : undefined reference to `e820mangler_size' > bin/filo.rt.o: In function `install_pxe_stack': > : undefined reference to `install_rm_callback_interface' > bin/filo.rt.o: In function `install_pxe_stack': > : undefined reference to `install_e820mangler' > bin/filo.rt.o: In function `use_undi_ds_for_rm_stack': > : undefined reference to `forget_real_mode_stack' > bin/filo.rt.o: In function `hook_pxe_stack': > : undefined reference to `hide_etherboot' > bin/filo.rt.o: In function `unhook_pxe_stack': > : undefined reference to `unhide_etherboot' > bin/filo.rt.o: In function `remove_pxe_stack': > : undefined reference to `forget_base_memory' > bin/filo.rt.o: In function `pxenv_restart_tftp': > : undefined reference to `get_free_base_memory' > make: *** [bin/filo.elf.rt] Error 1 > rm bin/elfprefix.entry.o bin/filo.rt.o bin/elfprefix.exit.o bin/filo.o > ---------------------------------------------------------------------------------------------------- Comment out this line: CFLAGS+= -DPXE_IMAGE -DPXE_EXPORT Stefan -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From fourstar10_2000 at yahoo.com Tue Jun 13 20:53:42 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Tue, 13 Jun 2006 11:53:42 -0700 (PDT) Subject: [LinuxBIOS] etherboot fails to compile for FILO Message-ID: <20060613185342.59645.qmail@web38901.mail.mud.yahoo.com> Same Problem: cc -DCONFIG_PCI -DCONFIG_ISA -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DCONFIG_FILO -DALLOW_ONLY_ENCAPSULATED -DBACKOFF_LIMIT=7 -DCONGESTED -DTAGGED_IMAGE -DELF_IMAGE -DDOWNLOAD_PROTO_TFTP -Os In file included from arch/i386/core/realmode.c:7: arch/i386/include/realmode.h:119: error: static declaration of 'allot_real_mode_stack' follows non-static declaration include/etherboot.h:330: error: previous declaration of 'allot_real_mode_stack' was here make: *** [bin/realmode.o] Error 1 Thank You. steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From stepan at coresystems.de Tue Jun 13 21:01:47 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Tue, 13 Jun 2006 21:01:47 +0200 Subject: [LinuxBIOS] etherboot fails to compile for FILO In-Reply-To: <20060613185342.59645.qmail@web38901.mail.mud.yahoo.com> References: <20060613185342.59645.qmail@web38901.mail.mud.yahoo.com> Message-ID: <20060613190147.GA12295@coresystems.de> * steve yannalfo [060613 20:53]: > Same Problem: > > cc -DCONFIG_PCI -DCONFIG_ISA -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DCONFIG_FILO > -DALLOW_ONLY_ENCAPSULATED -DBACKOFF_LIMIT=7 -DCONGESTED -DTAGGED_IMAGE > -DELF_IMAGE -DDOWNLOAD_PROTO_TFTP -Os In file included from arch/i386/core/ > realmode.c:7: > arch/i386/include/realmode.h:119: error: static declaration of > 'allot_real_mode_stack' follows non-static declaration > include/etherboot.h:330: error: previous declaration of 'allot_real_mode_stack' > was here > make: *** [bin/realmode.o] Error 1 Its a very different error message,.. I wonder why it tries to compile realmode.h at all... try removing the "static" in arch/i386/include/realmode.h line 119 -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From fourstar10_2000 at yahoo.com Tue Jun 13 22:59:12 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Tue, 13 Jun 2006 13:59:12 -0700 (PDT) Subject: [LinuxBIOS] To Stephan Message-ID: <20060613205912.16322.qmail@web38908.mail.mud.yahoo.com> Thank you, ------------------------------------------------------------------------- added in "etherboot.h" #ifndef LINUXBIOS extern void allot_real_mode_stack(void); #endif # make clean && make bin/filo.elf OK -------------------------------------------------------------------------- in "ck804_early_setup_car.c" added line 482: hard_reset(); FIXED soft/hard reset differences where LB would stop (soft reset only) PCI: 00:00.0 cmd <- 146 -------------------------------------------------------------------------- steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From per at mellander.org Wed Jun 14 07:03:06 2006 From: per at mellander.org (Per Mellander) Date: Wed, 14 Jun 2006 07:03:06 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> Message-ID: <20060614045610.M15151@mellander.org> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: Config.lb Type: application/octet-stream Size: 1550 bytes Desc: not available URL: From smithbone at gmail.com Wed Jun 14 18:27:55 2006 From: smithbone at gmail.com (Richard Smith) Date: Wed, 14 Jun 2006 11:27:55 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060614154313.M37889@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> <20060614045610.M15151@mellander.org> <8a0c36780606140751g101b134ax3c4cf0375247669d@mail.gmail.com> <20060614154313.M37889@mellander.org> Message-ID: <8a0c36780606140927k62d6900byfb2b8da32d3f6e13@mail.gmail.com> On 6/14/06, Per Mellander wrote: > Thank you, thank you, thank you for those words! > > I was nearly giving up today after trying 64k of zero's instead of VGA and nothing > worked. I was almost certain that I'm to stupid to do this ;) Hmm... That should have worked. The issue is that the buildsystem is creating a rom file that is 64k shy of the size of your ROM part. So all the addresses in the part will all be 64k lower than where they need to be. You can solve this by either prepending 64k data that bumps the size of the rom file up to the size of the rom part, or program the file into the part with a 64k offset. So regardless if you used 0x00's, 0xff, or random bytes you should still get _some_ serial output if the size is correct. You can check your rom file with the following. 'hd -s 255k ' If you don't see an 0xe9 at address 0x0003fff0 then your rom file is not valid. -- Richard A. Smith From smithbone at gmail.com Sun Jun 18 22:39:03 2006 From: smithbone at gmail.com (Richard Smith) Date: Sun, 18 Jun 2006 15:39:03 -0500 Subject: [LinuxBIOS] r2316 broke rumba Message-ID: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> linuxbios_ram.o: In function `enable_dev': northbridge.c:(.text+0x5d45): undefined reference to `graphics_init' collect2: ld returned 1 exit status make[1]: *** [linuxbios_ram] Error 1 make[1]: Leaving directory `/home/rsmith/projects/LinuxBIOSv2/targets/amd/rumba/rumba/normal' I thought we had abuild setup on linuxbios.org to run a nightly build check to catch these. -- Richard A. Smith From smithbone at gmail.com Sun Jun 18 23:06:45 2006 From: smithbone at gmail.com (Richard Smith) Date: Sun, 18 Jun 2006 16:06:45 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <8a0c36780606140751g101b134ax3c4cf0375247669d@mail.gmail.com> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <20060601091409.M98965@mellander.org> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> <20060614045610.M15151@mellander.org> <8a0c36780606140751g101b134ax3c4cf0375247669d@mail.gmail.com> Message-ID: <8a0c36780606181406x7263385see90b243f73e80a1@mail.gmail.com> > system does not handle this correctly. It expects there to be falback > and normal images. > So you have to trick it to make it work right. The trick is to set FALLBACK_SIZE=ROM_SIZE The default config has it set to 0x30000. I suspect it was set that way to allow for the addition of the VGA bios that can't be included in the default distribution. I tested and for me this builds a 256k image that has the reset vector in the right spot. I don't have any epia hardware so I can't test that it actually still boots though. -- Richard A. Smith From smithbone at gmail.com Sun Jun 18 23:23:53 2006 From: smithbone at gmail.com (Richard Smith) Date: Sun, 18 Jun 2006 16:23:53 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <8a0c36780606181406x7263385see90b243f73e80a1@mail.gmail.com> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> <20060614045610.M15151@mellander.org> <8a0c36780606140751g101b134ax3c4cf0375247669d@mail.gmail.com> <8a0c36780606181406x7263385see90b243f73e80a1@mail.gmail.com> Message-ID: <8a0c36780606181423h1f64708dr1100a971cc9f8d80@mail.gmail.com> On 6/18/06, Richard Smith wrote: > > system does not handle this correctly. It expects there to be falback > > and normal images. > > So you have to trick it to make it work right. > > The trick is to set FALLBACK_SIZE=ROM_SIZE > Looks like you need to comment out the following lines in the config as well or I think the addresses of the various entry points will be wrong. option ROM_SECTION_OFFSET=0x10000 option ROM_SECTION_SIZE=0x30000 -- Richard A. Smith From bios at lists.actweb.info Sun Jun 18 23:47:20 2006 From: bios at lists.actweb.info (bios at lists.actweb.info) Date: Sun, 18 Jun 2006 22:47:20 +0100 (BST) Subject: [LinuxBIOS] help selecting bios savour for EPIA-M In-Reply-To: Message-ID: <1150667240.18670@actweb.info> Hi, Can anyone help me with this? I hunted google and the lists but cant find a definate answer for this :( Can someone tell me which RD1-BIOS Savior from ioss.com.tw, I would need to work with the VIA-EPIA-M motherboards? I dont curently have one of these and it is going to be a week or 2 before i get it :( Also one other question :) If the M board takes a 1Mb Flash, can I use a 2Mb Flash chip? (or takes a 2Mb and use a 4Mb) will the board accept it? would i be able to access the extra space for, say installing a kernel or other software? Please note, the last time i used eprom/flash chips was when that was all you had to put OS and software on, and the whole lot had to be run from 32k of EEPROM, with 64k of RAM!!!!! LOL (Those were the days :) ) Thanks for any help, I know i could wait to get the board itself, and then order the RD1, but thats going to take quite a while :) Also if anyone can recomend a supplier for the RD1 in the UK, that would be great Thanks again for any help Matt From bari at onelabs.com Mon Jun 19 00:13:40 2006 From: bari at onelabs.com (Bari Ari) Date: Sun, 18 Jun 2006 17:13:40 -0500 Subject: [LinuxBIOS] Support for AM2 processors? In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4203094BCD@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4203094BCD@ssvlexmb2.amd.com> Message-ID: <4495D014.5030208@onelabs.com> Any news on when the new AM2 code will be released? The AM2 embargo has been lifted. -Bari Lu, Yinghai wrote: > The support code is done, and will be released to public tree after the > CPU is released to public. > > since the upcoming AM2 processors will have a new (DDR2) > memory controller, does that mean the RAM initialization > has to be rewritten completely? If so, is there any expected > time when LinuxBIOS support for these processors will be > available? > From rminnich at lanl.gov Mon Jun 19 04:25:09 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Sun, 18 Jun 2006 20:25:09 -0600 Subject: [LinuxBIOS] r2316 broke rumba In-Reply-To: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> References: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> Message-ID: <44960B05.7080805@lanl.gov> Richard Smith wrote: > linuxbios_ram.o: In function `enable_dev': > northbridge.c:(.text+0x5d45): undefined reference to `graphics_init' > collect2: ld returned 1 exit status > make[1]: *** [linuxbios_ram] Error 1 > make[1]: Leaving directory > `/home/rsmith/projects/LinuxBIOSv2/targets/amd/rumba/rumba/normal' > > I thought we had abuild setup on linuxbios.org to run a nightly build > check to catch these. > This has got to be a mistake on my part, let me dig around. Don't know how this one slipped on. Sorry. ron From rminnich at lanl.gov Mon Jun 19 04:30:40 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Sun, 18 Jun 2006 20:30:40 -0600 Subject: [LinuxBIOS] r2316 broke rumba In-Reply-To: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> References: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> Message-ID: <44960C50.7050907@lanl.gov> Richard Smith wrote: > linuxbios_ram.o: In function `enable_dev': > northbridge.c:(.text+0x5d45): undefined reference to `graphics_init' > collect2: ld returned 1 exit status > make[1]: *** [linuxbios_ram] Error 1 > make[1]: Leaving directory > `/home/rsmith/projects/LinuxBIOSv2/targets/amd/rumba/rumba/normal' > > I thought we had abuild setup on linuxbios.org to run a nightly build > check to catch these. > now I know why I don't always carefully run abuild ... I need to set up a cluster abuild. I will try to figure out how to do this this week. Then we could build all targets in O(1) time. ron From rminnich at lanl.gov Mon Jun 19 04:31:10 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Sun, 18 Jun 2006 20:31:10 -0600 Subject: [LinuxBIOS] r2316 broke rumba In-Reply-To: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> References: <8a0c36780606181339r541f1bd9ye430b6e136ade82b@mail.gmail.com> Message-ID: <44960C6E.9090307@lanl.gov> Richard Smith wrote: > linuxbios_ram.o: In function `enable_dev': > northbridge.c:(.text+0x5d45): undefined reference to `graphics_init' > collect2: ld returned 1 exit status > make[1]: *** [linuxbios_ram] Error 1 > make[1]: Leaving directory > `/home/rsmith/projects/LinuxBIOSv2/targets/amd/rumba/rumba/normal' > > I thought we had abuild setup on linuxbios.org to run a nightly build > check to catch these. > HMM. I don't get an error. Any chance you need to rerun buildtarget? ron From vincentetsou at nexcom.com.tw Mon Jun 19 09:44:06 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Mon, 19 Jun 2006 15:44:06 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <20060512100334.GB22489@coresystems.de> References: <6F7DA19D05F3CF40B890C7CA2DB13A4203094C87@ssvlexmb2.amd.com> <41fde3420605112122h675cf1e1j3b54ee4803d3a802@mail.gmail.com> <20060512100334.GB22489@coresystems.de> Message-ID: <41fde3420606190044j3c39d9cv378854791a4bf963@mail.gmail.com> Hello, Finally my linuxbios bring up the target board. capture5.txt is booting log. But most of device on the target board are not work. Such as BCM5704 under PCI-X bridge. If I try to load "tg3" module into the kernel, I got error message like this, [root at linuxbios ~]# modprobe tg3 PCI: No IRQ known for interrupt pin A of device 0000:03:04.0. Please try using pci=biosirq. PCI: No IRQ known for interrupt pin B of device 0000:03:04.1. Please try using pci=biosirq. How to assign an IRQ for each device ?? 2006/5/12, Stefan Reinauer : > > * Vincente Tsou [060512 06:22]: > > Dear Lu and Stefan, > > > > Thank you very much for your reply. > > > > But I can't find the inherent_ht.c in my LinuxBios source tree. > > Yinghai is talking about src/northbridge/amd/amdk8/incoherent_ht.c > > You need to try commenting out the lines I sent in the last mail from > src/northbridge/amd/amdk8/resourcemap.c > > Stefan > > -- > coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. > Tel.: +49 761 7668825 ? Fax: +49 761 7664613 > Email: info at coresystems.de ? http://www.coresystems.de/ > > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- LinuxBIOS-1.1.8h412_Fallback Mon Jun 19 15:02:16 CST 2006 starting... 01 nodes initialized. SBLink=01 NC node|link=01 ht reset - LinuxBIOS-1.1.8h412_Fallback Mon Jun 19 15:02:16 CST 2006 starting... 01 nodes initialized. SBLink=01 NC node|link=01 Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfd54 testx = 5a5a5a5a Copying data from cache to ram -- switching to use ram as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to ram. src=fffe0000 dst=00004000 linxbios_ram.bin length = 0001746c Jumping to LinuxBIOS. LinuxBIOS-1.1.8h412_Fallback Mon Jun 19 15:02:16 CST 2006 booting... Enumerating buses... PCI_DOMAIN: 0000 enabled APIC_CLUSTER: 0 enabled PCI: pci_scan_bus for bus 0 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] enabled Disabling static device: PCI: 00:19.0 Disabling static device: PCI: 00:19.1 Disabling static device: PCI: 00:19.2 Disabling static device: PCI: 00:19.3 PCI: 01:00.0 [1022/7450] enabled PCI: 01:01.0 [1022/7450] enabled next_unitid: 0003 PCI: 01:00.0 [1022/7460] enabled PCI: 01:03.0 [1022/7460] enabled next_unitid: 0007 PCI: pci_scan_bus for bus 1 PCI: 01:01.0 [1022/7450] enabled PCI: 01:01.1 [1022/7451] enabled PCI: 01:02.0 [1022/7450] enabled PCI: 01:02.1 [1022/7451] enabled PCI: 01:03.0 [1022/7460] enabled PCI: 01:04.0 [1022/7468] enabled PCI: 01:04.1 [1022/7469] enabled PCI: 01:04.2 [1022/746a] enabled PCI: 01:04.3 [1022/746b] enabled PCI: pci_scan_bus for bus 2 PCI: pci_scan_bus returning with max=02 PCI: 02: Conventional PCI PCI: pci_scan_bus for bus 3 PCI: 03:04.0 [14e4/16a8] enabled PCI: 03:04.1 [14e4/16a8] enabled PCI: pci_scan_bus returning with max=03 PCI: 03: 133MHz PCI-X PCI: pci_scan_bus for bus 4 PCI: 04:00.0 [1022/7464] enabled PCI: 04:00.1 [1022/7464] enabled USB2 disabled. PCI: 04:00.2 [1022/7463] disabled PCI: 04:02.0 [1002/4752] enabled PCI: 04:04.0 [8086/1229] enabled PCI: pci_scan_bus returning with max=04 PNP: 002e.0 disabled PNP: 002e.1 disabled PNP: 002e.2 enabled PNP: 002e.3 enabled PNP: 002e.5 enabled PNP: 002e.6 disabled PNP: 002e.7 disabled PNP: 002e.8 disabled PNP: 002e.9 disabled PNP: 002e.a disabled PNP: 002e.b enabled PCI: pci_scan_bus returning with max=04 PCI: pci_scan_bus returning with max=04 PCI: 00:18.3 siblings=0 CPU: APIC: 00 enabled done Allocating resources... Reading resources... PCI: 01:02.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 3 io PCI: 01:02.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 3 prefmem PCI: 01:03.0 24 <- [0x00fff00000 - 0x00ffefffff] bus 4 prefmem Done reading resources. Setting resources... PCI: 00:18.0 1a1 <- [0x00fd300000 - 0x00fd2fffff] prefmem PCI: 00:18.0 1a9 <- [0x00fc000000 - 0x00fd2fffff] mem PCI: 00:18.0 1d9 <- [0x0000001000 - 0x0000002fff] io PCI: 01:01.1 10 <- [0x00fd200000 - 0x00fd200fff] mem64 PCI: 01:02.0 20 <- [0x00fd100000 - 0x00fd1fffff] bus 3 mem PCI: 03:04.0 10 <- [0x00fd100000 - 0x00fd10ffff] mem64 PCI: 03:04.0 18 <- [0x00fd110000 - 0x00fd11ffff] mem64 PCI: 03:04.1 10 <- [0x00fd120000 - 0x00fd12ffff] mem64 PCI: 03:04.1 18 <- [0x00fd130000 - 0x00fd13ffff] mem64 PCI: 01:02.1 10 <- [0x00fd201000 - 0x00fd201fff] mem64 PCI: 01:03.0 1c <- [0x0000001000 - 0x0000001fff] bus 4 io PCI: 01:03.0 20 <- [0x00fc000000 - 0x00fd0fffff] bus 4 mem PCI: 04:00.0 10 <- [0x00fd050000 - 0x00fd050fff] mem PCI: 04:00.1 10 <- [0x00fd051000 - 0x00fd051fff] mem PCI: 04:02.0 10 <- [0x00fc000000 - 0x00fcffffff] mem PCI: 04:02.0 14 <- [0x0000001000 - 0x00000010ff] io PCI: 04:02.0 18 <- [0x00fd052000 - 0x00fd052fff] mem PCI: 04:02.0 30 <- [0x00fd000000 - 0x00fd01ffff] romem PCI: 04:04.0 10 <- [0x00fd053000 - 0x00fd053fff] mem PCI: 04:04.0 14 <- [0x0000001400 - 0x000000143f] io PCI: 04:04.0 18 <- [0x00fd020000 - 0x00fd03ffff] mem PCI: 04:04.0 30 <- [0x00fd040000 - 0x00fd04ffff] romem 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.5 60 <- [0x0000000060 - 0x0000000060] io PNP: 002e.5 62 <- [0x0000000064 - 0x0000000064] io PNP: 002e.5 70 <- [0x0000000001 - 0x0000000001] irq PNP: 002e.5 72 <- [0x000000000c - 0x000000000c] irq PNP: 002e.b 60 <- [0x0000000290 - 0x0000000297] io PNP: 002e.b 70 <- [0x0000000005 - 0x0000000005] irq PCI: 01:04.1 20 <- [0x0000002420 - 0x000000242f] io PCI: 01:04.2 10 <- [0x0000002400 - 0x000000241f] io PCI: 01:04.3 58 <- [0x0000002000 - 0x00000020ff] io PCI: 00:18.3 94 <- [0x00f8000000 - 0x00fbffffff] mem Done setting resources. Done allocating resources. Enabling resources... PCI: 00:18.0 cmd <- 140 PCI: 01:01.1 subsystem <- 00/00 PCI: 01:01.1 cmd <- 146 PCI: 01:02.0 bridge ctrl <- 0003 PCI: 01:02.0 cmd <- 146 PCI: 03:04.0 subsystem <- 00/00 PCI: 03:04.0 cmd <- 142 PCI: 03:04.1 subsystem <- 00/00 PCI: 03:04.1 cmd <- 142 PCI: 01:02.1 subsystem <- 00/00 PCI: 01:02.1 cmd <- 146 PCI: 01:03.0 bridge ctrl <- 0003 PCI: 01:03.0 cmd <- 147 PCI: 04:00.0 subsystem <- 00/00 PCI: 04:00.0 cmd <- 142 PCI: 04:00.1 subsystem <- 00/00 PCI: 04:00.1 cmd <- 142 PCI: 04:02.0 cmd <- 1c3 PCI: 04:04.0 cmd <- 143 PCI: 01:04.0 subsystem <- 00/00 PCI: 01:04.0 cmd <- 14f w83627hf hwm smbus enabled PCI: 01:04.1 subsystem <- 00/00 PCI: 01:04.1 cmd <- 141 PCI: 01:04.2 subsystem <- 00/00 PCI: 01:04.2 cmd <- 141 PCI: 01:04.3 subsystem <- 00/00 PCI: 01:04.3 cmd <- 141 PCI: 00:18.1 subsystem <- 00/00 PCI: 00:18.1 cmd <- 140 PCI: 00:18.2 subsystem <- 00/00 PCI: 00:18.2 cmd <- 140 PCI: 00:18.3 cmd <- 140 done. Initializing devices... Root Device init PCI: 00:18.0 init PCI: 01:02.0 init PCI: 03:04.0 init PCI: 03:04.1 init PCI: 01:03.0 init PCI: 01:04.0 init amd8111: ioapic bsp_apicid = 00 RTC Init Invalid CMOS LB checksum enabling HPET @0xfed00000 PNP: 002e.2 init PNP: 002e.3 init PNP: 002e.5 init PNP: 002e.b init PCI: 01:04.1 init IDE1 IDE0 PCI: 01:04.3 init set power on after power fail PCI: 00:18.1 init PCI: 00:18.2 init PCI: 00:18.3 init NB: Function 3 Misc Control.. done. APIC_CLUSTER: 0 init Initializing CPU #0 CPU: vendor AMD device f5a Enabling cache Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB, RdMEM, WrMEM Setting fixed MTRRs(24-88) Type: WB, RdMEM, WrMEM DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 512MB, type WB DONE variable MTRRs Clear out the extra MTRR's MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled microcode: equivalent processor rev id = 0x004a, patch id = 0x00000000 microcode: patch id that want to apply= 0x00000047 microcode: updated to patch id = 0x00000047 success Setting up local apic... apic_id: 0 done. Clearing memory 2048K - 524288K: ------- done CPU #0 Initialized APIC delivery error (4). CPU 1 would not start! CPU 1 did not initialize! All AP CPUs stopped PCI: 04:02.0 init PCI: 04:04.0 init Devices initialized Writing IRQ routing tables to 0xf0000...done. Wrote the mp table end at: 00000020 - 000001b8 Moving GDT to 0x500...ok Wrote linuxbios table at: 00000530 - 00000dcc checksum a17 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 rom_stream: 0xfffc0000 - 0xfffdffff Found ELF candiate at offset 0 Loading Etherboot version: 5.2.6 Dropping non PT_LOAD segment New segment addr 0x20000 size 0x6469a offset 0xb0 filesize 0xd0cd (cleaned up) New segment addr 0x20000 size 0x6469a offset 0xb0 filesize 0xd0cd Loading Segment: addr: 0x000000001ffa4000 memsz: 0x0000000000020000 filesz: 0x000000000000d0cd Clearing Segment: addr: 0x000000001ffb10cd memsz: 0x0000000000012f33 Loading Segment: addr: 0x0000000000040000 memsz: 0x000000000004469a filesz: 0x0000000000000000 Clearing Segment: addr: 0x0000000000040000 memsz: 0x000000000004469a Jumping to boot code at 0x20000 ROM segment 0x0000 length 0x0000 reloc 0x00020000 CPU 2281 Mhz Etherboot 5.2.6 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO] Relocating _text from: [0002d0d0,00086240) to [1fea6e90,1ff00000) Boot from (N)etwork (D)isk or (Q)uit? D Probing pci disk... [FILO]FILO version 0.4.1 (vincente at TSOU) Wed May 3 15:16:34 CST 2006 Press for default boot, or for boot prompt... 2 1 timed out boot: hda1:/boot/vmlinuz initrd=/boot/initrd noacpi ro root=/dev/hda1 console=tty0 console=ttyS0,115200 hda: LBA: Maxtor 6Y080P0 Mounted ext2fs Found Linux version 2.6.9-1.667 (bhcompile at tweety.build.redhat.com) #1 Tue Nov 2 14:41:25 EST 2004 bzImage. Loading kernel... ok Loading initrd... ok Jumping to entry point... Linux version 2.6.9-1.667 (bhcompile at tweety.build.redhat.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:41:25 EST 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 0000000000000e34 type 16 BIOS-e820: 0000000000000e34 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 00000000000f0400 type 16 BIOS-e820: 0000000000100000 - 0000000020000000 (usable) 0MB HIGHMEM available. 512MB LOWMEM available. zapping low mappings. DMI not present. ACPI: Unable to locate RSDP Built 1 zonelists Kernel command line: noacpi ro root=/dev/hda1 console=tty0 console=ttyS0,115200 mapped 4G/4G trampoline to ffff4000. Initializing CPU#0 CPU 0 irqstacks, hard=023d5000 soft=023d4000 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 2205.406 MHz processor. Using tsc for high-res timesource Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 515148k/524288k available (2068k kernel code, 8584k reserved, 647k data, 144k init, 0k highmem) Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: AMD 02/05 stepping 0a Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. checking if image is initramfs... it is Freeing initrd memory: 386k freed NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040816 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Unable to handle 64-bit address space for PCI: Discovered primary peer bus 01 [IRQ] PCI: Using IRQ router default [1022/7468] at 0000:01:04.0 PCI: IRQ 0 for device 0000:01:04.2 doesn't match PIRQ mask - try pci=usepirqmask apm: BIOS not found. audit: initializing netlink socket (disabled) audit(1009857017.468:0): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 6ECDA687281A73E5 - key was been created 89567280 seconds in future - User ID: Red Hat, Inc. (Kernel Module GPG key) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 vesafb: probe of vesafb0 failed with error -6 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12 Linux agpgart interface v0.100 (c) Dave Jones serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled ?ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AMD8111: IDE controller at PCI slot 0000:01:04.1 AMD8111: chipset revision 3 AMD8111: not 100% native mode: will probe irqs later AMD8111: 0000:01:04.1 (rev 03) UDMA133 controller ide0: BM-DMA at 0x2420-0x2427, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0x2428-0x242f, BIOS settings: hdc:pio, hdd:pio hda: Maxtor 6Y080P0, ATA DISK drive Using cfq io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 128KiB hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63, UDMA(133) hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown ide0: reset: success hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown ide0: reset: success hda1 hda2 hda3 ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard on isa0060/serio0 input: ImPS/2 Logitech Wheel Mouse on isa0060/serio1 md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 NET: Registered protocol family 2 IP: routing cache hash table of 1024 buckets, 32Kbytes TCP: Hash tables configured (established 131072 bind 37449) Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Freeing unused kernel memory: 144k freed Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Loading jbd.ko module Loading ext3.ko module Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Switching to new root SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks INIT: version 2.85 booting Welcome to Fedora Core Press 'I' to enter interactive startup. Starting udev: [ OK ] Initializing hardware... storage network audio done[ OK ] Configuring kernel parameters: [ OK ] Setting clock (utc): Tue Jan 1 11:50:35 CST 2002 [ OK ] Setting hostname linuxbios: [ OK ] Checking root filesystem [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda1 /1: clean, 333623/1026144 files, 1822094/2048279 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Setting up Logical Volume Management: [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a /dev/hda3 /home1: clean, 32800/8863744 files, 531251/17697605 blocks [ OK ] Mounting local filesystems: [ OK ] Enabling local filesystem quotas: [ OK ] Enabling swap space: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Starting sysstat: [ OK ] Checking for new hardware [ OK ] Applying iptables firewall rules: [ OK ] Starting pcmcia: [ OK ] Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting irqbalance: [ OK ] Starting portmap: [ OK ] Starting NFS statd: [ OK ] Starting NFS4 idmapd: [ OK ] Mounting other filesystems: [ OK ] Starting lm_sensors: [ OK ] Starting automount:No Mountpoints Defined[ OK ] Starting nifd... Starting mDNSResponder... [ OK ] Starting smartd: [ OK ] Starting hpoj: [ OK ] Starting cups: [ OK ] Starting sshd:[ OK ] Starting xinetd: [ OK ] Starting sendmail: make: Warning: File `Makefile' has modification time 8.4e+07 s in the future make: warning: Clock skew detected. Your build may be incomplete. /usr/sbin/sendmail: /usr/sbin/sendmail: cannot execute binary file [FAILED] Starting sm-client: /usr/sbin/sendmail: /usr/sbin/sendmail: cannot execute binary file [FAILED] Starting console mouse services: [ OK ] Starting IIIMF input server: [ OK ] Starting Canna server: [ OK ] Starting crond: [ OK ] Starting xfs: [ OK ] Starting anacron: [ OK ] Starting atd: [ OK ] Starting system message bus: [ OK ] Starting cups-config-daemon: [ OK ] Starting HAL daemon: [ OK ] Fedora Core release 3 (Heidelberg) Kernel 2.6.9-1.667 on an i686 linuxbios login: From noodles at earth.li Mon Jun 19 09:58:42 2006 From: noodles at earth.li (Jonathan McDowell) Date: Mon, 19 Jun 2006 08:58:42 +0100 Subject: [LinuxBIOS] help selecting bios savour for EPIA-M In-Reply-To: <1150667240.18670@actweb.info> References: <1150667240.18670@actweb.info> Message-ID: <20060619075842.GC9851@earth.li> On Sun, Jun 18, 2006 at 10:47:20PM +0100, bios at lists.actweb.info wrote: > Can anyone help me with this? > > I hunted google and the lists but cant find a definate answer for this > :( > > Can someone tell me which RD1-BIOS Savior from ioss.com.tw, I would > need to work with the VIA-EPIA-M motherboards? I dont curently have > one of these and it is going to be a week or 2 before i get it :( I am using an RD1-PL with my EPIA-M (the original BIOS chip is an SST 39SF020A). > Also one other question :) If the M board takes a 1Mb Flash, can I use > a 2Mb Flash chip? (or takes a 2Mb and use a 4Mb) will the board accept > it? would i be able to access the extra space for, say installing a > kernel or other software? I believe this depends on the board; you need the extra address line(s) brought out to the socket for it to work. I haven't tried it myself. The EPIA-M is a 2M (ie 256Kbyte) part. > Also if anyone can recomend a supplier for the RD1 in the UK, that > would be great I'm in the UK and couldn't find a supplier easily when I looked; I ordered from http://www.eksitdata.com/ J. -- Avoid temporary variables and strange women. From per at mellander.org Mon Jun 19 13:13:41 2006 From: per at mellander.org (Per Mellander) Date: Mon, 19 Jun 2006 13:13:41 +0200 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <8a0c36780606181423h1f64708dr1100a971cc9f8d80@mail.gmail.com> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <8a0c36780606090746w282a2bfdx8bbc034b658c7874@mail.gmail.com> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> <20060614045610.M15151@mellander.org> <8a0c36780606140751g101b134ax3c4cf0375247669d@mail.gmail.com> <8a0c36780606181406x7263385see90b243f73e80a1@mail.gmail.com> <8a0c36780606181423h1f64708dr1100a971cc9f8d80@mail.gmail.com> Message-ID: <20060619111036.M65762@mellander.org> On Sun, 18 Jun 2006 16:23:53 -0500, Richard Smith wrote > On 6/18/06, Richard Smith wrote: > > > system does not handle this correctly. It expects there to be falback > > > and normal images. > > > So you have to trick it to make it work right. > > > > The trick is to set FALLBACK_SIZE=ROM_SIZE > > > > Looks like you need to comment out the following lines in the config as well > or I think the addresses of the various entry points will be wrong. > > option ROM_SECTION_OFFSET=0x10000 > option ROM_SECTION_SIZE=0x30000 > Don't know if I missed something, but this Config.lb gives the same reboots after kernel has been loaded :( /Per ----8<--------------------------------------------------- # Sample config file for EPIA-M # This will make a target directory of ./epia-m target epia-m mainboard via/epia-m option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1 ### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=0x30000 ## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000 # ### ### Compute the start location and size size of ### The linuxBIOS bootloader. ### # # EPIA-M # #romimage "normal" # option USE_FALLBACK_IMAGE=0 # option ROM_IMAGE_SIZE=0xc000 # option ROM_SECTION_OFFSET=0x10000 # option ROM_SECTION_SIZE=0x18000 # option XIP_ROM_BASE=0xfffd0000 # option LINUXBIOS_EXTRA_VERSION=".0Normal" # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi # payload /filo.elf #end romimage "fallback" option FALLBACK_SIZE=ROM_SIZE option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 # option ROM_SECTION_OFFSET=0x10000 # option ROM_SECTION_SIZE=0x30000 # option XIP_ROM_BASE=0xfffe0000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi payload /filo.elf # payload /memtest end buildrom ./linuxbios.rom ROM_SIZE "fallback" ----8<--------------------------------------------------- From stuge-linuxbios at cdy.org Mon Jun 19 17:18:02 2006 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Mon, 19 Jun 2006 17:18:02 +0200 Subject: [LinuxBIOS] help selecting bios savour for EPIA-M In-Reply-To: <20060619075842.GC9851@earth.li> References: <1150667240.18670@actweb.info> <20060619075842.GC9851@earth.li> Message-ID: <20060619151804.20646.qmail@cdy.org> On Mon, Jun 19, 2006 at 08:58:42AM +0100, Jonathan McDowell wrote: > > Also one other question :) If the M board takes a 1Mb Flash, can I use > > a 2Mb Flash chip? (or takes a 2Mb and use a 4Mb) will the board accept > > it? would i be able to access the extra space for, say installing a > > kernel or other software? > > I believe this depends on the board; you need the extra address line(s) > brought out to the socket for it to work. I haven't tried it myself. The > EPIA-M is a 2M (ie 256Kbyte) part. If the part is connected via an LPC bus no more lines are needed, but then it's up to the address decoder in the southbridge. I don't know if they typically only decode limited ranges to the LPC bus. //Peter From smithbone at gmail.com Mon Jun 19 17:14:53 2006 From: smithbone at gmail.com (Richard Smith) Date: Mon, 19 Jun 2006 10:14:53 -0500 Subject: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie ) In-Reply-To: <20060619111036.M65762@mellander.org> References: <01M32C24KYG48YB0Y3@EMAIL1.BYU.EDU> <13426df10606100911r7bd5e35at4a0bec05a83acfea@mail.gmail.com> <20060612114421.M22682@mellander.org> <20060613125600.M11621@mellander.org> <8a0c36780606130741k4c2a2aau4bc42154263ccf1f@mail.gmail.com> <20060614045610.M15151@mellander.org> <8a0c36780606140751g101b134ax3c4cf0375247669d@mail.gmail.com> <8a0c36780606181406x7263385see90b243f73e80a1@mail.gmail.com> <8a0c36780606181423h1f64708dr1100a971cc9f8d80@mail.gmail.com> <20060619111036.M65762@mellander.org> Message-ID: <8a0c36780606190814r43dbb12bwe20190cbce4cc91@mail.gmail.com> > > Don't know if I missed something, but this Config.lb > gives the same reboots after kernel has been loaded :( All I was trying to solve was your incorrect build size. If it boots at all then my suggestion worked. *grin* -- Richard A. Smith From smithbone at gmail.com Mon Jun 19 17:25:31 2006 From: smithbone at gmail.com (Richard Smith) Date: Mon, 19 Jun 2006 10:25:31 -0500 Subject: [LinuxBIOS] help selecting bios savour for EPIA-M In-Reply-To: <20060619151804.20646.qmail@cdy.org> References: <1150667240.18670@actweb.info> <20060619075842.GC9851@earth.li> <20060619151804.20646.qmail@cdy.org> Message-ID: <8a0c36780606190825w15dfe2dcja303559d1329a04e@mail.gmail.com> On 6/19/06, Peter Stuge wrote: > On Mon, Jun 19, 2006 at 08:58:42AM +0100, Jonathan McDowell wrote: > > > Also one other question :) If the M board takes a 1Mb Flash, can I use > > > a 2Mb Flash chip? (or takes a 2Mb and use a 4Mb) will the board accept > > > it? would i be able to access the extra space for, say installing a > > > kernel or other software? > > > > I believe this depends on the board; you need the extra address line(s) > > brought out to the socket for it to work. I haven't tried it myself. The > > EPIA-M is a 2M (ie 256Kbyte) part. > > If the part is connected via an LPC bus no more lines are needed, but > then it's up to the address decoder in the southbridge. I don't know > if they typically only decode limited ranges to the LPC bus. > If you duplicate the image in the larger part then it should work either way. So if you are using a 2M chip and your orginal was only 1M then take your 1M image cat it onto itself and use that in your 2M part. Then it dosen't matter what the upper address line does. The code fetched will be the same. -- Richard A. Smith From bari at onelabs.com Mon Jun 19 17:37:09 2006 From: bari at onelabs.com (Bari Ari) Date: Mon, 19 Jun 2006 10:37:09 -0500 Subject: [LinuxBIOS] help selecting bios savour for EPIA-M In-Reply-To: <20060619151804.20646.qmail@cdy.org> References: <1150667240.18670@actweb.info> <20060619075842.GC9851@earth.li> <20060619151804.20646.qmail@cdy.org> Message-ID: <4496C4A5.5020001@onelabs.com> Depends on the chipset. I've had parts that theoretically could access beyond 256k Bytes of range but had all kinds of hoops to jump through in register settings to decode beyond that. -Bari Peter Stuge wrote: > If the part is connected via an LPC bus no more lines are needed, but > then it's up to the address decoder in the southbridge. I don't know > if they typically only decode limited ranges to the LPC bus. > From rminnich at lanl.gov Mon Jun 19 18:18:54 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Mon, 19 Jun 2006 10:18:54 -0600 Subject: [LinuxBIOS] help selecting bios savour for EPIA-M In-Reply-To: <4496C4A5.5020001@onelabs.com> References: <1150667240.18670@actweb.info> <20060619075842.GC9851@earth.li> <20060619151804.20646.qmail@cdy.org> <4496C4A5.5020001@onelabs.com> Message-ID: <4496CE6E.6020601@lanl.gov> Bari Ari wrote: > Depends on the chipset. I've had parts that theoretically could access > beyond 256k Bytes of range but had all kinds of hoops to jump through in > register settings to decode beyond that. all the new chipset, however, seem to have enough of the right bits to get to at least 16 mbits -- 2 mybtes. ron From yinghai.lu at amd.com Mon Jun 19 18:12:59 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Mon, 19 Jun 2006 09:12:59 -0700 Subject: [LinuxBIOS] New guy in LinuxBios Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FDE@ssvlexmb2.amd.com> You need to update the entries at mptable.c for your slots or onboard pci device. YH -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.johnson at celoxica.com Mon Jun 19 22:04:49 2006 From: dan.johnson at celoxica.com (Dan Johnson) Date: Mon, 19 Jun 2006 15:04:49 -0500 Subject: [LinuxBIOS] Initiate LDTSTOP (without RESET) Message-ID: <26DD6747056781428950953ADC66461C2A9B22@exchangeus.us.celoxica.com> I have been reading over the mailing list and reading over the LinuxBIOS code trying to get a feel for things but I am in need of some wisdom. It seems LDTSTOP is not used by the LinuxBIOS for the most part and I am curious why. What I have gathered so far is that it is system specific (Southbridge?) to trigger. I found some mailing list mentions of old code from years ago that is no longer in the current tree. I am searching for a way to disable and re-enable HT links for various reasons _without_ performing a reset (for example changing link speed/width or enabling/disabling devices at runtime). It seems that LinuxBIOS has chosen to not use LDTSTOP and just use resets instead. Is this a workaround due to the difficulty of implementing LDTSTOP? I am using a Tyan K8SRE (S2891) motherboard. The board has an Nvidia nForce 4 Pro (CK804). Regards, Dan Johnson _____________________________________________________________________ This message has been checked for all known viruses by the MessageLabs Virus Scanning Service, on behalf of Celoxica Ltd. This email and any files transmitted with it are confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed. If you have received this in error, please contact the sender and delete the material immediately. Whilst this email has been swept for viruses, you should carry out your own virus check before opening any attachment. Celoxica Ltd accepts no liability for any loss or damage which may be caused by software viruses or interception or interruption of this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Mon Jun 19 22:34:12 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Mon, 19 Jun 2006 13:34:12 -0700 Subject: [LinuxBIOS] Initiate LDTSTOP (without RESET) Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FE3@ssvlexmb2.amd.com> LDTSTOP may need to SB to help. When trying to change cpu fid, CPU need LDTSTOP to make the FID change effective. enable_fid_change_on_sb will enable ldtstop on sb. Current Amd8111 support code already have enable_fid_change_on_sb in the public tree. Serverworks ht1000 need to call ldtstop explicitly to make fid change effective. I will check in the code after the new cpu is released. The problem the ck804 has problem with ldtstop. We have to use some other way to make it effective... YH -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhendrix at google.com Mon Jun 19 22:41:48 2006 From: dhendrix at google.com (David Hendricks) Date: Mon, 19 Jun 2006 13:41:48 -0700 Subject: [LinuxBIOS] Initiate LDTSTOP (without RESET) In-Reply-To: <26DD6747056781428950953ADC66461C2A9B22@exchangeus.us.celoxica.com> References: <26DD6747056781428950953ADC66461C2A9B22@exchangeus.us.celoxica.com> Message-ID: It looks like Stefan wanted to do it a while back, but Eric noted that it wouldn't be easy: http://www.linuxbios.org/pipermail/linuxbios/2003-November/005994.html Perhaps the remaining errata has been worked out by now? On 6/19/06, Dan Johnson wrote: > > It seems that LinuxBIOS has chosen to not use LDTSTOP and just use resets > instead. Is this a workaround due to the difficulty of implementing LDTSTOP? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.gambus at gmail.com Tue Jun 20 22:09:26 2006 From: stephane.gambus at gmail.com (steph) Date: Tue, 20 Jun 2006 22:09:26 +0200 Subject: [LinuxBIOS] Linuxbios on Inspiron 8500 DELL Laptop Message-ID: <1150834166.5542.21.camel@localhost.localdomain> Hello, I would like to install Linuxbios on my Inspiron 8500 Dell Laptop. Can someone tell me if it is possible without breaking everything ? Can you tell me the probability of a success ? Do you need other informations ? Tanks to all Stephane Here are the results of system commands on my sarge debian lspci ------------------------------------------------------------------------------------------- 0000:00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 04) 0000:00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04) 0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03) 0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03) 0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03) 0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 03) 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83) 0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03) 0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 03) 0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) 0000:01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 Go AGP 8x] (rev a1) 0000:02:00.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 0000:02:01.0 CardBus bridge: Texas Instruments PCI4510 PC card Cardbus Controller (rev 02) 0000:02:01.1 FireWire (IEEE 1394): Texas Instruments PCI4510 IEEE-1394 Controller ------------------------------------------------------------------------------------------- dmesg ------------------------------------------------------------------------------------------- Linux version 2.6.16.16 (root at debian) (version gcc 3.3.5 (Debian 1:3.3.5-13)) #1 PREEMPT Sat May 20 11:04:54 CEST 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved) BIOS-e820: 0000000000100000 - 000000003ffae000 (usable) BIOS-e820: 000000003ffae000 - 0000000040000000 (reserved) BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 262062 DMA zone: 4096 pages, LIFO batch:0 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 32686 pages, LIFO batch:7 DMI 2.3 present. ACPI: RSDP (v000 DELL ) @ 0x000fdf00 ACPI: RSDT (v001 DELL CPi R 0x27d5061e ASL 0x00000061) @ 0x3fff0000 ACPI: FADT (v001 DELL CPi R 0x27d5061e ASL 0x00000061) @ 0x3fff0400 ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000e) @ 0x00000000 ACPI: PM-Timer IO Port: 0x808 Allocating PCI resources starting at 50000000 (gap: 40000000:beda0000) Built 1 zonelists Kernel command line: root=/dev/hda2 ro lapic Local APIC disabled by BIOS -- reenabling. Found and enabled local APIC! mapped APIC to ffffd000 (fee00000) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 2193.924 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1032808k/1048248k available (1543k kernel code, 14712k reserved, 547k data, 160k init, 130744k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4395.06 BogoMIPS (lpj=8790124) Security Framework v1.0.0 initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled CPU: Intel Mobile Intel(R) Pentium(R) 4 - M CPU 2.20GHz stepping 07 Checking 'hlt' instruction... OK. ACPI: setting ELCR to 0200 (from 0800) checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 3180k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfc96e, last bus=2 PCI: Using configuration type 1 ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 0880-08bf claimed by ICH4 GPIO PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Boot video device is 0000:01:00.0 PCI: Transparent bridge - 0000:00:1e.0 PCI: Bus #03 (-#06) may be hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11 ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT] Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:02: ioport range 0x4d0-0x4d1 has been reserved pnp: 00:02: ioport range 0x800-0x805 could not be reserved pnp: 00:02: ioport range 0x808-0x80f could not be reserved pnp: 00:03: ioport range 0xf400-0xf4fe has been reserved pnp: 00:03: ioport range 0x806-0x807 has been reserved pnp: 00:03: ioport range 0x810-0x85f could not be reserved pnp: 00:03: ioport range 0x860-0x87f has been reserved pnp: 00:03: ioport range 0x880-0x8bf has been reserved pnp: 00:03: ioport range 0x8c0-0x8df has been reserved pnp: 00:08: ioport range 0x900-0x97f has been reserved PCI: Bridge: 0000:00:01.0 IO window: c000-cfff MEM window: fc000000-fdffffff PREFETCH window: f0000000-f3ffffff PCI: Bus 3, cardbus bridge: 0000:02:01.0 IO window: 0000d000-0000d0ff IO window: 0000d400-0000d4ff PREFETCH window: 50000000-51ffffff MEM window: f6000000-f7ffffff PCI: Bridge: 0000:00:1e.0 IO window: d000-efff MEM window: f6000000-fbffffff PREFETCH window: 50000000-51ffffff PCI: Setting latency timer of device 0000:00:1e.0 to 64 PCI: Enabling device 0000:02:01.0 (0000 -> 0003) ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered ACPI: Video Device [VID] (multi-head: yes rom: no post: no) PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize NET: Registered protocol family 2 input: AT Translated Set 2 keyboard as /class/input/input0 IP route cache hash table entries: 65536 (order: 6, 262144 bytes) TCP established hash table entries: 262144 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered TCP bic registered Using IPI Shortcut mode ACPI wakeup devices: LID PBTN PCI0 USB0 USB1 USB2 USB3 MODM PCIE ACPI: (supports S0 S1 S3 S4 S5) RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 3180KiB [1 disk] into ram disk... |/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-done. VFS: Mounted root (cramfs filesystem) readonly. Freeing unused kernel memory: 160k freed NET: Registered protocol family 1 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH4: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 ICH4: chipset revision 3 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: HTS726060M9AT00, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: HL-DT-STCD-RW/DVD-ROM GCC-4240N, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 512KiB hda: 117210240 sectors (60011 MB) w/7877KiB Cache, CHS=16383/255/63, UDMA(100) hda: cache flushes supported hda: hda1 hda2 hda3 EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds Adding 979956k swap on /dev/hda3. Priority:-1 extents:1 across:979956k EXT3 FS on hda2, internal journal hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 ACPI: AC Adapter [AC] (on-line) ACPI: Battery Slot [BAT0] (battery present) ACPI: Battery Slot [BAT1] (battery absent) ACPI: Lid Switch [LID] ACPI: Power Button (CM) [PBTN] ACPI: Sleep Button (CM) [SBTN] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM] (41 C) input: PS/2 Mouse as /class/input/input1 input: AlpsPS/2 ALPS GlidePoint as /class/input/input2 Linux agpgart interface v0.101 (c) Dave Jones b44.c:v0.97 (Nov 30, 2005) ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 eth0: Broadcom 4400 10/100BaseT Ethernet 00:0b:db:18:7d:8b usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v2.3 ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1d.0 to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 11, io base 0x0000bf80 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1d.1 to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 11, io base 0x0000bf40 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.2: irq 11, io base 0x0000bf20 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected usb 1-1: new low speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice usbcore: registered new driver hiddev input: Combo Mouse Combo Mouse as /class/input/input3 input: USB HID v1.10 Mouse [Combo Mouse Combo Mouse] on usb-0000:00:1d.0-1 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1d.7 to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: debug port 1 PCI: cache line size of 128 is not supported by device 0000:00:1d.7 ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:1d.7: irq 11, io mem 0xf4fffc00 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected usb 1-1: USB disconnect, address 2 usb 1-1: new low speed USB device using uhci_hcd and address 3 usb 1-1: configuration #1 chosen from 1 choice input: Combo Mouse Combo Mouse as /class/input/input4 input: USB HID v1.10 Mouse [Combo Mouse Combo Mouse] on usb-0000:00:1d.0-1 mice: PS/2 mouse device common for all mice agpgart: Detected an Intel i845 Chipset. agpgart: AGP aperture is 128M @ 0xe8000000 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1f.5 to 64 intel8x0_measure_ac97_clock: measured 54889 usecs intel8x0: clocking to 48000 ieee1394: Initialized config rom entry `ip1394' ACPI: PCI Interrupt 0000:02:01.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[faffd800-faffdfff] Max Packet=[2048] IR/IT contexts=[4/8] ieee1394: Host added: ID:BUS[0-00:1023] GUID[484fc00034585410] eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) Real Time Clock Driver v1.12ac parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA] NET: Registered protocol family 17 b44: eth0: Link is up at 10 Mbps, half duplex. b44: eth0: Flow control is off for TX and off for RX. NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8756 Wed Mar 29 14:26:26 PST 2006 agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode eth0: no IPv6 routers present ------------------------------------------------------------------------------------------- /proc/cpuinfo ------------------------------------------------------------------------------------------- processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Mobile Intel(R) Pentium(R) 4 - M CPU 2.20GHz stepping : 7 cpu MHz : 2193.924 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr bogomips : 4395.06 ------------------------------------------------------------------------------------------- /proc/bus/input/devices ------------------------------------------------------------------------------------------- I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/class/input/input0 H: Handlers=kbd B: EV=120013 B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe B: MSC=10 B: LED=7 I: Bus=0011 Vendor=0002 Product=0008 Version=0000 N: Name="PS/2 Mouse" P: Phys=isa0060/serio1/input1 S: Sysfs=/class/input/input1 H: Handlers=mouse0 B: EV=7 B: KEY=70000 0 0 0 0 0 0 0 0 B: REL=3 I: Bus=0011 Vendor=0002 Product=0008 Version=6337 N: Name="AlpsPS/2 ALPS GlidePoint" P: Phys=isa0060/serio1/input0 S: Sysfs=/class/input/input2 H: Handlers=mouse1 B: EV=f B: KEY=420 0 70000 0 0 0 0 0 0 0 0 B: REL=3 B: ABS=1000003 I: Bus=0003 Vendor=04b4 Product=aefa Version=0001 N: Name="Combo Mouse Combo Mouse" P: Phys=usb-0000:00:1d.0-1/input0 S: Sysfs=/class/input/input4 H: Handlers=mouse2 B: EV=7 B: KEY=70000 0 0 0 0 0 0 0 0 B: REL=103 ------------------------------------------------------------------------------------------- From smithbone at gmail.com Tue Jun 20 22:26:10 2006 From: smithbone at gmail.com (Richard Smith) Date: Tue, 20 Jun 2006 15:26:10 -0500 Subject: [LinuxBIOS] Linuxbios on Inspiron 8500 DELL Laptop In-Reply-To: <1150834166.5542.21.camel@localhost.localdomain> References: <1150834166.5542.21.camel@localhost.localdomain> Message-ID: <8a0c36780606201326n5a1870e7k557cb960236b46c7@mail.gmail.com> > I would like to install Linuxbios on my Inspiron 8500 Dell Laptop. > Can someone tell me if it is possible without breaking everything ? > Can you tell me the probability of a success ? Near zero. Newer Intel chipsets don't play well with LinuxBIOS. -- Richard A. Smith From rminnich at lanl.gov Tue Jun 20 23:16:49 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Tue, 20 Jun 2006 15:16:49 -0600 Subject: [LinuxBIOS] Linuxbios on Inspiron 8500 DELL Laptop In-Reply-To: <8a0c36780606201326n5a1870e7k557cb960236b46c7@mail.gmail.com> References: <1150834166.5542.21.camel@localhost.localdomain> <8a0c36780606201326n5a1870e7k557cb960236b46c7@mail.gmail.com> Message-ID: <449865C1.3030001@lanl.gov> Richard Smith wrote: >>I would like to install Linuxbios on my Inspiron 8500 Dell Laptop. >>Can someone tell me if it is possible without breaking everything ? >>Can you tell me the probability of a success ? > > > Near zero. Newer Intel chipsets don't play well with LinuxBIOS. > Not that they can not play well, mind you; it's just that Intel would rather they not :-) ron From JJia at Fortinet.com Wed Jun 21 02:07:26 2006 From: JJia at Fortinet.com (Jia Jianwei) Date: Tue, 20 Jun 2006 17:07:26 -0700 Subject: [LinuxBIOS] Initiate LDTSTOP (without RESET) References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FE3@ssvlexmb2.amd.com> Message-ID: <00fa01c694c7$39dc27d0$3a4610ac@fortinet.com> Could you please give me some reference code on how to make fid change effective on HT1000 southbridge? Thanks! Jianwei ----- Original Message ----- From: Lu, Yinghai To: Dan Johnson ; linuxbios at linuxbios.org Sent: Monday, June 19, 2006 1:34 PM Subject: Re: [LinuxBIOS] Initiate LDTSTOP (without RESET) LDTSTOP may need to SB to help. When trying to change cpu fid, CPU need LDTSTOP to make the FID change effective. enable_fid_change_on_sb will enable ldtstop on sb. Current Amd8111 support code already have enable_fid_change_on_sb in the public tree. Serverworks ht1000 need to call ldtstop explicitly to make fid change effective. I will check in the code after the new cpu is released. The problem the ck804 has problem with ldtstop. We have to use some other way to make it effective. YH ------------------------------------------------------------------------------ -- linuxbios mailing list linuxbios at linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Wed Jun 21 02:25:54 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Tue, 20 Jun 2006 17:25:54 -0700 Subject: [LinuxBIOS] Initiate LDTSTOP (without RESET) Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FE8@ssvlexmb2.amd.com> Ok, let me find some time to check in the code this week YH ________________________________ From: Jia Jianwei [mailto:JJia at Fortinet.com] Sent: Tuesday, June 20, 2006 5:07 PM To: Lu, Yinghai Cc: Dan Johnson; linuxbios at linuxbios.org Subject: Re: [LinuxBIOS] Initiate LDTSTOP (without RESET) Could you please give me some reference code on how to make fid change effective on HT1000 southbridge? Thanks! Jianwei ----- Original Message ----- From: Lu, Yinghai To: Dan Johnson ; linuxbios at linuxbios.org Sent: Monday, June 19, 2006 1:34 PM Subject: Re: [LinuxBIOS] Initiate LDTSTOP (without RESET) LDTSTOP may need to SB to help. When trying to change cpu fid, CPU need LDTSTOP to make the FID change effective. enable_fid_change_on_sb will enable ldtstop on sb. Current Amd8111 support code already have enable_fid_change_on_sb in the public tree. Serverworks ht1000 need to call ldtstop explicitly to make fid change effective. I will check in the code after the new cpu is released. The problem the ck804 has problem with ldtstop. We have to use some other way to make it effective... YH ________________________________ -- linuxbios mailing list linuxbios at linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincentetsou at nexcom.com.tw Wed Jun 21 04:05:16 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Wed, 21 Jun 2006 10:05:16 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FDE@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FDE@ssvlexmb2.amd.com> Message-ID: <41fde3420606201905y739ce710uf3664cbf858913fd@mail.gmail.com> Dear YH, excuse me, how about the irq_tables.c? should I modify it like tyan/s2882 did. printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 }; pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); pirq_info++; slot_num++; 2006/6/20, Lu, Yinghai : > > You need to update the entries at mptable.c for your slots or onboard > pci device. > > > > YH > > > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Wed Jun 21 04:13:49 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Tue, 20 Jun 2006 19:13:49 -0700 Subject: [LinuxBIOS] New guy in LinuxBios Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> Actually the irqtable entries is only for peer root pci bus scan when mptable is used. So you need to make sure mptable is right, and put entries for hypertransport chain other than on bus0. YH ________________________________ From: vincente.tsou at gmail.com [mailto:vincente.tsou at gmail.com] On Behalf Of Vincente Tsou Sent: Tuesday, June 20, 2006 7:05 PM To: Lu, Yinghai Cc: Stefan Reinauer; linuxbios at linuxbios.org Subject: Re: [LinuxBIOS] New guy in LinuxBios Dear YH, excuse me, how about the irq_tables.c? should I modify it like tyan/s2882 did. printk_debug("setting Onboard Broadcom NIC\n"); static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 }; pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); pirq_info++; slot_num++; 2006/6/20, Lu, Yinghai : You need to update the entries at mptable.c for your slots or onboard pci device. YH -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincentetsou at nexcom.com.tw Wed Jun 21 04:21:12 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Wed, 21 Jun 2006 10:21:12 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> Message-ID: <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> Dear YH, got it. Thanks for the information and your help. 2006/6/21, Lu, Yinghai : > > Actually the irqtable entries is only for peer root pci bus scan when > mptable is used. > > So you need to make sure mptable is right, and put entries for > hypertransport chain other than on bus0. > > > > YH > > > ------------------------------ > > *From:* vincente.tsou at gmail.com [mailto:vincente.tsou at gmail.com] *On > Behalf Of *Vincente Tsou > *Sent:* Tuesday, June 20, 2006 7:05 PM > *To:* Lu, Yinghai > *Cc:* Stefan Reinauer; linuxbios at linuxbios.org > > *Subject:* Re: [LinuxBIOS] New guy in LinuxBios > > > > Dear YH, > > > > excuse me, how about the irq_tables.c? > > should I modify it like tyan/s2882 did. > > > > printk_debug("setting Onboard Broadcom NIC\n"); > static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 }; > pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); > write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, 0x2, > 0xdef8, 0, 0, 0, 0, 0, 0); > pirq_info++; slot_num++; > > > > > 2006/6/20, Lu, Yinghai : > > You need to update the entries at mptable.c for your slots or onboard pci > device. > > > > YH > > > > > > > -- > Best Regards, > Vincente Tsou > > Engineer > R/D, S/W Dept. > NEXCOM International Co. > Tel: 886-2-82280606 Ext. 3205 > Fax: 886-2-82280506 > E-mail: vincentetsou at nexcom.com.tw > Web: http://www.nexcom.com.tw/ > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rajkumars at asianetindia.com Wed Jun 21 14:27:08 2006 From: rajkumars at asianetindia.com (Rajkumar S) Date: Wed, 21 Jun 2006 17:57:08 +0530 Subject: [LinuxBIOS] Buying a new board for LinuxBios Message-ID: <44993B1C.6040105@asianetindia.com> Hi, I am planning to buy a new board for a tiny cluster using Clustermatic. I am looking for a quard processor board, Which one would you suggest to buy so that I can use linuxbios on them for Clustermatic? I heard that tyan let's you buy board with linuxbios, is it true? I did not find any mention of it in their web site. with warm regards, raj From stepan at coresystems.de Wed Jun 21 14:44:27 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Wed, 21 Jun 2006 14:44:27 +0200 Subject: [LinuxBIOS] Buying a new board for LinuxBios In-Reply-To: <44993B1C.6040105@asianetindia.com> References: <44993B1C.6040105@asianetindia.com> Message-ID: <20060621124427.GA25851@coresystems.de> Hello Rajkumar, Sorry for being curious, are you named after the "annavru", btw? > I am planning to buy a new board for a tiny cluster using Clustermatic. I am looking for a > quard processor board, Which one would you suggest to buy so that I can use linuxbios on > them for Clustermatic? I heard that tyan let's you buy board with linuxbios, is it true? I > did not find any mention of it in their web site. If you buy Tyan, you have a pretty good chance to get LinuxBIOS running on the boards. The S4880 and S4882 are the two Quad boards supported from Tyan. There's another Quad board from Iwill which is equal to, or at least very similar the the agami aruma board. Otoh, if you are going to get a couple of nodes anyways for a cluster, you might want to go with the cheaper 2cpu (and maybe dualcore) systems. Stefan -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From yinghai.lu at amd.com Wed Jun 21 19:08:19 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Wed, 21 Jun 2006 10:08:19 -0700 Subject: [LinuxBIOS] Buying a new board for LinuxBios Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FED@ssvlexmb2.amd.com> FYI S4881, and S4885 can be used too. S4881 have ck804+amd8131, and S4885 have 2 ck804. You can get source code ball for them from Tyan if you buy the MBs. Arima has one four way MB with serverworks chipset too. (SW500). --- LinuxBIOS porting is done too. All above MBs have PCI Express Slot. The Arima sw500 even have Infiband chip onboard if you like. SuperMicro has similar four way MBs with Nvidia chipset or serverworks chipset. http://www.supermicro.com/aplus YH -----Original Message----- From: linuxbios-bounces at linuxbios.org [mailto:linuxbios-bounces at linuxbios.org] On Behalf Of Stefan Reinauer Sent: Wednesday, June 21, 2006 5:44 AM To: Rajkumar S Cc: linuxbios at linuxbios.org Subject: Re: [LinuxBIOS] Buying a new board for LinuxBios Hello Rajkumar, Sorry for being curious, are you named after the "annavru", btw? > I am planning to buy a new board for a tiny cluster using Clustermatic. I am looking for a > quard processor board, Which one would you suggest to buy so that I can use linuxbios on > them for Clustermatic? I heard that tyan let's you buy board with linuxbios, is it true? I > did not find any mention of it in their web site. If you buy Tyan, you have a pretty good chance to get LinuxBIOS running on the boards. The S4880 and S4882 are the two Quad boards supported from Tyan. There's another Quad board from Iwill which is equal to, or at least very similar the the agami aruma board. Otoh, if you are going to get a couple of nodes anyways for a cluster, you might want to go with the cheaper 2cpu (and maybe dualcore) systems. Stefan -- coresystems GmbH * Brahmsstr. 16 * D-79104 Freiburg i. Br. Tel.: +49 761 7668825 * Fax: +49 761 7664613 Email: info at coresystems.de * http://www.coresystems.de/ -- linuxbios mailing list linuxbios at linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios From fourstar10_2000 at yahoo.com Wed Jun 21 19:50:26 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Wed, 21 Jun 2006 10:50:26 -0700 (PDT) Subject: [LinuxBIOS] (no subject) Message-ID: <20060621175026.53159.qmail@web38906.mail.mud.yahoo.com> Hi all, I have LinuxBIOS booting the kernel on dual-core opteron w/ck804. Problem: the Kernel only sees 1 core, Processor #0 15:1 APIC version 16 Processor #1 15:1 APIC version 16 WARNING: NR_CPUS limit of 1 reached. Processor ignored. I/O APIC #2 Version 17 at 0xF4100000. Setting APIC routing to flat Processors: 1 Although: LinuxBIOS sees both cores, CPU #0 Initialized start_eip=0x00019000 Initializing CPU #1 Waiting for 1 CPUS to stop CPU: vendor AMD device 20f12 . . . CPU #1 Initialized I have started to merge the ACPI tables, they recompiled ok but, if I try to build with acpi_tables.o, dsdt.o, ssdt.o I get a compiler error about pm_base. pm_base is in southbridges...amd8111 and I don't have that. I only have the ck804. Do I need to write code for the ck804 so it has pm_base? And, what is pm_base? Is the kernel failing to see the dual cores because there are no ACPI tables built? Thank You, Steve --------------------------------- Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail Beta. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Wed Jun 21 19:57:21 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Wed, 21 Jun 2006 10:57:21 -0700 Subject: [LinuxBIOS] (no subject) Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FF0@ssvlexmb2.amd.com> You need to enable smp in your kernel. YH ________________________________ From: linuxbios-bounces at linuxbios.org [mailto:linuxbios-bounces at linuxbios.org] On Behalf Of steve yannalfo Sent: Wednesday, June 21, 2006 10:50 AM To: linuxbios at linuxbios.org Subject: [LinuxBIOS] (no subject) Hi all, I have LinuxBIOS booting the kernel on dual-core opteron w/ck804. Problem: the Kernel only sees 1 core, Processor #0 15:1 APIC version 16 Processor #1 15:1 APIC version 16 WARNING: NR_CPUS limit of 1 reached. Processor ignored. I/O APIC #2 Version 17 at 0xF4100000. Setting APIC routing to flat Processors: 1 Although: LinuxBIOS sees both cores, CPU #0 Initialized start_eip=0x00019000 Initializing CPU #1 Waiting for 1 CPUS to stop CPU: vendor AMD device 20f12 . . . CPU #1 Initialized I have started to merge the ACPI tables, they recompiled ok but, if I try to build with acpi_tables.o, dsdt.o, ssdt.o I get a compiler error about pm_base. pm_base is in southbridges...amd8111 and I don't have that. I only have the ck804. Do I need to write code for the ck804 so it has pm_base? And, what is pm_base? Is the kernel failing to see the dual cores because there are no ACPI tables built? Thank You, Steve ________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail Beta. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fourstar10_2000 at yahoo.com Wed Jun 21 20:47:29 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Wed, 21 Jun 2006 11:47:29 -0700 (PDT) Subject: [LinuxBIOS] 1 core Message-ID: <20060621184729.77207.qmail@web38906.mail.mud.yahoo.com> Thank you... that worked... my error. Can I use pm_base with the ck804, there is no link to that device for pm_base and the compiler complains when I try to create ACPI/fadt tables. Thank you, steve --------------------------------- Want to be your own boss? Learn how on Yahoo! Small Business. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fourstar10_2000 at yahoo.com Wed Jun 21 21:26:11 2006 From: fourstar10_2000 at yahoo.com (steve yannalfo) Date: Wed, 21 Jun 2006 12:26:11 -0700 (PDT) Subject: [LinuxBIOS] pcie irq's Message-ID: <20060621192611.32787.qmail@web38905.mail.mud.yahoo.com> The kernel complains::: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS I have them set in mptable.c for(i=0;i<4;i++) 0x10 + (2+i+4-sbdn%4)%4) 0x10 + (1+i+4-sbdn%4)%4) 0x10 + (0+i+4-sbdn%4)%4) 0x10 + (0+i)%4) And if I delete these lines in mptable.c i still get the same kernel compliant. Thank you, steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From stuge-linuxbios at cdy.org Wed Jun 21 23:15:08 2006 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Wed, 21 Jun 2006 23:15:08 +0200 Subject: [LinuxBIOS] pcie irq's In-Reply-To: <20060621192611.32787.qmail@web38905.mail.mud.yahoo.com> References: <20060621192611.32787.qmail@web38905.mail.mud.yahoo.com> Message-ID: <20060621211509.30374.qmail@cdy.org> On Wed, Jun 21, 2006 at 12:26:11PM -0700, steve yannalfo wrote: > I have them set in mptable.c > for(i=0;i<4;i++) > 0x10 + (2+i+4-sbdn%4)%4) > 0x10 + (1+i+4-sbdn%4)%4) > 0x10 + (0+i+4-sbdn%4)%4) > 0x10 + (0+i)%4) This looks like pseudocode, but anyway: check that the loop has curly braces. //Peter From scott at lubetech.com.au Thu Jun 22 03:00:26 2006 From: scott at lubetech.com.au (Scott) Date: Thu, 22 Jun 2006 11:00:26 +1000 Subject: [LinuxBIOS] Mini-ATX MB Message-ID: <009201c69597$42e286a0$0e0a640a@scottbedf9e644> Hi All, I am currently evaluating which MB to run with LinuxBIOS. Unfortunately Via's Eden are not powerful enough for my Spec. Tyan is too expensive and their boards are quite large. Has any one had anyluck with micro-ATX MB from AOPEN or Foxconn. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdegler at rumms.uni-mannheim.de Fri Jun 23 02:50:36 2006 From: pdegler at rumms.uni-mannheim.de (Philipp Degler) Date: Fri, 23 Jun 2006 02:50:36 +0200 Subject: [LinuxBIOS] irq_table/mptable problems? Message-ID: <200606230250.36355.pdegler@rumms.uni-mannheim.de> hi step by step I make my way booting a 2.6 kernel with linuxbios on an Iwill dk8htx board. I was able to compile a working rom and start loading a 2.6.13 kernel but something seems to be wrong with my irq_table/mptable settings. I first used initial cvs-settings. Finally I generated a new irq_table.c with getpir. But I still get a kernel panic. I think it must have something to do with the irq or mp settings. What can I do? This is what the kernel says: ------------------------------------------------------------------------------------------------------------- boot: hde2:/boot/static pci=noapci ro root=/dev/sda2 console=tty console=ttyS0,115200n8 hde: LBA48: ST380817AS ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Mounted ext2fs Found Linux version 2.6.13-15.8-default (geeko at buildhost) #2 SMP Thu Jun 22 15:56:16 CEST 2006 bzImage. Loading kernel... ok Jumping to entry point... Bootdata ok (command line is pci=noapci ro root=/dev/sda2 console=ttyS0,115200n8) Linux version 2.6.13-15.8-default (geeko at buildhost) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #2 SMP Thu Jun 22 15:56:16 CEST 2006 BIOS-provided physical RAM map: ?BIOS-e820: 0000000000000000 - 0000000000000e74 type 16 ?BIOS-e820: 0000000000000e74 - 00000000000a0000 (usable) ?BIOS-e820: 00000000000f0000 - 00000000000f0400 type 16 ?BIOS-e820: 0000000000100000 - 0000000080000000 (usable) ACPI: Unable to locate RSDP Scanning NUMA topology in Northbridge 24 Number of nodes 2 Node 0 MemBase 0000000000000000 Limit 000000003fffffff Node 1 MemBase 0000000040000000 Limit 000000007fffffff Using node hash shift of 24 Bootmem setup node 0 0000000000000000-000000003fffffff Bootmem setup node 1 0000000040000000-000000007fffffff Intel MultiProcessor Specification v1.4 ? ? Virtual Wire compatibility mode. OEM ID: IWILL ? ?<6>Product ID: DK8HTX ? ? ? <6>APIC at: 0xFEE00000 Processor #0 15:5 APIC version 16 Processor #1 15:5 APIC version 16 I/O APIC #2 Version 17 at 0xFEC00000. I/O APIC #3 Version 17 at 0xFD300000. I/O APIC #4 Version 17 at 0xFD301000. Setting APIC routing to flat Processors: 2 Allocating PCI resources starting at 80000000 (gap: 80000000:80000000) Checking aperture... CPU 0: aperture @ f8000000 size 64 MB CPU 1: aperture @ f8000000 size 64 MB Built 2 zonelists Kernel command line: pci=noapci ro root=/dev/sda2 console=ttyS0,115200n8 PCI: Unknown option `noapci' Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 2004.583 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 2053304k/2097152k available (4614k kernel code, 0k reserved, 2494k data, 288k init) Calibrating delay using timer specific routine.. 4018.02 BogoMIPS (lpj=8036053) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(1) -> Node 0 -> Core 0 mtrr: v2.0 (20020519) Using IO-APIC 2 Using IO-APIC 3 Using IO-APIC 4 Using local APIC timer interrupts. Detected 12.528 MHz APIC timer. Booting processor 1/2 APIC 0x1 Initializing CPU#1 Calibrating delay using timer specific routine.. 4009.46 BogoMIPS (lpj=8018924) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 1(1) -> Node 1 -> Core 0 AMD Opteron(tm) Processor 246 stepping 0a CPU 1: Syncing TSC to CPU 0. CPU 1: synchronized TSC with CPU 0 (last diff -626 cycles, maxerr 4804 cycles) Brought up 2 CPUs time.c: Using PIT/TSC based timekeeping. testing NMI watchdog ... OK. NET: Registered protocol family 16 PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI: Interpreter disabled. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Discovered primary peer bus 01 [IRQ] PCI: Discovered primary peer bus ff [IRQ] PCI->APIC IRQ transform: 0000:02:03.0[A] -> IRQ 193 PCI->APIC IRQ transform: 0000:02:04.0[A] -> IRQ 193 PCI->APIC IRQ transform: 0000:04:05.0[A] -> IRQ 177 PCI-DMA: Disabling IOMMU. PCI: Bridge: 0000:01:01.0 ? IO window: 1000-1fff ? MEM window: fd100000-fd2fffff ? PREFETCH window: disabled. PCI: Bridge: 0000:01:02.0 ? IO window: disabled. ? MEM window: disabled. ? PREFETCH window: disabled. PCI: Bridge: 0000:01:03.0 ? IO window: 2000-2fff ? MEM window: fc000000-fd0fffff ? PREFETCH window: disabled. IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Coda Kernel/Venus communications, v6.0.0, coda at cs.cmu.edu Installing knfsd (copyright (C) 1996 okir at monad.swb.de). subfs 0.9 ... testing michael_mic across pages PCI: MSI quirk detected. pci_msi_quirk set. PCI: MSI quirk detected. pci_msi_quirk set. PCI: No IRQ known for interrupt pin C of device 0000:04:06.0. Probably buggy MP table. atyfb: using auxiliary register aperture atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27] atyfb: vclk out of range atyfb: 8M SGRAM (1:1), 14.31818 MHz XTAL, 230 MHz PLL, 83 Mhz MCLK, 63 MHz XCLK Console: switching to colour frame buffer device 80x30 atyfb: fb0: ATY Mach64 frame buffer device on PCI vga16fb: mapped to 0xffff8100000a0000 fb1: VGA16 VGA frame buffer device Real Time Clock Driver v1.12 Non-volatile memory driver v1.2 hw_random: AMD768 system management I/O registers at 0x3000. hw_random hardware driver 1.0.0 loaded WDT driver for Acquire single board computer initialising. Acquire WDT: I/O address 0x0043 already in use WDT driver for Advantech single board computer initialising. Advantech WDT: initialized. timeout=60 sec (nowayout=0) ib700wdt: WDT driver for IB700 single board computer initialising. ib700wdt: failed to register misc device sbc60xxwdt: I/O address 0x0443 already in use machzwd: MachZ ZF-Logic Watchdog driver initializing. 0xffff machzwd: Watchdog using action = RESET can't misc_register on minor=130 eurwdt: can't misc_register on minor=130 w83877f_wdt: I/O address 0x0443 already in use WDT driver for the Winbond(TM) W83627HF Super I/O chip initialising. w83627hf WDT: cannot register miscdev on minor=130 (err=-16) sc520_wdt: cannot register miscdev on minor=130 (err=-16) alim7101_wdt: Steve Hill . alim7101_wdt: ALi M7101 PMU not present - WDT not set sc1200wdt: build 20020303<3>sc1200wdt: io parameter must be specified WDT driver for Wafer 5823 single board computer initialising. Wafer 5823 WDT: I/O address 0x0443 already in use cpu5wdt: misc_register failed usbcore: registered new driver pcwd_usb pcwd_usb: Berkshire USB-PC Watchdog driver v1.01 (15 Mar 2005) SoftDog: cannot register miscdev on minor=130 (err=-16) Linux agpgart interface v0.101 (c) Dave Jones ipmi message handler version v33 ipmi device interface version v33 IPMI System Interface driver version v33, KCS version v33, SMIC version v33, BT version v33 ? ? ACPI-0384: *** Warning: RSDP structure not found, AE_NOT_FOUND Flags=8 ACPI: System description tables not found ipmi_si: Trying "kcs" at I/O port 0xca2 ipmi_si: Trying "smic" at I/O port 0xca9 ipmi_si: Trying "bt" at I/O port 0xe4 ipmi_si: Unable to find any System Interface(s) IPMI Watchdog: driver version v33 Copyright (C) 2004 MontaVista Software - IPMI Powerdown via sys_reboot version v33. Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds). Hangcheck: Using monotonic_clock(). i8042.c: Can't read CTR while initializing i8042. Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A PCI: No IRQ known for interrupt pin B of device 0000:01:04.6. Probably buggy MP table. io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize loop: loaded (max 8 devices) pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (axboe at suse.de) and petero2 at telia.com nbd: registered device at major 43 loop: registered Twofish encryption Intel(R) PRO/1000 Network Driver - version 6.0.60-k2-NAPI Copyright (c) 1999-2005 Intel Corporation. e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection Ethernet Channel Bonding Driver: v2.6.3 (June 8, 2005) bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. Equalizer2002: Simon Janes (simon at ncm.com) and David S. Miller (davem at redhat.com) tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky Linux video capture interface: v1.00 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AMD8111: IDE controller at PCI slot 0000:01:04.1 AMD8111: chipset revision 3 AMD8111: not 100% native mode: will probe irqs later AMD8111: 0000:01:04.1 (rev 03) UDMA133 controller AMD8111: neither IDE port enabled (BIOS) ide-floppy driver 0.99.newide iscsi: registered transport (tcp) PCI: No IRQ known for interrupt pin B of device 0000:02:05.0. Probably buggy MP table. ata1: SATA max UDMA/100 cmd 0xFFFFC20000002080 ctl 0xFFFFC2000000208A bmdma 0xFFFFC20000002000 irq 0 ata2: SATA max UDMA/100 cmd 0xFFFFC200000020C0 ctl 0xFFFFC200000020CA bmdma 0xFFFFC20000002008 irq 0 ata3: SATA max UDMA/100 cmd 0xFFFFC20000002280 ctl 0xFFFFC2000000228A bmdma 0xFFFFC20000002200 irq 0 ata4: SATA max UDMA/100 cmd 0xFFFFC200000022C0 ctl 0xFFFFC200000022CA bmdma 0xFFFFC20000002208 irq 0 Unable to handle kernel NULL pointer dereference at 0000000000000010 RIP: {sysfs_hash_and_remove+14} PGD 0 Oops: 0000 [1] SMP CPU 0 Pid: 1, comm: swapper Not tainted 2.6.13-15.8-default RIP: 0010:[] {sysfs_hash_and_remove+14} RSP: 0000:ffff81007ffd9c18 ?EFLAGS: 00010282 RAX: ffffffff8072e3b8 RBX: ffffffff8072e3b8 RCX: ffffffff8080bb00 RDX: ffff810001f62370 RSI: ffffffff805f9847 RDI: 0000000000000000 RBP: ffff810001f62370 R08: 0000000000019b47 R09: 0000000000000037 R10: 0000000000000000 R11: 0000000000000004 R12: ffffffff8072e3b8 R13: 0000000000000000 R14: ffffffff805f9847 R15: ffff810001f61800 FS: ?0000000000000000(0000) GS:ffffffff808ab800(0000) knlGS:0000000000000000 CS: ?0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000010 CR3: 0000000000101000 CR4: 00000000000006e0 Process swapper (pid: 1, threadinfo ffff81007ffd8000, task ffff81003ffa94a0) Stack: ffffffff8072e3b8 ffff810001f62370 ffffffff8072e3b8 ffff810001f62380 ? ? ? ?ffffffff8072e300 ffffffff8038b9f8 ffff810001f62370 0000000000000001 ? ? ? ?ffff810001f62180 ffffc200000022ca Call Trace:{class_device_del+168} {class_device_unregister+33} ? ? ? ?{scsi_remove_host+125} {ata_host_remove+16} ? ? ? ?{ata_device_add+2389} {pci_conf1_read+223} ? ? ? ?{sil_init_one+944} {pci_device_probe+89} ? ? ? ?{driver_probe_device+123} {__driver_attach+73} ? ? ? ?{__driver_attach+0} {bus_for_each_dev+73} ? ? ? ?{bus_add_driver+152} {pci_register_driver+137} ? ? ? ?{init+482} {child_rip+8} ? ? ? ?{init+0} {child_rip+0} ? ? ? ? Code: 48 8b 6f 10 4c 8b a7 88 00 00 00 48 85 ed 0f 84 04 01 00 00 RIP {sysfs_hash_and_remove+14} RSP CR2: 0000000000000010 ?<0>Kernel panic - not syncing: Attempted to kill init! thx phil ? From jsimonetti at denit.net Thu Jun 22 16:24:24 2006 From: jsimonetti at denit.net (J. Simonetti) Date: Thu, 22 Jun 2006 16:24:24 +0200 Subject: [LinuxBIOS] Supermicro PDSMi and/or H8SSL-i Message-ID: <1150986264.25758.129.camel@jeroen.office.denit.net> Hello list, Any words on the availability of linuxbios on supermicro motherboards PDSMi and/or H8SSL-i http://www.supermicro.nl/products/motherboard/PD/E7230/PDSMi.cfm and http://www.supermicro.nl/Aplus/motherboard/Opteron/HT1000/H8SSL-i.cfm Respectively the Intel E7230 chipset and the ServerWorks HT1000 chipset. Kind regards, -- Met vriendelijke groeten, Jeroen Simonetti Network Manager Denit Internet Services BV Contactweg 131 1014 BJ Amsterdam Tel: +31 (0)20 337 2560 Fax: +31 (0)20 337 1802 * Fertility is hereditary. If your parents didn't have any children, neither will you. * From arturo.mann at gmail.com Fri Jun 23 01:53:14 2006 From: arturo.mann at gmail.com (Arturo Mann) Date: Thu, 22 Jun 2006 18:53:14 -0500 Subject: [LinuxBIOS] Tyan S2892 EtherBoot Message-ID: <601d22e40606221653o19761732kb587a03ed82c9c95@mail.gmail.com> Hello there, As i stated previously, i got my hands on a Tyan S2892, and it's included SST 49LF 8Mbit chip was botched, after a flashing, it went completely dead, I actually tried to prom it with a big-time universal 8-gang flash PLCC prommer today. Currently, there are no SST49LF 8Mbit replacements available in mexico (or any equivalents, actually), so, I got my hands on the best i could get on the spot, a 128KiB (Kilobyte) AMD chip which issupported by uniFlash. From rminnich at lanl.gov Fri Jun 23 16:50:38 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Fri, 23 Jun 2006 08:50:38 -0600 Subject: [LinuxBIOS] Tyan S2892 EtherBoot In-Reply-To: <601d22e40606221653o19761732kb587a03ed82c9c95@mail.gmail.com> References: <601d22e40606221653o19761732kb587a03ed82c9c95@mail.gmail.com> Message-ID: <449BFFBE.4000806@lanl.gov> Arturo Mann wrote: got two questions, and I would be very grateful if you lot > answered them: > 1. Can I fit LinuxBios with Etherboot to boot from SATA in 128KiB, it > does not matter how much i chunk out as long as the machine boots! I think you should be able to. > 2. If this is true, can someone PLEASE tell me how to build Etherboot > under x86_64? I think you have to go with a cross compiler. Or, can someone send Arturo a binary for now? thanks ron From arturo.mann at gmail.com Fri Jun 23 17:03:53 2006 From: arturo.mann at gmail.com (Arturo Mann) Date: Fri, 23 Jun 2006 10:03:53 -0500 Subject: [LinuxBIOS] Tyan S2892 EtherBoot In-Reply-To: <449BFFBE.4000806@lanl.gov> References: <601d22e40606221653o19761732kb587a03ed82c9c95@mail.gmail.com> <449BFFBE.4000806@lanl.gov> Message-ID: <601d22e40606230803n206ed5fes28b4ef0e939bdf95@mail.gmail.com> Well, it is good news i can smash linuxBios into that small space! if someone would be sending me a binary, I need to boot up with etherboot to detect my first SATA drive, which has the first partition (/dev/sda1) as ext2 with the kernel file name , the command line i use for the kernel is: root=/dev/sda3 quiet Thanks! Arturo On 6/23/06, Ronald G Minnich wrote: > > Arturo Mann wrote: > got two questions, and I would be very grateful if you lot > > answered them: > > 1. Can I fit LinuxBios with Etherboot to boot from SATA in 128KiB, it > > does not matter how much i chunk out as long as the machine boots! > > I think you should be able to. > > > 2. If this is true, can someone PLEASE tell me how to build Etherboot > > under x86_64? > > > I think you have to go with a cross compiler. Or, can someone send > Arturo a binary for now? > > thanks > > ron > -- ------------------------ ---- Stop the DRM! www.defectivebydesign.org ---- ---- Stop the TCPA from taking away OUR freedom! www.againsttcpa.com/ ----- ---- Arturo Mann, arturo.mann at gmail.com ---- -------------- next part -------------- An HTML attachment was scrubbed... URL: From arturo.mann at gmail.com Fri Jun 23 19:46:08 2006 From: arturo.mann at gmail.com (Arturo Mann) Date: Fri, 23 Jun 2006 12:46:08 -0500 Subject: [LinuxBIOS] Tyan S2892 EtherBoot In-Reply-To: <601d22e40606230803n206ed5fes28b4ef0e939bdf95@mail.gmail.com> References: <601d22e40606221653o19761732kb587a03ed82c9c95@mail.gmail.com> <449BFFBE.4000806@lanl.gov> <601d22e40606230803n206ed5fes28b4ef0e939bdf95@mail.gmail.com> Message-ID: <601d22e40606231046j735d5ff3u4a137029cb7116a4@mail.gmail.com> I have gotten the etherboot image built on rom-o-matic (using a pentium4, i tried but it complained about pci_init and just failed compilation, if anyone can tell me about this, it died at tg3 linkage) Anyway, now I have managed to prepare the tree for the s2892 following the s2881 tutorial, however, Make dies with: Horus s2892 # make if (cd normal; \ make linuxbios.rom)\ then true; else exit 1; fi; make[1]: Entering directory `/root/Source/LinuxBIOSv2/targets/tyan/s2892/s2892/normal' cp /root/Source/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb crt0.S gcc -Os -Wall -DARCH='i386' -DHAVE_MOVNTI='1' -DCROSS_COMPILE -DCC='gcc -m32' -DHOSTCC='gcc' -DOBJCOPY='objcopy --gap-fill 0xff' -DLINUXBIOS_VERSION='"1.1.8"' -DLINUXBIOS_BUILD='"Fri Jun 23 13:10:24 Local time zone must be set--see zic manual page 2006"' -DLINUXBIOS_COMPILE_TIME='"13:10:24"' -DLINUXBIOS_COMPILE_BY='"root"' -DLINUXBIOS_COMPILE_HOST='"Horus"' -DLINUXBIOS_COMPILE_DOMAIN='"artgraf.biz"' -DLINUXBIOS_COMPILER='"gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)"' -DLINUXBIOS_LINKER='"GNU ld version 2.16.1"' -DLINUXBIOS_ASSEMBLER='"GNU assembler version 2.16.1 (i686-pc-linux-gnu) using BFD version 2.16.1"' -DCONFIG_USE_INIT='0' -DHAVE_FALLBACK_BOOT='1' -DROM_IMAGE_SIZE='0x20000' -DPAYLOAD_SIZE='0x10000' -D_ROMBASE='0xfffa0000' -D_RESET='0xfffa0000' -D_EXCEPTION_VECTORS='0xfffa0100' -DSTACK_SIZE='0x2000' -DHEAP_SIZE='0x4000' -D_RAMBASE='0x4000' -DUSE_DCACHE_RAM='1' -DDCACHE_RAM_SIZE='0x1000' -DDCACHE_RAM_GLOBAL_VAR_SIZE='0x0' -DCONFIG_COMPRESS='1' -DCONFIG_UNCOMPRESSED='0' -DCONFIG_LB_MEM_TOPK='2048' -DHAVE_OPTION_TABLE='1' -DUSE_OPTION_TABLE='1' -DLB_CKS_RANGE_START='49' -DLB_CKS_RANGE_END='122' -DLB_CKS_LOC='123' -DCRT0='/root/Source/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb' -DDEBUG='1' -DCONFIG_CONSOLE_VGA='1' -DCONFIG_CONSOLE_VGA_MULTI='0' -DCONFIG_CONSOLE_VGA_ONBOARD_AT_FIRST='0' -DCONFIG_CONSOLE_BTEXT='0' -DCONFIG_CONSOLE_LOGBUF='0' -DCONFIG_CONSOLE_SROM='0' -DCONFIG_CONSOLE_SERIAL8250='1' -DDEFAULT_CONSOLE_LOGLEVEL='8' -DMAXIMUM_CONSOLE_LOGLEVEL='8' -DCONFIG_SERIAL_POST='0' -DTTYS0_BASE='0x3f8' -DTTYS0_BAUD='115200' -DTTYS0_LCS='0x3' -DMAINBOARD='/root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892' -DMAINBOARD_PART_NUMBER='"s2892"' -DMAINBOARD_VENDOR='"Tyan"' -DMAINBOARD_PCI_SUBSYSTEM_VENDOR_ID='4337' -DMAINBOARD_PCI_SUBSYSTEM_DEVICE_ID='0x2892' -DCONFIG_MAX_PCI_BUSES='255' -DCONFIG_SMP='1' -DCONFIG_MAX_CPUS='4' -DCONFIG_MAX_PHYSICAL_CPUS='2' -DCONFIG_LOGICAL_CPUS='1' -DSERIAL_CPU_INIT='1' -DAPIC_ID_OFFSET='0' -DENABLE_APIC_EXT_ID='0' -DLIFT_BSP_APIC_ID='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' -DCONFIG_ROM_STREAM_START='0xfff90000' -DCONFIG_COMPRESSED_ROM_STREAM='0' -DCONFIG_FS_STREAM='0' -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 console=tty0 console=ttyS0,115200"' -DUSE_WATCHDOG_ON_BOOT='0' -DCONFIG_HYPERTRANSPORT_PLUGIN_SUPPORT='1' -DCONFIG_AGP_PLUGIN_SUPPORT='1' -DCONFIG_CARDBUS_PLUGIN_SUPPORT='1' -DCONFIG_PCIX_PLUGIN_SUPPORT='1' -DCONFIG_PCIEXP_PLUGIN_SUPPORT='1' -DCONFIG_IDE='0' -DIDE_BOOT_DRIVE='0' -DIDE_OFFSET='0' -DCONFIG_CHIP_NAME='0' -DHAVE_INIT_TIMER='1' -DMAX_REBOOT_CNT='3' -DFAKE_SPDROM='0' -DHAVE_ACPI_TABLES='0' -DACPI_SSDTX_NUM='0' -DHT_CHAIN_UNITID_BASE='0' -DHT_CHAIN_END_UNITID_BASE='32' -DSB_HT_CHAIN_UNITID_OFFSET_ONLY='0' -DK8_SB_HT_CHAIN_ON_BUS0='2' -DK8_HW_MEM_HOLE_SIZEK='1048576' -DK8_HW_MEM_HOLE_SIZE_AUTO_INC='0' -DK8_HT_FREQ_1G_SUPPORT='1' -DCONFIG_PCI_ROM_RUN='1' -DCONFIG_PCI_64BIT_PREF_MEM='0' -DHAVE_MP_TABLE='1' -DHAVE_PIRQ_TABLE='1' -DUSE_FALLBACK_IMAGE='0' -DHAVE_HARD_RESET='1' -DIRQ_SLOT_COUNT='11' -DCONFIG_IOAPIC='1' -DFALLBACK_SIZE='0x40000' -DROM_SIZE='0x70000' -DROM_SECTION_SIZE='0x30000' -DROM_SECTION_OFFSET='0x0' -DXIP_ROM_SIZE='0x20000' -DXIP_ROM_BASE='0xfffa0000' -DLINUXBIOS_EXTRA_VERSION='"_s2892_Normal"' -DCONFIG_GDB_STUB='0' -DMAINBOARD_POWER_ON_AFTER_POWER_FAIL='MAINBOARD_POWER_ON' -DDCACHE_RAM_BASE='0xcf000' -DCONFIG_UDELAY_IO='0' -DCONFIG_UDELAY_TSC='0' -DCONFIG_TSC_X86RDTSC_CALIBRATE_WITH_TIMER2='0' -DAGP_APERTURE_SIZE='0x4000000' /root/Source/LinuxBIOSv2/util/options/build_opt_tbl.c -o build_opt_tbl ./build_opt_tbl -b --config /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cmos.layout --header option_table.h gcc -m32 -I/root/Source/LinuxBIOSv2/src -I. -I/root/Source/LinuxBIOSv2/src/include -I/root/Source/LinuxBIOSv2/src/arch/i386/include -I/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include -DARCH='i386' -DHAVE_MOVNTI='1' -DCROSS_COMPILE -DCC='gcc -m32' -DHOSTCC='gcc' -DOBJCOPY='objcopy --gap-fill 0xff' -DLINUXBIOS_VERSION='"1.1.8"' -DLINUXBIOS_BUILD='"Fri Jun 23 13:10:24 Local time zone must be set--see zic manual page 2006"' -DLINUXBIOS_COMPILE_TIME='"13:10:24"' -DLINUXBIOS_COMPILE_BY='"root"' -DLINUXBIOS_COMPILE_HOST='"Horus"' -DLINUXBIOS_COMPILE_DOMAIN='"artgraf.biz"' -DLINUXBIOS_COMPILER='"gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)"' -DLINUXBIOS_LINKER='"GNU ld version 2.16.1"' -DLINUXBIOS_ASSEMBLER='"GNU assembler version 2.16.1 (i686-pc-linux-gnu) using BFD version 2.16.1"' -DCONFIG_USE_INIT='0' -DHAVE_FALLBACK_BOOT='1' -DROM_IMAGE_SIZE='0x20000' -DPAYLOAD_SIZE='0x10000' -D_ROMBASE='0xfffa0000' -D_RESET='0xfffa0000' -D_EXCEPTION_VECTORS='0xfffa0100' -DSTACK_SIZE='0x2000' -DHEAP_SIZE='0x4000' -D_RAMBASE='0x4000' -DUSE_DCACHE_RAM='1' -DDCACHE_RAM_SIZE='0x1000' -DDCACHE_RAM_GLOBAL_VAR_SIZE='0x0' -DCONFIG_COMPRESS='1' -DCONFIG_UNCOMPRESSED='0' -DCONFIG_LB_MEM_TOPK='2048' -DHAVE_OPTION_TABLE='1' -DUSE_OPTION_TABLE='1' -DLB_CKS_RANGE_START='49' -DLB_CKS_RANGE_END='122' -DLB_CKS_LOC='123' -DCRT0='/root/Source/LinuxBIOSv2/src/arch/i386/init/crt0.S.lb' -DDEBUG='1' -DCONFIG_CONSOLE_VGA='1' -DCONFIG_CONSOLE_VGA_MULTI='0' -DCONFIG_CONSOLE_VGA_ONBOARD_AT_FIRST='0' -DCONFIG_CONSOLE_BTEXT='0' -DCONFIG_CONSOLE_LOGBUF='0' -DCONFIG_CONSOLE_SROM='0' -DCONFIG_CONSOLE_SERIAL8250='1' -DDEFAULT_CONSOLE_LOGLEVEL='8' -DMAXIMUM_CONSOLE_LOGLEVEL='8' -DCONFIG_SERIAL_POST='0' -DTTYS0_BASE='0x3f8' -DTTYS0_BAUD='115200' -DTTYS0_LCS='0x3' -DMAINBOARD='/root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892' -DMAINBOARD_PART_NUMBER='"s2892"' -DMAINBOARD_VENDOR='"Tyan"' -DMAINBOARD_PCI_SUBSYSTEM_VENDOR_ID='4337' -DMAINBOARD_PCI_SUBSYSTEM_DEVICE_ID='0x2892' -DCONFIG_MAX_PCI_BUSES='255' -DCONFIG_SMP='1' -DCONFIG_MAX_CPUS='4' -DCONFIG_MAX_PHYSICAL_CPUS='2' -DCONFIG_LOGICAL_CPUS='1' -DSERIAL_CPU_INIT='1' -DAPIC_ID_OFFSET='0' -DENABLE_APIC_EXT_ID='0' -DLIFT_BSP_APIC_ID='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' -DCONFIG_ROM_STREAM_START='0xfff90000' -DCONFIG_COMPRESSED_ROM_STREAM='0' -DCONFIG_FS_STREAM='0' -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 console=tty0 console=ttyS0,115200"' -DUSE_WATCHDOG_ON_BOOT='0' -DCONFIG_HYPERTRANSPORT_PLUGIN_SUPPORT='1' -DCONFIG_AGP_PLUGIN_SUPPORT='1' -DCONFIG_CARDBUS_PLUGIN_SUPPORT='1' -DCONFIG_PCIX_PLUGIN_SUPPORT='1' -DCONFIG_PCIEXP_PLUGIN_SUPPORT='1' -DCONFIG_IDE='0' -DIDE_BOOT_DRIVE='0' -DIDE_OFFSET='0' -DCONFIG_CHIP_NAME='0' -DHAVE_INIT_TIMER='1' -DMAX_REBOOT_CNT='3' -DFAKE_SPDROM='0' -DHAVE_ACPI_TABLES='0' -DACPI_SSDTX_NUM='0' -DHT_CHAIN_UNITID_BASE='0' -DHT_CHAIN_END_UNITID_BASE='32' -DSB_HT_CHAIN_UNITID_OFFSET_ONLY='0' -DK8_SB_HT_CHAIN_ON_BUS0='2' -DK8_HW_MEM_HOLE_SIZEK='1048576' -DK8_HW_MEM_HOLE_SIZE_AUTO_INC='0' -DK8_HT_FREQ_1G_SUPPORT='1' -DCONFIG_PCI_ROM_RUN='1' -DCONFIG_PCI_64BIT_PREF_MEM='0' -DHAVE_MP_TABLE='1' -DHAVE_PIRQ_TABLE='1' -DUSE_FALLBACK_IMAGE='0' -DHAVE_HARD_RESET='1' -DIRQ_SLOT_COUNT='11' -DCONFIG_IOAPIC='1' -DFALLBACK_SIZE='0x40000' -DROM_SIZE='0x70000' -DROM_SECTION_SIZE='0x30000' -DROM_SECTION_OFFSET='0x0' -DXIP_ROM_SIZE='0x20000' -DXIP_ROM_BASE='0xfffa0000' -DLINUXBIOS_EXTRA_VERSION='"_s2892_Normal"' -DCONFIG_GDB_STUB='0' -DMAINBOARD_POWER_ON_AFTER_POWER_FAIL='MAINBOARD_POWER_ON' -DDCACHE_RAM_BASE='0xcf000' -DCONFIG_UDELAY_IO='0' -DCONFIG_UDELAY_TSC='0' -DCONFIG_TSC_X86RDTSC_CALIBRATE_WITH_TIMER2='0' -DAGP_APERTURE_SIZE='0x4000000' /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c -Os -nostdinc -nostdlib -fno-builtin -Wall -c -S -o auto.inc In file included from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:14: /root/Source/LinuxBIOSv2/src/ram/ramtest.c: In function `ram_check': /root/Source/LinuxBIOSv2/src/ram/ramtest.c:97: warning: unused variable `result' In file included from /root/Source/LinuxBIOSv2/src/cpu/amd/mtrr/amd_earlymtrr.c:5, from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:32: /root/Source/LinuxBIOSv2/src/cpu/x86/mtrr/earlymtrr.c: In function `do_early_mtrr_init': /root/Source/LinuxBIOSv2/src/cpu/x86/mtrr/earlymtrr.c:73: warning: unused variable `cr0' In file included from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:32: /root/Source/LinuxBIOSv2/src/cpu/amd/mtrr/amd_earlymtrr.c: In function `do_amd_early_mtrr_init': /root/Source/LinuxBIOSv2/src/cpu/amd/mtrr/amd_earlymtrr.c:18: warning: unused variable `cr0' In file included from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:59: /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/raminit.c:605:2: warning: #warning "FIXME implement a better test for opterons" In file included from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:59: /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/raminit.c: In function `set_dimm_map': /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/raminit.c:792: warning: unused variable `dch' In file included from /root/Source/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c:18, from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:82: /root/Source/LinuxBIOSv2/src/lib/nrv2b.c: In function `unrv2b': /root/Source/LinuxBIOSv2/src/lib/nrv2b.c:38: warning: unused variable `file_len' In file included from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:82: /root/Source/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c: In function `copy_and_run': /root/Source/LinuxBIOSv2/src/cpu/amd/car/copy_and_run.c:25: warning: unused variable `ilen' In file included from /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:84: /root/Source/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c: In function `post_cache_as_ram': /root/Source/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c:60: warning: passing arg 1 of `memcopy' makes pointer from integer without a cast /root/Source/LinuxBIOSv2/src/cpu/amd/car/post_cache_as_ram.c:60: warning: passing arg 2 of `memcopy' makes pointer from integer without a cast /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c: In function `real_main': /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:214: error: `bsp_apicid' undeclared (first use in this function) /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:214: error: (Each undeclared identifier is reported only once /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c:214: error: for each function it appears in.) /root/Source/LinuxBIOSv2/src/mainboard/tyan/s2892/cache_as_ram_auto.c: At top level: /root/Source/LinuxBIOSv2/src/arch/i386/include/arch/romcc_io.h:182: warning: 'pci_locate_device_on_bus' defined but not used /root/Source/LinuxBIOSv2/src/pc80/mc146818rtc_early.c:51: warning: 'last_boot_normal' defined but not used /root/Source/LinuxBIOSv2/src/pc80/mc146818rtc_early.c:58: warning: 'do_normal_boot' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:69: warning: 'print_emerg_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:70: warning: 'print_emerg_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:71: warning: 'print_emerg_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:75: warning: 'print_alert_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:76: warning: 'print_alert_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:77: warning: 'print_alert_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:78: warning: 'print_alert_hex32' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:79: warning: 'print_alert' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:81: warning: 'print_crit_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:82: warning: 'print_crit_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:83: warning: 'print_crit_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:84: warning: 'print_crit_hex32' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:85: warning: 'print_crit' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:87: warning: 'print_err_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:88: warning: 'print_err_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:89: warning: 'print_err_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:93: warning: 'print_warning_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:94: warning: 'print_warning_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:95: warning: 'print_warning_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:96: warning: 'print_warning_hex32' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:97: warning: 'print_warning' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:99: warning: 'print_notice_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:100: warning: 'print_notice_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:101: warning: 'print_notice_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:102: warning: 'print_notice_hex32' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:103: warning: 'print_notice' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:105: warning: 'print_info_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:106: warning: 'print_info_hex8' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:107: warning: 'print_info_hex16' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:108: warning: 'print_info_hex32' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:117: warning: 'print_spew_char' defined but not used /root/Source/LinuxBIOSv2/src/arch/i386/lib/console.c:119: warning: 'print_spew_hex16' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/incoherent_ht.c:83: warning: 'ht_lookup_host_capability' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/incoherent_ht.c:596: warning: 'ht_setup_chain' defined but not used /root/Source/LinuxBIOSv2/src/southbridge/nvidia/ck804/ck804_smbus.h:25: warning: 'smbus_wait_until_ready' defined but not used /root/Source/LinuxBIOSv2/src/southbridge/nvidia/ck804/ck804_smbus.h:57: warning: 'do_smbus_recv_byte' defined but not used /root/Source/LinuxBIOSv2/src/southbridge/nvidia/ck804/ck804_smbus.h:93: warning: 'do_smbus_send_byte' defined but not used /root/Source/LinuxBIOSv2/src/southbridge/nvidia/ck804/ck804_early_smbus.c:32: warning: 'smbus_write_byte' defined but not used /root/Source/LinuxBIOSv2/src/cpu/x86/lapic/boot_cpu.c:4: warning: 'boot_cpu' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/reset_test.c:11: warning: 'cpu_init_detected' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/reset_test.c:22: warning: 'bios_reset_detected' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/reset_test.c:30: warning: 'cold_reset_detected' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/reset_test.c:75: warning: 'get_sblk' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/reset_test.c:83: warning: 'get_sbbusn' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:33: warning: 'print_pci_devices' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:91: warning: 'dump_pci_devices' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:116: warning: 'dump_pci_devices_on_bus' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:141: warning: 'dump_spd_registers' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:223: warning: 'dump_smbus_registers' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:264: warning: 'dump_io_resources' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/debug.c:299: warning: 'dump_mem' defined but not used /root/Source/LinuxBIOSv2/src/cpu/x86/mtrr/earlymtrr.c:30: warning: 'disable_var_mtrr' defined but not used /root/Source/LinuxBIOSv2/src/cpu/x86/mtrr/earlymtrr.c:55: warning: 'cache_lbmem' defined but not used /root/Source/LinuxBIOSv2/src/cpu/x86/mtrr/earlymtrr.c:100: warning: 'early_mtrr_init' defined but not used /root/Source/LinuxBIOSv2/src/cpu/x86/mtrr/earlymtrr.c:121: warning: 'early_mtrr_init_detected' defined but not used /root/Source/LinuxBIOSv2/src/cpu/amd/mtrr/amd_earlymtrr.c:67: warning: 'amd_early_mtrr_init' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/setup_resource_map.c:4: warning: 'setup_resource_map_offset' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/setup_resource_map.c:46: warning: 'setup_resource_map_x_offset' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/setup_resource_map.c:231: warning: 'setup_iob_resource_map' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/setup_resource_map.c:267: warning: 'setup_io_resource_map' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/raminit.c:2425: warning: 'mem_inited' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/raminit.c:2454: warning: 'fill_mem_ctrl' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/coherent_ht_car.c:164: warning: 'enable_apic_ext_id' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/coherent_ht_car.c:387: warning: 'get_linkn_last' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/coherent_ht_car.c:395: warning: 'get_linkn_last_count' defined but not used /root/Source/LinuxBIOSv2/src/northbridge/amd/amdk8/coherent_ht_car.c:493: warning: 'clear_temp_row' defined but not used /root/Source/LinuxBIOSv2/src/cpu/amd/model_fxx/init_cpus.c:151: warning: 'wait_all_aps_started' defined but not used /root/Source/LinuxBIOSv2/src/cpu/amd/model_fxx/init_cpus.c:161: warning: 'allow_all_aps_stop' defined but not used make[1]: *** [auto.inc] Error 1 make[1]: Leaving directory `/root/Source/LinuxBIOSv2/targets/tyan/s2892/s2892/normal' make: *** [normal/linuxbios.rom] Error 1 Horus s2892 # Note the bsd_apicid error Can anyone tell me how to fix this and build this damned thing? On 6/23/06, Arturo Mann wrote: > > Well, it is good news i can smash linuxBios into that small space! > if someone would be sending me a binary, I need to boot up with etherboot > to detect my first SATA drive, > which has the first partition (/dev/sda1) as ext2 with the kernel file > name , the command line i use for > the kernel is: > root=/dev/sda3 quiet > > Thanks! > Arturo > > > On 6/23/06, Ronald G Minnich wrote: > > > > Arturo Mann wrote: > > got two questions, and I would be very grateful if you lot > > > answered them: > > > 1. Can I fit LinuxBios with Etherboot to boot from SATA in 128KiB, it > > > does not matter how much i chunk out as long as the machine boots! > > > > I think you should be able to. > > > > > 2. If this is true, can someone PLEASE tell me how to build Etherboot > > > under x86_64? > > > > > > I think you have to go with a cross compiler. Or, can someone send > > Arturo a binary for now? > > > > thanks > > > > ron > > > > > > -- > ------------------------ > ---- Stop the DRM! www.defectivebydesign.org ---- > > ---- Stop the TCPA from taking away OUR freedom! www.againsttcpa.com/ > ----- > ---- Arturo Mann, arturo.mann at gmail.com ---- > -- ------------------------ ---- Stop the DRM! www.defectivebydesign.org ---- ---- Stop the TCPA from taking away OUR freedom! www.againsttcpa.com/ ----- ---- Arturo Mann, arturo.mann at gmail.com ---- -------------- next part -------------- An HTML attachment was scrubbed... URL: From stepan at coresystems.de Fri Jun 23 22:23:21 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 23 Jun 2006 22:23:21 +0200 Subject: [LinuxBIOS] Tyan S2892 EtherBoot In-Reply-To: <601d22e40606231046j735d5ff3u4a137029cb7116a4@mail.gmail.com> References: <601d22e40606221653o19761732kb587a03ed82c9c95@mail.gmail.com> <449BFFBE.4000806@lanl.gov> <601d22e40606230803n206ed5fes28b4ef0e939bdf95@mail.gmail.com> <601d22e40606231046j735d5ff3u4a137029cb7116a4@mail.gmail.com> Message-ID: <20060623202321.GA5695@coresystems.de> * Arturo Mann [060623 19:46]: > I have gotten the etherboot image built on rom-o-matic (using a pentium4, i > tried but it complained about pci_init and just failed compilation, if anyone > can tell me about this, it died at tg3 linkage) > Anyway, now I have managed to prepare the tree for the s2892 following the > s2881 tutorial, however, Make dies with: There was an error in the s2892 specific part of the source tree. Its fixed now and the tree compiles. No guaranty that it actually works though ;) Stefan -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From knuty at skolelinux.no Sun Jun 25 19:10:23 2006 From: knuty at skolelinux.no (Knut Yrvin) Date: Sun, 25 Jun 2006 19:10:23 +0200 Subject: [LinuxBIOS] Possibility to get a OLPC developer's board [Reply-to: debian-custom-list] Message-ID: <200606251910.23641.knuty@skolelinux.no> First of all I'm sorry to cross-post this request. But I need urgent reply to know if somebody wants to team up in a project making Debian ready for the One Laptop per Child hardware. If there is somebody interested applying for OLPC developer board to make things work, please reply to debian-custom at lists.debian.org. My project proposal: After a tip from Walter Bender at MIT, I was subscribing to the devel-boards list for the One Laptop per Child project. Walter is president, software and content, of the One Laptop per Child foundation. My subscription was forwarded to the list moderator for approval. Then i got a nice e-mail from Jim Gettys. He wrote that if my interest in the list is to get a developer's board, then please follow the following instructions (look at the bootom): http://wiki.laptop.org/index.php/Developers_Program This will result in a developer's board if the request is at all reasonable, and you will be added to the mailing list (which is meant to be low volume announcements for people with boards). I wrote some suggestions for a plan to get the OLPC-machine up running April 5th 2006: http://lists.debian.org/debian-edu/2006/04/msg00016.html So people, I could apply for boards to realize this plan. (The plan is not at all finale, but a suggestion): 1. To make the Debian installer work with OLPC-machines 2. To make bare bone Debian run with network connectivety in a mesh network (IPv6) 3. Make the power management work 4. To make X and a window manager with simplified debloated desktop But with no developers interested doing the development, I see no reason for applying for boards. So it depends on what the Debian Edu and Debian contributers are interested in. It's a considerable job tailoring the different subsystem in Debian to OLPC hardware. The installer has to be tailored, the network mesh net support has to work, simplified debloated desktop has to be configured, and the power management has to work. We have done interesting things with Custom Debian Distributions and Debian Installer in the Skolelinux / Debian Edu environment before. It seems to me that more people have joined the Skolelinux / Debian Edu project. I believe the One Laptop per Child is important for Debian, and we should do this development. - What do you think about this suggestions? - Who are interested to develop tailored Debian Edu for OLPC-machines? Regards Knut Yrvin Project manager Skolelinux Norway From vincentetsou at nexcom.com.tw Mon Jun 26 04:21:16 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Mon, 26 Jun 2006 10:21:16 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> Message-ID: <41fde3420606251921l6a375d53y12cdc2030768d58e@mail.gmail.com> Hi YH, Thanks again for your help. Now I can active all devices in my LinuxBios, it almost done except VGA function. I appended a 36k VGA option rom to LinuxBios, and enable Options about VGA. And I got the halt_sys message: PCI: 04:02.0 init rom address for PCI: 04:02.0 = fff80000 copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes entering emulator halt_sys: file /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, line 4387 PCI: 01:04.0 init then, I can see something output, but the output is like snow screen and I can't read anything. I think it is working in the wrong mode. When I made a blind type 'root' and password, I can login the Linux, and then the screen became clear. (work fine) I wonder how to fix the problem? is the halt_sys message normal ? I also got another question, could it possible boot to MS-DOS floppy/USB disk. The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to support it? 2006/6/21, Vincente Tsou : > > Dear YH, > > got it. > > Thanks for the information and your help. > > > > 2006/6/21, Lu, Yinghai : > > > Actually the irqtable entries is only for peer root pci bus scan when > > mptable is used. > > > > So you need to make sure mptable is right, and put entries for > > hypertransport chain other than on bus0. > > > > > > > > YH > > > > > > ------------------------------ > > > > *From:* vincente.tsou at gmail.com [mailto:vincente.tsou at gmail.com] *On > > Behalf Of *Vincente Tsou > > *Sent:* Tuesday, June 20, 2006 7:05 PM > > *To:* Lu, Yinghai > > *Cc: *Stefan Reinauer; linuxbios at linuxbios.org > > > > *Subject:* Re: [LinuxBIOS] New guy in LinuxBios > > > > > > > > Dear YH, > > > > > > > > excuse me, how about the irq_tables.c? > > > > should I modify it like tyan/s2882 did. > > > > > > > > printk_debug("setting Onboard Broadcom NIC\n"); > > static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 > > }; > > pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); > > write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, > > 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); > > pirq_info++; slot_num++; > > > > > > > > > > 2006/6/20, Lu, Yinghai : > > > > You need to update the entries at mptable.c for your slots or onboard > > pci device. > > > > > > > > YH > > > > > > > > > > > > > > -- > > Best Regards, > > Vincente Tsou > > > > Engineer > > R/D, S/W Dept. > > NEXCOM International Co. > > Tel: 886-2-82280606 Ext. 3205 > > Fax: 886-2-82280506 > > E-mail: vincentetsou at nexcom.com.tw > > Web: http://www.nexcom.com.tw/ > > > > > > -- > Best Regards, > Vincente Tsou > > Engineer > R/D, S/W Dept. > NEXCOM International Co. > Tel: 886-2-82280606 Ext. 3205 > Fax: 886-2-82280506 > E-mail: vincentetsou at nexcom.com.tw > Web: http://www.nexcom.com.tw/ > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghailu at gmail.com Mon Jun 26 07:36:21 2006 From: yinghailu at gmail.com (yhlu) Date: Sun, 25 Jun 2006 22:36:21 -0700 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <41fde3420606251921l6a375d53y12cdc2030768d58e@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> <41fde3420606251921l6a375d53y12cdc2030768d58e@mail.gmail.com> Message-ID: <2ea3fae10606252236q5917cc7bubd3e77f6affeb318@mail.gmail.com> the snow screen only happened when I was debugging the onboard VGA support. So i move the CPU init before other pci device init call. That is something related to mtrr setting around [0xa0000-0xb0000) the font buffer. the halt_sys display is normal...it means the vga option rom is executed successfully. you can use filo in etherboot to boot from usb stick. YH On 6/25/06, Vincente Tsou wrote: > > Hi YH, > > Thanks again for your help. > > Now I can active all devices in my LinuxBios, it almost done except VGA > function. > > I appended a 36k VGA option rom to LinuxBios, and enable Options about VGA. > > And I got the halt_sys message: > > PCI: 04:02.0 init > rom address for PCI: 04:02.0 = fff80000 > copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes > entering emulator > halt_sys: file > /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, > line 4387 > PCI: 01:04.0 init > > then, I can see something output, but the output is like snow screen and I > can't read anything. > I think it is working in the wrong mode. > > When I made a blind type 'root' and password, I can login the Linux, and > then the screen became clear. (work fine) > > I wonder how to fix the problem? is the halt_sys message normal ? > > I also got another question, could it possible boot to MS-DOS floppy/USB > disk. > The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to support > it? > > > > 2006/6/21, Vincente Tsou : > > > > > > Dear YH, > > > > got it. > > > > Thanks for the information and your help. > > > > > > > > 2006/6/21, Lu, Yinghai : > > > > > > > > > > > > > > > > > > > > Actually the irqtable entries is only for peer root pci bus scan when > mptable is used. > > > > > > So you need to make sure mptable is right, and put entries for > hypertransport chain other than on bus0. > > > > > > > > > > > > YH > > > > > > > > > > > > ________________________________ > > > > > > > From: vincente.tsou at gmail.com [mailto:vincente.tsou at gmail.com] On Behalf > Of Vincente Tsou > > > Sent: Tuesday, June 20, 2006 7:05 PM > > > To: Lu, Yinghai > > > Cc: Stefan Reinauer; linuxbios at linuxbios.org > > > > > > Subject: Re: [LinuxBIOS] New guy in LinuxBios > > > > > > > > > > > > > > > > > > > > > > > > Dear YH, > > > > > > > > > > > > > > > > > > > > > excuse me, how about the irq_tables.c? > > > > > > > > > should I modify it like tyan/s2882 did. > > > > > > > > > > > > > > > > > > printk_debug("setting Onboard Broadcom NIC\n"); > > > static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 > }; > > > pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); > > > write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, > 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); > > > pirq_info++; slot_num++; > > > > > > > > > > > > > > > > > > 2006/6/20, Lu, Yinghai : > > > > > > > > > > > > > > > You need to update the entries at mptable.c for your slots or onboard > pci device. > > > > > > > > > > > > YH > > > > > > > > > > > > > > > > > > > > > -- > > > Best Regards, > > > Vincente Tsou > > > > > > Engineer > > > R/D, S/W Dept. > > > NEXCOM International Co. > > > Tel: 886-2-82280606 Ext. 3205 > > > Fax: 886-2-82280506 > > > E-mail: vincentetsou at nexcom.com.tw > > > Web: http://www.nexcom.com.tw/ > > > > > > > > > > > > > > > -- > > Best Regards, > > Vincente Tsou > > > > Engineer > > R/D, S/W Dept. > > NEXCOM International Co. > > Tel: 886-2-82280606 Ext. 3205 > > Fax: 886-2-82280506 > > E-mail: vincentetsou at nexcom.com.tw > > Web: http://www.nexcom.com.tw/ > > > > > -- > Best Regards, > Vincente Tsou > > Engineer > R/D, S/W Dept. > NEXCOM International Co. > Tel: 886-2-82280606 Ext. 3205 > Fax: 886-2-82280506 > E-mail: vincentetsou at nexcom.com.tw > Web: http://www.nexcom.com.tw/ > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > From vincentetsou at nexcom.com.tw Mon Jun 26 08:57:41 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Mon, 26 Jun 2006 14:57:41 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <2ea3fae10606252236q5917cc7bubd3e77f6affeb318@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> <41fde3420606251921l6a375d53y12cdc2030768d58e@mail.gmail.com> <2ea3fae10606252236q5917cc7bubd3e77f6affeb318@mail.gmail.com> Message-ID: <41fde3420606252357i6e2e5b1cmf90bf9eec7c4967c@mail.gmail.com> Hi, Excuse me.... I don't know how to move the CPU init before other pci device init call.... sorry. I have tried to find it, but .... :( 2006/6/26, yhlu : > > the snow screen only happened when I was debugging the onboard VGA > support. > So i move the CPU init before other pci device init call. That is > something related to mtrr setting around [0xa0000-0xb0000) the font > buffer. > the halt_sys display is normal...it means the vga option rom is > executed successfully. > you can use filo in etherboot to boot from usb stick. > > YH > > On 6/25/06, Vincente Tsou wrote: > > > > Hi YH, > > > > Thanks again for your help. > > > > Now I can active all devices in my LinuxBios, it almost done except VGA > > function. > > > > I appended a 36k VGA option rom to LinuxBios, and enable Options about > VGA. > > > > And I got the halt_sys message: > > > > PCI: 04:02.0 init > > rom address for PCI: 04:02.0 = fff80000 > > copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes > > entering emulator > > halt_sys: file > > /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, > > line 4387 > > PCI: 01:04.0 init > > > > then, I can see something output, but the output is like snow screen and > I > > can't read anything. > > I think it is working in the wrong mode. > > > > When I made a blind type 'root' and password, I can login the Linux, and > > then the screen became clear. (work fine) > > > > I wonder how to fix the problem? is the halt_sys message normal ? > > > > I also got another question, could it possible boot to MS-DOS floppy/USB > > disk. > > The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to > support > > it? > > > > > > > > 2006/6/21, Vincente Tsou : > > > > > > > > > Dear YH, > > > > > > got it. > > > > > > Thanks for the information and your help. > > > > > > > > > > > > 2006/6/21, Lu, Yinghai : > > > > > > > > > > > > > > > > > > > > > > > > > > > Actually the irqtable entries is only for peer root pci bus scan > when > > mptable is used. > > > > > > > > So you need to make sure mptable is right, and put entries for > > hypertransport chain other than on bus0. > > > > > > > > > > > > > > > > YH > > > > > > > > > > > > > > > > ________________________________ > > > > > > > > > > From: vincente.tsou at gmail.com [mailto:vincente.tsou at gmail.com] On > Behalf > > Of Vincente Tsou > > > > Sent: Tuesday, June 20, 2006 7:05 PM > > > > To: Lu, Yinghai > > > > Cc: Stefan Reinauer; linuxbios at linuxbios.org > > > > > > > > Subject: Re: [LinuxBIOS] New guy in LinuxBios > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dear YH, > > > > > > > > > > > > > > > > > > > > > > > > > > > > excuse me, how about the irq_tables.c? > > > > > > > > > > > > should I modify it like tyan/s2882 did. > > > > > > > > > > > > > > > > > > > > > > > > printk_debug("setting Onboard Broadcom NIC\n"); > > > > static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, > 0 > > }; > > > > pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); > > > > write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, > > 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); > > > > pirq_info++; slot_num++; > > > > > > > > > > > > > > > > > > > > > > > > 2006/6/20, Lu, Yinghai : > > > > > > > > > > > > > > > > > > > > You need to update the entries at mptable.c for your slots or > onboard > > pci device. > > > > > > > > > > > > > > > > YH > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best Regards, > > > > Vincente Tsou > > > > > > > > Engineer > > > > R/D, S/W Dept. > > > > NEXCOM International Co. > > > > Tel: 886-2-82280606 Ext. 3205 > > > > Fax: 886-2-82280506 > > > > E-mail: vincentetsou at nexcom.com.tw > > > > Web: http://www.nexcom.com.tw/ > > > > > > > > > > > > > > > > > > > > > > -- > > > Best Regards, > > > Vincente Tsou > > > > > > Engineer > > > R/D, S/W Dept. > > > NEXCOM International Co. > > > Tel: 886-2-82280606 Ext. 3205 > > > Fax: 886-2-82280506 > > > E-mail: vincentetsou at nexcom.com.tw > > > Web: http://www.nexcom.com.tw/ > > > > > > > > > > -- > > Best Regards, > > Vincente Tsou > > > > Engineer > > R/D, S/W Dept. > > NEXCOM International Co. > > Tel: 886-2-82280606 Ext. 3205 > > Fax: 886-2-82280506 > > E-mail: vincentetsou at nexcom.com.tw > > Web: http://www.nexcom.com.tw/ > > -- > > linuxbios mailing list > > linuxbios at linuxbios.org > > http://www.openbios.org/mailman/listinfo/linuxbios > > > > > > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From stepan at coresystems.de Mon Jun 26 09:12:36 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Mon, 26 Jun 2006 09:12:36 +0200 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <41fde3420606252357i6e2e5b1cmf90bf9eec7c4967c@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> <41fde3420606251921l6a375d53y12cdc2030768d58e@mail.gmail.com> <2ea3fae10606252236q5917cc7bubd3e77f6affeb318@mail.gmail.com> <41fde3420606252357i6e2e5b1cmf90bf9eec7c4967c@mail.gmail.com> Message-ID: <20060626071236.GA1763@coresystems.de> * Vincente Tsou [060626 08:57]: > Hi, > > Excuse me.... > > I don't know how to move the CPU init before other pci device init call.... > sorry. > > I have tried to find it, but .... :( Other question: How did you produce your vga bios image? you should extract it from the vendor bios image, not from memory, as some modify themselfes. And, no, sorry, booting MSDOS is not possible at the moment (except maybe with ADLO, which has not been developed in a long time) -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From vincentetsou at nexcom.com.tw Mon Jun 26 09:46:25 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Mon, 26 Jun 2006 15:46:25 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <20060626071236.GA1763@coresystems.de> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207003FEA@ssvlexmb2.amd.com> <41fde3420606201921l56103a84ua5201de5addb8d7@mail.gmail.com> <41fde3420606251921l6a375d53y12cdc2030768d58e@mail.gmail.com> <2ea3fae10606252236q5917cc7bubd3e77f6affeb318@mail.gmail.com> <41fde3420606252357i6e2e5b1cmf90bf9eec7c4967c@mail.gmail.com> <20060626071236.GA1763@coresystems.de> Message-ID: <41fde3420606260046s9f1b6e6p68f3bec82898a066@mail.gmail.com> Hello Stefan, Yeah, the VGA BIOS is extract from vendor bios image. Thanks for your update of MS-DOS. 2006/6/26, Stefan Reinauer : > > * Vincente Tsou [060626 08:57]: > > Hi, > > > > Excuse me.... > > > > I don't know how to move the CPU init before other pci device init > call.... > > sorry. > > > > I have tried to find it, but .... :( > > Other question: How did you produce your vga bios image? you should > extract it from the vendor bios image, not from memory, as some modify > themselfes. > > And, no, sorry, booting MSDOS is not possible at the moment (except > maybe with ADLO, which has not been developed in a long time) > > -- > coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. > Tel.: +49 761 7668825 ? Fax: +49 761 7664613 > Email: info at coresystems.de ? http://www.coresystems.de/ > > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From yinghai.lu at amd.com Mon Jun 26 19:24:25 2006 From: yinghai.lu at amd.com (Lu, Yinghai) Date: Mon, 26 Jun 2006 10:24:25 -0700 Subject: [LinuxBIOS] New guy in LinuxBios Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4207004004@ssvlexmb2.amd.com> In the MB Config.lb The device apic_cluster 0 should be put before other pci devices YH ________________________________ From: linuxbios-bounces at linuxbios.org [mailto:linuxbios-bounces at linuxbios.org] On Behalf Of Vincente Tsou Sent: Sunday, June 25, 2006 11:58 PM To: yhlu Cc: Stefan Reinauer; linuxbios at linuxbios.org Subject: Re: [LinuxBIOS] New guy in LinuxBios Hi, Excuse me.... I don't know how to move the CPU init before other pci device init call.... sorry. I have tried to find it, but .... :( 2006/6/26, yhlu : the snow screen only happened when I was debugging the onboard VGA support. So i move the CPU init before other pci device init call. That is something related to mtrr setting around [0xa0000-0xb0000) the font buffer. the halt_sys display is normal...it means the vga option rom is executed successfully. you can use filo in etherboot to boot from usb stick. YH On 6/25/06, Vincente Tsou wrote: > > Hi YH, > > Thanks again for your help. > > Now I can active all devices in my LinuxBios, it almost done except VGA > function. > > I appended a 36k VGA option rom to LinuxBios, and enable Options about VGA. > > And I got the halt_sys message: > > PCI: 04:02.0 init > rom address for PCI: 04: 02.0 = fff80000 > copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes > entering emulator > halt_sys: file > /home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c, > line 4387 > PCI: 01:04.0 init > > then, I can see something output, but the output is like snow screen and I > can't read anything. > I think it is working in the wrong mode. > > When I made a blind type 'root' and password, I can login the Linux, and > then the screen became clear. (work fine) > > I wonder how to fix the problem? is the halt_sys message normal ? > > I also got another question, could it possible boot to MS-DOS floppy/USB > disk. > The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to support > it? > > > > 2006/6/21, Vincente Tsou : > > > > > > Dear YH, > > > > got it. > > > > Thanks for the information and your help. > > > > > > > > 2006/6/21, Lu, Yinghai < yinghai.lu at amd.com>: > > > > > > > > > > > > > > > > > > > > Actually the irqtable entries is only for peer root pci bus scan when > mptable is used. > > > > > > So you need to make sure mptable is right, and put entries for > hypertransport chain other than on bus0. > > > > > > > > > > > > YH > > > > > > > > > > > > ________________________________ > > > > > > > From: vincente.tsou at gmail.com [mailto:vincente.tsou at gmail.com] On Behalf > Of Vincente Tsou > > > Sent: Tuesday, June 20, 2006 7:05 PM > > > To: Lu, Yinghai > > > Cc: Stefan Reinauer; linuxbios at linuxbios.org > > > > > > Subject: Re: [LinuxBIOS] New guy in LinuxBios > > > > > > > > > > > > > > > > > > > > > > > > Dear YH, > > > > > > > > > > > > > > > > > > > > > excuse me, how about the irq_tables.c? > > > > > > > > > should I modify it like tyan/s2882 did. > > > > > > > > > > > > > > > > > > printk_debug("setting Onboard Broadcom NIC\n"); > > > static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0 > }; > > > pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9); > > > write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8, > 0x2, 0xdef8, 0, 0, 0, 0, 0, 0); > > > pirq_info++; slot_num++; > > > > > > > > > > > > > > > > > > 2006/6/20, Lu, Yinghai < yinghai.lu at amd.com >: > > > > > > > > > > > > > > > You need to update the entries at mptable.c for your slots or onboard > pci device. > > > > > > > > > > > > YH > > > > > > > > > > > > > > > > > > > > > -- > > > Best Regards, > > > Vincente Tsou > > > > > > Engineer > > > R/D, S/W Dept. > > > NEXCOM International Co. > > > Tel: 886-2-82280606 Ext. 3205 > > > Fax: 886-2-82280506 > > > E-mail: vincentetsou at nexcom.com.tw > > > Web: http://www.nexcom.com.tw/ > > > > > > > > > > > > > > > -- > > Best Regards, > > Vincente Tsou > > > > Engineer > > R/D, S/W Dept. > > NEXCOM International Co. > > Tel: 886-2-82280606 Ext. 3205 > > Fax: 886-2-82280506 > > E-mail: vincentetsou at nexcom.com.tw > > Web: http://www.nexcom.com.tw/ > > > > > -- > Best Regards, > Vincente Tsou > > Engineer > R/D, S/W Dept. > NEXCOM International Co. > Tel: 886-2-82280606 Ext. 3205 > Fax: 886-2-82280506 > E-mail: vincentetsou at nexcom.com.tw > Web: http://www.nexcom.com.tw/ > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincentetsou at nexcom.com.tw Tue Jun 27 03:16:29 2006 From: vincentetsou at nexcom.com.tw (Vincente Tsou) Date: Tue, 27 Jun 2006 09:16:29 +0800 Subject: [LinuxBIOS] New guy in LinuxBios In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4207004004@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4207004004@ssvlexmb2.amd.com> Message-ID: <41fde3420606261816k4bc80e7aw71bed26f2cc954f7@mail.gmail.com> Dear YH, thanks for your reply. you are my light in the dark ... I'm trying to modify dev_initialize() in devices/device.c ... how fool I am. 2006/6/27, Lu, Yinghai : > > In the MB Config.lb > > The device apic_cluster 0 should be put before other pci devices > > > > YH > > > ------------------------------ > -- Best Regards, Vincente Tsou Engineer R/D, S/W Dept. NEXCOM International Co. Tel: 886-2-82280606 Ext. 3205 Fax: 886-2-82280506 E-mail: vincentetsou at nexcom.com.tw Web: http://www.nexcom.com.tw/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From carnoz at gmail.com Thu Jun 29 08:28:23 2006 From: carnoz at gmail.com (Z Carno) Date: Thu, 29 Jun 2006 14:28:23 +0800 Subject: [LinuxBIOS] boot from network Message-ID: <5cd736360606282328m1076206eod4807c8d5841badc@mail.gmail.com> I want to test if my linuxbios could boot from network . but have not done that before ,could anyone please help me to check if my steps is right? 1.install an os on ide hdd on the test MB. 2.copy the installed image file to another Server MB. 3.make some configuration for DHCP. 4.remove test MB ide hdd ,and use linuxbios boot . I have test windows boot from network before, its steps seems this . but I've no idea whether linux is this too. Thank you. Carno -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhendrix at google.com Thu Jun 29 23:43:28 2006 From: dhendrix at google.com (David Hendricks) Date: Thu, 29 Jun 2006 14:43:28 -0700 Subject: [LinuxBIOS] boot from network In-Reply-To: <5cd736360606282328m1076206eod4807c8d5841badc@mail.gmail.com> References: <5cd736360606282328m1076206eod4807c8d5841badc@mail.gmail.com> Message-ID: Hello Mr. Carno, This is indeed possible. The basic steps that I've used in the past are: 1. Make an etherboot image. Etherboot should download the image from the server via TFTP. 2. Compile LinuxBIOS with the etherboot image as the payload. 3. Make sure DHCPD and TFTPD are set up properly on the host and that your kernel image is in the correct directory. If I recall correctly, booting a Linux kernel over DHCP requires that you specify the location of your image. For example: host n1 { hardware ethernet 0:d0:c9:56:03:29; # MAC address fixed-address 10.0.4.10; # IP address filename "/tftpboot/elfimage"; } I have some old notes for a somewhat similar project using Etherboot, TFTP, and Beoboot: http://home.comcast.net/~zen_weasel/linuxbios_stuff/geode/bproc-geode . Most of it is obsolete, but the DHCP example might be useful. I'll try and get some more up to date instructions for you later on tonight. On 6/28/06, Z Carno wrote: > > > I want to test if my linuxbios could boot from network . but have not > done that before ,could anyone please help me to check if my steps is > right? > > 1.install an os on ide hdd on the test MB. > 2.copy the installed image file to another Server MB. > 3.make some configuration for DHCP. > 4.remove test MB ide hdd ,and use linuxbios boot . > > I have test windows boot from network before, its steps seems this . but > I've no idea whether linux is this too. > > Thank you. > > Carno > > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bios at lists.actweb.info Fri Jun 30 02:08:50 2006 From: bios at lists.actweb.info (bios at lists.actweb.info) Date: Fri, 30 Jun 2006 01:08:50 +0100 (BST) Subject: [LinuxBIOS] cant detect bios with flash software In-Reply-To: Message-ID: <1151626130.15160@actweb.info> Hi, I have just got my RD1, and installed it into my EPIA-PD10000 m/board (same chipset as the EPIA-M), all works fine :) I ran the flashrom util fom the linuxbios source code, (downloaded via svn) when i run the flashrom util i get the following :- with bios savour switched in, but nothing written :- :~/bios/LinuxBIOSv2/util/flashrom# ./flashrom Calibrating delay loop... ok No LinuxBIOS table found. Enabling flash write on VT8235...OK W49F002U found at physical address: 0xfffc0000 Flash part is W49F002U OK, only ENABLING flash write, but NOT FLASHING. with original bios switched in :- ~/bios/LinuxBIOSv2/util/flashrom# ./flashrom Calibrating delay loop... ok No LinuxBIOS table found. Enabling flash write on VT8235...OK No EEPROM/flash device found. As you can see the RD1 bios chip is reconised fine but my original bios chip dosnt seem to be found :( on inspection of the bios chip, i can see a chip number of :F492002UA If ive understood the flashrom program, this isnt reconsied becasue there isnt a file of that name within the flashrom directory (each file represents its resective bios number????) Has anyone come accross this bios chip before, and if so can they supply the config file for flashrom? As i understand it, i should still be able to use the EPIA flash program, but as i dont have a working floppy drive in the house, and am not keen on using a cd for a 1.44Mb file, PLEASE could anyone recomend a way around this? Also if i use the EPIA flash program it makes it harder to get the compiled rom into the bios, as i have to jump from linux to windows all the time :( Is there a way to grab the entire bios using dd under linux? could this be sued to get a copy of the original bios, and then write this to the RD1? Many thanks Matt From stepan at coresystems.de Fri Jun 30 09:34:41 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 30 Jun 2006 09:34:41 +0200 Subject: [LinuxBIOS] cant detect bios with flash software In-Reply-To: <1151626130.15160@actweb.info> References: <1151626130.15160@actweb.info> Message-ID: <20060630073441.GA23109@coresystems.de> * bios at lists.actweb.info [060630 02:08]: > Calibrating delay loop... ok > No LinuxBIOS table found. > Enabling flash write on VT8235...OK > No EEPROM/flash device found. Run flashrom -V to see the id of the flash chip Stefan From bios at lists.actweb.info Fri Jun 30 11:51:49 2006 From: bios at lists.actweb.info (bios at lists.actweb.info) Date: Fri, 30 Jun 2006 10:51:49 +0100 (BST) Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <20060630073441.GA23109@coresystems.de> Message-ID: <1151661109.15492@actweb.info> ok when i run flashrom with -V i get the folloowing:- ~/bios/LinuxBIOSv2/util/flashrom# ./flashrom -V Calibrating delay loop... Setting up microsecond timing loop 176M loops per second ok No LinuxBIOS table found. Enabling flash write on VT8235...OK Trying Am29F040B, 512 KB probe_29f040b: id1 0x25, id2 0xa6 Trying Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Trying At29C040A, 512 KB probe_jedec: id1 0x8c, id2 0x0 Trying Mx29f002, 256 KB probe_29f002: id1 0x8c, id2 0x0 Trying SST29EE020A, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST28SF040A, 512 KB probe_28sf040: id1 0x25, id2 0xa6 Trying SST39SF020A, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST39VF020, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST49LF040B, 512 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST49LF040, 512 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF002A/B, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST49LF003A/B, 384 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST49LF004A/B, 512 KB probe_jedec: id1 0x8c, id2 0x0 Trying SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying Pm49FL002, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying Pm49FL004, 512 KB probe_jedec: id1 0x8c, id2 0x0 Trying W29C011, 128 KB probe_jedec: id1 0x8c, id2 0x0 Trying W29C020C, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying W49F002U, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying W49V002A, 256 KB probe_jedec: id1 0x8c, id2 0x0 Trying W39V040A, 512 KB probe_jedec: id1 0x8c, id2 0x0 Trying M29F040B, 512 KB probe_29f040b: id1 0x25, id2 0xa6 Trying M29F400BT, 512 KB probe_m29f400bt: id1 0x25, id2 0x2d Trying 82802ab, 512 KB probe_82802ab: id1 0x25, id2 0xa6 Trying 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Trying LHF00L04, 1024 KB probe_lhf00l04: id1 0xff, id2 0xff No EEPROM/flash device found. As far as i can see its not showing the rom number :( I cant seem to find a version number for flashrom, but it was downloaded via svn on 29 June (this year!!) I am running this on 'Ubuntu 5.10 "Breezy Badger"' Kernel : 'Linux ubuntu 2.6.12-9-386 #1 Mon Oct 10 13:14:36 BST 2005 i686 GNU/Linux' on an VIA EPIA-PD10000 m/board Matt Stefan Reinauer wrote .. > * bios at lists.actweb.info [060630 02:08]: > > Calibrating delay loop... ok > > No LinuxBIOS table found. > > Enabling flash write on VT8235...OK > > No EEPROM/flash device found. > > Run flashrom -V to see the id of the flash chip > > Stefan > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > MailScanner thanks ACTweb Computers for their support. From dhendrix at google.com Fri Jun 30 18:53:28 2006 From: dhendrix at google.com (David Hendricks) Date: Fri, 30 Jun 2006 09:53:28 -0700 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <1151661109.15492@actweb.info> References: <20060630073441.GA23109@coresystems.de> <1151661109.15492@actweb.info> Message-ID: Can you switch to using the RD1's BIOS, even if it's not flashed yet? It should be a PMC chip of some sort that flashrom currently supports. It could be that we simply need to add support for whatever flash chip your mainboard came with, in which case we'll need you to open up your machine and get the part number. On 6/30/06, bios at lists.actweb.info < bios at lists.actweb.info> wrote: > > ok when i run flashrom with -V i get the folloowing:- > > ~/bios/LinuxBIOSv2/util/flashrom# ./flashrom -V > Calibrating delay loop... Setting up microsecond timing loop > 176M loops per second > ok > No LinuxBIOS table found. > Enabling flash write on VT8235...OK > Trying Am29F040B, 512 KB > probe_29f040b: id1 0x25, id2 0xa6 > Trying Am29F016D, 2048 KB > probe_29f040b: id1 0xff, id2 0xff > Trying At29C040A, 512 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying Mx29f002, 256 KB > probe_29f002: id1 0x8c, id2 0x0 > Trying SST29EE020A, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST28SF040A, 512 KB > probe_28sf040: id1 0x25, id2 0xa6 > Trying SST39SF020A, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST39VF020, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST49LF040B, 512 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST49LF040, 512 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST49LF080A, 1024 KB > probe_jedec: id1 0xff, id2 0xff > Trying SST49LF002A/B, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST49LF003A/B, 384 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST49LF004A/B, 512 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying SST49LF008A, 1024 KB > probe_jedec: id1 0xff, id2 0xff > Trying Pm49FL002, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying Pm49FL004, 512 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying W29C011, 128 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying W29C020C, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying W49F002U, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying W49V002A, 256 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying W39V040A, 512 KB > probe_jedec: id1 0x8c, id2 0x0 > Trying M29F040B, 512 KB > probe_29f040b: id1 0x25, id2 0xa6 > Trying M29F400BT, 512 KB > probe_m29f400bt: id1 0x25, id2 0x2d > Trying 82802ab, 512 KB > probe_82802ab: id1 0x25, id2 0xa6 > Trying 82802ac, 1024 KB > probe_82802ab: id1 0xff, id2 0xff > Trying LHF00L04, 1024 KB > probe_lhf00l04: id1 0xff, id2 0xff > No EEPROM/flash device found. > > > As far as i can see its not showing the rom number :( > I cant seem to find a version number for flashrom, but it was downloaded > via svn on 29 June (this year!!) > I am running this on 'Ubuntu 5.10 "Breezy Badger"' Kernel : 'Linux ubuntu > 2.6.12-9-386 #1 Mon Oct 10 13:14:36 BST 2005 i686 GNU/Linux' > on an VIA EPIA-PD10000 m/board > > Matt > > > Stefan Reinauer wrote .. > > * bios at lists.actweb.info < bios at lists.actweb.info> [060630 02:08]: > > > Calibrating delay loop... ok > > > No LinuxBIOS table found. > > > Enabling flash write on VT8235...OK > > > No EEPROM/flash device found. > > > > Run flashrom -V to see the id of the flash chip > > > > Stefan > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > MailScanner thanks ACTweb Computers for their support. > > > -- > linuxbios mailing list > linuxbios at linuxbios.org > http://www.openbios.org/mailman/listinfo/linuxbios > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Fri Jun 30 18:56:20 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Fri, 30 Jun 2006 10:56:20 -0600 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: References: <20060630073441.GA23109@coresystems.de> <1151661109.15492@actweb.info> Message-ID: <44A557B4.7060201@lanl.gov> David Hendricks wrote: > Can you switch to using the RD1's BIOS, even if it's not flashed yet? It > should be a PMC chip of some sort that flashrom currently supports. It > could be that we simply need to add support for whatever flash chip your > mainboard came with, in which case we'll need you to open up your > machine and get the part number. I'm suspicious that flash write is not enabled in the chipset, but yeah, switch the bios savior to the rd1 position and see if it id's that flash part. ron From stepan at coresystems.de Fri Jun 30 19:12:26 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 30 Jun 2006 19:12:26 +0200 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <44A557B4.7060201@lanl.gov> References: <20060630073441.GA23109@coresystems.de> <1151661109.15492@actweb.info> <44A557B4.7060201@lanl.gov> Message-ID: <20060630171226.GA10351@coresystems.de> * Ronald G Minnich [060630 18:56]: > David Hendricks wrote: > > Can you switch to using the RD1's BIOS, even if it's not flashed yet? It > > should be a PMC chip of some sort that flashrom currently supports. It > > could be that we simply need to add support for whatever flash chip your > > mainboard came with, in which case we'll need you to open up your > > machine and get the part number. > > I'm suspicious that flash write is not enabled in the chipset, but yeah, > switch the bios savior to the rd1 position and see if it id's that flash > part. But with the bios savior the flash chip was detected, so in theory it might be an unsupported chip type tristar. Cant fint docs on this.. Also the flash device type :F492002UA looks very weird. Can you double check it does not say something different or something else on the chip? can you recognize a vendor (logo/string)? can you verify whether the image starts with 25 a6? Stefan -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/ From rminnich at lanl.gov Fri Jun 30 19:17:23 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Fri, 30 Jun 2006 11:17:23 -0600 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <20060630171226.GA10351@coresystems.de> References: <20060630073441.GA23109@coresystems.de> <1151661109.15492@actweb.info> <44A557B4.7060201@lanl.gov> <20060630171226.GA10351@coresystems.de> Message-ID: <44A55CA3.8010509@lanl.gov> Stefan Reinauer wrote: > But with the bios savior the flash chip was detected, so in theory it > might be an unsupported chip type tristar. Cant fint docs on this.. er, sorry, I missed that, oops. ron From bios at lists.actweb.info Fri Jun 30 19:42:50 2006 From: bios at lists.actweb.info (bios at lists.actweb.info) Date: Fri, 30 Jun 2006 18:42:50 +0100 (BST) Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <20060630171226.GA10351@coresystems.de> Message-ID: <1151689370.10330@actweb.info> Hi there, Got someone else to read the bios chip number (my eyes are getting bad LOL) Chip has the following on the top :- EFST F498002UA 90N AZB1MFR29 0303 Not quite sure of the '0303' on the last line it may be 8303, its not very clear :( Is there a way to get the bios number from inside linux? eg. is it held someware that could be grabbed via the /proc filesystem? Is there any way i can help to get the support for this bios chip? (im not very good at programming nowadays, used to program Z80/6502 chips not C code etc.) but given a good set of instructions i should be able to follow them :) Also, does this mean that there isnt anyway to get linuxbios working on my board? or is it just a case of writing a good image to the RD1 to get it working? the last time i used anything like this was when you had a small memory chip with built in battery that had an RTC in the upper 8 address bytes, and the rest was standard SRAM :) Im not sure what u mean by verifing that the image starts 25 a6??? are you talking about an image file taken from the BIOS using VIAs flash utility? Many thanks for all the info/help so far Matt Stefan Reinauer wrote .. > * Ronald G Minnich [060630 18:56]: > > David Hendricks wrote: > > > Can you switch to using the RD1's BIOS, even if it's not flashed yet? > It > > > should be a PMC chip of some sort that flashrom currently supports. > It > > > could be that we simply need to add support for whatever flash chip > your > > > mainboard came with, in which case we'll need you to open up your > > > machine and get the part number. > > > > I'm suspicious that flash write is not enabled in the chipset, but yeah, > > switch the bios savior to the rd1 position and see if it id's that flash > > part. > > But with the bios savior the flash chip was detected, so in theory it > might be an unsupported chip type tristar. Cant fint docs on this.. > > Also the flash device type :F492002UA looks very weird. Can you double > check it does not say something different or something else on the chip? > can you recognize a vendor (logo/string)? > > can you verify whether the image starts with 25 a6? > > Stefan > > > > -- > coresystems GmbH ??? Brahmsstr. 16 ??? D-79104 Freiburg i. Br. > Tel.: +49 761 7668825 ??? Fax: +49 761 7664613 > Email: info at coresystems.de ??? http://www.coresystems.de/ > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > MailScanner thanks ACTweb Computers for their support. From rminnich at lanl.gov Fri Jun 30 20:26:32 2006 From: rminnich at lanl.gov (Ronald G Minnich) Date: Fri, 30 Jun 2006 12:26:32 -0600 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <1151689370.10330@actweb.info> References: <1151689370.10330@actweb.info> Message-ID: <44A56CD8.1090307@lanl.gov> you have to find the vendor. Given the vendor and part #, we can get a data book and update flashrom to understand that chip. Don't give up -- we'll get it. ron From stepan at coresystems.de Fri Jun 30 21:49:22 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 30 Jun 2006 21:49:22 +0200 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <1151689370.10330@actweb.info> References: <20060630171226.GA10351@coresystems.de> <1151689370.10330@actweb.info> Message-ID: <20060630194922.GA17044@coresystems.de> * bios at lists.actweb.info [060630 19:42]: > EFST > F498002UA 90N > AZB1MFR29 0303 Good! This helps. The part is an EFST F49B002UA: http://www.esmt.com.tw/DB/manager/upload/F49B002UA.pdf > Is there a way to get the bios number from inside linux? Yes. each flash chip has an identification sequence. Unfortunately there are different such sequences for different manufacturers. But all in all each flash chip has one byte vendor id and one byte device id. > Also, does this mean that there isnt anyway to get linuxbios working > on my board? or is it just a case of writing a good image to the RD1 > to get it working? You can just write to the chip on the bios savior and leave the EFST alone (it has a good working bios image, right?) - Actually that is probably the best way to start. > the last time i used anything like this was when > you had a small memory chip with built in battery that had an RTC in > the upper 8 address bytes, and the rest was standard SRAM :) The programming got a lot easier since then. The hardware a lot more complex. :-) > Im not sure what u mean by verifing that the image starts 25 a6??? are > you talking about an image file taken from the BIOS using VIAs flash > utility? I thought that might be the vendor and device id. In fact it is 8c and 00, as it is a 256kb part Stefan From stepan at coresystems.de Fri Jun 30 22:16:47 2006 From: stepan at coresystems.de (Stefan Reinauer) Date: Fri, 30 Jun 2006 22:16:47 +0200 Subject: [LinuxBIOS] cant detect bios with flash software {Scanned} In-Reply-To: <20060630194922.GA17044@coresystems.de> References: <20060630171226.GA10351@coresystems.de> <1151689370.10330@actweb.info> <20060630194922.GA17044@coresystems.de> Message-ID: <20060630201647.GA18776@coresystems.de> * Stefan Reinauer [060630 21:49]: > > Im not sure what u mean by verifing that the image starts 25 a6??? are > > you talking about an image file taken from the BIOS using VIAs flash > > utility? > > I thought that might be the vendor and device id. In fact it is 8c and > 00, as it is a 256kb part Ok, can you please check out revision 2336. I checked in some untested support for your flash part. Can you try the following: Please be careful which chip you use at a time. If you mess the order up you will most likely render your system unusable ... 1. make a copy of your bios: switch to the EFST, then do: ./flashrom -r legacybios.bin 2. write the copy to your bios savior switch to the bios savior (Winbond W49F002U) ./flashrom -w legacybios.bin 3. Verify the copy in the bios savior ./flashrom -v legacybios.bin 4. Overwrite the EMST flash to see if the new flashbios version works switch to the EMST again! dd if=/dev/zero of=nullbios.bin bs=256k count=1 ./flashbios -w nullbios.bin ./flashbios -v nullbios.bin (it should say "verified" here!!!!) then you can write the original bios back to the EMST so you have two valid copies for playing later. ./flashbios -w legacybios.bin ./flashbios -v legacybios.bin Please post the results here.. -- coresystems GmbH ? Brahmsstr. 16 ? D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ? Fax: +49 761 7664613 Email: info at coresystems.de ? http://www.coresystems.de/