Porteus-v3.2.2 bug reports here
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2.2 bug reports here
^ This approach works: viewtopic.php?f=81&t=4632&p=33638#p33604 just disregard the first two points as they are not an option at this point.
Ed
-
- White ninja
- Posts: 5
- Joined: 09 May 2017, 21:39
- Distribution: (attempting) 3.2.2 xfce
- Location: Canada
Re: Porteus-v3.2.2 bug reports here
Thanks Ed_P for the tip. Unfortunately their was no change to either of my issues. I've also discovered that the newly created USB key won't boot on my older home machine or a newer laptop. All I see is the first line that starts with SYSLINUX 4.06 & then it just sits there. I will ask for help on the forums & report back here if it is a bug.Ed_P wrote:^ This approach works: viewtopic.php?f=81&t=4632&p=33638#p33604 just disregard the first two points as they are not an option at this point.
EDIT
Here is my newly created post viewtopic.php?f=140&t=6922
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Re: Porteus-v3.2.2 bug reports here
My Daughter recently got an Acer UEFI Laptop with seventh generation Processor and DDR4 memory,preloaded with Windows 10. Seeing discussions here,I fancied myself, to try Porteus-XFCE-v3.2.2 64 bit, in that machine with a Pen drive.
But,BIOS screen shows 'secure boot' enabled and locked.No way to navigate.
But there may be a provision to add a SSD and test, which I wouldn't venture.
1_In my Desktop, V3.2.2 64 bit runs well, but I felt 32 bit was faster.
During boot on entering level 4, a lot of information in very high resolution(small letters) is dumped by X11 before, showing the desktop.
Same way ,I noticed during shut down, the memory is not cleaned and shows lots of error messages(mostly about the last application) before unmounting union and all, to power off.
i remember to have read about rc.d rc.6, modification of script,regarding sync,unmount.
2)I am a fan of 'True Vector Internet monitor' from Zone alarm(2001) and still have it in XP. Net load plugin in XFCE is not able to initialize the interface error..The device name is 'eth0' and interface name is 'wired connection 1'. Any solution for this plugin to recognize this interface. I read that the naming is done by the Kernel.
3) Slony's module for Florence ,though gets installed and opens up, typing is not transferred to the screen,, dead I would say, still click sound heard in speakers. This is in XFCE. Donald said it works in KDE
But,BIOS screen shows 'secure boot' enabled and locked.No way to navigate.
But there may be a provision to add a SSD and test, which I wouldn't venture.
1_In my Desktop, V3.2.2 64 bit runs well, but I felt 32 bit was faster.
During boot on entering level 4, a lot of information in very high resolution(small letters) is dumped by X11 before, showing the desktop.
Same way ,I noticed during shut down, the memory is not cleaned and shows lots of error messages(mostly about the last application) before unmounting union and all, to power off.
i remember to have read about rc.d rc.6, modification of script,regarding sync,unmount.
2)I am a fan of 'True Vector Internet monitor' from Zone alarm(2001) and still have it in XP. Net load plugin in XFCE is not able to initialize the interface error..The device name is 'eth0' and interface name is 'wired connection 1'. Any solution for this plugin to recognize this interface. I read that the naming is done by the Kernel.
3) Slony's module for Florence ,though gets installed and opens up, typing is not transferred to the screen,, dead I would say, still click sound heard in speakers. This is in XFCE. Donald said it works in KDE
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
-
- Full of knowledge
- Posts: 2071
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
Re: Porteus-v3.2.2 bug reports here
@ raja
regarding florence
compile a new one
1.fetch the source and slackbuild from slackbuilds.org
2.open the florence.SlackBuild in mousepad and change
to
will work then in/with xfce;..tested in 3.2.2 XFCE 32 + mousepad.. 8)
regarding florence
compile a new one
1.fetch the source and slackbuild from slackbuilds.org
2.open the florence.SlackBuild in mousepad and change
Code: Select all
./configure \
--prefix=/usr \
Code: Select all
./configure \
--prefix=/usr --without-at-spi \
-
- Full of knowledge
- Posts: 2564
- Joined: 25 Jun 2014, 15:21
- Distribution: 3.2.2 Cinnamon & KDE5
- Location: London
Re: Porteus-v3.2.2 bug reports here
@ raja
Post moved to Intermediate/Advanced Section.
Post moved to Intermediate/Advanced Section.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Re: Porteus-v3.2.2 bug reports here
Could be that UEFI or something else is missing.
I just rebooted, even with the altered menu.lst I still get the same kernel trace/kernel panic:
Here some ls from sda1 and sda2:
why yes, I disabled/deleted all system boot fonts I don't need/don't want in sda1/Boot of Witless7 OS but en-US (would have preferred en-GB / en-UK but there is no such folder) and de-DE. Don't judge me. xD
As you can see: no such folders as isolinux (or syslinux) on sda1.
But on sda2, they are </yoda> :
Here again the current menu.lst, and the working 3.1 as well:
Hopefully one of you knows what's amiss. Should I copy the UEFI folder to sda1?
Or do you need to "install" UEFI?
I just rebooted, even with the altered menu.lst I still get the same kernel trace/kernel panic:
Code: Select all
[end trace]
kernel panic - not syncing: attempted to kill the idle task!
Code: Select all
root@porteus:/mnt/sda1# ls -o
total 196350
drwxrwxrwx 1 root 8192 Apr 13 21:41 Boot
drwxrwxrwx 1 root 0 Apr 13 21:45 Porteus_3.2.2
drwxrwxrwx 1 root 0 Jun 30 2010 Recovery
drwxrwxrwx 1 root 0 May 14 2010 System Volume Information
drwxrwxrwx 1 root 0 Oct 28 2011 TODO_new_Porteus
-rwxrwxrwx 2 root 188 May 11 2010 WinREPartition.ini
drwxrwxrwx 1 root 4096 Apr 22 08:02 backup
lrwxrwxrwx 1 root 16 Oct 28 2011 boot -> Boot
-rwxrwxrwx 1 root 383562 Jul 14 2009 bootmgr
drwxrwxrwx 1 root 4096 May 2 15:46 porteus
-rwxrwxrwx 1 root 99123200 Jul 14 2010 qrky-120.sfs
-rwxrwxrwx 1 root 101531648 Apr 18 07:55 qrkysave.3fs
drwxrwxrwx 1 root 4096 Jan 15 2011 quirky
drwxrwxrwx 1 root 0 Mar 20 06:52 tmp
lrwxrwxrwx 1 root 32 Oct 28 2011 welt -> ../sda5/welt
root@porteus:/mnt/sda1# ls -o Boot/
total 11856
-rwxrwxrwx 1 root 28672 Apr 25 03:41 BCD
-rwxrwxrwx 1 root 25600 Apr 23 20:33 BCD.LOG
-rwxrwxrwx 2 root 0 May 14 2010 BCD.LOG1
-rwxrwxrwx 2 root 0 May 14 2010 BCD.LOG2
-rwxrwxrwx 1 root 65536 May 14 2010 BOOTSTAT.DAT
drwxrwxrwx 1 root 0 May 14 2010 Fonts
-rwxrwxrwx 1 root 20190 Dec 23 00:00 cheatcodes_Porteus_3.2.2.txt
-rwxrwxrwx 1 root 0 Feb 24 2012 cs-CZ
-rwxrwxrwx 1 root 0 Feb 24 2012 da-DK
drwxrwxrwx 1 root 0 May 14 2010 de-DE
-rwxrwxrwx 1 root 0 Feb 24 2012 el-GR
drwxrwxrwx 1 root 0 May 14 2010 en-US
-rwxrwxrwx 1 root 0 Mar 5 2015 es-ES
-rwxrwxrwx 1 root 0 Feb 24 2012 fi-FI
-rwxrwxrwx 1 root 0 Feb 24 2012 fr-FR
-rwxrwxrwx 1 root 0 Feb 24 2012 hu-HU
-rwxrwxrwx 1 root 699656 Nov 25 2014 initrd.xz_Porteus_3.1_x86_64
-rwxrwxrwx 1 root 698872 Dec 23 00:00 initrd.xz_Porteus_3.2.2_x86_64
-rwxrwxrwx 1 root 1808240 Jul 14 2010 initrd_quirkyNOP120.gz
-rwxrwxrwx 1 root 0 Feb 24 2012 it-IT
-rwxrwxrwx 1 root 0 Feb 24 2012 ja-JP
-rwxrwxrwx 1 root 0 Feb 24 2012 ko-KR
-rwxrwxrwx 1 root 485440 Jul 14 2009 memtest.exe
-rwxrwxrwx 1 root 2057 Nov 27 2010 menu_FJ_Lifebook.lst
-rwxrwxrwx 1 root 4168 Nov 21 2010 menu_Q40.lst
-rwxrwxrwx 1 root 0 Feb 24 2012 nb-NO
-rwxrwxrwx 1 root 0 Feb 24 2012 nl-NL
-rwxrwxrwx 1 root 0 Feb 24 2012 pl-PL
-rwxrwxrwx 1 root 0 Feb 24 2012 pt-BR
-rwxrwxrwx 1 root 0 Feb 24 2012 pt-PT
-rwxrwxrwx 1 root 0 Feb 24 2012 ru-RU
-rwxrwxrwx 1 root 0 Feb 24 2012 sv-SE
-rwxrwxrwx 1 root 0 Feb 24 2012 tr-TR
-rwxrwxrwx 1 root 2825248 Dec 12 2014 vmlinuz_Porteus_3.1_x86_64
-rwxrwxrwx 1 root 3210784 Dec 23 00:00 vmlinuz_Porteus_3.2.2_x86_64
-rwxrwxrwx 1 root 2248032 Jul 14 2010 vmlinuz_quirkyNOP120
-rwxrwxrwx 1 root 0 Feb 24 2012 zh-CN
-rwxrwxrwx 1 root 0 Feb 24 2012 zh-HK
-rwxrwxrwx 1 root 0 Feb 24 2012 zh-TW
As you can see: no such folders as isolinux (or syslinux) on sda1.
But on sda2, they are </yoda> :
Code: Select all
root@porteus:/mnt/sda1# ls -o --time-style=long-iso /mnt/sda2/Boot/
total 636
drwxrwxrwx 1 root 4096 2017-05-03 09:00 .
drwxrwxrwx 1 root 12288 2017-05-03 13:21 ..
-rwxrwxrwx 1 root 24576 2010-05-06 09:48 BCD
-rwxrwxrwx 1 root 21504 2010-05-06 09:48 BCD.LOG
-rwxrwxrwx 2 root 0 2010-05-06 08:29 BCD.LOG1
-rwxrwxrwx 2 root 0 2010-05-06 08:29 BCD.LOG2
-rwxrwxrwx 1 root 65536 2010-05-06 08:29 BOOTSTAT.DAT
drwxrwxrwx 1 root 0 2010-05-06 08:29 Fonts
drwxrwxrwx 1 root 0 2010-05-06 08:29 de-DE
drwxrwxrwx 1 root 0 2010-05-06 08:29 en-US
drwxrwxrwx 1 root 0 2011-05-15 03:04 isolinux
-rwxrwxrwx 1 root 485440 2009-07-14 03:20 memtest.exe
-rwxrwxrwx 1 root 26442 2011-04-25 13:37 pxelinux.0
drwxrwxrwx 1 root 0 2011-05-15 03:04 pxelinux.cfg
drwxrwxrwx 1 root 4096 2011-05-15 03:04 syslinux
drwxrwxrwx 1 root 0 2011-05-15 03:04 tools
root@porteus:/mnt/sda1# ls -o /mnt/sda2/Boot/isolinux/
total 29
-rwxrwxrwx 1 root 24576 May 7 2011 isolinux.bin
-rwxrwxrwx 1 root 2048 May 7 2011 isolinux.boot
-rwxrwxrwx 1 root 26 Jan 5 2011 isolinux.cfg
Code: Select all
title Porteus 3.1 x86-64 XFCe
rootnoverify (hd0,0)
kernel (hd0,0)/Boot/vmlinuz_Porteus_3.1_x86_64 ramsize=45% zram=20% timezone=Europe/Berlin volume=75% kmap=de sgnfile=porteus_intHDD1_1.sgn
initrd (hd0,0)/Boot/initrd.xz_Porteus_3.1_x86_64
boot
title Porteus 3.2.2 x86-64 XFCe
rootnoverify (hd0,0)
kernel (hd0,0)/Boot/vmlinuz_Porteus_3.2.2_x86_64 from=/mnt/sda1/Porteus_3.2.2/ ramsize=45% zram=20% timezone=Europe/Berlin volume=75% kmap=de sgnfile=porteus-v3.2.2_intHDD1-x86_64.sgn
initrd (hd0,0)/Boot/initrd.xz_Porteus_3.2.2_x86_64
boot
Or do you need to "install" UEFI?
Cheers!
Yours Rava
Yours Rava
-
- Shogun
- Posts: 282
- Joined: 10 Jan 2016, 17:26
- Distribution: Porteus 5.0 rc3 xfce
- Location: Denver, Colorado
Re: Porteus-v3.2.2 bug reports here
"login=guest" takes me to the login screen -- is there any way to simply log users in as guest from the Porteus boot menu without requiring them to enter the credentials manually?
UPDATE: after a couple of manual logins, "login=guest" is working correctly, without requiring manual signin.
P.S. brokenman, please see viewtopic.php?f=48&t=6543&p=55151#p55151 and/or viewtopic.php?f=140&t=6928 -- can this be fixed?
UPDATE: after a couple of manual logins, "login=guest" is working correctly, without requiring manual signin.
P.S. brokenman, please see viewtopic.php?f=48&t=6543&p=55151#p55151 and/or viewtopic.php?f=140&t=6928 -- can this be fixed?
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2.2 bug reports here
That is what the login= cheatcode is designed to do.rchase wrote:"login=guest" takes me to the login screen
I've never used the login= cheatcode and I've always booted to the guest account without a prompt.-- is there any way to simply log users in as guest from the Porteus boot menu without requiring them to enter the credentials manually?
Not a bug.
Ed
-
- Shogun
- Posts: 282
- Joined: 10 Jan 2016, 17:26
- Distribution: Porteus 5.0 rc3 xfce
- Location: Denver, Colorado
Re: Porteus-v3.2.2 bug reports here
I edited my post; now the "login=guest" cheatcode takes me "to the guest account without a prompt" -- not "what the login= cheatcode is designed to do", according to you. By your reasoning, this behavior should be a bug; to mine, it is simply inconsistent behavior across boots that seems to have resolved itself into that I desired.Ed_P wrote:That is what the login= cheatcode is designed to do.rchase wrote:"login=guest" takes me to the login screen
I've never used the login= cheatcode and I've always booted to the guest account without a prompt.-- is there any way to simply log users in as guest from the Porteus boot menu without requiring them to enter the credentials manually?
Not a bug.
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Re: Porteus-v3.2.2 bug reports here
I already posted that in the above post... It's below "Here some ls from sda1 and sda2:"Ed_P wrote:^ What's the sda1 Boot folder look like?
I post it ... again :
Code: Select all
root@porteus:/mnt/sda1# ls -o Boot/
total 11856
-rwxrwxrwx 1 root 28672 Apr 25 03:41 BCD
-rwxrwxrwx 1 root 25600 Apr 23 20:33 BCD.LOG
-rwxrwxrwx 2 root 0 May 14 2010 BCD.LOG1
-rwxrwxrwx 2 root 0 May 14 2010 BCD.LOG2
-rwxrwxrwx 1 root 65536 May 14 2010 BOOTSTAT.DAT
drwxrwxrwx 1 root 0 May 14 2010 Fonts
-rwxrwxrwx 1 root 20190 Dec 23 00:00 cheatcodes_Porteus_3.2.2.txt
-rwxrwxrwx 1 root 0 Feb 24 2012 cs-CZ
-rwxrwxrwx 1 root 0 Feb 24 2012 da-DK
drwxrwxrwx 1 root 0 May 14 2010 de-DE
-rwxrwxrwx 1 root 0 Feb 24 2012 el-GR
drwxrwxrwx 1 root 0 May 14 2010 en-US
-rwxrwxrwx 1 root 0 Mar 5 2015 es-ES
-rwxrwxrwx 1 root 0 Feb 24 2012 fi-FI
-rwxrwxrwx 1 root 0 Feb 24 2012 fr-FR
-rwxrwxrwx 1 root 0 Feb 24 2012 hu-HU
-rwxrwxrwx 1 root 699656 Nov 25 2014 initrd.xz_Porteus_3.1_x86_64
-rwxrwxrwx 1 root 698872 Dec 23 00:00 initrd.xz_Porteus_3.2.2_x86_64
-rwxrwxrwx 1 root 1808240 Jul 14 2010 initrd_quirkyNOP120.gz
-rwxrwxrwx 1 root 0 Feb 24 2012 it-IT
-rwxrwxrwx 1 root 0 Feb 24 2012 ja-JP
-rwxrwxrwx 1 root 0 Feb 24 2012 ko-KR
-rwxrwxrwx 1 root 485440 Jul 14 2009 memtest.exe
-rwxrwxrwx 1 root 2057 Nov 27 2010 menu_FJ_Lifebook.lst
-rwxrwxrwx 1 root 4168 Nov 21 2010 menu_Q40.lst
-rwxrwxrwx 1 root 0 Feb 24 2012 nb-NO
-rwxrwxrwx 1 root 0 Feb 24 2012 nl-NL
-rwxrwxrwx 1 root 0 Feb 24 2012 pl-PL
-rwxrwxrwx 1 root 0 Feb 24 2012 pt-BR
-rwxrwxrwx 1 root 0 Feb 24 2012 pt-PT
-rwxrwxrwx 1 root 0 Feb 24 2012 ru-RU
-rwxrwxrwx 1 root 0 Feb 24 2012 sv-SE
-rwxrwxrwx 1 root 0 Feb 24 2012 tr-TR
-rwxrwxrwx 1 root 2825248 Dec 12 2014 vmlinuz_Porteus_3.1_x86_64
-rwxrwxrwx 1 root 3210784 Dec 23 00:00 vmlinuz_Porteus_3.2.2_x86_64
-rwxrwxrwx 1 root 2248032 Jul 14 2010 vmlinuz_quirkyNOP120
-rwxrwxrwx 1 root 0 Feb 24 2012 zh-CN
-rwxrwxrwx 1 root 0 Feb 24 2012 zh-HK
-rwxrwxrwx 1 root 0 Feb 24 2012 zh-TW
Cheers!
Yours Rava
Yours Rava
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2.2 bug reports here
Read the FAQ on what the login= cheatcode does. It is not designed for the default user id.rchase wrote: not "what the login= cheatcode is designed to do", according to you.
Ed
Re: Porteus-v3.2.2 bug reports here
LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/porteus
TEXT HELP
Run Porteus the best way we can.
Try to autoconfigure graphics
card and use the maximum
allowed resolution
ENDTEXT
the first line of porteus boot menu allow you to boot in init4 and always with guest account,the guest account is hardcoded into the system so you can't remove but you can use the root account if you want with a cheatcode or something like that,if you want to use a multiple system into a key syslinux maybe isn't the best bootloader to do this task, grub is better,but i do not know grub2.
MENU LABEL Graphics mode
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/porteus
TEXT HELP
Run Porteus the best way we can.
Try to autoconfigure graphics
card and use the maximum
allowed resolution
ENDTEXT
the first line of porteus boot menu allow you to boot in init4 and always with guest account,the guest account is hardcoded into the system so you can't remove but you can use the root account if you want with a cheatcode or something like that,if you want to use a multiple system into a key syslinux maybe isn't the best bootloader to do this task, grub is better,but i do not know grub2.
-
- Shogun
- Posts: 282
- Joined: 10 Jan 2016, 17:26
- Distribution: Porteus 5.0 rc3 xfce
- Location: Denver, Colorado
Re: Porteus-v3.2.2 bug reports here
No need; I just pointed out to you that your claim that use of "login=guest" is supposed to take users to the manual login screen is belied by the behavior of the OS, which (now) automatically signs me into the guest account when using "login=guest" and into the root account when I use "login=root".Ed_P wrote:Read the FAQ on what the login= cheatcode does. It is not designed for the default user id.rchase wrote: not "what the login= cheatcode is designed to do", according to you.
- Ed_P
- Contributor
- Posts: 8369
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Porteus-v3.2.2 bug reports here
I replaced my Porteus porteus-4.9.12 vmlinuz and 000-kernel.xzm modules with the ones from http://dl.porteus.org/x86_64/kernel/porteus-4.10.8/. This resulted in Porteus hanging on "copying content of /mnt/isoloop/porteus/rootcopy directory" when booting. I reverted back to the porteus-4.9.12 files.
Ed