Hi list.

I have some computers running Debian, and one of them (pentium 300mhz, 396 MB RAM), in the starting, before the desktop login appears, a black screen appears for 3 minutes. The hd doesn't work during this black screen. I tried other desktop (IceWm, blackbox) and the result is the same. Does anyone knows what could be wrong? In others list, a user of a pentium 200mhz said it's loaded instantly in that machine. Any information will be welcome.

My thanks in advance.

__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/

On Fri, 27 Apr 2007 09:11:42 -0300 (ART)
Renato Gondim Filho <gondim2@yahoo.com.br> wrote:

> Hi list.
>
> I have some computers running Debian, and one of them (pentium
> 300mhz, 396 MB RAM), in the starting, before the desktop login
> appears, a black screen appears for 3 minutes. The hd doesn't work
> during this black screen. I tried other desktop (IceWm, blackbox) and
> the result is the same. Does anyone knows what could be wrong? In
> others list, a user of a pentium 200mhz said it's loaded instantly in
> that machine. Any information will be welcome. My thanks in advance.

Could be a DNS issue. What is the hostname of the machine which exhibits
the delay? Is there an entry for that name in /etc/hosts?

--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Yes, but the computer is not connected to the LAN. Here is the hosts file:

127.0.0.1 localhost
127.0.1.1 blaster
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Is there any log file to look for?
Thanks.

Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Fri, 27 Apr 2007 09:11:42 -0300 (ART)
Renato Gondim Filho wrote:

> Hi list.
>
> I have some computers running Debian, and one of them (pentium
> 300mhz, 396 MB RAM), in the starting, before the desktop login
> appears, a black screen appears for 3 minutes. The hd doesn't work
> during this black screen. I tried other desktop (IceWm, blackbox) and
> the result is the same. Does anyone knows what could be wrong? In
> others list, a user of a pentium 200mhz said it's loaded instantly in
> that machine. Any information will be welcome. My thanks in advance.

Could be a DNS issue. What is the hostname of the machine which exhibits
the delay? Is there an entry for that name in /etc/hosts?

--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/

On Sat, Apr 28, 2007 at 08:41:57AM -0300, Renato Gondim Filho wrote:
> Yes, but the computer is not connected to the LAN. Here is the hosts file:
>
> 127.0.0.1 localhost
> 127.0.1.1 blaster
^

its possible that could be the problem, should be 127.0.0.1

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGM5WxaIeIEqwil4YRAoYdAJ9Mo+y4uMiIXK900qGVOW NUoQ8BPACgiBlL
LtPZTUllXvlZGlGZKRXt7yo=
=dZpO
-----END PGP SIGNATURE-----

On Sat, 28 Apr 2007 11:42:57 -0700
Andrew Sackville-West <andrew@farwestbilliards.com> wrote:

> On Sat, Apr 28, 2007 at 08:41:57AM -0300, Renato Gondim Filho wrote:
> > Yes, but the computer is not connected to the LAN. Here is the
> > hosts file:
> >
> > 127.0.0.1 localhost
> > 127.0.1.1 blaster
> ^
>
> its possible that could be the problem, should be 127.0.0.1
>
> A

Don't think so. It is often advised to separate the hostname and
localhost in the above manner. The address 127.0.1.1 is a valid
address. But it's always worth a try, of course ...

--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, 28 Apr 2007 08:41:57 -0300 (ART)
Renato Gondim Filho <gondim2@yahoo.com.br> wrote:

> Yes, but the computer is not connected to the LAN. Here is the hosts
> file:
>
> 127.0.0.1 localhost
> 127.0.1.1 blaster
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
>

That looks OK.

> Is there any log file to look for?
> Thanks.

The X server logs to /var/log/Xorg.0.log, while clients log to
~/.xsession-errors. You could try a 'tail -f' on those files in a
virtual console and see if you get a long pause at a particular line.

>
> Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Fri, 27 Apr 2007
> 09:11:42 -0300 (ART) Renato Gondim Filho wrote:
>
> > Hi list.
> >
> > I have some computers running Debian, and one of them (pentium
> > 300mhz, 396 MB RAM), in the starting, before the desktop login
> > appears, a black screen appears for 3 minutes. The hd doesn't work
> > during this black screen. I tried other desktop (IceWm, blackbox)
> > and the result is the same. Does anyone knows what could be wrong?
> > In others list, a user of a pentium 200mhz said it's loaded
> > instantly in that machine. Any information will be welcome. My
> > thanks in advance.
>
> Could be a DNS issue. What is the hostname of the machine which
> exhibits the delay? Is there an entry for that name in /etc/hosts?
>


