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 tried to update from Slackware 13.1 to 13.37 current (Kernel 3.1.13) a laptop ThinkPad T60 but, even if the release 13.1 operates with full satisfaction, when the release 13.37 is launched there is a crash with a stop and the display becames totally black.
I think the problem relates to udev because, if I make /etc/rc.d/rc.udev not executable the problem does not present, but obviously many services don't operate.
How the problem can be overcame?
A difficult it is that udev starts before syslog, so there isn't any trace of the crash in dmesg and in syslog.
i'm not sure whether an upgrade from 13.1 to current is possible without causing any troubles,
neither am i sure if this will help, but could you try to boot with the
Code:
nomodeset
option.
at least the "screen blanks after udev starts" looks like a kms-issue.
An upgrade using slackpkg is only supported from one release to the next. Skipping a release will cause you to miss all the new packages from the release you skipped, as well you're stuck with all the packages which were removed from the release you skipped.
That as a minimum. There can be other things you have to do to your configuration - the best place to check that is the CHANGES_AND_HINTS.TXT for the release you upgraded to as well as for the release you skipped.
If you upgraded manually, then these CHANGES_AND_HINTS.TXT files will be invaluable anyway because they list the packages that were added and removed.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
I use ThinkPad T60 with Slackware 13.37. I did the installation of the system on ThinkPad X60s and then I cloned it on ThinkPads T40 and T60. The only change I was forced to made in /etc/udev/ directory was to reset NAME="wlan1" and NAME="eth1" in 70-persistent-net.rules file to NAME="wlan0" and NAME="eth0" because of the following error:
Code:
SIOCSIFBRDADDR: No such device
I never tried to upgrade Slackware -- I always do the full installation of the new version.
***
The only problem concerning video on ThinkPad T60 I encountered so far were color artifacts that appear in a specific situations. I solved that putting to /etc/X11/xorg.conf.d/ directory the file 20-radeon.conf:
i'm not sure whether an upgrade from 13.1 to current is possible without causing any troubles,
neither am i sure if this will help, but could you try to boot with the
Code:
nomodeset
option.
at least the "screen blanks after udev starts" looks like a kms-issue.
Your advice was very good and I solved my problem with satisfaction.
Thank you and best regards
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.