[gentoo-user] xorg-server 1.7.

[gentoo-user] xorg-server 1.7.

[Dale]

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

:-)  :-)

Re: [gentoo-user] xorg-server 1.7.

[meino.cramer]

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



-- 
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.

[Dale]

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

:-)  :-)

Re: [gentoo-user] xorg-server 1.7.

[meino.cramer]

Dale <rdalek1967@gmail.com> [10-04-10 05:48]:
> 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
> 
> :-)  :-)
> 

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




-- 
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.

[Dale]

meino.cramer@gmx.de wrote:
> Dale<rdalek1967@gmail.com>  [10-04-10 05:48]:
>    
>> meino.cramer@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.

[meino.cramer]

Dale <rdalek1967@gmail.com> [10-04-10 06:16]:
> meino.cramer@gmx.de wrote:
> >Dale<rdalek1967@gmail.com>  [10-04-10 05:48]:
> >   
> >>meino.cramer@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.

[Dale]

meino.cramer@gmx.de wrote:
> Dale<rdalek1967@gmail.com>  [10-04-10 06:16]:
>    
>> meino.cramer@gmx.de wrote:
>>      
>>> Dale<rdalek1967@gmail.com>   [10-04-10 05:48]:
>>>
>>>        
>>>> meino.cramer@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

:-)  :-)

Re: [gentoo-user] xorg-server 1.7.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

On Sat, 10 Apr 2010 00:41:58 -0500, Dale wrote:

> 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.

emerge --oneshot $(qlist -IC x11-drivers)

just like the xorg elog message tells you to :P


-- 
Neil Bothwick

If a man is standing in the middle of the forest speaking and there is
no woman around to hear him - Is he still wrong?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server 1.7.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

On Sat, 10 Apr 2010 05:56:56 +0200, meino.cramer@gmx.de wrote:

> 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".

This is Gentoo, not Red Hat.


-- 
Neil Bothwick

It's not who you know; it's whom you know.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] xorg-server 1.7.

[Dale]

Neil Bothwick wrote:
> On Sat, 10 Apr 2010 00:41:58 -0500, Dale wrote:
>
>    
>> 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.
>>      
> emerge --oneshot $(qlist -IC x11-drivers)
>
> just like the xorg elog message tells you to :P
>
>
>    

And just like I did.  It still didn't work.  I had to go back to the old 
version to get things back to normal.  I found a thread on the forums 
where others are having issues with this as well.   They went back to 
the old versions as well.

Dale

:-)  :-)

Re: [gentoo-user] xorg-server 1.7.

[BRM]

----- Original Message ----

> From: Neil Bothwick <neil@digimed.co.uk>
> To: gentoo-user@lists.gentoo.org
> Sent: Sat, April 10, 2010 9:14:56 AM
> Subject: Re: [gentoo-user] xorg-server 1.7.
> > 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".
> This is Gentoo, not Red Hat.

And isn't it:

Run Level 1 - Single user w/o network
Run Level 2 - Multiuser w/o network
Run Level 3 - Multiuser w/ network
Run Level 4 - Multiuser w/ network+X
Run Level 5 - unassigned (typically same as Run Level 3)

So it would have to think it's in Run Level 4 not 5, which is still a sane setup, just incorrect by convention.

Or did LSB change the conventions?

Ben

[gentoo-user] Re: xorg-server 1.7.

[walt]

On 04/09/2010 10:41 PM, Dale wrote:> 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

#eselect opengl list
Available OpenGL implementations:
   [1]   nvidia *  <------ Are you using this one?
   [2]   xorg-x11

Re: [gentoo-user] Re: xorg-server 1.7.

[Dale]

walt wrote:
> On 04/09/2010 10:41 PM, Dale wrote:> 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
>
> #eselect opengl list
> Available OpenGL implementations:
>   [1]   nvidia * <------ Are you using this one?
>   [2]   xorg-x11
>
>
>

Yep.  I saw it switch to that during the emerge but I typed it in to 
make sure.  I downgraded back to the old versions and things are working 
now.  I did have to recompile all the input stuff again but at least it 
works.

According to the forums, this is a known problem since xorg is updated 
but apparently nvidia is not yet.

Dale

:-)  :-)

[gentoo-user] Re: xorg-server 1.7.

[walt]

On 04/10/2010 11:19 AM, Dale wrote:
> walt wrote:
>> On 04/09/2010 10:41 PM, Dale wrote:> 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
>>
>> #eselect opengl list
>> Available OpenGL implementations:
>> [1] nvidia * <------ Are you using this one?
>> [2] xorg-x11
>>
>>
>>
>
> Yep. I saw it switch to that during the emerge but I typed it in to make sure. I downgraded back to the old versions and things are working now. I did have to recompile all the input stuff again but at least it works.
>
> According to the forums, this is a known problem since xorg is updated but apparently nvidia is not yet.

Yes, I see now.  It works for me because I have the ~ version of the nvidia driver
unmasked.  I run the most recent kernel from Linus and the stable driver won't compile
against his newer kernels.

Re: [gentoo-user] xorg-server 1.7.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

On Sat, 10 Apr 2010 10:04:33 -0700 (PDT), BRM wrote:

> > This is Gentoo, not Red Hat.  
> 
> And isn't it:
> 
> Run Level 1 - Single user w/o network
> Run Level 2 - Multiuser w/o network
> Run Level 3 - Multiuser w/ network
> Run Level 4 - Multiuser w/ network+X
> Run Level 5 - unassigned (typically same as Run Level 3)

No, although that sounds a little like Slackware.

Gentoo uses runlevel three for everything, whether X is started or not is
defined by the softlevel and rc-update.

To switch to and from single, use

rc single
rc default


-- 
Neil Bothwick

WinErr 003: Dynamic linking error - Your mistake is now in every file

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: xorg-server 1.7.

[Dale]

walt wrote:
> On 04/10/2010 11:19 AM, Dale wrote:
>> walt wrote:
>>> On 04/09/2010 10:41 PM, Dale wrote:> 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
>>>
>>> #eselect opengl list
>>> Available OpenGL implementations:
>>> [1] nvidia * <------ Are you using this one?
>>> [2] xorg-x11
>>>
>>>
>>>
>>
>> Yep. I saw it switch to that during the emerge but I typed it in to 
>> make sure. I downgraded back to the old versions and things are 
>> working now. I did have to recompile all the input stuff again but at 
>> least it works.
>>
>> According to the forums, this is a known problem since xorg is 
>> updated but apparently nvidia is not yet.
>
> Yes, I see now.  It works for me because I have the ~ version of the 
> nvidia driver
> unmasked.  I run the most recent kernel from Linus and the stable 
> driver won't compile
> against his newer kernels.
>
>

I think this is a version mismatch thing.  Xorg, nvidia and maybe 
something else just don't like the currently available versions at the 
moment.  I did try that keyworded nvidia driver for my card but it 
wasn't happy with it either.  I think that was why I had a black 
screen.  I dunno.

At least it is working for now and maybe when the next version is 
released all this will be fixed.

Dale

:-)  :-)

Re: [gentoo-user] xorg-server 1.7.

[dan blum]

I have the same problem when I exit KDE 4.3.3 and xorg 1.6.8. When I try re-emerging the xorg server I got error messages (blocked packages) see below:
 * Use eselect news to read news items.                         

Calculating dependencies... done!
[ebuild     U ] x11-proto/fixesproto-4.1.1 [4.0]
[ebuild     U ] x11-proto/xf86dgaproto-2.1 [2.0.3]
[ebuild     U ] x11-proto/xineramaproto-1.2 [1.1.2]
[ebuild     U ] x11-proto/xf86vidmodeproto-2.3 [2.2.2]
[ebuild     U ] x11-base/xorg-drivers-1.7 [1.6] INPUT_DEVICES="evdev*" VIDEO_CARDS="-fbdev* -glint* -mach64* -mga* -neomagic* -nv* -r128* -radeon* -savage* -sis* -tdfx* -trident* -vesa* -via* -vmware*"                                                               
[ebuild     U ] x11-base/xorg-server-1.7.6 [1.6.5-r1]                                   
[blocks B     ] <x11-libs/libXxf86dga-1.0.99.1 ("<x11-libs/libXxf86dga-1.0.99.1" is blocking x11-proto/xf86dgaproto-2.1)                                                        
[blocks B     ] <x11-libs/libXxf86vm-1.0.99.1 ("<x11-libs/libXxf86vm-1.0.99.1" is blocking x11-proto/xf86vidmodeproto-2.3)                                                      

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  ('installed', '/', 'x11-libs/libXxf86dga-1.0.2', 'nomerge') pulled in by
    x11-libs/libXxf86dga required by ('installed', '/', 'x11-apps/xf86dga-1.0.2', 'nomerge')

  ('installed', '/', 'x11-libs/libXxf86vm-1.0.2', 'nomerge') pulled in by
    x11-libs/libXxf86vm required by ('installed', '/', 'kde-base/kbattleship-4.3.3', 'nomerge')
    x11-libs/libXxf86vm required by ('installed', '/', 'kde-base/kmenuedit-4.3.3', 'nomerge')
    x11-libs/libXxf86vm required by ('installed', '/', 'kde-base/kdepim-icons-4.3.3', 'nomerge')
    (and 238 more)

  ('ebuild', '/', 'x11-proto/xf86vidmodeproto-2.3', 'merge') pulled in by
    >=x11-proto/xf86vidmodeproto-2.2.99.1 required by ('ebuild', '/', 'x11-base/xorg-server-1.7.6', 'merge')

  ('ebuild', '/', 'x11-proto/xf86dgaproto-2.1', 'merge') pulled in by
    >=x11-proto/xf86dgaproto-2.0.99.1 required by ('ebuild', '/', 'x11-base/xorg-server-1.7.6', 'merge')

I am not sure that the above is causing the issue, but my KDE infrequently crashes, which I did not have before with earlier versions of xorg or KDE. I am not very bothered by this issue right now but would like to see if we can get to the root of the problem. If need be, how would one go back to a previous version of xorg, like 1.5.3?

--- On Sat, 4/10/10, Dale <rdalek1967@gmail.com> wrote:

> From: Dale <rdalek1967@gmail.com>
> Subject: Re: [gentoo-user] xorg-server 1.7.
> To: gentoo-user@lists.gentoo.org
> Date: Saturday, April 10, 2010, 12:41 AM
> meino.cramer@gmx.de
> wrote:
> > Dale<rdalek1967@gmail.com> 
> [10-04-10 06:16]:
> >    
> >> meino.cramer@gmx.de
> wrote:
> >>      
> >>> Dale<rdalek1967@gmail.com>   [10-04-10
> 05:48]:
> >>>
> >>>        
> >>>> meino.cramer@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
> 
> :-)  :-)
> 
> 

Re: [gentoo-user] xorg-server 1.7.

[Dale]

