LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   "Display is not set" ; boots to login, then frozen grey/white screen w. globes (https://www.linuxquestions.org/questions/slackware-14/display-is-not-set-%3B-boots-to-login-then-frozen-grey-white-screen-w-globes-805327/)

wiliamvw 05-01-2010 11:07 AM

"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.

Didier Spaier 05-01-2010 03:13 PM

Did you try to start at runlevel 3 (the default in Slackware) and then, type "startx" ?

Anyway it is possible that you have a display problem.

Please sent output of "lspci -k | grep -A3 VGA" so we can help you to choose the good X module for your graphical card.

Meanwhile it is usually safe, though not fancy, to choose a vesa module, using a minimum xorg.conf file for that.

If you want to try, just type as root "cp /etc/X11/xorg.conf-vesa /etc/X11/xorg.conf" then go back to regular user and type "startx".

wiliamvw 05-03-2010 05:57 PM

xterm data
 
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

Didier Spaier 05-04-2010 12:30 AM

Your output shows that your card is actually recognized as a radeon one.

Could you get X working with a vesa driver ?

If not, after having typed startx, please send the output of following commands, typed as root:
Code:

grep EE /var/log/Xorg.0.log
tail --lines 20 /var/log/Xorg.0.log


wiliamvw 05-05-2010 02:39 PM

xterm output
 
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

Didier Spaier 05-05-2010 03:37 PM

Hello Bill,

The fbdev X module is not shipped with Slackware, that explain the error message.

But I am surprised that it be requested.

If you have an /etc/X11/xorg.conf file, first check that the command (as root) "grep fbdev /etc/X11/xorg.conf" return nothing, as it should.

In that case set up an /etc/X11/xorg.conf file with only these lines:
Code:

Section "Device"
  Identifier "n"
  Driver "radeon"
EndSection

If that doesn't work, try replacing "radeon" with "vesa".

Check that the error "Failed to load module "fbdev" (module does not exist, 0)" disappear from /var/log/Xorg.0.log

And please let us know the outcome.

I can explain you how to install the fbdev driver but hopefully you won't need it.

wiliamvw 05-10-2010 05:30 PM

completed all suggestions -- no change
 
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.


All times are GMT -5. The time now is 05:55 AM.