openSUSE AMD64 June 2005

amd64@lists.opensuse.org

81 participants
76 discussions

by johncraig01＠netscape.net

Does anyone know if failover is implemented in the QLA2300 drivers in SuSE 9.3 x86-64, and how to use it? QLogic has software utilities to manage their cards, do you know which version is compatible? I just installed a dual controller Engenio storage array, and the LUN mappings keep switching around, which is apparently handled by a failover driver either in the HBA or a separate driver. Without such a driver, you have to access the data by different device names when failover occurs in the storage controller, which means you would have to remount the data. And this is a big problem if you want to manage multiple volumes with LVM. Any help would be appreciated. John Craig __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp

17 years

Gnomemeeting on SuSE9.3

by Yoriaki FUJIMORI

Dear listers, I started testing the stock gnomemeeting on SuSE9.3 for amd64. It fails at the end of execution; the gdb gives the following clue: Program received signal SIGSEGV, Segmentation fault. 0x00002aaab342ac88 in scim::ReferencedObject::unref () from /usr/lib64/libscim-1.0.so.6 I am running kernel 2.6.11.4-21.7-default. Is there any new libscim.so without this bug? Thanks for your attention. yoriaki fujimori

17 years

RE: [suse-amd64] Tyan S2881 network problem

by Black, Alain

Joe, What do you consider large files? I've got a 2 servers with MSI mother boards with the BCM5704 (don't know what the C difference is) chip and we nfs/sftp/rcp multi gig files. Nothing larger than 12 GB at this point though. We are quite pleased with their performance. This is both under SLES8SP3 and SLES9. -Alain -----Original Message----- From: Joe Georger [mailto:jgeorger@ll.mit.edu] Sent: Monday, June 13, 2005 12:17 PM To: Brad Dameron Cc: suse-amd64(a)suse.com Subject: Re: [suse-amd64] Tyan S2881 network problem We've got 7 of these units. On one the ethernet is dead. Some of them have qlogic cards and are serving 2-3 3TB raids. When we try to move copy large files over nfs or rcp, the machines like to lock up. We have gone from Suse 9.1 Pro to 9.2 Pro to SLES9 and nothing is staying up. Is the BCM5704C really that bad? I can't blame the OS because I just can't believe SLES9 would lock up like that. Joe Brad Dameron wrote: >Actually the 2881 has been know to have Ethernet issues. I have had to >return a few because the ethernet would stop working after pushing a few >hundred MB over it. But they would work at first. The above message >would indicate either a delay from spanning-tree turned on your switch, >auto-detect on the port not working thus setting it to something like >half-duplex and the BCM trying to communicate at full duplex, bad >ethernet cable (Verify link lights are on), or bad ethernet. > >Have you ran "ethtool eth0" to see if you have a link, etc? Can you get >us that info? Also is it loading the BCM5700 driver or the TG3? > >Brad Dameron >SeaTab Software >www.seatab.com > > > > -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

17 years

SuSe 9.2: Athlon 64 wireless network problem

by Ivanov Pavel

Dear All, i am trying to get working my 64-bit SuSe 9.2 with Linksys Wireless PCI network adapter. I was trying to use ndiswrapper, but it does not really work ("modprobe ndiswrapper" freezes the Linux). I use 64 - bit Broadcom drivers under WindowsXP 64 bit and with ndiswrapper. Can anybody help me with the problem? Thanks a lot, Pavel ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag

17 years

IOMMU Error on Suse 9.3

by Markus Jungemann

Hello, today our HP XW9300 dual opteron workstation with 8GB memory and Suse 9.3 reported problems with the ReiserFS and became unreachable. In the logs the beginning of the problems can be traced back to a PCI-DMA kernel messages complaining about IOMMU space. The relevant part of /var/log/messages is attached. Has someone seen this problem before and is there a way to avoid it? Many thanks, Markus Jun 15 04:29:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:29:09 fe72747 kernel: end_request: I/O error, dev sda, sector 453070313 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722000 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722001 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722002 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722003 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722004 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722005 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722006 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722007 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722008 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: Buffer I/O error on device sda7, logical block 53722009 Jun 15 04:29:09 fe72747 kernel: lost page write due to I/O error on sda7 Jun 15 04:29:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:29:09 fe72747 kernel: end_request: I/O error, dev sda, sector 223241777 Jun 15 04:29:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:29:09 fe72747 kernel: end_request: I/O error, dev sda, sector 223242801 Jun 15 04:29:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:29:09 fe72747 kernel: end_request: I/O error, dev sda, sector 223243825 Jun 15 04:29:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:29:09 fe72747 kernel: end_request: I/O error, dev sda, sector 223244849 Jun 15 04:30:02 fe72747 kernel: ReiserFS: warning: is_tree_node: node level 23871 does not match to the expected one 1 Jun 15 04:30:02 fe72747 kernel: ReiserFS: sda1: warning: vs-5150: search_by_key: invalid format found in block 33434. Fsck? Jun 15 04:30:02 fe72747 kernel: ReiserFS: sda1: warning: zam-7001: io error in reiserfs_find_entry Jun 15 04:30:02 fe72747 /usr/sbin/cron[7739]: (root) CMD (/etc/venus/2.1.0/bin/scCronRunner /etc/venus/cron/every15Minutes /var/venus/logs/cron/every15Minutes 5 90 >/dev/null 2>&1) Jun 15 04:30:02 fe72747 /usr/sbin/cron[7741]: (root) CMD (/etc/venus/2.1.0/bin/scCronRunner /etc/venus/cron/every5Minutes /var/venus/logs/cron/every5Minutes 5 90 >/dev/null 2>&1) Jun 15 04:30:02 fe72747 kernel: ReiserFS: warning: is_tree_node: node level 23855 does not match to the expected one 1 Jun 15 04:30:02 fe72747 kernel: ReiserFS: sda1: warning: vs-5150: search_by_key: invalid format found in block 33235. Fsck? Jun 15 04:30:02 fe72747 kernel: ReiserFS: sda1: warning: zam-7001: io error in reiserfs_find_entry Jun 15 04:30:02 fe72747 kernel: ReiserFS: sda1: warning: vs-7000: search_by_entry_key: search_by_key returned item position == 0 Jun 15 04:30:02 fe72747 kernel: ReiserFS: sda1: warning: zam-7001: io error in reiserfs_find_entry Jun 15 04:30:03 fe72747 kernel: ReiserFS: sda1: warning: vs-7000: search_by_entry_key: search_by_key returned item position == 0 Jun 15 04:30:03 fe72747 kernel: ReiserFS: sda1: warning: zam-7001: io error in reiserfs_find_entry Jun 15 04:30:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:30:09 fe72747 kernel: end_request: I/O error, dev sda, sector 233707817 Jun 15 04:30:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:30:09 fe72747 kernel: end_request: I/O error, dev sda, sector 233708841 Jun 15 04:30:09 fe72747 kernel: PCI-DMA: Out of IOMMU space for 524288 bytes at device 0000:00:07.0 Jun 15 04:30:09 fe72747 kernel: end_request: I/O error, dev sda, sector 233709865

