Re: 3C940 / Asus P4P800 gigabit LAN driver
On Thu, Nov 06, 2003 at 09:52:27PM -0800, Matthew Dillon wrote: :I just tried Jung-uk Kim's driver on -stable and sofar it works OK: : ... and I just ported it to DragonFly and it works fine there too with an ASUS K8V Motherboard. Kudos! Good to hear that ;) Jung-uk has provided me with some more patches to fix some issues with promiscuous mode. I have not had time to look at those yet. [EMAIL PROTECTED] committed some extra PCI-IDs to sk(4) yesterday, you might want to fold those into DragonFly as well. cheers, Wilko -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
:I just tried Jung-uk Kim's driver on -stable and sofar it works OK: : ... and I just ported it to DragonFly and it works fine there too with an ASUS K8V Motherboard. Kudos! -Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat, Sep 13, 2003 at 03:37:51PM +0100, Stuart Walsh wrote: On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote: I have my own *working* driver, which is for 4-STABLE. It works with SK-9521 V2.0 (for me, at least) and it should work with 3C940. Note: This driver is ported from Nathan L. Binkert's OpenBSD driver. Note: This is completely independent from Stuart Walsh's work. ;-) Note: You must recompile MII driver and dependent network drivers. It's worth noting my patch was a port of Natan's patch also(which is actually Bill's driver technically speaking ;), so I'd be interested to see where i went wrong. But if it works then great, I'll get on with something else :) It's somewhat difficult to fine tune a driver when you dont actually own the hardware in question. I just tried Jung-uk Kim's driver on -stable and sofar it works OK: pcib2: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 skc0: 3Com 3C940 Gigabit Ethernet port 0xd400-0xd4ff mem 0xfeaf8000-0xfeafbfff irq 11 at device 5.0 on pci2 skc0: 3Com Gigabit LOM (3C940) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:0c:6e:4f:77:0c miibus0: MII bus on sk0 e1000phy0: Marvell Semiconductor 88E1000* gigabit PHY on miibus0 e1000phy0: 1000baseTX-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX, 10baseTX, auto isp0: Qlogic ISP 1020/1040 PCI SCSI Adapter port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 10 at device 9.0 on pci2 This is with the LOM found on Asus P4P800 btw. Curious minds obviously wonder about the difference with Stuart's driver ;) ENOTIME to check right now. Sleep first. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote: I have my own *working* driver, which is for 4-STABLE. It works with SK-9521 V2.0 (for me, at least) and it should work with 3C940. Note: This driver is ported from Nathan L. Binkert's OpenBSD driver. Note: This is completely independent from Stuart Walsh's work. ;-) Note: You must recompile MII driver and dependent network drivers. It's worth noting my patch was a port of Natan's patch also(which is actually Bill's driver technically speaking ;), so I'd be interested to see where i went wrong. But if it works then great, I'll get on with something else :) It's somewhat difficult to fine tune a driver when you dont actually own the hardware in question. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 05, 2003 at 07:50:24PM +0100, Stuart Walsh wrote: On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. Sorry for the delay. I just upgraded this machine to -current and things have just now settled down. I compiled the if_sk module (it seemed to want yukonreg.h, which I found on your site), loaded it, and got this: skc0: 3Com 3C940 Gigabit Ethernet port 0xb800-0xb8ff mem 0xdc80-0xdc803fff irq 5 at device 9.0 on pci0 skc0: 3Com Gigabit LOM (3C940) sk0: GI Yukon MAC on skc0 sk0: Ethernet address: xx:xx:xx:xx:xx:xx Yukon chip deteched Phy type 4 addr 0 sk_intr sk_intr sk_intr sk_intr sk_intr sk_intr sk_intr At this point the machine seemed to be writing to swap and kldload was hung, so I rebooted. Note that this the onboard 3C940 on the Asus A77V600 motherboard. I will be more than happy to help test any more code you have to get this driver working. -jre ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 05, 2003 at 07:50:24PM +0100, Stuart Walsh wrote: On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've Changing nappies? ;) took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. OK.. what it does is as follows: - print ethernet address - then it prints: Yukon chip detected Phy type 4 adr 0 initialising yukon device phy reset set mac reset set mac reset clear mac reset set hang This all on an Asus P4P800. Obviously a copper based NIC, without cable connected in this case. hth Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Mon, Aug 25, 2003 at 11:20:23AM -0500, Glenn Johnson wrote: On Mon, Aug 25, 2003 at 11:14:25AM +0100, Stuart Walsh wrote: On Sun Aug 24, 10:42P -0500, Glenn Johnson wrote: On Sun, Aug 24, 2003 at 01:22:39PM +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. I have an Abit IS7 with a 3c940. I also get a lockup at boot time. I tried loading the module after bootup as well. I tried that two times; it loaded one time and locked the machine up the other time. Does it lock up after printing the ethernet address as in Wilko's case? Yes. Does the card work properly if the module does manage to load? I do not know. I did not have a cable plugged in to the 3c940 port at the time. I do remember some message about not being able to set up a jumbo frame. I was going to plug a cable into the port to see if it worked but I was not able to get the module to load again without locking up the machine. Also could you mail your dmesg. Yes, but not until I get home later this evening as the 3c940 is on my home system. Here is my dmesg output: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #94: Mon Aug 25 22:43:06 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GFORCE Preloaded elf kernel /boot/kernel/kernel at 0xc0433000. Preloaded elf module /boot/kernel/if_xl.ko at 0xc04331f4. Preloaded elf module /boot/kernel/miibus.ko at 0xc04332a0. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc043334c. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04333f8. Preloaded elf module /boot/kernel/random.ko at 0xc04334a4. Preloaded elf module /boot/kernel/acpi.ko at 0xc0433550. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2405.47-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 536805376 (511 MB) avail memory = 516743168 (492 MB) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: IntelR AWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00fdd30 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 IOAPIC #0 intpin 16 - irq 2 IOAPIC #0 intpin 19 - irq 5 IOAPIC #0 intpin 18 - irq 9 IOAPIC #0 intpin 23 - irq 10 IOAPIC #0 intpin 17 - irq 11 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: serial bus, USB at device 29.2 (no driver attached) pci0: serial bus, USB at device 29.3 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pci2: network, ethernet at device 2.0 (no driver attached) xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xfb004000-0xfb00407f irq 11 at device 9.0 on pci2 xl0: Ethernet address: 00:01:02:84:81:50 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 SATA150 controller port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 9 at device 31.2 on pci0 ata0: at 0x1f0 irq 14 on atapci0
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 01:22:39PM +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. I have an Abit IS7 with a 3c940. I also get a lockup at boot time. I tried loading the module after bootup as well. I tried that two times; it loaded one time and locked the machine up the other time. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun Aug 24, 10:42P -0500, Glenn Johnson wrote: On Sun, Aug 24, 2003 at 01:22:39PM +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. I have an Abit IS7 with a 3c940. I also get a lockup at boot time. I tried loading the module after bootup as well. I tried that two times; it loaded one time and locked the machine up the other time. Does it lock up after printing the ethernet address as in Wilko's case? Does the card work properly if the module does manage to load? Also could you mail your dmesg. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Mon, Aug 25, 2003 at 11:14:25AM +0100, Stuart Walsh wrote: On Sun Aug 24, 10:42P -0500, Glenn Johnson wrote: On Sun, Aug 24, 2003 at 01:22:39PM +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. I have an Abit IS7 with a 3c940. I also get a lockup at boot time. I tried loading the module after bootup as well. I tried that two times; it loaded one time and locked the machine up the other time. Does it lock up after printing the ethernet address as in Wilko's case? Yes. Does the card work properly if the module does manage to load? I do not know. I did not have a cable plugged in to the 3c940 port at the time. I do remember some message about not being able to set up a jumbo frame. I was going to plug a cable into the port to see if it worked but I was not able to get the module to load again without locking up the machine. Also could you mail your dmesg. Yes, but not until I get home later this evening as the 3c940 is on my home system. -- Glenn Johnson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Right, that is a valuable datapoint. Are you running up do date -current, or is there anything strange about your setup at all? Not that I know, but given that it works for another P4P800 I can find out what is special locally. W/ -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Hi Guys, I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix the swap-issue, so that I can reboot easily, I would test your patches, too. Jens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: ... Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? I just did a buildworld on a freshly checked out tree, applied the patches and tried again. Unfortunately that did not help. I continue my investigation. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
In message [EMAIL PROTECTED], Jens Rehsack writes: I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix the swap-issue, so that I can reboot easily, I would test your patches, too. swap-issue ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:17:52PM +, Jens Rehsack wrote: Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Hi Guys, I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix the swap-issue, so that I can reboot easily, I would test your patches, too. Que? What swap issue? I can dual boot stable and current just fine on the P4P800. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 03:13:18PM +0200, Wilko Bulte wrote: On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: ... Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? I just did a buildworld on a freshly checked out tree, applied the patches and tried again. Unfortunately that did not help. I continue my investigation. Going to the latest BIOS also did not make any difference (long shot, I know). Can someone with a P4P800 who has gotten it to work please post their dmesg? Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
3C940 / Asus P4P800 gigabit LAN driver
Hi,
I ported the openbsd additions to the sk driver to support the 3c940
gigabit network card which is commonly found in the above asus
motherboard. Testers/comments/commits welcome, but please don't blame
me if it burns your house down or something :)
Apply the diff in /usr/src/sys. It will have to be a fairly recent
-current because of the recent pci header reloactions.
Please be aware that I have had reports of panics on kldunloading the sk
module. I don't posess the hardware myself and this could be present in
the sk driver in general, so more information on this would be greatly
received.
Regards,
Stuart Walsh
Index: dev/mii/e1000phy.c
===
RCS file: /home/ncvs/src/sys/dev/mii/e1000phy.c,v
retrieving revision 1.8
diff -u -r1.8 e1000phy.c
--- dev/mii/e1000phy.c 19 Jan 2003 02:59:32 - 1.8
+++ dev/mii/e1000phy.c 23 Aug 2003 15:17:42 -
@@ -87,7 +86,8 @@
ma = device_get_ivars(dev);
id = ((ma-mii_id1 16) | ma-mii_id2) E1000_ID_MASK;
- if (id != E1000_ID_88E1000 id != E1000_ID_88E1000S) {
+ if (id != E1000_ID_88E1000 id != E1000_ID_88E1000S
+id != E1011_ID) {
return ENXIO;
}
@@ -101,6 +101,9 @@
struct mii_softc *sc;
struct mii_attach_args *ma;
struct mii_data *mii;
+#if 0
+u_int32_t id;
+#endif
getenv_int(e1000phy_debug, e1000phy_debug);
@@ -117,6 +120,14 @@
sc-mii_flags |= MIIF_NOISOLATE;
mii-mii_instance++;
+
+#if 0
+id = ((ma-mii_id1 16) | ma-mii_id2) E1000_ID_MASK;
+
+if ((id == E1011_ID) (PHY_READ(sc, E1000_ESSR) E1000_ESSR_FIBER_LINK))
+sc-mii_flags |= MIIF_HAVEFIBER;
+#endif
+
e1000phy_reset(sc);
device_printf(dev, );
@@ -126,27 +137,37 @@
ADD(IFM_MAKEWORD(IFM_ETHER, IFM_NONE, 0, sc-mii_inst),
E1000_CR_ISOLATE);
*/
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, 0, sc-mii_inst),
- E1000_CR_SPEED_10);
- printf(10baseT, );
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, IFM_FDX, sc-mii_inst),
- E1000_CR_SPEED_10 | E1000_CR_FULL_DUPLEX);
- printf(10baseT-FDX, );
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, 0, sc-mii_inst),
- E1000_CR_SPEED_100);
- printf(100baseTX, );
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, IFM_FDX, sc-mii_inst),
- E1000_CR_SPEED_100 | E1000_CR_FULL_DUPLEX);
- printf(100baseTX-FDX, );
- /*
-* 1000BT-simplex not supported; driver must ignore this entry,
-* but it must be present in order to manually set full-duplex.
-*/
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, 0, sc-mii_inst),
- E1000_CR_SPEED_1000);
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, IFM_FDX, sc-mii_inst),
- E1000_CR_SPEED_1000 | E1000_CR_FULL_DUPLEX);
- printf(1000baseTX-FDX, );
+#if 0
+if ((sc-mii_flags MIIF_HAVEFIBER) == 0) {
+#endif
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, 0, sc-mii_inst),
+ E1000_CR_SPEED_10);
+ printf(10baseT, );
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, IFM_FDX, sc-mii_inst),
+ E1000_CR_SPEED_10 | E1000_CR_FULL_DUPLEX);
+ printf(10baseT-FDX, );
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, 0, sc-mii_inst),
+ E1000_CR_SPEED_100);
+ printf(100baseTX, );
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, IFM_FDX, sc-mii_inst),
+ E1000_CR_SPEED_100 | E1000_CR_FULL_DUPLEX);
+ printf(100baseTX-FDX, );
+ /*
+* 1000BT-simplex not supported; driver must ignore this entry,
+* but it must be present in order to manually set full-duplex.
+*/
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, 0, sc-mii_inst),
+ E1000_CR_SPEED_1000);
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, IFM_FDX, sc-mii_inst),
+ E1000_CR_SPEED_1000 | E1000_CR_FULL_DUPLEX);
+ printf(1000baseTX-FDX, );
+#if 0
+} else {
+ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_SX, IFM_FDX,sc-mii_inst),
+E1000_CR_SPEED_1000 | E1000_CR_FULL_DUPLEX);
+}
+#endif
+
ADD(IFM_MAKEWORD(IFM_ETHER, IFM_AUTO, 0, sc-mii_inst), 0);
printf(auto\n);
#undef ADD
@@ -233,6 +254,13 @@
(void)e1000phy_mii_phy_auto(sc);
break;
+case IFM_1000_SX:
+e1000phy_reset(sc);
+
+PHY_WRITE(sc, E1000_CR, E1000_CR_FULL_DUPLEX | E1000_CR_SPEED_1000);
+PHY_WRITE(sc, E1000_AR, E1000_FA_1000X_FD);
+break;
+
case IFM_1000_T:
e1000phy_reset(sc);
@@ -351,40 +379,64 @@
return;
}
- if (ssr E1000_SSR_1000MBS)
- mii-mii_media_active |= IFM_1000_T;
- else if (ssr E1000_SSR_100MBS)
- mii-mii_media_active |= IFM_100_TX;
- else
- mii-mii_media_active |=
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat Aug 23, 04:45P +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Apply the diff in /usr/src/sys. It will have to be a fairly recent -current because of the recent pci header reloactions. Please be aware that I have had reports of panics on kldunloading the sk module. I don't posess the hardware myself and this could be present in the sk driver in general, so more information on this would be greatly received. I should have mentioned that there is code in the PHY driver which has #if 0 around it because it deals with fibre links and I have been unable to test that configuration. If you can, please feel free to enable the code. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat Aug 23, 04:45P +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Apply the diff in /usr/src/sys. It will have to be a fairly recent -current because of the recent pci header reloactions. Please be aware that I have had reports of panics on kldunloading the sk module. I don't posess the hardware myself and this could be present in the sk driver in general, so more information on this would be greatly received. Regards, Stuart Walsh Also, I forgot to mention that the code in the PHY driver to deal with fibre links is untested and as such #if 0'd out. If you can test this configuration, feel free to enable the code. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
