Porteus 3.0 final feedback

[Rava]

Yes it remembers. The default is 5 minutes. It can be changed to whatever you like or removed.

Just a few minutes sounds reasonable. Is that also set in sudoers?

//edit
Nope, looked into sudoer and I did not find any such entry, unless it's the default behaviour...

[brokenman]

Edit sudoers (you should use visudo) and add this:

Defaults timestamp_timeout=0

It will then ask every time. Set to 1 for 1 minute.

[Rava]

But why is it set to 5 minutes when no such entry is in the file?

Does it have another setup file? Or is that it's default behaviour?

[brokenman]

It is the default behaviour. See: man sudoers

[Rava]

Yeah, silly me should have looked up "timeout" in the manpage instead of asking that.

Thanks for the heads up. Set it to 1 min, more secure. And it should be long enough.

[inspector]

Porteus XFCE 3.0 64-bit Bug

It seems the boot usb is ejected when the system is suspended (put to sleep). When the system is awakened, an "Input/Output" error is generated for any application or code that was not used before the system was suspended. I used the noeject cheatcode, but this did not fix the problem. Replicated on two machines.

Here's how to recreate it:

1) Boot the system.

2) Launch Thunar and a Terminal.

3) Suspend the system.

4) Wake up the system.

5) Try to launch an application other than Thunar or Terminal (Eg. Geany).

If you are using the noeject cheatcode, the boot usb does not appear in Thunar's device list in step 2, but appears after step 4, which indicates that the usb was remounted. This behavior is different from Porteus 2.0, where the boot device never shows up in Thunar's device list.

Thanks and keep up the good work!

[fanthom]

hi inspector,

is copy2ram an option for you? if yes, and if you are not saving changes on the stick then it could be the solution (porteus would be fully independent from the booting media).

[inspector]

Hi fanthom,

Unfortunately, the total size of my modules is quite large and would take up to much ram. I am saving changes using magic folders. As a temporary fix, I have disabled sleep. Is it possible that the mopt cheat code could help?

[fanthom]

Is it possible that the mopt cheat code could help?

dont think so. today i will dig into this problem and let you know what i find.

[fanthom]

@inspector

cant recreate this bug. everything works ok after suspend - tested in XFCE and KDE4.
please recreate this bug once more -> generate 'psinfo' report -> upload to pastebin.com -> link here.

thanks

[inspector]

@fanthom

I booted Porteus using Always Fresh and here's what I got.

This is psinfo before sleep : http://pastebin.com/PEFF1wf2
This is psinfo after resume: http://pastebin.com/i2qT2w1A

Notice that the block device lists in the psinfo reports are different. As well, in the Partition lists, the boot device partition (labelled "Cruzer") changes from /dev/sdb to /dev/sdc.

Thanks for looking into this.

[fanthom]

yes i see it got remounted but i still cant recreate it on my PC.
here is my pastebin after a suspend:
http://pastebin.com/pCv7TeUM

most important parts:

Code: Select all

# Porteus data found in:
/mnt/sdc1/porteus

Code: Select all

Jul  4 20:27:05 porteus kernel: [    3.014086] scsi 8:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
Jul  4 20:27:05 porteus kernel: [    3.014834] sd 8:0:0:0: [sdc] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB)
Jul  4 20:27:05 porteus kernel: [    3.015829] sd 8:0:0:0: [sdc] Write Protect is off
Jul  4 20:27:05 porteus kernel: [    3.016831] sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul  4 20:27:05 porteus kernel: [    3.022364]  sdc: sdc1
Jul  4 20:27:05 porteus kernel: [    3.026224] sd 8:0:0:0: [sdc] Attached SCSI removable disk

Code: Select all