dan blum wrote:
> I have the same problem when I exit KDE 4.3.3 and xorg 1.6.8. When I try re-emerging the xorg server I got error messages (blocked packages) see below:
>   * Use eselect news to read news items.
>
> Calculating dependencies... done!
> [ebuild     U ] x11-proto/fixesproto-4.1.1 [4.0]
> [ebuild     U ] x11-proto/xf86dgaproto-2.1 [2.0.3]
> [ebuild     U ] x11-proto/xineramaproto-1.2 [1.1.2]
> [ebuild     U ] x11-proto/xf86vidmodeproto-2.3 [2.2.2]
> [ebuild     U ] x11-base/xorg-drivers-1.7 [1.6] INPUT_DEVICES="evdev*" VIDEO_CARDS="-fbdev* -glint* -mach64* -mga* -neomagic* -nv* -r128* -radeon* -savage* -sis* -tdfx* -trident* -vesa* -via* -vmware*"
> [ebuild     U ] x11-base/xorg-server-1.7.6 [1.6.5-r1]
> [blocks B     ]<x11-libs/libXxf86dga-1.0.99.1 ("<x11-libs/libXxf86dga-1.0.99.1" is blocking x11-proto/xf86dgaproto-2.1)
> [blocks B     ]<x11-libs/libXxf86vm-1.0.99.1 ("<x11-libs/libXxf86vm-1.0.99.1" is blocking x11-proto/xf86vidmodeproto-2.3)
>
>   * Error: The above package list contains packages which cannot be
>   * installed at the same time on the same system.
>
>    ('installed', '/', 'x11-libs/libXxf86dga-1.0.2', 'nomerge') pulled in by
>      x11-libs/libXxf86dga required by ('installed', '/', 'x11-apps/xf86dga-1.0.2', 'nomerge')
>
>    ('installed', '/', 'x11-libs/libXxf86vm-1.0.2', 'nomerge') pulled in by
>      x11-libs/libXxf86vm required by ('installed', '/', 'kde-base/kbattleship-4.3.3', 'nomerge')
>      x11-libs/libXxf86vm required by ('installed', '/', 'kde-base/kmenuedit-4.3.3', 'nomerge')
>      x11-libs/libXxf86vm required by ('installed', '/', 'kde-base/kdepim-icons-4.3.3', 'nomerge')
>      (and 238 more)
>
>    ('ebuild', '/', 'x11-proto/xf86vidmodeproto-2.3', 'merge') pulled in by
>      >=x11-proto/xf86vidmodeproto-2.2.99.1 required by ('ebuild', '/', 'x11-base/xorg-server-1.7.6', 'merge')
>
>    ('ebuild', '/', 'x11-proto/xf86dgaproto-2.1', 'merge') pulled in by
>      >=x11-proto/xf86dgaproto-2.0.99.1 required by ('ebuild', '/', 'x11-base/xorg-server-1.7.6', 'merge')
>
> I am not sure that the above is causing the issue, but my KDE infrequently crashes, which I did not have before with earlier versions of xorg or KDE. I am not very bothered by this issue right now but would like to see if we can get to the root of the problem. If need be, how would one go back to a previous version of xorg, like 1.5.3?
>
>    

I'm using this version and it works fine.

x11-base/xorg-server-1.6.5-r1

It's also still in portage so it would be easier to install too.  You 
may want to give that a try.  I think the 'source' devs know about this 
issues so it will most likely be fixed pretty soon.  According to what I 
read on the forums it is a change on xorg-server that the video drivers 
are not ready for or maybe the other way around.  That was my take.  For 
me, as long as they know it is a issue, I'm willing to give them time to 
fix it.

Now if they start taking things out of portage and leave us with nothing 
but broke stuff, then we have a problem.  We would then need to let the 
Gentoo devs know that those version are all that can be used until 
things get fixed upstream.

Dale

:-)  :-)

Re: [gentoo-user] xorg-server 1.7.

[Philip Webb]

