Salix Forums

Wasn't sure where to put this so I dropped it here. Maybe need to add a forum for “Current”.
Anyway, I successfully upgrade both my laptop (Salix 32) and desktop (Salix 64) to current (13.1) yesterday following the , as usual, excellent wiki instructions (http://www.salixos.org/wiki/index.php/H ... .0_to_13.1). I had no problems at all with the upgrade to the laptop once thenktor, via jabber, reminded me to do a dotnew. I always forget dotnew. I was going to add “do a dotnew” to the wiki instruction but was not really sure where the appropriate place for it.

As for the desktop, I had two problems (not counting the the dotnew one), but they were due to my particular setup. The first is that I am using grub2 for the boot loader on the desktop and the kernel upgrade instructions (http://rlworkman.net/howtos/libata-switchover) assume the lilo boot loader. After fumbling around with this, I finally found how to append grub2 and got it to boot.
The second issue was that nVidia proprietary driver would not build on the 2.6.33 kernel and needed to be patched. For me this (http://www.nvnews.net/vbulletin/showpos ... stcount=20) worked , but I had to blacklist the nouveau module module first. I edited /etc/modprobe/d/blacklist.conf adding “blacklist nouveau” and rebooted before patching and running the nVidia installer.

Regards
Rich

Here the noveau module crashes splashy:
As soon as it gets loaded my TFT switches off with "no signal" message, it needs some seconds to come back and then splashy has crashed because the resolution has changed to 1920x1200 with KMS. No idea how to handle this on the iso.
Of course blacklisting noveau solves the problem.

thenktor wrote:Here the noveau module crashes splashy:
As soon as it gets loaded my TFT switches off with "no signal" message, it needs some seconds to come back

Yes, I saw this also.

Splashy should probably need to be recompiled with a support for KMS. And if he hasn't, need to be patched.

Interresting link on ArchLinux about the subject :
http://wiki.archlinux.org/index.php/Spl ... de_Setting

Another small issue on my Salix 64 current installation. The network was not coming up on boot up. I had to go in to Wicd Network Manager and click on the "Connect" button. I finally noticed that the "Use as default profile" wasn't checked. Once I checked this box, the network now always starts on boot up .

Rich
ps. I use dhcp.

I didn't have any troubles doing it that way :
http://fredgnix.blogspot.com/2010/03/sa ... rrent.html

It's in french but the differents steps (1/ 2/ ...) are easy to understand.

++

fredg wrote:I didn't have any troubles doing it that way :
http://fredgnix.blogspot.com/2010/03/sa ... rrent.html

It's in french but the differents steps (1/ 2/ ...) are easy to understand.

slapt-get -i glibc-solibs pkgtools sed
This will install the slow Slackware package tools. Do not install them! Only update the spkg-pkgtools.