February 2004 - openSUSE AMD64 - openSUSE Mailing Lists

limits.conf file
by Bedard, Joe 28 Feb '04

28 Feb '04

Greetings: I am attempting to set my hard nofile limit to 16384 and SLES 8 (AMD64) won't let me. With the limits.conf file set with the below settings, only the root user can login via ssh. I have set this parameter under the x86 SLES 8 successfully. With the 'hard nofile' line set to > 1024, I get the following error. sshd[1480]: Accepted password for oracle from ::ffff:10.40.10.92 port 2165 ssh2 fatal: PAM session setup failed[6]: Permission denied Here is what I have. SLES 8 AMD64 with 2.4.21-199-smp /etc/security/limits.conf * soft nofile 2047 * hard nofile 16384 * soft nproc 2048 * hard nproc 16384 Tail end of /etc/profile if [ $USER = "oracle" ]; then ulimit -u 16384 ulimit -n 16384 fi If I comment out the 'hard nofile' line or set it to 1024, all non root users can login. If set it to 1025, error. Any ideas? Thanks Joe Bedard

2 1

stuck in first gear
by Jonathan Breeze 27 Feb '04

27 Feb '04

I have installed SuSe 9.0 x86_64 on a laptop with AMD64 3200+ cpu. The machine is based on a Mitac motherboard (Radeon 9600 etc.). Installation was fine, but when I did 'cat /proc/cpuinfo' it only registered a speed of 800MHz. Oh dear! Where's the rest of the speed? Running an intensive application quickly confirmed my fears, no increase in speed at all. In Windows XP the speed increased according to the load (as did the the noise from the fan). But I don't want to work in Windows ... I tried 'rccpufreqd start' but the daemon wouldn't start ... 'starting cpufreqd skipped' . grep cpugreqd /var/log/messages revealed 'CPU frequency scaling not supported with current settings! Is this machine supporting speedstep or powernow technology? Please have a look in /etc/sysconfig/powermanagement'. So I tried setting CPUFREQD_MODULE to "powernow-k8". rccpufreqd start resulted in 'failed' ... grep -> "CPU frequency scaling not supported". I checked the kernel configuration which says that frequency scaling is supported as a loadable module. I checked for the module and there it is at /lib/ A quick check using insmod revealed that the powernow-k8.o module woud not load into the kernel. Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg a look with dmesg revealed something interesting; amd64-cpuf: version 1.00.06 - August 13, 2003 amd64-cpuf: Found AMD Athlon 64 / Opteron processor supporting p-state transitions amd64-cpuf: voltage stabilization time: 5 (units 20us) amd64-cpuf: p states on battery: 0 - all available amd64-cpuf: ramp voltage offset: 2 amd64-cpuf: isochronous relief time: 0 amd64-cpuf: maximum voltage step: 0 - 0x1 amd64-cpuf: BIOS error - numpst must be 1 numpst : number of p state is wrong ... a problem with the BIOS it would seem. The BIOS is Insyde Software MobilPro Revision 4.00.05 BIOS version 1.02 . I've reached as far as my meager knowledge will take me. Is there anything I can do to get my computer into top gear ?? -- Jonathan Breeze Research Fellow Centre for Physical Electronics and Materials London South Bank University 103 Borough Road London SE1 0AA Tel: +44(0)20 7815 7582 Fax: +44(0)20 7815 7599

3 2

RE: [suse-amd64] S-ATA trouble. Can't boot installed system
by larry_prikockis＠natureserve.org 27 Feb '04

27 Feb '04

