Date: Tue, 26 Apr 2005 10:53:58 +0900 From: Joel <rees@ddcom.co.jp> To: freebsd-questions@freebsd.org Subject: Re: UPDATING on AMD Processor Message-ID: <20050426103359.861B.REES@ddcom.co.jp> In-Reply-To: <20050425173134.GA62603@ns2.wananchi.com> References: <20050425173134.GA62603@ns2.wananchi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> [...] > When it comes to the Intel platform, I can always find my way around, > but in this one case of AMD, I am purely clueless. I don't even know > what keyword to search for in the handbook, FAQ, google. > > Attached you will find the dmesg output of an oldish box on which I > just installed FreeBSD 5.x, and I would like to: Some people like dmesgs as attachments. I guess I'm kind of odd. I'd rather have the dmesg text just pasted in, like this: > Copyright (c) 1992-2004 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 5.3-RC2 #0: Sun Oct 31 08:32:33 UTC 2004 > root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD-K6(tm) 3D processor (451.03-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX> > AMD Features=0x80000800<SYSCALL,3DNow!> > real memory = 134217728 (128 MB) > avail memory = 121696256 (116 MB) > K6-family MTRR support enabled (2 registers) > npx0: [FAST] > npx0: <math processor> on motherboard > npx0: INT 16 interface > pcib0: <Host to PCI bridge> pcibus 0 on motherboard > pir0: <PCI Interrupt Routing Table: 8 Entries> on motherboard > pci0: <PCI bus> on pcib0 > $PIR: No matching entry for 0.7.INTD > agp0: <VIA 82C597 (Apollo VP3) host to PCI bridge> mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 > pcib1: <PCI-PCI bridge> at device 1.0 on pci0 > pci1: <PCI bus> on pcib1 > $PIR: ROUTE_INTERRUPT failed. Any idea what happened there? Have you checked the jumpers and BIOS settings? > pci1: <display, VGA> at device 0.0 (no driver attached) What about this? have you been able to identify the video controller? > isab0: <PCI-ISA bridge> at device 7.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <VIA 82C586B UDMA33 controller> port 0xe800-0xe80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > uhci0: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 10 at device 7.2 on pci0 > uhci0: [GIANT-LOCKED] > usb0: <VIA 83C572 USB controller> on uhci0 > usb0: USB revision 1.0 > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > rl0: <RealTek 8139 10/100BaseTX> port 0xe400-0xe4ff mem 0xe6100000-0xe61000ff irq 9 at device 12.0 on pci0 > miibus0: <MII bus> on rl0 > rlphy0: <RealTek internal media interface> on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:e0:4c:45:0c:c4 > pcib2: <PCI-PCI bridge> at device 19.0 on pci0 > pci2: <PCI bus> on pcib2 > $PIR: ROUTE_INTERRUPT failed. > $PIR: ROUTE_INTERRUPT failed. > $PIR: ROUTE_INTERRUPT failed. Again, any idea why this is happening? > vr0: <VIA VT6105M Rhine III 10/100BaseTX> port 0xd000-0xd0ff mem 0xe6000000-0xe60000ff irq 12 at device 8.0 on pci2 > miibus1: <MII bus> on vr0 > ukphy0: <Generic IEEE 802.3u media interface> on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vr0: Ethernet address: 00:0c:42:02:16:27 > vr1: <VIA VT6105M Rhine III 10/100BaseTX> port 0xd400-0xd4ff mem 0xe6001000-0xe60010ff irq 5 at device 9.0 on pci2 > miibus2: <MII bus> on vr1 > ukphy1: <Generic IEEE 802.3u media interface> on miibus2 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vr1: Ethernet address: 00:0c:42:02:16:28 > vr2: <VIA VT6105M Rhine III 10/100BaseTX> port 0xd800-0xd8ff mem 0xe6002000-0xe60020ff irq 11 at device 10.0 on pci2 > miibus3: <MII bus> on vr2 > ukphy2: <Generic IEEE 802.3u media interface> on miibus3 > ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vr2: Ethernet address: 00:0c:42:02:16:29 > vr3: <VIA VT6105M Rhine III 10/100BaseTX> port 0xdc00-0xdcff mem 0xe6003000-0xe60030ff irq 9 at device 11.0 on pci2 > miibus4: <MII bus> on vr3 > ukphy3: <Generic IEEE 802.3u media interface> on miibus4 > ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vr3: Ethernet address: 00:0c:42:02:16:2a > cpu0 on motherboard > orm0: <ISA Option ROM> at iomem 0xc0000-0xcbfff on isa0 > pmtimer0 on isa0 > atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: <Parallel port bus> on ppc0 > plip0: <PLIP network interface> on ppbus0 > lpt0: <Printer> on ppbus0 > lpt0: Interrupt-driven port > ppi0: <Parallel I/O> on ppbus0 > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > unknown: <PNP0303> can't assign resources (port) > unknown: <PNP0501> can't assign resources (port) > unknown: <PNP0700> can't assign resources (port) > unknown: <PNP0400> can't assign resources (port) > unknown: <PNP0501> can't assign resources (port) And there's more complaints from the video controller. > Timecounter "TSC" frequency 451025199 Hz quality 800 > Timecounters tick every 10.000 msec > ad0: 9641MB <QUANTUM FIREBALLlct10 10/A03.0900> [19590/16/63] at ata0-master UDMA33 > Mounting root from ufs:/dev/ad0s1a That's what my untrained eye digs out. But I wouldn't have seen that much except that for some reason I bothered to drag your dmesg out and open it up with a text editor. > make buildworld > make kernel > make installworld As has been said, this is generic. If this is not working, I can only think of two possibilities -- either the hardware has problems (RAM, disk, controller, conductive dust on the interrupt lines, misplaced jumpers, BIOS settings, something like that) or you're slipping configuration steps in there you aren't mentioning. That's why people want error messages. I know diggin up an RS-232 cable and terminal emulator can be a pain. Copying by hand is even more of a pain. But without information, metaphysical methods must be resorted to. Metaphysical methods don't have what we can call predictable results in the physical world. > [...] -- Joel Rees <rees@ddcom.co.jp> digitcom, inc. $B3t<02q<R%G%8%3%`(B Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp>; **
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050426103359.861B.REES>