coreboot

coreboot@coreboot.org

11 participants
39712 discussions

RE: [Etherboot-developers] lb+eb+filo in epia-5000
by elife elife 07 Sep '04

07 Sep '04

Hi Yinghai Lu, I don't know whether I am using the last patch. Where can I find the last patch? I browse the eb's cvs tree but seems filo not merge yet. My hardware is VIA EPIA-5000 board. The output of lspci just said 00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10) 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1e) 00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1e) 00:11.4 Non-VGA unclassified device: VIA Technologies, Inc. VT8235 ACPI (rev 10)00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 40) 00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 20) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51) 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) And when I boot from lb, related boot info: usb.c: registered new driver usbdevfs usb.c: registered new driver hub host/usb-uhci.c: $Revision: 1.275 $ time 11:08:56 Sep 6 2004 host/usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:11.2 IRQ routing conflict for 00:11.2, have irq 12, want irq 11 IRQ routing conflict for 00:11.3, have irq 12, want irq 11 PCI: Sharing IRQ 11 with 00:12.0 host/usb-uhci.c: USB UHCI at I/O 0x1c00, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 00:11.3 IRQ routing conflict for 00:11.2, have irq 12, want irq 11 IRQ routing conflict for 00:11.3, have irq 12, want irq 11 PCI: Sharing IRQ 11 with 00:12.0 host/usb-uhci.c: USB UHCI at I/O 0x1c20, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Thanks a lot! >From: "Yinghai Lu" <yhlu(a)tyan.com> >To: "'elife elife'" <rimy2000(a)hotmail.com>, <etherboot-developers(a)lists.sourceforge.net> >CC: <linuxbios(a)clustermatic.org> >Subject: RE: [Etherboot-developers] lb+eb+filo in epia-5000 >Date: Tue, 7 Sep 2004 09:19:57 -0700 > >Are you using the last patch? > >What's your USB controller model and etc? > >Regards > >YH > _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

1 0

lb+eb+filo in epia-5000
by elife elife 07 Sep '04

07 Sep '04

Hi, I am trying to use linuxbios+etherboot+filo to boot from usb stick. I use etherboot-5.2.4_btext_filo_usb.diff.bz2(Thanks, sjames). But the filo can't boot my kernel, below is th output: boot: uda1:/bzImage LinuxLabs USB bootloader New USB device, setting address 2 00000008:00000005:00000050 Manufacturor: USB Product: B�� Serial: ��~? boot: uda1:/bzImage Then I enable the debug info: [FILO]boot eax = 0xfbffffff boot ebx = 0xffffffff boot arg = 0xffffffff FILO version 0.4.1 (beatms@beatms) 2004Ä�� 09ÔÂ07ÈÕÐÇÆÚ¶þ Press <Enter> for default boot, or <Esc> for boot prompt... 2 1 timed out boot: uda1:/bzImage dev=uda1, path=/bzImage LinuxLabs USB bootloader Found UHCI at 00001c00 Resetting UHCI uhc_init setting framelist to: 036a5d10 Starting UHCI HCI at 00001c00 Found UHCI at 00001c20 Resetting UHCI uhc_init setting framelist to: 036a5d10 Starting UHCI HCI at 00001c20 frame_list is at ffffe2f0 frame_list_link: addr: 00058270 frame_list_link: raw addr: 036fdf80 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000001 frame_list_link: depth: 00000000 frame_list is at ffffc2f0 frame_list_link: addr: 00058290 frame_list_link: raw addr: 036fdfa0 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000001 frame_list_link: depth: 00000000 poll_usb1 i=0 poll_u_root_hub1 v=00000580 poll_u_root_hub1 v=00001493 poll_u_root_hub2 v=00001493 poll_u_root_hub21 v=00001493 Connection on port 00001c12 New USB device, setting address 2 uhci_control_msg: request_type = 00000000 request = 00000005 wLength=0 HCI at 00001c00 failed_transaction: TD(00050280): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: ²ÿÿaddr: 000502a0 failed_transaction: ²ÿÿ raw addr: 036f5fb0 failed_transaction: ²ÿÿterminate: 00000000 failed_transaction: ²ÿÿqueue: 00000000 failed_transaction: ²ÿÿdepth: 00000000 failed_transaction: TD(000502a0): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: fc95a2f0 failed_transaction: raw addr: 00000000 failed_transaction: terminate: 00000001 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 configure_device: set_address failed! poll_usb1 i=1 poll_u_root_hub1 v=00000180 poll_u_root_hub1 v=00000080 poll_usb1 i=0 poll_u_root_hub1 v=00000580 poll_u_root_hub1 v=00000493 poll_u_root_hub2 v=00000493 poll_u_root_hub21 v=00000493 Connection on port 00001c12 The usb stick works properly in lb+eb. What do above info mean and what should I do? Thanks a lot! _________________________________________________________________ ��ѽ��н��ʹ�� MSN Messenger: http://messenger.msn.com/cn

