Medion notebook dual boot: Azerty built-in keyboard not working

[toma1970]

A good idea...I posted my keyboard issue n the linux mint blog...If no answer in the coming days, then I'll have a look at an other distribution... Which one resembles Mint the most? OpenSuse?

It's a brand new computer, so no upgrade...
I don't remember if the keyboard was or wasn't working on the Live USB...I'll have to check...On Windows it works perfectly.

Have a great weekend!!

[hglee]

Fedora is available with the Cinnamon desktop, I believe, as one of its "spins".

Porteus, another Irish distro (like Mint), based on Slackware.

Artix Linux, which is based on Arch Linux of Canadian origin.

Gentoo in the US, which is unique because instead of downloading apps and updates as prebuilt binary files, it downloads source code which is then compiled by your PC. This might be a nuisance on some slower systems.

Manjaro of Germany and France. Devuan, a global effort.

The world is your oyster.

At the top left corner of Distrowatch there's a way to search by base distro or desktops.

[toma1970]

I've been visiting sites and fora and trying things out that helped other users, but till now nothing helping me...quite frustrating
As you asked, I booted once from liveUsb and built-in keyboard not working neither....

[toma1970]

@hglee, does this looks good as dual boot? I followed the LM installation guide.

Code: Select all

tomas@tomas-comp:~$ sudo fdisk -l
          
Disk /dev/sda: 476,96 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: S11-512G-PHISON-
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BBAC9D06-8668-4187-82ED-5BC8FE2AAB8E

Device         Start        End   Sectors   Size Type
/dev/sda1       2048     206847    204800   100M EFI System
/dev/sda2     206848     239615     32768    16M Microsoft reserved
/dev/sda3     239616  466802687 466563072 222,5G Microsoft basic data
/dev/sda4  933156864  935202815   2045952   999M Windows recovery environment
/dev/sda5  935202816  998117375  62914560    30G Microsoft basic data
/dev/sda6  998117376 1000214527   2097152     1G unknown
/dev/sda7  466802688  525398015  58595328    28G Linux filesystem
/dev/sda8  525398016  537118719  11720704   5,6G Linux swap
/dev/sda9  537118720  933156863 396038144 188,9G Linux filesystem

Partition table entries are not in disk order.

[hglee]

I don't see a problem.

You're really generous to Windows. I don't give it more than 70GB drive space, since I'm 99.9% of my time in Linux.

[toma1970]

@hglee
Still searching for a solution, I found following command with its output:

tomas@tomas-comp:~$ dmesg | grep -i i8042
[ 1.255876] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 1.255876] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.258511] serio: i8042 KBD port at 0x60,0x64 irq 1

Can I do something about that AUX port which is disabled

[hglee]

@hglee
Still searching for a solution, I found following command with its output:

tomas@tomas-comp:~$ dmesg | grep -i i8042
[ 1.255876] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 1.255876] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.258511] serio: i8042 KBD port at 0x60,0x64 irq 1

Can I do something about that AUX port which is disabled

The 8042 micocontoller is from the original IBM PS/2 design, circa 1987. Its functionality is now emulated in PC chipsets, for backward compatibility with legacy BIOS.

That dmesg info confirms that the 8042 still uses data port address 0x60 and command/status port 0x64 -- and when it needs attention from the CPU it asserts interrupt request #1 (IRQ1) on the system bus -- just as it originally did decades ago.

In addition to its primary function as a keyboard controller, the 8042 also provided an auxiliary (AUX) port for a second serial device -- such as a mouse. In a modern laptop the touchpad is typically connected internally as a USB device, so the old 8042 AUX port could be unused, which is what the dmesg log appears to indicate. You mentioned earlier that your touchpad is working okay.

I suspect that your keyboard is connected via the WMI -- Windows Management Instrumentation -- interface, which is an industry standard way for manufacturers to interface virtually any device. The WMI is a complex set of proprietary extensions to the Windows Driver Model (WDM).

[hglee]

Please post the output of this command...

Code: Select all

cat /proc/bus/input/devices

The following may print hundreds of kilobytes of data about your current bootup, so let's offload the output into a temporary webpage. After a momentary pause, this command will display a unique URL that looks something like https://termbin.com/abc9. Post that URL in a reply here.

Code: Select all

journalctl -b | nc termbin.com 9999

That URL will be good for about one month, then it's automatically deleted.

[toma1970]

What I forgot to mention is that I was able to disable 'secure boot' but I'm unable set it to 'legacy' cause I can't find it in my BIOS.
Indeed, my touchpad is working fine.
I found a site where they talk about 'scripts for disabling/enabling laptop keyboard'.

