March 2004 - openSUSE AMD64 - openSUSE Mailing Lists

Kernel 2.6 update HOWTO
by Quy NGUYEN DAI 12 Mar '04

12 Mar '04

Hi all, We have a workstation amd64 with updated kernel 2.4.x of SUSE 9.0. We would like to update to kernel 2.6 (rpm in ftp.suse.{de,com}). What's is the safe way to do that by keeping the current updated kernel 2.4 ? Thank you, Q. NGUYEN-DAI

3 3

RE: [suse-amd64] DBD::ODBC in Suse 9.0 Pro AMD64
by Vlad Didenko 12 Mar '04

12 Mar '04

I got the perl-32bit-9.0-0 installed, it does not have a file "perl". Also, will I need to uninstall the 64-bit UnixODBC and recompile it 32-bit, which will cascade for a lot of my other stuff to be recompiled as 32-bit. I wonder if it will be easier for me to just revert the whole system to 32 bit and wait 'till 64-bit matures a bit? Thank you for the suggestion and the time you are spending on this!!! Sincerely, Vlad. -----Original Message----- From: Andreas Jaeger [mailto:aj@suse.de] Sent: Friday, March 12, 2004 11:22 AM To: Vlad Didenko Cc: suse-amd64 Subject: Re: [suse-amd64] DBD::ODBC in Suse 9.0 Pro AMD64 "Vlad Didenko" <vdidenko(a)Getcollc.com> writes: > Helle All, > > While trying to run our Perl application on a Suse 9.0 Pro AMD64. I found it impossible so far to configure access to MS SQL Server 2000 DB via the DBD::ODBC module. Apparently, Suse shipped 64-bit UnixODBC libraries, which would require 64 -bit versions of either OpenLinkSW or EasySoft drivers, which neither of them have today. > > I tried an alternative to find 32-bit Perl on that system, however i did not find the executable in the perl-32bit package. and there is no unixodbc-32bit installed anyway. So it seems to be a hard path with a lot of non-suse supported recompiles involved. > > Am I missing anything? Is there is an easier way to do it? Is there is a way to do it at all? Should I just rip the 64-bit version off and reinstall 32-bit (that is where I am going today for now)? > > Appreciate any thoughts... A big hack: Grab the 32-bit perl package , unpack it locally, move the perl to /usr/bin/perl-32 and install the 32-bit perl packages.. Andreas -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

DBD::ODBC in Suse 9.0 Pro AMD64
by Vlad Didenko 12 Mar '04

12 Mar '04

Helle All, While trying to run our Perl application on a Suse 9.0 Pro AMD64. I found it impossible so far to configure access to MS SQL Server 2000 DB via the DBD::ODBC module. Apparently, Suse shipped 64-bit UnixODBC libraries, which would require 64 -bit versions of either OpenLinkSW or EasySoft drivers, which neither of them have today. I tried an alternative to find 32-bit Perl on that system, however i did not find the executable in the perl-32bit package. and there is no unixodbc-32bit installed anyway. So it seems to be a hard path with a lot of non-suse supported recompiles involved. Am I missing anything? Is there is an easier way to do it? Is there is a way to do it at all? Should I just rip the 64-bit version off and reinstall 32-bit (that is where I am going today for now)? Appreciate any thoughts... Vlad.

2 1

Ugh!
by Jason Vertrees 12 Mar '04

12 Mar '04

