Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 22 Aug 2018, 03:38
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
A Debian-Stretch-Live Starter Kit
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 8 of 9 [122 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9 Next
Author Message
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Wed 13 Jun 2018, 06:33    Post subject:
Subject description: PeasyWiFi
 

anikin wrote:
will it work with dash?

I have a no-bash version. But PWF has a learning curve. It would be preferable to test the standard version first in one of the current Dogs.

Its startup mechanisms may not work the same in pure Debian.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Fri 15 Jun 2018, 10:24    Post subject:  

Here is PeasyPrint ported from Puppy. The instructions are here.

Update: V3.0 also accepts other graphics formats, like GIF.
peasyprint_3.0.deb.gz
Description  Updated 2018-08-04
gz

 Download 
Filename  peasyprint_3.0.deb.gz 
Filesize  7.8 KB 
Downloaded  16 Time(s) 
peasyprint_2.9.deb.gz
Description  Remove the fake .gz extension
gz

 Download 
Filename  peasyprint_2.9.deb.gz 
Filesize  7.75 KB 
Downloaded  50 Time(s) 

Last edited by rcrsn51 on Sat 04 Aug 2018, 08:33; edited 1 time in total
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Mon 02 Jul 2018, 08:35    Post subject:  

How to install Stretch-live on a UEFI computer

Users with Win8/10 machines or new motherboards are familiar with the issues of UEFI, GRUB2 and Secure Boot. Here is a recipe for dealing with them.

1. At bootup, you need to access the UEFI setup menus. On old BIOS machines, you would see a message like "Press Del to enter setup". But Windows now has "Fast Boot" that hides these messages. So you need to know the "hot key" like F2 in advance. By pressing it repeatedly as the machine boots, you can get into the menus. Some googling may yield the hot key for your particular machine.

If not, let Windows start, then find the back-door into the UEFI firmware settings. There are instructions here.

2. Your first task in the UEFI setup is to disable Secure Boot. Most PC's have this option located somewhere in the menus. (It may be in a "Boot" submenu.) Then look for any Fast Boot options and disable them too. This will give you more time at bootup to press the hot key.

3. Note that we are leaving the machine as a UEFI boot device. We are NOT switching it back to "Legacy" or "CSM" mode. Any settings like Load Legacy Option ROM must be set to Disable.

4. If you are planning to dual-boot Windows, you also need to disable its hibernation feature, AKA "Fast Startup". Do this from within Windows - read here.

5. Build a UEFI-bootable flash drive. You can do this from either Windows or Linux.
a. Get a flash drive formatted as FAT32.
b. Download the uefi-grub2.iso from here.
c. Click on the file to mount it. Copy its contents onto the flash drive. There is a folder named EFI and three files.
d. Download a Stretch-live ISO and click-mount it. Copy the entire "live" folder onto the flash drive.
e. Also copy the whole ISO file onto the drive. You will need it to do a hard drive install.

6. Boot the flash drive.
a. Press the hot key to open the UEFI menus.
b. Locate the boot priority list and set USB first. If you cannot find the list, read the Update below.
c. Save and exit.

7. With any luck, the flash drive should boot. There will be a brief menu about locating a grub.cfg file. For now, ignore it.

8. The main GRUB2 menu has two choices. Try "Porteus boot" first. If it fails with a "file not found" error, reboot and try "live-boot" instead.

9. Please note that neither of these boot setups allow for persistence - having a save file/folder on the USB drive. The intent is to do a frugal install onto the hard drive. You will need a Linux-compatible partition there.

a. Stretch-Live has Gparted in its Preferences menu. In my experience, you can safely shrink a Windows main C: partition by 10-20GB. Then make a new ext4 partition in the empty space. YMMV.

b. Your flash drive has the stretch-live-frugal-install tool. Read here for instructions. Do a frugal install into the ext partition.

c. Run the GRUB2 converter tool to generate a menu entry for your frugal install.

10. You have two choices for how the system will boot:

a. Dual-boot with Windows. The safest procedure for Linux is to boot off the flash drive, then jump to the hard drive. Copy/paste the GRUB2 entry from above into your flash drive's grub.cfg. This will be a Porteus boot with a save folder in the ext partition.

b. Scrap Windows and start an all-Linux system. Using Gparted, delete the Windows partitions. Make a FAT32 "UEFI boot" partition and one or more ext partitions. (If there is already a FAT32 partition, leave it but delete the contents.) Set up the boot partition for UEFI with the same content as your flash drive. See the Update for how to replace the UEFI Windows boot entry with your own.

11. Is everything working? There may still be a small bug. If you re-boot off the flash drive, GRUB2 may find your hard drive's grub.cfg instead. Unlike Grub4Dos, GRUB2 searches all the available drives for a grub.cfg, NOT just the boot drive. At the brief initial menu, select "Manually specify location". In GRUB2 syntax, your flash drive will probably be drive 1, partition 1. Enter:
Code:
(hd1,1)/grub.cfg

Update: Some UEFI setups don't have a conventional boot priority list. So you have to press another hot key like F12 in order to boot from USB.

This is awkward if you need to do it each time. Here is how to add a permanent USB boot option.

1. Press F2 and open the Boot section.
2. Select: File browser add boot entry
3. Select the cryptic entry that looks like your USB drive.
4. Drill down and select the file: EFI/boot/bootx64.efi
5. Name the entry: USB.
6. Select Boot Option #1 and set it to USB. Windows should become Option #2.
7. Save and reboot. If the USB drive is present, it will boot instead of Windows.

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

Last edited by rcrsn51 on Fri 27 Jul 2018, 07:10; edited 17 times in total
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Mon 09 Jul 2018, 16:24    Post subject:  

In rare cases, you may be unable to find a working video driver. For example, the i915 modesetting driver may fail with some Intel chipsets and give a black-screen-of-death.

The only solution may be to use the Xorg vesa driver instead.

1. In your GRUB menu, add "i915.modeset=0" to the kernel line (if needed).

2. The Starter Kit does not have the vesa driver OOTB. You have two choices:

a. Download and install it on-the-fly from the console prompt (assuming you have a network connection).
Code:
apt-get update
apt-get install xserver-xorg-video-vesa
startx

b. Get the squashfs module from below and drop it into the "live" folder of your install.

Remove the fake .gz extension.

-------------
xserver-xorg-video-vesa_1%3a2.3.4-1+b2_i386.squashfs.gz
Description 
gz

 Download 
Filename  xserver-xorg-video-vesa_1%3a2.3.4-1+b2_i386.squashfs.gz 
Filesize  16 KB 
Downloaded  25 Time(s) 
xserver-xorg-video-vesa_1%3a2.3.4-1+b2_amd64.squashfs.gz
Description 
gz

 Download 
Filename  xserver-xorg-video-vesa_1%3a2.3.4-1+b2_amd64.squashfs.gz 
Filesize  16 KB 
Downloaded  25 Time(s) 
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Thu 19 Jul 2018, 06:40    Post subject:  

Fred's repo now has updates to the BT4Stretch Bluetooth system and the Batterup laptop battery monitor.

See Page 1 for links.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Sat 04 Aug 2018, 10:22    Post subject:  

Here is the Starter Kit on a Gigabyte Brix GB-BXBT-1900. It has a Celeron N2807 SoC and 4GB of RAM. Note the current CPU frequency.

It boots via a standard UEFI setup with both legacy CSM and Secure Boot disabled.

Everything works OOTB, including WiFi, Bluetooth and HDMI.

This is a silent fanless unit, aside from the internal 2.5-inch HDD.

Of all the bare-bones kits I have tried, this was the simplest by far. But it requires DDR3L low-voltage RAM.

-----------------------
gigabyte.png
 Description   
 Filesize   175.25 KB
 Viewed   541 Time(s)

gigabyte.png

Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Mon 06 Aug 2018, 15:29    Post subject:  

Here is the Starter Kit on a 2008 Lenovo single-core Atom netbook with 1.5GB RAM.

This is a legacy BIOS boot via Grub4Dos.

These early Atoms prefer the Xorg "intel" video driver over the "i915" modesetting driver.

It has Broadcom WiFi and uses the vendor wl driver. The touchpad works fine with tapping enabled, but it's tiny.

It can run Firefox Quantum 61 with YouTube video+audio (at 360p). Also Chromium 66.

Batterup works reliably as the battery monitor.

Unlike XP, where the fan ran constantly, this setup quiets down when it is not under load.

-------------------
lenovo.png
 Description   
 Filesize   152.78 KB
 Viewed   420 Time(s)

lenovo.png

Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Wed 08 Aug 2018, 06:38    Post subject:  

Here is the Starter Kit on an HP-Compaq 6005 SFF desktop box with an AMD CPU and 4GB RAM.

Xorg uses the "radeon" modesetting driver here. It requires firmware, which is included in the Starter Kit. Everything works OOTB, including the DisplayPort video output.

The unit has an additional PCI sound card, which is handled nicely by Sound Card Selector.

Originally, this was a Win7 machine with standard BIOS boot. It was upgraded to Win10 but kept the BIOS setup (no UEFI/Secure Boot). I split off an ext4 partition for the Starter Kit. It boots by running Legacy GRUB from the Linux partition boot sector. Win10 boots from the GRUB menu.
HP6005.png
 Description   
 Filesize   159.4 KB
 Viewed   371 Time(s)

HP6005.png

Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Fri 10 Aug 2018, 08:17    Post subject:  

Here is the Starter Kit on an Asus C200MA Chromebook. It has a Celeron N2830 SoC, 2GB RAM and 16GB eMMC.

Like all Chromebooks, you need three skills before starting.
1. How to put the unit in "developer" mode so you can install a Linux.
2. How to install the legacy BIOS firmware (if needed) so it can boot off a flash drive.
3. How to revert the unit back to ChromeOS if something goes wrong.

The eMMC drive was wiped and switched to an MS-DOS partition table. The Starter Kit was installed to the eMMC and boots via Grub4Dos.

Like some other SoC chipsets, this machine has trouble with ALSA audio. Luckily, it has Intel WiFi/Bluetooth, so you can send audio output to a BT speaker via BT4Stretch. Or connect to an HDMI display, or use a USB sound card adapter with headphones.

Everything else works well. Touchpad control is excellent.
chromebook.png
 Description   
 Filesize   150.17 KB
 Viewed   330 Time(s)

chromebook.png

Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Sat 11 Aug 2018, 11:39    Post subject:  

Here is the HP-6005 with an NVIDIA GeForce 710B PCIe card. OOTB, it uses the Xorg nouveau modesetting driver, which works fine.

It is connected to a 19inch TV via HDMI. Lxrandr finds the right monitor and Sound Card Selector picks the HDMI audio.

Instructions for installing the vendor "nvidia" driver are here.
nvidia.png
 Description   
 Filesize   250.58 KB
 Viewed   253 Time(s)

nvidia.png

Back to top
View user's profile Send private message 
roadkill13

Joined: 10 Aug 2011
Posts: 123
Location: United States

PostPosted: Mon 13 Aug 2018, 21:47    Post subject: multimedia keyring  

fredx181 wrote:

Quote:
There is deb-mutimedia repository which can be activated by uncommenting it (remove the "#" ) from /etc/apt/sources.list, so becomes this:
Code:
#Debian Multimedia
deb ftp://ftp.deb-multimedia.org/ stretch main non-free

Then, in terminal:
Code:
apt-get update

EDIT: And install deb-multimedia-keyring:
Code:
apt-get install deb-multimedia-keyring
apt-get update


Wouldn't work for me. Apt refused to update due to lack of pubkey. It could not download the multimedia keyring.

I resolved the issue this way:

wget http://www.deb-multimedia.org/pool/main/d/deb-multimedia-keyring/deb-multimedia-keyring_2016.8.1_all.deb

I installed this file from the right click menu then ran apt update.
Back to top
View user's profile Send private message Yahoo Messenger 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Tue 14 Aug 2018, 08:32    Post subject:  

@roadkill: Thanks for this update. I have added a link on the main post.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3230
Location: holland

PostPosted: Tue 14 Aug 2018, 09:10    Post subject:  

@roadkill, thanks, your method should work OK, but strange... for me it works when I type "y" when it asks to install without verification, it didn't for you ?:
Code:
root@live:~# apt-get install deb-multimedia-keyring
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  deb-multimedia-keyring
0 upgraded, 1 newly installed, 0 to remove and 37 not upgraded.
Need to get 10.7 kB of archives.
After this operation, 25.6 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  deb-multimedia-keyring
Install these packages without verification? [y/N] y
Get:1 ftp://ftp.deb-multimedia.org stretch/main i386 deb-multimedia-keyring all 2016.8.1 [10.7 kB]
Fetched 10.7 kB in 0s (33.7 kB/s)           
Selecting previously unselected package deb-multimedia-keyring.
(Reading database ... 44777 files and directories currently installed.)
Preparing to unpack .../deb-multimedia-keyring_2016.8.1_all.deb ...
Unpacking deb-multimedia-keyring (2016.8.1) ...
Setting up deb-multimedia-keyring (2016.8.1) ...


Fred

_________________
Dog Linux website
Back to top
View user's profile Send private message 
roadkill13

Joined: 10 Aug 2011
Posts: 123
Location: United States

PostPosted: Tue 14 Aug 2018, 16:02    Post subject:  

Quote:
@roadkill, thanks, your method should work OK, but strange... for me it works when I type "y" when it asks to install without verification, it didn't for you ?


No it did not. It let me off at the command prompt after stating "package not found". I also tried to force the install. I found this at deb-multimedia.org:

Quote:
After you have added the necessary line in /etc/apt/sources.list the first package to install is deb-multimedia-keyring.

apt-get update
The “-oAcquire::AllowInsecureRepositories=true” option is mandatory since Buster and thus also needed for unstable.
apt-get update -oAcquire::AllowInsecureRepositories=true
apt-get install deb-multimedia-keyring -oAcquire::AllowInsecureRepositories=true

Since Squeeze you can install this package with apt-aget. Simply press y when the package ask what to do (don't press return).

If apt-get can not find the new key, do that :

wget http://www.deb-multimedia.org/pool/main/d/deb-multimedia-keyring/deb-multimedia-keyring_2016.8.1_all.deb
sudo dpkg -i deb-multimedia-keyring_2016.8.1_all.debAfter you have added the necessary line in /etc/apt/sources.list the first package to install is deb-multimedia-keyring.


As suggested by this post I tried the first option which also did not work. Apt could not find the keyring. So I resorted to the second option described above. It worked.
Back to top
View user's profile Send private message Yahoo Messenger 
rcrsn51


Joined: 05 Sep 2006
Posts: 12276
Location: Stratford, Ontario

PostPosted: Tue 14 Aug 2018, 16:45    Post subject:  

I did a fresh install of the Starter Kit and followed fred's instructions. They worked for me.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 8 of 9 [122 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1279s ][ Queries: 13 (0.0447s) ][ GZIP on ]