January 2004 - openSUSE AMD64 - openSUSE Mailing Lists

Re: [suse-amd64] suse 9 and GA-K8N Pro (Titan) motherboard (was amd 64, gftp+kdvi problems)
by Bob Fischer 24 Jan '04

24 Jan '04

> I installed suse 9.0, 64-bit version, on a > gigabyte k8 triton motherboard with 1.5G ram, David, I'm running almost exactly the same configuration: * SuSE 9.0 (installed via FTP) * Gigabyte GA-K8N Pro Motherboard (K8 Triton Series) with nForce3 150 chipset * 1 Gb RAM (Corsair) * AMD Athlon64 3200+ CPU * ATI Rage 128 Video * Western Digital 160Gb ATA-100 drive First of all, you have to be very careful with getting RAM that will work with this motherboard. See the article at Tom's Hardware: http://www6.tomshardware.com/motherboard/20040112/memory_performance-11.html I suppose this is not the greatest motherboard, but with my Corsair memory, it does work. I'll assume you've got your hardware together. In that case, my experience shows you will almost certainly not get a working system without majorly upgrading the kernel. Mine crashed constantly until I upgraded. It wasn't a problem of any one application or the other, but rather of the kernel and motherboard combo. Consider the following message on the nForce3 Chipset, as of Sept. 17, 2003: http://www.ussg.iu.edu/hypermail/linux/kernel/0309.2/0447.html > "Re: [PATCH] 2.4.23-pre4 support for new nForce IDE controllers" > This adds support for some new and upcoming NVIDIA nForce IDE > controllers to > the combined AMD / NVIDIA IDE driver. I've also added > support for udma6 > (Ultra 133) as a separate patch that depends on this patch SuSE 9.0 runs the 2.4.21 kernel, which (I assume) does not have the patch. It crashed like crazy on me. It would work for a while, then hang up while making a short "zapping" sound through the speakers, like a mosquito zapper (if I had sound turned on). If I accessed the hard drive a lot, it would crash more. This happened even when I turned off DMA, used the VESA Framebuffer driver for video, and turned off audio (i.e. didn't load the driver in the kernel). It even managed to crash a 32-bit installation on the same computer, although not quite as fast. I finally fixed this problem by installing the 2.6.1 kernel, downloaded from www.kernel.org. Of coruse, you first need a stable system from which to compile the kernel (mine crashed way too much to compile the kernel). The problem is that NONE of the SuSE 9.0 systems (32-bit or 64-bit) is stable enough on this hardware to compile a kernel. I installed Gentoo on a separate partition (took an evening, I learned a lot), and then used that to compile and install my SuSE kernel. Alternately, you could try using the pre-compiled binary I made for myself (see below), see if that gives you a stable system. To compile and install, I did the following (this assumes some familiarity with how to recompile and install a Linux kernel): 0. Build a basic Stage3 Gentoo system with 2.6 kernel. I mounted my SuSE system partition as /SuSE64. Basically, you need to run the 2.6 kernel SOMEHOW because otherwise your system will crash while compiling. 1. Download the experimental 2.6.0 kernel source from SuSE, as of last summer: ftp://mirror.mcs.anl.gov/pub/suse/x86_64/supplementary/Kernel-2.6-Test/kern… Look in the README file: it suggests you also download modutils, mkinitrd and aaa_base, which I did. 2. Untar the source of the 2.6.1 kernel into /usr/src, as per the 2.6.1 kernel documentation. 3. Copy the .config file from the test 2.6.0 kernel to the 2.6.1 kernel directory. 4. Run make menuconfig in the 2.6.1 kernel directory. 5. Make sure the drivers required to boot are installed permanently (not as modules) in the kernel. For me, this was the ext3 and ReiserFS filesystem drivers. There may be others; the kernel will complain upon bootup if you don't get them right, then you can fix it. ALTERNATIVE: You can set up an initrd RAMDisk. I'm not quite sure how to do this, but probably that mkinitrd RPM from the SuSE mirror will be helpful. Then you can leave ext3 and reiserfs and stuff as modules. 6. Compile and install the kernel: a) make (make dep is no longer required for 2.6 kernels) b) Check the Makefile to see where the kernel will be installed. Generally, this will be in boot. Change it to /SuSE64/boot. Make sure the "make install" will not overwrite your current SuSE kernel (you can change installation to /SuSE64/boot2 to see what it will do, then change back to /SuSE64/boot and install again). b) make install. It should install as /boot/linux-2.6.1 c) Edit /boot/grub/menu.lst for your new kernel. You can do this by copying the line for the current SuSE bootup, changing the filename of the kernel, and deleting the initrd line (assuming you're not using an initrd). Make sure you don't disturb your old bootup procedure, in case you need to boot back into the old kernel! 7. Well, this worked for me. Once I booted up, I no longer had ethernet, audio, etc. I'm not sure what I did wrong. But basically, I read the Gentoo documentation on how to set those things up and it worked. The upshot is that the kernel module auto-loading somehow no longer works on my SuSE system. I've fixed that by manually loading the modules I know I'll need at bootup time, then devices sort of work. I've done this in /etc/init.d/boot.local: -------------------------------- # Hack: get my ethernet working modprobe r8169 # Hack: for sound modprobe snd-intel8x0 # Hack: for parallel printer (see Gentoo docs for usb printer) modprobe lp modprobe parport modprobe parport_pc modprobe lp ----------------------------------- You should definitely use the first two modprobe lines, since those are for devices on the Triton motherboard. You should use the last set of modprobes only for a parallel port printer. There are tons of device drivers from the old kernel that are no longer loaded. I suppose it will be an individual process of figuring out what I need to load for CD burning, etc. Running lsmod in the old kernel helps, since that shows what it loaded. Also, there have been some changes since 2.4: 1. CD burning uses different modules than it used to. I haven't investigated yet. 2. I've heard that the /etc/modules.conf system has changed. Maybe that's why SuSE module auto-configuration stuff no longer works for me, since it's expecting a 2.4-type kernel. No matter, the system works for me now and it hasn't crashed even once since I switched to the 2.6 kernel. I'm running at DMA ATA-100 mode (the max for my hard drive), and am using the proper XFree86 driver for my graphics card (ATI Rage 128, but no 3-D for now). Sound and printing both work (after a bit of heartache). ---------------- Rather than compiling your own kernel, you might also try the kernel that comes with the new bootable CD with SATA drivers, announced by Andreas Jaeger January 22 on the suse-amd64 e-mail list (see attached/below). Since this is a 2.4 kernel, it will almost certainly not break the auto-configure stuff I noted above. However, it might also not solve the problems with your motherboard. I've experienced total stability since I switched to the stock 2.6.1 as described above. I can also make available the binaries for my 2.6.1 kernel, see if they work for you. That would simplify the installation process, and your current SuSE kernel would probably run for long enough to avoid crashing while you copy the binary. No warranty is expressed or implied. One final note: I advise against using ReiferFS at this point with 64-bit systems. Gentoo has noted a few problems with it (see the Gentoo web site). For now play it safe, use ext3 instead. Best of luck, -- Bob On Sat, 2004-01-24 at 21:29, David Joyner wrote: > Hello: > > I installed suse 9.0, 64-bit version, on a > gigabyte k8 triton motherboard with 1.5G ram, > AMD64 athlon 3000+ cpu. Installation went completely > smoothly, with suse automatically recognizing the onboard > sound and ethernet, gforce3 video, LG dvd-rom and LG cdrom. > > However, some odd things began to pop up: gftp > (which I love) crashes. I tried to reinslall from the rpms > on the CDs of the non-64 bit version of suse 9.0, > which I also have. (I thought maybe the dvd disc was corrupted.) > It failed too. xftp crashes. (The text-based ftp however works.) > Another program I use a lot, kdvi (kde's dvi previewer for latex documents), > also crashes:-(. I've recently been having problems wth kmail, > and had to switch over to mozilla. I'm not sure if that's related though. > > Do you have any suggestions? Ever heard of anything like this? > I called suse tech support. They were very nice but didn't know > anything. > > - David Joyner

