CF-31 Linux

I now have a CF-31 Mk2 and Mk4. As usual I am installing Linux and that means plenty of fiddling. Luckily I actually enjoy this as opposed to some of us *cough*SHAWN*cough* so I usually get by and tweak my systems to my liking. I am concentrating on the Mk4 CF-31W with Debian 9.6. I added a Sierra MC7700, GPS and optical drive. (Thanks Shawn)

Naturally not all things work properly. Hopefully this thread will eventually contain enough information to help out others.

Using Debian 9.6 LXDE with Openbox and customized Slim login manager, kernel 4.9.0-8-amd64

What didn't work:

• WIFI missing firmware package
  
• Sound channel mixer volume for headset mistakenly controls internal speaker
• LCD brightness Fn keys
• Cannot calibrate touch screen -- FIX IN THIS THREAD

Wifi missing package is easy to fix. I had https://packages.debian.org/stretch/all/firmware-iwlwifi/download on a USB drive when prompted by the installation package. Otherwise if installed without it, just download firmware-iwlwifi (or your distro's equivalent) from the non-free repository with a wired ethernet connection.

Sound channel is an ALSA SNAFU which I remember having fixed once. I don't remember now.

LCD brightness is annoying. Various ACPI kernel parameters didn't work and the CF-31 doesn't directly support hardware backlight dimming with xbacklight as far as I can tell, so I wrote up a quick script that uses xrandr --brightness

EDIT: Script in later post supersedes this

Code:

#!/bin/bash
#Change device to match your hardware - figure this out with "xrandr | grep connected"
device=LVDS-1
#Limit xrandr range. 1.0 is maximum brightness  but you can go beyond these limits
#Strange things can happen if you go below 0.0 and way above 1.0
upper=1.0
lower=0.0
#Steps for each up and down command. Increase for larger steps.
increment=0.1
decrement=0.1
#Get the current brightness value
current=`xrandr --verbose | grep -i brightness | awk '{ print $2 }'`
#Define values for adding and subtracting from the current value
subinc=`bc <<< $current-$decrement`
addinc=`bc <<< $current+$increment`
#define up and down arguments
case $1 in
   up)
      if (( $(echo "$addinc <= $upper" | bc -l) )) ; then
           xrandr --output $device --brightness $addinc
      fi
   ;;
   down)
      if (( $(echo "$subinc >= $lower" | bc -l) )) ; then
           xrandr --output $device --brightness $subinc
      fi
   ;;
   *)
   ;;
esac

#echo $current

Shoved the above in a file named it brightness and chmodded it executable. Then typing brightness up or brightness down does the trick. After that it's just a question of using the desktop manager's hotkey configs to assign the up and down commands to the XF86MonBrightnessDown/XF86MonBrightnessUp keys. This script should work for almost any computer.


For the touch screen, I didn't get far yet. xinput_calibrator recognizes the Fujitsu panel but does little else. Xorg doesn't seem to be able to control it by using the "Fujitsu Component USB Touch Panel" name although that is what the kernel is reporting the device as. This one I'm still trying to figure out.

Plenty of other things to do and try out. Questions? Need clarifications? Got other bugs for other MK? Solutions? This is the thread. I think.

 

Harumpf! Software still frustrates me. I am a hardware guy. Going to attempt a repair on my Nikon D610 this weekend. 40-50 screws much smaller than the ones that hold a wifi card in.

You should have witnessed the Linux circus of Jeff and I. We tried about 20 distros on a CF U1.

Currently I am trying Elementary OS on a FZ G1 mk3.

 

Linux circus? You guys have all the fun.

I installed your GPS in the Mk4 earlier today. Easy peasy.

Speaking of which, today I found Gnome Maps which is a neat little GPS map and navigation application for Linux. It uses Openstreetmap under the hood. It was downloadable from the Debian repos.

 

Link to some of the circus

http://forum.notebookreview.com/threads/2-guys-a-cf-u1-and-internet-connection-to-linux.825660/

 

Still tinkering. Apparently xrandr --brightness and my script only changes the monitor gamma values and doesn't really dim the backlight. So no help in power savings.

 

Concerning touchscreen calibration, I found this webpage with useful advice:
https://cubiclenate.com/2018/04/

Relevant lines being:

Using this info, my calibration script (Touchscreen.sh) contains the following:

Code:

#!/bin/sh
# Coordinate touch panel to screen
xinput set-prop "Fujitsu Component USB Touch Panel" "Coordinate Transformation Matrix" 1.075, 0, -.03, 0, 1.1, -0.07, 0, 0, 1

Calibration utility can be used to fine-tune.

 

Thanks, seems to work. Too bad it has to go into a startup script instead of an xorg conf file, but it's progress!

 

