On Mon 21 Apr 2025 at 20:30:01 (-0400), Arbol One wrote:

In my Debian 12, the keyboard stopped working all of the sudden, i
tried using the 'Screen Keyboard', but it didn't work either. Coming
from the world of Windows 10, I intended to reinstall the Debian.
With the memory stick containing the Debian installation files
plugged, I proceeded to reboot the computer.
The booting process then tells me something I've never seen before,
something along the lines of

'Something went terribly wrong. Security Policy Violation, ... , SBAT
self check failed, ... '

What's going on with Debian 12, I'm not allowed to reinstall Debian?

Do I need to install Windows 11, and then reinstall Debian?

If anyone can suggest a better solution
it would be greatly appreciated.

Thanks in advance.

PD :

After the 'Screen Blackout' kicked in and then moving the mouse, I was
asked to enter the password, and the keyboard worked!

However, the keyboard doesn't work on any other application; no matter
what key I press.

Searching the web with SBAT self check failed turns up several
hits, and they range from Windows updating the list of bad signatures
(which would assume you have Secure Boot set, and a dual-booting
Windows/linux system), to the effect of malware altering the boot
system of the machine to its own ends.

So I'd keep the machine switched off, and do some research to see
what applies in your case.

Your PD bit (is that a postscript?) isn't very clear about when
the 'Screen Blackout' occurred. Was this when the keyboard originally
stopped working, or after you rebooted and got the error message?
And which password was it that you typed?

Cheers,
David.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 21 Apr 2025 20:30:01 -0400
Arbol One <ArbolOne@hotmail.ca> wrote:

In my Debian 12, the keyboard stopped working all of the sudden, i
tried using the 'Screen Keyboard', but it didn't work either. Coming
from the world of Windows 10, I intended to reinstall the Debian.

On-screen keyboards usually require a working mouse or touch screen.
Did the mouse work?

Re-installing is pretty drastic. I would have tried some diagnostics
first: broken keyboard, keyboard battery dead, keyboard unplugged, etc.
I might then have tried rebooting.

After the 'Screen Blackout' kicked in and then moving the mouse, I
was asked to enter the password, and the keyboard worked!

However, the keyboard doesn't work on any other application; no
matter what key I press.

That sounds like a software failure, interrupt or daemon not working.
Again, rebooting might be the thing.


--
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Timothy M Butterworth wrote:
...keyboard sometimes stops working...

I have that problem occasionally. I just unplug the USB connector then plug it back in and the keyboard works again.

yes, but it also may indicate a poor connection or a
bad cable so perhaps checking that is a good idea.

