Create Debian 9 (Stretch) minimal ISO similar to DebianDog
For people who are still having problems with Mozilla browsers and certain streaming content (like mp4/h.264), here is a solution.
a. Install the package libavcodec57 from the Debian repo.
b. Or convert it to a squashfs module and load it as needed.
a. Install the package libavcodec57 from the Debian repo.
b. Or convert it to a squashfs module and load it as needed.
Last edited by rcrsn51 on Thu 12 Dec 2019, 12:01, edited 2 times in total.
They might also try libavcodec-extra57.rcrsn51 wrote:For people who are still having problems with Mozilla browsers and certain YouTube content, here is a solution.
a. Install the package libavcodec57 from the Debian repo.
b. Or convert it to a squashfs module and load it as needed.
This package[libavcodec-extra57] replaces the libavcodec57 package and contains the following additional codecs:
* OpenCORE Adaptive Multi-Rate (AMR) Narrow-Band (Encoder/Decoder)
* OpenCORE Adaptive Multi-Rate (AMR) Wide-Band (Decoder)
* Android VisualOn Adaptive Multi-Rate (AMR) Wide-Band (Encoder)
I have posted here a k4.19.0-6-amd64 driver for the Realtek rtl8821ce PCI WiFi card. This driver is not yet in the mainstream kernel.
NOTE: 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.
1. Run the "lsmod" command to find the exact name of your driver.
2. Go to /etc/modprobe.d
3. Create a file like "rtl8723be.conf" that matches the driver name.
4. Insert the line "options rtl8723be ant_sel=1"
5. Do a COLD reboot.
If that doesn't help, try "ant_sel=2".
NOTE: 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.
1. Run the "lsmod" command to find the exact name of your driver.
2. Go to /etc/modprobe.d
3. Create a file like "rtl8723be.conf" that matches the driver name.
4. Insert the line "options rtl8723be ant_sel=1"
5. Do a COLD reboot.
If that doesn't help, try "ant_sel=2".
*** Updated mklive-stretch ***
Download (and make executable) then run 'mklive-stretch' script , from terminal e.g,
From partition (Linux filesystem formatted, e.g. ext3 or ext4) with at least 3GB free space.
This script can be used best from a 'Dog' based OS, see below for running from a Puppy OS (appimages, dependencies are included).
Changes and fixes:
Fixed that the script ended with failure because kernel 4.9.0-9 not found (removed from Debian repo) Major change is that the kernel (at this time 4.9.0-11) is pre-built in the form of a .squashfs module, vmlinuz1, initrd.img and initrd1.xz.
These files are now downloaded by the script and added to the 'live' folder (instead of installing the kernel by apt-get in chroot)
Appimages. For use on most modern Puppies (dependencies included), make executable before running:
32-bit appimage: mklive-stretch32
64-bit appimage: mklive-stretch64
Run e.g.:
From partition (Linux filesystem formatted, e.g. ext3 or ext4) with at least 3GB free space.
Also updated: upgrade-kernel (v2.0.1) for to upgrade the kernel to v4.9.0-11, install with synaptic or from terminal using apt:
Another way to upgrade the kernel (to v4.9.0-11) is to download one of these archives and extract in the 'live' directory, replacing vmlinuz1, initrd.img and initrd1.xz
https://debiandog.github.io/MakeLive/ke ... pae.tar.gz
https://debiandog.github.io/MakeLive/ke ... d64.tar.gz
Or the kernel from stretch-backports (v4.19):
https://debiandog.github.io/MakeLive/ke ... pae.tar.gz
https://debiandog.github.io/MakeLive/ke ... d64.tar.gz
Fred
Download (and make executable) then run 'mklive-stretch' script , from terminal e.g,
Code: Select all
./mklive-stretch -gui
This script can be used best from a 'Dog' based OS, see below for running from a Puppy OS (appimages, dependencies are included).
Changes and fixes:
Fixed that the script ended with failure because kernel 4.9.0-9 not found (removed from Debian repo) Major change is that the kernel (at this time 4.9.0-11) is pre-built in the form of a .squashfs module, vmlinuz1, initrd.img and initrd1.xz.
These files are now downloaded by the script and added to the 'live' folder (instead of installing the kernel by apt-get in chroot)
Appimages. For use on most modern Puppies (dependencies included), make executable before running:
32-bit appimage: mklive-stretch32
64-bit appimage: mklive-stretch64
Run e.g.:
Code: Select all
./mklive-stretch32 -gui
Also updated: upgrade-kernel (v2.0.1) for to upgrade the kernel to v4.9.0-11, install with synaptic or from terminal using apt:
Code: Select all
apt update
apt install upgrade-kernel
https://debiandog.github.io/MakeLive/ke ... pae.tar.gz
https://debiandog.github.io/MakeLive/ke ... d64.tar.gz
Or the kernel from stretch-backports (v4.19):
https://debiandog.github.io/MakeLive/ke ... pae.tar.gz
https://debiandog.github.io/MakeLive/ke ... d64.tar.gz
Fred
How to build a squashfs module for Cinelerra
This will be a repo2sfs third-party build. Note:
a. Start in a clean setup so you get all the dependencies. There are many.
b. Cinelerra wants mesa accelerated graphics. Install or load it separately.
c. It also appears to want PulseAudio, but I had sound working without it.
1. Go here and get the .deb package.
2. The Control file in this package does NOT specify the dependent libs, so you will get them via the Extra line.
3. Run: repo2sfs cin_5.1.debian9-20190930_amd64.deb
4. Use this list of Extras:
5. After building and activating the module, test it from the command line with: cin
This will be a repo2sfs third-party build. Note:
a. Start in a clean setup so you get all the dependencies. There are many.
b. Cinelerra wants mesa accelerated graphics. Install or load it separately.
c. It also appears to want PulseAudio, but I had sound working without it.
1. Go here and get the .deb package.
2. The Control file in this package does NOT specify the dependent libs, so you will get them via the Extra line.
3. Run: repo2sfs cin_5.1.debian9-20190930_amd64.deb
4. Use this list of Extras:
Code: Select all
libtheora0 libvorbis0a libvorbisfile3 libfftw3-3 libflac8 libsndfile1 libvdpau1 libva1 libva-x11-1 libva-drm1 libglu1-mesa
How to make a squashfs module of the Calibre ebook manager v4.1.0
1a. Go to the Calibre website and download a .txz package. Look under "Manual binary install".
1b. Extract the package into a temporary folder named "Calibre".
2a. Download and rename the attached .deb package. It contains a .desktop file for Calibre.
2b. It will also add two missing dependencies to the build: libxkbcommon-x11-0 and libnss3.
3. This setup runs Calibre as a non-root user. Under Menu > System, create the user "guest".
4. Do a repo2sfs third-party build: repo2sfs calibre-desktop_1.1_all.deb
5. At Pause B, go to /tmp/repo2sfs. Open the opt folder. Drop in the Calibre folder from Step 1.
6. Finish the build. Look for Calibre in the Accessories menu.
7. Calibre appears to use mesa accelerated graphics, but will run without it.
Troubleshooting: From the command line, run: calibre-guest
---------------------
1a. Go to the Calibre website and download a .txz package. Look under "Manual binary install".
1b. Extract the package into a temporary folder named "Calibre".
2a. Download and rename the attached .deb package. It contains a .desktop file for Calibre.
2b. It will also add two missing dependencies to the build: libxkbcommon-x11-0 and libnss3.
3. This setup runs Calibre as a non-root user. Under Menu > System, create the user "guest".
4. Do a repo2sfs third-party build: repo2sfs calibre-desktop_1.1_all.deb
5. At Pause B, go to /tmp/repo2sfs. Open the opt folder. Drop in the Calibre folder from Step 1.
6. Finish the build. Look for Calibre in the Accessories menu.
7. Calibre appears to use mesa accelerated graphics, but will run without it.
Troubleshooting: From the command line, run: calibre-guest
---------------------
- Attachments
-
- calibre-desktop_1.1_all.deb.gz
- Remove the fake .gz extension
- (1.04 KiB) Downloaded 168 times
I suspect that the problem with the stock initrd on some machines is related to the presence of USB3 hardware, even if you are booting off a USB2 flash drive in a USB2 port. When you put the Porteus boot in debug mode and run "blkid", the USB boot device is not even detected.
I have a machine where you can turn off USB3 support in the BIOS. When USB3 is off, I can boot with the stock initrd. When USB3 is on, I cannot.
My alternate versions (made with mk-initrd) fix this by making the USB devices visible (I don't know why). Unfortunately, they are unable to detect emmc drives. So if you are putting an install onto the emmc drive, you have to boot it with the stock initrd.
Strangely, the live-boot method never has this problem. But setting up persistence with live-boot is more complicated than with Porteus.
I currently have four newish machines with the problem. But I have one machine with USB3 that is OK with the stock initrd.
I have built the alternate initrd on several machines. The resulting files have different sizes, but they can all detect USB when there's a problem.
I have a machine where you can turn off USB3 support in the BIOS. When USB3 is off, I can boot with the stock initrd. When USB3 is on, I cannot.
My alternate versions (made with mk-initrd) fix this by making the USB devices visible (I don't know why). Unfortunately, they are unable to detect emmc drives. So if you are putting an install onto the emmc drive, you have to boot it with the stock initrd.
Strangely, the live-boot method never has this problem. But setting up persistence with live-boot is more complicated than with Porteus.
I currently have four newish machines with the problem. But I have one machine with USB3 that is OK with the stock initrd.
I have built the alternate initrd on several machines. The resulting files have different sizes, but they can all detect USB when there's a problem.
Here's new mk-initrd package:
https://fredx181.github.io/StretchDog/N ... .2_all.deb
Created initrd1.xz should boot in more cases.
EDIT: also it supports having changes on a f2fs partition (booting from it doesn't work since most bootloaders have no support for f2fs AFAIK), to create a f2fs partition, the package "f2fs-tools" needs to be installed, then it can be created/formatted with e.g gparted)
Also here's kernel 5.2 from buster-backports (added aufs), extract in the 'live' folder (should overwrite existing vmlinuz1, initrd.img, initrd1.xz), works for me in Beowulf(Devuan) and in Stretch too.
EDIT: initrd1.xz and initrd.img created with above mk-initrd
32-bit https://github.com/DebianDog/DevuanDog/ ... pae.tar.gz
64-bit https://github.com/DebianDog/DevuanDog/ ... d64.tar.gz
@Bill, thanks for the info, creating initrd1.xz with the new mk-initrd could make it work in both cases (booting from USB3 and emmc drive) because it combines the two (larger 'stock' initrd1.xz and more modules loaded from linuxrc script (as in the alternative) but I'm not sure.
Fred
https://fredx181.github.io/StretchDog/N ... .2_all.deb
Created initrd1.xz should boot in more cases.
EDIT: also it supports having changes on a f2fs partition (booting from it doesn't work since most bootloaders have no support for f2fs AFAIK), to create a f2fs partition, the package "f2fs-tools" needs to be installed, then it can be created/formatted with e.g gparted)
Also here's kernel 5.2 from buster-backports (added aufs), extract in the 'live' folder (should overwrite existing vmlinuz1, initrd.img, initrd1.xz), works for me in Beowulf(Devuan) and in Stretch too.
EDIT: initrd1.xz and initrd.img created with above mk-initrd
32-bit https://github.com/DebianDog/DevuanDog/ ... pae.tar.gz
64-bit https://github.com/DebianDog/DevuanDog/ ... d64.tar.gz
@Bill, thanks for the info, creating initrd1.xz with the new mk-initrd could make it work in both cases (booting from USB3 and emmc drive) because it combines the two (larger 'stock' initrd1.xz and more modules loaded from linuxrc script (as in the alternative) but I'm not sure.
Fred
mx linux sysVinit remains the default init system
MX-19 Beta 2.1 available for testing
September 8, 2019September 8, 2019
<https://mxlinux.org/blog/mx-19-beta-2-1 ... r-testing/> by
dolphin_oracle <https://mxlinux.org/author/dolphin_oracle/>
MX-19 Beta 2.1 available for testing
Updated iso images
–direct download:
https://sourceforge.net/projects/mx-lin … ing/MX-19/
<https://sourceforge.net/projects/mx-lin ... ing/MX-19/>
We are pleased to offer MX-19 Beta 2.1 for testing purposes.
The latest updates from debian 10.1 (buster), antiX and MX repos.
Xfce 4.14
GIMP 2.10.12
MESA 18.3.6
updated firmware
Latest debian 4.19 kernel
Browser: Firefox 69
Video Player: VLC 3.0.8
Music Manager/Player: Clementine 1.3.1
Email client: Thunderbird 60.8.0
Office suite: LibreOffice 6.1.5 (plus security fixes)
apparmor 2.13.2
and more in the MX repositories.
–New and updated mx-apps
mx-installer (based on gazelle-installer) fixes pertaining to automount
issues.
MX Date & Time, to make clock setting chores easier
formatusb, for formatting usb storage devices
mx-packageinstaller now displays version number for flatpak applications.
mx-alerts package for sending emergency messages to users.
mx-updater no longer requires a password to check for updates (still
required for installation of updates)
new wallpaper artwork (mx19-artwork package)
updated themes
tons of misc. updates to the mx tools.
most help files are now available on the iso
-antiX live system changes
The latest antiX live system updates, included improved support for
hyper-v and kvm.
improved support for frugal installations on ntfs devices
live system now boots with a informative text-based boot splash.
-Improved localization
almost all mx-apps received translation updates (we love translators)
Misc.
sysVinit remains the default init system. systemd is available as a boot
option on installed systems (but not on live systems). In other words,
exactly the same as MX17/18.
Set your gtk scaling in Appearance, log out/log in and Qt apps should
follow the scaling set.
New conky configs (conky-manager for selections)
September 8, 2019September 8, 2019
<https://mxlinux.org/blog/mx-19-beta-2-1 ... r-testing/> by
dolphin_oracle <https://mxlinux.org/author/dolphin_oracle/>
MX-19 Beta 2.1 available for testing
Updated iso images
–direct download:
https://sourceforge.net/projects/mx-lin … ing/MX-19/
<https://sourceforge.net/projects/mx-lin ... ing/MX-19/>
We are pleased to offer MX-19 Beta 2.1 for testing purposes.
The latest updates from debian 10.1 (buster), antiX and MX repos.
Xfce 4.14
GIMP 2.10.12
MESA 18.3.6
updated firmware
Latest debian 4.19 kernel
Browser: Firefox 69
Video Player: VLC 3.0.8
Music Manager/Player: Clementine 1.3.1
Email client: Thunderbird 60.8.0
Office suite: LibreOffice 6.1.5 (plus security fixes)
apparmor 2.13.2
and more in the MX repositories.
–New and updated mx-apps
mx-installer (based on gazelle-installer) fixes pertaining to automount
issues.
MX Date & Time, to make clock setting chores easier
formatusb, for formatting usb storage devices
mx-packageinstaller now displays version number for flatpak applications.
mx-alerts package for sending emergency messages to users.
mx-updater no longer requires a password to check for updates (still
required for installation of updates)
new wallpaper artwork (mx19-artwork package)
updated themes
tons of misc. updates to the mx tools.
most help files are now available on the iso
-antiX live system changes
The latest antiX live system updates, included improved support for
hyper-v and kvm.
improved support for frugal installations on ntfs devices
live system now boots with a informative text-based boot splash.
-Improved localization
almost all mx-apps received translation updates (we love translators)
Misc.
sysVinit remains the default init system. systemd is available as a boot
option on installed systems (but not on live systems). In other words,
exactly the same as MX17/18.
Set your gtk scaling in Appearance, log out/log in and Qt apps should
follow the scaling set.
New conky configs (conky-manager for selections)
I have posted an update to PeasyXorBurn here with an improved remastering tool.
The previous version assumed that the boot files like isolinux.bin were at the root of the ISO source folder.
The new version allows them to be in a subfolder named "isolinux". This is how the Dog ISOs are structured.
The previous version assumed that the boot files like isolinux.bin were at the root of the ISO source folder.
The new version allows them to be in a subfolder named "isolinux". This is how the Dog ISOs are structured.
I have posted a question about one of my PCs doesn't "see" the graphics cards here:
http://www.murga-linux.com/puppy/viewto ... 51#1041051
I didn't want to clutter this very good topic
http://www.murga-linux.com/puppy/viewto ... 51#1041051
I didn't want to clutter this very good topic