The Debian-Stretch-Live Starter Kit

[keniv]

@rcrsn51,
Thank you for this. I have been using Fred's xenial dog and now bionic beaver to run a sdr app called gqrx. I also have ubuntu 16.04 and XP on this machine. XP runs another sdr. Had to use grub2 (I think that's what ubuntu uses). I find it harder to use than grub4dos. Deb stretch live starter kit is up and running. Also using palemoon. As it happens I like it better than FF. Rather than in /live/modules I set it up to load on the fly. Also have gqrx installed and working. Thought it might be a bit faster on this but I'm not sure it is but it's working. Have not come across any problems yet.

Regards,

Ken.

[rcrsn51]

Thanks for testing.

There probably isn't much of a difference in speed. The only real difference is the size of 01-filesystem.squashfs. But it's not being loaded into RAM, so its size shouldn't have any major side effects on the applications that are running.

Fred could comment on this better than I.

[fredx181]

@keniv and @rcrsn51

There probably isn't much of a difference in speed. The only real difference is the size of 01-filesystem.squashfs. But it's not being loaded into RAM, so its size shouldn't have any major side effects on the applications that are running.

Yes, not much, Bionicdog is probably a little more bloated because of more startup processes (and maybe because of (default) systemd boot )

@all, Another subject, for info:
There is deb-mutimedia repository which can be activated by uncommenting it (remove the "#" ) from /etc/apt/sources.list, so becomes this:

Code: Select all

#Debian Multimedia
deb ftp://ftp.deb-multimedia.org/ stretch main non-free 

Then, in terminal:

Code: Select all

apt-get update

EDIT: And install deb-multimedia-keyring:

Code: Select all

apt-get install deb-multimedia-keyring
apt-get update

This repository has more multimedia apps included than the stock Debian repo's , or/and different/newer builds.
For example the vlc package has gtk2 support (more convenient from "Open file"), can be set in Preferences from "Interface settings", see screenshot.

Fred

[keniv]

@fredx181 and @rcrsn51,
As I said in an earlier post this machine is probably not up to the demands that sdr packages put on machines but as I don't have anything better I have to use it. I thought I might save some CPU cycles which might help with the sdr program but this has turned out not to be the case. Thanks for the explanation as to why. However, I still really like these dogs. I have added a few more small debs to this one from Freds repro linked to in the first post. These include firewall-puppy, evince and uextract. Installation went well. I have not tried anything yet that did not work. I like the idea of being able to build a dog to more exactly match my needs. I don't have the skills to do this for myself.

Regards,

Ken.

[dancytron]

I did a manual frugal install. I didn't do much with it, but it seems to work flawlessly.

Great job.

My only comment is to consider adding the quick-remaster. I can't imagine it takes much space and then it would have the built in ability to reproduce itself.

[rcrsn51]

Thanks for testing.

it seems to work flawlessly.

It should. It's just a minimal build of Fred's mklive script with some extra utilities.

My only comment is to consider adding the quick-remaster. I can't imagine it takes much space and then it would have the built in ability to reproduce itself.

I left out remastering because I never do it and I can't provide any help. But people can easily put it back in by getting the packages from Fred's repo.

Then he can be the support person.

Or they can use this ISO to run their own mklive build with their own selection of packages.

-----------------

[rcrsn51]

How to make your own 64bit Google Chrome Browser squashfs module

You will use the repo2sfs tool from Page 1. If you are new to this, do the test-run first.

Now for Chrome - you will need a non-root user:

In the System Tools menu, run Add New User
Create a user named "guest" with password "guest"
Accept the default list of groups.

Download Chrome:

Code: Select all

wget --no-check-cert  https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

Extract the chrome-guest-setup script attached below.

Because you are working with a 3rd-party Debian package, you will run repo2sfs a bit differently:
Start in an empty folder holding the chrome-guest-setup script and the Chrome .deb package.

Open a teminal (F4) and type:

Code: Select all

repo2sfs google-chrome-stable_current_amd64.deb #Hint: use Tab completion

Part-way through, you will get this dialog:

Code: Select all

In the next step, the package will be temporarily removed ...
Press Enter to continue:

Continue the build.

Stop at Pause B for "fix anything in /tmp/repo2sfs".
Open another terminal and run the chrome-guest-setup script.

Finish the build.
Load the module and run Google Chrome from the Internet menu.

[Moat]

You will need the repo2sfs tool attached below. It is a general-purpose script that pulls an app and its dependencies from the Debian repo and converts it into a squash module.

What a fantastic tool this is, sir!! In my personal mklive-stretch/Xfce build/re-master/project, it took this dingbat but three minutes to create perfectly-functioning .sfs's of Audacity and Gimp. The mind reels as to what to build next...

Thanks so much for this - as well as PeasyWiFi, which in my above build has been fast-connecting, trouble-free and solid as a rock (using WiFi only, so far). Wonderful stuff!!

And thanks also to Fred for his incredible mklive-stretch script and re-mastering tools!!

Bob

[backi]

Hi !
Just want to remind .....in Xenial/Debian Dog there is AptToSfs in Accessoire/Module Section which accomplish the same as repo2sfs .I think it is overlooked a lot somehow .
This Tool is one of my favorite Gimmicks .

Nevertheless want.. to thank rcrsn51 for his diligent never ending and creative Work .
Heaps of Tools and Contributions from him to the Community .
Thanks again .....So keep on rocking ...my Friends .

[Moat]

Ahh, yes, backi... I just built a working Stellarium .sfs with AptToSfs! Initially, by it's description I thought it was something a bit different (i.e. - building an .sfs from already installed packages) - but now see that it's functionally nearly the same as repo2sfs.

Both great, great tools!

Bob

[fredx181]

Download Chrome:
Code:
wget https://dl.google.com/linux/direct/goog ... _amd64.deb

Start in an empty folder holding the repo2sfs script and the .deb file. Because you are working with a 3rd-party Debian package, you will run repo2sfs a bit differently:

Hi Bill, in case you don't realize, the google-chrome repository is included in your build of DebLive_Stretch-amd64-52.iso (see /etc/apt/sources.list.d/google-chrome.list), so just apt-get will do:

Code: Select all

apt-get update
apt-get install google-chrome-stable

Fred

[fredx181]

I just built a working Stellarium .sfs with AptToSfs! Initially, by it's description I thought it was something a bit different (i.e. - building an .sfs from already installed packages) - but now see that it's functionally nearly the same as repo2sfs.

Yes, functionality is the same, but works in a different manner, apt2sfs installs the packages in chroot and repo2sfs just simply extracts the packages before making sfs.

BTW, I tried repo2sfs creating .squashfs for gimp, ffmpeg, bleachbit and all work fine.

@backi, you may want to try repo2sfs in Xenialdog, it could be that apt2sfs does too much "configuring", which may result in the problems you talked about earlier (just guessing, should be tested to be sure)

EDIT: To clarify more about apt2sfs and "configuring":
Most Debian packages have "pre" or "post" install scripts that are executed when installing/configuring).
Apt2sfs simulates normal install in a chroot (jail) environment (outside the running system).
Specially with packages that have systemd dependency, then sometimes unexpected things can happen, specially when unloading an SFS (on Xenialdog, which runs with systemd boot enabled).
(I must add that Debian-Stretch-Live Starter Kit runs by default WITHOUT systemd boot, so I expect no problems then with apt2sfs, unless you enable systemd-boot)

Fred

[backi]

deleted

[rcrsn51]

Thanks everyone.

I am certainly aware of apt2sfs - I use it myself.

But I wanted a tool with a little more control over the build process.

[rcrsn51]

How to install Master PDF Editor

Update: Fred has packaged v4.6.31 in DEB form with a complete dependency list and has added it to his repo. You can now build a squashfs module using a vanilla repo2sfs operation.

-----------------------

Go here and get a 32bit or 64bit Debian package.

You have two choices:

1. Do a regular install with Right-click > Install Deb. However, there is a missing dependency.

Code: Select all

apt-get update #if needed
apt-get install libsane

2. Build a squashfs module.

a. Get repo2sfs from page 1.
b. Read the Chrome instructions (page 2) for doing a third-party build. Ignore the non-root stuff.
c. Add "libsane" to the EXTRAS list.
d. Load the module and run it from the Office menu.

Hint: This is a QT app. If your base setup already has the QT libs, you may want to omit them from the squash module.
At Pause A, go into /var/cache/apt/archives and delete their .deb files.

Here is another example: Some apps want ghostscript. But if you already have ghostscript via CUPS, there is no need to include it in the module.

-------------------

[rcrsn51]

WiFi Drivers

The Starter Kit contains the drivers and firmware for many WiFi devices. The Intel internal PCI adapters need firmware. Run:

Code: Select all

apt-get update #if needed
apt-get install firmware-iwlwifi #for newer models
apt-get install firmware-ipw2x00 #for older models

Or download a firmware-iwlwifi squashfs module from here. Put it in the "live" folder of your frugal install.

For the old Broadcom b43 WiFi driver, get a firmware package here.

Update: Linux is moving some of its Realtek rtlwifi drivers into a new group called rtw88. They will require firmware. Get it here.

------------------------

I have a combo package of various third-party Broadcom and Realtek WiFi drivers for k4.19.0-6-amd64. The drivers are:

1. Broadcom wl.
2. Realtek 8192cu/8192eu/8188eu. These are built from github projects and use vendor sources.
They may work better than the in-kernel versions or provide AP-mode to use with Wlanmaker.
3. Realtek 8812au and 8822bu. These AC-mode devices are not yet in the mainstream kernel.
4. Realtek internal PCI 8821ce.
5. Realtek 8811cu/8821cu. (see below)
6. Realtek 8723de.
7. Realtek 8188ftv-fu.

