On my primary Linux workstation (Ubuntu 14.04, should be the same as Mint 17): 3.13.0-29-generic
On a second linux machine: 3.15.0-031500rc8-generic though this will become a 3.16 variant upon the next reboot (using kernels downloaded from the link several messages ago). My SolidK install is using a 3.14-1-amd64 kernel though it was installed with a 3.13 based kernel (I am actually impressed by this). Debian stable is of course quite a bit behind with 3.2, but that is to be expected (probably not a great idea to rely on the btrfs implementation of Debian at this point). Nobody runs Debian to play with next generation features. On Mon, Jun 30, 2014 at 3:36 PM, Mel Walters <melwalt...@telus.net> wrote: > Just wondering what kernal your running? > > running uname -a on SolydK gave: > Linux mysolyd 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 > GNU/Linux > Seems to do OK for modern > > on my workstation I get: > Linux myworkstationsname 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 > x86_64 GNU/Linux > (Debian Stable) > On Mon, 2014-06-30 at 14:26 -0600, Greg King wrote: > > I might try a live version of a really new kernel, but I'm going to > stick with Linux Mint LTS editions such as Mint 17, so it would be just for > informational purposes. The issue is the newness of the chips. Support will > arrive eventually. A $30 external sound card workaround is not a bad option > either. > > > > Greg > > ----- Original Message ----- > > From: "Mel Walters" <melwalt...@telus.net> > > To: clug-talk@clug.ca > > Sent: Monday, 30 June, 2014 1:24:14 PM > > Subject: Re: [clug-talk] Linux rules! and continues eliminate the > competition > > > > So you did not want to try the free experiment I sent in my last from my > > last post? A live boot would tell you in short order if it would work > > with your hardware. Why not try it? > > So far sound has just worked with anything I have tried it with Solyd > > Linux. Isn't that strange? > > > > On Mon, 2014-06-30 at 10:24 -0600, Greg King wrote: > > > I note from the product sheets that these all say Windows support and > one says no Mac support. Do you know from experience that they will work > with Linux? I don't want to swap one audio problem for another although it > is a pretty cheap experiment. > > > > > > Greg > > > > > > ----- Original Message ----- > > > From: "Bogi" <khan...@shaw.ca> > > > To: "CLUG General" <clug-talk@clug.ca> > > > Sent: Sunday, 29 June, 2014 3:58:32 PM > > > Subject: Re: [clug-talk] Linux rules! and continues eliminate the > competition > > > > > > I will note that this is not a solution but a workaround. > > > you can get one of them external USB sound devices, plug it in, and > more > > > likely than not, you will get better sound than your built in (card) > could > > > ever produce. > > > so without express recommendation: > > > http://www.memoryexpress.com/Products/MX31016 > > > http://www.memoryexpress.com/Products/MX25819 > > > > > > Now your problems could well stem from a bad driver, but they could be > rooted > > > in some out of spec hardware. Now i am not saying that this applies to > your > > > case hare, but generally speaking google for problems with you device > > > regarding you driver, if you find mention then check it, maybe there > is already > > > a solution, if not, just silently seek out the latest version of said > driver > > > from the developers website, many bug-fixes take years to get into > distro > > > repositories, while being available for download and compile on the > developers > > > website. > > > Bar a that, you may actually have a faulty hardware, this does not > seem to be > > > the case here, but in such case, i am sure the merchant you got your > hardware > > > from would be willing to replace the motherboard, just make sure you > have the > > > proper in shop replacement type warranties available for you. > > > > > > The root of the problem is the lack of systematic Linux distribution by > > > hardware manufacturers and retailers. And that should lead to a bit of > > > thinking from the community and a lot of action from the commercial > partners > > > who do make and distribute computer hardware. > > > > > > One way to do this, is for the community to offer a testing and > certification > > > platform for new hardware, make a certified for Linux sticker if you > like, so > > > the hardware manufacturers and retailers can advertise their hardware > works > > > with Linux or not. We need to make this a consistent and reliable > service that > > > can be accesses by commerce globally or locally. > > > > > > Ultimately the vendor do not have to ship it with Linux, tho we would > love it > > > better if they did, but they can sure put the sticker on the hardware > to > > > designate it as works with Linux 3.0+ for example :-) > > > > > > Cheers > > > Sam > > > > > > > > > On June 29, 2014 Sunday 10:27:17 Greg King wrote: > > > > "Linux dominates supercomputers as never before" See article: > > > > > http://www.zdnet.com/linux-dominates-supercomputers-as-never-before-7000030 > > > > 890/?s_cid=e539&ttag=e539&ftag=TRE17cfd61 > > > > > > > > Too bad it can't do the same on the desktop. For example, I just > bought a > > > > new system with a Gigabyte motherboard and I7 processor. I put Mint > 17 on > > > > it and 95% of things just work, except for the sound - full of > static and > > > > choppy. I've spent a few hours already downloading new drivers from > Realtek > > > > and compiling them (not exactly a "consumer friendly" activity) and > it > > > > still does not work correctly. Apparently it is a known bug with > Realtek > > > > ALC892 audio but none of the solutions I have found from googling > around > > > > has fixed it yet. Not much has changed in the past 7 years since I > similar > > > > problems with sound on a new machine back then too. Of course the > DVD that > > > > came with the motherboard is loaded with Windows drivers. It's > encouraging > > > > that Realtek at least published Linux drivers - too bad they were > never > > > > debugged, or the docs on how to get them to work are incomplete. > > > > > > > > If anyone else has solved this issue I'd love to hear the solution. > > > > > > > > Greg > > > > > > > > _______________________________________________ > > > > clug-talk mailing list > > > > clug-talk@clug.ca > > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > > **Please remove these lines when replying > > > > > > > > > _______________________________________________ > > > clug-talk mailing list > > > clug-talk@clug.ca > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > **Please remove these lines when replying > > > > > > _______________________________________________ > > > clug-talk mailing list > > > clug-talk@clug.ca > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > **Please remove these lines when replying > > > > > > > > _______________________________________________ > > clug-talk mailing list > > clug-talk@clug.ca > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > > _______________________________________________ > > clug-talk mailing list > > clug-talk@clug.ca > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > > _______________________________________________ > clug-talk mailing list > clug-talk@clug.ca > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying >
_______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
