Porteus-1.1-rc1-x86_64 is ready for testing

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
Hamza
Warlord
Warlord
Posts: 1908
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#41 by Hamza » 27 Oct 2011, 13:10

fanthom wrote:password function definitely does not work for me. this is frugal HD installation.
Did you rebooted after the first process to check if the password was changed ?
If this doesn't works, We will switch to passwd prompt to avoid any future problems related to this function.
fanthom wrote:for example start PSC and answer "NO" to each question (except first one), after 4 or 5 answers your application blows up.
I don't understand.
If you pressed No, it was supposed to skip to next step without problem. Please take look a on default scenario at bottom with --defconfig|-d|*)

Ciao
NjVFQzY2Rg==

cttan
Shogun
Shogun
Posts: 333
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 and 4.0 64bit KDE
Location: Malaysia

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#42 by cttan » 28 Oct 2011, 00:17

Hi fanthom,

cat /proc/cpuinfo | grep flags
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts

dmidecode output:-

Code: Select all

Processor Information
        Socket Designation: Intel(R) Genuine processor
        Type: Central Processor
        Family: Other
        Manufacturer: Intel(R) Corporation
        ID: FD 06 00 00 FF FB EB BF
        Signature: Type 0, Family 6, Model 15, Stepping 13
        Flags:
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)
                PAE (Physical address extension)
                MCE (Machine check exception)
                CX8 (CMPXCHG8 instruction supported)
                APIC (On-chip APIC hardware supported)
                SEP (Fast system call)
                MTRR (Memory type range registers)
                PGE (Page global enable)
                MCA (Machine check architecture)
                CMOV (Conditional move instruction supported)
                PAT (Page attribute table)
                PSE-36 (36-bit page size extension)
                CLFSH (CLFLUSH instruction supported)
                DS (Debug store)
                ACPI (ACPI supported)
                MMX (MMX technology supported)
                FXSR (FXSAVE and FXSTOR instructions supported)
                SSE (Streaming SIMD extensions)
                SSE2 (Streaming SIMD extensions 2)
                SS (Self-snoop)
                HTT (Multi-threading)
                TM (Thermal monitor supported)
                PBE (Pending break enabled)
        Version: Intel(R) Core(TM)2 Duo CPU     T5670  @ 1.80GHz
        Voltage: 1.6 V
        External Clock: 200 MHz
        Max Speed: 1800 MHz
        Current Speed: 1200 MHz
        Status: Populated, Enabled
        Upgrade: ZIF Socket
        L1 Cache Handle: 0x0003
        L2 Cache Handle: 0x0001
        L3 Cache Handle: Not Provided
        Serial Number: Not Specified
        Asset Tag: Intel(R) Genuine processor
        Part Number: Not Specified
@Hamza
My CPU is 64 bit and I can run 64 bit Porteus. I have tried with selecting OS Type : linux then Version : linux 2.6.

@brokenman
I have tried to use PAE/NX but getting the same error. No Virtualization options in my BIOS

Hi All,
Thanks you very much for the prompt responses.

I have found in Intel website that my laptop HP 6730S CPU (Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz) does not support Intel Virtualization Technology (Intel VT).
http://www.intel.com/products/processor ... ations.htm

In VirtualBox manual, "Chapter 3. Configuring virtual machines", it is stated that Hardware Virtualization is required:-
http://www.virtualbox.org/manual/ch03.html

VirtualBox supports 64-bit guest operating systems, even on 32-bit host operating systems,[11] provided that the following conditions are met:

1. You need a 64-bit processor with hardware virtualization support (see the section called “Hardware vs. software virtualization”).

2. You must enable hardware virtualization for the particular VM for which you want 64-bit support; software virtualization is not supported for 64-bit VMs.

3. If you want to use 64-bit guest support on a 32-bit host operating system, you must also select a 64-bit operating system for the particular VM. Since supporting 64 bits on 32-bit hosts incurs additional overhead, VirtualBox only enables this support upon explicit request.

4. On 64-bit hosts (which typically come with hardware virtualization support), 64-bit guest operating systems are always supported regardless of settings, so you can simply install a 64-bit operating system in the guest.