2 1

epia m vga + memcpy failed
by Trellix78＠aol.com 07 Sep '04

07 Sep '04

I was trying to figure why VGA wasn't being properly set on my epia m when I found that the code in mainboard.c was looking for device id 0x3123 while my epia m has device id 0x3122 for the CLE266. After changing the id, memcpy is failing to copy the bios code. Anyone know why that could be? Here's a piece of the log: . . . setting ethernet Assigning IRQ 11 to 0:12.0 Readback = 11 setting vga Assigning IRQ 11 to 1:0.0 Readback = 11 setting pci slot setting vt8235 slot Assigning IRQ 5 to 0:11.1 Readback = 5 Assigning IRQ 12 to 0:11.5 Readback = 12 INSTALL REAL-MODE IDT DO THE VGA BIOS found VGA: vid=1106, did=3122 Setting up VGA, VGABIOS_START: 0xfffe0000 First 16 bytes of VGA_ROM: 0x55 0xaa 0x7d 0xe9 0x26 0x7f 0x5e 0x1b 0xfa 0xf9 0xf4 0x82 0x0 0x0 0x0 0x0 Failed to copy VGA BIOS to 0xc0000 First 16 bytes of 0xc0000: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff setting VGA up anyway bus/devfn = 0x100 biosint: # 0x6, eax 0x100 ebx 0x100 ecx 0x100 edx 0x12 biosint: ebp 0x11a2c esp 0xff6 edi 0xda8c esi 0x12350 biosint: ip 0x3 cs 0xc000 flags 0x46 biosint: Oops, exception 6 Stack contents: 0x0003 0xc000 0x0046 0x4d75 0x0000 biosint: Bailing out Checking IRQ routing tables... . . .

2 1

linuxbios can work on QDIA6T MB
by zhu shi song 07 Sep '04

07 Sep '04

My linuxbios (V1) can boot my linux(linux-2.4.26) well. And I can login on serial tty. But vga can't work. There is still one problem that reboot linux make MB halt. When I reboot my linux, the MB halt while bios post code equal 0x10. tks zhu __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

2 1

VIA fastboot MII debug message
by Trellix78＠aol.com 07 Sep '04

07 Sep '04

I just found something interesting. I was playing around with VIA's fastboot debug USB-boot BIOS image for the Epia MII and came across a linuxbios message at the very end after the bootloader complained about not finding a suitable USB boot device. There is no such message in the IDE or CD-ROM images. The fastboot MII images are very fast but they don't work for the non-MII epia and I find it funny that VIA didn't include a way to use hooks like they did for the pre-MII fastboot. I say this because I've been struggling with CLE266 video and linuxbios while VIA releases binary-only images with a linuxbios message that don't work on the epia M.

2 1

Re: VGA Problem about 440bx chipset
by Chiu Gerald 07 Sep '04

07 Sep '04

Wow! I got it! I use another S3 video card,and succeeded in bringing up the VGA,and booted RedHat linux. So wonderful linuxbios is! Richard Smith,thanks for your help very very much! >From: Richard Smith <rsmith(a)bitworks.com> >To: LinuxBIOS <linuxbios(a)clustermatic.org> >Subject: Re: VGA Problem about 440bx chipset >Date: Wed, 01 Sep 2004 10:04:52 -0500 > >Chiu Gerald wrote: > >>you mean that PCI card works? > >Yes some PCI cards work. I've made several Assiliant 65550 and >69000 >based PCI cards work and some S3 based cards work. There are >reports of >some ATI cards working but I am still having problems getting my ATI >M1 >based card to work. > >>Now I changed to a PCI video card,and bochs had run the vga >>bios,but still nothing happened! > >>I have no idea what should I do next. > >Are you setting up the shadowing correctly? You have to setup the >shadowing in loader.s or bochs and the video bios never make it into >ram. The stock ADLO setup won't work on the 440bx. > >I've attached my loader.s which sets up the shadowing correctly. > >Also the DEBUG_SERIAL option in rombios.c is very useful. You can >enable it and all the bochs bios messages will be redirected out the >serial port. This way you can see if bochs rombios is even getting >called. You have to turn it back off to get text on the VGA screen. >But your cards VSYNC should happen regardless. (assuming the vbios >runs >correctly) > >I leave in a few hours and won't be back till Tuesday the 2nd so you >are >on your own for a few days. I'll try to check email during that >time >but I'm not promising anything. > >Search the mailing list for things like "ADLO", "vgabios", etc there >are >several threads on getting this up. _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

