OpenBIOS February 2000

openbios@openbios.org

43 participants
83 discussions

Starting linux aint much easy ?
by Winter Jörg 15 Feb '00

15 Feb '00

> I'm not sure how far you've gotten since saturday, but it sound to me like > you are almost there. I have set up a system to boot Linux from a flash. > From your descriptions, I believe you are on the right track. Before > jumping to Linux at 0x1000 for ..... Not far! I still have seveere trouble in starting the kernel ... from the firmware/init/main.c I am loading a vmlinux (1.2megs, uncompressed) image into my memory at 0x100000. I found out that the code in head.S is at offset 0x1000 inside the image. So I jump to 0x101000. That works. I modified the file: kernel/head.S: to notify me if I reached the head code: /* this is my dummycode ... to see if kernel starts .asciz "This is the kernel image entry point\n" << I used this to verify that I dont load garbage into RAM ... Fallback from Protected mode into Realmode, CLR PE1 */ movl %cr0,%eax andl $0xfffffffe,%eax movl %eax,%cr0 jmp flush flush: mov $0x3f8,%dx //here i give a char out to the uart (cause I dont have anything else to talk) mov $0x59,%al out %al ,%dx >>>>> until here everything works fine. but then ... cld movl $(__KERNEL_DS),%eax movl %ax,%ds movl %ax,%es movl %ax,%fs movl %ax,%gs #ifdef __SMP__ orw %bx,%bx jz 1f ... ... a bit later it should do: (same file) xorl %eax,%eax lldt %ax cld # gcc2 wants the direction flag cleared at all times call SYMBOL_NAME(start_kernel) L6: jmp L6 # main should never return here, but # just in case, we know what happens. ... therefore I expected to see the message i have put in /usr/src/linux/init/main.c : start_kernel(void) asmlinkage void __init start_kernel(void) { char * command_line; int i; #ifdef __SMP__ static int boot_cpu = 1; /* "current" has been set up, we need to load it now */ if (!boot_cpu) initialize_secondary(); boot_cpu = 0; #endif /* * Interrupts are still disabled. Do necessary setups, then * enable them say that were here already ... */ outb(0x58,0x03f8); for (i=0; i<0x0fff; i++); printk(linux_banner); .... .... but somewhere inbetween the machine stops. I cannot see my second char on the uart. I dont have an in-circuit debugger and since I´m not the prophet I dont know why and where it crashes ... Any ideas on that ?? btw. sorry for the lots of code i sent, but like that it was easier to show where I got stuck ... greetings, Jake. - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

2 1

ram on l440gx+
by Ronald G. Minnich 15 Feb '00

15 Feb '00

oops. While I am powering it up I'm doing something write. Writes always fail. I think it may be a refresh problem but ... who knows. I'm looking. All ideas welcome. I can forward my code to this list if anyone wants a look. ron - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

RE: [OpenBIOS] suggestion on ordering things
by Marcus Gossner 15 Feb '00

15 Feb '00

Hi, this is the POST code order of my Phoenix BIOS: 02 c8 c9 24 04 06 18 07 08 c4 11 0e 0c 16 17 28 3a 2a 2c 2e 2f 38 20 29 33 c1 09 0a 0b 0f 10 14 1a 1c 22 32 67 69 6b 3c 3d 42 46 45 47 49 c6 c5 48 4a 4c 24 59 cc 55 52 54 76 58 41 4b 4e 50 51 9d 5a 5b 5c 60 62 64 66 68 6a 6c 6e 70 72 4f 7c 7d 7e 80 ca 88 8a 81 87 85 82 84 86 83 89 8c cb cd 90 8b 95 92 b6 98 93 9c c7 9e a0 a2 a4 c3 ba c3 a8 aa ac ae b0 b2 b4 b5 be b6 bc b7 bd bf 8f 91 9f 97 99 b1 b9 c0 Marcus > -----Original Message----- > From: David Christensen > Sent: Monday, February 14, 2000 6:26 PM > To: openbios(a)elvis.informatik.uni-freiburg.de > Subject: RE: [OpenBIOS] suggestion on ordering things > > If you're looking for an idea on what to do during BIOS power-on self-test > (POST) you may start with this link: > http://www.phoenix.com/pcuser/userman.pdf > > Starting on page 35 you'll get a listing of POST codes and approximately > what occurs at each code. Unfortunately the codes are listed in numerical > order, not the order that they occur, but you should be able to figure out > which codes require RAM and which don't. Memory sizing occurs at POST > code > 28h, then you probably want to initialize RAM very soon afterwards by > writing a known value to every memory location to clear up any parity/ECC > errors that may be present because the contents of DRAM are not known at > power-up. > > Dave > > -----Original Message----- > From: owner-openbios(a)elvis.informatik.uni-freiburg.de > [mailto:owner-openbios@elvis.informatik.uni-freiburg.de]On Behalf Of > Ronald G. Minnich > Sent: Monday, February 14, 2000 7:37 AM > To: openbios(a)elvis.informatik.uni-freiburg.de > Subject: [OpenBIOS] suggestion on ordering things > > > I think memory startup should happen first or early. On the new machines > you can't use ram til you power on memory. > > ron > > - > To unsubscribe: send mail to majordomo(a)freiburg.linux.de > with 'unsubscribe openbios' in the body of the message > > - > To unsubscribe: send mail to majordomo(a)freiburg.linux.de > with 'unsubscribe openbios' in the body of the message - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

