SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I managed to make an upgrade to the latest current 32-bit packages using my Lenovo X60s machine.
However, some obstacles came into my way:
- mkinitrd didn't work for me (failed to make /boot/initrd.gz), the previous version of it I happily used instead (from 13.0) did the job properly, so I could reboot and got new kernel working,
- pppd is asking for libpcap.so.1 and does not initiate net connection,
- Xorg with KDE gives me a video that seems to be out of sync.
KDE itself looks like probably working - but I only see a pointer on the grey background that reacts properly to mouse motion and nothing more.
Clicking on the left bottom corner gives me a flickering resemblance of KDE menu.
To fix the KDE problem rename /etc/X11/xorg.conf-vesa to xorg.conf and restart X. If like me you run an Nvidia card you will have to patch the driver or grab the beta version. Unfortunately I haven't got them working yet, invalid module format.
To fix the KDE problem rename /etc/X11/xorg.conf-vesa to xorg.conf and restart X. If like me you run an Nvidia card you will have to patch the driver or grab the beta version. Unfortunately I haven't got them working yet, invalid module format.
Haven't tried mkinitrd yet and don't use pppd.
samac
I have an Intel 945gm graphics onboard.
Looking at /var/log/Xorg.0.log file I see an "(EE)" error saying that "fbdev" module failed to load.
I used xorg.conf-vesa as you suggested and it worked but that's not the most elegant solution, I suppose.
In case of pppd I used a version from Slack 13.0 disc and it works :-)
I have a feeling some people will realize after these updates that they really should stick with the stable release ...but then again..most slack aficianados are an adventurous bunch.
Installing slackware-current is my little way of helping and supporting slackware
Being new to slackware and linux in general, I've been wondering: Is there a proper way to test slackware current? I mean does running current and sharing on the forums provide any benefit beyond me and those people on the forums or is there a defined method for feedback (not that I have really found anything that didn't work or couldn't be made to work)?
You can report them on the forums here where others can confirm/deny/help fix them. AlienBOB, Robby Workman, PiterPunk and myself keep a pretty close eye on reports here.
You could jump into one of the Slackware Channels on IRC and discuss it there.
Alternatively, if you are pretty confident that you have a real bug and it hasn't been discussed/reported here already then you can email Patrick directly.
Do be aware that he is a very busy man and having 500 people email him to tell him that the same bug exists already is probably not an efficient use of his time =)
Thanks for the response and all y'all do. One of the (many) things I've come to appreciate about Slack is the regular contact with the devs/contributors. It's reassuring and impressive that (what I understand to be) such a small team of people not only find the time to build a great OS but interact with the users as well.
Looking at /var/log/Xorg.0.log file I see an "(EE)" error saying that "fbdev" module failed to load.
I used xorg.conf-vesa as you suggested and it worked but that's not the most elegant solution, I suppose.
In case of pppd I used a version from Slack 13.0 disc and it works :-)
Thanks for Xorg idea
The latest intel driver works only with kms. You have to put modeset=1 for i915 options. Just create a file named i915 in /etc/modprobe.d with "options i915 modeset=1" in it.
slackpkg.conf error after upgrade all from stable to current.
(didnt use the new kernel )(luks/lwm setup)
bash-4.1# uname -a
Linux slack 2.6.29.6-smp #1 SMP Mon Aug 17 00:18:05 CDT 2009 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
bash-4.1#
bash-4.1# slackpkg update
expr: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
Your slackpkg.conf is outdated. Please, edit it using slackpkg.conf.new
as example or overwrite it with slackpkg.conf.new.
You can use 'slackpkg new-config' to do that.
bash-4.1# slackpkg new-config
expr: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
Searching for NEW configuration files
No .new files found
There were some additions today that should resolve that issue.
You'll need to install this manually though.
a/coreutils-8.4-i486-2.txz: Rebuilt.
Use --without-gmp, at least for now. We don't want utilities in /bin
requiring a library in /usr/lib{,64} that may not be available.
l/libpng-1.4.1-i486-2.txz: Rebuilt.
Now with less rat.
To fix the KDE problem rename /etc/X11/xorg.conf-vesa to xorg.conf and restart X. If like me you run an Nvidia card you will have to patch the driver or grab the beta version. Unfortunately I haven't got them working yet, invalid module format.
samac
I'm in the same boat after update-all...just rebooted and pffft...is the patch in /patches?...is the beta at xorg? nvidia?
cheers
slackpkg.conf error after upgrade all from stable to current.
(didnt use the new kernel )(luks/lwm setup)
bash-4.1# uname -a
Linux slack 2.6.29.6-smp #1 SMP Mon Aug 17 00:18:05 CDT 2009 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
bash-4.1#
bash-4.1# slackpkg update
expr: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
Your slackpkg.conf is outdated. Please, edit it using slackpkg.conf.new
as example or overwrite it with slackpkg.conf.new.
You can use 'slackpkg new-config' to do that.
bash-4.1# slackpkg new-config
expr: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
Searching for NEW configuration files
No .new files found
I encountered that problem too, installpkg, upgradepkg, removepkg, slackpkg does not work. What I did was symlink that libgmp.so.10 to the old lib and restarted the upgrade.
However, it is better to download the gmp.***.txz and extract it and install it. As what the other thread suggested.
There were some additions today that should resolve that issue.
You'll need to install this manually though.
a/coreutils-8.4-i486-2.txz: Rebuilt.
Use --without-gmp, at least for now. We don't want utilities in /bin
requiring a library in /usr/lib{,64} that may not be available.
l/libpng-1.4.1-i486-2.txz: Rebuilt.
Now with less rat.
Thanks i grabbed it from the states,sweden doesnt have it yet.
/solved
and I had to re-compile the kernel modules like this
Quote:
i can confirm, cp /boot/config-huge-2.6.33 /usr/src/linux-2.6.33/.config && cd /usr/src/linux-2.6.33 && make && make modules_install && cp arch/x86_64/boot/bzImage /boot/vmlinuz && lilo && echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf && telinit 6 will allow the patched 190.53 nvidia drivers to work
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.