After I upgrade my slackware to current(kernel 2.6.35.11),X could not start.My video card is ATI Radeon HD 4570.and I do reinstall fglrx like old ways :
But after restart, X could not start,and Keyboard does not respond. Also ,when I try init 3 and remove xorg.conf,The X can start with a low resolution(1024X768).In console mode,I got a high resolution(1366X768). So,is there a confict between fglrx and new kernel or What have I done Wrong?
I am using slackware64-current and this morning I have updated my system with using slackpkg. (As you know, huge changes has been applied on the current branch. Kernel, glibc and etc..) Everything went flawness and seems OK. I did not see any error message or somethink like this. After the update, kde does not start. Problem is, after KDM login, nothing happens and turn back to KDM login screen.
To understand what is going on, I switched to init 3 and performed "startx" command. Result is same but I saw some dbus error.
Then I checked whether hald and dbus does run or not and I saw it is running without problem.
Lastly I have removed dbus and hald packages and reinstalled but problem is still running.
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xb2d772fd, pid=2766, tid=2953837424 # # JRE version: 6.0_24-b07
[code]....
I tried reinstalling both JDK and Netbeans to no avail.
Kde does not start after slackware 13.0 instalation. Mouse just stop and the computer freeze. When I type startx Kde try to start, but everything stop. Does anybody know what could be this ? What log should I look ?
I have upgraded from 13.1 to 13.37 on three PCs. No problems on 2 of these (home server and laptop), but on the third machine (main Desktop, where most KDE customisation had been done of course), KDE refuses to start for the main user (me). It will start OK for root and xfce will start OK for me, so X is OK with the updated NVIDIA driver that I have also installed. The KDE splash screen starts up and four of the five splash icons come into focus, but the fifth one never does. Some disk rattling goes on for a while but then ceases.
I have tried renaming the .kde folder and .kderc but this has not helped. Are there other KDE config files that I could try renaming / removing? Or are there log files / error messages somewhere that I should consult.
Obviously I am not in a position to change any KDE system settings from the KDE application.
Just tried KDE with a newly-created user and it's the same as with my user - no desktop. So KDE is only starting for root.
Hardware - Compaq615, video - radeon hd 3200 After clean installation of 13.37 x64, proprietary ati driver, multilib. xfce.
All was o.k., video rendering was direct etc., etc. then i rebooted, and system freeze at startx. Ctrl-Alt-Backspace not working, hard reset needed. I tried xorgconfig, Xorg -configure, aticinfig --initial, deleting /etc/X11/xorg.conf with no result at all. /var/log/Xorg.0.log empty. When i do startx from root - all is o.k, writing from root now.
I normally boot into runlevel 3. KDE is my default DE. I use
Code:
To open KDE. I would like to give the other DE's (full install of Slackware current) a fair try, but I am having trouble starting the other DE's from the command line. They all work from runlevel 4 using the kdm chooser, but that's just a hassle and in all honesty will likely irritate my lazy-bone to the point of not using them on a regular basis.
Booting into runlevel 4 isn't a good option because I am frequently experimenting and booting to the command line makes troubleshooting easier. What do I need to do to be able to start the other DE's in runlevel 3?
After much pain I finally got a fairly good install of 10.04 (apparently due to my large disk earlier versions like 9.1 are a no go on my machine a Gateway mx6028 laptop with a new 160 gb drive.) I bricked the machine several times applying the bulk auto updates after the initial install so this last time I applied the updates in smaller batches,, I believe the problem is associated with some of the open GL stuff,, any way to
A) go back one update?? B) anyway to permanently mark an update to never come in?
Since installing the 10.04 update on my kubuntu 9.10 x64 system I can no longer log out, kdm doesn't restart. It just ends up with a black screen. Also when I unmute the sound and mouse over anything that has a thumbnail icon in dolphin the speakers pop. This includes pictures and movies. Then also when I leave my computer idle for a long amount of time, it wont wake up, just black screen. I have the newest ati drivers installed from ati website. Linux ubuntu 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux
I upgraded to Ubuntu 10.04 when it became available. Had it running for a while, was working fine. When I installed the new upgrades a few days ago, it asked me to restart. I did, now I can't start my computer. It turns on, but after the VAIO display, nothing happens.
Had to go buy one of those mini laptops cause they're cheap. It has Windows 7 Starter on it, and You can't even change your background on it.
In today's updates there was an update for Docky to go from 2.0.5 to 2.0.6. The thing I thought was odd was that the update was only around 600 or 700kb in size where as its normally around ~13mb.
When I restarted the computer docky loaded but the whole system froze and wouldn't respond to either mouse or keyboard so I did a hard restart. Now Docky won't load either on restart or from the program menu but it is present in the System Monitor (see attached image).
I cant start mysql of my server after the update. my operating system is centos. I get this error. MySQL Daemon failed to start. Starting MySQL: [FAILED]
I can only start my Internet connection from the root bash. If i type pppoe-start/pppoe-stop in my user's shell it just says "command not found". Any way to permit the users to bring the ppp connection up and down ?
I installed Netbeans 6.9.1 with JDK bundle, I have installed jdk in /usr/local/jdk1.6.0_2 but when I try to start Netbeans I get error
Quote:
which: no javac in (/usr/local/jdk1.6.0_2/bin:/usr/local/jdk1.6.0_2:/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin) which: no java in (/usr/local/jdk1.6.0_2/bin:/usr/local/jdk1.6.0_2:/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin) Cannot find java. Please use the --jdkhome switch.
I have javac in /usr/local/jdk1.6.0_2/bin, I looked. I installed last time and it have worked fine. What is wrong now ?
I've just install Slack 13 and had been looking into the website for configure info. What is my problem is the #xorgconfig does not start on my system. It says command not found. I had searched for answer on the web and found no answer so I post here for help. Is there anything else I need to install to get my intel graphic card display more then 1024 resolution?
I installed android SDK together with eclipse Helios 3.6.1. I downloaded and installed all android package and setup a virtual device in android 2.1 (then 2.2, 2.3). However, when I click "start" device in "android SDK and avd manager", the dialog appear and then close, but nothing happen more. I also try to run it from console by change to tools directory of android SDK and run, but it also not work, there is only one line of desperate result: "Segmentation fault". I also try to add "-no-audio" as many forums advice, but it just keep the result segmentation fault.
My device I configured to have 32MiB of SD card (and I tried 16MiB or more also). I also created the helloworld application, then try to start it, but it just stop at "Launching a new emulator with Virtual Device a2" (a2 is name of my device), and nothing more happen, I also added "-no-audio" to run configuration but I still there. By now, I have not seen any virtual devices appear. I also tried to uninstall and install again all the packages of android, but nothing help. Here is the screen when I use GDB to figure out where is the fault:
Quote:
tqminh@kemsiro:/mnt/sda9/android-sdk-linux_x86/tools$ gdb emulator GNU gdb (GDB) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
I have 13.37 installed on three PCs. Two nvidia (propriertary driver from Slackbuilds) and one ATI (radeon dirver). Kaffeine 1.1 installed from Slackbuild on all three machines. Runs fine on the ATI box and on one of the nvidia boxes, but fails to start (or provide any messages when command-line started) on the other nvidia box.The box on which it will not start is also the box that has a DVB card in it - which is why I particularly want kaffeine to run there as it has a really easy interface to the TV card which ran just fine under Slack 13.1.
My gut feeling it that the problem is connected to the presence of the TV card which is somehow srewing up initialisation of kaffeine, but (other than removing the card physically) I am not sure how to test this or test whether the card is working. lspci and dmesg shows that it has recognised during boot-up.Any ideas on how I should investigate this? Or on how I can bypass the problem by configuring vlc (which runs fine for dvds and video clips) to view DVB output?
KDE has shut down without message. Am in runlevel 5, was taken to login screen. I can start xfce, but if I attempt to login with KDE as the window manager, I am presented with the login prompt again. No error messages. where to start trouble-shooting.
I did a clean install, and so far I haven't noticed any serious problems with KDE4, although I can't find what I'm looking for, usually. I don't use my laptop much though. I also did a clean install on another system to 13.0 about the same time. X won't start on that system, it can't figure out the hardware I guess.
So I've just been using the command line. I don't really need a graphical interface on that system anyway. Right now I'm using the motherboard graphics support, but I will probably install a video card in a PCI-E slot and try X again. The system that I just upgraded from 12.2 (LUKS encrypted volumes and LVM) to 13.0 tonight has a number of problems. This was an upgrade, not a clean install. Based on my experience so far on this system, KDE4 does not seem to be ready for prime time. It is buggy, the menu system is more difficult to navigate than KDE3, and there are some apps I just can't find (e.g., Kedit). Overall it seems to have fewer apps than KDE3. Either that or they are well hidden well enough that I can't find them. My first impression was that KDE4 had clean lines and a modern appearance.......
kdevelop doesn't start in Slackware 13.1. The output just says
Code: ... /usr/bin/kdevelop.bin: symbol lookup error: /usr/lib/qt/plugins/sqldrivers/libqsqlite.so: undefined symbol: sqlite3_open_v2 Relevant packages installed on my system (all unmodified from 13.1): sqlite-3.6.23.1-i486-1 kdevelop-4.0.0-i486-1 qt-4.6.2_2d3d3e5-i486-1
So it's a problem between sqlite and qt(?). Rebuild needed?
Kongueror grash when i start it.I think that problem is backtrace module.Application:Konqueror (kdeinit4), signal: Segmentation faultTraceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module> from gobject import register
I've got slack64 13.1 and I want to get mysqld up and running, problem is it won't start. I ran the mysql_install_db --user=root command listed in the comments of the startup script, but I still get these errors:
I've got a fresh Slackware 13 install in a sata disk. I am trying to backup data from another sata disk which has Ubuntu 9.04 (or 9.10, not quite sure). Lilo starts, boots ok but for some strange reason it finishes trying to start gnome from Ubuntu, it even says that the "nvidia card is going to run with low config" and freezes there. Fstab in Slackware is set with UUID values, bios and everything points to this disk, even inittab is set with runlevel 3... Why is this happening?? Any idea? Why Slackware mounts the second disk as root and grabs its fstab?
