[gentoo-user] ssd: using TRIM
Greets, gentoo-users, yesterday at last I put my Intel SSD X25-M G2 into my Thinkpad. Works fine so far ... I use the kernel 2.6.33-tuxonice on this machine, which should support TRIM. I also use ext4 for / which also should support TRIM if I mount it with the option "discard". Is this enough to enable TRIM ? Or do I have to do anything else? Thanks for any info, Stefan
[gentoo-user] [OT] shell ouput which file descriptor
This is not a question about cvs... its only used for example. I'm puzzled about a change in what I see when I run cvs -n update 2> /dev/null I've apparently lost the ability to remove stder from output. I used that command to trim out file descriptor 2 which used to leave a list of any changed files in the repo on the console, for a very long time. Suddenly there is no difference with: cvs -n update 2> /dev/null cvs -n update The stuff on stderr still shows in the ouput either way. Further; cvs -n update 2>er (redirect stder to ./er) Doesn't put anything in ./er However cvs -n update 1>out (redirect stdout to ./out) Does catch the output I'm after and leave out stderr. (as one would expect) So, again, apparently I've lost the ability to trim out stderr with a redirect to /dev/null (cvs -n update 2> /dev/null) ---- ---=--- - The only thing I've been tinkering with is evaluating the /etc/DIR_COLORS file. I switched from evaluating a custom version to evaluating the default version. That's when I first noticed the file descriptor anomaly but not sure if was going before since I didn't notice it before. So changed back to the original dir_colors... but the descriptor problem is still here. I've established a fresh login by ssh my...@localhost Still I see stderr in the console even when redirected with 2> /dev/null Anyone have an idea what I've done here, or what might explain what I'm seeing?
Re: [gentoo-user] X crashes, how to troubleshoot?
This is a late reply and you might have already solved the issue, however, I was running into this problem as well, and it was resolved for my by backing my X packages back down to stable as I was running a stable kernel. Another fix was to upgrade to an unstable X. I was informed that there have bee problems mixing unstable drivers and stable kernel. Hope this helps On Sat, Apr 3, 2010 at 12:42 PM, Willie Wong wrote: > Recently X has spontaneously crashed on me several times. Each time it > is triggered by opening up a new webpage in a new tab in Firefox. The > URL of the webpages are random, so I don't think it has to do with any > particular site (and those url often open fine on subsequent visits). > > The message that I end up having from X is: > > Backtrace: > 0: X (xorg_backtrace+0x3b) [0x80ab23b] > 1: X (0x8048000+0x5e1d5) [0x80a61d5] > 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb782240c] > 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb7299000+0x32cae) > [0xb72cbcae] > 4: X (0x8048000+0xc6550) [0x810e550] > 5: X (0x8048000+0x20745) [0x8068745] > 6: X (0x8048000+0x22df7) [0x806adf7] > 7: X (0x8048000+0x1d285) [0x8065285] > 8: /lib/libc.so.6 (__libc_start_main+0xe5) [0xb7397bb5] > 9: X (0x8048000+0x1ce51) [0x8064e51] > Bus error at address 0xb61f4000 > > Fatal server error: > Caught signal 7 (Bus error). Server aborting > > which is not too much to go on. As you can see, I use the intel > drivers. The behaviour may have started after my March 19 upgrades: > > Fri Mar 19 11:08:54 2010 >>> x11-libs/libXau-1.0.5 > Fri Mar 19 11:09:41 2010 >>> x11-libs/libXdmcp-1.0.3 > Fri Mar 19 11:10:06 2010 >>> x11-misc/util-macros-1.6.1 > Fri Mar 19 11:20:13 2010 >>> x11-libs/libX11-1.3.3 > Fri Mar 19 11:21:17 2010 >>> x11-libs/libdrm-2.4.19 > Fri Mar 19 11:22:44 2010 >>> x11-libs/libXt-1.0.8 > Fri Mar 19 11:23:26 2010 >>> x11-libs/libXScrnSaver-1.2.0 > Fri Mar 19 11:41:42 2010 >>> x11-libs/openmotif-2.3.3 > Fri Mar 19 11:42:17 2010 >>> x11-apps/xinput-1.5.1 > Fri Mar 19 12:30:55 2010 >>> x11-apps/xinit-1.2.1 > Fri Mar 19 12:54:23 2010 >>> x11-base/xorg-server-1.7.6 > Fri Mar 19 12:55:55 2010 >>> x11-drivers/xf86-video-intel-2.10.0-r1 > > For what it's worth, here's the lspci output: > > Gee-Mi-Ni elog # lspci -vs 00:02.* > 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express > Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Giga-byte Technology Device 1999 > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at 5828 (32-bit, non-prefetchable) [size=512K] > I/O ports at 60c0 [size=8] > Memory at 4000 (32-bit, prefetchable) [size=256M] > Memory at 5830 (32-bit, non-prefetchable) [size=256K] > Expansion ROM at [disabled] > Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- > Capabilities: [d0] Power Management version 2 > Kernel driver in use: i915 > > 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, > 943/940GML Express Integrated Graphics Controller (rev 03) > Subsystem: Giga-byte Technology Device 1999 > Flags: bus master, fast devsel, latency 0 > Memory at 5820 (32-bit, non-prefetchable) [size=512K] > Capabilities: [d0] Power Management version 2 > > > Any suggestions on what I can do to figure out what the problem is? > > Thanks, > > W > -- > Willie W. Wong ww...@math.princeton.edu > Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire > et vice versa ~~~ I. Newton > >
Re: [gentoo-user] Gfx for Linux Gaming
On Thu, Apr 8, 2010 at 4:21 PM, Robert Bridge wrote: > nVidia at the moment is a bit of a risk, as there is a whole raft of > issues going on with nVidia hardware. If their drivers work, they will > likely give better performance and features than AMDs options, and so > long as the hardware holds up. Read up on nVidia bumps issue for more > information. > > However... AMD have an open-source strategy and an official > open-source driver stack. Their open-source drivers are good, and > getting better, but are not feature complete yet, nor really > competitive for performance in 3D games. I'm not aware of any major > issues surrounding AMD graphics, except the general complaints that > the FOSS drivers aren't yet good enough. > > YMMV, > RobbieAB > > Thanks for the pointer on the nvidia problem. I hadn't heard about that, and: 1) I've got a 2 year old out-of-warranty Compaq laptop that's having trouble booting. As best I can tell it's not the disk and it's not memory, so... 2) I just put a fanless 9500GT-based card in my wife's new machine Guess I'm right in the thick of it as testing for lead vs eutectic bumps is not something you can figure out with a piece of software... I used to work in the semiconductor industry. The thing I'd worry about is whether the company doing packaging for nvidia, and it's almost certainly not nvidia themselves, have used these same high-lead bumps that they sold nvidia. If they have then anyone's chips could potentially have these same problems. OK, so let's investigate AMD/ATI at bit more. Am I understanding Volker's response that I want to look at the 5000 Series from ATI? http://www.amd.com/us/products/desktop/graphics/ati-radeon-hd-5000/Pages/ati-radeon-hd-5000.aspx Looking at NewEgg I think all the 5850 & 5870's are just more expensive than I want to pay. There are some 5730's for around $240, but tax and shipping is going to drive that over $300 which is still pretty step for something I won't use much. As I won't game and sometimes do music (writing, recording, listening, etc.) much I would appreciate quiet (i.e. - fanless) everyday whereas gaming might happen just once in awhile. So far I haven't spotted any 5700 or 5800 that are fanless. I do see 5500 and 5600 devices: 5570 http://www.newegg.com/Product/Product.aspx?Item=N82E16814131349 5670 http://www.newegg.com/Product/Product.aspx?Item=N82E16814131348 Prices are acceptable on both of those, although I'm sure the performance is probably lacking a bit. I'll have to look around at relative benchmarks to understand anything about the performance metrics. Thanks, Mark
Re: [gentoo-user] iptables: how can I include multiple hosts/IPs in "-s" and "-d"?
Hi, you can define a rule like that: iptables -A FORWARD -s 192.168.235.43,192.168.235.46 -d 10.0.0.1,192.168.0.1 -j ACCEPT it will create 4 rules. be sure to activate Networking support->Networking options->Network packet filtering framework->Core Netfilter Configuration->iprange address range match support Now you can do something like iptables -A FORWARD -m iprange --src-range '10.0.0.1-10.0.0.44' -j ACCEPT hope it helps -Stefan On Mon, Apr 05, 2010 at 07:32:17PM +0200, Jarry wrote: > Hi > > I'd like to ask if there is some way to include multiple discrete > hosts/IP's in --source and --destination options of iptables. > > I'm trying to write firewall rules for my server, but it has > 12 IP's from different segments (and maybe it gets a few more > later), and the script grows up as I have to write nearly > identical rules with difference only in -s/-d IP's. > > What I'm looking for is a way to define some variable at the > beginning of my script, like MY_IP="IP1 IP2 IP3 IP4..." and > later to use is in rules (iptables -A INPUT -s $MY_IP...). > But I do not know how to use it. As far as I understand it, > --source/--destination accepts only single IP's or continuous > IP-segments... > > Jarry > > -- > ___ > This mailbox accepts e-mails only from selected mailing-lists! > Everything else is considered to be spam and therefore deleted. > pgp8CBCXDQtso.pgp Description: PGP signature
Re: [gentoo-user] X crashes, how to troubleshoot?
On Fri, Apr 9, 2010 at 10:57 PM, AJ Spagnoletti wrote: > This is a late reply and you might have already solved the issue, > however, I was running into this problem as well, and it was resolved > for my by backing my X packages back down to stable as I was running a > stable kernel. Another fix was to upgrade to an unstable X. I was > informed that there have bee problems mixing unstable drivers and > stable kernel. Hope this helps > > On Sat, Apr 3, 2010 at 12:42 PM, Willie Wong wrote: >> Recently X has spontaneously crashed on me several times. Each time it >> is triggered by opening up a new webpage in a new tab in Firefox. The >> URL of the webpages are random, so I don't think it has to do with any >> particular site (and those url often open fine on subsequent visits). >> >> The message that I end up having from X is: >> >> Backtrace: >> 0: X (xorg_backtrace+0x3b) [0x80ab23b] >> 1: X (0x8048000+0x5e1d5) [0x80a61d5] >> 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb782240c] >> 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb7299000+0x32cae) >> [0xb72cbcae] >> 4: X (0x8048000+0xc6550) [0x810e550] >> 5: X (0x8048000+0x20745) [0x8068745] >> 6: X (0x8048000+0x22df7) [0x806adf7] >> 7: X (0x8048000+0x1d285) [0x8065285] >> 8: /lib/libc.so.6 (__libc_start_main+0xe5) [0xb7397bb5] >> 9: X (0x8048000+0x1ce51) [0x8064e51] >> Bus error at address 0xb61f4000 >> >> Fatal server error: >> Caught signal 7 (Bus error). Server aborting >> >> which is not too much to go on. As you can see, I use the intel >> drivers. The behaviour may have started after my March 19 upgrades: >> >> Fri Mar 19 11:08:54 2010 >>> x11-libs/libXau-1.0.5 >> Fri Mar 19 11:09:41 2010 >>> x11-libs/libXdmcp-1.0.3 >> Fri Mar 19 11:10:06 2010 >>> x11-misc/util-macros-1.6.1 >> Fri Mar 19 11:20:13 2010 >>> x11-libs/libX11-1.3.3 >> Fri Mar 19 11:21:17 2010 >>> x11-libs/libdrm-2.4.19 >> Fri Mar 19 11:22:44 2010 >>> x11-libs/libXt-1.0.8 >> Fri Mar 19 11:23:26 2010 >>> x11-libs/libXScrnSaver-1.2.0 >> Fri Mar 19 11:41:42 2010 >>> x11-libs/openmotif-2.3.3 >> Fri Mar 19 11:42:17 2010 >>> x11-apps/xinput-1.5.1 >> Fri Mar 19 12:30:55 2010 >>> x11-apps/xinit-1.2.1 >> Fri Mar 19 12:54:23 2010 >>> x11-base/xorg-server-1.7.6 >> Fri Mar 19 12:55:55 2010 >>> x11-drivers/xf86-video-intel-2.10.0-r1 >> >> For what it's worth, here's the lspci output: >> >> Gee-Mi-Ni elog # lspci -vs 00:02.* >> 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express >> Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) >> Subsystem: Giga-byte Technology Device 1999 >> Flags: bus master, fast devsel, latency 0, IRQ 16 >> Memory at 5828 (32-bit, non-prefetchable) [size=512K] >> I/O ports at 60c0 [size=8] >> Memory at 4000 (32-bit, prefetchable) [size=256M] >> Memory at 5830 (32-bit, non-prefetchable) [size=256K] >> Expansion ROM at [disabled] >> Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- >> Capabilities: [d0] Power Management version 2 >> Kernel driver in use: i915 >> >> 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, >> 943/940GML Express Integrated Graphics Controller (rev 03) >> Subsystem: Giga-byte Technology Device 1999 >> Flags: bus master, fast devsel, latency 0 >> Memory at 5820 (32-bit, non-prefetchable) [size=512K] >> Capabilities: [d0] Power Management version 2 >> >> >> Any suggestions on what I can do to figure out what the problem is? >> >> Thanks, >> >> W >> -- >> Willie W. Wong ww...@math.princeton.edu >> Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire >> et vice versa ~~~ I. Newton >> >> > > Seems that you also suffer problem with Intel driver and kernel 2.6.32. Upgrade your xf86-video-intel to v2.11.0 may help. -- Nguyễn Bảo Ngọc http://www.facebook.com/pymaster
Re: [gentoo-user] ssd: using TRIM
Am 09.04.2010 09:42, schrieb Stefan G. Weichinger: > > Greets, gentoo-users, > > yesterday at last I put my Intel SSD X25-M G2 into my Thinkpad. Additional thoughts ad "ssd, linux, laptop": * running hdapsd seems useless now ;-) * what about laptop-mode? gotta look through /etc/laptop-mode/laptop-mode.conf, maybe some hdd-related settings are counter-productive now ... * back then Volker recommended putting only stuff like / onto the ssd, and /home on hdd ... that's not possible on a one-drive-only laptop. Any additional maintenance-tasks to do in this case? - For sure, I will keep my old hdd, and pull images and backups from my thinkpad every few days. Stefan
[gentoo-user] Re: [OT] shell ouput which file descriptor
On 04/09/2010 08:19 AM, Harry Putnam wrote: This is not a question about cvs... its only used for example. I'm puzzled about a change in what I see when I run cvs -n update 2> /dev/null I've apparently lost the ability to remove stder from output. I used that command to trim out file descriptor 2 which used to leave a list of any changed files in the repo on the console, for a very long time. Suddenly there is no difference with: cvs -n update 2> /dev/null cvs -n update The stuff on stderr still shows in the ouput either way. Further; cvs -n update 2>er (redirect stder to ./er) Doesn't put anything in ./er However cvs -n update 1>out (redirect stdout to ./out) Does catch the output I'm after and leave out stderr. (as one would expect) So, again, apparently I've lost the ability to trim out stderr with a redirect to /dev/null (cvs -n update 2> /dev/null) ---- ---=--- - The only thing I've been tinkering with is evaluating the /etc/DIR_COLORS file. I switched from evaluating a custom version to evaluating the default version. I have no helpful advice, but I would try a couple of simple experiments: I have this in my home directory because I'm color blind: -rw-r--r-- 1 wa1ter users 0 2007-08-27 18:29 .dir_colors $cat nonexistantfile cat: nonexistantfile: No such file or directory $cat nonexistantfile 2> /tmp/testfile $ $cat /tmp/testfile cat: nonexistantfile: No such file or directory Are you running cvs as root, or user, or ...?
[gentoo-user] xorg-server 1.7.
Hi folks, I did my updates a bit ago. I notice xorg and a lot of friends were updated. The update went fine as far as it compiled and installed fine. I did my config updates and such as well. To make sure everything stayed sane, I logged out of KDE, then went to single user mode and back to default. I figured this was a sure way to restart all the services that would be upgraded. When kdm came back up, no keyboard, no mouse nothing. So I used the trusty sysreq keys to get back to a console. Now I'm trying to roll back to the older version that I was using before the upgrade. As most of you know, I have hal disabled and I confirmed that it is indeed still disabled. I masked mesa and xorg back to the old version. Now they won't compile. I get errors like this: config.status: executing depfiles commands config.status: executing libtool commands make -j2 make all-recursive make[1]: Entering directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' Making all in src make[2]: Entering directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' CC nv_cursor.lo CC nv_dac.lo In file included from /usr/include/xorg/vgaHW.h:29, from nv_include.h:51, from nv_cursor.c:28: /usr/include/X11/extensions/dpms.h:40: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ /usr/include/X11/extensions/dpms.h:42: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ /usr/include/X11/extensions/dpms.h:44: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSEnableâ /usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSDisableâ /usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ /usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSInfoâ In file included from /usr/include/xorg/vgaHW.h:29, from nv_include.h:51, from nv_dac.c:28: /usr/include/X11/extensions/dpms.h:40: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ /usr/include/X11/extensions/dpms.h:42: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ /usr/include/X11/extensions/dpms.h:44: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSEnableâ /usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSDisableâ /usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ /usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSInfoâ make[2]: *** [nv_cursor.lo] Error 1 make[2]: *** Waiting for unfinished jobs make[2]: *** [nv_dac.lo] Error 1 make[2]: Leaving directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' make: *** [all] Error 2 * ERROR: x11-drivers/xf86-video-nv-2.1.17 failed: * emake failed * * Call stack: * ebuild.sh, line 48: Called src_compile * environment, line 3297: Called x-modular_src_compile * environment, line 4125: Called x-modular_src_make * environment, line 4163: Called die * The specific snippet of code: * emake || die "emake failed" * * If you need support, post the output of 'emerge --info =x11-drivers/xf86-video-nv-2.1.17', * the complete build log and the output of 'emerge -pqv =x11-drivers/xf86-video-nv-2.1.17'. * The complete build log is located at '/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/temp/environment'. * S: '/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' >>> Failed to emerge x11-drivers/xf86-video-nv-2.1.17, Log file: >>> '/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log' * GNU info directory index is up-to-date. * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news to read news items. r...@smoker ~ # There is my wish list. If I can get the new xorg stuff working, that is cool. If no on
Re: [gentoo-user] xorg-server 1.7.
Dale [10-04-10 05:08]: > Hi folks, > > I did my updates a bit ago. I notice xorg and a lot of friends were > updated. The update went fine as far as it compiled and installed > fine. I did my config updates and such as well. To make sure > everything stayed sane, I logged out of KDE, then went to single user > mode and back to default. I figured this was a sure way to restart all > the services that would be upgraded. > > When kdm came back up, no keyboard, no mouse nothing. So I used the > trusty sysreq keys to get back to a console. Now I'm trying to roll > back to the older version that I was using before the upgrade. As most > of you know, I have hal disabled and I confirmed that it is indeed > still disabled. I masked mesa and xorg back to the old version. Now > they won't compile. I get errors like this: > > config.status: executing depfiles commands > config.status: executing libtool commands > make -j2 > make all-recursive > make[1]: Entering directory > `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' > Making all in src > make[2]: Entering directory > `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' > CC nv_cursor.lo > CC nv_dac.lo > In file included from /usr/include/xorg/vgaHW.h:29, > from nv_include.h:51, > from nv_cursor.c:28: > /usr/include/X11/extensions/dpms.h:40: error: expected â)â before > â*â token > /usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ > /usr/include/X11/extensions/dpms.h:42: error: expected â)â before > â*â token > /usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ > /usr/include/X11/extensions/dpms.h:44: error: expected â)â before > â*â token > /usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSEnableâ > /usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSDisableâ > /usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ > /usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSInfoâ > In file included from /usr/include/xorg/vgaHW.h:29, > from nv_include.h:51, > from nv_dac.c:28: > /usr/include/X11/extensions/dpms.h:40: error: expected â)â before > â*â token > /usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ > /usr/include/X11/extensions/dpms.h:42: error: expected â)â before > â*â token > /usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ > /usr/include/X11/extensions/dpms.h:44: error: expected â)â before > â*â token > /usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSEnableâ > /usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSDisableâ > /usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ > /usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, > â;â, âasmâ or â__attribute__â before âDPMSInfoâ > make[2]: *** [nv_cursor.lo] Error 1 > make[2]: *** Waiting for unfinished jobs > make[2]: *** [nv_dac.lo] Error 1 > make[2]: Leaving directory > `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' > make: *** [all] Error 2 > * ERROR: x11-drivers/xf86-video-nv-2.1.17 failed: > * emake failed > * > * Call stack: > * ebuild.sh, line 48: Called src_compile > * environment, line 3297: Called x-modular_src_compile > * environment, line 4125: Called x-modular_src_make > * environment, line 4163: Called die > * The specific snippet of code: > * emake || die "emake failed" > * > * If you need support, post the output of 'emerge --info > =x11-drivers/xf86-video-nv-2.1.17', > * the complete build log and the output of 'emerge -pqv > =x11-drivers/xf86-video-nv-2.1.17'. > * The complete build log is located at > '/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log'. > * The ebuild environment file is located at > '/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/temp/environment'. > * S: > '/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' > > >>> Failed to emerge x11-drivers/xf86-video-nv-2.1.17, Log file: > > >>> > '/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log' > > * GNU info directory index is
Re: [gentoo-user] xorg-server 1.7.
meino.cra...@gmx.de wrote: Dale [10-04-10 05:08]: Hi folks, I did my updates a bit ago. I notice xorg and a lot of friends were updated. The update went fine as far as it compiled and installed fine. I did my config updates and such as well. To make sure everything stayed sane, I logged out of KDE, then went to single user mode and back to default. I figured this was a sure way to restart all the services that would be upgraded. When kdm came back up, no keyboard, no mouse nothing. So I used the trusty sysreq keys to get back to a console. Now I'm trying to roll back to the older version that I was using before the upgrade. As most of you know, I have hal disabled and I confirmed that it is indeed still disabled. I masked mesa and xorg back to the old version. Now they won't compile. I get errors like this: config.status: executing depfiles commands config.status: executing libtool commands make -j2 make all-recursive make[1]: Entering directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' Making all in src make[2]: Entering directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' CC nv_cursor.lo CC nv_dac.lo In file included from /usr/include/xorg/vgaHW.h:29, from nv_include.h:51, from nv_cursor.c:28: /usr/include/X11/extensions/dpms.h:40: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ /usr/include/X11/extensions/dpms.h:42: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ /usr/include/X11/extensions/dpms.h:44: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSEnableâ /usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSDisableâ /usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ /usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSInfoâ In file included from /usr/include/xorg/vgaHW.h:29, from nv_include.h:51, from nv_dac.c:28: /usr/include/X11/extensions/dpms.h:40: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ /usr/include/X11/extensions/dpms.h:42: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ /usr/include/X11/extensions/dpms.h:44: error: expected â)â before â*â token /usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSEnableâ /usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSDisableâ /usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ /usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âDPMSInfoâ make[2]: *** [nv_cursor.lo] Error 1 make[2]: *** Waiting for unfinished jobs make[2]: *** [nv_dac.lo] Error 1 make[2]: Leaving directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' make: *** [all] Error 2 * ERROR: x11-drivers/xf86-video-nv-2.1.17 failed: * emake failed * * Call stack: * ebuild.sh, line 48: Called src_compile * environment, line 3297: Called x-modular_src_compile * environment, line 4125: Called x-modular_src_make * environment, line 4163: Called die * The specific snippet of code: * emake || die "emake failed" * * If you need support, post the output of 'emerge --info =x11-drivers/xf86-video-nv-2.1.17', * the complete build log and the output of 'emerge -pqv =x11-drivers/xf86-video-nv-2.1.17'. * The complete build log is located at '/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/temp/environment'. * S: '/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' Failed to emerge x11-drivers/xf86-video-nv-2.1.17, Log file: '/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log' * GNU info directory index is up-to-date. * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news to read news items. r...@smoker ~ # There is my wish list.
Re: [gentoo-user] xorg-server 1.7.
Dale [10-04-10 05:48]: > meino.cra...@gmx.de wrote: > >Dale [10-04-10 05:08]: > > > >>Hi folks, > >> > >>I did my updates a bit ago. I notice xorg and a lot of friends were > >>updated. The update went fine as far as it compiled and installed > >>fine. I did my config updates and such as well. To make sure > >>everything stayed sane, I logged out of KDE, then went to single user > >>mode and back to default. I figured this was a sure way to restart > >>all > >>the services that would be upgraded. > >> > >>When kdm came back up, no keyboard, no mouse nothing. So I used the > >>trusty sysreq keys to get back to a console. Now I'm trying to roll > >>back to the older version that I was using before the upgrade. As > >>most > >>of you know, I have hal disabled and I confirmed that it is indeed > >>still disabled. I masked mesa and xorg back to the old version. Now > >>they won't compile. I get errors like this: > >> > >>config.status: executing depfiles commands > >>config.status: executing libtool commands > >>make -j2 > >>make all-recursive > >>make[1]: Entering directory > >>`/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' > >>Making all in src > >>make[2]: Entering directory > >>`/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' > >> CC nv_cursor.lo > >> CC nv_dac.lo > >>In file included from /usr/include/xorg/vgaHW.h:29, > >> from nv_include.h:51, > >> from nv_cursor.c:28: > >>/usr/include/X11/extensions/dpms.h:40: error: expected â)â before > >>â*â token > >>/usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ > >>/usr/include/X11/extensions/dpms.h:42: error: expected â)â before > >>â*â token > >>/usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ > >>/usr/include/X11/extensions/dpms.h:44: error: expected â)â before > >>â*â token > >>/usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSEnableâ > >>/usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSDisableâ > >>/usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ > >>/usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSInfoâ > >>In file included from /usr/include/xorg/vgaHW.h:29, > >> from nv_include.h:51, > >> from nv_dac.c:28: > >>/usr/include/X11/extensions/dpms.h:40: error: expected â)â before > >>â*â token > >>/usr/include/X11/extensions/dpms.h:41: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSGetVersionâ > >>/usr/include/X11/extensions/dpms.h:42: error: expected â)â before > >>â*â token > >>/usr/include/X11/extensions/dpms.h:43: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSSetTimeoutsâ > >>/usr/include/X11/extensions/dpms.h:44: error: expected â)â before > >>â*â token > >>/usr/include/X11/extensions/dpms.h:45: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSEnableâ > >>/usr/include/X11/extensions/dpms.h:46: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSDisableâ > >>/usr/include/X11/extensions/dpms.h:47: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSForceLevelâ > >>/usr/include/X11/extensions/dpms.h:48: error: expected â=â, â,â, > >>â;â, âasmâ or â__attribute__â before âDPMSInfoâ > >>make[2]: *** [nv_cursor.lo] Error 1 > >>make[2]: *** Waiting for unfinished jobs > >>make[2]: *** [nv_dac.lo] Error 1 > >>make[2]: Leaving directory > >>`/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17/src' > >>make[1]: *** [all-recursive] Error 1 > >>make[1]: Leaving directory > >>`/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/work/xf86-video-nv-2.1.17' > >>make: *** [all] Error 2 > >> * ERROR: x11-drivers/xf86-video-nv-2.1.17 failed: > >> * emake failed > >> * > >> * Call stack: > >> * ebuild.sh, line 48: Called src_compile > >> * environment, line 3297: Called x-modular_src_compile > >> * environment, line 4125: Called x-modular_src_make > >> * environment, line 4163: Called die > >> * The specific snippet of code: > >> * emake || die "emake failed" > >> * > >> * If you need support, post the output of 'emerge --info > >>=x11-drivers/xf86-video-nv-2.1.17', > >> * the complete build log and the output of 'emerge -pqv > >>=x11-drivers/xf86-video-nv-2.1.17'. > >> * The complete build log is located at > >>'/var/log/portage/elog/x11-drivers:xf86-video-nv-2.1.17:20100410-022626.log'. > >> * The ebuild environment file is located at > >>'/var/tmp/portage/x11-drivers/xf86-video-nv-2.1.17/temp/environment'. > >> * S: > >>'/var/tmp/portage
Re: [gentoo-user] xorg-server 1.7.
meino.cra...@gmx.de wrote: Dale [10-04-10 05:48]: meino.cra...@gmx.de wrote: Hi Dale, Somne shots into the dark: I am running a non-kde and non-gnome Gentoo here (Openbox is my friend) and after upgrading X nothing works. I rtecompiled openbox, lxpanel and the X11-drivers like xf86-input-keyboard, xf86-input-mouse. nvidia-drivers and everything was ok. Try to recompile the x11-drivers and the kde equivalent of the window manager (I dont know much about kde/gnome...sorry ;) ) and may be X11 will be you friend again... HTH! Keep hacking! and have a nice weekend! mcc That makes sense now that you mention it. I'll give that a try. Heck, nothing to lose. I know how to use the sysreq keys pretty good now. lol Thanks. Dale :-) :-) Hi Dale, to get out of X (or not-so-X in your case :O) ) you dont need the sysreqs every time. since they are somehow a 'very hard hrmmm "feature"' ;). Look into your Xorg.conf file under /etc/X11 and look for "dont zap" or something like that (I removed this from my xorg.conf ;) ) and remove that (or better comment it out). After that you kann kill X without disturbing the kernel (and risk your data) with ALT-Backspace. You will get back a console. Log in as root and do a "telinit 2" since the setuo still think of running runlevel 5 "without X" and this is not a sane setup: Runlevel 5 is "with X" and runlevel 2 is "without X". To restart X the clean way do "teleinit 5" as root. HTH Keep hacking! mcc Well when it locks up hard, nothing works not even sysreq. That was the first time it failed me. I'm not sure what made it lock up tho. Oh, ctrl alt backspace doesn't do anything either. Dale :-) :-)
Re: [gentoo-user] xorg-server 1.7.
Dale [10-04-10 06:16]: > meino.cra...@gmx.de wrote: > >Dale [10-04-10 05:48]: > > > >>meino.cra...@gmx.de wrote: > >> > >>> > >>>Hi Dale, > >>> > >>>Somne shots into the dark: > >>>I am running a non-kde and non-gnome Gentoo here (Openbox is my > >>>friend) and after upgrading X nothing works. > >>> > >>>I rtecompiled openbox, lxpanel and the X11-drivers like > >>>xf86-input-keyboard, xf86-input-mouse. nvidia-drivers and > >>>everything was ok. > >>> > >>>Try to recompile the x11-drivers and the kde equivalent of the > >>>window manager (I dont know much about kde/gnome...sorry ;) ) > >>>and may be X11 will be you friend again... > >>> > >>>HTH! > >>> > >>>Keep hacking! and have a nice weekend! > >>>mcc > >>> > >>> > >>> > >>That makes sense now that you mention it. I'll give that a try. > >>Heck, > >>nothing to lose. I know how to use the sysreq keys pretty good now. > >>lol > >> > >>Thanks. > >> > >>Dale > >> > >>:-) :-) > >> > >> > >Hi Dale, > > > >to get out of X (or not-so-X in your case :O) ) you dont need the > >sysreqs every time. since they are somehow a 'very hard hrmmm > >"feature"' ;). > > > >Look into your Xorg.conf file under /etc/X11 and look for "dont zap" > >or something like that (I removed this from my xorg.conf ;) ) and > >remove that (or better comment it out). > > > >After that you kann kill X without disturbing the kernel (and risk > >your data) with ALT-Backspace. You will get back a console. Log in > >as root and do a "telinit 2" since the setuo still think of running > >runlevel 5 "without X" and this is not a sane setup: Runlevel 5 is > >"with X" and runlevel 2 is "without X". > >To restart X the clean way do "teleinit 5" as root. > > > >HTH > > > >Keep hacking! > >mcc > > > > > > Well when it locks up hard, nothing works not even sysreq. That was > the first time it failed me. I'm not sure what made it lock up tho. > > Oh, ctrl alt backspace doesn't do anything either. > > Dale > > :-) :-) > Hi Dale, you have to remove this "Dont Zap"-Option from your xorg.conf first. Should work then. But of course: If a busmaster (in this case your GraphicsCard) doesnot release the bus...no way for little folks little some tiny keys on the keyboard... ;) Keep hacking! mcc -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] xorg-server 1.7.
meino.cra...@gmx.de wrote: Dale [10-04-10 06:16]: meino.cra...@gmx.de wrote: Dale [10-04-10 05:48]: meino.cra...@gmx.de wrote: Hi Dale, Somne shots into the dark: I am running a non-kde and non-gnome Gentoo here (Openbox is my friend) and after upgrading X nothing works. I rtecompiled openbox, lxpanel and the X11-drivers like xf86-input-keyboard, xf86-input-mouse. nvidia-drivers and everything was ok. Try to recompile the x11-drivers and the kde equivalent of the window manager (I dont know much about kde/gnome...sorry ;) ) and may be X11 will be you friend again... HTH! Keep hacking! and have a nice weekend! mcc That makes sense now that you mention it. I'll give that a try. Heck, nothing to lose. I know how to use the sysreq keys pretty good now. lol Thanks. Dale :-) :-) Hi Dale, to get out of X (or not-so-X in your case :O) ) you dont need the sysreqs every time. since they are somehow a 'very hard hrmmm "feature"' ;). Look into your Xorg.conf file under /etc/X11 and look for "dont zap" or something like that (I removed this from my xorg.conf ;) ) and remove that (or better comment it out). After that you kann kill X without disturbing the kernel (and risk your data) with ALT-Backspace. You will get back a console. Log in as root and do a "telinit 2" since the setuo still think of running runlevel 5 "without X" and this is not a sane setup: Runlevel 5 is "with X" and runlevel 2 is "without X". To restart X the clean way do "teleinit 5" as root. HTH Keep hacking! mcc Well when it locks up hard, nothing works not even sysreq. That was the first time it failed me. I'm not sure what made it lock up tho. Oh, ctrl alt backspace doesn't do anything either. Dale :-) :-) Hi Dale, you have to remove this "Dont Zap"-Option from your xorg.conf first. Should work then. But of course: If a busmaster (in this case your GraphicsCard) doesnot release the bus...no way for little folks little some tiny keys on the keyboard... ;) Keep hacking! mcc I got rid of that a long time ago. I like to be able to switch when needed. I'm the only one on this rig so its not a security issue for me. I got the original issue solved. I emerged everything installed in x11-drivers/* and it works fine. I guess I missed something in the list earlier. I now have a new problem to solve. I mentioned this before but now it is a system killer. I boot the system, log into KDE as usual then log out. Instead of going back to kdm, the screen goes black and sits there. I thought maybe it was busy or something so I let it sit for about 10 minutes. It never did anything. The monitor stays on so it is getting some sort of a signal. Also, ctrl alt F* keys do nothing. They work elsewhere but not when it locks up. The only way to do anything is to go through the whole sysreq set until the system reboots. Then the process repeats. I can boot up, the services start fine, I can even log in but once I log out, it locks up with nothing on the screen. Anybody have a clue what could cause this? I searched the logs in /var/log and found this: (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) NVIDIA(0): log file that the GLX module has been loaded in your X (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If (EE) NVIDIA(0): you continue to encounter problems, Please try (EE) NVIDIA(0): reinstalling the NVIDIA driver. (II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 (NV34) at PCI:2:0:0 (GPU-0) (--) NVIDIA(0): Memory: 131072 kBytes (--) NVIDIA(0): VideoBIOS: 04.34.20.23.00 (II) NVIDIA(0): Detected AGP rate: 8X (--) NVIDIA(0): Interlaced video modes are supported on this GPU (--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:2:0:0: (--) NVIDIA(0): Gateway EV910 (CRT-0) (--) NVIDIA(0): Gateway EV910 (CRT-0): 350.0 MHz maximum pixel clock (WW) NVIDIA(0): The EDID for Gateway EV910 (CRT-0) contradicts itself: mode (WW) NVIDIA(0): "720x405" is specified in the EDID; however, the EDID's (WW) NVIDIA(0): valid HorizSync range (30.000-95.000 kHz) would exclude (WW) NVIDIA(0): this mode's HorizSync (29.5 kHz); ignoring HorizSync check (WW) NVIDIA(0): for mode "720x405". (II) NVIDIA(0): Assigned Display Device: CRT-0 I searched the forums and it appears this is a known issue. Going back to the older xorg is one solution according to what I read. If anyone has a sure fire fix, I'd be willing to fix but otherwise, I'm back tracking. Dale :-) :-)
