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.
Yeah and if you have trouble with the script just manually install from live session using cp command and then setup boot and etc manually (grub.cfg or etc/lilo.conf, fstab etc you know.
Whenever I'm remastering I usually just manually copy distro to folder or drive then set it up to boot.
Like right now Im manually remastering a Debian Live LXDE iso to make it smaller, pretty hard on Debian though...
It does not include the xfce live iso. From that same page (there's a lot of info, so I had to search for it):
Quote:
if the Live system contains a huge kernel (all ISO variants except XFCE) then the “setup2hd” script and the Slackware installer files are copied to “/usr/local/sbin” and “/usr/share/liveslak” respectively,
It does not include the xfce live iso. From that same page (there's a lot of info, so I had to search for it):
EDIT: Thanks bass, but I think we might be talking at cross-purposes - I think you were talking about the script, I was talking about Xfce being in the 3.4GB iso. My fault for not being specific.
As far as I can tell, the Xfce DE is included in the larger iso, but I will check tonight. I also have to run tests on the suspend function and see if I can get audio working.
Last edited by Lysander666; 02-20-2019 at 09:40 AM.
Been reading this thread. For personal learning for me. I am not trying to change any bodies mind here.
I run a 16 gig ssd Acer C710 with this install on here for about a year. Only thing I had to tweak was the touchpad config for copy and paste in browser while using 2 finger tap.
I am not sure Slackware current has same configs and library locations as I do on AntiX. So no two finger problem on touchpad may appear in Slackware Current. Talking about 2 different chromebooks also.
Good luck with this. I went with John Lewis Bios on my chromebook for usb boot back then.
I have books, movies, comics, changes, additions going on since Feb 2018 on this chromebook.
I don't run desktop environment n this chromebook. Just Window managers.
My other chromebook just like this one. But with broken write protect section on the eprom.
I run Ubuntu latest LTS xfce crouton on it instead because of broken write protection.
I have a earlier backup kernel image and header in case the 4.20 goes south on me for what ever reason in grub menu.
Like I said. Not trying to change anyone's mind here. Just supplying info. I am a member of Salix forums also and have installed it on single core atom n270 touch screen netbooks with 2 gig of ram in them. 30 gig toshiba ata spinning hardrive.
Have installed and ran Slackel Linux from time to time also. But like you said. Salix and and Slackel are not based on current Slackware.
Reason I tried and used Salix and Slackel. Curiosity and was wondering about touchscreen working with them. No problem on these passive touch screens.
I had to do something with these chromebooks I had when EOL kicked on Google ChromeOS on these older chromebooks. Kinda like they wish we had Bic lighters. Instead of turning them into Zippos.
Which after typing that out. I wonder. Does ChromeOS lock out newer versions that not EOL where you download and one can make a recovery usb with a non EOL ChromeOS iso.
See if it is blocked being installed on a older EOL chrome book.
Sounds like Idea for another experiment.
Looking at neverware.
Hmmmm https://distrowatch.com/table.php?di...ion=cloudready
Built by neverware using ChromeOS.
But I bet recovery usb is not possible with this.
Just a conventional Linux iso install.
Been reading this thread. For personal learning for me. I am not trying to change any bodies mind here.
I run a 16 gig ssd Acer C710 with this install on here for about a year. Only thing I had to tweak was the touchpad config for copy and paste in browser while using 2 finger tap.
I am not sure Slackware current has same configs and library locations as I do on AntiX. So no two finger problem on touchpad may appear in Slackware Current. Talking about 2 different chromebooks also.
What did you do to tweak your touchpad? The issue you are describing is similar to mine - I get no menu when I 'right-click', though 'right-click' works perfectly under Ubuntu.
My experiments tonight were not that successful. Suspend worked but on resume it asked me to re-enter my wifi password, which was rather annoying.
Audio did not work either, I tried the fix I used in the OP, but on trying to kill the pulse audio daemon I was told there was "no such process", so I couldn't start it either. Audio did not work after the other steps regardless.
And though the setup2hd script worked, one has to get into the actuall install of things before selecting a DE, I imagine [since it insists on selecting a partition and writing to it before getting any further], and I wasn't going to risk the install I have for that without knowing.
Unless Eric or someone can actually confirm that the 3.4GB iso includes Xfce, I won't be progressing much with an install since Ubuntu works so well on this machine.
EDIT: I tried Devuan as well, which was shameful. It managed to load the gfx drivers for the screen [more than 4.4.14 can do] but the touchpad and the keyboard were mostly non-functional [i.e. I couldn't click on anything with the touchpad, neither did return work for most things I selected via the keyboard].
Last edited by Lysander666; 02-20-2019 at 04:13 PM.
Im downloading it and will check for you lysander666
Quote:
Originally Posted by bassmadrigal
That is a "full" Slackware install and will contain only the programs found on a regular Slackware install.
Thanks to both of you. Interested to see what you find out, linus.
I tried Debian as well last night which was the worst yet for getting things to work - I had even less functionality in the touchpad and keyboard and the only way to get out was to do a hard shutdown. But that's my fault seeing as I forgot I should only be working with kernel 4.15 onwards.
That means Vector is out the running as well. So thus far, Ubuntu is the top contender, Slackware is still a possibly, with MX as another outsider.
The biggest issue with Slackware -current is the audio and that might be a big issue. If I can't get the audio to work, this install isn't going to happen. The Chromebook uses the audio processor chtmax98090 and there is absolutely zero on the internet about chtmax98090 and Slackware. Using plbossart’s Alsa Use Case Manager configuration didn't work, but I've opened an issue on Github to see if the dev has any idea how to get it working.
Last edited by Lysander666; 02-21-2019 at 03:40 AM.
Lysander666 the answer is YES the slackware current dvd live iso does have xfce as you can see in screenshot, it also includes kde and basically everything in a slackware install dvd
Lysander666 the answer is YES the slackware current dvd live iso does have xfce as you can see in screenshot, it also includes kde and basically everything in a slackware install dvd
I see it - thank you so much, linus. My sincere thanks for confirming. So things are one step further.
If I can sort out the audio issue that will be the next line crossed but that's currently up in the air.
Last edited by Lysander666; 02-21-2019 at 04:01 AM.
The second link I tried, the first I haven't. Also, looking at Slackdocs, it says that the linux-samus kernel must be compiled and used, however, it also says
Quote:
There is an all-in-one sound.sh script that should be run initially. Additionally, on every reboot, you will likely need to re-run the following to re-enable sound:
Code:
$ cd linux-samus/scripts/setup/sound
$ ALSA_CONFIG_UCM=ucm/ alsaucm -c bdw-rt5677 set _verb HiFi
Which is a pain, but that could be a script in rc.local. However, the Slackdocs article is for Pixelbooks and is three years old now. Additionally, the linux-samus page now says
As of v4.9 there is no need to patch the kernel sources to get sound support.
Current kernel version: v4.16.13
The Arch page gives a slightly different method of using erdnaxe's excellent solution:
Code:
# git clone https://github.com/plbossart/UCM.git
# cd UCM
# cp -r chtmax98090/ /usr/share/alsa/ucm/
# alsaucm -c chtmax98090 set _verb HiFi set _enadev Speakers (or)
# alsaucm -c chtmax98090 set _verb HiFi set _enadev Headphone
# alsactl store
I can test this out and see what happens.
Last edited by Lysander666; 02-21-2019 at 04:34 AM.
Scroll down to touchpad edits in that thread and how I mention 3 fingers to get a menu seems to be the default instead of 2.
Edit: over here
Quote:
Did some touchpad editing after helping another chromebook user on MX forums on his AntiX install. Helping him helped me. Just changing 3 finger right click to 2 finger right click. When you 1st install AntiX . The touchpad default after install is 3 fingers for right click copy and paste.
2nd edit: Use the MX forum link I supplied in that thread for any clarification.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.