Sid Boyce wrote:

Jyh-Shyong Ho wrote:

...

Hi,

I installed SuSE9.1 on my dual Opteron computer with TYAN2885. I have two problems and hope someone can help.

1. I am not able to install SuSE9.1 with NFS, the installer failed to load the network crad module, I tried bcm5700, tg3 and others from the network module list, with parameter set to eth0, the specified modules were not found by the installer. I wonder what might be the problem? I used both the downloaded boot image and a SuSE9.1 DVD for this installation.

2. After installed SuSE9.1 with the DVD, and I tried the beta version of a 3D visualization program Amira, I got the following error message:

/usr/lib64/libGL.so.1 : no version information available

Somehow the program does not pick up the version information of libGL.so.1 which does exist.

Regards

Jyh-Shyong Ho, Ph.D. Research Scientist National Center for High Performance Computing Hsinchu, Taiwan, ROC

I had some network stall problems on my AMD64 laptop with the bcm5788, it was using the bcm5700 module, switched to the tg3 and it's been OK. One thing I do rapidly after a SuSE install is to bin their kernel, see below, the President of Opensound flames SuSE kernels. http://www.ussg.iu.edu/hypermail/linux/kernel/0406.2/0530.html Regards Sid.

16 flames back at OpenSound by the kernel developers, some white hot. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====

Örn Hansen wrote:

fredag 18 juni 2004 05:20 skrev Sid Boyce:

...

16 flames back at OpenSound by the kernel developers, some white hot. Regards Sid.

Man, reading those mail from the kernel developers I can "perhaps" understand why SuSE needs 12.8Mb of diffs that aren't in the mainstream. It's true that the KBUILD environment is borked in 2.6.5-suse, but what an attitude.

The man's original point was this, the extreme changes in interface stoppes small developers from being able to release code that works mainstream. This is true. Reply arguement is, that he's not using an interface that's guaranteed to be constant ... probably true. But the originally adressed issue, is simply shrugged away with "We decide, eat what your given". So, we have to continue live with the same problems ... like the one I'm having with going from i386 to x86_64 ...

Linux has a long way to go ... and to get there, it needs proper management.

I wish the distros would establish more of a rapport in the interests of Linux, the consortium that was got together to produce a standard kernel, led by SuSE, was an excellent idea, even then Mandrake and RedHat refused to join or even cooperate and that's the stick that MS used a while ago. Imagine MS taking a SuSE box and a RedHat box into a customer, grabbing a RPM and installing it on one distro fine, then having it fail on the other, it won't look pretty. On Tuesday my friend and I attended a Novell seminar and were given a package at the end of the day which included SLES 8 and Netware, very nice, they also gave a nice demo of iFolder and gave us a URL to download it from. Installation failed, it needs mono, so if many at the well attended seminar had tried it, they may be disappointed. One chink of light, they have said that they intend to make all their products compatible across all the major distros, so Novell's thinking seems to be heading us in the right direction. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====

Jyh-Shyong Ho writes:

Dear Mr. Jaegar,

Thanks for your reply. I tried again the NFS installation, and I found the reason why I failed in my previous attempts. My TYAN 2885 motherboard has only one gigabit ethernet port, after selecting the name of the network card modules (tg3 or bcm5700) from the module list, I should leave the module parameter box empty (instead of typing eth0), and the installer correctly picked up the module driver /modules/tg3.ko, otherwise, it will try to look for /modules/tg3.koeth0

Btw. for NFS installation, you do not need the manual installation. Just pass at the linuxrc command line: install=nfs://1.1.1.1/path And everything will happen automatically - no need to specify the netcard, Andreas -- Andreas Jaeger, aj@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

* Jyh-Shyong Ho [040621 04:49]:

Hi,

I installed SuSE9.1 on my Opteron computer with all OpenPBS modules, the OpenPBS management/configuration is installed in /var/spool/pbs by default. However, I cannot find any of the OpenPBS command, i.e., qsub, qstat, etc., am I missing something?

The files are in package OpenPBS-clients, and get installed to /opt/pbs/bin

I also installed MPICH, gcc and g77 with SuSE9.1, and I found mpicc, mpif77 and mpif90 under directory /opt/mpich/ch_p4/bin, since GNU does not have fortran90 compiler, I wonder where the mpif90 came from?

No idea.

Regards

Jyh-Shyong Ho, Ph.D. Research Scientist National Center for High Performance Computing Hsinchu, Taiwan, ROC

