I think the best thing I did when I decided to make the switch a permanent one, is to stop comparing it to other desktop environments. This allowed me to fully experience the GNOME 3 desktop without comparing it with KDE, XFCE and so on. With this new mindset, I found that the integration and work-flow were actually quite refreshing.
Wayland seems awesome. Take everything wrong with xorg and pretend that you can rewrite xorg from scratch, with all the knowledge we have in 2014. Fantastic.
Why can't we have something similar for sound? I'm sick of trying to install software (a lot of DAWs lately) that has dependencies that will break sound for me in other ways. Example: Why should I install libjack2, killing alsa-equal, so that I can use a DAW but now suddenly my media players don't work (namely ncmpcpp)?
It's simple. I want a program that is supposed to make sound come out of speakers (or the headphone jack) do exactly that. I don't want to install different libraries to make some things work and break others. I hate that on my linux box, I can have a browser window open with some stupid flash applet running that hogs my sound card, and then not be able to have sound produced from any other application.
This problem does not exist on OSX. It does not exist on dreaded m$ OSes. In fact, in 1994 I built an Amiga with multiple sound cards for both recording music and music playback. It "just works" flawlessly to this day.
Why is linux sound so archaic? Can we not find developers ready to tackle one of gnu/linux's biggest current failures insofar as being able to make inroads into desktop computing? Wayland, but for sound. Screw all that old alsa/jack/pulse garbage and rewrite it from scratch to work the way it does everywhere else, but on linux.submitted by cloverskull
[link] [1 comment]
It’s been hard to get the BeagleBone Black(BBB); limited production capabilities have fought with some big adoption stories. If you are unfamiliar with the BBB, its a small board computer in the same size factor as the Raspberry Pi, but with eMMC storage, micro-SD slot and lots of I/O pins – what it lacks in media player cores, it makes up for in clock speed.
Thats “hard to get” nature is about to change though according to a blog post. Production is being ramped up at CircuitCo where they are also upping the storage from 2GB to 4GB which will give more breathing space to the new Debian distribution being shipped on the eMMC of BeagleBones, replacing the previous default Angstrom Linux. The upgraded boards will be referred to as Rev C BBBs. The price will likely be going up to cover the extra memory and production ramp-up but with a back-orders for 150,000 units, CircuitCo are going to be busy.
I recently converted one of my cryptocoins mining rig into a gaming pc running arch. Because the proprietary drivers for my Radeon R9 280x are garbage ( and the open source one has little support for the latest generation of gpus) my plan is to install windows in a vm and play games there using vga passthrough. My mobo is a Gigabyte Sniper B5 (it has vt-d) and vga output using the haswell gpu from a celeron g2820 (might be mistaken but is from the haswell family and supports virtualization according to intel specs). My question is the following : when I switch to the windows vm do I need to plug the monitor into the R9 280 x or the image will be translated to the intel gpu?
Edit: corrected spelling of the word windowssubmitted by Darth_bunny
[link] [3 comments]
While the Radeon R9 290 has been out more than a half-year, the open-source support is still poor. In fact, when running the latest open-source code there still isn't hardware acceleration by default, and with distributions like Ubuntu 14.04 LTS there's only mode-setting support without any 2D/3D hardware acceleration. In my most recent R9 290 open-source testing, I installed Ubuntu 14.04 x86_64, then installed the Linux 3.14 kernel (and later, Linux 3.15 Git), followed by using the Oibaf PPA for Mesa 10.2-devel and xf86-video-ati Git.
After running Ubuntu for a while, I decided to go to Debian testing (Jessie) following a recommendation from a friend.
The problem is now that the sound is not working even though this worked perfectly on both Ubuntu 12.04 and 13.10
When I run
lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
Googling this sound problem is a total mess. I really hope someone can help.submitted by spacemanspiiff
[link] [1 comment]