January 2007 - openSUSE AMD64 - openSUSE Mailing Lists

IOMMU...PCI memory hole...MTRR...I give up.
by David W. Hankins 26 May '07

26 May '07

I have an MSI K8D-Master-F motherboard with two Opteron 244's. It recently got retasked as a desktop machine due to another system's failure...I thought the little ATI Rage built into the motherboard would make more than a sufficient 2d desktop type framebuffer, and as far as other stuff inside this box... this should be a pretty kick ass, high performance workstation. But I can literally watch the screen redraw if I switch virtual desktops. Painfully slow. Thinking this was just some crippled built-in video bug, I threw in an old nVidia card we had lying around in one of the regular PCI slots. Slightly slower, if you can believe it. I think this: mtrr: type mismatch for e5000000,1000000 old: uncachable new: write-combining And of course this: $ cat /proc/mtrr reg00: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1 reg01: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1 Has something to do with it (and may also explain why I'm getting less than stellar performance out of other PCI devices, such as the RAID array that has a 128MB memory region the driver directly reads and writes on). The above is with the nVidia PCI card inserted, the built-in ATI card would also emit a similar mtrr rejection message, just the address is different, and the system would only list 512MB uncachable without the nVidia. Also notice that there's 4GB installed in this machine, in 2 2GB DIMMs installed in one bank together. And yet the BIOS map: BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable) BIOS-e820: 00000000bfff0000 - 00000000bffff000 (ACPI data) BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS) BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved) Lists nothing beyond the 4GB mark where that memory might reasonably have been moved to. Assuming this is just a neglectful BIOS, I tried setting 'mem=4G' and 'memmap=1G@4G' kernel options, to define the 1GB 'hole' I presume is being placed here, and which got me this added line to dmesg: user: 0000000100000000 - 0000000140000000 (usable) But still only 3GB available. To add even more insult to rising injury, I noticed while looking through dmesg that the IOMMU is being disabled. It appears the value being advertised by the CPU's: CPU 0: aperture @ 1b80000000 size 128 MB Is being rejected because it lies (WELL) above the 4GB mark. I've been going through archives and I'm not finding anything that looks like actionable advice. The latest BIOS MSI's webpage lists for this motherboard is 1.1: already installed. It has no option for 'pci hole: software'. The only options I'm finding are memory bank interleaving (which I tried disabling), and 'Disabled/Best-Fit/Absolute' settings for the IOMMU, as well as its aperture size (128M, which I might increase if it would be used rather than ignored...). One post in the archive that matched on motherboard make and model looks confused to me, because he refers to his BIOS as AWARD 2.0, but the only BIOS MSI puts out for this board is AMI (versioned 1.1). In summary what I'd like to know is: 1) Where is the 'go fast' button? re: pci video that's slower than even isa video should be (and presumably similar performance problems on other PCI devices). 2) How do I get the last 25% of my memory back? 3) How do I get the system to put the IOMMU somewhere in the range it stole under 4G (so Linux can use it)? Can Linux move this on its own accord? Thanks in advance for any and all help. -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins

5 13

Re: [opensuse-amd64] How to get a wifi connection running between two Pc Linux ?
by patheve 31 Jan '07

31 Jan '07

