LinuxQuestions.org
Register a domain and help support LQ
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 11-17-2010, 05:16 PM   #106
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,477

Rep: Reputation: 51

Well, there a number of updates again tonight, many of which looked like the same as the previous update. I had hoped this was going to be a fix, but no such luck. X still seg faults. I haven't found anything in this thread that works. Guess I won't be using Slack for a while. I will see if any future updates fixes the problem before I consider my two yearl old heavily configured installation totally hosed. I have put way too much time into it to not at least try to fix it.

I noticed that the last line states that:

Quote:
Xinit: unable to connect to x server: Connection refused.
I thought that kind of error could be fixed, but maybe not.

Bob
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 11-17-2010, 05:22 PM   #107
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Rep: Reputation: 96
Quote:
Originally Posted by BobNutfield View Post
Well, there a number of updates again tonight, many of which looked like the same as the previous update. I had hoped this was going to be a fix, but no such luck. X still seg faults. I haven't found anything in this thread that works. Guess I won't be using Slack for a while. I will see if any future updates fixes the problem before I consider my two yearl old heavily configured installation totally hosed. I have put way too much time into it to not at least try to fix it.

I noticed that the last line states that:



I thought that kind of error could be fixed, but maybe not.

Bob
I had the same problem after tonight's upgrade. I don't know what video card you have, but for me re-installing the Nvidia drivers solved it.
 
Old 11-17-2010, 05:32 PM   #108
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,477

Rep: Reputation: 51
Hi Zhandband,

Thanks for your post, but this is a laptop with an ATI X1250 graphics chip. It is no long supported by the proprietary ATI drivers, but the open source version had been working well. It is using the radeon driver which gave me DRI and the works, almost as well as ATI's prop. Driver. I am using and xorg.con file, but I have tried it with that disable, and still no dive.

Thanks for the tip, though

Bob
 
Old 11-17-2010, 05:48 PM   #109
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,656

Rep: Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233
With mesa 7.9 here :
Slackware 13.1 with last Robby's X packages : startx OK to launch KDE as well as Fluxbox.
Slackware current (fresh install up to date) : startx KO to launch KDE, OK to launch Fluxbox.

I don't care for KDE personnaly, nevertheless if I can be of any help to investigate further, just ask.

lspci says : 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1).

I append the (bad) Xorg.0.log.

PS I already posted here http://www.linuxquestions.org/questi...48#post4162348 but this thread gets more attention.
Attached Files
File Type: log Xorg.0.log (32.2 KB, 2 views)
 
1 members found this post helpful.
Old 11-17-2010, 06:03 PM   #110
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,519

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
@Didier_Spaier - One other thought is to check ~/.kde/share/config/kwinrc in the [Compositing] section. I have Backend=Xrender for the nouveau driver.
 
Old 11-17-2010, 06:36 PM   #111
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,656

Rep: Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233Reputation: 1233
@allend: I cp'd current's kwinrc to 13.1 and could still launch KDE. I'll try to do the opposite later - time to sleep in Paris now
 
Old 11-17-2010, 09:47 PM   #112
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,386

Rep: Reputation: 186Reputation: 186
with a nvidia geforce 6150se can only get nv driver to work. the nvidia propierty drive get /dev/nvidiactl error (no such device or wrong address). Before these latest current upgrades, never had no problems. When rworkmen call for testing, upgraded, nouveau worked and propeirty drivers worked. When current starting moving about a month ago, reverted back to current packages and still no problems till this latest set of updates, have already tried most of the suggestions in this thread and others. have cleared out /etc/slackpkg/blacklist.conf, reinstalled a,ap,d,l,k,x, ran slackpkg clean-system, upgraded/downgraded mesa, checked permissions on /dev/nvidiactl. Thinking about reinstalling packages from rworkman website again. and then see what happens. still got a few things to try but running out of ideas. Looking for suggestions.

Last edited by colorpurple21859; 11-17-2010 at 11:03 PM.
 
Old 11-17-2010, 09:53 PM   #113
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Rep: Reputation: 96
Quote:
Originally Posted by colorpurple21859 View Post
with a nvidia geforce 6150se can only get nv driver to work. the nvidia propierty drive get /dev/nvidiactl error (no such device or wrong address). Before these latest current upgrades, never had no problems. When rworkmen call for testing, upgraded, nouveau worked and propeirty drivers worked. When current starting moving about a month ago, reverted back to current packages and still no problems till this latest set of updates, have already tried most of the suggestions in this thread and others. have cleared out /etc/slackpkg/blacklist.conf, reinstalled a,ap,l,k,x, ran slackpkg clean-system, upgraded/downgraded mesa, checked permissions on /dev/nvidiactl. Thinking about reinstalling packages from rworkman website again. and then see what happens. still got a few things to try but running out of ideas. Looking for suggestions.

