Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!ihz.compuserve.com!mfoley
From: mfoley@csi.compuserve.com (M Foley)
Subject: Re: 386bsd 0.1 Patchkit 0.2.4 - Problems, Questions
Message-ID: <CCALJn.JEF@csi.compuserve.com>
Organization: CompuServe Incorporated
Date: Wed, 25 Aug 1993 01:59:44 GMT
Lines: 110
Thanks to all who responded to my original message. I thought I would
take a moment to give some feedback about my result. Everyone was very
helpful (although one person felt the need to be snide - hint: if you
think the person/question is too stupid to answer, don't!). Anyway,
perhaps these results will help other people.
>1. When I build a new kernel, the vers.o was still missing ...
Most folks felt this was a result of my not doing the buildworld.sh
before making a new kernel. It's true, but my reading of the
instructions tells me to do it this way (doc. UPGRADE-0.2.3):
It is recommended that you follow these steps to rebuild your kernel
at this time:
rm -r /sys/compile/* #HIGHLY RECOMMENDED!
cd /sys/i386/conf
config YOUR_KERNEL_NAME
cd /sys/compile/YOUR_KERNEL_NAME
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync;
reboot
Please do this before attempting to run buildworld.sh
README README README README README README README README README README
Also, on subsequent builds after having (successfully) done the
buildworld.sh, I follow the above advice (rm -r /sys/compile/*, etc) and
still have to run /sys/conf/newvers.sh after make depend. The rm also
seems to remove whatever it is that 'vers' needs since I am perpetually
at version 0.1.2. Also, what should go in the parens? Patch level?
>2. I notice that the new /dev/MAKEDEV does not contain ttyp* devices. I
> accidently deleted mine since I wanted to run a new MAKEDEV to create
> my new com port nodes (the patch procedure only created com00). The
> ttyp*'s didn't make. Remote telnets seem to require ttyp* devices. ...
The respondant to this one felt that these would be made using MAKEDEV pty*.
Since I created mine by hand, I haven't tried remaking them.
>3. BIGGEST PROBLEM: When running buildworld.sh (for hours and hours),
> my system has stopped working twice now ...
The consensus was that I did not have enough swap space (since I was
using the default 5MB from Tiny BSD). True enough. I rebuilt my
partitions with a 12MB space and everything built find (and FAST).
>4. With the patchkit, I can now access my 2nd hard drive. BUT, I have a
> problem. I create a disklabel using "disklabel -R /dev/rwd1a 41mb" where
> '41mb' is a disklabel format file describing my 43MB Seagate 157A IDE
> drive. I then do "newfs -m 0 wd1" to create a file system - which works
> fine. I mount it, use it, etc. However, when I reboot and try to mount it
> again, I get a "BOGUS BOOT BLOCK" message and have to redo the label and
> recreate the file system all over. Why isn't the label/file system
> information 'sticking'? Any ideas?
I got this to work by putting an entry (seagate-157) in the disktab file
for this drive and using: disklabel -r -w wd1 seagate-157. However, the
confusing part is that when I build my disk initially from the Tiny BSD
boot disk, I don't need to have disktab, the syntax shown in 4. above
works!??
>5. When I boot, I now get many "strayintr ff" messages on the console. ...
No one really knew exactly. Some speculated that it was from the printer
driver (my printer IRQ is setup OK to 7, but no printer attached). Other
people thought it was from some unknown device which was dropping its
request line. Consensus: don't worry - be happy.
>6. I really want access to my new com2 (formerly com3), but I don't think
> I can set my board to IRQ 5. Can this IRQ be changed in the
> /sys/i386/conf/MACHINE file? Can I set it to IRQ 4 like my com0 or
> will this screw up com0 (i.e., must the devices be on separate IRQ's
> or is the driver smart enough to daisy-chain)?
Folks wrote that all serial ports must be on separate interupts. OK. I
now have: com00 - irq 5, com01 - irq 3, com02 - irq 4. In case people
are wondering about this arrangement, I have a modem card which can only
be IRQ 3 or 4. I have a mouse which I want to use for Xwindows and OS/2
(also on this machine). OS/2 requires COM1/3 IRQ 3, or COM2/4 IRQ 4 -
IRQs 2 and 5 are not options. So:
com00 IRQ 5 38400bd - Terminal port
com01 IRQ 3 - Mouse (coming soon!)
com02 IRQ 4 2400bd - modem
>7. There is now a directory and patch info for 'pcfs'. What is it? ...
PC file system. Works on floppies only now. Let me know when you get it
going for hard drive partitions. I'm perfectly happy with mtools for DOS
floppies.
>8. Question not related to the patch-kit: What should my '/etc/ttys' line
> say to specify a default com port baud rate of 13400? ...
Putting an entry with std.38400 and sp#38400 into the gettytab worked
fine. What I was really trying to determine was "is 38400 a valid speed
for gettytab?" and, by extension, "what are valid speeds for gettytab?"
I know some Unices I've worked on topped out at 19200. If anybody has an
answer, I would be academically interested. The "just do it" approach
worked. Sorry to have confused several of you by mistyping the speed as
13400!
Again, thanks for the help. I hope the feedback helps someone else.