November 2005 - openSUSE AMD64 - openSUSE Mailing Lists

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

09 Nov '05

On Wednesday 09 November 2005 03:21, you wrote: > Hi, > > I read your post on the suse-mailinglist and have the same problem. > Do you have a solution by now? > > I checked everything from dependencies to versionnummers and reinstalled > the whole mono/sharp-package outgoing from monodevelops dependencies - > nothing worked. > > Hope you had more luck :) > > regards, > Michael No luck for me either.......... Anyone else? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Firefox-1.5rc1 64bit
by James Lockie 07 Nov '05

07 Nov '05

http://benjamin.smedbergs.us/blog/2005-10-27/gcc-40-workaround/ The workaround works for Firefox. Thunderbird runs but I can't share the profile with Windows so it is a show stopper for me.

1 0

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

07 Nov '05

Hi, I'm also having a few problems with NFS on SuSE 10. I am trying to mount resources from a SLES 9 machine, presumably set up for nfsvers 3??? Each boot time, I get the error message that the "server reports TCP unavailable, resorting to UDP". I also occasionally see error messages to the effect of "server reports nfsvers 4 not available, switching to version 3". All in all, it means that each time I reboot my SuSE 10 machine, I have to log in as root and issue the command: mount -vat nfs, and more often than not this will pick up the nfs drives that aren't being mounted at boot time. FYI, here's the lines from /etc/fstab: 163.1.82.28:/home /home nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home1 /home1 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home2 /home2 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 What are the implications of using UDP and nfsvers=2 on security/performance etc.???? Anyone know what's going on? I have another AMD64 machine (SuSE 9.3), which has exactly the same problem. Best wishes, Jon. Roger Oberholtzer wrote: > On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote: >> I have an Apple OS X 10.4.3 that was successfully connected to Suse >> Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple >> cannot find the Linux server. It can successfully ping the Linux IP >> address. What settings do I need when starting the Linux NFS >> services? There must be some differences between 9.2 and 10.0 that >> I'm missing. > > Probably the same thing I went through with OS-9 (Microware, not Apple) > connectivity. The 2.6 kernel (where NFS now lives) uses a newer version > of NFS by default. It also uses udp instead of tcp. > > Can you mount an export from OS/X on SUSE 10.0? > > When mounting on SUSE 10.0, I needed to add this to the fstab options: > > udp,nfsvers=2 > > I do not know how you specify this when exporting. Or even if you can. > But maybe this will get you started in the right direction. > > Hope this helps. > -- 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

1 0

Shockwave flash + Suse 10.0
by Dimitar Georgiev Popov 06 Nov '05

06 Nov '05

Hi, I upgraded my 9.3 to 10.0 and now konqueror does not play shockwave flash files. Konqueror plug-in scan does not find the shockwave flash plug-in, though libflashplayer.so exists in the directories it search. How can resolve this problem? Mitko

1 0

Re: [SLE] Gnome disappointment
by Jonathan Brooks 06 Nov '05

06 Nov '05

Andre Truter wrote: > On 11/6/05, Jonathan Brooks <jonathan.brooks(a)human-anatomy.oxford.ac.uk> wrote: > >>Financial suicide. Please see my earlier posts about gnome and SuSE >>x86_64, basically it doesn't work. There are bugs in it which mean that >>gnome hogs 100% CPU - this has been reported, has been known about for >>months, and yet nothing happens. As soon as I switched to KDE I could >>use my machine. >> > > > Hmm. Interesting. I have been running SUSE with GNOME desktop on two > x86_64 boxes since version 9.3 and my GNOME is not hogging my system. > > Mono do that from time to time, but I disable Beagle (mono does the > same thing on 32-bit machines too). This is a problem with Beagle, > not GNOME. If you used Beagle under KDE, or Xfce, or FWVM, then you > would end up with the same problem. > > >>Now personally I like the clean interface of Gnome, but it seems like a >>lot more time and effort is put into making KDE stable (if a bit slow). >> > > This being true, do you really think they will discontinue KDE and > commit "financial suicide" > > >>Hopefully there will be a U-turn soon, or I will be dropping SuSE from >>all our machines. >> > > > What do you mean with a U-Turn? Do you mean they should focus more on > getting GNOME better supported? (I would like that) > > -- > Andre Truter | Software Engineer | Registered Linux user #185282 > ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.za.org > > ~ A dinosaur is a salamander designed to Mil Spec ~ > SuSE 10 (Gnome 2.12) and gam_server was the one causing all the problems. Cheers, Jon -- Jonathan Brooks (Ph.D.) Research Fellow PaIN Group, Department of Human Anatomy & Genetics University of Oxford, South Parks Road, Oxford, OX1 3QX tel: 01865 282654 fax: 01865 282656

1 0

ATI fglrx rev. 8.18.8 problem with SuSE 10.0
by Bernd Paysan 06 Nov '05

