coreboot

coreboot@coreboot.org

12 participants
39779 discussions

Re: Pm49FL004 on Tyan Tiger AMD 76x chipset (fwd)
by Hendricks David W. 13 May '04

13 May '04

Has anyone flash a ROM on a Tyan Tiger mainboard? ---------- Forwarded message ---------- Date: Thu, 13 May 2004 10:05:51 -0500 From: Donald Zoch <donald.zoch(a)amd.com> To: Hendricks David W. <dwh(a)lanl.gov> Cc: Donald Zoch <donald.zoch(a)amd.com>, rminnich(a)lanl.gov, ollie(a)lanl.gov Subject: Re: Pm49FL004 on Tyan Tiger AMD 76x chipset Ok. Much appreciated. On Thu, May 13, 2004 at 09:03:45AM -0600, Hendricks David W. wrote: > We do not have any Tyan Tiger boards on our workbench. However if you'd > like I can forward your request to the LinuxBIOS mailing list. We have a > friend working at Tyan who I am very confident will be able to respond to > this issue. > > On Thu, 13 May 2004, Donald Zoch wrote: > > > Could any of you pass on any hints about how to get a Pm49FL004 > > detected in an AMD Athlon based Tyan Tiger board? The same chip > > flashes with flash_rom flawlessly in the K8W. > Donald ---- Donald Zoch Phone: (512) 602-7945 Pager: (512) 604-5401 donald.zoch(a)amd.com

1 0

Anyone using LinuxBIOS for hardware verification?
by Ken Fuchs 13 May '04

13 May '04

LinuxBIOS would seem to be an excellent tool for hardware verification, since it gets extremely close to the hardware and it is GPL licensed ... Please respond with your comments concerning hardware verification whether LinuxBIOS related or not. There are several places where hardware verification could be executed: 1) The verification code could be an optional part of LinuxBIOS itself to test hardware immediately after (or during) hardware initialization. 2) It could also be a LinuxBIOS payload (a stand-alone hardware verification program). 3) It could be integrated into the Linux kernel (loaded by LinuxBIOS) that finishes hardware initialization. 4) It could be a suite of user programs that are started by the initial (and only) Linux kernel via /sbin/init or user initiated. 5) It could be 3 above, except relative to a second Linux kernel (loaded via the initial Linux kernel). 6) It could be 4 above, except relative to a second Linux kernel (loaded via the initial Linux kernel). Points 5 and 6 are not directly LinuxBIOS related, but are probably the most common types of open source hardware verification code that is available. Any information regarding open (even closed) source hardware verification programs or code is welcome. Please respond via the list (or private e-mail if you prefer - I will summarize all private responses via the list, unless requested otherwise). Sincerely, Ken Fuchs <kfuchs(a)winternet.com>

1 0

答复: HDAMA+FILO booting SUSE Linux
by YhLu 13 May '04

13 May '04

