KLA-Manjaro-Openbox-CE-1.1

[Sofiya]

KLA-Manjaro-Openbox-CE-1.1

• Uses pamac -aur as package manager

  uses Pipewire as a sound server

  ISO:
  https://github.com/sofijacom/KLA-Manjar ... penbox-1.1

  md5 checksum: 209cd870de5ee0fcbe5c074286e590e5

[geo_c]

KLA-Manjaro-Openbox-CE-1.1

• ISO:
  https://github.com/sofijacom/KLA-Manjar ... penbox-1.1

  md5 checksum: 209cd870de5ee0fcbe5c074286e590e5

I'm getting 404 page not found on that link.

[josejp2424]

hi @Sofiya .
KLA Manjaro LXDE.
For testing, with grub2config. (l gru2config, there is a scrip,
to use the kl )
Midori browser.

https://drive.google.com/file/d/1GuiYmH ... sp=sharing

[Clarity]

Hello @josejp2424

Question
Is this an update or remaster of the original CE? Or is this a new build from the KLA build script that has LXDE as the default desktop?

Curious

[josejp2424]

Hello @josejp2424

Question
Is this an update or remaster of the original CE? Or is this a new build from the KLA build script that has LXDE as the default desktop?

Curious

Hy Clarity.

The 07LKA-manjaro.sfs. It is a new compilation.

[wiak]

Hello @josejp2424

Question
Is this an update or remaster of the original CE? Or is this a new build from the KLA build script that has LXDE as the default desktop?

Curious

Hy Clarity.

The 07LKA-manjaro.sfs. It is a new compilation.

That's great. Two different KLA builds to try. Interesting and exciting really.

[josejp2424]

Hello @josejp2424

Question
Is this an update or remaster of the original CE? Or is this a new build from the KLA build script that has LXDE as the default desktop?

Curious

Hy Clarity.

The 07LKA-manjaro.sfs. It is a new compilation.

That's great. Two different KLA builds to try. Interesting and exciting really.

In this there is a script that uses gru2config,
so that it can take all the kl.

[wiak]

Before you try it @Clarity, please note that the current LXDE named iso won't boot from iso with Ventoy. I noticed the grub.conf would need modified to have the correct iso name at the top for that to work. At the moment it has Sofiya's Openbox release name in these iso boot related config files inside the iso.

It certainly works as normal frugal install though, per the attached screenshot.

[wiak]

It certainly works as normal frugal install though, per the attached screenshot.

@josejp2424 I'm curious about something though - where does that vmlinuz kernel come from? Is it a Puppy-style huge kernel or is it an official manjaro kernel? If the latter I wondered why using 00modules and 01firmware rather than just having them in main root filesystem (though okay either way of course). If a huge kernel I'm wondering why modules needed inside the initrd.gz though I note that overlay is loaded as a module, but FR initrd should be able to load that module without it being embedded inside initrd.gz as long as all other needed boot modules are in a huge vmlinuz. I'm just concerned in case a huge kernel and something not working as I intend so would look into it. I haven't tried Sofiya's one yet - perhaps it is kernel from there?

EDIT: Okay - same kernel @Sofiya using so the question regarding where kernel comes from goes to her...

EDIT2: Actually the kernel may come from @rockedge so maybe question about how it is made should go there???! I see official Void Linux kernels often used so that could be the case here I suppose?

[josejp2424]

It certainly works as normal frugal install though, per the attached screenshot.

@josejp2424 I'm curious about something though - where does that vmlinuz kernel come from? Is it a Puppy-style huge kernel or is it an official manjaro kernel? If the latter I wondered why using 00modules and 01firmware rather than just having them in main root filesystem (though okay either way of course). If a huge kernel I'm wondering why modules needed inside the initrd.gz though I note that overlay is loaded as a module, but FR initrd should be able to load that module without it being embedded inside initrd.gz as long as all other needed boot modules are in a huge vmlinuz. I'm just concerned in case a huge kernel and something not working as I intend so would look into it. I haven't tried Sofiya's one yet - perhaps it is kernel from there?

EDIT: Okay - same kernel @Sofiya using so the question regarding where kernel comes from goes to her...

EDIT2: Actually the kernel may come from @rockedge so maybe question about how it is made should go there???! I see official Void Linux kernels often used so that could be the case here I suppose?

It is a vanilla kernel.
I think it's from @rockedge

[wiak]

I dont think it is a vanilla kernel. That would have overlayfs built in I think and would be huge kernel style so shouldnt need modules in the initrd.gz

[Amol]

Hello sofiya !
I've made an addendum to screener file stored in Startup directory :

if [ "$ENABLESAVER" = TRUE ]; then
xset s off
xautolock -time "$SAVERTIME" -locker /usr/share/screener/sxlock -corners 0-00 &
else
xset s on dpms 0 600 0 +dpms
fi

if [ "$ENERGYSAVE" = TRUE ]; then
ETIME=$(( $ENERGYTIME * 60 ))
xset dpms $ETIME $ETIME $ETIME
else
xset -dpms
fi

I've added the lines 4 and 5 :
else
xset s on dpms 0 600 0 +dpms

As result there is no standby of the system just the shutdown of the screen.
Best regards,
Amol

[Sofiya]

Hello sofiya !
I've made an addendum to screener file stored in Startup directory :

if [ "$ENABLESAVER" = TRUE ]; then
xset s off
xautolock -time "$SAVERTIME" -locker /usr/share/screener/sxlock -corners 0-00 &
else
xset s on dpms 0 600 0 +dpms
fi

if [ "$ENERGYSAVE" = TRUE ]; then
ETIME=$(( $ENERGYTIME * 60 ))
xset dpms $ETIME $ETIME $ETIME
else
xset -dpms
fi

I've added the lines 4 and 5 :
else
xset s on dpms 0 600 0 +dpms

As result there is no standby of the system just the shutdown of the screen.
Best regards,
Amol

Hi Amol !

For me, the script "/root/Startup/xlock_xidlehook" is responsible for this.

in it you just had to comment out the last 4 lines so that it wouldn't go into sleep mode

Code: Select all

#!/usr/bin/env bash

# Only exported variables can be used within the timer's command. xlock -nolock -mode clock
#  `# Don't lock when there's a fullscreen application` \
#  --not-when-fullscreen \


sleep 5
export PRIMARY_DISPLAY="$(xrandr | awk '/ primary/{print $1}')"

# Run xidlehook
xidlehook \
  `# Don't lock when there's audio playing` \
  --not-when-audio \
  `# Dim the screen after 60 seconds, undim if user becomes active` \
  --timer 900 \
    'xrandr --output "$PRIMARY_DISPLAY" --brightness .1' \
    'xrandr --output "$PRIMARY_DISPLAY" --brightness 1' \
  `# Undim & lock after 10 more seconds` \
  --timer 10 \
    'xrandr --output "$PRIMARY_DISPLAY" --brightness 1; xlock -nolock -mode clock' \
    '' 
#  `# Finally, suspend an hour(3600) after it locks` \
#  --timer 1200 \
#    'systemctl suspend' \
#    ''

[Amol]

Hello sofiya !
OK for that hint.
Amol