linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: benh@kernel.crashing.org
To: Stefan Piger <piger@rvs.uni-hannover.de>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Again with the firewire
Date: Thu, 22 Nov 2001 11:59:13 +0100	[thread overview]
Message-ID: <20011122105913.4639@mailhost.mipsys.com> (raw)
In-Reply-To: <1006413308.947.0.camel@grobi>


>
>After loading the modules, there is no /proc/ohci1394 as I remember from
>earllier versions of linux1394.
>When I plug in a firewire device the keyboard becomes unusable, but the
>machine doesn't crash, I can reboot it via ssh.
>I get no error messages in /var/log/messages.
>
>Do you have any idea why it doesn't work? I tried the same on a friends
>Pismo an had the same effects!

Forget about /proc/ohci1394, it was bogus anyway.

Since you can log via ssh, can you send me the dmesg log that gets
displayed when you plug your device ? Eventulally, compile with the
excessive debugging output enabled in .config, and send me a log
with that too.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-11-22 10:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  7:15 Again with the firewire Stefan Piger
2001-11-22  8:28 ` Derrik Pates
2001-11-22 11:00   ` benh
2001-11-22 15:18     ` Derrik Pates
2001-11-22 18:21   ` Benjamin Herrenschmidt
2001-11-24  2:08     ` Derrik Pates
2001-11-24 12:21       ` Benjamin Herrenschmidt
2001-11-24 23:32         ` Derrik Pates
2001-11-22 10:59 ` benh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-21 16:09 mocm
2001-11-21 18:27 ` benh
2001-11-22  6:31   ` Derrik Pates

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=20011122105913.4639@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=piger@rvs.uni-hannover.de \
    /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).