Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2372 ; Mon, 01 Mar 93 10:56:30 EST Newsgroups: comp.os.386bsd.bugs Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: my bug list Message-ID: <1993Feb28.011327.13900@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: Dept. of Computer Science, MSU, Bozeman Mt 59717 References: <1993Feb27.235240.7476@coe.montana.edu> <C34un3.Hp6@unix.portal.com> Date: Sun, 28 Feb 1993 01:13:27 GMT Lines: 165 In article <C34un3.Hp6@unix.portal.com> mykes@shell.portal.com (mike myke schwartz) writes: >Nate Williams (nate@cs.montana.edu) wrote: >: In article <C33u2A.Ap0@unix.portal.com> mykes@shell.portal.com (mike myke schwartz) writes: >: >I run a Dell 486D/50, 2 IDE drives, Adaptec SCSI controller, CD ROM >: >drive, PAS16 audio card, and WD8013 (Elite 16) eth card. > >: >Here is a summary of the bugs in my system that I have noticed so >: >far: >: > >: >1) I get mb_map full errors to the console when accessing an NFS >: > mounted SUN 3/60 (sunos 4.1.1) drive over ethernet. This randomly >: > trashes the files involved, or does not do the file access at all >: > (i.e. a copy from/to the Sun fails altogether). > >: 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? Nope, I don't have a WD card, but I understand there are others out there. >: >3) the IRQ for my Adaptec SCSI controller is at 10. I modified my >: > /sys/i386/conf/DELL file to reflect IRQ 10 instead of IRQ 11. >: > I only have the CDROM drive connected, and it is SCSI ID 4, >: > LUN 0. The CDROM is not recognized. > >: Are you using Julian's SCSI drivers? If not, as far as I can remember >: it will not notice on bootup, but it will connect to the drive the first >: time you access the device. > >I just found the scsi drivers (again, people mention them but NEVER >say where to get them). If I install these drivers, it looks like >I will be out of luck with respect to the patchkit stuff, which is >VERY COOL. Will I be able to back out old patches after installing >these? Since they are patches, you should be able to use patch -R on the patch files, and they should back out. Or, you could wait for the new patches Jordan is going to release that will integrage the SCSI drivers into the patchkit. No release date. >: >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. > >: Also, make sure the mouse works by using kermit to connect to >: the port and move your mouse around. > >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... Microsoft mice don't have middle buttons. > > >: >5) I managed to get a whereis.db file made. However, man-k still >: > fails because some of the lines in whereis.db are too long. > >: Hmm, can you give examples of this. > >I think I did a makewhereis from the /usr/othersrc tree (somewhere). >I now have a whereis.db... BUT: > >dell 1 # man -k mouse >apropos: /usr/share/man/whatis.db line too long. Did you apply patch00504? If not, do, and re-make whatis.db. >: > >: >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? Terry L. made a good case of it a while back. I don't remember the details, other than 'It doesn't work'. Sorry >: >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. /patch/FILES* is a listing of all files that have changed. Everything that depends on those files should be re-compiled (which, in all honesty is the entire system). However, your best bet is to re-compile everything that you can, and hope for the best. Hopefully we can figure out a better way of patching things, but for now you get what you pay for. :-) > >I have 16M of real ram (I mentioned that the 32M swap partition is 2x >my real RAM in the original post). Is someone working on this problem? I can't glean that much information on a quick reading. Anyway, yes, Bill is working on the problem. 0.2 is a fix to the VM system. Anything after that is pure speculation on my part. >: >2) The faq's I've found seem to all be from last year sometime... > >: I did one of them, and haven't had the time to update it. If you >: got some free time, you're welcome to update them. :-) > >Hey, I said MINOR nits :) and you wouldn't want me to update them - >at least not until I am a real unix wizard instead of just a wizard >in training :) I'm no wizard, just a warm body that knows a bug when I see it. I did the same thing you're doing now, and figured someone else would benefit from the same knowlege I was getting, so I organized it for everyone else to have. >: >3) The vers.o patch is not exactly documented correctly. You need >: > to do 'make newvers' in the ../compile/DELL directory. I mention >: > it in case the right person sees this and fixes the docs :) >: > >: It's not documented at all. You need to re-make config, install it, >: config your kernel, make depend in your MACHINENAME directory >: and vers.o will be updated. You DO NOT NEED TO DO A make newvers. > >I did remake config. I did install it. I did config the kernel. >I did make depend in my DELL directory. vers.o was NOT updated. >I got: >ld: vers.o not found Hmm, strange. Try removing your /sys/compile/DELL directory, and start from scratch. It's possible that something funky got left from before the patch. I have NEVER had to do a make newvers since 0.1 patchkit. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom