November 2005 - openSUSE AMD64 - openSUSE Mailing Lists

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