Bug reports

Arch based Porteus community project
Locked
User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Bug reports

Post#1 by brokenman » 04 Oct 2015, 18:27

Place suspected bug reports here. Anything confirmed will be added to the bitbucket issues section for attention.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 977
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Bug reports

Post#2 by ncmprhnsbl » 04 Oct 2015, 20:01

in cleanup-arch.sh
the '## Leave sane permissions' part at line 159 should be before makesfs ...
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Bug reports

Post#3 by brokenman » 04 Oct 2015, 20:35

Thanks. Updated and will push to git later tonight. I have finished the setup-locales script and I am testing it now.

EDIT:
Pushed update along with many others. Locales script is now in place and tested. Now working on creating dialog scripts for prettiness.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 977
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Bug reports

Post#4 by ncmprhnsbl » 04 Oct 2015, 22:30

to get build.sh to work in (my) arch install (works fine in porteus):
had preface commands with sh ie. sh ../git/scripts/build.sh 001
and in line 119 of build.sh > sh ../git/scripts/cleanup-arch.sh $ARCH $MOD
add -comp xz to mksquashfs command line 161 of cleanup-arch.sh

lines 95 to 100 of cleanup-arch.sh are unnecessary
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Bug reports

Post#5 by brokenman » 04 Oct 2015, 23:13

Ok thanks. I will update the script. I am building on Porteus host for now.

EDIT:
lines 95-100 are relevant. At the moment we are at 001-core but when we get to 003 it will be needed. I think the final ISO will be released with at least one working desktop environment.
Pushed the changes in the build script to git. Also upgraded kernel to stable 4.2.3 because I needed to add some kernel configs to get hostnamed and localed working. Forgot to redo the lib link in 000-kernel so reuploaded that too. Thats about it for the night so feel free to pull the latest and test away.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 977
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Bug reports

Post#6 by ncmprhnsbl » 05 Oct 2015, 11:49

building in porteus is much better,, no weird permissions issues...cool how you make an arch system without using pacman..

rebuilt with new kernel and installed to usb (copied contents of /iso to usb > ran Port..installer.com)
boots up fine... no ethernet
ip link
dhcpcd e****(cant remember exactly) seems to work
setup-pman works out pacman-config module placed in modules
pman -S 1 2 3
results in 1.xzm 2.xzm left in /tmp and 3.xzm in /porteus/modules(manually created)
only the last on the list makes it to /modules
also the xzms have no /var/lib/pacman/local/foo information so pacman cant tell thy're installed
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

stifiling
Contributor
Contributor
Posts: 93
Joined: 14 Jul 2013, 03:10
Distribution: Porteus w/pacman pm
Location: home

Re: Bug reports

Post#7 by stifiling » 05 Oct 2015, 13:54

I tested it out some last night. i've never used git to contribute to the development. one thing i'd add in is more firmware in the 000-kernel.xzm. my radeon card on my desktop is missing the firmware, and so is my wifi card on my laptop. i'd add these in, if i knew how.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Bug reports

Post#8 by brokenman » 06 Oct 2015, 01:18

only the last on the list makes it to /modules
also the xzms have no /var/lib/pacman/local/foo information so pacman cant tell thy're installed
Thanks. I'll check this out now. After booting and not having internet can you check if dhcpcd is running?
ps aux|grep dhcpcd

I have the option of defaulting the name to eth0 instead of predictive naming which is the new thing. Do you think this would be advantageous?

@stifiling
I will go through the kernel config again and make sure the firmware is there. For git just go to bitbucket and create an account and I will create a video tutorial for you.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4621
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Bug reports

Post#9 by fanthom » 06 Oct 2015, 07:22

@brokenman
You need out of the kernel tree firmware which you can find here:
https://www.archlinux.org/packages/core ... -firmware/
http://git.kernel.org/cgit/linux/kernel ... rmware.git

Unfortunately full package adds many unneded files (bloat) so i have created a script for kiosk which lists only firmware which is used by the certain kernel version/configuration. Its about 90% accurate. Some kernel drivers does not advertise which firmware and firmware version they need or advertise this incorrectly (pain especially for Intel wifi). Will post it here once i get back home.

If you dont care about the size that much then i would recommend full firmware package so everything will work even if user recompile the kernel.
Please add [Solved] to your thread title if the solution was found.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 977
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Bug reports

Post#10 by ncmprhnsbl » 06 Oct 2015, 12:15

brokenman wrote: After booting and not having internet can you check if dhcpcd is running?

Code: Select all

#ps aux | grep dhcpcd
root  656 0.0  0.0   492   4 tty1    R+   11:40   00:00 grep dhcpcd
#pstree 
systemd-------dbus-daemon
                    |---login ----bash----pstree
                    |---systemd ------(sd-pam)
                    |---systemd-journal
                    |---systemd-logind
                    |---systemd-udevd
systemctl start dhcpd 
#pstree 
systemd-------dbus-daemon
                    |---dhcpcd
                    |---login ----bash----pstree
                    |---systemd ------(sd-pam)
                    |---systemd-journal
                    |---systemd-logind
                    |---systemd-udevd

ip link says UP but pacman wont connect.... seems to be a bit random
brokenman wrote:I have the option of defaulting the name to eth0 instead of predictive naming which is the new thing. Do you think this would be advantageous?
could be ... every machine seems to have a differnt name..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Bug reports

Post#11 by brokenman » 06 Oct 2015, 14:41

@fanthom
Thanks a lot.
Ouch. 30Mb of firmware. Any chance of seeing your script for a general idea of what I can remove?
EDIT: Ok I just understood your sentence. I will checkout the existing Porteus extra firmware module.

@ncmprhnsbl
Thanks. Can you show me the /mnt/sdaXy/config/network file. Only Dhcp=yes should be uncommented.

Predictive naming sounds contradictive. Before I could be sure the card would be eth0. Now it could be any number of names. I am sure it is better for large scale production or in cases where people will swap hardware, but for most people I think the old scheme worked better. I think I will force a real predictive naming scheme.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 5083
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Bug reports

Post#12 by francois » 06 Oct 2015, 18:49

@brokenman:
After git pull:

Code: Select all

root@porteus:/mnt/sda5/nemesis/git# git pull
I just got this message while creating the os:

Code: Select all

root@porteus:/mnt/sda5/nemesis/build# ../git/scripts/build.sh 001
...
...
usr/bin/ksba-config
../git/scripts/cleanup-arch.sh: line 101: `strip_003-lxde': not a valid identifier
It seems to have stop the production of the files needed for the iso.

In cleanup-arch.sh replaced strip_003-lxde:
#strip_003-lxde()
strip_003()

Things seems ok now. Was it the good thing to do?
Voltaire: Le mieux est l'ennemi du bien.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4621
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Bug reports

Post#13 by fanthom » 06 Oct 2015, 19:50

@brokenman
Unsquash 000-kernel.xzm -> copy firmware you currently have to the lib/firmware folder -> run following script in the squashfs-root directory:

Code: Select all

#!/bin/sh

cd `pwd`
krn=`ls lib/modules`
rm -f fw-*
for x in $(cat lib/modules/$krn/modules.dep | cut -d: -f1 | sort -u); do modinfo -F firmware lib/modules/$krn/$x | wc -l | grep -q -v -w 0 && echo lib/modules/$krn/$x >> fw-all && modinfo -F firmware lib/modules/$krn/$x >> fw-all; done
grep -v lib/modules fw-all > fw
for x in `cat fw`; do test -e lib/firmware/$x || echo $x >> miss; done
for x in `cat miss`; do grep -B200 $x fw-all | tac | sed -n '/lib\/modules/{p;q;}' >> missing && echo $x >> missing; done
awk '!x[$0]++' missing > fw-missing
for x in `find lib/firmware -type f | egrep -v 'COPYRIGHT|LICENCE|LICENSE|BCM-LEGAL|b43|GPL|WHENCE' | sed s@lib/firmware/@@ | sort -u`; do grep -q $x fw || echo $x >> fw-extra; done
it will produce 3 files:
a) fw-all - all firmware which is needed by the kernel
b) fw-missing - firmware which is missing
c) fw-extra - firmware which is not needed

As i said before - result is about 90% accurate as some drivers does not advertise correctly which firmware they really need.
Please add [Solved] to your thread title if the solution was found.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 977
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Bug reports

Post#14 by ncmprhnsbl » 06 Oct 2015, 21:02

brokenman wrote:Can you show me the /mnt/sdaXy/config/network file. Only Dhcp=yes should be uncommented.
ok, my mistake, i had uncommented 'wired' and 'name'..... recommented , but during startup 'network-setup' fails'(and before)

Code: Select all

jounalctl | grep network-setup
.....  blah.....   /usr/local/sbin/network-setup : line 44 : get_value : command not found
from /var/log/network-setup.log

Code: Select all

Please set DeviceName= in /mnt/sdb1/config/network
Aborting network setup ... 
but now 'systemctl start dhcpcd' works
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Bug reports

Post#15 by brokenman » 07 Oct 2015, 01:39

@francois
I don't see this error. But it is definitely not a good identifier for a function. I will make the change in the git tree. Thanks.

@fanthom
Thanks very much. Appreciate that.

@ncmprhnsbl
Nice troubleshooting. The get_value function was indeed missing. Pushing an update now.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Locked