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.
let me rephrase, that cqhci driver wasn't included until slackware64-current was installed.
neither was the intel_xhci_usb_role_switch driver. My guess it was those two missing drivers causing the issue originally.
Last edited by colorpurple21859; 07-07-2020 at 08:37 PM.
So what we learn from this? The installer could access the MMC disk both in 14.2 and current. I think it's because udevd in the installer was able to automatically load all the necessary modules. But udevd could not do the same in the installed system, because the modules were not there in the initrd image, because mkinitrd_command_generator.sh did not list them. The answer would be to automatically copy all those modules into the /boot/initrd-tree/lib/modules which are listed in the lsmod output in the installer. Those need not be modprobed manually in /boot/initrd-tree/load_kernel_modules, I guess, though, but udevd would load them if needed.
Last edited by Petri Kaukasoina; 07-07-2020 at 02:43 PM.
Well, the only thing that's lacking is giving you both a lot of thanks. At last I have slackware on my laptop. I bought another one, an HP, with slackware on it and mechanical hard disk. I bought it because I was unhappy with only 32G in the "hard disk" (it has a 1TB hard disk). But it has numerical keypad which makes it bulky (too wide). Instead this Acer not only is less wide having no numerical keypad (which I never use) but the keyboard is American. The HP has a Spanish keyboard with a lot of keys. For instance the slash is above the 7 (seven). The most widely used key in the most uncomfortable position! And it has a powerful loudspeaker, so the bell character is clearly heard.
I'll never be able to thank you enough, guys. Good bye and best wishes.
No it won't work on a standard install, did a check in a vm neither one of those drivers are in the 14.2 kernels.
You are sure it can't be done with 14.2? Once I know what the drivers are, why not make an initrd.gz that contains them and boot with the generic, as I am presently doing?
I run alsamixer and it only has the master control. I move it to 100%. Now I play a movie with mplayer. And there is no sound! How could I begin to solve this problem? Perhaps this should go in a new thread?
EDIT: perhaps the other controls are muted. If I could make alsamixer to display them I could know. Why does alsamixer show the master control only?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.