Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 61901 - Boot stops or black screen, using gentoo-dev-sources-2.6.8-r3 or 2.6.7-r11
Summary: Boot stops or black screen, using gentoo-dev-sources-2.6.8-r3 or 2.6.7-r11
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-27 02:14 UTC by Alexander Schmid
Modified: 2004-09-05 16:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Schmid 2004-08-27 02:14:55 UTC
When using gentoo-dev-sources-2.6.7-r11 or gentoo-dev-sources-2.6.8-r3, the screen freezes, but the computer boots in the background, or the whole screen is black, but the computer boots in the background. I can log in and can enter init 6 or so,  but I cannot see anything...

I think there's a problem with Framebuffer.

Reproducible: Always
Steps to Reproduce:
1. Compiling the kernel
2. Rebooting
3. Black screen
4. Trying something with vga= in Grub
5. Booting.
Actual Results:  
After trying something with vga=x in Grub, there's a black screen or a freezing
screen again.

Expected Results:  
Boot clearly, display all kerrnel-booting logs.

I think it is a problem with vga or Framebuffer.

emerge info:
Portage 2.0.50-r10 (default-x86-2004.2, gcc-3.3.3, glibc-2.3.3.20040420-r1,
2.6.4-gentoo)
=================================================================
System uname: 2.6.4-gentoo i686 Intel(R) Pentium(R) 4 CPU 2.53GHz //
gentoo-dev-sources-2.6.8-r3 when using it.
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=pentium4 -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-mcpu=pentium4 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/
ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/
http://ftp.uni-erlangen.de/pub/mirrors/gentoo
ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo
http://ftp6.uni-erlangen.de/pub/mirrors/gentoo
ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo
ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo
ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo
ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo
ftp://ftp6.uni-muenster.de/pub/linux/distributions/gentoo
ftp://ftp.ipv6.uni-muenster.de/pub/linux/distributions/gentoo
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/
http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp://ftp.gentoo.mesh-solutions.com/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb cdr crypt cups encode foomaticdb gdbm gif gpm
gtk gtk2 imlib jpeg libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis
opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl
svga tcpd truetype x86 xml2 xmms xv zlib"
Comment 1 Alexander Schmid 2004-08-28 02:08:52 UTC
Ok, i finally got it working.

I played with ACPI and APM (but that was not the reason.)

If you have the same problem, try this:

Change from vesa-tng to vesa.

There may be no other devices in the Graphic Options than vesa.

Graphic Options - Console line ..... - Disable  Framebuffer Fonts. Enable anything else in Console Line.....

Good luck!
Comment 2 Daniel Drake (RETIRED) gentoo-dev 2004-08-28 08:35:07 UTC
Are you aware that in order to use vesafb-tng, you need to use a different style of vga= argument?
Comment 3 Michal Januszewski (RETIRED) gentoo-dev 2004-09-01 03:53:24 UTC
vga= does not work with vesafb-tng, you need a normal video= option, as with any other fb driver (eg. video=vesafb:1024x768-32@85).
Comment 4 Daniel Drake (RETIRED) gentoo-dev 2004-09-05 16:37:57 UTC
You should be able to use framebuffer + vesafb-tng if you use the correct kernel argument (video rather than vga). Closing.