April 2001 - openSUSE Users - openSUSE Mailing Lists

Fwd: recording from mpu401 - alsa MIDI 0-0 device
by basslake 04 Apr '01

04 Apr '01

---------- Forwarded Message ---------- Subject: recording from mpu401 - alsa MIDI 0-0 device Date: Thu, 15 Mar 2001 16:03:54 -0500 From: basslake <basslake(a)xtalwind.net> Hi all I still havn't been able to compile Muse - may be something amiss as I upgrade my systems - as for now instead of posting gcc output error info - I need to ask some questions. 1:) will it be critical as to which ALSA , and kernel I have ? Say - if I want to keep my present kernel and ALSA drivers, will new Muse require the newer kernels and ALSA drivers . - I have SuSE-linux-2.16 , which came with alsa 0.5.9c I have installed 0.5.9.d successfully without having to update my 2.2.16 kernel . I have set /etc/devfsd.conf to suggested settings I found - inquiries on Google . I have ymfpci724 alsa sound driver - that works great for pcm , and midi mpu401 - (my KAWAI Synth Keyboard) except that I am having quite a difficult time getting - jazz to record midi from my keynboard - jazz plays midi to the MIDI 0-0 device fine though . I figured that Muse would be more ALSA aware . cat /proc/asound/sndstat - gives [04:35pm][Thu Mar 15][basslake:/root]# cat /proc/asound/sndsta* Sound Driver:3.8.1a-980706 (ALSA v0.5.9d emulation code) Kernel: Linux basslake 2.2.16 #1 Wed Aug 2 20:22:26 GMT 2000 i586 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: Yamaha DS-XG PCI (YMF724) at 0xf1000000, irq 10 Audio devices: 0: YMFPCI (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: 0: MPU-401 (UART) Timers: 7: system timer Mixers: 0: SigmaTel STAC9704 [04:35pm][Thu Mar 15][basslake:/root]# I compiled alsa with synth device=yes and it happily compiled fine but with no synth device compiled in configuration . This is probably because oss apps are not ready for the new ALSA sound system - which points to /etc/devfsd.conf , by Richard Gooch [Enable full compatibility mode for old device names.] Musicians don't want to fuss so much when they have ' creating music ' taste in their mouth - but they love the possabilities and high quality of the ALSA drivers . So some of us have to hack ; - \ 2:) Then With my Kernel and ALSA drivers , which Muse version will be most likely to compile . ? SuSE Linux standard kernel 2,2,16 elf - @ /usr/src/linux /usr/src/linux/include /usr/src/linux/include/linux /usr/local/qt/lib/libqt.so.2.2.4 - ALSA 0.5.9d - gcc - 2.95.2 - nothing in /usr/i486-linux-libc6 old 1999 libs in /usr/i486-linux-libc5 probably not needed to compile Muse. ldd --version = ldd (GNU libc) 2.1.3 gcc --version = 2.95.2 These are the standard that came with SuSE version 7.0 - which I just recently bought - seems that they are somewhat Behind standards to compile new applications ; - have to upgrade right out of the box ! muse readme 0.3.8 - says that - '- qt 2.2.0 (best: 2.2.4) ftp://ftp.trolltech.com/qt/source MusE does _not_ compile with older versions - gcc 2.95.3 (untested with other versions) - glibc 2.2.x (untested with other versions) - Linux kernel with rtc (RealTimeClock) driver (device /dev/rtc) (apply "low latency patches" for low timing jitter) - optional ALSA from http://www.alsa-project.org/ checked version 0.5.10b; also checked ALSA OSS-Emulation - of course: an midi synthesizer ' 3:) So Do I need to upgrade to compile muse ? , or does anyone know that with my setup muse should compile ? Thanks for help - I hope the state of ALSA and MIDI improves - so we can get have it a little easier with our music endevors as well . John W Mislan -- God does not play dice" -- Einstein "Not only does God play dice, he sometimes throws them where they can't be seen." -- Stephen Hawking ------------------------------------------------------- -- God does not play dice" -- Einstein "Not only does God play dice, he sometimes throws them where they can't be seen." -- Stephen Hawking

1 0

XFree86 3.3.6 and SAX and /var/X11R6/sax/config/StartConfig
by Jethro Cramp 04 Apr '01

04 Apr '01

Today in an attempt to get Star Office working I tried to switch from XFree86.4 back to 3.3.6 using SAX. The X server wouldn't start and the Serverlog complained of errors in /var/X11R6/sax/config/StartConfig. When I checked the log further against this file I found: 1. It had barfed on every line of the file. 2. StartConfig looked nothing like an XF86Config file in that it was missing lots of sections. I don't know if I've screwed something up or not but in order to check could somebody please send me a copy of their StartConfig file from a 7.1 i386 system. TIA, Jethro

1 1

Test
by Edwin Erdman 04 Apr '01

04 Apr '01

Just a test........... Sorry for this, but my ISP has been bouncing messages from the list. -- Edwin O. Erdman Penguinista - diagonally parked in a parallel universe !!! User# 135893 Machine#s 59387, 82657, 82659 SuSE 7.1 - KDE 2.01 - XF86 4.02

