headers
XeCycle | 1 Apr 2012 03:06
Picon

Now looks like display issue (was: Lock at shutdown with some kernels)

Hello,

Last night I thought the bug may have come again, so I decided to
use another way to shutdown.  I think switching to tty1 then
login as root and shutdown will tell me what's wrong maybe, so I
pressed Ctrl-Alt-F1 --- and the system hangs.

So it failed to switch to tty1 and hung, now looks like a display
issue.

I use latest kernel from [core], have a ATI Mobility Radeon 5650
and Intel Core i5 (1st gen) switchable graphics (MUXed) operated
with vgaswitcheroo.  I use xf86-video-{ati,intel} along with
dependencies from [extra], all up-to-date.  Also is xorg.

Can you give me some extra hints on debugging?

--

-- 
Carl Lei (XeCycle)
Department of Physics, Shanghai Jiao Tong University
OpenPGP public key: 7795E591
Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591
Permalink | Reply | 0 comments |
headers
Eric Cook | 1 Apr 2012 05:13
Picon

Re: mkisofs question

On 03/31/2012 05:18 PM, Jude DaShiell wrote:
> Can any options be used with mkisofs to tell it if an single image will 
> have a size larger than 1 dvd can hold, make as many additional images as 
> necessary so that everything will fit on more than a single dvd?
piping tar into mkisofs could be a solution, but using mkisofs by itself
lacks a option to do so.
Permalink | Reply | 0 comments |
headers
David C. Rankin | 1 Apr 2012 06:59

Can you test machine to set --jobs[=N] from w/i PKGBUILD?

Guys,

  Is there any way to check the number of cores on a machine to set the number
of jobs within a PKGBUILD?:

make -j'X'

I have some dual-core and some quad-core boxes and the difference between -j2
and -j4 on build time is tremendous. However, for generically creating a source
package to be used by someone else, I can't hardcode the jobs number. Anyway to
test in pkgbuild or is this just a per box makepkg.conf issue?

--

-- 
David C. Rankin, J.D.,P.E.
Permalink | Reply | 17 comments |
headers
XeCycle | 1 Apr 2012 07:03
Picon

Re: Can you test machine to set --jobs[=N] from w/i PKGBUILD?

should be the latter. some don't want the system too heavily loaded by building a package, so they may prefer
building without parallel enabled.
-- 
抱歉暂时无法详细说明。这份邮件是使用安装有K-9 Mail的Android移动设备发送的。

"David C. Rankin" <drankinatty <at> suddenlinkmail.com>写到：

Guys,

Is there any way to check the number of cores on a machine to set the number
of jobs within a PKGBUILD?:

make -j'X'

I have some dual-core and some quad-core boxes and the difference between -j2
and -j4 on build time is tremendous. However, for generically creating a source
package to be used by someone else, I can't hardcode the jobs number. Anyway to
test in pkgbuild or is this just a per box makepkg.conf issue?

--

-- 
David C. Rankin, J.D.,P.E.
Permalink | Reply | 1 comment |
headers
gt | 1 Apr 2012 07:46
Picon
Favicon

Re: mkisofs question

On Sat, Mar 31, 2012 at 06:18:33PM -0400, Jude DaShiell wrote:
> Can any options be used with mkisofs to tell it if an single image will 
> have a size larger than 1 dvd can hold, make as many additional images as 
> necessary so that everything will fit on more than a single dvd?

From the mkisofs manpage:

-split-output

Split the output image into several files of approximately 1 GB.

This isn't exactly what you are looking for, but close enough.

--

-- 
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Permalink | Reply | 1 comment |
headers
David C. Rankin | 1 Apr 2012 08:14

Re: Can you test machine to set --jobs[=N] from w/i PKGBUILD?

On 04/01/2012 12:03 AM, XeCycle wrote:
> should be the latter. some don't want the system too heavily loaded by building a package, so they may
prefer building without parallel enabled.

Thanks! I guess that's the smart way to do it anyway.

--

-- 
David C. Rankin, J.D.,P.E.
Permalink | Reply | 0 comments |
headers
Jesse Jaara | 1 Apr 2012 09:52
Picon
Gravatar

Re: Can you test machine to set --jobs[=N] from w/i PKGBUILD?

Makepkg.conf
MAKEFLAGS="-jX"

Innstall renice and you wont even
Notice the building, as gcc's priority
is set so low by renice.
Permalink | Reply | 2 comments |
headers
XeCycle | 1 Apr 2012 10:28
Picon

Re: Can you test machine to set --jobs[=N] from w/i PKGBUILD?

Jesse Jaara <jesse.jaara <at> gmail.com>写到：

> Makepkg.conf
> MAKEFLAGS="-jX"
> 
> Innstall renice and you wont even
> Notice the building, as gcc's priority
> is set so low by renice.

That doesn't solve everything, though.  A notebook user like me may find the CPU gets too hot when building
with aggressive parallel options, and renice can't help.
--

-- 
Carl Lei (XeCycle)
Sent with my phone, sorry for inconveniences.
Permalink | Reply | 1 comment |
headers
Auguste Pop | 1 Apr 2012 10:45
Picon

Re: Can you test machine to set --jobs[=N] from w/i PKGBUILD?

On Sun, Apr 1, 2012 at 12:59 AM, David C. Rankin
<drankinatty <at> suddenlinkmail.com> wrote:
> Guys,
>
>  Is there any way to check the number of cores on a machine to set the number
> of jobs within a PKGBUILD?:
>
> make -j'X'
>
> I have some dual-core and some quad-core boxes and the difference between -j2
> and -j4 on build time is tremendous. However, for generically creating a source
> package to be used by someone else, I can't hardcode the jobs number. Anyway to
> test in pkgbuild or is this just a per box makepkg.conf issue?
>
> --
> David C. Rankin, J.D.,P.E.

i am not sure why are you trying to do it in PKGBUILD. if you have
several machines that you want to have different settings, why not set
/etc/makepkg.conf or $HOME/.makepkg.conf separately?

anyway, i think the following command can easily get the information you need:
grep -c processor /proc/cpuinfo
Permalink | Reply | 10 comments |
headers
Vitor Garcia | 1 Apr 2012 13:05
Picon

Re: Can you test machine to set --jobs[=N] from w/i PKGBUILD?

On Sun, 1 Apr 2012 04:45:08 -0400
Auguste Pop <auguste <at> gmail.com> wrote:

> anyway, i think the following command can easily get the information
> you need: grep -c processor /proc/cpuinfo

This command will make a few 2 Cores processor with some kind of
virtual processing technology (like hyper-threading) to be counted as a
4 cores processor.

You may use:
#cat /proc/cpuinfo | grep "physical id" | sort | uniq | wc -l

To get the number of CPU "slots" you have on the machine.

And then:
#cat /proc/cpuinfo | grep "cpu cores" | uniq

To get the number of cores per "slot".

Then you just have to multiply both numbers and you know how many "real
cpus" you have on the system. Otherwise you may be counting virtual
processors, which shouldn't be used for heavy stuff such as compiling.

Regards,
Vitor
Permalink | Reply | 6 comments |

Gmane