LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 12-17-2013, 11:16 PM   #1
liltux
Member
 
Registered: Mar 2011
Posts: 39

Rep: Reputation: 2
Slacke17 does or doesn't work on slack14.1_64 running on an Acer Aspire 5100?


Hello, ok so I am running a fresh install of slack14.1 w/ current updates. I was looking to try out enlightenment on slackware, and came across ngc891 hard work and figured I would give it a try. I first tried ngc891's easy installation script for the full install w/ extras. When I would either use kdm or startx I would get a pointer for a split second and then I would get a black screen. So I then removed the packages with the script, and using the nice slackbuilds, built all the packages on my machine and installed them that way. Also to note I followed the order described. Now here is the odd part, unlike the first attempt I did a reboot to tryout through kdm, this time all I did was logout to the kdm login screen. I was able to click the drop down list and select the enlightenment session and login. This time enlightenment started fine. I was able to spend all evening configuring my desktop and playing around with enlightenment. Then on the next Boot up of my laptop got me right back where I started the first time, a black screen. Now I have already been through /var/log/Xorg.0.log and /var/log/messages and I think I have found a place where it is describing the video card is already in use or something to that extent.
Here is what I get in the /var/log/Xorg.0.log:
Quote:
[ 44.798] (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/event7)
[ 44.798] (II) No input driver specified, ignoring this device.
[ 44.798] (II) This device may have been added with another device file.
[ 44.798] (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/js0)
[ 44.798] (II) No input driver specified, ignoring this device.
[ 44.798] (II) This device may have been added with another device file.
[ 83.776] (II) AIGLX: Suspending AIGLX clients for VT switch
and from /var/log/Xlog.1.log:
Quote:
[ 142.079] (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/event7)
[ 142.079] (II) No input driver specified, ignoring this device.
[ 142.079] (II) This device may have been added with another device file.
[ 142.079] (II) config/udev: Adding input device Acer BMA150 accelerometer (/dev/input/js0)
[ 142.080] (II) No input driver specified, ignoring this device.
[ 142.080] (II) This device may have been added with another device file.
[ 144.444] (II) RADEON(0): EDID vendor "QDS", prod id 65
[ 144.444] (II) RADEON(0): Printing DDC gathered Modelines:
[ 144.444] (II) RADEON(0): Modeline "1280x800"x0.0 68.90 1280 1301 1333 1408 800 804 808 816 -hsync -vsync (48.9 kHz eP)
[ 154.263] (II) RADEON(0): EDID vendor "QDS", prod id 65
[ 154.263] (II) RADEON(0): Printing DDC gathered Modelines:
[ 154.263] (II) RADEON(0): Modeline "1280x800"x0.0 68.90 1280 1301 1333 1408 800 804 808 816 -hsync -vsync (48.9 kHz eP)
[ 154.301] (II) RADEON(0): EDID vendor "QDS", prod id 65
[ 154.301] (II) RADEON(0): Printing DDC gathered Modelines:
[ 154.301] (II) RADEON(0): Modeline "1280x800"x0.0 68.90 1280 1301 1333 1408 800 804 808 816 -hsync -vsync (48.9 kHz eP)
[ 3251.829] [mi] Increasing EQ size to 512 to prevent dropped events.
and this is in the messages log:
Quote:
Dec 17 22:03:59 Slackware64 blueman-mechanism: Starting blueman-mechanism
Dec 17 22:03:59 Slackware64 dbus[614]: [system] Successfully activated service 'org.blueman.Mechanism'
Dec 17 22:04:00 Slackware64 blueman-mechanism: loading RfKill
Dec 17 22:04:00 Slackware64 blueman-mechanism: loading Config
Dec 17 22:04:00 Slackware64 blueman-mechanism: loading Network
Dec 17 22:04:00 Slackware64 blueman-mechanism: loading Ppp
Dec 17 22:04:29 Slackware64 blueman-mechanism: Exiting
Dec 17 22:21:35 Slackware64 -- MARK --
Dec 17 22:41:35 Slackware64 -- MARK --
So I am looking for suggestions as to where to dig deeper to find the problem or maybe one has experienced this same problem and I just need to make a slight change to my installation and or config file somewhere. Many thanks up front to any and all the help. And I would like to say "good job" to ngc891 for the packages, when I got it to work it seemed to work well.

