> b8? Anybody know what that one is?
The vgabios itself has a bug in it. The b8 is an invalid INT # and
what has happened is the vgabios code itself has crashed and is executing
randomly. On the EPIA-M I had seen this problem on certain units where if
the motherboard got too hot (but not really th
On Mon, 17 May 2004, Stefan Reinauer wrote:
> There's a potential hint in src/arch/i386/lib/idt.c:biosint():
>
> // cases in a good compiler are just as good as your own tables.
> switch (intnumber) {
> case 0 ... 15:
> [..]
> #ifdef CONFIG_PCIBIOS
>
On 17 May 2004, Mathieu Deschamps wrote:
> INSTALL REAL-MODE IDT
> DO THE VGA BIOS
> found VGA: vid=1106, did=3122
> write_protect_vgabios
> 0x55 0xaa 0x70 0xe9 0xfc 0x7f 0x8b 0x1b 0x34 0xde 0xca 0x83 0x0 0x0 0x0
> 0x0 bus/
that means it is ok.
___
Li
Not yet.
Status:
1. UHCI support: bulk transfer not working.
2. OHCI support: need add code to support ED and TD this week.
Regards
YH
-邮件原件-
发件人: Jay Miller [mailto:[EMAIL PROTECTED]
发送时间: 2004年5月17日 8:36
收件人: YhLu
抄送: [EMAIL PROTECTED]; [EMAIL PROTECTED]
主题: Re: USB boot
Has the cod
Let me know if your testbed is ready, and I would send my last usb dir tar
ball to you.
Regards
YH
-邮件原件-
发件人: Steven James [mailto:[EMAIL PROTECTED]
发送时间: 2004年5月17日 6:14
收件人: YhLu
抄送: Linuxbios; Takeshi Sone
主题: Re: USB boot
Greetings,
Sorry about the delay in replying.
The length
* Stefan Reinauer <[EMAIL PROTECTED]> [040517 17:51]:
> There needs to be some way to call into interrupts set up by the
> executed option rom, or otherwise functions like handleint21() will have
> to be added and changed for every minor release of a vga bios update.
There's a potential hint in sr
* Ignacio Verona <[EMAIL PROTECTED]> [040516 22:07]:
> biosint: # 0x15, eax 0x5f01 ebx 0xc01 ecx 0x700 edx 0x112
> biosint: ebp 0x10fca esp 0xf8e edi 0xac51 esi 0x1aacd
> biosint: ip 0x6448 cs 0xc000 flags 0x46
> biosint: # 0xb8, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0
> biosint: ebp 0x10fca esp 0xfc0
Has the code for USB support been committed, and if so, where?
Thanks,
Jay Miller
Actuality Systems, Inc.
[EMAIL PROTECTED]
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
* Nathanael Noblet <[EMAIL PROTECTED]> [040517 17:18]:
> >>biosint: Unsupport int #0xb8
> >
> >b8? Anybody know what that one is?
>
> It has something to do with VGA, I had similar problems (have been back
> to them so they are most likely still there). The Unsupported int
> number would change
On Sunday, May 16, 2004, at 07:08 PM, ron minnich wrote:
On Sun, 16 May 2004, Ignacio Verona wrote:
biosint: # 0xb8, eax 0x707 ebx 0x0 ecx 0x700 edx 0x0
biosint: ebp 0x10fca esp 0xfc0 edi 0xb880 esi 0x1010a
biosint: ip 0x188 cs 0xc000 flags 0x246
biosint: Unsupport int #0xb8
b8? Anybody know what t
Hi,
I don't know if it could help, i've gathered every used options in
V2. It helped me because of V1 to V2 port : some options aren't used
any more (e.g. side solutions incorporated in LB becoming "standards"
needn't a activated option to be taken into consideration in build)
while some other op
* Jay Miller <[EMAIL PROTECTED]> [040517 15:21]:
> 1) I've read on the mailing list archives that we need to use
> mkElfImage-1.6 from the freebios tree in order for things to work
> properly. When I checked-out the freebios tree I only got sources for
> mkElfImage, the mkElfImage-1.6 directory wa
Two more newbie problems:
1) I've read on the mailing list archives that we need to use
mkElfImage-1.6 from the freebios tree in order for things to work
properly. When I checked-out the freebios tree I only got sources for
mkElfImage, the mkElfImage-1.6 directory was empty. Is this normal?
2)
Greetings,
Sorry about the delay in replying.
The length field is encoded as n-1 with 0x7ff a special value meaning 0.
IIRC, a USB protocol error would cause a stall condition. A 0 transfer
when data is expected is a SCSI level error.
As you can see, the USB code doesn't have nearly enough erro
Ok, tonight I'll send you a ready-to-burn image, and please, if you burn
it with bios savior, try to write your experience. I've had a lot of
problems using it, and finally, i'm using two flash I get from a local
distributor (for free :D), but biosSavior is not working.
> Sounds interessting, I wa
Ingo: I've been working on linuxbios for 2 weeks or so (Delayed by
BiosSavior not working properly :( ) and what I have now is (as I've said
in subject, Epia mII-1 but I think almost everything should work on
epia-m as well):
LinuxBios booting, from hw detection to linux login on serial consol
well you can try to V2 but you'll see that VGA bios isn't as far
"worked" as it is in v1.
I'am not as far as you've gone, because you have this i don't:
INSTALL REAL-MODE IDT
DO THE VGA BIOS
found VGA: vid=1106, did=3122
write_protect_vgabios
0x55 0xaa 0x70 0xe9 0xfc 0x7f 0x8b 0x1b 0x34 0xde 0xca
Ron:
Thanks for your answ. Reading the serial output can you say something
about the PCMCIA problem?
And what about tft? May be cause VGA no to work? Right now I do not have
any CRTs here...
Mathieu:
Yes, I'm on v1 right now. And about the combined filo+vgabios payload this
is what I do for creati
18 matches
Mail list logo
