April 2005 - openSUSE AMD64 - openSUSE Mailing Lists

apache+php 64 calling elf32 exe
by Riccardo Ghiglianovich 17 Oct '05

17 Oct '05

Hi all, I am new here; I have found that if I call an ELF32 Executable program from a php page loaded by a 64 bit PHP module then I obtain a shared library error, even if the program does not require the library. practical example: compile this ====== pro.c #include <stdio.h> main() { printf("Hello world\n"); } ------ cc -o pro -m32 pro.c then call it from a php page: ========= r.phtml <?php $s = "/tmp/pro 2>/tmp/er 1>&2"; echo "$s : "; $rrr=exec($s); echo `cat /tmp/er`; echo "<hr>"; // just to test that it works... $s = "ls -al /tmp 2>/tmp/er 1>&2"; echo "$s : "; $rrr=exec($s); echo `cat /tmp/er`; ?> ---- http://localhost/r,phtml issuee? Error?Bug? my fault??? Hints? I cannot recompile at 64 all my programs ... Thanks, regards, Ric

3 6

what is best 64 bit motherboard
by Jack Malone 04 May '05

04 May '05

I'm fixing to put together a system for suse linux to run on from the 64 amd cpu. I'm looking at asus, abit, gigabyte, an msi motherboards. asus K8V-SE Deluxe K8T800 or K8N-E DELUXE abit KV8PRO K8T800 Pro gigabyte GA-K8NSPRO msi MSI K8N NEO Platinum I will put in 1 gig of ram on any of these systems. I have used asus boards in the past but am willing to try another one this time around. These are the models that one of our parts sources has in stock at the moment. If there is another one out there that you would recommend I would look at it also. If you using one of these does all the on board components work, sound lan ect with suse. I will be putting suse 9.3 on the machine. thanks

7 6

9.3 with 8GB ram
by Mark Horton 30 Apr '05

30 Apr '05

I just received 9.3 today and installed it on my workstation. I had to add 'mem=2000m' to the kernel boot options get it to boot up after the install. Is this a known problem? Here are some hardware details: tyan S2885 motherboard 2 opteron 248 cpus 8GB ram nvidia 6800 video card lsilogic megaraid pci-x card I'm also getting the following during bootup. The megaraid_mm and megaraid_mbox modules are loaded and the raid array seems to be operating ok. Although it seems quite a bit slower. kobject_register failed for megaraid (-17) Call Trace:<ffffffff80221ea6>{kobject_register+70} <ffffffff8028db37>{bus_add_driver+103} <ffffffff8022e4de>{pci_register_driver+110} <ffffffff8807a06e>{:megaraid:megaraid_init+110} <ffffffff801525de>{sys_init_module+6542} <ffffffff8016b012>{handle_mm_fault+418} <ffffffff8807a000>{:megaraid:megaraid_init+0} <ffffffff8016eaa6>{do_munmap+918} <ffffffff80336931>{__down_read+49} <ffffffff802243e0>{__up_write+48} <ffffffff8010e9de>{system_call+126} Mark

2 4

SuSE 9.3 XMMS compile
by Sudhir Anand 30 Apr '05

30 Apr '05

XMMS was installed from SuSE's dvd and all patches from YOU were applied. Whenever a cd is played, XMMS exits with a segmentation fault. I am now giving up with SuSE XMMS implementation and would like to compile it from source. At the moment, compiling XMMS gives libmikmid, libvorbis and libGL errors. It appears that the scripts cannot link with the right libraries and include files or cannot find them. Can anyone offer any assistance with compiling XMMS on a AMD64 computer? Thanks. Sudhir.

3 6

Re: [suse-amd64] Random lockups/freezes when running 64-bit SUSE 9.3
by Valur Olafsson 30 Apr '05

30 Apr '05

On Wednesday 27 April 2005 13:04, you wrote: > Valur Olafsson wrote: > >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 > > I had even worse problems with a Belkin F5D6050 usb adapter. The > adapter was recognised as "wlan0" device. However, whenever I tried to > connect to the wirless network my entire system would freeze, forcing me > to hard boot the PC. My solution was to delete the wireless drivers > provided by SuSE located in the /lib/modules directory and to compile > the drivers from source. > > My suggestion would be that you try this approach, if you can find the > source code for the the drivers. > > Sudhir Are you talking about the source that comes when you install the km_wlan rpm that comes with suse 9.3. If so, then that is just what I did, that is, I deleted the wireless drivers in /lib/modules and compiled the drivers from source that came from the km_wlan rpm. Did you maybe find some other source for the drivers that worked for you? I ask, because I believe that our USB adapters have the same atmel chipset. My adapter uses the at76c503 (at76c505_rfmd2958 to be more specific) kernel module. Anyway, after the recompile, I still need to hardwire the IP number for the adapter when I am setting it up in the network module in Yast2. But, so far, I've had no lockups and thus no hard reboots needed to fix that. Thanks for all the help, Valur