100418 dan blum wrote:
> When I try re-emerging the xorg server I got error messages below:
> [ebuild     U ] x11-proto/fixesproto-4.1.1 [4.0]
> [ebuild     U ] x11-proto/xf86dgaproto-2.1 [2.0.3]
> [ebuild     U ] x11-proto/xineramaproto-1.2 [1.1.2]
> [ebuild     U ] x11-proto/xf86vidmodeproto-2.3 [2.2.2]
> [ebuild     U ] x11-base/xorg-drivers-1.7 [1.6] INPUT_DEVICES="evdev*" VIDEO_CARDS="-fbdev* -glint* -mach64* -mga* -neomagic* -nv* -r128* -radeon* -savage* -sis* -tdfx* -trident* -vesa* -via* -vmware*"
> [ebuild     U ] x11-base/xorg-server-1.7.6 [1.6.5-r1]
> [blocks B     ] <x11-libs/libXxf86dga-1.0.99.1 ("<x11-libs/libXxf86dga-1.0.99.1" is blocking x11-proto/xf86dgaproto-2.1)
> [blocks B     ] <x11-libs/libXxf86vm-1.0.99.1 ("<x11-libs/libXxf86vm-1.0.99.1" is blocking x11-proto/xf86vidmodeproto-2.3)
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.

I did this upgrade yesterday without any further problem.
You get around the block by first emerging  libXxf86dga  libXxf86vm .
As I've reported before to much general derision,
I always emerge pkgs individually & thereby avoid many problems.

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] xorg-server 1.7.

[dan blum]

Phylip,

First of all, I currently do have a functioning xorg server; but not sure if it is working as well as it should, based on the reported errors. Does anyone know what are the libXxf86dga libXxf86vm libraries as compared to the "proto" variety"? They seem to be the offending packages pulled in by kde-base.

The way I read the error messages, to emerge the xorg-server, the above packages need to be gone and the "proto" variety packages will be than emerged.

Someone at Gentoo put in a block between the 2 package varieties, so working around this seems to be wrong. Why aren't the xorg and kde packages communicating?

Dan

--- On Mon, 4/19/10, Philip Webb <purslow@ca.inter.net> wrote:

> From: Philip Webb <purslow@ca.inter.net>
> Subject: Re: [gentoo-user] xorg-server 1.7.
> To: gentoo-user@lists.gentoo.org
> Date: Monday, April 19, 2010, 5:20 AM
> 100418 dan blum wrote:
> > When I try re-emerging the xorg server I got error
> messages below:
> > [ebuild     U ]
> x11-proto/fixesproto-4.1.1 [4.0]
> > [ebuild     U ]
> x11-proto/xf86dgaproto-2.1 [2.0.3]
> > [ebuild     U ]
> x11-proto/xineramaproto-1.2 [1.1.2]
> > [ebuild     U ]
> x11-proto/xf86vidmodeproto-2.3 [2.2.2]
> > [ebuild     U ]
> x11-base/xorg-drivers-1.7 [1.6] INPUT_DEVICES="evdev*"
> VIDEO_CARDS="-fbdev* -glint* -mach64* -mga* -neomagic* -nv*
> -r128* -radeon* -savage* -sis* -tdfx* -trident* -vesa* -via*
> -vmware*"
> > [ebuild     U ]
> x11-base/xorg-server-1.7.6 [1.6.5-r1]
> > [blocks B     ]
> <x11-libs/libXxf86dga-1.0.99.1
> ("<x11-libs/libXxf86dga-1.0.99.1" is blocking
> x11-proto/xf86dgaproto-2.1)
> > [blocks B     ]
> <x11-libs/libXxf86vm-1.0.99.1
> ("<x11-libs/libXxf86vm-1.0.99.1" is blocking
> x11-proto/xf86vidmodeproto-2.3)
> >  * Error: The above package list contains
> packages which cannot be
> >  * installed at the same time on the same
> system.
> 
> I did this upgrade yesterday without any further problem.
> You get around the block by first emerging 
> libXxf86dga  libXxf86vm .
> As I've reported before to much general derision,
> I always emerge pkgs individually & thereby avoid many
> problems.
> 
> -- 
> ========================,,============================================
> SUPPORT 
>    ___________//___,   Philip
> Webb
> ELECTRIC   /] [] [] [] []
> []|   Cities Centre, University of Toronto
> TRANSIT   
> `-O----------O---'   purslowatchassdotutorontodotca
> 
> 
>