Re: [BUG] Tulip for ULi M5263: No packets transmitted
Hello again. An update: the patch you suggested combined with a bios update have fixed the remaining issues. All is peachy now. Thanks everyone. On Mon, 2005-07-25 at 19:46 +0100, Ricardo Bugalho wrote: > Hello, > yes it does help. Thanks. > Still not perfect though, it gives a warning, reports to be working on > half-duplex and I can't use mii-tool with it. > > Here's the dmesg output (2.6.12.3 + patch): > Linux Tulip driver version 1.1.13 (May 11, 2002) > ACPI: PCI Interrupt :00:0d.0[A] -> GSI 17 (level, low) -> IRQ 17 > tulip0: EEPROM default media type Autosense. > tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) > block. > tulip0: Index #1 - Media 10baseT (#0) described by a (128) > block. > tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) > block. > tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) > block. > tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII > (0) block. > tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 > non-MII (0) block. > tulip0: ***WARNING***: No MII transceiver found! > eth0: ULi M5261/M5263 rev 64 at f884cc00, 00:0B:6A:D1:FC:B9, IRQ 17. > ... > eth0: Setting half-duplex based on MII#1 link partner capability of > . > ... > > When I try to run mii-tool, it yields: > # mii-tool eth0 > SIOCGMIIPHY on 'eth0' failed: No such device > > > On Mon, 2005-07-25 at 14:16 +0200, Jiri Benc wrote: > > > Does tulip-fixes-for-uli5261.patch from -mm tree help? > > > -- Ricardo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] Tulip for ULi M5263: No packets transmitted
Hello again. An update: the patch you suggested combined with a bios update have fixed the remaining issues. All is peachy now. Thanks everyone. On Mon, 2005-07-25 at 19:46 +0100, Ricardo Bugalho wrote: Hello, yes it does help. Thanks. Still not perfect though, it gives a warning, reports to be working on half-duplex and I can't use mii-tool with it. Here's the dmesg output (2.6.12.3 + patch): Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt :00:0d.0[A] - GSI 17 (level, low) - IRQ 17 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a unknown (128) block. tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. tulip0: ***WARNING***: No MII transceiver found! eth0: ULi M5261/M5263 rev 64 at f884cc00, 00:0B:6A:D1:FC:B9, IRQ 17. ... eth0: Setting half-duplex based on MII#1 link partner capability of . ... When I try to run mii-tool, it yields: # mii-tool eth0 SIOCGMIIPHY on 'eth0' failed: No such device On Mon, 2005-07-25 at 14:16 +0200, Jiri Benc wrote: Does tulip-fixes-for-uli5261.patch from -mm tree help? -- Ricardo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] Tulip for ULi M5263: No packets transmitted
Hello, yes it does help. Thanks. Still not perfect though, it gives a warning, reports to be working on half-duplex and I can't use mii-tool with it. Here's the dmesg output (2.6.12.3 + patch): Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt :00:0d.0[A] -> GSI 17 (level, low) -> IRQ 17 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a (128) block. tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. tulip0: ***WARNING***: No MII transceiver found! eth0: ULi M5261/M5263 rev 64 at f884cc00, 00:0B:6A:D1:FC:B9, IRQ 17. ... eth0: Setting half-duplex based on MII#1 link partner capability of . ... When I try to run mii-tool, it yields: # mii-tool eth0 SIOCGMIIPHY on 'eth0' failed: No such device On Mon, 2005-07-25 at 14:16 +0200, Jiri Benc wrote: > Does tulip-fixes-for-uli5261.patch from -mm tree help? > -- Ricardo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] Tulip for ULi M5263: No packets transmitted
On Sat, 23 Jul 2005 20:22:04 +0100, Ricardo Bugalho wrote: > the tulip driver isn't work out for my ULi M5263 network adapter. > The driver loads and the interface receives packets but it won't > transmit any. Running a packet capture on it shows no outbound packets, > so I guess the driver thinks the card is screwed up and can't transmit. Does tulip-fixes-for-uli5261.patch from -mm tree help? http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/broken-out/tulip-fixes-for-uli5261.patch -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] Tulip for ULi M5263: No packets transmitted
On Sat, 23 Jul 2005 20:22:04 +0100, Ricardo Bugalho wrote: the tulip driver isn't work out for my ULi M5263 network adapter. The driver loads and the interface receives packets but it won't transmit any. Running a packet capture on it shows no outbound packets, so I guess the driver thinks the card is screwed up and can't transmit. Does tulip-fixes-for-uli5261.patch from -mm tree help? http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/broken-out/tulip-fixes-for-uli5261.patch -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] Tulip for ULi M5263: No packets transmitted
Hello, yes it does help. Thanks. Still not perfect though, it gives a warning, reports to be working on half-duplex and I can't use mii-tool with it. Here's the dmesg output (2.6.12.3 + patch): Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt :00:0d.0[A] - GSI 17 (level, low) - IRQ 17 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a unknown (128) block. tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. tulip0: ***WARNING***: No MII transceiver found! eth0: ULi M5261/M5263 rev 64 at f884cc00, 00:0B:6A:D1:FC:B9, IRQ 17. ... eth0: Setting half-duplex based on MII#1 link partner capability of . ... When I try to run mii-tool, it yields: # mii-tool eth0 SIOCGMIIPHY on 'eth0' failed: No such device On Mon, 2005-07-25 at 14:16 +0200, Jiri Benc wrote: Does tulip-fixes-for-uli5261.patch from -mm tree help? -- Ricardo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[BUG] Tulip for ULi M5263: No packets transmitted
Hello, the tulip driver isn't work out for my ULi M5263 network adapter. The driver loads and the interface receives packets but it won't transmit any. Running a packet capture on it shows no outbound packets, so I guess the driver thinks the card is screwed up and can't transmit. I have a 939 AX8-M Motherboard with integrated ULi M5263 network adapter and the kernel version is 2.6.12.3. Another person with the same motherboard and problem was able to get the adapter running with ULi's GPL driver for 2.6.8 (haven't tryed that yet) but since the kernel driver's code explitly refers the M5262/3, I guess it's supposed to be supported. On dmesg, the following messages apear when the driver is loaded: Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt :00:0d.0[A] -> GSI 17 (level, low) -> IRQ 17 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a (128) block. tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. tulip0: MII transceiver #31 config status 7849 advertising 01e1. When the interface is configured, the following message apears in dmesg: eth0: Invalid media table selection 128. A full copy of dmesg is attached. Thanks for your attention. -- Ricardo Linux version 2.6.12.3 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian 1:3.3.6-7)) #1 Sun Jul 17 23:26:55 WEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 3ffb (usable) BIOS-e820: 3ffb - 3ffc (ACPI data) BIOS-e820: 3ffc - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: ff7c - 0001 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. 896MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 229376 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v000 ACPIAM) @ 0x000f9e50 ACPI: RSDT (v001 A M I OEMRSDT 0x05000510 MSFT 0x0097) @ 0x3ffb ACPI: FADT (v001 A M I OEMFACP 0x05000510 MSFT 0x0097) @ 0x3ffb0200 ACPI: MADT (v001 A M I OEMAPIC 0x05000510 MSFT 0x0097) @ 0x3ffb0390 ACPI: OEMB (v001 A M I AMI_OEM 0x05000510 MSFT 0x0097) @ 0x3ffc0040 ACPI: DSDT (v001 939A8 939A8133 0x0133 INTL 0x02002026) @ 0x ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:15 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bf7c) Built 1 zonelists Kernel command line: ro root=/dev/hda3 single mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 1799.791 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 903724k/917504k available (1533k kernel code, 13204k reserved, 719k data, 180k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 3579.90 BogoMIPS (lpj=1789952) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff e3d3fbff 0001 0001 CPU: After vendor identify, caps: 078bfbff e3d3fbff 0001 0001 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff e3d3fbff 0010 0001 0001 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 00 Enabling fast FPU save and restore... done.
[BUG] Tulip for ULi M5263: No packets transmitted
Hello, the tulip driver isn't work out for my ULi M5263 network adapter. The driver loads and the interface receives packets but it won't transmit any. Running a packet capture on it shows no outbound packets, so I guess the driver thinks the card is screwed up and can't transmit. I have a 939 AX8-M Motherboard with integrated ULi M5263 network adapter and the kernel version is 2.6.12.3. Another person with the same motherboard and problem was able to get the adapter running with ULi's GPL driver for 2.6.8 (haven't tryed that yet) but since the kernel driver's code explitly refers the M5262/3, I guess it's supposed to be supported. On dmesg, the following messages apear when the driver is loaded: Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt :00:0d.0[A] - GSI 17 (level, low) - IRQ 17 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a unknown (128) block. tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. tulip0: MII transceiver #31 config status 7849 advertising 01e1. When the interface is configured, the following message apears in dmesg: eth0: Invalid media table selection 128. A full copy of dmesg is attached. Thanks for your attention. -- Ricardo Linux version 2.6.12.3 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian 1:3.3.6-7)) #1 Sun Jul 17 23:26:55 WEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 3ffb (usable) BIOS-e820: 3ffb - 3ffc (ACPI data) BIOS-e820: 3ffc - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: ff7c - 0001 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. 896MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 229376 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v000 ACPIAM) @ 0x000f9e50 ACPI: RSDT (v001 A M I OEMRSDT 0x05000510 MSFT 0x0097) @ 0x3ffb ACPI: FADT (v001 A M I OEMFACP 0x05000510 MSFT 0x0097) @ 0x3ffb0200 ACPI: MADT (v001 A M I OEMAPIC 0x05000510 MSFT 0x0097) @ 0x3ffb0390 ACPI: OEMB (v001 A M I AMI_OEM 0x05000510 MSFT 0x0097) @ 0x3ffc0040 ACPI: DSDT (v001 939A8 939A8133 0x0133 INTL 0x02002026) @ 0x ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:15 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bf7c) Built 1 zonelists Kernel command line: ro root=/dev/hda3 single mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 1799.791 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 903724k/917504k available (1533k kernel code, 13204k reserved, 719k data, 180k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 3579.90 BogoMIPS (lpj=1789952) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff e3d3fbff 0001 0001 CPU: After vendor identify, caps: 078bfbff e3d3fbff 0001 0001 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff e3d3fbff 0010 0001 0001 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 00 Enabling fast FPU save and restore...
