MX Linux Forum

All I can say is wow and OMG.

New system

MSI Z68A-GD55 G3 MB

i3 ivy 3.4 Ghz

16 gigs of kingston Hyper X Genisis ( I love virtual box)

SeaSonic PS G series (G450)

ocZ ssd Agility 2 ( not sure if it will stay)

New system so nothing else was installed as of yet

Loaded from a unetbootin flash stick (Sandisk 8G Cruzer Blade) after deleting any ans all sandisk stuff

To get to the demo desktop took 17 mins, what a wait!

When I clicked install it took a little over 3 HOURS to install. What the

EDIT: I was installing M12 11.9.92 (64) Does anyone use 32 bit on new equipment?

After it finished it's install I shut down , removed the stick and rebooted.

First boot on a clean new system with the uefi took about 10 mins.

Sut down after the succesful boot and restarted.

YESSSSSSS everything settled down and now it takes about 12 SECONDS yes seconds to go from power switch to auto log in desktop :)

Every thing works well so far except my Logitech K400r wireless keyboard with touch pad.
Sometimes keystrokes drop out and the touch pad is jerky and slow enough to be a hinderance. Yes sadly it functions perfectly with that other op system and at three times the distance (18 feet) that i have been trying to get it to work with Mepis.

EDIT: it was a timing issue, the boot time out raced the dongle being ready for the driver, works excellent when you restart the driver so it's time to make a script to remove and restart the driver a bit later. (Thanks to timkb4cq) He serarched faster than me lol

All in all this is an excellent release so far and it's time to add in a Hauppauge 2250 dual tuner card.
2 1T 2.5 10,000 rpm drives stripped raid
Slim laptop blue ray drive (Fractal node 605 case)
internal usb hub to hide the blue tooth dongle, logitech unifying dongle and one maybe two flash sticks

After the disapointing load time and install time it has turned out to be excellent and worth the agony of waiting.

I've seen some threads about problems with that keyboard & debian. In a terminal, try It seems to be a timing problem where the driver tried to initialize the receiver before it's ready. If the above commands fix the issue you can put them in a script with an appropriate sleep command between to let the receiver settle.

That makes sense with the ssd and such a fast boot time. It's a race and the wireless dongle loses.

I think I will do the same for the blue tooth dongle.

I've been searching for the answer Thank you.

Edit: Yep that works, it was a losing race and it even happened with the blue tooth.

[quote="GDixon"]All I can say is wow and OMG.


Loaded from a unetbootin flash stick (Sandisk 8G Cruzer Blade) after deleting any ans all sandisk stuff

To get to the demo desktop took 17 mins, what a wait!

When I clicked install it took a little over 3 HOURS to install. What the

EDIT: I was installing M12 11.9.92 (64) Does anyone use 32 bit on new equipment?

After it finished it's install I shut down , removed the stick and rebooted.

First boot on a clean new system with the uefi took about 10 mins.

Those stats should be world records. I have never seen times like those in all the years of using Linux. Even when using my old clunky DVD player I can be booted up & installed within 30 mins.

timkb4cq wrote:I've seen some threads about problems with that keyboard & debian. In a terminal, try

Code: Select all

su
rmmod hid-logitech-dj
modprobe hid-logitech-dj

It seems to be a timing problem where the driver tried to initialize the receiver before it's ready. If the above commands fix the issue you can put them in a script with an appropriate sleep command between to let the receiver settle.

Just saw this and it may or may not have any bearing on what I'm dealing with.

Acer Aspire M5-581T-6807. This was purchased new by my niece last fall. I got it three or four months ago with a totally corrupted load of W8. Could not launch any of the recovery tools from within the OS or through the bios. Of course, no recovery media was made when she boughtt it. After she did absolutely nothing about either buying the recovery media or buying a load of W7, I decided to take matters into my own hands. I took it down to bare metal and loaded Wheezy KDE.

This machine has a 500G sata drive as HD0, and a 20G SSD as HD1. The SSD held two partitions, neither of which I could access, but I assume it held either the "Instant On" stuff this came with or maybe one of the recovery tools that didn't work. Both drives got blown away, and I loaded the root on HD1 and home on HD0. Boots lightening fast, and programs open in the blink of an eye.

The trackpad doesn't work worth a darn. It's all hurky jerky, and the weirdest thing is you can't resize windows. If you grab an edge or a corner with the left mouse button and then try to drag it, nothing happens -- the pointer doesn't move and the edge or corner stays put. It works perfectly fine with a plugged in USB mouse. I've got kde-config-touchpad installed, and nothing in there helps or even makes a difference.

Any chance this could be related to the situated reported upthread? Like the thing loading the desktop before the necessary trackpad modules are ready? Or something? Do I sound desperate?

A little research indicates that Laptop has an Elantech touchpad. This page at Arch Linux may have the answer - it's being detected as a ps/2 mouse instead of a touchpad...

timkb4cq wrote:A little research indicates that Laptop has an Elantech touchpad. This page at Arch Linux may have the answer - it's being detected as a ps/2 mouse instead of a touchpad...

Okay, that says I need the psmouse-elantech package, which is a tar.gz. I've downloaded and extracted it, but have no idea what to do with it.

uncle mark wrote:

timkb4cq wrote:A little research indicates that Laptop has an Elantech touchpad. This page at Arch Linux may have the answer - it's being detected as a ps/2 mouse instead of a touchpad...

Okay, that says I need the psmouse-elantech package, which is a tar.gz. I've downloaded and extracted it, but have no idea what to do with it.

I have a simialr situation with my Acer V5-572G, except the touchpad does not work at all.

It's a patch to the psmouse module that is installed using dkms. See here:
http://redoem.com/2011/07/04/enable-ful ... in-ubuntu/

However this may not work. The original elantech issue I found was reported to be fixed in the 3.0.2 kernel - although it appears to have been broken again by the time the 3.8 kernel came out.

I've found a newer thread on this. Fixes for some elantech touchpad issues have been accepted into the mainline 3.11 kernel. Ubuntu kernels (and headers) with the relevant patches have been built for Precise (3.2), Quantal (3.5) , Raring (3. & Saucy (3.10). Could be worth a try.
https://bugs.launchpad.net/ubuntu/+sour ... mments/100