Another note: I dont get around to my linux or any computer often so it might be a day or two before I get around to responding to posts or trying out suggestions.

Thanks again.

Last edited by liltux; 12-20-2013 at 06:53 AM.
 
Old 12-19-2013, 12:47 PM   #2
arsivci0
Member
 
Registered: Nov 2013
Location: Antalya
Distribution: Slackware64 14.1
Posts: 61

Rep: Reputation: 7
It's been 2+ years since I used e17 and I vaguely remember that it required PAM which Slackware does not carry. Try switching back to run level 3 instead of GDM/KDM or whatever.
 
Old 12-20-2013, 01:33 AM   #3
Stephen Morgan
Member
 
Registered: Feb 2011
Location: England
Distribution: Slackware
Posts: 147

Rep: Reputation: 15
slacke17 is compiled without PAM.
 
Old 12-20-2013, 04:44 AM   #4
arsivci0
Member
 
Registered: Nov 2013
Location: Antalya
Distribution: Slackware64 14.1
Posts: 61

Rep: Reputation: 7
Quote:
Originally Posted by Stephen Morgan View Post
slacke17 is compiled without PAM.
I am aware of that. Yet, I remember (I may be wrong) log in/out problems due to "lack of PAM", as I said previously, 2+ years ago.
 
Old 12-20-2013, 04:52 AM   #5
arsivci0
Member
 
Registered: Nov 2013
Location: Antalya
Distribution: Slackware64 14.1
Posts: 61

Rep: Reputation: 7
Let me clarify:

I successfully used e17 w/o PAM, i.e. I did not mean e17 does not work in Slackware. It does. Still I vaguely remember it complaining PAM is required for something related to log in/out. I am terribly sorry I cannot say exactly what it was.

Last edited by arsivci0; 12-20-2013 at 04:54 AM.
 
Old 12-20-2013, 06:48 AM   #6
liltux
Member
 
Registered: Mar 2011
Posts: 39

Original Poster
Rep: Reputation: 2
First, thanks for the replies.
Quote:
It's been 2+ years since I used e17 and I vaguely remember that it required PAM which Slackware does not carry. Try switching back to run level 3 instead of GDM/KDM or whatever.
Ok, arsivci0, I am experiencing the lockup situation from both run level 3 using startx and from run level 4 using kdm. I was wrong in my previous description that when in kdm it freezes with a black screen but instead it freezes with the kdm background on the screen and when in run level 3 it just gives me a black screen when it freezes up. I am always able to ctl+alt+F2 to get around it and kill the process. I did however find a slackbuild, nss-pam-ldapd (0.8.12), I might try installing it first and rebuilding my slacke17 packages.

Last edited by liltux; 12-20-2013 at 06:51 AM.
 
Old 12-20-2013, 06:59 AM   #7
arsivci0
Member
 
Registered: Nov 2013
Location: Antalya
Distribution: Slackware64 14.1
Posts: 61

Rep: Reputation: 7
Quote:
Originally Posted by liltux View Post
First, thanks for the replies.

Ok, arsivci0, I am experiencing the lockup situation from both run level 3 using startx and from run level 4 using kdm.
If that is the case, you should probably not mess with PAM at all. I'm sure someone else might suggest an alternative. Before you take such drastic steps (PAM), maybe you can cross post this do a desktop or e17 related forum.
 
Old 12-20-2013, 08:49 AM   #8
Stephen Morgan
Member
 
Registered: Feb 2011
Location: England
Distribution: Slackware
Posts: 147

Rep: Reputation: 15
Quote:
Originally Posted by arsivci0 View Post
Let me clarify:

I successfully used e17 w/o PAM, i.e. I did not mean e17 does not work in Slackware. It does. Still I vaguely remember it complaining PAM is required for something related to log in/out. I am terribly sorry I cannot say exactly what it was.
Screen lock complains about lack of PAM, although it does allow you to specify an external screen locking programme which solves the problem, slock or xlock or something similar.

I did use e17, but it frequently crashes, freezes or refuses to run. The settings dialogue box is especially likely to crash the entire desktop. These problems seem to become worse with every version.
 
Old 01-01-2014, 10:09 PM   #9
ngc891
Member
 
Registered: Jan 2012
Location: South Korea
Distribution: Slackware64 OpenBSD
Posts: 50

