Date: Mon, 29 Apr 2002 21:26:23 -0500 From: Larry Rosenman <ler@airmail.net> To: Eric Anholt <eanholt@gladstone.uoregon.edu> Cc: Joe Marcus Clarke <marcus@marcuscom.com>, John Utz <john@utzweb.net>, freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: New Laptop: i810: HELP Message-ID: <20020430022623.GB1483@lerlaptop.lerctr.org> In-Reply-To: <1020127967.466.8.camel@anholt.dyndns.org> References: <20020429164649.GA176@lerlaptop.iadfw.net> <Pine.LNX.4.44.0204291158040.6387-100000@jupiter.linuxengine.net> <20020429170538.GA196@lerlaptop.iadfw.net> <1020106827.22787.16.camel@gyros.marcuscom.com> <1020108438.39799.10.camel@ler-freebie.iadfw.net> <1020127967.466.8.camel@anholt.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Eric Anholt <eanholt@gladstone.uoregon.edu> [020429 19:54]: > On Mon, 2002-04-29 at 13:27, Larry Rosenman wrote: > > Well with that patch, we still get the same thing, but I suspect Eric > > did more than I did with the chips. > > > > Eric, > > I have the I830MG chipset in this laptop, and am willing to > > experiment and get it working on -STABLE. > > > > I currently get a X86 Illegal opcode right after the Gamma Correction > > message in the logs (same as before applying your agp_i810.[ch] patch. > > > > This is on a Fujitsu Lifebook C6651. > > Okay, I poked around in this, and I have to say that where it's going > wrong is totally out of my area of knowledge. As far as I can tell, > it's dying because the bios memory seems to be corrupted, or at least > it's more than the emulator can handle according to Stuart Barkley. > This is strange because Linux users have had it working. > > Just to make see if this is an interaction with AGP (since the agp code > has not been successfully used yet that I know of), could you try > removing AGP from your kernel or not modloading it at boot and see how X > works? It looks like X should handle not having AGP loaded, since you > have 8MB stolen for the card already. If it does work, you'll be > limited in resolution, but not as badly as those who only have 512k or > 1MB stolen. Playing with it, I can get a 320x200 X up in VGA mode, if I don't allow int10 to run. As soon as we bring int10 in, we get the checksum (I suspect we have a mapping issue somewhere). Is there anything I can run to map the BIOS ROMS on the machine? What can I do to help? I'd LOVE to get it running, but I suspect the BIOS mapping into the system is the issue, and I don't know what the maps are. LER > -- Larry Rosenman, Sr. Network Engineer, Internet America, Inc. E-Mail: ler@airmail.net Phone: +1 214-861-2571, Fax: 214-861-2663 US Mail: 350 N. St. Paul, Suite 3000, Dallas, TX 75201 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020430022623.GB1483>