November 2005 - openSUSE AMD64 - openSUSE Mailing Lists

Eclipse 3.1 startup error
by Philippe Andersson 22 Nov '05

22 Nov '05

Hello again, Just installed Eclipse 3.1 (eclipse-3.1-0.7) from the SLES9 SDK SP2 site kindly suggested to me earlier today. Unfortunately, eclipse dies just after displaying the splash screen, and the following error message is found in the log: -------------------------<cut>-------------------------- java.lang.NoSuchMethodError: org.eclipse.swt.internal.gtk.OS.GTypeInfo_sizeof()I at org.eclipse.swt.internal.gtk.GTypeInfo.<clinit>(GTypeInfo.java:26) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:777) at org.eclipse.swt.widgets.Display.create(Display.java:746) at org.eclipse.swt.graphics.Device.<init>(Device.java:141) at org.eclipse.swt.widgets.Display.<init>(Display.java:429) at org.eclipse.swt.widgets.Display.<init>(Display.java:420) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:394) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155) at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:128) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:79) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) -------------------------<cut>-------------------------- Anyone seen this ? TIA Cheers. Bye. Ph. A. -- ----------- | IBA | /*-----------------------------------------------------------------*/ /* Ion Beam Applications, S.A.| Philippe Andersson */ /* Av. Albert Einstein, 4, | Unix Admin. Control Team */ /* B-1348 Louvain-la-Neuve | pan(a)iba.be */ /* BELGIUM | +32-10-475.983 Fax: +32-10-475.837 */ /*-----------------------------------------------------------------*/

2 1

Extra packages for SLES9: where ?
by Philippe Andersson 22 Nov '05

22 Nov '05

Hello list, Something really bothers me: there seems to be so few packages provided with SLES9 (as compared with SuSE Linux 9.3 Pro, for instance). Where can I get extra RPM packages for SLES9 x86_64 (subversion comes to mind) ? TIA Cheers. Bye. Ph. A. -- ----------- | IBA | /*-----------------------------------------------------------------*/ /* Ion Beam Applications, S.A.| Philippe Andersson */ /* Av. Albert Einstein, 4, | Unix Admin. Control Team */ /* B-1348 Louvain-la-Neuve | pan(a)iba.be */ /* BELGIUM | +32-10-475.983 Fax: +32-10-475.837 */ /*-----------------------------------------------------------------*/

2 1

e1000_watchdog_task: NIC Link is Up 10 Mbps Full Duplex
by Ken Siersma 21 Nov '05

21 Nov '05

I've installed SUSE 10.0 (OSS) on a dual opteron 250, 4 GB RAM, with a Tyan S2875 K8W Tiger motherboard. The onboard NIC is Intel Gigabit Ethernet. My kernel is 2.6.13-15-smp, and I have the e1000 module loaded without any options. When my network comes up, I see in my logs: Nov 14 10:09:42 lincoln kernel: eth0: no IPv6 routers present Nov 14 10:09:50 lincoln kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 10 Mbps Full Duplex The network is obviously pretty slow with this setup. I've tried forcing the interface to 100BaseT full duplex (that's what my switch supports) by placing this in my /etc/modprobe.conf.local file: options e1000 Duplex=2 Speed=100 The interface appears to come up in the logs I see: Nov 14 10:22:29 lincoln kernel: Intel(R) PRO/1000 Network Driver - version 6.0.60-k2-NAPI Nov 14 10:22:29 lincoln kernel: Copyright (c) 1999-2005 Intel Corporation. Nov 14 10:22:29 lincoln kernel: e1000: 0000:02:03.0: e1000_check_copper_options: Forcing to 100 Mbps Full Duplex Nov 14 10:22:29 lincoln kernel: e1000: 0000:02:03.0: e1000_check_copper_options: Speed, AutoNeg and MDI-X specifications are incompatible. Setting MDI-X to a compatible value. Nov 14 10:22:29 lincoln kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection But, I can't access the network - i.e., ping by ipaddr gets me 'Destination Host Unreachable' Can anyone offer advice? Thanks, Ken -- Ken Siersma, Software Engineer EKK, Inc. phone: (248) 624-9957 fax: (248) 624-7158 http://www.ekkinc.com -- "Our lives begin to end the day we become silent about things that matter." -MLK Jr.

5 17

RE: [suse-amd64] what frequency should my CPU run at?
by Langsdorf, Mark 20 Nov '05

20 Nov '05

> 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. You're welcome. > So I did a bit of digging and found that cat /proc/cpuinfo gives: ... > 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? The SUSE SL10.0 kernel doesn't have any problems with CPU frequency scaling. The reported speed of 1 GHz that you're seeing is a feature provided by AMD: when your processor isn't doing anything, it reduces its frequency and voltage in order to dramatically reduce the amount of power it needs to run. If your system were actually running a significant load, the frequency would go up. You can check the current frequency with the following command: cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq If you want to know more about how to influence the frequency of your system, try man powersave I hope this helps. -Mark Langsdorf AMD, Inc.

3 2

Re: [suse-amd64] USB support in SuSE 10.0
by Constantine 'Gus' Fantanas 19 Nov '05

19 Nov '05

I would like to thank everybody who responded to my plea for help. I did a lot of research during the past 48 hours or so and was able to correct *SOME* of my problems with USB. Below I am summarizing my findings for the benefits of all. Upon close scrutiny, it seems that the syntax for '/etc/udev/rules.d/*.rules' files has changed a bit from SuSE 9.3 to SuSE 10.0. (These files enable the new hotplugging system udev to assign persistent names to peripherals which may be hotplugged in random order. For example, if you have two different USB storage devices, with the proper set of rules you can make them show up each with the same mountable partition, regardless of the order they are plugged in.) These changes are *not* documented in the SuSE 10.0 manual. Look, for example, at the bottom of page 492 of the SuSE 10.0 manual (available for download at http://www.novell.com/documentation/suse10/pdfdoc/suse10_ref/suse10_ref.pdf) and p. 349 of the printed SuSE 9.3 manual. You will observe that comparing for BUS keys now (in SuSE 10.0) requires a double equals sign, while in 9.3 a single equals sign worked. After changing the pertinent device rules to conform to the SuSE 10.0 syntax (and multiple reboots) yesterday, my cellphone and 512MB USB stick (which, by the way, carries an encrypted file system) began to work. I plugged and unplugged them hot several times in different order and the USB bus did not lock up. The cellphone looks like a USB dialup modem again, as it should (albeit a lot faster than a "real" one connected to a landline), pppd handles it as such just fine --as it should-- and the same peer, secrets, and chat files work, so I can surf wirelessly through it again. The USB compact flash card reader still does not show up as a partition, but it does no longer seem to lock up the USB bus (two days ago, the USB bus locked up and recognized no hot(un)plug events). I am not exactly certain what got most USB peripherals working again and why the whole USB system locked up two days ago, but so far it seems that correcting the syntax of udev rules has helped prevent USB bus lockups. During boot, I still get udev-related warntings/errors about missing brackets, so it seems I need to go through all the udev rules, which I inherited when I upgraded from 9.3, with a fine tooth comb. Again, I would like to thank everybody for their help and I hope that these postings will prevent others from having the problems with USB I just had. CF

1 0

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