3 2

Re: VGA Problem about 440bx chipset
by Gerald Chiu 07 Sep '04

07 Sep '04

Hello,Adam, I have problem on booting win2000,but the ADLO status said win2k is fully supported. The information displayed on screen is below: =============== Please select the operating system to start: Microsoft Windows 2000 Professional Microsoft Windows 98 Use your arrow keys to move the highlight to your choice. Please touch Enter to choose. Seconds until highlighted choice will be started automatically: 0 For troubleshooting and advanced startup options for Windows 2000, press F8. ================ When I choose win2k and touch Enter,it halts, the screen even not change to show progress bar! When I choose win98 ,after showed the welcome logo,it halts with the cursor flashing on the left_upper corner of screen. I want to boot win2k, then could you give me some idea on debugging? >From: Adam Sulmicki <adam(a)cfar.umd.edu> >To: Chiu Gerald <snow2moutain(a)hotmail.com> >CC: linuxbios(a)clustermatic.org >Subject: Re: VGA Problem about 440bx chipset >Date: Sun, 5 Sep 2004 13:26:32 -0400 (EDT) > > >perhaps it would make sense to summarize "lessons learned" and send them >to list, so that whoever will play with ADLO next can benefit from the >knowledge > >Just put in all right keywords so that it is easie to find it later on, >like ADLO, S3, etc. The shadow patch probably isn't big either. > > > >On Sun, 5 Sep 2004, Chiu Gerald wrote: > > > right. > > > > linuxbios+ADLO+Bochs > > > > >From: Adam Sulmicki <adam(a)cfar.umd.edu> > > >To: Chiu Gerald <snow2moutain(a)hotmail.com> > > >CC: rsmith(a)bitworks.com, <linuxbios(a)clustermatic.org> > > >Subject: Re: VGA Problem about 440bx chipset > > >Date: Sat, 4 Sep 2004 10:54:45 -0400 (EDT) > > > > > > > > >is this with ADLO? > > > > > >neat! > > > > > >On Sat, 4 Sep 2004, Chiu Gerald wrote: > > > > > > > Wow! I got it! > > > > I use another S3 video card,and succeeded in bringing up the VGA,and > > booted > > > > RedHat linux. > > > > So wonderful linuxbios is! > > > > Richard Smith,thanks for your help very very much! > > > > > > > > > > > > > > > > >From: Richard Smith <rsmith(a)bitworks.com> > > > > >To: LinuxBIOS <linuxbios(a)clustermatic.org> > > > > >Subject: Re: VGA Problem about 440bx chipset > > > > >Date: Wed, 01 Sep 2004 10:04:52 -0500 > > > > > > > > > >Chiu Gerald wrote: > > > > > > > > > >>you mean that PCI card works? > > > > > > > > > >Yes some PCI cards work. I've made several Assiliant 65550 and > > > > >69000 > > > > >based PCI cards work and some S3 based cards work. There are > > > > >reports of > > > > >some ATI cards working but I am still having problems getting my ATI > > > > >M1 > > > > >based card to work. > > > > > > > > > >>Now I changed to a PCI video card,and bochs had run the vga > > > > >>bios,but still nothing happened! > > > > > > > > > >>I have no idea what should I do next. > > > > > > > > > >Are you setting up the shadowing correctly? You have to setup the > > > > >shadowing in loader.s or bochs and the video bios never make it into > > > > >ram. The stock ADLO setup won't work on the 440bx. > > > > > > > > > >I've attached my loader.s which sets up the shadowing correctly. > > > > > > > > > >Also the DEBUG_SERIAL option in rombios.c is very useful. You can > > > > >enable it and all the bochs bios messages will be redirected out the > > > > >serial port. This way you can see if bochs rombios is even getting > > > > >called. You have to turn it back off to get text on the VGA screen. > > > > >But your cards VSYNC should happen regardless. (assuming the vbios > > > > >runs > > > > >correctly) > > > > > > > > > >I leave in a few hours and won't be back till Tuesday the 2nd so you > > > > >are > > > > >on your own for a few days. I'll try to check email during that > > > > >time > > > > >but I'm not promising anything. > > > > > > > > > >Search the mailing list for things like "ADLO", "vgabios", etc there > > > > >are > > > > >several threads on getting this up. > > > > > > > > _________________________________________________________________ > > > > 与联机的朋友进行交流，请使用 MSN Messenger: > > http://messenger.msn.com/cn > > > > > > > > _______________________________________________ > > > > Linuxbios mailing list > > > > Linuxbios(a)clustermatic.org > > > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > > > > > > > >_______________________________________________ > > >Linuxbios mailing list > > >Linuxbios(a)clustermatic.org > > >http://www.clustermatic.org/mailman/listinfo/linuxbios > > > > _________________________________________________________________ > > 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn > > > >_______________________________________________ >Linuxbios mailing list >Linuxbios(a)clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

2 1

Summarization on using ADLO to bring up VGA
by Gerald Chiu 07 Sep '04

07 Sep '04

>perhaps it would make sense to summarize "lessons learned" and send them >to list, so that whoever will play with ADLO next can benefit from the >knowledge Ok,after Richard Smith's help ,I succeded in booting linux with VGA supported. Mainboard: intel 440bx Video Card: S3 Trio64V+ (PCI card) And Richard said that he made Assiliant 65550 and 69000 PCI cards work and some S3 based cards work on 440bx mainboard. I had tried to use a ATI PCI card,but failed when the program run into VGA Bios ,and never return back.I also having problem on bringing up AGP video card,although I had set some registers about AGP enabling(maybe I hadn't set correctly,anyway, I don't care AGP too much now). Prepare pirq,vga bios(get them from a running os),then use ADLO to copy them to proper address,maybe you need to modify loader.s about setting up shadowing. Attached loader.s which was modified by Richard Smith sets up the shadowing correctly. I used it and succeeded,too.Thanks. ;***************************************************** ; $Id: loader.s,v 1.1 2002/11/25 02:07:53 rminnich Exp $ ;***************************************************** USE32 ; code it is loaded into memory at 0x7C00 ;***************************************************** nop nop ;***************************************************** ; A) setup GDT, so that we do not depend on program ; that loaded us for GDT. ; Ex: LinuxBIOS and EtherBOOT use different GDT's. ;----------------------------------------------------- ; 0) cli ;----------------------------------------------------- ; I) lgdt [0x7C00+protected_gdt] ;----------------------------------------------------- ; II) setup CS jmp 0x08:0x7C00+newpgdt newpgdt: nop ;----------------------------------------------------- ; III) setup all other segments mov ax, #0x10 mov ss, ax mov ds, ax mov es, ax mov fs, ax mov gs, ax ;----------------------------------------------------- ; IV) ; not now ;sti ;***************************************************** nop nop ; Outputs a value to PCI config space ; put the bus,dev,function,offset in eax ; and the byte value in dl then call this macro MACRO PCI_CONFIG_WRITE_BYTE shl edx, #8 mov dl, al and dl, #3 shl edx, #16 or eax, #0x80000000 and eax, #0xfffffffc mov dx, #0x0cf8 out dx, eax shr edx, #16 mov al, dh mov dh, #0 add edx, #0x0cfc out dx, al MEND ;***************************************************** ; B) shadow - ON (enable/read/write) ; This is orginal shadowing setup code ; Works on the Matsonic 7308e mainboard ;mov eax, #0x80000070 ;mov dx, #0x0cf8 ;out dx, eax ;mov eax, #0xFFFFFFFF ;mov dx, #0x0cfc ;out dx, eax ; This enables shadowing for the 0x0f0000 - ; 0x0fffff range and the 0x0C0000 - 0x0cffff range ; for the 440bx chipset. mov eax, #0x59 mov edx, #0x20 PCI_CONFIG_WRITE_BYTE mov eax, #0x5A mov edx, #0x22 PCI_CONFIG_WRITE_BYTE mov eax, #0x5b mov edx, #0x22 PCI_CONFIG_WRITE_BYTE ;***************************************************** nop nop ;***************************************************** ; C) copy -- boch bios ; counter - 64kb. mov ecx, #0x10000 ; source - 0x8000 ( 0x7C00+0x400 = 0x8000 ) mov ax, #0x10 ; src-segment - 2nd entry in GDT mov ds, ax mov eax, #0x8000 ; src-offset - 0x8000 mov esi, eax ; destination - 0xF0000 mov ax, #0x10 ; dst-segment - 2nd entry in GDT mov es, ax mov eax, #0xF0000 ; dst-offset - 0xF0000 mov edi, eax ; clear direction flag cld ; the copy rep movsb ;***************************************************** nop nop ;***************************************************** ; D) copy -- video bios ; on my system video bios is just 48KB (0x0C000) ; but just for paranoida we copy 64kb (0X10000) ; counter - 64kb mov ecx, #0x10000 ; source - 0x18000 ( 0x8000+0x10000 = 0x18000 ) mov ax, #0x10 ; src-segment - 2nd entry in GDT mov ds, ax mov eax, #0x18000 ; src-offset - 0x18000 mov esi, eax ; destination - 0xC0000 mov ax, #0x10 ; dst-segment - 2nd entry in GDT mov es, ax mov eax, #0xC0000 ; dst-offset - 0xC0000 mov edi, eax ; clear direction flag cld ; the copy rep movsb ;***************************************************** nop nop ;***************************************************** ; E) copy -- pirq table ; on my system video bios is just 48KB (0x0C000) ; but just for paranoida we copy 64kb (0X10000) ; counter - 256kb -- 0x100 mov ecx, #0x100 ; source - 0x7F00 ( 0x7C00+0x300 = 0x7F00 ) mov ax, #0x10 ; src-segment - 2nd entry in GDT mov ds, ax mov eax, #0x7F00 ; src-offset - 0x7F00 mov esi, eax ; destination - 0xFFD00 mov ax, #0x10 ; dst-segment - 2nd entry in GDT mov es, ax mov eax, #0xFFD00 ; dst-offset - 0xFD00 mov edi, eax ; clear direction flag cld ; the copy rep movsb ;***************************************************** nop nop ;***************************************************** ; X) copy -- LinuxBIOS table into safe place. ;; TODO. ;; Q1 : what is the size of table. ;; Q2 : where to copy? ;***************************************************** nop nop ;***************************************************** ; E) shadow - OFF (write) mov eax, #0x59 mov edx, #0x30 PCI_CONFIG_WRITE_BYTE mov eax, #0x5A mov edx, #0x33 PCI_CONFIG_WRITE_BYTE mov eax, #0x5b mov edx, #0x33 PCI_CONFIG_WRITE_BYTE ;mov eax, #0x80000070 ;mov dx, #0x0cf8 ;out dx, eax ;mov eax, #0xFFFFFFFF ;mov eax, #0x0000FFFF ;mov dx, #0x0cfc ;out dx, eax ;***************************************************** nop nop ;***************************************************** ; F) do a little prep work. ;----------------------------------------------------- ; I) disable cache ; if you disable cache, GRUB's GFX mode will be VERY slow. ; so DO NOT DISABLE ;mov eax, cr0 ;or eax, #0x60000000 ;wbinvd ;mov cr0, eax ;wbinvd ;----------------------------------------------------- ; II) disable MTRR ; clear the "E" (0x800) and "FE" (0x400) flags in ; IA32_MTRRdefType register (0x2FF) ;----------------------- ;mov ECX,#0x2FF ; select either of the two below ; depending on if your compiler suports ; {RD,WR}MSR or not ;rdmsr ; .byte 0x0F, 0x32 ;xor edx, edx ; xor eax, eax ;and eax, #0xFFFFF3FF ; select either of the two below ; depending on if your compiler suports ; {RD,WR}MSR or not ;wrmsr ; .byte 0x0F, 0x30 ;----------------------- ;; This is what PC BIOS is setting. -- P6STMT. ; add VIDEO BIOS cacheable!!!! ;----------------------- ; Fixed Range C0--C8 ;mov ECX,#0x268 ;mov EDX,#0x05050505 ;mov EAX,#0x05050505 ;wrmsr ;----------------------- ; Fixed Range C8--CF ;mov ECX,#0x269 ;mov EDX,#0x0 ;mov EAX,#0x05050505 ;wrmsr ;----------------------- ;----------------------------------------------------- ; III) tell BOCHS' BIOS we want to boot from hdd. ; 0x00 - floppy ; 0x02 - hdd ; In future there will be 'fd failover'option in bochs. mov al, #0x3d ;; cmos_reg out 0x70, al mov al, #0x02 ;; val (hdd) out 0x71, al ;----------------------------------------------------- ; IV) tell BOCHS' BIOS length of our mem block @ 1mb. ; This is for Int 15 / EAX=E820 ; 119mb = 0x77 00 00 00 ; (this is for 128mb of ram) ; (FIXME: this value is currently hard coded) ; (it should be being passed from LinuxBIOS ) ; for WinFast 6300 ; 07 70 = 0770 ; 06 80 = 0770 - 00F0 << ALT (for unpatched bochs) ; for P6STMT - 10kb less ram ; 077F - 10 = 07 6F ; 07 6F - 00 F0 = 06 7F mov al, #0x35 ;; cmos_reg out 0x70, al mov al, #0x06 ;; val out 0x71, al mov al, #0x34 ;; cmos_reg out 0x70, al mov al, #0x7F ;; val out 0x71, al mov al, #0x31 ;; cmos_reg out 0x70, al mov al, #0x00 ;; val out 0x71, al mov al, #0x30 ;; cmos_reg out 0x70, al mov al, #0x00 ;; val out 0x71, al ;----------------------------------------------------- ; V) tell BOCHS' BIOS we want to have LBA translation. ; 0x00 - NONE ; 0x01 - LBA <<<< ; 0x02 - LARGE ; 0x03 - R-CHS ; In future there will be 'fd failover'option in bochs. mov al, #0x39 ;; cmos_reg out 0x70, al mov al, #0x01 ;; val (LBA) out 0x71, al ;***************************************************** nop nop ;***************************************************** ; G) the switch -- protected to real mode ; IASDM, Vol 3 ; (8-14) 8.8.2 Switching Back to Real-Address Mode ;===================================================== ; 1) disable interrupts cli ;===================================================== nop ;===================================================== ; 2) paging ;not enabled, so not applicable. ;===================================================== ; 3) setup CS segment limit (64kb) ; I) lgdt [0x7C00+new_gdt] ;----------------------------------------------------- ; II) jmp 0x08:0x7C00+new64lim new64lim: nop ;===================================================== nop ;===================================================== ; 4) setup all other segments mov ax, #0x10 mov ss, ax mov ds, ax mov es, ax mov fs, ax mov gs, ax ;===================================================== nop ;===================================================== ; 5) LIDT ; I) ; set up Real Mode IDT table (0...3FF) ; for BOCH's BIOS the address 0xF000:0xFF53 ; cantains value 0xCF which is IRET opcode. ; counter mov cx, #0xFF ;1024 bytes(255 interrupts)(4*255=0x3FF) ; destination - 0x00000 = ES:EDI mov ax, #0x10 ; dst-segment - 2nd entry in GDT mov es, ax mov eax, #0x00000 ; dst-offset - 0x00000 mov edi, eax ; data to store -- 0xF000:FF53 mov eax, #0xF000FF53 ; clear direction flag cld ; the store rep stosd ;----------------------------------------------------- ; II) ; load interrupt descriptor table lidt [0x7C00+new_idt] ;===================================================== nop nop ;===================================================== ; 6) clear the PE flag in CR0 register. ; I) ; switch to 16 bit segments mov ax, #0x20 mov ss, ax mov ds, ax mov es, ax mov fs, ax mov gs, ax ;----------------------------------------------------- ; II) ; switch to 16 bit CS jmp 0x018:0x7C00+new16bit USE16 new16bit: nop ;----------------------------------------------------- ; III) ; the switch ;xor eax, eax mov eax, cr0 and eax, #0xFFFFFFFE mov cr0, eax ;switch to RM ;===================================================== nop nop ;===================================================== ; 7) far jump -- (to real mode address) jmp 0x0:0x7C00+realcs realcs: nop ;===================================================== ; 8) set all segment registers to 0's mov ax, #0x0 mov ss, ax mov ds, ax mov es, ax mov fs, ax mov gs, ax ;===================================================== ; 9) re-enable interrupts sti ;***************************************************** nop nop ;***************************************************** ; G) jump to BIOS. jmp 0xFFFF:0x0000 ;jmp 0xF000:0xFFF0 ;***************************************************** ;***************************************************** nop nop nop nop ;***************************************************** ;***************************************************** USE32 new_idt: dw 0x03ff ;; limit 15:00 dw 0x0000 ;; base 15:00 dw 0x0000 ;; base 23:16 new_gdt: dw 0x0028 ;; limit 15:00 dw 0x7C00+new_gdt_table ;; base 15:00 dw 0x0000 ;; base 23:16 protected_gdt: dw 0x0018 ;; limit 15:00 dw 0x7C00+pmode_gdt_table ;; base 15:00 dw 0x0000 ;; base 23:16 ;----------------------------------------------------- new_gdt_table: ;// 1 2 3 4 ;//0 dd 0x00000000 dd 0x00000000 ;//8 dd 0x0000ffff dd 0x00409E00 ;//10 dd 0x0000ffff dd 0x00409200 ;//18 dd 0x0000ffff dd 0x00009a00 ;//20 dd 0x0000ffff dd 0x00009200 ;------------------------- pmode_gdt_table: ;// 1 2 3 4 ;//0 dd 0x00000000 dd 0x00000000 ;//8 dd 0x0000ffff dd 0x00CF9E00 ;//10 dd 0x0000ffff dd 0x00CF9200 ;***************************************************** ;***************************************************** ; the file size must be 1024 bytes. ; -0x100 b/c we put $PIR table here. .org 0x400-1-0x100 ; dd 0xdeadbeef db 0x0 ;***************************************************** _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

