openSUSE AMD64 April 2005

amd64@lists.opensuse.org

84 participants
86 discussions

by Andrej Filipcic

Hi, I have troubles with openssh and krb5/afs setup on SuSE 9.3 x86_64. Desktop or console login works OK with pam_krb5afs. When using ssh, the KRB5CCNAME is not set. Although authentication succeedes, there is no krb5 ticket file and afs token. Apr 29 12:13:58 f9pc46 sshd[11192]: pam_krb5afs: module_stash_name: (pam_krb5afs_af(a)F9.IJS.SI_cred_stash) Apr 29 12:13:58 f9pc46 sshd[11192]: pam_krb5afs: Try to get KRB5CCNAME from PAM with pam_getenv() Apr 29 12:13:58 f9pc46 sshd[11192]: pam_krb5afs: `af' has uid 3355, gid 3100 Apr 29 12:13:58 f9pc46 sshd[11192]: pam_krb5afs: call pam_getenv() Apr 29 12:13:58 f9pc46 sshd[11192]: pam_krb5afs: pam_getenv() can't get KRB5CCNAME from PAM What has to be done to correct that? Cheers, Andrej

17 years, 2 months

K3B and dual layer

by jerry bookter

Hey folks-- Is anyone here using a dual layer DVD burner with 9.2? Any recommendations for which one I should get? TIA....

17 years, 2 months

PCI E and SLI board with Suse x86_64?

by Detlef Grittner

Hello, recently a friend asked me, if a board with PCI Express and SLI would be supported by SuSE x86_64. He is looking at this specific board: http://www.asus.com/products/mb/socket939/a8nsli/overview.htm Does anyone know if this board would be supported? Detlef

17 years, 2 months

RE: [suse-amd64] Random lockups/freezes when running 64-bit SUSE 9.3

by Corr, Thomas (Mission Systems)

Not sure what the issue is with your laptops. I have a Compaq Presario R3200 (DP533AV)with an AMD Athlon 64 3400 and am loving it! I have used both the internal wired internet adapter with a static IP address only for a short period of time without any problems, and have used the internal Broadcom wireless with DHCP and WEP encryption (THANKS TO THE NDISWRAPPER FOLKS - Cant say that enough!!!) for a week now without any problems what so ever. Matter of fact, I think I love this release better than I loved 9.2. I'm just waiting for another week or two to make sure I don't stumble onto anything major, and then I'll upgrade my two desktop PC's to 9.3. I ran 9.2 in 32 bit mode when I first got the laptop because of the wireless network card. However, by the time that 9.3 came out, I had had plenty of time to test and play with the ndiswrapper stuff in 64 bit mode, and discovered no major problems with it. I have been running the 64 bit 9.3 with ndiswrapper 1.1 for a week now without any issues. I surf frequently in the evenings and kmail is setup to check for new mail messages every 5 minutes. Maybe you should give NDISWRAPPER a try with the corresponding Winblows drivers for your network card? Just out of curiosity, could the problems your experiencing be related to the Power Management settings APM/ACPI, or the Screen Saver settings? I have used the nv and nvidia drivers for my display without any problems (GeForce4 440 64Meg). Can you go into Yast and deconfigure your internet connections (I know, not very useful)- just to see if the computer still locks up after some period of time? Just trying to isolate the problem if possible. It could be something in your bios, perhaps a dma setting that changed? Have you checked your boot.log file to make sure everyting started up and is working without complaints? Just some thoughts... Hopefully, 1 of them might prove useful. -----Original Message----- From: Valur Olafsson [mailto:volafsso@umich.edu] Sent: Thursday, April 28, 2005 12:47 PM To: suse-amd64(a)suse.com Subject: Re: [suse-amd64] Random lockups/freezes when running 64-bit SUSE 9.3 On Thursday 28 April 2005 11:28, R Kimber wrote: > On Thu, 28 Apr 2005 08:20:31 -0400 > > Valur Olafsson <volafsso(a)umich.edu> wrote: > > Spoke too soon, the computer froze not 10 minutes after I emailed > > the list. Still have the same problem. Any other suggestions to > > debug the problem? > > I have experienced something similar, always while using a browser. > This suggests it might be related to the network connection, but it > might well be something else. All I can say is that I've been > experimenting with a fully 64-bit distribution (as opposed to the > mixed > 64 and 32-bit that I assume most people have) and I have not > experienced the problem at all. On the other hand, the stability might > be due to some other difference between the 64-bit distribution > (Ubuntu) and Suse. I realise this isn't really very helpful, but it > may give you something to think about. > > - Richard Thanks for your reply. I've had these lockups even while I'm not using a browser. In fact, yesterday I connected to the internet, then needed to step away from the computer for a bit. When I came back, the computer had locked up and I needed to do a hard reboot. Frankly, I'm not certain if this only a problem due to me connection to the internet with a wireless USB adapter, i.e., driver related, or if this a general problem with the network in SUSE 9.3. But, until this has been resolved, I cannot upgrade my laptop to 9.3, simply because I actually need to do work there. This is less of an issue on my desktop, but it's still forcing me to use Windows XP instead, which I don't like. It's a shame that this problem is in 9.3, since everything else about 9.3 is pretty darn sweet. These hard reboots that I need to do constantly are really starting to bug me, and frankly my patience is starting to wear thin. I would really hate it if I needed to move to a different linux distribution, since I have been a SUSE user since the 7.x versions. Anyway, enough of this doom and gloom. I'm hoping that the next kernel upgrade will magically fix this. Here's hoping. - Valur > -- > Richard Kimber > British General Election 2005 > http://www.psr.keele.ac.uk/area/uk/ge05.htm -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

17 years, 2 months

Re: [suse-amd64] PCMCIA Wireless card

by patheve2

Hello David Welcome in the team of the people who have some problems with PCMCIA and Linux 64 bits :-)) !!!! Well, as Matt wrote it, you can find in this mailing list some informations that can help you, in particular my two messages : http://lists.suse.com/archive/suse-amd64/2005-Jan/0204.html http://lists.suse.com/archive/suse-amd64/2005-Jan/0205.html in which there are a solution. But I can explain how I could get my cards working fine after several tests with the help of Matt and David Hinds the "father" of the PCMCIA kit for linux. So my laptop : an Asus of the L5D series, the first one of Asus with Athlon 64. It is built with nVidia chipsets. On it : Win XP Pro SP2, SuSE AMD64 9.0 (kernel 2.4.21) and SuSE AMD64 9.1 with kernel (a 2.6.8-24.10 one) and PCMCIA package of the SuSE AMD64 9.2. My cards are a Com One modem card (Platinium 56k), a Netgear ethernet FA411 card and a Hayes modem card (Optima 288). Accordind to "lspci -vv", hereafter the data about the PCMCIA port of my laptop: 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 So with a full SuSE 9.2 (9.3 ?) AMD64, the basis is correct : kernel and PCMCIA package. At first, verify that your card is defined in the /etc/pcmcia/config file. If not, go to the next step, we will see after. Now, have a look on I/O windows and memory window above. These datas are required in the config.opts file in the /etc/pcmcia directory under this form : # range of port addresses : ##################### include port 0xb000-0xb7ff include port 0xb800-0xbfff include port 0xc000-0xc7ff include port 0xc800-0xcfff # range of memory addresses : ######################## include memory 0xf8a00000-0xfd1ff000 I have to take the min and max of the memory for defining one range and take all the ranges of port. Copy the original config.opts and rename it, modify the config.opts by suppressing all datas concerning port and memory and add your own datas. Reboot your PC. Insert a card and see the results with "dmesg" and tell us what you get. I think you can see at this level an improvement . No ?? Then with "/sbin/cardctl info", see the character strings after "PRODID_1" and "PRODID_2". With this, make an entry in the /etc/pcmcia/config file. If you don't know how to do, tell it us. If an entry is already defined, forget this step. Go to the following. Now, see what give /sbin/lsmod. Are there some loaded modules such as "pcmcia_core", "yenta_socket", "ds" and the module depending on the type of PCMCIA card (for example : serial_cs if modem) ? If wrong, don't worry, try this : with /sbin/lspci -vv, find the datas about PCI bridge with secondary=02. In my cas, here what I get : 0000:00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- Latency: 0 Bus: primary=00, secondary=02, subordinate=04, sec-latency=128 I/O behind bridge: 0000b000-0000dfff Memory behind bridge: f8a00000-feafffff Expansion ROM at 0000b000 [disabled] [size=12K] BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- Take the min and max of the memory behind brigde and put them in the config.opts file. Reboot your PC and see the results. Verify all the above steps after boot. Better or not ? If not, I thing that the solution should only come from .... Windows XP !!! Sorry. But if you have Windows on dual boot. This is the first time that Win XP can help Linux !!!!! In my case, I took the datas given by Win XP for PCMCIA port and used them as following in the config.opts file : # range of port addresses : ##################### include port 0xcc00-0xccff include port 0xd000-0xd0ff include port 0xd400-0xd4ff include port 0xdc00-0xdcff # range of memory addresses : ######################## include memory 0xfa200000-0xfeafcfff As you can see, there is a significant difference between my previous and actual config.opts files. With such a file, under SuSE 9.0 and SuSE 9.1, I can use my Com One modem card (not the Hayes and I can't explain why) and the FA411 card. So, if Win XP is not installed on your laptop, well try do it in order to get the right date for PCMCIA port. If you can try a dual installation, Win XP and SuSE 9.2 (9.3), the boot being managed by Win XP (lilo for linux on the boot partition). Perhaps with Grub. Well, it's up to you : try and tell us what you get. Regards Pascal =========================================== I have been trying to get a second wireless card to work in my hp laptop with a 64 AMD. I have not been successful at all. I have found that I believe that SuSE is mis detecting the orinoco gold card that I am trying to use. When that card is plugged in I get the following. When it is not plugged in these lines are not in the system log. Apr 18 16:50:55 DsHP cardmgr[6463]: executing: 'modprobe memory_cs 2>&1' Apr 18 16:50:55 DsHP cardmgr[6463]: + FATAL: Module memory_cs not found. Apr 18 16:50:55 DsHP cardmgr[6463]: modprobe exited with status 1 Apr 18 16:50:55 DsHP cardmgr[6463]: module /lib/modules/2.6.8-24.14-default/pcmcia/memory_cs.o not available Apr 18 16:50:55 DsHP cardmgr[6463]: bind 'memory_cs' to socket 0 failed: Invalid argument I have never had a problem with the orinoco gold card and SuSE. I have used it with 9.1 and 9.2 but only the 32 bit version. I am now using the 64b version. Any ideas? David

17 years, 2 months

Favo(u)rite motherboads

by Pierre Patino

Hello We're moving from Solaris to Linux for our "embedded" platforms. We're evaluating Asus A8V, Asus K8V, Tyan Tomcat K8E. We are also thinking about GigaByte and Shuttle. Can anyone suggest other relatively trouble-free motherboards that should be considered as well? We only need two PCI slots, two serial ports, USB, SATA and at least one (preferably two) Gb ethernets. Built-in XGA would be desirable too. TIA&Cheers

17 years, 2 months

Random lockups/freezes when running 64-bit SUSE 9.3

by Valur Olafsson

Hello all, Before going into the problem at hand let me say that my desktop computer was working as it should running SUSE 9.2, which was installed on the machine before I upgraded to SUSE 9.3. Now to the problem. As the title indicates I have been experiencing lockups after upgrading my AMD64 desktop machine to 64-bit SUSE 9.3. This all started when I wanted to configure my USB Linksys wireless card (WUSB11 v2.8) on my desktop. I needed to configure it to access the internet. So, like I did when I installed SUSE 9.2 in the past, I installed the wireless-tools and atmel-firmware rpms, and plugged the WUSB11 into a USB port on my desktop. Using 'dmesg' I saw that the atmel firmware got uploaded to the WUSB11. So the system recognized the WUSB11 as it had done when I was running 9.2. Then I went into the network module in Yast2 and setup the wireless connection. After that I needed to unplug and plug the WUSB11 to get it to start to connect to my router, but as it was about the get an IP from my router the computer froze. At first I did not know what the problem was, so I tried to install different versions of the atmel-firmware rpm, both the one that came with 9.2 (and had worked previously) and the most recent one from the homepage of the atmel-firmware project. Still the computer froze when the WUSB11 was about to get an IP from my router. Next I thought that maybe the dhcp client on SUSE 9.3 was to blame so I hardwired a particular IP to WUSB11 when setting up the connection in the network module in Yast2 to bypass it. This did the trick, I was finally able to get online, without the machine locking up. This is currently the only way I know how to get the computer online using the WUSB11. This however was to be a short victory, since about a half an hour after getting online for the first time, while surfing the net, the computer locked up again. This time, I was not doing anything specific, just browsing the web through the wireless connection. I thought that maybe this was a one off thing, but this has happened multiple times after that incident. As I said in the first paragraph, everything was working well when running SUSE 9.2 on the same hardware and using the same WUSB11 device to access the internet. Also, the machine is a dual boot machine, and everything is working fine in windows. So what would be my next steps in debugging this problem. Currently, I have no idea what is causing the lockups, or why even the dhcp should be causing lockups when I'm not bypassing that by hardwiring the IP. Any suggestions to logs or something of that sort that I should be looking at are welcome, 'cause I sure as hell don't know what should be my next steps. Regards, Valur Olafsson

17 years, 2 months

Resume on alarm doesn't work with SuSE 9.3

by Bernd Paysan

Hi, I use my PC as digital VDR, and therefore turn it on with an alarm timer. I set the time in the BIOS, and then shut the PC down from Linux. This worked well with SuSE 9.2 (and Windows 2k), but with SuSE 9.3, the PC doesn't come back to live. The other resume-on things (e.g. resume on password at the keyboard) work well. The mainboard is a Gigabyte K8VT800-Pro. Any ideas what's the reason here? -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/

17 years, 2 months

GNUstep on AMD64

by daniel＠kettonlane.me.uk

To put the question simply, is this a lost cause? I know GNUstep is alleged to run well on SPARC-64, but has anyone managed - or heard of others who've managed - to get GNUstep running on 64-bit Linux/AMD? GNUstep's own website does not list any AMD systems at all (Not even 32-bit, and, rather bafflingly, seems to list Linux support by a combination of specifically-named-distribution/CPU). ffcall and GNUstep-make seem to have complied okay, so far, and I've got as far as GNUstep-base, but the configuration script warns me that mframe wasn't been ported to AMD64, and (I think, from what I can gather about what mframe actually does) make is consequently throwing dozens of casting conversion errors (specifically, some ominous long-to-int length error ones), which don't seem to bode well at this early stage in the proceedings.

17 years, 2 months

Re: [suse-amd64] SUSE 9.3 (x86_64) installation on Fujitsu Siemens CELSIUS V810

by Andreas Wahlert

Hi@all, thanx to FSC for providing this information. best regards Andreas Wahlert ----------------------------------------------------------------------- Rainer Koenig wrote: > Hi there, > > today I encountered a kernel panic during installation of SUSE 9.3 on > our V810 dual opteron workstation. This bug occured only when more than > 4 GB of RAM were installed. > I found a workaround that does it on the latest BIOS (R1.07.1692): > The problem can be solved by changing BIOS settings under "Advanced/Chipset". The setting for "Node Memory Interleave" has to change from the default > "Disabled" to "Auto" which will also cause the setting "ACPI SRAT table" to > switch from "enabled to disabled". > After this the system boots fine also with more than 4 GB RAM. > > Best regards > Rainer König

17 years, 2 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE AMD64 April 2005