Page 5 of 6

Re: UP - 31/10/2013 [TESTING]

Posted: 04 Nov 2013 23:19
by ScottQuier
zerozero wrote: without configuration, so closer to the results Scott shows but listing all the packages to install
real 0m6.187s
user 0m0.584s
sys 0m0.024s
6.187s in a system probably equivalent to Scott's
Your's is slightly slower than mine now - I've upgraded, I'm running 8 cores at 3793MHz :)

But, that doesn't really change anything you've said.

Re: UP - 31/10/2013 [TESTING]

Posted: 04 Nov 2013 23:20
by timber
@Schoelje

That cleanup that you suggested DID THE TRICK ... ddm -d installed nvidia-driver with no problem after that.
ddm.txt
(39.19 KiB) Downloaded 78 times
Nice Work!!

I wonder if that cleanup should be (needs to be) a part of the ddm process, or if I did something along the way that cluttered things up (e.g. multiple tries via various UPs and DDM's).

Seeing that nVidia logo upon reboot was a relief ... :D.
Thanks for the help! It's appreciated.

Re: UP - 31/10/2013 [TESTING]

Posted: 04 Nov 2013 23:35
by ScottQuier
BTW - Aside from that long-standing "problem" with ddm, I've been having fun and playing and testing things ~2hrs and I've not had a single problem.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 06:37
by Arjen Balfoort
Can we conclude that execcmd.run is actually the culprit?

If it is, this is a technical issue that is very hard to tackle.

[Tech alert]
Currently, I'm piping the stdout while the command is executed (to return the output to the main screen).
stdout gets buffered, and the process has to wait untill it's filled or gets terminated.
Unfortunately, when the command returns a lot of text, this can take a long time.

I see some solutions:
  • Using Pexpect could solve the problem, but I never worked with this library, thus taking a lot of time to solve without actually knowing whether this is the right solution.
  • I could try to disable buffering, but I don't know what will be the consequence.
  • I could stop realtime output, but then you won't know what's happening during the execution of a command: people might think DDM isn't doing anything.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 08:47
by Arjen Balfoort
Santa finished building KDE.
I'm updating the testing repository now...

Wait with updating until I post back here.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 10:20
by Arjen Balfoort
I've slightly adapted the command execution in DDM.

In my ddm.log, you see that it takes 4 minutes to start DDM, checking my hardware, downloading the drivers, and installing the drivers on my system.
ddm.txt
(32.66 KiB) Downloaded 75 times
I think that's not a bad result. However, performance on my system was never bad. So, I'm not the right person to say this has solved the issue. This is where you com in ;)

You can download DDM here: http://downloads.solydxk.nl/dev/ddm_1.0.0_all.deb

For all you guys who love to see those system statistics ;) , this is my 8 year old machine:

Code: Select all

$ inxi -Fxx
System:    Host: solydk64 Kernel: 3.10-3-amd64 x86_64 (64 bit, gcc: 4.7.3) 
           Desktop: KDE 4.11.2 (Qt 4.8.6) dm: kdm Distro: SolydXK 1 testing
Machine:   Mobo: ASUSTeK model: M2N-SLI DELUXE version: 1.XX Bios: Phoenix version: ASUS M2N-SLI DELUXE 1502 date: 03/31/2008
CPU:       Dual core AMD Athlon 64 X2 4600+ (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 svm) bmips: 4018.16 
           Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
Graphics:  Card: NVIDIA G92 [GeForce 9800 GT] bus-ID: 03:00.0 chip-ID: 10de:0614 
           X.Org: 1.14.3 driver: nouveau Resolution: 1920x1080@60.0hz 
           GLX Renderer: Gallium 0.4 on NV92 GLX Version: 1.4 (3.0 Mesa 9.2.2) Direct Rendering: No
Audio:     Card-1: NVIDIA MCP55 High Definition Audio driver: snd_hda_intel bus-ID: 00:06.1 chip-ID: 10de:0371 
           Card-2: Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R) 
           driver: USB Audio usb-ID: 004-003 chip-ID: 0471:0329 
           Sound: Advanced Linux Sound Architecture ver: k3.10-3-amd64