Grr, OK, so this isn't going so well. I tried the normal 2.6.4 build. It compiled fine, but again the make modules_install gave me the usual "XXXX needs unknown symbol memcpy_toio" or "...memcpy_fromio". I also applied the patches provided and still haven't gotten it. I must have something wrong with my .config file, so it's included. (Although, I don't know how the ML will handle an attachment, so if it doesn't go, please see http://vertrees.org/~tree/.config Thanks! -- Jason P.S. Here's the error trace from modules_install: if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.4; fi WARNING: /lib/modules/2.6.4/kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/scsi/sata_promise.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/scsi/pcmcia/fdomain_cs.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/scsi/gdth.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/scsi/fdomain.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/mtd/chips/sharp.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/mtd/chips/cfi_cmdset_0020.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/mtd/chips/cfi_cmdset_0002.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/mtd/chips/cfi_cmdset_0001.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/mtd/chips/amd_flash.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/mtd/chips/jedec.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/net/8139cp.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/net/hp100.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/net/hp100.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/net/wireless/ray_cs.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/net/wireless/ray_cs.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/net/arcnet/arc-rimi.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/net/arcnet/arc-rimi.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/net/arcnet/com90xx.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/drivers/net/arcnet/com90xx.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/drivers/net/8139too.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/sound/core/snd.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/sound/core/snd.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/sound/pci/snd-rme96.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/sound/pci/snd-rme96.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/sound/pci/snd-rme32.ko needs unknown symbol memcpy_fromio WARNING: /lib/modules/2.6.4/kernel/sound/pci/snd-rme32.ko needs unknown symbol memcpy_toio WARNING: /lib/modules/2.6.4/kernel/sound/pci/nm256/snd-nm256.ko needs unknown symbol memcpy_toio -- Jason Vertrees BSCB Graduate Student @ UTMB, Galveston javertre(a)utmb.edu :: http://www.bscb.utmb.edu

3 2

AW: [suse-amd64] opteron based clusters: any technical feedbacks?
by Khamenia, Valery 12 Mar '04

12 Mar '04

