From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Debian Sid startup problems
Date: Fri, 11 Jun 2004 22:08:09 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20040611215205.01faf760@celine> (raw)
In-Reply-To: <Pine.LNX.4.58.0406112327150.1396@debian-emach>
At 11:36 PM 6/11/2004 -0500, James Miller wrote:
>On Fri, 11 Jun 2004, James Miller wrote:
>
> > PS I can still boot from a 2.4.x kernel on the system - though I'll be
> > without mouse support. Maybe I should try that?
>
>This is really wierd. Here I am, booted into a normally-working x
>session, having started the computer with the 2.4.25 kernel. I don't know
>what to think of this. I got to a command prompt, as I was getting to
>under the 2.6.5 kernel after taking Ray's advice about renaming
>/etc/rc2.d/S99xdm so it wouldn't boot into graphical mode. When I logged
>in and issued startx, the window manager fired up normally. No blank
>screen with "no signal" on it or anything. Just the same old gui I've
>been using these last few months (and the mouse even works!). Maybe I'm
>entering the twilight zone or something . . . Anyway, enough for tonight.
>I'm going to bed on this one. Maybe tomorrow I'll try this again with the
>2.6.5 kernel. Maybe I'll upgrade xfree. Suggestions welcome.
Putting all of this together ... "all" meaning this message and several
that preceded it ... leaves me suspecting some sort of kernel bug involving
a conflict between vesafb (yes, this is the framebuffer) and one of the usb
modules. Or possibly one of the usb modules and some other kernel feature,
like MTRR, that X uses.
To test this theory, I'd suggest rebooting to a console, disabling
installation of the various usb modules, rebooting, and seeing if startx
now works to get X running.
If it does now work, you've found the problem. To get it fixed, you need
someone with 2.6.x kernel expertise, and that's not me (I still run 2.4.24
or thereabouts).
If it doesn't now work ... I'm sorry to say that all the information you've
provided doesn't suggest any other ideas to me. Except checking the logged
STDERR output, as I previously suggested.
BTW, I can't tell you how to disable installation of the usb modules,
because Debian installs modules in several different ways, and I don't know
which of them gets used for the usb stuff.
They might be listed in /etc/modules . If so, comment them out.
They might be installed via init scripts. If so, find their symlinks in
rc2.d or rcS.d and change them the way you did S99xdm.
They might be loaded some way I'm not thinking of. Check the docs for the
lackage if neither of my earlier suggestions pans out (and you don't
already know the answer, of course).
-
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 5:08 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
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 [this message]
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.20040611215205.01faf760@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