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-19-2010, 08:46 AM   #136
kenjiro
LQ Newbie
 
Registered: Feb 2004
Location: Brazil
Distribution: Slackware Linux
Posts: 16

Rep: Reputation: 1

Hello there. I upgrade to slackware64-current yesterday. Before that I was already running -current.

So at first I had some nasty problems, but then after reading alienBob's blog I found out I should have upgraded the aaa_elflibs too. Ok, after that I have a new problem: Xorg won't work as it should with nvidia driver.

I use a Lenovo desktop at work, it has a NVidia 8400GS. I was already running the latest proprietary driver prior to this last upgrade on -current. If I use the 'nv' driver on xorg.conf I can use X normally, no matter the Window Manager.

Then if I try to use the nvidia driver (yes I uninstalled and installed it again, even rebooted the desktop), Xorg looks like it is working (it comes up and runs), but I get a black screen, no matter the WM I use (kde, lxde or xfce). No errors on the stderr or the /var/log/Xorg.0.log. So... it looks like it is running normally, I just can't see a thing.

Any hints?
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 11-19-2010, 09:39 AM   #137
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
Quote:
Originally Posted by rmjohnso View Post
Everything is working for me (granted I did a clean install), but now my /dev/cdrom symlink to /dev/sr0 is not being created anymore.
Try removing the persistent optical devices rules file in /etc/udev/rules.d/ -- that will (or should) make it be regenerated on next boot, and things should be okay from then on.
 
Old 11-19-2010, 09:40 AM   #138
rmjohnso
Member
 
Registered: Mar 2006
Location: Wisconsin
Distribution: Slackware64-Current
Posts: 294

Rep: Reputation: 43
Quote:
Originally Posted by GazL View Post
Did a completely clean install from a dvd-burn of yesterdays 64 current tree. I have the same issue as rmjohnso with regard to /dev/cdrom, /dev/dvd symlinks not being there, but I've fallen in to the habit of just using /dev/sr0 ever since the libata change, so I didn't actually notice until (s)he posted and I checked.
Other than having rc.local re-create the link every time the system boots, what are some other options?
 
Old 11-19-2010, 09:53 AM   #139
akiku
Member
 
Registered: Jun 2009
Distribution: Slackware
Posts: 62

Rep: Reputation: 17
Quote:
Originally Posted by BobNutfield View Post
Thanks for your reply. I have been using an xorg.conf file for a long time and it has always worked perfectly. The driver is the open source "radeon" driver.
I use the same drive and have the same problem as you and now my system is completely up to date with -current.

Looks like the radeon driver got hosed with the changes.
 
Old 11-19-2010, 10:02 AM   #140
GazL
Senior Member
 
Registered: May 2008
Posts: 3,503

Rep: Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026
Quote:
Originally Posted by rworkman View Post
Try removing the persistent optical devices rules file in /etc/udev/rules.d/ -- that will (or should) make it be regenerated on next boot, and things should be okay from then on.
It's a completely fresh install robby, so /etc/udev/rules.d was empty.

I think the problem is that the /lib/udev/write_cd_rules script that should be called by 75-cd-aliases-generator.rules is either not being called, or not creating a /etc/udev/rules.d/70-persistent-cd.rules at all.

I have got a 70-persistent-net.rules in there though, so it looks like it's just the cd-rules that aren't working.


God I hate udev. How the udev devs managed to make such a simple concept as udev so complicated is completely beyond me!

Last edited by GazL; 11-19-2010 at 10:16 AM.
 
Old 11-19-2010, 10:27 AM   #141
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
I did a clean install of Slackware-current yesterday using the November 18 build. I kept my home partition intact. I have not noticed any issues with this build yet. XFce functions normally and I can launch the KDE apps that I like to use from my menu.
I'll post back if I notice anything awry.
 
Old 11-19-2010, 12:08 PM   #142
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
Don't blame udev - this one is my fault. I killed too many lines while removing unneeded cruft.
That's also what's wrong with bluez probably

Code:
--- rc.udev.current	2010-11-19 11:01:02.199043877 -0600
+++ rc.udev	2010-11-19 11:05:11.185794299 -0600
@@ -111,6 +111,9 @@
 
 	  echo 'ACTION=="!remove", SUBSYSTEM=="block", ENV{MAJOR}=="'$MAJORNUMBER'", ENV{MINOR}=="'$MINORNUMBER'", SYMLINK+="root"' > /dev/.udev/rules.d/61-dev-root-link.rules
 
+	  # Set OPT="--action=add" to generate add events on coldplug
+	  OPT="--action=add"
+
 	fi
 
 	echo "Triggering udev events:  /sbin/udevadm trigger $OPT"
 
3 members found this post helpful.
Old 11-19-2010, 03:17 PM   #143
rmjohnso
Member
 
Registered: Mar 2006
Location: Wisconsin
Distribution: Slackware64-Current
Posts: 294

Rep: Reputation: 43
Thanks, Robby! I'll check it out when I get home later to see if that solves my problem.