Jul  4 20:28:02 porteus kernel: [   35.813167] i8042 kbd 00:09: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   35.813169] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Jul  4 20:28:02 porteus kernel: [   35.813175] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul  4 20:28:02 porteus kernel: [   35.813210] sd 0:0:0:0: [sda] Stopping disk
Jul  4 20:28:02 porteus kernel: [   35.813315] sd 1:0:0:0: [sdb] Stopping disk
Jul  4 20:28:02 porteus kernel: [   47.083255] [drm] Disabling audio 0 support
Jul  4 20:28:02 porteus kernel: [   47.787307] PM: suspend of devices complete after 11959.952 msecs
Jul  4 20:28:02 porteus kernel: [   47.787462] PM: late suspend of devices complete after 0.152 msecs
Jul  4 20:28:02 porteus kernel: [   47.798201] ehci-pci 0000:00:16.2: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.809108] ohci-pci 0000:00:16.0: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.809151] ohci-pci 0000:00:14.5: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.809216] ehci-pci 0000:00:13.2: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.820123] ohci-pci 0000:00:13.0: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.820146] ehci-pci 0000:00:12.2: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.831139] ohci-pci 0000:00:12.0: System wakeup enabled by ACPI
Jul  4 20:28:02 porteus kernel: [   47.831185] PM: noirq suspend of devices complete after 43.656 msecs
Jul  4 20:28:02 porteus kernel: [   47.831880] ACPI: Preparing to enter system sleep state S3
Jul  4 20:28:02 porteus kernel: [   47.832522] PM: Saving platform NVS memory
Jul  4 20:28:02 porteus kernel: [   47.837305] smpboot: CPU 1 is now offline
Jul  4 20:28:02 porteus kernel: [   47.839423] smpboot: CPU 2 is now offline
Jul  4 20:28:02 porteus kernel: [   47.840849] smpboot: CPU 3 is now offline
Jul  4 20:28:02 porteus kernel: [   47.842847] smpboot: CPU 4 is now offline
Jul  4 20:28:02 porteus kernel: [   47.844149] smpboot: CPU 5 is now offline
Jul  4 20:28:02 porteus kernel: [   47.846130] smpboot: CPU 6 is now offline
Jul  4 20:28:02 porteus kernel: [   47.847418] smpboot: CPU 7 is now offline
Jul  4 20:28:02 porteus kernel: [   47.848954] ACPI: Low-level resume complete
Jul  4 20:28:02 porteus kernel: [   47.848980] PM: Restoring platform NVS memory
Jul  4 20:28:02 porteus kernel: [   47.850537] LVT offset 0 assigned for vector 0x400
Jul  4 20:28:02 porteus kernel: [   47.850588] Enabling non-boot CPUs ...
Jul  4 20:28:02 porteus kernel: [   47.850625] x86: Booting SMP configuration:
Jul  4 20:28:02 porteus kernel: [   47.850626] smpboot: Booting Node 0 Processor 1 APIC 0x11
Jul  4 20:28:02 porteus kernel: [   48.523804] Initializing CPU#1
Jul  4 20:28:02 porteus kernel: [    0.002000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
Jul  4 20:28:02 porteus kernel: [   48.332555] CPU1 is up
Jul  4 20:28:02 porteus kernel: [   48.332555] smpboot: Booting Node 0 Processor 2 APIC 0x12
Jul  4 20:28:02 porteus kernel: [    0.002000] Initializing CPU#2
Jul  4 20:28:02 porteus kernel: [   48.343943] CPU2 is up
Jul  4 20:28:02 porteus kernel: [   48.343958] smpboot: Booting Node 0 Processor 3 APIC 0x13
Jul  4 20:28:02 porteus kernel: [    0.002000] Initializing CPU#3
Jul  4 20:28:02 porteus kernel: [   48.355188] CPU3 is up
Jul  4 20:28:02 porteus kernel: [   48.355202] smpboot: Booting Node 0 Processor 4 APIC 0x14
Jul  4 20:28:02 porteus kernel: [    0.002000] Initializing CPU#4
Jul  4 20:28:02 porteus kernel: [   48.366441] CPU4 is up
Jul  4 20:28:02 porteus kernel: [   48.366455] smpboot: Booting Node 0 Processor 5 APIC 0x15
Jul  4 20:28:02 porteus kernel: [    0.002000] Initializing CPU#5
Jul  4 20:28:02 porteus kernel: [   48.377696] CPU5 is up
Jul  4 20:28:02 porteus kernel: [   48.377710] smpboot: Booting Node 0 Processor 6 APIC 0x16
Jul  4 20:28:02 porteus kernel: [    0.002000] Initializing CPU#6
Jul  4 20:28:02 porteus kernel: [   48.388965] CPU6 is up
Jul  4 20:28:02 porteus kernel: [   48.388978] smpboot: Booting Node 0 Processor 7 APIC 0x17
Jul  4 20:28:02 porteus kernel: [    0.002000] Initializing CPU#7
Jul  4 20:28:02 porteus kernel: [   48.400229] CPU7 is up
Jul  4 20:28:02 porteus kernel: [   48.410927] Switched to clocksource acpi_pm
Jul  4 20:28:02 porteus kernel: [   48.410922] ACPI: Waking up from system sleep state S3
Jul  4 20:28:02 porteus kernel: [   48.410951] ohci-pci 0000:00:12.0: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] ehci-pci 0000:00:12.2: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] ohci-pci 0000:00:13.0: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] ehci-pci 0000:00:13.2: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] ohci-pci 0000:00:14.5: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] ohci-pci 0000:00:16.0: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] ehci-pci 0000:00:16.2: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] PM: noirq resume of devices complete after 77.220 msecs
Jul  4 20:28:02 porteus kernel: [   48.410951] PM: early resume of devices complete after 0.055 msecs
Jul  4 20:28:02 porteus kernel: [   48.410951] i8042 kbd 00:09: System wakeup disabled by ACPI
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000).
Jul  4 20:28:02 porteus kernel: [   48.410951] radeon 0000:01:00.0: WB enabled
Jul  4 20:28:02 porteus kernel: [   48.410951] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffb42c00
Jul  4 20:28:02 porteus kernel: [   48.410951] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffb42c0c
Jul  4 20:28:02 porteus kernel: [   48.410951] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c598 and cpu addr 0xf919c598
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] ring test on 0 succeeded in 1 usecs
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] ring test on 3 succeeded in 1 usecs
Jul  4 20:28:02 porteus kernel: [   48.410951] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul  4 20:28:02 porteus kernel: [   48.410951] ata4: SATA link down (SStatus 0 SControl 300)
Jul  4 20:28:02 porteus kernel: [   48.410951] ata3: SATA link down (SStatus 0 SControl 300)
Jul  4 20:28:02 porteus kernel: [   48.410951] ata1.00: configured for UDMA/133
Jul  4 20:28:02 porteus kernel: [   48.410951] ata6: SATA link down (SStatus 0 SControl 300)
Jul  4 20:28:02 porteus kernel: [   48.410951] ata5: SATA link down (SStatus 0 SControl 300)
Jul  4 20:28:02 porteus kernel: [   48.410951] sd 0:0:0:0: [sda] Starting disk
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] ring test on 5 succeeded in 1 usecs
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] UVD initialized successfully.
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] Enabling audio 0 support
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] ib test on ring 0 succeeded in 0 usecs
Jul  4 20:28:02 porteus kernel: [   48.410951] [drm] ib test on ring 3 succeeded in 1 usecs
Jul  4 20:28:02 porteus kernel: [   48.410951] usb 5-3: reset low-speed USB device number 2 using ohci-pci
Jul  4 20:28:02 porteus kernel: [   48.427235] [drm] ib test on ring 5 succeeded
Jul  4 20:28:02 porteus kernel: [   48.790245] usb 1-4: reset high-speed USB device number 2 using ehci-pci
Jul  4 20:28:02 porteus kernel: [   53.185029] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul  4 20:28:02 porteus kernel: [   53.193300] ata2.00: configured for UDMA/133
Jul  4 20:28:02 porteus kernel: [   53.204316] sd 1:0:0:0: [sdb] Starting disk
Jul  4 20:28:02 porteus kernel: [   53.210479] PM: resume of devices complete after 5382.252 msecs

