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

Bug#290925: marked as done (kernel-source-2.6.10: Blank Screen When Using intelfb Module)

Your message dated Wed, 12 Apr 2006 23:16:41 -0700 (PDT)
with message-id <Pine.LNX.4.63.0604122315590.15409@bobcat>
and subject line Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb Module
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kernel-source-2.6.10
Version: 2.6.10-3
Severity: normal


When the intelfb module is compiled into the kernel all consoles remain
blank until the X server starts up. Using it as a module is not an
option for non-CRT screens (see
http://www.xfree86.org/~dawes/intelfb.html, which I'm assuming not to be
outdated on this issue). This makes the driver unusable for laptops.

The initialization seems to be OK (from dmesg):

Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 830M Chipset.
agpgart: Maximum main memory to use for agp memory: 202M
agpgart: Detected 892K stolen memory.
agpgart: AGP aperture is 128M @ 0xe8000000
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G
chipsets
intelfb: Version 0.9.2
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 9 (level, low) -> IRQ 9
intelfb: 00:02.0: Intel(R) 830M, aperture size 128MB, stolen memory
892kB
intelfb: Non-CRT device is enabled ( DVO port B ).  Disabling mode
switching.
intelfb: Initial video mode is 640x480-16@60.

I was unable to try vesa modes with a higher resolution than vga=0x311
as my BIOS doesn't support these values.

This problem is similar to bug #289810, but I doubt that is directly
related as vesafb doesn't figure into this particular configuration.

Thanks for looking into this.
   Georg

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-gw1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-source-2.6.10 depends on:
ii  binutils                      2.15-5     The GNU assembler, linker and bina
ii  bzip2                         1.0.2-1    A high-quality block-sorting file 
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  fileutils                     5.2.1-2    The GNU file management utilities 

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Thu, 13 Apr 2006, Georg Wittenburg wrote:


Hi Juri,


As mentioned in the bug report, the problems you were experiencing most
likely resulted from Debian-specific modular framebuffer patches. These
patches have been dropped from Debian kernels long ago, and the kernel
you've originally reported the problem against is long gone too. Thus
there are reasons to believe that this bug is fixed in current kernels, so
I plan to close this bug report in two weeks from today (April 26th,
2006), unless you're still experiencing problems. If that's still the
case, please post updated information to the bug.


Please, feel free to close the bug. I'm running 2.6.15 now, which works like a
charm, and don't even own the hardware in question anymore.


Excellent, closing the bug.

Thanks,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

--- End Message ---
Reply to: