[coreboot] [PATCH] Abit BE6-II V2.0 support (repost)

Uwe Hermann uwe at hermann-uwe.de
Sun Jan 27 22:04:53 CET 2008


On Tue, Jan 22, 2008 at 12:49:18AM +0300, Sergei Antonov wrote:
> 0. filo-0.5 can't find hda HDD: 'No drive detected on IDE channel 0'.
> That is, I believe, because of bug in filo-0.5. The patch is attached
> which fixes the problem for me. I've already posted it, and it got
> some critique. Please reconsider it. If it may cause problems, explain
> them to me.

Please repost the patch in a new thread with a longer explanation of
what it does and why. I think it was overlooked in this (unrelated) thread.


> 1. PS/2 keyboard doesn't work. (USB keyboard does.) I'll try to
> investigate it myself.

Yep, known problem on several 440BX boards. It's likely superio or
southbridge (Intel 82371EB) related.


> 2. flashrom outputs: 'No EEPROM/flash device found'. It is probably
> because of a locked flash device. People on IRC gave me some tips, so
> I'll try to investigate it myself.

Please post the 'flashrom -V' output from the latest version of flashrom.
There can be several reasons why this doesn't work - unknown chipset,
unknown chip, broken code, missing board-specific chip hackery, etc.


> 3. I have a PCI card which is a host controller for IEEE 1394 and USB.
> When I boot with the standard BIOS, USB devices attached to it work.
> When I boot with coreboot, and plug in a USB device, it doesn't work
> and these messages appear:
> 	usb 1-4: new high speed USB device using ehci_hcd and address 3
> 	usb 1-4: device descriptor read/64, error -110
> 	usb 1-4: device descriptor read/64, error -110
> 	usb 1-4: new high speed USB device using ehci_hcd and address 4
> 	usb 1-4: device descriptor read/64, error -110
> 	usb 1-4: device descriptor read/64, error -110
> 	usb 1-4: new high speed USB device using ehci_hcd and address 5
> 	usb 1-4: device not accepting address 5, error -110
> 	usb 1-4: new high speed USB device using ehci_hcd and address 6
> 	usb 1-4: device not accepting address 6, error -110
> Googling on it suggests that it is a PCI IRQ-related problem.

Yep, likely, maybe your IRQ table is incorrect, that can happen. Try
booting with the 'irqpoll' Linux kernel option and see if it helps.

Also, please post your full boot log (coreboot + Linux) which you gather
on the serial port.

 
> 4. coreboot works with 'NVIDIA GeForce2 MX 400' video card (64 MB),
> but hangs with older 'NVIDIA Riva TNT' (16 MB). With the latter
> nothing is displayed and the computer hangs after 'entering emulator'.
> With the standard BIOS both cards work. Here are pieces of logs
> related to VGA:
> 
> NVIDIA GeForce2 MX 400 (64 MB):
> 	rom address for PCI: 01:00.0 = f9000000
> 	PCI Expansion ROM, signature 0xaa55, INIT size 0xcc00, data ptr 0x00f4
> 	PCI ROM Image, Vendor 10de, Device 0110,
> 	PCI ROM Image,  Class Code 030000, Code Type 00
> 	copying VGA ROM Image from 0xf9000000 to 0xc0000, 0xcc00 bytes
> 	entering emulator
> 
> NVIDIA Riva TNT (16 MB):
> 	rom address for PCI: 01:00.0 = f1000000
> 	PCI Expansion ROM, signature 0xaa55, INIT size 0x8000, data ptr 0x7623
> 	PCI ROM Image, Vendor 10de, Device 0020,
> 	PCI ROM Image,  Class Code 030000, Code Type 00
> 	copying VGA ROM Image from 0xf1000000 to 0xc0000, 0x8000 bytes
> 	entering emulator

Are both cards PCI, or AGP, or PCI-E? The VGA emulator is known to have
some problems with a bunch of graphics adapters, maybe you have one of
the non-working ones. Not sure how this can be fixed.


Uwe.
-- 
http://www.hermann-uwe.de  | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org




More information about the coreboot mailing list