| From: Aaron Job Andrus <[EMAIL PROTECTED]> | | Thanks! I'll start there.
I googled for: R3000Z freebsd and found: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/67745 Within that you can see what is wrong with our notebooks: the keyboard processor hangs on an apparently legitimate command. In particular, see: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=88636+0+/usr/local/www/db/text/2004/freebsd-amd64/20040704.freebsd-amd64 and use the wayback machine to look at the description of the AT keyboard hardware: http://web.archive.org/web/20041011052117/http://www.clipx.net/ng/hardware/ng1462d.php My understanding is that the workaround is in FreeBSD (the PR is closed). Perhaps you need to supply a boot flag of some kind to enable the workaround. Too bad the PR does not explain this. There may be important hints within: http://blackk.union.edu/~black/freebsd/ It appears to be outdated. Do look at the place where it says hint.atkbd.0.flags="0x9" *maybe* that is the way to enable the workaround. That page points to an interesting thread: http://lists.freebsd.org/pipermail/freebsd-amd64/2005-March/004018.html If I were a FreeBSD user, I'd want the workaround to be documented clearly. One place would be in the PR. Perhaps it is documented in some place like the release notes. _______________________________________________ Linuxr3000 mailing list [email protected] http://mail.kdewebdev.org/mailman/listinfo/linuxr3000
