[gentoo-user] crossdev --target armv7a-unknown-linux-gnueabi failed ...
Hi, with crossdev I tried to build a toolchain for the armv7a-unknown-linux-gnueabi target. The build process failed due to a wrong format of an archive of patches. Is there a way for a local quick fix...or am I lost for a longer period of time... ;) ??? Best regards, mcc Log: _ * Package:cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90 * Repository: proaudio * Maintainer: toolch...@gentoo.org * USE:amd64 cxx elibc_glibc kernel_linux nls userland_GNU zlib * FEATURES: sandbox ESC[1mESC[37mcfg-update-1.8.2-r1ESC[0mESC[0m: Checksum index is up-to-date ... Unpacking source... Unpacking binutils-2.22.90.tar.bz2 to /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work Unpacking binutils-2.22.90-patches-1.1.tar.xz to /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work unpack binutils-2.22.90-patches-1.1.tar.xz: file format not recognized. Ignoring. * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work/patch * ( patch ) * ERROR: cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90 failed (unpack phase): * Cannot find $EPATCH_SOURCE! * * Call stack: * ebuild.sh, line 85: Called src_unpack * environment, line 2962: Called toolchain-binutils_src_unpack * environment, line 3750: Called tc-binutils_apply_patches * environment, line 3059: Called epatch * environment, line 1378: Called die * The specific snippet of code: * die Cannot find \$EPATCH_SOURCE!; * * If you need support, post the output of `emerge --info '=cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90'`, * the complete build log and the output of `emerge -pqv '=cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90'`. * This ebuild used the following eclasses from overlays: * /var/lib/layman/pro-audio/eclass/unpacker.eclass * This ebuild is from an overlay named 'proaudio': '/var/lib/layman/pro-audio/' * The complete build log is located at '/var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/temp/environment'. * Working directory: '/var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work/binutils-2.22.90' * S: '/var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work/binutils-2.22.90'
[gentoo-user] qt-webkit doesn't compile
As title says, qt-webkit-4.8.2 doesnt compile on an amd64 config and a new install. Known problem ? Known solution ? Or should I fill a bug report ?
Re: [gentoo-user] qt-webkit doesn't compile
Am 17.08.2012 08:21, schrieb Alain Didierjean: As title says, qt-webkit-4.8.2 doesnt compile on an amd64 config and a new install. Known problem ? Known solution ? Or should I fill a bug report ? Please post the compile output (the last part where it fails is sufficient). And also your make.conf. signature.asc Description: OpenPGP digital signature
[gentoo-user] A patch about fbreader for gentoo amd64
Hello all, I'm trying to emerge app-text/fbreader, but I found there's a bug that not solved about glib.h not fount. Somebody gave a solution about it, but I don't like to modify the ebuild files.Then I get the source form /usr/portage/distfiles/fbreader-sources-0.12.10.tgz, and make it by myself. I found that we just need to fix some config in the source, and then makemake install it OK. I made a patch for it by git diff. I don't know how to make a fully patch for Gentoo, so I and send it here, hope it useful for the vindicators to fix the bug. Thanks B.R Kermit fbreader-0.12.10-gentoo-r1.patch.tar.bz2 Description: BZip2 compressed data
Re: [gentoo-user] qt-webkit doesn't compile
On Fri, Aug 17, 2012 at 08:21:28AM +0200, Alain Didierjean wrote:
As title says, qt-webkit-4.8.2 doesnt compile on an amd64 config and a new
install.
Known problem ?
Known solution ?
Or should I fill a bug report ?
I'm sure that it works OK, it's not a bug. It must be your config
error. You may need to paste more detail infomation about the errors.
$ eix qt-webkit
[I] x11-libs/qt-webkit
Available versions: (4) 4.7.4 4.8.1 4.8.2 **4.8.[1]
{{aqua dbus debug +exceptions +gstreamer (+)icu +jit kde pch qpa}}
Installed versions: 4.8.2(4)(03:53:07 PM 07/28/2012)(exceptions gstreamer
jit -aqua -debug -icu -pch -qpa)
Homepage:http://qt-project.org/ http://qt.nokia.com/
Description: The WebKit module for the Qt toolkit
[1] qt /var/lib/layman/qt
[gentoo-user] My PC died. What should I try?
Hi there! Two days ago, my PC suddenly died, after working fine for half a year. I used myrtcwake as usual to suspend to RAM, and it woke up in the morning. But after two minutes, the screen went blank and nothing, even SysRq, gave a reaction. I tried booting a couple of times again, and sometimes it did not even reach KDM. Now, I cannot even run Grub (from my USB stick) any more, I only see a GRUB string at the top right, then nothing happens. Booting with SystemRescueCD also freezes sometimes. If not, I can make it freeze after seconds by running 'memtester'. Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. Running memtester after booting from SystemrescueCD again makes the thing freeze in seconds. It once also froze while being in the BIOs setup. What could be the problem? CPU, board, or even the PSU? I do not think it has to do with bad memory. I removed most of the other stuff (hard drives, PCI cards). I have no similar hardware so I cannot simply exchange things, the question is what to buy and try. How would you proceed? The fan is still working, the cooler does not become hot, and in the BIOS there are not high temperatures begin reported. But one thing was strange: I updated Calligra from 2.4 to 2.5 (I think), and it took ages, at least 8 hours. I thought there may b something strange with the build process of this new version, forcing MAKEOPTS=-j1 and such, but still this is very long. But when working with it, I did not notice anything strange like sluggish reactions, and videos played fine. But I did not use it as much as I normally do, and maybe even when overheated and throttled down it would have been fast enough for me to not notice this. I watch the syslog normally, but maybe I just did not look closely that day, I was busy doing other stuff. CPUs don't just die, do they? Even when overheating, I think these days throttle down, so no permanent harm should be done? So maybe it's the board? It looks okay, no bent or leaking capacitors. This is really annoying. Of course most of my passwords are in my KDE wallet I cannot access. There's also Wiki, CVS and Git repositories, not needed every day, but still important. And the timinig is very bad, I just started my new job the day the problem happened, and I do not have much time for this now. Before, I was working at home, so I would have had all day to diagnose and try things. It's an AMD FX-4100 Quad-Core CPU, and an ASRock 880GMH/U3S3 board. Wonko
Re: [gentoo-user] My PC died. What should I try?
Hi Alex, ...shot in the dark: Remove as much as possible of the cards, addons, connections etc from the PC ... make in as much bare bone as possible. Check All coolers (the little ones also) for dust. Remove all dust even if it is not completly covered with it. Dont forget the internals of the power supply. Detach all cables. Remove the power supply. Go outside ;) and blow the dust inside away. Put the power supply back into the PC again an attach the cables. Remove all RAM, carefully clean the contacts, insert as less RAM as possible. Remove even the HD if it is possible to get into the BIOS without any HD attached. Remove the BIOS battery, wait at least a day and insert it again. Start the PC and go directly into the BIOS. Check the date/time. If it shows the current date/time, the battery wasn't removed long enough. Check the battery voltage. Reinsert the battery. If your board has a BIOS reset: Reset the BIOS. Then: In the BIOS enter a page which does something (reports continously temperatures for example). If this is possible, let the PC run for a while that BIOS page and see, whether it hangs again or not. If all went fine, add ONE component and try it again. Add the HD at last to sort out hardware from software bugs... May be one of the components and not the CPU or motherboard causes the problem and you will be able to identify it by this procedure... HTH! GOOD LUCK! Best regard, mcc Alex Schuster wo...@wonkology.org [12-08-17 09:56]: Hi there! Two days ago, my PC suddenly died, after working fine for half a year. I used myrtcwake as usual to suspend to RAM, and it woke up in the morning. But after two minutes, the screen went blank and nothing, even SysRq, gave a reaction. I tried booting a couple of times again, and sometimes it did not even reach KDM. Now, I cannot even run Grub (from my USB stick) any more, I only see a GRUB string at the top right, then nothing happens. Booting with SystemRescueCD also freezes sometimes. If not, I can make it freeze after seconds by running 'memtester'. Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. Running memtester after booting from SystemrescueCD again makes the thing freeze in seconds. It once also froze while being in the BIOs setup. What could be the problem? CPU, board, or even the PSU? I do not think it has to do with bad memory. I removed most of the other stuff (hard drives, PCI cards). I have no similar hardware so I cannot simply exchange things, the question is what to buy and try. How would you proceed? The fan is still working, the cooler does not become hot, and in the BIOS there are not high temperatures begin reported. But one thing was strange: I updated Calligra from 2.4 to 2.5 (I think), and it took ages, at least 8 hours. I thought there may b something strange with the build process of this new version, forcing MAKEOPTS=-j1 and such, but still this is very long. But when working with it, I did not notice anything strange like sluggish reactions, and videos played fine. But I did not use it as much as I normally do, and maybe even when overheated and throttled down it would have been fast enough for me to not notice this. I watch the syslog normally, but maybe I just did not look closely that day, I was busy doing other stuff. CPUs don't just die, do they? Even when overheating, I think these days throttle down, so no permanent harm should be done? So maybe it's the board? It looks okay, no bent or leaking capacitors. This is really annoying. Of course most of my passwords are in my KDE wallet I cannot access. There's also Wiki, CVS and Git repositories, not needed every day, but still important. And the timinig is very bad, I just started my new job the day the problem happened, and I do not have much time for this now. Before, I was working at home, so I would have had all day to diagnose and try things. It's an AMD FX-4100 Quad-Core CPU, and an ASRock 880GMH/U3S3 board. Wonko
Re: [gentoo-user] My PC died. What should I try?q
Aaa aAaa aaa a Am 17.08.2012 10:31 schrieb meino.cra...@gmx.de: Hi Alex, ...shot in the dark: Remove as much as possible of the cards,aadwqqqaaa www wpa www a weißes www aa Array www www www a aaa aa aadwqqqaaa aaa w aadwqqqaaa www aa aaa a aaa www Awaa aaa aa quattro Aquarellw aaa aa aa Webauftritt aaa a aaa aA aaa aAaAaAaq aaawa addons, connections etcwo from the PC ... make ian as much bare bone aaa stwww wwwaaa www qaaa wwwas a. www www waslittle ones also) for dust. Removeaa wwwaa all dust even if it is not completly covered with ait. Dona www ot forget the internals of the power supply. Detach all cables. Remove the power supply. Go outside ;) and blow the dust inside away. Put the power supply back into the PC again an attach the cables. Remove all RAM, carefully clean the contacts, insert as less RAM as possible. Remove even the HD if it is possible to get into the BIOS without any HD attached. Remove the BIOS battery, wait at least a day and insert it again. Start the PC and go directly into the BIOS. Check the date/time. If it shows the current date/time, the battery wasn't removed long enough. Check the battery voltage. Reinsert the battery. If your board has a BIOS reset: Reset the BIOS. Then: In the BIOS enter a page which does something (reports continously temperatures for example). If this is possible, let the PC run for a while that BIOS page and see, whether it hangs again or not. If all went fine, add ONE component and try it again. Add the HD at last to sort out hardware from software bugs... May be one of the components and not the CPU or motherboard causes the problem and you will be able to identify it by this procedure... HTH! GOOD LUCK! Best regard, mcc Alex Schuster wo...@wonkology.org [12-08-17 09:56]: Hi there! Two days ago, my PC suddenly died, after working fine for half a year. I used myrtcwake as usual to suspend to RAM, and it woke up in the morning. But after two minutes, the screen went blank and nothing, even SysRq, gave a reaction. I tried booting a couple of times again, and sometimes it did not even reach KDM. Now, I cannot even run Grub (from my USB stick) any more, I only see a GRUB string at the top right, then nothing happens. Booting with SystemRescueCD also freezes sometimes. If not, I can make it freeze after seconds by running 'memtester'. Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. Running memtester after booting from SystemrescueCD again makes the thing freeze in seconds. It once also froze while being in the BIOs setup. What could be the problem? CPU, board, or even the PSU? I do not think it has to do with bad memory. I removed most of the other stuff (hard drives, PCI cards). I have no similar hardware so I cannot simply exchange things, the question is what to buy and try. How would you proceed? The fan is still working, the cooler does not become hot, and in the BIOS there are not high temperatures begin reported. But one thing was strange: I updated Calligra from 2.4 to 2.5 (I think), and it took ages, at least 8 hours. I thought there may b something strange with the build process of this new version, forcing MAKEOPTS=-j1 and such, but still this is very long. But when working with it, I did not notice anything strange like sluggish reactions, and videos played fine. But I did not use it as much as I normally do, and maybe even when overheated and throttled down it would have been fast enough for me to not notice this. I watch the syslog normally, but maybe I just did not look closely that day, I was busy doing other stuff. CPUs don't just die, do they? Even when overheating, I think these days throttle down, so no permanent harm should be done? So maybe it's the board? It looks okay, no bent or leaking capacitors. This is really annoying. Of course most of my passwords are in my KDE wallet I cannot access. There's also Wiki, CVS and Git repositories, not needed every day, but still important. And the timinig is very bad, I just started my new job the day the problem happened, and I do not have much time for this now. Before, I was working at home, so I would have had all day to diagnose and try things. It's an AMD FX-4100 Quad-Core CPU, and an ASRock 880GMH/U3S3 board. Wonko Am 17.08.2012 10:31 schrieb meino.cra...@gmx.de: Hi Alex, ...shot in the dark: Remove as much as possible of the cards, addons, connections etc from the PC ... make in as much bare bone as possible. Check All coolers (the little ones also) for dust. Remove all dust even if it is not completly covered with it. Dont forget the internals of the power supply. Detach
[gentoo-user] /dev/snd/seq access mode and permission
Hi, how do I make changes to permissions and access mode of device nodes persistent? At the moment I have to chown and chmod the /dev/snd/seq node every boot to make it accessible to my user. the other nodes are fine. Here's the output of ls -l /dev/snd/ total 0 drwxr-xr-x 2 root root 60 Aug 17 18:44 by-path crw-rw+ 1 root audio 116, 12 Aug 17 18:44 controlC0 crw-rw+ 1 root audio 116, 11 Aug 17 18:44 hwC0D0 crw-rw+ 1 root audio 116, 10 Aug 17 18:44 hwC0D3 crw-rw+ 1 root audio 116, 9 Aug 17 18:44 hwC0D4 crw-rw+ 1 root audio 116, 8 Aug 17 18:44 hwC0D5 crw-rw+ 1 root audio 116, 7 Aug 17 18:44 pcmC0D0c crw-rw+ 1 root audio 116, 6 Aug 17 18:44 pcmC0D0p crw-rw+ 1 root audio 116, 5 Aug 17 18:44 pcmC0D1p crw-rw+ 1 root audio 116, 4 Aug 17 18:44 pcmC0D3p crw-rw+ 1 root audio 116, 3 Aug 17 18:44 pcmC0D7p crw-rw+ 1 root audio 116, 2 Aug 17 18:44 pcmC0D8p crw--- 1 root root 116, 1 Aug 17 18:44 seq crw-rw+ 1 root audio 116, 33 Aug 17 18:44 timer I need /dev/snd/seq to look look the others. I can't find the udev rule or configuration that creates these nodes. Many thanks for any consideration. _ Get your FREE, LinuxWaves.com Email Now! -- http://www.LinuxWaves.com Join Linux Discussions! -- http://Community.LinuxWaves.com
[gentoo-user] common flags for 2 cpu?
I'm in need of some expert advise about CFLAGS. I'm going to install Gentoo in two systems, an Atom 330 and a P4 prescott. Since compiling lots of stuff in an Atom is less than joyful, I intend to do almost all compilation on the prescott and produce binary packages to use on the Atom. So, something like CFLAGS=-march=native ... is out. I know I could set CFLAGS=-march=i686 -O2 -pipe -fomit-frame-pointer, but I would like to extract a bit more juice from the hw, while still keeping stable systems. So, I thought of setting CFLAGS for both systems as -march=i686, plus the flags that are pulled by -march=native in both systems, plus some other flags: -march=i686 -mno-aes -mno-pclmul -mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -mno-sse4.2 -mno-sse4.1 -mno-lzcnt -mno-rdrnd -mno-f16c -mno-fsgsbase --param l1-cache-size=16 --param l1-cache-line-size=64 --param l2-cache-size=1024 -pni -mtrr This is what is pulled by -march=native, using gcc -march=native -E -v - /dev/null 21 | grep cc1 Prescott: -march=prescott -mno-cx16 -mno-sahf -mno-movbe -mno-aes -mno-pclmul -mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -mno-sse4.2 -mno-sse4.1 -mno-lzcnt -mno-rdrnd -mno-f16c -mno-fsgsbase --param l1-cache-size=16 --param l1-cache-line-size=64 --param l2-cache-size=1024 -mtune=prescott Atom: -march=atom -mcx16 -msahf -mmovbe -mno-aes -mno-pclmul -mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -mno-sse4.2 -mno-sse4.1 -mno-lzcnt -mno-rdrnd -mno-f16c -mno-fsgsbase --param l1-cache-size=24 --param l1-cache-line-size=64 --param l2-cache-size=512 -mtune=atom Flags supported (from cat /proc/cpuinfo|grep flags): Prescott: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc pebs bts pni dtes64 monitor ds_cpl cid xtpr Atom: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm Some questions: 1) Is this strategy right? If so, any other flags to add? (or any flags to remove from the list?) 2) The --param flags are the ones of the computer that will do the compiling. I'm guessing the produced binaries are compatible with cpu with different --param flags. Is this right? TIA Jorge Almeida
Re: [gentoo-user] My PC died. What should I try?
Am Freitag, 17. August 2012, 09:50:40 schrieb Alex Schuster: sounds like a power problem. Either psu is gone bad (get a new one) or your mainboard's power circuitry gone bad (if replacement of psu does not help, get a new one). But first thing first: disconnect your hdds! No reason to risk them. -- #163933
Re: [gentoo-user] /dev/snd/seq access mode and permission
On Fri, 17 Aug 2012 01:54:34 -0700 Cinder cin...@linuxwaves.com wrote: Hi, how do I make changes to permissions and access mode of device nodes persistent? At the moment I have to chown and chmod the /dev/snd/seq node every boot to make it accessible to my user. the other nodes are fine. Here's the output of ls -l /dev/snd/ total 0 drwxr-xr-x 2 root root 60 Aug 17 18:44 by-path crw-rw+ 1 root audio 116, 12 Aug 17 18:44 controlC0 crw-rw+ 1 root audio 116, 11 Aug 17 18:44 hwC0D0 crw-rw+ 1 root audio 116, 10 Aug 17 18:44 hwC0D3 crw-rw+ 1 root audio 116, 9 Aug 17 18:44 hwC0D4 crw-rw+ 1 root audio 116, 8 Aug 17 18:44 hwC0D5 crw-rw+ 1 root audio 116, 7 Aug 17 18:44 pcmC0D0c crw-rw+ 1 root audio 116, 6 Aug 17 18:44 pcmC0D0p crw-rw+ 1 root audio 116, 5 Aug 17 18:44 pcmC0D1p crw-rw+ 1 root audio 116, 4 Aug 17 18:44 pcmC0D3p crw-rw+ 1 root audio 116, 3 Aug 17 18:44 pcmC0D7p crw-rw+ 1 root audio 116, 2 Aug 17 18:44 pcmC0D8p crw--- 1 root root 116, 1 Aug 17 18:44 seq crw-rw+ 1 root audio 116, 33 Aug 17 18:44 timer I need /dev/snd/seq to look look the others. I can't find the udev rule or configuration that creates these nodes. Many thanks for any consideration. If there's no explicit rule, then it's automagic. But you can still additionally tell udev how to set the mode and owner. Here's an example, Google knows more (this stuff does seem to change quite a lot): http://www.reactivated.net/writing_udev_rules.html#ownership -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] crossdev --target armv7a-unknown-linux-gnueabi failed ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.08.2012 08:19, meino.cra...@gmx.de wrote: Hi, with crossdev I tried to build a toolchain for the armv7a-unknown-linux-gnueabi target. The build process failed due to a wrong format of an archive of patches. Is there a way for a local quick fix...or am I lost for a longer period of time... ;) ??? Best regards, mcc Log: _ * Package:cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90 * Repository: proaudio * Maintainer: toolch...@gentoo.org * USE: amd64 cxx elibc_glibc kernel_linux nls userland_GNU zlib * FEATURES: sandbox ESC[1mESC[37mcfg-update-1.8.2-r1ESC[0mESC[0m: Checksum index is up-to-date ... Unpacking source... Unpacking binutils-2.22.90.tar.bz2 to /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work Unpacking binutils-2.22.90-patches-1.1.tar.xz to /var/tmp/portage/cross-armv7a-unknown-linux-gnueabi/binutils-2.22.90/work unpack binutils-2.22.90-patches-1.1.tar.xz: file format not recognized. Ignoring. SNIP .xz is lzma2. If you install app-arch/xz-utils you should be fine. It's quite common today, by the way (you'll get gnome and kernel stuff compressed it - the kernelsources are about 10MB smaller than bz2) WKR Hinnerk -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQLhEXAAoJEJwwOFaNFkYcKtkH/ikLSF3eYYNZFVVD6GuyqHdR +EdA0R4x2uVapASSqJb6wEUYisEhRGsbNx5oEhbSBkhBQjz8RZuxpxqt7kK1pTTp nwDy72+GxBeWH0/t8+VwPNLhbC/uLxhyu+EIZfEp5eBHUdewxbLqfWYz3vC7SDSx +1d/5pKZlc9dpvLFBzeeKdgaEdMkqsV/gK/tu6S0zOyl/dzG+GplNP0Vqbx7+zOa fab/w/FcoO6bASJO7pzROvdSo1gZtCcFON7aKMMv1j+Uaq7mvR6KfSrSnMPyfqyC oi5VxsQvy/7FL0pdjDBqyWNNb05EcBASqEWo9eglTN9j8U66YCcEisFxqinzib0= =rfM9 -END PGP SIGNATURE-
Re: [gentoo-user] My PC died. What should I try?
Hello! On Fri, 17 Aug 2012 09:50:40 +0200 Alex Schuster wo...@wonkology.org wrote: Hi there! Two days ago, my PC suddenly died, after working fine for half a year. I used myrtcwake as usual to suspend to RAM, and it woke up in the morning. But after two minutes, the screen went blank and nothing, even SysRq, gave a reaction. I tried booting a couple of times again, and sometimes it did not even reach KDM. Now, I cannot even run Grub (from my USB stick) any more, I only see a GRUB string at the top right, then nothing happens. Booting with SystemRescueCD also freezes sometimes. If not, I can make it freeze after seconds by running 'memtester'. Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. Running memtester after booting from SystemrescueCD again makes the thing freeze in seconds. It once also froze while being in the BIOs setup. If the system behaves in such an unpredictable way (freezing at a random point), I usually check the following things: - RAM; - bloated capacitors on the Motherboard; - bloated or dried capacitors in the power supply unit; If your PC is only half a year old, it is unlikely that the capacitors dried. But they could easily bloat, especially if they were of bad quality or situated near some hot surface like heat sinks. Testing the power supply needs not only visual analysis. It would be good to attach the oscilloscope to the output and see the voltage level. It should not have large peaks (voltage jumps). But this is usually true for the old units with dried capacitors, as I said. If I were you, I'd tried to temporarily replace the memory with a 100% working module, and if it does not help - replace the power supply unit (if you do not have the necessary equipment to test it thoroughly). And one more simple test: turn on the PC, enter the BIOS setup utility and keep it running in this state. If it runs ok for some time (like a couple of hours), I'd say the problem is in RAM. Regards, Vladimir - v...@ukr.net
Re: [gentoo-user] My PC died. What should I try?
meino.cra...@gmx.de writes: ...shot in the dark: Remove as much as possible of the cards, addons, connections etc from the PC ... make in as much bare bone as possible. Done already. Check All coolers (the little ones also) for dust. Remove all dust even if it is not completly covered with it. They are clean. Dont forget the internals of the power supply. Detach all cables. Remove the power supply. Go outside ;) and blow the dust inside away. I did not remove it yet... but if it's a temperature problem, it should not happen right after 30 seconds, when Grub already fails. The voltages reported in the BIOS are okay, but I don't know it this information is accurate and reliable. Put the power supply back into the PC again an attach the cables. If I only could find a spare one... I have it, but I don't know where. Remove all RAM, carefully clean the contacts, insert as less RAM as possible. Did that, using only 4 of 16 GB, and I switched the modules. Remove even the HD if it is possible to get into the BIOS without any HD attached. I also did that, only the CD-ROM is attached. Remove the BIOS battery, wait at least a day and insert it again. That's worth a try. My old PC had a jumper which I could short circuit to instantly drain it, not sure if this was normal. Start the PC and go directly into the BIOS. Check the date/time. If it shows the current date/time, the battery wasn't removed long enough. Check the battery voltage. Reinsert the battery. If your board has a BIOS reset: Reset the BIOS. Then: In the BIOS enter a page which does something (reports continously temperatures for example). If this is possible, let the PC run for a while that BIOS page and see, whether it hangs again or not. Okay, I will do this. If all went fine, add ONE component and try it again. Add the HD at last to sort out hardware from software bugs... Nah, I cannot even boot from my USB stick any more. I don't have a boot partition on my hard drive, so it is not involved there. May be one of the components and not the CPU or motherboard causes the problem and you will be able to identify it by this procedure... I hope it's the power supply, this would mean the least effort. I'd simply buy a new one, and I would not have to think about what board or which CPU I would like to get. HTH! GOOD LUCK! Thanks! I can need it. Wonko
Re: [gentoo-user] /dev/snd/seq access mode and permission
Am Fri, 17 Aug 2012 01:54:34 -0700 schrieb Cinder cin...@linuxwaves.com: Hi, how do I make changes to permissions and access mode of device nodes persistent? At the moment I have to chown and chmod the /dev/snd/seq node every boot to make it accessible to my user. the other nodes are fine. Here's the output of ls -l /dev/snd/ total 0 drwxr-xr-x 2 root root 60 Aug 17 18:44 by-path crw-rw+ 1 root audio 116, 12 Aug 17 18:44 controlC0 crw-rw+ 1 root audio 116, 11 Aug 17 18:44 hwC0D0 crw-rw+ 1 root audio 116, 10 Aug 17 18:44 hwC0D3 crw-rw+ 1 root audio 116, 9 Aug 17 18:44 hwC0D4 crw-rw+ 1 root audio 116, 8 Aug 17 18:44 hwC0D5 crw-rw+ 1 root audio 116, 7 Aug 17 18:44 pcmC0D0c crw-rw+ 1 root audio 116, 6 Aug 17 18:44 pcmC0D0p crw-rw+ 1 root audio 116, 5 Aug 17 18:44 pcmC0D1p crw-rw+ 1 root audio 116, 4 Aug 17 18:44 pcmC0D3p crw-rw+ 1 root audio 116, 3 Aug 17 18:44 pcmC0D7p crw-rw+ 1 root audio 116, 2 Aug 17 18:44 pcmC0D8p crw--- 1 root root 116, 1 Aug 17 18:44 seq crw-rw+ 1 root audio 116, 33 Aug 17 18:44 timer I need /dev/snd/seq to look look the others. I can't find the udev rule or configuration that creates these nodes. Many thanks for any consideration. I have a hack for the same issue in my /etc/local.d/. A comment I put there says this: # this is caused by using devtmpfs, which creates nodes with root:root and 600; # I believe this is fixed by udev upstream So devtmpfs creates the device node before udev runs, but udev does not correct the access permissions, which is however fixed by udev upstream (perhaps already in ~arch?). Sadly I do not remember where I read this, but google should be of help there. HTH -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] A patch about fbreader for gentoo amd64
On Friday 17 Aug 2012 07:57:49 Kermit wrote: Hello all, I'm trying to emerge app-text/fbreader, but I found there's a bug that not solved about glib.h not fount. Somebody gave a solution about it, but I don't like to modify the ebuild files.Then I get the source form /usr/portage/distfiles/fbreader-sources-0.12.10.tgz, and make it by myself. I found that we just need to fix some config in the source, and then makemake install it OK. I made a patch for it by git diff. I don't know how to make a fully patch for Gentoo, so I and send it here, hope it useful for the vindicators to fix the bug. Thanks B.R Kermit Hi Kermit and welcome to the mailing list. For the devs to consider your patch you will need to submit it to the BGO: https://bugs.gentoo.org/ There's already a bug opened here with some submissions attached to it: https://bugs.gentoo.org/show_bug.cgi?id=417043 HTH. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] My PC died. What should I try?q
Randolph Maaßen writes: Aaa aAaa aaa a Am 17.08.2012 10:31 schrieb meino.cra...@gmx.de mailto:meino.cra...@gmx.de: Hi Alex, ...shot in the dark: Remove as much as possible of the cards,aadwqqqaaa www wpa www a weißes www aa Array www www www a aaa aa aadwqqqaaa aaa w aadwqqqaaa www aa aaa a aaa www Awaa aaa aa quattro Aquarellw aaa aa aa Webauftritt aaa a aaa aA aaa aAaAaAaq aaawa addons, connections etcwo from the PC ... make ian as much bare bone aaa stwww wwwaaa www qaaa wwwas a. www www waslittle ones also) for dust. Removeaa wwwaa all dust even if it is not completly covered with ait. Woow! What is going on here? Wonko
Re: [gentoo-user] My PC died. What should I try?q
2012/8/17 Alex Schuster wo...@wonkology.org Randolph Maaßen writes: Aaa aAaa aaa a Am 17.08.2012 10:31 schrieb meino.cra...@gmx.de mailto:meino.cra...@gmx.de: Hi Alex, ...shot in the dark: Remove as much as possible of the cards,aadwqqqaaa www wpa www a weißes www aa Array www www www a aaa aa aadwqqqaaa aaa w aadwqqqaaa www aa aaa a aaa www Awaa aaa aa quattro Aquarellw aaa aa aa Webauftritt aaa a aaa aA aaa aAaAaAaq aaawa addons, connections etcwo from the PC ... make ian as much bare bone aaa stwww wwwaaa www qaaa wwwas a. www www waslittle ones also) for dust. Removeaa wwwaa all dust even if it is not completly covered with ait. Woow! What is going on here? Wonko Damn!! Sorry for this bad post, somehow my phone unlocked in my pocket. -- Mit freundlichen Grüßen / Best regards Randolph Maaßen
Re: [gentoo-user] My PC died. What should I try?
Alex Schuster wrote: Hi there! Two days ago, my PC suddenly died, after working fine for half a year. I used myrtcwake as usual to suspend to RAM, and it woke up in the morning. But after two minutes, the screen went blank and nothing, even SysRq, gave a reaction. I tried booting a couple of times again, and sometimes it did not even reach KDM. Now, I cannot even run Grub (from my USB stick) any more, I only see a GRUB string at the top right, then nothing happens. Booting with SystemRescueCD also freezes sometimes. If not, I can make it freeze after seconds by running 'memtester'. Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. Running memtester after booting from SystemrescueCD again makes the thing freeze in seconds. It once also froze while being in the BIOs setup. What could be the problem? CPU, board, or even the PSU? I do not think it has to do with bad memory. I removed most of the other stuff (hard drives, PCI cards). I have no similar hardware so I cannot simply exchange things, the question is what to buy and try. How would you proceed? The fan is still working, the cooler does not become hot, and in the BIOS there are not high temperatures begin reported. But one thing was strange: I updated Calligra from 2.4 to 2.5 (I think), and it took ages, at least 8 hours. I thought there may b something strange with the build process of this new version, forcing MAKEOPTS=-j1 and such, but still this is very long. But when working with it, I did not notice anything strange like sluggish reactions, and videos played fine. But I did not use it as much as I normally do, and maybe even when overheated and throttled down it would have been fast enough for me to not notice this. I watch the syslog normally, but maybe I just did not look closely that day, I was busy doing other stuff. CPUs don't just die, do they? Even when overheating, I think these days throttle down, so no permanent harm should be done? So maybe it's the board? It looks okay, no bent or leaking capacitors. This is really annoying. Of course most of my passwords are in my KDE wallet I cannot access. There's also Wiki, CVS and Git repositories, not needed every day, but still important. And the timinig is very bad, I just started my new job the day the problem happened, and I do not have much time for this now. Before, I was working at home, so I would have had all day to diagnose and try things. It's an AMD FX-4100 Quad-Core CPU, and an ASRock 880GMH/U3S3 board. Wonko Just my two cents here. Problems like this are usually the power supply. Could it be the mobo, yes it could but the power supply is more likely, usually cheaper to replace and easier to. I had a friends puter that was acting weird, random reboots and such, it was the power supply. A bad power supply can cause all sorts of weird problems. If you can, unplug everything including the CD/DVD drive. No hard drives either. Just play with the BIOS. Basically, don't try to boot anything, just look at the BIOS itself. If it acts weird, start with the power supply. If you have to, go to a local place and pick up a cheap power supply. Put it in just long enough to see if that is the problem. If it works, then order you a real good power supply. Just keep the cheapy for testing purposes. If the cheapy power supply presents the same problem, then it could be the mobo. Random problems are hard to fix sometimes. You just have to swap things until you find the bad part. I would put the odds at 80% that it is the power supply tho. While at it, do you know what brand and the wattage of your power supply? It could be that someone on here as experience with that particular brand or even that exact model. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
[gentoo-user] /usr/tmp - /var/tmp a problem with new udev?
I realize that new udev without dracut wants /usr part of root filesystem. The last few gentoo installations I have done all had /usr/tmp symlinked to /var/tmp and I don't believe I did this symlink manually. Will this be a problem with new udev and no dracut or are the programs that must run early trained not to use /usr/tmp? thanks, allan
Re: [gentoo-user] My PC died. What should I try?q
Randolph Maaßen wrote: 2012/8/17 Alex Schuster wo...@wonkology.org mailto:wo...@wonkology.org Randolph Maaßen writes: Aaa aAaa aaa a Am 17.08.2012 10:31 schrieb meino.cra...@gmx.de mailto:meino.cra...@gmx.de mailto:meino.cra...@gmx.de mailto:meino.cra...@gmx.de: Hi Alex, ...shot in the dark: Remove as much as possible of the cards,aadwqqqaaa www wpa www a weißes www aa Array www www www a aaa aa aadwqqqaaa aaa w aadwqqqaaa www aa aaa a aaa www Awaa aaa aa quattro Aquarellw aaa aa aa Webauftritt aaa a aaa aA aaa aAaAaAaq aaawa addons, connections etcwo from the PC ... make ian as much bare bone aaa stwww wwwaaa www qaaa wwwas a. www www waslittle ones also) for dust. Removeaa wwwaa all dust even if it is not completly covered with ait. Woow! What is going on here? Wonko Damn!! Sorry for this bad post, somehow my phone unlocked in my pocket. -- Mit freundlichen Grüßen / Best regards Randolph Maaßen Is your butt sending emails? I thought they had a different way of communicating. LOL Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Re: [gentoo-user] common flags for 2 cpu?
Am 17.08.2012 10:58, schrieb Jorge Almeida: I'm in need of some expert advise about CFLAGS. I'm going to install Gentoo in two systems, an Atom 330 and a P4 prescott. Since compiling lots of stuff in an Atom is less than joyful, I intend to do almost all compilation on the prescott and produce binary packages to use on the Atom. So, something like CFLAGS=-march=native ... is out. I know I could set CFLAGS=-march=i686 -O2 -pipe -fomit-frame-pointer, but I would like to extract a bit more juice from the hw, while still keeping stable systems. So, I thought of setting CFLAGS for both systems as -march=i686, plus the flags that are pulled by -march=native in both systems, plus some other flags: [...] This is what is pulled by -march=native, using gcc -march=native -E -v - /dev/null 21 | grep cc1 Prescott: -march=prescott -mno-cx16 -mno-sahf -mno-movbe -mno-aes -mno-pclmul -mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -mno-sse4.2 -mno-sse4.1 -mno-lzcnt -mno-rdrnd -mno-f16c -mno-fsgsbase --param l1-cache-size=16 --param l1-cache-line-size=64 --param l2-cache-size=1024 -mtune=prescott Atom: -march=atom -mcx16 -msahf -mmovbe -mno-aes -mno-pclmul -mno-popcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -mno-sse4.2 -mno-sse4.1 -mno-lzcnt -mno-rdrnd -mno-f16c -mno-fsgsbase --param l1-cache-size=24 --param l1-cache-line-size=64 --param l2-cache-size=512 -mtune=atom [...] Some questions: 1) Is this strategy right? If so, any other flags to add? (or any flags to remove from the list?) 2) The --param flags are the ones of the computer that will do the compiling. I'm guessing the produced binaries are compatible with cpu with different --param flags. Is this right? TIA Jorge Almeida 1) Yes. But as you can see, -march=prescott is basically a subset of atom. In fact, before there was a -march=atom option, prescott was the best flag for atoms. I think you can avoid some hassle by simply enabling -march=prescott --param l1-cache-line-size=64 --param l2-cache-size=512. 2) Yes, the param flags do not affect compatibility. Using the lower value will probably be better but this is just an educated guess. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] My PC died. What should I try?q
Randolph Maaßen wrote: Sorry for this bad post, somehow my phone unlocked in my pocket. I assumed your cat walking over the keyboard ;) -Matt
Re: [gentoo-user] /dev/snd/seq access mode and permission
On Fri, Aug 17, 2012 at 3:54 AM, Cinder cin...@linuxwaves.com wrote: Hi, how do I make changes to permissions and access mode of device nodes persistent? At the moment I have to chown and chmod the /dev/snd/seq node every boot to make it accessible to my user. the other nodes are fine. Here's the output of ls -l /dev/snd/ total 0 drwxr-xr-x 2 root root 60 Aug 17 18:44 by-path crw-rw+ 1 root audio 116, 12 Aug 17 18:44 controlC0 crw-rw+ 1 root audio 116, 11 Aug 17 18:44 hwC0D0 crw-rw+ 1 root audio 116, 10 Aug 17 18:44 hwC0D3 crw-rw+ 1 root audio 116, 9 Aug 17 18:44 hwC0D4 crw-rw+ 1 root audio 116, 8 Aug 17 18:44 hwC0D5 crw-rw+ 1 root audio 116, 7 Aug 17 18:44 pcmC0D0c crw-rw+ 1 root audio 116, 6 Aug 17 18:44 pcmC0D0p crw-rw+ 1 root audio 116, 5 Aug 17 18:44 pcmC0D1p crw-rw+ 1 root audio 116, 4 Aug 17 18:44 pcmC0D3p crw-rw+ 1 root audio 116, 3 Aug 17 18:44 pcmC0D7p crw-rw+ 1 root audio 116, 2 Aug 17 18:44 pcmC0D8p crw--- 1 root root 116, 1 Aug 17 18:44 seq crw-rw+ 1 root audio 116, 33 Aug 17 18:44 timer I need /dev/snd/seq to look look the others. I can't find the udev rule or configuration that creates these nodes. Many thanks for any consideration. Do you have files under /etc/udev/rules.d/? If so, make a backup of them, delete them, and try again. udev should automagically set the permissions. Also, check for orphan files (files which doesn't belong to any package) under /lib/udev/rules.d/ Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] My PC died. What should I try?q
Randolph Maaßen writes: 2012/8/17 Alex Schuster wo...@wonkology.org mailto:wo...@wonkology.org Woow! What is going on here? Damn!! Sorry for this bad post, somehow my phone unlocked in my pocket. I'm happy for every reply, and this was a very special one :) -- Mit freundlichen Grüßen / Best regards Randolph Maaßen The signature seems to be separated correctly by -- instead of --, yet my Thunderbird does not recognize it as such. Maybe it has a problem with quoted-printable format? Wonko
Re: [gentoo-user] My PC died. What should I try?
v...@ukr.net writes: If the system behaves in such an unpredictable way (freezing at a random point), I usually check the following things: - RAM; - bloated capacitors on the Motherboard; - bloated or dried capacitors in the power supply unit; If your PC is only half a year old, it is unlikely that the capacitors dried. But they could easily bloat, especially if they were of bad quality or situated near some hot surface like heat sinks. Testing the power supply needs not only visual analysis. It would be good to attach the oscilloscope to the output and see the voltage level. It should not have large peaks (voltage jumps). But this is usually true for the old units with dried capacitors, as I said. The power supply is older, I re-used it from the PC I had before this one. I hope it causes the trouble, and will try another one this evening. Thanks for this information, this strengthens my confidence that I do not have to buy a new board or CPU. Now I am driving home with a bag of three PSUs I had lent to a friend (and already forgotten). If I were you, I'd tried to temporarily replace the memory with a 100% working module, and if it does not help - replace the power supply unit (if you do not have the necessary equipment to test it thoroughly). I wish I had :) The RAM is okay, I think, I cannot imagine different memory modules to suddenly go bad all at once. And memtest86 found one error only after an hour, while the crashes happen after a few minutes already. And one more simple test: turn on the PC, enter the BIOS setup utility and keep it running in this state. If it runs ok for some time (like a couple of hours), I'd say the problem is in RAM. It once crashed after ten minutes. That was not reproducable, but I did not try that often. Wonko
Re: [gentoo-user] My PC died. What should I try?
On Fri, Aug 17, 2012 at 12:50 AM, Alex Schuster wo...@wonkology.org wrote: Hi there! Two days ago, my PC suddenly died, after working fine for half a year. I used myrtcwake as usual to suspend to RAM, and it woke up in the morning. But after two minutes, the screen went blank and nothing, even SysRq, gave a reaction. I tried booting a couple of times again, and sometimes it did not even reach KDM. Now, I cannot even run Grub (from my USB stick) any more, I only see a GRUB string at the top right, then nothing happens. Booting with SystemRescueCD also freezes sometimes. If not, I can make it freeze after seconds by running 'memtester'. Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. Running memtester after booting from SystemrescueCD again makes the thing freeze in seconds. It once also froze while being in the BIOs setup. What could be the problem? CPU, board, or even the PSU? I do not think it has to do with bad memory. I removed most of the other stuff (hard drives, PCI cards). I have no similar hardware so I cannot simply exchange things, the question is what to buy and try. How would you proceed? The fan is still working, the cooler does not become hot, and in the BIOS there are not high temperatures begin reported. But one thing was strange: I updated Calligra from 2.4 to 2.5 (I think), and it took ages, at least 8 hours. I thought there may b something strange with the build process of this new version, forcing MAKEOPTS=-j1 and such, but still this is very long. But when working with it, I did not notice anything strange like sluggish reactions, and videos played fine. But I did not use it as much as I normally do, and maybe even when overheated and throttled down it would have been fast enough for me to not notice this. I watch the syslog normally, but maybe I just did not look closely that day, I was busy doing other stuff. CPUs don't just die, do they? Even when overheating, I think these days throttle down, so no permanent harm should be done? So maybe it's the board? It looks okay, no bent or leaking capacitors. This is really annoying. Of course most of my passwords are in my KDE wallet I cannot access. There's also Wiki, CVS and Git repositories, not needed every day, but still important. And the timinig is very bad, I just started my new job the day the problem happened, and I do not have much time for this now. Before, I was working at home, so I would have had all day to diagnose and try things. It's an AMD FX-4100 Quad-Core CPU, and an ASRock 880GMH/U3S3 board. Wonko Hi Alex, Sorry for the problems. I've read most of the responses so it seems you're getting good info. A few things: 1) You asked CPUs don't just die, do they?. The answer is 'yes, they do.' It can happen at any time: http://en.wikipedia.org/wiki/Bathtub_curve 2) If I understand your post, along with the other discussions, it seems that you can remove all cards and all memory except 1 DIMM and boot the machine to BIOS. Is that correct? If so then your CPU isn't completely dead. 3) As you are seeing some memory problems it might be that memory died. (see bathtub curve again - it applies to everything.) However it seems very unlikely that all memory died at the same time. More likely is the the chipset. If you change DIMMs but keep plugging it into the same memory channel then it might be that channel in the chipset that's having trouble. If it's your chipset, you're sunk. Get a new MB. As others have suggested the PSU is a potential common problem. With everything else out of the box, memory swapped but the same problem occurring, and the ability to at least get into BIOS, it's likely either the PSU or the MB. Good luck, Mark
Re: [gentoo-user] common flags for 2 cpu?
On Fri, Aug 17, 2012 at 2:53 PM, Florian Philipp li...@binarywings.net wrote: Am 17.08.2012 10:58, schrieb Jorge Almeida: 1) Is this strategy right? If so, any other flags to add? (or any flags to remove from the list?) 2) The --param flags are the ones of the computer that will do the compiling. I'm guessing the produced binaries are compatible with cpu with different --param flags. Is this right? TIA Jorge Almeida 1) Yes. But as you can see, -march=prescott is basically a subset of atom. In fact, before there was a -march=atom option, prescott was the best flag for atoms. I think you can avoid some hassle by simply enabling -march=prescott --param l1-cache-line-size=64 --param l2-cache-size=512. 2) Yes, the param flags do not affect compatibility. Using the lower value will probably be better but this is just an educated guess. What about: CFLAGS=-O2 -pipe -fomit-frame-pointer -march=prescott -mtune=atom --param l1-cache-size=16 --param l1-cache-line-size=64 --param l2-cache-size=1024 If prescott were exactly a subset of atom, this would yield the best of both worlds. Can it still be safe? I read in http://forums.gentoo.org/viewtopic-t-895104.html : atom Intel Atom CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. Does this mean that these flags are pulled by -mtune=atom, or do we need to ask for them explicitly? The WiKi shows how to find which flags are pulled by -march=native, but not the other cases. Thanks Jorge Almeida
Re: [gentoo-user] My PC died. What should I try?
Volker Armin Hemmann writes: sounds like a power problem. Either psu is gone bad (get a new one) Well, I got three old ones instead :) or your mainboard's power circuitry gone bad (if replacement of psu does not help, get a new one). It did not help :( Too bad, I probably need a new mainboard. And I cannot get one before monday evening, I have to go to a wedding tomorrow (not mine) and I doubt I will have time to find a hardware store there. But first thing first: disconnect your hdds! No reason to risk them. I did that soon. I already had trouble with one two weeks ago, it had bad blocks on the home partition. The replacement drive also had bad blocks, I had to get yet another one. It's a good thing to have recent backups :) And there, it just crashed while in the BIOS setup. Wonko
Re: [gentoo-user] My PC died. What should I try?
On Fri, Aug 17, 2012 at 1:16 PM, Alex Schuster wo...@wonkology.org wrote: And there, it just crashed while in the BIOS setup. If you are using a video card (instead of built-in/on-board video) I would try a different video card, if you have an old or spare one. I have had lots of video cards die from overheating and power spikes. I only had one motherboard ever die, a computer I gave to my father died after a few months... it was ASRock brand but I'm sure that is a coincidence. :) It had blown/cracked capacitors all over the motherboard. It did not die completely at once. It would kind of work, but started to crash randomly and became worse and worse until finally it wouldn't boot at all. I replaced the MB, but kept the same CPU, RAM everything else, and it has been working ever since. That was after we bought a new power supply that didn't make any difference.
Re: [gentoo-user] /dev/snd/seq access mode and permission
Am Fri, 17 Aug 2012 11:40:47 +0200 schrieb Marc Joliet mar...@gmx.de: Am Fri, 17 Aug 2012 01:54:34 -0700 schrieb Cinder cin...@linuxwaves.com: Hi, how do I make changes to permissions and access mode of device nodes persistent? At the moment I have to chown and chmod the /dev/snd/seq node every boot to make it accessible to my user. the other nodes are fine. Here's the output of ls -l /dev/snd/ total 0 drwxr-xr-x 2 root root 60 Aug 17 18:44 by-path crw-rw+ 1 root audio 116, 12 Aug 17 18:44 controlC0 crw-rw+ 1 root audio 116, 11 Aug 17 18:44 hwC0D0 crw-rw+ 1 root audio 116, 10 Aug 17 18:44 hwC0D3 crw-rw+ 1 root audio 116, 9 Aug 17 18:44 hwC0D4 crw-rw+ 1 root audio 116, 8 Aug 17 18:44 hwC0D5 crw-rw+ 1 root audio 116, 7 Aug 17 18:44 pcmC0D0c crw-rw+ 1 root audio 116, 6 Aug 17 18:44 pcmC0D0p crw-rw+ 1 root audio 116, 5 Aug 17 18:44 pcmC0D1p crw-rw+ 1 root audio 116, 4 Aug 17 18:44 pcmC0D3p crw-rw+ 1 root audio 116, 3 Aug 17 18:44 pcmC0D7p crw-rw+ 1 root audio 116, 2 Aug 17 18:44 pcmC0D8p crw--- 1 root root 116, 1 Aug 17 18:44 seq crw-rw+ 1 root audio 116, 33 Aug 17 18:44 timer I need /dev/snd/seq to look look the others. I can't find the udev rule or configuration that creates these nodes. Many thanks for any consideration. I have a hack for the same issue in my /etc/local.d/. A comment I put there says this: # this is caused by using devtmpfs, which creates nodes with root:root and 600; # I believe this is fixed by udev upstream So devtmpfs creates the device node before udev runs, but udev does not correct the access permissions, which is however fixed by udev upstream (perhaps already in ~arch?). Sadly I do not remember where I read this, but google should be of help there. Ah, yes, I did a quick search on b.g.o and found this: https://bugs.gentoo.org/show_bug.cgi?id=406871 So my comment is wrong, it doesn't have anything to do with devtmpfs, but udev upstream did fix it :) . HTH -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] My PC died. What should I try?
Paul Hartman writes: If you are using a video card (instead of built-in/on-board video) I would try a different video card, if you have an old or spare one. I have had lots of video cards die from overheating and power spikes. Sorry, I did not mention that I do not have a video card, it's onboard video. I do not need great video power, and I wanted to have a quiet PC that also saves power. I only had one motherboard ever die, a computer I gave to my father died after a few months... it was ASRock brand but I'm sure that is a coincidence. :) It had blown/cracked capacitors all over the motherboard. It did not die completely at once. It would kind of work, but started to crash randomly and became worse and worse until finally it wouldn't boot at all. I replaced the MB, but kept the same CPU, RAM everything else, and it has been working ever since. That was after we bought a new power supply that didn't make any difference. I'd also say this is unusual. I had a board die, but that was my own error :) Well, all I can do now is to get a new board and see if things will be okay then. Thanks for all your responses! I know this is not really related to Gentoo, but that's what I love this list for, people are very helpful and competent here. Wonko
[gentoo-user] Re: My PC died. What should I try?
On 17/08/12 10:50, Alex Schuster wrote: Booting good old memtest86 ran for an hour and only found one error, then I aborted, removed three of my four memory modules (4GB each), and tried different ones in the first bank. Memtest86 again did not find much errors, but froze once. It finds errors in *all* modules?
Re: [gentoo-user] common flags for 2 cpu?
Am 17.08.2012 19:57, schrieb Jorge Almeida: On Fri, Aug 17, 2012 at 2:53 PM, Florian Philipp li...@binarywings.net wrote: Am 17.08.2012 10:58, schrieb Jorge Almeida: 1) Is this strategy right? If so, any other flags to add? (or any flags to remove from the list?) 2) The --param flags are the ones of the computer that will do the compiling. I'm guessing the produced binaries are compatible with cpu with different --param flags. Is this right? TIA Jorge Almeida 1) Yes. But as you can see, -march=prescott is basically a subset of atom. In fact, before there was a -march=atom option, prescott was the best flag for atoms. I think you can avoid some hassle by simply enabling -march=prescott --param l1-cache-line-size=64 --param l2-cache-size=512. 2) Yes, the param flags do not affect compatibility. Using the lower value will probably be better but this is just an educated guess. What about: CFLAGS=-O2 -pipe -fomit-frame-pointer -march=prescott -mtune=atom --param l1-cache-size=16 --param l1-cache-line-size=64 --param l2-cache-size=1024 If prescott were exactly a subset of atom, this would yield the best of both worlds. Can it still be safe? I read in http://forums.gentoo.org/viewtopic-t-895104.html : atom Intel Atom CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. Does this mean that these flags are pulled by -mtune=atom, or do we need to ask for them explicitly? The WiKi shows how to find which flags are pulled by -march=native, but not the other cases. Thanks Jorge Almeida Oh, sorry, I didn't think of the second generation atoms. I guess your newer atom is a bit more different from prescott than the one I talked about. Anyway, using -march=prescott is still viable. It just means you lose a bit more in terms of usable SSE extensions on your atom. Your CFLAGS look good to me. They won't pull in anything that your prescott cannot handle. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] common flags for 2 cpu?
On Fri, Aug 17, 2012 at 10:05 PM, Florian Philipp li...@binarywings.net wrote: Am 17.08.2012 19:57, schrieb Jorge Almeida: I read in http://forums.gentoo.org/viewtopic-t-895104.html : atom Intel Atom CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. Does this mean that these flags are pulled by -mtune=atom, or do we need to ask for them explicitly? The WiKi shows how to find which flags are pulled by -march=native, but not the other cases. Thanks Jorge Almeida Oh, sorry, I didn't think of the second generation atoms. I guess your newer atom is a bit more different from prescott than the one I talked about. Anyway, using -march=prescott is still viable. It just means you lose a bit more in terms of usable SSE extensions on your atom. Your CFLAGS look good to me. They won't pull in anything that your prescott cannot handle. Does -march=prescott not ensure that the prescott will work even if unsupported flags are added? Of, course such flags wouldn't be of use by the prescott, but the atom might be able to use them. Can you confirm this? Thanks, Jorge Almeida
Re: [gentoo-user] common flags for 2 cpu?
Am Freitag, 17. August 2012, 22:34:45 schrieb Jorge Almeida: Does -march=prescott not ensure that the prescott will work even if unsupported flags are added? no every flag on its own. If you set a flag it is your responsibility to check that they actually work. -- #163933
Re: [gentoo-user] My PC died. What should I try?
Mouse-to-mouse resuscitation? Unless it's headless. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
[gentoo-user] How can I bring back Konqueror as my man page viewer?
In KDE, I'm very used to simply type man:foo and have the man page of foo pop up immediately in Konqueror without having to open a terminal or anything. However, since I installed Chromium and making it my default browser, now man: brings up Chromium instead. That doesn't work; instead of displaying the man page, it downloads the *.bz2 from the local file system :-/ How can I set Konqueror to be the program that handles KDE's man: command?
Re: [gentoo-user] How can I bring back Konqueror as my man page viewer?
On Sat 18 Aug 2012 06:21:55 AM IST, Nikos Chantziaras wrote: In KDE, I'm very used to simply type man:foo and have the man page of foo pop up immediately in Konqueror without having to open a terminal or anything. However, since I installed Chromium and making it my default browser, now man: brings up Chromium instead. That doesn't work; instead of displaying the man page, it downloads the *.bz2 from the local file system :-/ How can I set Konqueror to be the program that handles KDE's man: command? Umm, my default browser is Firefox, but when I open Konqueror and type man:ls I get to see the man page. But if I launch using Alt+F2, it opens Firefox. I think this needs some xdg tweaking, using xdg-mime. I don't know the type of URL for man:, else could have posted the command. -- Nilesh Govindrajan http://nileshgr.com
