September 2004 - openSUSE AMD64 - openSUSE Mailing Lists

DVD writer not working
by Janis Klava 06 Sep '04

06 Sep '04

Gentlemen, After doing an online-update today to the latest kernel 2.6.5-7.108 default, the DVD writer has quit altogether. Insert the SuSE 9.1 AMD64 DVD disk to make a back-up and K3B signals: "Error, no media found". Debug gives the following message: System ----------------------- K3b Version:0.11.12 KDE Version: 3.2.1 QT Version: 3.3.1 CDs still function normally. System is a stock 9.1 for AMD64 with all upgrades. Tyan K8W, Opteron 248, Plextor PX-708A DVD-RW Janis K.

2 1

Advise for Compaq R3240US
by emir limar 06 Sep '04

06 Sep '04

hi i was considering to buy a Compaq Presario R3240US . Any one had experience with it. It is AMD 64. Does it good with Linux? major problems, any comments wellcome. emin -- _______________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.as…

2 1

make of kdevelop project fails because of libart_lgpl_2.la
by detlef.grittner＠t-online.de 06 Sep '04

06 Sep '04

Hello, I've tried to make a kde project with kdevelop 3.0 on SuSE 9.1. I added the line "--with-qt-libraries=/usr/lib/qt3/lib64/" to the configure options and now I get a make file. But if I want to compile and link the program, then make gives me the following error: /bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -L/usr/lib64/ -o kde232 -R /opt/kde3/lib -R /usr/lib/qt3/lib64/ -R /usr/X11R6/lib64 -L/usr/X11R6/lib64 -L/usr/lib/qt3/lib64/ -L/opt/kde3/lib main.o kde232.o -lkdeui *libtool: link: cannot find the library `/usr/lib/libart_lgpl_2.la' Actually the file libart_lgpl_2.la is installed in the path /usr/lib64/ I haven't managed to pass the correct pass to make. As you can see there is already the option "-L/usr/lib64/" on the command line of the libtool, but it doesn't work. On the other hand I can't believe that the tool wants to link a 64 bit program against a 32 bit library. Can anyone help me getting make to accept the correct path? Regards Detlef

1 1

AMD64, VMWare and USB
by W. Voos 06 Sep '04

06 Sep '04

