Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0 (PYUN Yong-Hyeon)
I'm not sure you suffers from the same problem but there was a Tx checksum offload related bug in msk(4) driver and it was fixed in HEAD. How about applying the diff in CVS rev 1.33 of if_msk? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_msk.c.diff?r1=1.32;r2=1.33;f=h Would love to have a crack at this but have never 'applied diffs' before?! I am guessing I look in to the source for the msk module, find line 2601, add the code in the green box, then remake the module and copy over the existing one? If theres a step by step to the correct procedure I'd appreciate pointers. As an aside I went back and added -txcsum -rxcsum whlist using the msk module and that also worked. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0 (PYUN Yong-Hyeon)
On Fri, 31 Oct 2008 08:18:20 - Graham Bentley [EMAIL PROTECTED] wrote: I'm not sure you suffers from the same problem but there was a Tx checksum offload related bug in msk(4) driver and it was fixed in HEAD. How about applying the diff in CVS rev 1.33 of if_msk? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_msk.c.diff?r1=1.32;r2=1.33;f=h Would love to have a crack at this but have never 'applied diffs' before?! I am guessing I look in to the source for the msk module, find line 2601, add the code in the green box, then remake the module and copy over the existing one? Assuming you already have the source, select unified diff on the above and save it to a file, then cd /usr patch patchfile where patchfile is the saved file, then build as normal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
select unified diff on the above and save it to a file, then cd /usr patch patchfilewhere patchfile is the saved file, then build as normal. 3bsd# patch if_msk.c.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- src/sys/dev/msk/if_msk.c 2008/09/25 07:31:45 1.32 |+++ src/sys/dev/msk/if_msk.c 2008/09/30 04:47:49 1.33 -- Patching file src/sys/dev/msk/if_msk.c using Plan A... Hunk #1 failed at 99. Hunk #2 succeeded at 2708 (offset 107 lines). 1 out of 2 hunks failed--saving rejects to src/sys/dev/msk/if_msk.c.rej done Don't like the look of first result? src/sys/dev/msk/if_msk.c.rej - *** *** 99,105 */ #include sys/cdefs.h - __FBSDID($FreeBSD: /usr/local/www/cvsroot/FreeBSD/src/sys/dev/msk/if_msk.c,v 1.32 2008/09/25 07:31:45 yongari Exp $); #include sys/param.h #include sys/systm.h --- 99,105 */ #include sys/cdefs.h + __FBSDID($FreeBSD: /usr/local/www/cvsroot/FreeBSD/src/sys/dev/msk/if_msk.c,v 1.33 2008/09/30 04:47:49 yongari Exp $); #include sys/param.h #include sys/systm.h ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
Hi ALl, I have a DFI LanParty Mobo that includes Marvells 88E8052 and 88E8053 LAN IF. Using the module with 7.0 [msk] the network preformance is terrible, Opera / Links stall, or wont page load at all although pings to the router are fine? I then tried using Marvells own driver the website [myk] and the results where about the same. Just before I was about to give up and put in my trusty old 3Com 3C509 [xl] I noticed that in the Marvell doco there where several tunable params so decided to try out a few. I discovered that adding -txcsum and -rxcsum (i.e. disabling hardware checksuming) to the ifconfig statement, the performance was as quick as it is on that other OS! It seems that hw cs is on by default so I added the above to my ifoncfig line in /etc/rc.conf and now all is snappy! I was wondering how could this be the case and also if anyone else had this issue with Marvell chips? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
I discovered that adding -txcsum and -rxcsum (i.e. disabling hardware checksuming) to the ifconfig statement, the performance was as quick as it is on that other OS! there is a lot of buggy chips produced today. normally the should go to thrash, but - what a problem - they put onto motherboards so user have no choice. then they include windoze drivers that simply disable non-working features and they are happy, not even telling anyone about this. unless you are buying motherboard for servers, DO NOT expect lan to work ;) it's my common practice. nvidia ethernet was the worst one (it never worked), but realtek gigabit ethernet on other motherboard needed the same as yours (-txcsum, -rxcsum) or it randomly drop packets, probably because it calculates checksums wrong. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
On Thu, Oct 30, 2008 at 11:33:34AM -, Graham Bentley wrote: Hi ALl, I have a DFI LanParty Mobo that includes Marvells 88E8052 and 88E8053 LAN IF. Using the module with 7.0 [msk] the network preformance is terrible, Opera / Links stall, or wont page load at all although pings to the router are fine? I then tried using Marvells own driver the website [myk] and the results where about the same. Just before I was about to give up and put in my trusty old 3Com 3C509 [xl] I noticed that in the Marvell doco there where several tunable params so decided to try out a few. I discovered that adding -txcsum and -rxcsum (i.e. disabling hardware checksuming) to the ifconfig statement, the performance was as quick as it is on that other OS! Yong-Hyeon Pyun can probably explain what's going on here. I've CC'd him on this mail; he usually hangs out on -stable though. You need to keep something in mind here: Marvell does not give out documentation for their cards publicly, so Yong-Hyeon has to reverse-engineer and tinker with what he already knows. Some hardware feature do not work, others are buggy, others work fine on specific revisions of the chip while later ones break. And if you tell me Well Linux has support for this chip!, I will throw the following evidence back in your face: Marvell and other companies are giving Linux developers development PCI cards to develop drivers with (sometimes even before the card is out in the market), so Linux has the upper hand here. They are not doing this with the BSDs. Purely as an example: in my Wiki, section Network devices, see the entry for the 88E8040 NIC. I'm still working with Yong-Hyeon to try to get him access to a laptop that has this chip so he can write the driver. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues This should give you some idea of the complexities. As I said, Linux has the upper hand, because they're getting support from Marvell. It seems that hw cs is on by default so I added the above to my ifoncfig line in /etc/rc.conf and now all is snappy! I was wondering how could this be the case and also if anyone else had this issue with Marvell chips? I would urge you to go out and purchase an Intel Pro/1000 PT card, which runs for around 30-40 USD. It's good to have a spare NIC on hand anyways -- your 3C509 xl(4) based NIC probably won't cut it, especially if you're complaining about performance. :-) No one uses those cards any more except individuals running on hardware from 1997, which you are obviously not. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
On Thu, 30 Oct 2008 13:15:04 +0100 (CET) Wojciech Puchar [EMAIL PROTECTED] wrote: I discovered that adding -txcsum and -rxcsum (i.e. disabling hardware checksuming) to the ifconfig statement, the performance was as quick as it is on that other OS! there is a lot of buggy chips produced today. normally the should go to thrash, but - what a problem - they put onto motherboards so user have no choice. then they include windoze drivers that simply disable non-working features and they are happy, not even telling anyone about this. Not technically correct. If you go into 'Control Panel' and access the correct logs you will see what has transpired when the driver was loaded. Most Window users do not want to be bothered with the details of what happened; they just want it to work (actually, not a bad concept). Think about it; if Microsoft actually displayed by default all error messages they or the OEM would probably be inundated with frivolous requests for support. unless you are buying motherboard for servers, DO NOT expect lan to work ;) it's my common practice. nvidia ethernet was the worst one (it never worked), but realtek gigabit ethernet on other motherboard needed the same as yours (-txcsum, -rxcsum) or it randomly drop packets, probably because it calculates checksums wrong. I had a friend who used nvidia. They never complained about it. I will see if I can find out what model and how they got it to work. -- Jerry [EMAIL PROTECTED] semper en excretus signature.asc Description: PGP signature
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
You need to keep something in mind here: Marvell does not give out documentation for their cards publicly, so Yong-Hyeon has to reverse-engineer and tinker with what he already knows. Some hardware feature do not work, others are buggy, others work fine on specific revisions of the chip while later ones break. Don't get me wrong - I appreciate that people are working in the trenches on this stuff and thats great about FreeBSD. I only switched to the Marvel .ko as it was suggested on previous questions list, so didnt spend much time with the stock 7.0 driver. And if you tell me Well Linux has support for this chip!, I will throw the following evidence back in your face: Marvell and other companies are giving Linux developers development PCI cards to develop drivers with (sometimes even before the card is out in the market), so Linux has the upper hand here. They are not doing this with the BSDs. I guess even specs would be nice - hardware donations would be nicer though :) I would urge you to go out and purchase an Intel Pro/1000 PT card Funnily enough, in the back of my mind I had the same thought upon seeing the words 'Marvell' amongst the mobo spec. Thats said at least they made an effort on supporting multi OS http://www.marvell.com/drivers/search.do even if they are a precious with their specs etc With some Vendors its Windos or nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
Purely as an example: in my Wiki, section Network devices, see the entry for the 88E8040 NIC. I'm still working with Yong-Hyeon to try to get him access to a laptop that has this chip so he can write the driver. the best solution is to not use that cards. it's producer's choice to loose some clients. I would urge you to go out and purchase an Intel Pro/1000 PT card, which runs for around 30-40 USD. It's good to have a spare NIC on hand i exactly did it everywhere i had such problems. they are excellent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
I had a friend who used nvidia. They never complained about it. I will see if I can find out what model and how they got it to work. mine (on amd64 board, nforce3 if i remember correctly, i sold that computer) simply stopped working every 5-10 minutes until you did ifconfig nve0 down ifconfig nve0 up ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8052 PCI-E LAN on FreeBSD 7.0
On Thu, Oct 30, 2008 at 05:38:15AM -0700, Jeremy Chadwick wrote: On Thu, Oct 30, 2008 at 11:33:34AM -, Graham Bentley wrote: Hi ALl, I have a DFI LanParty Mobo that includes Marvells 88E8052 and 88E8053 LAN IF. Using the module with 7.0 [msk] the network preformance is terrible, Opera / Links stall, or wont page load at all although pings to the router are fine? I then tried using Marvells own driver the website [myk] and the results where about the same. Just before I was about to give up and put in my trusty old 3Com 3C509 [xl] I noticed that in the Marvell doco there where several tunable params so decided to try out a few. I discovered that adding -txcsum and -rxcsum (i.e. disabling hardware checksuming) to the ifconfig statement, the performance was as quick as it is on that other OS! I'm not sure you suffers from the same problem but there was a Tx checksum offload related bug in msk(4) driver and it was fixed in HEAD. How about applying the diff in CVS rev 1.33 of if_msk? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/msk/if_msk.c.diff?r1=1.32;r2=1.33;f=h Yong-Hyeon Pyun can probably explain what's going on here. I've CC'd him on this mail; he usually hangs out on -stable though. You need to keep something in mind here: Marvell does not give out documentation for their cards publicly, so Yong-Hyeon has to reverse-engineer and tinker with what he already knows. Some hardware feature do not work, others are buggy, others work fine on specific revisions of the chip while later ones break. And if you tell me Well Linux has support for this chip!, I will throw the following evidence back in your face: Marvell and other companies are giving Linux developers development PCI cards to develop drivers with (sometimes even before the card is out in the market), so Linux has the upper hand here. They are not doing this with the BSDs. Purely as an example: in my Wiki, section Network devices, see the entry for the 88E8040 NIC. I'm still working with Yong-Hyeon to try to get him access to a laptop that has this chip so he can write the driver. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues This should give you some idea of the complexities. As I said, Linux has the upper hand, because they're getting support from Marvell. It seems that hw cs is on by default so I added the above to my ifoncfig line in /etc/rc.conf and now all is snappy! I was wondering how could this be the case and also if anyone else had this issue with Marvell chips? I would urge you to go out and purchase an Intel Pro/1000 PT card, which runs for around 30-40 USD. It's good to have a spare NIC on hand anyways -- your 3C509 xl(4) based NIC probably won't cut it, especially if you're complaining about performance. :-) No one uses those cards any more except individuals running on hardware from 1997, which you are obviously not. -- Regards, Pyun YongHyeon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
