MX Linux Forum

Posted: **Sun Dec 10, 2017 7:57 am**

If posting hardware issues, please post the output of the terminal command "inxi -F" at a minimum.

If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.

If posting remaster issues, please include the contents of /var/log/live/live-remaster.log

If posting issues with MX-PackeageInstaller "Popular Apps", please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).

Posted: **Sun Dec 10, 2017 9:23 am**

RC1 looks really good running from USB drive. Will this release update to final when the time comes or will a fresh install be required?

Posted: **Sun Dec 10, 2017 9:24 am**

After using Conky Manager to preveny Conky from starting, a menu item is still present in 'Favourites' to toggle Conky on/off, but does nothing.

I think this is going to cause confusion!

Chris

Posted: **Sun Dec 10, 2017 9:31 am**

Will this release update to final when the time comes or will a fresh install be required?

If this is not a FAQ I don't know what is... we should probably post the response in the announcement too.

RCs will update to Final (at least that what we did in the past).

Posted: **Sun Dec 10, 2017 9:36 am**

If this will be updated I will install it asap, a lot of potential users will dither [like me] if its not prominent.

I have to say that after trying literally dozens of distros MX-16 was the best I had tried, along with Solus, but MX-16 had it by a nose. As a mainly Windows user MX and Solus are the easiest for those moving across, as it happens I once had a dual install of XP and Mepis so this was the first place I looked for a new OS, after all these years its still the best for me.

Thanks for the prompt response.

Posted: **Sun Dec 10, 2017 9:48 am**

chrispop99 wrote:After using Conky Manager to preveny Conky from starting, a menu item is still present in 'Favourites' to toggle Conky on/off, but does nothing.

I think this is going to cause confusion!

Chris

I don't see it as a serious confusion issue, myself. But we could add the word "selected" to the comment so it read.

Posted: **Sun Dec 10, 2017 10:03 am**

I never thought I'd feel this way, but I'm hoping a MX-17 final release is not too soon. It'll take me 10+ hours to download RC1 on dial-up & I was having video related crashes with beta 3. So now I'm hoping I'll have enough time to post data on the crashes if they continue in RC1 --- and somebody will have time to resolve them before final.

Posted: **Sun Dec 10, 2017 10:11 am**

Welcome to the Forum! Can you post the output of this from your current beta 3

Code: Select all

inxi -G

Posted: **Sun Dec 10, 2017 10:15 am**

Don't know what happened, but this is the glichiest i've tested so far.
This time, just as last, installed everything on btrfs (on SSD) and everything was fine then.
Not so this time.
Everything was going bananas (too much to point out).
Have disabled compton and done upgrade, quite a few reboots.
Things seem to be a bit more stable now (takes a deep breath).

Update: have re-installed as ext4 and so far so good! :)

Posted: **Sun Dec 10, 2017 10:19 am**

Running Live on my production system in sig, Power Manager is that yellow icon.

Posted: **Sun Dec 10, 2017 11:08 am**

felicity wrote:I never thought I'd feel this way, but I'm hoping a MX-17 final release is not too soon. It'll take me 10+ hours to download RC1 on dial-up & I was having video related crashes with beta 3. So now I'm hoping I'll have enough time to post data on the crashes if they continue in RC1 --- and somebody will have time to resolve them before final. :snail:

Since you already have beta3 you can considerably reduce the amount you need to download if you download the b3_RC1 xdelta file or the zsync file. (or maybe that is what you were planning to do -- back when I had dialup it took a couple days to download 600 to 700 MB size isos)

Posted: **Sun Dec 10, 2017 11:16 am**

Jerry3904 wrote:Running Live on my production system in sig, Power Manager is that yellow icon.

I see the same icon when I run the ISO in KVM, but on my laptop it doesn't show up (I created the USB with live-usb-maker if that makes a difference). So there's some variation somewhere.

Just tested, I don't see the icon in VirtualBox either.

Posted: **Sun Dec 10, 2017 11:36 am**

Does it only appear on a non-laptop?

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

Posted: **Sun Dec 10, 2017 11:45 am**

asqwerth wrote:Does it only appear on a non-laptop?

I guess so, I see it in KVN/Qemu and on a test desktop, not on the laptop or VirtualBox.

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

It's a bit out of place next to the other gray icons in system tray, it's also good to have some consistency between laptops/desktops.

Posted: **Sun Dec 10, 2017 11:57 am**

Jerry3904 wrote:Welcome to the Forum! Can you post the output of this from your current beta 3
Code: Select all
inxi -G

Thanks Jerry3904.

Code: Select all

$ inxi -G
Graphics:  Card: Intel 82915G/GV/910GL Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel 915G x86/MMX/SSE2 version: 2.1 Mesa 13.0.6

Let me add that I fiddled with the graphics-related boot parameters. Here's the relevant part of the Grub Customizer Entry Editor window:

Code: Select all

echo  'Loading Linux 4.13.0-1-686-pae ...'
linux /boot/vmlinuz-4.13.0-1-686-pae root=UUID=087920e3-6bb0-4eab-bb4a-345e13e0d895 ro  vga=795 gfxsave video=1280x1024 failsafe

I did that because the MX-17 & antiX-17 standard kernels tend to boot into 1024x768 display resolution. And what's worse, they end up in some state that prevents me from changing the display resolution at all from this most unacceptable 1024x768. (I have no idea if these boot params are rational.)

But wait, there's more... Even though I can get the kernel into 1280x1024 resolution, I then change its default version of this resolution (for reasons explained later). The kernel likes to boot into video mode "1280x1024 (0x45) 108.879MHz" as below. But I force it into mode " 1280x1024 (0x9e) 108.000MHz" with a start-up script.

Code: Select all

$ sudo xrandr -q --verbose
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (0x9d) normal (normal left inverted right x axis y axis) 0mm x 0mm
...
  1280x1024 (0x9e) 108.000MHz +HSync +VSync +preferred
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1280x1024 (0x45) 108.879MHz -HSync +VSync
        h: width  1280 start 1360 end 1496 total 1712 skew    0 clock  63.60KHz
        v: height 1024 start 1025 end 1028 total 1060           clock  60.00Hz

I do this because I dual boot with XP (whose security vulnerabilities forced me into Linux) and XP chooses (I believe) this mode. Also, this mode (" 1280x1024 (0x9e) 108.000MHz") is the only one that my monitor's manual says it will accept (it's the standard VESA mode) at this resolution. This Acer AL1715 LCD monitor has a cranky module (the DAC?) and often refuses to do it's self-adjust thing successfully (especially when cold), so I want to stick with this one resolution.

Posted: **Sun Dec 10, 2017 11:58 am**

asqwerth wrote:Does it only appear on a non-laptop?

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

Yes, only on desktop machines.

It was reported during beta.

Chris

Posted: **Sun Dec 10, 2017 12:03 pm**

kmathern wrote:
felicity wrote:I never thought I'd feel this way, but I'm hoping a MX-17 final release is not too soon. It'll take me 10+ hours to download RC1 on dial-up & I was having video related crashes with beta 3. So now I'm hoping I'll have enough time to post data on the crashes if they continue in RC1 --- and somebody will have time to resolve them before final.
Since you already have beta3 you can considerably reduce the amount you need to download if you download the b3_RC1 xdelta file or the zsync file. (or maybe that is what you were planning to do -- back when I had dialup it took a couple days to download 600 to 700 MB size isos)

Yup, I sure did have to figure out that xdelta trick! (412 MiB/24 hrs @ 40 Kbps. But the darn (few remaining) ISP that support dial-up have taken to limiting us to only 10 hrs/day.

Posted: **Sun Dec 10, 2017 12:19 pm**

Try zsync it can use the older file as base and download only the changes, for example to download the 64bit one:

Code: Select all

zsync -i INPUTFILE http://iso.mxrepo.com/Testing/MX-17/MX-17.RC1_x64.iso.zsync

where INPUTFILE can be the last Beta you have, if you have beta3 you can do:

Code: Select all

zsync -i MX-17.b3_x64.iso http://iso.mxrepo.com/Testing/MX-17/MX-17.RC1_x64.iso.zsync

You need to run this command in the folder where you have that ISO (or use the full path of the ISO).

Posted: **Sun Dec 10, 2017 12:23 pm**

chrispop99 wrote:
asqwerth wrote:Does it only appear on a non-laptop?

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.
Yes, only on desktop machines.

It was reported during beta.

Chris

its the default icon for power-manager (also appears inside the settings) via the chosen theme. it only appears if there is no battery.

Posted: **Sun Dec 10, 2017 1:08 pm**

I remember that it was reported, didn't remember if it had been fixed.

I can turn off the switch that has it appear in NA from the settings, General tab: Appearance. Maybe we could consider doing that with a small script when not a laptop...?

Posted: **Sun Dec 10, 2017 1:12 pm**

chrispop99 wrote:After using Conky Manager to preveny Conky from starting, a menu item is still present in 'Favourites' to toggle Conky on/off, but does nothing.

I think this is going to cause confusion!

Chris

would it make more sense in that instance to launch conky-manager instead?

Posted: **Sun Dec 10, 2017 1:14 pm**

Good call.

Chris

Posted: **Sun Dec 10, 2017 1:47 pm**

Adrian wrote:Try zsync it can use the older file as base and download only the changes, for example to download the 64bit one:
Code: Select all
zsync -i INPUTFILE http://iso.mxrepo.com/Testing/MX-17/MX-17.RC1_x64.iso.zsync
where INPUTFILE can be the last Beta you have, if you have beta3 you can do:
Code: Select all
zsync -i MX-17.b3_x64.iso http://iso.mxrepo.com/Testing/MX-17/MX-17.RC1_x64.iso.zsync
You need to run this command in the folder where you have that ISO (or use the full path of the ISO).

Thanks for the example and suggestion. But can I interrupt zsync with CTRL-C (a virtual necessity on dial-up) and continue it later from where I stopped like I can do with wget? And does it give a nice running statistics like wget does?

Posted: **Sun Dec 10, 2017 1:57 pm**

I haven't needed to test this, but according to a DreamLinux thread: "If zsync is stopped for any reason it can be restarted with the same command-line and will simply reuse any sections already downloaded and keep going until the ISO is complete and checks out with the md5sum."

Posted: **Sun Dec 10, 2017 1:58 pm**

chrispop99 wrote:Good call.

Chris

give this one a try.

Posted: **Sun Dec 10, 2017 2:08 pm**

felicity wrote:
Jerry3904 wrote:Welcome to the Forum! Can you post the output of this from your current beta 3
Code: Select all
inxi -G
Thanks Jerry3904.
Code: Select all
$ inxi -G
Graphics:  Card: Intel 82915G/GV/910GL Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel 915G x86/MMX/SSE2 version: 2.1 Mesa 13.0.6
Let me add that I fiddled with the graphics-related boot parameters. Here's the relevant part of the Grub Customizer Entry Editor window:
Code: Select all
echo  'Loading Linux 4.13.0-1-686-pae ...'
linux /boot/vmlinuz-4.13.0-1-686-pae root=UUID=087920e3-6bb0-4eab-bb4a-345e13e0d895 ro  vga=795 gfxsave video=1280x1024 failsafe
I did that because the MX-17 & antiX-17 standard kernels tend to boot into 1024x768 display resolution. And what's worse, they end up in some state that prevents me from changing the display resolution at all from this most unacceptable 1024x768. (I have no idea if these boot params are rational.)

But wait, there's more... Even though I can get the kernel into 1280x1024 resolution, I then change its default version of this resolution (for reasons explained later). The kernel likes to boot into video mode "1280x1024 (0x45) 108.879MHz" as below. But I force it into mode " 1280x1024 (0x9e) 108.000MHz" with a start-up script.
Code: Select all
$ sudo xrandr -q --verbose
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (0x9d) normal (normal left inverted right x axis y axis) 0mm x 0mm
...
  1280x1024 (0x9e) 108.000MHz +HSync +VSync +preferred
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1280x1024 (0x45) 108.879MHz -HSync +VSync
        h: width  1280 start 1360 end 1496 total 1712 skew    0 clock  63.60KHz
        v: height 1024 start 1025 end 1028 total 1060           clock  60.00Hz
I do this because I dual boot with XP (whose security vulnerabilities forced me into Linux) and XP chooses (I believe) this mode. Also, this mode (" 1280x1024 (0x9e) 108.000MHz") is the only one that my monitor's manual says it will accept (it's the standard VESA mode) at this resolution. This Acer AL1715 LCD monitor has a cranky module (the DAC?) and often refuses to do it's self-adjust thing successfully (especially when cold), so I want to stick with this one resolution.

Hello felicity the problem is not with MX Linux but the problem is on your side to me also it happened like that my PC used to boot with 1024x768 resolution to get rid of it i used a startup script it worked fine later i replaced my monitor VGA or Display cable other than power supply to the monitor after that my system deducted 1280x1024 and many resolutions i think try this out. By the way what do you see when you open display option could you see any resolutions ??

Thanks..

Posted: **Sun Dec 10, 2017 2:44 pm**

dolphin_oracle wrote:give this one a try.

Nice solution, works fine. No more confusion to be had.

Posted: **Sun Dec 10, 2017 3:03 pm**