Hello thanks a lot for these informations. They remember me this is like for a cluster with two ethernet networks. I will try as soon as possible. I will tell you if it is better :-) Kind regards Pascal ================================================================================== El dc 31 de 01 del 2007 a les 20:56 +0100, en/na patheve va escriure: > Hello all > > I would like to link my two laptops with a wifi network : > PC n°1 : SuSE 9.2 Pro 64 bits, a wifi PC card built with chipset rt2500 > (module rt2500 up to date) > PC n°2 : SuSE 9.3 Pro 32 bits, a wifi PC card built with chipset rt61 (module > rt61 up to date) > > On each PC, there are eth0 (ethernet) and ra0 (wifi) interfaces. The IP > addresses are : > PC n°1 : eth0 with 192.168.1.101 (mask 255.255.255.0), ra0 with 192.168.1.201 > (mask 255.255.255.0), > no gateway, mode Ad-Hoc and no WEP key for wifi. > PC n°2 : eth0 with 192.168.1.102 (mask 255.255.255.0), ra0 with 192.168.1.202 > (mask 255.255.255.0), > no gateway, mode Ad-Hoc and no WEP key for wifi. Hello, You should use different network addresses for your wifi link. You have two different interfaces connected to the same network 192.168.1.x, your operating system doesn't know where to send packets to. Try: PC1 - eth0 - 192.168.1.2/24 --> modem ( 192.168.1.1 ) -> Internet - ra0 - 10.0.0.1/24 routes on PC1: network 192.168.1.0/24 dev eth0 network 192.168.2.0/24 via 10.0.0.2 network 0/0 via 192.168.1.1 PC2 - ra0 - 10.0.0.2/24 - eth0 - 192.168.2.1/24 routes on PC2 network 192.168.2.0/24 dev eth0 network 0/0 via 10.0.0.1 First of all, configure both ra0 interfaces and get ping working from both computers to 10.0.0.x interfaces. Later configure connection to the internet from PC1, and finally: Configure PC1 to masquerade 192.168.2.x traffic. hope this helps, > On PC n°1, there is an ADSL modem, plugged on eth0 and whose IP address is > 192.168.1.1. About firewall, ra0 is put in internal area without protection > on each PC. > > Normally by doing a ping -I ra0 192.168.1.202 from PC n°1, I should get an > answer ... like by an ethernet cable link. But NO !!! I get this : > ping -I ra0 192.168.1.202 > PING 192.168.1.202 (192.168.1.202) from 192.168.1.101 ra0: 56(84) bytes of > data. > From 192.168.1.201: icmp_seq=2 Destination Host Unreachable > From 192.168.1.201 icmp_seq=2 Destination Host Unreachable > From 192.168.1.201 icmp_seq=3 Destination Host Unreachable > From 192.168.1.201 icmp_seq=4 Destination Host Unreachable > From 192.168.1.201 icmp_seq=6 Destination Host Unreachable > > That's curious. No better effect with a gateway 192.168.1.201 put on PC n°1. > Am I forgetting something in network configuration ? If I put a name in ESSID > for PC n°1 for example, from the other PC I can see the name. So it seems > that wifi on each PC is OK but something is missing or is not properly > working. Any idea ?? A problem of firewall ? I put ra0 of each PC in internal > area, so it should not be a problem at this level. But .... > > Thanks > > Pascal > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-amd64+unsubscribe@xxxxxxxxxxxx > For additional commands, e-mail: opensuse-amd64+help@xxxxxxxxxxxx > -- --- Jordi Bruguera i Cortada <jordi@xxxxxx> Consultor en Programari Lliure LPIC1-ID: 000001116 Linux User #21587 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] How to get a wifi connection running between two Pc Linux ?
by patheve 31 Jan '07

31 Jan '07

Hello all I would like to link my two laptops with a wifi network : PC n°1 : SuSE 9.2 Pro 64 bits, a wifi PC card built with chipset rt2500 (module rt2500 up to date) PC n°2 : SuSE 9.3 Pro 32 bits, a wifi PC card built with chipset rt61 (module rt61 up to date) On each PC, there are eth0 (ethernet) and ra0 (wifi) interfaces. The IP addresses are : PC n°1 : eth0 with 192.168.1.101 (mask 255.255.255.0), ra0 with 192.168.1.201 (mask 255.255.255.0), no gateway, mode Ad-Hoc and no WEP key for wifi. PC n°2 : eth0 with 192.168.1.102 (mask 255.255.255.0), ra0 with 192.168.1.202 (mask 255.255.255.0), no gateway, mode Ad-Hoc and no WEP key for wifi. On PC n°1, there is an ADSL modem, plugged on eth0 and whose IP address is 192.168.1.1. About firewall, ra0 is put in internal area without protection on each PC. Normally by doing a ping -I ra0 192.168.1.202 from PC n°1, I should get an answer ... like by an ethernet cable link. But NO !!! I get this : ping -I ra0 192.168.1.202 PING 192.168.1.202 (192.168.1.202) from 192.168.1.101 ra0: 56(84) bytes of data. From 192.168.1.201: icmp_seq=2 Destination Host Unreachable From 192.168.1.201 icmp_seq=2 Destination Host Unreachable From 192.168.1.201 icmp_seq=3 Destination Host Unreachable From 192.168.1.201 icmp_seq=4 Destination Host Unreachable From 192.168.1.201 icmp_seq=6 Destination Host Unreachable That's curious. No better effect with a gateway 192.168.1.201 put on PC n°1. Am I forgetting something in network configuration ? If I put a name in ESSID for PC n°1 for example, from the other PC I can see the name. So it seems that wifi on each PC is OK but something is missing or is not properly working. Any idea ?? A problem of firewall ? I put ra0 of each PC in internal area, so it should not be a problem at this level. But .... Thanks Pascal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] YOU problem
by Philippe Andersson 31 Jan '07

