Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-28 Thread Eric Martin
Michael George wrote:
 I just upgraded my kernel from 2.6.19 to 2.6.23 and it takes almost a
 minute for X to start now.

 I have changed window managers (normally ctwm, tested with twm) with the
 same results.  I rebooted the 2.6.19 kernel and X fires right up as
 expected.  Booting back to 2.6.23 and it's excruciatingly long.

 I saw some prior posts which indicated a network problem, but in that
 case the OP said that the loopback interface wasn't up.  I checked my
 system (ifconfig) and both lo and eth0 are up and running.
I see that you checked if it was up, but have you pinged 127.0.0.1? 
Also, could you possibly have firewall rules setup blocking things on
lo?  It's a shot in the dark but sometimes the oddest of problems have
the simplest of solutions.

HTH
Eric
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-28 Thread Michael George
On Fri, Dec 28, 2007 at 10:18:55AM -0500, Eric Martin wrote:
 Michael George wrote:
  I just upgraded my kernel from 2.6.19 to 2.6.23 and it takes almost a
  minute for X to start now.
 
  I have changed window managers (normally ctwm, tested with twm) with the
  same results.  I rebooted the 2.6.19 kernel and X fires right up as
  expected.  Booting back to 2.6.23 and it's excruciatingly long.
 
  I saw some prior posts which indicated a network problem, but in that
  case the OP said that the loopback interface wasn't up.  I checked my
  system (ifconfig) and both lo and eth0 are up and running.

 I see that you checked if it was up, but have you pinged 127.0.0.1? 
 Also, could you possibly have firewall rules setup blocking things on
 lo?  It's a shot in the dark but sometimes the oddest of problems have
 the simplest of solutions.

Yes, it's up.  However, I think this error is a wild goose...

I rebooted to the 2.6.19 kernel and started X.  It came right up, and
this was the output of startx  startx.2.6.19 21:


xauth:  creating new authority file /home/george/.serverauth.6547


X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN 
Current Operating System: Linux brego 2.6.19-gentoo-r5 #5 SMP PREEMPT Thu Mar 8 
19:16:48 EST 2007 x86_64
Build Date: 22 December 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 27 20:30:12 2007
(==) Using config file: /etc/X11/xorg.conf
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(EE) MGA(0): Static buffer allocation failed, not initializing the DRI
(EE) MGA(0): Need at least 15360 kB video memory at this resolution, bit depth
(EE) MGA(1): Not initializing the DRI on the second head
(EE) AIGLX: Screen 0 is not DRI capable
(EE) AIGLX: Screen 1 is not DRI capable
Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname ':9202'
access control disabled, clients can connect from any host
SetClientVersion: 0 9
ctwm:  unable to find bitmap 
ctwm:  unable to find bitmap 
ctwm:  unable to find bitmap 
X Error: BadWindow (invalid Window parameter)
  Major Opcode:  4
fetchmail: background fetchmail at 6646 killed.
xscreensaver: 20:30:27: SIGHUP received: restarting...
xscreensaver: 20:30:27: running as george/george (500/500)



waiting for X server to shut down XIO:  fatal IO error 104 (Connection reset by 
peer) on X server :0.0

  after 0 requests (0 known processed) with 0 events remaining.

Console:  fatal IO error 32 (Broken pipe) or KillClient on X server :0.0

xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server :0.0

xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server :0.0

SchedTerm:  fatal IO error 32 (Broken pipe) or KillClient on X server :0.0

SchedTerm:  fatal IO error 32 (Broken pipe) or KillClient on X server :0.0

FreeFontPath: FPE /usr/share/fonts/misc refcount is 2, should be 1; fixing.





Notice the 9202 error line.  I then rebooted back into 2.6.23 and
started X with startx  startx.2.6.23 21.  It took 1-2min to for me to get
my window environment, and here is the output of that run:

xauth:  creating new authority file /home/george/.serverauth.6950


