OpenBIOS

openbios@openbios.org

4297 discussions

SiS 630 Status Udpate
by Ollie Lho 04 Jun '00

04 Jun '00

Ron, Could you please give us the status update on those topic ? DRAM SIZING Could intel_sis630ram.S work on your M/B, does it get corrrect value for ALL three DIMM with Signle/Double sided DRAM ?? SiS' status: yes, all three DIMM and single/double sided DRAM combination ares O.K. Keyboard Can your keybord controller works properly ?? have you monitor port 0x60 to see the scan code you type on keyboard ?? SiS' status: yes, we got correct scan code every time we press the keyboard. Frame Buffer Device Can you use SiSFB or MatroxFB to show the message on monitor ?? If the answer is yes, which Frame Buffer Device are you using ?? How and What is the EXACT procedure to do it ?? SiS' status: no, we can not make SiSFB work under current romimage. We are pushing VGA BIOS group very hard to release the code ASAP. For the moment, we are considering using Matrox FB instead of SiSFB, if you are succeeded in setting up MatroxFB. (We will be back on SiS FB once VGA BIOS provide enough information). PCI configuration (PCI IDE and etc.) Can you init the PCI devices ?? especially PCI IDE ?? since we need PCI IDE to mount root filesystem. CVS configureation What is the progression you and Jeff made in putting LinuxBIOS on FreeBIOS CVS ?? Other things Do you have another thing you want to know ?? What else do you want to sync with us ?? P.S We are having a long weekend this week. K.M. and I will not here until June 7, but we will keep monitoring the maillist. Ollie - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

4 4

Current States of LinuxBios on SiS 630
by Ollie Lho 02 Jun '00

02 Jun '00

Ron, We can boot the kernel from power-on now. With the romimage which will be sent to you seperately, we can reach the point of kernel_thread(init,...); in arch/i386/kernel/setup.c which means that everything is ready and we are going to load/execute scripts in rc.d. We are using kernel-2.3.99pre5 with the patch in export.tgz. If you can monitor port 0x80 with debug card you can get 0xed at the end. We don't experience the keyboard problem you described, does that happen after the kernel_thread() ?? After initrc are executed ?? The frame buffer device driver is included in 2.4.0-test1 and later kernel. There is some bug in Config.in which makes the option absent when make config, but it is really easy to fix. I think we should move to 2.4.0 now since we are going to need fbdev real soon. Finally, could you please put your source to the FreeBIOS CVS ?? Usually we are unsure if our version matches yours, you know, things like this make a lot of trouble. BTW, we are asking VGA BIOS group to release more information/source code. I hope we can turn on the monitor ASAP, using ICE and debug card is really a pain in the ass. P.S. Jeff, could you review the sisfb for us ?? What are we missing from the driver for this special purpose ?? Ollie - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

6 19

linuxbios build for L440GX
by Ronald G Minnich 02 Jun '00

02 Jun '00

this also works. You need two links: 1) ln -s <your-linux-tree> freebios/linuxbios/L440GX/linux 2) ln -s <intel-flash-disk> freebios/linuxbios/intel_flash_disk ron - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

linuxbios checked in to sourceforge, and it is buildable
by Ronald G Minnich 02 Jun '00

02 Jun '00

I just did a checkout of freebios from sourceforge, and was able to bash-2.01$ cd freebios/linuxbios/SIS630/ bash-2.01$ ln -s ~/src/bios/linux . bash-2.01$ make cc -I../../chip/intel -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -c crt0.S cc -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -c ../inflate/main.c ../inflate/main.c:187: warning: conflicting types for built-in function `memset'../inflate/main.c:198: warning: conflicting types for built-in function `memcpy'cc -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -c ../../chip/intel/intel_main.c cc -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -c ../../chip/intel/intel_subr.c cc -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -c fill_inbuf.c -o fill_inbuf.o cc -I ../../include -I. -O2 -DSIS630 -Di686 -Di586 -DINTEL_BRIDGE_CONFIG -DSIS630_NVRAM -DINTEL_PPRO_MTRR -DSIS630_KEYBOARD -c ../../chip/intel/pci.c objcopy -O binary -R .note -R .comment -S linux/vmlinux vmlinux.bin gzip -f -3 vmlinux.bin ld -T ldscript.ld -o linuxbios crt0.o main.o intel_main.o intel_subr.o fill_inbuf.o pci.o nm -n linuxbios > linuxbios.map objcopy -O binary -R .note -R .comment -S linuxbios linuxbios.strip cc -o mkrom ../../mkrom/mkrom.c ./mkrom -s 64 -f -o linuxbios.rom linuxbios.strip dd conv=sync bs=448k if=vmlinux.bin.gz of=vmlinux.bin.gz.block 0+1 records in 1+0 records out cat vmlinux.bin.gz.block linuxbios.rom > romimage cp romimage /tmp bash-2.01$ Works as far as I can tell. For those of you with commit. Be very very careful, please. If you can't test something then don't commit it. It's very easy to screw this up, esp. when it's out of ROM. I'm close to being able to test without the Arium and I'd like to keep it that way :-) For now until I get some more FLASH ram back I can't test anything. This is a snap of my last know good code. I will be putting the SiS keyboard fix in soon. I also worked out a trivial fix for parameters. Try it out if you can (especially you SiS folks :-) ) ron - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

