HDAMA+FILO booting SUSE Linux
Craig C Forney
cforney at opus.com
Thu May 13 02:37:00 CEST 2004
YH,
Thanks for the tip, but I had already tried all the failsafe options,
and I was still having trouble booting.
I stumbled upon a solution, and can now boot Suse Linux 9.0 from
HDAMA+LINUXBIOS+FILO only using a serial connection. Using
LINUXBIOS+FILO, I booted the 9.0 Suse CD and ran the repair function on
the 9.0 system on the hard drive (which has always booted just fine
under the HDAMA Phoenix BIOS). Somehow, I assume the reconfiguring must
have changed some dependencies on the Pheonix BIOS, thus allowing
LinuxBIOS to boot properly. I had to make a few changes to the /etc/rc
files (remove the keyboard startup), and I was able to get it to boot up
completely into init state 3.
So, I'm still struggling with trying to load off of the Suse 9.0
Distribution DVD. I'd really like to be able to load a complete system
from scratch using the serial port. It seems awfully close (the repair
worked fine ... even the update sems to work).
If anyone out there has been successful loading a disk using a standard
distribution (I'm not that particular about which distribution), I'd
like to hear about it. Alternatively, if there is a reasonable way to
make a custom distribution that would work, I'd appreciate any advice.
Thanks,
Craig Forney
Opus Innovations LLC
> -----Original Message-----
> From: YhLu [mailto:YhLu at tyan.com]
> Sent: Wednesday, May 12, 2004 1:23 PM
> To: cforney at opus.com; linuxbios at clustermatic.org
> Subject: 答复: HDAMA+FILO booting SUSE Linux
>
>
> Try add
>
> acpi=off
>
> YH
> -----邮件原件-----
> 发件人: Craig C Forney [mailto:cforney at opus.com]
> 发送时间: 2004年5月12日 12:42
> 收件人: linuxbios at 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 at 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 at 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 at clustermatic.org
> http://www.clustermatic.org/mailman/listinfo/l> inuxbios
>
>
More information about the coreboot
mailing list