date:20180410

Re: graphic tablet controls

2018-04-10 Thread Bruce Byfield

"how recent a kernel do you have?  what version of
Debian are you on?  what desktop?"

I'm running stretch, using a 4.9.0-6 kernel. The problem exists on all
the major desktops including GNOME, KDE, Cinammon, and LXDE, so the
problem is unlikely to be the desktop

"First of all check if your Wacom device is supported by linux - not
all of them are.

For more check here

https://www.reddit.com/r/linuxquestions/comments/3yfz1v/wacom_intuos_draw_and_linux/;

Thanks for the link, but I already know that the Intuos Draw is
supported at least partially, because I am using it as a mouse
replacement, and stretch detects it. The question is why the desktop
tools can't detect it.

I found some information on the Arch website that didn't directly help
me (https://wiki.archlinux.org/index.php/Wacom_tablet), but it does
suggest that /dev/input/wacom should have been created -- which, on my
system, didn't happen. Any idea if that file could be created manually
-- and, if so, how?



The Intuos Draw is clearly supported to a degree, because I am using
it as a replacement.

o ___o
Bruce Byfield (on Pacific time) 604-421-7189
Writer of "Designing with LibreOffice"
www.designingwithlibreoffice.com

Re: SSD's and many edits of a single file

2018-04-10 Thread David Christensen


On 04/09/18 20:58, Gene Heskett wrote:

On Monday 09 April 2018 21:25:34 David Christensen wrote:


On 04/09/18 07:30, Gene Heskett wrote:

On Monday 09 April 2018 09:51:37 Greg Wooledge wrote:

On Mon, Apr 09, 2018 at 09:46:07AM -0400, rhkra...@gmail.com

wrote:

To your original problem, have you tried going to a command line
and throwing in a couple =sync=s?  I would try that, maybe after
saving in your editor, and again maybe after open and / or saving
in the cnc program.


As others have explained, the OS (Linux) keeps a cache of file
contents that have been written by applications, but not yet
committed to permanent storage.  If you "save" from within the text
editor, then the saved contents should be immediately visible to
other processes reading the file, regardless of whether it has been
synced to disk. They'll simply get the cached version.


Which is not happening after several hours and a hundred or more
edits. Which is why its so intermittent.


On 04/09/18 02:53, Gene Heskett wrote:

Lots of people seem to like gedit, but its saves are the cause of
important configuration files being written back to disk with the
line order totally trashed, as if you had thrown it on the floor in
512 byte pieces, then picked it back up and reassembled it in random
order. Then try to recover a 1400 LOC configuration file...

Thats happened using gedit enough, on several different machines ...


One editor failing would also make me suspect the editor.


But two failing editors would make me suspect some common factor, such
as a shared library and/or the kernel.


I'd buy that if the failures were similar.  They are not.


They both seem to involve getting blocks from an app to memory and 
blocks from memory to disk (and/or disk to memory).  They could be 
variations on a theme.



Can you reproduce the bugs on a machine with straight-up Debian (e.g. no 
linuxcnc)?



As a safety net, I would suggest a versioning file system (e.g. similar 
to the versioning feature of VMS).  STFW is pretty thin, but copyfs 
might be worth a try:


https://packages.debian.org/search?keywords=copyfs=names=all=all


David

Re: No sound in Debian Stretch

2018-04-10 Thread deloptes

Daniel Bareiro wrote:

> Hi, deloptes.
> 
> On 10/04/18 19:36, deloptes wrote:
> 
>>> Has anyone experienced something like that and has some clue how to fix
>>> it?
> 
>> try
>> alsamixer -c0
>> or
>> amixer -c0
>> and see if something is muted there
>> usually 0 is the alsacard driver - it might be other index for you though
> 
...
> 
> I was also looking at the settings with the ncurses interface provided
> by "alsamixer -c0". "Master", "PCM" and "Speaker" is at maximum, unless
> I'm missing something. Here some screenshots:
> 
> https://ibin.co/3xx7l69DriYy.png
> https://ibin.co/3xx8ERkqHJwW.png
> https://ibin.co/3xx8ac8djtS4.png
> 
> I also tried setting "Internal" to the maximum, but it made no difference.
> 

Automute is enabled - this means when you plug in headphone, speaker is
turned off
Headphone is also muted - no sound

strange that you mention you have no sound at all - without headphones
plugged, it should work.
check also the pavucontrol settings in both cases (the icons for default
device etc)

If nothing helps remove ~/.pulse directory and reboot or login again or kill
pulse server (it should respawn)

regards

Re: No sound in Debian Stretch

2018-04-10 Thread Daniel Bareiro

Hi, Ben.

On 10/04/18 19:51, Ben Caradoc-Davies wrote:
> On 11/04/18 10:15, Daniel Bareiro wrote:
>>  From one day to the next I ran out of sound in Debian Stretch. It's
>> strange because I don't remember making any changes and everything was
>> running without problem.
>> I installed pavucontrol to see if there is something muted, but that
>> does not seem to be the case. For example when I am playing a Youtube
>> video, in "Firefox: Audiostream" and in "Output devices" (I'm not sure
>> if that's what it says in the English version because I have the
>> interface in Spanish here) I see how the bottom bar fluctuates as if it
>> was reproducing something, but I am not able to hear any sound neither
>> by the speakers nor by the headset.
>> Has anyone experienced something like that and has some clue how to
>> fix it?

> Did the problem start when you plugged in your headset? What happens if
> you unplug your headset? Do you get sound from your speakers? How are
> your speakers connected? Is this a laptop? I have had a laptop with an
> Intel chipset for which headphone autoswitching was broken. I ended up
> disabling (commenting out) the switch-on-port-available module in
> /etc/pulse/default.pa .
> 
> On my current disktop chipset, my headset is detected as line out (not
> headphones). I am using "Analog Stereo Duplex" in Configuration and
> "Line Out" in "Output Devices". Do you have any HDMI devices connected
> or listed as Configuration options?

The computer where I am having this problem is a Thinkpad T530 notebook.
I'm not getting sound at all, whether I have the headset plugged in or not.

Until a few days ago it was working without problems. I don't remember
exactly when I started to experience this. If it was after return the
notebook from sleeping state or at some other time.

This notebook does not have any HDMI port.

Thanks for your interest.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: No sound in Debian Stretch

2018-04-10 Thread Daniel Bareiro

Hi, deloptes.

On 10/04/18 19:36, deloptes wrote:

>> Has anyone experienced something like that and has some clue how to fix
>> it?

> try
> alsamixer -c0
> or
> amixer -c0
> and see if something is muted there
> usually 0 is the alsacard driver - it might be other index for you though

This is the output I get with "amixer -c0":

-
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 87
  Mono: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'Headphone',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 87
  Mono:
  Front Left: Playback 0 [0%] [-65.25dB] [off]
  Front Right: Playback 0 [0%] [-65.25dB] [off]
Simple mixer control 'Headphone',1
  Capabilities: pswitch
  Playback channels: Front Left - Front Right
  Mono:
  Front Left: Playback [on]
  Front Right: Playback [on]
Simple mixer control 'Speaker',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 87
  Mono:
  Front Left: Playback 87 [100%] [0.00dB] [on]
  Front Right: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [off]
  Front Right: Playback 31 [100%] [12.00dB] [off]
Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'IEC958',1
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'IEC958',2
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'Beep',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-34.50dB] [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 63
  Front Left: Capture 63 [100%] [30.00dB] [on]
  Front Right: Capture 63 [100%] [30.00dB] [on]
Simple mixer control 'Auto-Mute Mode',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Enabled'
Simple mixer control 'Digital',0
  Capabilities: cvolume
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 120
  Front Left: Capture 120 [100%] [30.00dB]
  Front Right: Capture 120 [100%] [30.00dB]
Simple mixer control 'Dock Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [off]
  Front Right: Playback 31 [100%] [12.00dB] [off]
Simple mixer control 'Dock Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Internal Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Loopback Mixing',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Disabled'
-

I was also looking at the settings with the ncurses interface provided
by "alsamixer -c0". "Master", "PCM" and "Speaker" is at maximum, unless
I'm missing something. Here some screenshots:

https://ibin.co/3xx7l69DriYy.png
https://ibin.co/3xx8ERkqHJwW.png
https://ibin.co/3xx8ac8djtS4.png

I also tried setting "Internal" to the maximum, but it made no difference.


Thanks for your reply.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Status of Intel-related vulnerabilities and bugs?

2018-04-10 Thread Niclas Arndt

Hello,

I'm trying to get my head around all the recent Intel-related vulnerabilities
and bugs and what they mean for the practical usefulness of my not-so-old and
still under warranty motherboards in the role of a secure Debian internet
server.

I have spent quite some time googling for both information about the technical
problems and also what the motherboard manufacturers have done and plan to do
about it.

It seems that many have rolled out BIOS updates for their 100-300 and x99-299
series motherboards (Intel Management Engine (IME), hyperthreading, and Spectre
variant 2).

For older motherboards there is a lot more uncertainty. ASRock (but not
Gigabyte, ASUS, nor MSI) has released H97 / Z97 BIOS updates to Haswell CPU
Microcode revision 24 and Broadwell revision 1D, but no update for IME.
Gigabyte hasn't responded to my support request regarding their plans for
97-series and older motherboards.

I have applied the Linux "microcode updated early" firmware from
stretch-backports (https://wiki.debian.org/Microcode), but that leaves me with
a few questions:

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

2. What is really the deal with IME on pre 100-series motherboards? According
to the "GIGABYTE Intel ME Critical FW Update Utility" there is "no need" to
update my H97N-WIFI motherboards, but the "Intel-SA-00086 Detection Tool" says
my Windows 7 machine is vulnerable. Some sources claim that certain consumer
motherboards are indeed vulnerable to the IME holes. As far as I understand,
the H97 and Z97 chipsets don't have vPro support (which I suppose means that
AMT is not implemented?), but some motherboards were instead designed with
Intel Small Business Advantage (SBA). For example, the Gigabyte H97N-WIFI /
Z97N-WIFI boards have SBA support, but the ASRock H97E-ITX/ac / Z97E-ITX/ac
don't, but does this mean that the Gigabyte boards are vulnerable but not the
ASRock boards?
https://www.gigabyte.com/Support/Utility/Motherboard#mefw
https://www.intel.com/content/www/us/en/support/articles/25619/software.html

3. Assuming that the H97 / Z97 motherboards with SBA are vulnerable to the IME
hole, what can be done to prevent exploits?

4. Has Microsoft decided only to apply their equivalent of the "microcode
updated early" firmware to the latest version of Windows 10, leaving the still
supported Windows 7 and 8.x with the Spectre 2 security hole?

52 matches

Mail list logo