Dug up this old post here that has sort of a solution for the sound mixer problem
http://forum.notebookreview.com/threads/linux-ubuntu-touch-pad-sound-fix-cf-31-mk2.813539/
Kudos for ToughbreaK for having posted it. However he did not describe what the problem was in the first place.

After applying the fix from that post, it still uses what is identified as Headphones in alsa-mixer for volume control but things line up properly in Pulseaudio. The speaker volume slider in alsa-mixer appears to do nothing at all. The speaker is not auto-muted as if it were headphones so it essentially fixes my problem. Otherwise I had to go in alsa-mixer, unmute and crank up the headphone volume to get sound through the speaker.

As for the touchpad, the only thing I have with mine is that it is detected as ImPS/2 Generic Wheel Mouse and I have little control in Xorg to modifying buttons, tapping and scrolling behaviour, very much like the Fujitsu touchscreen. Otherwise it works flawlessly and doesn't throw up any errors. The i8042.notimeout i8042.nomux kernel parameters don't seem necessary in my case.

 

Found a program that actually controls the backlight. Downloaded it from repos and it runs like this example for 50% brightness (values go from 0 to 1414)

Code:

brightnessctl -d intel_backlight s 707

Only problem is that it needs root permissions to access the device so commands may need to be preceded by sudo.

Code:

sudo brightnessctl -d intel_backlight s 707

/usr/bin/brightnessctl could be added to /etc/sudoers as a workaround, but I don't like it. I guess I could also change permissions on the device file.

If anyone is interested, here is an adaptation of my script with this program. If anybody needs specifics on how to get it to work, let me know. I am assuming, perhaps wrongly, a minimum of Linux knowledge to those who are following this thread so I apologize in advance if this isn't clear so just ask for help. Debian-like distros may need to

Code:

sudo apt-get brightnessctl

The script below copied into a file and made executable (chmod +x yournewfile)

Code:

#!/bin/bash
#Change device to match your hardware - figure this out with "brightnessctl -l"
device=intel_backlight
#No real need to change anything below this
#min/max values
upper=1414
lower=0
#Steps for each up and down command.
increment=10
decrement=10
#Get the current brightness value
current=`brightnessctl -d $device g`
#Define values for adding and subtracting from the current value
subinc=$(($current - $decrement))
addinc=$(($current + $increment))
#define arguments for up and down
case $1 in
   up)
       if (( $(echo "$addinc <= $upper") )) ; then
           brightnessctl -q -d $device s $addinc
       fi
   ;;
   down)
       if (( $(echo "$subinc >= $lower") )) ; then
           brightnessctl -q -d $device s $subinc
       fi
   ;;
   *)
       brightnessctl -d $device
       echo "Use \"up\" or \"down\" as arguments"
   ;;
esac

Properly dimming the backlight instead of mucking around with xrandr and its silly gamma tweaking makes a huge difference on battery usage. I am thinking that all I need is some ACPI-related package or suite of scripts to do what I need instead of scripting from scratch. I just haven't found it yet. But this is fun.

 

One other thing of note: I had to disable WICD as a network management utility which is now the new default for my distro. I don't particularly like Network Manager, which was the previous default in Debian 8, but in this case it supports WWAN connections while WICD does not. And I had dozens of saved Network Manager system-connections files from my CF-30 and CF-19 that I needed to copy over in order to keep my connection preferences/passwords for all the LANs/WLANs I use.

I wouldn't mind knowing what other CF-31 Linux users do to address this issue, what is your preferred network management software and so forth. I would have kept WICD had it been able to talk to the WWAN card. I've used it before and it works really well.

 

I decided to try out a Sierra MC7455 WWAN module.
Please note that I am in the habit of trying out WWAN modules for fun and assume the risk of non-Panasonic approved cards not working. Don't blame me if you try one out and it doesn't work out for you and you throw your money out the window in the process. To my knowledge Panasonic hasn't released any Toughbook with the MC7455.

That said, the MC7455 is interesting because it supports many GSM and LTE bands as well as LTE Advanced which would make it ideal for traveling if it works.

So I took the chance and bought one on eBay. Right away there were problems. It would suddenly disappear from the OS as if the device were pulled out of the slot and disabled itself consistently after a few minutes. When it was visible, it was almost impossible to connect. Looks like I fixed those issues.

1) Downloaded Linux QMI drivers: https://source.sierrawireless.com/r...rivers-linux-qmi-software-s2,-d-,36n2,-d-,55/ (requires sign up to download). The file is tar.bz2 but in fact it is gzip. (tar -xzvf filename.tar.bz2)
Then I cd into the extracted Gobinet directory. Ran 'make' then as root 'make install' or 'sudo make install'. Reboot and done

2) Added usbcore.autosuspend=-1 to GRUB_CMDLINE_LINUX_DEFAULT section in /etc/default/grub, then as root update-grub or 'sudo update-grub' and reboot.

