RAM codes.
by Feng, Libo
I am studying the LinuxBios project. I have a question about the RAM code: from Makefile, it seems that LinuxBios could load codes from FLASH to RAM twice, first for linuxbios_ram, second for so-called payload. My understanding is correct or not. However, also from Makefile, it seems that linuxbios is dependent on LINUXBIOS_RAM_ROM, but doesn't include it. The below is abstracted from a Makefile:
linuxbios: crt0.o $(INIT-OBJECTS) $(LINUXBIOS_APC) $(LINUXBIOS_RAM_ROM) ldscript.ld
$(CC) -nostdlib -nostartfiles -static -o $@ -T ldscript.ld crt0.o $(INIT-OBJECTS)
$(CROSS_COMPILE)nm -n linuxbios | sort > linuxbios.map.
So, there is no action on LINUXBIOS_RAM_ROM. Does it mean linuxbios_ram is not very important. Even without it, the system is also ok?
Feng Libo
13 years, 3 months
- 2
- 1
Filo problems booting El Torito (LiveCD) CD-ROMS?
by roger
Could it be I'm just having problems using Linuxbios & Filo under Qemu
emulation instead of actually booting from a flash device?
Anyways, here's my debug info:
I'm successfully using Qemu to load Linuxbios with a filo payload
specifying "hdc1" as my CD-ROM device within the Filo Config file.
/dev/hdc = DVD-ROM with DVD+R LiveCD
/dev/hdd = CD-ROM with CD-R LiveCD
Using an actual CD-ROM (DVD-ROM) device with the Qemu "-cdrom /dev/hdc"
option :
$ /home/roger/tmp/qemu/bin/qemu -L ~ -nographic -cdrom /dev/hdc -boot d
<snip Linuxbios & Filo messages>
boot: hdc1
malloc_diag: alloc: 208 bytes (5 blocks), free: 16168 bytes (1 blocks)
malloc_diag: alloc: 224 bytes (6 blocks), free: 16152 bytes (1 blocks)
file_open: dev=hdc1, path=<NULL>
find_ide_controller: found PCI IDE controller 8086:7010 prog_if=0x80
find_ide_controller: secodary channel: compatibility mode
find_ide_controller: cmd_base=0x170 ctrl_base=0x374
ide_software_reset: Waiting for ide1 to become ready for reset... ok
init_drive: Testing for hdc
init_drive: Probing for hdc
print_status: IDE: status=0x41, err=0x4
init_drive: Testing for hdc
init_drive: Probing for hdc
hdc: ATAPI: QEMU CD-ROM
init_drive: Testing for hdd
init_drive: Probing for hdd
print_status: IDE: status=0x0, err=0x1
init_drive: Testing for hdd
init_drive: Probing for hdd
print_status: IDE: status=0x0, err=0x1
atapi_detect_medium: block_len=2048
atapi_detect_medium: sectors=520415
1016MB medium detected
open_pc_partition: pc partition magic number not found
open_eltorito_image: El-Torito boot catalog at sector 53
open_eltorito_image: id=''
Disc doesn't use boot disk emulation
devopen: can't open partition 1
malloc_diag: alloc: 208 bytes (5 blocks), free: 16168 bytes (1 blocks)
malloc_diag: alloc: 192 bytes (4 blocks), free: 16184 bytes (1 blocks)
boot: hdc1
Using a Loop ISO Filesystem specified as a "-cdrom" option for Qemu:
$ /home/roger/tmp/qemu/bin/qemu -L ~ -nographic
-cdrom /home/roger/gentoo/install
cd/install-x86-minimal-2006.1.iso
<snip Linuxbios & Filo messages>
boot: hdc1
malloc_diag: alloc: 208 bytes (5 blocks), free: 16168 bytes (1 blocks)
malloc_diag: alloc: 224 bytes (6 blocks), free: 16152 bytes (1 blocks)
file_open: dev=hdc1, path=<NULL>
find_ide_controller: found PCI IDE controller 8086:7010 prog_if=0x80
find_ide_controller: secodary channel: compatibility mode
find_ide_controller: cmd_base=0x170 ctrl_base=0x374
ide_software_reset: Waiting for ide1 to become ready for reset... ok
init_drive: Testing for hdc
init_drive: Probing for hdc
print_status: IDE: status=0x41, err=0x4
init_drive: Testing for hdc
init_drive: Probing for hdc
hdc: ATAPI: QEMU CD-ROM
init_drive: Testing for hdd
init_drive: Probing for hdd
print_status: IDE: status=0x0, err=0x1
init_drive: Testing for hdd
init_drive: Probing for hdd
print_status: IDE: status=0x0, err=0x1
atapi_detect_medium: block_len=2048
atapi_detect_medium: sectors=27737
54MB medium detected
open_pc_partition: pc partition magic number not found
open_eltorito_image: El-Torito boot catalog at sector 34
open_eltorito_image: id=''
Disc doesn't use boot disk emulation
devopen: can't open partition 1
malloc_diag: alloc: 208 bytes (5 blocks), free: 16168 bytes (1 blocks)
malloc_diag: alloc: 192 bytes (4 blocks), free: 16184 bytes (1 blocks)
boot: hdc1
--
Roger
http://www.eskimo.com/~roger/index.html
Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
Sun Jan 28 21:32:04 PST 2007
13 years, 5 months
- 3
- 11
Hang executing memtest86 from Livecd
by roger
Loading memtest86 from a livecd hangs on memtest86 execution.
Thought the following was just an issue with running qemu with
"-no-graphic" option. But running without "-no-graphic", I still get a
hang with executing memtest86.
$ ~/tmp/qemu/bin/qemu -L ~ -nographic -cdrom /dev/hdc
...
pci_init: 00:01.3 8086:7113 0680 00
pci_init: 00:02.0 1013:00b8 0300 00
pci_init: 00:03.0 10ec:8029 0200 00
Press <Enter> for default boot, or <Esc> for boot prompt... timed out
boot: hdc:/isolinux/memtest86
malloc_diag: alloc: 224 bytes (5 blocks), free: 16152 bytes (1 blocks)
malloc_diag: alloc: 240 bytes (6 blocks), free: 16136 bytes (1 blocks)
file_open: dev=hdc, path=/isolinux/memtest86
find_ide_controller: found PCI IDE controller 8086:7010 prog_if=0x80
find_ide_controller: secodary channel: compatibility mode
find_ide_controller: cmd_base=0x170 ctrl_base=0x374
ide_software_reset: Waiting for ide1 to become ready for reset... ok
init_drive: Testing for hdc
init_drive: Probing for hdc
print_status: IDE: status=0x41, err=0x4
init_drive: Testing for hdc
init_drive: Probing for hdc
hdc: ATAPI: QEMU CD-ROM
init_drive: Testing for hdd
init_drive: Probing for hdd
print_status: IDE: status=0x0, err=0x1
init_drive: Testing for hdd
init_drive: Probing for hdd
print_status: IDE: status=0x0, err=0x1
atapi_detect_medium: block_len=2048
atapi_detect_medium: sectors=520415
1016MB medium detected
Mounted iso9660
malloc_diag: alloc: 224 bytes (5 blocks), free: 16152 bytes (1 blocks)
elf_load: Not a bootable ELF image
malloc_diag: alloc: 240 bytes (6 blocks), free: 16136 bytes (1 blocks)
file_open: dev=hdc, path=/isolinux/memtest86
devopen: already open
malloc_diag: alloc: 224 bytes (5 blocks), free: 16152 bytes (1 blocks)
Possible very old Linux (protocol 0x0) zImage or Image.
init_linux_params: Setting up paramters at 0x90000
set_memory_size: 0000000000000ba4 - 00000000000f0000
set_memory_size: 00000000000f0400 - 0000000008000000
set_memory_size: ramtop=0x8000000
set_memory_size: ext_mem_k=64512, alt_mem_k=130048
load_linux_kernel: offset=0xa00 addr=0x1000 size=0x16708
Loading kernel... ok
start_linux: eip=0x1000
Jumping to entry point...
--
Roger
http://www.eskimo.com/~roger/index.html
Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
Tue Jan 30 14:31:58 PST 2007
13 years, 5 months
- 1
- 0
Run from flash hang
by Krzysz Kowalski
Hi all!
I try write my own code which changes Cas Latency on motherboard with AM2 socket (CPU AMD64 family 0fh, motherboard with original BIOS).
My program is on FLASH chip in network card, on address 0xFDEC0000. I put execution there and program works (I can see that FLASH is reading).
The program hangs when I set EnDramInit (reg. 0x7c, bit 31, function 2, device 24).
Address map configuration is set properly. Program is running from flash - why program hangs?
Best regards
Kris
----------------------------------------------------
Ostatnia sobota karnawału - wielka impreza! Wyjątkowy koncert noJazz
- gwiazdy funk, jazz, hiphop. Występy czołówki polskich DJ.
17.02.2007 - Fabryka Trzciny, Warszawa - Szczegóły:
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fd65.html&sid=1…
13 years, 5 months
- 1
- 0
[PATCH] Filo README
by roger
Can somebody please update the Filo README file to including the
following concerning CD-ROM device file syntax?
ie. CD-ROM device is to be specified as "hdc1" and not "hdc"!
Following are the relevant Filo documentation clippings:
According to: http://te.to/~ts1/filo/CHANGES
"* Support for mounting boot disk image of El Torito bootable CD-ROM.
("hdc1" means the boot disk image of the CD-ROM at hdc.)"
However, I only see a very vague reference for the syntax of specifying
CD-ROM drives within Filo's README:
"Notation of DEVICE for IDE disk and CD-ROM is same as in Linux (eg.
hda1 means the first partition of master device on primary IDE
channel)."
With the above Filo README information, the user is going to think
"/dev/hdb" or "hdb" instead, FILO wants to see "hdb1"!
--
Roger
http://www.eskimo.com/~roger/index.html
Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
Sun Jan 28 21:30:07 PST 2007
13 years, 5 months
- 1
- 0
AMD Socket F BIOS information
by Dave Graham
Hi all,
I'm new to the list and just wanted to find out about any socket F mainboard
bios' floating around.
I'm also working on a project to allow AMD Athlon FX-7x series processors to
be used on Opteron 2000 based boards. I've got the hardware, just need the
know-how.
any insite would be GREATLY appreciated.
--
Dave Graham
Flickerdown Data Systems
1207 Main St. #2
Holden, MA. 01520
978.239.2489
13 years, 5 months
- 2
- 1
Cisco Content Engine ce507 Flash bios and boot
by marks twotoe.com
There are a lot of Cisco ce507 content engines going very cheap on the big
auction at the moment.
You can even pick one up on ebay for as low as ~$10AU if you are dillegent
enough watching the auctions.
Although they are obsolete for there intended purpose the hardware is very
cool.
The ce507 contain:
P3/600 cpu
256 meg ram
symbios 83C895 with 18gig deathstar drive
asiliant 69000 video chip,
1 IDE port
Floppy port
i8042 kb/mous interface
2 standard comports.
2 intel e100 (82559) network interfaces.
The chipset is 443BX with a PIIX4E.
The bios is a general software job, possibly with video/mouse/keyboard
handling removed.
All video goes out the console port (com1) at 9600, as does the input from
the kb/mouse.
The video and keyboard/mouse ports are availible via headers.
Although the kernel detects the i8042 and the asiliant video, I am unable to
get any video besides a cursor and no input from the kb/mouse happening.
The flash chips are 82F128J and a 82F400B and there is an altera EPM7032
sitting between them.
One of the flash chips is for the bios, the second is for the boot.
There is also a 93C46 1K microwire eeprom onboard.
If you access the bios at post and set the boot device to other than flash
you can boot floppy/ide/scsi.
In this way I have slack up and running on sda.
I also have zeroshell and ubuntu pyramid running off a cf card plugged into
ide0.
I used a boot floppy and scsi cd to install slack.
After that long winded background my 2 questions are:
Has anyone managed to put openbios on one of these or similar boards?
Has anyone managed to access the boot flash on one of these or similar
boards?
If so, what is the proceedure?
Best regards,
Marks < m a r k s @ t w o t o e . c o m >
13 years, 5 months
- 1
- 0