openSUSE AMD64 January 2005

amd64@lists.opensuse.org

105 participants
105 discussions

MSI K8N Neo Platinum -- USB hotplugging
by Martin Schröder 07 Apr '05

07 Apr '05

Hi, we have two machines with MSI K8N Neo Platinum mainboards and USB hotplugging doesn't work. Has anybody got it working with 9.2? Best regards Martin -- Martin Schröder, ms(a)artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de

5 4

Illegal format hash table (ispell with german, french, spanish, ...)
by Reiner Steib 31 Mar '05

31 Mar '05

2 4

AW: [suse-amd64] mjpegtools
by Graf, Markus 17 Mar '05

17 Mar '05

Hi Mike the answer is : recompile with -fPIC put this option (-fPIC) in every Makefile of this project as a CFLAG . In german you find the docu http://www.pseudonym.org/schauen.html, than look for mjpeg on this page. CU Markus > -----Ursprüngliche Nachricht----- > Von: Michael Steinhauser [mailto:mistr.rot@web.de] > Gesendet am: Montag, 4. Oktober 2004 21:04 > An: Mike.Philipp(a)passau.netsurf.de > Cc: suse-amd64(a)suse.com > Betreff: Re: [suse-amd64] mjpegtools > > Mike Philipp wrote: > > >Hi All, > > > >could anyone compile and link mjpegtools-1.6.2 on the AMD! > >I've tried it for three days now, but it doesn't work. > >Does anybody has a src.rpm or an already compiled x86_64 > >(with mpeg2enc)??? > > > >Thanx in advance > > Mike > > > > > > > Hi, > I tried it too and asked at mjpeg-users list. > Here are the postings: > I tried to install mjpegtools 1.6.2 on Suse 9.1 x86_64. I ran > configure > with --enable-libsuffix=64 and got no errors. > When I typed make, the following error was reportet: > /snap > > lib/x86_64-suse-linux/3.3.3/crtendS.o > /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib64/crtn.o > -Wl,-soname -Wl,libmplex2-1.6.so.0 -o .libs/libmplex2-1.6.so.0.2.2 > /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64- > suse-linux/bin/ld: > ../utils/libmjpegutils.a(mjpeg_logging.o): relocation R_X86_64_32 can > not be used when making a shared object; recompile with -fPIC > ../utils/libmjpegutils.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > make[2]: *** [libmplex2.la] Fehler 1 > make[2]: Leaving directory > `/SHARE/Linux/RPMS/SRC/mjpegtools-1.6.2/mplex' > make[1]: *** [all-recursive] Fehler 1 > make[1]: Leaving directory `/SHARE/Linux/RPMS/SRC/mjpegtools-1.6.2' > make: *** [all] Fehler 2 > > Can anyone help? > > the answer: > > Hi, > > On Fri, 2004-09-03 at 10:18, Michael Steinhauser wrote: > > >> I tried to install mjpegtools 1.6.2 on Suse 9.1 x86_64. > > > > > [..] > > >> ../utils/libmjpegutils.a(mjpeg_logging.o): relocation > R_X86_64_32 can > >> not be used when making a shared object; recompile with -fPIC > >> ../utils/libmjpegutils.a: could not read symbols: Bad value > > > > > > This should be corrected in CVS for some time already. > > Ronald > > So i downloaded the latest CVS-version, did a ./configure > --prefix=/usr --libdir=/usr/lib64 --enable-libsuffix=64 > --sysconfdir=/etc --with-x --x-includes=/usr/X11R6/include > --x-libraries=/usr/X11R6/lib64 --with-gnu-ld > --without-libquicktime --with-gtk-prefix=/opt/gnome and it > compiled with no errors. After a checkinstall, where i had to > change some settings (version was there to often) i had a > installable rpm. It installed without errors, but i did not > try it till now. > > > > > > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com > >

3 2

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

SUSE 9.2 on Simics 2.0
by Robert Schiele 16 Feb '05

16 Feb '05

Hello. Did someone succeed in installing the 64 bit version of SUSE Linux 9.2 on Simics 2.0? For me linuxrc segfaults immediately after being started from the installation media. Is Simics just too broken for installing SUSE Linux 9.2 or is it just me being to stupid writing a working configuration file? Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de

4 7

SATA, K8V Deluxe MB and SUSE 9.2
by Mitch Martinez 03 Feb '05

03 Feb '05

Has any one had any luck in getting a ASUS K8V Deluxe MB and SUSE 9.2 to see an IDE drive on the built in SATA bus? I've been told that it's possible but I haven't been able to see one of my drives on the bus, I've looked for a scsi device (no luck), Here's my Sysinfo: MB: ASUS K8V Deluxe CPU: AMD Athlon(tm) 64 Processor 3200+ MEM: 1540984 kB VID: G-Force FX5900 128 MB MON: ViewSonic P810 OS: SUSE 9.2 Pro CPU:

