[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#398964: marked as done (linux-image-2.6.17-2-686: i810 fb module conflicts with X)

Your message dated Mon, 27 Jul 2009 01:32:33 +0200
with message-id <20090726233233.GA12974@galadriel.inutil.org>
and subject line Re: linux-image-2.6.17-2-686: i810 fb module conflicts with X
has caused the Debian Bug report #398964,
regarding linux-image-2.6.17-2-686: i810 fb module conflicts with X
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
398964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398964
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Severity: important


When I load i810 fb module (which by itself works fine with my adapter), X (also a i810 
server) won't load and I get a message about X being unable to access the hardware. However, 
when I load vesafb (which I don't want to), both work fine. X also works fine when no fb.

I'm not quitw sure if it's a kernel or X bug, but I report it as a kernel bug based on the 
fact that X works fine, except when i810fb module loaded.

Arny


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=hr_HR, LC_CTYPE=hr_HR (charmap=ISO-8859-2)

Versions of packages linux-image-2.6.17-2-686 depends on:
ii  initramfs-tools [linux-initra 0.85a      tools for generating an initramfs
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo

Versions of packages linux-image-2.6.17-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
  linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:

--- End Message ---
--- Begin Message --- 
On Thu, Dec 04, 2008 at 11:16:30PM +0100, Moritz Muehlenhoff wrote:
> On Thu, Nov 16, 2006 at 08:57:05PM +0100, Arni Kromic wrote:
> > Package: linux-image-2.6.17-2-686
> > Version: 2.6.17-9
> > Severity: important
> > 
> > 
> > When I load i810 fb module (which by itself works fine with my adapter), X (also a i810 
> > server) won't load and I get a message about X being unable to access the hardware. However, 
> > when I load vesafb (which I don't want to), both work fine. X also works fine when no fb.
> > 
> > I'm not quitw sure if it's a kernel or X bug, but I report it as a kernel bug based on the 
> > fact that X works fine, except when i810fb module loaded.
> 
> Does this error still occur with more recent kernel and X.org versions?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: