I did a fresh install of Slackware64 13.37. All went well. I download the latest Ati video drivers, 11.4, and build the slackware package. Install, and run aticonfig --initial all good. But when I run startx I only get a black screen
View 13 RepliesI have just installed slackware. I have done
Code:
Xorg -configure
And chosen kde for init program while installing slackware. But when I type
Code:
Xorg -config -retro
or
Code:
startx
I get black screen with blinking button on monitor and keyboard. Obviously KDE doesn't start.
I put Slackware 13 and the scenarios is:
1. I start the computer and after startx I got black screen, the keyboard is not responding the led of the display is yellow etc. Now I reset the computer,
2. Booting Windoze
3. Choose Restart not Shutdown from Windoze
4. Booting Slack
5. startx works fine, the X server is starting and working great.
I have Radeon 9500. I configured X server with 3D accel over 2500 FPS on glxgears. The same problem persists even with X server VESA configured.
I installed backtrack4 (ubuntu based) few hours ago and i am facing a problem in getting into the graphical mode(live cd)!, hence I tried to check and run it in a "safe graphical mode" and unexpectedly it works fine! but when I switch to 1024x768 resolution in the same live cd ,and then when I type startx it just produces a black screen! After doing some research on finding a soultion to this problem I found out that this go to do some thing with editing the xorg.conf file! but when I type xorgconfig,it shows an error saying command not found!
sudo dpkg-reconfigure xserver-xorg command just talks about the keyboard!
nothing interesting on graphics or screen section!
resource: intel corporation 828456/gl 128 mb
How to modify the xorgconfig file.
I left slackware 13 with airodumb and airplay executed in console for 6 hours. When I got back, konsole had something similar to "packet has length error". I could open the packet using aircrack -m option, but when i shut down the OS, it didnt shut down properly. Now when I do startx black window stays forever. I tried pkgtool and change to KDE but the same happens.
View 4 Replies View RelatedI updated Debian system yesterday. I am getting black screen after I execute startx command. I am using system as server and manually boot into GUI mode whenever required.
View 10 Replies View RelatedI'm having a pretty serious problem, whenever I try to boot into Ubuntu the screen goes black, I see a flash of purple or violet and then i get a prompt asking for my login credentials, afterwards I'm stuck with a terminal trying to start the gui... I don't know what I'm doing wrong, fresh install tried to reboot after getting the display driversinstalled idk if that could be a problem. I tried to commands in the terminal already:
startx
sudo service gdm start
return = start: Job is already running: gdm
afeter installing ubuntu studio 10.10 a black login screen after login it asking me to type a command i've typed '' startx '' but it does't work
View 2 Replies View RelatedI'm running debian (AMD64 dist), and I recently upgraded via aptitude to KDE 4.3.4.After the upgrade I found that I could no longer start X (using startx from my user account).I am, however, able to launch kdm from a root command line and log in as a user to X this way (graphically).I want to run startx as a user and I cannot figure out where the hangup is. I've looked in my Xorg.0.log files comparing .old to current and nothing stands out. After I launch 'startx' the screen goes black and the computer waits. I can hit ctrl-alt-f2 and bring back the text-mode terminal screen; it's at a point where it looks like X is working. From there, I can control-c it and get back to the command prompt.
I'm thinking this is a software configuration thing but I don't know enough about how all the systems tie together to figure out where the problem is.
Redhat Ent Linux ES Release 2 (Taroon 8)
Kernel 2.4.21-4.ELsmp
startx(1): initialize X session - Linux man page
I thought I'd look into methods of recovering from a lost password for future use, how to change the passwd and shadow should I need to. So I started an X session, vi'd my .swp files then logged off. Perhaps I changed one of these files accidentally, but my intent was just to view them which I did. After starting up my computer the next day and logging in I began an X session - "startx". The session appears to have started, but with a black screen and an active mouse cursor.
Having slackware 13 after executing startx it gives me white screen. Heres log:
Code:
kephald starting up
XRANDR error base: 159
RRInput mask is set!!
RandRScreen::loadSettings - adding mode: 59 1024 x 768
RandRScreen::loadSettings - adding mode: 60 800 x 600
RandRScreen::loadSettings - adding mode: 61 640 x 480
RandRScreen::loadSettings - adding crtc: 57
RandRScreen::loadSettings - adding output: 58
Setting CRTC 57 on output "VGA" (previous 0 )
CRTC outputs: (58)
Output name: "VGA" .....
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted!
No battery found.
This is not a laptop, quitting ...
<unknown program name>(26219)/: Communication problem with "korgac" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "
QProcess: Destroyed while process is still running.
Graphic card is intel 82865g
Video driver installed is 2.9.0 from robby workman,
Kernel is 2.6.32.3 generic
I recently installed Slackware 13. But every time I run startx I get my XFCE screen & it hangs up. Command line works absolutely fine.
View 6 Replies View RelatedWhen trying to "startx" the machine goes to a black screen and just sits there. Only a hard reboot allows me to stop it. After SSHing into the machine and typing "startx"
[Code]...
Few days after installing Ubunto 9.10, during installation of gstreamer, the installation utility got stuck, and with it the whole desktop icons. (I think the gstreamer has nothing to do with it). When I tried to execute some icon, like the terminal, it will not open. After restarting the computer, I get a tty1 login terminal and not the graphical one (tty7). When pressing Ctrl+Alt+F7, nothing happens. It switches to a black screen. "sudo startx", gives some error log. I already reinstalled the X-server, ubuntu desktop and other stuff.
What can be the problem? Is it related to my video card (nvidia 7600 GT)? I didn't install any nvidia specific driver. This happened to me earlier and I reinstalled Ubunto. I think maybe I should move to some other distribution.
I just went out and bought a 19" flat screen LCD monitor. Plugged it in and it is not working correctly. When I start the computer the bios info will show up on the screen, then it goes to the screen that let's you choose an O/S if you were to dual boot. After clicking "enter" it will show the first line of the boot then it goes off into horizontal colors then goes black. I have search many different posts and googled but nothing is giving me a hint at this.I changed the xorg.conf to match the refresh rates to match the monitor but that did not work, and did not really think it would considering the point this monitor goes out on me. running: 2.6.27.7-smp 01:00.0 VGA compatible controller:
Silicon Integrated Systems [SiS] 315PRO PCI/AGP VGA Display Adapter
After updating my Slackware-Current (there was kernel and glibc package updates), I just get a black screen with a blinking "_" in the top-left corner when I logout.
I checked /var/log/kdm.log and found these errors:
Code:
I've found a workaround: uncommenting "TerminateServer=true" in kdmrc.
I'm running Slackware 13.37 64bit on an HP 2945 Laptop. KDE 4.5.5. I have a NVIDIA driver installed (270.41.06) and running KDE at 1200 x 800. I've upgraded to 13.37 about 2 months ago. I started noticing an issue with the windows in KDE pretty much upon start up. If I have multiple windows open and try to maximize a window or drag a corner of the window to a large size, the screen within the windows goes black. Also any menu in the windows goes black. If I resize back down the issue goes away. Or as stated before, if I have only one window open the problem doesn't exist.
View 2 Replies View RelatedHP laptop with Intel graphicsunning Slackware current with a 2.6.38.7-smp kernel.Booting with the "nomodeset" kernel parm works but X gets stuck with a 1024x768 resolution. When booting without, the screen goes black after a few pages scroll by, just at the point where the console switches to a higher resolution. Changing to a different console didn't help, so I blindly log on and type startx, and the screen comes back to life with KDE running at the higher 1366x768 resolution, I try a few apps, the webcam, suspend to RAM, resume, and everything is now working flawlessly so it doesn't look like an X issue.At this point I can change to another console (or exit KDE altogether) and the screen is back on at the higher resolution. Looking at the X log and some dmesg output makes it seem that starting X possibly replaces, reloads or unloads a driver? If this is the case, how can I prevent the conflicting driver from loading in the first place?Quote:
dmesg |grep drm
[ 11.481967] [drm] Initialized drm 1.1.0 20060810
[ 11.637941] [drm] MTRR allocation failed. Graphics performance may suffer.
[code]...
I'm trying to run Slackware 13.37 64-bit in a VirtualBox virtual machine. My VirtualBox version is 3.2.12. I had to disable compositing to keep the X-Server from reporting a segfault.Now the problem is that on logout from KDE I get a completely black screen. I can switch to a console session and type commands to get the login screen again.
telinit 3
telinit 4
I tried editing "kdmrc" to add the line "TerminateServer=true" but it had no effect on the problem.I had this working with Slackware 13.1 at one time, but I can't seem to get it working properly now even without desktop effects.I'm trying to avoid changing my VirtualBox software since each version seems to just introduce new and different bugs. The 4.X versions are not yet very stable.
i just installed slackware 13.37 which worked fine but when i boot it up it runs a number of lines and then the screen just goes black... i can login as root blindly and start x (i THINK, judging from hdd led)... but screen stays black... its a laptop and closing/opening the lid doesnt work either...
i am dualbooting with slack 13.1 which runs fine... it switches screen res at some point during boot (font is smaller) and i would say that is the point where the screen goes black in 13.37...
I am new to slackware, but not new to linux. I recently installed slackware 13.37, and am enjoying it very much so far. The most annoying problem I currently have is that, after starting X, I cannot switch to a virtual terminal or even end X without having a problem. For instance, from the GUI if I hit ctrl-alt-F1, instead of going to the 1st virtual terminal, the screen fades quickly to black and does not return. I have not been able to make any progress on this problem, so any input would be greatly appreciated.The only thing worth noting really is that I'm using Fluxbox as my default window manager. Other than that I haven't done a lot of modifications to the base system other than installing some basic packages, but I had this problem since booting directly after installation of the os.
View 14 Replies View RelatedGot my Slack running on vostro 1310 for a while now. But just Today... first for what ever reason my wifi stopped to work (at boot time) even though interface was up as usual, driver was loaded, supplicant has not been touched etc. So I wired up a LAN cable and the at boot time I saw an information from eth0 that packet length is 0 and cannot be parsed (great no network at all). Tried to investigate the problem on a different machine, and one of the suggestions I've found was to set router to no security and see if wireless will connect. I thought that it would be a good idea to reboot the machine to attach to the rooter at boot time and no eth0,wlan1 tries to connect to the network and then I get a black screen instead of login window
View 4 Replies View RelatedI installed Slackware 13.1 a little bit ago, played around with it, performed an upgrade with Slackpkg, messed around with some settings, and chose a new theme. I had set the runlevel to 4 and when I rebooted after choosing a new login theme the screen just went black at the point where the login prompt should have appeared. I couldn't even get into the CLI. Using a LiveCD, I set the run level to 3 again and was able to log in, but when I try to start X the screen goes black and freezes again, so I believe my new login theme is the culprit. Is there a way to change to the default login theme from the CLI?
View 14 Replies View RelatedI installed slackware 13.1 x86_64 bit with multilib, and its been about a month already, I'm really enjoying slackware but I am being troubled with my nvidia card, and I need to get my 3D acceleration working. And I've been looking around the net for information and kept on trying to make my nvidia card to work but to no avail. I cant get X to start, once I put in a xorg.conf stating to use the nvidia card. After troubleshooting for almost 2 weeks and now at my wits end, I now come humbly looking for help in linuxquestions slackware community forum.I've installed nvidia 64 bit kernel, drivers from slackbuilds (version 256.44). The laptop model I'm trying to get it working is an -ASUS K52J Intel Core i3 2.40Ghz with 2GB RAM and with an Nvidia Geforce 310M with 1GB dedicated VRAM.
View 14 Replies View RelatedI want to put:
xmodmap -e "pointer =3 2 1"
somewhere in the startup. It seems creating an .xsession is the solution. But after I create a .xsession file in my home folder, the next time I run startx the screen just turns black. (And only for a short while can I switch to another virtual terminal, before that too becomes impossible). After deleting the file it runs OK again. I'm not using any login/desktop manager. I use IceWM on Debian Squeeze. Is there some script/import that has to be present in the .xsession file, or is something else going on? Also I'd like to know what I should do when I get a black screen. Turning off the PC is such a crude method
i have an asus radeon x1650xt vga, i can use the latest radeon driver in ubuntu 10.04 and also in the newest fedora but in slackware 13.1 i get the same black screen i used to get with older ubuntu, fedora and other distros. i can only use slackware with the vesa driver, what could be the problem...here is my /var/log/Xorg.0.log
Code:
X.Org X Server 1.7.7
Release Date: 2010-05-04
[code]...
I was messing around with the screen orientation and thought it would be funny to orient it sideways. Big mistake The screen went black.I can force a shutdown, login and I get the same black screen. I tried hooking up an external monitor and the monitor showed no input so I'm guessing my laptop doesn't have that capability with Fedora.This is my main computer.
View 14 Replies View Relatedwhen i use the command startx my slackware goes to kde but when use X deos not. what is X command or whow i can make my X open kde with it
View 10 Replies View Relatedi've added a user using
useradd turf passwd turf and so on.. after loggin, i can't startx..
I'm running Slackware current, and just did a slackpkg upgrade. I can't startx. I get the following:
FATAL: Error inserting i915 (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format
(EE) intel(0): No kernel mode setting driver detected.
(EE) Screen(s) found, but none have a usable configuration