I had exactly the same problem... It seems the normal install routine doesn't quite create a working initrd. I needed to boot from the patch CD, load the sata drivers, then use that to boot from my /dev/sda2 partition. After that, I was able to edit /etc/sysconfig/kernel to contain the SATA_VIA line (it HAD 'ATA_VIA' - a typo?) and create a proper initrd. Since I've done that, everything has worked beautifully using the 2.4 kernel. -----Original Message----- From: Stefan Fent [mailto:sf@suse.de] Sent: Friday, February 27, 2004 5:09 AM To: depot(a)xs4all.nl Cc: suse-amd64(a)suse.com Subject: Re: [suse-amd64] S-ATA trouble. Can't boot installed system * depot(a)xs4all.nl <depot(a)xs4all.nl> [040226 18:35]: > Today I spent several hours installing 9.0 for AMD 64 through FTP > using the Suse 9.0 patch-boot cd. Not an easy task compared to > previous Suse FTP installations I did. Anyway now for the question I have. > > My fresh installed systeem hangs at boot. Kernel panic because the > root partition SDA5 cannot be mounted. I have a serial ata drive with > ext3 hooked on a Via controller on a MSI KT8 NEO board. > > I think the problem relates to to the possible absence of the sata_via > module/driver during boot. Besides sata_via you need libata, sd_mod and scsi_mod in your initrd. > > Can somebody confirm that initrd needs to contain the sata_via module? > How does a 'working' INITRD_MODULES variable in /etc/sysconfig/kernel > look? > here is mine: INITRD_MODULES="ext3 sata_via scsi_mod sd_mod libata" (But this should have been done during installation of the package) All of them are required to access the root filesystem which contains the (other) modules > Using the Suse 9.0 patch-boot cd I managed to boot the system. > > I tried to make a new initrd with the mkinitrd script. The response > was that the dependencies of sata_via couldn't be determined, "maybe > modules.dep is out of date". > Running depmod -a didn't help me: > "/lib/modules/2.4.20-4GB-athlon/modules.dep could'nt be opened for ^^^^^^^^^^^^^^^^^ > writing". I don't know why. Filesystem is mounted rw. This is certainly from a 32bit kernel, and rather old as well. What exactly are you doing? > > Please help. I am stuck. > > Regards, > Jeroen > Amsterdam > > > -- > Check the List-Unsubscribe header to unsubscribe For additional > commands, email: suse-amd64-help(a)suse.com > -- Stefan Fent SuSE Linux AG, Maxfeldstr. 5, D-90409 Nuernberg -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

1 0

vmware on suse9/amd64
by detlef oertel 27 Feb '04

27 Feb '04

Hello list, I tried to install my vmware 4 on my suse 9.0/amd64 system. After installing I fail to configure vmware. The error message is: "The kernel defined by this directory of header files does not have the same address space size as your running kernel." The output is like this: -------------------------------- sepia:~ # vmware-config.pl Making sure VMware Workstation's services are stopped. Stopping VMware services: Virtual machine monitor done Trying to find a suitable vmmon module for your running kernel. None of VMware Workstation's pre-built vmmon modules is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] The kernel defined by this directory of header files does not have the same address space size as your running kernel. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] -------------------------------------------- Any experience, any suggestions ? thanks a lot..... detlef

6 11

S-ATA trouble. Can't boot installed system
by depot＠xs4all.nl 27 Feb '04

27 Feb '04

Today I spent several hours installing 9.0 for AMD 64 through FTP using the Suse 9.0 patch-boot cd. Not an easy task compared to previous Suse FTP installations I did. Anyway now for the question I have. My fresh installed systeem hangs at boot. Kernel panic because the root partition SDA5 cannot be mounted. I have a serial ata drive with ext3 hooked on a Via controller on a MSI KT8 NEO board. I think the problem relates to to the possible absence of the sata_via module/driver during boot. Can somebody confirm that initrd needs to contain the sata_via module? How does a 'working' INITRD_MODULES variable in /etc/sysconfig/kernel look? Using the Suse 9.0 patch-boot cd I managed to boot the system. I tried to make a new initrd with the mkinitrd script. The response was that the dependencies of sata_via couldn't be determined, "maybe modules.dep is out of date". Running depmod -a didn't help me: "/lib/modules/2.4.20-4GB-athlon/modules.dep could'nt be opened for writing". I don't know why. Filesystem is mounted rw. Please help. I am stuck. Regards, Jeroen Amsterdam

3 2

VMware can't access fd0 and sr0; please help
by M. Ranjit Mathews 27 Feb '04

27 Feb '04

