Lexus IS200/IS300 Alarm Siren Removal

My theft warning siren was going off independently of the alarm system. Here is how to remove it.

The siren is behind the right side boot lining. Start by pulling it.

img_0366
Click for full size

The siren is installed on the back side of that panel with the white plug.

img_0355
Click for full size

Removal is as follows:

  • Remove the 2 gold nuts (10mm)
  • Pull out the siren module
  • Unclip the connector

Cable tie the connector in a position so it won’t rattle.

img_0358
Click for full size

Reinstall the boot liner.

img_0367
Click for full size

MX83 Toyota strut top bearings

This is regarding Toyota P/N 48609-22070 (factory Toyota only) strut mounts.

The bearings are a Nachi 6302 without seals. Nachi also make a sealed version

img_0281

I have no idea if they have a retaining compound on them, but if you know what you’re doing they should be replaceable. If yours are knocking or creaking replacing the bearings would be an economical alternative to getting new mounts.

Macports error on OSX Sierra

If you’re compiling a package and run into:

:error:configure Failed to configure gmp, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.1.1/config.log
:error:configure org.macports.configure for port gmp returned: configure failure: command execution failed

Then look at config.log, and find:

...
In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/__mutex_base:17:
/usr/include/pthread.h:423:1: error: C++ requires a type specifier for all declarations
__SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
^
/usr/include/pthread.h:423:66: error: expected ';' after top level declarator
__SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
                                                                 ^
2 errors generated.

In this case __SWIFT_UNAVAILABLE_MSG hasn’t been been defined. The definition is meant to come from Availability.h at /usr/include/Availability.h

A few OSX/Macports releases ago there was Issue 48471. As a workaround, some people used a locally modified Availability.h installed in /usr/local/include/ or /opt/local/include/, which are preferentially included over /usr/include/.

As the underlying problem is now resolved they are no longer required and can be deleted.

$ sudo rm /usr/local/include/Availability.h /opt/local/include/Availability.h

Once they are gone the current version of Availability.h from /usr/include/ will be included next time you try to build your package.

If you wiped out your original /usr/include/Availability.h for any reason, restore it with:

$ sudo cp /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/Availability.h /usr/include/Availability.h

Permissions are fine as they are.

Acknowledgments:

The macports-users mailing list also found this solution.

Alternatively, according to https://trac.macports.org/ticket/52258#comment:13
you can comment out the problem line in pthread.h as a workaround. (note: I do not recommend this)

Wireless card stops working on Linux

2 Tips, especially for ath9k users:

Tip 1 – Unload and Reload your driver

Have you tried turning it off and turning it on again? No, seriously. Unload and reload the driver. I had an ath9k card that would work again for hours after doing this:

$ modprobe -r ath9k
$ modprobe ath9k

Eventually it stopped working and I replaced it with a D-Link DWA-131. I could have tried tip 2 first:

Tip 2 – Turn off hardware encryption

The parameter name varies between drivers, but the method is largely the same:

Create/Edit driver options file:

$ sudo nano /etc/modprobe.d/ath9k.conf

Put contents:

options ath9k nohwcrypt=1

Then reboot.