From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Debian Sid startup problems
Date: Fri, 11 Jun 2004 18:55:41 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20040611183923.01fc9dc0@celine> (raw)
In-Reply-To: <Pine.LNX.4.58.0406111946550.2199@debian-emach>
At 08:05 PM 6/11/2004 -0500, James Miller wrote:
>Thanks for your input, Ray.
For the most part, I'm going to wait to think more about this until you
report the result of the telnet test. Also, since your problem does seem to
be specific to X, you should round up the usual suspects here ...
what kernel? Debian stock or compiled by you?
what video hardware (card and monitor)?
what X server (I saw a passing reference to radeon in the log
output, but please confirm this)?
am I correct in thinking (from the radeon reference) that you are
using a framebuffer in the kernel?
Check the timestamp on /etc/X11/XF86Config-4 to make sure it hasn't been
changed more recently than you think it should have been.
Debian normally is set up to log X's STDERR output to /var/log/XFree86.log
Check there, rather than in /var/log/mesages, for the details of whatever
problems X is finding.
In connection with the usb* installs, did you do an apt-get update/upgrade
(or dist-upgrade) of the system? If yes, is it possible that doing so
changed some of your X settings (by a new xserver-xfree86 package rewriting
/etc/X11/XF86Config-4, which would cause you to lose any changes you made
by hand ... that is, outside the debconf method)
As to usb modules ... since we only care about them if they are running,
use "lsmod" to check that.
>On Fri, 11 Jun 2004, Ray Olszewski wrote:
[deleted]
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-06-12 1:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 21:01 Debian Sid startup problems James Miller
2004-06-11 23:15 ` Ray Olszewski
2004-06-12 1:05 ` James Miller
2004-06-12 1:55 ` Ray Olszewski [this message]
2004-06-12 2:21 ` James Miller
2004-06-12 3:12 ` James Miller
2004-06-12 4:36 ` James Miller
2004-06-12 5:08 ` Ray Olszewski
2004-06-12 16:20 ` James Miller
2004-06-12 18:04 ` chuck gelm
2004-06-12 18:10 ` James Miller
2004-06-12 18:47 ` James Miller
2004-06-12 18:32 ` Ray Olszewski
2004-06-12 19:04 ` James Miller
2004-06-12 19:27 ` Ray Olszewski
2004-06-12 19:50 ` James Miller
2004-06-12 22:36 ` net (& module, I guess) problems after dist-upgrade James Miller
2004-06-13 3:57 ` Ray Olszewski
2004-06-14 15:01 ` James Miller
2004-06-14 16:35 ` Ray Olszewski
2004-06-14 17:33 ` James Miller
2004-06-14 18:06 ` James Miller
2004-06-14 18:50 ` Ray Olszewski
2004-06-14 19:13 ` James Miller
2004-06-14 22:44 ` James Miller
2004-06-14 19:25 ` pa3gcu
2004-06-13 4:43 ` joy
2004-06-12 1:36 ` Debian Sid startup problems James Miller
2004-06-12 2:07 ` Ray Olszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.1.20040611183923.01fc9dc0@celine \
--to=ray@comarre.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox