November 2005 - openSUSE AMD64 - openSUSE Mailing Lists

Re: MonoDevelop - gnome-sharp.dll
by Karaoulis Marios 11 Nov '05

11 Nov '05

On Friday 11 November 2005 12:57, you wrote: > > I found a solution: > > > > MonoDevelop doesn't work with the updated version of gtk-sharp2 which is > > installed by apt or YOU. You have to reinstall the old from the original > > SuSE 10 CDs or repositories. > > > > Otherwise: Update mono to 1.9.x and MonoDevelop to v0.8 :) > Yes. You are right. Now everything is working..... i even downgraded beagle, and it runs ok... So this is a problem of the gnome supplementary repository..... Thanks __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Question on HP - WS XW9300
by Jurzitza, Dieter 11 Nov '05

11 Nov '05

Dear listmembers, after some quirks I succeeded in making a 2x2-CPU HP-Ws work using SuSE9.3. However, what I cannot do is shutdown and turn off the machine using shutdown -h now. This is probably due to the fact that I have to add apci=off on the boot-commandline, otherwise the system does not boot. Is there any workaround for this? I would have appreciated to implement an auto-shutoff in case of overtemperature feature, but cannot do so because I cannot turn the monster off as I intended to. Any help is greatly appreciated. If someone would be interested in some details about how to install, please let me know. I think SuSE 10.0 will be easier in this regard. Take care Dieter Jurzitza -- ________________________________________________ HARMAN BECKER AUTOMOTIVE SYSTEMS Dr.-Ing. Dieter Jurzitza Manager Hardware Systems System Development Industriegebiet Ittersbach Becker-Göring Str. 16 D-76307 Karlsbad / Germany Phone: +49 (0)7248 71-1577 Fax: +49 (0)7248 71-1216 eMail: DJurzitza(a)harmanbecker.com Internet: http://www.becker.de ******************************************* Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. *******************************************

2 1

HP XW9300, Nvidia driver and SLES 9
by David Stadden 10 Nov '05

10 Nov '05

Has anyone had any experience with the HP XW9300 workstation with the Nvidia Quadra 280 card? Dave

1 0

BUG in AMD64 or faulty design of Compaq Presario R4000 ??
by MA SL 10 Nov '05

10 Nov '05

