search for: computersysteme

Well, this is interesting (to me, at least). I joined a W10 machine to the domain (4.8/4.9.4 mix, I'm working on it), then renamed it via "WMIC /node:<computer> computersystem where name="<computer>" call rename name="<newname>". Doing so changed the displayName, sAMAccountName, dNSHostName, and assorted servicePrincipalNames, but did not change the

...;merge key="power_management.quirk.vga_mode_3" type="bool">false</merge> </device> </deviceinfo> But nothing seems to work. Running pm-suspend does not do anything, running pm-suspend --quirk-vbe-post puts the Laptop to sleep. Any ideas? Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin at rhm.de

Dear Tomas, thank you for looking into this. Here's the output: # number of logical processors - what detectCores() should return out <- system("wmic cpu get numberoflogicalprocessors", intern=TRUE) [1] "NumberOfLogicalProcessors \r" "22 \r" "22 \r" [4] "20 \r"

Dear Tomas, thank you very much. I installed r-devel r75201 and tested. The machine with 88 cores has NUMA disabled. It therefore has 2 processor groups with 64 and 24 processors each. require(parallel) detectCores() # [1] 88 This is great! Then I went on to test with a simple 'foreach()' loop. I started with 64 processors (max limit of 1 processor group). I ran with a simple function

Dear R-devel list, R's detectCores() function internally calls "ncpus" function to get the total number of logical processors. However, this doesnot seem to take NUMA into account on Windows machines. On a machine having 48 processors (24 cores) in total and windows server 2012 installed, if NUMA is enabled and has 2 nodes (node 0 and node 1 each having 24 CPUs), then R's

Dear Arun, thank you for checking the workaround scripts. I've modified detectCores() to use GetLogicalProcessorInformationEx. It is in revision 75198 of R-devel, could you please test it on your machines? For a binary, you can wait until the R-devel snapshot build gets to at least this svn revision. Thanks for the link to the processor groups documentation. I don't have a machine

A summary for reference: the new detectCores() for Windows in R-devel seems to be working both for logical and physical cores on systems with >64 logical processors? (thanks to Arun for testing!). If the feature is important for anyone particularly using an older version of Windows and/or on a system with >64 logical processors, it would be nice if you could test and report any

Hey Looking at the Fedora ML there is some commotion about a Press Kit [1] they are constructing. I am thinking about doing something like this for CentOS. Now comes my question, what do people think should belong in such a kit. Do you think this is needed? Cheers for your help, Didi [1] https://fedoraproject.org/wiki/F13_press_kit -- Hoffmann Geerd-Dietger http://contact.ribalba.de

Dear Arun, thank you for the report. I agree with the analysis, detectCores() will only report logical processors in the NUMA group in which R is running. I don't have a system to test on, could you please check these workarounds for me on your systems? # number of logical processors - what detectCores() should return out <- system("wmic cpu get numberoflogicalprocessors",

...ssue and switching to Gnome is not an option either. Infact it's Novell's decision to ditch KDE3 and focus on KDE4 instead that made us turn our backs on openSUSE in the first place. So, is it possible to solve this teeny-tiny problem some other way? Thanks in advance, Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin at rhm.de

...else I could do? Either getting wl.ko to work with 2.6.18 (does somebody have a version older than 5.10.79.10 that they could email me?) or getting klaptop to realize that the laptop does indeed know how th suspend and hibernate with a non-CentOS-kernel would be fine. Thanks, Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin at rhm.de