[CentOS] Disable autoneg on r8169?
Two problems I hope to solve: 1. The switch being used has autoneg off and has port set to 100 full duplex. 2. Many times NIC fails to come up properly during PXE boot: r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready I can't use ethtool to disable autoneg because the nic driver is built into a bzImage. The root fs is currently being mounted via nfs during pxeboot at speed 10, half-duplex. In the past for sk98lin driver I could pass a kernel module parameter sk98lin.ConType=100FD on the kernel boot line. I looked at the r8169.c and tried to hard code the default to autoneg off but that didn't work. --- linux-2.6.18-274.12.1.el5.i686/drivers/net/r8169.c +++ disable-autoneg/drivers/net/r8169.c @@ -2814,7 +2814,8 @@ * rtl8169_set_speed_xmii takes good care of the Fast Ethernet * only 8101. Don't panic. */ - rtl8169_set_speed(dev, AUTONEG_ENABLE, SPEED_1000, DUPLEX_FULL); + //rtl8169_set_speed(dev, AUTONEG_ENABLE, SPEED_1000, DUPLEX_FULL); + rtl8169_set_speed(dev, AUTONEG_DISABLE, SPEED_100, DUPLEX_FULL); if ((RTL_R8(PHYstatus) TBI_Enable) netif_msg_link(tp)) printk(KERN_INFO PFX %s: TBI auto-negotiating\n, dev-name); Any other ideas? -Scott ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Unplugging DVI causes Disabling IRQ #11
I have some new PC hardware I'm using with the Intel H67 chipset. I created a bzImage I use for a PXE environment for a recovery mode, installing OS images, etc. The new mobo doesn't have a VGA port but instead DVI. Everytime I unplug the DVI cable it seems to cause Disabling IRQ #11. After that the PC is basically unusable. The /proc/interrupts shows that hdd, usb, nic, RAID controller for some reason all share the same interrupt. What the heck? I tried booting with acpi=off and the bios doesn't seem to offer any IRQ/PnP options. Am I missing a specific driver in my bzImage for the H67 chipset or any ideas of what I could try next? It's been a sad day. bash-2.05b# cat /proc/interrupts CPU0 0: 15185951XT-PIC-XTtimer 1: 4XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 7: 75XT-PIC-XTehci_hcd:usb2 8: 1XT-PIC-XTrtc 11:2090574XT-PIC-XTahci, ehci_hcd:usb1, eth0, rr172x I even see a similar error on a fresh CentOS 5.7 install: irq 169: nobody cared (try booting with the irqpoll option) Call Trace: IRQ [800bdf66] __report_bad_irq+0x30/0x7d [800be1a4] note_interrupt+0x1f1/0x232 [800bd6a5] __do_IRQ+0xfa/0x140 [8006d4c1] do_IRQ+0xe9/0xf7 [8005d615] ret_from_intr+0x0/0xa EOI [801a2220] acpi_safe_halt+0x25/0x36 [801a2a88] acpi_processor_idle_simple+0xe6/0x31c [801a29a2] acpi_processor_idle_simple+0x0/0x31c [80048fe2] cpu_idle+0x95/0xb8 [80078a9a] start_secondary+0x479/0x488 handlers: [801fc748] (usb_hcd_irq+0x0/0x55) Disabling IRQ #169 Thanks for any help. -ScottEJ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] chroot from 32-bit to 64-bit filesystem?
I have a 32-bit PXE environment and I want to chroot to a CentOS x64 root filesystem. Of course that doesn't work. Any tricks or hacks that would allow me to do that? Currently I get the error: chroot: /bin/bash: Exec format error What if I updated my PXE environment to 64-bit. Could I then chroot to a 32-bit? I use PXE to quickly troubleshoot both 32-bit and 64-bit arch. Thanks. -Scott ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
