linux-headers-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-headers-4.17.0-1_4.17.0-1.2~lp1728244_all.deb
linux-image-unsigned-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-modules-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-modules-4.17.0-1-generic_4.17.0-1.2~lp1728244_
Does not seem to be exactly the same. But do you suggest I try the same
fix anyway?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Touchpad detected as SYNA3602, does not work at all.
Found something that might be interesting:
martin@alanah:~$ dmesg | grep SYNA
[8.244204] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found,
using dummy regulator
[8.253359] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report
(32/1)
[8.256078] i2c_hid i2c-SYNA360
Hey! Thanks for following this up.
reffman@alanah:~$ uname -r
4.18.0-041800rc5-generic
reffman@alanah:~$
Does not seem to make any difference. Touchpad and (integrated) buttons
are completely dead.
I have investigated the touchpad a bit more (by disassembling the
netbook), and it's marke
Maybe the problem is the same (Ubuntu kernel not detecting the touchpad
correctly), but the touchpads are different models, and so ubuntu
responds differently to them.
There are people who have had trouble with the Ubuntu kernel driver not
resetting the touchpad on boot because of the touchpad beh
Ah. Well, that's not going to happen then. Maybe Jeffrey has a dual boot
installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Touchpad detected as SYNA3602, does not work at al
How do you check that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Touchpad detected as SYNA3602, does not work at all.
To manage notifications about this bug go to:
https://bugs.l
No. It is, and has always been completely dead. Except on Windows 10,
where it worked fine. I did not think to check on what make it was
reported as under Win 10 device manager, unfortunately, before I
installed Ubuntu 8.04 beta 2.
There has been no previous installation of Ubuntu on this laptop,
Installing kernel 4.17.1 did not help:
martin@alanah:~$ uname -r
4.17.1-041701-generic
cat /proc/bus/input/devices
I: Bus=0018 Vendor=0911 Product=5288 Version=0100
N: Name="SYNA3602:00 0911:5288 Touchpad"
P: Phys=i2c-SYNA3602:00
S:
Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i
@Joseph Salisbury, as specified in the OP this is a fresh install.
Previous versions of Ubuntu (older than 18.04) will not boot on this
latest generation of notebooks/netbooks at all due to Secure Boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5152005/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Ti
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5152003/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Ha
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5152004/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Ha
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5152002/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Titl
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151998/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151999/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5152000/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/177
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5152001/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151994/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151997/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151993/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151992/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Hantic
apport information
** Tags added: apport-collected
** Description changed:
On my cheaper-end laptop/netbook the touchpad, which I believe is the
Hantick HT 5288, is wrongly detected by Linux to be the SYNA 3602.
Accordingly it does not work at all, neither touchpad nor buttons.
Freshly i
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151995/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Hant
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1776155/+attachment/5151996/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776155
Title:
Hant
Public bug reported:
On my cheaper-end laptop/netbook the touchpad, which I believe is the
Hantick HT 5288, is wrongly detected by Linux to be the SYNA 3602.
Accordingly it does not work at all, neither touchpad nor buttons.
Freshly installed Ubuntu 18.04 system. I belive the issue is, as
reported
Dipanjan's workaround worked for me.
Ubuntu Mate 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760128
Title:
package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
install/upgrade: subpr
Issue still present in latest Ubuntu (on a MacBook 2,1).
David Duffeys solution in #81 helps partly, its still not quite
sensitive enough. Changing the threshold number does not change the
sensitivity, except if changed to 1 in which case sensitivity is
extremely low.
The other posted solutions h
This probably isn't helpful, but as nothing seems to be done about this
issue, and every new kernel keeps turning up with the same bug, I locked
the kernel version in Synaptic so that no kernel versions after
2.6.24.19 were installed. Worked fine for me until recently, when I
upgraded to Ubuntu 9.0
Previous kernel versions are probably removed if one selects "remove
unused packages" in apt. There is also an option in the grub
configuration files (and in the Startup-Manager applet) that will limit
the number of old kernel versions to be displayed at boot.
To access configuration files from a
I would suggest you do as I did. Do not install the buggy kernel update.
Go to the menu, select system -> administration ->synaptic and find your
installed kernel version. Select it and go to the menu in Synaptic,
select package -> lock version. Do the same with the kernel headers.
This way it will
Sorry, I can't. The problem has not materialized again after the
incident. I have restored my splash in menu.lst, and whatever packages
were not installed at the the abort the system seems to do fine without.
New upgrades since then have completed successfully.
--
package linux-image-2.6.27-9-gen
If the problem persists in newer kernels, it may affect jaunty too? Is
there anything like this issue on Intrepid?
--
Kernel panic after update to 2.6.24-23 on Acer Aspire One netbook
https://bugs.launchpad.net/bugs/322867
You received this bug notification because you are a member of Ubuntu
Bugs
Upgraded the Hardy installation to kernel 2.6.24-23 on my Aspire One
today, can confirm this bug (obviously not fixed yet). Kernel panic
happens directly after GRUB. Clearly readable screenshot is attached, it
is much the same, but slightly different from the ones above.
All previous Hardy kernels
Confirmed.
While installing the updates that came today (28. jan. 2009) for Ubuntu
8.10 - amongst them new kernel modules - I got a requester about what to
do with menu.lst (keep my version or install new). My menu.lst is
modified to keep all kernel version, and I had also added the "splash"
argum
The same goes for all NTFS drives on all my machines. Each and every
NTFS drive is displayed twice on the desktop.
They are displayed once labeled as their mount point like so: "sda1"
And once with an additional label, like so: "145GB NTFS volume (sda1)"
(this could also be their NTFS label, if t
36 matches
Mail list logo