Posted after 1 hour 13 minutes 24 seconds:
@cttan
1) what info would you expect over there? i have compared Porteus with latest Kubutu and all is pretty much the same.
Hi fanthom,

This is regarding missing info in the overwrite screen while copying files.
Pls see this screen capture on V1.0 Final for the info missing.
http://imageshack.us/photo/my-images/19 ... ot1ev.jpg/

compare to V1.1 RC1 with empty file info
http://imageshack.us/photo/my-images/87/snapshot1g.jpg/

Posted after 9 hours 46 minutes 4 seconds:
2) in 3.1 kernel sco and l2cap are compiled into kernel (it's not possible to choose M for them). the only thing which is missing is 'rfcomm' module.
i have seen an issue with 2.6.38.x kernel when rfcomm was loaded randomly on startup. this was fixed in 2.6.38.5 or later.
Anyway - please do couple of reboots and check if that module gets loaded. if not then add it to /etc/rc.d/rc.modules.local:

Code: Select all
echo "modprobe rfcomm" >> /etc/rc.d/rc.modules.local
chmod +x /etc/rc.d/rc.modules.local


let me know if that helped
@fanthom
I have tried the and it is still not working. I'm getting Bluetooth: hci1 command tx timeout and it seems like a kernel bug according to some forum.
Thank you.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#43 by Ahau » 28 Oct 2011, 14:03

2 issues found:

1 - typo in /etc/rc.d/rc.M, line 23. It echos, "Additional modules has been found..." This should read, "Additional modules have been found"

2 - new cheatcode kmap= has some kind of issue with KDE. For example, using kmap=ru at boot up, KDE starts loading and shows 'ru' in the panel. As soon as KDE finishes loading, it switches back to us. If you use a language that is not one of the defaults already loaded (I think it cycles through 4), this can make it challenging to get your keyboard map loaded. This behaviour is not present in LXDE. Tested in always fresh mode, root and guest accounts.

Cheers!
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5667
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#44 by fanthom » 28 Oct 2011, 18:07

@Hamza
were you able to recreate PSC crash as per my report?

@cttan
1) your CPU is short of 'vmx' flag:
http://www.howtogeek.com/howto/linux/li ... pports-vt/

a per cited Vbox documentation:
VirtualBox supports 64-bit guest operating systems, even on 32-bit host operating systems,[11] provided that the following conditions are met:
1. You need a 64-bit processor with hardware virtualization support (see the section called “Hardware vs. software virtualization”).
your CPU does not meet first condition which means that you wont have 64bit guest support. sorry about that.

2) missing info during override operation is caused by stripping off the nepomuk in porteus-1.1. i'm not going to bring it back so we must live without this feature.

3) hopefully your bluetooth driver will be fixed in 3.1.x kernel and can make into FINAL.

@Ahau
both issues are fixed now.

you may experience up to 10 sec delay until kbd layout is switched in KDE-4. this is caused by (in)famous "kmix daemon crash" bug which is affecting almost all distros:
https://bugs.kde.org/show_bug.cgi?id=209975
this bug is still opened and causing restart of "System Tray" - that's why we need up to 10 seconds delay before switching keyboard layouts.
this bug does not affect lxde and kde-3.

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

User avatar
Hamza
Warlord
Warlord
Posts: 1908
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#45 by Hamza » 01 Nov 2011, 14:59

@fanthom,
No,
Run PSC with fressyou argument, and send me the reports saved in /opt/psc/activity...
NjVFQzY2Rg==

User avatar
francois
Contributor
Contributor
Posts: 6435
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#46 by francois » 02 Nov 2011, 03:43

I just installed rc1, and will come with some feedback. How come the thread is so calm now?
Prendre son temps, profiter de celui qui passe.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#47 by Ahau » 02 Nov 2011, 12:00

francois, we were just waiting for our favorite French Canadian tester to show up. Now we're good to go!

Or, maybe it's because fanthom put together a kick-ass release with very few issues :D
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
Hamza
Warlord
Warlord
Posts: 1908
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#48 by Hamza » 02 Nov 2011, 12:04

PSC is ready for rc2.
Sent source to fanthom.
NjVFQzY2Rg==

User avatar
francois
Contributor
Contributor
Posts: 6435
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#49 by francois » 08 Nov 2011, 03:53

@Ahau: The first reason you mention sure pleases me. But alas, no doubt that the second reason is the real one. Good for us.

Yet I did not found much, though I did not work with it much. All I found on my hp pavilion 2713ca is that the kde gui when trigerred is cut on the left, preventing return to the previous menu.

Posted after 5 days 10 hours 45 minutes 24 seconds:
Rc1 looks very good and works quite fine. The bcmXX wifi driver works out of the box. If you add this feature the nvidia module of beny, all the needs of my pavilion 2713ca laptop are fulfilled.

However, I found that the lang=ca cheatcode in the menu.lst does not work. This is not the case for porteus rc1 32bit.
Prendre son temps, profiter de celui qui passe.

Kriss
Samurai
Samurai
Posts: 135
Joined: 06 Jul 2011, 07:07
Location: Russia

smplayer/mplayer bug (Porteus 1.1rc)?

Post#50 by Kriss » 12 Nov 2011, 16:22

Hello all!
Actually I'm not sure if this is bug, but it's as follows:
I have a quite old noteboook, Acer Aspire 5100, CPU Turion 64x2 2.3Ghz, 2 cores, 4Gb but it's barely enough for FullHD video (sometimes frames are skipped with CPU usage of ~40-50%, so I need -frameskip option).
Most likely because of videocard ATi x1100 mobile that uses 256Mb of RAM for its needs (I think I'll upgrade it to x1600 soon, but it takes time to change motherboard).
So in WinXP in SMPlayer I use -sndvol-max 2000 if I want to use headphones for everyone to hear (broken integrated soundcard and no way to use notebook's dynamics). Everything's relatively fine here (SMPlayer 3.6.9 SVN-r3611 + Mplayer Sherpya-SVN-r33883-4.2.5)

In Porteus x86_64 v1.1rc1 this setup leads to framerate of... 1 frame per 5 second, sometimes I only see static image (and CPU usage shows its not used at all).
If I uncheck framedrop option, everythin'g back to normal (except video lags behind sound because of lack of computing power).
I've tried to use mplayer alone "mplayer -framedrop -softvol-max 1100 ./video.mkv" with the same result.
GNOME player worked Ok but I wasn't able to make it louder with +60dB option. It just didn't worked.

P.S. Can somebody tell me how mplayer was compiled in 1.1rc1 so I'll try to compile newer mplayer in the same way. Slackware packages had dditional dependencies.

Added: Just checked and got the same results on quad-core computer with Radeon HD 4650... :shock:
Video used: "[Rising Sun] Spice and Wolf II - 01 [1920x1080-H264-FLAC][EA85CA2C].mkv"
Suggestions/corrections/additions are always welcome.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5667
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#51 by fanthom » 12 Nov 2011, 22:58

@Kriss
Merged here as bugs related to developmment versions should be posted in rc threads only.
Just checked and got the same results on quad-core computer with Radeon HD 4650
must be smplayer settings issue so (especially if it works in gnome-mplayer). pleas run porteus in "Always Fresh" mode and make sure that video driver in smplayer is set to 'xv' and not 'x11' or 'gl'.
i have tried on 720p movie trailer (dont have 1080p around atm) and works ok for 'xv' (eating 60% of the CPU).

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

Kriss
Samurai
Samurai
Posts: 135
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#52 by Kriss » 13 Nov 2011, 16:04

I'm sorry for confusion I've created over my own stupidity.
Originally I've tried to compare video playback in winXP (I've mentioned versions of mplayer and smplayer before) and this RC of Porteus after you've said that open-source drivers for legacy ATi cards are quite good, but then I got carried away and probably fooled myself with inaccurate tests.
The only thing I'm sure of now is that under windows SMPlayer+ Mplayer (I already mentioned versions I use, optimized for P4 with disabled 3DNow and 3DNowext because originally I had only Intel CPUs) plays video much better than default ones in this rc1 (CPU: AMD Turion with 3DNow and 3DNowext).
I excluded "driver isn't as good as from legacy branch" version because without "-framedrop" option video plays Ok with slowly growing audio/video desynchronisation (same for all players since they use Mplayer).
GNOME Mplayer just didn't honor its +60dB and -framedrop options (results were described above)

So in the end I have video and notebook that's at least VERY close to being able to play this video without problems.
In WinXP it's very hard to notice that some frames were dropped (if they are dropped at all) but it looks horrible in Porteus x86_64 1.1rc1
As I understand this can be because of:
drivers (less likely)
mplayer version differences 32819 vs 33883 (optimizations and fixed bugs)
mplayer build differences (optimizations)
Also I suspect that this version have very bad multithreading capabilities (Only one core of notebook is busy while other one does nothing judging by utility I've mentioned in another thread, besides mplayer don't use more than 49-50%). Although option -lavdopts threads=4 is passed to it

So in the end I just want to ask how did you compile mplayer (what flags, patches and so on) to tinker with it by myself.

P.S. I've tried almost all possible video outputs in smplayer before realized that it makes no difference.
Yes, I've got something similar on quad-core CPU, but I'm not so sure of that right now... I already wrote too much gibberish to explain it =)

