January 2005 - openSUSE AMD64 - openSUSE Mailing Lists

AMD64 notebook PCMCIA controller supported ?
by wlindenbauer＠t-online.de 20 Jan '05

20 Jan '05

Hello LinuxUsers is the PCMCIA-controller O2-Micro Modell 711 supported in 64bit-Linux Suse-9.2 ? In the Amilio A7640 notebook this chip is used for PCMCIA and the card-reader. Do other AMD64 notebooks also use this chip for PCMCIA ?? Also in Acer Aspire 1523 WMLi ? Best regards Wigbert

1 0

compile php5 with odbtp
by ray.carlino＠comcast.net 20 Jan '05

20 Jan '05

I am trying to compile php5 using apxs2 and odbtp but it fails everytime.. I get a linker error, I have read posts about users trying different switches but nothing worked. So the bottom line is I can't get libphp5.so created.. Ray

2 1

imap server help...
by Tom Nielsen 20 Jan '05

20 Jan '05

Not sure if I should post this here, but I'm stuck! I'm running SLES 9 with cyrus-imap, amavis-new, postfix, spamassassin, and fetchmail. In /var/log/mail I keep seeing these messages: Jan 19 16:21:52 mailserver2 postfix/qmgr[2838]: 0BC9F1A7D0: from=<virusalert(a)example.com>, size=3406, nrcpt=1 (queue ac tive) Jan 19 16:21:52 mailserver2 postfix/qmgr[2838]: 609831754B: from=<virusalert(a)example.com>, size=2717, nrcpt=1 (queue ac tive) Jan 19 16:22:22 mailserver2 postfix/smtp[4811]: connect to example.com[192.0.34.166]: Connection timed out (port 25) Jan 19 16:22:22 mailserver2 postfix/smtp[4812]: connect to example.com[192.0.34.166]: Connection timed out (port 25) Jan 19 16:22:22 mailserver2 postfix/smtp[4811]: 0BC9F1A7D0: to=<virusalert(a)example.com>, relay=none, delay=257134, stat us=deferred (connect to example.com[192.0.34.166]: Connection timed out) Jan 19 16:22:22 mailserver2 postfix/smtp[4812]: 609831754B: to=<virusalert(a)example.com>, relay=none, delay=348826, stat us=deferred (connect to example.com[192.0.34.166]: Connection timed out) I cannot figure out where this is coming from. I have no network with that IP. Mine is 192.168... Also, I can't figure out where to change the example.com or virusalert(a)example.com is configured. I've looked in all the config files and can find it. I'm sure I missed something. All mail gets sent and delivered, I just would like to get rid of this so I can rest. Thanks, Tom -- Tom Nielsen Neuro Logic Systems 1.805.389.5435 x18 www.neuro-logic.com

2 1

[suse-amd64] GOOD NEWS : PCMCIA modem card works now fine !!!
by patheve2 19 Jan '05

19 Jan '05

Well, I tested the pcmcia package 3.2.8 under SuSE 9.0 AMD64 => bad results So I had to downgrade this package into the original one : 3.2.4. I took the config.opts file (modified) of my SuSE 9.1. And the Com One modem card works !!! So, it seems that WinXP can have a benefit for PCMCIA cards under linux :-D : the config.opts file is base on some data given by WinXP. But have a look on the secondary PCI bridge with lspci -vv for the memory. Hereafter this file. And under my SuSE 9.1, my Netgear FA411 network card is well recognized and mounted as eth1 (ifconfig). Not the case under SuSE 9.0. My Hayes Optima 288 modem card does not work under the two SuSEs Regards Pascal # # Local PCMCIA Configuration File # #---------------------------------------------------------------------- # # System resources available for PCMCIA cards # # NOTE: these settings have no effect on resources assigned to a # CardBus bridge device itself; this file only affects resources # assigned to cards. Also, interrupt settings here will only affect # ISA bus interrupts assigned to 16-bit cards. PCI interrupts # generally can't be reconfigured. # # With the kernel PCMCIA subsystem, these settings also have no effect # at all on resources used for 32-bit CardBus cards. Those are set by # the PCI hotplug subsystem. # # This are the official ports to use from pcmcia-cs, but ... # include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff # ... ports 0x810-0x81f hurt on some DELL machines and ... # ... ports 0x3b0-0x3df hurt on some FSC machines. #include port 0x100-0x4ff #include port 0x800-0x8ff #include port 0xc00-0xcff #include port 0x3000-0x7fff # according to lspci -vv for Cardbus #include port 0x0000-0xafff # #include port 0xb000-0xbfff #include port 0xc000-0xcfff # avec ceci, carte reseau FA411 montee en eth1 #include port 0xd000-0xffff # d'apres WinXP include port 0xcc00-0xccff include port 0xd000-0xd0ff include port 0xd400-0xd4ff include port 0xdc00-0xdcff #include port 0xb000-0xb7ff #include port 0xb800-0xbfff #include port 0xc000-0xc7ff #include port 0xc800-0xcfff # according to lspci -vv for Cardbus #include memory 0xf8a00000-0xfd1ff000 # plage memoire relative au pont PCI (secondary=02) include memory 0xfa200000-0xfeafcfff # d'apres WinXP : #include 0xfa200000-0xfa200fff #include 0xfb200000-0xfd1fffff #include 0xfd200000-0xfd200fff #include 0xfdaf5000-0xfeaf4fff #include 0xfeaf5000-0xfeaf5fff #include 0xfeaf6000-0xfeaf6fff #include 0xfeaf7000-0xfeaf7fff #include 0xfeafc000-0xfeafcfff # decomposition en 2 => ne marche pas : carte non visible #include memory 0xf8a00000-0xfa1ff000 #include memory 0xfba00000-0xfd1ff000 # decomposition en 4 => ne marche pas : carte non visible #include memory 0xf8a00000-0xf95ff000 #include memory 0xf9600000-0xfa1ff000 #include memory 0xfba00000-0xfc5ff000 #include memory 0xfc600000-0xfd1ff000 # # High port numbers do not always work... # include port 0x1000-0x17ff # Extra port range for IBM Token Ring #include port 0xa00-0xaff # Resources we should not use, even if they appear to be available # First built-in serial port exclude irq 4 # Second built-in serial port #exclude irq 3 # First built-in parallel port exclude irq 7

1 0

GOOD NEWS : PCMCIA modem card works now fine !!!
by patheve2 19 Jan '05

19 Jan '05

Hello all If you well remember the previous mails about PCMCIA cards, there were a lot of problems. And this evening I could solve this one for modem card under SuSE 9.1 AMD64. For that, take the last kernel coming from SuSE 9.2 but updated (2.6.8-24.10) AND the pcmcia package 3.2.8 of SuSE 9.2 (instead of 3.2.7 of SuSE 9.1). Don't forget to configure the config.opts file according to "lspci -vv". And now, my Com One Platinium MC227 v90 card works very well. The device becomes ttyS4 when the card is inserted and the symbolic link "modem -> ttyS4" is well created. My laptop is an Asus L5DF. So, it should work with a full SuSE 9.2. And probably under SuSE 9.0 AMD64 (kernel 2.4.21-xxx), the problem can be solved with the above pcmcia package. I will try as soon as possible. Regards Pascal

1 0

Segmentation fault with "which"
by Marc Wuilleret 19 Jan '05

19 Jan '05

