coreboot

coreboot@coreboot.org

39582 discussions

linuxbios with ADLO [EPIA]
by NEWBELL7＠magicn.com 30 Apr '03

30 Apr '03

Hello! Long time no see. I am trying to use framebuffer using linuxbios. So I am about to use ADLO. linuxbios -> etherboot -> ADLO -> Bochs -> VGA BIOS -> LiLo -> Linux ( flash rom ) ( remote server ) (MBR) Is that sequence right ? And I adopt the code which Andrew lp wrote on mailing list to enabel VGA device. But etherboot didn't work. ( Before enabling VGA device , it worked. ) .. The debug message is below. why didn't etherboot worked ? I think that the difference between enabling VGA and disabling VGA is PCI bus scanning and resource allocation part. Who does know this problem ? Thanks for your attention and your help. ======================================================================== ===== 0 LinuxBIOS-1.0.0 Wed Apr 30 15:46:33 KST 2003 starting... Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.0.0 Wed Apr 30 15:46:33 KST 2003 booting... Finding PCI configuration type. PCI: Using configuration type 1 Scanning PCI bus...PCI: pci_scan_bus for bus 0 PCI: 00:00.0 [1106/0601] PCI: 00:01.0 [1106/8601] PCI: 00:11.0 [1106/8231] PCI: 00:11.1 [1106/0571] PCI: 00:11.2 [1106/3038] PCI: 00:11.3 [1106/3038] PCI: 00:11.4 [1106/8235] PCI: 00:11.5 [1106/3058] PCI: 00:11.6 [1106/3068] PCI: 00:12.0 [1106/3065] PCI: pci_scan_bus for bus 1 PCI: 01:00.0 [1023/8500] PCI: pci_scan_bus returning with max=01 PCI: pci_scan_bus returning with max=01 done Allocating PCI resources... PCI: 00:00.0 register 10(00000008), read-only ignoring it PCI: 00:00.0 register 10(00000008), read-only ignoring it PCI: 00:00.0 register 10(00000008), read-only ignoring it PCI: 00:00.0 register 10(00000008), read-only ignoring it ASSIGN RESOURCES, bus 0 PCI: 00:01.0 1c <- [0x00001000 - 0x00000fff] bus 1 io PCI: 00:01.0 24 <- [0xfe900000 - 0xfe8fffff] bus 1 prefmem PCI: 00:01.0 20 <- [0xfd800000 - 0xfe8fffff] bus 1 mem ASSIGN RESOURCES, bus 1 PCI: 01:00.0 10 <- [0xfd800000 - 0xfdffffff] mem PCI: 01:00.0 14 <- [0xfe800000 - 0xfe81ffff] mem PCI: 01:00.0 18 <- [0xfe000000 - 0xfe7fffff] mem ASSIGNED RESOURCES, bus 1 PCI: 00:11.1 20 <- [0x00001c40 - 0x00001c4f] io PCI: 00:11.2 20 <- [0x00001c00 - 0x00001c1f] io PCI: 00:11.3 20 <- [0x00001c20 - 0x00001c3f] io PCI: 00:11.5 10 <- [0x00001000 - 0x000010ff] io PCI: 00:11.5 14 <- [0x00001c50 - 0x00001c53] io PCI: 00:11.5 18 <- [0x00001c60 - 0x00001c63] io PCI: 00:11.6 10 <- [0x00001400 - 0x000014ff] io PCI: 00:12.0 10 <- [0x00001800 - 0x000018ff] io PCI: 00:12.0 14 <- [0xfe900000 - 0xfe9000ff] mem ASSIGNED RESOURCES, bus 0 Allocating VGA resource done. Enabling PCI resourcess...PCI: 00:00.0 cmd <- 06 PCI: 00:01.0 cmd <- 07 PCI: 00:11.0 cmd <- 87 PCI: 00:11.1 cmd <- 81 PCI: 00:11.2 cmd <- 01 PCI: 00:11.3 cmd <- 01 PCI: 00:11.4 cmd <- 00 PCI: 00:11.5 cmd <- 01 PCI: 00:11.6 cmd <- 01 PCI: 00:12.0 cmd <- 83 PCI: 01:00.0 cmd <- 03 done. Initializing PCI devices... PCI devices initialized sizeram: returning 0x3e000 KB sizeram: NOT returning 0x3e000 KB sizeram: there are still some SPD problems ... sizeram: SO we return only 0x10000 KB totalram: 64M Initializing CPU #0 Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 64MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs done. Max cpuid index : 1 Vendor ID : CentaurHauls Processor Type : 0x00 Processor Family : 0x06 Processor Model : 0x07 Processor Mask : 0x00 Processor Stepping : 0x08 Feature flags : 0x00803035 MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled Disabling local apic...done. CPU #0 Initialized Mainboard fixup IDE enable in reg. 50 is 0x7 set IDE reg. 50 to 0x7 IRQs in reg. 4c are 0x4 setting reg. 4c to 0x4 enables in reg 0x40 0x8 enables in reg 0x40 read back as 0xb enables in reg 0x9 0x8f enables in reg 0x9 read back as 0x8a command in reg 0x4 0x81 command in reg 0x4 reads back as 0x7 Ethernet fixup Configuring VIA LAN RTC Init Invalid CMOS LB checksum Final mainboard fixup Southbridge fixup setting southbridge Assigning IRQ 12 to 0:11.2 Readback = 12 Assigning IRQ 12 to 0:11.3 Readback = 12 Assigning IRQ 10 to 0:11.5 Readback = 10 Assigning IRQ 10 to 0:11.6 Readback = 10 setting ethernet Assigning IRQ 11 to 0:12.0 Readback = 11 setting pci slot Checking IRQ routing tables... /home/newbell/LinuxBios/freebios/src/arch/i386/lib/pirq_routing.c: 24:check_0 done. Copying IRQ routing tables to 0xf0000...done. Verifing priq routing tables copy at 0xf0000...failed Wrote linuxbios table at: 00000500 - 00000664 checksum 2a26 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 203:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Searching for 16 byte tags 64:rom_read_bytes() - overflowed source buffer. max_block = 15 init_bytes found 0 tags Found ELF candiate at offset 0 New segment addr 0x94000 size 0x74e8 offset 0x60 filesize 0x396c (cleaned up) New segment addr 0x94000 size 0x74e8 offset 0x60 filesize 0x396c Loading Segment: addr: 0x0000000000094000 memsz: 0x00000000000074e8 filesz: 0x0c Clearing Segment: addr: 0x000000000009796c memsz: 0x0000000000003b7c Jumping to boot code at 0x94000