Download the package here. Then use right-click > Install Deb.

Some of these drivers may require a change to the PeasyWiFi config. Set DRIVER=nl80211.

Hint: To compile your own Broadcom WiFi driver, read here (steps 1 and 5).

Update: The D-Link DWA-171 USB WiFi adapter uses the Realtek 8821cu driver.
It is a dual-format device that initially presents itself as a USB flash drive, so Windows can auto-install the driver.
You need to switch it into a WiFi device.

a. Install the combo driver package above.
b. Install the package "usb-modeswitch".

Code: Select all

apt-get update #if needed
apt-get install usb-modeswitch

c. Unplug/replug the adapter.
d. Run the command: iwconfig. It should show a 'wlan0' interface.
e. If not, do a reboot.

------------------

A note about antennas: Although the drivers in the rtl-wifi series are intended for dual-antenna cards, some laptop vendors have cheaped-out and only provided one antenna. So if the driver on your system happens to pick the absent antenna, WiFi will fail. Here is a sample fix:

1. Go to /etc/modprobe.d
2. Create the file "rtl8723be.conf"
3. Insert the line "options rtl8723be ant_sel=1"
4. Do a COLD reboot.

If that doesn't help, try "ant_sel=2".

----------------------

[proebler]

Hi,
I like the concept that allows for a system set up with few applications which just meet my quite basic needs.
So I have tried the Debian-Stretch-Live Starter Kit.
I am having mixed success on different computers with a frugal basic install on an ext2 USB with only the palemoon....squashfs in the ‘modules’ directory.
I rename or delete the ‘changes’ directory when switching computers [so that a new ‘changes’ directory gets created].

Computer 1: Lap top HP Elitebook 8460p, Intel core i5
no problem booting,
peasywifi detecting and connecting to wlan0

Computer 2: Lap top HP Elitebook 6930p, Intel core2
no problem booting,
peasywifi indicates:
Interface wlan0 is NOT active
Kernel module : unknown
I know from running a different system, that the built-in wifi is an Intel Ultimate N WiFi Link 5300 (8086:4236), which uses the iwlwifi driver.

When I plug in a TP-Link wifi dongle [instead of trying to use the built-in wifi], then peasywifi detects it correctly,
kernel module rt73USB is used, and the connection is working.

Computer 3: Lap top HP nc8000, Pentium M, no built-in wifi
no problem booting when using forcepae
peasywifi detecting and connecting via the TP-Link dongle, no problem

Computer 4: Desktop HP P4, 2GB RAM
appears to be booting up ok but at the end fails to connect to the Xserver and stops at the command prompt.

On the screen I see [remaining]:
Server terminated with error (1)
Closing log file
Sending discover .....
Sending discover .....
Sending select for 10.1.1.243
Lease of 10.1.1.243 obtained, lease time 86400
SIOCDELERT: No such process
xinit: giving up
xinit: unable to connect to Xserver: Connection refused
xinit: server error
root@live:~#

See also the attached log file

My questions:
Computer 2: How do I get the built-in wifi to work ?
Computer 4: Is a fix possible for the Xserver problem or do I have to accept that the P4 simply is too old for the task at hand ?

Thanks for any help,
regards
proebler

[rcrsn51]

Thanks for testing.

Computer #2 is probably a firmware problem with the Intel WiFi. Run dmesg and check for errors. Using your USB adapter, run

Code: Select all

apt-get update
apt-get install firmware-iwlwifi

Otherwise, download and install it manually from https://packages.debian.org/stretch/firmware-iwlwifi
The Starter Kit has some older Intel firmware. I was reluctant to include the whole package.

I don't know much about video, but computer #4 is probably a video driver problem. Your log has a reference to "mga" A google search of "debian stretch mga video" finds the package "xserver-xorg-video-mga"

So at the console prompt, try

Code: Select all

apt-get update
apt-get install xserver-xorg-video-mga

Then try "startx" or reboot.

------------------

[proebler]

@rcrsn51
The suggestion has worked for computer 2.
peasywifi now uses wilwifi; auto connect also works when so set.

I applied what was suggested for computer 4.
Instead of ending up at the command prompt, I now get to a blank [black] screen, no prompt.
Not what is wanted, but I guess it is one step closer to a working screen.
Alt+Ctrl+Del does what it is supposed to do.

I attach the new Xorg.0.log file [Xorg.0.log_stretch-live.gz] together with the corresponding log file from booting radky's Dpup Stretch 7.5 CE (RC-2), which DOES boot to a working screen on computer 4.
Thanks for helping.
proebler

[rcrsn51]

Line 471 of Dpup-Stretch loads swrast. The Starter Kit does not have it. So it may have something to do with accelerated video.

Code: Select all

apt-get install libgl1-mesa-dri
startx

If that fails, run dmesg from the console. Maybe there are some hints.