Linux Mint on the CF-31

[droppointalpha]

Sounds like you need more batteries.

I'll be around for awhile and notate anything else I find. Whenever you or anyone thinks of something to test, I'll be checking in now and again through out the day this week at least to see. I realise the database of information is a little lacking on the 31.

[Azrial]

The CF-31 seems very much like the CF-30 to me, more so then the 30 to the 29.

[droppointalpha]

It does feel like a closer bump from the 30 to 31. I think, given the nature of how computing has reached some better level of standardization in both components and construction, that the paths should become smoother on the whole.

I am still trying to puzzle the model number though, as it does not seem to follow standard formatting. Configurator doesn't register it either.

[Shawn]

core 2 duo to i5 is a big hardware jump.

[SHEEPMAN!]

I have a couple batteries, I just need to charge them.

Just to clarify CF-31 went to Interlink Touchpad at MK2.

There's a thread about it here some-place.

This 1110 hour CF-29 is messing with me. FYI if you get pastel bios colors go back inside and plug the lcd ALL THE Way in. The one under the keyboard. And the touchscreen repair didn't take again. I hope techtuff is reading his mail.

viewtopic.php?f=39&t=2662&start=40&hilit=interlink Has nothing to do with CF-31 MK1 just CASUAL READING

Jeff

[droppointalpha]

Using Qubes, it is not seeing the touchpad... So this "casual" reading might be necessary.

[kode-niner]

I have a couple batteries, I just need to charge them.

Just to clarify CF-31 went to Interlink Touchpad at MK2.

There's a thread about it here some-place.

This 1110 hour CF-29 is messing with me. FYI if you get pastel bios colors go back inside and plug the lcd ALL THE Way in. The one under the keyboard. And the touchscreen repair didn't take again. I hope techtuff is reading his mail.

viewtopic.php?f=39&t=2662&start=40&hilit=interlink Has nothing to do with CF-31 MK1 just CASUAL READING

Jeff

Thank goodness I missed that thread. I would have been pontificating about why some of you went through sudo hell and should never use it.

[SHEEPMAN!]

Using Qubes, it is not seeing the touchpad... So this "casual" reading might be necessary.

Any input is appreciated.

With the weird model # you may have gotten a MK1 with a Interlink pad. Odd.

As I recall, the Interlink thinks it's a PS/2 mouse. Page three or four we started getting the idea.

What is Qubes?

[droppointalpha]

https://www.qubes-os.org/

It is an interesting method of security through (by my view) an incredible level of virtualization for one machine. Doesn't run bad on this mk1 either and is far more resource efficient than using Oracle's free version of their VM software.

It is kinda strange, with all the various virtualizations and the AdminVM is very restricted... It is a big download but if you want to try the variation I'm working with, find below.

https://www.whonix.org/wiki/Download

EDIT
Didn't see anything that might be useful in Qubes. I'm not sure how to approach the admin level VM or the Xen hypervisor. The settings panel for the admin level shows the touchpad greyed out.

The possibility of an interlink pad did dawn on me, as the texture of this one is unlike any toughbook I have handled yet. But then the fact that my both Debian and Arch based distros have detected and functioned no problem make me wonder.

The Hypervisor and general build theory isolate USB controllers. If I have an interlink, does it still use PS/2? I see the touchscreen under USB controllers in Qubes, which has a convenient hardware display pane I can access somewhat similar to device manager in windows. I'm not sure how to check which controllers and what devices fall under USB in Mint except using lsusb, which is not telling me anything particularly useful.

[droppointalpha]

Okay, haven't got much further (for lack of effort- visiting family and all that) but what little I have read is not been helpful. So I plan to start at square one. I still have the Win7 HDD the unit came with; I will attempt to ascertain the exact make/model touchpad and see how windows sees the device.

Simultaneously, I need to read more about how to view and manipulate how linux sees, points, and interacts w/ HIDs, as I am woefully unfamiliar.

I'll report what I find on the touch pad and situation. Hopefully, one of you or myself may stumble upon a solution that furthers our knowledge.