Posts by Ron

Ron · Other Issues

Head_on_a_Stick wrote:

Ouch. Perhaps I was wrong about that broken POS software...

So the RAM is bad and needs replacing, I presume. I'll see if I can get it done tomorrow. One question, how come the bad RAM is only affecting the browsers and nothing else?

Ron · Other Issues

So I installed memtest86+ and ran it. How long is it supposed to run? I cut it off after 2 hours and 46 minutes. I took three pics as it ran, one at 40 minutes, the second at 65 minutes, and the last at 2 hours and 46 minutes. Here they are. It doesn't look good, but I don't know how to decipher what it means:

Ron · Other Issues

Okay, now we're getting somewhere. There are a lot of failures. Are they meaningless, or are they a problem?

ron@ron:~$ sudo memtester 1800 5
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 1800MB (1887436800 bytes)
got  1800MB (1887436800 bytes), trying mlock ...locked.
Loop 1/5:
  Stuck Address       : testing   2FAILURE: possible bad address line at offset 0x3601ff60.
Skipping to next test...
  Random Value        : ok
  Compare XOR         : ok
FAILURE: 0x81e016f420806686 != 0x81e016f420846686 at offset 0x00ac6f50.
  Compare SUB         :   Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : testing   8FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x14cdcb28.
  Block Sequential    : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x2527eb28.
FAILURE: 0x00040000 != 0x00000000 at offset 0x351a9b38.
  Checkerboard        : testing   4FAILURE: 0x5555555555555555 != 0x5555555555515555 at offset 0x168f27e0.
  Bit Spread          : testing 111FAILURE: 0xfffffffffffaffff != 0xfffffffffffeffff at offset 0x027e6b28.
  Bit Flip            : testing   0FAILURE: 0x00040001 != 0x00000001 at offset 0x351a9b38.
  Walking Ones        : ok         
  Walking Zeroes      : testing   0FAILURE: 0x00040001 != 0x00000001 at offset 0x351a9b38.
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 2/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x67b5fb38.
Skipping to next test...
  Random Value        : ok
  Compare XOR         : ok
FAILURE: 0x210a71e31169926a != 0x210a71e3116d926a at offset 0x024f8b28.
FAILURE: 0x210a71e31169926a != 0x210a71e3116d926a at offset 0x0e7d4b28.
  Compare SUB         :   Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x027fab28.
  Block Sequential    : testing  16FAILURE: 0x1010101010101010 != 0x1010101010141010 at offset 0x00ac6b28.
  Checkerboard        : testing  17FAILURE: 0xaaaaaaaaaaaaaaaa != 0xaaaaaaaaaaaeaaaa at offset 0x020b6f50.
  Bit Spread          : testing   0FAILURE: 0x00000005 != 0x00040005 at offset 0x0eabcf50.
FAILURE: 0x00000005 != 0x00040005 at offset 0x2f660f50.
  Bit Flip            : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x12856b28.
  Walking Ones        : testing 109FAILURE: 0xfffffffffffbffff != 0xffffffffffffffff at offset 0x14cdcb28.
  Walking Zeroes      : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x0eabcb28.
FAILURE: 0x00000001 != 0x00040001 at offset 0x2f642f50.
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 3/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x3abe5b38.
Skipping to next test...
  Random Value        : ok
FAILURE: 0x849452d58100b80b != 0x849452d58104b80b at offset 0x027e6b28.
  Compare XOR         : FAILURE: 0xe030724480962f6d != 0xe030724480922f6d at offset 0x323bfb38.
  Compare SUB         :   Compare MUL         : ok
FAILURE: 0x00000001 != 0x00040001 at offset 0x027e6b28.
  Compare DIV         :   Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : testing   1FAILURE: 0x00000000 != 0x00040000 at offset 0x2f660f50.
  Block Sequential    : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x073d6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x2f67eb28.
  Checkerboard        : testing   4FAILURE: 0x5555555555555555 != 0x5555555555515555 at offset 0x12856820.
  Bit Spread          : testing  19FAILURE: 0x00280000 != 0x002c0000 at offset 0x2d2f8f50.
  Bit Flip            : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x0e7d4b28.
  Walking Ones        : ok         
  Walking Zeroes      : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x0e814f50.
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 4/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x32509f60.
Skipping to next test...
  Random Value        : ok
  Compare XOR         : ok
FAILURE: 0x58011009044c94b4 != 0x58011009044894b4 at offset 0x351a9b38.
  Compare SUB         : FAILURE: 0xf81ce9a8d028b00f != 0xf81ce9a8d02cb00f at offset 0x12856f50.
FAILURE: 0xf81ce9a8d028b00f != 0xf81ce9a8d02cb00f at offset 0x2f67eb28.
  Compare MUL         :   Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
FAILURE: 0xcefd860afce107b3 != 0xcefd860afce507b3 at offset 0x0d134b28.
FAILURE: 0xcefd860afdd85838 != 0xcefd860afddc5838 at offset 0x14cdcf50.
  Sequential Increment:   Solid Bits          : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x0d0f6b28.
FAILURE: 0x00040000 != 0x00000000 at offset 0x351a9b38.
  Block Sequential    : testing   8FAILURE: 0x808080808080808 != 0x8080808080c0808 at offset 0x0e814b28.
  Checkerboard        : testing   4FAILURE: 0x5555555555555555 != 0x5555555555515555 at offset 0x027e6820.
  Bit Spread          : testing   0FAILURE: 0x00000005 != 0x00040005 at offset 0x14cdcf50.
  Bit Flip            : testing   7FAILURE: 0x00040001 != 0x00000001 at offset 0x32661f60.
  Walking Ones        : ok         
  Walking Zeroes      : testing   0FAILURE: 0x00040001 != 0x00000001 at offset 0x351a9b38.
  8-bit Writes        : ok
  16-bit Writes       : -FAILURE: 0x768fbe9efbf3a928 != 0x768fbe9efbf7a928 at offset 0x0eabcf50.

Loop 5/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x3abe5b38.
Skipping to next test...
  Random Value        : ok
FAILURE: 0xaa4c2f2dd8405405 != 0xaa4c2f2dd8445405 at offset 0x23486f50.
  Compare XOR         :   Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
FAILURE: 0xdaa76f56fa99a191 != 0xdaa76f56fa9da191 at offset 0x14cdcb28.
  Sequential Increment:   Solid Bits          : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x12856b28.
  Block Sequential    : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x00ac6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x14cdcb28.
FAILURE: 0x00040000 != 0x00000000 at offset 0x352a9b38.
  Checkerboard        : testing   4FAILURE: 0xaaaaaaaaaaaaaaaa != 0xaaaaaaaaaaaeaaaa at offset 0x027e6b28.
  Bit Spread          : testing   0FAILURE: 0x00000005 != 0x00040005 at offset 0x0eabcf50.
FAILURE: 0x00000005 != 0x00040005 at offset 0x1528cf50.
  Bit Flip            : testing   2FAILURE: 0x00000001 != 0x00040001 at offset 0x12856b28.
  Walking Ones        : ok         
  Walking Zeroes      : ok         
  8-bit Writes        : ok
  16-bit Writes       : ok

Done.
ron@ron:~$ echo $?
6

Ron · Other Issues

Is the below correct? From what I've read it should return "0" but I got a "1".

ron@ron:~$ sudo memtester free 5
[sudo] password for ron: 
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000

Usage: memtester [-p physaddrbase [-d device]] <mem>[B|K|M|G] [loops]
ron@ron:~$ echo $?
1

Ron · Other Issues

andyprough wrote:

If Ron is using the .deb packages, he may want to try switching to the tarball from the website.

I was using the tarball, and a few days ago switched to Steve's .deb. It doesn't appear to make a difference. I'm beginning to wonder if I have bad RAM, but I'm not knowledgeable of myself to know whether that's the case or not.

andyprough wrote:

You'll be relieved to hear that "that fat **** Tobin" is gone from the forum by the way. His millions of adoring fans are in mourning.

Actually, that's not true. While his last post was Dec 22, he was in fact active on the forum just today.

And at risk of repeating myself, here's the results of a memory test I did, and of which I don't know how to decipher:

ron@ron:~$ sudo memtester 3700 5
[sudo] password for ron:
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3700MB (3879731200 bytes)
got  3700MB (3879731200 bytes), trying mlock ...Killed
ron@ron:~$ echo $?
137

Ron · Other Issues

Head_on_a_Stick wrote:

Can you share the full error?

That's all the terminal said. Is there a log somewhere that has documented this?

Head_on_a_Stick wrote:

You can generate a stack trace for them by following https://wiki.debian.org/HowToGetABacktrace but I don't know about the relevant debug symbols. Ask on their forums.

I see this link mentions gdb. In my searches about this problem I came across this app being recommended. Honestly though I'm getting tired of this issue.

I should add I also did a memory test (during which I had Pale Moon opened and during the test it crashed). Here's the results, and I have no idea what 137 means:

ron@ron:~$ sudo memtester 3700 5
[sudo] password for ron:
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3700MB (3879731200 bytes)
got  3700MB (3879731200 bytes), trying mlock ...Killed
ron@ron:~$ echo $?
137

Ron · Other Issues

I was able to get a crash after opening Pale Moon in via the terminal. After the crash the terminal said Segmentation Fault. Question: would adding more RAM fix this, or is the problem deeper than merely adding RAM? I have 4gigs RAM.

Ron · Other Issues

golinux wrote:

That needed to be done long before Devuan existed. That doesn't mean that it wasn't intentional but not for reasons you might be imagining . . .

I don't know . . . I have a very vivid (and crazy) imagination at times.

Ron · Other Issues

Question: since this has worked on older versions of Devuan, and since this file did not exist on my current system, does this mean that Devuan or Debian has deliberately made the choice to have this disabled?

Ron · Other Issues

Thanks HoaS (again). It works now on an unfrozen system. Waiting for another freeze to see if it works then (I'm assuming it will).

Ron · Other Issues

Along the lines of my other recent post about browser crashes, I had a computer freeze-up while browsing the web, and for the first time Alt + SysRq then r e i s u b did not reboot the system. It stayed frozen; had to do a hard shut down. This has now happened more than once. Any idea what why the reboot didn't work?

Ron · Other Issues

After playing a handful of youtube videos on Chromium it hasn't crashed at all yet, unlike Vivaldi where I'd get crashes on just about every other video (and sometimes multiple crashes on the same video). FTR, Chromium did crash on me once, but there were no videos playing at the time.

So, I'm guessing there really isn't anything that can be done about this? I'd really prefer using Vivaldi over Chromium for youtube watching.

Ron · Other Issues

golinux wrote:

I thought uBlock Origin did that automatically. Maybe I'm missing something . . .

I think it does. 🤔

Ron · Other Issues

Thanks for the link HoaS. I run uBlock Origin in all my browsers . . . is the add-on you linked to still necessary?

Ron · Other Issues

In going through Chromium's settings I came across something that looks like a typical "gooble-ism" spyware, the setting Continue running background apps when Chromium is closed in Settings >> Advanced >> System. Anybody have any idea what in the world this is? Why would I want background apps (apparently for Chromium??) to continue running when I close the browser? Of course I unchecked it. Any input on what this is and does would be appreciated.

Ron · Other Issues

Head_on_a_Stick wrote:

Try the three vertically-placed dots at the top-right, just underneath the window close button.

Looked all through there. It doesn't look like Chromium has an option for a menu bar, which doesn't surprise me.
Anyway, so far, no crashes on it; but haven't tested long enough yet to my satisfaction.

If the problem is indeed PM and Vivaldi are using their own libraries, then the first question that comes to my mind is then why didn't I experience so many crashes when I was running Devuan 2.1 (i.e., the Miyo version based on 2.1)?

Ron · Other Issues

Head_on_a_Stick wrote:

So are those Steve Pusser's and Vivaldi's own .deb packages, respectively?
They both bundle their own libraries in flagrant violation of Debian policy[1] so I would advise trying a browser from the Devuan repositories instead. The firefox-esr package tends to stay up to date better than chromium so I would (and do) use that. Report back if that also crashes.
If an "official" browser remains stable then perhaps take your chances on the Pale Moon forums. If you do that then please share a link, I have some popcorn ready...

For Vivaldi, yes I use its own .deb packages, for Pale Moon I download the tarball direct off the Pale Moon's site, I don't use Steve's packages. I will download Chromium (I don't like FF lately) for testing purposes (only to test Youtube). Will report back here if I get crashes on it or not.

Note: installed Chromium as I was typing this. How to get a menu bar? I hate it already.

Ron · Other Issues

I've been getting a lot of browser crashes. Here's the details. I did not have this problem on Devuan 2, but I have it on Devuan 3, and now on Devuan 4 (this is all via Miyo) since day 1. It happens with both browsers I use. On Pale Moon, it mostly happens when I have a handful of yahoo news tabs opened; yahoo news stories usually have playing video. On Vivaldi, I get crashes when watching youtube videos. So I'm guessing it has something to do with videos being played, along with something that must have changed between Devuan 2 and 3/4. Below are my computer's specs. Any ideas what the problem is and if anything can be done about it?

