From: Stefan Jeglinski <jeglin@4pi.com>
To: "Iain Sandoe" <iain@sandoe.co.uk>,
linux <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.2 USB and "mon>" (was Re: All 6 cards!!!)
Date: Tue, 6 Mar 2001 11:24:36 -0500 [thread overview]
Message-ID: <p04330100b6cabf67a3e4@[38.205.4.5]> (raw)
In-Reply-To: <20010306151708.54D722EFB4@apollo.valhalla.net>
> > 1. I get a "mon>" prompt on about half of the boots. And on half of
>> those, typing "x" exits me from mon and continues the boot. The rest
>> just hang. What is mon anyway? I've already seen reference to this on
>> the user list, not sure what the solution is...
>
>the kernel has "oopsed" - and dropped you into xmon (debugger). You can
>find out more by doing "?" to list the commands and getting a traceback and
>exception report.
>
>This will tell people where the problem lies.
OK, thanks.
> > 2. No USB mouse response in X. lspci -vv, in part, gives:
>
>> I can live with the mon, but not without my mouse. Any suggestions here?
>
>have you done the changes in /dev to accommodate the new input layer?
Yes, I was already running input layer on 2.2.18, with no problems.
AFAICT, there are no /dev changes for 2.4.2 if I had already done
them for 2.2.18, no?
Stefan Jeglinski
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-06 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 15:17 2.4.2 USB and "mon>" (was Re: All 6 cards!!!) Iain Sandoe
2001-03-06 16:24 ` Stefan Jeglinski [this message]
[not found] <p04330100b6ccd0a23c2c@[24.162.228.89]>
2001-03-08 11:45 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-03-07 9:18 Iain Sandoe
2001-03-06 16:30 Iain Sandoe
2001-03-06 14:59 Stefan Jeglinski
2001-03-06 16:55 ` Benjamin Herrenschmidt
2001-03-06 22:10 ` Michel Lanners
2001-03-06 23:06 ` Benjamin Herrenschmidt
2001-03-07 6:49 ` Michel Lanners
2001-03-07 12:19 ` Benjamin Herrenschmidt
2001-03-06 23:08 ` Benjamin Herrenschmidt
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='p04330100b6cabf67a3e4@[38.205.4.5]' \
--to=jeglin@4pi.com \
--cc=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).