zero0w

I guess it can run KDE on 160MB but swapping will be very often.

I would choose to run XFCE-4 with less memory configuration.

Celeron 800 should run OK.

However, make sure you have enough main memory.

256 MB is probably the minimum you need in order to run KDE and other programs. More is better.

According to the Creative Open source page:

http://opensource.creative.com/soundcard.html

Driver support on both

1. Dell model of SB Live! (snd-emu10k1x)

2. SB Audigy LS (snd-audigyls)

is coming with ALSA 1.0.6.

You can try the ALSA 1.0.6 official release:

http://www.alsa-project.org/

Notice each of them has its own module name.

Do not use 'snd-emu10k1' module with these soundcard models.

EMU10k1X is different from EMU10k1.

The former is a Dell model of SB Live!, which is different from the standard SB Live! on the market.

The upcoming ALSA 1.0.6 release will support the Dell model:

http://mandrakeusers.org/index.php?showtopic=17294

Well, it looks my next upgrade card will be nVidia's NV43: GeForce 6600 GT w/ AGP support.

It has 8 pipelines, 500Mhz GPU/ 128bit 1000Mhz video memory support (exact figures may differ on launch) - not a vast improvement over 9800XT but it will exhibit excellent Linux support and is reasonably priced US$ 199. NV43 will also have some fine tuning in memory performance. 3D Mark 2003 sample testing suggests it will score around 8,000. Not bad.

http://www.theinquirer.net/?article=17619

Just installed it. Works great.

This is mostly a bug-fix release. Good job.

Good news!

The Creative Open Source page has been updated.

http://opensource.creative.com/soundcard.html

Both

1. Dell Model SB Live! (snd-emu10k1x)

2. SB Audigy LS (snd-audigyls)

will be supported in ALSA 1.0.6.

ALSA 1.0.6 is now available at the ALSA official page:

http://www.alsa-project.org/

http://www.linuxhardware.org/article.pl?sid=04/08/16/1850201

Well I suppose the whole range of Creative soundcards will become Linux compatible pretty soon with updated ALSA drivers.

PS: Notice each of them has its own module name.

Do not use 'snd-emu10k1' module with these soundcard models.

More likely, it is both bias and missing the point.

I believe when you generate enough response/feedback from the Windows people, it just means there is something happening - rather than a non-issue as they claimed.

The recent OSS and Linux commentary is getting more and more interesting. I am bemused to read these two blog items in the same Oreillynet.com network. Take a look, they are interesting read (don't read the second before the first or you'll miss the fun =P ):

http://www.oreillynet.com/pub/wlg/5299

http://www.oreillynet.com/pub/wlg/5368

Sometimes, you got to respond as if they were not a real threat.

Sounds convincing, isn't it?

Doom III changes everything, so I suggest try and see approach:

http://www.anandtech.com/video/showdoc.aspx?i=2146

There is some grey area on distributing Windows DLL codec on other platforms.

License and EULA may prevent you to use it (or reverse engineer to get it running). Having a legitimately, licensed MPEG-4 / MP3 compliant codecs bring GREAT credibility to the Linux platform.

Hooray! Realplayer 10 for Linux final, downloading now!

Other related links

1. Realplayer 10 for Linux download, RPM version:

https://helixcommunity.org/forum/forum.php?forum_id=145

http://www.real.com/linux/

https://player.helixcommunity.org/2004/downloads/

2. Helixplayer & Realplayer Project page (for most updated version)

https://helixcommunity.org/projects/player

3. Player FAQ and tutorial

https://player.helixcommunity.org/2004/unix/

http://fedoranews.org/tchung/realplayer/

To Linux Firefox users:

Please note that in Firefox 0.8-0.9.x, there is a bug which prevents passing proper metafile to Realplayer 10 for online streaming playback:

4. Firefox bug: Realplayer playback issue

http://bugzilla.mozilla.org/show_bug.cgi?id=240068

However, this bug does not exist in vanilla Mozilla.

Hence you can use Mozilla in the meanwhile until this bug is fixed.

IMHO, I think this news is important enough to be moved to Everything Linux.

Just don't distract yourself with some non-Linux business like E-learning or other dotCOM (ad)ventures.

<{POST_SNAPBACK}>

 

do I detect a certain amount of sarcasm there? :o

<{POST_SNAPBACK}>

Look at some of the earlier annual report of MandrakeSoft since 1999/2000 (the year it started losing money), and you will find out what I mean.

Go Mandrake! Go!

Mandrake has made some great deals recently so I believe it has a bright outlook.

Just don't distract yourself with some non-Linux business like E-learning or other dotCOM (ad)ventures.

As DOOM 3 release is approaching, here comes more detail on DOOM 3 hardware requirement, from the Official DOOM 3 [H]ardware Guide:

http://www2.hardocp.com/article.html?art=NjQ0

On the contrary I like the feel of GUI, guess it's a matter of taste.

My SB Live! supports hardware mixing so I don't have this problem.

Just read the OSNews article today:

http://www.osnews.com/story.php?news_id=7852

I have tried the MainActor v5 Demo (with watermark) on Linux.

I think it's pretty cool stuff. You can get the demo and try it.

Feel free to report your feedback on the Linux client at the Skype forum:

Skype for Linux forum:

http://forum.skype.com/bb/viewforum.php?f=18

I've tried installing the ALSA drivers by downloading the latest cvs files and installing as guided here. It appears to be compiling and installing properly. But when i go to insert the module it spits out this error message:

 

[root@mandy alsa-driver-1.0.5a]# modprobe snd-emu10k1

http://www.alsa-project.org/~james/alsa-driver/

After looking into the file "audigyls.diff.txt" located at the above address:

snd-emu10k1x-objs := emu10k1x.o

+snd-audigyls-objs := audigyls.o

 

obj-$(CONFIG_SND_EMU10K1X) += snd-emu10k1x.o

+obj-$(CONFIG_SND_AUDIGYLS) += snd-audigyls.o

Now I suspect the ALSA module for SB Audigy LS would be called snd-audigyls, not snd-emu10k1.

Try to modprobe snd-audigyls and see if there's any response from your soundcard (make sure your mixer is not muted).

Good luck. :D

NVIDIA's SLI won't help as logically, i.e. from the perspective of the application, API and OS, only the memory on "one card" is available. e.g. two 256MB boards in SLI = 256MB of VMemory. Reason is that both cards need the same data onboard to be able to work on the same frame; neither the SLI bridge nor PCI-Express are fast enough for one card to fetch stuff from the other's video memory, so SLI doesn't support it.

I remember back when 3dfx Vodoo2, dual SLI did provide higher resolution of 3D acceleration (2 x 8MB PCI Vodoo2, I believe), so I won't count it off so fast.

I think both cards would store the same texture, maybe.

But there are other information which are different on the dual configuration.

As for bandwidth in SLI, uncompressed data bandwidth is certainly not great.

But compressed data should be another story. I happen to think nVidia should have improved this technology for the time it has acquired it from 3dfx years ago - because PCI Express has greater bandwidth, the SLI should not be sitting ducks or risk useless in that regard.

are there cards with 512MB?  i have found only very few...and they're fscking insanely priced.

<{POST_SNAPBACK}>

Maybe PCI Express dual GeForce 6800 configuration would fit the bill now.

Also, check out the new GeForce 6800 LE, when overclocked it matches GeForce 6800 closely:

http://www.tbreak.com/reviews/article.php?cat=grfx&id=325

Although it is currently only available thru OEM channels, nVidia may offer it to wider audience later once GeForce FX5200/5600 series phase out.

I would suggest that you wait until checking out Doom III on Linux, then the clear answer will come out because it is the first game to push your graphics card to the edge on this platform.

id's Robert Duffy has updated his .plan with a huge post regarding Doom 3 system requirements. Covering what amount of VRAM you'll need for certain across-the-board video quality levels in the game, in addition to mentioning that Doom 3 is using Ogg Vorbis and a variety of other snippets of detail on RAM usage and such:

http://www.bluesnews.com/cgi-bin/finger.pl...=20040726134608

Edit:

Please see the next post.