From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg-server 1.7.
Date: Fri, 09 Apr 2010 22:42:49 -0500 [thread overview]
Message-ID: <4BBFF3B9.6050002@gmail.com> (raw)
In-Reply-To: <20100410032741.GA5068@solfire>
meino.cramer@gmx.de wrote:
> Dale<rdalek1967@gmail.com> [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.
>>
>> root@smoker ~ #
>>
>>
>> There is my wish list. If I can get the new xorg stuff working, that
>> is cool. If no one else is having trouble with them and it is my
>> hardware or something then getting the old version to compile and
>> install would be fine too.
>>
>> Anyone have a clue how to get something to work here?
>>
>> BTW, if I log into KDE with the new packages, I can log in once but
>> when I log out of KDE, the screen goes black and nothing happens. Even
>> the sysreq keys do nothing. Reset button is all that works.
>>
>> Thoughts? I need a hammer?
>>
>> Dale
>>
>> :-) :-)
>>
>>
> 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
:-) :-)
next prev parent reply other threads:[~2010-04-10 3:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 2:47 [gentoo-user] xorg-server 1.7 Dale
2010-04-10 3:27 ` meino.cramer
2010-04-10 3:42 ` Dale [this message]
2010-04-10 3:56 ` meino.cramer
2010-04-10 4:13 ` Dale
2010-04-10 4:38 ` meino.cramer
2010-04-10 5:41 ` Dale
2010-04-10 13:13 ` Neil Bothwick
2010-04-10 16:23 ` Dale
2010-04-10 17:55 ` [gentoo-user] " walt
2010-04-10 18:19 ` Dale
2010-04-10 19:46 ` walt
2010-04-10 20:10 ` Dale
2010-04-19 4:23 ` [gentoo-user] " dan blum
2010-04-19 4:41 ` Dale
2010-04-19 10:20 ` Philip Webb
2010-04-19 16:56 ` dan blum
2010-04-10 13:14 ` Neil Bothwick
2010-04-10 17:04 ` BRM
2010-04-10 20:05 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BBFF3B9.6050002@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox