Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX on the Laptop

Help for Current Versions of MX
Message
Author
User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1491
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX on the Laptop

#21 Post by fehlix » Mon Jul 09, 2018 10:39 am

MarkG wrote:
Mon Jul 09, 2018 10:22 am
...Why is it SO HARD for DEVELOPERS to produce installers that do not break the distro?????
Well, as experienced linux user you know the answer to your question yourself. You just can break it.
For new user we have a manual to mitigate such experiences.

But back to the topic. Have you tried running from a freshly made LivebUSB or Snappshot
to install and run your extra apps to see how you system behaves.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 3257
Joined: Sun May 27, 2007 5:37 am

Re: MX on the Laptop

#22 Post by asqwerth » Mon Jul 09, 2018 12:16 pm

How did you install WIne? If via terminal, what commands did you use?

And I still think that 3rd party repo you connected to for the samsung drivers still bears some investigating since it's not affiliated with Samsung. Did it pull down other packages when you installed the printer driver, or since, when updating your system?
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Gaer Boy
Forum Guide
Forum Guide
Posts: 2125
Joined: Sat Jun 06, 2009 6:06 am

Re: MX on the Laptop

#23 Post by Gaer Boy » Mon Jul 09, 2018 12:20 pm

asqwerth wrote:
Mon Jul 09, 2018 12:16 pm
And I still think that 3rd party repo you connected to for the samsung drivers still bears some investigating since it's not affiliated with Samsung. Did it pull down other packages when you installed the printer driver, or since, when updating your system?
To answer this question specifically, I've been using the bchemnet.com/suldr repo since I tried MX. My printer/scanner worked fine on Mepis, but the scanner wouldn't work in MX. Others also endorse this repo - see https://forum.mxlinux.org/viewtopic.php ... 05#p378751
Phil

AsRock FM2A88X-ITX+, A8-6500, 8GB, 120GB Samsung SSD (GPT), 1TB HDD (MBR), MX-17.1
Lenovo Thinkpad X220, dual-core i5, 3MB, 320GB Hitachi HDD, Win7, MX-17.1

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1491
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX on the Laptop

#24 Post by fehlix » Mon Jul 09, 2018 12:33 pm

asqwerth wrote:
Mon Jul 09, 2018 12:16 pm
How did you install WIne? If via terminal, what commands did you use?
Thats' actual a good question. I might point the OP to chapter 6.1 of the user manual. And if the OP has done it differently or does not need our recommendations we gave within user manual, we shall consider this when replying to OP's complains.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1491
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX on the Laptop

#25 Post by fehlix » Mon Jul 09, 2018 12:45 pm

Gaer Boy wrote:
Mon Jul 09, 2018 12:20 pm
... I've been using the bchemnet.com/suldr repo since I tried MX. My printer/scanner worked fine on Mepis, but the scanner wouldn't work in MX. Others also endorse this repo - see https://forum.mxlinux.org/viewtopic.php ... 05#p378751
Phil
We do have fairly recent hplip in the testrepo. Would rather recommend to use this only instead of a untrusted 3rd party repo.
If a scanner would not work we shall better request a package update request if needed to get this sorted.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Gaer Boy
Forum Guide
Forum Guide
Posts: 2125
Joined: Sat Jun 06, 2009 6:06 am

Re: MX on the Laptop

#26 Post by Gaer Boy » Mon Jul 09, 2018 12:51 pm

fehlix wrote:
Mon Jul 09, 2018 12:45 pm
Gaer Boy wrote:
Mon Jul 09, 2018 12:20 pm
... I've been using the bchemnet.com/suldr repo since I tried MX. My printer/scanner worked fine on Mepis, but the scanner wouldn't work in MX. Others also endorse this repo - see https://forum.mxlinux.org/viewtopic.php ... 05#p378751
Phil
We do have fairly recent hplip in the testrepo. Would rather recommend to use this only instead of a untrusted 3rd party repo.
If a scanner would not work we shall better request a package update request if needed to get this sorted.
Thanks, fehlix. hplip contains nothing for Samsung scanners and drivers from Samsung often fail to work.

AsRock FM2A88X-ITX+, A8-6500, 8GB, 120GB Samsung SSD (GPT), 1TB HDD (MBR), MX-17.1
Lenovo Thinkpad X220, dual-core i5, 3MB, 320GB Hitachi HDD, Win7, MX-17.1

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 3257
Joined: Sun May 27, 2007 5:37 am

Re: MX on the Laptop

#27 Post by asqwerth » Mon Jul 09, 2018 12:59 pm

I wonder if it's similar to the problem for Brother scanner drivers here:

https://mxlinux.org/wiki/hardware/scanners


From midway through MX15/16's life onwards, I had to manually create symlinks for my Brother scanner driver to work, regardless of distro used.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1491
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX on the Laptop

#28 Post by fehlix » Mon Jul 09, 2018 4:19 pm

Gaer Boy wrote:
Mon Jul 09, 2018 12:51 pm
hplip contains nothing for Samsung scanners...
oops, indeed :alien:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1491
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX on the Laptop

#29 Post by fehlix » Mon Jul 09, 2018 4:23 pm

asqwerth wrote:
Mon Jul 09, 2018 12:59 pm
I wonder if it's similar to the problem for Brother scanner drivers here
They seem to have fixed this within their recent drivers. I did not need to manually symlinking since MX 17 and freshly installed drives
for older any newer brothers.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

MarkG
Forum Novice
Forum  Novice
Posts: 40
Joined: Sun May 06, 2018 3:54 pm

Re: MX on the Laptop

#30 Post by MarkG » Sun Jul 22, 2018 5:58 am

asqwerth wrote:
Wed Jul 04, 2018 7:46 am
MarkG wrote:
Tue Jul 03, 2018 8:27 pm
I am curious as to why suddenly all audio ceased working after an update, several other programs ceased working, including WINE and despite removing it, installing it, and same for other programs that have ceased working, I am still at a loss as to why a perfectly working system could be so easily crippled after an update that was in the name of security as stated in the downloads updater widget that you have in the launch bar.

Last update saw Slic3r stop working, despite reinstalling it, it won't run. Cura is a bit on and off and Repetier Host was also acting up and KediKAD....

All these programs functioned fine prior to the updates that followed the update the crippled the laptop....

There does not appear to be any rollback feature to undo an update.

I read a thread t hat talks about rolling back A driver, but nothing I can see about rolling back updates from MX updates. What I want to do is rollback to the point the machine was in before the whole install went sideways.
A google search on Slic3r also turns up its github page:

https://github.com/slic3r/Slic3r/wiki/R ... -GNU-Linux

The page indicates that the latest version of Debian that the program was compatible with was Debian 8 (Jessie). MX17 is based on Debian 9 (Stretch) so your compiled Slic3r was very likely not fully compatible with MX17 right from the start. It was probably living on borrowed time trying to run on a Debian 9 system and now the latest round of updates have stopped it running.

But that's my very non-tech view though!
Slic3r is working.

The link to it stopped working after the update, I discovered the executable folder and that the link had been obliterated. I reinstated the link and works just fine.

Post Reply

Return to “MX Help”