linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "David A. Gatwood" <dgatwood@deepspace.mklinux.org>
Cc: linuxppc-dev@lists.linuxppc.org, dorland@lords.com,
	hollis+@andrew.cmu.edu
Subject: Re: Floppy problems
Date: Sat, 20 Nov 1999 22:40:58 +0100	[thread overview]
Message-ID: <199911202140.WAA00815@appel.flower> (raw)
In-Reply-To: Your message of "Sat, 20 Nov 1999 10:52:37 PST." <Pine.LNX.3.96.991120105010.4129B-100000@deepspace.mklinux.org>


On Saturday, 20 November 1999, "David A. Gatwood" writes:

> > > It is very weird. Again, other G3 users, does your floppy drive work?
> > 
> > No, mine doesn't work either.  I've reported and asked several times here,
> > but never got replies (other than: use gdb.. duh)
> 
> Something to check: look inside and see what the drive used is.  As far as
> I know, it should be either the standard Panasonic or the mostly standard
> Mitsubishi, but if it's a different drive, there could be some issues.

Yes, it's a Mitsubishi.

> And again, you should try MkLinux and see if it can handle the drive so
> that if so, the LinuxPPC coders can use that as a working reference to see
> what's wrong in the drivers.  (Of course, if MkLinux doesn't work, there's
> probably a hardware bug, since we use Copland's floppy driver.)

Ok, I checked: it works fine under Mklinux. (must address as /dev/fd0H1440,
because fd0 is 'no such device'.  Also, X didn't work anymore, but these
maybe mk-newbe problems.)

On another unrelated note: while I was at it I tried to mount a
home-brew CD-ROM under Mklinux.  It failed gracefully, printing these
errors:

    <lev 2> block_read_reply: rdev 16:00 rsector 0x40 size 0x400 err=0x9c4=2500 "unknown error code" 
    isofs_read_super: bread failed, dev 16:00 iso_blknum 16 block 32 
    block_ioctl(dev=16:00, cmd=0x20001260) not implemented 

Trying to mount this particular CD-ROM under linuxppc-Q3's 2.2.6 or 2.3.23
freezes the kernel (not pingable, nothing in logs).

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien/      | http://www.lilypond.org/

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

  reply	other threads:[~1999-11-20 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-20 13:27 Floppy problems Jan Nieuwenhuizen
1999-11-20 18:52 ` David A. Gatwood
1999-11-20 21:40   ` Jan Nieuwenhuizen [this message]
1999-11-20 21:52     ` David A. Gatwood
1999-11-20 23:22       ` Jan Nieuwenhuizen
1999-11-20 23:37         ` David A. Gatwood
1999-11-24 16:20 ` Giuliano Pochini
1999-11-24 19:41   ` Jeff Hubbach
  -- strict thread matches above, loose matches on Subject: below --
1999-11-20  1:58 Eric Dorland
1999-11-20  3:20 ` Hollis R Blanchard
1999-11-20  3:45   ` David A. Gatwood
1999-11-20  5:53     ` Eric Dorland
1999-11-20  6:17       ` David A. Gatwood
1999-11-20  6:18         ` Eric Dorland

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=199911202140.WAA00815@appel.flower \
    --to=janneke@gnu.org \
    --cc=dgatwood@deepspace.mklinux.org \
    --cc=dorland@lords.com \
    --cc=hollis+@andrew.cmu.edu \
    --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).