April 2004 - openSUSE AMD64 - openSUSE Mailing Lists

[suse-amd64] SUSE Linux Component DataBase
by Detlef Heinrich 04 Apr '04

04 Apr '04

Hello Suse Team, although Suse 9.1 is on the horizon, I want to give you a short feedback regarding the 9.0 installation on my hardware combination. (GA-KA8VNXP is not listed in your database) equipment: M.-Board : Giga-byte GA-KA8VNXP Processor: AMD Athlon64 (Socket 754) Graphic : AUSUS 9800XT Sound : On-Board SATA RAID: On-Board VIA VT8237 1. Installation (on SATA disks) with SuSE-Linux Patch CD was done without any problems (Thank you four your efforts) 2. Graphic: is ok. waiting still for an answer from ATI regarding my request for an 64bit driver (my be it will be a christmas gift) 3. Sound : is ok. XMMS (1.2.8) is only working with aRts Driver (0.4) proper. 4. DVD with "Kaffeine" is ok. (I've seen some postings, notifying errors regarding playing DVD`s) Only one issue is driving me crasy: The seti@home 32bit client is running much more faster than the 64bit client (30 minutes). ;-) Kr...Detlef Heinrich

2 1

Nvidia AMD64 1.0-5332 trouble
by Jeroen Leijen 02 Apr '04

02 Apr '04

Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers? I compiled and installed the drivers according the instructions as supplied by nvidia. On my system (suse 9.0, k_deflt 2.4.21.201.x86_64, msi k8t neo fisr, athlon 64 3000, msi geforce fx5200) sax2 shows only a blank screen. Thanks Jeroen Amsterdam

7 8

RE: [suse-amd64] Solved Re: [suse-amd64] Nvidia AMD64 1.0-5332 trouble
by Elvis Chen 02 Apr '04

02 Apr '04

hi, >From: Jeroen Leijen <depot(a)xs4all.nl> >To: suse-amd64(a)suse.com >Subject: [suse-amd64] Solved Re: [suse-amd64] Nvidia AMD64 1.0-5332 trouble > >"NvAgp" "1" did the trick. So my system is using the Nvidia AGP module. I >don't understand why X doesn't run when using the regular kernel module >AGPGART (i.e. Option "NvAgp" "3", the default setting). I had/have the same problem. In fact, setting "NvAGP" to 1 *DISABLES* AGP. see my explaination below. >1. Has anyone X running with agpgart using the system setup described >below? >2. Benchmark exchange: >jeroen@linux:~> glxgears >7695 frames in 5.0 seconds = 1539.000 FPS >8951 frames in 5.0 seconds = 1790.200 FPS My Athlon 2400+ with GForce 4200 has a frame rate of: 31088 frames in 5.0 seconds = 6217.600 FPS 34026 frames in 5.0 seconds = 6805.200 FPS under Suse 8.2. Not knowing what hardware you have, I can't say if yours is running optimally. However, I have another machine with Athlon 64-3400+ with GF 5950Ultra, and I'm only getting about *600* FPS under Suse 9.0 (for AMD64). Changing "NvAGP" from "1" to "0" (0 disables AGP) resulted in the same frame rate. This is on 2.4.21 kernel. so, I suspect you have your AGP disabled. Elvis _________________________________________________________________ STOP MORE SPAM with the MSN Premium and get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

gcc / BFD problem
by Joseph Comfort 02 Apr '04

02 Apr '04

I have been trying to compile the CERN library (cernlib) on a dual Opteron. With some patches in the configuration files, everything looks good with 64-bit compilation. The lib....a libraries appear to compile in 32-bit (-m32) form. But some programs produced from these files, and SuSE system files, fail. Below is the log file from the attempt to produce paw++. The complaint relates to BFD code. I don't know if the problem is there, or in the cernlib somewhere -- or how to find it. The message says to report the bug. Please advise. Thank you. installing in /pawlib/paw... gmake[1]: Entering directory `/usr/local/cern/2003_new/build/pawlib/paw' making Makefiles in /pawlib/paw/programs... installing in /pawlib/paw/programs... gmake[2]: Entering directory `/usr/local/cern/2003_new/build/pawlib/paw/programs' rm -f 0pamain.o g77 -c -O -m32 -fno-automatic -fno-second-underscore -fugly-complex -I/usr/local/cern/2003_new/build/pawlib/paw -I/usr/local/cern/2003_new/src/pawlib/paw -I/usr/local/cern/2003_new/src/pawlib/paw/programs -I/usr/local/cern/2003_new/src/include -DCERNLIB_LINUX -DCERNLIB_UNIX -DCERNLIB_LNX -DCERNLIB_QMGLIBC -o 0pamain.o /usr/local/cern/2003_new/src/pawlib/paw/programs/0pamain.F rm -f pawX11 Linking with cern libraries /usr/local/cern/2003_new/lib/libpawlib.a /usr/local/cern/2003_new/lib/liblapack3.a /usr/local/cern/2003_new/lib/libblas.a /usr/local/cern/2003_new/lib/libgraflib.a /usr/local/cern/2003_new/lib/libgrafX11.a /usr/local/cern/2003_new/lib/libpacklib.a /usr/local/cern/2003_new/lib/libmathlib.a /usr/local/cern/2003_new/lib/libkernlib.a -L/usr/X11R6/lib -lX11 -lnsl -lcrypt -ldl g77 -o pawX11 -O -m32 -fno-automatic -fno-second-underscore -fugly-complex -Wl,-E -L/usr/local/cern/2003_new/src../lib 0pamain.o `cernlib pawlib graflib/X11 packlib mathlib kernlib` \ || rm -f pawX11 /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.2/../../../../x86_64-suse-linux/bin/ld: BFD 2.14.90.0.5 20030722 (SuSE Linux) internal error, aborting at ../../bfd/elfcode.h line 224 in bfd_elf64_swap_symbol_in /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.2/../../../../x86_64-suse-linux/bin/ld: Please report this bug. collect2: ld returned 1 exit status Error: pawX11 not executable gmake[2]: *** [pawX11] Error 1 gmake[2]: Leaving directory `/usr/local/cern/2003_new/build/pawlib/paw/programs' gmake[1]: *** [install.bin] Error 2 gmake[1]: Leaving directory `/usr/local/cern/2003_new/build/pawlib/paw' make: *** [install.bin] Error 2

1 0

dvd+rw-tools vs. SLES*/AMD64
by Stephen Williams 02 Apr '04

02 Apr '04

OK, got my fnacy new DVD writer, and I'm able to mount CD-ROMS on it, and I can (miraculously) play DVD videos using xine. But I'm trying to get dvd+rw-tools to run, to no avail. Things like dvd+rw-mediainfo and dvd+rw-format seem to work, but when I try to write a simple ISO9660 image with growisofs it ends with an I/O error message. The long list of pointer/integer size warnings when compiling the tools did not give me warm fuzzies. Has this worked for anybody on an AMD64? Details: /usr/local/bin/dvd+rw-mediainfo /dev/cdrecorder INQUIRY: [SONY ][DVD RW DRU-530A ][1.0d] GET [CURRENT] CONFIGURATION: Mounted Media: 14h, DVD-RW Sequential Media ID: SONY000000U9 GET PERFORMANCE: Speed Descriptor#0: 00/256047 Reading(a)4.0x Writing(a)1.0x READ DVD STRUCTURE[#10h]: Media Book Type: 32h, DVD-RW book [revision 2] Legacy lead-out at: 2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: Media Book Type: 32h, DVD-RW book [revision 2] Last border-out at: 2298496*2KB=4707319808 READ DISC INFORMATION: Disc status: complete Number of Sessions: 1 State of Last Session: complete Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: complete Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size: 256048*2KB FABRICATED TOC: Track#1 : 14@0 Track#AA : 14@256048 Multi-session Info: #1@0 -- Steve Williams "The woods are lovely, dark and deep. steve at XXXXXXXXXX But I have promises to keep, http://www.XXXXXXXXXX and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."

1 1

RE: [suse-amd64] SATA on SLES8
by Black, Alain 02 Apr '04

02 Apr '04

Frank, I'm running the 3Ware 8506-12 12Port SATA Raid running as an add on card to the Tyan 2880UGNR Dual Opteron MB. So the information that you provided seems to fit QUITE nicely into my setup. Now I've got some calls to make to my VAR. Thanks for the info, -Alain -----Original Message----- From: pieczy(a)web.de [mailto:pieczy@web.de] Sent: Thursday, April 01, 2004 10:27 AM To: suse-amd64(a)suse.com Subject: Re: [suse-amd64] SATA on SLES8 On Wednesday 31 March 2004 18:01, Black, Alain wrote: > I am getting the following entries in the /var/log/messages file. The > entries are in reference to my 12 port 3Ware SATA RAID card. I tried a 11 > disk RAID set (with one hot spare) which I've been told is not supported > with the kernel provided with SLES8. I've moved to smaller RAID sets, but > the system will still hang after writing more than 8GB to the RAID sets. Which controller do you use? On which board? There is a know HW issue with 3ware controllers on Tyan boards: http://www.tyan.com/support/html/f_s2885.html Why can't I get my 3ware Raid card to work correctly with this motherboard? 3ware and Tyan have worked together to identify the issue between 3ware 7506 ATA and 8506 SATA RAID controllers and certain chipsets. 3Ware has a technical note available on their knowledge base: https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf Tyan will be working with 3Ware to validate the next generation of 8506/9500 RAID controllers on our motherboards. May be you need a new controller :-( Regards Frank -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

1 0

Realplayer hangs
by Jeroen Leijen 01 Apr '04

01 Apr '04

I am running Suse 9.0 installed by FTP. This means I don't have a realplayer package supplied by Suse. I downloaded it from Real. When I start realplayer the window shows up but after that it immediately hangs. I am curious if you all have the same problem. Thanks, Jeroen from Amsterdam

1 0

SATA VIA Re-revisited (DMA timer_expiry)
by Jason Vertrees 01 Apr '04

01 Apr '04

Johan et. al., I'm still having those ire producing dma_timer_expiry problems. I rebuilt my kernel with Johan's (claims to have 2.6.x working with SATA flawlessly) kernel's ".config" and couldn't even get that booted. Aside from that, I even switched to SuSe's new 64-bit 2.6.4-29-smp kernel and that didn't work. Right now (w/2.6.4-29-smp) under load, I get hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt from dmesg w/15 second bus reset. I've changed from sata_via to libata (I think) and still am having problems. My /etc/sysconfig/kernel line is INITRD_MODULES="libata scsi_mod sd_mod reiserfs" where removing "sata_via" didn't help any. Also, I tried turning off (any of) Samsung's acoustic management tuning. Right now hdparm -Tt shows: /dev/hda: Timing buffer-cache reads: 1964 MB in 2.00 seconds = 981.66 MB/sec Timing buffered disk reads: 174 MB in 3.02 seconds = 57.68 MB/sec I just noticed that throughout the whole process the device has always been /dev/hda2 and not /dev/sda2 as it should have been with libata, right? So, maybe removing "sata_via" from the /etc/sysconfig/kernel file (and remaking initrd) didn't do anything for me (indicating sata_via's built into the kernel?). Ok, so I'm remaking 2.6.5-rc2 with 'sata_via' as module, will remove it from the /etc/sysconfig/kernel file and reboot. -- minutes later -- Ok, sata_via's been built as a module. I've left it OUT of the INITRD (dmesg agrees) but still /dev/hda2 exists (and was booted from). Still /dev/hda2 not /dev/sda2. Not sata modules recognized in 'lsmod' or in dmesg. I'm almost 100% sure I'll get the error soon. Ideas and comments are always welcome! Thanks! -- Jason -- Jason Vertrees BSCB Graduate Student @ UTMB, Galveston javertre(a)utmb.edu :: http://www.bscb.utmb.edu

3 2

[suse-amd64] SATA on SLES8
by Black, Alain 01 Apr '04

01 Apr '04

I am getting the following entries in the /var/log/messages file. The entries are in reference to my 12 port 3Ware SATA RAID card. I tried a 11 disk RAID set (with one hot spare) which I've been told is not supported with the kernel provided with SLES8. I've moved to smaller RAID sets, but the system will still hang after writing more than 8GB to the RAID sets. Please let me know if I have not provided enough information for this to make sense. Mar 31 08:02:10 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: INFO: Initialization started: Unit #5. Mar 31 08:02:10 bsiarc1 kernel: klogd 1.4.1, ---------- state change ---------- Mar 31 08:02:10 bsiarc1 kernel: Inspecting /boot/System.map-2.4.21-207-smp Mar 31 08:02:10 bsiarc1 kernel: Loaded 14963 symbols from /boot/System.map-2.4.21-207-smp. Mar 31 08:02:10 bsiarc1 kernel: Symbols match kernel version 2.4.21. Mar 31 08:02:10 bsiarc1 kernel: Error seeking in /dev/kmem Mar 31 08:02:10 bsiarc1 kernel: Symbol #nls_iso8859-1, value a013c000 Mar 31 08:02:10 bsiarc1 kernel: Error adding kernel module table entry. Mar 31 08:03:22 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: ERROR: Drive error: Port #5. Mar 31 08:03:22 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: WARNING: Sector repair occurred: Port #5. Mar 31 08:03:32 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: ERROR: Drive error: Port #5. Mar 31 08:03:32 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: WARNING: Sector repair occurred: Port #5. Mar 31 08:03:41 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: ERROR: Drive error: Port #5. Mar 31 08:03:41 bsiarc1 kernel: 3w-xxxx: scsi0: AEN: WARNING: Sector repair occurred: Port #5. -Alain.

2 1