Hello, there seems to be a (known?) problem with VMWare 4.5 and SuSE 9.1 regarding USB-support. It seems to be resolved with newer 32-bit Kernels, after a node under /proc was named back to the kernel default. ( http://www.vmware.com/community/thread.jspa?forumID=19&threadID=6044 ) However, there still seems to be another problem with 64bit kernels. This problem looks very similar, the host-kernel recognizes the USB-device correctly, you can connect it to the guest (in VMWare), but the Guest-OS then only recognizes an "unknown device". If I look into the vmware-log, I see entries stating: Aug 27 01:47:06: vmx| USB: Connecting device 0xf0010002057c1900 Aug 27 01:47:06: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices Aug 27 01:47:06: vmx| USBGL: SUBMITURB=0x8578bc0 failed -1:22:Invalid argument Aug 27 01:47:06: vmx| type=2 endpoint=80 status=0 flags=0 buffer=0x8578bec Aug 27 01:47:06: vmx| buflen=10 actlen=0 sof=0 numpkts=0 errcount=0 Aug 27 01:47:06: vmx| signr=0 ucontext=0x8578bb8 Aug 27 01:47:06: vmx| USB: Setup issued during another setup action and in the guest-OS /var/log/messages (SUSE 9.1 i386) I see: Aug 27 00:36:14 server02 kernel: usb 1-1: new full speed USB device using address 2 Aug 27 00:36:15 server02 kernel: usb 1-1: device not accepting address 2, error -71 A dmesg on the host gives me the messages: ioctl32(vmware-vmx:13090): Unknown cmd fd(106) cmd(802c550a){00} arg(085a47c0) on /proc/bus/usb/002/002 ioctl32(vmware-vmx:13090): Unknown cmd fd(106) cmd(802c550a){00} arg(084363b0) on /proc/bus/usb/002/002 Now, for me it looks like there is some kind of missing compatibility between 32 bit programs (VMWare) and the 64bit kernel. How could this be resolved? I have seen some mapping calls in vmmon (which is a module that is built by vmware for the host kernel), but I guess those where mostly added by the maintanier of vmware-any-any (a patch to enable better 64bit support). Should the fixes go into that module, into some kind of LD_PRELOAD library (suggested in the thread at the vmware-site) or should these be in the kernel itself? There is a ioctl32 which I guess is the compat-layer in the kernel, but either the wrapping for this particular call is wrong (perhaps because it includes a structure?!), or entirely missing. Any ideas? Kind regards, Wolfgang

2 2

Re: [suse-amd64] amd64 (x86-64) support in cdrecord and cdrtools
by Andi Kleen 06 Sep '04

06 Sep '04

On Mon, Sep 06, 2004 at 10:17:40AM +0200, Joerg Schilling wrote: > Andi Kleen <ak(a)suse.de> wrote: > > > An 32bit version of cdrecord should work on x86-64 in theory. > > Correct for Solaris, not correct for Linux because of missing 64/32 bit support > in the drivers :-( You are wrong on this. We have pretty good 32bit emulation including most ioctls since many years (99+% coverage). In fact there are whole 64bit ports who usually run 32bit programs and 64bit only in special cases (like sparc64 or ppc64). > > Things that need to be planned take a long time on Linux. Solaris offers full > 64/34 bit support since 1997, let's see when Linux will come up with it.... The earliest copyrights in the 32bit emulation code of Linux (for sparc32/sparc64) date back to 1997 too. The x86-64 32bit emulation is only a few years old, but builds heavily on the work of other architectures who do this much longer and is also quite mature. -Andi

2 1

amd64 (x86-64) support in cdrecord and cdrtools
by Joel Wiramu Pauling 06 Sep '04

06 Sep '04

Hi Jörg, I just grabbed the latest sources from the ftp server. Seems that support for the x86-64 arch is missing. Any timeline for when this will be added? I'm currently using the Suse patched version (suse 9.1 is the most complete and useable amd64 environment unfortunately) because they came with the distro. But everytime I burn a DVD the process completes, but I am unable to read the media afterwards... I managed to burn 1 dvd with the media supplied by liteon, but that too had errors all over it. (But at least was readable). Any help on the situations of x86_64 support is appreciated. Kind regards Joel W New Zealand System Amble follows. -- Linux rincewind 2.6.8.1-mm4 #7 Sat Aug 28 17:01:43 NZST 2004 x86_64 x86_64 x86_64 GNU/Linux --- ide-cdrom version 4.61 --- LITE-ON DVDRW SOHW-832S --- Cdrecord-Clone-dvd 2.01a27 (x86_64-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version.

3 2

Microsoft natural multimedia keyboard
by rkimber＠ntlworld.com 06 Sep '04

06 Sep '04

I've acquired a Microsoft natural multimedia keyboard. What puzzles me is that some of the extra keys work but some don't. xev cannot detect anything from "My Pictures", "My Music", "Messenger", "Log Off", or "Sleep", though it can detect all the others. Is there some technical reason why these particular keys are not detected? On the face of it, I would expect that if "My Documents" is detected, then "My Pictures" should also be. Surely the key generates a scan code? Or is there a better program than xev for detecting what happens? It works OK in Windows, so presumably some code is generated by a keypress. - Richard. -- Richard Kimber http://www.psr.keele.ac.uk/

2 1

Re: [suse-amd64] Creating SuSE RPMS
by Marcin Kurc 02 Sep '04

02 Sep '04

try this http://www.rpm.org/max-rpm/ also, you might want to install some *.src.rpm, take the spec file and modify to your needs. The spec file will be in /usr/src/packages/SPECS thanks, Marcin Kurc Linux Impact Team Novell, Inc (973) 493-6235 >>>Raimund Eimann <raimund(a)cs.auckland.ac.nz> 09/02/04 2:02 pm >>> Hi, can anyone give me a short intro on how to build a SuSE RPM for a package that I have only as tarball or point me to some docs about this? As far as I understand I need to write a SPEC file for this, but I couldn't find anything about typical SuSE SPEC file settings... Cheers, Raimund -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

2 1

Missing .la files
by Raimund Eimann 02 Sep '04

02 Sep '04

Hello! Compiling packages from scratch on my new Athlon64 is a quite annoying and cumbersome process! My latest problem is knetload. First my Qt-library was not found, so I patched this problem with "--with-qt-libraries=$QTDIR/lib64". The next problem was a missing "/usr/lib/libart_lgpl_2.la" file that I fixed(?) by copying it over from my old SuSE 9.1 32 bit installation. The latest pain with this package is "cannot find the library `/usr/lib/qt3/lib/libqt-mt.la'" and now I'm out of ideas. I actually have got that file, but in /usr/lib/qt3/lib64/libqt-mt.la. When I tell the configure script explicitly to take Qt from QTDIR/lib64, why does it still look for the libqt-mt.la file in /usr/lib/qt3/lib/? Any help would be appreciated. Cheers, Raimund make[2]: Entering directory `/home/raimund/knetload-2.3/knetload' /bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -o knetload -R /opt/kde3/lib -R /usr/lib/qt3/lib64 -R /usr/X11R6/lib64 -L/usr/X11R6/lib64 -L/usr/lib/qt3/lib64 -L/opt/kde3/lib devicedialog.o icontoggleaction.o knetdock.o knetload.o knetproc.o main.o scaledialog.o speeddialog.o statdock.o statpopup.o -lkdeui libtool: link: cannot find the library `/usr/lib/qt3/lib/libqt-mt.la' make[2]: *** [knetload] Error 1 make[2]: Leaving directory `/home/raimund/knetload-2.3/knetload' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/raimund/knetload-2.3' make: *** [all] Error 2

2 1

USB and FireWire drives with 2.6.5-7.108-default
by Raimund Eimann 02 Sep '04

02 Sep '04

Hi, did anyone else notice that USB and FireWire drives are no longer getting automounted with kernel 2.6.5-7.108-default? I didn't have this problem with kernel 2.6.5-7.104-default... Cheers, Raimund

1 0

Ignoring Updates
by Steve 02 Sep '04

02 Sep '04

Is there a way to tell SuSE watcher to ignore an update and not turn red for it? I really don't want to go through the hassle of downloading the latest Kernel update, downloading it's source, and recompiling my Nvidia drivers. Thanks, -- Steve <steve(a)swthomas.org> --- [This E-mail scanned for viruses]

4 3

Quanta Plus
by Örn Hansen 02 Sep '04

02 Sep '04

I've noticed one odd thing about Quanta Plus, that is available through apt4suse download. There is no support for editing Unicode files, it will always revert to them as latin, no matter what the locale is. Any way to change this behaviour?

3 2

ieee1394 driver broken(?)
by Yoriaki FUJIMORI 02 Sep '04

02 Sep '04

Dear listers, This is just a note. I tried to use ieee1394 cameras with gnomemeeting(GM) on suse 9.1, both i386 and amd64. It does not work properly. The following is a part of dmesg: video1394_0: Waking up iso dma ctx=0 video1394_0: Waking up iso dma ctx=0 ohci1394: fw-host0: Unrecoverable error! ohci1394: fw-host0: Iso Recv 0 Context died: ctrl[8000884e] cmdptr[028db260] match[f0000100] video1394_0: On release: Iso receive context 0 stop listening on channel 0 mask: 0000000000000001 usage: 0000000000000000 video1394_0: Iso receive DMA: 4 buffers of size 155648 allocated for a frame size 153600, each with 39 prgs video1394_0: iso context 0 listen on channel 0 video1394_0: Waking up iso dma ctx=0 video1394_0: Iso context 0 stop talking on channel 0 mask: 0000000000000001 usage: 0000000000000000 video1394_0: Iso receive DMA: 4 buffers of size 155648 allocated for a frame size 153600, each with 39 prgs video1394_0: iso context 0 listen on channel 0 video1394_0: Waking up iso dma ctx=0 video1394_0: Waking up iso dma ctx=0 video1394_0: Waking up iso dma ctx=0 ohci1394: fw-host0: Unrecoverable error! ohci1394: fw-host0: Iso Recv 0 Context died: ctrl[8000884e] cmdptr[0d8ce260] match[f0000100] (Some repeated messages are removed.) The same sympthom can be observed if kernel is updated to recent one, on both SuSE 9.0 and 9.1, i386 and amd64. The stock kernel on 9.0DVD worked, if my memory is correct, at least for i386. I wonder if somebody is using firewire tools, such as external hardisk units, on kernel 2.6. Thanks for your attention. yoriaki fujimori

1 0

APM on AMD64
by Whomparr 01 Sep '04

01 Sep '04

I recently upgraded to a AMD64 machine and install Suse 9.1 on this. However it doesn't seem that the install has correctly configured APM in my kernel, even though according to YAST the linux-atm package is installed. As a result my modem will not work as it's using pppoatm. What do I need to do to get ATM to work ? Does anyone currently have atm / pppoatm working on a AMD64 / kernel 2.6 machine ? Hope you can help.

1 0

Re: [suse-amd64] Nvidia driver question
by Paul C. Leopardi 01 Sep '04

01 Sep '04

Hi. See my response below. Best regards. On Wednesday 01 September 2004 05:34, Tom Nielsen wrote: > This is my first post to this group. Normally I bug the folks on the 32-bit > list. > > I just got a Sun W110z and installed 9.1 Pro on it. I looked at my Sun CD > that came with the machine and there's an Nvidia driver that was made for > Linux. Should I use this? I gather I should since it's for the card that > came with machine. I am not familiar with this machine or the driver. Do you mean an nVIDIA nForce* chipset driver or an nVIDIA GeForce* graphics card driver? Does "made for Linux" mean "made for the 2.6 kernel"? Is it a 64 bit binary? Is there any difference between the driver and what you can find on the nVIDIA web site - which should be more up-to-date?

2 1