Network:   Card-1: NVIDIA MCP55 Ethernet driver: forcedeth port: b000 bus-ID: 00:08.0 chip-ID: 10de:0373
           IF: eth2 state: down mac: 00:17:31:f1:43:ff
           Card-2: NVIDIA MCP55 Ethernet driver: forcedeth port: ac00 bus-ID: 00:09.0 chip-ID: 10de:0373
           IF: eth1 state: down mac: 00:17:31:f1:51:31
           Card-3: Ralink RT2870/RT3070 Wireless Adapter driver: rt2800usb ver: 2.3.0 usb-ID: 005-002 chip-ID: 148f:3070
           IF: wlan0 state: up mac: 00:a1:b0:f0:05:94
Drives:    HDD Total Size: 3501.2GB (14.1% used)
           1: id: /dev/sda model: SAMSUNG_HD502HJ size: 500.1GB serial: S20BJ9KBA04275 temp: 46C 
           2: id: /dev/sdb model: WDC_WD30EFRX size: 3000.6GB serial: WD-WMC1T2198804 temp: 50C 
           3: USB id: /dev/sdc model: Flash_Disk size: 0.5GB serial: 132569703598-0:0 temp: 0C 
Partition: ID: / size: 50G used: 12G (26%) fs: ext4 ID: /home size: 50G used: 7.5G (17%) fs: ext4 
           ID: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap 
Sensors:   System Temperatures: cpu: 53.0C mobo: 50.0C 
           Fan Speeds (in rpm): cpu: 2076 psu: 968 sys-1: 0 sys-2: 0 sys-3: 0 sys-4: 0 
Info:      Processes: 187 Uptime: 31 min Memory: 927.0/3965.0MB Runlevel: 2 Gcc sys: 4.8.2 alt: 4.4/4.6/4.7 

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 11:32
by Arjen Balfoort
I found that after the update, including the Nvidia drivers, Conky's clock isn't rendered correctly: the seconds hand of the clock skips seconds irregularly.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 12:06
by ScottQuier
Schoelje wrote:I've slightly adapted the command execution in DDM.

In my ddm.log, you see that it takes 4 minutes to start DDM, checking my hardware, downloading the drivers, and installing the drivers on my system.
ddm.txt
I think that's not a bad result. However, performance on my system was never bad. So, I'm not the right person to say this has solved the issue. This is where you com in ;)

You can download DDM here: http://downloads.solydxk.nl/dev/ddm_1.0.0_all.deb
I'll be on this in about 9 hours, after work and the completion of a couple of errands for the DW. Please expect update around 1700 EST.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 12:16
by Arjen Balfoort
Okay, be sure to download when you get back. I probably will adapt more in the mean time.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 13:04
by ScottQuier
Schoelje wrote:Okay, be sure to download when you get back. I probably will adapt more in the mean time.
Right. The steps:
  1. Read this thread for additions/changes/corrections/humor
  2. Restore my testing image which was updated against the testing repos yesterday but does not include nvidia drivers
  3. $ sudo apt-get update && sudo apt-get upgrade #just in case
  4. Download the new(est) ddm.deb
  5. $ sudo dpkg -i ~/Downloads/ddm.deb
  6. ddm -d
  7. $ mv ~/ddm.log ~/ddm.txt
  8. Post results and ddm.txt back to this thread
The above is my attempt at geek-humor (yep, very, very poor :) ) - not to get concurrance that I've got all my ducks lined up. However, please make a note if I've missed something important.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 13:22
by Arjen Balfoort
The synchronization of kdenext is done: you can now start upgrading KDE.
I'm updating my system right now: another 200MB to download.

@ScottQuier
Looking good :)

