April 2005 - openSUSE AMD64 - openSUSE Mailing Lists

mono and java on SuSE 9.3
by Detlef Grittner 09 Apr '05

09 Apr '05

As I have learned from the list, the first people have received their SuSE 9.3 boxes. So finally I can ask the questions: Is there a 64 bit version of mono and which version is it? If there is one, does it include monodoc and monodevelop and are they working? Is there a 64 bit version of Java and which version is it? Detlef

2 2

Visioneer One Touch 7300 USB Scanner
by William Westfall 09 Apr '05

09 Apr '05

Has anyone got this scanner working on SuSE 9.2 64bit? I tried to use YaST but it is not recognized and I am too new at this, to mess around with settings confortably. Besides YaST said something to the affect that I could damage the scanner if I didn't get it right. Thanks to anyone who can help and a play by play install would be very helpful. This is the last item I need to get working on my system... Please someone help! Oh yea, I have 50 gmail invites to give away if anyone wants an account... 2 gigs storage now and it's still free. Send email [OFFLIST] to william.westfall(a)gmail.com if you want to try it out. Thanks! -- wgwestfall1(a)privatemail.me.uk William.Westfall(a)gmail.com Made with:___________________________________________ Thunderbird 1.0.2 (20050317) http://www.mozilla.org/products/ Linux 2.6.8-24.14 AMD64 GNU/Linux (SuSE 9.2)

1 0

RE: [suse-amd64] need help with megaraid driver, suse 9.2
by James D. Parra 07 Apr '05

07 Apr '05

>With modprobe I get; > # modprobe megaraid >FATAL: Module megaraid not found. >...and lspci shows; ># lspci >0000:00:09.0 I2O: LSI Logic / Symbios Logic MegaRAID (rev 01) >...while dmesg shows; >dmesg |grep I2O >I2O Core - (C) Copyright 1999 Red Hat Software >i2o: Checking for PCI I2O controllers... >i2o: I2O controller found on bus 0 at 72. >i2o: PCI I2O controller at E8800000 size=4194304 >iop0: Activating I2O controller... >I2O controller: probe of 0000:00:09.0 failed with error -110 >I2O configuration manager v 0.04. >I2O Block Storage OSM v0.9 >I don't see a "megaraid.ko" file. Are the ".ko" extensions for modules not >used on Suse 9.2? >The directory contents of ../megaraid/ are; >-rw-r--r-- 1 root root 2753 Mar 18 03:31 Kconfig.megaraid >-rw-r--r-- 1 root root 93 Mar 18 03:31 Makefile >-rw-r--r-- 1 root root 21173 Mar 18 03:31 mbox_defs.h >-rw-r--r-- 1 root root 9454 Mar 18 03:31 mega_common.h >-rw-r--r-- 1 root root 8312 Mar 18 03:31 megaraid_ioctl.h >-rw-r--r-- 1 root root 94385 Mar 18 03:32 megaraid_mbox.c >-rw-r--r-- 1 root root 9071 Mar 18 03:32 megaraid_mbox.h >-rw-r--r-- 1 root root 24679 Mar 18 03:31 megaraid_mm.c >-rw-r--r-- 1 root root 2141 Mar 18 03:31 megaraid_mm.h >Is anything missing? After disabling ACPI in the BIOS and re-installing without ACPI support in the kernel, the install still failed to load the module for the megaraid card. During the 9.2 install it did ask for the module disk 2 (IDE, SCSI, etc, modules) which I created earlier, to load a module into the kernel, but it did specify which module it was loading. Interestingly, I loaded Mandrake 10 to see if it loaded the megaraid module, which it did. Personally, although I have nothing against Mandrake (it is an excellent distro perfect for new Linux users) I would prefer using Suse. Anyone have any ideas as to why Mandrake can detect and load the correct module for a megaraid card while Suse 9.2 cannot? If anybody has any ideas on how to fix this under Suse 9.2, I would be most grateful. Many thanks, James -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

2 1

Re: [suse-amd64] MSI K8N Neo Platinum -- USB hotplugging
by Matthias Titeux 07 Apr '05

07 Apr '05

Thank you for the answers. I do remember of a problem with hotplug under SuSE 9.1 on 32 bit. I run 2 SuSE 9.1 machines at work, both 32 bits, and i read everyday (not exactly, in fact !!) the suse-e-linux mailing list. I think the broken hotplug package has been fixed months ago. Anyway, on both 32 bits machines, it works like a charm. Do you think that SuSE did not patch the hotplug package for x86-64 by now ? Best regards Matthias Le jeudi 7 Avril 2005 14:20, andy(a)epox.org a écrit : > I am sorry but I am presently out of the office until 11th April. I shall > be checking my e-mail whilst I am away although may not be able to respond > to it until my return. > > Apologies for any inconvenience caused during this period. > > Best Regards, > > > Andrew Cotterill > UK Business Manager > EPoX UK -- __________________________________ Matthias Titeux, PhD INSERM U563 - CPTP Departement de Genetique fonctionnelle des maladies des epitheliums Batiment Lefebvre - 2eme etage CHU Purpan Avenue de Grande Bretagne 31059 Toulouse Cedex 03 FRANCE --------------- Tel: 33 (5) 62 74 45 03 _________________________________

1 0

Re: [suse-amd64] MSI K8N Neo Platinum -- USB hotplugging
by TimSchofield.7552659＠bloglines.com 07 Apr '05

07 Apr '05

--- TimSchofield.7552659(a)bloglines.com wrote: > If > memory serves me correct there was a problem with 9.1 and the hotplugging/subfs > where this happened. I have to admit that i was on 32-bit at the time and > there were many people who had the same problem - search the suse-linux-e > archives. > Replying to my own email! I seem to remember that if you used the package on the CDs / DVDs it worked. It got broken if you did an online update and reverting to the old package solved it. Tim

