MX Linux Forum

• New sections on some MX Tools, Static DNS, few others
• Many new and revised images
• Bunch of corrections
• PDF link below Titles

New machine translations for the languages that we know are being worked on, that is : French, German, Greek, Italian and Spanish will be available from links in this thread ASAP.

Jerry3904 wrote:The new version is up--remember to refresh your page to see it.
....

Written by a programmer named “h2”

less /usr/sbin/smxi

#### Copyright (C) Harald Hope, sidux team members 2007-2010

Whenever possible, a migration path is provided with distribution upgrades (i.e., apt-get dist-upgrade) so that users can avoid reinstallation

apt-get dist-upgrade Intelligently handles changing dependencies with new versions of packages

aus9 wrote:and then add a note outside the box
apt-get upgrade is the command to run for those who prefer CLI to upgrade their packages if they are on the most recent MX verssion

skidoo wrote:user manual shipped within the MX15 iso, at section 3.2, shows correct screenshot
but the online html and pdf show an outdated screenshot for MX Tools.

Gordon Cooper wrote:

skidoo wrote:user manual shipped within the MX15 iso, at section 3.2, shows correct screenshot
but the online html and pdf show an outdated screenshot for MX Tools.

Have now checked this. Figure 3.3, the MX Tools Dashboard was updated (along with several other other images) at the end of June. The files available from the Manuals Tab here on the forum are correct.

Spartak77 wrote:Ok, TeamViewer is a good freeware software. It has a Linux version but it is not an open-source application.
Why don't you add also an open-source software example? For example Jitsi.
Jitsi features: voip,chat, sharing and remote desktop, file transfare, video meeting,possibility of traffic encryption.

Still seeing old screencap

skidoo wrote:{blush} facepalm.
Sorry, for the bad report.
I was seeing that because it was a freshly-made pendrive and I had not yet updated the mx-docs package, mx-tools package, etc.
Now I understand that the "white background with gray frame" is the GUI for the __newer__ version.

Spartak77 wrote:Ok Jerry, I was going to correct my post adding this:“But I want to underline that the manual is a great work, done very well, and it is obvious that something needs to be perfected gradually”
However I think I can say that I haven't forget to inform of things to tweak, and about a month ago I sent Gordon a file with several suggestions on how to further clarify some points
Perhaps it can be misunderstood, but I send the reports not to criticize but in the spirit of improving toghether this great work, but this does not mean that I would not serve 3 hands to press all those keys

Jerry3904 wrote:I would really appreciate it if one of you would post a complete improved description of the REISUB procedure sometime during the next week.

often only the first 2 letters are sufficient. Example, Ctrl-Alt-SysRq + R, then E, then try what you were attempting to do before the failure, if the system is still unresponsive, continue with the I, try again and if you still have no joy, you may as well finish the sequence and the machine will usually reboot.

On laptops that use Fn key to differentiate SysRq from PrtScrn, it may not actually be necessary to use the Fn key (i.e., Alt-PrtSc+letter could work).
You may need to press Ctrl along with Alt. So for example, full key shortcut would be Ctrl-Alt-SysRq+R.

Internet connections are handled by Network Manager; click the applet in the Notification Area to see status, connect and explore options.
Right-click the applet > Edit Connections to open up a Settings box with five tabs.

Code: Select all

2 The found network does not function after the completion of Step 1. 
Find out basic information by opening a terminal and entering one at a time:
 lspci 
 lsusb 
Become root in that open terminal and enter:
 iwconfig -a 
The output from the first commands (example below) will give you the exact name, model and version (if any) of your wireless chipset, as well as the associated driver and the mac address; from the second, the name of the access point (AP) you are linked to and other connection information. 
 Network
 Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi 
 IF: wlan0 state: up mac: 00:21:6a:81:8c:5a 
Use the information you have gathered in one of the following ways:
Do a web search using that information. Some examples using the above lspci output.
1) linux Intel Ultimate N WiFi Link 5300 (rev 03)
2) debian stable 00:21:6a:81:8c:5a 
Consult the Linux Wireless site below to find out which driver your chipset needs, what conflicts might exist, and whether it needs firmware installed separately. 
Post your information on the Forum and ask for help.

iwconfig -a

iwconfig

The output from the first commands (example below) will give you the exact name, model and version (if any) of your wireless chipset, as well as the associated driver and the mac address; from the second, the name of the access point (AP) you are linked to and other connection information.
 Network
 Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi
 IF: wlan0 state: up mac: 00:21:6a:81:8c:5a

inxi -n

the first commands (example below) will give you the exact name, model and version (if any) of your wireless chipset

Do a web search using that information. Some examples using the above lspci output.
 2) debian stable 00:21:6a:81:8c:5a

aus9 wrote: its smarter to setup your bios to power off after long pressing the power button for 4 seconds

IMHO its smarter to setup your bios to power off after long pressing

skidoo wrote:aus9, dintya notice ~~ doG kills a kitten every time you do that !

Spartak77 wrote: One less empirical way is to use Diagnostic Section in MX Broadcom Manager with which you can do the operation of ping to your router using the mac address obtained by the above commands.