I'm running SUSE 9.0 for AMD64: # uname -a Linux linux 2.4.21-201-smp #1 SMP Wed Feb 18 19:17:53 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux I installed VMware 4.5 & configured it with vmware-config.pl: # rpm -qa | fgrep -i vmware VMwareWorkstation-4.5.0-7174 I went to the dev directory and linked sr0 to cdrom # ls -l cdrom lrwxrwxrwx 1 root root 3 Feb 26 02:08 cdrom -> sr0 I have no trouble accessing fd0 and cdrom from a command line with media in them: # dd if=/dev/fd0 of=/dev/null count=1 1+0 records in 1+0 records out # dd if=/dev/cdrom of=/dev/null count=1 1+0 records in 1+0 records out When I start the virtual machine, it says fd0 doesn't seem to be a floppy drive and that I can start the virtual machine without a floopy drive. When the boot proceeds gets to the cdrom, an oops message from the kernel appears and to get things back to normal, I have to restart the host system (dual Opteron 240) If I remove fd0 and cdrom from the virtual machine definition, the boot sequence makes it to a PXE boot; there's no more Oops. QUESTION: How can I give the virtual machine access to a floppy drive and CDROM (I have an NEC BD2500 DVD-RW/ CD-RW)?

2 3

All plugins fail in Mozilla
by Emile van Mierlo 26 Feb '04

26 Feb '04

Hello list, I don't know if this is related to the 64bit platform, but I fail to install any plugin in mozilla 1.4 x86_64. I tried Java, Acroread, RealPlayer. When I start mozilla after any symbolic link is in place, this message shows: LoadPlugin: failed to initialize shared library libXt.so [libXt.so: cannot open shared object file: No such file or directory] LoadPlugin: failed to initialize shared library /usr/X11R6/lib/libXt.so.6 [/usr/X11R6/lib/libXt.so.6: cannot open shared object file: No such file or directory] libXt.so is not on present on my system, libXt.so.6 is there where mozilla looks for it (as a symlink to libXt.so.6.1) Does somebody know what goes wrong? Do I need to install libXt.so? Where does it belong? Why can libXt.so.6 not be found? Thanks. Emile van Mierlo System: Tyan Tiger K8W (s2875), Dual Opteron 244, 2 x 1GB Kinston PC2700 registered RAM Adaptec 29160 SCSI, 2 x Maxtor Atlas 10k4 SCSI Nvidia FX5900 Graphics (Asus V9950SE), Plextor PX-708A CD/DVD Suse 9.0 kernel 2.4.21-201-smp, Nvidia 1.0-5336 driver

10 17

IGMP on suse-amd64
by Karsten Künne 26 Feb '04

26 Feb '04

Hi, we have some serious trouble to get multicast networking to work on our AMD Opteron machines. The problem seems to be that for some reason the amd64 machines are sending IGMP V3 messages with a wrong checksum whereas our Intel boxes are sending IGMP V2 messages. Following is a packet dump from one of our Opteron boxes as we start xntpd in multicast mode (IP addresses changed to protect the innocent): "uname -a" output: Linux monster540 2.4.21-201-smp #1 SMP Wed Feb 18 19:17:53 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux "tethereal -V igmp" output: Capturing on eth0 Frame 1 (54 bytes on wire, 54 bytes captured) Arrival Time: Feb 25, 2004 14:40:01.975282000 Time delta from previous packet: 0.000000000 seconds Time relative to first packet: 0.000000000 seconds Frame Number: 1 Packet Length: 54 bytes Capture Length: 54 bytes Ethernet II, Src: 00:09:3d:00:09:fe, Dst: 01:00:5e:00:00:16 Destination: 01:00:5e:00:00:16 (01:00:5e:00:00:16) Source: 00:09:3d:00:09:fe (00:09:3d:00:09:fe) Type: IP (0x0800) Internet Protocol, Src Addr: some.ip.add.ress (some.ip.add.ress), Dst Addr: 224.0.0.22 (224.0.0.22) Version: 4 Header length: 24 bytes Differentiated Services Field: 0xc0 (DSCP 0x30: Class Selector 6; ECN: 0x00) 1100 00.. = Differentiated Services Codepoint: Class Selector 6 (0x30) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 40 Identification: 0xa360 (41824) Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 1 Protocol: IGMP (0x02) Header checksum: 0x1ff5 (correct) Source: some.ip.add.ress (some.ip.add.ress) Destination: 224.0.0.22 (224.0.0.22) Options: (4 bytes) Router Alert: Every router examines packet Internet Group Management Protocol IGMP Version: 3 Type: Membership Report (0x22) Header checksum: 0xf9fe (incorrect, should be 0xf8fc) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this looks suspicious Num Group Records: 1 Group Record : 224.0.1.1 Change To Exclude Mode Record Type: Change To Exclude Mode (4) Aux Data Len: 0 Num Src: 0 Multicast Address: 224.0.1.1 (224.0.1.1) If I do the same thing on a i686 machine it looks like this: "uname -a": Linux greyhound 2.4.21-192-default #1 Wed Feb 18 19:26:28 UTC 2004 i686 i686 i386 GNU/Linux "tethereal -V igmp": Frame 2 (46 bytes on wire, 46 bytes captured) Arrival Time: Feb 25, 2004 14:41:16.268523000 Time delta from previous packet: 1.944834000 seconds Time relative to first packet: 1.944834000 seconds Frame Number: 2 Packet Length: 46 bytes Capture Length: 46 bytes Ethernet II, Src: 00:06:5b:76:d0:03, Dst: 01:00:5e:00:01:01 Destination: 01:00:5e:00:01:01 (01:00:5e:00:01:01) Source: 00:06:5b:76:d0:03 (00:06:5b:76:d0:03) Type: IP (0x0800) Internet Protocol, Src Addr: some.other.ip.addr (some.other.ip.addr), Dst Addr: 224.0.1.1 (224.0.1.1) Version: 4 Header length: 24 bytes Differentiated Services Field: 0xc0 (DSCP 0x30: Class Selector 6; ECN: 0x00) 1100 00.. = Differentiated Services Codepoint: Class Selector 6 (0x30) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 32 Identification: 0x0bfd (3069) Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 1 Protocol: IGMP (0x02) Header checksum: 0xc6c3 (correct) Source: some.other.ip.addr (some.other.ip.addr) Destination: 224.0.1.1 (224.0.1.1) Options: (4 bytes) Router Alert: Every router examines packet Internet Group Management Protocol IGMP Version: 2 Type: Membership Report (0x16) Max Response Time: 0.0 sec (0x00) Header checksum: 0x08fe (correct) Multicast Address: 224.0.1.1 (224.0.1.1) Does anybody know why these two platforms behave differently and why the x86_64 machines uses IGMP V3 and not V2? Karsten.