--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Apr 28, 2007 at 09:18:54PM +0100, Liam O'Toole wrote:
> On Sat, 28 Apr 2007 11:42:57 -0700
> Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
>
> > On Sat, Apr 28, 2007 at 08:41:57AM -0300, Renato Gondim Filho wrote:
> > > Yes, but the computer is not connected to the LAN. Here is the
> > > hosts file:
> > >
> > > 127.0.0.1 localhost
> > > 127.0.1.1 blaster
> > ^
> >
> > its possible that could be the problem, should be 127.0.0.1
> >
> > A
>
> Don't think so. It is often advised to separate the hostname and
> localhost in the above manner. The address 127.0.1.1 is a valid
> address. But it's always worth a try, of course ...

huh. I won't argue the point as I don't know. But is it still a
loopback address? 'cuz if its not that could cause problems if some
process is looking for 'blaster' instead of 'localhost'. do please
educate me on that if you know.

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGNCqxaIeIEqwil4YRAjsNAKDhDVMIPOo+KI3wF4Y6wf ulshqOXQCgrbL3
Wf+q+Q73uXPqYB27IkAE6/k=
=s7ax
-----END PGP SIGNATURE-----

On Sat, 28 Apr 2007 22:18:41 -0700
Andrew Sackville-West <andrew@farwestbilliards.com> wrote:

> On Sat, Apr 28, 2007 at 09:18:54PM +0100, Liam O'Toole wrote:
> > On Sat, 28 Apr 2007 11:42:57 -0700
> > Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
> >
> > > On Sat, Apr 28, 2007 at 08:41:57AM -0300, Renato Gondim Filho
> > > wrote:
> > > > Yes, but the computer is not connected to the LAN. Here is the
> > > > hosts file:
> > > >
> > > > 127.0.0.1 localhost
> > > > 127.0.1.1 blaster
> > > ^
> > >
> > > its possible that could be the problem, should be 127.0.0.1
> > >
> > > A
> >
> > Don't think so. It is often advised to separate the hostname and
> > localhost in the above manner. The address 127.0.1.1 is a valid
> > address. But it's always worth a try, of course ...
>
> huh. I won't argue the point as I don't know. But is it still a
> loopback address? 'cuz if its not that could cause problems if some
> process is looking for 'blaster' instead of 'localhost'. do please
> educate me on that if you know.
>
> A

Yes, it's a valid loopback address. Try pinging it ;-)

--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Sorry about my ignorance, some conventions I don't know well (yeat), but "virtual console" means a command line in Terminal?
If it´s correct, I should do this:

tail -f /var/log/Xorg.0.log

Thanks.


Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Sat, 28 Apr 2007 08:41:57 -0300 (ART)
Renato Gondim Filho wrote:

> Yes, but the computer is not connected to the LAN. Here is the hosts
> file:
>
> 127.0.0.1 localhost
> 127.0.1.1 blaster
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
>

That looks OK.

> Is there any log file to look for?
> Thanks.

The X server logs to /var/log/Xorg.0.log, while clients log to
~/.xsession-errors. You could try a 'tail -f' on those files in a
virtual console and see if you get a long pause at a particular line.

>
> Liam O'Toole
escreveu: On Fri, 27 Apr 2007
> 09:11:42 -0300 (ART) Renato Gondim Filho wrote:
>
> > Hi list.
> >
> > I have some computers running Debian, and one of them (pentium
> > 300mhz, 396 MB RAM), in the starting, before the desktop login
> > appears, a black screen appears for 3 minutes. The hd doesn't work
> > during this black screen. I tried other desktop (IceWm, blackbox)
> > and the result is the same. Does anyone knows what could be wrong?
> > In others list, a user of a pentium 200mhz said it's loaded
> > instantly in that machine. Any information will be welcome. My
> > thanks in advance.
>
> Could be a DNS issue. What is the hostname of the machine which
> exhibits the delay? Is there an entry for that name in /etc/hosts?
>


--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/

On Sun, 29 Apr 2007 11:15:47 -0300 (ART)
Renato Gondim Filho <gondim2@yahoo.com.br> wrote:

> Sorry about my ignorance, some conventions I don't know well (yeat),
> but "virtual console" means a command line in Terminal? If it´s
> correct, I should do this:
>
> tail -f /var/log/Xorg.0.log
>
> Thanks.

What I am suggesting is that you try the following.

1. Switch to a virtual console using the key combination ctrl-alt-f1.
2. Login as root.
3. Issue the command '/etc/init.d/gdm restart && tail -f /var/log/Xorg.0.log'. Here I assume that GDM is your display manager.
4. The previous step will probably take you to the login screen (even though the login prompt hasn't appeared). If so, repeat step 1 to return to the virtual console.
5. Watch the progress of output as you follow the log file. Is there a point at which the output pauses for a long time?
6. You can toggle to the login screen at any time using ctrl-alt-f7.

Good luck.

On Sun, Apr 29, 2007 at 09:16:44AM +0100, Liam O'Toole wrote:
> On Sat, 28 Apr 2007 22:18:41 -0700
> Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
>
> > On Sat, Apr 28, 2007 at 09:18:54PM +0100, Liam O'Toole wrote:
> > > On Sat, 28 Apr 2007 11:42:57 -0700
> > > Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
> > >
> > > > On Sat, Apr 28, 2007 at 08:41:57AM -0300, Renato Gondim Filho
> > > > wrote:
> > > > > Yes, but the computer is not connected to the LAN. Here is the
> > > > > hosts file:
> > > > >
> > > > > 127.0.0.1 localhost
> > > > > 127.0.1.1 blaster
> > > > ^
> > > >
> > > > its possible that could be the problem, should be 127.0.0.1
> > > >
> > > > A
> > >
> > > Don't think so. It is often advised to separate the hostname and
> > > localhost in the above manner. The address 127.0.1.1 is a valid
> > > address. But it's always worth a try, of course ...
> >
> > huh. I won't argue the point as I don't know. But is it still a
> > loopback address? 'cuz if its not that could cause problems if some
> > process is looking for 'blaster' instead of 'localhost'. do please
> > educate me on that if you know.
> >
> > A
>
> Yes, it's a valid loopback address. Try pinging it ;-)

what, the easy way? heh. thanks

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGNOD5aIeIEqwil4YRAs+hAKCSbiumRRqFe6k8MH53q6 1wrxjAxACcCcd4
zumjXQXwEKzHbAzrAUUtY4o=
=83xj
-----END PGP SIGNATURE-----

I tried the command '/etc/init.d/gdm restart && tail -f /var/log/Xorg.0.log', but it didn't work. The black screen appeared instead of the output.
But looking at the Xorg.0.log, this message appears many times:

(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)

It could be this?

Thanks.

Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Sun, 29 Apr 2007 11:15:47 -0300 (ART)
Renato Gondim Filho wrote:

> Sorry about my ignorance, some conventions I don't know well (yeat),
> but "virtual console" means a command line in Terminal? If it´s
> correct, I should do this:
>
> tail -f /var/log/Xorg.0.log
>
> Thanks.

What I am suggesting is that you try the following.

1. Switch to a virtual console using the key combination ctrl-alt-f1.
2. Login as root.
3. Issue the command '/etc/init.d/gdm restart && tail -f /var/log/Xorg.0.log'. Here I assume that GDM is your display manager.
4. The previous step will probably take you to the login screen (even though the login prompt hasn't appeared). If so, repeat step 1 to return to the virtual console.
5. Watch the progress of output as you follow the log file. Is there a point at which the output pauses for a long time?
6. You can toggle to the login screen at any time using ctrl-alt-f7.

Good luck.



__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/

On Tue, 1 May 2007 08:37:33 -0300 (ART)
Renato Gondim Filho <gondim2@yahoo.com.br> wrote:

> I tried the command '/etc/init.d/gdm restart && tail
> -f /var/log/Xorg.0.log', but it didn't work. The black screen
> appeared instead of the output.

Did you try ctrl-alt-f1 to return to the console from which you issued
the command?

> But looking at the Xorg.0.log, this
> message appears many times:
>
> (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
> directory)
>
> It could be this?

Unfortunately, no. It is just a warning that the X server cannot use
ACPI for power management.

>
> Thanks.
>
> Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Sun, 29 Apr 2007
> 11:15:47 -0300 (ART) Renato Gondim Filho wrote:
>
> > Sorry about my ignorance, some conventions I don't know well (yeat),
> > but "virtual console" means a command line in Terminal? If it´s
> > correct, I should do this:
> >
> > tail -f /var/log/Xorg.0.log
> >
> > Thanks.
>
> What I am suggesting is that you try the following.
>
> 1. Switch to a virtual console using the key combination ctrl-alt-f1.
> 2. Login as root.
> 3. Issue the command '/etc/init.d/gdm restart && tail
> -f /var/log/Xorg.0.log'. Here I assume that GDM is your display
> manager. 4. The previous step will probably take you to the login
> screen (even though the login prompt hasn't appeared). If so, repeat
> step 1 to return to the virtual console. 5. Watch the progress of
> output as you follow the log file. Is there a point at which the
> output pauses for a long time? 6. You can toggle to the login screen
> at any time using ctrl-alt-f7.
>
> Good luck.
>
>
>
> __________________________________________________
> Fale com seus amigos de graça com o novo Yahoo! Messenger
> http://br.messenger.yahoo.com/


--

Liam

Yes, but nothing heappens. I did the steps:

Turn on the computer;
The graphical login prompt appears;
Press ctrl+alt+F1;
Command line login appears;
Log as root;
Did the comand;
The black screen appears;
Pressed ctrl+alt+F1, many times, nothing heappeans;
The graphical login prompt appears again;
Pressed ctrl+alt+F1, the command line appears, with the text of the Xorg.0.log printted in the screen.
Repeat the command, many times, same result.

Thanks, again.

Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Tue, 1 May 2007 08:37:33 -0300 (ART)
Renato Gondim Filho wrote:

> I tried the command '/etc/init.d/gdm restart && tail
> -f /var/log/Xorg.0.log', but it didn't work. The black screen
> appeared instead of the output.

Did you try ctrl-alt-f1 to return to the console from which you issued
the command?

> But looking at the Xorg.0.log, this
> message appears many times:
>
> (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
> directory)
>
> It could be this?

Unfortunately, no. It is just a warning that the X server cannot use
ACPI for power management.

>
> Thanks.
>
> Liam O'Toole
escreveu: On Sun, 29 Apr 2007
> 11:15:47 -0300 (ART) Renato Gondim Filho wrote:
>
> > Sorry about my ignorance, some conventions I don't know well (yeat),
> > but "virtual console" means a command line in Terminal? If it´s
> > correct, I should do this:
> >
> > tail -f /var/log/Xorg.0.log
> >
> > Thanks.
>
> What I am suggesting is that you try the following.
>
> 1. Switch to a virtual console using the key combination ctrl-alt-f1.
> 2. Login as root.
> 3. Issue the command '/etc/init.d/gdm restart && tail
> -f /var/log/Xorg.0.log'. Here I assume that GDM is your display
> manager. 4. The previous step will probably take you to the login
> screen (even though the login prompt hasn't appeared). If so, repeat
> step 1 to return to the virtual console. 5. Watch the progress of
> output as you follow the log file. Is there a point at which the
> output pauses for a long time? 6. You can toggle to the login screen
> at any time using ctrl-alt-f7.
>
> Good luck.
>
>
>
> __________________________________________________
> Fale com seus amigos de graça com o novo Yahoo! Messenger
> http://br.messenger.yahoo.com/


--

Liam



__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/

On Tue, 1 May 2007 11:21:40 -0300 (ART)
Renato Gondim Filho <gondim2@yahoo.com.br> wrote:

> Yes, but nothing heappens. I did the steps:
>
> Turn on the computer;
> The graphical login prompt appears;
> Press ctrl+alt+F1;
> Command line login appears;
> Log as root;
> Did the comand;
> The black screen appears;
> Pressed ctrl+alt+F1, many times, nothing heappeans;
> The graphical login prompt appears again;
> Pressed ctrl+alt+F1, the command line appears, with the text of the
> Xorg.0.log printted in the screen. Repeat the command, many times,
> same result.

Ah, I see. Assuming you have not set the option 'DontVTSwitch' in
your /etc/X11/xorg.conf file, your X server is locking the keyboard
completely during this mysterious pause. Presumably the ability to
switch consoles returns after the login prompt, but by that time it is
not useful to you :-(

You mentioned before that the machine is not connected to the LAN, but
if you could connect it and start an SSH server, then you could login
remotely and monitor the log file from another machine.

Hopefully someone can advise you of other debugging options. It would
be ful for example if you could find a way of telling the X server
to write time stamps to the log file.

--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

I tried putting the follow along the xorg.conf:

date >> /tmp/res.txt

But didn't work.

I'll look for something like that, and tell the result.

Thanks!

Liam O'Toole <liam.p.otoole@gmail.com> escreveu: On Tue, 1 May 2007 11:21:40 -0300 (ART)
Renato Gondim Filho wrote:

> Yes, but nothing heappens. I did the steps:
>
> Turn on the computer;
> The graphical login prompt appears;
> Press ctrl+alt+F1;
> Command line login appears;
> Log as root;
> Did the comand;
> The black screen appears;
> Pressed ctrl+alt+F1, many times, nothing heappeans;
> The graphical login prompt appears again;
> Pressed ctrl+alt+F1, the command line appears, with the text of the
> Xorg.0.log printted in the screen. Repeat the command, many times,
> same result.

Ah, I see. Assuming you have not set the option 'DontVTSwitch' in
your /etc/X11/xorg.conf file, your X server is locking the keyboard
completely during this mysterious pause. Presumably the ability to
switch consoles returns after the login prompt, but by that time it is
not useful to you :-(

You mentioned before that the machine is not connected to the LAN, but
if you could connect it and start an SSH server, then you could login
remotely and monitor the log file from another machine.

Hopefully someone can advise you of other debugging options. It would
be ful for example if you could find a way of telling the X server
to write time stamps to the log file.

--

Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/