LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 12.0 default vesa xorg.conf - blank screen (https://www.linuxquestions.org/questions/slackware-14/slackware-12-0-default-vesa-xorg-conf-blank-screen-566861/)

Z038 07-08-2007 08:41 AM

When I installed Slackware 11.0 last year on my Thinkpad T43, I chose the wrong keyboard layout during install. Consequently I couldn't Ctrl+Alt+Backspace to get out of the x black screen because the key mappings were wrong. Choosing a different keyboard map that matched my T43 more closely got around that. It saved me from having to cold boot every time I got the black screen, at least.

So you might also ensure you have the right keyboard map selected during install. That won't fix your x problem, but it makes it less painful to debug it since you'll be able to exit back to the cli without having to boot.

send 07-08-2007 04:15 PM

Thanks for all the help everyone.


Road_map: I tried the settings you suggested. Still no go. :confused:

send 07-10-2007 11:12 AM

What do I have to do to try and debug this problem. Where should I be looking for errors? Thanks.

bioe007 07-10-2007 02:32 PM

also I don't know what the kernel level driver for the trident card is but I only see ali_agp, is there another one? you could try modprobing these to see if there is an issue with the kernel inserting the modules.

you can also try using (as root) xorgsetup as opposed to xorgconfig?

send 07-10-2007 05:57 PM

bioe007: I've tried using xorgsetup (as root). It also freezes up. As far as the modprobing, what should the command look like? 'modprobe ali_agp' or 'modprobe trident'? Thanks for all your help btw.

bioe007 07-11-2007 09:00 AM

it seems ali_agp is already loaded, but for example with X running on my lappy;

Code:

radeon                110752  2
drm                    73748  3 radeon
...
intel_agp              23068  1
...
agpgart                31792  2 drm,intel_agp

so you see there should be at least (AFAIK) two modules for your card. one for the agp (already loaded - ali_agp) and usually there is a another than uses drm. I'm not sure what that one is. I tried looking in my own .config but it eluded me.

for my setup it is the i845 chipset and ATI radeon card, so for AGP the intel_agp, then for drm the radeon module.

send 07-11-2007 10:52 AM

Hmm, is there a way I can explicitly log the relevent events or areas I need to be logging? For example, those were the modules loaded when you were already in X, my problem is that it doesn't even make it that far. I 'startx', the screen goes blank like it's initializing, and then freezes. I check the logs and there are no errors. So I essentially need to log lsmod output right after I 'startx' no? If so, what is a good way to approach this? Thanks.

bioe007 07-11-2007 01:04 PM

there are some options in man Xorg you can try:

Code:

Xorg -verbose 3 -probeonly &
then you can check module insertion from dmesg | tail -<number>

where <number> is some number of lines up to let you see whats what..

hth

johnpo 07-12-2007 07:47 AM

Quote:

Originally Posted by send
Hello all, I've just installed Slackware 12.0 on my Toshiba 1805-s273. (Full install) I've been having problems with X as my xorg.conf settings (used in previous slackware versions) don't seem to work anymore. I've read a similar post to this and tried the solutions outlined within, but to no avail. What's confusing is that the Xorg log shows no errors. So I decided to try the vesa xorg.conf that is the default. I'm still getting blank screens. I don't even know where to start to try to troubleshoot this. So just to summarize, I'm using the default xorg.conf (VESA) that comes with Slack, no errors in the Xorg logs, and I'm getting blank screens (I have to cold shutdown to get back up). Where's the next place to look?... Thanks in advance for any help anyone could provide.

Oh, and one more thing (for what it's worth) i tried that mode 0666 for dri uncommented and commented with the same results.

Thanks again everyone.
I had the exact same problem. startx would just blank the screen and nothing would work. Not even Ctrl-Alt-F* to get to the command prompt. Had to do a cold boot every time. I've had previous versions of slackware as well as other distros on this machine and they ran fine so I did not suspect a hardware issue.

After reading the posts here I got the output of lspci -v to get the details for my graphics card, ran xorgconfig (or xorgsetup, i dont remeber which) from the command line and then everything ran fine.

send, i hope you got yours working now.

thanks to all for the help.
john

Anonymo 07-12-2007 06:50 PM

I had this problem before installing the nvidia driver. I would logout of xfce and it would just be a black screen. Slackware 12

send 07-14-2007 01:27 AM

bioe007: I tried the 'Xorg -verbose 3 -probeonly &' command and X still freezes. I am at a complete loss as to what exactly is going on. I'm still up for suggestions. I really want to get this working, so I'll keep trying.

Thanks for all the help everyone.

hlima 07-18-2007 12:17 PM

Same problem with 1805-S203
 
I'm dealing with the same problem, the computer still freezing. :confused:

slack&lovinit 07-18-2007 01:45 PM

Black screen lock-ups
 
Hi there!

Just thought I'd add my 2 centimes worth...

I had exactly the same issues as are being spelled out here and this is how the story went:

Slackware 12 on Sharp laptop - S3 Savage video.

Leaving KDE was essentially impossible since any attempt to log-out or reboot in ANY way locked the computer to a BLACK SCREEN. No combination of keystrokes would do anything useful so powering off was the only way out.

Initial Googling brought results pointing to making amendments to a couple of files - THIS DID NOT WORK FOR ME but I include it *just* in case it helps a future reader.

~~~~~~Quote Begins~~~~~~~~~~~~~~~~~~~~~~~~~~~

My solution --

1. open /etc/X11/xorg.conf and add to Section "Device":
Option "UseInternalAGPGART" "no"

2. open /etc/kde3/kdm/kdmrc and uncomment/add this line:
TerminateServer=true

If you're using Gnome, you might want to instead do

2. open /etc/X11/gdm/gdm.conf and uncomment/add this line:
AlwaysRestartServer=true

This forces the system to restart the X server completely instead of just resetting it.
Thanks for all the help!!

~~~~~~~Quote Ends~~~~~~~~~~~~~~~~~~~~~~~~~~

As I said this didn't work for me but the following did:

from a command line, preferably before starting X issue -

lspci -v (pipe it through "less" if needed ie lspci -v | less)

near or at the bottom will be your video cards name, model number which you should make a note of.

Now before continuing make a back up of your /etc/X11/xorg.conf file as it will be over-written in the next step. The backup obviously is just in case it all goes wrong (but it shouldn't)

Next, again at the cmdline run xorgconfig.


This will take you through a menu driven setup for your keyboard, mouse, screen and video card - its pretty straightforward, if you don't know something either take the default option or err on the side of caution.

In my case there were no exact matches for my model of card but I was able to scroll through and find a generic model from the manufacturer so I chose that.

Once complete you can issue "startx" and once KDE is running log-out and/or reboot just to check.

Worked perfectly for me, I hope this helps you!

PS As noted earlier my laptop's gfx card model wasn't listed so I might go one step further and download the proper drivers from VIAARENA at some future time but hey if it ain't broke...

hlima 07-18-2007 01:50 PM

A temporary fix...
 
I copied /etc/X11/xorg.conf-fbdev to /etc/X11/xorg.conf and i got into X, and it partially worked.

bioe007 07-18-2007 02:20 PM

this is a bit of a shot in the dark.. can you try ?
Code:

$ dmesg | grep assign
if you see something like 'append pci=assign-busses' then try adding to your lilo.conf entry
Code:

append="pci=assign-busses"
and remember to run /sbin/lilo then reboot & try

also you can try appending: pci=routeirq

even both..

you can also try playing with this
Code:

Section "Device"
    Identifier  "Trident CyberBlade (generic)"
    Driver      "trident"
    #VideoRam    8192
    # Insert Clocks lines here if appropriate
EndSection

section of your xorg.conf, there are some options you can try in 'man trident'


All times are GMT -5. The time now is 09:29 PM.