Doesn't Not Compute

My log of experiences with GNU/Linux and computers in general.

Uvesafb, and Possibly PCI, Problem with Linux kernel 2.6.34-ARCH

As part of a project to make my netbook what it’s designed to be — a device for internet browsing only, instead a laptop — I’ve dd’d the latest Arch Linux ISO to a flashdrive and wiped out Ubuntu Lucid.

The post-installation process went normally — set vga=791 so I have a 1024×768 screen, configure my wireless network connection (WPA necessitates some typing 😛 ), update the package lists, upgrade pacman, then upgrade the whole system.

But when I tried to follow the procedure for getting the full 1366×768 resolution, I discovered upon reboot that, even though I remembered  remove the “vga=xxx” kernel parameter — preventing the VESA framebuffer from overriding the new, “fancier” UVESAFB, I got a message reporting “uvesafb could not reserve memory at” something-or-other.

Not knowing what could be wrong, I started reading the kernel’s dmesg log (/var/log/dmesg.log)  and noticed this message:

pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000c0000-0x000dffff] conflicts with reserved [mem 0x000d00000-0x000ffff]

A few lines above, I saw

PCI: Using host bridge windows from ACPI; if necessary, use “pci=nocrs” and report a bug.

I wasn’t sure if the two had anything to do with each other, but I rebooted, edited the kernel line in GRUB and added the “pci=nocrs” parameter, and continued booting. Everything worked perfectly.

There is an open bug about this problem in the Arch Linux system.


3 responses to “Uvesafb, and Possibly PCI, Problem with Linux kernel 2.6.34-ARCH

  1. Luca July 17, 2010 at 4:14 pm

    I absolutely love this comment on the bug report “Poulsbo is the worst chipset ever.” 😀 It strikes me as odd that these dodgy chipsets are still being used. Clearly it is because the big players (Nvidia, ATI, Intel, etc) don’t provide a good value chipset, I’m surprised they haven’t yet filled this gap in the market.

  2. Luca July 17, 2010 at 4:15 pm

    Oh… that is an Intel chipset. 😛

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: