September 2004 - openSUSE AMD64 - openSUSE Mailing Lists

Realplayer 10.00 /Helix Player
by Graf, Markus 13 Sep '04

13 Sep '04

Hello, Is someone out there who run the realplay 10 / Helix player on a AMD 64 Box? In the source there are -march=pentium -mcpu=pentium ???? The pure helix developer do not have AMDs ;-) CU Markus

1 0

Problems with alsasound (SB Live Value and Audigy 2 NX usb)
by spam＠mrplanlos.de 13 Sep '04

13 Sep '04

Hello there, a few weeks ago I bought a qbic 3801 barebone for AMD 64. I knew that the onboard sound chip, a CMedia 8768 won't work and the NIC will be supported with an 2.6.8 Kernel. So I bought a usb sound card which I also can use with my Notebook. I took the Creative Audigy 2 NX usb which works by other Linux users (not completely but iot works). After installing the 64 Bit SuSE and disabling the onboard sound chip in the BIOS I couldn't install the Audigy sound card. It is detected by the usb port and I can see it in the SuSE plugger, but alsaconf and yast2 don't find any sound card. I tried to use the generic usb sound driver from alsa, but it fails. After installing the newest kernel of the day (2.6.8-20040909144556-default), my NIC works great (It's a force depth nvidia driver), but my soundcard still is quiet. After many tries I decided to use an old SB Live value from a friend, but this pci card also keeps quiet. Yast2 tells me: "Das Kernelmodul snd-emu10k1 konnte nicht geladen werden. Ein möglicher Grund dafür können falsche Modulparameter sein, sowie ungültige IO - oder IRQ - Parameter". So I tried to insert the module step by step: andy:/lib/modules/2.6.8-20040909144556-default/kernel/sound/pci/emu10k1 # insmod snd-emu10k1.ko insmod: error inserting 'snd-emu10k1.ko': -1 File exists then I tried modprobe: modprobe snd-emu10k1 but dmesg tells the following: ALSA sound/pci/ac97/ac97_codec.c:1937: AC'97 0 does not respond - RESET ALSA sound/pci/ac97/ac97_codec.c:1945: AC'97 0 access is not valid [0x0], removing mixer. EMU10K1_Audigy: probe of 0000:02:06.0 failed with error -5 emu10k1: Unknown symbol midi_synth_reset emu10k1: Unknown symbol midi_synth_controller emu10k1: Unknown symbol midi_synth_set_instr emu10k1: Unknown symbol midi_devs emu10k1: Unknown symbol sound_alloc_mididev emu10k1: Unknown symbol midi_synth_ioctl emu10k1: Unknown symbol midi_synth_open emu10k1: Unknown symbol midi_synth_send_sysex emu10k1: Unknown symbol sequencer_init emu10k1: Unknown symbol midi_synth_close emu10k1: Unknown symbol midi_synth_bender emu10k1: Unknown symbol midi_synth_start_note emu10k1: Unknown symbol sound_unload_mididev emu10k1: Unknown symbol midi_synth_load_patch emu10k1: Unknown symbol midi_synth_panning emu10k1: Unknown symbol midi_synth_aftertouch emu10k1: Unknown symbol midi_synth_setup_voice emu10k1: Unknown symbol midi_synth_kill_note emu10k1: Unknown symbol midi_synth_hw_control emu10k1: Unknown symbol midi_synth_reset emu10k1: Unknown symbol midi_synth_controller emu10k1: Unknown symbol midi_synth_set_instr emu10k1: Unknown symbol midi_devs emu10k1: Unknown symbol sound_alloc_mididev emu10k1: Unknown symbol midi_synth_ioctl emu10k1: Unknown symbol midi_synth_open emu10k1: Unknown symbol midi_synth_send_sysex emu10k1: Unknown symbol sequencer_init emu10k1: Unknown symbol midi_synth_close emu10k1: Unknown symbol midi_synth_bender emu10k1: Unknown symbol midi_synth_start_note emu10k1: Unknown symbol sound_unload_mididev emu10k1: Unknown symbol midi_synth_load_patch emu10k1: Unknown symbol midi_synth_panning emu10k1: Unknown symbol midi_synth_aftertouch emu10k1: Unknown symbol midi_synth_setup_voice emu10k1: Unknown symbol midi_synth_kill_note emu10k1: Unknown symbol midi_synth_hw_control emu10k1: Unknown symbol midi_synth_reset emu10k1: Unknown symbol midi_synth_controller emu10k1: Unknown symbol midi_synth_set_instr emu10k1: Unknown symbol midi_devs emu10k1: Unknown symbol sound_alloc_mididev emu10k1: Unknown symbol midi_synth_ioctl emu10k1: Unknown symbol midi_synth_open emu10k1: Unknown symbol midi_synth_send_sysex emu10k1: Unknown symbol sequencer_init emu10k1: Unknown symbol midi_synth_close emu10k1: Unknown symbol midi_synth_bender emu10k1: Unknown symbol midi_synth_start_note emu10k1: Unknown symbol sound_unload_mididev emu10k1: Unknown symbol midi_synth_load_patch emu10k1: Unknown symbol midi_synth_panning emu10k1: Unknown symbol midi_synth_aftertouch emu10k1: Unknown symbol midi_synth_setup_voice emu10k1: Unknown symbol midi_synth_kill_note emu10k1: Unknown symbol midi_synth_hw_control NET: Registered protocol family 4 ax25: unsupported module, tainting kernel. NET: Registered protocol family 3 NET: Registered protocol family 5 eth0: no IPv6 routers present ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 12 (level, low) -> IRQ 12 ALSA sound/pci/ac97/ac97_codec.c:1937: AC'97 0 does not respond - RESET ALSA sound/pci/ac97/ac97_codec.c:1945: AC'97 0 access is not valid [0x0], removing mixer. EMU10K1_Audigy: probe of 0000:02:06.0 failed with error -5 ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 12 (level, low) -> IRQ 12 ALSA sound/pci/ac97/ac97_codec.c:1937: AC'97 0 does not respond - RESET ALSA sound/pci/ac97/ac97_codec.c:1945: AC'97 0 access is not valid [0x0], removing mixer. EMU10K1_Audigy: probe of 0000:02:06.0 failed with error -5 That's it, I can't find the problem, I reinstalled SuSE and tried to configure the Soundblaster Live (which works with the 32 Bit SuSE on my older computer) with the original 2.6.5 SuSE Kernel, but it still doesn't work. Seems to be a failure in the module, but I don't know what to do now. Is there anybody ou there who could help me? Thanks Andy -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

1 0

OpenPBS issue
by Torsten Wolf 13 Sep '04

13 Sep '04

Hi, a rather nasty issue troubles me on our linux opteron cluster. qdel (taken from SuSE9.1 x86-64 OpenPBS packages) needs to be invoked at least two times. If a job exceeds a queue limit, it is killed partially; i.e. the tasks are terminated via the epilogue-script (via the invocation of mpiclean), but the job remains in the queue with state running! Thus, the nodes are blocked. An additional qdel removes the job from the queue. The same happens when the job finishes within the queue limits. If a job needs to be terminated manually, a first qdel kills the tasks and a second invocation clears the queue. In search for a trivial workaround, I created a script called qdel which calls the original qdel twice, which works fine for a manual removal of running jobs. Alas, this does not work when a job exceeds existing limits of the queue or finishes orderly. Any help is greatly appreciated. Best wishes, Torsten

1 0

This installation doesn't support glibc-2.1 on x86_64
by Roy F. Cabaniss 12 Sep '04

12 Sep '04

I went to install some games I had on my old box, railroad tycoon and SOF to be precise (Civilization was next). In both cases I got the following error message. This installation doesn't support glibc-2.1 on x86_64 Are the few decent linux based games I have toast, or can I salvage this mess? -- Dr. Roy F. Cabaniss Associate Professor of Marketing University of Arkansas Monticello

2 4

SUSE Enterprise 9 AMD 64 install on Penguin Atlus 1000 server issue
by Frank Li (frali) 11 Sep '04

11 Sep '04

Has any of you guys tried to install SUSE Enterprise 9 AMD 64 on one of the penguin Atlus 1000 server ? It is a Dual Opteron box with 1 G of RAM. I can't seem to get the install kernel to boot properly, it states some machine Check exceptions around the line CPU 0 IO APIC and stops. I've tried various options such as noacpi, acpi=oldboot, nodma, nothing seem to help. I can boot from the 32-bit 2.6.X kernels just fine, it is just the 64bit 2.6.X that's giving me a problem.

2 3

mldonkey: configure: ok - make: ok - make install: error
by Raimund Eimann 11 Sep '04

11 Sep '04

Hi, I'm trying to install mldonkey 2.5.21 or 2.5.22 from the sources on my Athlon64 running SuSE Linux 9.1 (x86_64). For both versions "./configure" and "make" run without problems. In both cases "make install" brings up this: # make install no -inline 10 -I src/utils/cdk -I src/daemon/chat -I src/utils/lib -I src/utils/net -I tools -I src/daemon/common -I src/daemon/driver -I src/utils/mp3tagui -I src/config/unix -I src/networks/gnutella -I src/networks/gnutella2 -I src/networks/fasttrack -I src/networks/fileTP -I src/networks/bittorrent -I src/networks/donkey -c src/utils/lib/date.ml make: no: Command not found make: *** [src/utils/lib/date.cmx] Error 127 To me that looks like a linewrap somewhere. The bizarre thing is that I can compile and install these packages on SuSE 9.1 for i586 without running into this problem. Did anyone have a similar experience with trying to get mldonkey running on SuSE for AMD64? Or better: is anyone able to help with that? Cheers, Raimund

8 12

Re: [suse-amd64] latest kotd, SATA again using SCSI "emulation"?
by Roel Vestjens 10 Sep '04

10 Sep '04

On Sunday 15 August 2004 20:53, Vojtech Pavlik wrote: > On Sun, Aug 15, 2004 at 07:50:53PM +0200, Arjen Runsink wrote: > > Hi Vojtech, > > > > On Sunday 15 August 2004 18:56, Vojtech Pavlik wrote: > > > Not possible. If the sata_via or sata_sil drivers are used, it's always > > > sda. There, however, ale the IDE drivers (VIA_IDE - vt82cxxx, "SiI IDE" > > > - siimage.c), which can drive the SATA drives as well, and then the > > > drive will appear as hda. > > > > > > So I suppose what happened is that the IDE driver got initialized first > > > in the "hda" cases and the libata (SATA) driver in the "sda" cases. > > > > And thus a "mistery" is explained. So I talked to a kernel hacker too and > > he said that using the sata_* would be better and will be used in future > > kernels, for TCQ etc. It really works better for me, I had to use the "barrier=off" boot parameter to be able to boot with the official kernel releases from kernel-default-2.6.5-7.75 and onwards (my latest was 2.6.5-7.108). All these kernels addressed the serial ATA disk as hda and delivered a very poor performance of only 3-5 MB/sec (hdparm -t). Now I'm using the latest KOTD which addresses the same disk (ATA SAMSUNG SP1614C) as sda (no barrier parameter is needed) and it delivers a performance of 55-150 MB/sec. This is like it should be. > > > > How can I force the standard suse kernels to use sata_via instead of > > blk_dev_via82cxxx ? > > You might be able to use something like "ide0=noprobe" (replace 0 with > the proper number for your SATA interface). It might not work, though, > since the IDE driver could still grab the controller, even if it doesn't > touch the drives. ide0=noprobe didn't work for me, installing a different kernel (the latest KOTD) did the job > > -- > Vojtech Pavlik > SuSE Labs, SuSE CR Roel Vestjens

1 0

Support for NVidia 6 series?
by Yasunari Tosa 10 Sep '04

10 Sep '04

Hi, Is anyone out there using NVidia 6 series like 6800 under SuSE 9.1 Pro? Does it work with SuSE 9.1? Thank you. Tosa

2 1

32 bit fortan compilers
by Luis Jose Maia Amoreira 10 Sep '04

10 Sep '04

Hello, Wen I use a 32 bit compiler like g95 or gfortran95, I get more then one hundred assembler messages, like the ones below hadron:f9x$ g95 elmt.f95 /tmp/cckVcW6l.s: Assembler messages: /tmp/cckVcW6l.s:12: Error: suffix or operands invalid for `push' /tmp/cckVcW6l.s:15: Error: `8(%ebp)' is not a valid 64 bit base/index expression /tmp/cckVcW6l.s:16: Error: `(%eax)' is not a valid 64 bit base/index expression /tmp/cckVcW6l.s:17: Error: `-8(%ebp)' is not a valid 64 bit base/index expression [.... loads of simmilar messages.....] /tmp/cckVcW6l.s:71: Error: suffix or operands invalid for `push' /tmp/cckVcW6l.s:73: Error: suffix or operands invalid for `push' /tmp/cckVcW6l.s:74: Error: suffix or operands invalid for `push' /tmp/cckVcW6l.s:75: Error: suffix or operands invalid for `push' [.... more loads of messages like the ones in the first set above....] /tmp/cckVcW6l.s:236: Error: suffix or operands invalid for `pop' /tmp/cckVcW6l.s:237: Error: suffix or operands invalid for `pop' /tmp/cckVcW6l.s:238: Error: suffix or operands invalid for `pop' /tmp/cckVcW6l.s:239: Error: suffix or operands invalid for `pop' hadron:f9x$ Is there a simple solution to this? I tried to compile g95, but had no success... TIA Ze ______________________________________________________________ Departamento de Física http://www.dfisica.ubi.pt Universidade da Beira Interior http://www.ubi.pt ______________________________________________________________

