Porteus-v4.0rc4 bug reports

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.
Binary Enigma
White ninja
White ninja
Posts: 4
Joined: 22 Feb 2018, 11:44
Distribution: Porteus v4 32 bit

Porteus-v4.0rc4 bug reports

Post#31 by Binary Enigma » 26 Feb 2018, 23:49

jssouza wrote:
26 Feb 2018, 07:03
- porteus.cfg does have changes=/porteus. AFAIK, this was the same even in porteus 3.2.2.
But, since you had to change this to /changes, I assume you have a changes directory? Is this from your older 3.2.2? If yes, could you try booting without your changes and see if the problem still occurs?
Oh, I was mistaken, in porteus 3.2.2 I have "changes=/", yet it saves changes to /changes (there's where I got confused), but when I left porteus.cfg as it was (with changes=/porteus) in v4, it gave me a notification in the corner saying "Changes are not saved" (This did not happen after the reinstall stated below)

Something that should be noted(isn't quite a bug), when going to the tab "Places" on the cinnamon menu, opening any of
the locations results in errors because it attempts to open folders with Audacious, the way to fix this is simple, right
clicking any folder within nemo, Open With > Other Application... and changing the default application(which is Audacious
for some reason) to "Files"
I just installed Porteus v4 (with cinnamon) once again(hoping that the kernel update helped things), the results aren't all that better:

- I can log in with any user, it logs in with guest by default(like it did in 3.2.2), "Users and Groups" in settings works;
- Notification tells me that cinnamon is in software rendering mode on computers where it used to run without it (I thought it was just work computers but my home one has it too);
- The desktop itself doesn't work, shortcuts added don't show up, can't right click or drag around (This was probably there last time but I didn't notice);
- Internet still doesn't work, but in a different way, now it doesn't show ethernet or adapters at all:
bour59 wrote:
26 Feb 2018, 14:54
Porteus-XFCE-v4.0rc4-i586.iso 2018-02-25 12:41
no network interface
iwconfig says only : lo
no eth0
Same but instead of "no eth0", it says "no wireless extensions"

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-v4.0rc4 bug reports

Post#32 by ncmprhnsbl » 26 Feb 2018, 23:58

paf wrote:
25 Feb 2018, 20:55
Big issue: no networking because no network interfaces, and doing lsmod, no modules appear...

Possible cause: there is a /lib/modules/4.15.0-rc7-porteus/ folder...
confirmed
bour59 wrote:
26 Feb 2018, 14:54
Porteus-XFCE-v4.0rc4-i586.iso 2018-02-25 12:41
no network interface
iwconfig says only : lo
no eth0
see above..
there has been mistake made with the kernel module on the i586 ISOs..
thank you for your patience while it's fixed .. normal service will resume shortly :sorry:
brokenman wrote:
25 Feb 2018, 12:42
Very sorry. Corrected now.
partly , see above
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v4.0rc4 bug reports

Post#33 by Ed_P » 27 Feb 2018, 04:34

jssouza wrote:
26 Feb 2018, 07:03
- porteus.cfg does have changes=/porteus. AFAIK, this was the same even in porteus 3.2.2.
I think there is a different file with 4.0.
brokenman https//forum.porteus.org/viewtopic.php?f=35&t=7561 wrote: New configuration file at porteus/porteus-v4.0-x86_64.cfg
Ed

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus-v4.0rc4 bug reports

Post#34 by jssouza » 27 Feb 2018, 05:22

Ed_P wrote:
27 Feb 2018, 04:34
jssouza wrote:
26 Feb 2018, 07:03
- porteus.cfg does have changes=/porteus. AFAIK, this was the same even in porteus 3.2.2.
I think there is a different file with 4.0.
brokenman https//forum.porteus.org/viewtopic.php?f=35&t=7561 wrote: New configuration file at porteus/porteus-v4.0-x86_64.cfg
Ed_P, we are talking about /boot/syslinux/porteus.cfg
Binary Enigma wrote:
26 Feb 2018, 23:49
- Notification tells me that cinnamon is in software rendering mode on computers where it used to run without it (I thought it was just work computers but my home one has it too);
- Internet still doesn't work, but in a different way, now it doesn't show ethernet or adapters at all:
There is a mismatch between the kernel version and the modules version. So neither your graphics driver nor your network driver is loaded and hence the above problems.
uname -a gives 4.15.2-porteus while /lib/modules has 4.15.0-rc7-porteus. AI for brokenman.
Binary Enigma wrote:
26 Feb 2018, 23:49
- The desktop itself doesn't work, shortcuts added don't show up, can't right click or drag around (This was probably there last time but I didn't notice);
Checked this logged in as guest and it works. Is this when you are logged in as root? This is upstream. Cinnamon developers have disabled logging in as root.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v4.0rc4 bug reports