P.P.S. It was written somewhere related to mplayer-win builds to always prefer optimized builds over runtime CPU detection (not sure if it's mplayer in general or about windows builds).
Suggestions/corrections/additions are always welcome.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5667
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#53 by fanthom » 13 Nov 2011, 21:20

i have used latest version of Mplayer which supports vaapi from Splitted Desktop site:
http://www.splitted-desktop.com/static/ ... yer-vaapi/
vaapi works great for all i3/i5/i7 systems. this mplayer supports also vdpau. xvba is broken with latest amd drivers so i have removed it.
unfortunatelly this version does not support multithreading due to colliding patches.

here is the config for 64bits:
[codeCFLAGS="-Os -march=x86-64" CXXFLAGS="-Os -march=x86-64" MAKEOPTS="-j2" ./configure --prefix=/usr --mandir=/usr/man --libdir=/usr/lib64 --enable-runtime-cpudetection --yasm=''][/code]
and 32bits:

Code: Select all

CFLAGS="-Os -march=i486 -mtune=i686" CXXFLAGS="-Os -march=i486 -mtune=i686" MAKEOPTS=-j2 ./configure --prefix=/usr --mandir=/usr/man --libdir=/usr/lib --enable-runtime-cpudetection --yasm=''
my proposition:
please compile latest mplayer for both archs with multithread support (and other features if you like) and share it in "Community Efforts" or "xzm modules" section.
i'll test them, compare features and decide if they could be used in official release.

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

Kriss
Samurai
Samurai
Posts: 135
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#54 by Kriss » 15 Nov 2011, 11:35

Thank you!
I'm sorry for creating such a fuss instead of just trying to compile latest svn version. I was afraid that I'll end-up installing tons of different codecs and tools first, but lucky for me it's not true in case of mplayer =)
Just tried to compile it and it needed only yasm (improves performance on h264 videos) and git (configure tries to download latest ffmpeg using git).
Default mplayer configuration was enough to play that problematic FullHD video using only a little bit more than 50% of CPU time.

P.S. I'll post modules when I'll create something I won't be ashamed of.

P.P.S. There was a typo in informational message about proprietary ATi driver. It was written properietary IIRC.

Added: Looks like in the past I've run into something similar to bugs, mentioned here (video stops with CPU doing nothing, but sound continued to play) with default Porteus64 1.1rc1 mplayer.
Last edited by Kriss on 17 Nov 2011, 20:02, edited 2 times in total.
Suggestions/corrections/additions are always welcome.

User avatar
libernux
White ninja
White ninja
Posts: 28
Joined: 01 Nov 2011, 17:36
Distribution: porteus v3.1 32bit XFCE
Location: Netherlands

Re: Porteus-1.1-rc1-x86_64 is ready for testing

Post#55 by libernux » 17 Nov 2011, 08:14

Hi all,

The library libpng is missing in the initial install. I discovered this when i was compiling E17. According to pkg-config libpng is a required library for gdk-pixbuf but because it was missing it did not return any CFLAGS. Can you please fix this. For now I solved it by installing libpng.
I was born with nothing and I still got most of it.

Locked