*BSD News Article 12440


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: my bug list
Message-ID: <1993Mar9.202944.9745@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University  (Ogden, UT)
References: <1993Feb27.235240.7476@coe.montana.edu> <C34un3.Hp6@unix.portal.com>
Date: Tue, 9 Mar 93 20:29:44 GMT
Lines: 99

In article <C34un3.Hp6@unix.portal.com> mykes@shell.portal.com (mike myke schwartz) writes:
>Nate Williams (nate@cs.montana.edu) wrote:
>: Hmm, never seen this.  You might try to get one of the newer WD ethernet
>: driver's on ref..
>
>Can you be specific as to which driver, where on ref to get it, etc?

Get it out of the build tree for the kernel on ref... /sys/...

>: >4) My busmouse NEVER worked (ps/2 Microsoft mouse - a ms mouse that
>: >   plugs into a din plug in the back of the machine).  So I went
>: >   and bought a cheapo Compudyne 3 button mouse.  This mouse has
>: >   a switch on the bottom that says "Microsoft/Mouse Systems" and
>: >   XFree86-1.2 does NOT see the middle mouse button (the mouse has
>: >   3 obviously :)
>
>: Which way is the switch connected?  If it is in Microsoft mode, make
>: sure you have Microsoft in the mouse comment field in your Xconfig.
>: If it's mouse-systems, use the Logitech version.
>
>The mouse works.  It just doesn't recognize the MIDDLE mouse button.
>The switch is set to microsoft.  I will try going to Logitech and
>changing the switch...

Turn off 3rd button emulation in the Xconfig.

Also: the DIN port on the back of the machine is a mouse-port, *not* a
bus-mouse connector.  It works not through a bus-mouse interface, but
through the keyboard controller.  I don't think there is a driver for
it yet -- if there were it would be a "PS/2 style mouse", not a bus-mouse
driver.

>: >6) My Ethernet card requires a HARD reset each time I shutdown
>: >   using 'sync;shutdown -h now'.  The wd patch in the patchkit
>: >   mentions both that the patch forces Unix to assume a wd eth
>: >   card and something about checksums.  However, it still doesn't
>: >   get recognized after warm reboot.  Yeah, I've read the buglist -
>: >   but DOS manages to reset it, and so does OS/2.  It obviously
>: >   CAN be done.
>
>: They do things that Berkeley Unix avoids.
>
>Heh.  I suggested a fix :)  Can you be more specific as to why
>BSD can't be made to do the reset of the eth card?

It can;  however, it requires a change to the device interface for *all*
drivers; this requires waiting until a major revision of the OS for a
rerelease of all drivers.  Doing this as a patch is nearly impossible.
If this were to be done outside the scope of the 0.2 (or other official
release), I would be tempted to reimplement the configuration interface
almost entirely.

>: >8) This is a oddball bug...  I have 2 A3000's (Amiga) and a Sun
>: >   3/60 on a local ethernet with the Dell/BSD machine.  I have
>: >   all the network files configured correctly, at least I am
>: >   sure I have :)  I can mount either of the amiga's exports
>: >   from the Sun or the other amiga, but I get authentication
>: >   error when I try to do it from the Dell.  In short:
>: >   Amiga<->Amiga works, Amiga<->Sun works, Sun<->Dell works, BUT
>: >   Amiga<->Dell fails.  I've reported this problem to Commodore,
>: >   but they seem to think the problem is with the BSD networking
>: >   software.
>
>: Have you recompiled mountd?  Make sure you re-compile any files that
>: were changed in the patchkit.  I don't think that is the fix, but you
>: never know.
>
>Is there a nice file documenting all the things that need to be remade
>due to the patchkit changes?  I only remade my kernel.

The patches themselves document the changed files in their "INFO" pieces;
you should probably print these out; also note that there is a bug in UFS,
and if you replace any running images (like "init"), you will need to "mv"
the old image rather than overwriting it (O_CREAT fails to force an unlink
on non-0 reference count inodes vnode-p's).  In previous kits (ala 0.1) I
included a file listing these references.  I haven't checked the internals
of the 0.2 kit (I trust Nate), but I suspect there is an equivalent.

The "oddball" bug you are having with the Amiga's authentication errors
has to do with the fact that you aren't using a reserved port for the
source request on the 386BSD as a client.  You show "Amiga<->Dell fails"
implying you get the same error trying to mount the Dell's disks from
the Amiga, or is this just a typo?

The priveleged port patches to NFS should be in the patchkit; perhaps
there's an RPC problem on the Amiga side?


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------