17 years

upgrading 9.2 to latest kernel 2.6.10, or later

by James D. Parra

Hello, What is the best way to get and install the latest kernel (2.6.10 or later), without breaking compiled driver modules, specifically the 3w_9xxx (3Ware) module? Thank you, James

17 years

SCSI card

by James D. Parra

Hello, Can anyone recommend a good Advansys SCSI 160 card for Suse? Thank you, James

17 years

RE: [suse-amd64] AMD Dual Core & kernel 2.6

by Bedard, Joe

An optimized kernel will see 4 CPU's and 2 memory nodes. It will see CPU 0,1 on node 1 and CPU 2,3 on node 2 My question is where does SLES 9 stand on dual core optimizations? -----Original Message----- From: James D. Parra [mailto:Jamesp@MusicReports.com] Sent: Monday, June 13, 2005 2:14 PM To: SuSE AMD64 (E-mail) Subject: RE: [suse-amd64] AMD Dual Core & kernel 2.6 Importance: Low > Will the kernel in Suse 9.1 support Dual AMD, Dual Core, processors? >It should work, but no optimizations and the CPUs are not reported as >siblings (this means if you have a license manager that licenses per >CPU it might make you pay too much) So the kernel will only see 2 CPU's not 4? Thanks, ~James -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

17 years

RE: [suse-amd64] Mobos/Chipsets for Athlon64 3200+ &SuSE Linux 9.x

by chu＠tes-mail.jpl.nasa.gov

Alain Black wrote: >I have an MSI K8N Neo2 Platinum that I am quite pleased with. I use >the Parallel ATA as well at SATA. The only piece that I have not tried >yet is the firewire as I haven't had any digital editing to do since I >hooked this system up. I'm glad to hear that, as I am also looking at that board for my next computer. Mikhail Kuzminsky wrote: >I don't want to use Nvidia chipsets because of potential problems >w/graphics. OK, there is VIA K8T800 Pro chipset. I think you might be confusing the nvidia mobo chipsets with their graphics chipsets. The K8N Neo2 Platinum that Alain referred to above uses a nvidia gforce3 ultra I/O chip, and works quite well on various flavors of Linux, based on all the reports I've seen of it. Plus it has the built-in Gig-E interface, which can give you full Gig-E performance without sapping up bandwidth on the PCI bus. I do not believe the VIA K8T800 Pro has this feature. You don't need to use a nvida graphics card with this mobo; something from ATI should work just as well. Nvidia used to claim to have good support for their graphics chips on Linux systems. I'm not sure what the situation is now, so I would like to learn that as well. eyc

17 years

RE: [suse-amd64] Touchpad Issues in 9.3

by Black, Alain

-----Original Message----- From: Barry Premeaux [mailto:bpremeaux@gmail.com] Sent: Sunday, June 12, 2005 2:19 PM To: suse-amd64(a)suse.com Subject: Re: [suse-amd64] Touchpad Issues in 9.3 > >Where would you put it? > > > Unless you want to see it at every boot, between resume=/dev/hda2 and > showopts. I gave that another try, making sure I didn't add anything but a space between parameters.. I got the same results. Although I see init 5 started during the boot up, and it drops me to the CLI. Startx fails and I end up deleting it from the line and then am able to complete a full reboot. As I said, I have tried stuffing it in alternate locations within the line and the result is the same. It simply does not like psmouse.proto=bare. Barry Barry, Have you tried using the Yast -> System -> Boot Loaded Configuration tool? It worked for me. -Alain.

17 years

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE AMD64 June 2005