Hi, Michael. Noticed your previous post after sending mine. :-) Fallback code for older ThinkPads looks reasonable and gives no new (not known) regression. As I don't have new (0x200) ThinkPads (T420 is my latest), I cannot review and test for new protocol and functionality. Sorry. Just FYI, `acpidump -d -t DSDT | fgrep MHKV` on my T420 claims "Method (MHKV, 0, NotSerialized)" only. So it would go fallback way. Preferrably, user(s) of latest (i.e, T480) models pops in and report this worked or not. [Is there one more protocol like 0x300?] Thanks for your work! On Fri, 2 Feb 2018 12:38:47 +0100 Michael Gmelin <freebsd_at_grem.de> wrote: > > > On Fri, 2 Feb 2018 20:23:32 +0900 > Tomoaki AOKI <junchoon_at_dec.sakura.ne.jp> wrote: > > > Not 100% sure but possibly some (one?) EisaId are (is) missing in > > ibm_ids definition of sys/dev/acpi_support/acpi_ibm.c. > > Currently it contains "IBM0068" and "LEN0068". > > > > Run `acpidump -d -t | fgrep EisaId` as root on your T470s and look for > > EisaId something other than... > > > > IBM0068 > > LEN0068 > > IBM3780 > > PNP???? > > > > If there's something new, insert them (it) to > > static char *ibm_ids[] = {"IBM0068", "LEN0068", NULL}; > > line of sys/dev/acpi_support/acpi_ibm.c, between "LEN0068" and "NULL". > > > > If there's none, it's over my hand. :-( > > There could be some incompatibility, like struct member change etc. > > Hi Tomoaki, > > Could you please take a look at this? > > https://reviews.freebsd.org/D14103 > > Thanks, > Michael > > > > > > > See my web page [1] of part "Note for limitations of ACPI in ThinkPad > > T420" and The FreeBSD Forums' thread noted there [2] for more info. > > Although old, but part of them can be useful. > > > > [1] http://www.dec.sakura.ne.jp/~junchoon/machine/freebsd-e.html > > [2] https://forums.freebsd.org/threads/26759/ > > > > > > On Thu, 1 Feb 2018 21:13:05 -0500 > > Bridger Dyson-Smith <bdysonsmith_at_gmail.com> wrote: > > > > > Hi list and Michael - > > > > > > I received a T470s at work and decided to jump into the CURRENT end > > > of the FreeBSD pool. I have a weird acpi_ibm issue and I'm not sure > > > where to start trying to diagnose the issue. > > > > > > # uname -a > > > FreeBSD spanner 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328126: Thu > > > Jan 18 15:25:44 UTC 2018 root_at_releng3.nyi.freebsd.org:/ > > > usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > > > > > I've loaded acpi_ibm via /boot/loader.conf: > > > acpi_ibm_load="YES" > > > > > > and the module shows as being loaded: > > > # kldstat | grep acpi_ibm > > > 8 1 0xffffffff8278e000 7570 acpi_ibm.ko > > > > > > However, I don't have any of the sysctl knobs available; e.g. > > > # sysctl -a | grep acpi_ibm > > > # > > > > > > or > > > # sysctl dev.acpi_ibm.0.fan_speed > > > sysctl: unknown oid 'dev.acpi_ibm.0.fan_speed' > > > > > > I've (tried) to look through the commit messages on svn-src-head, > > > but I'm not seeing anything specifically related to acpi work, or I > > > just don't know what I'm looking at (a definite possibility). > > > > > > Would someone be able to provide a bit of debugging direction here? > > > Reviewing `dmesg -a` doesn't tell me anything specific about > > > acpi_ibm. > > > > > > Thanks in advance for your time and trouble. > > > Bridger > > > _______________________________________________ > > > freebsd-current_at_freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > > > "freebsd-current-unsubscribe_at_freebsd.org" > > > > > > > > -- > Michael Gmelin > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > -- Tomoaki AOKI <junchoon_at_dec.sakura.ne.jp>Received on Sun Feb 04 2018 - 10:58:23 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC