Re: Problem with Floppies in 4-STABLE?
On Tue, Jan 22, 2002 at 08:20:40AM -0500, Jason Stephenson wrote: > > The machine that doesn't see the floppy drive doesn't print the fd0: line. > > I'm wondering: has anything changed in the floppy code since Jan. 15th > or is my floppy drive dead? You could always test the floppy by trying to boot from it. -- Bob <[EMAIL PROTECTED]> | Please don't feed the sock puppet. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3COM 3XP card
On Tue, Jan 22, 2002 at 09:48:23AM -0600, David W. Chapman Jr. wrote: > On Tue, Jan 22, 2002 at 07:43:32AM -0600, Paul Root wrote: > > Hi, > > I've recently received a 3COM ethernet card that > > has the 3XP chip allowing 3DES encryption on board. > > > > I see that the card is supported by 4.4. Can I > > use the encryption technology? How? > > > I have an intel pro S that does the same, but I don't think freebsd > currently supports this in these features although I have heard that > its rumored someone is being sponsored to add this feature. Not for Intel cards - not unless Intel is willing to release documentation. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3COM 3XP card
On Tue, Jan 22, 2002 at 07:43:32AM -0600, Paul Root wrote: > Hi, > I've recently received a 3COM ethernet card that > has the 3XP chip allowing 3DES encryption on board. > > I see that the card is supported by 4.4. Can I > use the encryption technology? How? > I have an intel pro S that does the same, but I don't think freebsd currently supports this in these features although I have heard that its rumored someone is being sponsored to add this feature. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Error in make buildworld
On Tue, Jan 22, 2002 at 09:34:56AM -0600, Stephen Montgomery-Smith wrote: > I have recent sources (the most recent CTM delta). I do make -j4 > buildworld > on three different computers. It works on two of them, but on one of > them (the fastest), I get: > > ===> usr.sbin/i4b/ispppcontrol > rm -f .depend > mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include > /usr/src/usr.sbin/i4b/ispppcontrol/ispppcontrol.c > cd /usr/src/usr.sbin/i4b/ispppcontrol; make _EXTRADEPEND > echo ispppcontrol: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend > ===> usr.sbin/i4b/man > ===> usr.sbin/boot0cfg > rm -f .depend > mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include > /usr/src/usr.sbin/boot0cfg/boot0cfg.c > cd /usr/src/usr.sbin/boot0cfg; make _EXTRADEPEND > echo boot0cfg: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > I didn't get this problem when I removed the -j4. This computer had a > hard drive failure a few months ago, and the replacement drive is > exceedingly fast. So maybe this computer is "too fast" for -j4 to > work. As computers get faster and faster, maybe more and more people > will have this problem. This is a known difficulty with multiple make threads. Note that I do _NOT_ call it a problem. It is caused by a thread that needs getting to the part that expects to have been built before the thread that actually builds gets to the build-foo code. I have found that I frequently can reissue the same command and will get built before it is required by something in another thread, and the make will run to completion the second time. It _will_ _not_ always run to completion, and if the first part of the make code cleans up, so that the make always starts from a clean set of output files, it probably won't run to completion. -- 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
Error in make buildworld
I have recent sources (the most recent CTM delta). I do make -j4 buildworld on three different computers. It works on two of them, but on one of them (the fastest), I get: ===> usr.sbin/i4b/ispppcontrol rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/i4b/ispppcontrol/ispppcontrol.c cd /usr/src/usr.sbin/i4b/ispppcontrol; make _EXTRADEPEND echo ispppcontrol: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend ===> usr.sbin/i4b/man ===> usr.sbin/boot0cfg rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/boot0cfg/boot0cfg.c cd /usr/src/usr.sbin/boot0cfg; make _EXTRADEPEND echo boot0cfg: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend 1 error *** Error code 2 1 error *** Error code 2 1 error I didn't get this problem when I removed the -j4. This computer had a hard drive failure a few months ago, and the replacement drive is exceedingly fast. So maybe this computer is "too fast" for -j4 to work. As computers get faster and faster, maybe more and more people will have this problem. -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ATA driver feature request
Yes, I always see this same thing if I place an older CD-ROM slave on the same cable. It drops to UDMA33. If I remove the CD-ROM, then the systme sees the cable fine as ATA100. If I then put my new CD-ROM on the cable, it likes that too. At 12:04 AM 1.22.2002 -0600, [EMAIL PROTECTED] wrote: > >On Sun, 20 Jan 2002, Dmitry Valdov wrote: >> >> On Sun, 20 Jan 2002, Bill Moran wrote: >> > > FreeBSD limits both >> > > drives on the bus because there is 'non-ATA66 compliant cable'. >> > >> > Are you sure you have an 80 conductor cable and that it isn't too long? >> >> Yes. When I disconnect secondary (non ATA-66/100 compliant) drive from this >> cable, FreeBSD use ATA-100 on primary. >> > >FWIW, I'm seeing the exact same symptom. I just added to 80gb Western >Digital (IDE) drives to the system. I used the 80-wire cables that came >with the drives, and I see the following messages: > >atapci0: port 0xd000-0xd00f at device 7.1 on pci0 >ata0: at 0x1f0 irq 14 on atapci0 >ata1: at 0x170 irq 15 on atapci0 >. . . >ad0: 19458MB [39535/16/63] at ata0-master UDMA66 >ad1: 76319MB [155061/16/63] at ata0-slave UDMA66 >ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable >ad2: 76319MB [155061/16/63] at ata1-master UDMA33 >ad3: 2503MB [5086/16/63] at ata1-slave UDMA33 > >They are the exact same drives using the exact same cable. My controller >only supports UDMA66, not 100... but the reason that the 2nd controller >seems to print out "non-ATA66 compiant cable" appears to simply be that >ad3 is only ATA33 capable. > >Just thought I'd pipe up, since the subject came up :) > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin === Sage-American http://www.sage-american.com [EMAIL PROTECTED] "My center is giving way, my right is in retreat; situation excellent! I shall attack!" === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
3COM 3XP card
Hi, I've recently received a 3COM ethernet card that has the 3XP chip allowing 3DES encryption on board. I see that the card is supported by 4.4. Can I use the encryption technology? How? Thanks, Paul. -- Paul T. RootE/Mail: [EMAIL PROTECTED] 600 Stinson Blvd, Fl 1S PAG: +1 (877) 693-7155 Minneapolis, MN 55413 WRK: +1 (612) 664-3385 NIC:PTR FAX: +1 (612) 664-4779 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Problem with Floppies in 4-STABLE?
I cvsup'd my machine at home on Sunday and rebuilt the system and kernel following the instructions in the handbook. Last night, when I tried to use the floppy drive, it didn't work. The first couple times that I tried it, I would get an "input/output error." Since the activity light on the drive never blinked, I took the case off my machine and checked that the cables were properly connected. They were. Next, I tried remaking the fd0 devices with sh MAKEDEV. This time, when I tried to access the drive, I got "device not configured." I also did a "sh MAKEDEV all." Here's how I have it configured in my kernel config: # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 and the kernel apparently sees it: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold I've tried two floppies, one a msdos formatted disk and the other a tar archive that I made on the machine in question on 12/30 with 4.4 Release. I get the same error from "tar tf /dev/rfd0" as I do from "mount -t msdos /dev/fd0 /floppy". This is the first time I've tried using the floppy drive since moving to 4.5-RC on this machine. I have another machine at the office, the one I'm using now, that is also running 4.5-RC, but it was last cvsup'd on Jan. 15th. The floppies work on it, and it is configured more or less the same. Although, in looking at the output from dmesg, I do notice a difference: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 The machine that doesn't see the floppy drive doesn't print the fd0: line. I'm wondering: has anything changed in the floppy code since Jan. 15th or is my floppy drive dead? -- Jason Stephenson - UNIX Administrator Univ. of KY College of Engineering 280 Anderson Hall - 7-5497 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot btx halted problem
> On Tue, 22 Jan 2002, Danny Braniss wrote: > Before I posted my first message, I flashed the last Boot Agent onto the > NIC, and after seeing your message, I hunted down and flashed the last BIOS > for the motherboard which was from mid 97. Unfortunately, it is still > crashing with exactly the same halted message. For those that might be > interested in the hardware, the system is a Pentium 166, on a Biostar > 8500TUC MB with 32 MB of RAM. That particular MB uses the Intel 430HX > chipset. Only expansion cards in the system are a Matrox Millenium video > card, and the Intel PRO/100 S NIC. There are no hard drives or floppy drives > in the system. This machine used to be my server until I replaced it a few > months ago with a new machine. ok, so till someone can shed some light from the BTX dump (hint hint), check 1) if the pxeboot is ok 2) try tcpdump/ethereal and see if all the file is laoded ok. i gather that the host you are trying to boot, actualy is in good health ? danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot btx halted problem
On Tue, 22 Jan 2002, Danny Braniss wrote: > im no expert in reading btx dump, but from past experience, upgrading the > firmware of the BIOS/NIC solved the problem. Before I posted my first message, I flashed the last Boot Agent onto the NIC, and after seeing your message, I hunted down and flashed the last BIOS for the motherboard which was from mid 97. Unfortunately, it is still crashing with exactly the same halted message. For those that might be interested in the hardware, the system is a Pentium 166, on a Biostar 8500TUC MB with 32 MB of RAM. That particular MB uses the Intel 430HX chipset. Only expansion cards in the system are a Matrox Millenium video card, and the Intel PRO/100 S NIC. There are no hard drives or floppy drives in the system. This machine used to be my server until I replaced it a few months ago with a new machine. -- Jason K. Fritcher [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d-() s+:++ a- C+++() UBS+++$ P++(-) L- !E W+(--) N++(+) o? K? w--() O M- V-- PS+>+++ PE Y+ PGP(++) t+@ 5 X+ R>+ tv+(--) b+>++ DI+ D++ G e>+++ h r+++ y+++ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Strange lock-ups during backup over nfs after adding 1024M RAM
Hi! Our server runs FreeBSD 4.4-STABLE. Until recently everything was ok, but when we increased the amount of RAM from 1024Mb to 2048Mb strange lock-ups started to happen. All lock-ups happened at night where activity was pretty low. We run backup over nfs nightly, and there is a good chance it is nfs that causes the problem. When the lock-ups happen backup is usually somewhere in the middle and after the server is restarted backup finishes ok. The most strange thing about it is the lock-up itself. The server keeps responding to pings, keyboard is working (it is possible to switch consoles and type, but not log in), there is nothing on console and in any logs, but nothing else (cron, web server, telnet, ftp, etc) is working. Nothing even happens if ctrl-alt-del is pressed on console. After the hard reboot everything works fine until next night. Anyone has any ideas what can cause the problem? I don't think it is hardware problem, since server works fine all the day during heavy load. I suspect that there could be some problem with the amount of memory, maybe kernel (nfs code?) can't handle situation where cache gets too big (say, more than 1Gb)... Any ideas on how to investigate and find the problem will be greatly appreciated! Regards, Sergey Gershtein -- Ural Relcom Ltd, Ekaterinburg, Russia To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message