1 0

Re: [suse-amd64] suse 9 amd 64, gftp+kdvi problems
by Michael Mondragon 24 Jan '04

24 Jan '04

> > That would mean that either: > > - one of our local patches is broken > > - your binary on the disk is broken (check with rpm -Va the md5sums) > > - you used a different compiler than we did - but we ship the same > > that we use... > > > > I'm really surprised that recompilation helped... > >... - or it was a placebo effect. Not uncommon in software testing. I guess you could argue that crashing consistently and then not crashing after recompilation has some placebo in it ;) More likely it was version differences; I obtained the source from the project pages directly and did not consider checking whether the latest version was the same as the SUSE rpms. In some cases I had to play with configure options like --disable-mmx and so forth. Not very scientific, and I didn't make any notes ... just stuck with the policy of disabling all platform-specific options. All part of a pointless effort anyways, since I had to go back to a 32-bit linux kernel/distro just so I could run VMWare for testing kmods... _m _________________________________________________________________ Rethink your business approach for the new year with the helpful tips here. http://special.msn.com/bcentral/prep04.armx

1 0

RE: [suse-amd64] Solving the Tyan 2885 AGP performance issues
by mark.langsdorf＠amd.com 24 Jan '04

24 Jan '04

> From: Andrew Halliwell [mailto:ah@gnd.com] > > And even though the patches are mentioned... > where can they be downloaded? (I've looked on the nvidia site > and couldn't find the newer drivers either) The patches in plaintext below. I didn't realize the SUSE list doesn't support attachments. -Mark Langsdorf Team Lead, Linux Device Drivers Advanced Micro Devices diff -u -u -r1.39 agpgart_be.c --- linux/drivers/char/agp/agpgart_be.c 2003/10/28 23:20:20 1.39 +++ linux/drivers/char/agp/agpgart_be.c 2003/10/28 23:26:02 @@ -67,6 +67,7 @@ EXPORT_SYMBOL(agp_backend_release); static void flush_cache(void); +static int agp_init_one(struct pci_dev *dev); static struct agp_bridge_data agp_bridge; static int agp_try_unsupported __initdata = 0; @@ -6490,15 +6491,24 @@ static int __init agp_find_supported_device(void) { struct pci_dev *dev = NULL; - u8 cap_ptr = 0x00; + int ret = -ENODEV; #ifdef CONFIG_AGP_HP_ZX1 if (hp_zx1_gart_init() == 0) return 0; #endif - if ((dev = pci_find_class(PCI_CLASS_BRIDGE_HOST << 8, NULL)) == NULL) - return -ENODEV; + while ((dev = pci_find_class(PCI_CLASS_BRIDGE_HOST << 8, dev)) != NULL) { + ret = agp_init_one(dev); + if (ret != -ENODEV) + break; + } + return ret; +} + +static int __init agp_init_one(struct pci_dev *dev) +{ + u8 cap_ptr = 0x00; agp_bridge.dev = dev; diff -u linux-work/arch/x86_64/kernel/mtrr.c-o linux-work/arch/x86_64/kernel/mtrr.c --- linux-work/arch/x86_64/kernel/mtrr.c-o 2002-09-05 17:27:05.000000000 +0200 +++ linux-work/arch/x86_64/kernel/mtrr.c 2004-01-16 18:27:04.000000000 +0100 @@ -70,6 +70,9 @@ #define MTRR_VERSION "2.02 (20020716)" +#define MTRR_BEG_BIT 12 +#define MTRR_END_BIT 7 + #undef Dprintk #define Dprintk(...) @@ -192,8 +195,9 @@ static void get_mtrr (unsigned int reg, u64 *base, u32 *size, mtrr_type * type) { - u32 mask_lo, mask_hi, base_lo, base_hi; - u64 newsize; + u32 count, tmp, mask_lo, mask_hi; + int i; + u32 base_lo, base_hi; rdmsr (MSR_MTRRphysMask(reg), mask_lo, mask_hi); if ((mask_lo & 0x800) == 0) { @@ -206,10 +210,16 @@ rdmsr (MSR_MTRRphysBase(reg), base_lo, base_hi); - /* Work out the shifted address mask. */ - newsize = (u64) mask_hi << 32 | (mask_lo & ~0x800); - newsize = ~newsize+1; - *size = (u32) newsize >> PAGE_SHIFT; + count = 0; + tmp = mask_lo >> MTRR_BEG_BIT; + for (i = MTRR_BEG_BIT; i <= 31; i++, tmp = tmp >> 1) + count = (count << (~tmp & 1)) | (~tmp & 1); + + tmp = mask_hi; + for (i = 0; i <= MTRR_END_BIT; i++, tmp = tmp >> 1) + count = (count << (~tmp & 1)) | (~tmp & 1); + + *size = (count+1); *base = base_hi << (32 - PAGE_SHIFT) | base_lo >> PAGE_SHIFT; *type = base_lo & 0xff; } @@ -243,7 +253,7 @@ base64 = (base << PAGE_SHIFT) & size_and_mask; wrmsr (MSR_MTRRphysBase(reg), base64 | type, base64 >> 32); - size64 = ~((size << PAGE_SHIFT) - 1); + size64 = ~(((u64)size << PAGE_SHIFT) - 1); size64 = size64 & size_and_mask; wrmsr (MSR_MTRRphysMask(reg), (u32) (size64 | 0x800), (u32) (size64 >> 32)); }

3 3

suse 9 amd 64, gftp+kdvi problems
by David Joyner 24 Jan '04

24 Jan '04

Hello: I installed suse 9.0, 64-bit version, on a gigabyte k8 triton motherboard with 1.5G ram, AMD64 athlon 3000+ cpu. Installation went completely smoothly, with suse automatically recognizing the onboard sound and ethernet, gforce3 video, LG dvd-rom and LG cdrom. However, some odd things began to pop up: gftp (which I love) crashes. I tried to reinslall from the rpms on the CDs of the non-64 bit version of suse 9.0, which I also have. (I thought maybe the dvd disc was corrupted.) It failed too. xftp crashes. (The text-based ftp however works.) Another program I use a lot, kdvi (kde's dvi previewer for latex documents), also crashes:-(. I've recently been having problems wth kmail, and had to switch over to mozilla. I'm not sure if that's related though. Do you have any suggestions? Ever heard of anything like this? I called suse tech support. They were very nice but didn't know anything. - David Joyner

1 0

Are my SATA disks running correctly?
by Johan Backlund 24 Jan '04

24 Jan '04

Hi all, I have a new server based on the MSI K8T Master2 mobo with dual Opterons. I have three disks: one PATA (added that for installation purposes) and two SATA drives. It is running quite alright, but I have some questionmarks around my disks. I thought I knew a lot about Linux but this really puzzles me. I am running SuSE kernels (downloaded from kraxel) and I have just now upgraded to 2.6.1-5. Now the questions: My PATA disk becomes hde and the SATA disks become hda and hdc (if SATA is enabled, otherwise PATA disk is hda). Is this normal? Other people seem to see their PATA disks on hda-hdd and SATA on hde-hdh. Here are some excerpts from dmesg: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0 VIA8237SATA: chipset revision 128 VIA8237SATA: 100% native mode on irq 20 ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio hda: WDC WD1200JD-00FYB0, ATA DISK drive Using anticipatory io scheduler ide0 at 0xc000-0xc007,0xc402 on irq 20 hdc: WDC WD1200JD-00FYB0, ATA DISK drive ide1 at 0xc800-0xc807,0xcc02 on irq 20 VP_IDE: IDE controller at PCI slot 0000:00:0f.1 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1 ide2: BM-DMA at 0xd800-0xd807, BIOS settings: hde:DMA, hdf:DMA ide3: BM-DMA at 0xd808-0xd80f, BIOS settings: hdg:pio, hdh:pio hde: ExcelStor Technology J680, ATA DISK drive hdf: _NEC DVD_RW ND-1300A, ATAPI CD/DVD-ROM drive ide2 at 0x1f0-0x1f7,0x3f6 on irq 14 What is the deal with the double drive devices (hda/hdb for first SATA, hdc/hdd for second, hde/hdf for PATA and hdg/hdh for DVD)? Is that normal? I don't seem to get the libata stuff loaded - otherwise I guess I would have the disks on sda and sdb, right? Can I somehow choose to use this driver instead? Do I want to run this driver instead? I have seen people talking about setting the noprobe option on the hd devices and thereby getting the libata driver going - I have not been able to do this. What about performance? What should be expected from SATA disks? I had really lousy performance on 2.6.1-2 compared to the PATA disk, but the 2.6.1-5 made the situation better although SATA disks are still slower than the PATA disk - at least according to hdparm: /dev/hda: Timing buffered disk reads: 150 MB in 3.00 seconds = 49.99 MB/sec /dev/hdc: Timing buffered disk reads: 150 MB in 3.01 seconds = 49.89 MB/sec /dev/hde: Timing buffered disk reads: 174 MB in 3.02 seconds = 57.57 MB/sec On 2.6.1-2 I head about 30-32 MB/sec on the drives. Finally, I thought I had got rid of the problem by upgrading, but I just noticed that it is still there. At least one of the SATA drives (hda) is sometimes reporting this: hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt which basically causes the drive to "hang" for 10 seconds or so, causing 100% IO-wait and then resumes activity. No corruption seen (yet). I see people on the internet talking about disabling dma, but that doesn't seem like a very good idea? As you can see there are a lot of questions...basically I feel that the SATA disks are not delivering what I had expected and I would really like to get any hints on what could be the problem. Linux? VIA VT8237? The disks? BIOS settings? Because the reasons I built this server was to run some intense database stuff and if PATA disks are better than SATA, then I'll just throw these suckers out and be done with it - but I really thought they were supposed to give me a little more? thanks for listening. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/

1 0

RE: [suse-amd64] Solving the Tyan 2885 AGP performance issues
by mark.langsdorf＠amd.com 24 Jan '04

24 Jan '04

> From: Steven A. DuChene [mailto:linux-clusters@mindspring.com] > > Great, but what about the same fixes for the 2.6 kernels? A better fix for the AGP issue already exists in the 2.6 kernel. Andi Kleen and I are looking into the MTRR issue, but we need a test case that doesn't depend on the nVidia driver, since that driver doesn't support 2.6. We should have an answer by the end of the month. -Mark Langsdorf Team Lead, Linux Device Drivers Advanced Micro Devices

2 1

kernel panic loading dpt_i2o
by Paul Sturm 23 Jan '04

23 Jan '04

I am trying to install 9.0 for AMD64 on a Tyan S2882 motherboard with Adaptec 2015S ZRC RAID. I have successfully installed the i386 version on this machine using the dpt_i2o driver. When I try to load the same driver when booting from the AMD64 CD, I get a kernel panic with the following message: Unable to handle kernel paging request at virtual address 00000000 5e9f08. The system has 4GB of RAM installed. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.547 / Virus Database: 340 - Release Date: 12/2/2003

2 1

Re: [suse-amd64] Solving the Tyan 2885 AGP performance issues
by Andrew Halliwell 22 Jan '04

22 Jan '04

And verily, didst Kevin_Gassiot(a)veritasdgc.com announce to the hordes: > > > > > > The stock 102 kernel, 4499 driver, and stock BIOS will not work. You need > to update the BIOS, update the kernel, and update the Nvidia driver.... The nvidia driver on the site was still on 4499 when I read the original message, must've been hitting a webcache somewhere. It's there now. > I am running the S2885101k BIOS from Tyan, the 171-smp kernel from SuSE > with the mtrr.c replaced by the one supplied by AMD, and the 5331 driver > from Nvidia. You need all of these various bits to get the board to work > correctly. I have been working with these guys for some months now, trying > to get things to work, and as of Monday, I have a truly functioning system > :) You've not got the RAID on the silicon image on-board SATA working though, I'll wager... :) Just a pain that the kernel won't patch with those from that message. Obviously too old now to accept them. Just have to try to cheat the driver into working, by compiling a later 2.4.21- kernel and putting the build number in the makefile back to 102.