Post#35 by Ed_P » 27 Feb 2018, 06:52

jssouza wrote:
27 Feb 2018, 05:22
Ed_P wrote:
27 Feb 2018, 04:34
jssouza wrote:
26 Feb 2018, 07:03
- porteus.cfg does have changes=/porteus. AFAIK, this was the same even in porteus 3.2.2.
I think there is a different file with 4.0.
brokenman https//forum.porteus.org/viewtopic.php?f=35&t=7561 wrote: New configuration file at porteus/porteus-v4.0-x86_64.cfg
Ed_P, we are talking about /boot/syslinux/porteus.cfg
It is my understanding that the latter has been replaced with the former. Are you saying 4.0 has two .cfg files!!
Ed

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus-v4.0rc4 bug reports

Post#36 by jssouza » 27 Feb 2018, 06:57

Ed_P wrote:
27 Feb 2018, 06:52
Are you saying 4.0 has two .cfg files!!
Yes, porteus.cfg is for configuring syslinux the bootloader.
The .sgn file from earlier has been replaced by a .cfg file, which is used to configure porteus (with cheatcodes). It's just that both have the same extension.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v4.0rc4 bug reports

Post#37 by Ed_P » 27 Feb 2018, 07:14

hmmm but changes that can be made to the syslinux one, basically the boot menu, can be made to the new one. Specifically the location of the changes file. And then the question of which one gets used when on EFI vs BIOS systems.
Ed

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus-v4.0rc4 bug reports

Post#38 by jssouza » 27 Feb 2018, 07:33

Ed_P wrote:
27 Feb 2018, 07:14
And then the question of which one gets used when on EFI vs BIOS systems.
Does not matter EFI or BIOS. But if you mean which has higher precendence, from /mnt/live/finit it looks like porteus-v4.0-x86_64.cfg is checked first, hence has first preference.

brokenman, finit in initrd has the function value() defined twice.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v4.0rc4 bug reports

Post#39 by Ed_P » 27 Feb 2018, 14:15

In 3.2.2 the REFInd.conf file is the menu used on EFI systems and the porteus.cfg file on BIOS systems. The new 4.0 cfg file I thought was making for just 1 file to be used on either system. But in looking at the porteus-v4.0-x86_64.cfg file that certainly is not a menu file.
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-v4.0rc4 bug reports

Post#40 by ncmprhnsbl » 27 Feb 2018, 21:30

Ed_P wrote:
27 Feb 2018, 14:15
But in looking at the porteus-v4.0-x86_64.cfg file that certainly is not a menu file.
yeah Ed, it just does cheatcodes.
and note that whatever cheatcodes are set in that file will be passed to whatever boot entry you choose..
so special boot options ( say eg: load=foo noload=bah 3 ) should be in ReFind.conf or porteus.cfg.
and of course if you're booting isos via grub(or whatever), you have no option(without remastering) to edit porteus-v4.0-x86_64.cfg..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Binary Enigma
White ninja
White ninja
Posts: 4
Joined: 22 Feb 2018, 11:44
Distribution: Porteus v4 32 bit

Porteus-v4.0rc4 bug reports

Post#41 by Binary Enigma » 27 Feb 2018, 22:46

jssouza wrote:
27 Feb 2018, 05:22
Checked this logged in as guest and it works. Is this when you are logged in as root? This is upstream. Cinnamon developers have disabled logging in as root.
This turned out to be just a temporary bug, not sure, it no longer happens.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v4.0rc4 bug reports

Post#42 by Ed_P » 27 Feb 2018, 22:48

ncmprhnsbl wrote:
27 Feb 2018, 21:30
and of course if you're booting isos via grub (or whatever), you have no option (without remastering) to edit porteus-v4.0-x86_64.cfg..
Actually when booting via grub2 porteus-v4.0-x86_64.cfg, porteus.cfg and rEFInd.conf are not used. The booting options are specified in the grub2 menu and passed to vmlinuz.

