Porteus-v3.2.2 bug reports here

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.

Re: Porteus-v3.2.2 bug reports here

Postby CyberScooby » 10 May 2017, 00:12

Issue #2
same installation setup as before except I am now using a DOS partition scheme instead of GPT.

Now I am receiving a segfault from extlinux.com. I tried https://forum.porteus.org/viewtopic.php?f=117&t=3774&p=27173&hilit=extlinux.com#p27174 but still received a segfault. So as per the post I switched from using the Porteus boot CD and instead used the latest Arch Linux install CD which worked like a charm. The Porteus Linux installer is reporting success. Time to reboot. :Yahoo!:
CyberScooby
White ninja
White ninja
 
Posts: 5
Joined: 09 May 2017, 22:39
Location: Canada
Distribution: (attempting) 3.2.2 xfce

Re: Porteus-v3.2.2 bug reports here

Postby Ed_P » 10 May 2017, 00:55

^ This approach works: UEFI Boot Confusion [Solved] just disregard the first two points as they are not an option at this point.
Ed
User avatar
Ed_P
Contributor
Contributor
 
Posts: 2800
Joined: 06 Feb 2013, 23:12
Location: Western NY, USA
Distribution: Cinnamon 3.2.* 64-bit ISO

Re: Porteus-v3.2.2 bug reports here

Postby CyberScooby » 10 May 2017, 15:58

Ed_P wrote:^ This approach works: UEFI Boot Confusion [Solved] just disregard the first two points as they are not an option at this point.


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.

EDIT
Here is my newly created post https://forum.porteus.org/viewtopic.php?f=140&t=6922
CyberScooby
White ninja
White ninja
 
Posts: 5
Joined: 09 May 2017, 22:39
Location: Canada
Distribution: (attempting) 3.2.2 xfce

Re: Porteus-v3.2.2 bug reports here

Postby raja » 11 May 2017, 10:25

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
raja
White ninja
White ninja
 
Posts: 8
Joined: 02 May 2017, 10:51
Location: India
Distribution: 3.1 and 3.2.2

Re: Porteus-v3.2.2 bug reports here

Postby donald » 11 May 2017, 17:41

@ 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
Code: Select all
./configure \
  --prefix=/usr  \

to
Code: Select all
./configure \
  --prefix=/usr --without-at-spi \

will work then in/with xfce;..tested in 3.2.2 XFCE 32 + mousepad.. 8)
donald
Full of knowledge
Full of knowledge
 
Posts: 1040
Joined: 17 Jun 2013, 14:17
Location: Germany
Distribution: Porteus 3.2.2 XFCE 32bit

Re: Porteus-v3.2.2 bug reports here

Postby Bogomips » 15 May 2017, 14:56

@ raja
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
Bogomips
Full of knowledge
Full of knowledge
 
Posts: 2295
Joined: 25 Jun 2014, 16:21
Location: London
Distribution: 3.2.2 Cinnamon & KDE5

Re: Porteus-v3.2.2 bug reports here

Postby Rava » 18 May 2017, 14:24

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:
Code: Select all
[end trace]
kernel panic - not syncing: attempted to kill the idle task!


Here some ls from sda1 and sda2:

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

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> :
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


Here again the current menu.lst, and the working 3.1 as well:
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


Hopefully one of you knows what's amiss. Should I copy the UEFI folder to sda1?
Or do you need to "install" UEFI?
Cheers!
Yours Rava
User avatar
Rava
Contributor
Contributor
 
Posts: 1280
Joined: 11 Jan 2011, 03:46
Location: Germany
Distribution: Porteus 3.1.0 x86-64 XFCe

Re: Porteus-v3.2.2 bug reports here

Postby Ed_P » 18 May 2017, 16:02

^ What's the sda1 Boot folder look like?
Ed
User avatar
Ed_P
Contributor
Contributor
 
Posts: 2800
Joined: 06 Feb 2013, 23:12
Location: Western NY, USA
Distribution: Cinnamon 3.2.* 64-bit ISO

Re: Porteus-v3.2.2 bug reports here

Postby rchase » 19 May 2017, 03:01

"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 Installing on a 3.0 USB Stick and/or Installing on USB 3.0 flash drive -- can this be fixed?
rchase
Samurai
Samurai
 
Posts: 139
Joined: 10 Jan 2016, 18:26
Location: Denver, Colorado
Distribution: Porteus 3.2.2 xfce

Re: Porteus-v3.2.2 bug reports here

Postby Ed_P » 19 May 2017, 06:25

rchase wrote:"login=guest" takes me to the login screen

That is what the login= cheatcode is designed to do.

-- is there any way to simply log users in as guest from the Porteus boot menu without requiring them to enter the credentials manually?

I've never used the login= cheatcode and I've always booted to the guest account without a prompt.

Not a bug.
Ed
User avatar
Ed_P
Contributor
Contributor
 
Posts: 2800
Joined: 06 Feb 2013, 23:12
Location: Western NY, USA
Distribution: Cinnamon 3.2.* 64-bit ISO

Re: Porteus-v3.2.2 bug reports here

Postby rchase » 19 May 2017, 07:36

Ed_P wrote:
rchase wrote:"login=guest" takes me to the login screen

That is what the login= cheatcode is designed to do.

-- is there any way to simply log users in as guest from the Porteus boot menu without requiring them to enter the credentials manually?

I've never used the login= cheatcode and I've always booted to the guest account without a prompt.

Not a bug.

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.
rchase
Samurai
Samurai
 
Posts: 139
Joined: 10 Jan 2016, 18:26
Location: Denver, Colorado
Distribution: Porteus 3.2.2 xfce

Re: Porteus-v3.2.2 bug reports here

Postby Rava » 19 May 2017, 14:53

Ed_P wrote:^ What's the sda1 Boot folder look like?


I already posted that in the above post... It's below "Here some ls from sda1 and sda2:"

I post it ... again :roll: :

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
User avatar
Rava
Contributor
Contributor
 
Posts: 1280
Joined: 11 Jan 2011, 03:46
Location: Germany
Distribution: Porteus 3.1.0 x86-64 XFCe

Re: Porteus-v3.2.2 bug reports here

Postby Ed_P » 19 May 2017, 16:33

rchase wrote: not "what the login= cheatcode is designed to do", according to you.

Read the FAQ on what the login= cheatcode does. It is not designed for the default user id.
Ed
User avatar
Ed_P
Contributor
Contributor
 
Posts: 2800
Joined: 06 Feb 2013, 23:12
Location: Western NY, USA
Distribution: Cinnamon 3.2.* 64-bit ISO

Re: Porteus-v3.2.2 bug reports here

Postby beny » 19 May 2017, 16:36

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.
beny
Full of knowledge
Full of knowledge
 
Posts: 709
Joined: 02 Jan 2011, 12:33
Location: italy

Re: Porteus-v3.2.2 bug reports here

Postby rchase » 19 May 2017, 17:08

Ed_P wrote:
rchase wrote: not "what the login= cheatcode is designed to do", according to you.

Read the FAQ on what the login= cheatcode does. It is not designed for the default user id.

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".
rchase
Samurai
Samurai
 
Posts: 139
Joined: 10 Jan 2016, 18:26
Location: Denver, Colorado
Distribution: Porteus 3.2.2 xfce

PreviousNext

Return to Bug Reports



Who is online

Users browsing this forum: No registered users and 2 guests