Andreas Jaeger wrote:

...

Jyh-Shyong Ho writes:

...

Dear Mr. Jaegar,

Thanks for your reply. I tried again the NFS installation, and I found the reason why I failed in my previous attempts. My TYAN 2885 motherboard has only one gigabit ethernet port, after selecting the name of the network card modules (tg3 or bcm5700) from the module list, I should leave the module parameter box empty (instead of typing eth0), and the installer correctly picked up the module driver /modules/tg3.ko, otherwise, it will try to look for /modules/tg3.koeth0

Btw. for NFS installation, you do not need the manual installation. Just pass at the linuxrc command line: install=nfs://1.1.1.1/path

And everything will happen automatically - no need to specify the netcard,

Andreas -- Andreas Jaeger, aj@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

------------------------------------------------------------------------ Part 1.2Type: application/pgp-signature

-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com

-- Stefan Fent SuSE Linux AG, Maxfeldstr. 5, D-90409 Nuernberg GPG fingerprint = B226 E3DA 37B0 2170 7403 D19C 18AF E579 9161 4BBC

I'm going to make my statement here as a user of the OpenSoundSystem to this *bad* discussion at the kernel mailing list. First i have to say that i got a lot of help from the OSS president personally to get my sound working properly, all that without buying a License :-) - while i was trying to get ALSA running before i received no answers or "buy a other soundcard" for my questions :-( Related to this kernel-discussion: i'm very unhappy about the way this discussion had gone and it would have been better if the OSS president had explained his problems in a more polite and neutral way... on the other site i understand really why he has gone so angry: they just solved all the issues (problems that occured only with SuSE and none of the other great distributions) with SuSE 9.1 and released a new OSS version this week that works good with the SuSE 2.6.4-xx-x86_64 kernels. one day later SuSE provided the 2.6.5-7.x kernel via YaST Online Update and all is broken again :-( i could feel with the OSS team that this is a bit too much at the moment... i hope that SuSE can take a bit care off such kernel changes, as they're taking a lot off care that they don't break nVidias drivers ;-) the worst thing is that the OSS president said he don't have the possibility to discuss his problems directly with SuSE - i hope that SuSE can start a direct dialogue for that i'm not a developer so i couldn't say if this mass of kernel changes is necessary but it causes a lot of problems for the users like me - not only with OSS - i know a lot of guys that had to change to other distributions because they didn't get special drivers (for internet- connections for example) running with this SuSE kernels. i think that it's very important to find a solution for that... i know that SuSE makes a lot for improving the Linux-kernels and this may cause changes but please don't forget the compatibility with standard kernels and other distributions... best regards Franz PS: i couldn't and won't believe that SuSE makes anything like a 'attack' against OSS as the OSS president seems to say, i hope that this 'discussion' could get back in a normal non-emotional track soon... ___________________________________________________________ Bestellen Sie Y! DSL und erhalten Sie die AVM "FritzBox SL" für 0€. Sie sparen 119€ und bekommen 2 Monate Grundgebührbefreiung. http://de.adsl.yahoo.com

Come on, let's get some facts together - and yes, I'm working for SUSE;-) - Currently no distribution can ship a vanilla kernel: * For example to support AMD64, a small patch has to be issued for 2.6.7 (details on the discuss at amd64.org mailing list). The patch is getting smaller each kernel release - and has different patches in it. - SUSE is dedicated to get all patches in the official kernel. - During release phase, we do not import all patches from Linus, just those that fix critical bugs. Therefore our 2.6.5 kernel contains lots of patches that you'll find in 2.6.6 and 2.6.7. The 2.6.4 kernel contained already for example the new VM that just went in... - We try to add for each patch a boiler plate and a ChangeLog (kernel-source.changes), for example: ------------------------------------------------------------------- Thu Jun 17 15:35:34 CEST 2004 - ak@suse.de - Fix bad use of __initdata in x86-64 mce code [this patch has no boilerplate but others have] - You can use the 2.6.7 vanilla kernel with SUSE, nobody forces you to use the SUSE patched kernel. - We add a number of new drivers that the vendors have not submitted (and work with them to get them submitted but this takes time). - The linux kernel developers make no guarantee that the internal ABI interface stays the same. - And guys - there's even a README.SUSE in the kernel-source and if that commercial OSS guys had read it, they would even had less problems. Andreas -- Andreas Jaeger, aj@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

My problem is already solved,
i can use the new SuSE patched kernel with the OSS :-)

