From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.4.0-t8 (dumb question & two crashes)
Date: Wed, 20 Sep 2000 16:38:12 +0100 [thread overview]
Message-ID: <200009201537.QAA05334@hyperion.valhalla.net> (raw)
OK...
I don't seem to be able to get modprobe to work on 2.4.0-t8 unless I move
the modules from where the build puts them into their old positions.
According to rpmfind I have the latest modutils... where am I going wrong?
====
It crashes (not got output from xmon yet) on my 9600 on reboot [don't know
where]
crashes on G3/beige on reboot (ditto on xmon output) but this time I'm
fairly sure it only crashes when it has an unknown USB device on the bus (an
epson styluscan 2500) - seems OK if the printer is switched off.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-20 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-20 15:38 Iain Sandoe [this message]
2000-09-20 15:48 ` 2.4.0-t8 (dumb question & two crashes) Michel Dänzer
2000-09-20 19:38 ` Martin Costabel
-- strict thread matches above, loose matches on Subject: below --
2000-09-20 21:05 Iain Sandoe
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=200009201537.QAA05334@hyperion.valhalla.net \
--to=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).