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.
-
evergreen
- Shogun

- Posts: 201
- Joined: 27 Mar 2016, 16:58
- Distribution: Porteus x86_64
- Location: Argentine, Patagonia
-
Contact:
Post#46
by evergreen » 27 Jun 2019, 22:55
Hello guys,
I am not sure if it's missing under purpose
gtk+3, but I think it was included in
Porteus 4.0, I am just noticing that because I am compiling again some packages and I haven't seen that notification before.
Cheers
I am testing Porteus v5.0rc1 XFCE
AMD A8-7410, APU AMD Radeon R5 Graphics M330
evergreen
-
ncmprhnsbl
- DEV Team

- Posts: 4290
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
-
Contact:
Post#47
by ncmprhnsbl » 27 Jun 2019, 23:20
evergreen wrote: ↑27 Jun 2019, 22:55
I am not sure if it's missing under purpose gtk+3, but I think it was included in Porteus 4.0, I am just noticing that because I am compiling again some packages and I haven't seen that notification before.
gtk+3 is there, but the devel module doesn't have the headers(/usr/include/*) needed for compiling..
because the headers frome the DEs haven't been merged into devel yet...
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
ncmprhnsbl
-
nanZor
- Shogun

- Posts: 489
- Joined: 09 Apr 2019, 03:27
- Distribution: Porteus 5.1 Alpha OpenBox
Post#48
by nanZor » 28 Jun 2019, 09:19
Thanks! Got it installed with RC1 and am testing now.
Oddly, other than a few times I could repeat it earlier, the problem no longer exists for me now, even prior to installation of the entropy module. I can't explain it.
So what I did for grins was to do a factory reset on my monitor (just to take out that wild variable).
It might also be related to this problem between syslinux and video I put into the hardware subforum:
Possible solution for video hang on Intel
So far so good. I have a feeling it is just my combination of hardware, which has magically fixed itself. Ugh - I hate 'magic' fixes!

That's a UNIX book - cool. -Garth
nanZor
-
nanZor
- Shogun

- Posts: 489
- Joined: 09 Apr 2019, 03:27
- Distribution: Porteus 5.1 Alpha OpenBox
Post#49
by nanZor » 28 Jun 2019, 09:28
nanZor wrote: ↑19 Jun 2019, 02:27
Sluggish Mount detective work ...
Aha! It seems that the sluggish filesystem mounts of up to 20 seconds on my XFCE4 RC1 may be due to permissions.
Update: I have reduced the automounting delay from 20 seconds down to about 10 seconds from when the desktop first appears.
Since I regularly crash my boxes testing things out, and since I have an NTFS windows filesystem that gets automatically mounted, I ran the equivalent of fsck on it with administrator priveleges in windows:
It found and fixed a bunch of errors. And now Porteus 5.0RC1 seems to automount about 10 seconds faster. I must have corrupted something that was confusing linux.
Need to find a way to *selectively* not automount those NTFS filesystems anyway - I'll search that out...
That's a UNIX book - cool. -Garth
nanZor
-
joe nar quo
- White ninja

- Posts: 7
- Joined: 22 Jun 2019, 00:24
- Distribution: porteus mate
Post#51
by joe nar quo » 09 Jul 2019, 10:55
joe nar quo wrote: ↑24 Jun 2019, 13:39
Ed_P wrote: ↑22 Jun 2019, 05:22
Hello
joe.
Did you have these chrome problems with version 4.0 of Porteus
Hi Ed,
Before I use Porteus 3.2.2 on my old laptop and have no problem. Now I try to use Porteus 5.0 on my new laptop Acer Aspire 3 A315-41-R3LC AMD Ryzen 3 and I got this problem.
I have solved this problem, I use vmlinuz initrd.xz and kernel.xzm from porteus v5.0 ; core.xzm and xorg.xzm from porteus v3.2.2rc5 and mate.xzm from porteus v3.2.2 rc4. And everything work fine. Beautiful.
joe nar quo
-
Rava
- Contributor

- Posts: 5424
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Post#52
by Rava » 09 Jul 2019, 22:51
joe nar quo wrote: ↑09 Jul 2019, 10:55
I have solved this problem, I use vmlinuz initrd.xz and kernel.xzm from porteus v5.0 ; core.xzm and xorg.xzm from porteus v3.2.2rc5 and mate.xzm from porteus v3.2.2 rc4. And everything work fine. Beautiful.
That is one h*ll of a mix, but when it works, all is fine.
Hopefully the issue can be solved for 5.0 finale version.