RE: [OpenBIOS] Exception 13 ?
by Attarian, Gary 14 Feb '00

14 Feb '00

I'm not sure how far you've gotten since saturday, but it sound to me like you are almost there. I have set up a system to boot Linux from a flash. >From your descriptions, I believe you are on the right track. Before jumping to Linux at 0x1000 for zImages and 0x10000 for bzImages you have to have the system set up the same way a standard POST would have. That is, all of the peripherals need to be active and any machine dependant initializations need to have occured. Finally you need to put the processor into a quasi protected mode (I've heard it called unreal mode but I'm not sure if there is an official name). Basically this means you need to set up a GDT which alows access to all memory. And finally you need to jump to the Linix kernel with a far jump using the 32 bit address override. The code which linux loads ont a floppy to do just this stuff is in the file kernel/arch/i386/boot/setup.S. It has a lot of moving the kernel code which I believe you've already got. But then it does some setup stuff (and explains it better than I can) that you need. Once you've got this stuff I think you shold be able to boot the linux image you've loaded. :) Let me know how it goes and good luck! Gary > -----Original Message----- > From: Winter Jörg [SMTP:joerg.winter@disch-gmbh.de] > Sent: Saturday, February 12, 2000 12:56 AM > To: openbios(a)elvis.informatik.uni-freiburg.de > Subject: [OpenBIOS] Exception 13 ? > > > James: (jvh(a)uclink4.berkeley.edu): Thanks for the hint on loading a > Kernel, > but: > > Now I have a verified routine that loads the kernel (block by block) from > my > ATA-Disk into memory (at whatever I like. Currently at 0x00010000). I´m > loading a zImage at 0x00010000, the bootsect at 0x9000, > the setupsectors (4) at 0x9200. It´s just like the other loaders do it > ...he? > > I have the code like: static void (*v)() =(void *)KERNEL_START; > > I start like: v(); > > and the machine (the openbios) throws me an exception 13. (general > Protection Fault errorcode 0). > > I tried nearly any combination of stack-location, entry-adress and > kerneltype ... all fails ... > I now read alot about descriptors and segments and so cause I suspect the > problem is somewhere there ... > > But I just dont get the point. What am I doing wrong now ?? I thought the > kernel would just set up and start? > > I figured out that already the jump done with the v(); is the one that > causes the exception, no matter if there is a kernel or just dummy code > (like: jmp $). > > There must be something I misunderstood completely !! Help, I´m lost ... > > greetinx, J.Winter > > - > To unsubscribe: send mail to majordomo(a)freiburg.linux.de > with 'unsubscribe openbios' in the body of the message

1 0

suggestion on ordering things
by Ronald G. Minnich 14 Feb '00

14 Feb '00

I think memory startup should happen first or early. On the new machines you can't use ram til you power on memory. ron - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

3 3

Exception 13 ?
by Winter Jörg 14 Feb '00

14 Feb '00

James: (jvh(a)uclink4.berkeley.edu): Thanks for the hint on loading a Kernel, but: Now I have a verified routine that loads the kernel (block by block) from my ATA-Disk into memory (at whatever I like. Currently at 0x00010000). I´m loading a zImage at 0x00010000, the bootsect at 0x9000, the setupsectors (4) at 0x9200. It´s just like the other loaders do it ...he? I have the code like: static void (*v)() =(void *)KERNEL_START; I start like: v(); and the machine (the openbios) throws me an exception 13. (general Protection Fault errorcode 0). I tried nearly any combination of stack-location, entry-adress and kerneltype ... all fails ... I now read alot about descriptors and segments and so cause I suspect the problem is somewhere there ... But I just dont get the point. What am I doing wrong now ?? I thought the kernel would just set up and start? I figured out that already the jump done with the v(); is the one that causes the exception, no matter if there is a kernel or just dummy code (like: jmp $). There must be something I misunderstood completely !! Help, I´m lost ... greetinx, J.Winter - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

4 3

Newbie question about the FAQ
by Kervin Low 13 Feb '00

13 Feb '00

Hi, I have been trying to retrieve the FAQ from the OpenBIOS homepage for the past couple of days. The server holding the document seems to be down. Has anyone else encountered this problem? Is there a mirror somewhere where I could get hold of this? Thanks. Kervin - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

2 1

openbios on nvram on l440gx+
by Ronald G. Minnich 12 Feb '00

12 Feb '00

well, I have my first cut, and it failed. It got to the sdram init and died. such is life ... you can see the story at www.acl.lanl.gov/linuxbios ron - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

5 5

"OpenBIOS" from AOpen
by Daniele Frijia 12 Feb '00

12 Feb '00

Hiho... Please take a look at: http://www.aopen.com.tw/company/news/1999/openbios.htm and tell me something about this kind of product. Are we still able to use the word "OpenBIOS"? Regards, Daniele - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

4 3

RE: [OpenBIOS] Exception 13 ?
by Winter Jörg 12 Feb '00

12 Feb '00

Yeah, thanks, but that still doesnt tell me anything about the exception problem. (I´m having my eyes open now since 27 hours and still no idea whats wrong with the code ... thats annoying) greetings to u, J. Winter - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →