Fienix - New PowerPC Distro

[caseycullen]

Hello,

Your tests on Fienix are very interesting and they are a great help for me to build the OS. I encounter the same problem as kilaueabart, presented in a previous post: http://forum.hyperion-entertainment.com ... 8&start=50

Did you manage in the meantime to find a solution for the graphical problem when starting Fienix?

Regards

If I remember correctly this was a glamor issue. Please open terminal and enter the following as su:

Code: Select all

mv '/usr/lib/xorg/modules/libglamoregl.so' '/usr/lib/xorg/modules/libglamoregl.so.bak'

Then restart.

[Amiguy]

Hello,

Your tests on Fienix are very interesting and they are a great help for me to build the OS. I encounter the same problem as kilaueabart, presented in a previous post: http://forum.hyperion-entertainment.com ... 8&start=50

Did you manage in the meantime to find a solution for the graphical problem when starting Fienix?

Regards

If I remember correctly this was a glamor issue. Please open terminal and enter the following as su:

Code: Select all

mv '/usr/lib/xorg/modules/libglamoregl.so' '/usr/lib/xorg/modules/libglamoregl.so.bak'

Then restart.

Hi Casey,

Thank you very much for the tip. It works well now.

[kilaueabart]

We should get your wired networking up and running again first. Let's see if dhclient can get you back online; please enter the following into terminal: "/sbin/dhclient eth0"
Then, please enter "ip -a" and post the output.

I don't think this is what we wanted; it seems to need an OBJECT:

Code: Select all

fienix@Fienix:~$ /sbin/dhclient eth0
Cannot find device "eth0"
fienix@Fienix:~$ su
Password: 
root@Fienix:/home/fienix# /sbin/dhclient eth0
Cannot find device "eth0"
root@Fienix:/home/fienix# ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
       ip [ -force ] -batch filename
where  OBJECT := { link | address | addrlabel | route | rule | neigh | ntable |
                   tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |
                   netns | l2tp | fou | macsec | tcp_metrics | token | netconf | ila |
                   vrf | sr }
       OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
                    -h[uman-readable] | -iec | -j[son] | -p[retty] |
                    -f[amily] { inet | inet6 | mpls | bridge | link } |
                    -4 | -6 | -I | -D | -M | -B | -0 |
                    -l[oops] { maximum-addr-flush-attempts } | -br[ief] |
                    -o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
                    -rc[vbuf] [size] | -n[etns] name | -a[ll] | -c[olor]}
root@Fienix:/home/fienix# 

Maybe I should try some of the things Christian suggested to Icbrkr

[xeno74]

@kilaueabart

Please post the output of ip a.

-- Christian

[caseycullen]

I don't think this is what we wanted; it seems to need an OBJECT:

Code: Select all

fienix@Fienix:~$ /sbin/dhclient eth0
Cannot find device "eth0"
fienix@Fienix:~$ su
Password: 
root@Fienix:/home/fienix# /sbin/dhclient eth0
Cannot find device "eth0"
root@Fienix:/home/fienix# ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
       ip [ -force ] -batch filename
where  OBJECT := { link | address | addrlabel | route | rule | neigh | ntable |
                   tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |
                   netns | l2tp | fou | macsec | tcp_metrics | token | netconf | ila |
                   vrf | sr }
       OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
                    -h[uman-readable] | -iec | -j[son] | -p[retty] |
                    -f[amily] { inet | inet6 | mpls | bridge | link } |
                    -4 | -6 | -I | -D | -M | -B | -0 |
                    -l[oops] { maximum-addr-flush-attempts } | -br[ief] |
                    -o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
                    -rc[vbuf] [size] | -n[etns] name | -a[ll] | -c[olor]}
root@Fienix:/home/fienix# 

Maybe I should try some of the things Christian suggested to Icbrkr

Sorry, I mistakenly asked you to post the output of "ip -a"; as Christian posted, it should have been "ip a" (without the "-").

[Roland]

Noticed a bug in the Power Management preferences of Fienix... The delay set to 'Display' does not work at all as it should. If it is set e.g. to '1h', screen goes off after 20 min, and if it is set to 'never', the delay is only 10 min! But if it is set to 1 min, the delay is much longer than that.

Is there already a fix for this absurd issue...?

BTW, checked this also in Ubuntu 16.04, and there the same worked normally.

[kilaueabart]

Hello,
... I encounter the same problem as kilaueabart, presented in a previous post: http://forum.hyperion-entertainment.com ... 8&start=50
Did you manage in the meantime to find a solution for the graphical problem when starting Fienix?

If I remember correctly this was a glamor issue. Please open terminal and enter the following as su:

Code: Select all

mv '/usr/lib/xorg/modules/libglamoregl.so' '/usr/lib/xorg/modules/libglamoregl.so.bak'

Then restart.

Wow! Thank you for that! Fienix now starts SO much nicer!

[kilaueabart]

Same result (of course) for dhclient eth0

Code: Select all

fienix@Fienix:~$ /sbin/dhclient eth0
Cannot find device "eth0"
fienix@Fienix:~$

BTW, I've been having to wait for a start job running for Raise network interfaces when I boot Fienix. Suggests 8 min 5 sec but quits after about one minute.

ip a gets

Code: Select all

fienix@Fienix:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether e2:25:40:fb:8d:4c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::e025:40ff:fefb:8d4c/64 scope link 
       valid_lft forever preferred_lft forever
3: enP4096p4s4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 38:83:45:ee:f9:f3 brd ff:ff:ff:ff:ff:ff
4: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
5: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
6: ip6_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd ::
7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
8: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd ::
9: wlx00e04c819253: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e0:4c:81:92:53 brd ff:ff:ff:ff:ff:ff
fienix@Fienix:~$ 

For good measure, did ifconfig -a as well:

Code: Select all

fienix@Fienix:~$ /sbin/ifconfig -a
dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 1500
        inet6 fe80::e025:40ff:fefb:8d4c  prefixlen 64  scopeid 0x20<link>
        ether e2:25:40:fb:8d:4c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23  bytes 4906 (4.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enP4096p4s4: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 38:83:45:ee:f9:f3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip6_vti0: flags=128<NOARP>  mtu 1364
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip6tnl0: flags=128<NOARP>  mtu 1452
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip_vti0: flags=128<NOARP>  mtu 1480
        tunnel   txqueuelen 1000  (IPIP Tunnel)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4  bytes 240 (240.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4  bytes 240 (240.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

sit0: flags=128<NOARP>  mtu 1480
        sit  txqueuelen 1000  (IPv6-in-IPv4)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tunl0: flags=128<NOARP>  mtu 1480
        tunnel   txqueuelen 1000  (IPIP Tunnel)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlx00e04c819253: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 00:e0:4c:81:92:53  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[xeno74]

Hi Kilaueabart,

Please try

Code: Select all

/sbin/dhclient enP4096p4s4

After that please post the output of

Code: Select all

ip a

Thanks,
Christian

[caseycullen]

Noticed a bug in the Power Management preferences of Fienix... The delay set to 'Display' does not work at all as it should. If it is set e.g. to '1h', screen goes off after 20 min, and if it is set to 'never', the delay is only 10 min! But if it is set to 1 min, the delay is much longer than that.

Is there already a fix for this absurd issue...?

BTW, checked this also in Ubuntu 16.04, and there the same worked normally.

That's odd; I'm not able to reproduce this.. it works as it should for me. How long have you noticed this? Are you able to run a fresh install off a usb to see if it still happens?
Anyone else have issues with Power Management / Display?
-Casey