Mepis has been mentioned and the time it takes to download MX over dial up.
For most of the time that I used Mepis I was on dial up.
I always found it much easier to buy Linux Cd's online when I was on dial up.
I would use Mepis until the next version came out on CD then order the next one.
Those of you who download Linux on dial up are blessed with more patience than I have.
I recommend you go somewhere where you can use a faster connection to do that.
The MX DVDs as well as USB drives will be for sale online after release. They always are.
This release looks like the best one yet.
I really appreciate all of the hard work you guys and gals have done.
I will be making donations before the end of the month to support both Antix and MX.
I hope others will do the same. Remember this is not a commercial venture.
Great Job!

Posted: **Sun Dec 10, 2017 3:39 pm**

duane wrote:Mepis has been mentioned and the time it takes to download MX over dial up.
For most of the time that I used Mepis I was on dial up.
I always found it much easier to buy Linux Cd's online when I was on dial up.
I would use Mepis until the next version came out on CD then order the next one.
Those of you who download Linux on dial up are blessed with more patience than I have.
I recommend you go somewhere where you can use a faster connection to do that.
The MX DVDs as well as USB drives will be for sale online after release. They always are.

This brought back memories. My first two Mepis CDs came from OSDisc.com, back in my dial-up days. SimplyMEPIS 3.4-2 RC1 and SimplyMEPIS 3.4-3 RC3. I still have the CDs! But would any MX RC releases be available at OSDisc.com? I don't see RC1 there yet, but maybe keep an eye out.

Posted: **Sun Dec 10, 2017 3:54 pm**

But would any MX RC releases be available at OSDisc.com?

They do Final releases only, sorry.

Posted: **Sun Dec 10, 2017 4:52 pm**

Jerry3904 wrote:
But would any MX RC releases be available at OSDisc.com?
They do Final releases only, sorry.

Oh, well. Again, the old Mepis disks I have sitting in front of me were RC disks from there -- obviously a thing of the distant past. I've wondered why they ever did that in the first place -- at the time, I didn't even know what "RC" meant. Is it looking like there will be more than one MX-17 Release Candidate, or is it still way too early to tell? Looking for a flash drive right now to clear up so I can test RC1 out.

Posted: **Sun Dec 10, 2017 5:09 pm**

I can't upgrade mpv. 0.26 is in stable repo. 0.27 is shown in test repo. Checking in and hitting update button would reinstall 0.26 version over itself.

Posted: **Sun Dec 10, 2017 5:28 pm**

If you install a higher version, it won't be overwritten unless there is some unusual problem.

Posted: **Sun Dec 10, 2017 5:28 pm**

Code: Select all

eadwine@eadwinemx17rc1:~
$ inxi -F
System:    Host: eadwinemx17rc1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop Mobo: ASUSTeK model: M4A785TD-V EVO v: Rev X.0x serial: N/A
           BIOS: American Megatrends v: 2005 date: 04/15/2010
CPU:       Quad core AMD Athlon II X4 635 (-MCP-) cache: 2048 KB
           clock speeds: max: 2900 MHz 1: 2200 MHz 2: 1700 MHz 3: 1700 MHz 4: 1700 MHz
Graphics:  Card: NVIDIA GK208 [GeForce GT 640 Rev. 2]
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GT 640/PCIe/SSE2 version: 4.5.0 NVIDIA 387.34
Audio:     Card-1 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel
           Card-3 Logitech QuickCam E 3500 driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 48:5b:39:f4:93:4e
           Card-2: Ralink MT7601U Wireless Adapter driver: mt7601u
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 1640.4GB (3.7% used)
           ID-1: /dev/sda model: WDC_WD5000AAKS size: 500.1GB
           ID-2: /dev/sdb model: Hitachi_HDT72106 size: 640.1GB
           ID-3: USB /dev/sdc model: HDP725050GLA360 size: 500.1GB
Partition: ID-1: / size: 48G used: 4.9G (11%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 384G used: 123M (1%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   System Temperatures: cpu: 37.0C mobo: 34.0C gpu: 37C
           Fan Speeds (in rpm): cpu: 2490 psu: 0 sys-1: 820
Info:      Processes: 211 Uptime: 10 min Memory: 860.7/7986.9MB Client: Shell (bash) inxi: 2.3.53

Hey all.. I am running into something. The ID-3: USB /dev/sdc (ntfs) drive's partitions always used to open when I clicked on it in thunar, now it requires a root password. Apparently ownership is set to root, and that ain't right. I couldn't find how to fix it in the manual, so... maybe one of you knows how to sort this so I don't have to enter the root password anymore?

Also.. this drive is always on and connected to the system. Used to appear in fstab. This is the currect fstab on mx17rc1. I will take a looksee on the MX16 install how this has been fiddled there.

Code: Select all

# /etc/fstab: static file system information
#
# Created by make-fstab on Sun Dec 10 23:03:03 CET 2017

# <file system>                            <mount point>                               <type>     <options>                       <dump/pass>

#-> /dev/sda1  label=rootMX17
UUID=4cb8c6e4-55d3-46c7-8283-2a30208a7beb  /                                           ext4       defaults                        1 1
#-> /dev/sda2  label=homeMX17
UUID=b115300c-9005-4829-b6c2-cff24cb448d9  /home                                       ext4       defaults                        1 2
#-> /dev/sda3  label=MXswap
UUID=92d96fbc-c28a-49b9-b27b-5e96f78d8a96  swap                                        swap       defaults                        0 0

Posted: **Sun Dec 10, 2017 5:35 pm**

Jerry3904 wrote:some unusual problem.

that's why I posted.

Posted: **Sun Dec 10, 2017 5:38 pm**

Another one is I have to be root to power off the system?

*scratches head*

Posted: **Sun Dec 10, 2017 5:40 pm**

From the command line?

Posted: **Sun Dec 10, 2017 5:45 pm**

Nope, from the menu, and then top right the log out button, and then shut down (IIRC).

I have found the fstab on my current installed MX16

Code: Select all

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

#Entry for /dev/sda1 :
UUID=77319b3b-77d5-4e99-9ebe-fdcc1c212d1d	/	auto	defaults,noatime	1	1
#Entry for /dev/sdb1 :
UUID=2EAD013249FC871A	/media/eadwine/Backups	ntfs	defaults,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177,uhelper=udisks2	0	0
#Entry for /dev/sdb3 :
UUID=2F5789B27BF514F2	/media/eadwine/Downloads	ntfs	defaults,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177,uhelper=udisks2	0	0
#Entry for /dev/sda2 :
UUID=78d2c83a-9b04-42a4-b162-7475c082e67a	/home	auto	defaults,noatime	1	2
#Entry for /dev/sda3 :
UUID=44c395fa-d328-45ae-a7c4-3a2a2714009e	swap	swap	defaults	0	0

Maybe that will give a clue.

Posted: **Sun Dec 10, 2017 5:48 pm**

Great release 17 rc1 i HAVE A DESKTOP THAT NOW WORKS THE FAILSAFE F6 OPTION ON BOOT OF DVD SOLVED THE BOOT ISSUE--My old computer likes all changes made to solve the 32 bit problemns.Thanks for all work done the new system is great and fast.I've also have a 64 bit system which also runs great John

Posted: **Sun Dec 10, 2017 5:51 pm**

Ok.. crooked volt.. I put the RC drive back in and now I can open the external drive partitions as user..

checking fstab, no changes there.

Now for the shutdown.....

and it shuts down as user.

Ok.. fixed.

Not a clue what happened there.

Posted: **Sun Dec 10, 2017 6:02 pm**

golden45 wrote:Great release 17 rc1 i HAVE A DESKTOP THAT NOW WORKS THE FAILSAFE F6 OPTION ON BOOT OF DVD SOLVED THE BOOT ISSUE--My old computer likes all changes made to solve the 32 bit problemns.Thanks for all work done the new system is great and fast.I've also have a 64 bit system which also runs great John

yay!

Posted: **Sun Dec 10, 2017 6:09 pm**

here is the system infoSystem: Host: mx1 Kernel: 4.13.0-1-686-pae i686 bits: 32 Desktop: Xfce 4.12.3
Distro: MX-17.RC1_386 Horizon December 10, 2017
Machine: Device: desktop Mobo: ASUSTeK model: P4SP-MX v: REV 1.xx serial: N/A
BIOS: Award v: ASUS P4SP-MX 1006 Beta 002 date: 04/14/2006
CPU: Single core Intel Pentium 4 (-MT-) cache: 1024 KB
clock speeds: max: 1994 MHz 1: 1994 MHz 2: 1994 MHz
Graphics: Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
Display Server: x11 (X.Org 1.19.2 ) drivers: vesa (unloaded: modesetting,fbdev)
Resolution: 1280x1024@0.00hz
OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.9, 128 bits) version: 3.3 Mesa 13.0.6
Audio: Card Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller
driver: snd_intel8x0
Sound: Advanced Linux Sound Architecture v: k4.13.0-1-686-pae
Network: Card: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet driver: sis900
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:11:2f:99:eb:dc
Drives: HDD Total Size: 30.8GB (18.6% used)
ID-1: /dev/sda model: Maxtor_6E030L0 size: 30.8GB
Partition: ID-1: / size: 28G used: 5.3G (20%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 0.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 168 Uptime: 40 min Memory: 691.8/1987.8MB Client: Shell (bash) inx

Posted: **Sun Dec 10, 2017 6:16 pm**

Please edit that post and use the code tags. Thanks.

Posted: **Sun Dec 10, 2017 6:19 pm**

Mind, just have to say that I really like how crisp and clean MX17 looks. Well done!!

Posted: **Sun Dec 10, 2017 8:03 pm**

vamsi wrote:
felicity wrote:
Jerry3904 wrote:Welcome to the Forum! Can you post the output of this from your current beta 3
Code: Select all
inxi -G
Thanks Jerry3904.
Code: Select all
$ inxi -G
Graphics:  Card: Intel 82915G/GV/910GL Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel 915G x86/MMX/SSE2 version: 2.1 Mesa 13.0.6
Let me add that I fiddled with the graphics-related boot parameters. Here's the relevant part of the Grub Customizer Entry Editor window:
Code: Select all
echo  'Loading Linux 4.13.0-1-686-pae ...'
linux /boot/vmlinuz-4.13.0-1-686-pae root=UUID=087920e3-6bb0-4eab-bb4a-345e13e0d895 ro  vga=795 gfxsave video=1280x1024 failsafe
I did that because the MX-17 & antiX-17 standard kernels tend to boot into 1024x768 display resolution. And what's worse, they end up in some state that prevents me from changing the display resolution at all from this most unacceptable 1024x768. (I have no idea if these boot params are rational.)

But wait, there's more... Even though I can get the kernel into 1280x1024 resolution, I then change its default version of this resolution (for reasons explained later). The kernel likes to boot into video mode "1280x1024 (0x45) 108.879MHz" as below. But I force it into mode " 1280x1024 (0x9e) 108.000MHz" with a start-up script.
Code: Select all
$ sudo xrandr -q --verbose
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (0x9d) normal (normal left inverted right x axis y axis) 0mm x 0mm
...
  1280x1024 (0x9e) 108.000MHz +HSync +VSync +preferred
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1280x1024 (0x45) 108.879MHz -HSync +VSync
        h: width  1280 start 1360 end 1496 total 1712 skew    0 clock  63.60KHz
        v: height 1024 start 1025 end 1028 total 1060           clock  60.00Hz
I do this because I dual boot with XP (whose security vulnerabilities forced me into Linux) and XP chooses (I believe) this mode. Also, this mode (" 1280x1024 (0x9e) 108.000MHz") is the only one that my monitor's manual says it will accept (it's the standard VESA mode) at this resolution. This Acer AL1715 LCD monitor has a cranky module (the DAC?) and often refuses to do it's self-adjust thing successfully (especially when cold), so I want to stick with this one resolution.
Hello felicity the problem is not with MX Linux but the problem is on your side to me also it happened like that my PC used to boot with 1024x768 resolution to get rid of it i used a startup script it worked fine later i replaced my monitor VGA or Display cable other than power supply to the monitor after that my system deducted 1280x1024 and many resolutions i think try this out. By the way what do you see when you open display option could you see any resolutions ??

Thanks..

Thanks for commenting, vamsi. It's been some time since I had an MX-17 or antiX-17 install frozen at 1024x768 resolution, but as I recall, I could see the other resolutions in Display Manager, but selecting them would be without effect. Likewise, issuing the appropriate sudo xrandr command was also ineffectual. (By "appropriate" I mean conforming to the monitor's specifications.) Also xrandr would report the monitor's name as "default" rather than the "VGA1" that it does when the OS is not frozen at 1024x768 res. Web searching, I did find a few other references to this problem with Ubuntu or Debian. But any solutions given did not seem simply or directly related to my system, involving as they did, re-installing or changing the config file parameters of software that was not part of my system.

Thanks, in particular, for your advice to replace the "monitor VGA or Display cable." That might work. But I know that this old Acer monitor has limited capability of communicating with the OS, that is, it has support for only the earlier, more primitive, version of the DDC protocol, the DDC2 one, not the more advanced DDC-CI protocol. See
Display Data Channel
https://en.wikipedia.org/wiki/Display_Data_Channel

So I suspect the current Linux kernels being used for MX-17 or antiX-17 have some trouble configuring themselves for this older hardware. And even if the VGA cable or monitor does not trip them up, possibly the on-board Intel chip display adapter may.

By the way, for the record, here is my complete inxi -F output (the first responder to my post, Jerry3904, only asked for the inxi -G one):

Code: Select all

$ inxi -F
System:    Host: mx17 Kernel: 4.13.0-1-686-pae i686 bits: 32 Desktop: Xfce 4.12.3
           Distro: MX-17.b3_386 Horizon November 28, 2017
Machine:   Device: desktop System: Dell product: OptiPlex GX280 serial: N/A
           Mobo: Dell model: 0H5354 serial: N/A BIOS: Dell v: A08 date: 03/03/2006
CPU:       Single core Intel Pentium 4 (-UP-) cache: 1024 KB speed: 2794 MHz (max)
Graphics:  Card: Intel 82915G/GV/910GL Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel 915G x86/MMX/SSE2 version: 2.1 Mesa 13.0.6
Audio:     Card Intel 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller
           driver: snd_intel8x0
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-686-pae
Network:   Card: Broadcom Limited NetXtreme BCM5751 Gigabit Ethernet PCIE driver: tg3
           IF: eth0 state: down mac: 00:0f:1f:da:c7:04
Drives:    HDD Total Size: 1000.2GB (20.4% used)
           ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
Partition: ID-1: / size: 77G used: 5.1G (8%) fs: ext4 dev: /dev/sda9
           ID-2: /home size: 23G used: 87M (1%) fs: ext4 dev: /dev/sda10
           ID-3: swap-1 size: 5.24GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 157 Uptime: 12 min Memory: 231.8/994.3MB Client: Shell (bash) inxi: 2.3.43

Going back to looking for a software, rather than a hardware solution, MX-16 & Windows XP never had this problem of display resolution being frozen at 1024x768. And antiX-17 also had it initially. But then I found a way to prevent it from being frozen at 1024x768 that has been stable with no video-related crashes occurring. That way was to install from an optical disk (CD or DVD) with the Virtual Machine mode boot parameter. (That is, for some reason, only an option from a disk but not a USB flash drive install.) Then there are a only a couple of complaints from the kernel during boot-up (without the quiet boot parameter). It says it's disabling some Virtual Machine features (presumably, the kernel can detect that it is not in a VM, but in physical hardware), but then antiX-17 has been stable and it does allow me to change video mode freely. (So actually I currently have a quadruple, not a dual boot system: Windows XP Professional, MX-16.1, MX-17 beta 3, antiX-17.)

Can anybody kindly tell me if the graphics-related boot parameters I have manually chosen for MX-15 beta 3 are rational, or suggest any better ones to prevent booting into 1024x768 display resolution and then being unable to change from it to my LCD monitor's highest possible one, 1024x1280? Again, here's the relevant part of the Grub Customizer Entry Editor window:

Code: Select all

echo  'Loading Linux 4.13.0-1-686-pae ...'
linux /boot/vmlinuz-4.13.0-1-686-pae root=UUID=087920e3-6bb0-4eab-bb4a-345e13e0d895 ro  vga=795 gfxsave video=1280x1024 failsafe

MX-15 beta 3 is currently unstable with these; it is having video-related crashes, although it is not frozen in 1024x768 display resolution.

Posted: **Sun Dec 10, 2017 8:19 pm**

felicity wrote:I never thought I'd feel this way, but I'm hoping a MX-17 final release is not too soon. It'll take me 10+ hours to download RC1 on dial-up & I was having video related crashes with beta 3. So now I'm hoping I'll have enough time to post data on the crashes if they continue in RC1 --- and somebody will have time to resolve them before final.

We also have two different ways to create an RC 1 ISO from the beta 3--either download and apply the delta file, or use the zsync method. Both need about 170 MB of download total. Zsync can make an ISO from any input file, but the closer it is to the desired output, the less you'll have to download.

Posted: **Sun Dec 10, 2017 8:42 pm**

felicity wrote: (kernel problems stuff)
.

It is possible to install and boot the standard Debian 4.9 kernel to check if it has the same issue, though I realize this is more of a task with dial up service.

Posted: **Sun Dec 10, 2017 8:43 pm**

Eadwine Rose wrote:

Code: Select all

eadwine@eadwinemx17rc1:~
$ inxi -F
System:    Host: eadwinemx17rc1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop Mobo: ASUSTeK model: M4A785TD-V EVO v: Rev X.0x serial: N/A
           BIOS: American Megatrends v: 2005 date: 04/15/2010
CPU:       Quad core AMD Athlon II X4 635 (-MCP-) cache: 2048 KB
           clock speeds: max: 2900 MHz 1: 2200 MHz 2: 1700 MHz 3: 1700 MHz 4: 1700 MHz
Graphics:  Card: NVIDIA GK208 [GeForce GT 640 Rev. 2]
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GT 640/PCIe/SSE2 version: 4.5.0 NVIDIA 387.34
Audio:     Card-1 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel
           Card-3 Logitech QuickCam E 3500 driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 48:5b:39:f4:93:4e
           Card-2: Ralink MT7601U Wireless Adapter driver: mt7601u
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 1640.4GB (3.7% used)
           ID-1: /dev/sda model: WDC_WD5000AAKS size: 500.1GB
           ID-2: /dev/sdb model: Hitachi_HDT72106 size: 640.1GB
           ID-3: USB /dev/sdc model: HDP725050GLA360 size: 500.1GB
Partition: ID-1: / size: 48G used: 4.9G (11%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 384G used: 123M (1%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   System Temperatures: cpu: 37.0C mobo: 34.0C gpu: 37C
           Fan Speeds (in rpm): cpu: 2490 psu: 0 sys-1: 820
Info:      Processes: 211 Uptime: 10 min Memory: 860.7/7986.9MB Client: Shell (bash) inxi: 2.3.53

Hey all.. I am running into something. The ID-3: USB /dev/sdc (ntfs) drive's partitions always used to open when I clicked on it in thunar, now it requires a root password. Apparently ownership is set to root, and that ain't right. I couldn't find how to fix it in the manual, so... maybe one of you knows how to sort this so I don't have to enter the root password anymore?

Also.. this drive is always on and connected to the system. Used to appear in fstab. This is the currect fstab on mx17rc1. I will take a looksee on the MX16 install how this has been fiddled there.

Code: Select all

# /etc/fstab: static file system information
#
# Created by make-fstab on Sun Dec 10 23:03:03 CET 2017

# <file system>                            <mount point>                               <type>     <options>                       <dump/pass>

#-> /dev/sda1  label=rootMX17
UUID=4cb8c6e4-55d3-46c7-8283-2a30208a7beb  /                                           ext4       defaults                        1 1
#-> /dev/sda2  label=homeMX17
UUID=b115300c-9005-4829-b6c2-cff24cb448d9  /home                                       ext4       defaults                        1 2
#-> /dev/sda3  label=MXswap
UUID=92d96fbc-c28a-49b9-b27b-5e96f78d8a96  swap                                        swap       defaults                        0 0

I used to have this problem, too. And for years I just accepted it as a security feature. However, in my recent experience I have stumbled on a solution: use the Disk Manager app. Then you only have to enter the root password once to open the app. Once you have it open click the "Enable" check boxes for the partitions/drives you want to just open in Thunar w/o entering the root pw. Disk Manager automatically configures fstab for you (but it allows you some ability to fiddle & experiment with changing its choices, too).

Posted: **Sun Dec 10, 2017 9:14 pm**

Stevo wrote:
felicity wrote: (kernel problems stuff)
.
It is possible to install and boot the standard Debian 4.9 kernel to check if it has the same issue, though I realize this is more of a task with dial up service.

Let me see... So you would like me do a kernel download and set up MX-17 beta 3 to be able to boot not only from its given kernel, but from this alternate "Debian 4.9 kernel" as well. Is that right?

If that's correct, would I use the handy MX Package Installer app under Kernels? I am in MX-16.1 right now and I see two Debian kernels listed. But they are both greyed out because they are already available. (I also only have 33.3 minutes remaining of dial-up time tonight. Although the ISP's meter should reset at midnight EST, when I will again have another 10 hours of connect time available per 24 hour period.)

Posted: **Mon Dec 11, 2017 5:29 am**

Posting about the panel this time :) [SOLVED!]

I had an easy backup and restore thing going on:

copy the folder .restore into
/home/username/
Of course replacing the one that was there.

hit the restore from backup button in MX tools – MX default look

Now.. the latter is gone by the looks [no it's not, it's a checkbox now!], and when I log out and in the default panel is there still. I even unchecked save session to see if that made a difference, but nope. Did something change from 16 to 17? :)

Posted: **Mon Dec 11, 2017 5:44 am**

dr-kart wrote:I can't upgrade mpv. 0.26 is in stable repo. 0.27 is shown in test repo. Checking in and hitting update button would reinstall 0.26 version over itself.

Decided to remove 0.26 mpv before installing newer 0.27 from testing repo. Here we go. This is what I got from current test repo for reportedly 0.27 version:

Code: Select all

mpv --version

mpv 0.23.0 (C) 2000-2016 mpv/MPlayer/mplayer2 projects
 built on UNKNOWN

EDIT:
another mx package installer update just arrived. Success. 0.27 is installed from test repo.

Posted: **Mon Dec 11, 2017 6:06 am**

I am missing gcalctool in the repos.. it was so handy because it is not just a calculator, but also has monetary conversions in there.. does anyone know where it is?

Same for gis-weather and moonphase-qt and transcode

*double checks before posting or it solves itself again lol*

Posted: **Mon Dec 11, 2017 6:22 am**

@Eadwine Rose, there is no more MX Defaultlook; the successor is MX-Tweak. Did you do a fresh install of MX17 RC?

Posted: **Mon Dec 11, 2017 6:23 am**

@asqwerth: I marked that bit solved already

:) Just made it bigger so it stands out better.

I always do fresh installs.

Posted: **Mon Dec 11, 2017 6:32 am**

Another thing.. megasync (I wager the transition from 16 to 17 is a bigger change than last year's version change).

I have megasync 8 here, which gdebi now complains on 17 that a dependency is not satisfiable: libcrypt++9 [solved, see post below that has info on how to obtain megasync 9]

I THINK this page has the solution, but I am seeing cross-eyed already after a few sentences :(

https://lerdorf.com/archives/60-megasyn ... retch.html

Posted: **Mon Dec 11, 2017 6:36 am**

The switch from Jessie to Stretch brings changes in the available software for sure.

Posted: **Mon Dec 11, 2017 6:42 am**

That is for sure.. I found there IS indeed a version 9.0 available, called

megasync-Debian_9.0_amd64.deb

This one does install, taking one package along, libc-ares2

You can get that file here: https://mega.nz/sync

Posted: **Mon Dec 11, 2017 6:45 am**

I presume MX-17 will adopt Stretch after antiX does right?

Posted: **Mon Dec 11, 2017 6:51 am**

Eadwine Rose wrote:I am missing gcalctool in the repos.. it was so handy because it is not just a calculator, but also has monetary conversions in there.. does anyone know where it is?

Same for gis-weather and moonphase-qt and transcode

*double checks before posting or it solves itself again lol*

You should make the appropriate package requests in the MX17 section. Quite some time ago I recall the packaging team asking people to let them know what packages from the MX16 main/Test repos they wanted updated for the MX17 repos.

Posted: **Mon Dec 11, 2017 7:01 am**

danielson wrote:I presume MX-17 will adopt Stretch after antiX does right?

MX 17 and antix 17 are both stretch based.

Posted: **Mon Dec 11, 2017 7:04 am**

asqwerth wrote:You should make the appropriate package requests in the MX17 section. Quite some time ago I recall the packaging team asking people to let them know what packages from the MX16 main/Test repos they wanted updated for the MX17 repos.

Aha.. yeah I am always late to the testing party. I have to conserve energy where I can after all, so I jump in at the RC stage. I will post in that section, thanks!

Posted: **Mon Dec 11, 2017 10:35 am**

@dolphin_oracle - then i presume it best to wait for MX to update to latest Debian release.

Posted: **Mon Dec 11, 2017 10:37 am**

Stretch is Debian's latest release and that is what antix17 and MX17 are already based on.

Posted: **Mon Dec 11, 2017 11:56 am**

I downloaded RC1, md5 was good. I burned to a USB with the MX tools.
Booting in the signature system was fast, and a few minutes for the install.

All works as expected, sound, eth0, nvidia installer went well after the reboot. (375.82 I think(?) the backport version)
Installed 106 packages, all OK, reboot, made a few desktop tweaks.

But I am still working my Ryzen stability issue. antix 17 is very stable, with now an accumulated 21 days in 3 sessions without a crash or lock-up on the 4.10 kernel.

In contrast, the RC1 was left idle yesterday evening after all the installing and configuring. When I came down this morning, I noted RC1 was at a log in screen. I logged in, and based on the up-time, the install had rebooted after about an hour of idle time (firefox had an oops, and restored the session). Something with the 4.13 kernel I believe is causing these reboots. [and I just updated the BIOS to the 1201 which promised "increased system stability"].

Other than that, looks beautiful. Perhaps tonight I can install on a few older systems.

What would RC1 look like if I installed the antix 4.10 kernel? What would I lose?

Posted: **Mon Dec 11, 2017 12:15 pm**

entropyfoe wrote:I downloaded RC1, md5 was good. I burned to a USB with the MX tools.
Booting in the signature system was fast, and a few minutes for the install.

All works as expected, sound, eth0, nvidia installer went well after the reboot. (375.82 I think(?) the backport version)
Installed 106 packages, all OK, reboot, made a few desktop tweaks.

But I am still working my Ryzen stability issue. antix 17 is very stable, with now an accumulated 21 days in 3 sessions without a crash or lock-up on the 4.10 kernel.

In contrast, the RC1 was left idle yesterday evening after all the installing and configuring. When I came down this morning, I noted RC1 was at a log in screen. I logged in, and based on the up-time, the install had rebooted after about an hour of idle time (firefox had an oops, and restored the session). Something with the 4.13 kernel I believe is causing these reboots. [and I just updated the BIOS to the 1201 which promised "increased system stability"].

Other than that, looks beautiful. Perhaps tonight I can install on a few older systems.

What would RC1 look like if I installed the antix 4.10 kernel? What would I lose?

I don't think you would lose anything.

Posted: **Mon Dec 11, 2017 12:42 pm**

timkb4cq wrote:I haven't needed to test this, but according to a DreamLinux thread: "If zsync is stopped for any reason it can be restarted with the same command-line and will simply reuse any sections already downloaded and keep going until the ISO is complete and checks out with the md5sum."

I can confirm this works as described. I love using zsync, I wish more distros made it an option.

Posted: **Mon Dec 11, 2017 12:51 pm**

tstechy wrote:
timkb4cq wrote:I haven't needed to test this, but according to a DreamLinux thread: "If zsync is stopped for any reason it can be restarted with the same command-line and will simply reuse any sections already downloaded and keep going until the ISO is complete and checks out with the md5sum."
I can confirm this works as described. I love using zsync, I wish more distros made it an option.

Yes, it's an amazing tool, it takes few seconds to generate a .zsync file, not sure why not more distros use it. I especially like that it accept any input file for example a Beta1 if you don't have a Beta3 (the difference will be larger so it will download more but still a great saving).

Posted: **Mon Dec 11, 2017 1:04 pm**

felicity wrote:
Going back to looking for a software, rather than a hardware solution, MX-16 & Windows XP never had this problem of display resolution being frozen at 1024x768. And antiX-17 also had it initially. But then I found a way to prevent it from being frozen at 1024x768 that has been stable with no video-related crashes occurring. That way was to install from an optical disk (CD or DVD) with the Virtual Machine mode boot parameter. (That is, for some reason, only an option from a disk but not a USB flash drive install.) Then there are a only a couple of complaints from the kernel during boot-up (without the quiet boot parameter). It says it's disabling some Virtual Machine features (presumably, the kernel can detect that it is not in a VM, but in physical hardware), but then antiX-17 has been stable and it does allow me to change video mode freely. (So actually I currently have a quadruple, not a dual boot system: Windows XP Professional, MX-16.1, MX-17 beta 3, antiX-17.)

Can anybody kindly tell me if the graphics-related boot parameters I have manually chosen for MX-15 beta 3 are rational, or suggest any better ones to prevent booting into 1024x768 display resolution and then being unable to change from it to my LCD monitor's highest possible one, 1024x1280? Again, here's the relevant part of the Grub Customizer Entry Editor window:

I think that inxi-F output will vary differently for the resolution whatever the resolution you have selected that will be used as the output of this command. So, better go to whisker menu and search for display and see that your monitor name is displayed on that screen and can you able to select the resolutions if everything is okay there it must be software problem i used to run the above command as startup script to force the MX linux to change resolution kindly try this.

Use sudo xrandr my output is this

Code: Select all

Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 410mm x 260mm
   1440x900      59.89 +
   1280x1024     75.02*   60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.08    70.07    60.00  
   800x600       72.19    75.00    60.32  
   640x480       75.00    72.81    60.00  
   720x400       70.08

if it is not VGA change the related in the startup script and add it to startup so that will force the resolution

Code: Select all

#!/bin/bash

	xrandr --newmode  "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync

xrandr --addmode VGA1 1280x1024_60.00

xrandr --output VGA1 --mode 1280x1024_60.00

suppose if i change my resolution to 1024*768 and when i used this command my output is

Code: Select all

inxi -G
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
           Display Server: X.Org 1.19.5 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1024x768@75.08hz
           OpenGL: renderer: Mesa DRI Intel 945G x86/MMX/SSE2 version: 2.1 Mesa 12.0.3

So don't take the output of this command as basis rather than use the command

Code: Select all

sudo xrandr

then it should display the available resolutions if not then there is some hardware problem i think.

Thanks..

Posted: **Mon Dec 11, 2017 2:52 pm**

What is Next to RC 1 either RC2 or RC3 or Final Version

Posted: **Mon Dec 11, 2017 2:57 pm**

Most likely the Final Version if was are satisfied with the changes and if we don't need extra testing.

Posted: **Mon Dec 11, 2017 4:49 pm**

One little thing I did encounter. The grey desktop thing after you turned on display compositing in settings manager - windows manager tweaks - compositing.

In the alpha5 thread it is said: "Due to a post on the Debian forums, I confirmed that the desktop will turn blank grey for a few seconds while starting up if the xfce compositor is being used. Since using Compton instead will fix this non-fatal yet possibly annoying issue, perhaps we can just suggest that fix in the manual if the user is bugged by it."

It might be worth a mention in the manual. I have used Compton in the past, but for whatever reason I switched back to the xfce one. Likely because Compton and I didn't become friends

I'll give it another go though, see what I find. If I can find again where the thing is located that is..

Ah.,. mx tweak, compositor, drop down menu.

Posted: **Mon Dec 11, 2017 6:12 pm**

vamsi wrote:
felicity wrote:
Going back to looking for a software, rather than a hardware solution, MX-16 & Windows XP never had this problem of display resolution being frozen at 1024x768. And antiX-17 also had it initially. But then I found a way to prevent it from being frozen at 1024x768 that has been stable with no video-related crashes occurring. That way was to install from an optical disk (CD or DVD) with the Virtual Machine mode boot parameter. (That is, for some reason, only an option from a disk but not a USB flash drive install.) Then there are a only a couple of complaints from the kernel during boot-up (without the quiet boot parameter). It says it's disabling some Virtual Machine features (presumably, the kernel can detect that it is not in a VM, but in physical hardware), but then antiX-17 has been stable and it does allow me to change video mode freely. (So actually I currently have a quadruple, not a dual boot system: Windows XP Professional, MX-16.1, MX-17 beta 3, antiX-17.)

Can anybody kindly tell me if the graphics-related boot parameters I have manually chosen for MX-15 beta 3 are rational, or suggest any better ones to prevent booting into 1024x768 display resolution and then being unable to change from it to my LCD monitor's highest possible one, 1024x1280? Again, here's the relevant part of the Grub Customizer Entry Editor window:
I think that inxi-F output will vary differently for the resolution whatever the resolution you have selected that will be used as the output of this command. So, better go to whisker menu and search for display and see that your monitor name is displayed on that screen and can you able to select the resolutions if everything is okay there it must be software problem i used to run the above command as startup script to force the MX linux to change resolution kindly try this.

Use sudo xrandr my output is this
Code: Select all
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 410mm x 260mm
   1440x900      59.89 +
   1280x1024     75.02*   60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.08    70.07    60.00  
   800x600       72.19    75.00    60.32  
   640x480       75.00    72.81    60.00  
   720x400       70.08  
if it is not VGA change the related in the startup script and add it to startup so that will force the resolution
Code: Select all
#!/bin/bash

	xrandr --newmode  "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync

xrandr --addmode VGA1 1280x1024_60.00

xrandr --output VGA1 --mode 1280x1024_60.00
suppose if i change my resolution to 1024*768 and when i used this command my output is
Code: Select all
inxi -G
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
           Display Server: X.Org 1.19.5 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1024x768@75.08hz
           OpenGL: renderer: Mesa DRI Intel 945G x86/MMX/SSE2 version: 2.1 Mesa 12.0.3
So don't take the output of this command as basis rather than use the command
Code: Select all
sudo xrandr 
then it should display the available resolutions if not then there is some hardware problem i think.

Thanks..

Thank you for your suggestion.

As I recall, I have already tried changing the resolution of MX-17 beta (and antiX-17) installations that were frozen at 1024x768 with many, many variations of sudo xrandr commands of the same nature as your suggested examples. But none worked. There was always a failure of the xrandr commands to change the resolution. Hence my use of the term frozen. (Unfortunately, I did not record the output of these xrandr commands at the time, so I cannot give you verbatim their complaints indicative of failure to change graphics mode.)

My current MX-17 installation is the beta 3 one which I was able to unfreeze (but which is unstable with patently graphics-related crashes) by tinkering with the boot parameters in the installation set-up menu (and Grub Customizer post-installation). So there is no point now in experimenting with xrandr --- it works! But I am finally ready to upgrade to MX-17 RC1. Then I will have ample opportunity to experiment again. And since it is certainly possible that in the past I entered xrandr commands that were not quite correct, your recent examples may potentially be helpful.

BTW, so far in my reading of this topic's posts I have found at least one other poster complaining that MX-17 RC1 is unstable.

Posted: **Mon Dec 11, 2017 6:42 pm**

You can get a lock screen for security if coming back from suspend2ram, suspend2disk, or just screen blanking by just installing light-locker. The lock screen setting is in power management settings. I think we should have light-locker installed by default, perhaps the high-security settings remain as they are.

Posted: **Mon Dec 11, 2017 6:52 pm**

Stevo wrote:
felicity wrote: (kernel problems stuff)
.
It is possible to install and boot the standard Debian 4.9 kernel to check if it has the same issue, though I realize this is more of a task with dial up service.

OK! Looks like (after educating myself) I may be ready to do this.

I found the following three sources:
Debian -- Details of package linux-image-686-pae in stretch
https://packages.debian.org/stretch/linux-image-686-pae
Debian -- Details of package linux-image-4.9.0-4-686-pae in stretch
https://packages.debian.org/stretch/lin ... -4-686-pae
HowToUpgradeKernel - Debian Wiki
https://wiki.debian.org/HowToUpgradeKernel

I am open to any comments/suggestions anyone may make.

Thanks

Posted: **Mon Dec 11, 2017 8:46 pm**

Getting an error from Synaptic:

Code: Select all

E: mx-system: subprocess installed post-installation script returned error exit status 2
E: mx-apps: dependency problems - leaving unconfigured

A similar issue when I tried to add Australian spell/thesaurus packages

Anyone else?

Posted: **Mon Dec 11, 2017 8:51 pm**

What mirror are you using? I haven't been able to duplicate it

Posted: **Mon Dec 11, 2017 8:54 pm**

I changed to the LA mirror after the initial NZ had defaulted, but neither work for me.

*Just added Waterfall, but again the same glitch.

Code: Select all

Selecting previously unselected package gwaterfall.
(Reading database ... 310148 files and directories currently installed.)
Preparing to unpack .../gwaterfall_0.1-5.1+b1_amd64.deb ...
Unpacking gwaterfall (0.1-5.1+b1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up mx-system (17~rc1) ...
python-bluez was already set to manually installed.
system-config-printer was already set to manually installed.
system-config-samba was already set to manually installed.
sed: can't read /etc/grub.d/10_linux: No such file or directory
dpkg: error processing package mx-system (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of mx-apps:
 mx-apps depends on mx-system; however:
  Package mx-system is not configured yet.

dpkg: error processing package mx-apps (--configure):
 dependency problems - leaving unconfigured
Processing triggers for menu (2.1.47+b1) ...
Setting up gwaterfall (0.1-5.1+b1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for menu (2.1.47+b1) ...
Errors were encountered while processing:
 mx-system
 mx-apps
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up mx-system (17~rc1) ...
python-bluez was already set to manually installed.
system-config-printer was already set to manually installed.
system-config-samba was already set to manually installed.
sed: can't read /etc/grub.d/10_linux: No such file or directory
dpkg: error processing package mx-system (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of mx-apps:
 mx-apps depends on mx-system; however:
  Package mx-system is not configured yet.

dpkg: error processing package mx-apps (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 mx-system
 mx-apps

Posted: **Mon Dec 11, 2017 8:55 pm**

32 or 64 bit?

Posted: **Mon Dec 11, 2017 8:59 pm**

Sorry, 64bit

Code: Select all

 inxi -F
System:    Host: mx1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop System: LENOVO product: 7522RU3 v: ThinkCentre A58 serial: N/A
           Mobo: LENOVO model: N/A serial: N/A BIOS: LENOVO v: 5HKT52AUS date: 07/15/2010
CPU:       Dual core Intel Core2 Duo E7300 (-MCP-) cache: 3072 KB
           clock speeds: max: 2670 MHz 1: 1603 MHz 2: 1603 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           OpenGL: renderer: Mesa DRI Intel G41 version: 2.1 Mesa 13.0.6
Audio:     Card Intel NM10/ICH7 Family High Def. Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-amd64
Network:   Card-1: Marvell 88E8057 PCI-E Gigabit Ethernet Controller driver: sky2
           IF: eth0 state: down mac: 00:01:6c:48:1a:77
           Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 1000.2GB (44.0% used)
           ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 49G used: 4.8G (11%) fs: ext4 dev: /dev/sda13
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 38.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 193 Uptime: 17 min Memory: 937.0/3920.8MB Client: Shell (bash) inxi: 2.3.53

The only thing unusual I did was add the driver for the new dongle per recent thread. Although, my Data drive is read-only too I have just noticed after trying to rename/copy-paste that driver folder name.

Posted: **Mon Dec 11, 2017 9:05 pm**

I'll test out Synaptic with the USB I used to install, for comparison and advise....

**Testing USB shows....

Posted: **Mon Dec 11, 2017 9:08 pm**

Thank You. That narrows the problem down to the postinst script in mx-system.
It works on a LiveUSB or VM from iso. Let me see why it doesn't work on a hardware install...

Posted: **Mon Dec 11, 2017 9:17 pm**

timkb4cq wrote:Thank You. That narrows the problem down to the postinst script in mx-system.
It works on a LiveUSB or VM from iso. Let me see why it doesn't work on a hardware install...

looks to me like the /etc/grub.d/10_linux file on his system may be missing. that doesn't sound good.

Posted: **Mon Dec 11, 2017 9:17 pm**

Yep, no problems updating Synaptic in a live session, nor mounting my 'data' partition (copy/delete etc working fine).
I thought I might have a bad *.iso and might download again at the library today just to be sure.

**never fear, reinstalling is not a problem here.

Posted: **Mon Dec 11, 2017 10:05 pm**

After install and using rc1 I cannot see why rc1 will not be the final .Everything just works for me on my old 32 bit system.Thanks to all john

Posted: **Mon Dec 11, 2017 10:07 pm**

Just create the empty file with

Code: Select all

sudo touch /etc/grub.d/10_linux

and then see if the upgrade goes through.

I'll add that to the postinst script so we won't have this problem with a missing file, though I don't know how that happens, I think Jerry got it, too.

Posted: **Mon Dec 11, 2017 10:08 pm**

golden45 wrote:After install and using rc1 I cannot see why rc1 will not be the final .Everything just works for me on my old 32 bit system.Thanks to all john

Very well, but we need to make sure it's working well for the vast majority of testers first.

Posted: **Mon Dec 11, 2017 10:09 pm**

Stevo wrote:Just create the empty file with
Code: Select all
sudo touch /etc/grub.d/10_linux
and then see if the upgrade goes through.

I'll add that to the postinst script so we won't have this problem with a missing file, though I don't know how that happens, I think Jerry got it, too.

I'm working on a version that tests for the file now.

However, I'm more interested in why 10_linux is missing? its a key part of the grub configuration.

question: did people with this problem run snapshot by any chance?

Posted: **Mon Dec 11, 2017 10:15 pm**

Here's the update to mx-system:

mx-system_the-good-touch.zip

Posted: **Mon Dec 11, 2017 10:16 pm**

I'm not sure that "touching" 10_linux is a good idea, given that the file will be sourced during an update-grub. I'm not sure what will happen, have you tried it?

I would really like to see tascoast's /etc/grub.d folder contents.

Posted: **Mon Dec 11, 2017 10:27 pm**

I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.

Posted: **Mon Dec 11, 2017 10:28 pm**

Yes, the touch just fixes the nonexistent file problem, like testing for the existence first...but both a missing or an empty file are equally bad, since it's really essential the full contents of the file be there. Or it could just be a bad install or a bad spot on the hard drive, too.

Posted: **Mon Dec 11, 2017 10:44 pm**

The SATA drive I use is around 12 months old and should be OK, but I'll have another go installing with a fresh download later today. The data partition (but not two other common partitions) being read-only/owned by root is good enough reason to begin anew. Please continue with the fine work and cheers meanwhile. )

Posted: **Mon Dec 11, 2017 10:52 pm**

Eureka!
Grub Customizer changes that filename.
It sets up 10_linux_proxy and moves the original 10_linux to /etc/grub.d/backup/10_linux *and* to /etc/grub.d/proxifiedScripts/linux
I'm pretty sure it's the latter one that is used by 10_linux_proxy.
So I guess there needs to be a test to see if the user has used grub-customizer

Posted: **Mon Dec 11, 2017 10:54 pm**

tascoast wrote:I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.

Have you used grub customizer by chance?

Posted: **Mon Dec 11, 2017 11:18 pm**

dolphin_oracle wrote:
tascoast wrote:I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.
Have you used grub customizer by chance?

Indeed I did. Apart from basic desktop personalisations, I routinely use Grub Customizer after an install. Greetings from my local library.

Posted: **Tue Dec 12, 2017 12:09 am**

I just installed RC1 and it completed smooth as silk. One minor error I noticed is default Conky shows free HD space after the word USED. Checked the config file and indeed it has fs_free where it should be fs_used

Posted: **Tue Dec 12, 2017 12:22 am**

tascoast wrote:
dolphin_oracle wrote:
tascoast wrote:I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.
Have you used grub customizer by chance?
Indeed I did. Apart from basic desktop personalisations, I routinely use Grub Customizer after an install. Greetings from my local library.

I have always felt that repeated use of GC to modify menu entries, particularly when you have many distros on your system, will eventually lead to one's grub menu being messed up. I think I mentioned in this forum before that GC began to add extra os_prober entries in my /etc/grub.d folder, leading to a grub menu that was repeated 2 or 3 times whenever grub was updated/re-generated. I stopped using it maybe 2 years ago.

Posted: **Tue Dec 12, 2017 2:23 am**

sunrat wrote:I just installed RC1 and it completed smooth as silk. One minor error I noticed is default Conky shows free HD space after the word USED. Checked the config file and indeed it has fs_free where it should be fs_used

Oops, thanks. I switched at the end to simplify and forgot to change that.

Posted: **Tue Dec 12, 2017 4:06 am**

Take two for installing and all looks OK so far. I suspect the NZ repo might not be up-to-date yet, and switched to LA again.
/etc/grub.d/10_Linux is 12.4KB

Posted: **Tue Dec 12, 2017 4:42 am**

When the MX installer is told to use the whole drive for installation, it creates the partitions dependent on what type of Live-boot environment it running in, e.g., EFI boot or Legacy boot, and as a part of the process, it marks one partition as bootable and the rest is music to my ears.

The same is not true of an installation to custom or existing partitions, and in some rare cases, especially those where the user starts with a fully blank drive, the installation routine finishes but after rebooting, the computer BIOS fails to find an installed OS and requests some form of bootable device be inserted. This is what happens with one of my laptops and a similar thing was reported on our facebook page.

In such a situation, the solution is simple, reboot from Live-media, fire up gparted and on MBR formatted drives, set the boot flag on the partition used for root, or on GPT drives set the boot flag to the esp partition and reboot.

I believe it prudent to have this written up someplace, possibly our wiki or our troubleshooting section of the manual, and maybe even release notes because this is a complex issue that likely can not be addressed in this release cycle.

Posted: **Tue Dec 12, 2017 5:39 am**

The fluxgui (f.lux) version 1.1.9 for MX16.1 (32bit & 64bit) and the recently updated version 1.1.10, just works and perfectly !! .
Either with MX16.1 installed or run from a USB stick on the following machines:
HP Compaq 6715b;
HP Compaq 6910p;
HP Compaq nx6325 (32bit)
Lenovo Thinkpad T500;
Lenovo Thinkpad X220;
ASUS Eee PC 1005HA (32bit).

The fluxgui version 1.1.10 for MX17-RC1 32bit & 64bit, it's a whole different story:

-the fluxgui on MX17-RC1 64bit, run from USB stick on the:
HP Compaq 6715b - works perfectly
HP Compaq 6910p - works perfectly
HP Compaq nx6325 (32bit) - does not apply
Lenovo Thinkpad T500 - does not work
Lenovo Thinkpad X220 - does not work
ASUS Eee PC 1005HA (32bit) - does not apply

-the fluxgui on MX17-RC1 32bit, run from USB stick on the:
HP Compaq 6715b - messes up the display, badly. Must log-out & log-on to restore the display.
HP Compaq 6910p - messes up the display, badly. Must log-out & log-on to restore the display.
HP Compaq nx6325 (32bit) - messes up the display, badly. Must log-out & log-on to restore the display.
Lenovo Thinkpad T500 - does not work
Lenovo Thinkpad X220 - does not work
ASUS Eee PC 1005HA - works perfectly

----------------- -------------------- ----------------
https://github.com/xflux-gui/fluxgui
https://justgetflux.com/linux.html

"The f.lux indicator applet fluxgui is an indicator applet to control xflux, an application that makes the color of your computer's display adapt to the time of day, warm at nights and like sunlight during the day. Reducing blue light exposure in the evening (...)."

Besides this fluxgui issue, I really like the MX17. Good work!!!
Cheers!!

Posted: **Tue Dec 12, 2017 6:58 am**

Can you post the output of

Code: Select all

inxi -G

for one of the machines that doesn't work, with MX-16 and -17.

Posted: **Tue Dec 12, 2017 7:35 am**

nanoSYS wrote:The fluxgui (f.lux) version 1.1.9 for MX16.1 (32bit & 64bit) and the recently updated version 1.1.10, just works and perfectly !! .
Either with MX16.1 installed or run from a USB stick on the following machines:
HP Compaq 6715b;
HP Compaq 6910p;
HP Compaq nx6325 (32bit)
Lenovo Thinkpad T500;
Lenovo Thinkpad X220;
ASUS Eee PC 1005HA (32bit).

The fluxgui version 1.1.10 for MX17-RC1 32bit & 64bit, it's a whole different story:

-the fluxgui on MX17-RC1 64bit, run from USB stick on the:
HP Compaq 6715b - works perfectly
HP Compaq 6910p - works perfectly
HP Compaq nx6325 (32bit) - does not apply
Lenovo Thinkpad T500 - does not work
Lenovo Thinkpad X220 - does not work
ASUS Eee PC 1005HA (32bit) - does not apply

-the fluxgui on MX17-RC1 32bit, run from USB stick on the:
HP Compaq 6715b - messes up the display, badly. Must log-out & log-on to restore the display.
HP Compaq 6910p - messes up the display, badly. Must log-out & log-on to restore the display.
HP Compaq nx6325 (32bit) - messes up the display, badly. Must log-out & log-on to restore the display.
Lenovo Thinkpad T500 - does not work
Lenovo Thinkpad X220 - does not work
ASUS Eee PC 1005HA - works perfectly

----------------- -------------------- ----------------
https://github.com/xflux-gui/fluxgui
https://justgetflux.com/linux.html

"The f.lux indicator applet fluxgui is an indicator applet to control xflux, an application that makes the color of your computer's display adapt to the time of day, warm at nights and like sunlight during the day. Reducing blue light exposure in the evening (...)."

Besides this fluxgui issue, I really like the MX17. Good work!!!
Cheers!!

could you update your list to specify legacy vs. uefi boot on each machine. thank you.

Posted: **Tue Dec 12, 2017 7:38 am**

@ Jerry3904, outputs as requested,

Lenovo Thinkpad T500 - fluxgui on MX16.1 64bit, works perfectly. inxi -G

Code: Select all

$ inxi -G
Graphics:  Card-1: Intel Mobile 4 Series Integrated Graphics Controller
           Card-2: Advanced Micro Devices [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650]
           Display Server: X.Org 1.16.4 drivers: ati,radeon,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1680x1050@59.98hz
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express version: 2.1 Mesa 13.0.4

Lenovo Thinkpad T500 - fluxgui on MX17-RC1 64bit, does not work. inxi -G

Code: Select all

$ inxi -G
Graphics:  Card-1: Intel Mobile 4 Series Integrated Graphics Controller
           Card-2: Advanced Micro Devices [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: modesetting,ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.98hz
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express version: 2.1 Mesa 13.0.6

Lenovo Thinkpad X220 - fluxgui on MX16.1 64bit, works perfectly. inxi -G

Code: Select all

$ inxi -G
Graphics:  Card: Intel 2nd Generation Core Integrated Graphics Controller
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 12.0.3

Lenovo Thinkpad X220 - fluxgui on MX17-RC1 64bit, does not work. inxi -G

Code: Select all

$ inxi -G
Graphics:  Card: Intel 2nd Generation Core Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 13.0.6

Cheers!

Posted: **Tue Dec 12, 2017 7:45 am**

m_pav wrote:When the MX installer is told to use the whole drive for installation, it creates the partitions dependent on what type of Live-boot environment it running in, e.g., EFI boot or Legacy boot, and as a part of the process, it marks one partition as bootable and the rest is music to my ears.

The same is not true of an installation to custom or existing partitions, and in some rare cases, especially those where the user starts with a fully blank drive, the installation routine finishes but after rebooting, the computer BIOS fails to find an installed OS and requests some form of bootable device be inserted. This is what happens with one of my laptops and a similar thing was reported on our facebook page.

In such a situation, the solution is simple, reboot from Live-media, fire up gparted and on MBR formatted drives, set the boot flag on the partition used for root, or on GPT drives set the boot flag to the esp partition and reboot.

I believe it prudent to have this written up someplace, possibly our wiki or our troubleshooting section of the manual, and maybe even release notes because this is a complex issue that likely can not be addressed in this release cycle.

Thanks for this detail, m_pav...important bug in MX Installer...will add to queue (unless already there).

Posted: **Tue Dec 12, 2017 7:51 am**

Yesterday, on this signature machine there were two crashes. This agrees with some reports on the net, one Red Hat engineer with a Ryzen 1700 and my same motherboard, reported random reboots every few hours with kernel 4.13.

So two crashes in one day, with little to lose, ana my stable antix17 (21 up days no crashes) installation on the same machine, ..... I did what?

I boldly went and read the manual ! Thanks jerry. Instead of quickly skimming like last kernel expedition, this time I searched the .pdf, and came to the section on the MX Package installer. Selected the kernel item, and there was the antix 4.10. I simply checked the box for 4.10 and rebooted.

That was easy !

What a great tool. Sure beats my earlier manual attempt, maybe just the versions, but the NVIDIA driver is still installed, and no black screens or blinking cursors.
This morning the system is still up, cross fingers, but under 4.13, I had one crash over night, so I am past that. I have a good feeling about this stability now, but time will tell.

And thanks to Dolphin Oracle, who suggested I would lose nothing by the kernel downgrade. I have kind of a hybrid now, antix conky, antix kernel, but all the niceties of MX 17 RC1 desktop.

Code: Select all

music@Ryzen:~
$ inxi -F
System:    Host: Ryzen Kernel: 4.10.5-antix.3-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: N/A
           UEFI [Legacy]: American Megatrends v: 1201 date: 10/18/2017
CPU:       6 core AMD Ryzen 5 1600X Six-Core (-MT-MCP-) cache: 3072 KB
           clock speeds: max: 3600 MHz 1: 2200 MHz 2: 2200 MHz 3: 2200 MHz 4: 2200 MHz
           5: 2200 MHz 6: 2200 MHz 7: 2200 MHz 8: 2200 MHz 9: 2200 MHz 10: 2200 MHz 11: 2200 MHz
           12: 2200 MHz
Graphics:  Card: NVIDIA GK208 [GeForce GT 710B]
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 version: 4.5.0 NVIDIA 375.82
Audio:     Card-1 Advanced Micro Devices [AMD] Device 1457 driver: snd_hda_intel
           Card-2 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp
Network:   Card: Intel I211 Gigabit Network Connection driver: igb
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 60:45:cb:a0:1a:e3
Drives:    HDD Total Size: 1250.3GB (40.9% used)
           ID-1: /dev/sda model: Samsung_SSD_850 size: 1000.2GB
           ID-2: /dev/nvme0n1 model: Samsung_SSD_960_EVO_250GB size: 250.1GB
Partition: ID-1: / size: 39G used: 5.9G (17%) fs: ext4 dev: /dev/nvme0n1p1
           ID-2: /home size: 73G used: 341M (1%) fs: ext4 dev: /dev/nvme0n1p3
           ID-3: swap-1 size: 17.83GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p2
Sensors:   System Temperatures: cpu: N/A mobo: N/A gpu: 35C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 350 Uptime: 9:09 Memory: 995.7/16046.7MB Client: Shell (bash) inxi: 2.3.53

Posted: **Tue Dec 12, 2017 8:04 am**

@ dolphin_oracle

could you update your list to specify legacy vs. uefi boot on each machine. thank you.

I think only the Thinkpad X220 does UEFi boot, and the BIOS is set to both boots (Legacy and UEFI) with Legacy first priority.
What would be the easiest way to check it?
Thank you.

Posted: **Tue Dec 12, 2017 8:25 am**

Looks like the common factor in the ones where it doesn't work is that modesetting is enabled. All the working models have it unloaded.

Posted: **Tue Dec 12, 2017 8:27 am**

could be.

I know my thinkpad backlight works differently in UEFI vs. legacy boot. its weird and it shouldn't but it does. the controls are backwards. there is an intel video driver option to flip it. I really don't know if this is related to the flux thing or not.

Posted: **Tue Dec 12, 2017 8:35 am**

m_pav wrote:When the MX installer is told to use the whole drive for installation, it creates the partitions dependent on what type of Live-boot environment it running in, e.g., EFI boot or Legacy boot, and as a part of the process, it marks one partition as bootable and the rest is music to my ears.

The same is not true of an installation to custom or existing partitions, and in some rare cases, especially those where the user starts with a fully blank drive, the installation routine finishes but after rebooting, the computer BIOS fails to find an installed OS and requests some form of bootable device be inserted. This is what happens with one of my laptops and a similar thing was reported on our facebook page.

In such a situation, the solution is simple, reboot from Live-media, fire up gparted and on MBR formatted drives, set the boot flag on the partition used for root, or on GPT drives set the boot flag to the esp partition and reboot.

I believe it prudent to have this written up someplace, possibly our wiki or our troubleshooting section of the manual, and maybe even release notes because this is a complex issue that likely can not be addressed in this release cycle.

The tracker has two entries on this. One should be deleted. The earlier one has a comment by D_O and should be retained.

Posted: **Tue Dec 12, 2017 9:04 am**

Posted: **Tue Dec 12, 2017 10:55 am**

Hi everyone. I'm running live MX RC1 on gpd pocket. Can't connect to network. Another laptop with same usb stick and same network connects without issue. Also custom remaster with persistent(No chance of mistype password).

inxi -F

Code: Select all

System:    Host: mx1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: desktop Mobo: AMI model: N/A serial: N/A UEFI: American Megatrends v: 5.11 date: 06/28/2017
CPU:       Quad core Intel Atom x7-Z8750 (-MCP-) cache: 1024 KB
           clock speeds: max: 2560 MHz 1: 1600 MHz 2: 1600 MHz 3: 1600 MHz 4: 1600 MHz
Graphics:  Card: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers
           Display Server: x11 (X.Org 1.19.2 ) driver: intel Resolution: 1200x1920@60.38hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics (Cherrytrail) version: 4.5 Mesa 13.0.6
Audio:     Card-1 chtrt5645 driver: chtrt5645 Sound: ALSA v: k4.13.0-1-amd64
           Card-2 Intel HDMI/DP LPE Audio driver: HdmiLpeAudio
Network:   Card: Broadcom Limited BCM4356 802.11ac Wireless Network Adapter driver: brcmfmac
           IF: wlan0 state: down mac: b0:f1:ec:82:fe:5a
Drives:    HDD Total Size: 4.1GB (77.4% used)
           ID-1: /dev/mmcblk0 model: N/A size: 125.1GB
           ID-2: USB /dev/sda model: Transcend_4GB size: 4.1GB
Partition: ID-1: / size: 5.8G used: 178M (4%) fs: overlay dev: N/A
           ID-2: /home size: 239M used: 48M (22%) fs: ext4 dev: /dev/loop1
Sensors:   System Temperatures: cpu: 38.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 196 Uptime: 18 min Memory: 593.0/7389.2MB Client: Shell (bash) inxi: 2.3.53

daemon.log throws:

Code: Select all

wlan0: Failed to initiate sched scan
wlan0: Failed to initiate sched scan
wlan0: Failed to initiate sched scan
wlan0:Reject scan trigger since one is already pending
wlan0: Failed to initiate sched scan
wlan0: Failed to initiate sched scan
wlan0: Trying to associate with SSID 'Xperia X'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: Trying to associate with SSID 'Xperia X'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: Trying to associate with SSID 'Xperia X'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Xperia X"
auth_failures=1 duration=10 reason=CONN_FAILED

Also tried Wicd. No success -"Bad password".
Currently lubuntu installed on disk has no problem with connection. Would love to install mx though.

Posted: **Tue Dec 12, 2017 12:11 pm**

Firstly, great work on MX17 - used the RC since release... only 2 minor problems:

CD/DVDs aren't detected unless I load them using something like VLC to attempt to play the content. To be clear, nothing shows up in Thunar until loaded by VLC.

Also, resume from suspend is unpredictable - sometimes just get a black screen; only way around it is login to TTY1 (CTRL-ALT-F1) and then TTY7 (CTRL-ALT-F7) gets the Desktop back.

I'm not on MX17 ATM, as I'm updating Manjaro.

Code: Select all

System:    Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 serial: N/A
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: N/A
           BIOS: Phoenix v: 03PA.M001.20110312.XW date: 03/12/2011
Battery    BAT1: charge: 9.7 Wh 100.0% condition: 9.7/47.5 Wh (20%)
CPU:       Dual core Intel Core i3 M 380 (-MT-MCP-) speed/max: 1066/2533 MHz
Graphics:  Card: NVIDIA GT218M [GeForce 315M]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@59.99hz
           OpenGL: renderer: Gallium 0.4 on NVA8 version: 3.3 Mesa 13.0.6
Network:   Card-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter driver: wl
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 250.1GB (53.5% used)
Info:      Processes: 198 Uptime: 1:36 Memory: 735.8/5832.7MB Client: Shell (bash) inxi: 2.3.53

EDIT: I've switched to the 4.9 series Kernel as it works fine with my hardware... both of the above problems occur with the later Kernels too

Posted: **Tue Dec 12, 2017 12:34 pm**

You might try the Nvidia proprietary driver instead of nouveau, using the MX Tool.

Posted: **Tue Dec 12, 2017 12:56 pm**

Debian hasn't updated the firmware for that chipset in quite a while, and I've seen threads from other distros where using the newest firmware fixes your problem. I just downloaded the latest from the kernel git repository
Download this, extract the 2 files, and copy them as root to /lib/firmware/brcm/
http://teharris.net/misc/brcmfmac4356-pcie.bin.zip
Reboot, and try again. If they do fix your problem, let us know so we can get them in the iso.
Good luck!

Posted: **Tue Dec 12, 2017 12:59 pm**

I prefer nouveau, as I use it without problems on a number of Distros - so I'll wait for now to see if the suspend/resume gets fixed.

I've fixed the CD/DVD problem by adding

Code: Select all

echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs

to /etc/rc.local

Posted: **Tue Dec 12, 2017 1:12 pm**

I've been a bit out of it this release cycle but have installed RC1 on my desktop (UEFI, 64-bit). With limited testing, I can't find a problem. Installed about 20 applications - all work OK. KMyMoney is my only remaining KDE app - it now brings in 214 packages,compared with 270 in MX-16. I haven't yet installed VirtualBox but hope to in the next few days.

Also installed on the Thinkpad X220, writing over MX-16.1. I had a few problems of my own making with setting up the default user, but again everything works fine. On boot, the screen is at minimum brightness but one touch on the Fn key brings it up and after that it's fine. I will probably upgrade this copy to Final - the desktop has many more tweaks and I will install Final from scratch when I have a break in workload.

On both systems, the appearance is great. Attractive backgrounds and the clearest text I have ever had on any system. Well done, all who have produced this. I'm even converted to using the Conky - one swift tweak to the time format and it's good. It shows that I will soon have to make larger root partitions - with only a couple of apps added, HDD use on the Thinkpad is 22.9GB out of 28.9GB, and that's with a separate /home.

Phil

Posted: **Tue Dec 12, 2017 1:24 pm**

It shows that I will soon have to make larger root partitions - with only a couple of apps added, HDD use on the Thinkpad is 22.9GB out of 28.9GB, and that's with a separate /home.

If you were using the default conky, this might be the conky mistake spotted a few pages ago where the conky code used displayed the free space rather than the used space.

Posted: **Tue Dec 12, 2017 2:06 pm**

@asqwerth - Obviously! I must have thought I was back using Windows.

Phil

Posted: **Tue Dec 12, 2017 2:08 pm**

Gaer Boy wrote:@asqwerth - Obviously! I must have thought I was back using Windows.

Phil

Posted: **Tue Dec 12, 2017 2:31 pm**

timkb4cq wrote:Debian hasn't updated the firmware for that chipset in quite a while, and I've seen threads from other distros where using the newest firmware fixes your problem. I just downloaded the latest from the kernel git repository
Download this, extract the 2 files, and copy them as root to /lib/firmware/brcm/
http://teharris.net/misc/brcmfmac4356-pcie.bin.zip
Reboot, and try again. If they do fix your problem, let us know so we can get them in the iso.
Good luck!

Thank you for quick response. Unfortunately new firmware didn't help. Network is down. Putting it up makes SIOCSIFFLAGS: input/output error. Are there any other versions of this firmware?

Posted: **Tue Dec 12, 2017 3:26 pm**

piwadam wrote:
timkb4cq wrote:Debian hasn't updated the firmware for that chipset in quite a while, and I've seen threads from other distros where using the newest firmware fixes your problem. I just downloaded the latest from the kernel git repository
Download this, extract the 2 files, and copy them as root to /lib/firmware/brcm/
http://teharris.net/misc/brcmfmac4356-pcie.bin.zip
Reboot, and try again. If they do fix your problem, let us know so we can get them in the iso.
Good luck!
Thank you for quick response. Unfortunately new firmware didn't help. Network is down. Putting it up makes SIOCSIFFLAGS: input/output error. Are there any other versions of this firmware?

I'm typing from my gpd pocket. timkb4cq tank you for your help. I copied firmware from lubuntu I installed earlier on gpd. Solved.

Posted: **Tue Dec 12, 2017 3:31 pm**

What lubuntu version was that? t'would be good to have it available.

Posted: **Tue Dec 12, 2017 3:53 pm**

Sorry it is xubuntu from this site. 17.04 but these are respins so firmware might be changed in theme.

Posted: **Tue Dec 12, 2017 3:54 pm**

Forgot to paste site: https://apt.nexus511.net/

Posted: **Tue Dec 12, 2017 11:54 pm**

Is there a way of usb format and usb image writer

Posted: **Wed Dec 13, 2017 1:58 am**

golden45 wrote:Is there a way of usb format and usb image writer

USB image writer UNETBOOTIN preinstalled installed on mx linux

and USB FORMAT GPARTED preinstalled installed on mx linux

Posted: **Wed Dec 13, 2017 2:59 am**

Oh.. speaking of unetbootin, IIRC I actually had to install that myself on 17rc1 as it was not appearing as installed in synaptic when I was installing my usual list of packages.

Posted: **Wed Dec 13, 2017 4:16 am**

Eadwine Rose wrote:Oh.. speaking of unetbootin, IIRC I actually had to install that myself on 17rc1 as it was not appearing as installed in synaptic when I was installing my usual list of packages.

correct...somewhere along the way we chose to remove unetbootin because it was flakey for some people.

however, our live-usb-maker-gui now has a "dd" mode, which should support any distro, not just ours.

Posted: **Wed Dec 13, 2017 4:21 am**

I still prefer unetbootin because dd mode causes an entire flash drive to become completely useless for any other operation, which is a terrible waste when using 16, 32 & 64GB drives, or when a drive is to be shared across differing operating systems.

Posted: **Wed Dec 13, 2017 4:50 am**

The person who asked the question mentioned: "usb image writer". Isn't that SUSE's version of a GUI for dd mode? If so, MX's live-usb-maker-gui is the equivalent of what he was looking for.

To be honest, I haven't used unetbootin for a long time. I either use dd or save the iso file onto an Easy2Boot-prepared multiboot USB drive.

This is apart from using MX's own live usb maker for MX isos.

Posted: **Wed Dec 13, 2017 5:08 am**

(ties up) an entire flash drive

This overlaps the pain point I mentioned regarding mxsnapshot. A live user winds up needing an extra, separate, device
(linuxfs + rootfs + apt upgrade = too large to fit in RAM, so cannot "toram" then unmount and repartition the boot device)
edit: Zzzzz, Reading that, it looks incorrect as a "reason why user winds up..."

when a drive is to be shared across differing operating systems

Wide of the mark for this rc1 topic but, yeah, for cross-platform users the merit of "LiveUsbStorage" directories is diminished by having them located on ext3-formatted media.

our live-usb-maker-gui now has a "dd" mode

The point of feedback here: users probably need "dd mode" to include an intermediate step, providing an opportunity to repartition the target device.

Posted: **Wed Dec 13, 2017 6:48 am**

How much space on HDD is MX-17 to use?
Have barely anything more installed and it shows 17.8G of 24G:
https://snag.gy/M2i5lY.jpg

Posted: **Wed Dec 13, 2017 6:52 am**

danielson wrote:How much space on HDD is MX-17 to use?
Have barely anything more installed and it shows 17.8G of 24G:
https://snag.gy/M2i5lY.jpg

There is an error in the conky label. That is giving space free, not used. It will be corrected.

Posted: **Wed Dec 13, 2017 6:53 am**

That has been corrected and uploaded, will show in the next update.

Posted: **Wed Dec 13, 2017 7:18 am**

m_pav wrote:I still prefer unetbootin because dd mode causes an entire flash drive to become completely useless for any other operation, which is a terrible waste when using 16, 32 & 64GB drives, or when a drive is to be shared across differing operating systems.

Ya i agree with you if we play with dd command it will totally mess with the system i prefer unetbootin i think mx 17 it is not there

i should install it from repos i think

Posted: **Wed Dec 13, 2017 7:22 am**

Unetbootin has usually been a failure for me, and many others. And it should remain out of MX default apps in my opinion. Those who want it can always get it from the repos.

Posted: **Wed Dec 13, 2017 7:33 am**

richb wrote:Unetbootin has usually been a failure for me, and many others. And it should remain out of MX default apps in my opinion. Those who want it can always get it from the repos.

just saw LIVE USB MAKER in MX linux is it also useful to burn iso's

Posted: **Wed Dec 13, 2017 7:34 am**

skidoo wrote:The point of feedback here: users probably need "dd mode" to include an intermediate step, providing an opportunity to repartition the target device.

interesting. dd usually wipes out partitions. is there something that needs zeroed out of something?

Posted: **Wed Dec 13, 2017 7:39 am**

vamsi wrote:
richb wrote:Unetbootin has usually been a failure for me, and many others. And it should remain out of MX default apps in my opinion. Those who want it can always get it from the repos.
just saw LIVE USB MAKER in MX linux is it also useful to burn iso's

Live USB Maker creates Live USB thumb drives from MX and antiX isos. It does not usually work for other OS's. That is why dd was added as an option.

Posted: **Wed Dec 13, 2017 7:54 am**

richb wrote:
vamsi wrote:
richb wrote:Unetbootin has usually been a failure for me, and many others. And it should remain out of MX default apps in my opinion. Those who want it can always get it from the repos.
just saw LIVE USB MAKER in MX linux is it also useful to burn iso's
Live USB Maker creates Live USB thumb drives from MX and antiX isos. It does not usually work for other OS's. That is why dd was added as an option.

dd the CLI package has always been around.

However, the new MX live usb maker has an option to run dd via GUI, which will detect the device number for your USB drive, so that you don't accidentally wipe out your hard drive by naming the wrong device in your dd commands in terminal.

Posted: **Wed Dec 13, 2017 8:46 am**

Still looking good.

RC1 still stable after one and a half days under kernel 4.10 (the antix kernel).
So far encouraging, the 4.13 kernel crashed twice the first day.

Posted: **Wed Dec 13, 2017 9:03 am**

Jerry3904 wrote:That has been corrected and uploaded, will show in the next update.

Great!

Odd though, file manager shows 19.1G free while conky says 17.7G.

Wonderful looking Conky btw! :)

Posted: **Wed Dec 13, 2017 9:12 am**

Re: BCM4356 firmware issue:
Xubuntu, MX & Debian all have exactly the same firmware files for that chipset. There is an extra file, brcmfmac4356-pcie.bin.txt that is used just for some chromebook type computers (including the GPD piwadam has). It is specific to that particular configuration and is not generally applicable to other BCM4356 devices.
It is included with the operating systems that come installed on those notebooks, and in the the GPD specific Ubuntu respins.
Since it would likely cause problems with other, more common, BCM4356 wifi adapters this is not something we should include.

Posted: **Wed Dec 13, 2017 10:03 am**

danielson wrote:[...]

Odd though, file manager shows 19.1G free while conky says 17.7G.

Wonderful looking Conky btw! :)

Probably due to Conky showing GiB and Thunar showing GB

Posted: **Wed Dec 13, 2017 11:41 am**

re: unetbootin, always used that. I can never get the mx one to work properly *shrug*

Ah well, it is easy enough to install the thing afterward :)

Posted: **Wed Dec 13, 2017 11:45 am**

Eadwine Rose wrote:re: unetbootin, always used that. I can never get the mx one to work properly *shrug*

Ah well, it is easy enough to install the thing afterward :)

Even for MX isos? That surprises me. For other OS's I can understand that unless you use the dd option in the GUI.

Posted: **Wed Dec 13, 2017 11:47 am**

Yep. I only make MX isos, don't use anything else (windows at work, but that's it).

Posted: **Wed Dec 13, 2017 2:23 pm**

Liking the RC very much. No issues to report. Thanks to the team.

Posted: **Wed Dec 13, 2017 4:06 pm**

I tried the MX 17-rc release and the one big problem I've run into is trying to work with Snap packages. The snapd package is in the repos, but when I install it, Snap fails to work. Any operation (snap find, snap install, etc) results in an error saying the server at a localhost cannot be contacted. Looks like the default Snap repo is probably not enabled.

Posted: **Wed Dec 13, 2017 4:18 pm**

newguy wrote:I tried the MX 17-rc release and the one big problem I've run into is trying to work with Snap packages. The snapd package is in the repos, but when I install it, Snap fails to work. Any operation (snap find, snap install, etc) results in an error saying the server at a localhost cannot be contacted. Looks like the default Snap repo is probably not enabled.

boot in systemd mode thru the advanced menu. systemd is requird to be running for snap to operate.

I have run snap packages this way.

Posted: **Wed Dec 13, 2017 5:39 pm**

I should add that to the next Manual

Posted: **Thu Dec 14, 2017 4:19 am**

Live USB Maker creates Live USB thumb drives from MX and antiX isos. It does not usually work for other OS's

About a year ago, my testing indicated otherwise. For isohybrid ISOs distributed by other distros, Live USB Maker created a bootable pendrive for all except one (11of12 tested? or 9of10?). FWIW, I only tested "legacy boot" (not efi) and after posting or PMing to report successes, I did not keep copies-to-self notes.

The point of feedback here:
users probably need "dd mode" to include an intermediate step, providing an opportunity to repartition the target device.
interesting. dd usually wipes out partitions. is there something that needs zeroed out of something?

Yah, my sleepy brain needs zeroed out (or something!)
do-over:
"probably need an alternative to dd mode, one which provides an opportunity to repartition the target device."
(to accommodate use with ISOs from other distros, ability to choose partition labels, e.g. "casper-rw" or "persistence" would also be desirable)

Posted: **Thu Dec 14, 2017 5:12 am**

skidoo wrote:
Live USB Maker creates Live USB thumb drives from MX and antiX isos. It does not usually work for other OS's
About a year ago, my testing indicated otherwise. For isohybrid ISOs distributed by other distros, Live USB Maker created a bootable pendrive for all except one (11of12 tested? or 9of10?). FWIW, I only tested "legacy boot" (not efi) and after posting or PMing to report successes, I did not keep copies-to-self notes.

Here's your post: viewtopic.php?p=397035#p397035
Looks like Refracta and Sparky worked. These are Devuan/Debian-based distros.

Same here, about a year ago, I tested MX Live USB maker with a few isos.

My post: viewtopic.php?p=398694#p398694

live-usb-maker:

It doesn't seems to work for all iso images, which I guess might be due to how a distro creates their iso.

1. slackel Openboxlive -- size =900+ MB -- when I tried to write it using l-u-m, it told me fat partition was not big enough, and stopped writing
2. peppermint: size=1.1 GB -- was able to write. Unable to boot using legacy USB option but when I chose the UEFI USB option from the boot order list, it booted up just fine
3. manjaro: size=1.6GB -- when I tried to write it using l-u-m, it told me fat partition was not big enough, and stopped writing

Based on the above, it might be that LUM works best with Debian/Ubuntu-based distros? It certainly isn't the iso file size since peppermint was larger than slackel.

In each case, I used the same 8GB thumb drive, wiped it clean, redid the partition table (msdos), and formatted the whole thumb drive as a single partition fat32 before running lum.

Bitjam's reply:

viewtopic.php?p=399002#p399002

It was designed to work with MX and antiX only/mostly. It creates a /root/.config/live-usb-maker/live-usb-maker.conf config file that could be altered to make it work with other distros. The idea was to do a good job with antiX and MX and try to make it flexible enough so people could easily tailor it for some/many other distros.

For example, cloning a running live system is only going to work for antiX and its decedents. But you might be able to get it to work with other distros by editing the config file.

In PM, he said that I could access live usb maker via CLI and change the size of the fat partition.

We make a small fat partition and copy over the /EFI and /boot directories to it. This allows the live-usb to boot via UEFI while still use an ext4 partition for the main live-usb. Our combined /EFI and /boot directories take only 14 Meg so I used 50 Meg as the default size for the fat partition.

The line to change in the config file is:

Code: Select all
FAT_SIZE="50"

I should probably make that size adapt automatically to what is needed. I didn't because I haven't run into this issue before.

You can adjust the size of the fat partition with the --esp-size=xx option where xx is the size in MiB.

I also pushed a small change that makes the size of the fat partition increase automatically if it is too small.

Unfortunately I don't think I ever got the time to test that solution.

But it looks possible in the case of Ubuntu and Debian-based distros.

Posted: **Thu Dec 14, 2017 5:14 am**

Congratulations, I like the desktop and the default Conky.
Vacation time is now past and catching up.

Code: Select all

 inxi -Fxz
System:    Host: mx17rc1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 gcc: 6.3.0
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01 serial: N/A
           Mobo: Dell model: 0H3MT5 v: A00 serial: N/A BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 53.5 Wh 78.5% condition: 68.2/99.9 Wh (68%)
           model: LGC-LGC3.0 DELL J7KGM29 status: Discharging
CPU:       Dual core Intel Core i5-3320M (-MT-MCP-) arch: Ivy Bridge rev.9 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10365
           clock speeds: max: 3300 MHz 1: 2591 MHz 2: 2591 MHz 3: 2591 MHz 4: 2591 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
           Card-2: NVIDIA GF108GLM [NVS 5200M] bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.2 )
           drivers: modesetting,nouveau (unloaded: fbdev,vesa)
           Resolution: 1600x900@59.99hz
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile
           version: 3.3 Mesa 13.0.6 Direct Render: Yes
Audio:     Card Intel 7 Series/C216 Family High Def. Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-amd64
Network:   Card-1: Intel 82579LM Gigabit Network Connection
           driver: e1000e v: 3.2.6-k port: f060 bus-ID: 00:19.0
           IF: eth0 state: down mac: <filter>
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi bus-ID: 03:00.0
           IF: wlan0 state: down mac: <filter>
Drives:    HDD Total Size: 120.0GB (7.6% used)
           ID-1: /dev/sda model: SSD2SC120G1CS175 size: 120.0GB
Partition: ID-1: / size: 106G used: 4.3G (5%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 54.0C mobo: N/A gpu: 50.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 193 Uptime: 5 min Memory: 377.1/7892.7MB
           Init: SysVinit runlevel: 5 Gcc sys: 6.3.0 Client: Shell (bash 4.4.121) inxi: 2.3.53

Posted: **Thu Dec 14, 2017 5:42 am**

skidoo wrote:
Live USB Maker creates Live USB thumb drives from MX and antiX isos. It does not usually work for other OS's
About a year ago, my testing indicated otherwise. For isohybrid ISOs distributed by other distros, Live USB Maker created a bootable pendrive for all except one (11of12 tested? or 9of10?). FWIW, I only tested "legacy boot" (not efi) and after posting or PMing to report successes, I did not keep copies-to-self notes.

Experiences vary. Perhaps I should have said some instead of most. I had problems with Netrunner and Kubuntu, I do not recall which versions.

Posted: **Thu Dec 14, 2017 6:01 am**

Do we have kind of regional settings here in xfce? (not just locale)
Both LibreOffice 5.4.3.2 40m0(Build:2) and OnlyOffice show letter as default paper size. Inches as units.

Posted: **Thu Dec 14, 2017 6:57 am**

Can we Expect MX -17 by christmas as christmas gift

Posted: **Thu Dec 14, 2017 7:00 am**

vamsi wrote:Can we Expect MX -17 by christmas as christmas gift

Santa does not reveal his secrets. But the elfs are planning on it. (Or is it elves?)

Posted: **Thu Dec 14, 2017 7:05 am**

richb wrote:
vamsi wrote:Can we Expect MX -17 by christmas as christmas gift
Santa does not reveal his secrets. But the elfs are planning on it. (Or is it elves?)

Ya

Posted: **Thu Dec 14, 2017 9:12 am**

Most importantly, have you been nice?

Posted: **Thu Dec 14, 2017 10:52 am**

ChrisUK wrote:Firstly, great work on MX17 - used the RC since release... only 2 minor problems:

CD/DVDs aren't detected unless I load them using something like VLC to attempt to play the content. To be clear, nothing shows up in Thunar until loaded by VLC.

Also, resume from suspend is unpredictable - sometimes just get a black screen; only way around it is login to TTY1 (CTRL-ALT-F1) and then TTY7 (CTRL-ALT-F7) gets the Desktop back.

I'm not on MX17 ATM, as I'm updating Manjaro.
Code: Select all
System:    Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.RC1_x64 Horizon December 10, 2017
Machine:   Device: laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 serial: N/A
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: N/A
           BIOS: Phoenix v: 03PA.M001.20110312.XW date: 03/12/2011
Battery    BAT1: charge: 9.7 Wh 100.0% condition: 9.7/47.5 Wh (20%)
CPU:       Dual core Intel Core i3 M 380 (-MT-MCP-) speed/max: 1066/2533 MHz
Graphics:  Card: NVIDIA GT218M [GeForce 315M]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@59.99hz
           OpenGL: renderer: Gallium 0.4 on NVA8 version: 3.3 Mesa 13.0.6
Network:   Card-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter driver: wl
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 250.1GB (53.5% used)
Info:      Processes: 198 Uptime: 1:36 Memory: 735.8/5832.7MB Client: Shell (bash) inxi: 2.3.53 
EDIT: I've switched to the 4.9 series Kernel as it works fine with my hardware... both of the above problems occur with the later Kernels too

Just an update:

No need to actually login to TTY1 on resume, just activate TTY1 then switch to TTY7 (so just do CTRL-ALT-F1 then CTRL-ALT F7. Not happening often though, and it's not a problem for me.

After installing all of the programs that I use daily, and setting everything up to suit me, I'm very happy with the result. Some nice touches here and there by the devs, it's the attention to detail that makes a Distro stand out from the crowd... again, nice work

Posted: **Thu Dec 14, 2017 1:26 pm**

Just watched this video MX-17 build Compiz Reloaded
https://www.youtube.com/watch?v=rJwhGehfey8
will it cause any instability if i do this??

Thanks..

Posted: **Thu Dec 14, 2017 1:38 pm**

Compiz is available in the MX Package installer, no need to build anything, I have been using it since beta 2 without a problem.

Posted: **Thu Dec 14, 2017 1:56 pm**

As a rule of thumb if you look for a program try first to see if it's available in MX Package (either under Popular Application tab, or under Full App Catalog: either Stable or MX Test Repo). If it's not there you can make a request to our packagers and they are usually very quick to add a build to MX Test Repo (if possible, depending on the app).

Posted: **Thu Dec 14, 2017 2:04 pm**

richb wrote:Compiz is available in the MX Package installer, no need to build anything, I have been using it since beta 2 without a problem.

i think it is bit outdated ..

Posted: **Thu Dec 14, 2017 2:09 pm**

richb wrote:Compiz is available in the MX Package installer, no need to build anything, I have been using it since beta 2 without a problem.

hmm.. actually there is difference between compiz and compiz related

http://www.pclinuxos.com/forum/index.php?topic=138878.0
https://www.reddit.com/r/linuxmasterrac ... ining_the/

and compiz reloaded is under development it seems
https://github.com/compiz-reloaded

Posted: **Thu Dec 14, 2017 2:11 pm**

vamsi wrote:
richb wrote:Compiz is available in the MX Package installer, no need to build anything, I have been using it since beta 2 without a problem.
i think it is bit outdated ..

Isn't the compiz in MXPI actually the revived Compiz Reloaded, ie, 0.8.14? I think that was the reason behind Stevo packaging this in MXPI.

Version 0.9 doesn't seem as popular as Reloaded.

And it's better to just do the one-click install from MXPI Popular Apps tab. There was no need to try to figure out which of the many compiz packages were needed or part of the same version.

Posted: **Thu Dec 14, 2017 2:13 pm**

vamsi wrote:
richb wrote:Compiz is available in the MX Package installer, no need to build anything, I have been using it since beta 2 without a problem.
i think it is bit outdated ..

It is 2.08.14. The latest stable version is 2.08.8 The 2.09 versions are listed as unstable.It is completely functional with all the goodies that are needed.

The 0.9.x versions up to 0.9.5 were seen as unstable/beta software.
Compiz Reloaded[edit]
A group[28] forked the Compiz 0.8 series code base and modernized it and maintains it as of 2017

https://en.wikipedia.org/wiki/Compiz

Posted: **Thu Dec 14, 2017 2:21 pm**

richb wrote:
vamsi wrote:
richb wrote:Compiz is available in the MX Package installer, no need to build anything, I have been using it since beta 2 without a problem.
i think it is bit outdated ..
It is 2.08.14. The latest stable version is 2.08.8 The 2.09 versions are listed as unstable.It is completely functional with all the goodies that are needed.

The 0.9.x versions up to 0.9.5 were seen as unstable/beta software.
Compiz Reloaded[edit]
A group[28] forked the Compiz 0.8 series code base and modernized it and maintains it as of 2017
https://en.wikipedia.org/wiki/Compiz

okay how about adding unstable version to MX Test Repo

Posted: **Thu Dec 14, 2017 2:26 pm**

vamsi wrote:
richb wrote:
vamsi wrote:

It is 2.08.14. The latest stable version is 2.08.8 The 2.09 versions are listed as unstable.It is completely functional with all the goodies that are needed.

https://en.wikipedia.org/wiki/Compiz
okay how about adding unstable version to MX Test Repo

In my opinion we should not put unstable versions of Compiz in our test repo. They are still under development. Also I see no reason to do so.

Posted: **Thu Dec 14, 2017 2:33 pm**

@vamsi:

okay how about adding unstable version to MX Test Repo

Pls read the wiki link on compiz that richb provided.

- 0.8 series is Reloaded, the one you were so excited about in the youtube link. It is still maintained. It is so easily installed via the Popular Apps tab of MXPI ("window managers" category).
- unstable version is the unpopular 0.9 series that doesn't seem very well used.
- this request is not feedback on the RC
- this is a potential package request, so please post in the correct place and you can try to persuade the packaging team as to why version 0.9 should be packaged.

Posted: **Thu Dec 14, 2017 3:30 pm**

asqwerth wrote:@vamsi:

okay how about adding unstable version to MX Test Repo
Pls read the wiki link on compiz that richb provided.

- 0.8 series is Reloaded, the one you were so excited about in the youtube link. It is still maintained. It is so easily installed via the Popular Apps tab of MXPI ("window managers" category).
- unstable version is the unpopular 0.9 series that doesn't seem very well used.
- this request is not feedback on the RC
- this is a potential package request, so please post in the correct place and you can try to persuade the packaging team as to why version 0.9 should be packaged.

understood!

Posted: **Thu Dec 14, 2017 4:01 pm**

i thought I explained the differences and reasons for the packaging in the compiz-reloaded thread at the start...

The 0.9 series removes many plugins and features. Is that what you want?

Posted: **Thu Dec 14, 2017 4:42 pm**

Stevo wrote:i thought I explained the differences and reasons for the packaging in the compiz-reloaded thread at the start...

The 0.9 series removes many plugins and features. Is that what you want?

oops i didn't saw it

Posted: **Fri Dec 15, 2017 11:11 pm**

Stevo wrote:You can get a lock screen for security if coming back from suspend2ram, suspend2disk, or just screen blanking by just installing light-locker. The lock screen setting is in power management settings. I think we should have light-locker installed by default, perhaps the high-security settings remain as they are.

How can I turn-off the lock screen entirely? When I set Xfce Power Manager to Suspend using the laptop power button or when laptop lid is closed (battery and plugged in), I get a screen lock on resume. I also get the lock screen with the "Switch off display" selection.

"The Xfce Power Manager Security "Lock screen when system is going for sleep" box is NOT checked in the "System" tab. Is this check box bugged?

When I suspend using the Whisker menu Log Out button, MX-17 resumes without the lock screen, which is the desired behavior.

Thanks for any suggestions!

Update:

I no longer have the problem. ("Lock screen when system is going for sleep" box now works.) I'm nearly 100% sure that the unchecked state of the box started to function correctly immediately after I enabled a screensaver for the first time in "Screensaver." (I enabled the screensaver on a hunch that it might affect the lock screen behavior.) Now I can even disable the the screensaver and the state of the box correctly controls the lock screen option. I've attempted to change and toggle numerous related settings and have not been able to duplicate the bug.

Posted: **Sat Dec 16, 2017 6:17 am**

Eadwine Rose wrote:Another one is I have to be root to power off the system?

*scratches head*

Lifting this to the top, it happens on the new MX17 final install as well.

Only once though after a fresh install, once you have rebooted it's gone.

So weird.

I cannot reproduce since I have rebooted, but when I am all done tweaking and fiddling I can see with another drive what it does and try some things out with someone if you want.

Posted: **Sun Dec 17, 2017 3:47 am**

I never saw a final answer as to whether those with a well-running MX17 Rc1 need to to a full reinstall to final. If we are doing well on RC1 can we just do the dist-upgrade and sail along? I don't mind missing a few small tweaks to graphics or something like that.

Posted: **Sun Dec 17, 2017 4:15 am**

From Adrian 10 Dec

"If this is not a FAQ I don't know what is... we should probably post the response in the announcement too.
RCs will update to Final (at least that what we did in the past)."

Posted: **Sun Dec 17, 2017 4:16 am**

nathan2423 wrote:I never saw a final answer as to whether those with a well-running MX17 Rc1 need to to a full reinstall to final. If we are doing well on RC1 can we just do the dist-upgrade and sail along? I don't mind missing a few small tweaks to graphics or something like that.

Have a look here

Posted: **Sun Dec 17, 2017 8:10 am**

Thank you!

Posted: **Sun Dec 17, 2017 10:25 am**

Thank you all for feedback. I think it's probably time to close this thread since it's about the version before the official release. We should continue the discussions in the feedback thread for the MX-17 release.

Posted: **Sun Dec 17, 2017 10:33 am**

Adrian wrote:Thank you all for feedback. I think it's probably time to close this thread since it's about the version before the official release. We should continue the discussions in the feedback thread for the MX-17 release.

Done

Posted: **Fri Dec 22, 2017 2:25 pm**

A user posted on FB that snap can be run without rebooting into systemd with the following command:

Code: Select all

sudo /usr/lib/snapd/snapd &

MX Linux Forum

MX-17 Release Candidate 1 - Feedback

MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback

Re: MX-17 Release Candidate 1 - Feedback