SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm trying to upgrade from 11.0.0 to current. I followed the upgrade.txt. I've got the 2.4.33.3 kernel. The 2.6 (huge) kernel installed ok and the computer boots but the mouse doesn't function (it loads kde ok).
I'm upgrading from 11.0 to current - I have the 2.6 (huge) kernel and am able to boot to runlevel 3 and login and then startx to kde - but when I try runlevel 4 it goes to a login screen that goes black (after logging in) and then back to the login screen and doesn't bring up kde. Also - the "windows" choice in lilo brings up "invalid system disk" and won't boot any longer. I've installed the a, d, x, kde and l packages so far.
I'm doing it this way because it takes so much time to install the packages with upgradepkg. I couldn't find an iso version to put on a cd. Also, I'm running out of space on my hard drive. I've got a 2nd drive that has lots of space but I don't know a way to get the programs to install to it. So, I have to go thru and delete to make space.
I was wondering why you need to be in runlevel 1 to install the packages? There are no other users on this system.
You can get an unnoficial -current cd or dvd iso here (updates every week) or use the all famous AlienBob script to create it.
I guess it's easier to reinstall using the iso and then check the changelog to be up to date.
gl
was wondering why you need to be in runlevel 1 to install the packages? There are no other users on this system.
You don't need to switch into runlevel 1 to upgrade every package, but when upgrading something like glibc (or any other widely used library) you want to be in runlevel 1 so that as few processes as possible are running. This limits (and ideally eliminates) the chances of a process attempting to access the library you are currently upgrading before the upgrade has completed.
It Seems to me you have a X-server configuration problem, not kde.
Try running starting "startx" at runlevel 3. If you get the same problem, and i guess you will, you can suspect the configuration ( -files ) of the X-server ( Overwritten probably during upgrade )
I would check xorg.conf and/or the logfile of the X server under /var/log.
Maybe try to rerun xorgcfg or xorgconfig might help, especially the display graphic adpater section(s).
that looks like a disaster waiting to happen... so much has changed, the X/gcc/HAL stuff alone is enough to scare me off (and this is coming from a long-time slack fan ) at the moment I need this machine to work, so I can't afford to spend the time to dig my way out of the inevitable problems. I'll be waiting for the official 12.0 release.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.