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 Thu 21 Nov 2019, 09:57
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
EasyOS Pyro 1.2.8, Buster 2.1.8 November 6, 2019
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 130 of 133 [1994 Posts]   Goto page: Previous 1, 2, 3, ..., 128, 129, 130, 131, 132, 133 Next
Author Message
tom22251


Joined: 08 Oct 2019
Posts: 10

PostPosted: Thu 24 Oct 2019, 12:03    Post subject:  

Hi Jürg,

Let'say you have an internal drive with 3 partitions.
They are called sda1, sda2, sda3 and we want to
install EASY-2.1.6 on an external USB drive.

1) UEFI
Take 1 anything USB: memorystick or external drive just
large enough to fit 3-or 4 times the easy.img's size.
8GB is more than plenty. This will be the sdb drive.

2) GParted
Make a fat32 partition, set the bootflag on.
Give it a label like LINUX or EASY or anything.This will
make it easier to write the configuration files, using
this instead a UUID number. This drive is now sdb1.
Make a second partition ext3, this will be sdb2.

3) Make a new folder in the fat32 partition with
a simple name like E-126.
From now on you'll do everything manually. That is clicking
on the easy.img file and drag easy.sfs, initrd and vmlinuz
into this E-126 folder.
You also drag the EFI folder onto the fat32 drive, where
you'll have only these 2 folders: EFI and E-216.

4) editing the configuration file inside EFI => BOOT
named: refind.conf (it's a simple text file)
Erase everything and paste in just this text:

Code:

 menuentry "EASY-2.1.6" {
    volume LINUX
    loader /E-216/vmlinuz
    initrd /E-216/initrd
      icon /EFI/BOOT/icons/os_easy.png
    ostype  Linux
   options "rootwait rw vga=792"
}



Leave the other files untouched,
like: BOOTIA32.EFI and BOOTX64.EFI
Without them it won't boot.
You'll also see the icons folder where you
can put new logos, 128x128 pixels. I have
about 8-10 different easy logos, for different
easy versions. But it works just as well without
logos.

Now you'll ask what about the second partition ext3.
That is for saving, unsquashing, editing a remaster etc.
You cannot do that in fat32.

So wat I do is I set up a folder with a similar name
inthis case E-216 and after clicking an easy.sfs, drag
everything here. Basically what you have is the whole
Easy-2.1.6 unsquashed ready for editing. Add-remove whatever
you like, and resquashing the folder E-216:

Code:

aplay /usr/share/audio/bark.au           
cd /mnt/sdb2/
mksquashfs E-216 easy.sfs
sync
aplay /usr/share/audio/2barks.au
exit



Now you can replace the original easy.sfs in the fat32 patition.

Inside /mnt/sdb2/E-216 create an other folder called SAVE
or whatever other name you like.
This is the folder for saving any changes you want during the
live session when drives sdb1 and sdb2 are unplugged.
Replug before you want to save and mount sdb2:

Code:

mount /dev/sdb2 /mnt/sdb2
aplay /usr/share/audio/bark.au           
cd /mnt/sdb2/E-216/
cp -a /mnt/wkg/.session/* SAVE
sync
aplay /usr/share/audio/2barks.au
cd
umount /mnt/sdb2
exit



End when you start Easy anew, of course will
boot into the original, pristine version.
So to apply the changes you run this little
script "updt.sh":

Code:

mount /dev/sdb2 /mnt/sdb2
aplay /usr/share/audio/bark.au           
cd /mnt/sdb2/E-216/
cp -a SAVE/* /
sync
aplay /usr/share/audio/2barks.au
cd
umount /mnt/sdb2
restartwm
exit



That's all for now.
Let me know if it works.
This EFI business worked even with
my sister's MacBook Pro, which everybody
says is wery difficult.In fact that's where
I experimented the stuff.

Oh, and by the way, you can have just one
ext3 partition but then you need the other
bootloader "extlinux", and each Easy Version
has its own folder, with the SAVE folder
and unsqushed folder inside, next to easy.sfs,
vmlinuz and initrd files. So basically the
whole drive will have one BOOT folder and
the different Easy folders like E-126, E-127,
E-215, E-217, E-1.1 etc

Bye.
Tom
Back to top
View user's profile Send private message 
Terry H

Joined: 29 Mar 2009
Posts: 671
Location: The Heart of Muskoka, ON Canada

PostPosted: Thu 24 Oct 2019, 12:41    Post subject:  

belham2 wrote:

am I incorrectly forgetting what urxvt controls??


Hi belham2,

I did similar test to you to check. rxvt is not changed following changes made in urxvt control, but the appearance when using urxvt is changed.
Back to top
View user's profile Send private message 
tom22251


Joined: 08 Oct 2019
Posts: 10

PostPosted: Thu 24 Oct 2019, 13:09    Post subject:  

In my last post I left out 2 lines.
The correct code is:
Code:

timeout 33333
scanfor manual

 menuentry "EASY-2.1.6" {
    volume LINUX
    loader /E-216/vmlinuz
    initrd /E-216/initrd
    icon /EFI/BOOT/icons/os_easy.png
    ostype  Linux
    options "rootwait rw vga=792"
}



sorry
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1703

PostPosted: Thu 24 Oct 2019, 13:29    Post subject:  

Terry H wrote:
belham2 wrote:

am I incorrectly forgetting what urxvt controls??


Hi belham2,

I did similar test to you to check. rxvt is not changed following changes made in urxvt control, but the appearance when using urxvt is changed.


Oh man Embarassed .......is this a sign that old age is starting to get me?

How did I brain-fart to such an extent that I forget to open urxvt and stubbornly bang on xrvt wondering what's going on? Rolling Eyes

Apologies all.

Apologies Barry.
Back to top
View user's profile Send private message 
lp-dolittle

Joined: 25 Apr 2016
Posts: 112

PostPosted: Thu 24 Oct 2019, 15:46    Post subject: EasyOS running totally in RAM
Subject description: tom22251 method
 

@ tom22251

Hi Tom,

your ongoing support proves to be very helpful. Despite being slow on the uptake, amply lacking basic knowledge (I'm just a layman who is willing to learn more about IT-technology), I begin to understand the details.

I will follow your instructions, step by step, as soon as possible; and you will get feedback.

If I'm right, you actually are speaking of 2 variants, the 'fat-partition plus save-partition' method and the 'ext3-partition only' alternative. Firstly, I have in mind to focus on the former which seems to work without an "extlinux" boot loader.

thank you very much, your help is highly appreciated!!

kind regards

Jürg
Back to top
View user's profile Send private message 
rooftop

Joined: 10 Oct 2019
Posts: 3
Location: Melbourne, Australia

PostPosted: Thu 24 Oct 2019, 18:42    Post subject: Re: Battery app not updating.  

I had a quick look at the battery app last night. It appears that the problem is that the Update() function does not explicitly return a value, and in some cases it is returning FALSE (or 0) which causes the function to never be called again.

The easy fix is to replace all 'return' statements in the Update function with 'return(TRUE)' and add a 'return(TRUE)' as the last line of the function. This has the added bonus of getting rid of all the compiler warnings Smile

It might also be worth while replacing gtk_timeout_add() with g_timeout_add_seconds() as the former has been depreciated and the later is claimed to be more efficient. If using g_timeout_add_seconds() the interval needs to be changed from 15000 to 15 as is is given in seconds rather than milliseconds.

I've attached my modified version of powerapplet_tray.c (with all the above modifications) in case anyone is interested...

-- Neal
powerapplet_tray.c.gz
Description  Modified version of powerapplet_tray.c
gz

 Download 
Filename  powerapplet_tray.c.gz 
Filesize  2.77 KB 
Downloaded  32 Time(s) 
Back to top
View user's profile Send private message Visit poster's website 
Leon

Joined: 22 Jun 2005
Posts: 265

PostPosted: Fri 25 Oct 2019, 18:40    Post subject: Re: Battery app not updating.  

rooftop wrote:
I've attached my modified version of powerapplet_tray.c (with all the above modifications) in case anyone is interested...

Hello rooftop,

Thank you very much for the most needed fix for my favorite Quirky Beaver64 8.7.1.

I downloaded the source from:
http://distro.ibiblio.org/easyos/source/alphabetical/p/powerapplet_tray-2.6.tar.bz2
and replaced the file powerapplet_tray.c with your version.

I also replaced the compile command in compile script
from
Code:
gcc `pkg-config --cflags --libs gtk+-2.0` powerapplet_tray.c -o powerapplet_tray
to
Code:
gcc -Wl,--no-as-needed `pkg-config --cflags --libs gtk+-2.0` powerapplet_tray.c -o powerapplet_tray

as recommended here:
http://www.murga-linux.com/puppy/viewtopic.php?t=85752

Then I compiled the source in Quirky Beaver64 8.7.1, made the pet package and tested it.

It works perfectly.

Patched powerapplet_tray pet package for Quirky Beaver64 8.7.1 is here:
http://murga-linux.com/puppy/viewtopic.php?p=1040444#1040444
Back to top
View user's profile Send private message 
rooftop

Joined: 10 Oct 2019
Posts: 3
Location: Melbourne, Australia

PostPosted: Fri 25 Oct 2019, 21:22    Post subject: Re: Battery app not updating.  

I've made another small change to the battery app so that the icon will update immediately (well, within 15 seconds anyway) when the charging status changes rather than waiting until the battery percantage changes.

I've also added more comments as requested by Barry Smile
powerapplet_tray.c.gz
Description  Updated version of powerapplet_tray.c
gz

 Download 
Filename  powerapplet_tray.c.gz 
Filesize  2.95 KB 
Downloaded  27 Time(s) 
Back to top
View user's profile Send private message Visit poster's website 
scsijon

Joined: 23 May 2007
Posts: 1531
Location: the australian mallee

PostPosted: Sat 26 Oct 2019, 21:15    Post subject: pyro 1.2.7  

Doing some pyro testing:

I notice that libnotify and the GDBUS are erroring at startup.

Errors appearing are:

(nm-applet:2938): libnotify-WARNING **: Failed to connect to proxy

(nm-applet:2938): nm-applet-WARNING **: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

The second error also re-appears in a slightly different form against ModemManager rather than GDBUS when shutting down.

And a little note to anyone using Firefox, it's now up to 70.0, please update as soon as possible, there's quite a number of fixes and things that make it worthwhile.
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 9069
Location: Perth, Western Australia

PostPosted: Sun 27 Oct 2019, 05:47    Post subject: Re: Battery app not updating.  

rooftop wrote:
I've made another small change to the battery app so that the icon will update immediately (well, within 15 seconds anyway) when the charging status changes rather than waiting until the battery percantage changes.

I've also added more comments as requested by Barry Smile


Thanks very much for looking into that! I have downloaded your code, keen to try it.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 9069
Location: Perth, Western Australia

PostPosted: Sun 27 Oct 2019, 05:54    Post subject: Re: pyro 1.2.7  

scsijon wrote:
Doing some pyro testing:

I notice that libnotify and the GDBUS are erroring at startup.

Errors appearing are:

(nm-applet:2938): libnotify-WARNING **: Failed to connect to proxy

(nm-applet:2938): nm-applet-WARNING **: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

The second error also re-appears in a slightly different form against ModemManager rather than GDBUS when shutting down.

And a little note to anyone using Firefox, it's now up to 70.0, please update as soon as possible, there's quite a number of fixes and things that make it worthwhile.


This is only a warning, not an error. In Buster, you will see a popup message whenever network-manager-applet does something, such as achieve a network connection. Pyro doesn't have these popups.

This is because Pyro doesn't have a notify daemon to present messages as popups. There are many notification daemons to choose from, a list is here:

https://wiki.archlinux.org/index.php/Desktop_notifications

Buster is using 'notification daemon':

https://github.com/GNOME/notification-daemon

If this is installed in Pyro, then you should get the popups and those warnings will go away.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 9069
Location: Perth, Western Australia

PostPosted: Sun 27 Oct 2019, 06:11    Post subject:  

A report on the updated xorg intel driver in Pyro 1.2.7.

I have Pyro installed to the hard drive of my laptop, Acer Aspire1 model A114-31-C014, completely removed Win10.

I did the upgrade thing, replacing the files vmlinuz, easy.sfs and initrd, and no problem with the upgrade.

However, I did notice one thing. I think, though not 100% certain if my memory is correct, that Xorg chose the 'modesetting' driver before. Now it is choosing the 'intel' driver.

The 'intel' driver is the very latest from github. The last official release of the xorg intel driver was 2014, so it is recommended to use a later one from github. But, it is still considered to be flakey, and some distros no longer use the intel driver, instead use the modestting driver for intel graphics GPU.

Right, so my laptop... yesterday was compiling seamonkey, 2.49.5 again, and the desktop froze. Did a hard reboot, attempted compile again, after sometime, froze again.

Hard reboot, exited from X to the commandline, ran "xorgwizard", and it stated the using "sna" acceleration for the intel driver, which can be troublesome, and can change to the older "uxa" acceleration ...which I did, and was able to compile seamonkey.

So, if anyone else has this issue, that might be your fix.

Or, you can run xorgwizard and change to the modesetting driver.

Instead of running xorgwizard, if you go to /etc/X11/xorg.conf.d, you will see file '20-intel-uxa.condDISABLED' that you can rename to enable it, then restart X.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
lp-dolittle

Joined: 25 Apr 2016
Posts: 112

PostPosted: Sun 27 Oct 2019, 07:58    Post subject: running easyOS totally in RAM
Subject description: tom22251 method
 

@ tom22251

Hi Tom,

unfortunately, all my attempts at configuring an external drive (hard drive) according to your detailed instructions failed so far. The drive has a fat32 partition (sdb1; larger than 1 GB, labelled LINUX, boot-flag set) apart from sdb2 (ext3; containing the Folders E-216 and SAVE).
I replaced the 1. 'code' by your corrected variant, and all coding sections were copied to sakura where they were executed automatically.
Alas, booting does not work. I also tried to leave out the last step, assuming that I possibly had created and applied the 'updt.sh' script in a mistaken manner and that the drive without that step would boot into the original, pristine version, but booting failed with the same error message.

I will continue rethinking my procedure ... and I would not like to waste your time overly. As soon as I will succeed - if at all -, you will get feedback.

kind regards, and thank you very much for all your support

Jürg
Back to top
View user's profile Send private message 
illiapoplawski

Joined: 22 Oct 2019
Posts: 3

PostPosted: Sun 27 Oct 2019, 11:30    Post subject:  

BarryK wrote:
A report on the updated xorg intel driver in Pyro 1.2.7.

I have Pyro installed to the hard drive of my laptop, Acer Aspire1 model A114-31-C014, completely removed Win10.

I did the upgrade thing, replacing the files vmlinuz, easy.sfs and initrd, and no problem with the upgrade.

However, I did notice one thing. I think, though not 100% certain if my memory is correct, that Xorg chose the 'modesetting' driver before. Now it is choosing the 'intel' driver.

The 'intel' driver is the very latest from github. The last official release of the xorg intel driver was 2014, so it is recommended to use a later one from github. But, it is still considered to be flakey, and some distros no longer use the intel driver, instead use the modestting driver for intel graphics GPU.

Right, so my laptop... yesterday was compiling seamonkey, 2.49.5 again, and the desktop froze. Did a hard reboot, attempted compile again, after sometime, froze again.

Hard reboot, exited from X to the commandline, ran "xorgwizard", and it stated the using "sna" acceleration for the intel driver, which can be troublesome, and can change to the older "uxa" acceleration ...which I did, and was able to compile seamonkey.

So, if anyone else has this issue, that might be your fix.

Or, you can run xorgwizard and change to the modesetting driver.

Instead of running xorgwizard, if you go to /etc/X11/xorg.conf.d, you will see file '20-intel-uxa.condDISABLED' that you can rename to enable it, then restart X.


Running xorgwizard and setting the modesetting driver fixed my issues that I was mentioning before regarding starting with xwin. Thank you for your help @BarryK
Back to top
View user's profile Send private message 
scsijon

Joined: 23 May 2007
Posts: 1531
Location: the australian mallee

PostPosted: Sun 27 Oct 2019, 20:07    Post subject: Re: pyro 1.2.7  

BarryK wrote:
scsijon wrote:
Doing some pyro testing:

I notice that libnotify and the GDBUS are erroring at startup.

Errors appearing are:

(nm-applet:2938): libnotify-WARNING **: Failed to connect to proxy

(nm-applet:2938): nm-applet-WARNING **: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

The second error also re-appears in a slightly different form against ModemManager rather than GDBUS when shutting down.

And a little note to anyone using Firefox, it's now up to 70.0, please update as soon as possible, there's quite a number of fixes and things that make it worthwhile.


This is only a warning, not an error. In Buster, you will see a popup message whenever network-manager-applet does something, such as achieve a network connection. Pyro doesn't have these popups.

This is because Pyro doesn't have a notify daemon to present messages as popups. There are many notification daemons to choose from, a list is here:

https://wiki.archlinux.org/index.php/Desktop_notifications

Buster is using 'notification daemon':

https://github.com/GNOME/notification-daemon

If this is installed in Pyro, then you should get the popups and those warnings will go away.


I know, I was wondering in this case why then they were appearing on the screen as if they were serious problems, rather than be in the approporiate startup log file instead.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 130 of 133 [1994 Posts]   Goto page: Previous 1, 2, 3, ..., 128, 129, 130, 131, 132, 133 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
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.1164s ][ Queries: 13 (0.0487s) ][ GZIP on ]