Rep: Reputation: Disabled
Quote:
Originally Posted by liltux View Post
So I am looking for suggestions as to where to dig deeper to find the problem or maybe one has experienced this same problem and I just need to make a slight change to my installation and or config file somewhere.
The fact you get different behavior after a reboot makes me think about an hardware problem. Maybe the video driver?

First thing to check: be sure your /tmp is clean and has correct permissions.

Then, be sure to nuke your ~/.e before the first launch and don't use init 4 at first.

Try to change your video driver.

If you are still getting problem, I suggest you to post your problem to <enlightenment-devel@lists.sourceforge.net> joining your hardware spec along with contents of ~/.xsession-errors and ~/.e-crashdump.txt if any.

I'll push SlackE18 in few days, you could try it and maybe you'll be luckier.
 
Old 01-01-2014, 10:28 PM   #10
ngc891
Member
 
Registered: Jan 2012
Location: South Korea
Distribution: Slackware64 OpenBSD
Posts: 50

Rep: Reputation: Disabled
Quote:
Originally Posted by Stephen Morgan View Post
I did use e17, but it frequently crashes, freezes or refuses to run. The settings dialogue box is especially likely to crash the entire desktop. These problems seem to become worse with every version.
That's not my experience and I'm using it everyday on several Slackware systems. The only remaining issue i got was a random focus problem, difficult to reproduce. E17 is in stable state since it's first release in 2012 and didn't get any new code then. If you check the git code history you'll see that there have been hundreds of bugfixes and backports in 2013 for the 0.17 branch. It's objectively difficult to say that things are getting worse.

If you're going to play with E18 or even E19, that's another story.
 
Old 01-02-2014, 08:46 PM   #11
liltux
Member
 
Registered: Mar 2011
Posts: 39

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by ngc891 View Post
The fact you get different behavior after a reboot makes me think about an hardware problem. Maybe the video driver?

First thing to check: be sure your /tmp is clean and has correct permissions.

Then, be sure to nuke your ~/.e before the first launch and don't use init 4 at first.

Try to change your video driver.

If you are still getting problem, I suggest you to post your problem to <enlightenment-devel@lists.sourceforge.net> joining your hardware spec along with contents of ~/.xsession-errors and ~/.e-crashdump.txt if any.

I'll push SlackE18 in few days, you could try it and maybe you'll be luckier.
Thanks for the information. I was thinking it is more than likely a driver issue? Is it possible that the enlightenment desktop is trying to use a different driver? or has a compatability issue with its configuration and the driver? Oh well, I think we are on the right track. I will try and get on my linux box this weekend and see what I can get out of it. I appreciate all the responses and help!
 
Old 01-05-2014, 02:56 PM   #12
liltux
Member
 
Registered: Mar 2011
Posts: 39

Original Poster
Rep: Reputation: 2
to ngc891:

no luck on any log files:
Quote:
along with contents of ~/.xsession-errors and ~/.e-crashdump.txt if any.
output of lspci:
Quote:
01:05.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] RS482M [Mobility Radeon Xpress 200]
I am curious now if anyone else with this hardware has experienced same issue. I will look into the sourceforge devel for some advice, thanks for the help.
 
Old 01-06-2014, 10:52 PM   #13
liltux
Member
 
Registered: Mar 2011
Posts: 39

Original Poster
Rep: Reputation: 2
Well I believe it is a hardware issue on my side. I tried downloading another distro that comes built around Enlightenment. I tried running Bodhi Linux, which I have tried out before on a desktop of mine. Well when I booted the live disc it failed to open the window manager and defaulted to a console. So at this point I will have to wait until I get a better video card or an updated laptop. oh well just means I get to explore xfce more. Thanks for all the help from everyone!!
 
  


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
Mouse doesn't work at times on Acer Aspire X1200 with Ubuntu 11.04 TheRegan Linux - Newbie 1 08-20-2011 12:09 PM
Audio Driver for Acer Aspire 5100 bezgodo Solaris / OpenSolaris 1 08-21-2007 02:54 AM
installation problem on Acer aspire 5100 bezgodo Linux - Laptop and Netbook 8 06-12-2007 08:09 PM
Wireless on Acer Aspire 5100 Cabeza de Huevo Linux - Laptop and Netbook 1 12-17-2006 02:59 PM
ACER Aspire 5100 Wireless taj Suse/Novell 4 11-11-2006 09:26 PM


All times are GMT -5. The time now is 05:20 AM.

Main Menu
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