[EDIT]
Updated my main system with UM: no problem at all.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 14:23
by ane champenois
Just a little message to say: All is smooth for me (SolydX 32) after all UP on this testing.
I'll inform you if something seems to be broken, of course ;)

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 15:29
by zerozero
ScottQuier wrote:
Schoelje wrote:Okay, be sure to download when you get back. I probably will adapt more in the mean time.
Right. The steps:
  1. Read this thread for additions/changes/corrections/humor
  2. Restore my testing image which was updated against the testing repos yesterday but does not include nvidia drivers
  3. $ sudo apt-get update && sudo apt-get upgrade #just in case
  4. Download the new(est) ddm.deb
  5. $ sudo dpkg -i ~/Downloads/ddm.deb
  6. ddm -d
  7. $ mv ~/ddm.log ~/ddm.txt
  8. Post results and ddm.txt back to this thread
The above is my attempt at geek-humor (yep, very, very poor :) ) - not to get concurrance that I've got all my ducks lined up. However, please make a note if I've missed something important.
Scott,
3. should be

Code: Select all

sudo apt-get update && sudo apt-get dist-upgrade
please do never use upgrade with SolydXK RR (it will be a perfect maintenance command for the upcoming LTS ed.).
with RR you need to dist-upgrade in order to install new lib/packages, remove old/obsolete (this part only dist-upgrade does) and fully upgrade the system.

the upgrade command is conservative but the main problem when applied to a RR (or half-rolling) is that it will quickly break the system because it is updating the system but not making the renewal that some of those updated app/lib are expecting.
upgrade
upgrade is used to install the newest versions of all packages currently installed on the system from the sources
enumerated in /etc/apt/sources.list. Packages currently installed with new versions available are retrieved and
upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved
and installed. New versions of currently installed packages that cannot be upgraded without changing the install status
of another package will be left at their current version. An update must be performed first so that apt-get knows that
new versions of packages are available.
dist-upgrade
dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with
new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most
important packages at the expense of less important ones if necessary. The dist-upgrade command may therefore remove
some packages. The /etc/apt/sources.list file contains a list of locations from which to retrieve desired package files.
See also apt_preferences(5) for a mechanism for overriding the general settings for individual packages.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 15:39
by timber
Schoelje wrote:I found that after the update, including the Nvidia drivers, Conky's clock isn't rendered correctly: the seconds hand of the clock skips seconds irregularly.
Prior to this very latest UP, conky background is black rather than transparent.
Seconds hand no problem here prior to latest.
Doing UP now, will let you know how it all goes.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 15:41
by ScottQuier
@zerozero
Thanks for the clarification. I tought that since I'd done the dist-upgrade already that I was set. I now see the error of my ways.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 15:54
by Arjen Balfoort
timber wrote:Prior to this very latest UP, conky background is black rather than transparent.
Had that too, but I thought I broke something while testing!
In SolydK, I just unabled / enabled the desktop effects, and all was fine again (Ctrl-Shift-F12 twice).

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 16:33
by timber
Thanks,
Had to go to Desktop Effects, then re-enable OpenGL detection (due to prior Kwin crash ... nvidia).
Fine now, Thank You.

Latest UP went fine ... no apparent problems.

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 17:13
by zerozero
done the kde update 8-) no issues to report! ;)

Code: Select all

zerozero@home ~ $ kde4-config --version; uname -a; lsb_release -a
Qt: 4.8.6
KDE Development Platform: 4.11.3
kde4-config: 1.0
Linux home 3.10-3-amd64 #1 SMP Debian 3.10.11-1 (2013-09-10) x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: SolydXK
Description:    SolydXK
Release:        1
Codename:       testing

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 17:17
by Arjen Balfoort
UP 2013.11.06 postponed

Today Santa finished working on KDE 4.11.3
We need some extra time to test.

Therefor the release of the next UP is postponed to 8 November.

Also blogged: http://solydxk.nl/up-2013-11-06-postponed/

Re: UP - 31/10/2013 [TESTING]

Posted: 05 Nov 2013 20:06
by timber
All up to date, will let you know if we see anything out of the ordinary.
Thanks for all!