Now I have a working MC7455 in a CF-31.

YMMV

 

Hey kode. I have a CF-31Mk3 that is running MX Linux 18.3. It has a MC7700 that I am going to try and get working. Will let you know how it went if things go well. If things do not go well, I will be looking for some help. L8R.

 

Coolness. I really want to know how it turns out.

 

On my 53, the wireless kept acting up so I de-activated network manager and installed CENI from synaptic manager.
That might be another one to try if so inclined. This is on an installed Mx18.3 CF-53
Wireless works good now at work.
From Synaptic CENI is: "
A Curses user interface for configuring network interfaces with ifupdown.
Ceni can manage basic network interface ifupdown configuration stanzas for
ethernet and wireless devices."

 

Curious. What exactly was happening under Network Manager?

 

Would not could not connect to the hospital WiFi network.
For some odd reason CENI did the trick and didn’t play with it anymore.


Sent from my CF-M34

 

I have a no mouse issue with MX-18.3 on CF-31JCG802M
Loading newest Peppermint and LMDE3 same issue of no mouse using the touchpad. Works in windows 7 hdd from the MK4 CF-31
Searched and tried several fixes from links:
https://forum.mxlinux.org/viewtopic.php?t=43690
Ran this solution but nothing happens:
demo@mx1:~
$ sudo echo "options psmouse proto=imps" | sudo tee /etc/modprobe.d/psmouse.conf >/dev/null
demo@mx1:~
$

http://forum.notebookreview.com/threads/linux-ubuntu-touch-pad-sound-fix-cf-31-mk2.813539/
This link looks like it edits grub however in Terminal running the solution shows:
demo@mx1:~
$ sudo gedit /etc/default/grub
sudo: gedit: command not found
Edit...And am at a stand-still now asking for solutions....Edit
Just found this old linkage and will try page 3: http://toughbooktalk.com/viewtopic.php?f=39&t=2662&start=50
Followed Sheepman's directions for Terminal, and when I ran update-grub got this:
$ sudo update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.
demo@mx1:~
$

 

Simply shows that gedit isn't installed, which is Gnome's standard text editor. Try another editor. I think the default graphical text editor for MX Linux is leafpad.
sudo leafpad /etc/default/grub

Or try a text-based editor like nano or pico. Keep us updated!

 

Nano works, ran this:
sudo nano /etc/default/grub

 

In the above, changed the grub line as described in toughbooktalk link, and then when I ran update-grub got this:
$ sudo update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.
demo@mx1:~

So it doesn't look like grub was updated, and wondering what overlay means.

 

Backing up, I changed (added this in front of quiet)
GRUB_CMDLINE_LINUX_DEFAULT="i8042.notimeout i8042.nomux quiet splash"
Exit with control X
Saved with Y

 

So you got this figured out?

 

Are you running this from a full install on a hard drive or some form of live USB/CD/DVD?

 

Not figured out yet
Worked previous with Mx16 persistence usb but no joy Mx18 persistence usb
I don’t want to install this (yet)
Trying to tweak touchpad and sound first with live usb using persistence


Sent from my CF-M34

 

Just having problem with updating grub after tweaking the system as you describe.
More information needed on the canonical path of overlay...
$ sudo update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.

 

Could this be because of the LiveUSB?

Possibly a system in place to protect grub and thus the LiveUSB?

Try it again using persist_static and save when you are launching the stick. Persist-static saves to the USB as you are using it. Slightly slower because of writing to the stick but you make up for it in shut down speed.

Catching me is easier with PM.....start a new one if this subject will be long-winded.

Lefty

 

[ QUOTE="SHEEPMAN!, post: 10932952, member: 319309"]Could this be because of the LiveUSB?
Possibly a system in place to protect grub and thus the LiveUSB?
Try it again using persist_static and save when you are launching the stick. Persist-static saves to the USB as you are using it. Slightly slower because of writing to the stick but you make up for it in shut down speed.
Catching me is easier with PM.....start a new one if this subject will be long-winded.
Lefty [/QUOTE]
Great idea, will follow through and report back on the 31

 

Great idea, will follow through and report back on the 31[/QUOTE]
Follow up, a tweak that works with a one liner in Terminal and no Grub work needed:
NEW INFORMATION AND A ONE LINER

OPEN A TERMINAL
CUT AND PASTE THIS:
sudo echo "options psmouse proto=bare" | sudo tee /etc/modprobe.d/psmouse.conf >/dev/null
REBOOT

Uggg...Thanks!
Mouse pad is now working with this one liner thank you very much Sheepman

 