1 0

RE: epia m vga + memcpy failed
by Chiu Gerald 06 Sep '04

06 Sep '04

Before memcpying,you need to shadow on 0xc0000-0xcffff ,please refer to your northbridge datasheet,and set a register on host-pci bridge(device 0) correctly ! >From: Trellix78(a)aol.com >To: linuxbios(a)clustermatic.org >Subject: epia m vga + memcpy failed >Date: Mon, 06 Sep 2004 18:30:27 -0400 > >I was trying to figure why VGA wasn't being properly set on my epia m >when I found that the code in mainboard.c was looking for device id 0x3123 >while my epia m has device id 0x3122 for the CLE266. After changing >the id, memcpy is failing to copy the bios code. Anyone know why that >could be? Here's a piece of the log: >. >. >. >setting ethernet >Assigning IRQ 11 to 0:12.0 > Readback = 11 >setting vga >Assigning IRQ 11 to 1:0.0 > Readback = 11 >setting pci slot >setting vt8235 slot >Assigning IRQ 5 to 0:11.1 > Readback = 5 >Assigning IRQ 12 to 0:11.5 > Readback = 12 >INSTALL REAL-MODE IDT >DO THE VGA BIOS >found VGA: vid=1106, did=3122 >Setting up VGA, VGABIOS_START: 0xfffe0000 >First 16 bytes of VGA_ROM: 0x55 0xaa 0x7d 0xe9 0x26 0x7f 0x5e 0x1b 0xfa 0xf9 0xf4 0x82 0x0 0x0 0x0 0x0 >Failed to copy VGA BIOS to 0xc0000 >First 16 bytes of 0xc0000: 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff >setting VGA up anyway >bus/devfn = 0x100 >biosint: # 0x6, eax 0x100 ebx 0x100 ecx 0x100 edx 0x12 >biosint: ebp 0x11a2c esp 0xff6 edi 0xda8c esi 0x12350 >biosint: ip 0x3 cs 0xc000 flags 0x46 >biosint: Oops, exception 6 >Stack contents: 0x0003 0xc000 0x0046 0x4d75 0x0000 >biosint: Bailing out >Checking IRQ routing tables... >. >. >. >_______________________________________________ >Linuxbios mailing list >Linuxbios(a)clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

1 0

Re: usbboot in EPIA-5000
by elife elife 06 Sep '04

06 Sep '04

Hi Steven, Thanks for your help. Another question: Where can I find Yinghai Lu's eb+filo+usbboot patch? I found a post of him in the lb archive(http://www.mail-archive.com/linuxbios@clustermatic.org/msg07219.htm… but the link he gave is the diff against a patched eb tree. Best Regards! _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot