| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 106554 | 2010-01-13 10:13:00 | Question for the Linux gurus.... (PCI-E NIC causing all sorts of trouble) | Agent_24 (57) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 848407 | 2010-01-14 04:24:00 | I don't see much point in asking on the MSI forum just yet, what I was trying to establish was what exactly the errors in my dmesg output I posted were. | Agent_24 (57) | ||
| 848408 | 2010-01-14 04:37:00 | ...No IPv6 router, just IPv4. I assume that message is normal since I don't have IPv6? *-network description: Ethernet interface product: RTL8111/8168B PCI Express Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:02:00.0 logical name: eth0 version: 03 serial: 00:24:21:23:14:d9 size: 10MB/s capacity: 1GB/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:30 ioport:c800(size=256) memory:f8fff000-f8ffffff(prefetchable) memory:f8ff8000-f8ffbfff(prefetchable) memory:fe9e0000-fe9fffff(prefetchable) *-network description: Ethernet interface product: VT6120/VT6121/VT6122 Gigabit Ethernet Adapter vendor: VIA Technologies, Inc. physical id: 0 bus info: pci@0000:04:00.0 logical name: eth1 version: 82 serial: 00:00:00:00:00:04 size: 100MB/s capacity: 1GB/s width: 64 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-velocity driverversion=1.14 duplex=full ip=192.168.0.4 latency=0 link=yes multicast=yes port=twisted pair speed=100MB/s resources: irq:17 ioport:e800(size=256) memory:febffc00-febffcff It is using the via-velocity driver, which I have had no experience with. The driver seems to be up-to-date. It should not be looking for an IPv6 router by default, or you should be able to turn off this default behaviour. Unfortunately there is no manpage explaining how to turn this behaviour off. Sorry, that's all I got to help you with. |
vinref (6194) | ||
| 848409 | 2010-01-14 05:13:00 | Why not its an MSI mobo isnt it. You'll probably find an answer quicker there than here | Speedy Gonzales (78) | ||
| 848410 | 2010-01-14 05:38:00 | Unfortunately there is no manpage explaining how to turn this behaviour off.No man perhaps, but woman with google How To Disable The IPv6 Protocol (www.cyberciti.biz). :p I had to disable IPv6 when it first got enabled by default on Fedora (a few years ago) as it messed up my connection. I haven't had to disable it in later releases though. |
Jen (38) | ||
| 848411 | 2010-01-14 10:13:00 | No man perhaps, but woman with google How To Disable The IPv6 Protocol (www.cyberciti.biz). :p I had to disable IPv6 when it first got enabled by default on Fedora (a few years ago) as it messed up my connection. I haven't had to disable it in later releases though. Bahahaha. I googled and googled for that sort of thing but got nothing. |
vinref (6194) | ||
| 848412 | 2010-01-14 10:47:00 | Why not its an MSI mobo isnt it. You'll probably find an answer quicker there than here Yes but I though the dmesg log was important, thought I'd ask about it as a Linux question rather than an MSI Motherboard question. I had hopes that someone might read it, and say "Aah! Now what you've got there is this that and the other thing, do this to fix it etc. I guess that isn't the case. Although it seemed a hell of a lot more descriptive than anything I would have been able to get out of Windows... No man perhaps, but woman with google How To Disable The IPv6 Protocol (www.cyberciti.biz). :p I had to disable IPv6 when it first got enabled by default on Fedora (a few years ago) as it messed up my connection. I haven't had to disable it in later releases though. What did it mess up? I doubt it was anything as spectacular as my problems, though? There could be something in what you say though, Vista also has IPv6 support by default, although the same isn't true with XP, which I also had problems in... One thing that strikes me as weird is the MAC address. 00:00:00:00:00:04 just doesn't seem usual. |
Agent_24 (57) | ||
| 848413 | 2010-01-14 11:15:00 | ...One thing that strikes me as weird is the MAC address. 00:00:00:00:00:04 just doesn't seem usual. Errr. I missed that too. Yes, the MAC address does not look right. |
vinref (6194) | ||
| 848414 | 2010-01-15 04:27:00 | From the look of it you may be having an IRQ conflict with your sound device. Can you post an output from: cat /proc/interrupts |
ughnz (8297) | ||
| 848415 | 2010-01-15 05:35:00 | CPU0 CPU1 CPU2 CPU3 0: 89 87 883 22462 IO-APIC-edge timer 1: 0 1 14 596 IO-APIC-edge i8042 4: 0 0 0 2 IO-APIC-edge 6: 0 0 0 4 IO-APIC-edge floppy 7: 1 0 0 0 IO-APIC-edge 8: 0 0 0 1 IO-APIC-edge rtc0 9: 0 0 0 0 IO-APIC-fasteoi acpi 14: 1 40 577 1905 IO-APIC-edge pata_atiixp 15: 0 0 0 0 IO-APIC-edge pata_atiixp 16: 0 0 6 1553 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, HDA Intel 17: 0 1 34 2607 IO-APIC-fasteoi ehci_hcd:usb1, eth1 18: 0 5 55 2375 IO-APIC-fasteoi ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, ohci1394, nvidia 19: 0 36 585 7542 IO-APIC-fasteoi ehci_hcd:usb2 24: 10755 0 0 0 HPET_MSI-edge hpet2 29: 0 2 201 7723 PCI-MSI-edge ahci 30: 0 0 0 0 PCI-MSI-edge eth0 NMI: 0 0 0 0 Non-maskable interrupts LOC: 80 8607 8940 4598 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts CNT: 0 0 0 0 Performance counter interrupts PND: 0 0 0 0 Performance pending work RES: 8567 9836 8081 7523 Rescheduling interrupts CAL: 9734 9049 5285 5800 Function call interrupts TLB: 698 559 640 463 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 1 1 1 1 Machine check polls ERR: 1 MIS: 0 |
Agent_24 (57) | ||
| 848416 | 2010-01-16 00:15:00 | Umm.. From the look of the dmesg you posted the system is getting tied up processing IRQ requests. Are you using the irqbalance daemon? Also it looks like you are using APIC, have you tried adding the noapic and nolapic options to the kernel at boot? If you boot up with the options mentioned above and then look at another dump of /proc/interrupts it will show a better indication of what is sharing with what. |
ughnz (8297) | ||
| 1 2 3 | |||||