network interface dies randomly - ifconfig down then up fixes
I have a Arris Cornerstone CM200 cable modem connected to my FreeBSD stable (cvsupped last week) box via UTP into a NE2000 compatible ISA Ethernet adaptor. The connection randomly dies. I can send pings out of it and see the Activity LED flash on the modem but the FreeBSD box never sees any replies. Doing ifconfig ed1 down followed by ifconfig ed1 up fixes it. It's been happening for about the last two weeks (so it happened before the most recent cvsup also). Does anybody have any suggestions? Thanks for any help, Graham To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Burncd errors...
On Wed, Oct 31, 2001 at 07:51:37PM -0800, Mikko Tyolajarvi wrote: In local.freebsd.stable you write: I'm trying to write a small audio file to a CD. Burncd refuses to do it... for instance... if I do something like: burncd -f /dev/acd0c -s 1 audio audio.raw fixate [...] Oct 31 21:45:18 endymion /kernel: acd0: WRITE_BIG - ILLEGAL REQUEST asc=64 ascq=00 error=00 [...] I cannot issue the msinfo or blank commands either. Any data files (data, XAmode1, mode2) are written correctly and flawlessly. The only reference I could find to errors similar to these were on NetBSD under different circumstances and with a Yamaha burner on FreeBSD. The FreeBSD reference mentioned bugs in the ATA driver that'd be fixed in 4.4-STABLE (which I'm running... cvsupped as of Sept 27th)... The burner is: acd0: CD-RW LG CD-RW CED-8080B at ata1-master using PIO4 Not that it is any help to you, but I have the same problem (data burns ok, audio does not) with an 8083B. And apparently we're not alone: http://www.freebsd.org/cgi/query-pr.cgi?pr=27893. My solution? I bought a Plextor. When I had this problem, I found that it was fixed by a cvsup/buildworld/installworld/newkernel cycle -- in the correct order. I was using a Sony CRX-140S SCSI burner at the time, and still am. Works fine now. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: network interface dies randomly - ifconfig down then up fixes
On Thu, Nov 01, 2001 at 10:39:33PM +1100, Graham Menhennitt wrote: I have a Arris Cornerstone CM200 cable modem connected to my FreeBSD stable (cvsupped last week) box via UTP into a NE2000 compatible ISA Ethernet adaptor. The connection randomly dies. I can send pings out of it and see the Activity LED flash on the modem but the FreeBSD box never sees any replies. Doing ifconfig ed1 down followed by ifconfig ed1 up fixes it. It's been happening for about the last two weeks (so it happened before the most recent cvsup also). It could be your cable provider doing things on their network. I have found that they are fond of making changes during prime time daylight, rather than in the wee hours, and most of their changes require me to reset my cablemodem (power cycle). If your /var/log/messages shows things like your upstream gateway MAC address changing (I run arpwatch, so I see that), then that has a high probability of being the problem. If not, then you may need to run tcpdump continuously on that interface to catch the ACK and SYN packets. I do that, too, so that I can trace attacks, but I do computer security for a living and hence am a professional paranoid. -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make buildworld dies
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1 Thanks for the reply. At first I thought this would fix the problem,but it didn't. I am cvsupíng with the stable-supfile profided bycvsup. I am using cvsup version SNAP_16_1e. It is still giving methe same error. Here are the last 30 lines from the buildworld log. Let me know if you need more. cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth-options.c cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/session.c cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth-chall.c cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth2-chall.c cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth-pam.c /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth-pam.c: Infunction `do_pam_conversation': /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/auth-pam.c:128:warning: passing arg 1 of `read_passphrase' discards qualifiers frompointer target type cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login/login_access.c cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c/usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/groupaccess.c cc -nostdinc -O -pipe -DLIBWRAP -DHAVE_LOGIN_CAP -DLOGIN_ACCESS- -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM- -DHAVE_PAM_GETENVLIST -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"- -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -o sshd sshd.oauth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o sshpty.osshlogin.o servconf.o serverloop.o auth.o auth1.o auth2.oauth-options.o session.o auth-chall.o auth2-chall.o auth-pam.ologin_access.o groupaccess.o -lopie -lmd/usr/obj/usr/src/secure/usr.sbin/sshd/../../lib/libssh/libssh.a- -lcrypt -lcrypto -lutil -lz -lwrap -lpam gzip -cn /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/sshd.8 sshd.8.gz === etc === etc/sendmail make: don't know how to make freebsd.mc. Stop *** Error code 2 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. - -Mike Loiterman [EMAIL PROTECTED]- -- - Original Message - From: Kent Stewart To: Mike Loiterman Cc: [EMAIL PROTECTED] Sent: Wednesday, October 31, 2001 5:13 PMSubject: Re: make buildworld dies Mike Loiterman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm sure I'm doing something stupid here, but I simply can't figure out what. I've searched all over google, yahoo, deja.com and the bsd archives, but I am baffled by this. What did you cvsup from and what options are you using on the cvsup.Also what version of cvsup are you using? To find out the version do"cvsup -v". If you aren't using 16.11d or higher, that could be yourproblem. You can get a fixed version at http://people.freebsd.org/~jdp/s1g/ I just cvsup'ed to 4.4-STABLE and I followed the handbook instructions exactly in terms of doing make buildworld, but I keep getting this error when I do the make buildworld... make: don't know how to make freebsd.mc. Stop *** Error code 2 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src I have logged the entire output of make
Re: make buildworld dies
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1 I have and have had a copy of freebsd.c in /etc/mail. I do not have an /etc/make.conf. I have a /etc/defaults/make.confand the line SENDMAIL_MC=/etc/mail/myconfig.mc is commeneted out inthis file. There is no reference to SENDMAIL_CF in/etc/defaults/make.conf. I don't understand why I am having theseproblems...I did a build, install cycle the other day on this verymachine without any problems, but I ended up wiping the system andstarting over clean. I can't figure this out. I guess I will try to uncomment NO_SENDMAIL=true and build andinstall from there. - -Mike Loiterman [EMAIL PROTECTED]- -- - Original Message - From: Glen Foster To: Mike Loiterman Sent: Thursday, November 01, 2001 7:08 AMSubject: Re: make buildworld dies Here are some things that should make the error go away, any one ofthem should work, use whichever seems most convenient: Make sure you have a copy of freebsd.mc in /etc/mail, it used to bein/usr/src/etc/sendmail/. Run the build again (actually, make- -DNOCLEANshould be fine and speed things up considerably). Check your /etc/make.conf and /etc/defaults/make.conf file for anyreference to SENDMAIL_MC or SENDMAIL_CF (the latter is nowdecprecatedbut maybe not on the system that you are working with). Set NO_SENDMAIL=true in /etc/make.conf, build, install, mergemaster,take it out and build and install again. Backup your /etc directory, run mergemaster to update it, then trythebuild again. -BEGIN PGP SIGNATURE-Version: PGPfreeware 7.0.3 for non-commercial use http://www.pgp.comComment: Digitally signed by Mike Loiterman iQA/AwUBO+FP+3J6B0BI4qMYEQLzPgCg7UXH+r4BkElzvb+aKxNTogtuGjoAoObCCH3ERQVmUEKzvIbbjxkgJbDc=leIp-END PGP SIGNATURE-
Re: make buildworld dies
Did you happen to use the example cvsup refuse file? Cause there's a line there that says to refuse the very file that you're referring to. Mike Loiterman writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have and have had a copy of freebsd.c in /etc/mail. I do not have an /etc/make.conf. I have a /etc/defaults/make.conf and the line SENDMAIL_MC=/etc/mail/myconfig.mc is commeneted out in this file. There is no reference to SENDMAIL_CF in /etc/defaults/make.conf. I don't understand why I am having these problems...I did a build, install cycle the other day on this very machine without any problems, but I ended up wiping the system and starting over clean. I can't figure this out. I guess I will try to uncomment NO_SENDMAIL=true and build and install from there. - - Mike Loiterman [EMAIL PROTECTED] - - - - Original Message - From: Glen Foster To: Mike Loiterman Sent: Thursday, November 01, 2001 7:08 AM Subject: Re: make buildworld dies Here are some things that should make the error go away, any one of them should work, use whichever seems most convenient: Make sure you have a copy of freebsd.mc in /etc/mail, it used to be in /usr/src/etc/sendmail/. Run the build again (actually, make - -DNOCLEAN should be fine and speed things up considerably). Check your /etc/make.conf and /etc/defaults/make.conf file for any reference to SENDMAIL_MC or SENDMAIL_CF (the latter is now decprecated but maybe not on the system that you are working with). Set NO_SENDMAIL=true in /etc/make.conf, build, install, mergemaster, take it out and build and install again. Backup your /etc directory, run mergemaster to update it, then try the build again. -BEGIN PGP SIGNATURE- Version: PGPfreeware 7.0.3 for non-commercial use http://www.pgp.com Comment: Digitally signed by Mike Loiterman iQA/AwUBO+FP+3J6B0BI4qMYEQLzPgCg7UXH+r4BkElzvb+aKxNTogtuGjoAoObC CH3ERQVmUEKzvIbbjxkgJbDc =leIp -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
make buildworld dies
I want to apologize if this has been asked/answered. I've been out of it for almost three weeks while I was recovering from surgery. Today I cvsup'd and when I tried a buildworld, it failed: install -c -o root -g wheel -m 444 hcreate.3.gz /usr/share/man/man3 install: hcreate.3.gz: No such file or directory *** Error code 71 Stop in /usr/src/lib/libc. *** Error code 1 I've searched the stable archives but can't find a reference for it. If anyone has an idea on how to fix it, I'd appreciate it. Robert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Upgrading from 3.3 to RELENG_4_4
I'm trying to use cvsup to upgrade from 3.3-RELEASE to RELENG_4_4. My make buildworld has hit the xinstall/strtofflags problem reported many times on this list. So I am following the recommendation given by a few users that I go to RELENG_4_1_1_RELEASE first. This doesn't seem unreasonable, but it would be good if UPDATING told me I had to do this (maybe under To update from 3.x to 4.x stable). Nick Barnes Ravenbrook Limited To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make buildworld fail @/usr/src/gnu/usr.bin/perl
No, no-one answered. There was a thread about it which said it was due to a 1 billion second bug in cvsup, and you needed to get cvsup-16.e.tgz, and install it, rm -rf /usr/src rm -rf /usr/obj, and cvsup again. But that didn't work for me. Someone also suggested to again delete everything, and re-cvsup again -- which makes no sense to me why that might work -- but I tried it, and it too failed. What did work was to first upgrade to FreeBSD 4.2 from cdrom using cvs (and not cvsup and following the instructions in the README on the second cd). Once 4.2 was on, I then cvsup'd to 4.4. I tried that because I had no trouble upgrading from FreeBSD 4.2 to 4.4, but all the 4.0 boxes failed with the BrandELF problem. That's one solution anyway. --- andreas [EMAIL PROTECTED] wrote: hi, i saw your post to the freebsd stable list, and was wondering if you ever found out what was going wrong with your upgrade from 4.0-release - 4.4-stable. I am having the same issue where it gives the ELF binary type not known. ELF binary type not known. Use brandelf to brand it. Abort trap *** Error code 134 thanx in advance, andreas __ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Upgrading from 3.3 to RELENG_4_4
3.3-RELEASE to RELENG_4_1_1_RELEASE failed due to absence of mkstemps. On further archive trawling I see I should go to RELENG_3 first. Sigh. Nick Barnes Ravenbrook Limited At 2001-11-01 16:35:28+, Nick Barnes writes: I'm trying to use cvsup to upgrade from 3.3-RELEASE to RELENG_4_4. My make buildworld has hit the xinstall/strtofflags problem reported many times on this list. So I am following the recommendation given by a few users that I go to RELENG_4_1_1_RELEASE first. This doesn't seem unreasonable, but it would be good if UPDATING told me I had to do this (maybe under To update from 3.x to 4.x stable). Nick Barnes Ravenbrook Limited To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Upgrading from 3.3 to RELENG_4_4
I just filed a -doc PR on this. You can find some info in the FAQ, under Installing, but it's only relevant if you have bad144 on a 3.x IDE drive. Hopefully the web page will be updated soon. On Thu, Nov 01, 2001 at 04:35:28PM +, Nick Barnes wrote: I'm trying to use cvsup to upgrade from 3.3-RELEASE to RELENG_4_4. My make buildworld has hit the xinstall/strtofflags problem reported many times on this list. So I am following the recommendation given by a few users that I go to RELENG_4_1_1_RELEASE first. This doesn't seem unreasonable, but it would be good if UPDATING told me I had to do this (maybe under To update from 3.x to 4.x stable). Nick Barnes Ravenbrook Limited To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: PXE/DHCP/tftpd boot failure in FBSD 4.4-STABLE since yesterday!! Please Help!
On Wed, Oct 31, 2001 at 11:50:35PM +0100, Hartmann, O. wrote: On Wed, 31 Oct 2001, Chris Peiffer wrote: For testing purposes, I switched the sources back to the 20th October, I know that this codestage definitely worked! I recompiled a 'make world', all the terminal related stuff, new kernels and installed them, then I rebooted. After reboot I recompiled the dhcp code from the ports, with the same effect: nothing has changed, the stations still fail to boot. I think this is a problem with our LAN and the maintanace of the computer center. Now is the essentiell question: how to figure out what's going wrong? I need to examine what the DHCP recieves and delivers and I need to know what type of packets are exchanged between the DHCP server, its client and what happens when the client has recieved its dhcp config info and trys to get pxeboot image. How can I watch whether the diskless client gets its pxeboot image? Well, I would like to know some details about the protocol. The reason is, that the guys of our computer center tend to push away responsibilty and I would like to avoid having all the trouble I did not produce carrying on my shoulders ... tcpdump is your friend I guess, possibly together with ethereal. It should at least be possible to see dhcp requests, offers, etc. If the kernel is transfered using TFTP, it should be difficult to see that in tcpdump. With ethereal you will be able to analyze traffic captured with tcpdump more closely. You should run tcpdump on the DHCP server if you've a switched network (I guess so). Also, try to enable as much logging (or debugging) as possible in dhcpd, tftp (-l switch), etc. HTH, Alson -- ,---. Name: Alson van der Meulen Personal:[EMAIL PROTECTED] School: [EMAIL PROTECTED] `---' what's this hash prompt on my terminal mean? - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /usr/src/UPDATING
Hi, I had a similar query about just this very thing when 4.4 just went into release mode and Warner Losh had replied to the post saying that UPDATING in different tags (namely RELENG_4 and RELENG_4_4) are maintained independantly of each other, so one UPDATING could differ to the other. Makes sense when the releng_4_4 tag is security updates only and shouldnt as many contain strange errors/workarounds as releng_4 would. HTH PsyV On Wed, 31 Oct 2001, Jochem Kossen wrote: That's weird...I just cvsup'ed (RELENG_4), and the latest thing with me is: 20010814: The pci attachment for pcic device was merged from current. Are you sure you didn't add it yourself? ;) On Tue, Oct 30, 2001 at 11:15:48PM +0100, Eric Veraart wrote: The latest thing added to my UPDATING is: 20010915: FreeBSD 4.4-RELEASE. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
problem building smbfs module, any hint ?
Hi, i am having problems building the smbfs module in a relatively recent (Oct.25) STABLE. The module build dies saying something like don't know how to build iconv_converter_if.h This is happening while using the picobsd build script on STABLE tree, but i do not think the issue is picobsd-specific because the same thing works for CURRENT-based tree, and other modules also build ok. Any ideas ? cheers luigi --+- Luigi RIZZO, [EMAIL PROTECTED] . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 --+- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