Hi, I was testing the benchmark superPI for calculating the number PI. I wanted to compare my laptop Compaq Presario R4025 AMD64(2Ghz,512Kb) againts an Opteron846(2Gz,1024Kb) and a Pentium 4(3,2Ghz,512kb). I run superPi 25 which seems to calculate PI with 33554432 digis or 25 bits. The run proceeds until the end in both the opteron as well as the P4, but ABORTS in my latop at half of the calculation after aprox 30min with the message: STOP ERROR Not convergent in SQR statement executed Everything seems to work fine for other values of bits. I tried with 7,10,22 and 24 and it ran until completition. The only hit I found with google refering to this error message relates to unstability issues when overclocking. I checked my latop was not specially hot when aborting. Can anyone reproduce this error on a Compaq Presario R4000? Any HP with the same processor might also help. I posted this also on the R3000 list (initially devoted to the Compaq Presario R3000). I got a few answers of success on an R3000 -one using Gentoo; another using SUSE10 aborted with segmentation fault... Does AMD64 has a bug?? Has the Compaq Preario R4000 a faulty design?? It is also well possible that the problem lies elsewhere (my particular machine -cpu, Xpress200M, libraries-, Suse, or the program itself...) but given all troubles I'm having running Suse9.3 -CPU clock 2xfaster, impossible to use Xpress200M video card- and the crappy WinXP installation I got that doesn't lets me reduce its partition size below 12Gb, I can't avoid to fear that I'm facing a defective laptop. :( Any suggestions for other benchmarks I could use to discard a problem with my hardware ? I'd like at least to be able to trust any calculation I may do using it. Thanks in advance, MA ***************************** The specs of my CPU: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 15 model name : AMD Athlon(tm) 64 Processor 3200+ stepping : 0 cpu MHz : 997.133 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 pni sysc all nx mmxext lm 3dnowext 3dnow bogomips : 1961.52 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

1 0

Current Asus Support
by Ciro Iriarte 10 Nov '05

10 Nov '05

I'm getting a new system, and i'm worried about compatibility issues with current Suse release (i was expecting to wait for 10.2, but the pc seems to arrive earlier :) Specs: Asus A8N-SLI Premium AMD Athlon 64 3500+ 2GB Corsair RAM 1 WD Raptor for OS 4 Seagate SATA drives for data in RAID5 (would it be best to use MD or just the Silicon Image controler?) Are there any known issues?, i expect to run the 64bit version of the distro regards, Ciro

2 1

Thanks
by Abu Jalloh 10 Nov '05

10 Nov '05

Hello friends, Thanks very much. I agree with all the conditions laid for the suscriptions. Thanks again. Your friend, Jalloh, Abu _________________________________________________________________ Acepta el reto MSN Premium: Correos más divertidos con fotos y textos increíbles en MSN Premium. Descárgalo y pruébalo 2 meses gratis. http://join.msn.com?XAPID=1697&DI=1055&HL=Footer_mailsenviados_correosmasdi…

1 0

Monitor Out of range
by gilligan 09 Nov '05

09 Nov '05

Somehow I managed to crash Suse 10. So no problem, I'll reinstall. Install goes well and I told Suse to use VESA except it doesn't. Up comes the dreaded Out of Range on monitor. I remember someone telling me the command to use when I do Ctrl-Aly-F2. Well I can't or didn't remember it correctly. Can someone tell me how to do it. Thanks

2 1

Suspend on Suse 10
by Juanra 09 Nov '05

09 Nov '05

I have a Compaq r3375ea with nforce3 chipset, nvidia 4440 Go 64M, AMD64 3000+. When I suspend with nvidia driver the computer reboots. If I dont use the driver sometimes suspend and resume well and sometimes hangs during resume without any errors. Using kernel 2.6.13 and last nvidia driver. I follow the acpi howto<http://www.columbia.edu/%7Eariel/acpi/acpi_howto.txt>but it does not work. My /etc/sysconfiw/powersave/sleep: ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Description: Configuration of all three sleep modes (S2 is not supported):\n \ ## S1 sleep (only ACPI) low wake-up latency, \n \ ## S3 (ACPI) suspend to ram or (on APM systems) standby and \n \ ## S4 (ACPI) suspend to disk or (on APM systems) suspend. \n \ ## \n \ ## For some hardware, modules have to be unloaded before entering the \ ## sleep state. You can configure these in this section. These modules \ ## will be unloaded in the specified order. Modules which depend on one \ ## of the specified modules, will also be unloaded. If not all modules \ ## can be unloaded, entering the sleep state will fail. \n \ ## After resuming, the modules that have been unloaded will be reloaded \ ## in reverse order. \n \ ## The same applies for the "SERVICES_TO_RESTART"-variables which define \ ## services which have to be stopped before entering a sleep state. ## Path: System/Powermanagement/Powersave/Sleep_Modes ### Type: string ## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 lt_modem Intel536 Intel537" ## ServiceRestart: # # These modules will be unloaded before entering suspend to disk # See README.unload-modules for more information. # "NONE" means don't unload any modules. UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 lt_modem Intel536 Intel537 sata-nv rt2570" ## Path: System/Powermanagement/Powersave/Sleep_Modes ### Type: string ## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 lt_modem Intel536 Intel537" ## ServiceRestart: # # These modules will be unloaded before entering the corresponding # sleep state. See README.unload-modules for more information. # "NONE" means don't unload any modules. UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 lt_modem Intel536 Intel537 rt2570" ## Path: System/Powermanagement/Powersave/Sleep_Modes ### Type: string ## Default: "usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 lt_modem Intel536 Intel537" ## ServiceRestart: # # These modules will beunloaded before entering the corresponding # sleep state. See README.unload-modules for more information. # "NONE" means don't unload any modules. UNLOAD_MODULES_BEFORE_STANDBY="usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394 ipw2200 rt2500 prism54 lt_modem Intel536 Intel537 rt2570" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: string ## Default: "slmodemd irda" # # All services that have to be stopped before entering a sleep mode # and restarted after the machine resumes. # If you notice problems of some services that may be related to # suspend/standby, restarting the service may solve the problem. # The names to enter here are simply the filenames of the init scripts # in /etc/init.d. The services are stopped in the order entered here. # They are restarted after resume in the reverse order. # Entering "NONE" disables restarting of services ("" means default). SUSPEND2DISK_RESTART_SERVICES="network" SUSPEND2RAM_RESTART_SERVICES="network" STANDBY_RESTART_SERVICES="network" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "yes" # # Should FAT and NTFS filesystems be unmounted before entering # a sleep mode and remounted after the machine resumed? # You should do this for suspend to disk if you want to boot # Windows while Linux is suspended to avoid severe data corruption # on the Windows filesystems. # Note that suspend will fail if the partitions cannot be unmounted. # This may cause problems with external storage media connected during # suspend. # Defaults to yes for suspend to disk, no for suspend to RAM / standby. SUSPEND2DISK_UNMOUNT_FATFS="yes" SUSPEND2RAM_UNMOUNT_FATFS="yes" STANDBY_UNMOUNT_FATFS="yes" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # Should PCMCIA cards (CardBus and PC-Card) be ejected before entering # a sleep mode and reinserted after the machine resumed? # This should not be necessary for most CardBus cards, PC-Cards seem to # need this more often. SUSPEND2DISK_EJECT_PCMCIA="yes" SUSPEND2RAM_EJECT_PCMCIA="yes" STANDBY_EJECT_PCMCIA="yes" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" ## ServiceRestart: powersaved # # Set this variable to yes to disable suspend to disk. DISABLE_USER_SUSPEND2DISK="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "yes" ## ServiceRestart: powersaved # # Set this variable to no to enable suspend to RAM. # Be careful, many machines do not support this, see the README. DISABLE_USER_SUSPEND2RAM="no" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "yes" ## ServiceRestart: powersaved # # Set this variable to no to enable standby (also needs BIOS support!) DISABLE_USER_STANDBY="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: integer(0:1000) ## Default: 0 # # Specify the time in seconds a sleep state should be delayed. This can # be used to delay a power-button-induced suspend for some seconds to # be able to power off the machine hard. # SUSPEND2DISK_DELAY="" SUSPEND2RAM_DELAY="" STANDBY_DELAY="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: string(platform,firmware,shutdown,reboot) ## Default: "platform" # # Specify the shutdown method the kernel uses after suspend-to-disk. # "shutdown" is known to work on most machines, "platform" may work, # too. "firmware" will most likely not work, "reboot" is for # debugging only. Use only if you know what this is for. # SUSPEND2DISK_SHUTDOWN_MODE="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # Should the system clock be reset from the hardware clock after # suspend-to-disk or suspend-to-RAM? This may be unneccessary depending # on kernel version and SUSPEND2DISK_SHUTDOWN_MODE, but will not hurt. SUSPEND2DISK_RESTORE_CLOCK="yes" SUSPEND2RAM_RESTORE_CLOCK="" STANDBY_RESTORE_CLOCK="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # Should we suspend to disk even if it seems the kernel in /boot # is not matching the running kernel? This is very dangerous, if # the kernels don't match, resume will not work. Use only if you # absolutely need to (e.g. you are compiling a custom kernel). # SUSPEND2DISK_IGNORE_KERNEL_MISMATCH="" ## Path: System/Powermanagement/Powersave/Sleep_Modes ## Type: yesno ## Default: "no" # # Should we switch to a text console _in userspace_ before entering # a sleep mode? The kernel usually does this anyway, but if you need # to run some initialization code before switching back to X, this # might be handy. Also on ppc, the kernel does not switch, so this needs # to be "yes" there. SUSPEND2DISK_SWITCH_VT="" SUSPEND2RAM_SWITCH_VT="" STANDBY_SWITCH_VT=""

1 0

Re: [SLE] NFS in V 10 and Apple OS
by Jonathan Brooks 09 Nov '05

09 Nov '05

Roger Oberholtzer wrote: > On Wed, 2005-11-09 at 11:16 +0000, Jonathan Brooks wrote: >> Roger Oberholtzer wrote: >>> On Tue, 2005-11-08 at 18:55 -0800, Joseph Loo wrote: >>>> There is an option on the /etc/fstab that does the mounting >>>> automtaically. It has to do with the last 2 numbers on the list. I >>>> suggest you add 1 n where n is the order of mounting. If you have 0 in >>>> the first number, it will not automatically moun the partition. >>> Naahh.. >>> >>> The fifth number on the line (I get this from the fstab man page) is >>> related to the dump() command, and the sixth (last number on the line) >>> is related to fsck(). I think you are thinking of the key word 'auto' or >>> 'noauto' that you can provide in the comma separated list of mount >>> options in item four on the line. To understand those, look at the >>> 'mount' man page. Still, this is only automatic relative to when the >>> system boots. It does not mean that they will be automatically mounted >>> on demand at a later time. 'autofs' seems to be for that. >>> >> Okay, so is there a problem with NFS, SuSE10 and AMD64? It seems like my >> fstab was correct, and things should be mounted automagically at boot >> time. Are there any particular commands/logs I can look at on the server >> when the client boots, to see why it's not being allowed to connect? Is >> there something different with NFS under SuSE10? I.e. does it want to >> use nfsvers=4, and the server barfs when it gets these requests? >> >> Roger: is this why setting nfsvers=2 fixed your problems? > > Yes. The system I really needed this for was a vxWorks NFS server. It > exported the directory and only understood NFS version 2. As the 2.6 > kernel (SUSE 9.3 and later) does NFS version 3 internally and by > default, this option (and the 'udp' option) was needed to be able to > talk to the vxWorks server. Why NFS version 3 does not have a mechanism > to fall back on version 2 is anyone's guess. > >> However, I'm thinking that this isn't something SuSE 10 specific, more >> something related to AMD64, since the other AMD64 machine with this >> problem is on SuSE 9.3. > > Meaning kernel 2.6. All Linux with this version of the kernel would > exhibit this behavior. > >> Hope someone has some ideas out there? :) >> >> Best wishes, >> >> Jon. >> Hmm, our i586 (athlonXP/pentium4) machines running SuSE 9.3 (kernel 2.6) never have this problem. So I think there must be something different in the x86_64 kernel implementations of NFS (?) Or, our SLES server doesn't like the way our AMD64 machines talk to it. Any ideas? Jon. -- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon

2 1

AMD vs Intel - maybe you can offer less bias than I usually encounter
by lonn＠lonnd.com 09 Nov '05

09 Nov '05

Hello out there in AMD/Linux land, Has anyone risen above the many arguments and formulated any comparison between throughput in normal operations and in heavily burdened systems (not bench marks) for AMD 64 series CPU internal rate (advertised rate) and Intel of similar capability? Does same type of info exist for the later CPU generation of those two manufacturers? Lonn C. Dugan

3 2