http://www.opensound.com/linux-x86.html#suse

I didn't said that i prefer a vanilla kernel
instead of the SuSE patched kernel ...
My problem was just that i want to get my sound
working
As i'm a 'normal' user and no developer i couldn't
say what really happened with this kernel-headers or
whatever ...
I'm just surprised that there isn't a normal relation
between SuSE and 4Front for discussing such things
internally
and i was really a bit shocked that the OSS president
posted his problems in that way :-(

Thanks for all your replies
best regards
Franz


--- eshsf  schrieb: > >- You can
use the 2.6.7 vanilla kernel with SUSE,
> nobody forces you to
> >  use the SUSE patched kernel.
> 
> Is it the problem of nVidia that vannila
> kaernel(2.6.7) failed to start up X ?
> startx command aborted in vannila kaernel.
> append a log at that time.
> 
> But SUSE's Kernel no problem.
> 
> 
> On Fri, 18 Jun 2004 15:12:40 +0200
> Andreas Jaeger  wrote:
> 
> > 
> > Come on, let's get some facts together - and yes,
> I'm working for
> > SUSE;-)

I know that you work for SuSE and there's no problem
with that - i'm using SuSE since 5.1 and i love it -
i'm just searching for solutions for (my)
problems ;-)
Thanks for your information,
i sent your info about the kernel to D. Mazumdar
and hope it helps them...

> > - Currently no distribution can ship a vanilla
> kernel:
> > 
> >   *  For example to support AMD64, a small patch
> has to be issued for
> >      2.6.7 (details on the discuss at amd64.org
> mailing list).  The
> >      patch is getting smaller each kernel release
> - and has different
> >      patches in it.
> > 
> > - SUSE is dedicated to get all patches in the
> official kernel.
> > 
> > - During release phase, we do not import all
> patches from Linus, just
> >   those that fix critical bugs.  Therefore our
> 2.6.5 kernel contains
> >   lots of patches that you'll find in 2.6.6 and
> 2.6.7.  The 2.6.4
> >   kernel contained already for example the new VM
> that just went in...
> > 
> > - We try to add for each patch a boiler plate and
> a ChangeLog
> >   (kernel-source.changes), for example:
> > 
> >  
>
-------------------------------------------------------------------
> > Thu Jun 17 15:35:34 CEST 2004 - ak@suse.de
> > 
> > - Fix bad use of __initdata in x86-64 mce code
> >   [this patch has no boilerplate but others have]
> > 
> > 
> > - You can use the 2.6.7 vanilla kernel with SUSE,
> nobody forces you to
> >   use the SUSE patched kernel.
> > 
> > - We add a number of new drivers that the vendors
> have not submitted
> >   (and work with them to get them submitted but
> this takes time).
> > 
> > - The linux kernel developers make no guarantee
> that the internal ABI
> >   interface stays the same.
> > 
> > - And guys - there's even a README.SUSE in the
> kernel-source and if
> >   that commercial OSS guys had read it, they would
> even had less
> >   problems.
> > 
> > Andreas
> > -- 
> >  Andreas Jaeger, aj@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
> > 
> 
> > -- 
> Check the List-Unsubscribe header to unsubscribe
> For additional commands, email:
suse-amd64-help@suse.com 


	

	
		
___________________________________________________________
Bestellen Sie Y! DSL und erhalten Sie die AVM "FritzBox SL" für 0€.
Sie sparen 119€ und bekommen 2 Monate Grundgebührbefreiung.
http://de.adsl.yahoo.com

Laurent GUERBY writes:

On Fri, 2004-06-18 at 15:12, Andreas Jaeger wrote:

...

- We try to add for each patch a boiler plate and a ChangeLog (kernel-source.changes), for example:

------------------------------------------------------------------- Thu Jun 17 15:35:34 CEST 2004 - ak@suse.de

- Fix bad use of __initdata in x86-64 mce code [this patch has no boilerplate but others have]

Hi Andreas,

I assume you get this changelog by rpm -qp --changelog kernel-source-xxx.rpm? If so, one question: are release boundaries noted in this changelog? I see lots of dated and quite well commented entries but I can't seem to find a what point a particular release was made which makes it hard to know in what release a patch went in. May be I'm missing something obvious though...

I got this with: rpm -q --changelog kernel-default|less And we do have some marks in the changelog - but I'll pass this on so that it happens more regular... Andreas -- Andreas Jaeger, aj@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