X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN 
Current Operating System: Linux brego 2.6.23-gentoo-r3 #3 SMP PREEMPT Sun Dec 
23 21:35:17 EST 2007 x86_64
Build Date: 22 December 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 27 20:32:51 2007
(==) Using config file: /etc/X11/xorg.conf
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(EE) MGA(0): Static buffer allocation failed, not initializing the DRI
(EE) MGA(0): Need at least 15360 kB video memory at this resolution, bit depth
(EE) MGA(1): Not initializing the DRI on the second head
(EE) AIGLX: Screen 0 is not DRI capable
(EE) AIGLX: Screen 1 is not 

Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-28 Thread Michael George
On Fri, Dec 28, 2007 at 01:47:53PM -0500, Michael George wrote:
 
 Notice there is little difference between them.  I think I need to trim
 out my .xinitrc file and see if there is something I'm starting from
 there that is causing the delay with a different kernel...

I don't see anything in my .xinitrc file that would be causing the
problem.  Here are the contents of that file:

#!/bin/sh

DISPLAY=${DISPLAY-unix:0}; export DISPLAY
RDISPLAY=${RDISPLAY-`hostname`:0}; export RDISPLAY

# I've tried taking this line out and it doesn't speed anything up...
sh /usr/local/src/ltsp-server-pkg-static-0.1/xsession-lbus-start 

# Change the keys around
xmodmap .xmodmap.pass1
xmodmap .xmodmap.pass2

# Load .Xdefaults into the X resource database
xrdb -nocpp -display $DISPLAY -load .Xdefaults

# Start a console window.  This line should not be removed.
xterm -T Console -n Console -name Console -C -iconic +vb -geometry =80x14-0+0 

# Start another xterm
xterm -display $DISPLAY -geometry 80x50+0-0 -T Shell -n Shell 
sleep 1
xterm -display $DISPLAY -geometry 80x50-1280-0 -T Shell -n Shell 

# Start a terminal for the schedule screen
xterm -display $DISPLAY -name SchedTerm -geometry 80x50+0-0 -T Shell -n 
Shell 
sleep 1
xterm -display $DISPLAY -name SchedTerm -geometry 80x50-1280-0 -T Shell -n 
Shell 

xcalendar -name xIdeal -display $DISPLAY 

gkrellm 
xload -display $DISPLAY 
gkrellm2 -c secondary 

xcalendar -name xHopper11 -display $DISPLAY 

xdaliclock 

# open up my planner
xcalendar -display $DISPLAY 

# Set the background
# I've run this script manually and it doesn't take long at all to run
(sleep 1; $HOME/bin/background) 

#turn on the screensaver
xscreensaver 

#disable access control
xhost +

# Make the mouse move a little faster than normal
xset m 3 4
# Make the keys repeat more quickly
xset r rate 300 20

# start fetchmail
fetchmail

#Start the window manager
ctwm

#fix keyboard
/usr/bin/kbd_mode -a

# stop fetchmail
fetchmail --quit

#clear


There isn't anything there that I can see which would cause the 2min.
delay in even getting an X mouse pointer...

I'm leaning toward some strange type of Xorg -- kernel interaction,
but I'm not sure what it might be...

-- 
-M

There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-27 Thread Michael George
On Mon, Dec 24, 2007 at 02:19:14PM -0800, [EMAIL PROTECTED] wrote:
 On Sun, Dec 23, 2007 at 10:36:16PM -0500, Michael George wrote:
 
  I do have this error from startx, though:
  Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname 
  ':9202'
 
 I hate to offer so primitive a suggestion, but grep -rl 9202 /etc
 might help.

I checked /etc/services and it indicates a WAP service.  I don't use
wireless networking here.

The odd thing is this: The only variable which changes is the kernel.
2.6.19 vs. 2.6.23.  The xorg.conf is the same, the services that start
at boot time are the same, xinit.conf is the same.  The only change is
the kernel, and I build that with make oldconfig to grab all the same
configurations it could from the old kernel...

I'm baffled...

-- 
-M

There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-24 Thread Randy Barlow
Michael George wrote:
 Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname 
 ':9202'

I'm not sure why the kernel would make this difference, but it looks
like something is trying to connect to No Host:9202.  Do you have your
hostname properly configured?  And in /etc/hosts do you have your
127.0.0.1 entry?

-- 
Randy Barlow
http://electronsweatshop.com
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-24 Thread Michael George
On Mon, Dec 24, 2007 at 11:06:21AM -0500, Randy Barlow wrote:
 Michael George wrote:
  Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname 
  ':9202'
 
 I'm not sure why the kernel would make this difference, but it looks
 like something is trying to connect to No Host:9202.  Do you have your
 hostname properly configured?  And in /etc/hosts do you have your
 127.0.0.1 entry?

I agree with your assessment.  I found a similar message on an LTSP
list, but the terminal's name was before 9202.  (That post was about a
different problem, so the solution there didn't help me.)

My /etc/hosts file includes the localhost entry (127.0.0.1 localhost)
and also an entry for my system's real IP address and hostname
(192.168.0.251 brego ...).

So I don't think that is the problem.  Thank you for the suggestion,
though, as I had not double-checked /etc/hosts yet...

-- 
-M

There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-24 Thread felix
On Sun, Dec 23, 2007 at 10:36:16PM -0500, Michael George wrote:

 I do have this error from startx, though:
 Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname 
 ':9202'

I hate to offer so primitive a suggestion, but grep -rl 9202 /etc
might help.

-- 
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
 Felix Finch: scarecrow repairman  rocket surgeon / [EMAIL PROTECTED]
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 2.6.23 and xorg delayed startup

2007-12-24 Thread David Relson
On Sun, 23 Dec 2007 22:36:16 -0500
Michael George wrote:

 I just upgraded my kernel from 2.6.19 to 2.6.23 and it takes almost a
 minute for X to start now.
 
 I have changed window managers (normally ctwm, tested with twm) with
 the same results.  I rebooted the 2.6.19 kernel and X fires right up
 as expected.  Booting back to 2.6.23 and it's excruciatingly long.
 
 I saw some prior posts which indicated a network problem, but in that
 case the OP said that the loopback interface wasn't up.  I checked my
 system (ifconfig) and both lo and eth0 are up and running.
 
 I do have this error from startx, though:
 Couldn't establish a connection to :9202: IO::Socket::INET: Bad
 hostname ':9202'
 
 I forgot to check if I had that error when running 2.6.19...  I tried
 a web search for this type of error and came up empty.  What part of X
 would this error be from?
 
 Thanks!
 
 -- 
 -M

A one minute delay makes me think of DNS lookup time-out failures.  The
can't establish connection ...9202 sounds like port 9202 of a
non-existant host is wanted.  grep 9202 /etc/services produces:

  wap-wsp-s 9202/tcp # WAP secure connectionless session service 
  wap-wsp-s 9202/udp

Do you do anything with wireless?

HTH,

David

-- 
[EMAIL PROTECTED] mailing list



[gentoo-user] 2.6.23 and xorg delayed startup

2007-12-23 Thread Michael George
I just upgraded my kernel from 2.6.19 to 2.6.23 and it takes almost a
minute for X to start now.

I have changed window managers (normally ctwm, tested with twm) with the
same results.  I rebooted the 2.6.19 kernel and X fires right up as
expected.  Booting back to 2.6.23 and it's excruciatingly long.

I saw some prior posts which indicated a network problem, but in that
case the OP said that the loopback interface wasn't up.  I checked my
system (ifconfig) and both lo and eth0 are up and running.

I do have this error from startx, though:
Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname ':9202'

I forgot to check if I had that error when running 2.6.19...  I tried
a web search for this type of error and came up empty.  What part of X
would this error be from?

Thanks!

-- 
-M

There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.

-- 
[EMAIL PROTECTED] mailing list