31 Jan '07

Hi list, Maybe not the best place for this question, but I'm sure some of you must have the answer: Fresh install of OpenSuSE 10.2 (minimal install -- no X). Network properly configured. Start "yast" in ncurses mode, select "Online Update". It loads the list of installed packages and then reports that no patches are available. Based on a quick look on the site (ftp.suse.com), it looks like some patches are available (which is expected, a few months after the release). Is there some change in Yast that I missed (since the 9.3 version) ? YOU used to ask you which server it should connect to to retrieve the patches, but it doesn't seem to do that any longer. Any help or pointer to the relevant doc is appreciated. Thanks in advance. Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan(a)iba-group.com <http://www.iba-worldwide.com> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] Trouble installing openSuSE 10.2 due to pci_init
by brian_linux 23 Jan '07

23 Jan '07

Hello: I am having difficulty upgrading my openSuSE 10.1 installation to openSuSE 10.2. In fact, my difficult arises from the fact that I cannot reliably boot into the installation program. Background: (1) I have a Tyan K8HM 3892S motherboard and two dual-core Opterons. (2) I installed the latest BIOS (1.05). I tried a number of BIOS settings but they are currently set to "optimal defaults". (3) openSuSE 10.1 runs without any known problems. Originally I had the double realtime clock issue but a previous BIOS update fixed that. (4) I'm using the openSuSE 10.2 install DVD. I checked the MD5 and it matched. I have also burned a number of DVDs, even using different programs and the behavior is consistent. Issue: (1) The DVD starts to boot. In fact I can get to the "main screen" where I can select to "Boot from the Hard Drive", "Install", ... (2) When I select install to start the upgrade, usually the system hangs. (3) I installed using text mode and the initcall_debug kernel option and I can see progress up until the following: Calling initcall 0xffffffff80317987: pci_init +0x0/0x2b() What I find weird is that sometimes the system will get into the install program, but the vast majority of the time it will not. So it's intermittent. I haven't been able to identify any pattern that I can use to predict whether it'll work on any given boot sequence. Does anyone have any suggestions? This isn't a crisis since I have 10.1 working well, it's just that I really wanted to upgrade to 10.2. Of course I'm willing to provide additional information to the best of my ability. I'm somewhat competent, but must admit that I'm a little out of my comfort zone. Any help or suggestions would be greatly appreciated. Thank you. Brian Schang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64]
by r.ramos＠freenet.de 13 Jan '07

13 Jan '07

