NIC problems
Hi, I have a Intel Desktop Board D946GZIS and im using FreeBSD 6.2 Pre-release. I can't get the NIC to work. Please can someone help me as this is urgent. __ Matthew Edwards Clarotech Consulting (Pty) Ltd. Tel: +27 21 762-2928 Fax: +27 21 762-7654 Cell: +27 82 471-3443 Web: www.clarotech.co.za ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC problems
On Wednesday 06 December 2006 08:38, Matthew Edwards wrote: Hi, I have a Intel Desktop Board D946GZIS and im using FreeBSD 6.2 Pre-release. I can't get the NIC to work. Please can someone help me as this is urgent. __ Matthew Edwards Clarotech Consulting (Pty) Ltd. Tel:+27 21 762-2928 Fax:+27 21 762-7654 Cell: +27 82 471-3443 Web:www.clarotech.co.za ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Matthew, What are some of the symptoms? Has the nic worked before? If so, are there any error messages in /var/log/messages? What does ifconfig -a show? lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA OnBoard NIC problems
Your onboard card isn't in the supported hardware list (from 5.2 that is) and your Intel one is, so I guess that explains your problem. I know you don't want to hear it, but you got no other choice then putting an new network card in it if you want your network to be stable. Cheers, Jorn On Monday 02 February 2004 01:34, [EMAIL PROTECTED] wrote: Hi everybody.. I have problem with onboard NIC on VIA EPIA Mini ITX mainboard 5000 series. (this is small part from dmesg) vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xe800-0xe8ff mem 0xe410-0xe410 00ff irq 11 at device 18.0 on pci0 . If i try rsync to synchronize large ISO files (~700MB) from internet (mw 192 kBit) thru this card the md5 signature is allways invalid. Also if i use the machine as samba server with 6 clients and havy traffic, the samba hangs after 10-30 min. If I use other PCI NIC . fxp0: Intel 82557 Pro/100 Ethernet port 0xec00-0xec1f mem 0xe400-0xe40 f,0xe4101000-0xe4101fff irq 15 at device 20.0 on pci0 . ewerything is OK. But I NEED this PCI slot (there is only one) for another card (SCSI). The same happens with 4.9 and 5.2.. Any Idea?? Dont tell me I need other board. Sorry for my inglis TomBA ___ EuroWeb Webmail, http://www.euroweb.sk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA OnBoard NIC problems
I'm running 5.2 right now with a VIA EPIA 800 setup. It uses that same card, vr0, and it seems to work so far, then again I don't have anything that's much of load for it. Luke On Feb 1, 2004, at 3:17 PM, Jorn Argelo wrote: Your onboard card isn't in the supported hardware list (from 5.2 that is) and your Intel one is, so I guess that explains your problem. I know you don't want to hear it, but you got no other choice then putting an new network card in it if you want your network to be stable. Cheers, Jorn On Monday 02 February 2004 01:34, [EMAIL PROTECTED] wrote: Hi everybody.. I have problem with onboard NIC on VIA EPIA Mini ITX mainboard 5000 series. (this is small part from dmesg) vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xe800-0xe8ff mem 0xe410-0xe410 00ff irq 11 at device 18.0 on pci0 . If i try rsync to synchronize large ISO files (~700MB) from internet (mw 192 kBit) thru this card the md5 signature is allways invalid. Also if i use the machine as samba server with 6 clients and havy traffic, the samba hangs after 10-30 min. If I use other PCI NIC . fxp0: Intel 82557 Pro/100 Ethernet port 0xec00-0xec1f mem 0xe400-0xe40 f,0xe4101000-0xe4101fff irq 15 at device 20.0 on pci0 . ewerything is OK. But I NEED this PCI slot (there is only one) for another card (SCSI). The same happens with 4.9 and 5.2.. Any Idea?? Dont tell me I need other board. Sorry for my inglis TomBA ___ EuroWeb Webmail, http://www.euroweb.sk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 on ASUS P4C800 (onboard NIC problems, 3Com 3C940) (a solution)
I know there is no support 3c940 nic with FreeBSD 5.1 version. But it is added later. I look at the CVS. In FreeBSD 5.1 the driver version of the sk is 1.59 (if_sk.c). But 3c940 support added to sk with version 1.65. So i take the 1.65. then i put these files to kernel and i compile itl. Now i am happy with my 3c940 on FreeBSD 5.1. you can download if_sk.c 1.65 version from http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_sk.c . But it depend to 2 other files (if_skreg.h and yukonreg.h) so you must download they also. Steps --- (+)download if_sk.c version 1.65 - http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/pci/if_sk.c?rev=1.64content-type=text/plain (+)download if_skreg.h version 1.16 - http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/pci/if_skreg.h?rev=1.16content-type=text/plain (+)download yukonreg.h version 1.1 - http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/pci/yukonreg.h?rev=1.1content-type=text/plain (+) backup your orginal files which are in /usr/src/sys/pci/ mv /usr/src/sys/pci/if_sk.c /usr/src/sys/pci/if_sk.c.orig mv /usr/src/sys/pci/if_skreg.c /usr/src/sys/pci/if_skreg.h.orig mv /usr/src/sys/pci/yukonreg.h /usr/src/sys/pci/yukonreg.h.orig (+) copy your downloaded files to /usr/src/sys/pci/ cd /floppy/ #I guess that cp if_sk.c if_skreg.h yukonreg.h /usr/src/sys/pci/ (+) Now you can compile kernel cd /usr/src/sys/i386/conf/ config GENERIC cd ../compile/GENERIC make depend make make install (+) reboot the system reboot (+) if everything ok you can see your sk driver with 3c940 Krad Yusuf KONU KYK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 on ASUS P4C800 (onboard NIC problems, 3Com 3C940)
I don't believe the 3C940 is currently supported in FreeBSD (nothing about it in hardware notes for 5.1 i386). So, you can try googling to see if anyone's working on a driver for it. Chances are however that you'll have to use another NIC. - Original Message - From: Gab [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 8:31 AM Subject: FreeBSD 5.1 on ASUS P4C800 (onboard NIC problems, 3Com 3C940) Hello, I successfully installed FreeBSD 5.1 on my ASUS P4C800 motherboard. The only remaining problem is that sysinstall did not find any ethernet device during the installation. The onboard NIC is a 3Com 3C940. What should I exactly do in order to make the system detect this 3Com 3C940 ethernet device and make it work properly? Many thanks for your help. Gab ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 on ASUS P4C800 (onboard NIC problems, 3Com 3C940)
Hello, I successfully installed FreeBSD 5.1 on my ASUS P4C800 motherboard. The only remaining problem is that sysinstall did not find any ethernet device during the installation. The onboard NIC is a 3Com 3C940. What should I exactly do in order to make the system detect this 3Com 3C940 ethernet device and make it work properly? Many thanks for your help. Gab ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ABIT KX7-333R problems: RAID NIC problems
I'm having some problems with a RAID setup and the network on a new system. I haven't found anyone mentioning the problems in the searching I've done (Google, FreeBSD Website, mailing lists). Hopefully someone can get me pointed in the right direction or tell me what I'm missing (or fix a bug if that is the case). Summary of Problems: Intel network cards (identical models -- see below) refuse to work on the network. They will not pull DHCP, and if manually configured, will not talk to anything on the network. All systems are connected via a hub. DHCP is run off of a FreeBSD system. The HUB and the cards do show a link light. When I create a mirrored array (2x 60GB 7200 RPM Seagates), each drive is set as master on its own IDE channel without anything else attached to the controller. When creating files, even very large ones, on the local system I get good throughput -- On the order of 20MB/sec. When I FTP a file from the other FreeBSD server down onto the mirrored array, the transfer will only go at about 100k/sec. (Additional debugging/testing I've performed below). Information: FreeBSD Version: Generic install off of the FreeBSD 4.6 cds for the testing below. Identical problems were noted after cvsup'ing to 4.7 remaking the world. Hardware Setup: Motherboard: ABIT KX7-333 w/RAID (Flashed the board with its latest BIOS update, problems remain) VIA KT333 VT8233A chipsets HighPoint HPT 372 RAID controller (UDMA/133 on board) CPU: Athlon 1600XP+ Drives: 2x 60GB 7200 RPM Seagate IDE drives. (All are running as UDMA 100) Drive Setup: Tried with the following configurations: 1) Directly to the mainboard IDE port, single drive, set as master. 2) Mirrored array, both disks, hooked onto the RAID controller. (Each set as a master on their individual channel) 3) Non RAID setup, using a disk connected to the RAID controller. Network Cards: I've tried a total of 4 cards: 2 x Intel 10BT/100BTX PILA8460B PRO/100+ PCI (fxp) 1 x Phoebe (rl) 1 x CNET (dc) NETWORK PROBLEM: I've tried at least 4 cables, all of which work on other systems. One specific cable was used for all of the below tests. The cards have all been tried in all PCI slots except slot 5, which the boards manual suggests not using because it /may/ have IRQ steering problems with the raid controller. To test the card I attempt to get dhcp configuration (dhclient interface), then I try and FTP a 180MB test file from another server (the DHCP server in this case). The three cards: Intel (fxp): I have two identical models here. Neither cards will pick up DHCP. If I manually set the IP addresses, they will still not talk to anything on the network. The link lights do light up on both the hub and the nic. RealTek (rl): The card gets DHCP info wonderfully, and will transfer files at about 6MB/sec. No errors, warning, etc. CNET (dc): Card also has no problems getting on the network. When I do the transfer, some problems can occur. I get TX underrun -- Increasing TX threshold repeatedly. Then, every 8 or 9 reboots, it will stall and give a broken pipe error. You then have to reboot to make the link work again. While it runs, it pulls at about 7MB/sec. In searching, I've seen a number of people with that error message with the dc driver, but because it normally (9 times out of 10) will continue to work, it doesn't feel like a NIC or NIC driver problem to me. Disabling the onboard RAID controller (in the BIOS) didn't have any effect on the problems whatsoever. RAID Problems: The problems occur with dc0 *and* rl0 network cards when FTPing the 180MB test file. The RAID -and- single drive setups work like a charm for everything local (and will install at the max speed the CDROM can handle -- regardless of configuration). Setup #1) Using the Raid IDE as general (non RAIDed) setup -- I'm able to install FreeBSD onto it and boot without a problem. Installs reads at drives speed (20+ MB/sec). Doing the FTP download the download will go at maximum speed the remote system network cards can handle. Setup #2) Using RAID with Mirroring option -- Each drive set as master of its IDE channel. Nothing else connected to it. I'm able to install FreeBSD onto it and boot without a problem. Installs reads at drives speed (20+ MB/sec). Doing the FTP download the download will only go about 100k/sec (UPLOADING that file to another system will go at full speed, just the download is severely limited). Both network cards go this speed. Identical CABLE NIC setups as the other configurations.. Setup #3) Using the regular IDE channel on the motherboard -- I'm able to install FreeBSD onto it and boot without a problem. Installs reads at drives speed (20+ MB/sec). Doing the FTP download the download will go at maximum speed the remote system network cards can handle. My goals are to get the Intel NICs to work, and get RAID to act properly (ie: full speed). I've
RealTek 8129/8139 nic problems
Greetings, I have a Accton 100baseTX nic that uses the RealTek 8129/8139 chipset. The nic works fine if I plug it into a 10mbit hub but as soon as I plug it into a switch ( 3Com Baseline 10/100 ) which I use internally for ftp'ing it starts transferring data ok and then slowly dies. After awhile it will not permit me at all to connect and I have to manually bring down the interface using ifconfig and then bring it back up before I can reconnect. I have configured my kernel with the correct drivers ( device rl ). I have 2 identical nic's in the same machine and they both give the same problem and I have tried several ftp clients. I'm using 4.6 Stable. Has anyone experienced similar problems with these nic's ? Any help, suggestions would be appreciated. Kind regards, Nelis To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: RealTek 8129/8139 nic problems
At 11:43 3-10-2002 +0200, Nelis Lamprecht wrote: I have a Accton 100baseTX nic that uses the RealTek 8129/8139 chipset. The nic works fine if I plug it into a 10mbit hub but as soon as I plug it into a switch ( 3Com Baseline 10/100 ) which I use internally for ftp'ing it starts transferring data ok and then slowly dies. After awhile it will not permit me at all to connect and I have to manually bring down the interface using ifconfig and then bring it back up before I can reconnect. I have configured my kernel with the correct drivers ( device rl ). I have 2 identical nic's in the same machine and they both give the same problem and I have tried several ftp clients. I'm using 4.6 Stable. Has anyone experienced similar problems with these nic's ? Any help, suggestions would be appreciated. I had the same problems with two RTL8139 nic's. The problem was easily solved by locking the nic's to one speed (100mbit or 10mbit) This is done with ifconfig I believe. Sicco Miedema To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