3 5

Problems running 32bit programs
by Willibald Krenn 26 Feb '04

26 Feb '04

Hi! Yesterday I successfully installed SuSE 9.0 on my Athlon64 system (Shuttle AN50R). Today I wanted to install and run the Borland Kylix 3 RAD IDE. The install process went fine, however when running the Delphi IDE / the Delphi command line compiler I always get following errors in my messages log: Jan 9 18:53:18 linux kernel: delphi[5238] general protection rip:5699028a rsp:ffffd084 error:2004 Jan 9 18:42:52 linux kernel: dcc[5146]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000000000000000 error 14 As I know that this software runs fine on SuSE 9.0 non AMD64 (even when using the 2.6.x kernel) I can not quite understand why it fails on the AMD64 version when other 32bit programs are running fine.. JFYI: Till now it seems that even programs produced by Kylix will fail to run on SuSE 9.0 AMD64. Any ideas how to solve this issue? Thanks, Willibald Krenn

5 20

VMware can't access fd0 and sr0
by M. Ranjit Mathews 26 Feb '04

26 Feb '04

I'm running SUSE 9.0 for AMD64: # uname -a Linux linux 2.4.21-201-smp #1 SMP Wed Feb 18 19:17:53 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux I installed VMware 4.5 & configured it with vmware-config.pl: # rpm -qa | fgrep -i vmware VMwareWorkstation-4.5.0-7174 I went to the dev directory and linked sr0 to cdrom # ls -l cdrom lrwxrwxrwx 1 root root 3 Feb 26 02:08 cdrom -> sr0 I have no trouble accessing fd0 and cdrom from a command line with media in them: # dd if=/dev/fd0 of=/dev/null count=1 1+0 records in 1+0 records out # dd if=/dev/cdrom of=/dev/null count=1 1+0 records in 1+0 records out When I start the virtual machine, it says fd0 doesn't seem to be a floppy drive and that I can start the virtual machine without a floopy drive. When the boot proceeds gets to the cdrom, an oops message from the kernel appears and to get things back to normal, I have to restart the host system (dual Opteron 240) If I remove the cdrom from the virtual machine definition, the boot sequence makes it to a PXE boot; there's no more Oops. QUESTION: How can I give the virtual machine access to a floppy drive and CDROM (I have an NEC BD2500 DVD-RW/ CD-RW)?

1 0