November 2004 - openSUSE AMD64 - openSUSE Mailing Lists

need help in converting autoconf project to x86_64
by Yasunari Tosa 10 Nov '04

10 Nov '04

Hi, I have a autoconf/automake/libtool project with libraries, which works for 32 bit processor. How can I convert this to a x86_64-aware project? That is, when compiled on AMD64, it will compile for 64 bit and install libs in lib64 directory. when compiled on 32bit linux, it will compile for 32 bit and install libs in lib directory. I have seen the configure option "--enable-libsuffix=64" on this list. I don't see how to use this option to rewrite "configure.ac" and "Makefile.am". A sample "configure.ac" and "Makefile.am" would be appreciated. Tosa -- Yasunari Tosa, Ph.D. Email: tosa(a)nmr.mgh.harvard.edu NMR Ctr, Mass. General Hospital TEL: 617-726-4050 Building 149, 13th Street Charlestown, MA 02129 USA

3 3

nedit in 9.1
by Chuck Gibke 10 Nov '04

10 Nov '04

Howdy, I have two boxes running Athlon64s - one with 9.0 (co-located) and the other with 9.1 (home). One utility I have been using on Suse 9.0, Red Hat (various versions), and SGI IRIX is "nedit". It was included in the installation of 9.0 but does not seem to exist in 9.1 (not sure about 9.2). Just wondering "why?" and if there is a Suse RPM that would install on 9.1... Thanks. ......Chuck

7 8

kernel 2.6.8, PCMCIA 16 bits modem card : problem solved or not ?
by patheve2 10 Nov '04

10 Nov '04

Hello all My previous mails were sent during last August about this problem with PCMCIA card and Linux 2.6.5. I could hope that the kernel 2.6.8 should solve it, as it was written by some users. Hereafter my proble 0== my laptop, the PCMCIA cards and linux system : Asus L5800DF Athlon64 socket 754 - modem PCMCIA Platinum Card MC227 v90 of ComOne (should work fine according to tuxmobil.org) - ethernet card Netgear FA411 (a 16 bits one) SuSE Linux 9.1 AMD64 with the kernel of the SuSE 9.2 AMD64, a 2.6.8-24-3 (the previous one : a 2.6.5-7-111) 1== what says linux during boot without PCMCIA card (dmesg) : Linux Kernel Card Services options: [pci] [cardbus] [pm] ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9 Yenta: CardBus bridge found at 0000:02:01.0 [1043:1854] Yenta: ISA IRQ mask 0x0098, PCI irq 9 Socket status: 30000006 ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11 Yenta: CardBus bridge found at 0000:02:01.1 [1043:1854] Yenta: ISA IRQ mask 0x0098, PCI irq 11 Socket status: 30000006 2== details about cardbus with "lspci -vv" : 0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) Subsystem: Asustek Computer, Inc.: Unknown device 1854 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 168 Interrupt: pin A routed to IRQ 9 Region 0: Memory at fd200000 (32-bit, non-prefetchable) Bus: primary=02, secondary=03, subordinate=06, sec-latency=176 Memory window 0: fba00000-fc5ff000 (prefetchable) Memory window 1: fc600000-fd1ff000 I/O window 0: 0000c000-0000c7ff I/O window 1: 0000c800-0000cfff BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 0000:02:01.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) Subsystem: Asustek Computer, Inc.: Unknown device 1854 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 168 Interrupt: pin B routed to IRQ 11 Region 0: Memory at fa200000 (32-bit, non-prefetchable) Bus: primary=02, secondary=07, subordinate=0a, sec-latency=176 Memory window 0: f8a00000-f95ff000 (prefetchable) Memory window 1: f9600000-fa1ff000 I/O window 0: 0000b000-0000b7ff I/O window 1: 0000b800-0000bfff BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 3== the config.opts file in /etc/pcmcia (partial view) # 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-0x1000 include port 0xb000-0xcfff # include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff include memory 0x60000000-0x60ffffff include memory 0xe0100000-0xe17fffff # according to lspci -vv for Cardbus include memory 0xf8a00000-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 4== with the inserted network card FA411 : --- cardctl status Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card --- cardctl ident Socket 0: product info: "NETGEAR", "FA411", "Fast Ethernet" manfid: 0x0149, 0x0411 function: 6 (network) Socket 1: no product info available --- cardctl info PRODID_1="NETGEAR" PRODID_2="FA411" PRODID_3="Fast Ethernet" PRODID_4="" MANFID=0149,0411 FUNCID=6 PRODID_1="" PRODID_2="" PRODID_3="" PRODID_4="" MANFID=0000,0000 FUNCID=255 ===> it seems OK but nothing else done with this card. Wiith Yast, the NetGear FA411 is well seen for configuration. A good new :-) ? 4== with the inserted modem card : --- dmesg serial_cs: no usable port range found, giving up serial_cs: RequestIO: No more items ====> no such info with last kernel 2.6.5-7-111 --- in /dev/ a symbolic link /dev/modem is done with /dev/ttyS2, instead of /dev/cua2 with kernel 2.6.5-7-111 NB : ttyS0 is serial port, ttyS1 is the irda port --- cardctl status Socket 0: 5V 16-bit PC Card function 0: [ready], [wp] Socket 1: no card --- cardctl ident Socket 0: product info: "PCMCIA CARD MEMBER", "FM56R-NCTV2", "021", "A" manfid: 0x0013, 0x0000 function: 2 (serial) Socket 1: no product info available --- cardctl info PRODID_1="PCMCIA CARD MEMBER" PRODID_2="FM56R-NCTV2" PRODID_3="021" PRODID_4="A" MANFID=0013,0000 FUNCID=2 PRODID_1="" PRODID_2="" PRODID_3="" PRODID_4="" MANFID=0000,0000 FUNCID=255 5== with kppp when a request is sent to the /dev/modem or /dev/ttyS2 with kppp, the answer is : modem is busy :-( So, I am probably doing something bad but I don't see what. If you see what I have to do, thanks very much to write it me :-) Pascal

2 1

Firefox 1.0 release
by Ray Carlino 10 Nov '04

10 Nov '04

Anyone know when this will be ready for 9.2 x86_64? It fixes some problems I was having with a few sites and not looks great. -- Ray

1 0

Sound problem after upgrading to 9.2
by Gernot Bauer 09 Nov '04

09 Nov '04

Hi again, another problem I saw is, that after using 9.1 with no problems, the sound only cracks in the speakers when I do "Yast -> Hardware -> Sound -> Test". I seem to have a VT8233/A/8235/8237 AC97 Audio Controller (on-board). As I said, it used to work with Suse 9.1. I also tried deleting the soundcard and adding it again. No luck. :( Anybody have the same problems? Gery

2 2

Problem compiling firefox (glib-problem?)
by Gernot Bauer 09 Nov '04

09 Nov '04

Dear all, I tried to compile firefox (1.0rc2) but I keep getting error-messages like this: > GLib-ERROR **: could not reallocate 34359738368 bytes > aborting... Somebody from the firefox list told me to compile glib 1.2.10 again. I tried, but ./configure stops with: > checking host system type... Invalid configuration > `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized > checking build system type... Invalid configuration > `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized Can anybody give me a hint please, what's wrong here? Thank you, Gery

1 1

SATA on ASUS K8V Deluxe (SuSE 9.1)
by Pierre Patino 09 Nov '04

09 Nov '04

Hello Can anyone tell me a horror or happy story about SATA disks for this motherboard? Can I have a SATA drive as the only drive? The ASUS K8V documentation says it has a Promise R20378 Controller. TIA & Cheers

3 2

RE: [suse-amd64] SATA on ASUS K8V Deluxe (SuSE 9.1)
by Black, Alain 09 Nov '04

09 Nov '04

The story that I can tell you is that SuSE 9.1 support SATA straight out of the box. I loaded it up on my MSI NEO-2 based system and it loaded right onto the SATA drive which was the only drive in the system. My only suggestion would be to make sure the BIOS on your motherboard is current. -Alain -----Original Message----- From: Pierre Patino [mailto:pierre@cruzio.com] Sent: Tuesday, November 09, 2004 1:14 AM To: suse-amd64(a)suse.com Subject: [suse-amd64] SATA on ASUS K8V Deluxe (SuSE 9.1) Hello Can anyone tell me a horror or happy story about SATA disks for this motherboard? Can I have a SATA drive as the only drive? The ASUS K8V documentation says it has a Promise R20378 Controller. TIA & Cheers -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

2 1

wrong BIOS version
by Jose Luis Ricardo Chavez 09 Nov '04

09 Nov '04

Hello all, I excuse myself if the question I am about to ask is not directly related to SuSE AMD64. Many of you will laugh after hearing this but, here it goes... we flashed the BIOS of one of our opteron servers (Tyan S2882 mobo) but put the wrong BIOS image (S2885 instead of S2882) so the system is unable to boot. Is there a way to correct this problem without having to send the computer back to the provider in order to change the chip? Thanks in advance, - Jose Luis

2 1

NVidia Driver problem / X Crash
by john_ozarchuk＠goodyear.com 09 Nov '04

09 Nov '04

Hello, I am running Suse Linux Enterprise Server 9.0 for AMD64, with the FX1100 driver version 1.0-6111 on 12 machines at my company. The problem we have is that everytime users log out of the X environment, the entire thing crashes. The screen fills up with purple lines and fuzz. The only way to get out of this is to remotesh in and reboot, or to hit the Reset button on the machine. I have looked everywhere for people having these same problems, and nobody can seem to replicate this. I am not using any TV Out options, just a standard monitor configuration. I installed the Nvidia driver successfully, with the step by step instructions that Nvidia provided. Has anyone else seen this issue? Here is a chunk of the /var/log/messages at the time of this graphics crash. Again, this is only occuring when a user logs out of X. Especially common when the "root" user logs out. Thanks, John >>> Nov 4 14:22:27 rds023 kernel: ----------- [cut here ] --------- [please bite here ] --------- Nov 4 14:22:27 rds023 kernel: Kernel BUG at pageattr:106 Nov 4 14:22:27 rds023 kernel: invalid operand: 0000 [1] SMP Nov 4 14:22:27 rds023 kernel: CPU 1 Nov 4 14:22:27 rds023 kernel: Pid: 4950, comm: X Tainted: PF U 2.6.5-7.97-smp Nov 4 14:22:27 rds023 kernel: RIP: 0010:[<ffffffff801230b9>] <ffffffff801230b9>{change_page_attr+1225} Nov 4 14:22:27 rds023 kernel: RSP: 0018:000001007ccf1c08 EFLAGS: 00010282 Nov 4 14:22:27 rds023 kernel: RAX: 0000000000000df0 RBX: 8000000000000163 RCX: 8000000000000163 Nov 4 14:22:27 rds023 kernel: RDX: 0000010000009df0 RSI: 0000010000000000 RDI: 000001007fffe080 Nov 4 14:22:27 rds023 kernel: RBP: 0000000000009000 R08: 0000000000000001 R09: 0000000000000001 Nov 4 14:22:27 rds023 kernel: R10: 00000000000000cb R11: 0000000000003246 R12: 0000010037c1f000 Nov 4 14:22:27 rds023 kernel: R13: 0000010001c326c8 R14: 0000010000009df0 R15: 0000000000000000 Nov 4 14:22:27 rds023 kernel: FS: 0000002a95e094c0(0000) GS:ffffffff804e7e80(0000) knlGS:000000005585c9e0 Nov 4 14:22:27 rds023 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Nov 4 14:22:27 rds023 kernel: CR2: 000000000099e0a0 CR3: 0000000037e9c000 CR4: 00000000000006e0 Nov 4 14:22:27 rds023 kernel: Process X (pid: 4950, threadinfo 000001007ccf0000, task 00000100c9cc0b10) Nov 4 14:22:27 rds023 kernel: Stack: 0000000100000093 0000010001c326c8 0000010037c1f000 0000010000000000 Nov 4 14:22:27 rds023 kernel: ffffffffa07df0b8 0000010077e1c298 ffffffffa07def40 ffffffff802577eb Nov 4 14:22:27 rds023 kernel: 0000010077e1c300 0000010077e1c300 Nov 4 14:22:27 rds023 kernel: Call Trace:<ffffffff802577eb>{agp_generic_destroy_page+187} <ffffffff802580cf>{agp_free_memory+159} Nov 4 14:22:27 rds023 kernel: <ffffffffa04aafcb>{:nvidia:KernFreeAGPPages+70} <ffffffffa04a83e9>{:nvidia:nv_free_pages+277} Nov 4 14:22:27 rds023 kernel: <ffffffffa02f4256>{:nvidia:_nv001607rm+106} <ffffffffa02df75a>{:nvidia:_nv001163rm+150} Nov 4 14:22:27 rds023 kernel: <ffffffffa02df57b>{:nvidia:_nv001167rm+193} <ffffffffa02deb58>{:nvidia:_nv001176rm+298} Nov 4 14:22:27 rds023 kernel: <ffffffffa02f9aae>{:nvidia:rm_disable_interrupts+64} Nov 4 14:22:27 rds023 kernel: <ffffffffa02da9d0>{:nvidia:_nv003441rm+120} <ffffffffa02fad89>{:nvidia:_nv001137rm+461} Nov 4 14:22:27 rds023 kernel: <ffffffffa02f9d8e>{:nvidia:rm_ioctl+58} <ffffffffa04aa24a>{:nvidia:nv_kern_ioctl+910} Nov 4 14:22:27 rds023 kernel: <ffffffff8019765f>{sys_ioctl+1023} <ffffffff801106f4>{system_call+124} Nov 4 14:22:27 rds023 kernel: Nov 4 14:22:27 rds023 kernel: Nov 4 14:22:27 rds023 kernel: Code: 0f 0b 55 ff 35 80 ff ff ff ff 6a 00 48 b8 ff ff ff 7f ff ff Nov 4 14:22:27 rds023 kernel: RIP <ffffffff801230b9>{change_page_attr+1225} RSP <000001007ccf1c08> <<

3 2