06 Nov '05

Hi, Just in case someone struggles with the same problem: The ATI proprietary driver won't be able to load its module on top of the kernel that comes with SuSE 10.0. The problem is a conflict between the kernel-embedded DRM, and the ATI DRM. You'll see an error message like that in your /var/log/messages: ... kernel: Trying to register duplicated ioctl32 handler c0246400 ... kernel: [fglrx:firegl_init_32compat_ioctls] *ERROR* unable to register ioctl32 0 ... kernel: [fglrx:firegl_init] *ERROR* Couldn't register compat32 ioctls! The problem goes away if you recompile the kernel with DRM disabled. The easiest way to get there is to simply do the following: cd /usr/src/linux zgrep -v DRM /prog/config.gz >.config make make install -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/

1 0

Re: [suse-amd64] (OT) 64-bit linux
by patheve2 05 Nov '05

05 Nov '05

Hello Mike My answers : 1/ SuSE 9.0 (still used), SuSE 9.1 (no more use) and SuSE 9.2 (upgrade of 9.1). Before I prefered SuSE 9.0 (kernel 2.4.21 AMD64), now I use the SuSE 9.2 AMD64. Both SuSE are installed on an Asus L5D laptop. 2/ In the package 9.2 : books, 2 DVD (64 and 32 bits) and 5 CD (32 bits). Idem for 9.1. For 9.0, only DVD (64 bits) provided by Transtec AG. 3/ I have beenn running a 64 bits system (this laptop) since July 15th 2004. For my own use. At work, since May/June 2004. I think the SuSE AMD64 is the best one among Fedora Core and Mandrake. No problem for 32 and 64 bits on a SuSE AMD64. Kind regards Pascal ==================================================================== Hello everyone: I'm currently working on a presentation and need your help. Is there anyone running a Linux distribution in 64-bit mode on an AMD 64 machine. Now, I already know about SuSE - what I'm looking for is other, non-SuSE Linux distributions. So, if you're actually running such a system, could you please tell me: 1) which distribution (name and version number e.g.: SuSE v10.0 / 64-bit), and 2) if purchased, what's in the package (e.g.: SuSE 5 CDs, 1 dual-layer DVD [32 & 64 bit] plus a paper manual), and 3) how long you've been running a 64-bit system. You may reply directly to me but, please don't guess. If you've 'only heard' that such a distribution is 64-bit, don't reply. If you're running such a system (other than SuSE), then I'd like to hear from you. Thanks for your help. Cheers, Mike

1 0

resmgr problem with /dev/mixer
by Sid Boyce 05 Nov '05

05 Nov '05

