Things That Won't Run in -Current (21 April 2015).
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.
@Poprocks,
I've had a similar problem since the 21 April updates.
It doesn't matter if the media is in an external drive or in one of the 3 CD/DVD drives in this box, some are read and some are not. In one case the CD is seen, but the only option is to copy it, that is, I can't view the contents with a file manager.
And, as said before, the same CD/DVDs I've had trouble with in Slackware64 since 21 April, read perfectly, using the same hardware, when viewed via winXp or PC-BSD.
Interesting. I haven't had problems with CD/DVDs as yet, but I haven't tried much.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Quote:
Originally Posted by ReaperX7
No problems here. Did you remove any packages cwizardone?
No, and in an effort to accommodate PC-BSD's recent requirement that you use their "customized" version of GRUB, I've done several complete, from scratch, installations in recent weeks. The result, as far as the CD/DVD problem and Slackware64-current, hasn't changed.
As to PC-BSD, being forced to use GRUB is a deal breaker and I've gone back to PC-BSD-10.0.1, which gives you the option to use your own boot manager (in my case, LILO) and not install their boot manager (GRUB).
I did manage to learn GRUB-2 and successfully used it to dual boot Slackware64 and PC-BSD-10.1.2, but I just don't care for GRUB.
Last edited by cwizardone; 06-14-2015 at 11:57 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
@Poprocks,
.....since the 21 April updates.
It doesn't matter if the media is in an external drive or in one of the 3 CD/DVD drives in this box, some are read and some are not. In one case the CD is seen, but the only option is to copy it, that is, I can't view the contents with a file manager.
And, as said before, the same CD/DVDs I've had trouble with in Slackware64 since 21 April, read perfectly, using the same hardware, when viewed via winXp or PC-BSD.
I was just monkeying around and put one of the CD/DVDs disks I haven't been able to access into one of the drives, manually mounted it, and as user was able to open the disk and browse it with a file manager.
So, to recap, as user I cannot access the CD/DVD, but once manually mounted by root, I, as user, can access it.
What would be the cause and solution?
Thanks.
Seems dhcpcd client not working correctly with my Fritz router.
Revert back to previous one and is OK.
Does the router associate a fixed IP with the PC?
The router probably identifies the PC via its MAC-address and the version string from the dhcp client.
You can set a custom string in /etc/dhcpcd.conf with the vendorclassid option.
Suggestion: make dhclient the default in NetworkManager.conf
Making dhclient the default in NetworkManager.conf will improve Slackware-current "Out-of-the-Box" experience.
Code:
# /etc/NetworkManager/NetworkManager.conf
#
# See NetworkManager.conf(5) for more information on this file
[main]
plugins=keyfile
dhcp=dhclient
[keyfile]
hostname=yourhostname
I find that Networkmanager and dhcpd do not play well together. I've tested mostly on several Atheros wifi chipsets (ath9k) and Realtek gigibit LAN (r8169). For NetworkManager.conf the following does not work: dhcpd=internal : fails to connect dhcp=dhcpd : connect/disconnect loop
When I switched to OpenRC, I found NetworkManager didn't behave itself and dumped it for good ol' dhcpcd. Haven't tried wicd yet with OpenRC, but I might.
When I switched to OpenRC, I found NetworkManager didn't behave itself and dumped it for good ol' dhcpcd. Haven't tried wicd yet with OpenRC, but I might.
Using OpenRC and NetworkManager works fine here. I do need to use dhclient instead of dhcpcd though for it to work.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Is there some issue with cups in -current (2.0.2 and 2.0.3) related to non-SSE2 CPU?
I installed -current from scratch (AlienBob iso) in a new partition and cups didn't start at boot
(with 'cups: unable to start scheduler.' message from rc.cups).
Then I logged in as root and ran 'lpstat' with 'Illegal instruction' as result.
Now I have two -currents in the same machine:
-One is my 'old' -current install (since 14.0) with cups from Slackware 14.1
(1.5.4, with this version I can print, but it seems that I cannot print remotely with Samba).
-And the new partition with -current from scratch.
In my 'old' -current:
I already ran 'slackpkg' to see if there is some package missing.
I already reinstall (upgradepkg --install-new --reinstall) all packages from the -current iso from AlienBob.
I already tried to build cups with sources from -current tree but it fails with this message
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.