Upgraded Debian to 10.0 (buster) and gpsd stopped working because I had IPv6 disabled. It needs the v6 loopback interface to work and I suspect the systemd service file is running arguments to connect to the socket in parallel to the IPv4 loopback, because gpsd runs fine when you invoke it by hand.

Instead of mucking around with fixing it, I just re-activated IPv6.

Edit:
/lib/systemd/system/gpsd.socket

Code:

[Unit]
Description=GPS (Global Positioning System) Daemon Sockets

[Socket]
ListenStream=/var/run/gpsd.sock
ListenStream=[::1]:2947
ListenStream=127.0.0.1:2947
SocketMode=0600

[Install]
WantedBy=sockets.target

Edit 2:
Woo! Already a dist-upgrade available to 10.1 today.

 

Fingerprint sensor for authentication in Debian? Why the heck not.

Install as root or sudo:
apt-get install fprintd

For testing, install fprint-demo, run it and enroll your left thumb (five swipes) then verify it.

Install as root or sudo:
apt-get install libpam-fprintd

Run as root or sudo pam-auth-update and check the fingerprint authentication option

fprintd-enroll -f left-thumb <username>
(or run fprintd-enroll -f left-thumb without the username to enroll the currently logged in user)
Swipe your thumb 5 times.

Logout then log back in to check for results.


Even works with my slim login manager. To disable because your thumb got amputated, bypass it all by booting in rescue mode (select it from the grub menu) then re-run pam-auth-update and uncheck fingerprint. Otherwise run pam-auth-update anytime. There are ways to shore up security even more by disallowing such an easy way to disable it in PAM but I'm not that paranoid yet. Right now it's just pretty convenient and I can put more robust passwords. If I continue using this, I better stock up on fingerprint sensor plastic covers.

 

After upgrading to Debian 10 (buster) I ran in to a familiar issue with swapped output devices in the mixer. You know something is funny when every time you turn it on the volume icon shows it is on mute.

I ran into these sort of pulseaudio shenanigans before so I just had to take the time to figure it out again, and it wasn't high priority for me.

Edit /usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf

Look for these two Element Headphone and Speaker sections and modify them to that they look like this, by adding, editing or removing lines as necessary (requires root or sudo'ing of course) :

[Element Headphone]
switch = off
volume = merge
override-map.1 = all
override-map.2 = all-left,all-right

[Element Speaker]
required-any = any
switch = mute
volume = off

 

Recently I had to ditch the Sierra MC7700 and take back the MC7455 I put into the wife's CF-31. My carrier did something to their network and I needed the extra bands to work around it.

The MC7455 has given me a lot of trouble. I requires a kit config of 0, which is unusual. But what really got me was that I typically run a "powertop --auto-tune" on startup which helps a bit with power consumption. It will auto-suspend USB devices (including WWAN modules) when they're not in use and do a few other minor tweaks which in some cases can translate into 30 minutes of extra battery time. Normally I highly recommend doing so. No problems with the MC7700 but the MC7455 gets a little squirrely when you muck around with its power settings so I had to disable that startup script.

Doing a few more tests to see how stable it is now that made the changes.

 

[/QUOTE
Look for these two Element Headphone and Speaker sections and modify them to that they look like this, by adding, editing or removing lines as necessary (requires root or sudo'ing of course) :

[Element Headphone]
switch = off
volume = merge
override-map.1 = all
override-map.2 = all-left,all-right

[Element Speaker]
required-any = any
switch = mute
volume = off[/QUOTE]

Thanks for this code Kode. Worked fine.

 

Here's one for the books.

A few months ago I snagged a CF-31 with a Panasonic dock CF-VEB311. (thanks Morgan)
Still with Debian buster...
If you boot your unit with a mouse plugged into the dock, it will NOT work unless you unplug and re-plug it in. You have to pass a kernel parameter...

Edit as sudo or root with your favourite text editor - vi, nano, pico, leafpad.... etc...

Code:

sudo nano /etc/default/grub

Pass this parameter to GRUB_CMDLINE_LINUX_DEFAULT

Code:

usbcore.autosuspend=-1

My GRUB_CMDLINE_LINUX_DEFAULT presently looks like this but you can ignore most of it since I was just testing and debugging stuff. The good stuff was added to the end:

Code:

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log_priority=3 usbcore.autosuspend=-1"

As sudo or root - update grub.

Code:

sudo update-grub

Reboot then the mouse will work immediately when the unit powers on while docked with the mouse in one of the dock's USB ports.

I suspect other USB devices such as keyboards and so-forth might also benefit from this.

Originally I added this kernel parameter to help with the Sierra WWAN acting all squirrely, then noticed it fixed my USB mouse issue as a side-effect.

:beer:

 

Thanks for the information kode.

I might have to try this on the 52 and see if it helps with the wifi card dropping off every 6 hours or so. All I do when it happens is cycle the wireless switch off and on again.