I'm seeing this problem on x86_64 SuSE 10.0, SuSE 10.0 x86 is OK and on Mandriva 2006 x86 where one box is OK and the other isn't, When the x86_64 box is booted, sound modules are not loaded, I have to do "rcalsasound restart" as root and change ownership of /dev/mixer from root.audio to <user>.audio. I have put a line in /etc/resmgr.conf add /dev/mixer desktop noacl With that line I still have the problem. On the Mandriva box the sound modules start, but I have to alter the ownership of /dev/mixer. In both cases sound works, but there is no mixer until I change the ownerships of /dev/mixer. /dev/snd/* all have root.audio ownerships and I leave them that way. Just a heads up in case anyone else is seeing this and I shall submit a bug to SuSE and Mandriva (resmgr not used). Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks

1 0

(OT) 64-bit Linux - THANKS
by Mike Roy 03 Nov '05

03 Nov '05

Hello everyone: Just a short note to say thank you to all of you who responded to my earlier request about 64-bit machines and Linux. I didn't realize just how many flavors of Linux are running on AMD 64 machines, it was an eye-opener. Again, many thanks. Cheers, Mike

1 0

(OT) 64-bit linux
by Mike Roy 03 Nov '05

03 Nov '05

Hello everyone: I'm currently working on a presentation and need your help. Is there anyone running a Linux distribution in 64-bit mode on an AMD 64 machine. Now, I already know about SuSE - what I'm looking for is other, non-SuSE Linux distributions. So, if you're actually running such a system, could you please tell me: 1) which distribution (name and version number e.g.: SuSE v10.0 / 64-bit), and 2) if purchased, what's in the package (e.g.: SuSE 5 CDs, 1 dual-layer DVD [32 & 64 bit] plus a paper manual), and 3) how long you've been running a 64-bit system. You may reply directly to me but, please don't guess. If you've 'only heard' that such a distribution is 64-bit, don't reply. If you're running such a system (other than SuSE), then I'd like to hear from you. Thanks for your help. Cheers, Mike

1 0

Re: [suse-amd64] Problem with bind
by Constantine 'Gus' Fantanas 02 Nov '05

02 Nov '05

Markus Koßmann wrote: > Am Dienstag, 1. November 2005 07:35 schrieben Sie: > [...] > >> -------------------------------------------SNIP---------------------------- >> ----- presario:/usr/src/linux # rcnamed start >> Starting name server BIND named: capset failed: Operation not permitted: >> please ensure that the capset kernel module is loaded. see insmod(8) >> startproc: exit status of parent of /usr/sbin/named: 1 >> >> > Is the module capability.ko loaded ? If not; does loading the module solve > the problem ? > > I made sure it was loaded with 'modprobe capability', but named still crashed. 'lsmod' showed that 'capabilily' was used 0 times. I have the latest version of bind from the apt-get repositories. Before that, I downgraded to the version on my 9.3 DVD and got the same results (crash, same error message). So, I begin to suspect the problem is with the '/etc/sysconfig/named' configuration script.

2 4

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

02 Nov '05

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

4 3

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

02 Nov '05

> >>> Ok, so I tried to play around with that a little bit. With memory > >>> remapping, /proc/mtrr looks like that: > >> reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1 > >> reg01: base=0x100000000 (4096MB), size= 512MB: write-back, count=1 > >> reg02: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1 > >> reg03: base=0xe0000000 (3584MB), size= 128MB: write-combining, > >> count=1 > > > > This doesn't work. If your BIOS is doing this (as opposed to > > you mucking with the settings), I need to get the AMD BIOS > > developers to talk to your BIOS developers. > > sorry for warming up such an old thread :-) I just tested the > latest beta > bios for the Asus A8V Deluxe (1015.002 from Oct 19th) to check if they > had added sth. about discrete/continuous MTRRs. Unfortunately they > still haven't. What's changed is the amount of memory > available without > remapping the memory hole: At least 3.8 of the 4GB are available, in > contrats to 3.5 and 3.3 with earlier bios versions. > > However, with "hardware memory hole" enabled in the bios, all the 4 GB > are available for linux, but things like fglrx still can't load and > the /proc/mtrr looks like this: > > cantor:~ # cat /proc/mtrr > reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1 > reg01: base=0x100000000 (4096MB), size= 256MB: write-back, count=1 > reg02: base=0xf0000000 (3840MB), size= 256MB: uncachable, count=1 > reg03: base=0xf0000000 (3840MB), size= 128MB: write-combining, count=1 > > Do you see a chance to get the AMD bios guys make the ASUS people do > *some* real work at last? ;-)) They do real work all the time. They just sometimes don't do it right. I will go have another discussion about why making the video aperture uncachable is not the same thing as leaving it unassigned. -Mark Langsdorf AMD, Inc.

2 1

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

02 Nov '05

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

2 3

Mono problem in SuSE 10.0
by Karaoulis Marios 01 Nov '05

01 Nov '05

Every time i try to start beagle daemon this occurs marios@base-06:~> beagled INFO: Starting Beagle Daemon (version 0.1.1) DEBUG: Command Line: /usr/lib64/beagle/BeagleDaemon.exe --fg DEBUG: Starting main loop DEBUG: Starting messaging server ** (beagled:31504): WARNING **: The following assembly referenced from /usr/lib/mono/gac/gmime-sharp/2.0.0.0__677013d4cb5910f0/gmime-sharp.dll could not be loaded: Assembly: glib-sharp (assemblyref_index=1) Version: 2.0.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/gac/gmime-sharp/2.0.0.0__677013d4cb5910f0). ** (beagled:31504): WARNING **: The class GLib.Object could not be loaded, used in /usr/lib/mono/gac/gmime-sharp/2.0.0.0__677013d4cb5910f0/gmime-sharp.dll (token 0x0100000a) ** ERROR **: file class.c: line 2119 (mono_class_setup_parent): should not be reached aborting... Aborted The same with monodevelop3 marios@base-06:~> monodevelop ** (./MonoDevelop.exe:31824): WARNING **: The following assembly referenced from /usr/lib/monodevelop/bin/MonoDevelop.exe could not be loaded: Assembly: gnome-sharp (assemblyref_index=4) Version: 2.0.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/monodevelop/bin/). ** (./MonoDevelop.exe:31824): WARNING **: Missing method get_UI in assembly /usr/lib/monodevelop/bin/MonoDevelop.exe, type Gnome.Modules Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object only monodoc runs What's wrong? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Problem with bind
by Constantine 'Gus' Fantanas 01 Nov '05

01 Nov '05

Hi all. The package 'bind' (which is the DNS server) was working fine under 9.3. After upgrading to 10.0, without changing any configuration files, 'bind' craches on startup. Here is what I see: -------------------------------------------SNIP--------------------------------- presario:/usr/src/linux # rcnamed start Starting name server BIND named: capset failed: Operation not permitted: please ensure that the capset kernel module is loaded. see insmod(8) startproc: exit status of parent of /usr/sbin/named: 1 failed -----------------------SNIP--------------------------------------------- Any ideas? TIA CF

1 0