Hi all, I have upgraded to 10.2. I have the following problem with an avm fritzcard dsl sl usb device. With 10.1 I didn't have any problems. <4>NMI Watchdog detected LOCKUP on CPU 0 <4>CPU 0 <4>Modules linked in: fcdslslusb capi capifs kernelcapi usbhid nvidia ohci1394 snd_intel8x0 snd_ac97_codec snd_ac97_bus ieee1394 ide_cd cdrom snd_pcm snd_timer forcedeth snd soundcore snd_page_alloc ohci_hcd ehci_hcd i2c_nforce2 i2c_core usbcore parport_pc lp parport reiserfs edd fan sg sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core <4>Pid: 1842, comm: capiinit Tainted: P U 2.6.18.2-34-default #1 <4>RIP: 0010:[.text.lock.spinlock+34/138] [.text.lock.spinlock+34/138] .text.lock.spinlock+0x22/0x8a <4>RSP: 0018:ffff81007b8c9c70 EFLAGS: 00000086 <4>RAX: 0000000000000282 RBX: 0000000000000800 RCX: ffffffff8887b840 <4>RDX: ffff81007b8c9cb0 RSI: ffff81007b8c9cb8 RDI: ffff81007a55724c <4>RBP: ffff81007a557244 R08: ffff81007bad5004 R09: 0000000000000000 <4>R10: 0000000000000003 R11: ffff81007ff14980 R12: ffff81007a55724c <4>R13: ffff81007b8c9cb8 R14: ffff81007b8c9cb0 R15: 0000000000000000 <4>FS: 00002b24a519d6f0(0000) GS:ffffffff805b7000(0000) knlGS:0000000000000000 <4>CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>CR2: 00002b24a4cbb000 CR3: 000000007b6df000 CR4: 00000000000006e0 <4>Process capiinit (pid: 1842, threadinfo ffff81007b8c8000, task ffff81007d7f5080) <4>Stack: ffffffff8889f0b2 0000000000000800 ffffffff8887b840 ffff81007bad5004 <4> ffff81007bad5024 0000000000000800 ffffffff8889b3cb 0000000000000003 <4> 0000000000000003 0000000000000000 0000000000000246 0000000000000800 <4>Call Trace: <4> [_end+136900786/2130640896] :fcdslslusb:claim_urb+0x1d/0x8f <4> [_end+136755264/2130640896] :fcdslslusb:Block_RxHandler+0x0/0x4d0 <4> [_end+136885195/2130640896] :fcdslslusb:os_usb_submit_rx+0x32/0xe9 <4> [_end+136893893/2130640896] :fcdslslusb:OSHWRxBuffer+0x44/0x4f <4> [_end+136527809/2130640896] :fcdslslusb:BLK_Start+0x91/0xe0 <4> [_end+136531091/2130640896] :fcdslslusb:E1_Activate+0x13/0x20 <4> [_end+136454454/2130640896] :fcdslslusb:CM_Activate+0x6/0x50 <4> [_end+136889408/2130640896] :fcdslslusb:start+0x1b4/0x21f <4> [_end+136889849/2130640896] :fcdslslusb:load_ware+0x14e/0x1ab <4> [_end+136295344/2130640896] :kernelcapi:capi20_manufacturer+0x2d5/0x57c <4> [do_gettimeofday+80/148] do_gettimeofday+0x50/0x94 <4> [getnstimeofday+16/40] getnstimeofday+0x10/0x28 <4> [rb_insert_color+97/218] rb_insert_color+0x61/0xda <4> [enqueue_hrtimer+85/112] enqueue_hrtimer+0x55/0x70 <4> [_end+136407267/2130640896] :capi:capi_ioctl+0x2c1/0x441 <4> [do_ioctl+85/107] do_ioctl+0x55/0x6b <4> [vfs_ioctl+584/609] vfs_ioctl+0x248/0x261 <4> [sys_ioctl+89/120] sys_ioctl+0x59/0x78 <4> [system_call+126/131] system_call+0x7e/0x83 <4> <4> <4>Code: 83 3f 00 7e f9 e9 d4 fe ff ff f3 90 83 3f 00 7e f9 e9 d3 fe <4>console shuts up ... And here is the beginnning of the log: Inspecting /boot/System.map-2.6.18.2-34-default Loaded 23895 symbols from /boot/System.map-2.6.18.2-34-default. Symbols match kernel version 2.6.18. No module symbols loaded - kernel modules not enabled. klogd 1.4.1, log source = ksyslog started. <4>Bootdata ok (command line is root=/dev/sda6 vga=0x317 resume=/dev/sda5 splash=silent) <5>Linux version 2.6.18.2-34-default (geeko@buildhost) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006 I have attached the complete log. Thank you Ramon Ramos "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" http://www.klarmobil.de/index.html?pid=73025 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] opensuse 10.2 a100u2w and k8temp modules AWOL on x86_64?
by Bernd Felsche 01 Jan '07

01 Jan '07

I've recently installed opensuse 10.2 (release) on some new hardware and have found that the a100u2w and k8temp modules are missing. CPU AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ in Gigabyte GA-M55plus-S3G mainboard with 1GB RAM Everything else works fine. Nice and stable. The former drives the Initio A100U2W SCSI host adapter (modprobe during boot tries but can't load absent module) and the latter is suggested by sensors-detect to ascertain the processor temperature. Driver `k8temp' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `AMD K8 thermal sensors' (confidence: 9) I've tried to figure out why they are absent but can't work it out. Kernel configuration provides the option to build the a100u2w module, and it's compiling now, but I'm stuck on the k8temp as there's no obvious option to build that. -- /"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia \ / ASCII ribbon campaign | "If we let things terrify us, X against HTML mail | life will not be worth living." / \ and postings | Lucius Annaeus Seneca, c. 4BC - 65AD. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0