Slackware 12.0 default vesa xorg.conf - blank screen
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. |
One thing you can do is when it locks up is to hold CTRL+ALT then hit F1...see if this will let you see what's going with X...perhaps there is an error there that you're missing. You could also Ctrl-C it from here to end it. I would also wonder though if you've got some sort incorrect paramter in your xorg.conf file.
|
The whole computer freezes, I can't do anything.
|
Please post here the output of lspci -v command (I don't find 1805-s23 model). Do you use framebuffer or vga = normal (/etc/lilo.conf)?
|
Sorry, the model is Toshiba Satellite 1805-s273. I use vga = normal in /etc/lilo.conf. What specific info did you need from lspci? I will try to post the output later. Thanks.
|
Read http://www.kurtwerks.com/linux/toshiba.html (see Section "Monitor"). It's for Toshiba Satellite 1805-S253. Maybe help you.
|
Thanks for the link, I tried the suggestions, but it still freezes. Any idea where I should be looking? As far as logs, etc. besides Xorg log?
|
If it is freezing I'd almost point the finger at something hardware related. Overheating, memory issues...
|
Well, I ruled out hardware problems because it works w/ old xorgs (old as in not modular x) from gentoo 2007.0 live cd and pclinuxos' latest offering as well. Does your Xorg logs end w/ the loading of a DDC module? As there are no errors in my Xorg log, maybe it's because the system locks before it can write out an error...
|
i just noticed that some of my old options in xorg.conf now kill my system... specifically:
Code:
#Option "AGPFastWrite" "true" # [<bool>] I don't know what card you have, but you might try a fresh xorgsetup to make a new xorg.conf, then (what I did) Code:
diff -u /etc/X11/xorg.conf myXorg.conf > somefile |
xorg
Quote:
|
The card is a Trident Cyberblade card. In the past xorg has used the trident driver. Unfortunately there's not much (new) info using this card and the new xorg. I've read most of the articles that google's given me but, none of them cover the new modular xorg. What's got me stumped is that even the default xorg.conf that Pat provides doesn't even work and it's always worked for me, even in 11.0.
So far I've tried the "NoDDC" option, the "DPMS" option, the DRI mode 0666 option... with the same results. I'm going to re-install 11.0 and diff that xorg.conf w/ a 12.0 one... along the lines of what bioe007 suggested. In the mean time, if anyone can shed _any_ light or point me in the right direction I would greatly appreciate it. I appreciate everyone's help who has replied. Thank you. |
it might be helpful if your post: lspci -v, xorg.conf, lsmod
|
Here is my lsmod output, lspci -v output, and xorg.conf file. Hope this helps. Thanks.
lsmod Code:
Module Size Used by Code:
00:00.0 Host bridge: ALi Corporation M1632M Northbridge+Trident (rev 01) xorg.conf Code:
# File generated by xorgconfig. |
Try these settings in /etc/X11/xorg.conf
Code:
# Identifier and driver Code:
Identifier: Trident CyberBlade (generic) |
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. |
Thanks for all the help everyone.
Road_map: I tried the settings you suggested. Still no go. :confused: |
What do I have to do to try and debug this problem. Where should I be looking for errors? Thanks.
|
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? |
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.
|
it seems ali_agp is already loaded, but for example with X running on my lappy;
Code:
radeon 110752 2 for my setup it is the i845 chipset and ATI radeon card, so for AGP the intel_agp, then for drm the radeon module. |
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.
|
there are some options in man Xorg you can try:
Code:
Xorg -verbose 3 -probeonly & where <number> is some number of lines up to let you see whats what.. hth |
Quote:
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 |
I had this problem before installing the nvidia driver. I would logout of xfce and it would just be a black screen. Slackware 12
|
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. |
Same problem with 1805-S203
I'm dealing with the same problem, the computer still freezing. :confused:
|
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... |
A temporary fix...
I copied /etc/X11/xorg.conf-fbdev to /etc/X11/xorg.conf and i got into X, and it partially worked.
|
this is a bit of a shot in the dark.. can you try ?
Code:
$ dmesg | grep assign Code:
append="pci=assign-busses" also you can try appending: pci=routeirq even both.. you can also try playing with this Code:
Section "Device" |
Just like to add that I have the same make and model of Laptop ad tried loading Absolute Linux, a slackware based distro, yesterday.
I got exactly the same problem. From what I've read, it appears to be a problem with V12, not V11 |
All times are GMT -5. The time now is 08:41 PM. |