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.
-
Ed_P
- Contributor

- Posts: 8957
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1
by Ed_P » 13 Jun 2025, 22:29
Ed_P
-
ncmprhnsbl
- DEV Team

- Posts: 4290
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
-
Contact:
Post#2
by ncmprhnsbl » 15 Jun 2025, 01:24
there's been no change to any of the module activation scripts between 5.01 and 5.1 alpha.
bash has been updated from 5.1 to 5.2, so, maybe, it's less tolerant of whatever might be wrong with your script ..idk.
you could try removing all your dev/null bits in the script, run it from a terminal, and perhaps it'll shed some light on what's happening.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
ncmprhnsbl
-
Ed_P
- Contributor

- Posts: 8957
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#3
by Ed_P » 15 Jun 2025, 04:35
ncmprhnsbl wrote: ↑15 Jun 2025, 01:24
run it from a terminal,
A good suggestion. Thank you
ncmp.
The results:
A second problem, the Shift+PrtScr option doesn't work. Ctrl+PrtScr didn't help. Full screen is the only option.

Ed_P
-
fulalas
- DEV Team

- Posts: 2060
- Joined: 26 Oct 2016, 15:34
- Distribution: Porteus
- Location: Brazil
Post#4
by fulalas » 16 Jun 2025, 21:17
@Ed_P, have you tried using -q parameter (i.e. activate -q module.xzm)?
fulalas
-
Ed_P
- Contributor

- Posts: 8957
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#5
by Ed_P » 17 Jun 2025, 00:17
fulalas wrote: ↑16 Jun 2025, 21:17
@Ed_P, have you tried using -q parameter (i.e.
activate -q module.xzm)?
I have not
fulalas. Do you think -q
Code: Select all
To disable UI messages use '-q':
module.xzm -q
will resolve the Module Already Active problem and actually load the module?
Added in 5 hours 7 minutes 3 seconds:

So I made a module of my script that sets the DRV variable to my boot drive and when it is activated when booting my OP posting's script works
The error I was getting about the problem was totally misleading.

Module not found or Directory not found or Invalid variable would have been more helpful.
The Shift+PrtScr option not working for screen selection is still a problem though.
Ed_P