Hi Dan, thank you for your response > There are no real issues with Opteron clusters - just install > a standard SuSE distro, enable rsh et al > and install something like MPICH. Indeed there is > even an NPACI ROCKS distribution for AMD64. so, you mean non-SSI cluster. After trying SSI-cluster (OpenMosix) on win32 i am quite eager to switch to Opteron-based hardware. However neither OpenMosix nor OpenSSI run SuSE9-AMD :( -- Valery

1 0

2.4.21-201 kernel bug
by John McCorquodale 12 Mar '04

12 Mar '04

Hi, I've got a QLogic 2342 2-channel fiberchannel card with a storagetek 9940B tape drive alone on a channel. The drive supports block sizes to 256k, but using that blocksize in dd causes 2.4.21-201 kernel blowup with the message (see below for full output) "Kernel BUG at pci_dma:42". If I use the default blocksize, it works without problems (just very slowly). The offending section of pci-dma.c identifies itself as "temporary 2.4 hack", so I'm guessing the problem lies there. :) 256k blocksize works fine in 2.6.3-rc2. I can't just run that version because the 3ware driver seems to be just totally broken in 2.6 (first access seeks the drives then freezes the machine, no message, no nothing). But you guys aren't in the 2.6 game so you don't have to solve that problem. ;-) Ideas? -mcq --- Mar 9 22:39:32 misery kernel: qla2x00_set_info starts at address = ffffffffa00600c0 Mar 9 22:39:32 misery kernel: qla2x00: Found VID=1077 DID=2312 SSVID=1077 SSDID=101 Mar 9 22:39:32 misery kernel: scsi(5): Found a QLA2312 @ bus 3, device 0x1, irq 5, iobase 0x4000 Mar 9 22:39:32 misery kernel: scsi(5): Allocated 4096 SRB(s). Mar 9 22:39:32 misery kernel: scsi(5): Configure NVRAM parameters... Mar 9 22:39:32 misery kernel: scsi(5): 64 Bit PCI Addressing Enabled. Mar 9 22:39:32 misery kernel: scsi(5): Scatter/Gather entries= 896 Mar 9 22:39:32 misery kernel: scsi(5): Verifying loaded RISC code... Mar 9 22:39:32 misery kernel: scsi(5): Verifying chip... Mar 9 22:39:32 misery kernel: scsi(5): Waiting for LIP to complete... Mar 9 22:40:32 misery kernel: scsi(5): Cable is unplugged... Mar 9 22:40:32 misery kernel: qla2x00: Found VID=1077 DID=2312 SSVID=1077 SSDID=101 Mar 9 22:40:32 misery kernel: scsi(6): Found a QLA2312 @ bus 3, device 0x1, irq 10, iobase 0x4400 Mar 9 22:40:32 misery kernel: scsi(6): Allocated 4096 SRB(s). Mar 9 22:40:32 misery kernel: scsi(6): Configure NVRAM parameters... Mar 9 22:40:32 misery kernel: scsi(6): 64 Bit PCI Addressing Enabled. Mar 9 22:40:32 misery kernel: scsi(6): Scatter/Gather entries= 896 Mar 9 22:40:32 misery kernel: scsi(6): Verifying loaded RISC code... Mar 9 22:40:32 misery kernel: scsi(6): Verifying chip... Mar 9 22:40:32 misery kernel: scsi(6): Waiting for LIP to complete... Mar 9 22:40:33 misery kernel: scsi(6): LIP reset occurred. Mar 9 22:40:33 misery kernel: scsi(6): LIP occurred. Mar 9 22:40:33 misery kernel: scsi(6): LOOP UP detected. Mar 9 22:40:33 misery kernel: scsi(6): Topology - (Loop), Host Loop address 0x0 Mar 9 22:40:34 misery kernel: scsi5 : QLogic QLA2312 PCI to Fibre Channel Host Adapter: bus 3 device 1 irq 5 Mar 9 22:40:34 misery kernel: Firmware version: 3.01.18, Driver version 6.05.00 Mar 9 22:40:34 misery kernel: Mar 9 22:40:34 misery kernel: scsi6 : QLogic QLA2312 PCI to Fibre Channel Host Adapter: bus 3 device 1 irq 10 Mar 9 22:40:34 misery kernel: Firmware version: 3.01.18, Driver version 6.05.00 Mar 9 22:40:34 misery kernel: Mar 9 22:40:34 misery kernel: Vendor: STK Model: T9940B Rev: 1.32 Mar 9 22:40:34 misery kernel: Type: Sequential-Access ANSI SCSI revision: 03 Mar 9 22:40:34 misery kernel: st: Version 20030403, bufsize 32768, max init. bufs 4, s/g segs 16 Mar 9 22:40:34 misery kernel: Attached scsi tape st0 at scsi6, channel 0, id 0, lun 0 (I run dd if=some_file of=/dev/st0 bs=256k) Mar 9 21:28:10 misery kernel: st0: Block limits 1 - 262144 bytes. Mar 9 21:32:11 misery kernel: Kernel BUG at pci_dma:42 Mar 9 21:32:11 misery kernel: invalid operand: 0000 Mar 9 21:32:11 misery kernel: CPU 1 Mar 9 21:32:11 misery kernel: Pid: 1309, comm: dd Not tainted Mar 9 21:32:11 misery kernel: RIP: 0010:[<ffffffff801166fc>]{pci_map_sg+124} Mar 9 21:32:11 misery kernel: RSP: 0018:00000100291f7ba8 EFLAGS: 00010002 Mar 9 21:32:11 misery kernel: RAX: 0000000000000001 RBX: 000001000e976840 RCX: 0000000000000001 Mar 9 21:32:11 misery kernel: RDX: 000000008020b9e0 RSI: 00000100004c0000 RDI: 00000101ff95d800 Mar 9 21:32:11 misery kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: 000000000000003a Mar 9 21:32:11 misery kernel: R10: 000001000e39add0 R11: 0000000000000060 R12: 0000000000000001 Mar 9 21:32:11 misery kernel: R13: 000000000000000f R14: 000001000e976840 R15: 00000101ff95d800 Mar 9 21:32:11 misery kernel: FS: 000000000050e080(0000) GS:ffffffff8041f2c0(0000) knlGS:0000000000000000 Mar 9 21:32:11 misery kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Mar 9 21:32:11 misery kernel: CR2: 0000002a955f6000 CR3: 00000001ff911000 CR4: 00000000000006e0 Mar 9 21:32:11 misery kernel: Process dd (pid: 1309, stackpage=100291f7000) Mar 9 21:32:11 misery kernel: Stack: 00000100291f7ba8 0000000000000018 ffffffff8013aaa3 00000100291f3550 Mar 9 21:32:11 misery kernel: 000001000e8400d0 000000000000020a 000001000e83cea8 000001000e83ce80 Mar 9 21:32:11 misery kernel: 000001000e976840 000001000e39ac00 ffffffffa00676e0 000001000000003a Mar 9 21:32:11 misery kernel: Call Trace: [<ffffffff8013aaa3>]{do_anonymous_page+259} Mar 9 21:32:11 misery kernel: [<ffffffffa00676e0>]{:qla2300-60650:qla2x00_64bit_start_scsi+832} Mar 9 21:32:11 misery kernel: [<ffffffffa006de5c>]{:qla2300-60650:qla2x00_next+508} Mar 9 21:32:11 misery kernel: [<ffffffffa0062256>]{:qla2300-60650:qla2x00_queuecommand+1078} Mar 9 21:32:11 misery kernel: [<ffffffff8020c0d2>]{scsi_dispatch_cmd+642} [<ffffffff80214c2e>]{scsi_request_fn+990} Mar 9 21:32:11 misery kernel: [<ffffffff80213d2f>]{__scsi_insert_special+127} [<ffffffff80213da2>]{scsi_insert_special_req+34} Mar 9 21:32:11 misery kernel: [<ffffffff8020c401>]{scsi_do_req+385} [<ffffffffa004f300>]{:st:st_sleep_done+0} Mar 9 21:32:11 misery kernel: [<ffffffffa004f533>]{:st:st_do_scsi+339} [<ffffffffa0051082>]{:st:st_write+2178} Mar 9 21:32:11 misery kernel: [<ffffffff8015201f>]{sys_write+191} [<ffffffff801100c3>]{system_call+119} Mar 9 21:32:11 misery kernel: Mar 9 21:32:11 misery kernel: Mar 9 21:32:11 misery kernel: Code: 0f 0b 7e da 28 80 ff ff ff ff 2a 00 eb 56 66 66 90 66 66 90