1 0

Linuxbios + Etherboot + tagged Kernel Image
by Yap Ee Huey 30 Apr '03

30 Apr '03

Hi hackers : I am a little bit confused here after building linuxbios, etherboot and making a tagged kernel image with mknbi. Hopefully I can get some help here : I have made ide_disk.elf, (22k) I tag bzImage with mknbi-linux, (888k) I have built linuxbios.rom (64k) I have 256k bios, so the kernel should be put somewhere on my harddisk. If i am not wrong my ide_disk.elf should be placed at the first sector of my bios rom. My question is: where should I put my Kernel Image and linuxbios.rom so that ide_disk.elf will know where to get and load them ? Do I need to modify the -DDEFAULT_BOOTFILE option which defaulted to tftp:///tftpboot/kernel ? Thanks a lot ! best regards, eehuey _________________________________________________________________ Are you in love? Find a date on MSN Personals http://match.msn.com.my/

4 4

Another way of using ADLO
by bendany 29 Apr '03

29 Apr '03

Hm, It seems that my way is buggy, But it works. ;-) I am trying to use the VGA with LinuxBIOS. since I am trying to use the Xwindows. if you want to start the Xserver, you must have the vgabios. I think when the Xserver startup, it will probe the videocard. but since the LinuxBIOS does not have the videobios. so the Xserver crash. you can using the Xserver with the kernel framebuffer driver. such as fbdev. but it lack the ability of hardware accel. such as play the movie fullscreen. so use the ADLO & bochs bios & vgabios will give you a second way to run the Xserver. since the LinuxBIOS switch the CPU into protected mode early, and the commercial vgabios runs in realmode. so the commercial vgabios cann't run after the LinuxBIOS. so the ADLO will do some preparation works. Load the bochs bios & vgabios. switch the CPU to the realmode. execute the bochs bios. the bochs will try to init the vgabios first.it scan the address 0xC0000 to 0xC7FFF in 2k increments. and then scan the General ROM from 0xC8000 to 0xDFFFF in 2k increments, so if we put the etherboot+AA patch after the address of vgabios. the etherboot will be excuted after bochs init the vgabios. the way why I do this is that the bochs bios is lack the ability of dealing with the real hardware. such as ide harddisk. In my experiment, when I use the IBM 30G harddisk. the speed of lilo & grub load the kernel normally, but when I use the flash IDE. the speed of lilo & grub , or syslinux, is too slow. if you want to run the etherboot with the bochs bios. you must do some work yourself. first, using ADLO to get your own vgabios. my mainboard chipset is sis630. the vgabios is 48kb. plus the etherboot+AA rom. and the bochs bios .altogether 144kb. and the ADLO only provide 3 types of elf loader. so you must create the 145kb loader yourself. and also modify the loader.s. and you will need to modify the etherboot5.0.6+AA patch too. hope help. Best regards.

4 7

RE: Linuxbios + Etherboot + tagged Kernel Image
by Yap Ee Huey 29 Apr '03

29 Apr '03

Hi, I am using etherboot 5.1.7 , any later versions will have it. regards, eehuey >Hi, > > what version of etherboot are you using, I tried with etherboot5.0.9 and >etherboot5.0.10 but "make ide_disk.elf" doesn't work, neither does "make >bin32/ide_disk.elf" > >Regards, >Shubhangi _________________________________________________________________ Download the latest MSN Messenger http://messenger.msn.com.my

1 0

Re: Bios flashing continued
by Nathanael Noblet 29 Apr '03

29 Apr '03

