Welcome!
Important information
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.1 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4 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-18 Users Manual: Review (S2)

Topics relating to MX Docs and MX Videos
User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 24091
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-18 Users Manual: Review (S2)

#11

Post by Jerry3904 » Mon Jan 14, 2019 2:29 pm

Thanks.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4763
Joined: Wed Jul 12, 2006 4:05 pm

Re: MX-18 Users Manual: Review (S2)

#12

Post by timkb4cq » Mon Jan 14, 2019 5:39 pm

mxum wrote:2.4.2 The standard opening screen
When the LiveMedium boots up, you will be presented with a screen similar to the Figure above; the installed screen looks quite different. (The 386 ISO offers both the pae and non-pae versions.) Custom entries may also appear in the main menu. Detailed Help on this screen can be found in this document.
mxum wrote:MX-18 (<RELEASE DATE>)
This entry is selected by default, and is the standard way that most users will boot the Live system. Simply press Return to boot the system. On the 386 ISO two entries will appear, one for PAE (default) and the other for non-PAE.
Boot from Hard Disk
Allows for user to select a stored ISO to boot.
Memory Test
Runs a test to check RAM. If this test passes then there may still be a hardware problem or even a problem with RAM but if the test fails then you know something is wrong.
Just created & booted a 32bit MX-18 usb drive to check. There is only one entry to boot into MX on the grub screen, and examining the flash drive, only one vmlinuz file. It appears that a non-pae kernel is not provided on the 32 bit iso.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 24091
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-18 Users Manual: Review (S2)

#13

Post by Jerry3904 » Wed Jan 23, 2019 4:41 pm

Thanks to people for the feedback. Things will be a bit quieter for a bit, so I hope to get these first two up by the end of the week.

Will close this now, and open the challenging S3 thread.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 24091
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-18 Users Manual: Review (S2)

#14

Post by Jerry3904 » Wed Jan 30, 2019 11:09 am

asqwerth wrote:
Mon Jan 14, 2019 12:26 pm
Section 2.2.1
- page 4: this ties in with the comments in the other thread about which download link should be found on the Home page. I think it only makes sense that the home page should contain the first link set out in sentence 1.

Section 2.2.3, "USB" section:
- I feel a warning about using dd from command line should be added. Suggest adding this right at the end:
"WARNING: be careful to identify your destination USB correctly in the dd command line string listed above, as the dd command will completely write over the destination device or medium named! You do not want to accidentally write over your data backup drive, for example.

To ascertain the correct device name/letter for your destination USB, type:

Code: Select all

lsblk
in the terminal and press ENTER.
A list of all devices connected to your system will be listed. You should be able to identify your destination USB by its listed storage size."
Then in the 4th bullet point above the warning, suggest the following consequential changes in red:
"If the graphic USB creators fail, use one of the command line options below (now in Live-usb maker). Let us assume your USB is identified as sde (the naming format is sdX, where X is a letter of the alphabet like a, b, c, d, e, and so on), then copy and paste this line......"
Thanks, that's good. That is really too much detail for the Users Manual, so I moved the whole topic to the Wiki and just link to it.

For all reviewers: the overriding concept is for a hierarchy of detail:
--Users Manual: broad scope, restricted detail
--Wiki: detailed treatment of general topics
--Forum: specific discussions in detail.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 24091
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-18 Users Manual: Review (S2)

#15

Post by Jerry3904 » Fri Feb 01, 2019 4:17 pm

I have finished revisions (including replacing a number of images) and uploaded just now to my GitHub repo. For translators: ready for your work.

I will be turning now to S3 and, when it is done, will make a pull request to DO so we can get a good revision of the most important parts into users' hands.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

User avatar
cyrilus31
Forum Regular
Forum Regular
Posts: 705
Joined: Thu Nov 03, 2016 3:24 pm

Re: MX-18 Users Manual: Review (S2)

#16

Post by cyrilus31 » Mon Feb 11, 2019 5:15 pm

Small typo :
section 2.2.3 USB
MX Linux includes the tools Live usb maker
section 2.3.3 Do I need
For less then
Last edited by cyrilus31 on Mon Feb 11, 2019 5:45 pm, edited 1 time in total.

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 24091
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-18 Users Manual: Review (S2)

#17

Post by Jerry3904 » Mon Feb 11, 2019 5:19 pm

It is small, but welcome.

Je te remercie.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

User avatar
cyrilus31
Forum Regular
Forum Regular
Posts: 705
Joined: Thu Nov 03, 2016 3:24 pm

Re: MX-18 Users Manual: Review (S2)

#18

Post by cyrilus31 » Mon Feb 11, 2019 5:58 pm

Jerry3904 wrote:
Mon Feb 11, 2019 5:19 pm
It is small, but welcome.

Je te remercie.
Yes I know they are very small contributions, but as I'm making progress in the translation task I may find one or two
I'm sure you have better things to do other than correcting them ;)

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 24091
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-18 Users Manual: Review (S2)

#19

Post by Jerry3904 » Mon Feb 11, 2019 6:55 pm

No no: it takes me no more than 10 seconds to make the change in my local repo, then I only upload to my GitHub repo when I have a new Section ready.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

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

Re: MX-18 Users Manual: Review (S2)

#20

Post by asqwerth » Tue Feb 12, 2019 3:54 am

Jerry3904 wrote:
Wed Jan 30, 2019 11:09 am
asqwerth wrote:
Mon Jan 14, 2019 12:26 pm

...Section 2.2.3, "USB" section:
- I feel a warning about using dd from command line should be added. Suggest adding this right at the end:
"WARNING: be careful to identify your destination USB correctly in the dd command line string listed above, as the dd command will completely write over the destination device or medium named! You do not want to accidentally write over your data backup drive, for example.

To ascertain the correct device name/letter for your destination USB, type:

Code: Select all

lsblk
in the terminal and press ENTER.
A list of all devices connected to your system will be listed. You should be able to identify your destination USB by its listed storage size."
.....
Thanks, that's good. That is really too much detail for the Users Manual, so I moved the whole topic to the Wiki and just link to it. ....

Perhaps the lsblk command and warning should still be in the main Manual rather than Wiki, since the consequences of writing to the wrong device can be very serious. A forum member recently almost had this happen to him.

viewtopic.php?p=483873#p483873
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

Post Reply

Return to “Documentation and videos”