On Wed, Apr 11, 2018 at 07:57:07PM -0500, David Wright wrote:
> On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote:
> > I am trying to upgrade two test boxes from Wheezy to Stretch (skipping
> > Jessie). The upgrade worked on one of them, although I ran into errors and
> > had to run "apt-
On Wednesday, April 11, 2018 03:27:48 AM Gene Heskett wrote:
> What seems to be lost on you folks not running realtime patched kernels,
> is that when linuxcnc is running, it has total control over the
> hardware, and that linux becomes a client of the realtime system,
> getting what cpu time is le
On Tue, 10 Apr 2018, Niclas Arndt wrote:
> 1. Can the latest microcode updates still in stretch-backports be
> trusted to run properly by now?
> https://newsroom.intel.com/wp-content/uploads/sites/11/2018/04/microcode-update-guidance.pdf
Yes, these microcode updates are stable.
The same might or
On Thursday 12 April 2018 07:44:39 rhkra...@gmail.com wrote:
> On Wednesday, April 11, 2018 03:27:48 AM Gene Heskett wrote:
> > What seems to be lost on you folks not running realtime patched
> > kernels, is that when linuxcnc is running, it has total control over
> > the hardware, and that linux
On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote:
> hello,
> I am getting an error on boot in my dual boot Win 10-Debian 9 system,
> ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/
> exmutex-393)
> ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66]
> (Nod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Apr 12, 2018 at 08:09:08AM -0500, Anil Duggirala wrote:
> On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote:
> > hello,
> > I am getting an error on boot in my dual boot Win 10-Debian 9 system,
> > ACPI Error: Cannot release Mutex [PATM]
On Thu, 12 Apr 2018, Anil Duggirala wrote:
> On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote:
> > I am getting an error on boot in my dual boot Win 10-Debian 9 system,
> > ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/
> > exmutex-393)
> > ACPI Error: Method parse/executi
Thanks!
On Thursday, April 12, 2018 08:43:50 AM Gene Heskett wrote:
> On Thursday 12 April 2018 07:44:39 rhkra...@gmail.com wrote:
> > On 2nd reading, I think the answer is yes, i.e., if I have a midi
> > program making use of the / a real time kernel, it will have total
> > control of the machin
David Parker wrote:
...
given they are test boxes you should go straight
to reinstall from netinst image or whatever you can
get that will do it. :)
much much faster than trying to fiddle around with
upgrades. especially when many versions in between.
of course, always check installation
Gene Heskett wrote:
...
> Lots of other stuff that would be TL;DR for most here.
i'm actually facinated by this level of knowledge and
wish i had such toys around for milling some rocks into
carvings so i wouldn't have to do it by hand...
good fodder for daydreaming. :)
songbird
Anil Duggirala wrote:
...
> Can someone please help me out, or let me know why Im not getting any help
> with this,
lack of details about machine, debian versions,
things tried, etc, and for me being busy with
other things for a while to even begin to look
at this message to begin with.
s
Bruce Byfield wrote:
...
> The Intuos Draw is clearly supported to a degree, because I am using
> it as a replacement.
have you read through this site?
https://linuxwacom.github.io/
songbird
On Thu, Apr 12, 2018, at 8:31 AM, to...@tuxteam.de wrote:
> Is there any negative effect on your boot you link to this
> message?
>
I do not understand the wording of this question, could you please rephrase it?
I did not link anything to my O post. The only negative effect I see is the
error
> Assuming the kernel is not broken, it means that the firmware writers
> screwed it up, and are trying to release a lock (mutex) that was not
> taken.
>
I am also getting missing firmware notices, namely,
[9.269384] ath10k_pci :03:00.0: firmware: failed to load
ath10k/pre-cal-pci-:0
> have you updated BIOS to latest version from machine
> vendor?
>
I have not, I will see if there is a newer version. I am running Debian Stretch
on a Dell 3580 Latitude machine. I have not tried anything so far to fix this
error,
thanks a lot,
On Thu, 12 Apr 2018 11:40:15 -0500
Anil Duggirala wrote:
> On Thu, Apr 12, 2018, at 8:31 AM, to...@tuxteam.de wrote:
>
> > Is there any negative effect on your boot you link to this
> > message?
> >
>
> I do not understand the wording of this question, could you please
> rephrase it? I did no
> I think what he means could be said in other words for example like "Is
> there any negative effect when the machine boots that you believe is
> related to this error message?"
>
I am also getting notices of missing firmware,
that is the only other thing I have noticed,
thanks,
On Thu 12 Apr 2018 at 06:42:33 (-0400), Dan Ritter wrote:
> On Wed, Apr 11, 2018 at 07:57:07PM -0500, David Wright wrote:
> > On Wed 11 Apr 2018 at 15:31:32 (-0400), David Parker wrote:
> > > I am trying to upgrade two test boxes from Wheezy to Stretch (skipping
> > > Jessie). The upgrade worked o
Anil Duggirala wrote:
>> have you updated BIOS to latest version from machine
>> vendor?
>>
>
> I have not, I will see if there is a newer version. I am running Debian
> Stretch on a Dell 3580 Latitude machine. I have not tried anything so far
> to fix this error, thanks a lot,
what is referr
On Thu 29 Mar 2018 at 21:19:38 (+0100), Jonathan de Boyne Pollard wrote:
> David Wright:
>
> >an extra ^@ character¹
> >
>
> Unix & Linux Stack Exchange had this last year.
These look like very different symptoms. Taken in reverse order,
> * https://unix.stackexchange.com/questions/360830/
The
On Tue 03 Apr 2018 at 08:37:29 (+0200), john doe wrote:
> On 3/30/2018 6:11 PM, David Wright wrote:
> >On Fri 30 Mar 2018 at 08:05:31 (+0200), john doe wrote:
> >>On 3/29/2018 9:56 PM, mick crane wrote:
> >>>On 2018-03-29 19:34, Curt wrote:
> On 2018-03-29, mick crane wrote:
> >following r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Apr 12, 2018 at 11:43:09AM -0500, Anil Duggirala wrote:
> > Assuming the kernel is not broken, it means that the firmware writers
> > screwed it up, and are trying to release a lock (mutex) that was not
> > taken.
> >
>
> I am also getting mi
to...@tuxteam.de composed on 2018-04-12 23:43 (UTC+0200):
> On Thu, Apr 12, 2018 at 11:43:09AM -0500, Anil Duggirala wrote:
>> Do you also recommend updating my BIOS?
> I don't know. There are others around here with more experience in
> that than me.
IME, a BIOS update is usually the only way
Hi, deloptes.
On 12/04/18 02:29, deloptes wrote:
>> Killing the 'pulseaudio' process solved the problem. Good to have sound
>> again :)
> Did you remove the .pulse directory before killing or not?
I was checking, but that directory did not exist. So I simply tried
killing the process directly.
On Thu, 12 Apr 2018, Anil Duggirala wrote:
> I am also getting missing firmware notices, namely,
> [9.269384] ath10k_pci :03:00.0: firmware: failed to load
> ath10k/pre-cal-pci-:03:00.0.bin (-2)
> [9.269386] ath10k_pci :03:00.0: Direct firmware load for
> ath10k/pre-cal-pci-00
On Thursday 12 April 2018 10:50:07 songbird wrote:
> Gene Heskett wrote:
> ...
>
> > Lots of other stuff that would be TL;DR for most here.
>
> i'm actually facinated by this level of knowledge and
> wish i had such toys around for milling some rocks into
> carvings so i wouldn't have to do it b
26 matches
Mail list logo