in your case i can also see:

Code: Select all

Jul  4 09:32:21 porteus kernel: [   99.447973] PM: resume of devices complete after 2362.560 msecs

but then some weird thing happens:

Code: Select all

Jul  4 09:32:21 porteus kernel: [   99.555055] usb 1-4: USB disconnect, device number 3
Jul  4 09:32:21 porteus kernel: [   99.555482] scsi 6:0:0:0: killing request
Jul  4 09:32:21 porteus kernel: [   99.668036] usb 1-4: new high-speed USB device number 4 using ehci-pci
Jul  4 09:32:21 porteus logger: ACPI group jack / action lineout is not defined
Jul  4 09:32:21 porteus logger: ACPI group jack / action videoout is not defined
Jul  4 09:32:21 porteus kernel: [   99.786248] usb-storage 1-4:1.0: USB Mass Storage device detected
Jul  4 09:32:21 porteus kernel: [   99.795051] scsi7 : usb-storage 1-4:1.0

and later your stick gets renamed as sdc:

Code: Select all

Jul  4 09:32:23 porteus kernel: [  100.796885] scsi 7:0:0:0: Direct-Access     SanDisk  U3 Cruzer Micro  4.04 PQ: 0 ANSI: 2
Jul  4 09:32:23 porteus kernel: [  100.798626] sd 7:0:0:0: [sdc] 8027793 512-byte logical blocks: (4.11 GB/3.82 GiB)
Jul  4 09:32:23 porteus kernel: [  100.799722] sd 7:0:0:0: [sdc] Write Protect is off
Jul  4 09:32:23 porteus kernel: [  100.807626]  sdc:
Jul  4 09:32:23 porteus kernel: [  100.810110] sd 7:0:0:0: [sdc] Attached SCSI removable disk

i see only one difference between our setups: my stick has partition while your one does not.
could you create partition on it, reformat it with VFAT and check if that makes any difference?

thanks

[inspector]

@fanthom

Thanks for the suggestion. I used gParted to create a partition table on the usb, created on partition, and recopied Porteus to it. Porteus is initially mounted as sdb1 instead of sdb, but the issue is still there. I will keep investigating.

[MacGuges]

Since installing Porteus 3.0 last weekend I've observed that flash in Firefox will crash more often than not. Has anyone else encountered this? While I can still watch videos or check the weather report, I've observed that any flash will eventually crash after switching to another tab. Of course Firefox has also, frequently, become unresponsive for several seconds at a time.

Under the circumstances I consider I ought to switch back to Chrome. But I would like to help the devs here identify the problem, if there isn't something I can do right now to fix this.

EDIT: Oops, this wasn't the best place for this question. Pardon me for posting to this old thread.

[brokenman]

Has anyone else encountered this?

Yes. I have a feeling it is related to GPU. Perhaps some settings in about:config to disable some aspect of rendering can help. Updating to Porteus v3.0.1 I don't notice the crash so often (onboard intel graphics). I also use chrome for this reason.