Something for you Linux folks to read

[Asher]

I concur with Ari, I literally chuckled to myself reading that post.

[Sava]

There's no need for you to be upset because this is all over your head. After all, you dropped out of compsci to go to some liberal arts college, I'm surprised you could figure out how the Post Reply button works.

Actually Richard, I transferred from a bloated, private college that was a bureaucratic mess with no job placement program to a fully accredited professional institution that has a 97% job placement for graduates with average starting salaries at $47,000 US.

And despite the fact I work as an IT consultant, build networks and computers in my free time for a substantial part time salary, I have the luxury of working with leaders in the game industry who are my instructors.

Again, the whole fan boy thing suits you because you don't know that much else

[Asher]

Actually Richard, I transferred from a bloated, private college that was a bureaucratic mess with no job placement program to a fully accredited professional institution that has a 97% job placement for graduates with average starting salaries at $47,000 US.

And despite the fact I work as an IT consultant, build networks and computers in my free time for a substantial part time salary, I have the luxury of working with leaders in the game industry who are my instructors.

Give me the names of these "leaders" in the game industry that are your instructors.

Hell, even my Uni offers a BSc in compsci with a concentration in game design, and has some of the Bioware PhDs teaching the upper level courses. I'd be interested to hear what your college teaches you.

---------------

On a side note, I finally got Nvidia drivers working in Linux. For some reason, Nvidia's installer wouldn't install properly to load the kernel module on bootup, so instead of pissing away time finding out the proper way to do it, I added the insmod command at the very top of /etc/init.d/sysklogd, and now it works perfectly. (yay tuxracer).

But the sound is more of a pain in the ass. I've got a SB Audigy sound card, so I downloaded the drivers and tools from Creative's website for Linux, followed the instructions to the letter, compiled all the components, etc. But when it came to running the configuration script, it told me /dev/mixer doesn't exist, and it doesn't do anything.

Anyone know a way around that?

[Ari Rahikkala]

On a side note, I finally got Nvidia drivers working in Linux. For some reason, Nvidia's installer wouldn't install properly to load the kernel module on bootup, so instead of pissing away time finding out the proper way to do it, I added the insmod command at the very top of /etc/init.d/sysklogd, and now it works perfectly. (yay tuxracer).

http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-custombootscripts

(Not the most painless way to do this that I've seen, BTW) tells where you should put your custom scripts. /etc/modules is where you should put the names of the modules you want to load at bootup in Debian.

But the sound is more of a pain in the ass. I've got a SB Audigy sound card, so I downloaded the drivers and tools from Creative's website for Linux, followed the instructions to the letter, compiled all the components, etc. But when it came to running the configuration script, it told me /dev/mixer doesn't exist, and it doesn't do anything.

Audigy is controlled by the emu10k1 drivers, which are in the vanilla kernel tree. All you should need to do is to include support for SB Live! in make (?:|menu|x)config (add "emu10k1" to modules.autoload if you decide to build it as a module) and optionally run audigy-script. But just as a wild guess, try modprobe emu10k1. If that works, the program that you downloaded did build the module succesfully and put it in the right directory but forgot to load it.

[Asher]

I've tried the emu10k1 drivers in the kernel (I downloaded 2.4.20 and recompiled it with SB Live support enabled), still had no sound.

I'd read online that I need he latest emu10k1 from Creative's SourceForge page (dated sometime in December), so I got those and installed them.

I got the emu10k1 module to load now with modprobe (did this about a half hour ago now), and the sound does work...sorta. All it does is takes the input from my microphone and outputs it to the speaker, I get no sounds from the computer itself.

When I run "audigy-script" it just instantly returns me back to the prompt, no output at all...

[Ari Rahikkala]

Hm... the script does not have any echo statements and it's possible that all the programs that it uses are quiet...

# Requirements:
# ------------
# This script needs the following to be installed:
#
# -the emu10k1 tools:
# emu-config, emu-dspmgr and the dsp .bin files
# -aumix (installed by default on many Linux distros)

Does your system fill these? If it does but the script doesn't work, you could try fiddling with aumix itself.

[Asher]

It's somewhat working now, I don't know what I did though.

I added "ac97_codec" as a module to load, just did the whole install procedure again, rebooted, and TuxRacer has sound...

KDE still won't play any sounds when I map sounds to certain KDE events, but I may just need to configure KDE for it now...

Thanks for your help though, Ari, much appreciated.

[Ari Rahikkala]

KDE still won't play any sounds when I map sounds to certain KDE events, but I may just need to configure KDE for it now...

KDE uses aRts for playing its sounds. www.arts-project.org/doc/handbook/artsd.html (might be down, Google cache is available) says you need to enable it in the KControl Sound Server panel.

Thanks for your help though, Ari, much appreciated.

Tech support speaks louder than advocacy .

[Inverse Icarus]

http://www.cnn.com/2003/TECH/biztech/02/01/microsoft.security.reut/index.html

[Asher]

Oh my God, how stupid can those "experts" be?

"Trustworthy Computing is failing," Russ Cooper of TruSecure Corp. said of the Microsoft initiative. "I gave it a 'D-minus' at the beginning of the year, and now I'd give it an 'F."'

Yeah, a product that came out a couple years before "Trustworthy Computing" even existed, and a patch was released to fix the problem back in October.

The problem is people don't patch, for whatever reasons they have, and it has nothing to do with the "trustworthy computing" initiative.

In October Microsoft released a fix for a different SQL Server problem that if installed in the expected manner would have made patched systems vulnerable again, he said. "If I followed their advice I'd have been vulnerable."

*cough*Bull*****cough*

Can someone point me to the fix for the problem which makes patched systems vulnerable again...

Pathetic article, dumbass analysts...

Yes, the patching system needs work, and yes, that patching system was completely overhauled for SQL Server 2003 which is due out in a couple of months to replace 2000 (which was affected). Trustworthy computing had zero impact on SQL Server 2000's designs, and when people knock the trustworthy computing stuff and point to difficulty in patching SQL Server 2000, I have to wonder how they can have a job as an industry analyst...

[Asher]

Originally posted by Ari Rahikkala
KDE uses aRts for playing its sounds. www.arts-project.org/doc/handbook/artsd.html (might be down, Google cache is available) says you need to enable it in the KControl Sound Server panel.

It has aRts enabled, but the "test sound" button is greyed out.

When I try to use aRts from the commandline to specify to use /dev/dsp, it tells me:

[/home/glonk/335/asst1]> artsd -D /dev/dsp
artsd: error while loading shared libraries: libvorbisfile.so.0: cannot open shared object file: No such file or directory

I've tried apt-get to get anything vorbis related, and it still says it.

[Ari Rahikkala]

WTF? Is that still broken? When I first started using Vorbis I had to fix that... and I can't even remember how long ago that was. More than a year... at least.

What you need to do is to create symlinks from the files your programs need to where the libraries actually are. I'm not sure about the exact names, but a little web search reveals that /usr/lib/libvorbisfile.so.0 needs to be a link to libvorbisfile.so.3 to work (if the name hasn't changed, of course). I'm not sure if this is the Right Way, but it worked for me and I never even got a warning from it, much less any problems. The same procedure needs to be done for all other Vorbis-related files - libvorbisenc and libvorbis, at least (on my system).

What I need to do now is to go to Debian's website, find out about their bug tracking system, and ask if the maintainer of the Vorbis packages intends to make them bloody work in Woody within this decade...

[Ari Rahikkala]

Well, as I expected, it's already been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=178756 . And with bad luck won't be fixed until Sarge is released, which means that you can look forward to a working libvorbis (or whatever it will be called) package in stable around the time when Duke Nukem Forever is out...

[Velociryx]

Repeat after Asher:

Gates is God...Microsoft makes the best products in the world....None can compare, and all shall fall to the mighty scythe of The Gates.



-=Vel=-

[Drake Tungsten]

I'll trust the experts over some Canadian coms-sci student any day of the week...