| View previous topic :: View next topic |
| Author |
Message |
toofastforyahuh
Apprentice
Joined: 18 May 2004
Posts: 172
|
 Posted: Fri Jun 18, 2004 9:00 am Post subject: 2.6.7 : Lost the Console/blank screen |
 |
|
I just tried compiling kernel.org's 2.6.7 kernel for my amd64 system and discovered I can't get a visible text console.
I can startx fine. The system appears to work fine. I just can't see anything on the screen until startx (thank goodness for tab completion). I also don't have a display after I exit X. The monitor still has sync; it's just the screen is blank.
The system runs fine on 2.6.6 with the Radeon (R100), but I've tried 2.6.7 3 different ways:
1. plain jane text console
2. vesa console (using vga=792 mode)
3. radeonfb
And all produce the same result.
Has anyone else got a fix for this?
Relevant info from system log, from boot and after calling startx. Please ignore the radeonfb warning because the problem happens even without the radeonfb module compiled. I had overlapping MTRRs before (VESA FB sets the MTRR first, then X complains it can't reset the same MTRR, but this happened in 2.6.6, too.).
This is an amd64 with the VIA chipset and the R100 Radeon using open source drivers.
| Code: |
Bootdata ok (command line is root=/dev/hde3 vga=792)
Linux version 2.6.7 (root@kitsune) (gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)) #1 Fri Jun 18 00:07:50 PDT 2004
Kernel command line: root=/dev/hde3 vga=792 console=tty0
agpgart: Detected AGP bridge 0
agpgart: Maximum main memory to use for agp memory: 1919M
agpgart: AGP aperture is 256M @ 0xe0000000
PCI-DMA: Disabling IOMMU.
vesafb: framebuffer at 0xd0000000, mapped to 0xffffff000008f000, size 4608k
vesafb: mode is 1024x768x24, linelength=3072, pages=13
vesafb: scrolling: redraw
vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0
fb0: VESA VGA frame buffer device
radeonfb: cannot reserve FB region
mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x400000
devfsd[419]: error calling: "unlink" in "GLOBAL"
[drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc Radeon R100 QD [Radeon 7200]
devfsd[419]: error calling: "unlink" in "GLOBAL"
mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x400000
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
|
dmesg said these snippets:
| Code: |
CPU 0: aperture @ e0000000 size 256 MB
Console: colour dummy device 80x25
PCI: Using ACPI for IRQ routing
agpgart: Detected AGP bridge 0
agpgart: Maximum main memory to use for agp memory: 1919M
agpgart: AGP aperture is 256M @ 0xe0000000
PCI-DMA: Disabling IOMMU.
vesafb: framebuffer at 0xd0000000, mapped to 0xffffff000008f000, size 4608k
vesafb: mode is 1024x768x24, linelength=3072, pages=13
vesafb: scrolling: redraw
vesafb: directcolor: size=0:8:8:8, shift=0:16:8:0
fb0: VESA VGA frame buffer device
|
And trust me, the .config file is very similar to my 2.6.6 .config file, with only token differences for other very unrelated modules. This was from attempt #2 (without radeonfb module):
| Code: |
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE is not set
|
Help is appreciated! |
|
| Back to top |
|
 |
primero.gentoo
Guru
Joined: 23 Dec 2003
Posts: 402
|
| Posted: Fri Jun 18, 2004 9:54 am Post subject: |
|
|
Have you configured all Console related options in "Character Device" section of kernel configuration?
If your X works fine, but you don't have Console i think the problem is not Video-Related but Console configuration related.
Check it out
Bye
_________________
"Linux, the choice of a GNU generation"
==Micro$oft - just say NO==
(L#USER 353039) |
|
| Back to top |
|
|
toofastforyahuh
Apprentice
Joined: 18 May 2004
Posts: 172
|
| Posted: Sat Jun 19, 2004 10:25 am Post subject: Yes, was missing options |
|
|
You're right I was missing options. They weren't in character devices. It's just that the console and framebuffer hierarchies seem different now in menuconfig, relative to 2.6.6, and things weren't set sanely by default.
I was missing a few major settings like the CONFIG_FRAMEBUFFER_CONSOLE and the logo.  I didn't have (or need) these before, but I know alot of framebuffer changes were made in 2.6.7.
Thanks! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
