[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-03-10 Thread Md Ayquassar
Yes, Ctrl + zooms in and out. If we believe https://www.microsoft.com/accessories/en-ww/products/keyboards/natural- ergonomic-keyboard-4000/b2m-00012 (though my model is not B2M-00012 but 1048) , Microsoft intended the zoom slider on the keyboard to map to zoom in and out, too. -- You received

[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-02-28 Thread Md Ayquassar
@ddstreet Thank for the explanation. (Myself, I don't know why the keyboard behaves this way; I can imagine any option, e.g., a glitch of the keyboard firmware or hardware, an unintended bug introduced by the developers of the manufacturer, a cost-reducing design of the manufacturer, or an

[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-01-24 Thread Md Ayquassar
@ddstreet Thanks for the feedback. The keyboard has “Microsoft® Natural® Ergonomic Keyboard 4000 v1.0”, “Model 1048” printed on its bottom. The keyboard looks pretty standard to me from outside. Do you really mean it's broken? Is any combination of the sliding key with any modifier key(s)

[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-12-24 Thread Md Ayquassar
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d,

[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-12-24 Thread Md Ayquassar
In the meantime, I updated Ubuntu to groovy 20.10. My dmesg is [0.00] microcode: microcode updated early to revision 0x28, date = 2019-11-12 [0.00] Linux version 5.8.0-33-generic (buildd@lgw01-amd64-036) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu)

[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-12-13 Thread Md Ayquassar
This command would disclose potentially sensitive information of a production machine to the public; I won't do it unless given an opportunity to anonymize the results upfront. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you

[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
By the way, I know the BIOS is outdated (A21 instead of A24), but I failed to update it via FreeDOS process. (The manual https://wiki.ubuntuusers.de/BIOS_aktualisieren is partially out of date in this point or I do something wrong, but it's a different issue anyway, having little to do with this

[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
Result of `sudo acpidump > acpi.log` attached. As for USB issues: 1. I sometimes experience bad contact to my iPhone when I charge it using a USB port. This seems to be a physically bad contact to me, however, but I cannot tell for sure. 2. Another issue is that after a USB thumb drive has

[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
I won't run the suggested command (apport-collect 1890467), as is doesn't anonymize or pseudonymize my data or the data of the laptop sufficiently. If given an opportunity to do so manually and paste the result using the Web interface, I will gladly proceed. ** Changed in: linux (Ubuntu)

[Kernel-packages] [Bug 1890467] [NEW] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
Public bug reported: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-03 Thread Md Ayquassar
I recall that on one of my machines I had exactly the same situation as reported in #20 and #21 up to the timings (5.3.0-26-generic in Ubuntu 19.10 with EFI Secure Boot and dual boot with Windows 10, fastboot/hibernation disabled, LZ4 image by default, booting failed often, booting succeeded upon

[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard

2020-07-27 Thread Md Ayquassar
Same for me here on Ubuntu focal. # uname -a Linux undisclosedHostName 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Jul 27 14:42:41 undisclosedHostName kernel: device-mapper: uevent: version 1.0.3 Jul 27 14:42:41 undisclosedHostName kernel:

[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-07-03 Thread Md Ayquassar
See #6. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M

[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-07-03 Thread Md Ayquassar
Provide me with a method to anonymize my data... ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title:

[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-06-06 Thread Md Ayquassar
@janitor I won't do "apport-collect ", since I do wish to anonymize my private data and the laptop data before it goes here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title:

[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active

2020-05-20 Thread Md Ayquassar
Alright; thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see

[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active

2020-05-20 Thread Md Ayquassar
I don't even have PS/2 mouse/keyboard ports on the machine in question. They are only present on the docking station. If the computer is not plugged into the docking station, the warning still appears. If the computer is plugged into the docking station, USB keyboard and USB mouse are used. --

[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active

2020-05-20 Thread Md Ayquassar
If WHAT doesn't affect normal usage? As all computers, the computer in question suffers various issues of varying degree of severity from time to time, starting with (luckily, extremely seldom) shutting itsself off without warning and ending with dozens of warning printfs scattered over dozens of

[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-04-06 Thread Md Ayquassar
** Description changed: - While looking at a dmesg on an up-to-date eoan, I found certain lines - containing *BAD* and "can not find optimal value", "please specify...". - For me, they are just intimidating printfs. Should I get worried? + While looking at the attached dmesg on an up-to-date

[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-04-05 Thread Md Ayquassar
@Ubuntu Kernel Bot: I won't do "apport-collect ", since I have to manually anonymize my private data and the laptop data before it goes here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)

2020-04-05 Thread Md Ayquassar
Btw., the messages for me is slightly different as far as the numbers are concerned, e.g.: [0.556821] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190703/utaddress-204) -- You

[Kernel-packages] [Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)

2020-04-05 Thread Md Ayquassar
Since the above is a warning, I feel, ergo, warned. But I don't know about what. I usually expect to get warned the following way: "If you do this and that, you run into such and such kind of trouble". Now, what is it that I get warned about in this case? I have various kinds of problems

[Kernel-packages] [Bug 1870994] [NEW] "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-04-05 Thread Md Ayquassar
Public bug reported: While looking at a dmesg on an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? ** Affects: linux (Ubuntu) Importance: Undecided

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-05 Thread Md Ayquassar
After "update-grub; update-initramfs -c -k all; update-grub" and a reboot, the message disappeared on the boot after the reboot. We'll see what happens next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-05 Thread Md Ayquassar
Same message for me. The grub menu waits for at least 6 seconds, I think, instead of 0. I won't try anything crazy out before new package version(s) appears, as it is a production system, and I can't repair it in case booting fails. Attachment: the initial part of the dmesg log. ** Attachment