[gentoo-user] Re: Overclocking CPU causes segmentation fault
On 23/01/13 03:55, Dale wrote: [...] I tired overclocking once a good while back. It just wasn't worth it. I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three years. Instead of a new CPU, I only bought a €30 cooler. Oh, it *was* totally worth it. Mainly for games, where the performance difference was really dramatic.
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
»Q« wrote: Peter Humphrey pe...@humphrey.ukfsn.org wrote: My daily update pulled in udev-197-r3. The installation went smoothly but I decided I ought to reboot to check that I could. I couldn't. Udev couldn't start because my kernel config didn't have CONFIG_DEVTMPFS=y. So I booted my rescue system on the same disk, chrooted in and built a new kernel with that option. On rebooting everything was fine. This got me too. Now there's a discussion in -dev about making config warnings fatal. Good idea, but as I updated udev yesterday on one of my Gentoo systems, in the usual after-update messages there was a line in red, telling me You don't have CONFIG_DEVTMPFS enabled. udev will not start. So it's not really a surprise, is it? Hence, I built a new kernel *before* rebooting :-) -Matt
[gentoo-user] Re: Kernel Questions
The 23/01/13, Silvio Siefke wrote: I use the good old Pentium 4 on the desktop and an atom on the laptop. But I have often the problem when the computer has much to do, that the system freeze. That's on the atom often so. The opera is my favorite Browser, but often the call on a website and the result end in freeze. What is really strange, when i run emerge --sync ; emerge -avuDN @world, the Pentium 4 is faster as the Atom. Is that normal? Did you check if the system is swapping when that happen? -- Nicolas Sebrecht
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wed, 23 Jan 2013 09:29:19 +0100, Matthias Hanft wrote: This got me too. Now there's a discussion in -dev about making config warnings fatal. Good idea, but as I updated udev yesterday on one of my Gentoo systems, in the usual after-update messages there was a line in red, telling me You don't have CONFIG_DEVTMPFS enabled. udev will not start. So it's not really a surprise, is it? Hence, I built a new kernel *before* rebooting :-) That's fine if you see the message, which you should, and the system does not suffer an unplanned reboot, which it shouldn't. But leaving a system in a state that won't reboot following a crash or power failure is not particularly clever, making the warnings fatal sounds a safe default to me. As this is Gentoo there will always be a way to turn the airbags off and even disable the brakes :) -- Neil Bothwick Some cause happiness wherever they go. Others whenever they go. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
In linux.gentoo.user, you wrote: On Wed, 23 Jan 2013 09:29:19 +0100, Matthias Hanft wrote: Good idea, but as I updated udev yesterday on one of my Gentoo systems, in the usual after-update messages there was a line in red, telling me You don't have CONFIG_DEVTMPFS enabled. udev will not start. So it's not really a surprise, is it? Hence, I built a new kernel *before* rebooting :-) That's fine if you see the message, which you should, and the system does not suffer an unplanned reboot, which it shouldn't. But leaving a system in a state that won't reboot following a crash or power failure is not particularly clever, making the warnings fatal sounds a safe default to me. As this is Gentoo there will always be a way to turn the airbags off and even disable the brakes :) A similar message has been shown after quite a few previous udev updates, not just this last one. I remember having to add the CONFIG_DEVTMPFS=y option to my gentoo kernels at least 6 months ago after seeing a message telling me that this option must be enabled for udev or there'll be big problems later on. I have all update messages emailed to me using: PORTAGE_ELOG_*=blah In my /etc/portage/make.conf After every update I read every message that portage sends me and I act appropriately upon them. BTW, My udev update went without a hitch. I had a revdep-rebuild to do for a libudev update and that was about it. Even if you didn't see the message and your system didn't boot then you could still fix things by using your Minimal Install CD to start up, then chroot into your normal system and rebuild your kernel. -- Regards, Gregory.
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
on 01/23/2013 04:41 AM »Q« wrote the following: On Sun, 20 Jan 2013 16:57:59 + Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Sunday 20 January 2013 08:51:43 Philip Webb wrote: I just tried upgrading to udev-197 , which is supposed to be stable. There were multiple problems I'm now back with udev-171 . My daily update pulled in udev-197-r3. The installation went smoothly but I decided I ought to reboot to check that I could. I couldn't. Udev couldn't start because my kernel config didn't have CONFIG_DEVTMPFS=y. So I booted my rescue system on the same disk, chrooted in and built a new kernel with that option. On rebooting everything was fine. Just a note for anyone else who may not have that kernel option. This got me too. Now there's a discussion in -dev about making config warnings fatal. It hit me too, as I hadn't noticed any warning messages..., maybe the messages were added afterwards..., or I was not careful enough...
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
on 01/23/2013 01:10 PM Thanasis wrote the following: on 01/23/2013 04:41 AM »Q« wrote the following: On Sun, 20 Jan 2013 16:57:59 + Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Sunday 20 January 2013 08:51:43 Philip Webb wrote: I just tried upgrading to udev-197 , which is supposed to be stable. There were multiple problems I'm now back with udev-171 . My daily update pulled in udev-197-r3. The installation went smoothly but I decided I ought to reboot to check that I could. I couldn't. Udev couldn't start because my kernel config didn't have CONFIG_DEVTMPFS=y. So I booted my rescue system on the same disk, chrooted in and built a new kernel with that option. On rebooting everything was fine. Just a note for anyone else who may not have that kernel option. This got me too. Now there's a discussion in -dev about making config warnings fatal. It hit me too, as I hadn't noticed any warning messages..., maybe the messages were added afterwards..., or I was not careful enough... Looking at the log, I can see now, that there *was* a warning..., but I only noticed the suggestion about revdep-rebuild... near the end. :\ INFO: setup Package:sys-fs/udev-197-r3 Repository: gentoo Maintainer: udev-b...@gentoo.org USE:acl amd64 elibc_glibc gudev hwdb kernel_linux keymap kmod openrc userland_GNU FEATURES: sandbox Package:sys-fs/udev-197-r3 Repository: gentoo Maintainer: udev-b...@gentoo.org USE:acl amd64 elibc_glibc gudev hwdb kernel_linux keymap kmod openrc userland_GNU FEATURES: sandbox Determining the location of the kernel source code Found kernel source directory: /usr/src/linux Found kernel object directory: /usr/src/linux Found sources for kernel version: 3.6.11-gentoo Checking for suitable kernel configuration options... ERROR: setup DEVTMPFS is not set in this kernel. Udev will not run. WARN: setup Please check to make sure these options are set correctly. Failure to do so may cause unexpected problems. INFO: setup Determining the location of the kernel source code Found kernel source directory: /usr/src/linux-3.6.11-gentoo Found kernel object directory: /usr/src/linux Found sources for kernel version: 3.6.11-gentoo INFO: prepare Applying various patches (bugfixes/updates) ... 0001-udev-net_id-skip-stacked-network-devices.patch ... 0006-udev-don-t-call-fclose-on-NULL-in-is_pci_multifuncti.patch ... Done with patching Running elibtoolize in: systemd-197/build-aux/ Applying portage/1.2.0 patch ... Applying sed/1.5.6 patch ... Applying as-needed/2.4.2 patch ... INFO: install Removing unnecessary /usr/lib64/libgudev-1.0.la (requested) Removing unnecessary /usr/lib64/libudev.la (requested) Removing unnecessary /usr/lib64/libsystemd-daemon.la (requested) WARN: postinst Upstream has removed the persistent-cd rules generator. If you need persistent names for these devices, place udev rules for them in /etc/udev/rules.d. udev-197 and newer introduces a new method of naming network interfaces. The new names are a very significant change, so they are disabled by default on live systems. Please see the contents of /etc/udev/rules.d/80-net-name-slot.rules for more information on this feature. You need to restart udev as soon as possible to make the upgrade go into effect. The method you use to do this depends on your init system. Old versions of installed libraries were detected on your system. In order to avoid breaking packages that depend on these old libs, the libraries are not being removed. You need to run revdep-rebuild in order to remove these old dependencies. If you do not have this helper program, simply emerge the 'gentoolkit' package. # revdep-rebuild --library '/lib64/libudev.so.0' rm '/lib64/libudev.so.0' LOG: postinst For more information on udev on Gentoo, writing udev rules, and fixing known issues visit: http://www.gentoo.org/doc/en/udev-guide.xml
Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Nikos Chantziaras wrote: On 23/01/13 03:55, Dale wrote: [...] I tired overclocking once a good while back. It just wasn't worth it. I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three years. Instead of a new CPU, I only bought a €30 cooler. Oh, it *was* totally worth it. Mainly for games, where the performance difference was really dramatic. I doubt most get that lucky tho. After all, overclocking is mostly luck. Some CPU's won't overclock that much long term because of either the CPU itself or some other component that can't handle the increase. When you overclock, you are searching for that weak link. Most of the time, you find that weak link. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Re: Kernel Questions
Hello, On Wed, 23 Jan 2013 09:30:02 +0100 Nicolas Sebrecht nsebre...@piing.fr wrote: Did you check if the system is swapping when that happen? Im sorry, you mean Swap? How can check them best? Thank you Greetings Silvio
Re: [gentoo-user] Re: Kernel Questions
On 24/01/13 21:21, Silvio Siefke wrote: Hello, On Wed, 23 Jan 2013 09:30:02 +0100 Nicolas Sebrecht nsebre...@piing.fr wrote: Did you check if the system is swapping when that happen? Im sorry, you mean Swap? How can check them best? Thank you Greetings Silvio Hi Silvio, can you check the date on your systems ... your emails are future dated which kinda stuffs things up ... BillK
[gentoo-user] Re: Overclocking CPU causes segmentation fault
On 23/01/13 14:09, Dale wrote: Nikos Chantziaras wrote: On 23/01/13 03:55, Dale wrote: [...] I tired overclocking once a good while back. It just wasn't worth it. I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three years. Instead of a new CPU, I only bought a €30 cooler. Oh, it *was* totally worth it. Mainly for games, where the performance difference was really dramatic. I doubt most get that lucky tho. After all, overclocking is mostly luck. Some CPU's won't overclock that much long term because of either the CPU itself or some other component that can't handle the increase. When you overclock, you are searching for that weak link. Most of the time, you find that weak link. In my experience, most of the time you can overclock. The issue is with the user not knowing exactly how to do it. You need to understand a few things and how they affect each other. It's not just a knob you can turn.
Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
On Wednesday 23 January 2013 07:52:03 PM IST, Nikos Chantziaras wrote: On 23/01/13 14:09, Dale wrote: Nikos Chantziaras wrote: On 23/01/13 03:55, Dale wrote: [...] I tired overclocking once a good while back. It just wasn't worth it. I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three years. Instead of a new CPU, I only bought a €30 cooler. Oh, it *was* totally worth it. Mainly for games, where the performance difference was really dramatic. I doubt most get that lucky tho. After all, overclocking is mostly luck. Some CPU's won't overclock that much long term because of either the CPU itself or some other component that can't handle the increase. When you overclock, you are searching for that weak link. Most of the time, you find that weak link. In my experience, most of the time you can overclock. The issue is with the user not knowing exactly how to do it. You need to understand a few things and how they affect each other. It's not just a knob you can turn. That pretty much applies to me. I don't know much about hardware stuff. Regarding your 1 Ghz overclock, you probably have good components in terms of RAM SMPS. When I bought this rig in 2008, I knew nothing about good components, blindly trusted local vendor... also internet shopping wasn't advanced here. So pretty much substandard components. Now that I know stuff, I'm thinking of assembling my own AMD FX8350 rig soon by buying components from the web. So, let's close this topic :-) -- Nilesh Govindarajan http://nileshgr.com
Re: [gentoo-user] Re: Kernel Questions
Hello, On Wed, 23 Jan 2013 21:53:58 +0800 William Kenworthy bi...@iinet.net.au wrote: Hi Silvio, can you check the date on your systems ... your emails are future dated which kinda stuffs things up ... Yes thank you i have change it. Thank you Greetings Silvio
[gentoo-user] Re: Overclocking CPU causes segmentation fault
On 23/01/13 17:09, Nilesh Govindrajan wrote: On Wednesday 23 January 2013 07:52:03 PM IST, Nikos Chantziaras wrote: [...] In my experience, most of the time you can overclock. The issue is with the user not knowing exactly how to do it. You need to understand a few things and how they affect each other. It's not just a knob you can turn. That pretty much applies to me. I don't know much about hardware stuff. Regarding your 1 Ghz overclock, you probably have good components in terms of RAM SMPS. When I bought this rig in 2008, I knew nothing about good components, blindly trusted local vendor... also internet shopping wasn't advanced here. So pretty much substandard components. The part that's really important is the mainboard. RAM doesn't matter. In my case, I had pretty basic 800MHz DDR2 RAM. Raising the FSB would bring it above that, so I changed the DRAM ratio to 1:1, and the RAM then ran at only 600Mhz. That was the starting point to rule out RAM problems. After that, I raised FSB but kept the VCore constant until I hit the first instabilities. When that happened, I raised VCore a bit. Rinse and repeat, until the VCore was still below the maximum recommendation by Intel. That happened at 3.4GHz (378MHz FSB * 9 CPU multiplier = 3402MHz CPU clock.) The E6600 CPU I got was an average sample. Others were running it at 3.6GHz (or even higher with water cooling.) This was a process that took about 3 days to complete (needs a lot of stability testing.) The good thing about those older CPUs was that the performance boost I got by OCing wasn't just scaling linearly with the CPU frequency. It was scaling *better* than that, because raising the FSB also made the mainboard itself perform better and with lower latencies. Now that I know stuff, I'm thinking of assembling my own AMD FX8350 rig soon by buying components from the web. So, let's close this topic :-) As I said above, the mainboard is really the only important factor.
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wed, 23 Jan 2013 13:10:44 +0200 Thanasis thana...@asyr.hopto.org wrote: on 01/23/2013 04:41 AM »Q« wrote the following: On Sun, 20 Jan 2013 16:57:59 + Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Sunday 20 January 2013 08:51:43 Philip Webb wrote: I just tried upgrading to udev-197 , which is supposed to be stable. There were multiple problems I'm now back with udev-171 . My daily update pulled in udev-197-r3. The installation went smoothly but I decided I ought to reboot to check that I could. I couldn't. Udev couldn't start because my kernel config didn't have CONFIG_DEVTMPFS=y. So I booted my rescue system on the same disk, chrooted in and built a new kernel with that option. On rebooting everything was fine. Just a note for anyone else who may not have that kernel option. This got me too. Now there's a discussion in -dev about making config warnings fatal. It hit me too, as I hadn't noticed any warning messages..., maybe the messages were added afterwards..., or I was not careful enough... A news item about this is coming down the wire very soon now (aka within hours judging by the thread on -dev). Unfortunately, it's too late for you now but at least many other users will see the message before they emerge world and save them some pain -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] libv8 segfault
I tried compiling all versions of chromium (-O3, but it always worked
previously) v8 (tried -O3 -O2 too)
but it always segfaults when I try to open the settings page.
CrRendererMain[6059]: segfault at 5 ip 7f0d0834970c sp
7fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
Quite interestingly, the binary version of chrome works without hitches,
which I don't want to run because I'm a little paranoid about it ;-)
And that also means that there is no hardware fault.
dev-lang/v8-3.15.11.5
www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
beta, but chromium 25 doesn't work either).
Flags:
CFLAGS=-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe
CXXFLAGS=${CFLAGS}
LDFLAGS=-Wl,-O1 -Wl,--as-needed
Just replace that O3 with O2 for v8.
Anybody knows what's going on here?
--
Nilesh Govindarajan
http://nileshgr.com
[gentoo-user] Re: libv8 segfault
On Wednesday 23 January 2013 09:22:21 PM IST, Nilesh Govindrajan wrote:
I tried compiling all versions of chromium (-O3, but it always worked
previously) v8 (tried -O3 -O2 too)
but it always segfaults when I try to open the settings page.
CrRendererMain[6059]: segfault at 5 ip 7f0d0834970c sp
7fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
Quite interestingly, the binary version of chrome works without hitches,
which I don't want to run because I'm a little paranoid about it ;-)
And that also means that there is no hardware fault.
dev-lang/v8-3.15.11.5
www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
beta, but chromium 25 doesn't work either).
Flags:
CFLAGS=-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe
CXXFLAGS=${CFLAGS}
LDFLAGS=-Wl,-O1 -Wl,--as-needed
Just replace that O3 with O2 for v8.
Anybody knows what's going on here?
Looks like I proved myself wrong. The binary version crashed on
extensions page with a segfault -_-
--
Nilesh Govindarajan
http://nileshgr.com
Re: [gentoo-user] libv8 segfault
On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan m...@nileshgr.com wrote:
I tried compiling all versions of chromium (-O3, but it always worked
previously) v8 (tried -O3 -O2 too)
but it always segfaults when I try to open the settings page.
CrRendererMain[6059]: segfault at 5 ip 7f0d0834970c sp
7fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
Quite interestingly, the binary version of chrome works without hitches,
which I don't want to run because I'm a little paranoid about it ;-)
And that also means that there is no hardware fault.
dev-lang/v8-3.15.11.5
www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
beta, but chromium 25 doesn't work either).
Flags:
CFLAGS=-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe
CXXFLAGS=${CFLAGS}
LDFLAGS=-Wl,-O1 -Wl,--as-needed
Just replace that O3 with O2 for v8.
Anybody knows what's going on here?
What USE flags are enabled for chromium? You haven't specified that
you're using the custom-cflags USE flag, so whatever's in your global
CFLAGS setting is largely irrelevant.
Also, you don't need to specify --as-needed; that's default, now. I
don't know what those other flags are doing.
Start with revdep-rebuild, see if that fixes it. If not, you probably
ought to re-emerge chromium and its direct dependencies. Given your
recent experience with overclocking and the rather correct warnings
about silent data corruption, you may need to re-emerge a lot more
than that.
--
:wq
Re: [gentoo-user] libv8 segfault
On Wednesday 23 January 2013 09:29:22 PM IST, Michael Mol wrote:
On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan m...@nileshgr.com
wrote:
I tried compiling all versions of chromium (-O3, but it always worked
previously) v8 (tried -O3 -O2 too)
but it always segfaults when I try to open the settings page.
CrRendererMain[6059]: segfault at 5 ip 7f0d0834970c sp
7fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
Quite interestingly, the binary version of chrome works without hitches,
which I don't want to run because I'm a little paranoid about it ;-)
And that also means that there is no hardware fault.
dev-lang/v8-3.15.11.5
www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
beta, but chromium 25 doesn't work either).
Flags:
CFLAGS=-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe
CXXFLAGS=${CFLAGS}
LDFLAGS=-Wl,-O1 -Wl,--as-needed
Just replace that O3 with O2 for v8.
Anybody knows what's going on here?
What USE flags are enabled for chromium? You haven't specified that
you're using the custom-cflags USE flag, so whatever's in your global
CFLAGS setting is largely irrelevant.
Also, you don't need to specify --as-needed; that's default, now. I
don't know what those other flags are doing.
Start with revdep-rebuild, see if that fixes it. If not, you probably
ought to re-emerge chromium and its direct dependencies. Given your
recent experience with overclocking and the rather correct warnings
about silent data corruption, you may need to re-emerge a lot more
than that.
--
:wq
I didn't merge anything while I was playing with overclocking.
custom-cflags is enabled.
I found the LDFLAGS on Gentoo Wiki as safe LDFLAGS for optimal
performance.
--
Nilesh Govindarajan
http://nileshgr.com
Re: [gentoo-user] libv8 segfault
On Wed, Jan 23, 2013 at 11:07 AM, Nilesh Govindrajan m...@nileshgr.com wrote:
On Wednesday 23 January 2013 09:29:22 PM IST, Michael Mol wrote:
On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan m...@nileshgr.com
wrote:
I tried compiling all versions of chromium (-O3, but it always worked
previously) v8 (tried -O3 -O2 too)
but it always segfaults when I try to open the settings page.
CrRendererMain[6059]: segfault at 5 ip 7f0d0834970c sp
7fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
Quite interestingly, the binary version of chrome works without hitches,
which I don't want to run because I'm a little paranoid about it ;-)
And that also means that there is no hardware fault.
dev-lang/v8-3.15.11.5
www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
beta, but chromium 25 doesn't work either).
Flags:
CFLAGS=-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe
CXXFLAGS=${CFLAGS}
LDFLAGS=-Wl,-O1 -Wl,--as-needed
Just replace that O3 with O2 for v8.
Anybody knows what's going on here?
What USE flags are enabled for chromium? You haven't specified that
you're using the custom-cflags USE flag, so whatever's in your global
CFLAGS setting is largely irrelevant.
Also, you don't need to specify --as-needed; that's default, now. I
don't know what those other flags are doing.
Start with revdep-rebuild, see if that fixes it. If not, you probably
ought to re-emerge chromium and its direct dependencies. Given your
recent experience with overclocking and the rather correct warnings
about silent data corruption, you may need to re-emerge a lot more
than that.
--
:wq
I didn't merge anything while I was playing with overclocking.
custom-cflags is enabled.
I found the LDFLAGS on Gentoo Wiki as safe LDFLAGS for optimal
performance.
Well, then that wiki page is out of date. :)
--
:wq
Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
On Wed, Jan 23, 2013 at 05:35:09PM +0200, Nikos Chantziaras wrote: The part that's really important is the mainboard. RAM doesn't matter. As I said above, the mainboard is really the only important factor. Though I've not overclocked in better than a decade, I disagree with your statement that RAM doesn't matter. Especially now, since there is a plethora of junk RAM on the market. Just my 2 cents. -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
[gentoo-user] Re: Overclocking CPU causes segmentation fault
On 23/01/13 18:22, Bruce Hill wrote: On Wed, Jan 23, 2013 at 05:35:09PM +0200, Nikos Chantziaras wrote: The part that's really important is the mainboard. RAM doesn't matter. As I said above, the mainboard is really the only important factor. Though I've not overclocked in better than a decade, I disagree with your statement that RAM doesn't matter. Especially now, since there is a plethora of junk RAM on the market. Just my 2 cents. It doesn't matter because you don't overclock the RAM (in fact I ended up underclocking it slightly.) Which you can do if the mainboard allows you to set DRAM speeds.
Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Am 23.01.2013 09:21, schrieb Nikos Chantziaras: On 23/01/13 03:55, Dale wrote: [...] I tired overclocking once a good while back. It just wasn't worth it. I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three years. Instead of a new CPU, I only bought a €30 cooler. Oh, it *was* totally worth it. Mainly for games, where the performance difference was really dramatic. yeah and all those files with bit flips (not a problem with films or pics or mp3s) you don't know about were totally worth it...
Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Am 23.01.2013 16:35, schrieb Nikos Chantziaras: On 23/01/13 17:09, Nilesh Govindrajan wrote: On Wednesday 23 January 2013 07:52:03 PM IST, Nikos Chantziaras wrote: [...] In my experience, most of the time you can overclock. The issue is with the user not knowing exactly how to do it. You need to understand a few things and how they affect each other. It's not just a knob you can turn. That pretty much applies to me. I don't know much about hardware stuff. Regarding your 1 Ghz overclock, you probably have good components in terms of RAM SMPS. When I bought this rig in 2008, I knew nothing about good components, blindly trusted local vendor... also internet shopping wasn't advanced here. So pretty much substandard components. The part that's really important is the mainboard. RAM doesn't matter. In my case, I had pretty basic 800MHz DDR2 RAM. Raising the FSB would bring it above that, so I changed the DRAM ratio to 1:1, and the RAM then ran at only 600Mhz. That was the starting point to rule out RAM problems. After that, I raised FSB but kept the VCore constant until I hit the first instabilities. When that happened, I raised VCore a bit. Rinse and repeat, until the VCore was still below the maximum recommendation by Intel. That happened at 3.4GHz (378MHz FSB * 9 CPU multiplier = 3402MHz CPU clock.) The E6600 CPU I got was an average sample. Others were running it at 3.6GHz (or even higher with water cooling.) This was a process that took about 3 days to complete (needs a lot of stability testing.) The good thing about those older CPUs was that the performance boost I got by OCing wasn't just scaling linearly with the CPU frequency. It was scaling *better* than that, because raising the FSB also made the mainboard itself perform better and with lower latencies. and here we are - the point where the suspension of disbelief ends. All you may have gained you threw away with the slower ram - and you are trying to tell us that your rig was faster? You do know that with today's CPUs the CPU is not the bottleneck - the slow as molasses, no speed bump for 10 years ram is. (just look at the internal clock rate of dram chips - and you realize that ddr1-3 are pretty much the same crap).
Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
On Wed, Jan 23, 2013 at 12:16 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am 23.01.2013 16:35, schrieb Nikos Chantziaras: On 23/01/13 17:09, Nilesh Govindrajan wrote: On Wednesday 23 January 2013 07:52:03 PM IST, Nikos Chantziaras wrote: [...] In my experience, most of the time you can overclock. The issue is with the user not knowing exactly how to do it. You need to understand a few things and how they affect each other. It's not just a knob you can turn. That pretty much applies to me. I don't know much about hardware stuff. Regarding your 1 Ghz overclock, you probably have good components in terms of RAM SMPS. When I bought this rig in 2008, I knew nothing about good components, blindly trusted local vendor... also internet shopping wasn't advanced here. So pretty much substandard components. The part that's really important is the mainboard. RAM doesn't matter. In my case, I had pretty basic 800MHz DDR2 RAM. Raising the FSB would bring it above that, so I changed the DRAM ratio to 1:1, and the RAM then ran at only 600Mhz. That was the starting point to rule out RAM problems. After that, I raised FSB but kept the VCore constant until I hit the first instabilities. When that happened, I raised VCore a bit. Rinse and repeat, until the VCore was still below the maximum recommendation by Intel. That happened at 3.4GHz (378MHz FSB * 9 CPU multiplier = 3402MHz CPU clock.) The E6600 CPU I got was an average sample. Others were running it at 3.6GHz (or even higher with water cooling.) This was a process that took about 3 days to complete (needs a lot of stability testing.) The good thing about those older CPUs was that the performance boost I got by OCing wasn't just scaling linearly with the CPU frequency. It was scaling *better* than that, because raising the FSB also made the mainboard itself perform better and with lower latencies. and here we are - the point where the suspension of disbelief ends. All you may have gained you threw away with the slower ram - and you are trying to tell us that your rig was faster? You do know that with today's CPUs the CPU is not the bottleneck - the slow as molasses, no speed bump for 10 years ram is. (just look at the internal clock rate of dram chips - and you realize that ddr1-3 are pretty much the same crap). Volker, in applications speficially tuned to keep their hot data small enough to stay in CPU cache (so, anything with a frames per second measurement), overclocking the CPU would still see performance improvements. Cache misses are always painful. -- :wq
[gentoo-user] /proc/net/wirelesslessness
I'm trying to build a kernel with this Atheros AR9287 wifi card. I had it working last week and rebuilt the kernel without saving my config, now I'm kind of stuck. The most immediate problem I see is that I have /proc/net/wireless, even though when I boot with SystemRescueCD it comes up fine. Thanks in advance! (Here's the info I have, feel free to query for more): - iwconfig wlan0 # On the bad boot wlan0 No wireless extensions - dmesg | grep -i ath # Same both boots (except for timestamps) [9.852491] ath: phy0: ASPM enabled: 0x42 [9.852495] ath: EEPROM regdomain: 0x65 [9.852496] ath: EEPROM indicates we should expect a direct regpair map [9.852498] ath: Country alpha2 being used: 00 [9.852499] ath: Regpair used: 0x65 [9.853587] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [9.853716] Registered led device: ath9k-phy0 [9.853720] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xc9001072, irq=17 - lspci -v | perl -ne 'print if /^03/../^$/' # Same on both boots 03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Foxconn International, Inc. Device e034 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at c050 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12 Capabilities: [170] Power Budgeting ? Kernel driver in use: ath9k Kernel modules: ath9k - lsmod # on the SystemRescueCD arc4 12390 2 ath9k 102072 0 mac80211 350410 1 ath9k ath9k_common 12681 1 ath9k coretemp 12440 0 ath9k_hw 335435 2 ath9k,ath9k_common ath21059 3 ath9k,ath9k_common,ath9k_hw crc32c_intel 12440 0 ghash_clmulni_intel12526 0 cfg80211 133830 3 ath9k,mac80211,ath acer_wmi 28774 0 tpm_tis16533 0 microcode 20802 0 tpm17694 1 tpm_tis tpm_bios 12440 1 tpm i2c_i801 16533 0 sparse_keymap 12655 1 acer_wmi joydev 16535 0 rfkill 17293 2 cfg80211,acer_wmi iTCO_wdt 16533 0 iTCO_vendor_support12639 1 iTCO_wdt raid10 32929 0 raid45653467 0 async_raid6_recov 12457 1 raid456 async_pq 12534 2 raid456,async_raid6_recov raid6_pq 82586 2 async_raid6_recov,async_pq async_xor 12452 3 raid456,async_raid6_recov,async_pq xor12425 1 async_xor async_memcpy 12388 2 raid456,async_raid6_recov async_tx 12624 5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy raid1 28846 0 raid0 16515 0 multipath 12390 0 linear 12390 0 radeon723200 0 ttm54081 1 radeon i915 349881 2 drm_kms_helper 26341 2 radeon,i915 usb_storage46993 1 drm 183602 5 radeon,ttm,i915,drm_kms_helper atl1c 30162 0 i2c_algo_bit 12477 2 radeon,i915 i2c_core 22125 6 i2c_i801,radeon,i915,drm_kms_helper,drm,i2c_algo_bit video 16668 2 acer_wmi,i915 wmi16837 1 acer_wmi
Re: [gentoo-user] Kernel Questions
Am 24.01.2013 00:27, schrieb Silvio Siefke: Hello, On Tue, 22 Jan 2013 20:48:49 +0100 Florian Philipp li...@binarywings.net wrote: [...] What kind of workload do we talk about? Properly niced and ioniced compile jobs? Is the freeze temporary? If I run a program, depending on the size the System Freeze for few seconds. When i start emerge -s, emerge --sync, emerge what ever the system freeze. Its ever temporary but its make crazy. Hmm, the last time I encountered something like this, DMA was deactivated for the hard disk. That happened because the wrong driver (generic IDE) took over. What raw throughput do you get? `dd if=/dev/sda of=/dev/null bs=4M count=100 iflag=direct` Odd. Maybe GPU related? Again, does the system recover? No GPU is deactivated. When have more then 10 tabs, system hang. You mean you have not enabled drm and/or use the generic vesa driver? Maybe something is trying to use opengl and software emulation slows you down. Doesn't surprise me. P4 and Atom are both horrible micro architectures. But Atom is also horribly stripped down and has a lower clock frequency. Oh, okay i know Atom is shit, but P4. Which architecture is recommended for? P4s suffer because their pipeline is very long and poorly utilized. In fact, they can execute fewer instructions per clock tick than a P3. Anything newer is a vast improvement, especially Core2 and newer. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Kernel Questions
Overheating problem? Considering it's about a Pentium 4, that seems a likely cause. Which P4 i has not so probs. The probs come with Atom. Older systems used to reset on overheat so it was obviously hardware. Newer cpus actually halt and then continue operation. Most of the time you won't notice, your laptop will just run slower than the spec would suggest. Some laptops never actually use the cpu fully from day one and so things like dust or a failing fan may make it very noticeable. Could be lots of things but I would check your temp sensors from the os or bios before the kernel. -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
Re: [gentoo-user] Kernel Questions
Anything newer is a vast improvement, especially Core2 and newer. As long as you ignore the unfixable security issues even by microcode of core2 duos ;-). -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
[gentoo-user] Re: Overclocking CPU causes segmentation fault
On 23/01/13 19:16, Volker Armin Hemmann wrote: Am 23.01.2013 16:35, schrieb Nikos Chantziaras: On 23/01/13 17:09, Nilesh Govindrajan wrote: On Wednesday 23 January 2013 07:52:03 PM IST, Nikos Chantziaras wrote: [...] In my experience, most of the time you can overclock. The issue is with the user not knowing exactly how to do it. You need to understand a few things and how they affect each other. It's not just a knob you can turn. That pretty much applies to me. I don't know much about hardware stuff. Regarding your 1 Ghz overclock, you probably have good components in terms of RAM SMPS. When I bought this rig in 2008, I knew nothing about good components, blindly trusted local vendor... also internet shopping wasn't advanced here. So pretty much substandard components. The part that's really important is the mainboard. RAM doesn't matter. In my case, I had pretty basic 800MHz DDR2 RAM. Raising the FSB would bring it above that, so I changed the DRAM ratio to 1:1, and the RAM then ran at only 600Mhz. That was the starting point to rule out RAM problems. After that, I raised FSB but kept the VCore constant until I hit the first instabilities. When that happened, I raised VCore a bit. Rinse and repeat, until the VCore was still below the maximum recommendation by Intel. That happened at 3.4GHz (378MHz FSB * 9 CPU multiplier = 3402MHz CPU clock.) The E6600 CPU I got was an average sample. Others were running it at 3.6GHz (or even higher with water cooling.) This was a process that took about 3 days to complete (needs a lot of stability testing.) The good thing about those older CPUs was that the performance boost I got by OCing wasn't just scaling linearly with the CPU frequency. It was scaling *better* than that, because raising the FSB also made the mainboard itself perform better and with lower latencies. and here we are - the point where the suspension of disbelief ends. All you may have gained you threw away with the slower ram - and you are trying to tell us that your rig was faster? Yes. It made the difference in all games. I'm talking 40 vs 60FPS here. It was huge. The RAM wasn't much slower. Stock was 800 and I was running it at 756. You do know that with today's CPUs the CPU is not the bottleneck - the slow as molasses, no speed bump for 10 years ram is. (just look at the internal clock rate of dram chips - and you realize that ddr1-3 are pretty much the same crap). The slightly slower RAM had no effect. As I said, the performance gain was huge. If the RAM ends up heavily underclocked to the FSB change, you just pick another ratio for it that brings it closer to its stock frequency, or slightly above it. Again, a good motherboard that has plenty of ratios to choose from helps immensely. Of course today this isn't important anymore. On my i5 CPU I can change the CPU multiplier. Not that I do; performance is plenty right now without OCing. I intend to overclock it in the future, just like I did with the C2D; if new games get more demanding, I'll do it then.
[gentoo-user] Re: Overclocking CPU causes segmentation fault
On 23/01/13 19:13, Volker Armin Hemmann wrote: Am 23.01.2013 09:21, schrieb Nikos Chantziaras: On 23/01/13 03:55, Dale wrote: [...] I tired overclocking once a good while back. It just wasn't worth it. I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three years. Instead of a new CPU, I only bought a €30 cooler. Oh, it *was* totally worth it. Mainly for games, where the performance difference was really dramatic. yeah and all those files with bit flips (not a problem with films or pics or mp3s) you don't know about were totally worth it... Stability testing is important. If no bit gets flipped after 5 hours of Prime95, one can be confident that the chip can take it. But I never noticed anything. At least git would have picked this up (I'm working on a project with 330k lines of code; a change gets picked up as a difference.) But I agree; if I had any hugely important data on my system, I would not have OCed it. I do not consider game saves, email and porn as hugely important :-P The source code *is* important, but I said, it's on a git server and therefore guarded against corruption.
[gentoo-user] MySQL startup problem - interface does not have an address yet.
I'm having a problem with booting my Gentoo system due to MySQL hanging at startup. My system is up-to-date stable (including udev-197, although I believe the problem started while I was still on 171) except for the kernel, which is at 3.1.10 because I can't seem to get lirc to work correctly on newer kernels. The problem started after a large system update just before the udev 171 to 197 migration. Among other upgrades dhcpcd was upgraded from 5.2.12 to 5.6.4, net-tools was upgraded from 1.60_p20110409135728 to 1.60_p20120127084908, and openrc was upgraded from 0.9.8.4 to 0.11.8. For historical reasons, this system has two ethernet adapters, eth0 and eth1. eth0 is not configured any more (it used to be used for IPTV connectivity to my cable provider for MythTV before they changes their system.) eth1 is configured via DHCP to an RFC 1918 10.x.x.x address - the DHCP server is always configured to provide the same IP address for this system. net.eth1 is symlinked to /etc/runlevels/default. The boot process starts, configures eth1, starts LCDd, and then attempts to start MySQL - and hangs for about 15 minutes before continuing with the boot. I added several debugging statements to /etc/init.d/mysql and found that even though the log shows that eth1 got its IP address, when MySQL attempts to start the interface does not have an IP address assigned. It's like the net.eth1 script exits before the interface is completely up. After the 15 minute hang, the system boots up as usual, except for MySQL not running. If I then start mysql manually it comes up immediately. Here's the rc.log output: * Starting D-BUS system messagebus ... [ ok ] * Bringing up interface eth1 * dhcp ... * Running dhcpcd ... dhcpcd[8400]: version 5.6.4 starting dhcpcd[8400]: eth1: waiting for carrier dhcpcd[8400]: eth1: carrier acquired dhcpcd[8400]: eth1: sending IPv6 Router Solicitation dhcpcd[8400]: eth1: sendmsg: Cannot assign requested address dhcpcd[8400]: eth1: rebinding lease of 10.x.y.14 dhcpcd[8400]: eth1: acknowledged 10.x.y.14 from 10.x.y.1 dhcpcd[8400]: eth1: checking for 10.x.y.14 dhcpcd[8400]: eth1: Router Advertisement from ::::: dhcpcd[8400]: forked to background, child pid 8454 [ ok ] * received address [ ok ] * Adding routes * 239.0.0.0/8 ... [ ok ] * Starting LCDd ... [ ok ] * Starting mysql ... [ !! ] * ERROR: mysql failed to start * Starting syslog-ng ... [ ok ] * Mounting network filesystems ... [ ok ] I added the following commands before the start-stop-daemon line in /etc/init.d/mysql: date /var/log/mysqlstart.log netstat -anp | grep 3306 /var/log/mysqlstart.log ps -efl | grep mysql /var/log/mysqlstart.log lsof -i @10.x.y.14:3306 /var/log/mysqlstart.log ifconfig -a /var/log/mysqlstart.log The output of this was: Wed Jan 23 09:56:03 PST 2013 0 S root 8497 8290 0 80 0 - 4301 poll_s 09:56 ? 00:00:00 /sbin/runscript /etc/init.d/mysql --lockfd 10 start 4 S root 8498 8497 1 80 0 - 3425 wait 09:56 ? 00:00:00 /bin/sh /lib64/rc/sh/runscript.sh /etc/init.d/mysql start 0 S root 8537 8498 0 80 0 - 2142 pipe_w 09:56 ? 00:00:00 grep mysql eth0: flags=4098BROADCAST,MULTICAST mtu 1500 ether 00:22:15:b7:ff:bc txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 22 base 0xa000 eth1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet6 ::::::: prefixlen 64 scopeid 0x0global inet6 ::::: prefixlen 64 scopeid 0x20link ether 00:1b:21:b1:cb:bb txqueuelen 1000 (Ethernet) RX packets 9 bytes 1149 (1.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 936 (936.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xfebe-fec0 lo: flags=73UP,LOOPBACK,RUNNING mtu 16436 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 As you can see, eth1 has no IPV4 address assigned. Once the server boots (after the 15 minute mysql timeout ends) ifconfig shows the following: eth1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 10.x.y.14 netmask 255.255.255.0 broadcast 10.x.y.255 inet6 ::::::: prefixlen 64 scopeid 0x0global inet6 ::::: prefixlen 64 scopeid 0x20link ether 00:1b:21:b1:cb:bb txqueuelen 1000 (Ethernet) RX packets 2732 bytes 496650
[gentoo-user] How can I update *every* ebuild?
Hi Gentoo-users, I always thought the right way to update everything was: emerge --update --deep --newuse world emerge --update --deep --newuse system When I try the above mentioned, nothing to update is found. Yet when I try i.e. emerge --pretend nasm, I see: [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01] So there is apparently update for dev-lang/nasm, yet it was not pulled when I tried to update the world or system. And who knows for how many other ebuilds there is update available... So how can I update really *every* ebuild? Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] How can I update *every* ebuild?
Am 23.01.2013 20:48, schrieb Jarry: Hi Gentoo-users, I always thought the right way to update everything was: emerge --update --deep --newuse world emerge --update --deep --newuse system When I try the above mentioned, nothing to update is found. Yet when I try i.e. emerge --pretend nasm, I see: [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01] So there is apparently update for dev-lang/nasm, yet it was not pulled when I tried to update the world or system. And who knows for how many other ebuilds there is update available... So how can I update really *every* ebuild? Jarry That's because nasm is only a build-dependency. Portage will update it when it is required for building the next time. Use --with-bdeps y to change that. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, Jan 23, 2013 at 2:48 PM, Jarry mr.ja...@gmail.com wrote: Hi Gentoo-users, I always thought the right way to update everything was: emerge --update --deep --newuse world emerge --update --deep --newuse system When I try the above mentioned, nothing to update is found. Yet when I try i.e. emerge --pretend nasm, I see: [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01] So there is apparently update for dev-lang/nasm, yet it was not pulled when I tried to update the world or system. And who knows for how many other ebuilds there is update available... So how can I update really *every* ebuild? Well, terminology issue first. An 'ebuild' is a file describing how the system handles a specific version of a particular package. So what you probably want to do is update every *package*. And in answer...you've got it right. (Though I would use @world and/or @system, rather than leaving off the @) Why nasm isn't getting updated might have something to do with your packages.mask file. -- :wq
Re: [gentoo-user] How can I update *every* ebuild?
On 23 January 2013 11:53, Michael Mol mike...@gmail.com wrote: On Wed, Jan 23, 2013 at 2:48 PM, Jarry mr.ja...@gmail.com wrote: snip/ emerge --update --deep --newuse world emerge --update --deep --newuse system snip/ So how can I update really *every* ebuild? And in answer...you've got it right. (Though I would use @world and/or @system, rather than leaving off the @) Why? While @world refers to the world set explicitly, it does exactly the same as world, doesn't it?. You could save a whole character! ;-) More seriously, the @ character isn't easy to type so I'd rather avoid it unless there is a real benefit to using it. More to the point, doing emerge ... system *after* emerge ... world seems pointless. World includes system so I would expect everything in system to already have been updated. It would make more sense to start with emerge ... system but even then: what is the advantage over simply (only) running emerge ... world? Cheers, Hilco
[gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wed, 23 Jan 2013 17:45:33 +0200 Alan McKinnon alan.mckin...@gmail.com wrote: [about udev and CONFIG_DEVTMPFS=y] A news item about this is coming down the wire very soon now (aka within hours judging by the thread on -dev). It's there now. Among other things, it mentions checking the /dev entry in fstab, if there is one. I don't have one, but I'm curious. Is it the udev-mount service in my default runlevel that makes it unnecessary to have /dev in fstab? Also, what would be the reasons for adding a /dev entry? Unfortunately, it's too late for you now but at least many other users will see the message before they emerge world and save them some pain Yeah. I use elogv to look at anything with warnings or errors after an emerge, and I can't explain how I overlooked the bright red notice this time. Normally, I follow this group and know what has come up for people running ~arch (or if I don't *know*, I at least remember there's to keep my eyes open for). But I've given up on following udev threads here, which tend to get pretty noisy. Of course there's no substitute for paying attention, but it's nice to get a news item, even nicer if it comes before things hit stable.
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, Jan 23, 2013 at 3:07 PM, Hilco Wijbenga hilco.wijbe...@gmail.com wrote: On 23 January 2013 11:53, Michael Mol mike...@gmail.com wrote: On Wed, Jan 23, 2013 at 2:48 PM, Jarry mr.ja...@gmail.com wrote: snip/ emerge --update --deep --newuse world emerge --update --deep --newuse system snip/ So how can I update really *every* ebuild? And in answer...you've got it right. (Though I would use @world and/or @system, rather than leaving off the @) Why? While @world refers to the world set explicitly, it does exactly the same as world, doesn't it?. You could save a whole character! ;-) More seriously, the @ character isn't easy to type so I'd rather avoid it unless there is a real benefit to using it. I don't know about your keyboard layout, but in en-us, @ is shift-2, which is pretty easy. And if you type cross-host email addresses at all (since the 80s, anyway), @ should come naturally. :) So, to answer 'why': 1. Newer versions of portage have broader support for sets. Using @ when talking about sets is useful for maintaining your understanding that you're working with sets. 2. While it may well never happen (unless portage drops support for resolving 'world' to mean '@world'), if there is ever a package named 'world', then emerge world when asking for the @world set will be ambiguous, and lead to surprising results. If you use apostrophes and punctuation in normal writing, a single @ in an infrequently-typed command shouldn't pose much of a problem. :) More to the point, doing emerge ... system *after* emerge ... world seems pointless. World includes system so I would expect everything in system to already have been updated. It would make more sense to start with emerge ... system but even then: what is the advantage over simply (only) running emerge ... world? That, I don't know. I usually just emerge -uDN @world, followed by emerge --depclean, followed by revdep-rebuild. And if I'm writing a script[1], I'll throw --resume in there somewhere. And maybe cycle it until everything comes out clean [1] https://github.com/mikemol/gentoo-install -- :wq
Re: [gentoo-user] /proc/net/wirelesslessness
On Wed, Jan 23, 2013 at 11:25 AM, ☈king rking...@sharpsaw.org wrote: I'm trying to build a kernel with this Atheros AR9287 wifi card. I had it working last week and rebuilt the kernel without saving my config, now I'm kind of stuck. The most immediate problem I see is that I have /proc/net/wireless, even though when I boot with SystemRescueCD it comes up fine. Thanks in advance! (Here's the info I have, feel free to query for more): - iwconfig wlan0 # On the bad boot wlan0 No wireless extensions Do you have CONFIG_WIRELESS_EXT=y ? If you can boot your old (working) kernel you may have /proc/config.gz where you can extract the kernel config (gzip -dc /proc/config.gz) similarly you can do the same from your boot CD environment and use it as a starting point for customizing.
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, Jan 23, 2013 at 08:48:03PM +0100, Jarry wrote: Hi Gentoo-users, I always thought the right way to update everything was: emerge --update --deep --newuse world emerge --update --deep --newuse system When I try the above mentioned, nothing to update is found. Yet when I try i.e. emerge --pretend nasm, I see: [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01] So there is apparently update for dev-lang/nasm, yet it was not pulled when I tried to update the world or system. And who knows for how many other ebuilds there is update available... So how can I update really *every* ebuild? This alias is in /root/.bashrc: alias ud='eix-sync emerge -aDjNuv @world dispatch-conf emerge -a --depclean revdep-rebuild -i clear exit' emerge -aDjNuv @world a = ask (Yes/No prompt -- don't waste time with --pretend) D = deep (consider the entire dependency tree of packages) j = jobs (no number after j means to run as many simultaneously as possible) N = newuse (pkgs with changed USE flags) u = update (to the best version available) v = verbose @world = world set man emerge would be very enlightening for you... It's important to sync (eix-sync) before you start, or your local portage tree won't have any new software; and equally important to check configs (dispatch-conf), clean out pkgs no longer needed (--depclean), and rebuild any deps (revdep-rebuild). Don' forget to read news (eselect news read). Running this ud alias every morning with coffee on no less than 8 Gentoo boxen on this LAN keeps everything updated, clean, and I'm usually one of the first to find new bugs. Well, since my test machine running ~amd64 is no longer in service, there are less bugs. But, still, there are enough bugs in amd64. Cheers, Bruce -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wed, 23 Jan 2013 22:06:17 +1100, Gregory Shearman wrote: That's fine if you see the message, which you should, and the system does not suffer an unplanned reboot, which it shouldn't. But leaving a system in a state that won't reboot following a crash or power failure is not particularly clever, making the warnings fatal sounds a safe default to me. As this is Gentoo there will always be a way to turn the airbags off and even disable the brakes :) I have all update messages emailed to me using: PORTAGE_ELOG_*=blah As do I. After every update I read every message that portage sends me and I act appropriately upon them. As do I. BTW, My udev update went without a hitch. I had a revdep-rebuild to do for a libudev update and that was about it. As did mine, but none of that has any real relevance to my previous point. What if you have an unintentional reboot before you have had a chance to read on and act on the message. The point is that this update can render your machine unbootable, until you take remedial action that you are only informed about after the update. Effectively, that elog message is saying I have just broken your computer, you'd better fix it before you reboot!. Even if you didn't see the message and your system didn't boot then you could still fix things by using your Minimal Install CD to start up, then chroot into your normal system and rebuild your kernel. That remedy should be reserved for unforseen circumstances, not used as an excuse for casual breakage. -- Neil Bothwick why do kamikazee pilots wear helmets? signature.asc Description: PGP signature
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, 23 Jan 2013 15:21:35 -0600, Bruce Hill wrote: N = newuse (pkgs with changed USE flags) --changed-use makes more sense than -N, it saves unnecessary compiling. -- Neil Bothwick Mac screen message: Like, dude, something went wrong. signature.asc Description: PGP signature
Re: [gentoo-user] Kernel Questions
Hello,
On Wed, 23 Jan 2013 18:31:10 +
Kevin Chadwick ma1l1i...@yahoo.co.uk wrote:
Could be lots of things but I would check your temp sensors from
the os or bios before the kernel.
is lmsensors ok?
siefke@gentoo-mobile : ~ $ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:+52.0°C (crit = +98.0°C)
coretemp-isa-
Adapter: ISA adapter
Core 0: +38.0°C (crit = +90.0°C)
Maybe is make.conf the wrong way?
CHOST=i686-pc-linux-gnu
CFLAGS=-march=native -O2 -fomit-frame-pointer -pipe -mfpmath=sse
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2
Thank you Regards
Re: [gentoo-user] Kernel Questions
Hello, On Wed, 23 Jan 2013 19:27:17 +0100 Florian Philipp li...@binarywings.net wrote: You mean you have not enabled drm and/or use the generic vesa driver? Maybe something is trying to use opengl and software emulation slows you down. In Opera no, in other i not have really something change in config files. P4s suffer because their pipeline is very long and poorly utilized. In fact, they can execute fewer instructions per clock tick than a P3. Anything newer is a vast improvement, especially Core2 and newer. I have look for new Netbook today. Maybe should buy one with i3 or i5, what is so with AMD? Is there something intresting? Thank you Greetings Silvio
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, Jan 23, 2013 at 10:27:54PM +, Neil Bothwick wrote: On Wed, 23 Jan 2013 15:21:35 -0600, Bruce Hill wrote: N = newuse (pkgs with changed USE flags) --changed-use makes more sense than -N, it saves unnecessary compiling. If I understand man emerge, --newuse tells me if an installed package has a USE flag that was added, removed, turned on, or turned off; whereas --changed-use only notifies me if a USE flag that I've chosen on my installed packages are changed -- not any other USE flags the maintainer, or some other committer, has changed (those have bitten me in the past). Since I'm not really interested in reading the ChangeLog for *hundreds* of packages, N (--newuse) suits me better. Those flags have special colors and one or more of - * % () symbols so a quick glance lets me know *which* pkgs the dev has changed, and *which* pkgs ChangeLog I might want to read. -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, 23 Jan 2013 17:01:11 -0600, Bruce Hill wrote: N = newuse (pkgs with changed USE flags) --changed-use makes more sense than -N, it saves unnecessary compiling. If I understand man emerge, --newuse tells me if an installed package has a USE flag that was added, removed, turned on, or turned off; whereas --changed-use only notifies me if a USE flag that I've chosen on my installed packages are changed -- not any other USE flags the maintainer, or some other committer, has changed (those have bitten me in the past). That's right. So --changed-use only reemerges the package if the change only affects your system, whereas -N will rebuild it even if the changed flag is of no interest to you, such as when a flag you were not using is removed. It saves recompiling packages for no reason, which is presumably the reason it was added, it is a newer option than -N. -- Neil Bothwick This is the day for firm decisions! Or is it? signature.asc Description: PGP signature
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, Jan 23, 2013 at 11:15:10PM +, Neil Bothwick wrote: That's right. So --changed-use only reemerges the package if the change only affects your system, whereas -N will rebuild it even if the changed flag is of no interest to you, such as when a flag you were not using is removed. It saves recompiling packages for no reason, which is presumably the reason it was added, it is a newer option than -N. The purpose of -a (ask) is so you can see the stuff before taking action, and if it needs rebuilding then do it. Nothing is rebuilt just because it shows up in the output; but not seeing changes to a package you use that were made is not too bright. If you ever built from source before, I'm sure you didn't blindly build the software without reading ./configure --help and checking your options. -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] How can I update *every* ebuild?
Michael Mol wrote: On Wed, Jan 23, 2013 at 3:07 PM, Hilco Wijbenga hilco.wijbe...@gmail.com wrote: On 23 January 2013 11:53, Michael Mol mike...@gmail.com wrote: On Wed, Jan 23, 2013 at 2:48 PM, Jarry mr.ja...@gmail.com wrote: snip/ emerge --update --deep --newuse world emerge --update --deep --newuse system snip/ So how can I update really *every* ebuild? And in answer...you've got it right. (Though I would use @world and/or @system, rather than leaving off the @) Why? While @world refers to the world set explicitly, it does exactly the same as world, doesn't it?. You could save a whole character! ;-) More seriously, the @ character isn't easy to type so I'd rather avoid it unless there is a real benefit to using it. I don't know about your keyboard layout, but in en-us, @ is shift-2, which is pretty easy. And if you type cross-host email addresses at all (since the 80s, anyway), @ should come naturally. :) So, to answer 'why': 1. Newer versions of portage have broader support for sets. Using @ when talking about sets is useful for maintaining your understanding that you're working with sets. 2. While it may well never happen (unless portage drops support for resolving 'world' to mean '@world'), if there is ever a package named 'world', then emerge world when asking for the @world set will be ambiguous, and lead to surprising results. If you use apostrophes and punctuation in normal writing, a single @ in an infrequently-typed command shouldn't pose much of a problem. :) More to the point, doing emerge ... system *after* emerge ... world seems pointless. World includes system so I would expect everything in system to already have been updated. It would make more sense to start with emerge ... system but even then: what is the advantage over simply (only) running emerge ... world? That, I don't know. I usually just emerge -uDN @world, followed by emerge --depclean, followed by revdep-rebuild. And if I'm writing a script[1], I'll throw --resume in there somewhere. And maybe cycle it until everything comes out clean [1] https://github.com/mikemol/gentoo-install -- :wq All I ever do is emerge -uvaDN world and it catches everything. If you use plain world, it includes the system set. If you use @world, then some things in the @system set may not be upgraded. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
[gentoo-user] Nginx with Python
Hello, has someone run this part of Server and maybe will share the way? I look since days for tutorial but so really want nothing run. With Gentoo found nothing really most of them speak from Ubuntu. Thank you for Help Greetings Silvio
Re: [gentoo-user] libv8 segfault
I didn't merge anything while I was playing with overclocking. custom-cflags is enabled. Disable custom-cflags and try again. You shouldn't expect things to work when that's on. You may get lucky at times, but youre not getting lucky now.
Re: [gentoo-user] /proc/net/wirelesslessness
Do you have CONFIG_WIRELESS_EXT=y ? No, I sure don't. Looking at this list of conditions that are required to enable that setting is quite impressive/daunting. I'm not sure which I should enable. I'll work on it. -RK
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wednesday 23 January 2013 11:06:17 Gregory Shearman wrote: Even if you didn't see the message ...as I didn't... and your system didn't boot ...as mine didn't... then you could still fix things by using your Minimal Install CD to start up, then chroot into your normal system and rebuild your kernel. ...as I did. I described this in my message of Sunday last. Anyway, my point is that I didn't see any warnings of what was about to happen, and I don't expect to find myself with an unbootable, supposedly stable system, i.e. without setting ~amd64. Something went wrong here. Mind you, it was nothing like the mayhem caused by the latest kmail. -- Peter
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wednesday 23 January 2013 20:10:45 »Q« wrote: Of course there's no substitute for paying attention, but it's nice to get a news item, even nicer if it comes before things hit stable. Indeed. -- Peter
Re: [gentoo-user] Overclocking CPU causes segmentation fault
On Wednesday 23 January 2013 01:55:19 Dale wrote: Also, I used to run foldingathome. It does not do well with overclocking. It will error out pretty quick. I tried this on a Abit NF7 v2 mobo. At that time, they were pretty much the king of overclocking. I bought everything intending to overclock but it wasn't worth it. I had a HUGE copper heat sink on that CPU. I remember your enthusiasm at the time. I'm glad you came back down to earth in the end :-) -- Peter
Re: [gentoo-user] Kernel Questions
On Wed, Jan 23, 2013 at 06:33:38PM +, Kevin Chadwick wrote: Anything newer is a vast improvement, especially Core2 and newer. As long as you ignore the unfixable security issues even by microcode of core2 duos ;-). -v please -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any Facebook service. Does fuzzy logic tickle? signature.asc Description: Digital signature
Re: [gentoo-user] PATA vs SATA kernel driver (was: 4 machines - no /dev/cdrom or /dev/dvd anymore)
On Fri, Jan 11, 2013 at 12:14:18AM +0200, Alan McKinnon wrote: Since this is depreciated, which generally means no longer maintained nitpick The word you want is deprecated. depreciated is something else entirely, it's what your employer does to the book value of your company car over 5 years to get the value down to nothing. /nitpick Depreciated is perfectly cromulent in this instance. You really think it's copacetic? I never heard of copacetic till now, had to look it up. Sorry to necropost, but I waited many a month for this opportunity, for I have a nitpick to shoot back with: What a wonderful word, I feel embiggened by it's correctness ^ “it’s”, just like “he’s”, is a contraction with the verb “is”. What you meant was “its”, meaning a posession belonging to “it”. *runs, ducks and hides* Depreciate, for me, is basically de- (which usually has a negative meaning) and preciate, i.e. gollum ”making a precious” /gollum). ;-) But well, being a foreign speaker and a grammar n*zi, I might have an unfair advantage about such thing. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any Facebook service. Bank -- an institution where you can borrow money for the proof that you don’t need it. signature.asc Description: Digital signature
Re: [gentoo-user] Overclocking CPU causes segmentation fault
Peter Humphrey wrote: On Wednesday 23 January 2013 01:55:19 Dale wrote: Also, I used to run foldingathome. It does not do well with overclocking. It will error out pretty quick. I tried this on a Abit NF7 v2 mobo. At that time, they were pretty much the king of overclocking. I bought everything intending to overclock but it wasn't worth it. I had a HUGE copper heat sink on that CPU. I remember your enthusiasm at the time. I'm glad you came back down to earth in the end :-) I still would run folding if it would work right. It seems every time I turn around, something was broke. The biggest problem, when I start it, there is no work to do. I haven't tried it this year. Just never got around to it. So, if it worked, I'd still be doing it. I'm not cured of my medical issues but wouldn't mind donating to help with someone else's. One never knows what it could lead too or already has. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] Nginx with Python
On Thursday 24 January 2013 05:34:50 AM IST, Silvio Siefke wrote: Hello, has someone run this part of Server and maybe will share the way? I look since days for tutorial but so really want nothing run. With Gentoo found nothing really most of them speak from Ubuntu. Thank you for Help Greetings Silvio Have a look at uwsgi. It can run pretty much anything. -- Nilesh Govindarajan http://nileshgr.com
Re: [gentoo-user] How can I update *every* ebuild?
On Wed, 23 Jan 2013 20:48:03 +0100 Jarry mr.ja...@gmail.com wrote: Hi Gentoo-users, I always thought the right way to update everything was: emerge --update --deep --newuse world emerge --update --deep --newuse system When I try the above mentioned, nothing to update is found. Yet when I try i.e. emerge --pretend nasm, I see: [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01] So there is apparently update for dev-lang/nasm, yet it was not pulled when I tried to update the world or system. And who knows for how many other ebuilds there is update available... So how can I update really *every* ebuild? What are your bdep settings in make.conf? (see man emerge for more info on bdeps) nasm is unlikely to be a run-time depend for anything, considering what it does it's more likely to be a build depend. If nothing in world that uses nasm to build itslef is to be built, then nasm won't be upgraded; it will be left as-is until it really does need to be rebuilt. You should learn to trust portage, it knows more about your system than you do. really update every package sounds a lot more like pedantic OCD insistence that it all be done always rather than a sensible decision :-) And before anyone rips me a new one for being unbelievably rude to list users again, I have the same issue myself. So I got really good at spotting it and recognizing why it is not really a good thing. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: Udev-197 : 4 show-stoppers
On Wed, 23 Jan 2013 14:10:45 -0600 »Q« boxc...@gmx.net wrote: On Wed, 23 Jan 2013 17:45:33 +0200 Alan McKinnon alan.mckin...@gmail.com wrote: [about udev and CONFIG_DEVTMPFS=y] A news item about this is coming down the wire very soon now (aka within hours judging by the thread on -dev). It's there now. Among other things, it mentions checking the /dev entry in fstab, if there is one. I don't have one, but I'm curious. Is it the udev-mount service in my default runlevel that makes it unnecessary to have /dev in fstab? Also, what would be the reasons for adding a /dev entry? yes it's udev-mount: if ! grep -qs devtmpfs /proc/filesystems; then eerror CONFIG_DEVTMPFS=y is required in your kernel configuration eerror for this version of udev to run successfully. eerror This requires immediate attention. if ! mountinfo -q /dev; then mount -n -t tmpfs dev /dev busybox mdev -s mkdir /dev/pts fi I don't see any good reason whatsoever to add /dev to fstab, unless you want to change the default mount options for some reason Unfortunately, it's too late for you now but at least many other users will see the message before they emerge world and save them some pain Yeah. I use elogv to look at anything with warnings or errors after an emerge, and I can't explain how I overlooked the bright red notice this time. Normally, I follow this group and know what has come up for people running ~arch (or if I don't *know*, I at least remember there's to keep my eyes open for). But I've given up on following udev threads here, which tend to get pretty noisy. Of course there's no substitute for paying attention, but it's nice to get a news item, even nicer if it comes before things hit stable. :-) I seem to have lost my virtual consoles recently, courtesy of udev-197 :-( Haven't figured out why yet, I suppose I'll have to read all those noisy udev threads again -- Alan McKinnon alan.mckin...@gmail.com
