Hi there!
I just ran into the same problem as described in the first post. However, after reading a lot about update-rc.d, I recognized where the problem is: The TW-driver is setting up itself as a service by using the update-rc.d tool. Therefore, the file TWDrvStartup has to put some hints in its comment-header to notify update-rc.d on how to register itself as a service. See details here: http://wiki.debian.org/LSBInitScripts/
So, the first two warnings are:
Code:
update-rc.d: warning: /etc/init.d/TWDrvStartup missing LSB keyword 'required-start'
update-rc.d: warning: /etc/init.d/TWDrvStartup missing LSB keyword 'required-stop'
They will disappear when inserting the lines
Code:
# Required-Start:
# Required-Stop:
to the header. I assume they were left out, because the are no dependencies, so the values can just be empty.
So, the latter two warnings are:
Code:
update-rc.d: warning: TWDrvStartup start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (2 5)
update-rc.d: warning: TWDrvStartup stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 1 3 4 6)
As far as I understood, they just tell us, that the TWDrvStartup script requests to register for run-leves 2 5 (Start) and 0 1 3 4 5 (Stop), but the system is recommending to register a standard script at run-levels 2 3 4 5 (Start) and 0 6 (Stop). See the header in TWDrvStartup:
Code:
# Default-Start: 2 5
# Default-Stop: 0 1 3 4 6
So, the warnings will disappear, when we change those lines to
Code:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
So, altogether, the comment-header of TWDrvStartup.ORIG should be modified to:
Code:
### BEGIN INIT INFO
# Provides: TwDriver
# Required-Start:
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: Start the MT 7 touch screen driver
### END INIT INFO
Hopefully, this should still match the intention of the driver's programmer. If you now run ./Install, no warnings will appear.
And now (hopefully) the best news:
All this outputs were just warnings, no errors! So you probably already had a successful installation of the 3M-drivers, but didn't recognize it, since there is no final message like "installation successful finished". I just ran into the same trouble and thought there were some installation errors.
However, for the moment I do not have any 3M monitor to test it, but at least the tools TWCalib and StartCP are present (StartCP is generated during installation) and work, so I have the hope that all works fine as soon as I plug in a 3M touchscreen.
Perhaps you could already try it out?
Bookmarks