The same error message appears when trying to boot the Live i686 image into Mac Mini (Intel).

I can confirm this happens when booting the live i686 image onto my Toshiba Satellite Pro L20.

It then stops booting.

I get the same error message when i tried booting my notebook SONY VAIO VGN-FJ270 from a live USB. This is when I used the Fedora 12 i686 as the live image, before I have fedora 10 i686 and was booting the machine without any issues form the live usb. I have another distro in the notebook . is it because of that .

the booting stops after i get this error message. This error message is followed by another message whih is 

Boot has failed, sleeping forever

Same problem on Samsung NC10 netbook with Lenovo external USB DVD drive.

Works if i boot from a USB stick that is created from the same media using livecd-iso-to-disk.

Same here,

kernel version 2.6.31.6-145.fc12.i686.PAE
ATI Technologies Inc M56P [Radeon Mobility X1600]

Got same problem with fc12 i686 on USB -- prior to that the system was hanging after a few sucesful boots from the USB key.

Using Compaq laptop 6910p w a HP 4gb USB key for LIVE boot image.

I don't have that issue on my HP 6710s, but my friend has on his Toshiba A300-1MM with Intel 4500M Graphics (non-HDMI version).

I would bet it's Intel specific, and that comment #5 is a different bug.

@  Vedran Miletić: Should I start a new bug report then?

I notice that my machine doesn't stop booting, so it might as well be a different bug...

Complete lines with errors are (I have two screens attached):
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id

I can confirm the same issue on my Fujitsu Tablet T4215, Intel Core 2 Duo, i686 version of fedora 12 with KDE off the main website, loaded using unetbootin to a flash drive.

My machine is x86_64, I am retrying now with the x86_64 version, and I have the same error.

I have the same error, my machine is HP6510b, kernel is 2.6.31.6-127.fc12.x86_64.
OS is installed in USD disk.

I've experienced the same error ([drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own) and the machine stop booting with (Boot has failed, sleeping forever)
The notebook is Toshiba Portege R500. I am trying to boot KDE Live x86_64 CD image.
lspci -v | grep VGA:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Laptop model: Asus K40IJ
Running fully updated F12 native on /dev/sda1 with the other OS on a extended partition.

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
$ uname -r
2.6.31.6-166.fc12.i686.PAE

dmesg snippet
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

consistent with above comments. X still boots per normal with no noticeable issues.

I have an Asus eeepc 901 and it stops on booting, but only with the eeepc modified kernel from fedora-eee.com . The same message appears using dmesg, but nothing noticeable happens. It only happens to me with F12, so I will downgrade myself back to F11 again :)

I used F12 a few days later (The KDE live-cd) and it managed to work.. I've been working for a few days now, the bug still appears in dmesg, but it's not causing any noticeable issues.

Can you boot the system in text mode?

When Fedora shows grub init screen you can press the "a" key and add the "3" number at the end of the kernel boot options. Then you can boot in text mode (init 3).

