LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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 01-22-2011, 06:06 PM   #1
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Rep: Reputation: 1
Unhappy Just ran 'slackpkg upgrade-all'..... Now X windows doesn't work. v.segfault


I installed 13.1 on my laptop a couple months ago, everything working smoothly.
(32-bit version on an HP Pavilion P4)

This morning I ran slackpkg to update everything:
slackpkg update
slackpkg install-new
slackpkg upgrade-all

All the updates seemed to be ok, except towards the very end (I saw the 'zoo' package install ok, so it was at some point after that), there were a bunch of error-looking messages that flew past.

I reran install-new and it said everything was upgraded. But when I rebooted, and then tried to run 'startx', I got a 'signal 11: segmentation fault at address (nil)' error.

I tried running 'slackpkg reinstall' on the xinit package, but that didn't do anything.

Suggestions?
Would the backtrace lines from /var/log/Xorg.0.log be helpful?

Last edited by wolf2600; 01-22-2011 at 06:09 PM.
 
Old 01-22-2011, 06:10 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,621

Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
which mirror did you use for slackpkg? 13.1 or -Current?
 
Old 01-22-2011, 06:11 PM   #3
Noway2
Senior Member
 
Registered: Jul 2007
Distribution: Ubuntu 10.10, Slackware 64-current
Posts: 2,124

Rep: Reputation: 776Reputation: 776Reputation: 776Reputation: 776Reputation: 776Reputation: 776Reputation: 776
It really sounds like you installed something that is incompatible. Did you perchance set the repository in your /etc/slackpkg/mirrors to the wrong version, such as a 64 bit on a 32 bit install?
 
Old 01-22-2011, 06:12 PM   #4
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,278

Rep: Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587
One can sometimes have md5 errors when running slackpkg upgrade-all. Perhaps try running slackpkg upgrade-all again from run level three.
 
Old 01-22-2011, 06:46 PM   #5
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by hitest View Post
One can sometimes have md5 errors when running slackpkg upgrade-all. Perhaps try running slackpkg upgrade-all again from run level three.
Well, there's a problem with that. When I start with 'linux 3', my wireless doesn't work. I had it setup and working using wicd, but for some reason in linux 3, wicd isn't being used or something like that, so I have no network connectivity.
 
Old 01-22-2011, 06:48 PM   #6
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by willysr View Post
which mirror did you use for slackpkg? 13.1 or -Current?
For the mirror, I'm not sure which it used. I didn't specify one explicitly when I ran slackpkg.
The site it used in the mirrors file was slackware.oregonstate.edu.
I don't recall seeing any "64" mentioned in any of the directory paths when it was downloading the packages, so I think (hope) that I'm ok in that regard.


edit: just reran 'slackpkg update' and it IS using -current as the version.

Last edited by wolf2600; 01-22-2011 at 06:50 PM.
 
Old 01-22-2011, 06:53 PM   #7
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
How would I reinstall/overwrite JUST the Xwindows installation using the original 13.1 DVD?

Do I just boot from the DVD and it'll give me that option, without overwriting the entire installation?

Last edited by wolf2600; 01-22-2011 at 06:54 PM.
 
Old 01-22-2011, 07:05 PM   #8
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
Here's what I get spit back when 'startx' fails (if it's any help):


enable LVDS
disable primary dac
disable TV

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e6d0b]
1: /usr/bin/X (0x8048000+0x5daf5) [0x80a5af5]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
3: /usr/lib/xorg/modules/extensions/libglx.so (0xb72ea000+0x407ac) [0xb732a7ac]
4: /usr/lib/xorg/modules/extensions/libglx.so (0xb72ea000+0x37848) [0xb7321848]
5: /usr/bin/X (InitExtensions+0x9d) [0x80cb83d]
6: /usr/bin/X (0x8048000+0x1ad22) [0x8062d22]
7: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7371c66]
8: /usr/bin/X (0x8048000+0x1aaa1) [0x8062aa1]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

finished PLL2
finished PLL1
Entering Restore TV
Restore TV PLL
Restore TVHV
Restore TV Restarts
Restore Timing Tables
Restore TV standard
Leaving Restore TV
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

My_Command_Prompt#


(and I gotta say, navigating this site in lynx is not pleasant)

Last edited by wolf2600; 01-22-2011 at 07:08 PM.
 
Old 01-22-2011, 07:09 PM   #9
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,621

Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Quote:
Originally Posted by wolf2600 View Post
For the mirror, I'm not sure which it used. I didn't specify one explicitly when I ran slackpkg.
The site it used in the mirrors file was slackware.oregonstate.edu.
I don't recall seeing any "64" mentioned in any of the directory paths when it was downloading the packages, so I think (hope) that I'm ok in that regard.