1 1

Solving the Tyan 2885 AGP performance issues
by mark.langsdorf＠amd.com 22 Jan '04

22 Jan '04

The 2P Opteron based Tyan 2885 K8W has some problems with AGP/openGL graphics performance when using nVidia graphics cards under Linux. AMD, Tyan, and nVidia have been working together to develop fixes for the problems. Four problems have been resolved for the Tyan 2885 design. The first issue was the inabilty of the Linux kernel to find the AMD-8151 AGP Tunnel. The AMD-8151 AGP controller is not at the normal PCI address, and the Linux kernel had to be modified to account for the change. SUSE Linux kernels starting with k_smp-2.4.21-139 include the change. The two attached patches (tyan_agp.generic.patch and tyan_agp.RHEL3.patch) fix the problem for most kernels and for the Red Hat 2.4.21-4EL kernels, respectively. The second issue was a misallocation of MTRRs in the Tyan BIOS that prevented the nVidia driver from correctly caching the AGP aperture. Tyan fixed this with the 2885101i.ROM (1.01i) BIOS, available at ftp://ftp.tyan.com/bios_beta/2885101i.zip. The third issue involved the nVidia 10-4499 graphics driver. nVidia has corrected the problems exposed by the updated AGP and BIOS code and released the 10-5332 driver to their website on January 20th. The final issue involved the Linux kernel MTRR code. A patch that fixes the problem is attached to this message (mtrr.patch). It has not been included in any production kernels at this time. These four updates, taken together, allow the 2885 to provide excellent 3D performance under Linux. AMD would like to thank all those who contributed to defining, debugging, and verifying this problem. Mark Langsdorf Team Lead, Linux Device Drivers Advanced Micro Devices mark.langsdorf(a)amd.com