1 0

Re: [suse-amd64] MSI K8N Neo Platinum -- USB hotplugging
by TimSchofield.7552659＠bloglines.com 07 Apr '05

07 Apr '05

> However, it never appears in the drives:// section. I tried to stop and > restart the hotplug daemon with no success. > > Since people apparently had this problem with another mobo, it is maybe the > same kind of problem. Is anyone has been able to have hotplug working with > this mobo ? If memory serves me correct there was a problem with 9.1 and the hotplugging/subfs where this happened. I have to admit that i was on 32-bit at the time and there were many people who had the same problem - search the suse-linux-e archives. I do not think that there ever was a solution for this in 9.1 apart from switching off the subfs http://portal.suse.com/sdb/en/2004/05/hmeyer_91_revert_from_subfs.html Upgrading to 9.2 where it works in both 32 & 64 bit version may be your only solution. Tim

1 0

MSI K8N Neo Platinum -- USB hotplugging
by Martin Schröder 07 Apr '05

07 Apr '05

Hi, we have two machines with MSI K8N Neo Platinum mainboards and USB hotplugging doesn't work. Has anybody got it working with 9.2? Best regards Martin -- Martin Schröder, ms(a)artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de

5 4

Re: [suse-amd64] radiusd
by Riccardo Ghiglianovich 07 Apr '05

07 Apr '05

Il giorno 07/apr/05, alle 10:16, Stefan Fent ha scritto: > * Riccardo Ghiglianovich <riccardo(a)logicalsystem.it> [050406 18:06]: >> hi all, >> I am using Suse Enterprise 9.0 amd64; >> I am trying to use freeradius as radius daemon. >> I can install it from the CDs but it doesnt work. >> at start, it says >> Failed to link to module 'rlm_exec': rlm_exec.a: cannot open shared >> object file: No such file or directory > > This is no shared library, but static. > >> >> I discovered that rlm_exec.la looks for rlm_exec.a and it DOES EXIST >> and it is in the right place: /usr/lib/freeradius >> >> mhh... the radiusd is ELF64 but the lib is 32... may be this the >> issue? >> I dont know, ... > > This is not true: > > 1033 sf@f240:/tmp/usr/lib/freeradius/ > objdump -a rlm_exec.a > In archive rlm_exec.a: > > rlm_exec.o: file format elf64-x86-64 > rw-r--r-- 0/0 6880 Sep 24 03:16 2003 rlm_exec.o > > > It might be in the wrong path, but 9.0 is very old ok but in the conf file the libdir path is according to the real path so it should be found. > > >> >> Is there here someone that has freeradius up and running?? > > I don't, but at least it's no 64bit/32bit issue. > Good, don't you have any ideas? I also downloaded a newer freeradius rpm (for SUSE 9.2) freeradius-1.0.0-5.5.x86_64.rpm, from mirrors.uol.com.br/pub/suse/i386/9.2/suse/x86_64/ but I obtain the same result. >> >> thanks, >> Ric

1 0

9.3 without MP3 support??
by Cristian Rodriguez 07 Apr '05

07 Apr '05

Hi: I recently read one review at http://madpenguin.org/cms/?m=show&id=3851&page=2 abut the upcoming SUSE 9.3 One thing that brings my attention its the "removed MP3 support"?? Is that really true? GStreamer, Arts, and aKode COMPILED without Mp3 support? I know some folks at SUSE are reading this maillist..can somebody confirm it? If this is true,Its time to move to another distro.the lack of multimedia codecs was easy to solve, but this news are really annoying. bye

2 2

lm_sensors and /proc/sys/dev/sensors
by Scott Leighton 07 Apr '05

07 Apr '05

At the risk that this is an incredibly stupid question, I'm going to ask it anyways <g>. I have lm_sensors installed on my AMD64 box, it seems to work fine other than a questionable voltage alarm that is likely a sensors.conf setting issue. # sensors w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.50 V (min = +1.71 V, max = +1.89 V) +3.3V: +3.38 V (min = +3.14 V, max = +3.47 V) +5V: +5.16 V (min = +4.76 V, max = +5.24 V) +12V: +12.28 V (min = +10.82 V, max = +13.19 V) -12V: -12.28 V (min = -13.18 V, max = -10.80 V) -5V: -5.30 V (min = -5.25 V, max = -4.75 V) ALARM V5SB: +5.51 V (min = +4.76 V, max = +5.24 V) VBat: +3.65 V (min = +2.40 V, max = +3.60 V) fan1: 3443 RPM (min = 33750 RPM, div = 2) fan2: 0 RPM (min = 1328 RPM, div = 4) temp1: +58°C (high = +0°C, hyst = +0°C) sensor = PII/Celeron diode temp2: +34.5°C (high = +80°C, hyst = +75°C) sensor = thermistor alarms: beep_enable: Sound alarm disabled eeprom-i2c-0-51 Adapter: SMBus Via Pro adapter at 0400 Memory type: DDR SDRAM DIMM Memory size (MB): 512 eeprom-i2c-0-50 Adapter: SMBus Via Pro adapter at 0400 Memory type: DDR SDRAM DIMM Memory size (MB): 512 I wanted to track the sensor info over time, so I tried to install the rrdtool scripts that come packaged with lm_sensors. No go, it complains that /proc/sys/dev/sensors doesn't exist. Some googling reveals that means that sensor support isn't compiled into the kernel. That doesn't make sense to me, if sensor support isn't compiled in, then why does lm_sensors seem to work fine? If it is compiled in, then why do I not have a /proc/sys/dev/sensors ? Needless to say, I'm confused and could use some enlightenment. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.11-default x86_64

1 1