Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 144556 - RTx86 RTamd64 - X doesn't start: missing /dev/fb0
Summary: RTx86 RTamd64 - X doesn't start: missing /dev/fb0
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: LiveCD/DVD/USB (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-20 14:20 UTC by Simon Stelling (RETIRED)
Modified: 2006-09-01 16:11 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 Simon Stelling (RETIRED) gentoo-dev 2006-08-20 14:20:07 UTC
LiveCD md5sum: 48c4536699d325524321c0ee6736b78a

So I did complete a dynamic stage3 installation with a livecd-kernel (networkless installation) and rebooted. X didn't want to start:
 # startx
xauth:  creating new authority file /root/.serverauth.13419

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-gentoo-r7 x86_64
Current Operating System: Linux localhost 2.6.17-gentoo-r5 #1 SMP Tue Aug 15 23:47:35 UTC 2006 x86_64
Build Date: 06 August 2006
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 20 06:29:13 2006
(==) Using config file: "/etc/X11/xorg.conf"

dlopen: /usr/lib64/xorg/modules/extensions/libGLcore.so: undefined symbol: __glXLastContext
(EE) Failed to load /usr/lib64/xorg/modules/extensions/libGLcore.so
(EE) Failed to load module "GLcore" (loader failed, 7)
(EE) open /dev/fb0: No such file or directory
(EE) No devices detected.

Fatal server error:
no screens found
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

 # ls /dev/fb0
ls: /dev/fb0: No such file or directory

 # ls -F /dev
agpgart@    kmem     psaux@  ram9@    tty    tty24  tty40  tty57    vcs12
bus/        kmsg     ptmx    random   tty0   tty25  tty41  tty58    vcs2
cdrom@      log=     pts/    rd/      tty1   tty26  tty42  tty59    vcs3
cdrom1@     loop/    ram0@   rtc@     tty10  tty27  tty43  tty6     vcs4
cdrw@       loop0@   ram1@   sda      tty11  tty28  tty44  tty60    vcs5
console     loop1@   ram10@  sda1     tty12  tty29  tty45  tty61    vcs6
core@       loop2@   ram11@  sda2     tty13  tty3   tty46  tty62    vcs7
dac960_gam  loop3@   ram12@  sda3     tty14  tty30  tty47  tty63    vcsa
disk/       loop4@   ram13@  sda5     tty15  tty31  tty48  tty7     vcsa1
dvd@        loop5@   ram14@  sda6     tty16  tty32  tty49  tty8     vcsa12
fd@         loop6@   ram15@  sg0      tty17  tty33  tty5   tty9     vcsa2
full        loop7@   ram2@   shm/     tty18  tty34  tty50  ttyS0    vcsa3
gpmctl=     mapper/  ram3@   snd/     tty19  tty35  tty51  ttyS1    vcsa4
hda         mcelog   ram4@   stderr@  tty2   tty36  tty52  ttyS2    vcsa5
hdb         mem      ram5@   stdin@   tty20  tty37  tty53  ttyS3    vcsa6
hpet        misc/    ram6@   stdout@  tty21  tty38  tty54  urandom  vcsa7
initctl|    null     ram7@   synth    tty22  tty39  tty55  vcs      zero
input/      port     ram8@   tts/     tty23  tty4   tty56  vcs1
Comment 1 Simon Stelling (RETIRED) gentoo-dev 2006-08-20 14:22:09 UTC
manually executing 'udevstart' didn't fix the problem
Comment 2 Andrew Gaffney (RETIRED) gentoo-dev 2006-08-20 15:33:58 UTC
Try editing the kernel commandline in grub to include 'vga=791' (or whatever mode you want). I believe /dev/fb0 isn't getting created since there's no vga= option being passed.
Comment 3 Simon Stelling (RETIRED) gentoo-dev 2006-08-21 02:08:49 UTC
Indeed, adding 'vga=791' fixed the problem.
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2006-08-21 13:45:47 UTC
OK.  It looks like the proper "fix" for this is to use a different patch on amd64/x86 than on, say, sparc.  Basically, because the "nv" driver sucks so badly, we're replacing it w/ fbdev.  This works on the LiveCD because we're using the framebuffer.  This would also be a problem if using "gentoo-nofb" on amd64/x86.  On all other architectures, they set a framebuffer no matter what, so it isn't an issue.  I had only tested it on "gentoo" and never thought about "gentoo-nofb" so I didn't catch it.

Kugelfang/agaffney:  You can change this in your fsscript to fix the issue.

sed -i 's/DRIVER fbdev/DRIVER vesa/' /usr/share/hwdata/Cards

I'll change hwdata-gentoo itself, so we don't have the same issue next release.
Comment 5 Andrew Gaffney (RETIRED) gentoo-dev 2006-08-21 13:58:53 UTC
It's in my fsscript for the next build.
Comment 6 Danny van Dyk (RETIRED) gentoo-dev 2006-08-22 07:51:49 UTC
In my releng data.
Comment 7 Chris Gianelloni (RETIRED) gentoo-dev 2006-09-01 16:11:11 UTC
I'm going to assume that this was FIXED, since I didn't hear otherwise.  Also, I updated hwdata-gentoo, so future releases will be using VESA on x86/amd64, and fbdev on everything else.