1 0

Newer ALSA RPMs
by Jeffrey K LaCroix 04 Apr '01

04 Apr '01

Does anyone know where I can find some newer (possibly CVS?) ALSA RPMs than the ones that come with 7.1? I don't want to have to compile my own. Hopefully someone out there has some newer ones compiled against the 2.4.0 kernel? Thanks much... Jeff

1 0

7.1 + onstream di30
by Sjoerd Venema 04 Apr '01

04 Apr '01

Hi, I've got SuSE 7.1 running and want to use the Onstream di30 tapedevice to make backups. However, taper sees the device but gives write errors to the device. On the Onstream site there are kernelpatches available for 2.2.16 kernel, but I use the 2.2.18 kernel distributed with SuSE 7.1. Does anyone know how to get the device up and running?? Regards, Sjoerd

2 1

Re: [SLE] The SuSE "boot concept"
by Purple Shirt 04 Apr '01

04 Apr '01

ftp://ftp.suse.com/pub/suse/i386/7.1/full-names/i386/ >From: Albert Wagner <alwagner(a)tcac.net> >To: suse_users<suse-linux-e(a)lists.suse.com >Subject: [SLE] The SuSE "boot concept" >Date: Wed, 4 Apr 2001 06:40:08 -0500 > >Before I go off half-cocked and wipe this system, I thought I had better >give >the benefit of doubt to SuSE, and ask: Where is the documentation for "The >SuSE boot concept?" > >I've been on SysV(Redhat, Mandrake) and BSD-like(Slack) and now I am >confronted with yet another "boot concept", apparently non-standard and >hidden beneath a proprietary layer called SuSEConfig. > >If I understand correctly, this documentation is contained in another >proprietary document, the SuSE Handbook, which was not included in my boxed >set. It seems that only SuSE rpms will install correctly on a SuSE system >and SuSE rpms are as rare as hen's teeth. > >I am not saying that SuSE does not have the right to obfuscate and change >booting, configuration, and installation to suit themselves. What I am >complaining about is that their new approach was not made clear in the >sales >hype and is poorly documented, leaving those coming from other linux >environments at a total loss. > >Those of you who don't know what I am talking about should read: > >/etc/init.d/README > >I sincerely hope that someone can convince me that SuSEConfig is a great >thing and that I am totally wrong. I probably am totally wrong. I hope >so. >I am tired of installing linux systems looking for the ideal. (Slackware >with RPMs?). Meanwhile, I'm going to go find LSB and see what it's all >about. > > >-- >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the FAQ at http://www.suse.com/support/faq > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

2 1

rpm's
by Landy Roman 04 Apr '01

04 Apr '01

is there a solution for suse 7 for these erros trying to upgrade rpm's many have said that lates rpm from suse does this, but i dont see their upgrade for suse 7.0 this was on latest fetchmail rpm but lots of rpms are giving me thi error i hope the solution is not 7.1 since even i have box already i dont want to upgrade yet only packages with major numbers <= 3 are supported by this version of RPM error: fetchmail-5.8.0-1.i386.rpm cannot be installed -- SuSe 7.0 Linux 2.4.2 i686 Tue Apr 3 18:05:00 EDT 2001

3 3

modprobe ide-scsi
by scc 04 Apr '01

04 Apr '01

Hi everyone. Is there any place I can put the modprobe command without having to type it every time I want to use it? Suse 7.1. Thanks, Steve

5 5

Problem with cdrecord
by Gerassimos Toumazatos 04 Apr '01

04 Apr '01

Hi, I' m using SuSE 7.1 and I have a Plextor scsi cdwriter. Allthougth my system recognizes the device when I run the command "cdrecord -scanbus" as root I get the following message: "bash-2.04# cdrecord -scanbus Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 Jφrg Schilling cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. bash-2.04# " Can anyone help me? Thanks. Gerassimos

4 6

Re: [SLE] Fwd: Re: [SLE] is # or ! a comment?
by Tor Sigurdsson 04 Apr '01

04 Apr '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, You wrote: [snip] > >There is one set of programs I know of that uses ! as a comment character, > >and there are versions of this for DOS, Windows, and Unix--Sun systems, > >I believe, but am not sure. Those programs are from EESOF, or what is [snip] There is a program on Linux that uses '!' as a comment character. Check out the file "/usr/src/linux/arch/i386/boot/bootsect.S" for a sample. The program is 'as' '#' is used by most, if not all scripting languages as a comment character, and by make as well. '*' is used by AIX as a comment character, f.ex. in /etc/filesystems. '//' is C++ '/*..... */' is C, and I'll be damned if there wasn't some Pascal that used it as well I have also seen '(*....*)', '{......}' ''' ( visual basic ) and a few others that I can't recall just now... Comment characters are based on the whim of the author of the language in question :-) [snip] I hope all this helps..... ( well.. informs :-) - -tosi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6ymjE6mRH+PEpr2YRApF9AKCU/mdSpqEtXQfGu2pnPkNpXlMX7QCgj68j VL09gsJ8UvuP5KDT2d6FhcQ= =GrMq -----END PGP SIGNATURE-----

1 0