Re: Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb Module
Horms wrote: On Mon, Jan 17, 2005 at 08:30:24PM +0100, Georg Wittenburg wrote: 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. hlh has already mentioned that we need to walk away from the modular fb code, for reasuns such as this. I am not sure what unplesant side effects that is going to have in relation to mkinitrd and the debian installer. But perhaps 2.6.10 would be a good place to start the rollback. Does this mean all fb drivers would need to be built in? Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb Module
On Tue, Jan 18, 2005 at 06:43:50PM +0100, Thiemo Seufer wrote: Horms wrote: On Mon, Jan 17, 2005 at 08:30:24PM +0100, Georg Wittenburg wrote: 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. hlh has already mentioned that we need to walk away from the modular fb code, for reasuns such as this. I am not sure what unplesant side effects that is going to have in relation to mkinitrd and the debian installer. But perhaps 2.6.10 would be a good place to start the rollback. Does this mean all fb drivers would need to be built in? I spoke to dilinger about this on IRC, and my intepretation of hch's (not hlh, he is a different guy) remarks seem to have been a bit off. I now think that he was only talking about vesafb. Which along with intelfb would make two drivers. What may well be a good solution, which was kind of what I was thinking of, and what dilinger also thought might work, is to put loading the fb drivers into initrd. That may help a lot of problems. But as for vesafb, there seems to be a consensus that it needs to be non-modular. And the same seems to be true of intelfb, so they seem destined to be built into the kernel. I guess the real trick is finding which ones need to be in the kernel, and which can live as modules. Hopefuly there aren't to many of the former. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb Module
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 @ 0xe800 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 :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 [EMAIL PROTECTED] 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-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
