Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
Hello, one of my motherboards has an onboard Attansic network interface, I think an AR8121. # pciconf -lcv no...@pci0:4:0:0: class=0x02 card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' device = 'L1 Gigabit Ethernet 10/100/1000Base-T Ethernet Controller' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[48] = MSI supports 1 message, 64 bit cap 10[58] = PCI-Express 1 endpoint cap 03[6c] = VPD Today I decided to give it a try. But if I try loading the if_age module, the system prints the following lines and then it freezes. age0: mem 0xfbdc-0xfbdf irq 36 at device 0.0 on pci4 age0: PCI device revision : 0x00b0 age0: Chip id/revision : 0x9006 age0: 1280 Tx FIFO, 2364 Rx FIFO age0: MSIX count : 0 age0: MSI count : 1 age0: Using 1 MSI messages. age0: Read request size : 512 bytes. age0: TLP payload size : 128 bytes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
>On Mon, Jan 05, 2009 at 11:36:54AM +0100, Barbara wrote: > >[...] > > > I've tried all the thing you've suggested with > > the same result. > > I've disabled "LAN Option ROM", but it seems that I don't have > > the other options you mentioned. > > I've downloaded and burned the 7.1-RELEASE dvd > > and tried to boot from it, but it hangs at the same point. > > Finally I've tried > > booting a CURRENT snapshot cd (8.0-CURRENT-200812) and I was able to properly > > configure the device in sysinstall. > > Any idea about the problem? > >No, there is no source code differences between CURRENT and 7.1- RELEASE. > > > I've installed > > from 7.0 and I have another NIC, but being now age in GENERIC, I hope it will > > not cause troubles to other people installing for the first time. > > Anyway thank > > you for now, and ask me if there is something that I can do to fix the problem > > like more tests, patches, etc. > > > >Would try the following WIP version? >http://people. freebsd.org/~yongari/age/if_age.c >http://people.freebsd. org/~yongari/age/if_agereg.h >I have no longer access to L1 hardware so I don't know whether it >helps or not. > >-- >Regards, >Pyun YongHyeon Well, it works! As I've said, it's not a real problem for me, but I'm so sorry about not having tested before so it could be merged before 7.1-RELEASE, but I had it disabled and nearly forgot about that. Please, feel free to ask whenever you want if you want me doing tests on that NIC. Thanks Barbara ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
Any news about that? http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
> Today I decided to give it a try. > But if I try loading the if_age module, the > system prints the following lines and then it freezes. Could you please print the full dmesg / uname (build date) output? Thanks. --- Kevin K. Systems Administrator www.linux-vps-servers.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
>> Today I decided to give it a try. >> But if I try loading the if_age module, the >> system prints the following lines and then it freezes. > > > >Could you please print the full dmesg / uname (build date) output? > > >Thanks. > > >--- >Kevin K. >Systems Administrator >www.linux-vps-servers.com > Sure! /usr/src has been synced right before starting the buildworld. # uname -a FreeBSD satanasso.local.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Dec 31 03:55: 33 CET 2008 r...@satanasso.local.net:/usr/obj/usr/src/sys/SATANASSO i386 If I load age adding it in my kernconf or with the loader, the system freezes so the relevant part on dmesg should be the following two lines: pci4: on pcib5 pci4: at device 0.0 (no driver attached) Here comes the full dmesg output. Unfortunately the web client of my mail provider, does something stupid with the text, so I know it could be confused. If asked I can send it via email as attachment. # dmesg Copyright (c) 1992- 2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Wed Dec 31 03:55:33 CET 2008 r...@satanasso. local.net:/usr/obj/usr/src/sys/SATANASSO Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2499.74-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x60fb1 Stepping = 1 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f Cores per package: 2 real memory = 2147155968 (2047 MB) avail memory = 2087157760 (1990 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 vgapci0: port 0xdc00-0xdc7f mem 0xfa00- 0xfaff,0xd000-0xdfff,0xf800-0xf9ff irq 24 at device 0.0 on pci2 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] pcib3: irq 31 at device 3.0 on pci0 pci6: on pcib3 pcib4: irq 35 at device 3.1 on pci0 pci5: on pcib4 pcib5: irq 39 at device 3.2 on pci0 pci4: on pcib5 pci4: at device 0.0 (no driver attached) pcib6: irq 43 at device 3.3 on pci0 pci3: on pcib6 atapci0: port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807, 0xc480-0xc483,0xc400-0xc40f,0xc000-0xc0ff irq 21 at device 15.0 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] uhci0: port 0xb480-0xb49f irq 20 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb800-0xb81f irq 22 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb880-0xb89f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xbc00-0xbc1f irq 23 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xf7fffc00-0xf7fffcff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 pcib7: at device 19.0 on pci0 pci128: on pcib7 pcm0: mem 0xfbffc000-0xfbff irq 17 at device 1.0 on pci128 pcm0: [ITHREAD] pcib8: at device 19.1 on pci0 pci7: on pcib8 rl0: port 0xe800-0xe8ff mem 0xfbeffc00-0xfbeffcff irq 19 at device 9.0 on pci7 miibus0: on rl0 rlphy0: PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:08:a1:27: 1f:bb rl0: [ITHREAD] acpi_button0: on acpi0 acpi_bu
RE: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
>>> Today I decided to give it a try. >>> But if I try loading the if_age module, >the >>> system prints the following lines and then it freezes. >> >> >> >>Could you >please print the full dmesg / uname (build date) output? >> >> >>Thanks. >> >> >>--- > >>Kevin K. >>Systems Administrator >>www.linux-vps- servers.com >> > Maybe this is better: http://pastebin.ca/1297510 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Wed, Dec 31, 2008 at 06:34:08AM +0100, Barbara wrote: > Hello, > one of my motherboards has an onboard Attansic network interface, I > think an AR8121. > > # pciconf -lcv > no...@pci0:4:0:0: class=0x02 > card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00 > vendor = 'Attansic > (Now owned by Atheros)' > device = 'L1 Gigabit Ethernet 10/100/1000Base-T > Ethernet Controller' > class = network > subclass = ethernet > cap > 01[40] = powerspec 2 supports D0 D3 current D0 > cap 05[48] = MSI supports > 1 message, 64 bit > cap 10[58] = PCI-Express 1 endpoint > cap 03[6c] = VPD > > > Today I decided to give it a try. > But if I try loading the if_age module, the > system prints the following lines and then it freezes. > > age0: Technology Corp, L1 Gigabit Ethernet> mem 0xfbdc-0xfbdf irq 36 at > device 0.0 on pci4 > age0: PCI device revision : 0x00b0 > age0: Chip id/revision : > 0x9006 > age0: 1280 Tx FIFO, 2364 Rx FIFO > age0: MSIX count : 0 > age0: MSI count : > 1 > age0: Using 1 MSI messages. > age0: Read request size : 512 bytes. > age0: TLP > payload size : 128 bytes. > I guess it could be related with VPD access code in age(4) or automatic power-down feature of hardware. Unfortunately I have no longer access to L1 hardware so it looks hard to write a patch for the issue. Would you try following instructions? - Shutdown your box. - Completely remove power cord from your system and wait 5 to 10 min.(Just turning system off is not enough.) - Make sure to plug UTP cable to your controller before system boot. - Plug power cord and let system boot. - Enter BIOS menu and search onboard PCIe LAN configuration in the menu. If "LAN Option ROM" was enabled, disable the option. - Some motherboard might have set another option for "Check Atheros LAN cable". If it was set, disable it. If you also have an option for "Asus Express Gate" try disabling it. - Save changes and reboot. Does that make any difference? -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
>On Wed, Dec 31, 2008 at 06:34:08AM +0100, Barbara wrote: > > Hello, > > one of my motherboards has an onboard Attansic network interface, I > > think an AR8121. > > > > # pciconf -lcv > > no...@pci0:4:0:0: class=0x02 > > card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00 > > vendor = 'Attansic > > (Now owned by Atheros)' > > device = 'L1 Gigabit Ethernet 10/100/1000Base-T > > Ethernet Controller' > > class = network > > subclass = ethernet > > cap > > 01[40] = powerspec 2 supports D0 D3 current D0 > > cap 05[48] = MSI supports > > 1 message, 64 bit > > cap 10[58] = PCI-Express 1 endpoint > > cap 03[6c] = VPD > > > > > > Today I decided to give it a try. > > But if I try loading the if_age module, the > > system prints the following lines and then it freezes. > > > > age0: > Technology Corp, L1 Gigabit Ethernet> mem 0xfbdc- 0xfbdf irq 36 at > > device 0.0 on pci4 > > age0: PCI device revision : 0x00b0 > > age0: Chip id/revision : > > 0x9006 > > age0: 1280 Tx FIFO, 2364 Rx FIFO > > age0: MSIX count : 0 > > age0: MSI count : > > 1 > > age0: Using 1 MSI messages. > > age0: Read request size : 512 bytes. > > age0: TLP > > payload size : 128 bytes. > > > >I guess it could be related with VPD access code in age(4) or >automatic power-down feature of hardware. Unfortunately I have no >longer access to L1 hardware so it looks hard to write a patch for >the issue. Would you try following instructions? > - Shutdown your box. > - Completely remove power cord from your system and wait 5 to 10 > min.(Just turning system off is not enough.) > - Make sure to plug UTP cable to your controller before system > boot. > - Plug power cord and let system boot. > - Enter BIOS menu and search onboard PCIe LAN configuration in the > menu. If "LAN Option ROM" was enabled, disable the option. > - Some motherboard might have set another option for "Check > Atheros LAN cable". If it was set, disable it. If you also have > an option for "Asus Express Gate" try disabling it. > - Save changes and reboot. > >Does that make any difference? > >-- >Regards, >Pyun YongHyeon I've tried all the thing you've suggested with the same result. I've disabled "LAN Option ROM", but it seems that I don't have the other options you mentioned. I've downloaded and burned the 7.1-RELEASE dvd and tried to boot from it, but it hangs at the same point. Finally I've tried booting a CURRENT snapshot cd (8.0-CURRENT-200812) and I was able to properly configure the device in sysinstall. Any idea about the problem? I've installed from 7.0 and I have another NIC, but being now age in GENERIC, I hope it will not cause troubles to other people installing for the first time. Anyway thank you for now, and ask me if there is something that I can do to fix the problem like more tests, patches, etc. Best regards Barbara ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Mon, Jan 05, 2009 at 11:36:54AM +0100, Barbara wrote: [...] > I've tried all the thing you've suggested with > the same result. > I've disabled "LAN Option ROM", but it seems that I don't have > the other options you mentioned. > I've downloaded and burned the 7.1-RELEASE dvd > and tried to boot from it, but it hangs at the same point. > Finally I've tried > booting a CURRENT snapshot cd (8.0-CURRENT-200812) and I was able to > properly > configure the device in sysinstall. > Any idea about the problem? No, there is no source code differences between CURRENT and 7.1-RELEASE. > I've installed > from 7.0 and I have another NIC, but being now age in GENERIC, I hope it > will > not cause troubles to other people installing for the first time. > Anyway thank > you for now, and ask me if there is something that I can do to fix the > problem > like more tests, patches, etc. > Would try the following WIP version? http://people.freebsd.org/~yongari/age/if_age.c http://people.freebsd.org/~yongari/age/if_agereg.h I have no longer access to L1 hardware so I don't know whether it helps or not. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Sat, Jan 10, 2009 at 04:07:24AM +0100, Barbara wrote: [...] > >Would try the following WIP version? > >http://people. > freebsd.org/~yongari/age/if_age.c > >http://people.freebsd. > org/~yongari/age/if_agereg.h > >I have no longer access to L1 hardware so I don't > know whether it > >helps or not. > > > >-- > >Regards, > >Pyun YongHyeon > > Well, it > works! > As I've said, it's not a real problem for me, but I'm so sorry about not > having tested before so it could be merged before 7.1-RELEASE, but I had it > disabled and nearly forgot about that. > Please, feel free to ask whenever you > want if you want me doing tests on that NIC. > I'm confused, the WIP version works whereas age(4) in 7.1-RELEASE didn't work right? If the WIP version works, would you show me the output of verbose boot message? -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote: > > Any news about that? > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html > I'm sorry, I forgot this issue which was caused by my disk crash happened in the end of Jan, 2009. I've updated age(4) patch in the following URL. http://people.freebsd.org/~yongari/age/age.diff Please test the with 1. shutdown your box 2. remove power cable and wait 5 min. 3. unplug UTP cabble 4. boot and see whether age(4) does not lockup your box 5. plug UTP cable and see whether age(4) can send/receive traffics And please do 1. reboot your box with UTP cable plugged in 2. check whether age(4) works Please also see whether ethernet MAC address is correctly detected in both cases. Thanks for reminder. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
> On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote: > > > > Any news about that? > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html > > > > I'm sorry, I forgot this issue which was caused by my disk crash > happened in the end of Jan, 2009. > I've updated age(4) patch in the following URL. > http://people.freebsd.org/~yongari/age/age.diff > > Please test the with > 1. shutdown your box > 2. remove power cable and wait 5 min. > 3. unplug UTP cabble > 4. boot and see whether age(4) does not lockup your box > 5. plug UTP cable and see whether age(4) can send/receive traffics > > And please do > 1. reboot your box with UTP cable plugged in > 2. check whether age(4) works > > Please also see whether ethernet MAC address is correctly detected > in both cases. > > Thanks for reminder. > I tried with the last commited version after updating src with no luck: still hang on boot (actually it hangs when I kldload it, as I removed it from my KERNCONF, so I can boot with the NIC enabled). Then I applied your patch and, as with the previous one you asked me to try, it's working. I did the two tests exactly how you asked and everything seems fine. The MAC address is correct in both cases. The connection is working and I did some huge file transfer with ssh with another pc with performance comparable with my rl0 (I think at the limits of a 100Mbps net, imposed by my router). Here you can find my dmesg -a http://pastebin.com/f4afd50db If you have any other test I can do for you, please ask. Do you have any idea if it will included it 7.2-RELEASE? Thanks Barbara ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Sat, Mar 28, 2009 at 02:32:09AM +0100, barbara wrote: > > On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote: > > > > > > Any news about that? > > > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html > > > > > > > I'm sorry, I forgot this issue which was caused by my disk crash > > happened in the end of Jan, 2009. > > I've updated age(4) patch in the following URL. > > http://people.freebsd.org/~yongari/age/age.diff > > > > Please test the with > > 1. shutdown your box > > 2. remove power cable and wait 5 min. > > 3. unplug UTP cabble > > 4. boot and see whether age(4) does not lockup your box > > 5. plug UTP cable and see whether age(4) can send/receive traffics > > > > And please do > > 1. reboot your box with UTP cable plugged in > > 2. check whether age(4) works > > > > Please also see whether ethernet MAC address is correctly detected > > in both cases. > > > > Thanks for reminder. > > > > I tried with the last commited version after updating src with no luck: still > hang on boot (actually it hangs when I kldload it, as I removed it from my > KERNCONF, so I can boot with the NIC enabled). > Then I applied your patch and, as with the previous one you asked me to try, > it's working. > > I did the two tests exactly how you asked and everything seems fine. > The MAC address is correct in both cases. > The connection is working and I did some huge file transfer with ssh with > another pc with performance comparable with my rl0 (I think at the limits of > a 100Mbps net, imposed by my router). > > Here you can find my dmesg -a > http://pastebin.com/f4afd50db > If you have any other test I can do for you, please ask. > FYI, patch committed to HEAD(r190499). > Do you have any idea if it will included it 7.2-RELEASE? > I'm not sure, it needs more testing as there are several variants of Attansic L1 controllers. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
