Re: Dell latitude 7490 touchpad support?
On Saturday, September 29, 2018, 8:48 PM (UTC+0100), Johannes Lundberg wrote: > Hi > > I just got a new work laptop and the touchpad does not work. Some > information points to that this machine has a Microsoft precision touchpad. > I can't see any USB device so I'm wondering if this is an I2C device? > > Do we have any driver for this? > > /Johannes > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Hi, I am also interested in this issue (broadly), as my laptop (Acer Aspire E5-575) has Synaptics one in it. By factory default setting, the touchpad is not detected at all even if I have `ig4_load="YES"` in `/boot/loader.conf`. However, when I switch the touchpad option in BIOS from 'Advanced' to 'Basic,' kernel started to see it as `psm0: model Synaptics Touchpad, device ID 0`. Hence I am using it under 'Basic' mode for now. (might not be related to the above) Also, this laptop also has a key combo (fn + F7) to enable/disable the touchpad; while the key combo does work on killing or reviving touchpad, kernel spits these messages every time I do that: ``` acpi_ec0: EcCommand: no response to 0x84 acpi_ec0: EcCommand: no response to 0x84 acpi_ec0: GPE query failed: AE_NO_HARDWARE_RESPONSE ``` So my understanding is that the `acpi_ec` driver expects something from hardware in return to a probing but could not get what it wants? I have no clue at all as I could not find any info on `acpi_ec`. Can anyone tell me what is happening? I'm running amd64 r339274 at the moment. Thank you, -- Hyun Hwang ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT r331284: crashing with USB
On Wednesday, March 21, 2018, 11:41 PM (UTC-0600), Warner Losh <i...@bsdimp.com> wrote: > Do you have a traceback? This I got from core.txt: ``` db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe46e3c0 vpanic() at vpanic+0x18d/frame 0xfe46e420 panic() at panic+0x43/frame 0xfe46e480 dadone() at dadone+0x1cc9/frame 0xfe46e9e0 xpt_done_process() at xpt_done_process+0x390/frame 0xfe46ea20 xpt_done_td() at xpt_done_td+0xf6/frame 0xfe46ea70 fork_exit() at fork_exit+0x84/frame 0xfe46eab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe46eab0 ``` Is this suffice? Full dump is available [here](https://www.amazon.com/clouddrive/share/48KzBn0452wRk6bS56oDu1MGXG8p8ug7TGsj8yhGkKN) if you need. (I'll unshare this next month.) Also, judging by the stack trace, this problem looks very similar to [this](https://lists.freebsd.org/pipermail/freebsd-current/2018-March/068900.html), I guess? > actually, can you test https://reviews.freebsd.org/D14792 for me please? I would love to and I can try, but... > I won't be able to test until Friday Same here, I cannot physically access the machine of interest until Friday. :( -- Hyun Hwang ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT r331284: crashing with USB
On Wednesday, March 21, 2018, 12:07 PM (UTC+0100), "Hartmann, O." <ohartm...@walstatt.org> wrote: > Hello. > > Incident: CURRENT r331284 can be brought down reliably with an USB > flash drive plugged in and out without mounting or doing anything with > it. > > [...] > > Does anyone else observe this bug? > Can confirm: whenever I plug my Transcend USB microSD reader into my builder (amd64, r331284), the kernel does attach da0 then immediately panics and falls down to `db>` prompt. > I can plugin the USB and then unplug it and after two or three times doing > this, the box goes down. I did not even have to plug-unplug the reader three times; plug the reader in and bam! immediate panic. AFAIK, r331115 did not have this issue because I was able to update my RPi 2 with the very reader from the very builder. I managed to salvage kernel binary dump; in case the dump is needed, please let me know. -- Hyun Hwang ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
