Porteus 3.0 final feedback

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus 3.0 final feedback

Post#106 by fanthom » 29 Apr 2014, 13:42

Any ideas??
yes - please setup changes and provide log files after the crash. i wish to get whole /var/log or at least /var/log/messages.
thanks
Please add [Solved] to your thread title if the solution was found.

User avatar
Obosan
Samurai
Samurai
Posts: 113
Joined: 28 Mar 2014, 17:02
Distribution: Porteus xfce 32BIT v3.0
Location: JAPAN

Re: Porteus 3.0 final feedback

Post#107 by Obosan » 29 Apr 2014, 21:38

@wread Buenos dias.

Your Toshiba Satellite is not dead yet. :angel:
If you google "Toshiba Satellite black cursor", you'll find that the problem occured due to the sleep mode setting.
This is typical on Toshiba Satellite W$ Vista pre-installed models and some XP ones updated to W$7.

At first you might need to reset cmos of your computer by short jumper pins.
http://laptop-and-passwords.blogspot.sk ... l-for.html
I hope you'll find your model in the blog.
How to short will be find in YouTube by serching "Toshiba Satellite cmos reset".
(This procedure won't be necessary if you can see the bios menu after reboot.)

Then after reboot Porteus, you need to modify your Power Manager Settings.
No sleep mode! Both on AC and on Battery.
(Hybernate doesn't work properly on Satellite. I'm not sure in case of Suspend, though.)

Adios.

User avatar
wread
Module Guard
Module Guard
Posts: 1065
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus 3.0 final feedback

Post#108 by wread » 30 Apr 2014, 03:07

Hi Tom!
I made as you said, logged in with changes=/porteus so to record the last seconds before the crash. Rebooted, zipped the folder /changes/var/log and sent it to mediafire: http://www.mediafire.com/download/tr4db ... log.tar.gz

This time I didn't log in base_only norootcopy, but I don't think it matters..I hope you can pinpoint suspicious agents.

Thanks
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

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

Re: Porteus 3.0 final feedback

Post#109 by fanthom » 30 Apr 2014, 10:14

@wread
unfortunately i see nothing in the log files. probably disabling ACPI is the only solution so please try 'acpi=off' cheatcode. 'sleep' feature will be disabled but at least your PC should not crash when idling.
Please add [Solved] to your thread title if the solution was found.

User avatar
wread
Module Guard
Module Guard
Posts: 1065
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus 3.0 final feedback

Post#110 by wread » 30 Apr 2014, 11:56

@fanthom
Weird thing....With cheatcode acpi=off the machine will not start!

It stops at the third line by "loading intirdxz.....ready" and then the ventilator blows at maximum speed; the start process falls in a loop and can not advance.

I also tried some settings at the Bios level (Advanced>Wakeup on Keybord=on) without success. I will keep on trying and report any progress.

Regards!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1065
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus 3.0 final feedback

Post#111 by wread » 30 Apr 2014, 21:27

@Obosan

I am studying your post to see if my model can be treated as described in that blog.

As soon as I have understand all I have to do and try it, I will report back. That seems to be an issue of Toshiba machines.....

Thank you, Obosan, for the tip!

Regards
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

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

Re: Porteus 3.0 final feedback

Post#112 by brokenman » 01 May 2014, 01:00

That seems to be an issue of Toshiba machines.....
Yes my toshiba satellite also suffers this. I remember having to use the acpi=force kernel cheat. It would then wake up from sleeping. I will do some more testing to pinpoint where the problem is.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1065
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus 3.0 final feedback

Post#113 by wread » 01 May 2014, 12:56

@brokenman
Now I tried acpi=force cheatcode without success...

Then I started the system in text mode, started x (xinit) and then started google-earth (kde was not running); after 10 minutes or so GE went sleep, I moved the mouse and it woke up ok!

As the crash doesn't happen in Porteus 2.1, it is an issue of 003-kde vs. Toshiba Satellite..., no doubt!

I will keep trying and reporting.

Cheers!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1065
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus 3.0 final feedback

Post#114 by wread » 03 May 2014, 02:21

Eureka :Yahoo!:

Te crash probably caused by powerdevil 4.11.7 module of 003-kde3 (triggered by ksmserver 4.11.7 !). The bug was reported recently and solved upstream (April 2004).

I just disabled it in System Settings>Startup and Shutdown>Service Manager>Uncheck Power Management!

Now I get a blackscreen after about 10 minutes of idling, and when I move the mouse, the computer wakes up normally.

I have then put the new systemsettingsrc in rootcopy, so by restart the Power Management is unchecked.

Porteus 3.0 KDE4 is again the best :)

