LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-28-2010, 05:01 AM   #1
mlpa
Member
 
Registered: May 2008
Location: Aveiro
Distribution: Slackware
Posts: 542

Rep: Reputation: 50
Update Slackware64 13.1 (27/08/2010)


Hi, today I update my boxes running Slackware64 13.1.
My box with Nvidia graphic card went ok without problems.
On the other hand my box with Ati graphic card went very very wrong.

I update the system in Run-level 3, I type startx, I get a black screen and a bar in the top, and none key combinations work.
I reboot the machine, copy the xorg.conf-vesa to xorg.conf and then startx run, but with very bad graphics. I think just download new Ati drivers, remove the old ones, build the packages of the new ones and install.

I remove the old drivers, I download the new ones, I buildpkg Slackware/All, install module and driver, and my user account is gone. Not the folder, but I can't login with my normal user. I can login with root, but I have one problem every task I want to performe I get no valid sudoers file.

This all happen with Ati graphics drivers? What have I done wrong?

Last edited by mlpa; 08-28-2010 at 07:18 AM.
 
Old 08-28-2010, 06:46 AM   #2
rpedrica
Member
 
Registered: Nov 2008
Location: Cape Town
Distribution: Slackware64 -current
Posts: 281

Rep: Reputation: 42
What Slackware version were you running? Were you on 13.1 and then updated? Or was it an earlier version you updated to 13.1? Have you checked for any *.new files in /etc/ and /etc/rc.d?

This contradicts:

"my user account is gone" and "but I can login with my normal user"

What does this mean?
 
Old 08-28-2010, 07:18 AM   #3
mlpa
Member
 
Registered: May 2008
Location: Aveiro
Distribution: Slackware
Posts: 542

Original Poster
Rep: Reputation: 50
Sorry it's a typpo, I mean I can't login with my normal account.
The box with Ati card is for mu research in the university, so I format and install Slackware64 13.1.

I think that the problem is Ati drivers and Xorg files
 
Old 08-28-2010, 08:42 AM   #4
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

Rep: Reputation: 62
I am having an issue with the new update as well. My issue is that when I login to X11, the KDE keyboard layout manager crashes. I tried to go to settings and regional settings but when I click the regional settings, it crashes as well.

This maybe related to why your key combinations don't work. I'm on 32 bit. Getting several seg faults from applications (KDE and non-KDE)

Last edited by smoooth103; 08-28-2010 at 08:53 AM.
 
Old 08-28-2010, 10:06 AM   #5
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
Quote:
Originally Posted by smoooth103 View Post
I am having an issue with the new update as well. My issue is that when I login to X11, the KDE keyboard layout manager crashes. I tried to go to settings and regional settings but when I click the regional settings, it crashes as well.

This maybe related to why your key combinations don't work. I'm on 32 bit. Getting several seg faults from applications (KDE and non-KDE)
This is irrelevant. The Original Poster is talking about 13.1, not -current (i assume) your're running. You need to either upgrade to libxml2-2.7.7 on your own or revert to the old zlib-1.2.3 Slackware package.
 
Old 08-28-2010, 02:20 PM   #6
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843
xorg-server was updated, so you should properly uninstall the ATI drivers, reinstall the latest patched xorg-server (and maybe mesa) and then reinstall the ATI drivers. I'm assuming you meant updating to the latest patches and that, therefore, your problem is with the xorg-server upgrade.
 
Old 08-28-2010, 05:56 PM   #7
mlpa
Member
 
Registered: May 2008
Location: Aveiro
Distribution: Slackware
Posts: 542

Original Poster
Rep: Reputation: 50
So my error was upgrade Slackware first and the remove ati graphics?
 
Old 08-28-2010, 06:13 PM   #8
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843
The problem is that the proprietary ATI drivers have files that conflict with xorg-server and mesa. Installing xorg-server on your system wrote over those files, and therefore your ATI setup would not work (you need the proprietary files). Uninstalling the ATI drivers removed essential files from xorg-server (since removepkg just looks at /var/log/packages/packagename when removing files -- and the ATI package lists files that were overwritten by the new xorg-server files) so X won't start at all. You should uninstall the ATI drivers (if installed), then reinstall the xorg-server and mesa packages from Slackware, and then reinstall the ATI drivers. In theory that should fix everything up, unless the new version of xorg-server has introduced an incompatibility with the ATI drivers.
 
Old 08-28-2010, 07:57 PM   #9
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875

Rep: Reputation: 282Reputation: 282Reputation: 282
Quote:
Originally Posted by T3slider View Post
Uninstalling the ATI drivers removed essential files from xorg-server (since removepkg just looks at /var/log/packages/packagename when removing files
Actually your wrong

removepkg creates a file list using the entire package database and then removes files that only exist in the package been removed

This means that the overwritten files still exist and even worse they probably include libs linked to removed files

The nividia installer is good in this regard as it includes functions to clean up after itself and it creates backup files of overwritten files that can be restored by hand if required.
 
Old 08-28-2010, 08:22 PM   #10
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843
Quote:
Originally Posted by wildwizard View Post
Actually your wrong

removepkg creates a file list using the entire package database and then removes files that only exist in the package been removed
Right you are. The corrective action should remain the same.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware64 -current (20-04-2010) problem with slackpkg mlpa Slackware 5 04-22-2010 01:55 AM
[SOLVED] Digikam 1.2.0 on Slackware64-current of 31st March, 2010 gargamel Slackware 7 04-02-2010 07:51 AM
[SOLVED] Slackware64-current 1st April, 2010: Black screen on leaving KDE session gargamel Slackware 2 04-01-2010 03:08 AM
Slackware64, v 13 no long boots after update. JamesGT Slackware 5 12-14-2009 07:47 PM
Sbopkg and Slackware64 Update chess Slackware 1 05-27-2009 09:11 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:11 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration