Re: problem with plip stealing clock
Peter Jeremy wrote: > > On 2001-Apr-30 08:29:31 -0700, John Merryweather Cooper <[EMAIL PROTECTED]> >wrote: > >While using my main workstation as a local FTP for my laptop over plip, > >I noticed that FreeBSD was losing track of time at a prodigious rate. > > PLIP receives/transmits each IP packet inside a loop at splhigh(). > If either system is slow, or the MTU is too high, the time taken to > transfer each packet can exceed 1 tick - meaning that clock interrupt > is lost. Other PIO peripherals (ethernet or disk) will aggravate the > problem. I suspect transfering between a AMD Duron 700 and an Intel 386SX/20 qualifies . . . :) Couldn't the plip interface arbitrate this though by driving it's "bus" cycle at the pace of the slowest system? I'm sure, in practice, that the rarest use of plip is between two machines of nearly equal CPU speed. Probably, my use is fairly typical. If my damn laptop had a network port, I'd use that--but the Token Ring 16/4 Adapter seems as rare a gold for my ancient AST Premium Exec 386SX/20 . . . :) Probably wouldn't work with FreeBSD anyway . . . bummer. > I did have the problem with PLIP between my 386 laptop and 486 desktop > until I reduced the MTU to 512. Anything "magical" about 512 (or is lower better here). If lower is better, how low can I go (I guess I'll find out). > Have you considered using a PPP link running at 115.2kbps instead? > You will find it a lot more CPU friendly. Yes. Not looking forward to buying yet another single-purpose cable. The null modem I have doesn't seem to do the trick anymore. > Peter > jmc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Next STABLE release going to be 4.4?
(makes note to request [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall error
-BEGIN PGP SIGNED MESSAGE- On Mon, 30 Apr 2001, Chris Byrnes wrote: > awww# pwd > /usr/src/release/sysinstall > awww# make all depend install > Warning: Object directory not changed from original /usr/src/release/sysinstall > make: don't know how to make sysinstall.1. Stop > awww# Your world is out of date. There has been some changes to /usr/share/mk/* that will prevent manual pages from building if your source tree is more up to date than your world. - --- Christopher Shumway [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBOu7lLBy/2UU0h5d1AQGA8wP/Yit/JLgfgCtkOSWw5K5ESnrAMe17kejo Zu1PVJAqr6GFPINfKormSeaH21I4EJJ51x9wjUh2oyGDm5fIVyDpocxndPUbr1bg HHCnRkzjq8HOvsvnyQNyMxJFGxgktHGuMTK0D4q+pq3G4CPV3fM9bkJ9EneniTY/ DLKWXnTRb9s= =4R68 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: tail
On Tue, May 01, 2001 at 07:30:18AM +0200, Steve O'Hara-Smith wrote: > JS> Not sure about this; if you e.g. vi a directory, it will warn you that it > > It is dangerous to vi a directory, but it is not dangerous to tail > one. More to the point, opening a directory for writing is an error. Since you normally use an editor to modify files, instead of just viewing them, it makes sense that vi warns you that you won't be able to write back your changes. It would not make sense for tail to warn you, because it only reads files. wopr:~$ perl -e 'open SPORK, ">tmp/" or die "$!"' Is a directory at -e line 1. wopr:~$ perl -e 'open SPORK, "tmp/" or die "$!"' wopr:~$ (See also "man 2 open".) -- Matthew Hunt <[EMAIL PROTECTED]> * Clearly there are more things in the http://www.pobox.com/~mph/ * heavens than anyone anticipated. -enp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall error
Thanks. I re-built /usr/src/share/mk/* and all went well. Chris Byrnes <[EMAIL PROTECTED]> JEAH Communications, LLC. Toll-Free <1-866-AWW-JEAH> On Tue, 1 May 2001, Christopher Shumway wrote: > -BEGIN PGP SIGNED MESSAGE- > > On Mon, 30 Apr 2001, Chris Byrnes wrote: > > > awww# pwd > > /usr/src/release/sysinstall > > awww# make all depend install > > Warning: Object directory not changed from original /usr/src/release/sysinstall > > make: don't know how to make sysinstall.1. Stop > > awww# > > Your world is out of date. There has been some changes to /usr/share/mk/* that > will prevent manual pages from building if your source tree is more up to date > than your world. > > - --- > Christopher Shumway [EMAIL PROTECTED] > > -BEGIN PGP SIGNATURE- > Version: 2.6.3ia > Charset: noconv > > iQCVAwUBOu7lLBy/2UU0h5d1AQGA8wP/Yit/JLgfgCtkOSWw5K5ESnrAMe17kejo > Zu1PVJAqr6GFPINfKormSeaH21I4EJJ51x9wjUh2oyGDm5fIVyDpocxndPUbr1bg > HHCnRkzjq8HOvsvnyQNyMxJFGxgktHGuMTK0D4q+pq3G4CPV3fM9bkJ9EneniTY/ > DLKWXnTRb9s= > =4R68 > -END PGP SIGNATURE- > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.3 Release: PPP problem
Hi, I am writing to report that there are some problems with the ppp on 4.3 release. My box couldn't complete the login procedure with my DSL provider. There is no such ppp problem before I cvsup to 4.3 release from 4.3 beta. Currently, I have to cvsup back to 4.3 beta to resolve this problem (*default date = 2001.03.20.00.00.00.00. The same problem occurs with 4.3 RC (date=2001.04.01.00.00.00.00). Hence, I suspect this ppp (pppoe + netgraph) problem was introduced when 4.3 beta was patched to 4.3 RC. I use this freebsd box as internet gateway, and hence ppp, ppp nat, netgraph, sshd & ipfilter are used. NIC is 3Com 3C905B. This ppp problem is resolved after I rebuilt from the 4.3 beta source tree. The rc.conf, kernel conf and ppp log are attached at the end. FYI -echelon rc.conf: (abstract only) gateway_enable="YES" sshd_enable="YES" ipfilter_enable="YES" ppp_enable="YES" ppp_mode="auto" ppp_nat="YES" kernel conf: (abstract only) options NETGRAPH options NETGRAPH_ETHER options NETGRAPH_PPPOE options NETGRAPH_SOCKET Here is the ppp.log (abstract only) May 1 05:30:01 host ppp[111]: Phase: bundle: Establish May 1 05:30:01 host ppp[111]: Phase: deflink: closed -> opening May 1 05:30:01 host ppp[111]: Phase: deflink: Connected! May 1 05:30:01 host ppp[111]: Phase: deflink: opening -> dial May 1 05:30:01 host ppp[111]: Chat: deflink: Dial attempt 1 of 1 May 1 05:30:01 host ppp[111]: Phase: deflink: dial -> carrier May 1 05:30:06 host ppp[111]: Phase: deflink: Disconnected! May 1 05:30:06 host ppp[111]: Phase: deflink: carrier -> hangup May 1 05:30:06 host ppp[111]: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out May 1 05:30:06 host ppp[111]: Phase: deflink: : 119162 packets in, 90998 packets out May 1 05:30:06 host ppp[111]: Phase: total 0 bytes/sec, peak 0 bytes/sec on Tue May 1 05:30:06 2001 May 1 05:30:06 host ppp[111]: Phase: deflink: hangup -> closed May 1 05:30:06 host ppp[111]: Phase: bundle: Dead May 1 05:30:11 host ppp[111]: Phase: bundle: Establish May 1 05:30:11 host ppp[111]: Phase: deflink: closed -> opening May 1 05:30:11 host ppp[111]: Phase: deflink: Connected! May 1 05:30:11 host ppp[111]: Phase: deflink: opening -> dial May 1 05:30:11 host ppp[111]: Chat: deflink: Dial attempt 1 of 1 May 1 05:30:11 host ppp[111]: Phase: deflink: dial -> carrier May 1 05:30:16 host ppp[111]: Phase: deflink: Disconnected! May 1 05:30:16 host ppp[111]: Phase: deflink: carrier -> hangup May 1 05:30:16 host ppp[111]: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out May 1 05:30:16 host ppp[111]: Phase: deflink: : 119162 packets in, 90998 packets out May 1 05:30:16 host ppp[111]: Phase: total 0 bytes/sec, peak 0 bytes/sec on Tue May 1 05:30:16 __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Strange BTX halted error
I have an N440BX motherboard that, when using console redirection (so the BIOS messages and such come over the serial port), displays the following: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 635kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Wed Oct 4 15:01:32 PDT 2000) Loading /boot/defaults/loader.conf int=000d err= efl=00010216 eip=5a6c eax=ff08428b ebx=760c ecx= edx=00030160 esi=00037788 edi=00093468 ebp=00093258 esp=00093258 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=89 11 83 40 08 04 c9 c3-55 89 e5 8b 45 08 8b 48 ss:esp=98 32 09 00 d8 91 00 00-8b 42 08 ff 60 01 03 00 BTX halted I was wondering if anyone else has seen this. The problem seems somewhat intermittent. It doesn't *always* happen but it often does. If I hit the reset switch, it seems to boot reliably from there. This system (actually systems. It's more than one so I know it's not hardware) booted perfectly until I enabled the console redirection. Nothing on the box has changed other than that. Any ideas? I'm stumped. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange BTX halted error
I had the exact same problem when I had 'SCSI Bios' enabled on my Adaptec 2940. Turned it off and that stopped. Not sure what the problem is, but I know that is the solution for me :) Marc On Tue, 1 May 2001, Gordon Tetlow wrote: > I have an N440BX motherboard that, when using console redirection (so the > BIOS messages and such come over the serial port), displays the following: > > BTX loader 1.00 BTX version is 1.01 > Console: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 635kB/523200kB available memory > > FreeBSD/i386 bootstrap loader, Revision 0.8 > ([EMAIL PROTECTED], Wed Oct 4 15:01:32 PDT 2000) > Loading /boot/defaults/loader.conf > > int=000d err= efl=00010216 eip=5a6c > eax=ff08428b ebx=760c ecx= edx=00030160 > esi=00037788 edi=00093468 ebp=00093258 esp=00093258 > cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 > cs:eip=89 11 83 40 08 04 c9 c3-55 89 e5 8b 45 08 8b 48 > ss:esp=98 32 09 00 d8 91 00 00-8b 42 08 ff 60 01 03 00 > BTX halted > > I was wondering if anyone else has seen this. The problem seems somewhat > intermittent. It doesn't *always* happen but it often does. If I hit the > reset switch, it seems to boot reliably from there. > > This system (actually systems. It's more than one so I know it's not > hardware) booted perfectly until I enabled the console redirection. > Nothing on the box has changed other than that. > > Any ideas? I'm stumped. > > -gordon > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange BTX halted error
Well, that's not going to work, as I don't have an Adaptec and I need the onboard SCSI to boot =/ Thanks for the help though. If someone can decipher what all the register's mean, I can provide access to the boot loader binary and source (4.1.1-RELEASE I believe). -gordon On Tue, 1 May 2001 [EMAIL PROTECTED] wrote: > I had the exact same problem when I had 'SCSI Bios' enabled on my > Adaptec 2940. > > Turned it off and that stopped. Not sure what the problem is, but I > know that is the solution for me :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange BTX halted error
:Well, that's not going to work, as I don't have an Adaptec and I need the :onboard SCSI to boot =/ Thanks for the help though. If someone can :decipher what all the register's mean, I can provide access to the boot :loader binary and source (4.1.1-RELEASE I believe). : :-gordon : :On Tue, 1 May 2001 [EMAIL PROTECTED] wrote: : :> I had the exact same problem when I had 'SCSI Bios' enabled on my :> Adaptec 2940. :> :> Turned it off and that stopped. Not sure what the problem is, but I :> know that is the solution for me :) I was getting BTX halted failures due to BIOS confusion related to dangerously dedicated partitions. It's what prompted me to fix the disklabel code to allow boot blocks to be installed on slices. Unfortunately, the only way I could fix my particular problem was to get rid of my dangerously dedicated partition which meant blowing away the hard drive and repartitioning and relabeling it. The very last example, just before the SEE ALSO section for the 'disklabel' manual page shows how to do this. But be warned: it blows away the disk. http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&apropos=0&sektion=0&manpath=FreeBSD+4.3-RELEASE&format=html I do not know if my problem is the same as yours, so this could be all for nothing. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange BTX halted error
:The very last example, just before the SEE ALSO section for the :'disklabel' manual page shows how to do this. But be warned: it blows :away the disk. : : :http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&apropos=0&sektion=0&manpath=FreeBSD+4.3-RELEASE&format=html : opps, in the above manual page it is the example-before-last. In the 4.x manual page it is the last example. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange BTX halted error
No, we don't use dangerously dedicated since the word "dangerous" was in it. Figured it might not be a good thing =) Thanks though. -gordon On Tue, 1 May 2001, Matt Dillon wrote: > I was getting BTX halted failures due to BIOS confusion related to > dangerously dedicated partitions. It's what prompted me to fix the > disklabel code to allow boot blocks to be installed on slices. > > Unfortunately, the only way I could fix my particular problem was > to get rid of my dangerously dedicated partition which meant blowing > away the hard drive and repartitioning and relabeling it. > > The very last example, just before the SEE ALSO section for the > 'disklabel' manual page shows how to do this. But be warned: it blows > away the disk. > > >http://www.FreeBSD.org/cgi/man.cgi?query=disklabel&apropos=0&sektion=0&manpath=FreeBSD+4.3-RELEASE&format=html > > I do not know if my problem is the same as yours, so this could be all > for nothing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SoundBlaster PCI 128
On Mon, 30 Apr 2001, Dave Uhring wrote: > Honestly, I simply put the line > > devicepcm > > into my KERNCONF file and don't even know how to load kernel modules. My > system even has an on-the-motherboard via-686a sound chip and it works > perfectly - well, almost. I think something that's /possibly/ being overlooked here is that some, myself included, who had perfectly-working sound before... now do not. I've got the proper lines in my kernel config, I've remade all my devices, yet the same config that worked in the previous STABLE now does not. It seems obvious something changed, just not sure what. Later, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
