Filipe,
as far as I can see you're having issue with usbhid module, not with i8042. But
since you get a very similar issue could be very related to my issue. Good luck!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I've created a script for lightDM to check the state of the keyboard with
xinput: it starts when X is loaded (tested with display-setup-script and
greeter-setup-script options) and check the state of the internal keyboard then
create a txt in my home.
The keyboard is correctly identified from t
** Tags removed: kernel-bug-exists-mainline-4.11rc1
** Tags added: kernel-bug-exists-mainline-4.12.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599306
Title:
[HP Pavilion dv2910us Entertainment
Finally I got the time to test (with a second SSD just to be sure) this
notebook with some quirks.
So far, the quirks I've found and tested are:
i8042.kbdreset
i8042.reset
i8042.nomux
i8042.dumbkbd
i8042.direct
i8042.noaux (irrelevant but tested anyway)
i8042.nokbd (completely kill the keyboard)
** Tags added: kernel-bug-exists-mainline-4.11rc7 kernel-bug-exists-
upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637347
Title:
Xubuntu 16.10: drm errors causing slow boot
To manage noti
It's not restricted to Xubuntu, but this bug affects all *buntu I've
tested in the last week. Now I'm testing Ubuntu Budgie on a notebook HP
2910us and kernel 4.10.0-19-generic.
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
i8042.kbdreset=1, i8042.reset and i8042.nomux=1 with no luck.
I don't remember if I've tested atkbd, but I can give a new spin of boot
options tomorrow just to be sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Yes, the touchpad works just fine (see videos on OP).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599306
Title:
[HP Pavilion dv2910us Entertainment Notebook PC] i8042 need to start
early after
Tested (even with broken wifi drivers)
4.11.0-041100rc1-generic #201703051731 SMP Sun Mar 5 22:34:02 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Issue still present.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-mainline-4.11rc1
--
You recei
Christopher, sorry for the delay but I completely missed your last
messages.
My bios is the latest version:
F.2D 08/26/2008
And the issue is still present with any *buntu I've tried.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Tags removed: bios-outdated-f.2d
** Tags a
I've made another test on a Dell 1545 with an Intel GM45 chipset. This notebook
is using the i8042 to identify devices but no delay at all. Again seems the
issue is just with HP NOtebook.
What can I do to help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Sure Christopher.
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd leds event0
B: PROP=0
B: EV=120013
B: KEY=2 20 0 0 1500f02140003 3803078
*** This bug is a duplicate of bug 1599306 ***
https://bugs.launchpad.net/bugs/1599306
** This bug has been marked a duplicate of bug 1599306
16.04: i8042 need to start early after grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Joseph,
thank you for your reply.
All the tests I've made were done starting from fresh install.
The issue persist on 4.7.0-040700rc6-generic (X64): at least 10 seconds before
have the keyboard working again.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: k
Public bug reported:
The kernel module i8042 need to start early after grub selection. I've upgrade
my notebook (HP dv2700 series, model dv2910us) with an SSD and now I need to
wait 15 seconds after LightDM show up before I can use the internal keyboard.On
bios and on GRUB the keyboard works fi
I've tried to boot with a keylogger loaded on rc.local and as an option on
lightdm to see if the keys are captured but I got no input from the moment I
leave GRUB and the kernel start to load until the infamous 15 seconds after
LighDM is loaded.
Since the issue seems to be strongly related to
** Also affects: xinput (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Ubuntu 16.04: unable to use internal keyboard for 15 sec on boot
+ Ubuntu 16.04: unresponsive keyboard (15 sec) on boot
** Summary changed:
- Ubuntu 16.04: unresponsive keyboard (15 sec) on boot
Since I fear ubuntu is unable to detect correctly my keyboard at startup after
passing grub (why?), I'm trying to solve with xinput after X init.
Here's my xinput list:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid
** Also affects: kbd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596200
Title:
Ubuntu 16.04: unable to us
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596200
Title:
Ubuntu 16.04: unable to use internal keyboard for 15 sec on b
Tested the same SSD with Ubuntu 14.04, same issue.
I gave a spin with Windows 7 just to be sure is not an hardware related issue:
the keyboard works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
I've upgraded my notebook with an SSD. All works fine and I can reach
the login in less than 10 seconds. Problem is I can't use the internal
keyboard (perfectly working on grub) for at least 10-15 seconds, then it
starts to working just fine. The touchpad and capacitive button
Ok, after a few test I'm not sure if is completely related to the boot speed,
but I'm quite sure is part of the problem, because booting with a fresh install
on an old sata2 hdd I don't have any problem with the keyboard.
Let me explain: I'm using an HP Pavilliion dv2700 notebook, and all works f
I had a similar behavior when I changed my HDD and installed a fast SSD for
Xubuntu 16.04. I can use buttons, and dropdowns with no issues. It happens with
unity and webkit greeters.
Seems you need to wait at least 10-15 seconds before all the services are
effectively up and running. Nothing sus
Christopher,
as soon as possible I'll have a look with a newest release based on xfce or
lxde. This notebook is not my primary machine but just a spare one I used
to debug when I was part of the Lububtu team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Christopher,
I reinstalled my Windows Vista from my restoration DVD just to check if
brightness works and I had many difficult installing it.
I was able to install an old XP and I discovered multiple errors about ACPI and
the brightness control has issues on this OS too: I can see the brightness
I found on dmesg those lines:
[ 16.487465] ACPI Warning: 0x1028-0x102f SystemIO
conflicts with Region \PMIO 1 (20131115/utaddress-251)
[ 16.487476] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[ 16.487481] ACPI
Today I've updated my 14.04 install and the osd no longer works.
Anyway the issue is present on the latest rc4 too.
Acpi_listen is reporting the keypressed code and the backlight files are
correctly updated but nothing changes.
** Tags removed: kernel-bug-exists-upstream-3.14-rc3
** Tags added: k
Done.
http://marc.info/?l=linux-acpi&m=139290477319769&w=2
** Summary changed:
- 8086:2a02 [Dell Vostro 1310] no brightness control on (x)ubuntu 13.10
+ 8086:2a02 [Dell Vostro 1310] no brightness control on (x)ubuntu 13.10 / 14.04
--
You received this bug notification because you are a member
** Description changed:
- When I press the appropriate keys on keyboard (which ones specifically?)
- the slider appears on the upper right corner of the screen but the
- brightness doesn't change.
+ When I press the appropriate keys on keyboard (Fn+up/Fn+down) the slider
+ appears on the upper rig
Ok. As soon as I can I'll push the bug to acpi_intel list and his
mantainer.
** Tags removed: kernel-bug-exists-upstream-3.14-rc2
** Tags added: kernel-bug-exists-upstream-3.14-rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Christoper,
I've tested the latest available Ubuntu 14.04 64bit iso from
http://cdimage.ubuntu.com/daily-live/current/ .
Same issues with both stock 3.13.0-8-generic and 3.14.0-031400rc2-generic (rc3
has not 64bit packages to test) from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D .
Public bug reported:
A customer of mine gave me his old notebook because he bought a new one.
I trow in a new HDD and now the laptop is running an up to date Xubuntu
13.10 64bit. Everithing is working fine exept for the brightness
control: when I press the appropriate keys on keyboard the slider
a
Christopher,
thanks for your reply. I'll open the new bug ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261853
Title:
8086:0166 [Dell Inspiron 15R 5521] Impossible to adjust the screen
bac
A customer of mine gave me his old notebook because he bought a new one.
The laptop is running an p to date Xubuntu 13.10 64bit. Now I'm
suffering similar issue with brightness control: when I press the
appropriate keys on keyboard the slide appears on the upper right corner
of the screen but even
Yes, the patch from Lubuntu-dev/staging PPA (post #55) is working fine
in OEM install ( and on OBI too). Thanks Iberê.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circu
my desktop (running 13.04) is set to PT-BR, if I change language to US the
keyboard start acting strange as on others PC.
Setting to PT-BR my netbook and notebook solved the problem but I need an
English setup here. And have a keyboard that change behavior with the language
is not the best.
--
Public bug reported:
For my work and for real life I write a lot in English, Italian and Portuguese
so on all my system desktop (Lubuntu 13.04), netbook and notebook (Lubuntu
13.10), I set my keyboard to US alternative international.
What I expect pressing the key " ' " followed by " c " from th
Another solution is to open Preferences --> Default applications for
LXSession, then go to the autostart tab and here change the option
"Disable autostarted applications" from the default "config-only" to
"no". You may need to change the settings for laptop-mode from "no"to
"yes". (settings tab).
Public bug reported:
package syslinux-themes-debian 12-1.1 failed to install/upgrade: sub-
processo script post-removal instalado retornou estado de saída de erro
127
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: syslinux-themes-debian 12-1.1
Uname: Linux 3.9.0-030900-generic x86_64
N
Understood Chris, sometimes I need to read with more attention, English is not
my primary language.
Seems my display simply can't handle 24bit color depth, if I force a 16bit
color depth on xorg I can see great degrade of the render, clearly evident on
desktop wallpaper (see pic).
About the 24b
Chris,
I don't want to bother you but I have to insist: with the UXA accelmethod the
problem does not occurs.
I created the file /etc/X11/xorg.conf.d/20-intel.conf instead of using the old
xorg.conf and my notebook now works fine on both 13.04 (kernel 3.8.x) and 13.10
(3.10.x).
Don't you thin
My display is set to 1024x768x16bit and I can assure it's working fine now with
UXA.
I tested this render method only by accident to see if it will improve Flash on
such an old machine.
Just to let you know I'm using flash 10.x due to an incompatibility with my cpu
and 11.x.
As soon as I can I
Chris,
on Lubuntu mailing list we have a thread speaking about a workaround for
another issue with xserver-xorg-video-intel and flash that seems to solve the
problem I have.
As reported on commentary #1 on bug 1178982, using UXA as accelmethod option
on xorg.xonf solve the issue of that bug
Thanks Andrea, I'm using the version found on lubuntu-dev ppa
((1.1.0+bzr905+201306281636~raring1) on three different computers and I
can confirm it's working fine now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
45 matches
Mail list logo