3 5

Re: Segfault in SUSE 9.1 AMD64 & postfix
by Emiliano Sutil 31 Jan '05

31 Jan '05

I have no solution to that problem. I see that this makes that the wrong mails stay in the queue for ever until I delete them manually. I have several machines with suse 9.1 i586 and this problem does not happen, so I think that is a problem with the AMD64 implementation of the queue manager. Somebtoy have any idea? On Tue, 25 Jan 2005 11:27:42 -0600, Tim Smith <tim(a)somethingcool.com> wrote: > I saw your post in suse-amd64 newsgroup about this problem. > > I am having the same problem, here is a snippet from my logfile: > > Jan 5 14:04:33 bulldogs kernel: smtp[27470]: segfault at > 0000000000000000 rip 000000000042d14a rsp 0000007fbffff4c0 error 4 > > This has been going on for a while, but things appear to work fine. I > noticed there was no reply to your post.. Did you ever figure this one > out? I use postfix & mailman, and my 200 users mostly use Squirrelmail > for their email client. > > Thanks in advance! > > Tim Smith > >

3 6

PCMCIA + amd64 + 9.2 = still not working, and a workaround
by Matt T. 31 Jan '05

31 Jan '05

There had been already some discussions about PCMCIA with SuSE for amd64 on AMD64 notebooks. Andreas reported a few days ago about the test results of his colleagues at SuSE, who gave the impression that it mostly works. After the problems with PCMCIA and 9.1 amd64, I did take this as a good sign for 9.2, apparently the problems are under control. Well, they are not. It does not work out of the box. Andreas, I assume you read this sooner or later. You might want to give this to your notebook guys. There are 2 problems to fix. These are clearly problems of the 64 bit SuSE ! 1) The /etc/pcmcia/config.opts is correct for 32 bit hardware, and does not work for (most, I assume even all) 64 bit hardware. Modifying it is not a big problem for the linux gurus, but certainly nothing you want a normal user, even a power user, to do. Yast should do it during the installation. Sooner or later you piss of every user who installs SuSE 64 on amd64 notebook, because sooner or later everyone will want to use a PCMCIA card. As far as I can see it, it does never work out of tho box, never! 2) Many cards do not get recognized correctly. This was a kernel issue of kernels < 2.6.7, but the problem does exist still or again with the recent 9.2 kernels. Please see the example documented here. Here are my test results, and the workaround I found for the cards which get falsely recognized as memory cards: ----------------------------------------------- I tested with the Axen / Sagem GPRS card. This card does work fine, out of the box, with 32 bit SuSE 9.0, 9.1 and 9.2 on a 32 bit notebook (Fujitsu lifebook). The same card does not work on a amd64 notebook (HP pavillion zv5188EA) with SuSE 9.1 and 9.2 out of the box. I got it to work by 1. modifying the file /etc/pcmcia/config.opts (memory range and ports) according to the output of lspci -vv 2. installing a kernel > 2.6.7. First a vanilla 2.6.8, then the SuSE kernels, once they reached 2.6.8 It still worked after upgrading the 9.1 to 9.2. Then I saw the message of Pascal here on this list a few weeks ago, that his modem card worked for him now by using the 9.2 kernel and the 9.2 pcmcia. At the same time my upgraded box worked for this card, but there was another problem, the ultrafast boot of 9.1 had changed to a snail slow boot after upgrading to 9.2. X got started, and crashed, and got started again, but then I had sometimes a full keyboard and sometims it reacted to just half of the keys.) To avoid wasting time to debug the upgrade, I did a clean new install of 9.2. Result: - The boot process was normal again (but not as lightning fast as before with 9.1) - The PCMCIA card did NOT work anymore, even after modifying the file /etc/pcmcia/config.opts (memory range and ports) according to the output of lspci -vv I tried updating the PCMCIA module and the kernel, still nothing. I tried the 2.6.10 kernel of the day, still nothing. The card does not get recognized at all, but identified as a memory card. See the log output of dmesg, /var/log/messages etc. below: memory_cs gets called instead of serial_cs. Then I had an idea for a workaround, see below, and it worked. It's certainly not a fix, but just a dirty workaround. I would appreciate any ideas or comments on it, may be there is a better solution. I will do further testing with different cards (sierra wireless gprs and a modem card). Regards, Matt ------------------ The configuration and log files: /var/log/messages (before modifying /etc/pcmcia/config) ===============/var/log/messages begin ================ Jan 28 03:50:21 linux cardmgr[4143]: socket 0: Anonymous Memory Jan 28 03:50:21 linux kernel: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xfffff Jan 28 03:50:21 linux kernel: cs: memory probe 0x60000000-0x60ffffff: excluding0x60000000-0x60ffffff Jan 28 03:50:21 linux kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding0xa0000000-0xa0ffffff Jan 28 03:50:21 linux kernel: cs: memory probe 0xe0c00000-0xe0fff000: excluding0xe0c00000-0xe101dfff Jan 28 03:50:21 linux kernel: cs: unable to map card memory! Jan 28 03:50:21 linux last message repeated 5 times Jan 28 03:50:21 linux cardmgr[4143]: executing: 'modprobe memory_cs 2>&1' Jan 28 03:50:21 linux cardmgr[4143]: + FATAL: Module memory_cs not found. Jan 28 03:50:21 linux cardmgr[4143]: modprobe exited with status 1 Jan 28 03:50:21 linux cardmgr[4143]: module /lib/modules/2.6.8-24.10-default/pcmcia/memory_cs.o not available Jan 28 03:50:21 linux cardmgr[4143]: bind 'memory_cs' to socket 0 failed: Invalid argument ===============/var/log/messages end ================ dmesg (before modifying /etc/pcmcia/config): =================================================== cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xfffff cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff cs: memory probe 0xe0c00000-0xe0fff000: excluding 0xe0c00000-0xe101dfff cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! ================== dmesg end ====================== cardctl ident : no product info available =================================================== uname -r : 2.6.8-24.10-default identical result with uname -r : 2.6.8-24.11-default =================================================== rpm -q pcmcia : pcmcia-3.2.8-3 identical result with pcmcia-3.2.8-3.1 =================================================== Conclusion: 1) Obviously the card does not get identified correctly, but classified as "Anonymous Memory" (see /var/log/messages) 2) According to /etc/pcmcia/config a card "Anonymous Memory" gets bound to "memory_cs". Which is BS, because "memory_cs" does not get used anymore in 2.6 kernels. It simply does not exist anymore. (Why is /etc/pcmcia/config in SuSE 9.2 not corrected?) 3) A dirty workaround comes to my mind: memory_cs is BS anyway, and I'm not using memory cards at the moment, so why not changing "memory_cs" to "serial_cs" for "Anonymous Memory" in /etc/pcmcia/config. Changing /etc/pcmcia/config ======================================== card "Anonymous Memory" anonymous bind "memory_cs" -------- change to > ------------ card "Anonymous Memory" anonymous bind "serial_cs" ======================================== After restarting cardmanager (killall cardmgr / cardmgr) and resinserting the card NOW it works, the card gets assigned /dev/ttyS4 and I can query it with minicom (ati / ati1 etc.) /var/log/messages and dmesg look better also: /var/log/messages (after modifying /etc/pcmcia/config): ===============/var/log/messages begin ================ Jan 31 23:08:00 linux cardmgr[5791]: watching 2 sockets Jan 31 23:08:04 linux cardmgr[5792]: socket 0: Serial or Modem .... Jan 31 23:08:05 linux kernel: ttyS4 at I/O 0x7100 (irq = 11) is a 16C950/954 ===============/var/log/messages end ================ dmesg: =================================================== ttyS4 at I/O 0x7100 (irq = 11) is a 16C950/954 ================== dmesg end ====================== the card even gets recognized now: cardctl ident : ============================================= Socket 0: product info: "GPRS", "Modem", "", "" manfid: 0x0279, 0x950b function: 2 (serial) =============================================

1 0

64bit Suse 9.2 Personal (download version)
by ozymandias＠pt-cruiser.net 31 Jan '05

31 Jan '05

Hi, I am currently running the 64bit version of 9.1 Professional, and wanted to try out the new version before committing to buying a professional version, or even if I needed the professional version. I downloaded the DVD, and the hash checked OK. The system boots off the DVD, but will not detect an installed HDD. The HDD is a Serial ATA running in a Shuttle SN95G5. I had zero problems installing 9.1 onto the HDD, nor Windows XP. So I am curious as to why it is not detecting the HDD now. A quick look does have the SATA controller detected. Help, this has me puzzled. Lance

2 1

e2fsck of the root filesystem
by rkimber＠ntlworld.com 29 Jan '05

29 Jan '05

Theodore Ts'o has said on the ext3 list that:- "The real right thing would be to have the e2fsck of the root filesystem happen out of the initial ramdisk, but no distribution I know of does this at this point." Maybe this is something that Suse could consider. - Richard -- Richard Kimber http://www.psr.keele.ac.uk/

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE AMD64 January 2005