Re: eye-candy hack - warp_saver changing direction :)
unsubscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Gigabit ethernet
Do both the Netgear GA620 and GA620T work? On Wed, 2 Aug 2000, Kenneth D. Merry wrote: > On Wed, Aug 02, 2000 at 09:15:00 -0700, Josef Grosch wrote: > > > > Simple question: > > > > Which Gigabit ethernet card works best with FreeBSD? > > Alteon-based boards. This includes Alteon ACEnics, the 3Com 3c985B (which > has 1MB SRAM), and the Netgear GA620 (which has 512K SRAM). > > You can get the Netgear board for about $320, and the copper version of the > board for about $310 from www.necxdirect.com. The 3Com board is about $680 > from the same place. (You're paying for the extra memory, which can make a > difference, albeit not an enormous difference. Also, the Windows drivers > for the Netgear boards don't do jumbo frames. I'm not sure whether the > 3Com Windows drivers do jumbo frames, but I would guess that they do.) > > If you want bandwidth numbers, see: > > http://people.freebsd.org/~ken/zero_copy/ > > Ken > -- > Kenneth Merry > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel 840 Chipset Discontinue
Apparently it affects all boards that the Intel 840 chipset. Yeah, it does suck that the 370DLx boards dont have AGP, but for a server you can still find old PCI video cards. On Fri, 21 Jul 2000, Kenneth D. Merry wrote: > On Fri, Jul 21, 2000 at 12:31:58 -0400, Essenz Consulting wrote: > > I was told by several of my distributors that all motherboards based off > > of the Intel 840 chipset are being discontinued. That means the Supermicro > > PIIDM3 and PIIIDME, and any other 840 board. > > Are you sure they don't just mean any 840 board that uses SDRAM? > > It looks like Supermicro has a RAMBUS 840 board on their web page now: > > http://www.supermicro.com/PRODUCT/MotherBoards/840/PIIIDR3a.htm > > > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > > have also been hearing bad news about these boards as well. > > Not quite identical. They don't have AGP, which makes it difficult to > get graphics boards. (If you want to use it for a workstation. Most > graphics boards don't come in plain PCI anymore.) > > Ken > -- > Kenneth Merry > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Intel 840 Chipset Discontinue
I was told by several of my distributors that all motherboards based off of the Intel 840 chipset are being discontinued. That means the Supermicro PIIDM3 and PIIIDME, and any other 840 board. Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to the 840 boards, but using some kind of "ServerWork LE" chipset. However, I have also been hearing bad news about these boards as well. Has anyone worked with these boards? Supermicro SAYS that they work fine under Linux and Solaris. However, one of my distributors says thay they are extremely touchy when it comes to memory. Only Registered PC133 ECC memory will work. If someone at freebsd.org wants to seriously test these boards, let me know, and I'll donate one. Without the 840 boards, server configs are now back to the 440GX days! -john v.e. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 160/m support...
Marc, Do you know anyone who has tried the support of AIC-7899 chips? That chipset is used on some quad and dual XEON boards. -john v.e. On Sun, 16 Jul 2000, Marc Veldman wrote: > On Tue, 11 Jul 2000, Kenneth D. Merry wrote: > > > > Is Adaptec aic-7892 and 7899 160/m SCSI support in the pipeline to be > > > worked on? aka, has adaptec released any info to those FreeBSD team > > > members who work on the SCSI drivers? Is it possible that maybe within the > > > next 4 months 160/m support will exist in FreeBSD 4/5? > > > > It's working, but isn't in the tree yet. > > AFAIK, the aic-7892 works just fine in 4.0-STABLE, and it has worked > fine for a few months now. I'm not sure if the actual 160/m works though. > > This is from my dmesg: > > ahc0: port 0xfc00-0xfcff mem >0xfffbf000-0xfffb irq 7 at device 13.0 on pci0 > ahc0: aic7892 Wide Channel A, SCSI Id=15, 16/255 SCBs > . > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) > > Could some kind committer add a line to RELNOTES.TXT that the > 19160 adapter is supported (or at least works partially) ? > > === > > Get off the keyboard you furry feline ! > > Marc Veldman, CFBSDN (Certified FreeBSD Newbie) > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
System Crash
Question. I have a machine that is crashing. Basically, random processes will die off and give SEGMENTATION FAULTS, then followed by a core dump, and the machine halts. Has to be manual rebooted after that. I tryed another hard drive in the machine, and same problems come up. So I am not sure if it is bad memory or a bad processor, or a bad motherboard. Is there anyway to find out? -john v. e. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
160/m support...
Just curious, This has probably been asked before, but.. Is Adaptec aic-7892 and 7899 160/m SCSI support in the pipeline to be worked on? aka, has adaptec released any info to those FreeBSD team members who work on the SCSI drivers? Is it possible that maybe within the next 4 months 160/m support will exist in FreeBSD 4/5? -john v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UPS Daemons
I know that APC SmartUPS and BackUPS are supported under FreeBSD but what about the APC PowerStack? I was looking at the APC PowerStack 250 Rackmount UPS. It comes with a RS-232 cables and supports that same kind of emergency shutdown that the SmartUPS systems have. Anybody use a PowerStack? I would only use if I knew that I could tie it in to FreeBSD for automatic shutdown when battery power is used up. -john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3dfx driver for freebsd
Hmmm, I guess this point was overlooked, but Has anyone tried this new code to see if it works well under FreeBSD 4.0? -jve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Mylex AccelRAID 150 and Quantum Drives...
I am having problems getting a Mylex AccelleRAID 150 RAID Card to see my Quantum Atlass 10k SCA 80-pin drives. Mylex is a little unclear as why quantum drives dont work. Has anyone used quantum atlass 10k SCA drives with a Mylex card? Thanks. -john v. e. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Unexpected reboot.
I posted this awhile back I didnt get much response. Basically, I have a machine with FreeBSD 4.0-RELEASE. Every couple of days it reboots for now reason. When I looked at the logs, it shows regular log data, then the next line reads "/kernel: Copyright (c) 1992-2000 The FreeBSD Project. Then the standard kernel stuff gets listed. At the end of the kernel data is says WARNING: / was not properly dismounted. There is nothing before the kernel data about shutting down or rebooting. I have an Intel PRO/100+ network card, U2W scsi. Has anybody encountered something like this? This same hardware configuration has no problems with other versions of FreeBSD, could it be a 4.0 problem. Any help would be great. Thanks. -john von essen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Supermicro PIIIDM3 Problems...
On the PIIIDM3 that I was working with I had both ECC and PC100 SDRAM. I forget what I had and when. I did though at one point have ECC unbuffered memory, and had ECC enabled. I will have some more of these boards later these week and will retest them, making note of what I have in there. I'll try ecc and pc100 individual and play with the settings, to see if I can find exactly what configuration is giving the problem. -john v. e. On Mon, 22 May 2000, Kenneth D. Merry wrote: > On Mon, May 22, 2000 at 11:33:52 -0700, Mike Smith wrote: > > > > Can you be more specific about "panicing"? As far as details go, you're > > not helping yourself. > > > > > I was doing a FreeBSD 4.0 Install on a fairly new Supermicro PIIIDM3 > > > motherboard. I eventually got FreeBSD 4.0 installed, however, during the > > > install, it kept hanging up and panicing. After trying to do a bin only > > > install, it took about 7 trys until it didnt hang up and panic. When I did > > > get it installed, everything worked, and it booted. But if I go into > > > sysinstall and try to do a post install addition of, lets say src/sys, > > > same thing happens. It freezes up and hangs part way throw, and eventually > > > will throw up a panic error. > > > > > > Any ideas about the stability of the aix78xx driver for this motherboard > > > and it's aic-7892 chip? > > > > I use one of these boards on a daily basis; it's been very stable under > > both -stable and -current, although I don't use the SCSI interface very > > often anymore. > > Well, one question is whether or not you have ECC memory in the machine, > and if so, if you have parity checking or ECC turned on. > > Mike's board doesn't have ECC memory, and I've been trying to find someone > with a SuperMicro 840 board with ECC turned on. (To see whether their > boards have the problem with the MRH-S chip.) > > As far as the 7892 chip, the driver should be pretty stable, I don't think > other folks have had trouble with it. > > Ken > -- > Kenneth Merry > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Supermicro PIIIDM3 Problems...
I was doing a FreeBSD 4.0 Install on a fairly new Supermicro PIIIDM3 motherboard. I eventually got FreeBSD 4.0 installed, however, during the install, it kept hanging up and panicing. After trying to do a bin only install, it took about 7 trys until it didnt hang up and panic. When I did get it installed, everything worked, and it booted. But if I go into sysinstall and try to do a post install addition of, lets say src/sys, same thing happens. It freezes up and hangs part way throw, and eventually will throw up a panic error. Any ideas about the stability of the aix78xx driver for this motherboard and it's aic-7892 chip? -john v. e. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ILOVEYOU
This ILOVEYOU virus is some sort of VB script. I put the source code for it at http://www.ecsel.psu.edu/~vonessen/viewer.cgi?file=iloveyou.dat Dont worry, the MIME type is text/plain -john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Onboard Intel NIC
Maybe I got lost in the hub-bub, but I am still having trouble getting my onboard NIC to work, still get unsupported phy errors. When you say its fixed are you refering to the patch the DG sent out the other day, or your patch. I applied DG's patch and the problem still exists. And I cant compile my kernel with your patch. Does your if_fxp.c file need to be compiled on a 3.4 system? Because I am running 4.0. In any case I am starting to get real frustrated again. Maybe I am using the wrong patch or something?! -John On Wed, 29 Mar 2000, Dennis wrote: > > >> obviously not the one that has the error. Are you paying attention? > > > >You really are an arrogant prat aren't you. How do you know it's the same > >one? Have you asked him? Let me guess.. you're *assuming* aren't you. > > Wait, so we were talking about the "newer" intel boards not being fully > supported in the fxp driver and this drubb chimes in with "Im using an > eepro with no problems"clearly that isnt relevant, since on-one along > the line ever said that all intel cards didnt work. > > So, it is clear that you too are not paying attention, yet you seem to have > an opinion regarding things that you also know little about. Dont browbeat > me for putting down some dope who doesnt know what hes talking about who > feels compelled to voice an opinion based on ignorance. > > What is really funny is that, as usual, all of the people who feel > compelled to make comments about me are not experiencing the problemits > real easy to pick on someone when the issue doenst effect you. > > Meanwhile, the problem is fixed, and scads of people who have experienced > the problem are emailing me to thank me for lighting a fire under some butts. > > DB > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Onboard Intel NIC
Mike, I am sorry I was so jumpy with the description of my problem. Let me elaborate some more. I have two NIC's, a PCI Card Intel PRO/100 and an onboard Intel PRO/100. The onboard NIC is giving the following kernel error: /kernel: fxp1: warning: unsupported PHY, type = 17, addr = 2 Yes, the card itself is still working, it actually works fine, but every minute this error comes up. Since this is a firewall box, I dont want hundreds of these errors in my log every day. I did a little investigating, I am no where near as knowledgable as soom of the freebsd people, but I looked at the if_fxp.c driver src and saw that PHY Media refered to the Media of your LAN. (simplex, duplex, 10Mbit, 100Mbit) In any case, this is a signifacant bug to be worked out. David Greenman sent me an email with a little snipit of code to add the to fxp src, I will try that today. He also voiced his opinion about trying to fix this issue with onboard networking, because those supermicro boards are rolling out quickly. Getting back to my idea of this problem being with media type, I did ifconfig -a and got the following: fxp0: flags=8843 mtu 1500 inet 216.243.128.21 netmask 0xff80 broadcast 216.243.128.127 ether 00:90:27:b0:39:9d media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP fxp1: flags=8806 mtu 1500 inet 216.243.129.1 netmask 0xff00 broadcast 216.243.129.255 ether 00:30:48:10:0a:2d media: manual supported media: manual Obviously, they do not match. For starters I dont even know how to set these to be the same media. I tryed ifconfig fxp1 media 100BaseTX, but that was met with the error: SIOCSIFMEDIA: Device not configured. Again, any help on this would be great. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
