Nikos Mouat (nikm@conjungi.com)
Fri, 2 Oct 1998 11:04:27 -0700 (PDT)
Hi..
I've been wrestling again today with the ANS500 and I've found a bug in
the dusers kernel.. I posted to the linux-ppc mailing list the other day
about this bug, and it appears to only show up in the dusers kernel..
My situation is this:
- I left the batery out all night, and came in this morning and
re-installed.
- I copied over the dusers kernel, and pdisk -i'd the internal disk
and cp -xa'd over the filesystem
- the entire /dev directory shows up with a 0 as the minor device
number!!!!
- when I try and mknod under the dusers kernel, the minor is either
wildly incorrect or zero, but mknod works fine under the distribution
kernel. Unfortunately I can't mv the device's over the to internal
disk.. argh.
What I need is a kernel that sees the internal disk with a working mknod.
I think the problems I was having with quik last time was not because
of a pdisk formating error but instead because the devices I was trying to
access were not correct device numbers..
One thing that I'm doing which has allowed be a fair level of sucess wrt
to DEFAULT CATCH's is I'm not touching any of the front panel buttons.
Instead I'm unplugging the power cord to turn it off, and using the
keyboard button to power up..
This archive was generated by hypermail 2.0b3 on Thu Dec 10 1998 - 16:55:56 PST