When exactly do those 0x0s get sent? Before ram initialization starts? Before the initial banner is sent? Before the payload is executed? "before booting" can mean a lot of things ;)

-Corey

On Thu, Nov 6, 2008 at 10:46 PM, Elia Yehuda <z4ziggy@gmail.com> wrote:

found the problem - its my buggy vga.rom!!! it's missing the damn device_id!

ive patched it, and now the screen turns on upon boot, but no messages. however....
once i "modprobe i810fb" from the serial console, look and be-hold - we've got onboard-vga working!

many thanks, now if we can figure out why it wont display upon bootup it will be great.

also, another thing which troubles me - BEFORE booting begins, there are 0x00 sent to the serial for about 2 minutes (i've counted about 80 o those 0x00 being sent) and only then the coreboot messages starts to appear and the boot continues. i would appreciate eliminating this 2 minutes delay... any relevant information would be appreciated.

Regards,
Elia.

On Fri, Nov 7, 2008 at 5:37 AM, Corey Osgood <corey.osgood@gmail.com> wrote:

On Thu, Nov 6, 2008 at 10:27 PM, Elia Yehuda <z4ziggy@gmail.com> wrote:

thanks for the suggestion - ive added
#define PCI_DEVICE_ID_INTEL_82810E_IG   0x7125

to src/include/device/pci_ids.h but still no luck :

rom address for PCI: 00:01.0 = fffc0000

PCI Expansion ROM, signature 0xaa55, INIT size 0xa000, data ptr 0x0110
PCI ROM Image, Vendor 8086, Device 0000,

Device or Vendor ID mismatch Vendor 8086, Device 0000 (Expected Vendor 8086, Device 7125)

im guessing the device_id needs to be declated somewhere in the code or maybe in the Config.lb?

Huh? Where is the device ID of 0000 coming from? It's been a while since I've been in that part of v2, but it looks like it's coming from the rom itself. If that's the case, can you hack pci_rom.c to ignore the device ID and run the rom anyway?

-Corey
 

Regards,
Elia.

On Fri, Nov 7, 2008 at 5:06 AM, Joseph Smith <joe@settoplinux.org> wrote:

On Fri, 7 Nov 2008 04:55:41 +0200, "Elia Yehuda" <z4ziggy@gmail.com> wrote:
> yep, ive extraced my vga using awardeco which should be fine (and it does
> seems fine on the lspci -n, which is very frustrating)
>
> On Fri, Nov 7, 2008 at 4:48 AM, Joseph Smith <joe@settoplinux.org> wrote:
>
>>
>>
>>
>> On Fri, 7 Nov 2008 04:24:38 +0200, "Elia Yehuda" <z4ziggy@gmail.com>
>> wrote:
>> > tnx Joseph,
>> >
>> > i've fixed the following (to match my 256kb bios) :
>> >
>> >   device pci_domain 0 on
>> >
>> >       device pci 0.0 on end            # Host bridge
>> >         chip drivers/pci/onboard
>> >           device pci 1.0 on end            # Onboard video
>> >           register "rom_address" = "0xfffc0000"
>> >       end
>> >   ...
>> >   end
>> >
>> > and now the rom_address is set AND i see the device in lspci :
>> > lspci:
>> > 00:01.0 VGA compatible controller: Intel Corporation 82810E DC-133
> (CGC)
>> > Chipset Graphics Controller (rev 03)
>> > lspci -n:
>> > 00:01.0 0300: 8086:7125 (rev 03)
>> >
>> > but still no vga-output!
>> > i found the following to might suggest another problem :
>> >
>> > PCI Expansion ROM, signature 0xaa55, INIT size 0xa000, data ptr 0x0110
>> > PCI ROM Image, Vendor 8086, Device 0000,
>> > Device or Vendor ID mismatch Vendor 8086, Device 0000
>> >
>> > and no "copying VGA ROM Image"...
>> Yep that is your problem. Is there something wrong with your vga bios.
> It
>> is reading the vendor id ok but the device id should be 7125.
>> Have you checked this out? It may help you to get a valid vga bios.
>> http://www.coreboot.org/VGA_support
>>

coreboot uses a different pci.ids file than Linux. That's why Linux can
find it but coreboot can't? Check and see if the coreboot pci.ids file
includes 8086 / 7125. It may be missing and just needs to be added?

--

Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org

--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot