Porteus-v5.0x86_64_bugs reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v5.0x86_64_bugs reports

Post#121 by Ed_P » 28 Aug 2022, 22:33

What cheatcode did you try?

Do you save changes?

What's the machine's clock set to?

Did you see this posting? [Solved] Date and Time setting not working (Post by hope #89445)
Ed

kultex
Black ninja
Black ninja
Posts: 71
Joined: 30 Dec 2015, 12:11
Distribution: Porteus 4.0 XFCE
Location: Austria

Porteus-v5.0x86_64_bugs reports

Post#122 by kultex » 29 Aug 2022, 11:09

thx Ed_P especially for the link....

very funny - another problem I have is power consumption - running Porteus 5.0 my battery is very quick empty - so I changed to windows this morning, to test.... coming back to porteus, the time was correct

1) my grub2
menuentry "Porteus-LXDE-v5.0-x86_64" {
set gfxpayload=keep
linux /boot/syslinux/vmlinuz changes=porteus timezone=Europe/Vienna kmap=at
initrd /boot/syslinux/initrd.xz
}

2) I have toubles to search the porteus forum with firefox - I get no search results - only an emty page - maybe the reason is - I have set firefox to very strong private security - I found a workaround - I installed netsurf - now I get search results very quick....

I will tell, if it stays now correct or if I have to use your link....

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#123 by Rava » 29 Aug 2022, 13:23

kultex wrote:
29 Aug 2022, 11:09
very funny - another problem I have is power consumption - running Porteus 5.0 my battery is very quick empty - so I changed to windows this morning, to test.... coming back to porteus, the time was correct
When the rechargeable battery gets older, it looses capacity, from 100% capacity it can go down to only 30% or even only 10%.
You need
There are system monitors that can tell you what the capacity of your battery is when it is said to be "fully loaded" since "fully loaded" not equals 100%.

usually the only solution to that is to buy a new battery… unless you can live with the reduced capacity, you have to figure it out what the real actual capacity is for yourself.

My tip is: when your power grid is stable, remove the battery when you have your notebook on power via the electric grid, the battery only suffers when it gets loaded even when it's already full.
You would risk a crash when your power grid collapses since then the notebook would switch off just like any other PC without uninterruptible power supply.
Cheers!
Yours Rava

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v5.0x86_64_bugs reports

Post#124 by Ed_P » 29 Aug 2022, 15:44

kultex wrote:
29 Aug 2022, 11:09
another problem I have is power consumption - running Porteus 5.0 my battery is very quick empty - so I changed to windows
Interesting. My system is the opposite. With Windows the battery lasts about 2 hrs, between charges, with Porteus 5.0 about 7 hrs.
Ed

kultex
Black ninja
Black ninja
Posts: 71
Joined: 30 Dec 2015, 12:11
Distribution: Porteus 4.0 XFCE
Location: Austria

Porteus-v5.0x86_64_bugs reports

Post#125 by kultex » 29 Aug 2022, 18:56

the battery seems to be ok - 92% of the new one...

Code: Select all

  upower -i /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          BAT1
  model:                G71C000L0110
  serial:               0
  power supply:         yes
  updated:              Mo 29 Aug 2022 20:48:44 (0 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       none
    energy:              17,692 Wh
    energy-empty:        0 Wh
    energy-full:         44,311 Wh
    energy-full-design:  47,88 Wh
    energy-rate:         6,976 W
    voltage:             11,4 V
    time to empty:       2,5 hours
    percentage:          39%
    capacity:            92,5459%
    technology:          lithium-ion
    icon-name:          'battery-good-symbolic'
  History (charge):
    1661798908	39,000	discharging
    1661798882	40,000	discharging
  History (rate):
    1661798924	6,976	unknown
    1661798901	7,023	discharging
working mode its ok, but suspend seems to be the porblem - the problem is I have no time at the momet to check... I will report as soon as I know more......

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#126 by Rava » 29 Aug 2022, 18:57

kultex wrote:
29 Aug 2022, 18:56
the battery seems to be ok - 92% of the new one...
That sounds good indeed.
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#127 by Rava » 09 Sep 2022, 06:28

System 5.0 with most recent XFCE 4.12 module

My system went into an unsuccessful state of suspend - during that I fell asleep.
During the falling asleep I thought the system would crash, but it was back on again after I woke up.

But - networking was disabled.
Image

The Network manager icon entry for [ ] Enable networking looks functional (not greyed out) - it still won't work, when I click it
Image
and go back to the icon or menu I see the same as in the above screenshots.

So, all I could do as interim attempt to fix that is killing Network manager and restarting it in the hopes that would fix the issue.
In case you wonder, currently I am on my other machine with i586 4.0-Port.

Added in 17 minutes 32 seconds:
Searching with my psg function for etwork I got two hits

Code: Select all

root@porteus:~# type psg
psg is a function
psg () 
{ 
    /bin/ps ax | /bin/grep $* | /bin/grep -v grep
}
root@porteus:~# psg etwork
 1544 ?        Ssl    0:03 /usr/sbin/NetworkManager
 2432 ?        Sl     0:00 /usr/libexec/gvfsd-network --spawner :1.15 /org/gtk/g
Since I have no idea what /usr/libexec/gvfsd-network does - it refuses to tell me

Code: Select all

root@porteus:~# /usr/libexec/gvfsd-network --help
Usage: /usr/libexec/gvfsd-network key=value key=value …
I hope killing and starting anew NetworkManager will suffice. (I looked into NetworkManager --help-all and found nothing about "restart")

After

Code: Select all

root@porteus:~# kill -9 1544
root@porteus:~# NetworkManager 
the icons on both machines showed a working "Wired Connection 1" - but I still did not get the Intertubes on my x86-64 Port 5.0. (see here for details how I connect to the intertubes via a shared WLAN [Solved via Networkmanager] masquerading and sharing via iptables )
Switching off "Wired Connection 1" and switching on "Wired Connection 1" in the Network Manager icon finally did the trick.
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-v5.0x86_64_bugs reports

Post#128 by ncmprhnsbl » 09 Sep 2022, 10:05

Rava wrote:
09 Sep 2022, 06:45
I hope killing and starting anew NetworkManager will suffice. (I looked into NetworkManager --help-all and found nothing about "restart")
for future reference:

Code: Select all

# /etc/rc.d/rc.networkmanager restart
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#129 by Rava » 09 Sep 2022, 10:13

ncmprhnsbl wrote:
09 Sep 2022, 10:05
for future reference:

Code: Select all

# /etc/rc.d/rc.networkmanager restart
Made me a brand new help.* info script:

Code: Select all

root@porteus:~# help.network 
help.network V0.1
to restart a malfunctioning NetworkManager (e.g. "disabled" and unable to change
that state):
(as root)
/etc/rc.d/rc.networkmanager restart
:D
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#130 by Rava » 13 Sep 2022, 06:14

this

Code: Select all

Sep 13 06:04:16 porteus syslogd[696]: -- MARK --
Sep 13 06:21:15 porteus kernel: usb 2-1.3: USB disconnect, device number 8
Sep 13 06:21:16 porteus kernel: usb 2-1.3: new high-speed USB device number 9 us
ing ehci-pci
Sep 13 06:21:16 porteus kernel: usb 2-1.3: New USB device found, idVendor=8644, 
idProduct=800b, bcdDevice= 1.00
Sep 13 06:21:16 porteus kernel: usb 2-1.3: New USB device strings: Mfr=1, Produc
t=2, SerialNumber=3
Sep 13 06:21:16 porteus kernel: usb 2-1.3: Product: USB Flash Disk              
  
Sep 13 06:21:16 porteus kernel: usb 2-1.3: Manufacturer: General                
       
Sep 13 06:21:16 porteus kernel: usb 2-1.3: SerialNumber: 1456000000003A31
Sep 13 06:21:16 porteus kernel: usb-storage 2-1.3:1.0: USB Mass Storage device d
etected
Sep 13 06:21:16 porteus kernel: scsi host8: usb-storage 2-1.3:1.0
Sep 13 06:21:16 porteus mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Sep 13 06:21:16 porteus mtp-probe: bus: 2, device: 9 was not an MTP device 
Sep 13 06:21:16 porteus kernel: usb 2-1.3: USB disconnect, device number 9
Sep 13 06:44:16 porteus syslogd[696]: -- MARK --
should have been the connection with my Samsung Galaxy S4 - 2 devices, the internal one and the external SD card - but none appeared.

This is how it should have looked like instead:

Code: Select all

Aug 30 14:02:52 porteus syslogd[697]: -- MARK --
Aug 30 14:16:23 porteus kernel: usb 2-1.3: new high-speed USB device number 11 u
sing ehci-pci
Aug 30 14:16:23 porteus kernel: usb 2-1.3: New USB device found, idVendor=04e8, 
idProduct=6860, bcdDevice= 4.00
Aug 30 14:16:23 porteus kernel: usb 2-1.3: New USB device strings: Mfr=1, Produc
t=2, SerialNumber=3
Aug 30 14:16:23 porteus kernel: usb 2-1.3: Product: SAMSUNG_Android
Aug 30 14:16:23 porteus kernel: usb 2-1.3: Manufacturer: SAMSUNG
Aug 30 14:16:23 porteus kernel: usb 2-1.3: SerialNumber: bla0blubb0
Aug 30 14:16:24 porteus mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Aug 30 14:16:24 porteus mtp-probe: bus: 2, device: 11 was an MTP device 
Aug 30 14:17:44 porteus kernel: usb 2-1.3: USB disconnect, device number 11
Aug 30 14:17:44 porteus kernel: usb 2-1.3: new high-speed USB device number 12 using ehci-pci
Aug 30 14:17:44 porteus kernel: usb 2-1.3: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 4.00
Aug 30 14:17:44 porteus kernel: usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 30 14:17:44 porteus kernel: usb 2-1.3: Product: SAMSUNG_Android
Aug 30 14:17:44 porteus kernel: usb 2-1.3: Manufacturer: SAMSUNG
Aug 30 14:17:44 porteus kernel: usb 2-1.3: SerialNumber: bla0blub0
Aug 30 14:17:44 porteus mtp-probe: Sep 13 06:21:16 porteus kernel: usb 2-1.3: New USB device found, idVendor=8644, 
idProduct=800b, bcdDevice= 1.00checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Aug 30 14:17:44 porteus mtp-probe: bus: 2, device: 12 was an MTP device 
As you can see, vendor and id as recognized do not match up, but I presume they should have:

recognized variant

Code: Select all

Aug 30 14:16:23 porteus kernel: usb 2-1.3: New USB device found, idVendor=04e8, 
idProduct=6860, bcdDevice= 4.00
vs today's unrecognised one:

Code: Select all

Sep 13 06:21:16 porteus kernel: usb 2-1.3: New USB device found, idVendor=8644, 
idProduct=800b, bcdDevice= 1.00
How does one debug such issues?

Added in 46 minutes 25 seconds:
Plugging in and out the Smartphone Port finally got the info

Code: Select all

Sep 13 08:57:13 porteus kernel: usb 2-1.3: new high-speed USB device number 11 using ehci-pci
Sep 13 08:57:13 porteus kernel: usb 2-1.3: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 4.00
Sep 13 08:57:13 porteus kernel: usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 13 08:57:13 porteus kernel: usb 2-1.3: Product: SAMSUNG_Android
Sep 13 08:57:13 porteus kernel: usb 2-1.3: Manufacturer: SAMSUNG
Sep 13 08:57:13 porteus kernel: usb 2-1.3: SerialNumber: bla0blubb0
Sep 13 08:57:13 porteus mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Sep 13 08:57:13 porteus mtp-probe: bus: 2, device: 11 was an MTP device 
and I could also access the drives for copying files.
Cheers!
Yours Rava

nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Porteus-v5.0x86_64_bugs reports

Post#131 by nanZor » 20 Sep 2022, 06:22

MD5 error on updater 001.xzm Core but 002.xzm Xorg ok?

Huh, tried to update my existing 5.0 x86_64 LXDE in the Porteus Settings Centre, and when the script ran, it notified me that 001 Core and 002 Xorg were available for updates.

Only 002 Xorg was downloaded and updated just fine, but 001 had the MD5 error, and was automatically removed after downloading - so no update for 001 for me. :) I tried twice, but 001 always failed with md5 and got removed...