Make sure you're using the latest drivers from the Nvidia website. The version at Slackbuilds.org will not work with the new x. I ran into that problem as well.
 
Old 11-17-2010, 10:18 PM   #114
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,386

Rep: Reputation: 186Reputation: 186
The latest nvidia driver was working before these last updates.
 
Old 11-17-2010, 10:30 PM   #115
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Rep: Reputation: 96
Try re-installing it if you haven't already.
 
Old 11-17-2010, 10:44 PM   #116
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,386

Rep: Reputation: 186Reputation: 186
already tried reinstalling from a fresh downloaded.
 
Old 11-17-2010, 10:47 PM   #117
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Rep: Reputation: 96
Oh... damn. Sorry, can't help you much then... re-installing the drivers worked for me.
 
Old 11-18-2010, 12:26 AM   #118
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218
One thing for everyone to keep in mind:

If you've been running -current for a while, you may have hosed something that didn't cause issues before, and then this update brought that old error to the surface. With the updates of GTK and X, other "rogue" libraries and/or packages sitting around on your system may be causing havoc.

I, for example, had been running -current without a full reinstall since the x86_64 branch first went public. Over that time, I did a lot of things; some things which I knew even at the time were not wise in the long-term. For example, when Google Chrome first came out, before the Slackbuilds.org script was available, I downloaded an Ubuntu RPM, opened it with ark, and manually placed the binaries and other files into my system. When the binaries cried for libraries, I just went out onto the net, found the actual *.so files, and put those into place. I also didn't really know what the dependencies were, so I probably wound up putting a bunch of stuff in there that I didn't really need, and who knows what they had originally been linked against.

I did stuff like that with a lot of things.

Point is, when these updates loaded up, I did everything correctly during the actual update process, but I still had lots of weird problems, none of which have been mentioned in this thread. And who would be surprised? I'd done an untold number of sketchy things to my system, because I'm a take-it-apart-and-break-it kind of guy.

So I loaded up the -current install image, mounted up my root file system and manually deleted everything except for my home directory, then pointed the setup program at my favorite mirror, installed without formating, and wallah. It all works great. And, beyond that, I was forced to reinstall all of the extraneous software I had accumulated and still use, and I did it this time using Slackbuilds.

It may seem drastic, but to really be certain that a "bug" you are observing is the fault of the update and not something else that you'd previously done and may have forgotten about, you should probably do the same.

It's mostly painless, and kinda fun. Plus, the Slackware setup is so nice and flexible, you don't even need to worry about losing any data or configurations if you do things right.

Running -current is supposed to be an adventure, anyway.

Last edited by foodown; 11-18-2010 at 12:29 AM.
 
2 members found this post helpful.
Old 11-18-2010, 03:06 AM   #119
repo
LQ 5k Club
 
Registered: May 2001
Location: Belgium
Distribution: Linux Mint
Posts: 8,516

Rep: Reputation: 896Reputation: 896Reputation: 896Reputation: 896Reputation: 896Reputation: 896Reputation: 896
Quote:
Originally Posted by mlangdn View Post
Nah, I didn't drink any red wine and I can tell a big difference. Just trying to determine if I like the difference or not.
I don't like it, fonts are ugly now.
Any suggestions?
 
Old 11-18-2010, 03:30 AM   #120
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,226

Rep: Reputation: 187Reputation: 187
Quote:
Originally Posted by repo View Post
I don't like it, fonts are ugly now.
Any suggestions?
see post #4
http://www.linuxquestions.org/questi...1114-a-844502/
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Latest current problems brodo Slackware 17 03-03-2010 11:14 AM
Latest current ? brodo Slackware 34 03-13-2009 04:15 PM
Latest nmap (4.50) in current and its gui jazzor Slackware 30 05-16-2008 01:22 PM
Race condition in /etc/rc.d/ with latest -current ? Yalla-One Slackware 1 08-06-2006 03:23 PM
warning about latest current aaa_elflibs-10.1.0 xushi Slackware 2 01-25-2005 08:57 AM


All times are GMT -5. The time now is 03:33 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration