The Starter Kit and X video
The Starter Kit is pretty good at finding the right video driver for your hardware. However, Debian has dropped support for some old video cards. In this situation, X may automatically fall back to using the VESA driver (which is contained in the ISO) and boot successfully. This may also happen if you need to disable the kernel modesetting driver.
But not all video cards support VESA. If all else fails, here is a possible solution that uses framebuffer video instead. This for 64bit Buster.
1. Download the attached squashfs module and remove the fake .gz extension.
2. Starting with a bootable flash drive, put the module in its "live" folder.
3. Boot off the flash drive.
4. If X starts, install the Starter Kit to your hard drive as usual using the stretch-live-frugal-install tool.
5. Copy the framebuffer module to its "live" folder.
6. Reboot off the hard drive.
----------------------
The Debian-Stretch-Live Starter Kit
- Attachments
-
- xserver-xorg-video-fbdev_1%3a0.5.0-1_amd64.squashfs.gz
- (12 KiB) Downloaded 180 times
NVIDIA Updates
Buster k4.19.0
a. The Stretch .deb package here appears to work OK in Buster.
b. If it does NOT support your video card, the best option is Method A.
c. I cannot get Method B to work with this kernel.
Buster k5.4.0.bpo - Method A
a. Add the following line to the file /etc/apt/sources.list
b. Run: apt update Hint: Make sure that your time zone and clock are set correctly.
c. Follow the regular procedure but use
Buster k5.4.0.bpo - Method B
a. You may need the NVIDIA 440-series source package with this new kernel.
b. Update your sources.list as above.
c. If you make your own mini-devx module, build it as usual.
d. Install two extra packages: pkg-config libglvnd-dev
e. Follow the regular procedure. At the end, ignore the error message about "nvidia-drm".
f. Reboot
------------------
Buster k4.19.0
a. The Stretch .deb package here appears to work OK in Buster.
b. If it does NOT support your video card, the best option is Method A.
c. I cannot get Method B to work with this kernel.
Buster k5.4.0.bpo - Method A
a. Add the following line to the file /etc/apt/sources.list
Code: Select all
deb http://ftp.debian.org/debian/ buster-backports main contrib non-freec. Follow the regular procedure but use
Code: Select all
apt install -t buster-backports nvidia-xxxa. You may need the NVIDIA 440-series source package with this new kernel.
b. Update your sources.list as above.
c. If you make your own mini-devx module, build it as usual.
d. Install two extra packages: pkg-config libglvnd-dev
e. Follow the regular procedure. At the end, ignore the error message about "nvidia-drm".
f. Reboot
------------------
How to build a squashfs module for Zoom video conferencing
This will be a third-party build with a guest user and an extra package. Read the instructions for the Google Chrome browser on Page 2.
1. Go to the Zoom site and download zoom_amd64.deb.
2. Download and extract the attached zoom-guest-setup script.
3. Run: repo2sfs zoom_amd64.deb
4. Include the extra packages: libnss3
5. At Pause B, open another terminal and run the setup script.
6. The module puts an entry in the Internet menu which starts a launcher in the system tray.
This has only been tested as far as the Zoom login screen, so I don't know how the audio/video works.
This will be a third-party build with a guest user and an extra package. Read the instructions for the Google Chrome browser on Page 2.
1. Go to the Zoom site and download zoom_amd64.deb.
2. Download and extract the attached zoom-guest-setup script.
3. Run: repo2sfs zoom_amd64.deb
4. Include the extra packages: libnss3
5. At Pause B, open another terminal and run the setup script.
6. The module puts an entry in the Internet menu which starts a launcher in the system tray.
This has only been tested as far as the Zoom login screen, so I don't know how the audio/video works.
- Attachments
-
- zoom-guest-setup.tar.gz
- (304 Bytes) Downloaded 180 times
Last edited by rcrsn51 on Fri 03 Apr 2020, 11:22, edited 2 times in total.
How to make a GRUB2 bootable flash drive
You may need GRUB2 to boot certain ISOs using a loop-mounting technique. There are two procedures depending on the machine that you plan to boot with the flash drive.
A. If the target machine is UEFI, the setup is easy. Read here and go to Step 5. This UEFI bootloader uses GRUB2.
B. If the target is BIOS, you need to install GRUB2 yourself.
1. Using repo2sfs, make a squashfs module of the Debian package "grub2".
2. Activate the module.
3. Format a flash drive as ext3/4. Make additional partitions as required.
4. Mount the flash drive. We will assume that it is device sdb.
5. Run these commands. As usual, make sure that you select the right device!
6. Your grub.cfg file will eventually go in /boot/grub of the flash drive.
You may need GRUB2 to boot certain ISOs using a loop-mounting technique. There are two procedures depending on the machine that you plan to boot with the flash drive.
A. If the target machine is UEFI, the setup is easy. Read here and go to Step 5. This UEFI bootloader uses GRUB2.
B. If the target is BIOS, you need to install GRUB2 yourself.
1. Using repo2sfs, make a squashfs module of the Debian package "grub2".
2. Activate the module.
3. Format a flash drive as ext3/4. Make additional partitions as required.
4. Mount the flash drive. We will assume that it is device sdb.
5. Run these commands. As usual, make sure that you select the right device!
Code: Select all
mkdir /mnt/sdb1/boot
grub-install --boot-directory=/mnt/sdb1/boot /dev/sdbCan you please tell me what should be my parameters to boot this?
here is what i did. but didn't work.
here is what i did. but didn't work.
Code: Select all
#
title DebianStretch
root (hd0,0) <-- GRUB legacy, ex: hd1,0
uuid ed452e03-b2ce-4e0f-8428-263348161af0
kernel /DebianStretch/live/vmlinuz1 pmedia=atahd psubdir=DebianStretch
initrd /DebianStretch/live/initrd1.xz
#You are mixing in Puppy parameters.ethplorer wrote:Can you please tell me what should be my parameters to boot this?
here is what i did. but didn't work.
Code: Select all
# title DebianStretch root (hd0,0) <-- GRUB legacy, ex: hd1,0 uuid ed452e03-b2ce-4e0f-8428-263348161af0 kernel /DebianStretch/live/vmlinuz1 pmedia=atahd psubdir=DebianStretch initrd /DebianStretch/live/initrd1.xz #
Try
Code: Select all
title DebianStretch
uuid ed452e03-b2ce-4e0f-8428-263348161af0
kernel /DebianStretch/live/vmlinuz1 noauto from=/DebianStretch/ changes=EXIT:/DebianStretch/
initrd /DebianStretch/live/initrd1.xzCode: Select all
title ChromeDog64NoNvidia from=ChromeDog64NoNvidia/ changes=EXIT:/ChromeDog64NoNvidia/
uuid 74b29a4d-f300-424c-8c48-d91a7xxxxxxx
kernel /ChromeDog64NoNvidia/live/vmlinuz1 noauto from=/ChromeDog64NoNvidia/ changes=EXIT:/ChromeDog64NoNvidia/
initrd /ChromeDog64NoNvidia/live/initrd1.xzHow to make a USB boot drive for the Starter Kit
For newcomers to the Starter Kit project, here is a recipe for making an initial USB boot device.
A. You are a current Puppy user:
A1. The target machine is BIOS. There are two choices:
A11. Make an ISObooter flash drive from here. Use "non-Puppy" mode.
A12. Use the stretch-live-frugal-install tool from here. It has an option to put the Grub4Dos bootloader on the drive.
A2. The target machine is UEFI. Make a UEFI-bootable flash drive using the instructions here. Start at Step 5.
B. You are a current Ubuntu/Mint/etc. user:
B1. The target machine is BIOS. See the alternate instructions for ISObooter here.
B2. The target machine is UEFI. Make a UEFI-bootable flash drive using the instructions here. Start at Step 5.
C. You are starting from Windows:
C1. The target machine is BIOS. See the alternate instructions for ISObooter here.
C2. The target machine is UEFI. Make a UEFI-bootable flash drive using the instructions here. Start at Step 5.
For newcomers to the Starter Kit project, here is a recipe for making an initial USB boot device.
A. You are a current Puppy user:
A1. The target machine is BIOS. There are two choices:
A11. Make an ISObooter flash drive from here. Use "non-Puppy" mode.
A12. Use the stretch-live-frugal-install tool from here. It has an option to put the Grub4Dos bootloader on the drive.
A2. The target machine is UEFI. Make a UEFI-bootable flash drive using the instructions here. Start at Step 5.
B. You are a current Ubuntu/Mint/etc. user:
B1. The target machine is BIOS. See the alternate instructions for ISObooter here.
B2. The target machine is UEFI. Make a UEFI-bootable flash drive using the instructions here. Start at Step 5.
C. You are starting from Windows:
C1. The target machine is BIOS. See the alternate instructions for ISObooter here.
C2. The target machine is UEFI. Make a UEFI-bootable flash drive using the instructions here. Start at Step 5.
This is the Buster Starter Kit on an old ThinkPad T61 with a Core2Duo CPU, 2GB RAM and NVIDIA graphics. The video can use either the nouveau modesetting driver or my NVIDIA vendor package from Stretch. It can render fullscreen YouTube video at 720p.
The new backlight control in Touchpad works with both drivers. The Centrino WiFi and Bluetooth audio work as expected.
The machine has a clean install of XP that I want to save for testing purposes. So I split off a Linux partition, flagged it as bootable and put Legacy GRUB Stage1 on the PBS. On a BIOS machine, this continues to be the simplest way to multi-boot without touching Windows.
The new backlight control in Touchpad works with both drivers. The Centrino WiFi and Bluetooth audio work as expected.
The machine has a clean install of XP that I want to save for testing purposes. So I split off a Linux partition, flagged it as bootable and put Legacy GRUB Stage1 on the PBS. On a BIOS machine, this continues to be the simplest way to multi-boot without touching Windows.
- Attachments
-
- snappie.png
- (178.12 KiB) Downloaded 430 times
Attached below is an update to PeasyScan.
1. PeasyScan now recognizes SANE device names (URI's) that contain spaces. This is required by some next-generation SANE backends that use multi-word device names.
2. The OCR function has been removed in favour of the separate pic2txt app which has been updated here.
3. V2.16 recognizes the following PAPER choices to use in config files for Auto scanning:
Custom paper sizes and scan areas can be handled with the OTHER variable:
-----------------------
1. PeasyScan now recognizes SANE device names (URI's) that contain spaces. This is required by some next-generation SANE backends that use multi-word device names.
2. The OCR function has been removed in favour of the separate pic2txt app which has been updated here.
3. V2.16 recognizes the following PAPER choices to use in config files for Auto scanning:
Code: Select all
letter, legal
ledger (11x17)
a3, a4, a5
a6 (4x6 photo)
b6 (5x7 photo)
b7 (5x3 index card)Code: Select all
export OTHER="-x www -y hhh" #in millimetres- Attachments
-
- peasyscan_2.16_amd64.deb.gz
- Updated 2020-06-18
- (49.84 KiB) Downloaded 136 times
-
- peasyscan_2.16_i386.deb.gz
- Updated 2020-06-18
- (48.84 KiB) Downloaded 141 times
Last edited by rcrsn51 on Fri 19 Jun 2020, 11:22, edited 5 times in total.
first I want to thank you for this great addition, it worked on my xenialpup. However I have some questions in regard to how it operates.rcrsn51 wrote:WlanMaker
-----------------
To enable Internet sharing, do the following:
The server machine needs the additional package "iptables" via apt-get.
Start the server with: wlanmaker wlan0 ssid passphrase eth0
The fourth argument is the server's Internet-facing port.
Client machines will get an IP address via DHCP and a route to the Internet.
--------------------------
----------------------
1) if my firewall is working, then there is no access to internet. However, I want to keep my firewall operational.how can I achieve this.
2)even though I closed my terminal, it is still operate in the background and I could access internet ( while disabeling the firewall). how to stop it or enable it again?
kindly explain in easy terms as I am a beginner in linux in general and puppy in particular. Thanks again
Xanialpup 7.5 32 bit