On Tuesday, April 29, 2003, at 07:42 AM, ron minnich wrote: > Do you have a plain old flash part you can put in there? SST 28SF040 is > ideal. So I ordered the flash parts that were already in the machine when I bought it, the chances of another type of flash working is slim to none right? Were I to purchase the one above, how would I know if it would work? -- Nathanael Noblet Gnat Solutions 4604 Monterey Ave NW Calgary, AB T3B 5K4 T/F 403.288.5360 C 403.809.5368 http://www.gnat.ca/

4 7

Socket 370 boards...
by Dale Harris 29 Apr '03

29 Apr '03

Hi, I'm kind of looking at a situation where I'm probably going to purchase some dual CPU Socket 370 boards, cause I have bunch of Pentium III - 1Ghz chips laying around. What is the best board at this point to purchase, that is supported by LinuxBIOS? Need to be able to support at least 2Gb RAM. -- Dale Harris rodmur(a)maybe.org /.-)

1 0

Re: Bios flashing continued
by Yap Ee Huey 29 Apr '03

29 Apr '03

Hi, I have been looking for a program to flash my eeprom as well. The standard flash programs do not allow me to burn unidentified bios. I have found two very useful and general flash and burn programs : (1)UNIFLASH (DOS program) http://www.pppr.sk/rainbow/programs.html (2)/dev/bios (Linux program) http://www.openbios.info/development/devbios.html Hope it helps u ! Although they don't work on my board -> TUSL2-C (eeprom SST49LF002A) because of some undocumented write protect registers maybe. good luck, eehuey > >Message: 5 >Date: Mon, 28 Apr 2003 13:07:24 -0600 >Subject: Re: Bios flashing continued >From: Nathanael Noblet <nathanael(a)gnat.ca> >To: linuxbios(a)clustermatic.org > > >On Monday, April 28, 2003, at 09:23 AM, ron minnich wrote: > > > if you get really stuck, try the MTD drivers from linux. I am hoping > > Ollie > > can help tell what's going on. > >So I have been unable so far to make any progress. Using google to >search for bios flashing mtd gets me nothing of value. I can't get the >flash_and_burn stuff to do anything for me so I hope Ollie can help as >well. If there are any resources I should look/read please pass them >this way as well. > >-- >Nathanael Noblet >Gnat Solutions >4604 Monterey Ave NW >Calgary, AB >T3B 5K4 > >T/F 403.288.5360 >C 403.809.5368 > >http://www.gnat.ca/ > > _________________________________________________________________ Download ringtones, logos and picture messages from MSN Malaysia http://www.msn.com.my/mobile/ringtones/default.asp

4 5

Question on Storage Area Networks(SAN) with LINUX, what is the BEST forrum
by Deepak Kotian 29 Apr '03

29 Apr '03

Hi , Sorry, off topic/may if off forum.. But any help would be appreciated. Where would be best place to put queries for SAN Linux HOSTS. As LinuxBIOS is close with clusters, I am just guessing some people on this list may have good idea about this. Thanks and Regards Deepak

1 0

can't get 2.4.19 to compile
by demian sinclair 29 Apr '03

29 Apr '03

I am trying to get linux bios to work on my m758lmr+ for my carputer. Unfortunately I am stuck at the first stage. When I try make bzImage after patching with the 2.4.19-sis patch, I get this: ld -m elf_i386 -T /usr/src/linux-2.4.19/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o init/do_mounts.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/video/video.o \ net/network.o \ /usr/src/linux-2.4.19/arch/i386/lib/lib.a /usr/src/linux-2.4.19/lib/lib.a /usr/src/linux-2.4.19/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/video/video.o(.data+0x1bd4): undefined reference to `local symbols in discarded section .text.exit' make: *** [vmlinux] Error 1 This is on debian woddy with gcc 2.95. I have also tried 2.4.17 and I get this: ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/ide/idedriver.o drivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/mtd/mtdlink.o drivers/video/video.o drivers/usb/usbdrv.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/sound/sounddrivers.o(.data+0x1d4): undefined reference to `local symbols in discarded section .text.exit' drivers/mtd/mtdlink.o(.text.lock+0xf6): undefined reference to `local symbols in discarded section .text.exit' drivers/video/video.o(.data+0x1bd4): undefined reference to `local symbols in discarded section .text.exit' make: *** [vmlinux] Error 1 Would someone plz point me in the right direction. Thanks, DS

3 2

RE: Using ADLO with Linuxbios
by dkotian3＠vsnl.net 29 Apr '03

29 Apr '03

But, with this the romimage created would very large to to fit in an 256K/512K FLASH ROMS. One needs to put only minimal LinuxBIOS on BIOS flashrom due to size constraint of the flashrom and boot it from CF, how does one do it ? Can someone give sample config for this as well if possible.. Could someone please elaborate. Regards Deepak rminnich(a)lanl.gov wrote On Tue, 29 Apr 2003, Shubhangi Jadhav wrote: > Can this be the same kernel image from which I created my elf image? stupid me. Sorry. you mkelfImage and then use that as the payload. Memory glitch on my part. ron

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot