Fabio A. Correa wrote: > > The bottom line is that a BIOS error is likely the problem with > > BAR allocation on your machine. Have you checked to see if an > > updated one is available? > > Hey, I found an updated BIOS available in the HP site, obviously > requiring Windows. I had deleted those partitions, so I will get a > Windows hard disk/CD and try to flash it. You may be able to use flashrom as developed by the coreboot project to flash your BIOS. Maybe. If not, come on IRC or the mailing list and we can try to help you get it to work on your laptop. http://coreboot.org/Flashrom http://coreboot.org/IRC http://coreboot.org/Mailinglist > By the way, what is BAR? The boot firmware (usually BIOS) assigns PCI devices an address range through which software can exchange data with the device. Each device specifies the size for it's address ranges, the firmware calculates how all ranges fit together, and then writes the start, or base, address to the respective BAR in each device. The addresses are the same as RAM addresses, which is why 32-bit systems can not use full 4GB of RAM. The PCI device address ranges will occupy the last part of memory space. Better BAR allocation algorithms could allow more usable RAM, but it also depends on chipset limitations. //Peter -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
