Re: xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread doug 



On Wed, 30 Dec 2009, Warren Block wrote:


On Wed, 30 Dec 2009, d...@safeport.com wrote:

After updating ports, 'portsdb -Fu' and 'portversion -vL=' will show 
what's outdated.  (That's with portupgrade installed.  Some would have you 
believe it's second in evil only to HAL.  Maybe true, but it works.)


And then 'portupgrade -r portname' (or 'portupgrade -ar', if you like) 
should upgrade the outdated stuff and everything that depends on it. And 
-P or -PP might help by retrieving packages, although I haven't tried that 
in years.


This includes libc? man 2 libc


Doh, I was thinking of ports, not system.  Some ports have code to check for 
system version requirements, and I'd expect packages to do the same thing. 
But they're moving targets, and developers and porters can't check all the 
combinations.


First building the system does indeed solve all xorg package problems. Second I 
am not sure I agree with your statement. I think the answer is relatively easy:
(1) build packages against the base release, or, (2) document the problem, or 
lastly (3) have the port management tools check for this.


While I am not sure if (3) is possible, I am pretty sure (2) is.

Anyway X and its successor Xorg is at once the great leveler and I have learned 
more about FreeBSD getting my Desktops going than any other single activity. I 
appreciate all the time you spent leading me to the solution. Bouncing thoughts 
and ideas with you was most helpful.


I wanted to post my original comment and this to make explicit that a version 7
package will not necessarily work on a 7.2 system. I certainly do not have the 
knowledge to know what system libraries a port is built on. This was actually 
quite easy to find because of the error. If there is no error you are left doing 
a ktrace or something. By the way have gotten the error and figuring out that 
libc was involved, I did not understand the implication, I had help there.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread Warren Block 

On Wed, 30 Dec 2009, d...@safeport.com wrote:

After updating ports, 'portsdb -Fu' and 'portversion -vL=' will show what's 
outdated.  (That's with portupgrade installed.  Some would have you believe 
it's second in evil only to HAL.  Maybe true, but it works.)


And then 'portupgrade -r portname' (or 'portupgrade -ar', if you like) 
should upgrade the outdated stuff and everything that depends on it. And -P 
or -PP might help by retrieving packages, although I haven't tried that in 
years.


This includes libc? man 2 libc


Doh, I was thinking of ports, not system.  Some ports have code to check 
for system version requirements, and I'd expect packages to do the same 
thing.  But they're moving targets, and developers and porters can't 
check all the combinations.


-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread doug 

j

On Wed, 30 Dec 2009, Warren Block wrote:


On Wed, 30 Dec 2009, d...@safeport.com wrote:


On Wed, 30 Dec 2009, d...@safeport.com wrote:

[non applicable stuff cut]


Starting xdm gives the following in /var/log/xdm-log:

:
 finished PLL1
 set RMX
 set LVDS
 enable LVDS
 disable primary dac
 disable FP1
 disable TV
 /libexec/ld-elf.so.1: /usr/local/bin/X: Undefined symbol "shmctl"
 xdm error (pid 1416): server unexpectedly died
 xdm error (pid 1416): Server for display :0 can't be started, session
 disabled


This is mostly likely because my 7.2 libc is earlier than the one used to 
build the package. I am told that, "there's a strong argument that 7-stable 
packages should actually be built against 7.0, which defines the binary 
interface, but the portmgr folks are not convinced to do so".


After updating ports, 'portsdb -Fu' and 'portversion -vL=' will show what's 
outdated.  (That's with portupgrade installed.  Some would have you believe 
it's second in evil only to HAL.  Maybe true, but it works.)


And then 'portupgrade -r portname' (or 'portupgrade -ar', if you like) should 
upgrade the outdated stuff and everything that depends on it. And -P or -PP 
might help by retrieving packages, although I haven't tried that in years.


This includes libc? man 2 libc

As an end-user I would at least plead for a doc-change. This bit explains a 
lot of 'random' behavior that gets reported. Getting an error is the best 
that can be hoped for. A change in a syscall that produces a silent error 
is much more time consuming. Xorg being Xorg this is just, I am sure, the 
next layer. This is also most likely the answer to threads on 10/09/09 and 
12/17/09.


Is the slow startup with xdm fixed by upgrading libc?  By replacing the 
package or via ports?



Still building Warren, will let you know.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread Warren Block 

On Wed, 30 Dec 2009, d...@safeport.com wrote:


On Wed, 30 Dec 2009, d...@safeport.com wrote:

[non applicable stuff cut]


Starting xdm gives the following in /var/log/xdm-log:

:
 finished PLL1
 set RMX
 set LVDS
 enable LVDS
 disable primary dac
 disable FP1
 disable TV
 /libexec/ld-elf.so.1: /usr/local/bin/X: Undefined symbol "shmctl"
 xdm error (pid 1416): server unexpectedly died
 xdm error (pid 1416): Server for display :0 can't be started, session
 disabled


This is mostly likely because my 7.2 libc is earlier than the one used to 
build the package. I am told that, "there's a strong argument that 7-stable 
packages should actually be built against 7.0, which defines the binary 
interface, but the portmgr folks are not convinced to do so".


After updating ports, 'portsdb -Fu' and 'portversion -vL=' will show 
what's outdated.  (That's with portupgrade installed.  Some would have 
you believe it's second in evil only to HAL.  Maybe true, but it works.)


And then 'portupgrade -r portname' (or 'portupgrade -ar', if you like) 
should upgrade the outdated stuff and everything that depends on it. 
And -P or -PP might help by retrieving packages, although I haven't 
tried that in years.


As an end-user I would at least plead for a doc-change. This bit explains a 
lot of 'random' behavior that gets reported. Getting an error is the best 
that can be hoped for. A change in a syscall that produces a silent error is 
much more time consuming. Xorg being Xorg this is just, I am sure, the next 
layer. This is also most likely the answer to threads on 10/09/09 and 
12/17/09.


Is the slow startup with xdm fixed by upgrading libc?  By replacing the 
package or via ports?


-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread Warren Block 

On Wed, 30 Dec 2009, d...@safeport.com wrote:


I am also pretty sure my hardware just does not work with hal and dbus.


What keyboard and mouse do you have?  Also, which version of FreeBSD are 
you using?


All these issues are with xorg 7.4_1. I have installed xorg-7.4_2 via pkg_add 
on a clean system and xdm-1.1.8_2. Nothing else is installed.


Well, yes, but I was asking about the FreeBSD version: 7.2, 8.0, etc. 
Mainly the difference is for USB devices.


[...xdm info saved for another message...]


I added one line to the xorg.conf file generated by Xorg -configure:

 Option  "AutoAddDevices" "false"


That prevents dbus/hal from being used by xorg, so it's not surprising 
they don't work.


A diff shows this file to be exactly what I was using with xorg-7.4_1 (which 
works albeit with a very slow startup). I have excerpted various [relevant] 
outputs to show my hardware. I needed I can either attach or include the 
entire files.


startx works but locks the keyboard.


I may have asked before, but does ctrl-alt-f1 still work?  Even if the 
rest of the keyboard is not responding, that can tell you if X is alive.


-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread doug 

On Wed, 30 Dec 2009, d...@safeport.com wrote:

[non applicable stuff cut]


Starting xdm gives the following in /var/log/xdm-log:

:
 finished PLL1
 set RMX
 set LVDS
 enable LVDS
 disable primary dac
 disable FP1
 disable TV
 /libexec/ld-elf.so.1: /usr/local/bin/X: Undefined symbol "shmctl"
 xdm error (pid 1416): server unexpectedly died
 xdm error (pid 1416): Server for display :0 can't be started, session
 disabled


This is mostly likely because my 7.2 libc is earlier than the one used to build 
the package. I am told that, "there's a strong argument that 7-stable packages 
should actually be built against 7.0, which defines the binary interface, but 
the portmgr folks are not convinced to do so".


As an end-user I would at least plead for a doc-change. This bit explains a lot 
of 'random' behavior that gets reported. Getting an error is the best that can 
be hoped for. A change in a syscall that produces a silent error is much more 
time consuming. Xorg being Xorg this is just, I am sure, the next layer. This is 
also most likely the answer to threads on 10/09/09 and 12/17/09.


So in general if you have an issue with one of these mega-packages first make 
sure your build is later than the package build date. With ports that get 
unexplained compile error[s], the answer is also [first] update your system.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

xorg-7.4_2 error (was xorg 7.4 questions)

2009-12-30 Thread doug 

On Tue, 29 Dec 2009, Warren Block wrote:


On Tue, 29 Dec 2009, d...@safeport.com wrote:

[xdm slow startup]

The answer appears to be to add an empty LISTEN statement to 
/usr/local/lib/X11/xdm/Xaccess. The xdm package issues a IPV6 DHCP request. 
While the xdm man page suggests this is not needed:


  To disable listening for XDMCP connections altogther, a line of
  LISTEN with no addresses may be specified, or the previously
  supported method of setting DisplayManager.requestPort to 0 may
  be used.

This seems not to be the case as adding this line gets rid of the long 
delay and suppresses the IPV6 DHCP request. The DisplayManager.requestPort 
is set to 0 in the default configuration. This solves the long start (I am 
pretty sure). Thank you for your suggestions that pushed me to find this.


I was wrong about this. With this change xdm started fine from the command line 
and took perhaps even longer when started from /etc/ttys. This describes 7.4_1 
behavior.


Hmm.  That sounds like a bug (maybe IPV6 support being added but the feature 
to disable it being forgotten).  Does having an IPV6 localhost defined in 
/etc/hosts ("::1 localhost") have the same effect?



I am also pretty sure my hardware just does not work with hal and dbus.


What keyboard and mouse do you have?  Also, which version of FreeBSD are you 
using?


All these issues are with xorg 7.4_1. I have installed xorg-7.4_2 via pkg_add on 
a clean system and xdm-1.1.8_2. Nothing else is installed.


Starting xdm gives the following in /var/log/xdm-log:

 :
  finished PLL1
  set RMX
  set LVDS
  enable LVDS
  disable primary dac
  disable FP1
  disable TV
  /libexec/ld-elf.so.1: /usr/local/bin/X: Undefined symbol "shmctl"
  xdm error (pid 1416): server unexpectedly died
  xdm error (pid 1416): Server for display :0 can't be started, session
  disabled

I added one line to the xorg.conf file generated by Xorg -configure:

  Option  "AutoAddDevices" "false"

A diff shows this file to be exactly what I was using with xorg-7.4_1 (which 
works albeit with a very slow startup). I have excerpted various 
[relevant] outputs to show my hardware. I needed I can either attach or 
include the entire files.


startx works but locks the keyboard. After running fsck scores of times, it 
finally occurred to me to ssh into the system so I can force a shutdown. With 
both startx (which appears to work) and xdm a reboot is required to recover 
the system. Starting xdm get an error logged to STDERR that an IPV6 LISTEN can 
not be done.


My laptop is built without IPV6. hal and dbus are not started.

Thanks for any help. This appears to be either an error in the way the package 
was build or something I can [hopefully] configure around.



Hardware: IBM thinkpad T42p

  dmesg
  --
  pci1:  on pcib1
  vgapci0:  port 0x3000-0x30ff mem
  0xe000-0xe7ff,0xc010-0xc010 irq 11 at device 0.0
  on pci1
 :
  atkbdc0:  port 0x60,0x64 irq 1 on acpi0
  atkbd0:  irq 1 on atkbdc0

  pciconf
  
  hos...@pci0:0:0:0:  class=0x06 card=0x05291014 chip=0x33408086
  rev=0x03
  hdr=0x00
  vendor = 'Intel Corporation'
  device = '82855PM Processor to I/O Controller'
  class  = bridge
  subclass   = HOST-PCI
  pc...@pci0:0:1:0:   class=0x060400 card=0x chip=0x33418086
  rev=0x03  hdr=0x01
  vendor = 'Intel Corporation'
  device = '82855PM Processor to AGP Controller'
  class  = bridge
  subclass   = PCI-PCI
  :
  vgap...@pci0:1:0:0: class=0x03 card=0x054f1014 chip=0x4e541002
  rev=0x80
  hdr=0x00
  vendor = 'ATI Technologies Inc'
  device = 'Radeon Mobility M10 NT (RV350-WS)'
  class  = display
  subclass   = VGA


_
Douglas Denault
http://www.safeport.com
d...@safeport.com
Voice: 301-217-9220
  Fax: 301-217-9277
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"