November 2005 - openSUSE AMD64 - openSUSE Mailing Lists

what frequency should my CPU run at?
by Jonathan Brooks 18 Nov '05

18 Nov '05

Hi, I have an AMD64 X2 4400+ and had noticed that the CPU frequency (as reported by a Windows XP Pro virtual machine running under VMware 5.5beta on SuSE 10 x86_64 host) is being reported as 1GHz. So I did a bit of digging and found that cat /proc/cpuinfo gives: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 35 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping : 2 cpu MHz : 1005.155 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 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 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips : 2012.38 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 processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 35 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping : 2 cpu MHz : 1005.155 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 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 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips : 2012.38 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 Sorry if this is a repetition of the earlier thread regarding CPUFREQD, but I am still uncertain of the implications of the bug in the CPU frequency scaling. Is there a workaround? Best wishes, Jon.

1 0

AIM benchmark strangeness
by Pierre Patino 18 Nov '05

18 Nov '05

Greetings I downloaded AIM IX http://sourceforge.net/projects/aimbench (which untars to aim9 directory) from sourceforge to compare two motherboards against an older UltraSparcII,600MHz Solaris 8 system. As expected the two newer motherboards, both with SuSE 10.0, Athlon 64 3000+ were much faster except for three tests: Sync Random Writes, Sync Sequential Writes and Sync Disk Copies. In these three cases, the Sun board was 10 to 30 times faster. The Sun board has an EIDE ATA66 hard drive (40GB). Both Linux boards had 250GB SATA drives with 8MB buffers. The Linux FS is the default reiserfs. Before I drill any deeper, has anyone got any hints? TIA & Cheers

2 2

USB support in SuSE 10.0
by Constantine 'Gus' Fantanas 18 Nov '05

18 Nov '05

Is USB support in SuSE 10.0 broken? After upgrading to 10.0 from 9.3, I cannot get hotplug to properly recognize USB peripherals. In particular, I have my cellphone and a compact flash reader; both of them worked great under 9.3. Neither seems to work after the upgrade to 10.0. 'ls /proc/partitions' does not even see the CF card. After plugging and unplugging the cellphone and or the CF card reader a couple of times, udev seems not to recognize any USB connects/disconnects any more. 'lsusb' and 'usbview' do not see them either. This did not happen in 9.3. The computer in question is a Compaq Presario 3240 laptop, AMD64-based, with the nVidia chipset and nVidia graphics card (I downloaded the nVidia chipset drivers last month and that fixed my ethernet lockup probelms). I have the latest updates from the repositories and my kernel is 2.6.13-15. I am glad I retained my 9.3 DVDs. I am seriously thinking about returning to 9.3. Below I provide syslogs regarding the CF card reader (when the connection is recognized) if that may help. CF --------------------------------snip------------------------------------------------------------ Nov 17 16:22:35 presario kernel: ohci_hcd 0000:00:02.1: wakeup Nov 17 16:22:35 presario kernel: usb 3-1: new full speed USB device using ohci_hcd and address 8 Nov 17 16:22:35 presario kernel: scsi5 : SCSI emulation for USB Mass Storage devices Nov 17 16:22:35 presario kernel: usb-storage: device found at 8 Nov 17 16:22:35 presario kernel: usb-storage: waiting for device to settle before scanning Nov 17 16:22:41 presario kernel: Vendor: Model: Rev: Nov 17 16:22:41 presario kernel: Type: Direct-Access ANSI SCSI revision: 02 Nov 17 16:22:41 presario kernel: SCSI device sda: 125440 512-byte hdwr sectors (64 MB) Nov 17 16:22:41 presario kernel: sda: test WP failed, assume Write Enabled Nov 17 16:22:41 presario kernel: sda: assuming drive cache: write through Nov 17 16:22:41 presario kernel: SCSI device sda: 125440 512-byte hdwr sectors (64 MB) Nov 17 16:22:41 presario kernel: sda: test WP failed, assume Write Enabled Nov 17 16:22:41 presario kernel: sda: assuming drive cache: write through Nov 17 16:22:41 presario kernel: sda: sda1 Nov 17 16:22:41 presario kernel: Attached scsi removable disk sda at scsi5, channel 0, id 0, lun 0 Nov 17 16:22:41 presario kernel: Attached scsi generic sg0 at scsi5, channel 0, id 0, lun 0, type 0 Nov 17 16:22:41 presario kernel: Vendor: Microtec Model: CameraMate (DPCM Rev: 0100 Nov 17 16:22:41 presario kernel: Type: Direct-Access ANSI SCSI revision: 00 Nov 17 16:22:41 presario kernel: usb 3-1: reset full speed USB device using ohci_hcd and address 8 Nov 17 16:22:41 presario kernel: usb 3-1: device descriptor read/64, error -32 Nov 17 16:22:41 presario kernel: usb 3-1: device descriptor read/64, error -32 Nov 17 16:22:41 presario kernel: usb 3-1: reset full speed USB device using ohci_hcd and address 8 Nov 17 16:22:42 presario kernel: usb 3-1: device descriptor read/64, error -32 Nov 17 16:22:42 presario kernel: usb 3-1: device descriptor read/64, error -32 Nov 17 16:22:42 presario kernel: usb 3-1: reset full speed USB device using ohci_hcd and address 8 Nov 17 16:22:42 presario kernel: usb 3-1: device not accepting address 8, error -32 Nov 17 16:22:43 presario kernel: usb 3-1: reset full speed USB device using ohci_hcd and address 8 Nov 17 16:22:43 presario kernel: usb 3-1: device not accepting address 8, error -32 Nov 17 16:22:43 presario kernel: usb 3-1: USB disconnect, address 8 Nov 17 16:22:43 presario kernel: sdb : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sdb : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sdb : sense not available. Nov 17 16:22:43 presario kernel: sda : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sda : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sda : sense not available. Nov 17 16:22:43 presario kernel: sdb: Write Protect is off Nov 17 16:22:43 presario kernel: sdb: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sdb: assuming drive cache: write through Nov 17 16:22:43 presario kernel: sda: Write Protect is off Nov 17 16:22:43 presario kernel: sda: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sda: assuming drive cache: write through Nov 17 16:22:43 presario kernel: sdb : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sdb : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sdb : sense not available. Nov 17 16:22:43 presario kernel: sda : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sda : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sda : sense not available. Nov 17 16:22:43 presario kernel: sdb: Write Protect is off Nov 17 16:22:43 presario kernel: sdb: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sdb: assuming drive cache: write through Nov 17 16:22:43 presario kernel: sda: Write Protect is off Nov 17 16:22:43 presario kernel: sda: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sda: assuming drive cache: write through Nov 17 16:22:43 presario kernel: sda:<4>printk: 12 messages suppressed. Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 0 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 0 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 0 Nov 17 16:22:43 presario kernel: unable to read partition table Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 0 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 1 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 2 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 3 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 4 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 5 Nov 17 16:22:43 presario kernel: Buffer I/O error on device sda, logical block 6 Nov 17 16:22:43 presario kernel: sdb : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sdb : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sdb : sense not available. Nov 17 16:22:43 presario kernel: sda : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sda : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sda : sense not available. Nov 17 16:22:43 presario kernel: sdb: Write Protect is off Nov 17 16:22:43 presario kernel: sdb: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sdb: assuming drive cache: write through Nov 17 16:22:43 presario kernel: sdb: unable to read partition table Nov 17 16:22:43 presario kernel: sda: Write Protect is off Nov 17 16:22:43 presario kernel: sda: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sda: assuming drive cache: write through Nov 17 16:22:43 presario kernel: Attached scsi removable disk sdb at scsi5, channel 0, id 0, lun 1 Nov 17 16:22:43 presario kernel: Attached scsi generic sg1 at scsi5, channel 0, id 0, lun 1, type 0 Nov 17 16:22:43 presario kernel: sda : READ CAPACITY failed. Nov 17 16:22:43 presario kernel: sda : status=0, message=00, host=1, driver=00 Nov 17 16:22:43 presario kernel: sda : sense not available. Nov 17 16:22:43 presario kernel: sda: Write Protect is off Nov 17 16:22:43 presario kernel: sda: Mode Sense: 00 00 00 00 Nov 17 16:22:43 presario kernel: sda: assuming drive cache: write through Nov 17 16:22:43 presario kernel: sda:<7>usb-storage: device scan complete Nov 17 16:22:43 presario kernel: scsi5 (0:0): rejecting I/O to dead device Nov 17 16:22:43 presario kernel: scsi5 (0:0): rejecting I/O to dead device Nov 17 16:22:43 presario kernel: scsi5 (0:0): rejecting I/O to dead device Nov 17 16:22:43 presario kernel: unable to read partition table Nov 17 16:22:43 presario kernel: scsi5 (0:0): rejecting I/O to dead device Nov 17 16:22:43 presario kernel: usb 3-1: new full speed USB device using ohci_hcd and address 9 Nov 17 16:22:43 presario kernel: usb 3-1: device descriptor read/64, error -110 Nov 17 16:22:44 presario kernel: usb 3-1: device descriptor read/64, error -110 Nov 17 16:22:44 presario kernel: usb 3-1: new full speed USB device using ohci_hcd and address 10 Nov 17 16:22:44 presario kernel: usb 3-1: device descriptor read/64, error -110 Nov 17 16:22:44 presario kernel: usb 3-1: device descriptor read/64, error -110 Nov 17 16:22:44 presario kernel: usb 3-1: new full speed USB device using ohci_hcd and address 11 Nov 17 16:22:45 presario kernel: usb 3-1: device not accepting address 11, error -110 Nov 17 16:22:45 presario kernel: usb 3-1: new full speed USB device using ohci_hcd and address 12 Nov 17 16:22:45 presario kernel: usb 3-1: device not accepting address 12, error -110

4 3

RE: [suse-amd64] suse amd64 9.3 and firefox-1.0.7 issue...help!
by Corr, Thomas 17 Nov '05

17 Nov '05

Not sure if this well help, but have your verified the settings of LD_LIBRARY_PATH variable? >From root: echo $LD_LIBRARY_PATH >From user: echo $LD_LIBRARY_PATH Just to make sure they are set the same. -----Original Message----- From: Ryan Biltz [mailto:rbiltz@ncmir.ucsd.edu] Sent: Thursday, November 17, 2005 2:59 PM To: suse-amd64(a)suse.com Subject: [suse-amd64] suse amd64 9.3 and firefox-1.0.7 issue...help! Hello All, I've been struggling with this for a while. I'm not sure why it's happening and a search on google doesn't reveal much. I receive the following error when a normal user tries to run firefox: /opt/MozillaFirefox/lib/firefox-bin: symbol lookup error: /opt/MozillaFirefox/lib/firefox-bin: undefined symbol: gdk_threads_lock root can run firefox ok. thanks for any help. --ryan -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

3 2

suse amd64 9.3 and firefox-1.0.7 issue...help!
by Ryan Biltz 17 Nov '05

17 Nov '05

Hello All, I've been struggling with this for a while. I'm not sure why it's happening and a search on google doesn't reveal much. I receive the following error when a normal user tries to run firefox: /opt/MozillaFirefox/lib/firefox-bin: symbol lookup error: /opt/MozillaFirefox/lib/firefox-bin: undefined symbol: gdk_threads_lock root can run firefox ok. thanks for any help. --ryan

1 0

OFF-TOPIC - *very* bad
by Jurzitza, Dieter 16 Nov '05

16 Nov '05

Dear listmembers, a big please: could you try sudo -s <ROOTPASSWD> ROOTSHELL Ctrl-d (back to original shell) sudo -s ROOTSHELL !!!! No question for password. This should never happen. !!!! Ctrl-d (back to original shell) I perceive this as a serious bug. I see this here on SuSE 9.3 (both amd64 and i586) and have no other platform to test - any feedback is highly appreciated! The system asks again for the password after a certain amount of time (10min to 30min). I haven't debugged this with too much depth. Thanks in advance, 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. *******************************************

7 6

Postfix + Cyrus SASL problems
by Florin Vlaicu 16 Nov '05

16 Nov '05

Hello, I had some problems with running postfix and Cyrus SASL on openSuSE 10 The first problem i ran into was that although Cyrus SASL was compiled with mysql support it didn't know anything about mysql. this is my proof Nov 9 22:18:20 aka-build postfix/smtpd[23244]: SQL engine 'mysql' not supported Nov 9 22:18:20 aka-build postfix/smtpd[23244]: auxpropfunc error no mechanism available Nov 9 22:18:20 aka-build postfix/smtpd[23244]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: sql I recompiled the cyrus-sasl package and I added to the --with-mysql option in the spec file also the path to the headers making it --with-mysql=/usr/include/mysql After doing this mysql queries worked Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql auxprop plugin using mysql engine Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin try and connect to a host Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin trying to open db 'postfix' on host 'localhost' Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin try and connect to a host Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin trying to open db 'postfix' on host 'localhost' Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin try and connect to a host Nov 16 00:02:54 aka-build postfix/smtpd[4790]: sql plugin trying to open db 'postfix' on host 'localhost' Now my problem is another one. In my database I have the passwords stored with crypt md5 (system) not the one from mysql (it was easy to migrate from shadow to mysql) So I applied this patch to cyrus-sasl -----------------------begin patch *** lib/checkpw.c.orig Thu Feb 13 14:07:23 2003 --- lib/checkpw.c Thu Feb 13 14:07:03 2003 *************** *** 145,151 **** "*cmusaslsecretPLAIN", NULL }; struct propval auxprop_values[3]; ! if (!conn || !userstr) return SASL_BADPARAM; --- 145,155 ---- "*cmusaslsecretPLAIN", NULL }; struct propval auxprop_values[3]; ! ! /* added lopaka */ ! char *salt = malloc(13); ! char *crypt_passwd = NULL; ! if (!conn || !userstr) return SASL_BADPARAM; *************** *** 182,193 **** goto done; } /* At the point this has been called, the username has been canonified * and we've done the auxprop lookup. This should be easy. */ if(auxprop_values[0].name && auxprop_values[0].values && auxprop_values[0].values[0] ! && !strcmp(auxprop_values[0].values[0], passwd)) { /* We have a plaintext version and it matched! */ return SASL_OK; } else if(auxprop_values[1].name --- 186,211 ---- goto done; } + /* 20030213 lopaka */ + /* encrypt the passwd and then compare it with the encrypted passwd */ + if(strlen(auxprop_values[0].values[0]) > 13) + { + /* MD5 */ + strncpy(salt,auxprop_values[0].values[0],13); + } + else + { + /* DES */ + strncpy(salt,auxprop_values[0].values[0],3); + } + crypt_passwd = crypt(passwd,salt); + /* At the point this has been called, the username has been canonified * and we've done the auxprop lookup. This should be easy. */ if(auxprop_values[0].name && auxprop_values[0].values && auxprop_values[0].values[0] ! && !strcmp(auxprop_values[0].values[0], crypt_passwd)) { /* We have a plaintext version and it matched! */ return SASL_OK; } else if(auxprop_values[1].name ---------------end patch After applying this patch I get this in the log: Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql auxprop plugin using mysql engine Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin try and connect to a host Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin trying to open db 'postfix' on host 'localhost' Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin try and connect to a host Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin trying to open db 'postfix' on host 'localhost' Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin try and connect to a host Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin trying to open db 'postfix' on host 'localhost' Nov 16 00:17:34 aka-build postfix/smtpd[15345]: begin transaction Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin create statement from userPassword aka lumina.ro Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin doing query SELECT password FROM mailbox WHERE username = 'aka(a)lumina.ro'; Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin create statement from cmusaslsecretPLAIN aka lumina.ro Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin doing query SELECT password FROM mailbox WHERE username = 'aka(a)lumina.ro'; Nov 16 00:17:34 aka-build postfix/smtpd[15345]: commit transaction Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin Parse the username aka(a)lumina.ro Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin try and connect to a host Nov 16 00:17:34 aka-build postfix/smtpd[15345]: sql plugin trying to open db 'postfix' on host 'localhost' Nov 16 00:17:34 aka-build kernel: smtpd[15345]: segfault at ffffffffac1972e0 rip 00002aaaabdbf8b0 rsp 00007fffffe93678 error 4 The thing that worries me is that segfault :P Does anyone have any suggestions?

1 0

BUG in powersaved: cpufreq unreliable with Athlon64 X2 (dual core)
by Bernd Paysan 16 Nov '05

16 Nov '05

[already entered as BUG report into the powersaved project at sf] Hi, As far as I can tell, cpufreq/powersaved seems to have a problem with the Athlon64 X2 dual core chips. If I load just one core, the CPU frequency boost is unreliable (toggles between 1GHz and 2GHz). Loading the second core, too, sort-of-fixes that problem. The reason is obvious: The Athlon X2 has a *single* CPU frequency setting which affects *both* cores. So you can't simply use a SMP setting, treating the two CPUs as two processors with two speed settings, you have to know that it's a dual-core CPU, and that you can't independently set the CPU frequency. If one core is loaded, both must run at double frequency. Note that the kernel does know about this fact: /sys/devices/system/cpu/cpu0/cpufreq> cat affected_cpus 0 1 /sys/devices/system/cpu/cpu1/cpufreq> cat affected_cpus 0 1 Setting powersaved to be more verbose confirms the confusion (the following is with one core loaded by an endless loop, the other core loaded lightly): ------------------------------------------------- Nov 10 13:24:48 linux [powersave]: Info (setSpeed:90) Speed set to: 1800000KHz in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed Nov 10 13:24:48 linux [powersave]: Info (setSpeed:90) Speed set to: 2000000KHz in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed Nov 10 13:24:48 linux [powersave]: Info (adjustSpeed:196) Speed directly set to max (2000000) MHz Nov 10 13:24:48 linux [powersave]: Info (decreaseSpeed:138) current speed: 2000000KHz new speed: 1800000KHz Nov 10 13:24:48 linux [powersave]: Info (setSpeed:90) Speed set to: 1800000KHz in file /sys/devices/system/cpu/cpu1/cpufreq/scaling_setspeed Nov 10 13:24:48 linux [powersave]: Info (adjustSpeed:207) Speed decreased to (1800000) MHz Nov 10 13:24:48 linux [powersave]: Info (decreaseSpeed:138) current speed: 2000000KHz new speed: 1800000KHz Nov 10 13:24:48 linux [powersave]: Info (setSpeed:90) Speed set to: 1800000KHz in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed Nov 10 13:24:48 linux [powersave]: Info (adjustSpeed:207) Speed decreased to (1800000) MHz Nov 10 13:24:48 linux [powersave]: Info (setSpeed:90) Speed set to: 2000000KHz in file /sys/devices/system/cpu/cpu1/cpufreq/scaling_setspeed Nov 10 13:24:48 linux [powersave]: Info (adjustSpeed:196) Speed directly set to max (2000000) MHz Nov 10 13:24:48 linux [powersave]: Info (decreaseSpeed:138) current speed: 1800000KHz new speed: 1000000KHz Nov 10 13:24:48 linux [powersave]: Info (setSpeed:90) Speed set to: 1000000KHz in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed Nov 10 13:24:48 linux [powersave]: Info (adjustSpeed:207) Speed decreased to (1000000) MHz ------------------------------------------------- This seems to be a pretty severe bug, rendering powersaved pretty unusable on a dual-core Athlon64. I already checked the source, and there really is no code that looks at cpufreq/affected_cpus. There should be only one object per affected set of CPUs, and a list/bitset of processors instead of a single processor number. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/

3 5

AW: [suse-amd64] OFF-TOPIC - *very* bad
by Jurzitza, Dieter 15 Nov '05

15 Nov '05

Dear listmembers, I discovered this accidentally and never ever had had thought that something like this could happen. There are cases where a "sudo" option IMHO is preferrable over an extra root login on some console window, this is why I use it on a common base. And, when installing sudo, I cannot remember having been warned about something like this. Ok, ok, it is a RTFM issue. Nevertheless I cannot see a good reason to use 5 min password asking timeout as the default - I think that 0 min would be appropriate - whoever needs it shorter, can set it accordingly - but on his / her own risk. I think it would be a good policy for SuSE to change this as it is a risk that is adjustable and leaks should - IMHO - not be open as default. Thanks for all your feedback, 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 > -----Ursprüngliche Nachricht----- > Von: Ken Siersma [mailto:siersmak@ekkinc.com] > Gesendet: Dienstag, 15. November 2005 10:09 > An: suse-amd64(a)suse.com > Betreff: Re: [suse-amd64] OFF-TOPIC - *very* bad > > > Tim Janssen wrote: > >Also, this feature is not Suse specific. The sudo memory is > (I think) > >standard for sudo on most distributions (at least RedHat and Fedora, > >which I can verify). Nevertheless, it is indeed a security issue. > > > >Cheers, > > > >Tim > >--- Siegbert Baude <siegbert.baude(a)gmx.de> wrote: > > > > > >>Jerry Westrick schrieb: > >> > >> > >>>On Tuesday 15 November 2005 11:15, Jurzitza, Dieter wrote: > >>> > >>> > >>> > >>>>Dear listmembers, > >>>>a big please: could you try > >>>> > >>>>sudo -s > >>>><ROOTPASSWD> > >>>>ROOTSHELL > >>>>Ctrl-d > >>>>(back to original shell) > >>>> > >>>>sudo -s > >>>>ROOTSHELL !!!! No question for password. This should > never happen. > >>>>!!!! Ctrl-d (back to original shell) > >>>> > >>>>I perceive this as a serious bug. I see this here on SuSE > 9.3 (both > >>>>amd64 and i586) and have no other platform to test - any > feedback is > >>>>highly appreciated! The system asks again for the > password after a > >>>>certain amount of time (10min to 30min). I haven't debugged this > >>>>with too much depth. Thanks in advance, take care > >>>> > >>>> > >>>> > >>>>Dieter Jurzitza > >>>> > >>>> > >>>> > >>>Ditto SUSE 10.0 Pro (Comercial)... > >>> > >>> > >>> > >>The same on SUSE 9.2, but this is not a bug, it's a feature. "Man > >>sudo" > >>reveals this in the first paragraph, in the paragraph about sudo > >>security you also find interesting pieces of information. > To change this > >>"man sudoers" says: > >> > >>timestamp_timeout > >> Number of minutes that can elapse before > sudo will > >>ask for a passwd again. > >> The default is 5. Set this to 0 to > always prompt for > >>a password. If set to > >> a value less than 0 the user's timestamp > will never > >>expire. This can be used > >> to allow users to create or delete their own > >>timestamps via sudo -v and sudo > >> -k respectively. > >> > >> > >>Ciao > >>Siegbert > >> > >>-- > >>Check the List-Unsubscribe header to unsubscribe > >>For additional commands, email: suse-amd64-help(a)suse.com > >> > >> > >> > > > > > > > AFAIK, it has been standard practice for quite some time to > not install > sudo if you are concerned about security. I don't have it on my home > system which has a direct connection to the internet, with > good reason, > or my firewall at work, which I installed a good 3 years ago. > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com > > ******************************************* 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. *******************************************

4 3

AW: [suse-amd64] Question on HP - WS XW9300
by Jurzitza, Dieter 15 Nov '05

15 Nov '05

Dear listmembers, many thanks for all the replies. I tried your suggestions, pci=noacpi does the trick. So, if there is any "RTFM" for XW9300 WS out in the net, I would volunteer to put this in, if someone else would do -> fine as well. Thank you once again, happlily shutting off now, 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. *******************************************

1 0

RE: [suse-amd64] Re: [powersave-devel] [ powersave-Bugs-1353119 ] cpufreq unreliable with Athlon64 X2 (dual core)
by Langsdorf, Mark 14 Nov '05

14 Nov '05

> > Setting powersaved to be more verbose confirms the > > confusion (the following is with one core loaded by an > > endless loop, the other core loaded lightly): > > I remember Mark Langsdorf telling me that if two speeds are > set for two cores on the same socket, the higher one will > be activated on both. For this case the old alogrithm > should still be sufficient and the concerns for > 10.0 stated above should not be the case, but I maybe wrong here. That's true for the version of the driver in SLES, but the cpufreq interface for dual-core changed in 2.6.10 and the new driver is last change wins. -Mark Langsdorf AMD, Inc.

1 0

Re: [suse-amd64] Question on HP - WS XW9300
by Karsten Weiss 14 Nov '05

14 Nov '05

On Fri, 11 Nov 2005, mike wrote: > On Friday 11 November 2005 14:41, Jurzitza, Dieter wrote: > > 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 > > I don't think there is. From what I remember, there is something about a > dual CPU machine prevents the automatic shutdown as with a single cpu > system. It does have something to do with the acpi=off, but exactly > what I'm not sure. I know that on my dual amd 2800 machine, I must hit > the button to turn it off. We also had boot problems with a dual-core xw9300 system because even the latest SuSE 9.3 erratum kernel does not detect the lsi logic scsi controller with the default boot options. However, on my xw9300 system it was sufficient to use "pci=noacpi" instead of "acpi=off" to fix this detection problem. I also tried "pci=lastbus=0x61" without "pci=acpi" but that didn't work out. 0000:61:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) 0000:61:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) Apart from that we still have problems with the internal nic on SuSE 9.3 and latest the nvnet driver. We talked with NVIDIA about it and they would like us to test with a fully acpi-enabled kernel. But as mentioned above this does not work without at least "pci=noacpi". Side node: The vanilla SuSE 9.3 kernel installed by the dvd installer doesn't work with Dual-Core Opterons. However, this can be worked around by temporarily disabling the Dual-Core feature in the bios, installing+upgrading to the latest suse93 kernel and finally reenabling the dual-core feature. Best regards, Karsten -- __________________________________________creating IT solutions Dipl.-Inf. Karsten Weiss science + computing ag phone: +49 7071 9457 452 Hagellocher Weg 71-75 teamline: +49 7071 9457 681 72070 Tuebingen, Germany email: knweiss(a)science-computing.de www.science-computing.de

2 1

Re: [powersave-devel] [ powersave-Bugs-1353119 ] cpufreq unreliable with Athlon64 X2 (dual core)
by Thomas Renninger 14 Nov '05

14 Nov '05

SourceForge.net wrote: > Bugs item #1353119, was opened at 2005-11-10 13:35 > Message generated for change (Tracker Item Submitted) made by Item Submitter > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=700009&aid=1353119&group_… > > Please note that this message will contain a full copy of the comment thread, > including the initial issue submission, for this request, > not just the latest update. > Category: None > Group: None > Status: Open > Resolution: None > Priority: 5 > Submitted By: Bernd Paysan (paysan) > Assigned to: Nobody/Anonymous (nobody) > Summary: cpufreq unreliable with Athlon64 X2 (dual core) > > Initial Comment: > Hi, > > As far as I can tell, cpufreq/powersaved (of 0.10.15.1, as in > SuSE 10.0) seems to have a severe problem with the > Athlon64 X2 dual core chips. If I load just one core, the > CPU frequency boost is unreliable (toggles between 1GHz > and 2GHz). Loading the second core, too, sort-of-fixes that > problem. So the assumption, that the higher value when writing to two sibling cores is taken is wrong, but the last value written is taken? See below. > > The reason is obvious: The Athlon X2 has a *single* CPU > frequency setting which affects *both* cores. So you can't > simply use a SMP setting, treating the two CPUs as two > processors with two speed settings, you have to know that > it's a dual-core CPU, and that you can't independently set > the CPU frequency. If one core is loaded, both must run at > double frequency. > > Note that the kernel does know about this fact: > > /sys/devices/system/cpu/cpu0/cpufreq> cat affected_cpus > 0 1 > /sys/devices/system/cpu/cpu1/cpufreq> cat affected_cpus > 0 1 > Yes, I have done this already for SLES9-SP2. IIRC there was no affected_cpus file in 2.6.5, so I had to parse /proc/cpuinfo for siblings and cores. > Setting powersaved to be more verbose confirms the > confusion (the following is with one core loaded by an > endless loop, the other core loaded lightly): I remember Mark Langsdorf telling me that if two speeds are set for two cores on the same socket, the higher one will be activated on both. For this case the old alogrithm should still be sufficient and the concerns for 10.0 stated above should not be the case, but I maybe wrong here. Hmm, I just rechecked. This cannot be the case for newer kernels any more as there /sys/devices/.../cpu0/cpufreq is a link to /sys/devices/.../cpu1/cpufreq so probably the last speed written into one of them gets the active freq. The cpumask approach patch looks nice, but for a quick look, it's not complete (it should need a hack in adjustSpeed function itself, setMode should only be invoked once when the user switches between e.g. dynamic to performance mode). We should either: 1) only create one object per cpu socket that sets the speed for all its cores. Probably the nicer solution (but IIRC needs some redoing of code to be able to access/create file paths to the other CPU(s). 2) Still use CPU core objects and set the speed according to the max Load of both. Disadvantage: memory/performance waste (two objects for 1 socket and two times written into each core). Ok, I just talked with Holger and he already has something. If I understood him right, he goes for 1. based on Bernd's patch and workarounds the accessing file paths problem by checking and ignoring the symlink directory. Be careful that this only works on very current kernels as those symlink directories for dual cores seem to be introduced very recently. We should also check whether all cpufreq drivers (speedstep-centrino, powernow-k8 and acpi-cpufreq) are behaving in the same way. Thanks a lot Bernd and Holger for finding and fixing this, Thomas

1 0

Re: [suse-amd64] Current Asus Support
by Ciro Iriarte 13 Nov '05

13 Nov '05

2005/11/13, Ciro Iriarte <cyruspy(a)gmail.com>: > > How big a power supply? > > 400W or greater? > Looking for a decent 600w PSU (have 2 in mind) > > > > > AMD Athlon 64 3500+ > > > 2GB Corsair RAM > > > > PC3200? > yep > > Dual channel? > not sure > > My 2G RAM on that mb only works at PC3000 in dual channel mode (it is > > PC3200 and works that way if only 1G is installed). > > I'm not sure it is the mb or CPU but my CPU is supposed to handle it and > > there are other cases on the ASUS website (but no solutions yet and > > nothing from ASUS). > > > Any issues with the onboard raid controller?, data corruption? > > CI.- > Sorry for the direct reply....

3 2

Problems with Anjuta 1.2.3
by Detlef Grittner 13 Nov '05

13 Nov '05

I've tried Anjuta 1.2.3 on a Suse x86_64 installation, but the editor isn't working. It overlaps lines and positions them incorrectly during scrolling. Now I've downloaded Anjuta 1.2.4 as source code, built it as 64 bit application, and the editor is working correcly in this version. Has anyone an idea what is wrong with the 1.2.3 version of Suse? Detlef

1 0

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