System:
  Kernel: 5.10.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
    Desktop: MATE 1.24.1 Distro: Devuan GNU/Linux 4 (chimaera)
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A
    serial: <superuser required>
  Mobo: ASUSTeK model: H81M-C v: Rev X.0x serial: <superuser required>
    BIOS: American Megatrends v: 3602 date: 03/26/2018
CPU:
  Info: dual core model: Intel Pentium G3220 bits: 64 type: MCP arch: Haswell
    rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 2993 min/max: 800/3000 cores: 1: 2993 2: 2993
    bogomips: 11972
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0
  Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting
    unloaded: fbdev,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics (HSW GT1) v: 4.5 Mesa 20.3.5
    direct render: Yes
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Sound Server-1: ALSA v: k5.10.0-11-amd64 running: yes
  Sound Server-2: PulseAudio v: 14.2 running: yes
  Sound Server-3: PipeWire v: 0.3.19 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK H81M-C driver: r8169 v: kernel port: e000 bus-ID: 03:00.0
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 387.53 GiB used: 90.54 GiB (23.4%)
  ID-1: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB
  ID-2: /dev/sdb vendor: Seagate model: ST3160815AS size: 149.05 GiB
Partition:
  ID-1: / size: 233.66 GiB used: 5.9 GiB (2.5%) fs: ext4 dev: /dev/sda5
Swap:
  ID-1: swap-1 type: file size: 256 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 154 Uptime: 5h 24m Memory: 3.71 GiB used: 1.59 GiB (43.0%)
  Init: SysVinit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1597
  Shell: Bash v: 5.1.4 inxi: 3.3.12

Ron · Devuan Derivatives

Thanks MiyoLinux. That's got everything working as it should.

Ron · Devuan Derivatives

Hi Miyo, I installed your new upload of Miyo and the bootup works great. But one problem I'm having is this: to fix the major screen tearing I get in my browser, I always edit the compton.conf file from this:

backend = "xrender";
#backend = "glx";

to this:

#backend = "xrender";
backend = "glx";

However for some reason, this time this file doesn't exist. What can I do? (Yes I deleted picon and installed compton. Was that a mistake?)

Ron · Other Issues

Okay then. But the system should reflect that, like it did for ascii.

Ron · Other Issues

So then am I to assume that I really am on 3.1?

Ron · Other Issues

I have installed the Miyo version based on beowulf. When I hover over the start menu button on the panel, the pop-up says Devuan GNU/Linux 3 (beowulf). An inxi report also says version 3. However, this page here says the current version of beowulf is 3.1. When I was on ascii the pop-up would say 2.1 for ascii. According to Synaptic I'm up to date. So why isn't my system being upgraded to beowulf 3.1?

Ron · Other Issues

Once again, HoaS for the win! Thanks.

Ron · Other Issues

Head_on_a_Stick wrote:

Both versions will play the sound file until it ends (or until the script/command is interrupted with <ctrl>+c).

I'm sorry, I wasn't clear. What I want is for it to repeat the sound file until I tell it to stop repeating.

The officially official Devuan Forum!

#151 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-13 21:49:26

#152 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-13 19:11:50

#153 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 23:32:13

#154 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 22:02:18

#155 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 20:06:58

#156 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 17:45:54

#157 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 14:29:38

#158 Re: Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 18:20:34

#159 Re: Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 17:27:37

#160 Re: Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 13:55:24

#161 Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 02:56:19

#162 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-07 17:41:27

#163 Re: Other Issues » Weird option in Chromium settings » 2022-02-07 17:35:01

#164 Re: Other Issues » Weird option in Chromium settings » 2022-02-07 16:09:42

#165 Other Issues » Weird option in Chromium settings » 2022-02-07 14:44:33

#166 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-06 17:58:17

#167 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-06 14:11:43

#168 Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-05 19:18:31

#169 Re: Devuan Derivatives » [MiyoLinux] New Releases Uploaded » 2022-01-31 03:37:12

#170 Re: Devuan Derivatives » [MiyoLinux] New Releases Uploaded » 2022-01-31 01:49:30

#171 Re: Other Issues » Why isn't my beowulf being upgraded to 3.1? » 2022-01-21 17:43:42

#172 Re: Other Issues » Why isn't my beowulf being upgraded to 3.1? » 2022-01-21 15:51:36

#173 Other Issues » Why isn't my beowulf being upgraded to 3.1? » 2022-01-21 15:19:52

#174 Re: Other Issues » Suggestions for a good simple alarm clock/timer » 2022-01-19 21:14:19

#175 Re: Other Issues » Suggestions for a good simple alarm clock/timer » 2022-01-19 18:56:26

Board footer