edit: just reran 'slackpkg update' and it IS using -current as the version.
ic... that's the problem
i think you should go back to 13.1 for stable version if you need a stable system
-Current is for development and there might be some problem if you are not used to it, even though most people (including me) have no problem running -Current as of now
 
Old 01-22-2011, 07:11 PM   #10
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by willysr View Post
ic... that's the problem
i think you should go back to 13.1 for stable version if you need a stable system
-Current is for development and there might be some problem if you are not used to it, even though most people (including me) have no problem running -Current as of now
I see. So just rerun slackpkg, but specify 13.1 as the version?
 
Old 01-22-2011, 07:46 PM   #11
EdGr
Member
 
Registered: Dec 2010
Location: California, USA
Distribution: Slackware
Posts: 117

Rep: Reputation: 22
Do you have an ATI video card?

The X11 in Slackware -current segfaults in exactly the manner that you described on two of my machines with ATI radeon video cards.

For -current to work with these cards, you need to enable kernel modesetting

echo options radeon modeset=1 > /etc/modprobe.d/radeon-kms.conf

and load the radeon kernel module

/sbin/modprobe radeon

Then, startx. X should work fine.
Ed
 
Old 01-22-2011, 07:50 PM   #12
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by EdGr View Post
Do you have an ATI video card?

The X11 in Slackware -current segfaults in exactly the manner that you described on two of my machines with ATI radeon video cards.

For -current to work with these cards, you need to enable kernel modesetting

echo options radeon modeset=1 > /etc/modprobe.d/radeon-kms.conf

and load the radeon kernel module

/sbin/modprobe radeon

Then, startx. X should work fine.
Ed
Yes, it has an ATI. That's probably it. But I'm already reverting back to the 13.1 packages. In the unlikely event that the revert doesn't work, I'll give this a shot.

Thanks to everyone who replied. Learned some new tidbits.
 
Old 01-22-2011, 08:19 PM   #13
wolf2600
LQ Newbie
 
Registered: Nov 2010
Distribution: Slackware
Posts: 29

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by EdGr View Post
Do you have an ATI video card?

The X11 in Slackware -current segfaults in exactly the manner that you described on two of my machines with ATI radeon video cards.

For -current to work with these cards, you need to enable kernel modesetting

echo options radeon modeset=1 > /etc/modprobe.d/radeon-kms.conf

and load the radeon kernel module

/sbin/modprobe radeon

Then, startx. X should work fine.
Ed
One more quick question- would enabling the modesetting on the 13.1 version cause any problems? Provide any benefits?
 
Old 01-22-2011, 08:31 PM   #14
EdGr
Member
 
Registered: Dec 2010
Location: California, USA
Distribution: Slackware
Posts: 117

Rep: Reputation: 22
Quote:
Originally Posted by wolf2600 View Post
One more quick question- would enabling the modesetting on the 13.1 version cause any problems? Provide any benefits?
As I understand, the kernel modesetting works on most cards but not all, which is why it is off by default. Linux and X11 have been moving in the direction of requiring kernel modesetting because user modesetting was a very bad design decision.

I have kernel modesetting enabled on three machines running -current and it works completely correctly on two, and is usable on the third as long as I don't switch between X and the console more than three times.

I'm not sure about 13.1. Your mileage may vary.
Ed
 
Old 01-23-2011, 07:47 AM   #15
Noway2
Senior Member
 
Registered: Jul 2007
Distribution: Ubuntu 10.10, Slackware 64-current
Posts: 2,124

Rep: Reputation: 776Reputation: 776Reputation: 776Reputation: 776Reputation: 776Reputation: 776Reputation: 776
I am still running 13.1, but I remembered that there was mention of X in the process of upgrading from 13.1 to -current, which is what you appear to have inadvertent done with the selection of the mirror. It probably won't help you now, but for future reference, here is the link. BTW, this is an excellent Slackware tutorial site.
 
  


Reply

Tags
segmentation fault, slackpkg, xwindows


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
[SOLVED] Salome-Meca doesn't work after slackpkg upgrade-all theCapitain Slackware 3 09-25-2010 09:39 AM
[SOLVED] After upgrade all using slackpkg upgrade, configuration is failed to read ethereal1m Linux - Newbie 3 04-28-2010 02:03 AM
slackpkg upgrade-all does not show an upgrade sycamorex Slackware 6 11-03-2009 06:29 AM
Ran dist upgrade and now my printer does not work davholla Debian 1 10-28-2006 12:17 PM
just ran upgrade-system and... xucaen Debian 10 10-09-2006 04:21 PM


All times are GMT -5. The time now is 11:29 AM.

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