October 2005 - openSUSE AMD64 - openSUSE Mailing Lists

RE: [suse-amd64] Sata Raid Controller for 64 bit?
by Black, Alain 14 Feb '06

14 Feb '06

Same here. Lspci shows it as " 01:01.0 RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 01)" We are also running the 3dm software to monitor the card/RAID set. -Alain. -----Original Message----- From: Kevin_Gassiot(a)veritasdgc.com [mailto:Kevin_Gassiot@veritasdgc.com] Sent: Tuesday, October 18, 2005 7:42 AM To: Andy Cc: Black, Alain; suse-amd64(a)suse.com; suse-ia64(a)suse.com Subject: Re: [suse-amd64] Sata Raid Controller for 64 bit? I've got one of the 8506 series SATA RAID controllers running the stock 3w-xxxx driver with no problems so far - had more problems finding an XP64 driver for it.... Kevin Gassiot Advanced Systems Group Visualization Systems Support Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot(a)veritasdgc.com "Andy" <frum(a)ar-sd.net> To 10/18/2005 02:57 "Black, Alain" AM <ablack(a)bloodsystems.org>, <suse-amd64(a)suse.com>, <suse-ia64(a)suse.com> cc Subject Re: [suse-amd64] Sata Raid Controller for 64 bit? >> We also use the 3ware RAID controllers for SATA. And have had no >> problems with them. I supose you mean the 3ware 9500S series controllers. I couldn't find any drivers for suse 9x 64 for the 8506 series. Andy. ----- Original Message ----- From: "Black, Alain" <ablack(a)bloodsystems.org> To: <suse-amd64(a)suse.com>; <suse-ia64(a)suse.com> Sent: Monday, October 17, 2005 10:24 PM Subject: RE: [suse-amd64] Sata Raid Controller for 64 bit? -----Original Message----- From: Jack Malone [mailto:jmalone@horizonind.com] Sent: Monday, October 17, 2005 4:18 AM To: suse-amd64(a)suse.com; suse-ia64(a)suse.com Subject: Re: [suse-amd64] Sata Raid Controller for 64 bit? At 04:06 AM 10/17/2005, Andy wrote: >Hi to all, > >We have a Fujitsu Siemens Econel 200 Server. 2x Intel Xeon 2.8, 2x >SATA HDD. Suse 9.1 64 Prof is installed. > >At the moment we are using a software raid, but we want to buy 2 >more HDD's and implement a 0+1 or 1+0 RAID. >I looked over and over about raid controllers, have found from 120 >EURO's to 1000 EURO's but there seems to be a little problematic >the Suse 64 driver. > >A very convenient driver would be the >Promise FastTrack S150 TX4 or >SX4 controller >but I still don't know if the drivers are quite functional. > >The tx4 seems faster as the sx4 but has no 64 driver. > >We had in the past some problems with hardware raid controller on suse. > >Does anyone uses some good raid controllers and could give me some >informations? > >I have been using 3ware sata raid on two different machines here at >work with amd 64 cpu's in them with no problem. suse has the 3ware >driver built in for years now. been using 3ware raid cards for years >also with no problems. now I am not sure what they cost in >EURO's since im in the US. jack -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com We also use the 3ware RAID controllers for SATA. And have had no problems with them. -Alain -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

4 4

RE: [suse-amd64] many lost ticks
by Langsdorf, Mark 02 Nov '05

02 Nov '05

> > > > Last thing when I look at the output of dmesg I get the > following (see > > below), I am slightly worried, since I have read somewhere that the > > kernel needs to be patched to include a more recent version of > > powernow-k8. Is this error expected, or should I patch? > > Known problem, but harmless. Just ignore for now. Some future > update kernel will likely fix it. Andi - I can submit a patch, but I'm not sure what to do. The code loops through NR_CPUS and ignores the ones that are not online: if (!cpu_online(i)) continue; This code used to work, but the hotplug changes broke it. What's the correct code now to check if a cpu isn't available? -Mark Langsdorf AMD, Inc.

4 3

RE: [suse-amd64] PCI memory hole and remapping (was -> Re: [suse-amd64] Memory Problem: 3Gb instead of 4Gb, TYAN K8WE s2895, 2x252 Opteron )
by Langsdorf, Mark 02 Nov '05

02 Nov '05