Try add acpi=off YH -----邮件原件----- 发件人: Craig C Forney [mailto:cforney@opus.com] 发送时间: 2004年5月12日 12:42 收件人: linuxbios(a)clustermatic.org 主题: HDAMA+FILO booting SUSE Linux First, thanks for fixing the broken sourceforge LinuxBIOS tree earlier this week. I've been using LinuxBIOS successfully for some custom dense board designs being used for hardware verification, primarily running memtest86. I only have a serial port available. I'm using an Arima HDAMA board as a known working testbed for trying software before running it on our own boards. At this point, I'd like to attempt to boot up Linux. The first step is getting it to work properly on the Arima HDAMA board. I have booted and loaded Suse 9.0 Professional (I'm awaiting delivery of 9.1), as well as the Suse 9.1 Live CD, without problems with the standard Phoenix BIOS on the Arima HDAMA board. Using LinuxBIOS plus FILO, I'm not having much luck. I've checked through the archives, but I'm not finding the right combination of steps that works. -- Booting of the Suse 9.0 DVD in an attempt to install Linux on disk gets up to the point where yast has determined the proper partition sizes during it's initial config screens, but then hangs. It's in the middle of the yast formatted screens, so I don't know a good way to copy this to an email. -- Booting an already loaded 9.0 system panics the kernel: POSIX conformance testing by UNIFIX mtrr: v2.02 (20020716)) CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K (64 bytes/line/2 way) CPU: L2 Cache: 1024K (64 bytes/line/8 way) CPU0: stepping 01 per-CPU timeslice cutoff: 5119.55 usecs. task migration cache decay timeout: 10 msecs. Booting processor 1/1 rip 6000 page 000001000261a000 Not respondin<4>NMI Watchdog detected LOCKUP on CPU0, eip ffffffff80204027, registers: CPU 0 Pid: 0, comm: swapper Not tainted RIP: 0010:[<ffffffff80204027>]{serial_in+71} RSP: 0018:ffffffff804dfda8 EFLAGS: 00000202 RAX: 0000000000000000 RBX: 00000000000f4238 RCX: 0000000000008000 RDX: 00000000000003fd RSI: 0000000000000005 RDI: ffffffff804837a0 RBP: ffffffff804837a0 R08: 000000000000006e R09: 00000000409fa439 R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff80413bf4 R13: 000000000000000d R14: 0000000000000010 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff804cb3c0(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0 Process swapper (pid: 0, stackpage=ffffffff804df000) Stack: ffffffff804dfda8 0000000000000018 0000000000040000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Call Trace: <EOE> [<ffffffff80209ff0>]{serial_console_write+96} [<ffffffff80124fcc>]{__call_console_drivers+76} [<ffffffff80125127>]{call_console_drivers+231} [<ffffffff801254b2>]{release_console_sem+82} [<ffffffff80125355>]{vprintk+357} [<ffffffff801253fd>]{printk+141} [<ffffffff802d164c>]{__delay+12} Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89 d0 83 f8 console shuts up ... -- Booting the Suse 9.1 Live CD (I copied all the files on the Live CD to the root file system on an already installed Suse 9.0 system) boot: hda3:/livecd/vmlinuz root=/dev/hda3 initrd=hda3:/livecd/initrd.gz console=ttyS0,115200 Found Linux version 2.6.4-52-default (geeko@buildhost) #1 Wed Apr 7 02:08:30 UTC 2004 bzImage. Loading kernel... ok Loading initrd... ok Jumping to entry point... Linux version 2.6.4-52-default (geeko@buildhost) (gcc version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 0000000040000000 (usable) 128MB vmalloc/ioremap area available. 128MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 262144 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:16 HighMem zone: 32768 pages, LIFO batch:8 DMI not present. ACPI: Unable to locate RSDP Built 1 zonelists Kernel command line: root=/dev/hda3 console=ttyS0,115200 Initializing CPU#0 PID hash table entries: 4096 (order 12: 32768 bytes) CKRM Initialized Detected 1403.889 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Memory: 1009620k/1048576k available (1969k kernel code, 37972k reserved, 677k data, 212k init, 131072k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 2760.70 BogoMIPS Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. Failure registering capabilities with the kernel selinux_register_security: Registering secondary module capability Capability LSM initialized Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) checking if image is initramfs... it is Freeing initrd memory: 26442k freed 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 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX do_initcalls init_elf_binfmt NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay ACPI: ACPI tables contain no PCI IRQ routing entries PCI: Invalid ACPI-PCI IRQ routing table PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) ... the first call_usermodehelper: pci_bus CPU 0: Machine Check Exception: 0000000000000004 Bank 4: b200000000070f0f Kernel panic: CPU context corrupt So, it's pretty clear I am missing a crucial step (or two or three) to booting Linux successfully with LinuxBIOS+FILO. I'd appreciate some help in identifying the basic steps. Thanks, Craig Forney Opus Innovations LLC _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

3 2

Re: Epia-M + Linuxbios
by "Dmitry Borisov=?koi8-r?Q?=22=20?= 12 May '04

12 May '04

-----Original Message----- From: Jerome Ibanes <jibanes(a)eskimo.com> > > Hi, I'd like to get LinuxBios on some Epia boards, and I have a couple of > questions about that: Dear Jerome, Please use this link to find your answers: http://www.google.com/search?as_q=+Linuxbios&num=10&hl=en&btnG=Google+Searc… Dmitry/

1 0

Re: Lessons learned and more ???
by Hendricks David W. 12 May '04

12 May '04

On a side note, what's going on with your memory? It should not fail to initialize. Maybe try removing each DIMM to see if one is bad? On Wed, 12 May 2004, Jay Miller wrote: > Thanks everyone for your help! > > It took me some time to realize the reason that I wasn't seeing any data > on the VGA console is because it doesn't work on the S2885. But I have > my null modem connected and am seeing lots of interesting stuff now. > > YH sent me a pre-built S2885 image and the FIRST time it executed I got > this: > > > LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 starting... > > setting up resource map....done. > coherent_ht_finalize > done > Ram1.00 > Ram1.01 > Ram2.00 > Ram2.01 > No memory for this cpu > Ram3 > Initializing memory: done > Initializing memory: > ........................................................... > > ........................................................................ > > ........................................................................ > ........ > > ........................................................................ > . failed > > > Clearing LinuxBIOS memory: done > Ram4 > Copying LinuxBIOS to ram. > Jumping to LinuxBIOS. > LinuxBIOS-1.1.62.0_Fallback Sun Dec 31 20:53:07 EST 2000 booting... > > Finding PCI configuration type. > PCI: Using configuration type 1 > Enumerating static devices... > Enumerating: AMD K8 Northbridge > Enumerating: AMD K8 Northbridge > Enumerating: AMD K8 CPU > Enumerating: AMD K8 > Enumerating: AMD 8111 Southbridge > Enumerating: Winbond w83627hf > Enumerating buses... > amdk8_scan_root_bus > amdk8_scan_root_bus: start scaning pci bus > > 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] ops > PCI: 00:18.3 [1022/1103] enabled > PCI: 00:19.0 [ffff/ffff] enabled > PCI: 00:19.1 [ffff/ffff/00ffff] has unknown header type ff, ignoring. > > PCI: 00:19.1 No device operations > PCI: 00:19.2 [ffff/ffff/00ffff] has unknown h > > PCI: 00:19.2 No device operations > PCI: 00:19.3 [ffff/ffff/00ffff] has unknown header type ff, ignoring. > > PCI: 00:19.3 No device operations > amdk8_scan_chains max: 0 starting... > Hyper transport scan link: 0 max: 1 > PCI: 01:01.0 [1022/7454] enabled next_unitid: 0004 > > HyperT reset not needed > PCI: pci_scan_bus for bus 1 > PCI: 01:01.0 [1022/7454] ops > PCI: 01:01.0 [1022/7454] enabled > PCI: 01:02.0 [1022/7455] bus ops > PCI: 01:02.0 [1022/7455] enabled > PCI: pci_scan_bus for bus 2 > PCI: 02:00.0 [10de/0333] enabled > PCI: pci_scan_bus returning with max=02 > > PCI: pci_scan_bus returning with max=02 > > Hyper transport scan link: 0 new max: 2 > > Hypertransport scan link done > Hyper transport scan link: 2 max: 3 > PCI: 03:01.0 [1022/7450] enabled next_unitid: 0003 > > amd8111_enable_dev: enabling PCI: 03:00.0 [1022/7460] > > PCI: 03:03.0 [1022/7460] enabled next_unitid: 0007 > > HyperT reset not needed > PCI: pci_scan_bus for bus 3 > PCI: 03:01.0 [1022/7450] bus ops > PCI: 03:01.0 [1022/7450] enabled > PCI: 03:01.1 [1022/7451] ops > PCI: 03:01.1 [1022/7451] enabl > PCI: 03:02.0 [1022/7450] bus ops > PCI: 03:02.0 [1022/7450] enabled > PCI: 03:02.1 [1022/7451] ops > PCI: 03:02.1 [1022/7451] enabled > amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460] > > PCI: 03:03.0 [1022/7460] bus ops > amd8111_enable_dev: enabling PCI: 03:03.0 [1022/7460] > > PCI: 03:03.0 [1022/7460] enabled > amd8111_enable_dev: enabling PCI: 03:04.0 [1022/7468] > > PCI: 03:04.0 [1022/7468] bus ops > amd8111_enable: enabling PCI: 03:04.0 [1022/7468] > > PCI: 03:04.0 [1022/7468] enabled > amd8111_enable_dev: enabling PCI: 03:04.1 [102 > > PCI: 03:04.1 [1022/7469] ops > amd8111_enable_dev: enabling PCI: 03:04.1 [1022/7469] > > PCI: 03:04.1 [1022/7469] enabled > amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a] > > amd8111_enable_dev: enabling PCI: 03:04.2 [1022/746a] > > PCI: 03:04.2 [1022/746a] enabled > amd8111_enable_dev: enabling PCI: 03:04.3 [1022/746b] > > PCI: 03:04.3 [1022/746b] ops > amd8111_enable: enabling PCI: 03:04.3 [1022/746b] > > PCI: 03:04.3 [1022/746b] enabled > amd8111_enable_dev: enabling PCI: 03:04.5 [1022/746d] > > PCI: 03:04.5 [1022/746d] ops > amd8111_enable: enabling PCI: 03:04.5 [1022/746d] > > PCI: 03:04.5 [1022/746d] enabled > amd8111_enable_dev: enabling PCI: 03:04.6 [1022/746e] > > PCI: 03:04.6 [1022/746e] ops > amd8111_enable: disabling PCI: 03:04.6 [1022/746e] > > PCI: 03:04.6 [1022/746e] disabled > PCI: pci_scan_bus for bus 4 > PCI: 04:09.0 [14e4/16a7] 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 for bus 6 > amd8111_enable_dev: enabling PCI: 06:00.0 [1022/7464] > > PCI: 06:00.0 [102 > amd8111_enable: enabling PCI: 06:00.0 [1022/7464] > > PCI: 06:00.0 [1022/7464] enabled > amd8111_enable_dev: enabling PCI: 06:00.1 [1022/7464] > > PCI: 06:00.1 [1022/7464] ops > amd8111_enable: enabling PCI: 06:00.1 [1022/7464] > > PCI: 06:00.1 [1022/7464] enabled > amd8111_enable_dev: enabling PCI: 06:00.2 [1022/7463] > > PCI: 06:00.2 [1022/7463] ops > amd8111_enable: disabling PCI: 06:00.2 [1022/7463] > > PCI: 06:00.2 [1022/7463] disabled > amd8111_enable_dev: enabling PCI: 06:01.0 [1022/7462] > > PCI: 06:01.0 [1022/7462] ops > PCI: 06:01.0 [1022 > PCI: 06:01.0 [1022/7462] disabled > PCI: 06:0b.0 [1095/3114] enabled > PCI: 06:0c.0 [104c/8023] ops > PCI: 06:0c.0 [104c/8023] enabled > PCI: pci_scan_bus returning with max=06 > > scan_static_bus for PCI: 03:04.0 > PNP: 002e.0 enabled > 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 disabled > PNP: 002e.9 disabled > PNP: 002e.a disabled > PNP: 002e.b enabled > scan_static_bus done > PCI: pci_scan_bus returning with max=06 > > Hyper transport scan link: 2 new > Hypertransport scan link done > amdk8_scan_chains max: 6 done > amdk8_scan_chains max: 6 starting... > > > > This looked pretty good, but I didn't know what it was trying to start. > Unfortunately the next time the same image executed (reset via power > cycle) I got this: > > > LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting... > > setting up resource map....done. > No connection to Node 1. > ht reset - > > > LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 starting... > setting up resource map....done. > No connection to Node 1. > Ram1.00 > Ram1.01 > Ram2.00 > Ram2.01 > No memory for this cpu > Ram3 > Initializing memory: done > Initializing memory: > ........................................................... > ........................................................................ > ........ > ........................................................................ > ........ > ........................................................................ > . failed > > Clearing LinuxBIOS memory: done > Ram4 > Copying LinuxBIOS to ram. > Jumping to LinuxBIOS. > LinuxBIOS-1.1.62.0_Fallback Thu May 6 18:25:41 PDT 2004 booting... > > > > Has anyone seen this issue? Is something not getting reset? BTW, my > own image does the same thing. > > Thanks, > > Jay Miller > Actuality Systems, Inc. > jmiller(a)acutality-systems.com > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

答复: S2885 Uni-processor image
by YhLu 12 May '04

12 May '04

auto.c and mainboard.c -----邮件原件----- 发件人: Jay Miller [mailto:jmiller@actuality-systems.com] 发送时间: 2004年5月12日 13:19 收件人: linuxbios(a)clustermatic.org 主题: S2885 Uni-processor image My S2885 board is only uni-processor, so I modified the follow options: option CONFIG_MAX_CPUS=1 option CONFIG_LOGICAL_CPUS=0 option CONFIG_MAX_PHYSICAL_CPUS=1 But the static.c that is generated still enumerates two CPUs. What else do I need to do to force uni-processor? Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

Re: S2885 Uni-processor image
by ron minnich 12 May '04

12 May '04

On Wed, 12 May 2004, Jay Miller wrote: > My S2885 board is only uni-processor, so I modified the follow options: > > option CONFIG_MAX_CPUS=1 > option CONFIG_LOGICAL_CPUS=0 > option CONFIG_MAX_PHYSICAL_CPUS=1 > > But the static.c that is generated still enumerates two CPUs. What else > do I need to do to force uni-processor? > It should not matter. I would be happier if you left it at 2 and we made it work with 1. ron

1 0

S2885 Uni-processor image
by Jay Miller 12 May '04

12 May '04

My S2885 board is only uni-processor, so I modified the follow options: option CONFIG_MAX_CPUS=1 option CONFIG_LOGICAL_CPUS=0 option CONFIG_MAX_PHYSICAL_CPUS=1 But the static.c that is generated still enumerates two CPUs. What else do I need to do to force uni-processor? Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com

1 0

HDAMA+FILO booting SUSE Linux
by Craig C Forney 12 May '04

12 May '04

First, thanks for fixing the broken sourceforge LinuxBIOS tree earlier this week. I've been using LinuxBIOS successfully for some custom dense board designs being used for hardware verification, primarily running memtest86. I only have a serial port available. I'm using an Arima HDAMA board as a known working testbed for trying software before running it on our own boards. At this point, I'd like to attempt to boot up Linux. The first step is getting it to work properly on the Arima HDAMA board. I have booted and loaded Suse 9.0 Professional (I'm awaiting delivery of 9.1), as well as the Suse 9.1 Live CD, without problems with the standard Phoenix BIOS on the Arima HDAMA board. Using LinuxBIOS plus FILO, I'm not having much luck. I've checked through the archives, but I'm not finding the right combination of steps that works. -- Booting of the Suse 9.0 DVD in an attempt to install Linux on disk gets up to the point where yast has determined the proper partition sizes during it's initial config screens, but then hangs. It's in the middle of the yast formatted screens, so I don't know a good way to copy this to an email. -- Booting an already loaded 9.0 system panics the kernel: POSIX conformance testing by UNIFIX mtrr: v2.02 (20020716)) CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K (64 bytes/line/2 way) CPU: L2 Cache: 1024K (64 bytes/line/8 way) CPU0: stepping 01 per-CPU timeslice cutoff: 5119.55 usecs. task migration cache decay timeout: 10 msecs. Booting processor 1/1 rip 6000 page 000001000261a000 Not respondin<4>NMI Watchdog detected LOCKUP on CPU0, eip ffffffff80204027, registers: CPU 0 Pid: 0, comm: swapper Not tainted RIP: 0010:[<ffffffff80204027>]{serial_in+71} RSP: 0018:ffffffff804dfda8 EFLAGS: 00000202 RAX: 0000000000000000 RBX: 00000000000f4238 RCX: 0000000000008000 RDX: 00000000000003fd RSI: 0000000000000005 RDI: ffffffff804837a0 RBP: ffffffff804837a0 R08: 000000000000006e R09: 00000000409fa439 R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff80413bf4 R13: 000000000000000d R14: 0000000000000010 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff804cb3c0(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0 Process swapper (pid: 0, stackpage=ffffffff804df000) Stack: ffffffff804dfda8 0000000000000018 0000000000040000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Call Trace: <EOE> [<ffffffff80209ff0>]{serial_console_write+96} [<ffffffff80124fcc>]{__call_console_drivers+76} [<ffffffff80125127>]{call_console_drivers+231} [<ffffffff801254b2>]{release_console_sem+82} [<ffffffff80125355>]{vprintk+357} [<ffffffff801253fd>]{printk+141} [<ffffffff802d164c>]{__delay+12} Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89 d0 83 f8 console shuts up ... -- Booting the Suse 9.1 Live CD (I copied all the files on the Live CD to the root file system on an already installed Suse 9.0 system) boot: hda3:/livecd/vmlinuz root=/dev/hda3 initrd=hda3:/livecd/initrd.gz console=ttyS0,115200 Found Linux version 2.6.4-52-default (geeko@buildhost) #1 Wed Apr 7 02:08:30 UTC 2004 bzImage. Loading kernel... ok Loading initrd... ok Jumping to entry point... Linux version 2.6.4-52-default (geeko@buildhost) (gcc version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 0000000040000000 (usable) 128MB vmalloc/ioremap area available. 128MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 262144 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:16 HighMem zone: 32768 pages, LIFO batch:8 DMI not present. ACPI: Unable to locate RSDP Built 1 zonelists Kernel command line: root=/dev/hda3 console=ttyS0,115200 Initializing CPU#0 PID hash table entries: 4096 (order 12: 32768 bytes) CKRM Initialized Detected 1403.889 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Memory: 1009620k/1048576k available (1969k kernel code, 37972k reserved, 677k data, 212k init, 131072k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 2760.70 BogoMIPS Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. Failure registering capabilities with the kernel selinux_register_security: Registering secondary module capability Capability LSM initialized Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) checking if image is initramfs... it is Freeing initrd memory: 26442k freed 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 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX do_initcalls init_elf_binfmt NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay ACPI: ACPI tables contain no PCI IRQ routing entries PCI: Invalid ACPI-PCI IRQ routing table PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) ... the first call_usermodehelper: pci_bus CPU 0: Machine Check Exception: 0000000000000004 Bank 4: b200000000070f0f Kernel panic: CPU context corrupt So, it's pretty clear I am missing a crucial step (or two or three) to booting Linux successfully with LinuxBIOS+FILO. I'd appreciate some help in identifying the basic steps. Thanks, Craig Forney Opus Innovations LLC

1 0

flash_rom with exclude range
by YhLu 12 May '04

12 May '04

Ollie, I add exclude range feature to the Pm49FL004, and it should apply to other chip. But can not make getopt work with input parameter. Please check it. I hardcode exclude_start_position to 0x60000, and exclude_end_postion to 0x8000. Regards YH

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot