"Display is not set" ; boots to login, then frozen grey/white screen w. globes
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
"Display is not set" ; boots to login, then frozen grey/white screen w. globes
First attempt at Slack (13 & on laptop & with full install using official cd).
1st install no good, but did second to fix some possible mistakes.
Booted to login prompt and then, after login, nothing until entered telinit 4, then scrambled screen, then changed to probably the normal screen background of grey/white with numerous white globes, but nothing else and cursor moved, but wouldn't function on occasions also got box with login name, password locations.
Got message of "Display not set" and that the problem was so complex it couldn't be explained with these minimal resources.
Did third full install and changed screen option from my known resolution with framebuffer, to safe standard, but no improvement.
Lilo was installed to MBR, and had 2 partitions flagged as bootable (/ and /boot).
Found nothing on forums or FAQ, but suppose could give change of kernel a shot, but as used what cd started with, that seems unlikely.
No idea what to try next; suggestions appreciated.
Thank you Didier for your suggestions. Yes, I went with all the defaults from the start, and did try startx.
My output from "lspci -k | grep -A3 VGA" was:
01:00.0 VGA compatible controller: ATI Technologies Inc. Radeon RV250 [Mobility FireGL] (rev 02)
Subsystem: Twinhead International Corp. Device 0311
Kernel modules: radeonfb
02:01.0 Network controller: Intel Corporation PRO/wireless 2200BG [Calexico] Network Connection (rev 05)
Appreciatively, Bil VERCH
Dear Didier, the output from: grep EE /var/log/Xorg.0.log is:
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "fbdev" (module does not exist, 0)
the output from: tail --lines 20 /var/log/Xorg.0.log is:
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT TRanslated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Option "xkb_options" "terminate:ctrl_alt_bksp"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event6"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Option "xkb_options" "terminate:ctrl_alt_bksp"
Thanks again for taking the time to deal with this problem.
Bil VERCH
Hello Didier, Finally completed all suggestions, but no change.
Tried the vesa module (after created a regular user for the startx), but no change.
No longer get "(EE) Failed to load module "fbdev" (module does not exist, 0)" when enter "grep EE /var/log/Xorg.0.log"
Used vi to change part of the /etc/X11/xorg.conf file (it now refers to vesa) as follows (as it specified that there are over 400 lines in this file, I assume you didn't mean to delete the whole thing):
Section "Device"
Identifier "VESA Framebuffer" changed to Identifier "n"
Driver "vesa" changed to Driver "radeon"
#VideoRam 4096
#Install Clocks lines here if appropriate
EndSection
Nothing made any improvement.
Open to try more suggestions, but possibly a new install may help if choose different screen resolution, or problem may be connected to fact that I use a touchscreen (but really doesn't seem likely).
Reguarding install, encountered strange refusal to make a /var partition; got line-after-line repeating that couldn't find /etc/fstab/var or possibly it was /var/etc/fstab, so ended-up having to create the partition as /usr/var. Still can't figure that one out.
Thanks again for your time and efforts, and any new suggestions appreciated.
Well I tried new install, and this time got to (just once, wouldn't come up again) blue screen with at first the start of normal icons in middle, etc., but quickly changed to fuzzy bottom panel, upper left of 2 white poles attached to white shield with red inverted v in it, and at top center to far right a narrow rectangle saying "Nepomuk Data Storage" "Rebuilding Nepomuk full text search index for new features. This will only..." and then runs off screen. And while cursor moved, it wouldn't click on anything.
Also got message when used xrandr that "can't open display"; also got repeated message on boot up that "File System NOT clean".
So tried new install with all slow check on all partitions, but when got to SELECT for software, it kept looping back to HELP, but finally got that, but after selected simple full install, it then immediately started a reboot which led nowhere -- except message of "kernel panic -- No INIT found" with suggestion try "init= options", but worthless as blinking cursor wouldn't accept any input.
THAT WAS THE BEST I GOT. From there everafter, nothing but boot attempt with "kernel panic" and REFUSED TO ACCEPT INSTALL DISC EVER AGAIN. EVEN AFTER SHUT OFF EVERYTHING AND TRIED AFRESH.
Seems the install disc itself has somehow deteriorated with each new install attempt, and now won't even come up (some residual input from earlier attempts creating a blockage???).
Obviously am at the end of all I can do as now even the install disc won't function (keep it with own protective see-through cover between usages). This appears to be the end of my hopes to get to use Slackware, unless there is something I'm overlooking.
Last edited by wiliamvw; 06-11-2010 at 03:20 PM.
Reason: update
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.