> > If your BIOS is doing this (as opposed to > > you mucking with the settings), I need to get the AMD BIOS > > developers to talk to your BIOS developers. > > That would be great. Please do that. What's shown above is > indeed the mtrr settings that come from the bios. I didn't > change anything. And that's the same on two different PCs > (both iwth A8V), so it's not that just one PC is broken or > sth... However, whatever problems I was reporting to ASUS, I > never got anything helpful back, or a fix in the next release > etc. They seem to ignore user bug reports, but I guess they > won't ignore AMD... What motherboard, BIOS vendor, and BIOS version are you using? > > You may want to check if your BIOS has an option for "Discrete" or > > "continuous" usage of MTRRs. Experiment with both settings - I > > believe "discrete" should work better in a memory hoisting > > environmnet. > > Unfortunately not! I read about other mainboards having this > option in the bios and looked for it carefully, because other > people reported they could fix the problem with the fglrx > driver using this setting. Unfortunately, Asus didn't put > such a setting in their latest release... They're supposed to have done so, after a huge fuss we had over these issues last year. After you give me the motherboard models, BIOS vendor, and BIOS version I can hopefully get this resolved. -Mark Langsdorf AMD, Inc.

2 3

Multimedia support after upgrading to kde 3.4.3
by Karaoulis Marios 31 Oct '05

31 Oct '05

Hi all, I just installed suse 10. I added to my repositories packman, and update all kde libs so i can have mp3 support. I want to add to my repositories also supplementary support for kde 3.4.3, but i saw that packman only have support for kde 3.4.2? What will happen if i update to kde 3.4.3? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

SuSE 10 x86_64 and Modem US Robotics
by Marcos Jordão 30 Oct '05

30 Oct '05

Hello, I'm brazilian and trying to leave Windows and to use Linux. I'm install SuSE 10 x86_64 on my Athlon 64 3000+. The only one problem that I have was the Modem Device. My modem is a US Robotics USR-263095-OEM and I know the Linuxant drivers support it. But in SuSE 10, I don't can do it work. The Linuxant offers installation for this modem and have a precompile version for SuSE 10. But it's for SuSE 10 i386... but my system is SuSE 10 x86_64. I get the generic package for 64 and try to install on my system, but it not work. I get the error: -------------------------------------------------------------------------------- linux:/home/marcos/modem # rpm -i hsfmodem-7.18.00.05x86_64full-1.x86_64.rpm aviso: hsfmodem-7.18.00.05x86_64full-1.x86_64.rpm: V3 DSA signature: NOKEY, key ID 5dfbf7dc Conexant HSF softmodem driver, version 7.18.00.05x86_64full If you need license keys, assistance or more information, please go to: http://www.linuxant.com/ When reporting a problem for the first time, please send us the file generated by "hsfconfig --dumpdiag". No pre-built modules for: SuSE-10.0 linux-2.6.13-15-default x86_64 Trying to automatically build the driver modules... (this requires a C compiler and proper kernel sources to be installed) Building modules for kernel 2.6.13-15-default, using source directory /lib/modules/2.6.13-15-default/build. Please wait... ERROR: Module build failed! Please examine the log file "/tmp/hsfconfig-buildlog.txt" to determine why. erro: %post(hsfmodem-7.18.00.05x86_64full-1) scriptlet failed, exit status 1 -------------------------------------------------------------------------------- I already install kernel-sources and gcc.. but no work! The hsfconfig-buildlog file returned: http://www.demolay.e-trends.com.br/hsfconfig-buildlog.txt Can somebody help me? Thank you, and I'm sorry by my english Marcos Antonio Campos Jordão'' Brazil

2 1

Re: [suse-amd64] many lost ticks
by Jonathan Brooks 29 Oct '05

29 Oct '05

Langsdorf, Mark wrote: >>> Last thing when I look at the output of dmesg I get the >> >> >> following (see >> >>> below), I am slightly worried, since I have read somewhere that the kernel needs to be patched to include a more recent version of powernow-k8. Is this error expected, or should I patch? >> >> >> Known problem, but harmless. Just ignore for now. Some future update kernel will likely fix it. > > > > Andi - > > I can submit a patch, but I'm not sure what to do. > > The code loops through NR_CPUS and ignores the ones that > are not online: > if (!cpu_online(i)) > continue; > > This code used to work, but the hotplug changes broke it. > What's the correct code now to check if a cpu isn't available? > Hi Andi/everyone, To test the timing issues I altered the boot command line, see below: root=/dev/sda3 vga=0x317 selinux=0 notsc resume=/dev/sda2 splash=silent But when I look with dmesg I see the following: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping 02 CPU 1: Syncing TSC to CPU 0. CPU 1: synchronized TSC with CPU 0 (last diff 0 cycles, maxerr 539 cycles) Brought up 2 CPUs Disabling vsyscall due to use of PM timer time.c: Using PM based timekeeping. I don't fully understand this message, but if I were a gambling man, I would say that this isn't what you'd expect to see? :) Best wishes, Jon -- Jonathan Brooks (Ph.D.) Research Fellow PaIN Group, Department of Human Anatomy & Genetics University of Oxford, South Parks Road, Oxford, OX1 3QX tel: 01865 282654 fax: 01865 282656

