Re: ip stack broken?
On Sat, 18 Oct 2003, mjoyner wrote: It works fine with a 5.1 kernel. What version is your userland? Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
I removed CPU=athlon from my /etc/make.conf as well as removing -O0 and now it works. I am going to try both one then the other flag to see if it is just one or the other causing the problem, or a combination of both. Doug White wrote: On Sat, 18 Oct 2003, mjoyner wrote: It works fine with a 5.1 kernel. What version is your userland? Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
-march athlon breaks my networking was: ip stack broken?
I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? slave-mike wrote: FYI: here is the output from ifconfig, arp -an, ipv4 routing tables while running the 5.1-RELEASE kernel. dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGSc80dc0 10 link#4 UC 10 vmnet1 10.255.255.255 ff:ff:ff:ff:ff:ff UHLWb 2 58 vmnet1 127.0.0.1 127.0.0.1 UH 11 3250lo0 192.168.0.0ff:ff:ff:ff:ff:ff UHLWb 09dc0 = 192.168.0 link#1 UC 40dc0 192.168.0.100:a0:c5:e6:58:00 UHLW98dc0332 192.168.0.2127.0.0.1 UGHS05lo0 192.168.0.253 00:06:25:54:2a:20 UHLW01dc0 1057 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 4 147dc0 slave-mike wrote: Follows is my arp table entries and interface while running a -current kernel. My system can see the default gateway etc, and appears to be transmitting packets (based on activity of hub lights), but does not seem to be receiving them back or knowing they are received back beyond the arp/rarp packets or it just plain eats them. :) 192.168.0.1 is my default gw I have tried both fxp0 and dc0. I have tried both with and without vmnet being loaded. ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active mjoyner wrote: It works fine with a 5.1 kernel. Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -march athlon breaks my networking was: ip stack broken?
On Sun, Oct 19, 2003 at 03:39:59PM -0400, slave-mike wrote: I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? That's a syntax error - can you please confirm you meant -march=athlon? Kernels aren't usually built without optimization (-O0). Is there some reason you chose to do that? Kris pgp0.pgp Description: PGP signature
Re: -march athlon breaks my networking was: ip stack broken?
On Sun, 19 Oct 2003, slave-mike wrote: I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? Could you change only one variable at a time? Start off by using -march=athlon and -O to eliminate the -march argument. As Kris pointed out, kernels are usually not built with -O0. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -march athlon breaks my networking was: ip stack broken?
in /etc/make.conf #CPUTYPE= athlon #COPTFLAGS= -O0 is what is in my /etc/make.conf -march should be -mcpu. sorry!. :) as in cc -O -pipe -mcpu=pentiumpro ... Aparantly, when I have my CPUTYPE set to ATHLON, and the build is called with -mcpu=athlon, something is going screwy. I had optimization turned off for some reason or other... don't remember why now, it has been a long time since it's been in there, so it has now been commented out, as has CPUTYPE, when seems to result in a default CPUTYPE of pentiumpro Kris Kennaway wrote: On Sun, Oct 19, 2003 at 03:39:59PM -0400, slave-mike wrote: I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? That's a syntax error - can you please confirm you meant -march=athlon? Kernels aren't usually built without optimization (-O0). Is there some reason you chose to do that? Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
Follows is my arp table entries and interface while running a -current kernel. My system can see the default gateway etc, and appears to be transmitting packets (based on activity of hub lights), but does not seem to be receiving them back or knowing they are received back beyond the arp/rarp packets or it just plain eats them. :) 192.168.0.1 is my default gw I have tried both fxp0 and dc0. I have tried both with and without vmnet being loaded. ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active mjoyner wrote: It works fine with a 5.1 kernel. Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -march athlon breaks my networking was: ip stack broken?
Roger Wilco! Andre Guibert de Bruet wrote: On Sun, 19 Oct 2003, slave-mike wrote: I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? Could you change only one variable at a time? Start off by using -march=athlon and -O to eliminate the -march argument. As Kris pointed out, kernels are usually not built with -O0. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
It works fine with a 5.1 kernel. Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
FYI: here is the output from ifconfig, arp -an, ipv4 routing tables while running the 5.1-RELEASE kernel. dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGSc80dc0 10 link#4 UC 10 vmnet1 10.255.255.255 ff:ff:ff:ff:ff:ff UHLWb 2 58 vmnet1 127.0.0.1 127.0.0.1 UH 11 3250lo0 192.168.0.0ff:ff:ff:ff:ff:ff UHLWb 09dc0 = 192.168.0 link#1 UC 40dc0 192.168.0.100:a0:c5:e6:58:00 UHLW98dc0332 192.168.0.2127.0.0.1 UGHS05lo0 192.168.0.253 00:06:25:54:2a:20 UHLW01dc0 1057 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 4 147dc0 slave-mike wrote: Follows is my arp table entries and interface while running a -current kernel. My system can see the default gateway etc, and appears to be transmitting packets (based on activity of hub lights), but does not seem to be receiving them back or knowing they are received back beyond the arp/rarp packets or it just plain eats them. :) 192.168.0.1 is my default gw I have tried both fxp0 and dc0. I have tried both with and without vmnet being loaded. ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active mjoyner wrote: It works fine with a 5.1 kernel. Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX full-duplex) status: active ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ip stack broken?
When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? BOOT MESSAGES: Oct 17 18:37:07 duron kernel: Copyright (c) 1992-2003 The FreeBSD Project. Oct 17 18:37:07 duron kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 17 18:37:07 duron kernel: The Regents of the University of California. All rights reserved. Oct 17 18:37:07 duron kernel: FreeBSD 5.1-CURRENT #1: Fri Oct 17 15:31:54 EDT 2003 Oct 17 18:37:07 duron kernel: [EMAIL PROTECTED]:/usr/src/sys/i386/compile/athlon Oct 17 18:37:07 duron kernel: Preloaded elf kernel /boot/kernel/kernel at 0xc0a8a000. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/vesa.ko at 0xc0a8a1f4. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/snd_sb16.ko at 0xc0a8a2a0. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/snd_sbc.ko at 0xc0a8a350. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc0a8a3fc. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/bktr.ko at 0xc0a8a4a8. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/bktr_mem.ko at 0xc0a8a554. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/aio.ko at 0xc0a8a604. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/r128.ko at 0xc0a8a6ac. Oct 17 18:37:07 duron kernel: Preloaded elf module /boot/kernel/acpi.ko at 0xc0a8a758. Oct 17 18:37:07 duron kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Oct 17 18:37:07 duron kernel: CPU: AMD Athlon(tm) processor (1200.05-MHz 686-class CPU) Oct 17 18:37:07 duron kernel: Origin = AuthenticAMD Id = 0x642 Stepping = 2 Oct 17 18:37:07 duron kernel: Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR Oct 17 18:37:07 duron kernel: AMD Features=0xc044RSVD,AMIE,DSP,3DNow! Oct 17 18:37:07 duron kernel: real memory = 402587648 (383 MB) Oct 17 18:37:07 duron kernel: avail memory = 381362176 (363 MB) Oct 17 18:37:07 duron kernel: bktr_mem: memory holder loaded Oct 17 18:37:07 duron kernel: Pentium Pro MTRR support enabled Oct 17 18:37:07 duron kernel: VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc09c6a02 (122) Oct 17 18:37:07 duron kernel: VESA: ATI RAGE128 Oct 17 18:37:07 duron kernel: npx0: [FAST] Oct 17 18:37:07 duron kernel: npx0: math processor on motherboard Oct 17 18:37:07 duron kernel: npx0: INT 16 interface Oct 17 18:37:07 duron kernel: acpi0: VIA694 AWRDACPI on motherboard Oct 17 18:37:07 duron kernel: pcibios: BIOS version 2.10 Oct 17 18:37:07 duron kernel: Using $PIR table, 7 entries at 0xc00fdd50 Oct 17 18:37:07 duron kernel: acpi0: Power Button (fixed) Oct 17 18:37:07 duron kernel: Timecounter ACPI-fast frequency 3579545 Hz quality 1000 Oct 17 18:37:07 duron kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 Oct 17 18:37:07 duron kernel: acpi_cpu0: CPU on acpi0 Oct 17 18:37:07 duron kernel: acpi_button0: Power Button on acpi0 Oct 17 18:37:07 duron kernel: acpi_button1: Sleep Button on acpi0 Oct 17 18:37:07 duron kernel: pcib0: ACPI Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 Oct 17 18:37:07 duron kernel: pci0: ACPI PCI bus on pcib0 Oct 17 18:37:07 duron kernel: pcib0: slot 7 INTD is routed to irq 10 Oct 17 18:37:07 duron kernel: pcib0: slot 7 INTD is routed to irq 10 Oct 17 18:37:07 duron kernel: pcib0: slot 11 INTA is routed to irq 9 Oct 17 18:37:07 duron kernel: pcib0: slot 11 INTA is routed to irq 9 Oct 17 18:37:07 duron kernel: pcib0: slot 18 INTA is routed to irq 11 Oct 17 18:37:07 duron kernel: pcib0: slot 20 INTA is routed to irq 10 Oct 17 18:37:07 duron kernel: agp0: VIA 82C8363 (Apollo KT133A) host to PCI bridge mem 0xd000-0xd3ff at device 0.0 on pci0 Oct 17 18:37:07 duron kernel: pcib1: PCI-PCI bridge at device 1.0 on pci0 Oct 17 18:37:07 duron kernel: pci1: PCI bus on pcib1 Oct 17 18:37:07 duron kernel: pcib0: slot 1 INTA is routed to irq 12 Oct 17 18:37:07 duron kernel: pcib1: slot 0 INTA is routed to irq 12 Oct 17 18:37:07 duron kernel: drm0: ATI Rage 128 Pro Ultra TF (AGP) port 0x9000-0x90ff mem 0xd900-0xd9003fff,0xd400-0xd7ff irq 12 at device 0.0 on pci1 Oct 17 18:37:07 duron kernel: info: [drm] AGP at 0xd000 64MB Oct 17 18:37:07 duron kernel: info: [drm] Initialized r128 2.5.0 20030725 on minor 0 Oct 17 18:37:07 duron kernel: isab0: PCI-ISA bridge at device 7.0 on pci0 Oct 17 18:37:07 duron kernel: isa0: ISA bus on isab0 Oct 17 18:37:07 duron kernel: atapci0: VIA 82C686B UDMA100 controller port 0xa000-0xa00f at device 7.1 on pci0 Oct 17 18:37:07 duron kernel: atapci0: Correcting VIA config for southbridge data corruption bug Oct 17 18:37:07 duron kernel: ata0: at 0x1f0 irq 14 on atapci0 Oct 17 18:37:07 duron