[edit]The patch to rc.udev fixed my cdrom symlink issue.[/edit]

Last edited by rmjohnso; 11-19-2010 at 06:04 PM. Reason: Implemented Robby's patch from above
 
Old 11-19-2010, 07:59 PM   #144
rfernandez
Member
 
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264

Rep: Reputation: 40
Quote:
Originally Posted by rworkman View Post
Don't blame udev - this one is my fault. I killed too many lines while removing unneeded cruft.
That's also what's wrong with bluez probably

Code:
--- rc.udev.current	2010-11-19 11:01:02.199043877 -0600
+++ rc.udev	2010-11-19 11:05:11.185794299 -0600
@@ -111,6 +111,9 @@
 
 	  echo 'ACTION=="!remove", SUBSYSTEM=="block", ENV{MAJOR}=="'$MAJORNUMBER'", ENV{MINOR}=="'$MINORNUMBER'", SYMLINK+="root"' > /dev/.udev/rules.d/61-dev-root-link.rules
 
+	  # Set OPT="--action=add" to generate add events on coldplug
+	  OPT="--action=add"
+
 	fi
 
 	echo "Triggering udev events:  /sbin/udevadm trigger $OPT"
That solved my problem with bluetooth usage. But I also noticed that Bluez-4.78 did not initialize my bluetooth module right; everytime I had to "hciconfig hci0 reset" so I could use it. On the bluez.org site

Quote:
Release of bluez-4.79

This release fixes a race conditions with the adapter initialization. Additionally it also updates support for the new Bluetooth Management interface.
upgrading to bluez-4.79 solved my bluetooth initialization.
 
2 members found this post helpful.
Old 11-19-2010, 09:43 PM   #145
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,658
Blog Entries: 3

Rep: Reputation: 224Reputation: 224Reputation: 224
Quote:
So at first I had some nasty problems, but then after reading alienBob's blog I found out I should have upgraded the aaa_elflibs too. Ok, after that I have a new problem: Xorg won't work as it should with nvidia driver.
this happened on my current x86 system the fix I had to do two things. deleted my .kde file then
this got kde going. but the next problem is the setting for composite kwin desk when you do that it goes blank then goes black. I had to go in even though i was using nvidia and set it to direct render then it failed nice then reset to openglx and it is fixed. this is a kwin problem after the last upgrade and it did it for 4.5.1 to 4.5.3 . it has to to with kwin composite setting.
It works because your reading this. did not have the problem in x86_64 yet going to upgrade that now.
as posted earlier
Quote:
@Didier_Spaier - One other thought is to check ~/.kde/share/config/kwinrc in the [Compositing] section. I have Backend=Xrender for the nouveau driver.

Last edited by Drakeo; 11-19-2010 at 09:49 PM.
 
Old 11-19-2010, 09:44 PM   #146
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 433

Rep: Reputation: 30
So far everything is working fine. I do the updates to follow UPGRATE.TXT, literally ...

My hardware
Giga-Byte motherboard GA_MA78GM_S2H
Nvidia 9500GT video card (NVIDIA-Linux-x86_64-260.19.21.run)
CDRW
DVDRW
AMD Processor 5200 +
OS Slackware (of course :-)) current 64bit multilib
Until now, even my Lucent winmodem works and so access the Internet through it ...

Last edited by afreitascs; 11-19-2010 at 09:45 PM.
 
Old 11-19-2010, 09:52 PM   #147
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,658
Blog Entries: 3

Rep: Reputation: 224Reputation: 224Reputation: 224
Quote:
So far everything is working fine. I do the updates to follow UPGRATE.TXT, literally
last night on my multi lib 4.5.3 kde I read alien bob reminded me of the aaa_elf and it went ok.
 
Old 11-19-2010, 10:14 PM   #148
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Originally Posted by rfernandez View Post
That solved my problem with bluetooth usage. But I also noticed that Bluez-4.78 did not initialize my bluetooth module right; everytime I had to "hciconfig hci0 reset" so I could use it. On the bluez.org site

upgrading to bluez-4.79 solved my bluetooth initialization.
Yeah confirmed here thanks, we were looking into the issue when I spotted this.

Should be included in the next batch.
 
Old 11-19-2010, 10:53 PM   #149
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,945

Rep: Reputation: Disabled
Quote:
Originally Posted by rfernandez View Post
That solved my problem with bluetooth usage. But I also noticed that Bluez-4.78 did not initialize my bluetooth module right; everytime I had to "hciconfig hci0 reset" so I could use it. On the bluez.org site

upgrading to bluez-4.79 solved my bluetooth initialization.
As the hobgoblin said, thanks for the heads-up on that - I somehow didn't notice the new version of bluez being out.
 
Old 11-19-2010, 11:25 PM   #150
rfernandez
Member
 
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264

Rep: Reputation: 40
Thank you, guys. Already got the latest update on both udev and bluez and everything is in deep harmony. :-)
 
  


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 09:09 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