EDIT: I must say that now it comes up without wallpaper (wallpaper starts with the function I suppressed); so i must set it by hand....
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus 3.0 final feedback

Post#115 by Rava » 03 May 2014, 21:17

Issues with cdrecord:

Code: Select all

root@porteus:/mnt/live/memory/images# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a16 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2013 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Funny, Joerg Schilling, believe it or not, I tried for possible targets 'cdrecord -scanbus :%)

Any ideas how to overcome that issue? Sure I could fire up Pburn and write down for each system which pg is the recorder (or reader), or which bus/target/lun is the correct one for the writer, or for the reader... :P

But in my book, it should be possible to make all that via console only... :)

one way to at least get the sr? is so:

Code: Select all

root@porteus:/dev# ls -l|grep sr0
lrwxrwxrwx 1 root root           3 May  2 09:33 cdrom -> sr0
lrwxrwxrwx 1 root root           3 May  2 09:33 cdrom0 -> sr0
lrwxrwxrwx 1 root root           3 May  2 09:33 dvd -> sr0
lrwxrwxrwx 1 root root           3 May  2 09:33 dvd0 -> sr0
brw-rw---- 1 root cdrom    11,   0 May  2 09:33 sr0
root@porteus:/dev# ls -l|grep sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 cdr1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 cdrom1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 cdrw1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 cdwriter1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 dvd1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 dvdr1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 dvdrw1 -> sr1
lrwxrwxrwx 1 root root           3 Apr 24 21:01 dvdwriter1 -> sr1
brw-rw---- 1 root cdrom    11,   1 Apr 24 21:01 sr1
But still, when I need / want bus/target/lun, this is not the solution...
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus 3.0 final feedback

Post#116 by Rava » 03 May 2014, 21:45

Burning an audio cd (created by cdrdao, bin with toc)

Trying to burn it with PBurn gives me this error:

Code: Select all

ERROR: Failed to load plugin /usr/lib64/ao/plugins-4/libesd.so => dlopen() failed
Cdrdao version 1.2.3 - (C) Andreas Mueller <andreas@daneb.de>
/dev/sr1: TEAC ===	Rev: ===
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

Starting write at speed 8...
Is libesd.so important?

And:
Would it have worked at all, burning an audio cd from a toc/bin combo if I not had created and loaded my cdrdao-1.2.3-x86_64_incl_libao-1.1.0.xzm and esound-0.2.41-x86_64-2.xzm modules, I wonder? O___o

(System: Port 3.0 x86-64, XFCe version)
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus 3.0 final feedback

Post#117 by Rava » 05 May 2014, 00:06

sadly, using USM still not works...

Searching for a file works, like for FBReader
But when I try to download the fbreader-0.99.4-x86-64-1dj.txz I get the libs.txt error

Code: Select all

Message
Fatal error
LIBS.TXT
...

And when trying to update the databases it's again this:

Code: Select all

Starting salix database update.
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
Downloading: MANIFEST.bz2  DONE
bunzip2: /var/usm/salix/MANIFEST.bz2 is not a bzip2 file.
..........

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while usm was running:.......................
.
FATAL ERROR!
usm update_database 203
Could not decompress: MANIFEST.bz2
Is there a workaround?
Since the file is just a gz, not a bzip2...

Code: Select all

$ file /var/usm/salix/MANIFEST.bz2
/var/usm/salix/MANIFEST.bz2: gzip compressed data, from Unix, max speed
So, gunzipping and manually bzip2'ing should be possible... :)
Cheers!
Yours Rava

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

Re: Porteus 3.0 final feedback

Post#118 by fanthom » 05 May 2014, 18:51

@Rava
cdrtools comes from stock slackware so maybe one on linuxquestions has an answer?

"Would it have worked at all, burning an audio cd from a toc/bin combo if I not had created and loaded my cdrdao-1.2.3-x86_64_incl_libao-1.1.0.xzm and esound-0.2.41-x86_64-2.xzm modules, I wonder? O___o"
never tried myself but please let me know in case you try to burn audio without these and it fails so i'll pull them to next release.

thanks
Please add [Solved] to your thread title if the solution was found.

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

Re: Porteus 3.0 final feedback

Post#119 by brokenman » 05 May 2014, 20:06

Rava I just tested USM under 64bit v3.0. Downloaded the latest slackware package from sourceforge and updated without problems. Downloading fbreader was also successful.

So forgive me if I have asked before but:
1) 32 or 64bit?
2) v3.0 porteus?

Your profile says v2.1.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus 3.0 final feedback

Post#120 by Rava » 06 May 2014, 03:22

brokenman wrote:So forgive me if I have asked before
Me forgives you, bro! *brofists*
brokenman wrote:1) 32 or 64bit?
ATM 3 times 64bit (2 PCs, one Laptop), and one time 32 bit (Laptop)...
brokenman wrote:2) v3.0 porteus?
Your profile says v2.1.
Nope. It says x86-64 and 3.0...
Yeah, lazy me only just updated it like a minute ago... xD
________________________________________________________________
brokenman wrote:Rava I just tested USM under 64bit v3.0. Downloaded the latest slackware package from sourceforge and updated without problems. Downloading fbreader was also successful.
Ohh... kay...
Then I try it again, too... I forgot to say so, but usm has another issue. When starting from XFCe menu, it asks me for root PW, and I give the correct one, still it asks me 3 times, then exists without any info why.
So I have to start it from a root terminal via

Code: Select all

root@porteus:/# ( usmgui & )
This gives me this error in the terminal:

Code: Select all

widget_comboboxtext_input_by_file(): Couldn't open '/tmp/usm.ZmR1Ua/sbo-categories.tmp' for reading.
And this explains it's inability to start from XFCe menu, cause it cannot access its working temp file ...

And the error with Update / Update All is still the same:

Code: Select all

Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

 Starting salix database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
Downloading: MANIFEST.bz2  DONE
bunzip2: /var/usm/salix/MANIFEST.bz2 is not a bzip2 file.
          

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while usm was running:                       
 
FATAL ERROR!
usm update_database 203
Could not decompress: MANIFEST.bz2
 
============================================================================== 


sh-4.2#
When I try to update by hand and start with alien, the terminal window it opens just has sh-4.2#, and the terminal from which I started usmgui gets me this error:

Code: Select all

touch: cannot touch ‘/tmp/usm.ZmR1Ua/term1.tmp’: No such file or directory
sh: /tmp/usm.ZmR1Ua/term1.tmp: No such file or directory
widget_terminal_input_by_file(): Couldn't open '/tmp/usm.ZmR1Ua/term1.tmp' for reading.
Also, this:

Code: Select all

root@porteus:/tmp# file /tmp/usm.ZmR1Ua
/tmp/usm.ZmR1Ua: ERROR: cannot open `/tmp/usm.ZmR1Ua' (No such file or directory)
Seems to be an usm working temp directory issue, somehow... But how to solve it?

Usm is Version 3.1.0

But still the same error as above, it finds 3 fbreaders:
Image
________________________________________________________________
fanthom wrote:never tried myself but please let me know in case you try to burn audio without these and it fails so i'll pull them to next release.
Since I like doing stuff from the console when possible (scripting stack and other possibilities.... 8) ) I checked out via ps and /proc/"PID"/cmdline how Pburn does it:

Code: Select all

cdrdao write --device /dev/sr1 --speed 10 'ArtistName - AlbumTitle.toc'
So, burning an audio CD via Pburn's menu entry Burn / Audio from TOC file... sure only works with cdrdao and needed libs.
I created a cdrdao-1.2.3-x86_64_incl_libao-1.1.0.xzm, but also esound-0.2.41-x86_64-2.xzm is needed...
Cheers!
Yours Rava

Post Reply