Installed The Latest Changes to Current and......

kenjiro · 11-19-2010, 07:46 AM

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?

rworkman · 11-19-2010, 08:39 AM

Quote:

Originally Posted by rmjohnso

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.

rmjohnso · 11-19-2010, 08:40 AM

Quote:

Originally Posted by GazL

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?

akiku · 11-19-2010, 08:53 AM

Quote:

Originally Posted by BobNutfield

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.

GazL · 11-19-2010, 09:02 AM

Quote:

Originally Posted by rworkman

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!

hitest · 11-19-2010, 09:27 AM

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.

rworkman · 11-19-2010, 11:08 AM

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"

rmjohnso · 11-19-2010, 02:17 PM

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]

rfernandez · 11-19-2010, 06:59 PM

Quote:

Originally Posted by rworkman

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.

Drakeo · 11-19-2010, 08:43 PM

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.

afreitascs · 11-19-2010, 08:44 PM

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 ...

Drakeo · 11-19-2010, 08:52 PM

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.

mRgOBLIN · 11-19-2010, 09:14 PM

Quote:

Originally Posted by rfernandez

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.

rworkman · 11-19-2010, 09:53 PM

Quote:

Originally Posted by rfernandez

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.

rfernandez · 11-19-2010, 10:25 PM

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