4 11

Anyone Get 9.3 To Install On an eMachnes M6809?
by Stu Green 29 Apr '05

29 Apr '05

If anyone has been able to get 9.3 to install on one of these please let me know the boot options given. TIA, Stu

1 0

RE: [suse-amd64] k3b and suse 9.0 AMD64
by patheve2 29 Apr '05

29 Apr '05

Hello Thanks for giving this link. I had a look : there is only an update for SuSE 9.0 i586. As my k3b does not work properly, I use now cdbakeoven but this is only for CD, not for DVD. For DVD, I have to boot with SuSE 9.1 Regards Pascal

1 0

RE: [suse-amd64] k3b and suse 9.0 AMD64
by Corr, Thomas (Mission Systems) 29 Apr '05

29 Apr '05

You could visit http://packman.links2linux.org under Multimedia. He builds a lot of different packages for various suse releases. I know he has a k3b that matches you suse distro, not sure about the kde part though. -----Original Message----- From: patheve2 [mailto:patheve2@tele2.fr] Sent: Thursday, April 28, 2005 6:58 PM To: suse-amd64(a)suse.com Subject: [suse-amd64] k3b and suse 9.0 AMD64 Hello k3b freezes when I try to burn an ISO image. This k3b 0.10 with KDE 3.1.4 of SuSE 9.0 AMD64. Where can I find a update of k3b for this SuSE ? Regards Pascal -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

1 0

Printing Issues Galore
by Joel Webb 29 Apr '05

29 Apr '05

We are having major problems with our Athlon 64 system that is being used as a desktop. We are running a Brother printer that is not listed in the drivers list, but has been printed to using the gimp-print driver. (known to work the largest number of printers) Now Brother doesn't "support" linux, but they do provide linux drivers for some of their other printers. Also the printer is similar to our HP laserjet, and it runs flawlessly. It seems most of the issues are coming from printing from OpenOffice, which seems weird. But it gets even weirder. Now looking at the print queue it looks like this: krusty:~ # lpq mfc7820n is ready and printing Rank Owner Job File(s) Total Size active brian 4 (stdin) 6144 bytes 1st brian 5 Untitled1 26624 bytes 2nd brian 6 Job Report - KJobViewer 56320 bytes 3rd brian 7 file:/// 232448 bytes 4th brian 8 file:/// 232448 bytes 5th brian 9 file:/// 232448 bytes But nope, it isn't printing. Any suggestions?? We have removed the printer, and re-added it. Hooked it up directly through USB, and also had it networked as well. While the printer was networked, we could only get one page to be sent to the printer and then the CUPS server said the printer "wasn't ready" any more. Any suggestions?? -- Thanks Again, Joel Webb President and CEO WebbGroup Network Systems L.L.C. Home of: www.TheCreativeInvestor.com www.AllYouCanRent.com www.SellAnyHouseQuick.com 703-778-5755 x101

4 5

k3b and suse 9.0 AMD64
by patheve2 29 Apr '05

29 Apr '05

Hello k3b freezes when I try to burn an ISO image. This k3b 0.10 with KDE 3.1.4 of SuSE 9.0 AMD64. Where can I find a update of k3b for this SuSE ? Regards Pascal

2 1

9.3 krb5afs and openssh
by Andrej Filipcic 29 Apr '05

29 Apr '05

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

1 0

K3B and dual layer
by jerry bookter 28 Apr '05

28 Apr '05

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

3 2

PCI E and SLI board with Suse x86_64?
by Detlef Grittner 28 Apr '05

28 Apr '05

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

2 1

RE: [suse-amd64] Random lockups/freezes when running 64-bit SUSE 9.3
by Corr, Thomas (Mission Systems) 28 Apr '05

28 Apr '05

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

1 0

Re: [suse-amd64] PCMCIA Wireless card
by patheve2 27 Apr '05

27 Apr '05

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

4 5

Favo(u)rite motherboads
by Pierre Patino 27 Apr '05

27 Apr '05

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

2 1

Random lockups/freezes when running 64-bit SUSE 9.3
by Valur Olafsson 27 Apr '05

27 Apr '05

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

2 1

Resume on alarm doesn't work with SuSE 9.3
by Bernd Paysan 27 Apr '05

27 Apr '05

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/

1 0

GNUstep on AMD64
by daniel＠kettonlane.me.uk 27 Apr '05

27 Apr '05

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.

1 0

Re: [suse-amd64] SUSE 9.3 (x86_64) installation on Fujitsu Siemens CELSIUS V810
by Andreas Wahlert 26 Apr '05

26 Apr '05

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

1 0