in the past i have had keyboards that were designed
with a plastic case which is not rigid enough to stand up
to my use case (on my lap, unsupported at either end),
after a few years both of them developed the same
intermittent failure where the connection ribbin inside
the keyboard was losing a firm contact. which was too
bad since i liked those keyboards otherwise (i still have
them but have never figured out how to repair them and
they're not worth sending back to be repaired).


songbird

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

songbird <songbird@anthive.com> wrote:

Timothy M Butterworth wrote:
...keyboard sometimes stops working...

I have that problem occasionally. I just unplug the USB connector
then plug it back in and the keyboard works again.

yes, but it also may indicate a poor connection or a
bad cable so perhaps checking that is a good idea.

in the past i have had keyboards that were designed
with a plastic case which is not rigid enough to stand up
to my use case (on my lap, unsupported at either end),
after a few years both of them developed the same
intermittent failure where the connection ribbin inside
the keyboard was losing a firm contact. which was too
bad since i liked those keyboards otherwise (i still have
them but have never figured out how to repair them and
they're not worth sending back to be repaired).

Glue some ply or plastic underneath to stiffen them?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 4/21/25 17:13, Arbol One wrote:

In my Debian 12, the keyboard stopped working all of the sudden, i
tried using the 'Screen Keyboard', but it didn't work either. Coming
from the world of Windows 10, I intended to reinstall the Debian.
With the memory stick containing the Debian installation files
plugged, I proceeded to reboot the computer. The booting process
then tells me something I've never seen before, something along the
lines of

'Something went terribly wrong. Security Policy Violation, ... ,
SBAT self check failed, ...'

What's going on with Debian 12, I'm not allowed to reinstall Debian?

Do I need to install Windows 11, and then reinstall Debian?

If anyone can suggest a better solution it would be greatly
appreciated.

Thanks in advance.

PD :

After the 'Screen Blackout' kicked in and then moving the mouse, I
was asked to enter the password, and the keyboard worked!

However, the keyboard doesn't work on any other application; no
matter what key I press.

Get Outlook for Android<https://aka.ms/AAb9ysg>

On 4/21/25 17:30, Arbol One wrote:

In my Debian 12, the keyboard stopped working all of the sudden, i
tried using the 'Screen Keyboard', but it didn't work either. Coming
from the world of Windows 10, I intended to reinstall the Debian.
With the memory stick containing the Debian installation files
plugged, I proceeded to reboot the computer. The booting process
then tells me something I've never seen before, something along the
lines of

'Something went terribly wrong. Security Policy Violation, ... ,
SBAT self check failed, ... '

What's going on with Debian 12, I'm not allowed to reinstall Debian?

Do I need to install Windows 11, and then reinstall Debian?

If anyone can suggest a better solution it would be greatly
appreciated.

Thanks in advance.

PD :

After the 'Screen Blackout' kicked in and then moving the mouse, I
was asked to enter the password, and the keyboard worked!

However, the keyboard doesn't work on any other application; no
matter what key I press.

Those two posts are almost identical, but not. This is confusing and
wastes time and effort:

2025-04-22 11:26:20 dpchrist@laalaa ~
$ diff foo bar
1c1,2
< On 4/21/25 17:13, Arbol One wrote:> In my Debian 12, the keyboard
stopped working all of the sudden, i
---

On 4/21/25 17:30, Arbol One wrote:>

In my Debian 12, the keyboard stopped working all of the sudden, i

10c11
< > SBAT self check failed, ...'
---

SBAT self check failed, ... '

29,30d29
< >
< > Get Outlook for Android<https://aka.ms/AAb9ysg>


On 4/22/25 11:03, Arbol One wrote:

As stated in the OP, with the USB containing the installation files
for Debian 12 already inserted in the computer, I booted up the >
computer and instead of going to the installation files, as it
should, I get a message saying

Verifying shim SBAT data failure: Security Policy Violation.
Som6has gone seriously wrong: SBAT self-check failed: Security
Policy Violation.

There's something in me saying that it is a virus, but that might
be 'cos I'm still traumatized by all those years of Win-OS usage.

Again, any help would be greatly appreciated.

Thanks in advance.

By the way, I've tried other keyboards but to no avail.

Get Outlook for Android<https://ak

On Tue 22 Apr 2025 at 18:03:09 (+0000), Arbol One wrote:

As stated in the OP, with the USB containing the installation files for Debian 12 already inserted in the computer, I booted up the computer and instead of going to the installation files, as it should, I get a message saying

Verifying shim SBAT data failure: Security Policy Violation.
Som6has gone seriously wrong: SBAT self-check failed: Security Policy Violation.

There's something in me saying that it is a virus, but that might be 'cos I'm still traumatized by all those years of Win-OS usage.

Again, any help would be greatly appreciated.

Doesn't the same post invite the same replies?

Perhaps I need to be more explicit:

Is this machine dual-boot, ie does it have Windows and linux installed?

Was Secure Boot enabled already?

Answering those questions may change expectations of getting an error
message like that.

Cheers,
David.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

debian-user@howorth.org.uk wrote:

songbird <songbird@anthive.com> wrote:

Timothy M Butterworth wrote:
...keyboard sometimes stops working...

I have that problem occasionally. I just unplug the USB connector
then plug it back in and the keyboard works again.

yes, but it also may indicate a poor connection or a
bad cable so perhaps checking that is a good idea.

in the past i have had keyboards that were designed
with a plastic case which is not rigid enough to stand up
to my use case (on my lap, unsupported at either end),
after a few years both of them developed the same
intermittent failure where the connection ribbin inside
the keyboard was losing a firm contact. which was too
bad since i liked those keyboards otherwise (i still have
them but have never figured out how to repair them and
they're not worth sending back to be repaired).

Glue some ply or plastic underneath to stiffen them?

unfortunately too late for that, once i took them apart
i could not get them back together again to where they
would work reliably. :( it is a very strange design of
a connection where it is basically a type of ribbon held
only by pressure and not very well. i don't know why
they could not have used a more normal slot that you stuck
the ribbon cable in... for $0.25 or so...


songbird

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 22/04/2025 11:09, Timothy M Butterworth wrote:

On Mon, 21 Apr 2025 20:30:01 -0400
Arbol One <ArbolOne@hotmail.ca <mailto:ArbolOne@hotmail.ca>> wrote:

> In my Debian 12, the keyboard stopped working all of the sudden

I have that problem occasionally. I just unplug the USB connector then plug it back in and the keyboard works again.

I also have that problem occasionally, and the same fix works. But the USB socket is in a rather inconvenient place. The mouse still works on these occasions so a custom menu item to click that ran a command to emulate the unplugging and re-plugging of
the keyboard would be nice to have.

Does anybody know a command that will do that?

--
John

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 25 Apr 2025, at 09:06, John Crawley wrote:

I also have that problem occasionally, and the same fix works. But the
USB socket is in a rather inconvenient place.

So, run a USB extension cable from there to an accessible place?

Extension cables are also a good way to protect oft-used sockets
from becoming loose/unreliable.

--
Jeremy Nicoll - my opinions are my own.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 25/04/2025 18:50, Thomas Schmitt wrote:

John Crawley wrote:

[...] a command to emulate the
unplugging and re-plugging of the keyboard would be nice to have.

The internet mentions usbreset(1), available from package "usbutils".

But the source code in
https://sources.debian.org/src/usbutils/1%3A018-2/usbreset.c
shows that the decisive action is a call to ioctl USBDEVFS_RESET, about
which the Linux kernel documentation
https://www.kernel.org/doc/Documentation/driver-api/usb.rst
says
----------------------------------------------------------------------- USBDEVFS_RESET
Does a USB level device reset. The ioctl parameter is ignored. After
the reset, this rebinds all device interfaces. File modification
time is not updated by this request.

**Warning**

*Avoid using this call* until some usbcore bugs get fixed, since
it does not fully synchronize device, interface, and driver (not
just usbfs) state. -----------------------------------------------------------------------

The man page is
https://manpages.debian.org/unstable/usbutils/usbreset.1.en.html Addressing the USB port looks tricky, as it does not work via /dev file paths.
("Reset by product name" could be a good choice.)

Thank you.
The product name wasn't hard to extract, and
sudo usbreset "ELECOM TK-FCP097"
claimed to be resetting the keyboard, which at least continued to work. However, after that the terminal went into an endless output of new prompts and had to be closed.
(The keyboard still works.)
I'll set that command up in a mouse-accessible menu and wait till the next keyboard dropout to see what it does.
That might not be for a couple of months though, so thanks again.

--
John

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)