sis630 problem temporary resolution.
by Ronald G Minnich 02 Jun '00

02 Jun '00

There's no current standard way to communicate memory size info from linuxbios boot code to the kernel. My kernel was dying because of a hard-coded size in arch/i386/kernel/setup.c: ALT_MEM_K = 254*1024; The quick fix for now: ALT_MEM_K = 62*1024; I was about to test this when my flash ram stopped programming, I am now waiting on an order for more. Try it on your version. We need a standard way to get PARAM to the kernel, now that the BIOS is no longer there to do it. The 0x90000 PARAM won't work, since that set of locations is managed in code we don't even run (from arch/i386/boot). Ideas welcome. ron p.s. I'd appreciate seeing 'make' errors from anybody. Please remember though that for linuxbios you have to: cd freebios/linuxbios/<mainboard-name>, e.g. cd freebios/linuxbios/SIS630 Then type make Make from the top level of freebios does not work. - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

4 7

Keyboard O.K. On SiS 630
by Ollie Lho 02 Jun '00

02 Jun '00

Ron, We got keyboard working properly on SiS 630 with the pseduo code we sent to you. Again, we can reach kernel_thread(init, ...) and beyond. The C source code and rom image will ge sent in a seperate mail. You mentioned in a post that you can get monitor on ?? Which frame buffer device did you use ?? sisfb ?? How did you do that ? Ollie - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

3 5

SiS 630 booting Linux from power on.
by Ronald G Minnich 30 May '00

30 May '00

We're not up to multiuser, because we have a keyboard hang problem. But we think we'll get that soon. Getting there! ron - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

question for the experts on PII vs. Celeron startup
by Ronald G Minnich 25 May '00

25 May '00

I have been having trouble getting PII to work with memory from powerup. I just now realized that I'm seeing basically the same problem on the Intel and SiS motherboards. Engineers at SiS, using the same linuxbios romimage as I am using, has no troubles on the motherboard BUT: they are using Celeron. (see the linuxbios web page: I can still get the intel motherboard up with linuxbios, but I have to let the flash recovery code run first by twiddling the jumper). The symptom is that during memory init, at some point the processor seems to take a trap during a memory write. It is as though some piece of hardware between the processor and memory is unhappy :-) I'm working with SiS to try a different motherboard. But: I'm now wondering if I'm encountering some kind of PII L2 Cache init problem on the Slot 1 cards I'm using here. I'm very suspicious that I'm seeing a particular kind of problem on my Slot 1 PII systems that SiS is not seeing using a Celeron, and that I'm seeing the same kind of problem on both Intel and SiS mainboards. Any comments on this? Any thoughts? Anyone know if anything special happens for L2 cache on a Slot 1 card at powerup? It would probably look like an IN or OUT to an undocumented address (undocumented since this is Intel we're talking about here). ron p.s. linuxbios: http://www.acl.lanl.gov/linuxbios - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

3 5

Programming ROMS
by Edwin Rhodes 24 May '00

24 May '00

Hi, I've managed to obtain some 486 and 386 ROM's that I would like to program. I would like to replace the current ROM code with that of the linux bios code. unfortunately I don't think that the boards support flash update?? how do I go about re-programming them??? what hardware and software is required to re-write the bios?? would I be able to get away with a hot-swap??? or do i need a proper rom programmer, if so which one would you recommend. thanks, Edwin ps. well done for getting so far with linux bios. if there is anything I can do to help let me know. :)

2 1

RE: [OpenBIOS] Programming ROMS
by Jessen, Per 24 May '00

24 May '00

> -----Original Message----- > From: Edwin Rhodes [mailto:edwin_rhodes@hotmail.com] > Sent: 24 May 2000 15:18 > To: openbios(a)elvis.informatik.uni-freiburg.de > Subject: [OpenBIOS] Programming ROMS > > > Hi, I've managed to obtain some 486 and 386 ROM's that I > would like to program. I would like to replace the current > ROM code with that of the linux bios code. unfortunately I > don't think that the boards support flash update?? how do I > go about re-programming them??? what hardware and software is Assuming they are indeed EPROMs, you need to determine the type of EPROM (make, code - e.g. AMD27Cxxxx and so on). Retrieve the datasheet from the manufacturers website, then determine how to program them. > required to re-write the bios?? would I be able to get away > with a hot-swap??? or do i need a proper rom programmer, if > so which one would you recommend. If the EPROMs are not flashable, simply go for a burner that supports the type of chip(s) you have. I'm not sure what you mean by 'hot-swap' ? regards, Per Jessen - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

Jump to page: