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, 00:16
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 129 of 133 [1994 Posts]   Goto page: Previous 1, 2, 3, ..., 127, 128, 129, 130, 131, 132, 133 Next
Author Message
Sage

Joined: 04 Oct 2005
Posts: 5498
Location: GB

PostPosted: Tue 22 Oct 2019, 03:07    Post subject:  

Many thanks for prompt response, Barry.
Sound: scsijon may not be correct. For the last few versions, the default sound has been set at 60%. This is far too low to hear the feeble output on diddy-little speakers in many laptops and certainly inbuilt speakers in monitors; better set @90% and turn it down if working? It is really helpful when testing kit to know whether sound is working at first boot, not least because sound settings cause so much angst amongst less well-informed users!
.isos always well appreciated. (Ha! my bad - didn't expect to look under the "legacy" listing. This is going to help at least one of my present colleagues trying to migrate but having fairly ancient kit. Will also save some unused CD-Rs languishing beside my desk from even more landfill. ).
As for Qsync, I like to have it running before completing the initial setup and why slow running of SM causes me grief - it's the first thing I want to check on defective machines, especially from rogue operators! And there' a lot of those, defecting (or wishing to...) from the devil's OS.
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: Tue 22 Oct 2019, 11:25    Post subject:  

Terry H wrote:
scsijon wrote:
Terry H wrote:
@scsijon thanks for the response. Screen capture using screeny with the browser in Full screen mode is also distorted. Screen resolution is 1366 X 768. No problem for the very few screen captures I may do, i'll use TAS.


Interesting, it's not happening for me in pyro 1.2.7 with Screeny in both the inbuilt Seamonkey and installed Firefox (69.0.3). Is there anything in /tmp/xerrs.log after a capture that could help track it down? you could also try reducing your browser to 1024x768 (a standard size) and try capturing that, maybe there is a driver problem in widescreen.


Sorry, just saw this, I've been watching election results. It's late here now. I'll check some more tomorrow.


I checked xerrs.log, which gave me nothing to go on. I have no idea what the diff output shown below means. At present I don't consider it worth pursuing further.


Code:
# diff /home/personal/xerrs.log /tmp/xerrs.log
61a62,63
> xwdtopnm: writing PPM file
> EXIT="Exit on timeout"
#
 
Back to top
View user's profile Send private message 
illiapoplawski

Joined: 22 Oct 2019
Posts: 3

PostPosted: Tue 22 Oct 2019, 17:33    Post subject: Graphics Issue Pyro 1.2.7
Subject description: Graphics not working since drivers update in pyro 1.2.7
 

Running Pyro 1.2.5 had no issues however after upgrading to 1.2.7 the error in the attached image is given (written below).

"expr: warning: '^/dev/tty[0-90\+$': using '^' as the first character of a basic regular expression is not portable; it is ignored
/usr/bin/startx: line 169: /usr/bin/mcookie: No such file or directory
Couldn't create cookie"

I created a clean usb install and error persisted then reverted back to a clean pyro 1.2.5 and graphics work again. Running on an acer aspire e1-522-3884 with AMD Radeon HD 8240 graphics
IMG_20191022_160840.jpg
Description 
jpg

 Download 
Filename  IMG_20191022_160840.jpg 
Filesize  243.01 KB 
Downloaded  29 Time(s) 
Back to top
View user's profile Send private message 
BarryK
Puppy Master


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

PostPosted: Tue 22 Oct 2019, 22:57    Post subject: Re: PPM  

scsijon wrote:
I notice that the Petget Package Manager ?isn't downloading to the right spot. It says it's downloading to /root, shouldn't it now be downloading to the $/file/downloads, especially when your working in a container. It use to download to /root/Downloads.


Some apps, such as SeaMonkey, default to download to /home/downloads

The PPM though, most people would choose to install packages, not just download them. When installed, they are kept in /audit/packages

Note, there is no /file folder, that was for Quirky only.

_________________
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: Wed 23 Oct 2019, 02:19    Post subject:  

BarryK wrote:
scsijon wrote:
Terry H wrote:
In attempting to get a screen capture of the flashing icon change mentioned in previous post I attempted to get screenshots using screeny. I set to capture full screen to show the tray. When I viewed the output the images, they are all tilted and shown in monochrome. Screen capture of window only is OK, it is in colour and not distorted.

Dell laptop Core i5- 5200U processor.


Terry,

Try again with the browser set in full window size, it should be ok then, I wrote about this fix earlier but for referance, it seems that screeny doesn't like odd sizes, if you set it to one of the video drivers resolution matrix's it usually saves correctly, it's just if you try a non-matrix it fails. ie 1280x1024/960, 1680x1050, 1024x768 should be ok, setting it for a part screen will fail unless it's an acceptable resolution to your video card.


There was a permanent fix posted to the Puppy forum awhile back, but I haven't chased it up. Maybe I should just remove Screeny, as Take a Shot does a pretty good job.


Just did a search of the forum, yes, the distortion problem was identified a couple of years ago, and fixed:

http://murga-linux.com/puppy/viewtopic.php?t=76204&start=45

It is caused by the 'xwdtopnm' utility in the 'netpbm' package.

Quirky and Easy use a very old version of netpbm, as later versions were found to break something else, but I don't recall what.

OK, I will test the latest netpbm, and look at all scripts that use the netpbm utilities, see if any of them become broken.

If yes, then I could stay with the old netpbm and just use the latest xwdtopnm (with the libnetpbm library linked statically).

_________________
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: Wed 23 Oct 2019, 02:31    Post subject: Re: Graphics Issue Pyro 1.2.7
Subject description: Graphics not working since drivers update in pyro 1.2.7
 

illiapoplawski wrote:
Running Pyro 1.2.5 had no issues however after upgrading to 1.2.7 the error in the attached image is given (written below).

"expr: warning: '^/dev/tty[0-90\+$': using '^' as the first character of a basic regular expression is not portable; it is ignored
/usr/bin/startx: line 169: /usr/bin/mcookie: No such file or directory
Couldn't create cookie"

I created a clean usb install and error persisted then reverted back to a clean pyro 1.2.5 and graphics work again. Running on an acer aspire e1-522-3884 with AMD Radeon HD 8240 graphics


That's interesting. Start X by running 'xwin', not 'startx':

Code:
# xwin


It is interesting because back in the Quirky and Puppy days I had /usr/bin/startx as a symlink to xwin. However, now it is a script that some package has installed. Right, I need to get that restored to a symlink.

If X will not start and drops you back to the commandline, look in /var/log/Xorg.0.log see if anything obvious in there.

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

Joined: 22 Oct 2019
Posts: 3

PostPosted: Wed 23 Oct 2019, 15:14    Post subject: Re: Graphics Issue Pyro 1.2.7
Subject description: Graphics not working since drivers update in pyro 1.2.7
 

BarryK wrote:
illiapoplawski wrote:
Running Pyro 1.2.5 had no issues however after upgrading to 1.2.7 the error in the attached image is given (written below).

"expr: warning: '^/dev/tty[0-90\+$': using '^' as the first character of a basic regular expression is not portable; it is ignored
/usr/bin/startx: line 169: /usr/bin/mcookie: No such file or directory
Couldn't create cookie"

I created a clean usb install and error persisted then reverted back to a clean pyro 1.2.5 and graphics work again. Running on an acer aspire e1-522-3884 with AMD Radeon HD 8240 graphics


That's interesting. Start X by running 'xwin', not 'startx':

Code:
# xwin


It is interesting because back in the Quirky and Puppy days I had /usr/bin/startx as a symlink to xwin. However, now it is a script that some package has installed. Right, I need to get that restored to a symlink.

If X will not start and drops you back to the commandline, look in /var/log/Xorg.0.log see if anything obvious in there.


Tried starting with xwin and it blocks on a non blinking white cursor on a black screen that i can't move away from except for force restarting the laptop. When going into /var/log after restarting there are no Xorg logs to be found to help find the source of the issue. Tried with Buster 2.1.7 and i have no issues with graphics.
Back to top
View user's profile Send private message 
gcav


Joined: 25 May 2012
Posts: 81
Location: Ontario

PostPosted: Wed 23 Oct 2019, 19:58    Post subject: Dosbox.  

Hi all.. playing around with dosbox under EasyBuster from both downloaded and compiled dosboxes I get the following:

[/home]$ dosbox
DOSBox version 0.74-3
Copyright 2002-2019 DOSBox Team, published under GNU GPL.
---
**
GLib:ERROR:../../../glib/ghash.c:377:g_hash_table_lookup_node: assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count, 0))
Aborted (core dumped)


Any hints before going down the rabbit hole?..

gcav

ps: as someone mentioned before the battery tray app is not updating.


--stack trace for the curious---
GNU DDD 3.3.12 (x86_64-pc-linux-gnu), by Dorothea LReading symbols from /usr/local/bin/dosbox...done.
[New LWP 7075]
[New LWP 7074]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `dosbox'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fe8a5f127bb in raise () from /lib/libc.so.6
[Current thread is 1 (Thread 0x7fe8a45cd700 (LWP 7075))]
(gdb) where
#0 0x00007fe8a5f127bb in raise () from /lib/libc.so.6
#1 0x00007fe8a5efd535 in abort () from /lib/libc.so.6
#2 0x00007fe8a55b5dc3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007fe8a560f67a in g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007fe8a55d5cd6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007fe8a5ac0244 in pa_stream_unref () from /usr/lib/libpulse.so.0
#6 0x00007fe8a5abdb93 in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
#7 0x00007fe8a5abe0aa in pa_mainloop_run () from /usr/lib/libpulse.so.0
#8 0x00007fe8a5ac0e23 in ?? () from /usr/lib/libpulse.so.0
#9 0x00007fe8a688dfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007fe8a5fd44cf in clone () from /lib/libc.so.6
(gdb)
Back to top
View user's profile Send private message 
scsijon

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

PostPosted: Wed 23 Oct 2019, 21:25    Post subject: Re: Dosbox.  

gcav wrote:
Hi all.. playing around with dosbox under EasyBuster from both downloaded and compiled dosboxes I get the following:

[/home]$ dosbox
DOSBox version 0.74-3
Copyright 2002-2019 DOSBox Team, published under GNU GPL.
---
**
GLib:ERROR:../../../glib/ghash.c:377:g_hash_table_lookup_node: assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count, 0))
Aborted (core dumped)


Any hints before going down the rabbit hole?..

gcav

ps: as someone mentioned before the battery tray app is not updating.


--stack trace for the curious---
GNU DDD 3.3.12 (x86_64-pc-linux-gnu), by Dorothea LReading symbols from /usr/local/bin/dosbox...done.
[New LWP 7075]
[New LWP 7074]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `dosbox'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fe8a5f127bb in raise () from /lib/libc.so.6
[Current thread is 1 (Thread 0x7fe8a45cd700 (LWP 7075))]
(gdb) where
#0 0x00007fe8a5f127bb in raise () from /lib/libc.so.6
#1 0x00007fe8a5efd535 in abort () from /lib/libc.so.6
#2 0x00007fe8a55b5dc3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007fe8a560f67a in g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007fe8a55d5cd6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007fe8a5ac0244 in pa_stream_unref () from /usr/lib/libpulse.so.0
#6 0x00007fe8a5abdb93 in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
#7 0x00007fe8a5abe0aa in pa_mainloop_run () from /usr/lib/libpulse.so.0
#8 0x00007fe8a5ac0e23 in ?? () from /usr/lib/libpulse.so.0
#9 0x00007fe8a688dfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007fe8a5fd44cf in clone () from /lib/libc.so.6
(gdb)


There are a small number of error reports relating to this, most seem to blame libevent versions being mixed when building glib packages (something related to libevent versions being different, even when close numbers is mentioned in some of them). Mind you there are quite a few fault reports relating to the g_hash_table~ and all complain about glib / glibc version non-compatability for previously compiled packages. Even Ubuntu was caught with v17.10.

Doubt this helped, but your apparently not alone.
Back to top
View user's profile Send private message Visit poster's website 
tom22251


Joined: 08 Oct 2019
Posts: 10

PostPosted: Thu 24 Oct 2019, 01:38    Post subject: running easyOS in RAM
Subject description: reply to lp-dolittle
 

Hi lp-dolittle,

apologies for not getting back sooner, I was (still is)
under the weather.
That external ext3 drive should be exelent, all you need
is a boot loader on it and setting the bootflag on, with gparted.
I recommend extlinux which is
what I use in the past 8-10 years. It is the simplest and
most reliable in my opinion.

So you already have the EASY_216 folder with the 3 files
inside. Now you need a BOOt folder where you install the
extlinux loader. Type in the terminal:
Code:
extlinux --install /mnt/sda1/BOOT


I have only one USB drive (no harddrives) that's why sda1,
you of course should substitute sda1 with your own drives
name: sdb1 or sdc1, whatever.

That's it, you will have 1- or 2 files in the BOOT folder named ldlinux.sys
and some times an other one too, called ldlinux.c32.
Now the final thing: open a new text file and name it
extlinux.conf. This is where you write your configuration parameters.


Code:


default 1
prompt 1
timeout 33333

say press 1 for Easy-216
say press 2 for Easy-215


label 1
kernel /EASY_216/vmlinuz
initrd /EASY_216/initrd
append  rw vga=792

label 2
kernel /EASY_215/vmlinuz
initrd /EASY_215/initrd
append  rw vga=792




explanation: timeout 33333 is the maximum you can
set and is more then an hour if I remember well.
I usually have sometime more then 10 different
puppy versions on the same drive, so I like to have plenty
of time to decide which one to run.


Now, regarding UEFI you indeed need 2 partitions,
where the boot partition has to be fat32, with the
boot flag on. Copy the EFI folder from Barry's easy-2.1.6-amd64.img file to this partition.
Open up EFI, inside there is BOOT, where you edit only
the file refind.conf :

Code:

timeout 33333
scanfor manual

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

 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"
}


Thats all, it should boot nicely on a
UEFI machine, and in RAM only. You can unplug
the USB drive and plug it in again when you want
to save something, to the ext3 partition.

Let me know if you need more explanation.
Be well,

Tom
[/b]
Back to top
View user's profile Send private message 
lp-dolittle

Joined: 25 Apr 2016
Posts: 112

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

@ tom22251

Hi Tom,

thank you for the additional support!

It will take me some time to fully digest the detailed instructions.

In a first attempt, I will try to figure out your 'starting configuration'. Running EasyOS from a usb-stick which is prepared according to Barry's instructions and then configuring a second usb-stick according to your method?

As far as I can see, this second usb-stick cannot simply be a sdx-drive which has only one ext3 partition (labelled LINUX). I need to ponder on when and how you create the UEFI-aware fat boot-partition.

Don't feel obliged to respond quickly. I will let you know the result of my attempts.

kind regards and thanks again

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

Joined: 04 Oct 2005
Posts: 5498
Location: GB

PostPosted: Thu 24 Oct 2019, 05:20    Post subject:  

Wow! Am I happy. These .iso s on CD-R are oodles faster and with write-once media, ultra secure. Goodbye USB sticks and all that fiddle-faddle with two partitions & co. Muchas Garcias, Barry.
Back to top
View user's profile Send private message 
scsijon

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

PostPosted: Thu 24 Oct 2019, 05:56    Post subject:  

Sage wrote:
Wow! Am I happy. These .iso s on CD-R are oodles faster and with write-once media, ultra secure. Goodbye USB sticks and all that fiddle-faddle with two partitions & co. Muchas Garcias, Barry.


If your cd/dvd drive is a dual layer type, as a lot are nowadays, you can also get double layer dvd's that are write-once on the main level and rewrite on the second level, V'b'n have them so they are not the cheapest out, but I haven't had any from the 20pack I got a couple of years ago fail yet. I just formatted the second layer as it's own partition and mapped it across in /etc/fstab. That's 4.5g ro +4.5g rw of space to play with. I did rebuild my iso to have the devx, firefox, buiulding stuff like woofq and a couple of my favorite games in the iso so I wasn't wasting too much space in the first partition. Much better than dual layer rewrite discs for cost too.
Back to top
View user's profile Send private message Visit poster's website 
belham2

Joined: 15 Aug 2016
Posts: 1700

PostPosted: Thu 24 Oct 2019, 07:24    Post subject:  

Hi Barry,

Hope you're well and in good health & spirits.

Updated to 2.1.7 Buster EasyOS from 2.1.6, went very smooth/easy. All seems good.

Found one little thing, not real important, but if you get a chance maybe could look at it: shouldn't urxvt control (if you set it up & apply it like I did in below pic)..shouldn't it control what rxvt will look like when opening rxvt up?

Here's a pic showing where I can't change rxvt's appearance at all (or am I incorrectly forgetting what urxvt controls??):
rxvt-and-urxvt.jpg
 Description   
 Filesize   61.87 KB
 Viewed   249 Time(s)

rxvt-and-urxvt.jpg

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

Joined: 04 Oct 2005
Posts: 5498
Location: GB

PostPosted: Thu 24 Oct 2019, 08:30    Post subject:  

Many thanks for those interesting comments, scijon.
Yes, I do, and use, all of those things. I usually use DVD-RW for testing the OS and overwrite them when the next version arrives. These are not what I need and use for HW testing, though. I have a stack of CD-R which have been gifted over the years. These are perfect for machine testing and repair - I never want to save or write to them - quite the opposite - I want them closed/finito! Of course, one can select the option to leave them 'open' so that additional tracks can be added - not good for my purposes. Furthermore, the compact size of Puppies and their various manifestations provide 'light' in the sense of small, size but fully operational OS. [BK's original Puppy was ~29Mb - then John came along with a 50Mb 'credit card' size version, ideal for the top/shirt pocket. Sadly those media are no longer available thanks to the entire field being caught up in the WIntel bloatware race initiated by Redmond many years ago.]
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 129 of 133 [1994 Posts]   Goto page: Previous 1, 2, 3, ..., 127, 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.1050s ][ Queries: 12 (0.0324s) ][ GZIP on ]