1 0

RE: [suse-amd64] many lost ticks
by Langsdorf, Mark 28 Oct '05

28 Oct '05

> * On Thu, Oct 27, 2005 at 01:04 PM (+0100), Jonathan Brooks wrote: > > > I have an AMD Athlon64 X2 machine running SuSE 10 (x86_64) on an > > Nvidia Nforce4 Ultra motherboard, and have noticed that the system > > clock has become unstable (it runs too fast). Not sure when it > > occurred, but I have been getting a lot of error messages > like this in > > dmesg: > > > > warning: many lost ticks. > > Your time source seems to be instable or some driver is hogging > > interupts rip acpi_processor_idle+0x12f/0x37f [processor] > > I had a very similar (or the same?) problem on a "Tyan Thunder K8SE > 2892G3NR" dual Opteron machine running SuSE Linux 9.3: The system > time ran much too fast (minutes were almost running like seconds), > the screen saver started only seconds after not moving the mouse > or pressing a key and the log file was full of these messages > ("many lost ticks"). > > My notice was that it especially happend when the CPU usage > grew, so I suppose it was related to the "powernow" feature > of the CPU, because at least on Opteron systems SuSE's "power > management" changes the CPU clock based on the load. > > After I upgraded to the most recent vanilla kernel the > problem was gone. The powernow-k8 driver in SL9.3 caused clock instability on SMP machines that did not support HPET timers; SL10.0 and the mainstream kernel support PMTimer for those machines. That's most likely what you were seeing. The single processor, dual-core problem is believed to be something different and is under investigation at AMD. We will make a statement as soon as we have definite information. -Mark Langsdorf AMD, Inc.

5 4

RE: [suse-amd64] many lost ticks
by Langsdorf, Mark 28 Oct '05

28 Oct '05

> On Thursday 27 October 2005 19:42, Langsdorf, Mark wrote: > > > Unofficially, clock=pmtmr should at least reduce the amount of lost > > ticks. > > I doubt it will help on 64bit kernels, which don't have this > option (ok placebos are sometimes known to help on computers too > clock= only exists on 32bit. I'll defer to you, Andi, but 2.6.13.4 definitely has PM timer support for AMD64. Is there really no way to force a particular time source on AMD64? > notsc might do the trick on 64bit though. However it will > only work on multi processor systems. On uniprocessor there > is currently no way to force another clock. Okay. Would a patch to change this be accepted? -Mark Langsdorf AMD, Inc.

3 11

Can't load SuSE 9.3 on new motherboard
by Pierre Patino 28 Oct '05

28 Oct '05

Greetings I obtained a newly released Opteron/Athlon64 socket 939 motherboard from SuperMicro. I built the box and put the DVD in and booted. After I get through the installation choices, the installer stops and says it can no longer "see" the DVD/CD reader (panel becomes painted in red). This I tried with every installation choice (acpi on/off, safe mode etc.). I tried loading SLE9 and I got a different problem -- it could not see the SATA hard disk. I suspect that the loaded 9.3 kernel module has trouble talking to the DVD drive because of some chipset issue. I'm surprised that the initial whatchamacallit that boots and starts the installation process has no trouble with the DVD drive. Has anybody conquered this demon? TIA & Cheers

2 4

RE: [suse-amd64] many lost ticks
by Langsdorf, Mark 27 Oct '05

27 Oct '05

> >> My notice was that it especially happend when the CPU usage > >> grew, so I suppose it was related to the "powernow" feature > >> of the CPU, because at least on Opteron systems SuSE's "power > >> management" changes the CPU clock based on the load. > >> > >> After I upgraded to the most recent vanilla kernel the > >> problem was gone. > > > > The powernow-k8 driver in SL9.3 caused clock instability on SMP > > machines that did not support HPET timers; SL10.0 and the > > mainstream kernel support PMTimer for those machines. That's > > most likely what you were seeing. > > > > The single processor, dual-core problem is believed to > > be something different and is under investigation at AMD. > > We will make a statement as soon as we have definite > > information. > > So can you confirm that the kernel options clock=pmtmr and > notsc will not have any effect on this problem, and we should > wait for a resolution from AMD? I cannot confirm that. They may help. We're working on finding the answer. I suspect that clock=pmtmr will help, for what it's worth. > Sorry for the request for clarification, but I'm stumbling > around in the dark on this matter, and don't want to waste > any more time on the problem - especially if it's all fruitless. All I can officially say at this point is that AMD is aware of the problem and will be releasing a statement when we have more information. Unofficially, clock=pmtmr should at least reduce the amount of lost ticks. -Mark Langsdorf AMD, Inc.

3 2