Cheers!
Yours Rava
Rava
-
sci_fi
- Black ninja

- Posts: 58
- Joined: 28 Dec 2010, 18:25
Post#53
by sci_fi » 11 Jul 2019, 12:47
Problem with broadcom wireless.
Dell laptop (Latitude 6330) with broadcom wireless h/w worked fine on version 4.0 but wireless no longer works on version 5 rc1.
Porteus seems to be finding the wireless card as this is the output from Porteus system/wireless:
WIRELESS INFO:
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
Subsystem: Dell Device 0015
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f7d00000 (64-bit, non-prefetchable)
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-cc-ff-ff-34-00-71
Capabilities: [16c] Power Budgeting <?>
Also contents of etc/modprobe.d/broadcom_blacklist.conf:
# Default driver for supporting broadcom wifi chipsets is proprietary broadcom-sta (wl.ko).
# Please refer to 'Broadcom wifi under Porteus' HOWTO
# in case when you want to use the opensource drivers (b43/brcmsmac):
# http://forum.porteus.org/viewtopic.php?f=39&t=1099
#
# Blacklist opensource drivers they wont interfere with wl.ko:
blacklist wl
Also contents of etc/modprobe.d/b43_blacklist.conf:
blacklist wl
Not sure how to proceed.
Thank you and best regards,
sci_fi
sci_fi
-
raja
- Shogun

- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Post#54
by raja » 11 Jul 2019, 17:08
Volume icon on boot shows a cross mark, with Device as "Default". Becomes normal when device selected as HDA Intel PCH. Some conflict with Pulse installation.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
raja
-
Blaze
- DEV Team

- Posts: 3998
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#55
by Blaze » 11 Jul 2019, 17:41
sci_fi,
Version 4.0 questions (Пост Blaze #64647)
raja, this happens (about volume icon) in Openbox DE?
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze
-
sci_fi
- Black ninja

- Posts: 58
- Joined: 28 Dec 2010, 18:25
Post#56
by sci_fi » 15 Jul 2019, 14:18
@Blaze, Still on broadcom
Hi Blaze,
Thank you for the reminder regarding broadcom wireless fixes. That is what I did on version 4.0 and it worked fine. Unfortunately, it has not worked for me on version 5 rc1. Specifically, I get an error message with the modprobe command:
root@porteus:/home/guest# dmesg | grep -i b43
root@porteus:/home/guest# modprobe b43
modprobe: FATAL: Module b43 not found in directory /lib/modules/4.16.3-porteus
I observe that the folder /lib/modules/4.16.3-porteus does not exist. There is a a folder /lib/modules/5.1.5-porteus.
I created a folder /lib/modules/4.16.3-porteus and copied the contents of /lib/modules/5.1.5-porteus into it and tried again with this result.
root@porteus:/home/guest# modprobe b43
modprobe: ERROR: could not insert 'b43': Exec format error
sci_fi
-
chromer
- Black ninja

- Posts: 31
- Joined: 13 Jan 2019, 18:00
- Distribution: APorteus Cinnamon 64bit
- Location: Turkey
Post#57
by chromer » 17 Jul 2019, 09:35
chromer
-
fulalas
- DEV Team

- Posts: 2059
- Joined: 26 Oct 2016, 15:34
- Distribution: Porteus
- Location: Brazil
Post#58
by fulalas » 17 Jul 2019, 10:16
@chromer, yes. That's because ffmpeg Slackware current is still old -- I don't know why.
fulalas
-
Ed_P
- Contributor

- Posts: 8956
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#59
by Ed_P » 18 Jul 2019, 18:04
USM updates via the GUI end up with a blank terminal screen.
Ed_P
-
Blaze
- DEV Team

- Posts: 3998
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#60
by Blaze » 18 Jul 2019, 18:31
fulalas wrote: ↑17 Jul 2019, 10:16
because ffmpeg Slackware current is still old
Look at current updates of Slackware Wed Jul 17 21:57:16 UTC 2019
ftp://ftp.osuosl.org/pub/slackware/slac ... ngeLog.txt = ffmpeg-4.1.4
Отправлено спустя 5 минут 25 секунд:
sci_fi wrote: ↑15 Jul 2019, 14:18
I observe that the folder /lib/modules/4.16.3-porteus does not exist. There is a a folder /lib/modules/5.1.5-porteus.
I think that you are mixed changes from Porteus 4.0 and Porteus 5.0 rc1.
Boot up Porteus in the 'Text mode' and remove all files from changes folder. If need you can use for it
mc command.
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze