From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 14 21:59:08 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A784D16A4CE; Tue, 14 Dec 2004 21:59:08 +0000 (GMT) Received: from poczta.o2.pl (mx.go2.pl [193.17.41.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DFD443D5F; Tue, 14 Dec 2004 21:59:07 +0000 (GMT) (envelope-from knockefreebsd@o2.pl) Received: from ALFA (aaf223.warszawa.sdi.tpnet.pl [217.97.85.223]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by poczta.o2.pl (Postfix) with ESMTP id 7C258137788; Tue, 14 Dec 2004 22:59:04 +0100 (CET) Message-ID: <003501c4e228$5f2cd780$df5561d9@ALFA> From: "Heinz Knocke" To: , , Date: Tue, 14 Dec 2004 23:00:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Subject: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 21:59:08 -0000 Hi! Marvell's chip is not in supported nics section of 5_3 release notes, = but in man sk is , so I decided to write.=20 I've got some boxes with Marvell Gigabit NICs on-board (Gigabyte and = ASUS). Sadly, I can't be happy with it and freebsd 5.3 because of the = following two problems: a) sk0 driver seems to have some kind of bug in it - see = http://www.freebsd.org/cgi/query-pr.cgi?pr=3D71229 Does anybody know how is the work going on with it? I know that under = Linux they'd had some troubles with these NICs too, standard sk98lin = module didn't work properly and there was a vendors patch needed. Marvel = doesn't support FreeBSD, but maybe Windows NDIS2 will work?:=20 http://www.marvell.com/drivers/driverDisplay.do?dId=3D113&pId=3D16 . I = can do some tests, but let me know if it's not totaly useless (some tips = how to make it work would be helpfull to :)=20 b) according to the vendor's info, NIC should be able to do jumboframes. = (http://www.marvell.com/products/pcconn/yukon/Yukon_88E8001_10_073103_fin= al.pdf) ifconfig mtu 9000 works, but packets seems to come truncated (in both = directions) host1% sudo ping -s 2000 host2 PING host2 (10.10.10.2): 2000 data bytes ^C --- host2 ping statistics --- 23 packets transmitted, 0 packets received, 100% packet loss host2% sudo tcpdump -i sk0 -c 30 tcpdump: verbose output suppressed, use -v or -vv for full protocol = decode listening on sk0, link-type EN10MB (Ethernet), capture size 96 bytes 22:23:23.514150 IP truncated-ip - 524 bytes missing! dyplom1g > = dyplom2g: icmp 2008: echo request seq 3 22:23:24.524147 IP truncated-ip - 524 bytes missing! dyplom1g > = dyplom2g: icmp 2008: echo request seq 4 22:23:25.534282 IP truncated-ip - 524 bytes missing! dyplom1g > = dyplom2g: icmp 2008: echo request seq 5 22:23:26.544280 IP truncated-ip - 524 bytes missing! dyplom1g > = dyplom2g: icmp 2008: echo request seq 6 ^C Does anybody know what's going on?? Are a) and b) all the same big = Marvel problem :)) ?=20 Honestly said I don't know how to track it further, because the link = layer (hardware or the driver) seems just to clip frames. If there's not = enought info for the solution please tell me what tests can I do - I'll = do it ASAP.=20 I'd appreciate you support as usual :)) hk