5 8

Fujitsu Siemens Celsius V810
by Peter Rundberg 22 Jan '04

22 Jan '04

Hi. I just got a Fujitsu Siemens Celsius V810 dual Opteron Workstation. It comes equipped with an Nvidia QuadroFX card but I am having trouble getting the machine to run properly under Linux. The problem is that the 8151 AGP tunnel can not be found and thus the graphics card can not be found. I have tried the Suse kernel (up to and including -178) as well as 2.6.1-X8664-2. Could this be a similar problem to the one that affected the Tyan Thunder K8W (S2885) a while back when the kernel could not find the 8151 AGP tunnel because of some PCI search issue. The board looks very similar to the Tyan 2885 both feature wise and by visual inspection but apparently it is not the same as on my 2885 everything is works as expected and the 8151 is identified correctly. Output from lspci is as follows and as you can see there is no 8151 in sight. 00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) 00:07.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00:0b.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 01:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 01:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 01:0b.0 Unknown mass storage controller: CMD Technology Inc: Unknown device 3114 (rev 02) 01:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703 Gigabit Ethernet (rev 02) On my Tyan 2885 lspci find the 8151 as can be seen below. 00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) 00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) 00:07.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00:0b.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703 Gigabit Ethernet (rev 02) 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 03:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 03:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 04:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-8151 System Controller (rev 13) 04:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8151 AGP Bridge (rev 13) 05:00.0 VGA compatible controller: nVidia Corporation NV31 [GeForce FX 5600] (rev a1) Any ideas? /peter

4 5