Hello, I have just upgraded my AMD 64 XP system to Suse 9.2 and I have the following problem: The program "/usr/bin/which" produces a Segmentation fault. I tried to rebuild the util-linux package from the sources, During the build of "which", the following messages are generated: make[2]: Entering directory `/usr/src/packages/BUILD/which-2.13' gcc -DHAVE_CONFIG_H -I. -I. -I. -O2 -g -c getopt.c gcc -DHAVE_CONFIG_H -I. -I. -I. -O2 -g -c getopt1.c gcc -DHAVE_CONFIG_H -I. -I. -I. -O2 -g -c bash.c gcc -DHAVE_CONFIG_H -I. -I. -I. -O2 -g -c which.c gcc -O2 -g -o which getopt.o getopt1.o bash.o which.o ./tilde/libtilde.a /usr/lib/libiberty.a /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.4/../../../../x86_64-suse-linux/bin/ld: warning: i386 architecture of input file `/usr/lib/libiberty.a(xmalloc.o)' is incompatible with i386:x86-64 output /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.4/../../../../x86_64-suse-linux/bin/ld: warning: i386 architecture of input file `/usr/lib/libiberty.a(xexit.o)' is incompatible with i386:x86-64 output make[2]: Leaving directory `/usr/src/packages/BUILD/which-2.13' I suspect that these warnings about libiberty are the source of the problem, but I am not sure about how to fix that. Best regards, Marc Wuilleret.

3 3

reading windows chm files
by Mark Creamer 19 Jan '05

19 Jan '05

Is there a tool available to be able to open windows compiled help files (chm) in Linux, other than running a vmware windows system?

3 2

ATI fglrx driver update +what about DVI
by Arjen Runsink 19 Jan '05

19 Jan '05

Hi, ATI posted an update for their drivers yesterday. It now also includes xorg and x86_64! SuSE has made some special rpms and a How-To for this. But for x86_64 they have hidden below i386... go figure... On my 9200 SE I can only get VGA to work. If anyone knows how I can get DVI to work, please give me a pointer. ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/X/ATI… Or see your local mirror Regards! Arjen

2 3

libhistory.so 32bit on SuSE9.2
by Stephen Williams 18 Jan '05

18 Jan '05

On a 64bit machine, I compile Icarus Verilog vvp for 64bit *and* 32bit, the latter for compatibility with 32bit vpi code. But I cannot seem to find a 32bit libhistory.so? I think I remember having to hunt for it on SLES8 too. Why wasn't it just isntalled? The 64bit libhistory.so is present and functional. -- Steve Williams "The woods are lovely, dark and deep. steve at .......... But I have promises to keep, http://www........... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."

3 5

Bad RAM or software issue
by Torsten Wolf 18 Jan '05

18 Jan '05

Hi, we have problems with the stability of our Opteron Cluster running with SuSE 9.1. From time to time the kswapd processes on the master node run with 99% on one of the 2 cpus available - even though almost no swap space is used. Jobs submitted by OpenPBS stop at random times especially when data is transferred (via nfs). Sometimes dmesg gives centaur[31528]: segfault at 0000000000000000 rip 000000000807ca86 rsp 00000000ffffcfd8 error 4 centaur[761]: segfault at 0000000000000000 rip 000000000807ca86 rsp 00000000ffffcfd8 error 4 hybconvert[5561]: segfault at 0000002a96b5b000 rip 0000002a95a75336 rsp 0000007fbfffb240 error 4 hybconvert[5562]: segfault at 0000002a96e50000 rip 0000002a95a75336 rsp 0000007fbfffb240 error 4 hybconvert[5666]: segfault at 0000002a96b14000 rip 0000002a95a75336 rsp 0000007fbfffb240 error 4 hybconvert[5833]: segfault at 0000002a98eb6000 rip 0000002a95a75336 rsp 0000007fbfffb240 error 4 igesconv[2804]: segfault at 0000000000000120 rip 0000000008093d40 rsp 00000000ffffca58 error 4 hybconvert[16799]: segfault at 0000002a973cc000 rip 0000002a95a75336 rsp 0000007fbfffb1c0 error 4 hybconvert[23026]: segfault at 0000002aa88c5000 rip 0000002a95a75336 rsp 0000007fbfffb1c0 error 4 We noticed that the numbers following rip and rsp are equal for some processes. What does all this indicate? Is bad memmory causing such problems or might this be a kernel issue? Any help is greatly appreciated! Regards, Torsten

1 0