[SOLVED] startx command make my screen blank (VESA Driver)
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone, i have a problem when building (B)LFS 7.5 stable
My OS host is Ubuntu 12.04, my VGA driver in Ubuntu is : Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter (rev 10)
i issue all command in Chapter 24 and no error, just when i go to "startx", blank screen appear
the VGA have no issue in my host OS, but when i confiure the driver "sis" in xorg, an error come to the screen said my Screen not found, so i use VESA instead sis.
when use VESA, blank screen come to my build when i issue "startx", i just can use Ctrl+Alt+BckSpc to go back to my terminal
[ 17.974] (EE) open /dev/dri/card0: No such file or directory
That's it, my friend. You have no working video driver - vesa won't go near it. There may be an "xf86-video-SiS" or something like it package for X. you need that one badly.
That's it, my friend. You have no working video driver - vesa won't go near it. There may be an "xf86-video-SiS" or something like it package for X. you need that one badly.
thanks for your reply friend, i follow the tutorial in here, i downloaded all driver and compile it, from ATI to VMWare, so Sis is include too, IMHO maybe i must compile the driver in kernel ?
Quote:
Originally Posted by ReaperX7
I used the 6.4.2 section from the FreeBSD handbook to setup my X.
Um... depends on your kernel. I use a slightly modified Slackware-Huge kernel for my own system. Works well enough for my needs. However, unless you have the correct framebuffers, drm modules, etc. built for the kernel correctly it might not work.
Um... depends on your kernel. I use a slightly modified Slackware-Huge kernel for my own system. Works well enough for my needs. However, unless you have the correct framebuffers, drm modules, etc. built for the kernel correctly it might not work.
thanks again for the reply friend, can i ask you a question ?
how to know i have a "correct" framebuffer, drm modules, etc ?
anw, i have read the FreeBSD tutorial, and i think i was issue sudo X -configure in my (B)LFS, i have the driver "VESA" and i copy the /root/xorg.conf.new to /etc/xorg.conf, when i issue "startx", guess what, blank screen appear again T.T
when blank screen appear again, i press Ctrl+Alt+F1, and i see "tmw:warning:font for xxxxx is lacking", after that i issue : ctrl+c, and i see "argv:1:bad display name in remove command" or something like that T.T
any suggestion friend ?
Last edited by Th3_DarkSky; 09-10-2014 at 11:45 PM.
There were 16 video modes that are pretty universal and used for vga in Dos, for example, and starting X on fallback and so forth. The SiS 6326 didn't have them, and so nothing worked without the SiS driver.
You can install the SiS driver, or check that it is installed, and uninstall vesa and every other video driver if you want to get going. That will clear the landscape. The kernel offers the following config options
Code:
bash-4.2$ grep SIS /usr/src/linux-3.14.5/.config
# CONFIG_SATA_SIS is not set
# CONFIG_PATA_SIS is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_AGP_SIS is not set
# CONFIG_DRM_SIS is not set
# CONFIG_FB_SIS is not set
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_PERSISTENT_KEYRINGS is not set
bash-4.2$
You only need sis_agp if you have an agp socket; you definitely need sis_drm; and may find a use for sis_fb; compile in your chipset also.
If you are running a distro kernel, the config is usually stored as /boot/config-version or suchlike.
There were 16 video modes that are pretty universal and used for vga in Dos, for example, and starting X on fallback and so forth. The SiS 6326 didn't have them, and so nothing worked without the SiS driver.
You can install the SiS driver, or check that it is installed, and uninstall vesa and every other video driver if you want to get going. That will clear the landscape. The kernel offers the following config options
Code:
bash-4.2$ grep SIS /usr/src/linux-3.14.5/.config
# CONFIG_SATA_SIS is not set
# CONFIG_PATA_SIS is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_AGP_SIS is not set
# CONFIG_DRM_SIS is not set
# CONFIG_FB_SIS is not set
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_PERSISTENT_KEYRINGS is not set
bash-4.2$
You only need sis_agp if you have an agp socket; you definitely need sis_drm; and may find a use for sis_fb; compile in your chipset also.
If you are running a distro kernel, the config is usually stored as /boot/config-version or suchlike.
thanks for your comment friend, FYI, my machine is a local brand laptop (axioo), in kernel detected as CLEVO, i'm using vanilla kernel ( 3.13.3 ) like the LFS book said, for the sis driver, i must compile them (sis_agp, sis_drm, sis_fb and my chipset too) in kernel (in another word re-cmpiling the kernel) or when in BLFS ?
sorry for my stupid question about compiling driver, i'm new in kernel world T.T
The subject of this thread is :Black screen on X. X in LFS or X in your base system (whatever that is)?
If you are in a chroot, I wish you luck starting X because you will need it. That makes it difficult.
If you are not booting LFS, and complaining about LFS explain please where X does not start. Otherwise check your kernel options in LFS. Try the check I did.
One of the reasons I use a Slackware-Huge kernel config is because it covers everything I need, and think I'll need.
I do run make oldconfig against it enabling, disabling, and modularizing as given, and then recheck it with make menuconfig to double check what is and isn't enabled.
The only problem you may run across afterwards is OpenGL support. Mesa removed a lot of older hardware DRI1 support features back in the 7.x series including various SiS chipsets.
The subject of this thread is :Black screen on X. X in LFS or X in your base system (whatever that is)?
If you are in a chroot, I wish you luck starting X because you will need it. That makes it difficult.
If you are not booting LFS, and complaining about LFS explain please where X does not start. Otherwise check your kernel options in LFS. Try the check I did.
Black screen on X in my (B)LFS, in Ubuntu everything was fine
Quote:
Originally Posted by ReaperX7
One of the reasons I use a Slackware-Huge kernel config is because it covers everything I need, and think I'll need.
I do run make oldconfig against it enabling, disabling, and modularizing as given, and then recheck it with make menuconfig to double check what is and isn't enabled.
The only problem you may run across afterwards is OpenGL support. Mesa removed a lot of older hardware DRI1 support features back in the 7.x series including various SiS chipsets.
But sir, in Ubuntu everything was fine
Last edited by Th3_DarkSky; 09-14-2014 at 04:01 AM.
Thanks for all your attention everyone, the problem was FOUND and FIXED
the problem is not in my driver nor in my Xorg setting, the problem is in the Xorg font
when installing the Xorg font, i'm using BLFS 7.5 stable tutorial, in the tutoial for installing font, the book said like this :
Code:
for package in $(grep -v '^#' ../font-7.7.md5 | awk '{print $2}')
do
packagedir=${package%.tar.bz2}
tar -xf $package
pushd $packagedir
./configure $XORG_CONFIG
make
as_root make install
popd
rm -rf $packagedir
done
when i issue the command, the subshell is exit, the problem is in the 10th line "rm -rf $packagedir", if we use the command as non-root user, it may exit with error, so we must add "as_root" in the 10th line, so the code must be like this :
Code:
for package in $(grep -v '^#' ../font-7.7.md5 | awk '{print $2}')
do
packagedir=${package%.tar.bz2}
tar -xf $package
pushd $packagedir
./configure $XORG_CONFIG
make
as_root make install
popd
as_root rm -rf $packagedir
done
when i do that and rebuild the font + issue : "startx", everything is FINE, LIKE A CHARM ( twm, xterm and xclock are appear in my screen ) Thanks GOD
once again, thanks for all your attention FRIENDS, my problem was SOLVED, may the odds be ever in your favor
source : (B)LFS 7.5 errata
*P.S : for Moderator, please delete this thread, i make mistake so i make double-thread
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.