I may have seen this issue somewhere else, but can't find it...
That's a UNIX book - cool. -Garth

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#132 by Rava » 20 Sep 2022, 06:28

nanZor wrote:
20 Sep 2022, 06:22
I tried twice, but 001 always failed with md5 and got removed...
Have you tried a manual download via terminal, e.g. like so as guest

Code: Select all

cd /your/folder/with/write-permission-for-guest/
wget URL-to-001-core.xzm
and check the md5sum manually?

Added in 10 minutes 35 seconds:
Update
I wanted to look into the two modules you mentioned and try the manual downloading.
First I ran fastest-mirror and since that said the fastest mirror for me is http://ftp.nluug.nl/os/Linux/distr/porteus I went there… but found no updates.
Do some of the mirror update very rarely or not at all and is ftp.nluug.nl one of these?
yt-dlp-2022.09.01-noarch-1ncm.xzm is in x86_64/Porteus-v5.0/modules/ and that is quite new… "09-Sep-2022 10:34"
but there is nothing in x86_64/Porteus-v5.0/updates/ or in x86_64/Porteus-v5.0/updates/patches/ :crazy:

Added in 5 minutes 7 seconds:
In http://ftp.nluug.nl/os/Linux/distr/port ... /language/ I looked for "md5"(sum) and also for "check"(sum) but to no avail.
http://ftp.nluug.nl/os/Linux/distr/port ... d5sums.txt only has the md5sums of the ISOs.
Where do I find the checksums of the language/ modules?
Cheers!
Yours Rava

nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Porteus-v5.0x86_64_bugs reports

Post#133 by nanZor » 20 Sep 2022, 07:52

Ah, interesting, thanks Rava!

my fastest-mirror is ftp.riken.jp

In the updates/core 20220723 directory I can see both the 001 and 002 xzm's. 001 is 122m.

In the updates.txt file, I think the md5 for 001 is just wrong perhaps.

I manually downloaded the 001.xzm and updated the system. Running a version check:

cat /etc/porteus/*

I see that I'm running 20220723 for both 001 and 002 now picking up 001 manually. Thanks for the tip - guess a couple of mirror issues..
Last edited by nanZor on 20 Sep 2022, 08:04, edited 1 time in total.
That's a UNIX book - cool. -Garth

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus-v5.0x86_64_bugs reports

Post#134 by Rava » 20 Sep 2022, 08:00

nanZor wrote:
20 Sep 2022, 07:52
my fastest-mirror is ftp.riken.jp

In the updates/core 20220723 directory I can see both the 001 and 002 xzm's. 001 is 122m.
indeed, ftp.riken.jp has something in Linux/porteus/x86_64/Porteus-v5.0/updates/core/20220723/ while http://ftp.nluug.nl/os/Linux/distr/porteus does not. :wall:

Anyhow, I already installed the 2 updated modules, so I can tell you the md5sums of these, and since they work, I presume the md5sums show the working ones:

Code: Select all

guest@porteus:/mybin/linux/porteus/5.0/x86-64$ ls -o 001-core.xzm 002-xorg.xzm
-rwxrwxrwx 1 guest 127496192 Jul 23 14:35 001-core.xzm
-rwxrwxrwx 1 guest 116961280 Jul 23 14:38 002-xorg.xzm
guest@porteus:/mybin/linux/porteus/5.0/x86-64$ md5sum 001-core.xzm 002-xorg.xzm
b5fd16c4ea91d195ab3775a86eff35f5  001-core.xzm
ec5394911b7a771fae922edb5b96a3f6  002-xorg.xzm
Just check what the md5sums of your manually downloaded modules are, especially the 001-core.xzm one.

Added in 11 minutes 18 seconds:
In case you wonder, the above md5sums are the same as when I run

Code: Select all

md5sum $PORTDIR/base/001-core.xzm $PORTDIR/base/002-xorg.xzm
Cheers!
Yours Rava

nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Porteus-v5.0x86_64_bugs reports

Post#135 by nanZor » 20 Sep 2022, 08:17

Yep - you nailed it. The md5 for 001 on riken.jp is wrong.

Thanks for the help - I'm sure the mirror guys will look into this..
That's a UNIX book - cool. -Garth

Post Reply