2 1

YaST Online Update problem
by Terri Novotny 11 Mar '04

11 Mar '04

Hi, I have a problem with YOU. I had to use the SuSE Patch CD because I have only SATA drives in my System (Dual Opteron Fujitsu-Siemens Celsius V810). Any update attempt, independent of the server, results in the error message error Unable to get './x86_64/update/SuSE-Linux-PatchCD/9.0/patches/directory.3' or to read the directory (Connection aborted). Any help is greatly appreciated. - Terri __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

2 1

r8169 patch
by Andrej Filipcic 11 Mar '04

11 Mar '04

Hi I am using RealTek-8169 card on SuSE/9 AMD64. There is a problem with udp transmission. (nfs/afs writes do not work). The patch bellow from 2.4.26-pre2 corrects the problem. Could you include it in next kernel release? I have checked it on kernel 2.4.21-201-default Best regards, Andrej --------- diff -ur linux-2.4.22-1.2174.nptl_37.rhfc1.at/drivers/net/r8169.c linux-2.4.25/drivers/net/r8169.c --- linux-2.4.22-1.2174.nptl_37.rhfc1.at/drivers/net/r8169.c 2004-03-06 10:10:09.000000000 +0100 +++ linux-2.4.25/drivers/net/r8169.c 2004-03-07 08:35:58.000000000 +0100 @@ -291,8 +291,8 @@ MODULE_AUTHOR("Realtek"); MODULE_DESCRIPTION("RealTek RTL-8169 Gigabit Ethernet driver"); -MODULE_LICENSE("GPL"); MODULE_PARM(media, "1-" __MODULE_STRING(MAX_UNITS) "i"); +MODULE_LICENSE("GPL"); static int rtl8169_open(struct net_device *dev); static int rtl8169_start_xmit(struct sk_buff *skb, struct net_device *dev); @@ -874,7 +874,6 @@ void *ioaddr) { unsigned long dirty_tx, tx_left = 0; - int entry = tp->cur_tx % NUM_TX_DESC; assert(dev != NULL); assert(tp != NULL); @@ -884,14 +883,18 @@ tx_left = tp->cur_tx - dirty_tx; while (tx_left > 0) { + int entry = dirty_tx % NUM_TX_DESC; + if ((tp->TxDescArray[entry].status & OWNbit) == 0) { - dev_kfree_skb_irq(tp-> - Tx_skbuff[dirty_tx % NUM_TX_DESC]); - tp->Tx_skbuff[dirty_tx % NUM_TX_DESC] = NULL; + struct sk_buff *skb = tp->Tx_skbuff[entry]; + + tp->stats.tx_bytes += skb->len >= ETH_ZLEN ? + skb->len : ETH_ZLEN; tp->stats.tx_packets++; + dev_kfree_skb_irq(skb); + tp->Tx_skbuff[entry] = NULL; dirty_tx++; tx_left--; - entry++; } } -- _____________________________________________________________ doc. dr. Andrej Filipcic, E-mail: Andrej.Filipcic(a)ijs.si Department of Experimental High Energy Physics - F9 Jozef Stefan Institute, Jamova 39, P.o.Box 3000 SI-1001 Ljubljana, Slovenia Tel.: +386-1-477-3674 Fax: +386-1-425-7074 -------------------------------------------------------------

1 0

Woohoo!
by Jason Vertrees 11 Mar '04

11 Mar '04

OK, So, for 2.6.4 I have 8x AGP working (or so the logs say: glxgears gives me ~2400 FPS); broadcom 5700 GigaBit eth0 working; and, finally ALSA works. The latest x86-64 patch and 2.6.4 cleared this up! Thanks to everyone for your help! -- Jason -- Jason Vertrees BSCB Graduate Student @ UTMB, Galveston javertre(a)utmb.edu :: http://www.bscb.utmb.edu

1 0

Re: [suse-amd64] 2.6.4-rc3 errors: memcpy_fromio and memcpy_toio
by Jason Vertrees 11 Mar '04

11 Mar '04

Guys, The first patch produced many errors; the second patch reverted me to the initial state. 2.6.4 came out. It's compiling now. I'll let ya' know what happens. -- Jason On Wed, 2004-03-10 at 18:04, Rusty Russell wrote: > On Thu, 2004-03-11 at 10:24, Andi Kleen wrote: > > diff -u linux-2.6.4rc3-amd64/include/linux/module.h-o linux-2.6.4rc3-amd64/include/linux/module.h > > --- linux-2.6.4rc3-amd64/include/linux/module.h-o 2004-03-08 15:23:46.000000000 +0100 > > +++ linux-2.6.4rc3-amd64/include/linux/module.h 2004-03-17 04:21:38.000000000 +0100 > > @@ -178,7 +178,6 @@ > > __attribute__((section("__ksymtab_strings"))) \ > > = MODULE_SYMBOL_PREFIX #sym; \ > > static const struct kernel_symbol __ksymtab_##sym \ > > - __attribute_used__ \ > > __attribute__((section("__ksymtab" sec), unused)) \ > > = { (unsigned long)&sym, __kstrtab_##sym } > > That'll make it worse, if this is the problem. > > Try this instead: > > diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal .11285-linux-2.6.4-rc3-bk1/include/linux/module.h .11285-linux-2.6.4-rc3-bk1.updated/include/linux/module.h > --- .11285-linux-2.6.4-rc3-bk1/include/linux/module.h 2004-03-10 12:12:05.000000000 +1100 > +++ .11285-linux-2.6.4-rc3-bk1.updated/include/linux/module.h 2004-03-11 10:32:50.000000000 +1100 > @@ -179,7 +180,7 @@ void *__symbol_get_gpl(const char *symbo > = MODULE_SYMBOL_PREFIX #sym; \ > static const struct kernel_symbol __ksymtab_##sym \ > __attribute_used__ \ > - __attribute__((section("__ksymtab" sec), unused)) \ > + __attribute__((section("__ksymtab" sec))) \ > = { (unsigned long)&sym, __kstrtab_##sym } > > #define EXPORT_SYMBOL(sym) \ > > > > > > > > > > -Andi -- Jason Vertrees BSCB Graduate Student @ UTMB, Galveston javertre(a)utmb.edu :: http://www.bscb.utmb.edu

1 0