February 2004 - openSUSE AMD64 - openSUSE Mailing Lists

Playing DVDs on AMD64 system
by larry_prikockis＠natureserve.org 24 Feb '05

24 Feb '05

Has anyone managed to get any DVD playing software running properly under SuSE 9 for the AMD64? I've got an ASUS K8V Deluxe MB and an NVIDIA GF5200FX video card, for what that's worth. I've been trying, with little success, to compile a working version of the 'Ogle' DVD player, but am running into all sorts of dependency issues with RPMs, and missing library issues compiling from source. If someone else has gotten this working, I'd be interested in hearing exactly what RPMs/source files you used and what steps you followed. Thanks in advance ----------------------------------------- Real programmers confuse Christmas and Halloween because DEC 25 = OCT 31

6 8

memtest86+ to be included on future amd64 suse linux products?
by Andreas Bittner 28 Apr '04

28 Apr '04

hello there, i seem to have some bit errors in one of my memory modules on an asus k8v-d with two corsair cmx512-3200ll (xms3205v1.2) ddr 400mhz modules. memtest86 (on the suse linux 9.0) x86 media didnt recognize the board/hardware, but still reported the same failures, as the newer memtest86+ from http://www.memtest.org/ the memory module displays errors in test #5 at about 107mb and 123mb. the other module passes the tests just fine. the memtest86+ also supports the x86 platform, and correctly displays chipset and hardware information of the newer boards and amd64 platform. maybe suse will consider to include this into their amd64 products like they have the older memtest86 3.0 on their suse linux 9.0 for x86 media. thanks and cheers, andy

3 3

via SATA
by kevin＠trotmans.com 01 Mar '04

01 Mar '04

Have an Albatron with Via Southbridge Sata onboard. Install goes fine if I load sata_via mod and s98klin mod, but on reboot it apparently doesn't add the manually loaded mods to the conf cause it panics trying to mount the root disk (/dev/sda1 - rieser) and I never see anything about the SATA drive. I know there must be a kernel line for this, but I have no clue what it might be. Thankx.

4 5

Rtl 8169 (msi k8t800 neo onboard NIC)
by Tom Keresztes 01 Mar '04

01 Mar '04

Does rtl 8169 have support in suse 9.0 ? As I have seen, 2.6 series kernel have support for it, and I had problems with my linksys nic (ver4, with tulip driver) using ppp (only tested with suse 8.2 beta) Tom#

3 2

kylix on suse9/amd64
by detlef oertel 01 Mar '04

01 Mar '04

Hello, My kylix IDE is running on my suse9/amd64, but I always get a error if I compile a program with kylix. The error is: [Fehler] Falsches Dateiformat: libX11.so.6 possible english translation: [Error] wrong file format: libX11.so.6 I installed kylix with linux32 setup.sh and i start kylix with linux32 startdelphi my system is a suse9/amd64 kernel 2.4.21-201-default any hint for me ? thank you detlef oertel

2 1

SATA problem
by David Green 28 Feb '04

28 Feb '04

Hi, I've tried installing Suse on my machine but it can't see the hard disk (SATA, Promise RAID controller) and understand that only Kernel 2.6 supports this. Since I can't install Linux I can't compile a new Kernel to see the disk drive (I've never compiled a Kernel before so would all be a bit of a learning curve anyway). I've considered buying a second EIDE hard disk and using this for Linux instead but still want to be able to boot into WinXP/2000 (I'm a developer and need all 3 systems) on the SATA drive. Can I do this by (say) creating a boot CD-ROM for Suse to load from, or somehow installing a boot loader on the EIDE drive that boots to the SATA drive. How would I go about doing this? Any help would be much appreciated. Thanks, David

3 2

(online) Upgrade from 8.2 -> 9.0
by Kees Hoekzema 28 Feb '04

28 Feb '04

Hello list, Recently our opteron crashed and lost its filesystem, so i decided to install suse 9.0 instead of the old 8.2 it was still running. Unfortunatly only an 8.2 cd could boot the system, all the 9.0 boot-cd's hung at one point or another. So I decided to do a network install (i shared the 9.0 dvd with ftp from my laptop). Because i wanted to install 9.0 i pointed the installer to the ftp containing the 9.0 dvd. All went well, and the system is working fine again. But i cant use the online update. It is saying i'm running a 8.2 installation, so i used yast to upgrade it to 9.0 (from the same location as from where i installed it). This went well again, but still you says that im running a 8.2 install and tries to look for updates in the wrong ftp-dir. How do I tell yast that im running a 9.0 install and make him look in the right directory. -kees

2 3

powernow_k8: Unknown parameter `" "'
by Henk Slager 28 Feb '04

28 Feb '04

Hi all, I am using an ASUS K8V Deluxe with 1005 BIOS, Cool 'n' Quiet enabled and running SuSE 9.0. It works well with kernel 2.4.21-149-default. However, using the same sysconfig files and the 2.6.3 kernel the above error is seen when running dmesg. A part from my .config file: # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_PROC_INTF=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_24_API=y CONFIG_CPU_FREQ_TABLE=y # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=m If I do 'modprobe powernow-k8' , the extra dmesg output is: powernow-k8: Found AMD64 processor supporting PowerNow (version 1.00.08a) powernow-k8: voltage stable in 100 usec, ramp voltage offset: 2, isochronous relief time: 3, maximum voltage step: 0 powernow-k8: pll lock time: 0x2, maxfid 0xc (2000 MHz), maxvid 0x0 powernow-k8: fid 0 invalid : 0x0 I've played with the config settings and looking into the 2.4.21 .config files but this is the best I can get. Does anybody know what is wrong here ? Henk.

1 0

Boot from MD RAID possible?
by M. Ranjit Mathews 28 Feb '04

28 Feb '04

On Jan 22 2004, Andi Kleen wrote: The VIA and most other SATA RAID controllers are really software RAID. Linux doesn't usually support the format used by the Windows driver, but you can run the normal linux software MD RAID which works just fine. The few real SATA RAID controllers like 3ware are supported. If one uses MD RAID, would one be able to mirror the boot partition? Is it possible to create multiple MD RAIDs on 1 pair of disks such as separate RAID1s for /boot, / and an LVM vg and a RAID0 /space filesystem?

1 0

enable the IOMMU
by Milan Gabor 28 Feb '04

28 Feb '04

HI! I have mptherboard from MSI K8T Master2 and I noticed, that booting up kernel writes this out: Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup Where can I find option to enable IOMMU. I tried to find it in BIOS settings, but I cannot find it. Any hint where is it hidden? MIlan

1 0

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

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

kernel 2.6 and eth0
by Eros Albertazzi 25 Feb '04

25 Feb '04

Just for curiosity I tried (unsupported) kernel 2.6.3-6 on my Opteron Suse 9 box. Boot goes, but it cannot configure eth0 Is there something (different from what it does when I boot 2.4) that I have to add? Or, likely, should I better give up and wait. Regards. -- Eros Albertazzi CNR-IMM, Sez. Bologna Via P.Gobetti 101 I-40129 Bologna, Italy Tel:(+39)-051-639 9179 Fax:(+39)-051-639 9216

3 5

RE: [suse-amd64] Kernel support for large arrays...
by richard.brunner＠amd.com 25 Feb '04

25 Feb '04

There is a limitation with PGI F90 and large arrays greater than 2GB. F77 for PGI 5.1-3 doesn't have this limitation. This will be fixed in the future for F90 by PGI. Please contact PGI, they can give you the latest info. ] -Rich ... ] AMD Fellow ] richard.brunner at amd com

1 0

opteron lockup
by Andrej Filipcic 25 Feb '04

25 Feb '04

Hi, I have some troubles with dual opteron server, Tyan Thunder K8S pro motherboard, 2x246 opteron CPU, 4G mem, suse 9.0 AMD64, kernel 2.4.21-178-smp. I have not yet tested the latest kernel... Occassionaly (once in 2 weeks), there is a deadlock. I am not sure if this is a hardware or kernel problem, since the power supply died once. Any suggestions? There is a ksymoops output attached. Thanks, Andrej -- _____________________________________________________________ doc. dr. Andrej Filipcic, E-mail: Andrej.Filipcic(a)ijs.si Department of Experimental High Energy Physics - F9 Jozef Stefan Institute, Jamova 39, P.o.Box 3000 SI-1001 Ljubljana, Slovenia Tel.: +386-1-477-3674 Fax: +386-1-425-7074 ------------------------------------------------------------- ksymoops 2.4.9 on x86_64 2.4.21-178-smp. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-178-smp/ (default) -m /boot/System.map-2.4.21-178-smp (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Unable to handle kernel paging request at virtual address 000000121c9322c8 ffffffff801845b8 PML4 f65dd067 PGD 0 Oops: 0000 CPU 0 Pid: 26374, comm: top Tainted: P RIP: 0010:[<ffffffff801845b8>]{collect_sigign_sigcatch+56} Using defaults from ksymoops -t elf64-x86-64 -a i386:x86-64 RSP: 0018:000001002f699d80 EFLAGS: 00010006 RAX: 000000121c9322c0 RBX: 00000100a7294000 RCX: 0000000000000000 RDX: 000001002f699ed8 RSI: 000001002f699ed0 RDI: 00000100a7294000 RBP: 00000100570f45b8 R08: 000000121c9322c8 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000000 R12: 00000100570f4580 R13: 00000000003db000 R14: 0000000000000000 R15: 000000000051a780 FS: 000000000050eee0(0000) GS:ffffffff804bbf00(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 000000121c9322c8 CR3: 0000000000101000 CR4: 00000000000006e0 Process top (pid: 26374, stackpage=1002f699000) Stack: 000001002f699d80 0000000000000018 ffffffff80184bf7 00000100a7294000 ffffffff8016f3e0 0000000000000246 ffffffff80182edb 000001007f90b000 0000010080013020 ffffffff803d3480 fffffffffffffff4 00000100656344c0 Call Trace: [<ffffffff80184bf7>]{proc_pid_stat+407} [<ffffffff8016f3e0>]{new_inode+16} [<ffffffff80182edb>]{proc_pid_make_inode+235} [<ffffffff80183343>]{proc_base_lookup+563} [<ffffffff80161ae7>]{real_lookup+167} [<ffffffff8016c5d1>]{dput+33} [<ffffffff80166129>]{__link_path_walk+2425} [<ffffffff80182491>]{proc_info_read+113} [<ffffffff8015466f>]{sys_read+191} [<ffffffff80110143>]{system_call+119} Code: 49 8b 00 48 83 f8 01 75 0f 41 8d 49 ff 48 d3 e0 48 09 06 eb >>RIP; ffffffff801845b8 <collect_sigign_sigcatch+38/80> <===== Trace; ffffffff80184bf7 <proc_pid_stat+197/600> Trace; ffffffff8016f3e0 <new_inode+10/80> Trace; ffffffff80183343 <proc_base_lookup+233/250> Trace; ffffffff8016c5d1 <dput+21/160> Trace; ffffffff80182491 <proc_info_read+71/100> Trace; ffffffff80110143 <system_call+77/7c> Code; ffffffff801845b8 <collect_sigign_sigcatch+38/80> 0000000000000000 <_RIP>: Code; ffffffff801845b8 <collect_sigign_sigcatch+38/80> <===== 0: 49 8b 00 mov (%r8),%rax <===== Code; ffffffff801845bb <collect_sigign_sigcatch+3b/80> 3: 48 83 f8 01 cmp $0x1,%rax Code; ffffffff801845bf <collect_sigign_sigcatch+3f/80> 7: 75 0f jne 18 <_RIP+0x18> Code; ffffffff801845c1 <collect_sigign_sigcatch+41/80> 9: 41 8d 49 ff lea 0xffffffffffffffff(%r9),%ecx Code; ffffffff801845c5 <collect_sigign_sigcatch+45/80> d: 48 d3 e0 shl %cl,%rax Code; ffffffff801845c8 <collect_sigign_sigcatch+48/80> 10: 48 09 06 or %rax,(%rsi) Code; ffffffff801845cb <collect_sigign_sigcatch+4b/80> 13: eb 00 jmp 15 <_RIP+0x15> NMI Watchdog detected LOCKUP on CPU0, eip ffffffff80185d02, registers: CPU 0 Pid: 26375, comm: top Tainted: P RIP: 0010:[<ffffffff80185d02>]{.text.lock.array+7} RSP: 0018:000001007680dd80 EFLAGS: 00000086 RAX: 0000000000000000 RBX: 00000100a7294000 RCX: 0000000000000000 RDX: 000001007680ded8 RSI: 000001007680ded0 RDI: 00000100a7294000 RBP: 00000100570f45b8 R08: 0000010080000638 R09: 00000100828233d8 R10: 0000000000000001 R11: 0000000000000000 R12: 00000100570f4580 R13: 00000000003db000 R14: 0000000000000000 R15: 000000000051a780 FS: 00000000005260a0(0000) GS:ffffffff804bbf00(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000002a9556c000 CR3: 0000000000101000 CR4: 00000000000006e0 Process top (pid: 26375, stackpage=1007680d000) Stack: 000001007680dd80 0000000000000018 0000000000100000 ffffffff80117040 ffffffff80117130 0000000000000001 0000000000000000 0000000000000000 ffffffff803ca8e0 0000000000000000 0000000000000000 0000000000000000 Call Trace: <EOE> [<ffffffff80184bf7>]{proc_pid_stat+407} [<ffffffff802c8f98>]{sprintf+136} [<ffffffff80183343>]{proc_base_lookup+563} [<ffffffff8016c5d1>]{dput+33} [<ffffffff80166129>]{__link_path_walk+2425} [<ffffffff80182491>]{proc_info_read+113} [<ffffffff8015466f>]{sys_read+191} [<ffffffff80110143>]{system_call+119} Code: f3 90 7e f5 e9 84 e8 ff ff e8 70 1b 14 00 e9 80 e9 ff ff 41 >>RIP; ffffffff80185d02 <.text.lock.array+7/105> <===== Trace; ffffffff802c8f98 <sprintf+88/90> Trace; ffffffff8016c5d1 <dput+21/160> Trace; ffffffff80182491 <proc_info_read+71/100> Trace; ffffffff80110143 <system_call+77/7c> Code; ffffffff80185d02 <.text.lock.array+7/105> 0000000000000000 <_RIP>: Code; ffffffff80185d02 <.text.lock.array+7/105> <===== 0: f3 90 repz nop <===== Code; ffffffff80185d04 <.text.lock.array+9/105> 2: 7e f5 jle fffffffffffffff9 <_RIP+0xfffffffffffffff9> Code; ffffffff80185d06 <.text.lock.array+b/105> 4: e9 84 e8 ff ff jmpq ffffffffffffe88d <_RIP+0xffffffffffffe88d> Code; ffffffff80185d0b <.text.lock.array+10/105> 9: e8 70 1b 14 00 callq 141b7e <_RIP+0x141b7e> Code; ffffffff80185d10 <.text.lock.array+15/105> e: e9 80 e9 ff ff jmpq ffffffffffffe993 <_RIP+0xffffffffffffe993> Code; ffffffff80185d15 <.text.lock.array+1a/105> 13: 41 00 00 add %al,(%r8) 1 warning issued. Results may not be reliable.

1 0

RE: [suse-amd64] Kernel support for large arrays...
by richard.brunner＠amd.com 25 Feb '04

25 Feb '04

Physical memory available != virtual memory available for allocation. In an 8GB DRAM system, the BIOS gives the OS approximately 7.5GB (because of various I/O issues). You should be able to get the kernel to allocate a large amount but once you allocate larger than phys memory, you will page awfully. You don't say whether the app requesting the memory is 32-bit or 64-bit. I assume 64-bit. Which PGI compiler (F77? F90?) and which version (5.0? 5.1? 5.1-3?) are you using? How are you allocating the array? ] -Rich ... ] AMD Fellow ] richard.brunner at amd com > -----Original Message----- > From: JOSE LUIS RICARDO-CHAVEZ [mailto:ricardo@irsamc.ups-tlse.fr] > Sent: Tuesday, February 24, 2004 4:33 AM > To: Andreas Jaeger > Cc: suse-amd64(a)suse.com > Subject: Re: [suse-amd64] Kernel support for large arrays... > > > Andreas Jaeger wrote: > > >JOSE LUIS RICARDO-CHAVEZ <ricardo(a)irsamc.ups-tlse.fr> writes: > > > > > > > >>recently we have installed in our lab an Opteron system (Tyan 2882 > >>motherboard, two Opteron 244 processor, 8 GB memory) running SuSE > >>AMD64 9.0 Using the PGI compiler suite we did some memory > allocation > >>tests. We found a modest 4 GB > >>memory limit per allocated array. According to PGI engineers this is > >>not a compiler > >>fault, the limit is just set in kernel's mmap.c routine. > Would it be safe to > >>change this value and recompile the kernel or it would require > >>changing some other > >>routines? > >> > >> > > > >There's no such limit in the kernel. You should be allocate such an > >array without problems. > > > >Andreas > > > > > > Hi Andreas, > > You are right, I looked into the file > /usr/include/asm-x86-64/processor.h > and found the following: > > /* > * User space process size: 512GB - 1GB (default). > */ > #define TASK_SIZE (0x0000007fc0000000) > > /* This decides where the kernel will search for a free chunk of vm > * space during mmap's. > */ > #define IA32_PAGE_OFFSET ((current->personality & ADDR_LIMIT_3GB) ? > 0xc0000000 : 0xFFFFe000) > #define TASK_UNMAPPED_32 (PAGE_ALIGN(IA32_PAGE_OFFSET / 3)) > #define TASK_UNMAPPED_64 PAGE_ALIGN(TASK_SIZE/3) > #define TASK_UNMAPPED_BASE \ > (test_thread_flag(TIF_IA32) ? TASK_UNMAPPED_32 : > TASK_UNMAPPED_64) > > So the problem is not related to the way the OS maps > physical memory into virtual memory. > Could it be possible that the motherboard is tuned to support > mainly a 32-bit system and by that reason it uses the last > megabytes right before the 4 GB limit to allocate space for > drivers? I've heard that Tyan is considering to provide a > BIOS version designed to support only 64-bit operating > systems, I hate to wait but maybe that's the solution. > > Greeting from Toulose, > > - Jose Luis > > -- > JosÃ© Luis RICARDO-CHAVEZ Tel. +33-5-61-55-68-33 > Laboratoire de Physique Quantique Fax +33-5-61-55-60-65 > UniversitÃ© Paul Sabatier > 118 route de Narbonne > F-31062 Toulouse, France > > e-mail: ricardo(a)irsamc.ups-tlse.fr > > >

4 4