www.systutorials.com/how-to-disable-and ... ent-259892

I asked for advise cause they mention "AT Translated Set 2 keyboard" as you did in one of your first replies...wait and see...

[toma1970]

Code: Select all

tomas@tomas-comp:~$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input2
U: Uniq=
H: Handlers=event2 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
U: Uniq=
H: Handlers=kbd event3 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0003 Vendor=13d3 Product=56f5 Version=1901
N: Name="USB2.0 HD UVC WebCam: USB2.0 HD"
P: Phys=usb-0000:00:14.0-7/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/input/input8
U: Uniq=
H: Handlers=kbd event4 
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0018 Vendor=2808 Product=0101 Version=0100
N: Name="FTCS1000:00 2808:0101 Mouse"
P: Phys=i2c-FTCS1000:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-FTCS1000:00/0018:2808:0101.0001/input/input9
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=0
B: EV=17
B: KEY=30000 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0018 Vendor=2808 Product=0101 Version=0100
N: Name="FTCS1000:00 2808:0101 Touchpad"
P: Phys=i2c-FTCS1000:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-FTCS1000:00/0018:2808:0101.0001/input/input10
U: Uniq=
H: Handlers=mouse1 event6 
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="sof-hda-dsp Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input12
U: Uniq=
H: Handlers=event7 
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="sof-hda-dsp Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input13
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="sof-hda-dsp HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input14
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="sof-hda-dsp HDMI/DP,pcm=4"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input15
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="sof-hda-dsp HDMI/DP,pcm=5"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input16
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=140

[toma1970]

Code: Select all

tomas@tomas-comp:~$ journalctl -b | nc termbin.com 9999
https://termbin.com/j5bld

Since more than 10y I'm using LM, and very happy with it. If problems occurred, I always found solutions on 2 or 3 sites.
But the 2 last commands you asked me to post, could you provide me a little bit more explanation so I can understand and learn
Again, thx a lot for all your efforts!

[hglee]

Those commands provide details on how devices and subsystems are interfaced with your PC. The last shows how your PC attempts to identify and initialise everything it finds plugged in.

Your BIOS might refer to Legacy mode as CSM -- Compatibility Support Module.

[toma1970]

When I look at my BIOS, I see:

in MAIN: - BIOS version: 207
- EC VERSION EC REV 012
- GOP VERSION 17.0.1045
etc etc

in SECURITY: - Secure Boot: Not active
- System Mode : Deployed
- Secure Boot Menu (where I find Key Management)
- TPM Support

in BOOT: - Option # 1 : ubuntu
- Option # 2 : Windows
- PXE Boot

But nowhere CSM

[hglee]

In the Boot section of your BIOS, there might be Boot Mode, which could be set to either Legacy or UEFI.

Your system has booted as UEFI. If you change it in your BIOS now, dual-boot Windows shall be... upset.

[toma1970]

I remember following "easylinuxtipsproject" steps when dual-booting, so I probably looked for "legacy" but didn't find it...
So better to leave it that way?

[hglee]

I remember following "easylinuxtipsproject" steps when dual-booting, so I probably looked for "legacy" but didn't find it...
So better to leave it that way?

"If you're dual-booting with another OS, the two OSes' boot modes should match."

The only reason I've chosen UEFI for Linux is because I dual-boot Windows. On my other Dell 2-in-1 there's only Mint, no Windows, so it's installed as Legacy.

[visserkevis]

I have exact the same problem. Probably the same laptop from the same supermarket.
I found suggestions on the web, that it could be mint presumes the laptop,(although it has no touchscreen), is in tablet-mode. Thus: disabling the keyboard.

But the suggestions they did didn't work for me.

https://forum.chuwi.com/t/keyboard-not- ... inux/14453
and
https://askubuntu.com/questions/1269284 ... 8-04-20-04

I reported it as a bug.
https://bugs.launchpad.net/ubuntu/+sour ... ug/1909814

Im hooked on Linux Mint. Thinking about bringing the laptop back to the store. But where can I find such a laptop for the same price...

[toma1970]

@hglee
I checked and linux is in efi and windows in uefi, so that looks good...

[toma1970]

@visserkevis
The past days I ran into your bug report on the ubuntu site (bug.launchpad) but as well without success
Aldi?
Me too, like too much Mint to switch to an other OS I'm not familiar with...so first doing everything to try to solve this issue before switching

[toma1970]

@hglee

Did those 2 commands "cat /proc/bus/input/devices" and "journalctl -b | nc termbin.com 9999" give you some new ideas about the keyboard issue?