3 4

SuSE 9.1 Pro + SSH + Hostbased Authentication
by Bryan Stillwell 09 Sep '04

09 Sep '04

I'm running into a problem on SuSE 9.1 Professional for AMD64 where hostbased authentication doesn't seem to be working properly... In /etc/ssh/sshd_config and /etc/ssh/ssh_config I have it turned on: HostbasedAuthentication yes I've also turned on: PermitRootLogin yes In /etc/ssh/shosts.equiv I have the proper entry: master 10.1.1.128 But when I try to log in, it asks for the password. When running sshd with debugging turned on (sshd -d -d -d -p 2222), it reports the following (snipped for briefness): debug1: userauth-request for user root service ssh-connection method none debug1: attempt 0 failures 0 debug3: mm_getpwnamallow entering debug3: mm_request_send entering: type 6 debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM debug3: mm_request_receive_expect entering: type 7 debug3: mm_request_receive entering debug3: monitor_read: checking request 6 debug3: mm_answer_pwnamallow debug3: mm_answer_pwnamallow: sending MONITOR_ANS_PWNAM: 1 debug3: mm_request_send entering: type 7 debug2: monitor_read: 6 used once, disabling now debug3: mm_request_receive entering debug2: input_userauth_request: setting up authctxt for root debug3: mm_start_pam entering debug3: mm_request_send entering: type 45 debug3: monitor_read: checking request 45 debug3: mm_inform_authserv entering debug1: PAM: initializing for "root" debug3: mm_request_send entering: type 3 debug2: input_userauth_request: try method none Failed none for root from ::ffff:10.1.1.128 port 38469 ssh2 debug1: userauth-request for user root service ssh-connection method hostbased debug1: attempt 1 failures 1 debug2: input_userauth_request: try method hostbased debug1: userauth_hostbased: cuser root chost master. pkalg ssh-dss slen 55 debug3: mm_key_allowed entering debug3: mm_request_send entering: type 20 debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED debug3: mm_request_receive_expect entering: type 21 debug3: mm_request_receive entering debug3: Normalising mapped IPv4 in IPv6 address debug3: Trying to reverse map address 10.1.1.128. debug1: PAM: setting PAM_RHOST to "master" debug1: PAM: setting PAM_TTY to "ssh" debug2: monitor_read: 45 used once, disabling now debug3: mm_request_receive entering debug3: monitor_read: checking request 3 debug3: mm_answer_authserv: service=ssh-connection, style= debug2: monitor_read: 3 used once, disabling now debug3: mm_request_receive entering debug3: monitor_read: checking request 20 debug3: mm_answer_keyallowed entering debug3: mm_answer_keyallowed: key_from_blob: 0x55cb20 debug2: userauth_hostbased: chost master. resolvedname master ipaddr ::ffff:10.1.1.128 debug2: stripping trailing dot from chost master. debug2: auth_rhosts2: clientuser root hostname master ipaddr ::ffff:10.1.1.128 debug1: temporarily_use_uid: 0/0 (e=0/0) debug1: restore_uid: 0/0 debug1: temporarily_use_uid: 0/0 (e=0/0) debug1: restore_uid: 0/0 debug3: mm_answer_keyallowed: key 0x55cb20 is disallowed debug3: mm_request_send entering: type 21 debug3: mm_request_receive entering debug2: userauth_hostbased: authenticated 0 Failed hostbased for root from ::ffff:10.1.1.128 port 38469 ssh2 I believe the problem is in "mm_answer_keyallowed: key 0x55cb20 is disallowed", but I don't know why it's being rejected... Does anyone have any ideas? I've even tryed chmod'ing /usr/lib64/ssh/ssh-keysign to be suid root (4755) without success... Thanks, Bryan -- Aspen Systems, Inc. | http://www.aspsys.com/ Production Engineer | Phone: (303)431-4606 bryans(a)aspsys.com | Fax: (303)431-7196

1 3