I have the same error ([drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own) in a Toshiba Laptop NB100 and the system hangs during boot.
But if I boot the system in text mode, it loads OK. Then I write "startx" from console and I have gnome working. I have a different mouse cursor but everything seems to work.
The same error when I try to boot from Live Image into a USB disk created in Windows. I can boot perfectly from this image if I create it from a linux box (with live-cd-iso-to-disk).

Same problem with Intel 4500 graphics here. I don't know whether it is related but I use kdm and first time I try login into the system, it bounces back to the kdm login, the second try works. In /var/log/messages I see then:

Dec 15 23:40:28 localhost kernel: [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
Dec 15 23:40:36 localhost kdm: :0[1423]: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0
Dec 15 23:40:36 localhost kdm: :0[1423]: Client start failed
Dec 15 23:40:36 localhost kdm: :0[1423]: Cannot close ConsoleKit session: Unable to close session: no session open

I am experiencing the same issue with Intel GMA 950 video and Intel 945GC north bridge (MSI Wind pc). I experienced this with a regular install of Fedora 12 i686 along with a new install fully patched. I was also able to replicate this in Ubuntu Karmic Koala, so I do not believe it is limited to Fedora.

I can confirm I have the same problem trying to install Fedora 12 (KDE, XFCE etc) via USB created by Unetbootin. I am trying to install it on both a Dell Inspiron 2200 and an Acer Aspire One (A0A-150).



The error I get is:

[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

Boot has failed, sleeping forever




However, Fedora 11 works just fine with no issues at all. Argh!

I have the problem in fC 12 when my kernel was updated from 

2.6.31.5-127.fc12.i686.PAE 

to 

2.6.31.6-166.fc12.i686.PAE

I cannot boot with the new kernel I have to keep selecting the old kernel from grub.  The error I get is 

[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

Boot has failed, sleeping forever

Those of you who cannot boot, edit the boot command line and remove rhgb and quiet from the options and see if the fb message is truly the last error.  For me, it appears to cause no problems at all, am I'm suspicious that something else is causing the boot failures.

If you remove rhgb from kernel options, the system has no errors at boot time.
If you boot the system in text mode, it boots perfectly without errors.

There is something related to graphics module or screen boot that is interfering with a clean/standard boot.

*** Bug 547288 has been marked as a duplicate of this bug. ***

I had installed FC12 on 5th-dec. It worked fine till 21st and then suddenly it stopped responding after a reboot.
the error is the same as above..

[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own.

Booting has failed, sleeping forever.

after reading the posts here I tried rebooting in text mode (init level 3) but no luck. I got the following error message..

No root device found.

Boot has failed, sleeping forever.

I also tried some of the live cds (BackTrack 3) to get into the partitions and save my data (this the least I could do). But this also didn't work. The partitions is not responding to any of the other distros and fedora 12 dvd rescue mode itself.

although I am not a expert to advice something on this. but the way I look into the problem I would guess that the file table that exist inside the kernal is not accessible. because of which none of the other distro's are getting inside that partition including fedora 12 rescue mode.

I have tried to mount the linux file system in rescue mood of FC12, as it was not recognising the linux partition automatically.

after few attempts and looking at the dmesg | tail I realize that my FS is EXT4 instead of EXT3 which I had given while installing.

I did a successful manual install with the given arguments and saved my data.

on the next boot I realised that FC12 rescue mode recognised the linux partition and mounted it automatically.

now my system is booting/working with no problem at all.

Please move boot/root fs issues to another bug - this bug is for the drm message.

sorry for the misunderstanding Orion.

I have quoted the problem in comment #23.

I wrote comment #24 to inform about the solution I got to the drm problem occurred on my notebook.

although its not exactly the solution.

TWO USB DRIVES - TWO RESULTS

If using a USB SanDisk cruzer colours+ 4GB ERROR
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

Boot has failed, sleeping forever


If using USB LEXAR 33110-16GBA-1609 16GB - NO FAULT BOOT SUCCESS..

Both built using the same machine and image.

Repeatable using multiple desktops - DELL, NEC, IBM

On eee-901 have error in dmesg
---
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
---

System boot and work OK.

[root@eee901 ~]# uname -r
2.6.31.9-174.fc12.i686


[root@eee901 ~]# cat /boot/grub/grub.conf
---
...
default=0
timeout=3
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
# hiddenmenu
title Fedora (2.6.31.9-174.fc12.i686)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.31.9-174.fc12.i686 ro root=UUID=935bd116-c78e-455b-9f09-f68cc862fdea rhgb quiet LANG=ru_RU.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_plytheme=charge elevator=noop
        initrd /boot/initramfs-2.6.31.9-174.fc12.i686.img


[root@eee901 ~]# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
04:00.0 Ethernet controller: Attansic Technology Corp. Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)

just a note, I experienced this bug when creating a live usb drive with several spins of Fedora 12. 

What solved the issue for me was unmounting the flash drive before rebooting or removing the drive for use with a different machine.

(In reply to comment #19)
> I have the problem in fC 12 when my kernel was updated from 
> 
> 2.6.31.5-127.fc12.i686.PAE 
> 
> to 
> 
> 2.6.31.6-166.fc12.i686.PAE
> 
> I cannot boot with the new kernel I have to keep selecting the old kernel from
> grub.  The error I get is 
> 
> [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
> 
> Boot has failed, sleeping forever  

Sorry about the wrong information.  Actually I had not set up raid on root(/) properly.  The new kernel tried to load the raid device but failed thereby throwing up this error.  It started working when I fixed the RAID issue.

I have made an update last night that installs kernel-2.6.31.9-174 and another packages.
Now I can boot the system with rhgb kernel option activated and drm error has disappeared. I have booted the system with an older kernel and with rhgb option and the error has been removed.
So I keep on believing that the error is caused by something that loads with the graphic system, not the kernel because I could boot the system in text mode without problems. I could execute gnome from level 3 or I could write "init 5" without problems.
Unfortunately, the update installed 240 different packages and I don't know wich of them resolved the issue. If there is someone interested in the yum log, I can attach it in this bug.

Still present for me with latest updates-testing including 2.6.31.9-174.fc12.x86_64.

After removing the quiet I found that the error was misleading.  The error of trying to remove the fb was not related to the boot error.  My error was an unrecognized USB device after initial boot.  Once I changed to another device my system was able to boot fine, but still had the same frame buffer error.

I am not sure how many of these are specifically related to the FB error, or just the last error seen in the "graphical" boot mode.

Tanks to Orion at comment #20 for that suggestion.

I can see it here too, as well as the RH-bug 547599:

[fsw@hubble ~]$ dmesg |grep ERROR
[drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-D
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

but everything is working fine: bootsplash, correct screen size & refresh rate (1366x768@60Hz), playing YouTube videos or DVD, TV through ADSL and even with 3D effects enabled (by the way, one of the painless installation ever, no hand configuration 'till now...)!

And I've never had the boot problem that some have described before...

The box is a Fujitsu-Siemens Amilo Li 3710 laptop, with almost everything Intel inside, apart from LAN & WLAN from Realtek.
	
[fsw@hubble ~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

[fsw@hubble ~]$ lsusb
Bus 002 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[fsw@hubble ~]$ uname -r
2.6.31.9-174.fc12.x86_64

[fsw@hubble ~]$ dmesg |head
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.31.9-174.fc12.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.4.2 20091027 (Red Hat 4.4.2-7) (GCC) ) #1 SMP Mon Dec 21 05:33:33 UTC 2009
Command line: ro root=UUID=058f0935-56b9-4868-a181-217067b91ada noiswmd LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=fr rhgb quiet

So, it looks with my box more a cosmetic than a real issue, but I might be wrong...

Just to be exact, I've read too fast, I've also only a small part of the RH-bug 547599 (the i2c error message), not the whole problem, as it is far more annoying than that...

And I forgot to mention that I've installed Fedora 12 from the x86_64 Gnome Live-CD, if it's perhaps useful to know...

Same problem when I boot fedora 12 from a  USB stick created by UltraISO.
I've solved it.
This because fedora Live CD use CDLABEL to define root,but when we boot from USB, it change.
Edit "/syslinux/syslinux.cfg" and change the command: 
"append initrd=initrd0.img root=live:CDLABEL=Fedora-12-i686-Live" into
"append initrd=initrd0.img root=live:UUID=4471-9093" for USB HDD,
or change to
"append initrd=initrd0.img root=live:UUID=B4FE-5315" for USB ZIP.

As said in Comment 21 if I boot without the rhgb kernel parameter,
the fb error message disappears, so it really looks like being related to graphical boot:

[fsw@hubble ~]$ dmesg |grep ERROR
[drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-D

[fsw@hubble ~]$ dmesg |grep fb
fb0: inteldrmfb frame buffer device

[fsw@hubble ~]$ uname -r
2.6.31.12-174.2.3.fc12.x86_64

But the i2c error is still there...

Making it boot in Init mode 3 brings some weird errors, im using the x64_86 live CD. I get the same error as above, but before that i have: 

"according to mtab, /dev/mapper/live-rw is already mounted on /sysroot"

May, many times, then comes the error message and the system is sleeping forever, then i get some I/O errors on device sr0, logical blocks and sectors ranging between 8620-8630.

Hope this helps

I forgot to mention that im running a Fujitsu Siemens V6535, with the following processor:

*-cpu
          product: Intel(R) Pentium(R) Dual  CPU  T3400  @ 2.16GHz
          vendor: Intel Corp.
          physical id: 1
          bus info: cpu@0
          size: 1GHz
          capacity: 1GHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm cpufreq

And for the people who have mentioned it could be a graphics issue, im running the following:

*-display:0
             description: VGA compatible controller
             product: Mobile 4 Series Chipset Integrated Graphics Controller
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 07
             width: 64 bits
             clock: 33MHz
             capabilities: bus_master cap_list rom
             configuration: driver=i915 latency=0
             resources: irq:30 memory:f2400000-f27fffff memory:d0000000-dfffffff(prefetchable) ioport:1800(size=8)

Still happens with kernel-2.6.32.8-48.rc2.fc12.x86_64 on a ThinkPad T60 with i945GM

Also it happens once for each attached display, so with a dual display setup I get it twice.

[ykaul@ykaul ~]$ dmesg |grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] set up 31M of stolen space
fbcon: inteldrmfb (fb0) is primary device
fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
[drm:i915_gem_madvise_ioctl] *ERROR* Attempted i915_gem_madvise_ioctl() on a pinned object

[ykaul@ykaul ~]$ uname -r
2.6.32.9-67.fc12.x86_64

Lenovo T500,

Also happens with Fedora 13 Alpha, Radeon 9000 (RV250), KMS, rhgb,
kernel-2.6.33-1.fc13.i686

[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own

The problem doesn't seem to happen with 2.6.32-19.el6 on the RHEL6 almost beta. On a Lenovo X301

Also the Fedora 11 live CD also doesn't have the problem

This also happens to me (Fedora 13 Alpha) with 2.6.33.1-19.fc13.x86_64

I conform this bug on fedora 12 live CD installation.

Yep same here, no can do...can't boot this thing, next time test on some different machines before release how hard is that. Maybe is UNetbootin problem, it adds some more option for boot then Fedora it self after creating, boot from ISO works in Vbox but not from USB key. Maybe is this EFI problem i don't know that you use it, i have MSI G31 board.

*** Bug 533156 has been marked as a duplicate of this bug. ***

It's fixed on Fedora 13!

(In reply to comment #36)
> Same problem when I boot fedora 12 from a  USB stick created by UltraISO.
> I've solved it.
> This because fedora Live CD use CDLABEL to define root,but when we boot from
> USB, it change.
> Edit "/syslinux/syslinux.cfg" and change the command: 
> "append initrd=initrd0.img root=live:CDLABEL=Fedora-12-i686-Live" into
> "append initrd=initrd0.img root=live:UUID=4471-9093" for USB HDD,
> or change to
> "append initrd=initrd0.img root=live:UUID=B4FE-5315" for USB ZIP.    

(In reply to comment #36)
My Fedora12 live on USB stick would hang during booting because of wrong UUID value in "/syslinux/syslinux.cfg". 
To get correct UUID do:
sudo /lib/udev/vol_id --uuid /dev/sdc1 # Use your USB stick device name

After syslinux.cfg edit it boots fine but I still have problem with persistent changes. All changes are gone after a reboot.

Fedora 13 solved it all here also!
Now it looks great (again):

[fsw@hubble ~]$ uname -r
2.6.33.5-112.fc13.x86_64

[fsw@hubble ~]$ dmesg |grep ERROR

[fsw@hubble ~]$ dmesg |grep i2c

[fsw@hubble ~]$ dmesg |grep fb
fbcon: inteldrmfb (fb0) is primary device
fb0: inteldrmfb frame buffer device

[fsw@hubble ~]$ dmesg |grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] set up 127M of stolen space
fbcon: inteldrmfb (fb0) is primary device
fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

But I can't say if there was ever some similar troubles with USB in my case, as I only booted Fedora 12 & 13 on Live-CD than installed both on HDD...

I think this can be closed as solved in current release based on various confirmations.

I have this same error.

Fedora 12
Kernel: 2.6.32.16-141.fc12.i686)

lspci -v | grep VGA:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 01) (prog-if 00 [VGA controller])

Message in boot:
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id