SUSE 9.3 (x86_64) installation on Fujitsu Siemens CELSIUS V810
by Rainer Koenig 26 Apr '05

26 Apr '05

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 -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Business Clients Fujitsu Siemens Computers VP BC E SW OS Phone: +49-821-804-3321 Fax: +49-821-804-2131

1 0

Sager NP4750 AMD 64-bit laptop with Suse 9.3, Problem
by Col Jim Creech 24 Apr '05

24 Apr '05

With my new Sager NP4750 AMD 64-bit laptop with Suse 9.3, autologin is dumping me to a login page with an xconsole with these 2 msgs: ACPI-400: Warning: invalid active threshold [0], and cpu_init done, current fid 0x0, vid 0x0. After 2 to 3 logins I can't get past it, i.e. login. DMESG reads: ACPI: cpu0 power states: c1 (c1 c2 (c2) ACPI-400 ***Warning: invalid active threshold [0] ACPI: Thermal Zone [THRM] 53degC (note: this was immediately after install.) powernow-k8 found 1 amd Athlon/opteron processors (version 1.00.09e) powernow: 0: fid 0x10(2400Mhz), vid 0x2 (1500mv) powernow: 1: fid 0xc (2000Mhz), vid 0xa (1300mv) powernow: 2: fid 0xa (1800Mhz), vid 0xe (1200mv) powernow: 3: fid 0x0 (800Mhz), vid 0x12 (1100mv) cpuinit done, current fid 0x0, vid 0x0 ACPI-400 ***Warning: invalid active threshold [0] The Sager NP4750 AMD 64-bit laptop BIOS/Advanced Menu/Installed OS offers two choices winxp/win2000 or other. I have tried both with the exact same results. I believe that the 1st error message has to do with setting a temp in trip_points. just found how to find temp info: cd /proc/acpi/thermal_zone/THRM cat temperature temperature 36degC cat trip_points was something like 155:0:110:0:0 How do I change or set them & make them permanent when I reinstall? Next, how do I set the proper fid & vid when I reinstall? Is there a kernel patch that I need that will force fid,vid? Other solution possible? I am a novice at fixing kernels, so please point me to a good howto if this is the route that I have to take. Thanks for thinking on this. Jim

2 1

Sager NP4750 AMD 64-bit laptop with Suse 9.3, Problem
by Col Jim Creech 24 Apr '05

24 Apr '05

With my new Sager NP4750 AMD 64-bit laptop with Suse 9.3, autologin is dumping me to a login page with an xconsole with these 2 msgs: ACPI-400: Warning: invalid active threshold [0], and cpu_init done, current fid 0x0, vid 0x0. After 2 to 3 logins I can't get past it, i.e. login. DMESG reads: ACPI: cpu0 power states: c1 (c1 c2 (c2) ACPI-400 ***Warning: invalid active threshold [0] ACPI: Thermal Zone [THRM] 53degC (note: this was immediately after install.) powernow-k8 found 1 amd Athlon/opteron processors (version 1.00.09e) powernow: 0: fid 0x10(2400Mhz), vid 0x2 (1500mv) powernow: 1: fid 0xc (2000Mhz), vid 0xa (1300mv) powernow: 2: fid 0xa (1800Mhz), vid 0xe (1200mv) powernow: 3: fid 0x0 (800Mhz), vid 0x12 (1100mv) cpuinit done, current fid 0x0, vid 0x0 ACPI-400 ***Warning: invalid active threshold [0] The Sager NP4750 AMD 64-bit laptop BIOS/Advanced Menu/Installed OS offers two choices winxp/win2000 or other. I have tried both with the exact same results. I believe that the 1st error message has to do with setting a temp in trip_points. just found how to find temp info: cd /proc/acpi/thermal_zone/THRM cat temperature temperature 36degC cat trip_points was something like 155:0:110:0:0 How do I change or set them & make them permanent when I reinstall? Next, how do I set the proper fid & vid when I reinstall? Is there a kernel patch that I need that will force fid,vid? Other solution possible? I am a novice at fixing kernels, so please point me to a good howto if this is the route that I have to take. Thanks for thinking on this. Jim

1 0

bttv crash/freeze (Twinhan and similar)
by Bernd Paysan 24 Apr '05

24 Apr '05

Hi, The bttv driver in kernel 2.6.11 contains a deadly bug. It freezes the system when loaded (with cards like Twinhan Vision Plus). Fortunately, the linuxtv team has found the culprit, a superfluous bttv_reset_audio. The patch (as attached) is rather small, and works fine. Please integrate it into the kernel, and provide an update. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/

2 1

sftp:// in konqueror stopped working
by Ray Carlino 24 Apr '05

24 Apr '05

This stopped working in 9.2 after installing kde 3.4 and now a new install of 9.3 has same thing sftp://ip asks for username password but never returns a directory listing... -- Ray

2 1