[Bug 1815172]

2019-02-09 Thread craftyguy
FWIW, I am not able to reproduce this issue on Arch Linux with Mesa 18.3.3 and kernel 4.18.16. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2

[Bug 1775039] [NEW] networkd-dispatcher source location change

2018-06-04 Thread craftyguy
Public bug reported: Hi, developer of networkd-dispatcher here. Since this is shipping in Ubunutu 18.04, I just wanted to give a heads up that the source and project page locations are changing from github to gitlab.com. You can find the new home here: https://gitlab.com/craftyguy/networkd

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-12-03 Thread craftyguy
Unfortunately I killed my system when trying to apply a BIOS update to check another bug I reported, so I'm not able to confirm your patch (though I don't see any reason why that patch wouldn't work..) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscri

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-11-05 Thread craftyguy
I did, here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232877/comments/9 As far as I can tell, everything seems to be working properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232877

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-11-03 Thread craftyguy
I would love to be able to update my BIOS, however Acer's flash tool only supports Windows. The BIOS appears to be based on Insyde EFI, and I was able to extract a .fd file, however I wasn't able to find a utility to actually flash it (from freedos or ??). Do you, or anyone here, know of a way to u

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-10-03 Thread craftyguy
I've made some (hopefully) interesting progress: The firmware version seems to be 8, using the formula in the elantech_set_properties function, so I modified the file like this to force it to set hw_version to 4: clayton@ultrabook:~/Downloads$ diff -Naur psmouse-old/dkms_source_tree/src/elantec

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-10-03 Thread craftyguy
Here's the output after building/loading that module: clayton@ultrabook:~/Downloads$ dmesg|grep elantech [ 15.277239] psmouse serio1: elantech: unknown hardware version, aborting... [ 425.625027] psmouse serio1: elantech: unknown hardware version, aborting... [ 1214.662773] psmouse serio1: elan

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-10-03 Thread craftyguy
I have reported the bug to my best guess for maintainers ( linux- in...@vger.kernel.org), and as of right now I have not heard back yet. ** Tags added: kernel-bug-reported-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1232926] Re: Touchscreen stops working after resume from S3

2013-10-01 Thread craftyguy
confirmed on upstream kernel: clayton@ultrabook:~$ uname -a Linux ultrabook 3.12.0-031200rc3-generic #201309291835 SMP Sun Sep 29 22:37:02 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream --

[Bug 1232877] Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-09-30 Thread craftyguy
Confirmed in upstream: clayton@ultrabook:~$ dmesg|grep -i elan [7.263829] usb 2-7: Manufacturer: ELAN [ 17.900924] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/input/input6 [ 17.901119] hid-multitouch 0003:04F3:015B.0001: input,hiddev0,hidraw0: USB HID v1.

[Bug 1232926] Re: Touchscreen stops working after resume from S3

2013-09-29 Thread craftyguy
Xorg.0.log file attached ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232926/+attachment/3850040/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.n

[Bug 1232926] [NEW] Touchscreen stops working after resume from S3

2013-09-29 Thread craftyguy
Public bug reported: Touchscreen stops working after resume from S3 (suspend). This is printed to Xorg.0.log when the system is powered up: [29.915] (II) XINPUT: Adding extended input device "ELAN Touchscreen" (type: TOUCHSCREEN , id 11) [29.915] (II) evdev: ELAN Touchscreen: initialize

[Bug 1232877] [NEW] Touchpad reported as: "elantech: unknown hardware version, aborting"

2013-09-29 Thread craftyguy
3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC1: craftyguy2497 F pulseaudio  /dev/snd/controlC0: craftyguy2497 F

[Bug 1228801] Re: wpa_supplicant crashed with SIGSEGV

2013-09-28 Thread craftyguy
*** This bug is a duplicate of bug 1210785 *** https://bugs.launchpad.net/bugs/1210785 >This particular crash has already been reported and is a duplicate of bug #1210785, Uhh, that bug doesn't seem to exist. I am also experiencing this crash, and when I try to report it I am told that it's a

[Bug 665796] Re: Intel Core i7 - Timer interrupt freezes, high CPU usage, system becomes sluggish

2011-01-15 Thread craftyguy
Upgrading to 2.6.35.22 does not fix the issue for me. I'm running an i7 940, and my configuration is very similar to what is posted above -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665796 Title:

[Bug 267818] [NEW] must specify additional zero character when setting PCI passthrough device in Xen-3.3 vm.cfg files

2008-09-08 Thread craftyguy
Public bug reported: When adding a PCI device to a vm.cfg file in Xen-3.3, an extra zero has to be appended to the beginning of each octet in the PCI device ID. For example, adding the device 02:00.1 to a vm cfg file would look like this: pci = [ '002:000.1' ] It should (as in xen-3.2) be like