Code: Select all

#
#  SubMenu Entry 1       Porteus 4.0
#
submenu     'Porteus 4.0'       --class submenu   --class icon-porteus   --class custom_001  {
#
# start-custom-code
# Set the timeout for the submenu
set timeout=30

# Set the subdefault variable to the submenu entry you prefer
set subdefault=1

set gfxpayload=1024x768

     set linux_folder=/porteus4.0
     if [ -f /boot/syslinux/vmlinuz ]; then linux_folder=""; fi
#     set iso=/ISOs/porteus-4.0rc3-x86_64-20180128.iso
#     LXQT  MATE  OPENBOX  XFCE
     set iso=/ISOs/Porteus-CINNAMON-v4.0rc4-x86_64.iso
#     set porteusmods="extramod=$linux_folder/003Modules;"
     set porteusmods="extramod="

menuentry " Porteus 4.0 ISO - AF" --class slackware   --class icon-porteus  {

     set boot_parms="volume=33 reboot=cold $porteusmods "
#     set boot_parms="volume=33 reboot=cold "

     search -f $iso --set=root
     loopback loop $iso
     linux  (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
     initrd (loop)/boot/syslinux/initrd.xz
     }

menuentry " Porteus 4.0 ISO - AF+" --class slackware   --class icon-porteus  {

#     set boot_parms="volume=33 reboot=cold noload=my40changes extramod=$linux_folder/003Modules;$linux_folder/Modules"
     set boot_parms="volume=33 reboot=cold noload=my40changes $porteusmods$linux_folder/Modules"

     search -f $iso --set=root
     loopback loop $iso
     linux  (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
     initrd (loop)/boot/syslinux/initrd.xz
     }

menuentry " Porteus 4.0 ISO - AF'" --class slackware   --class icon-porteus  {

#     set boot_parms="volume=33 reboot=cold  extramod=$linux_folder/003Modules;$linux_folder/Modules"
     set boot_parms="volume=33 reboot=cold  $porteusmods$linux_folder/Modules"

     search -f $iso --set=root
     loopback loop $iso
     linux  (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
     initrd (loop)/boot/syslinux/initrd.xz
     }

menuentry " Porteus 4.0 ISO" --class slackware   --class icon-porteus  {

#     set boot_parms="volume=33 reboot=cold noload=xfce load=cinn extramod=$linux_folder/Modules resolution=1600x900"
#     set boot_parms="volume=33 reboot=cold extramod=$linux_folder/003Modules;$linux_folder/Modules changes=EXIT:$linux_folder/changes/porteussave.dat 3"
#     set boot_parms="volume=33 reboot=cold noload=my40changes extramod=$linux_folder/003Modules;$linux_folder/Modules changes=EXIT:$linux_folder/changes/porteussave.dat"
     set boot_parms="volume=33 reboot=cold noload=my40changes $porteusmods$linux_folder/Modules changes=EXIT:$linux_folder/changes/porteussave.dat"

     search -f $iso --set=root
     loopback loop $iso
     linux  (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
     initrd (loop)/boot/syslinux/initrd.xz
     }
# end-custom-code
}
Ed

throwaway
Ronin
Ronin
Posts: 1
Joined: 28 Feb 2018, 07:24
Distribution: Manjaro

link http://goo.gl/ci4EE leads to an error 500

Post#43 by throwaway » 28 Feb 2018, 23:36

I get an error 500 when I follow the link http://goo.gl/ci4EE found on the file USB_INSTALLATION.txt produced after mounting Porteus-LXQT-v4.0rc4-x86_64

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

link http://goo.gl/ci4EE leads to an error 500

Post#44 by Ed_P » 01 Mar 2018, 01:19

hmmm Somebody forget to pay the annual fee?? B)
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-v4.0rc4 bug reports

Post#45 by ncmprhnsbl » 01 Mar 2018, 01:30

thanks, the correct (redirected) link should be: http://www.porteus.org/component/conten ... guide.html (i assume)
not : http://porteus.org/info/docs/37-install ... -v-10.html
i will move this post to the rc4.0 bug reports (done)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply