MX Linux Forum

Posted: **Mon Nov 06, 2017 8:18 am**

MX-17 beta 1 images are now available for download and testing.

direct download:

https://sourceforge.net/projects/mx-lin ... X17/beta1/

torrents:
32bit http://linuxtracker.org/download.php?id ... rent&key=0

64bit http://linuxtracker.org/download.php?id ... rent&key=0

The beta 1 features the following :

latest live system changes and fixes from the antiX project

the latest updates from debian (stretch)

4.9.0-4 kernels (alphas featured 4.9.0-3)

the 32 bit iso has a PAE kernel. The non-pae has been removed.

updated packages, including libreoffice 5.4.1

new and updated mx-apps

mx-tweak replaces mx-defaultlook and provides one-stop spot for simple compositor (Xfce or Compton), panel, and other "tweak" type changes

mx-conky provides a method for doing simple edits to conky files (color changes, etc...)

mx-network-assistanct replaces mx-broadcom-manager as a general purpose network troubleshooting tool.

mx-tools now has a larger interface

changes to the update mananger (apt-notifier), including new themes available in preferences

misc. changes to most of the other mx-apps

the applications menu now has a mx-tools submenu to help organize the menu a little bit.

gthumb replaces shotwell and mirage (both still available in mx-packageinstaller)

featherpad, a qt-based text editor with tabbed interface and code markup, replaces leafpad.

new art work and icons (current wallpaper is not final, just being used for beta 1 release)

several pre-packaged conky configurations (see conky-manager to change and select)

Known Issues

The manual has not yet been updated for MX-17.

Translations are not yet complete for the new mx-apps and some are still being updated.

Some testers during alpha reported shutdown problems when using the encrypted home option. We have included a fix, but it has received limited testing.

Please post conky comments here: The MX-17 conkies

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

Thank you!

Dolphin Oracle (on behalf of the MX dev team).

Posted: **Mon Nov 06, 2017 9:05 am**

remastercc can't end, after 100% progress, endless running. i haven't cancel it yet, it is still running for 20 mins as i wrote this. maybe i use becoz yumi multi-boot live on usb but mx16.1 don't have any problem with remastercc.

Posted: **Mon Nov 06, 2017 9:13 am**

@stsoh, please make a copy of /var/log/live/live-remaster.log and attach it. We had one report of this problem in antiX-17 but the devs were not able to reproduce it.

Posted: **Mon Nov 06, 2017 9:17 am**

BitJam wrote:@stsoh, please make a copy of /var/log/live/live-remaster.log and attach it. We had one report of this problem in antiX-17 but the devs were not able to reproduce it.

@BitJam - just so you know, the live-remaster script is the same as what's on the antiX github, so hopefully we can solve this for both systems.

Posted: **Mon Nov 06, 2017 10:23 am**

attached live-remaster.log

Posted: **Mon Nov 06, 2017 11:38 am**

During Alpha testing, there was a problem where installing with 'home' encryption prevented normal shutdown completion, hanging at 'Stopping remaining crypto disks...'.

This was resolved, and I tested the fix successfully. However, I've just installed Beta 1 on two machines, enabling 'home' encryption, and the failure to shutdown has returned.

One of the machines was the one I used to successfully test this in Alpha, so I don't think it's a hardware issue.

Chris

Posted: **Mon Nov 06, 2017 12:02 pm**

@chrispop99, there is a bug in the sendsigs script that was released. Please edit /etc/init.d/sendsigs as root and change line 34 to:

Code: Select all

    for pid in $(pgrep "$PROTECT_LIST"); do

(remove the "-f")

Posted: **Mon Nov 06, 2017 12:16 pm**

dang it, grabbed the wrong ones.... noted for b2.

Posted: **Mon Nov 06, 2017 12:52 pm**

When will beta1 or beta2 be public betas?
Available for download, testing, and reports?

Posted: **Mon Nov 06, 2017 12:57 pm**

entropyfoe wrote:When will beta1 or beta2 be public betas?
Available for download, testing, and reports?

its public now, in the wide open.

Posted: **Mon Nov 06, 2017 1:02 pm**

Where to download?
The notice at the top of the board...

MX-17 beta 1 release info hereMX-17 beta 1 release info here

When I click...
Says I am not authorized to view that forum.

Now I have my antix 17 back up and running, I am ready for a new testing session.

Posted: **Mon Nov 06, 2017 1:04 pm**

ok that's weird.

Here's the blog post with the announcement info .

https://mxlinux.org/mx-17-beta-1

Posted: **Mon Nov 06, 2017 1:13 pm**

Thanks, I will download and test.
Hopefully tonight. I have several machines I can test...

Posted: **Mon Nov 06, 2017 1:57 pm**

BitJam wrote:@chrispop99, there is a bug in the sendsigs script that was released. Please edit /etc/init.d/sendsigs as root and change line 34 to:
Code: Select all
    for pid in $(pgrep "$PROTECT_LIST"); do
(remove the "-f")

Yep, that's fixed it!

Chris

Posted: **Mon Nov 06, 2017 2:06 pm**

This isn't restricted to MX 17, but I scaled up the desktop icon size on the live session to see if the "Installer" text would stop being ellipsisized, plus I have an HDPI 1080 screen and like bigger icons, and the installer icon changed to a generic text icon. So it's not scalable. I don't know what's a better solution, an SVG icon or pngs in a range of sizes.

Posted: **Mon Nov 06, 2017 2:13 pm**

Stevo wrote:This isn't restricted to MX 17, but I scaled up the desktop icon size on the live session to see if the "Installer" text would stop being ellipsisized, plus I have an HDPI 1080 screen and like bigger icons, and the installer icon changed to a generic text icon. So it's not scalable. I don't know what's a better solution, an SVG icon or pngs in a range of sizes.

semi-related - mx-tweak now has a function for allowing longer file names on the desktop (no ellipses).

Posted: **Mon Nov 06, 2017 2:14 pm**

Which way should I look at with my wifi network manager connection failure.
(details are viewtopic.php?f=77&t=43184)
Has new mx-network-assistant anything to do with it?

Posted: **Mon Nov 06, 2017 2:19 pm**

Sorry, we've been pretty busy with the new release and haven't had time to get back to your question.

The MX Network Assistant is not causing it, if that's what you mean. That screenshot was confusing, though, since it showed nothing at all yet you say the hardware is working.

Can you show us a bit more with these as regular user:

Code: Select all

lsusb | grep -i net
lspci | grep -i net

and this as root:

Code: Select all

iwconfig

Posted: **Mon Nov 06, 2017 2:53 pm**

'dmesg | tail' gives interesting sequence on that issue like
send auth to ...
authenticated
aborting authentication with ... by local choice (Reason: 3=DEAUTH_LEAVING)

Thanks to D_O
it works with workaround https://github.com/qca/open-ath9k-htc-f ... issues/132

Posted: **Mon Nov 06, 2017 3:13 pm**

That is interesting and, if you do a web search on the error message (3=DEAUTH_LEAVING), there are hits all over on it. Here's a couple to look at:

https://ubuntuforums.org/showthread.php?t=2259037
https://superuser.com/questions/974017/ ... then-drops

I don't know enough about this to help much more, but others here probably do.

Posted: **Mon Nov 06, 2017 3:29 pm**

Have admit, I have no idea how to fix the error. See attachment.
Installed to a SSD.

Code: Select all

 inxi -Fxz
System:    Host: mx17b1 Kernel: 4.9.0-4-amd64 x86_64 bits: 64 gcc: 6.3.0
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: MX-17.b1_x64 Horizon November 6, 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: 99.9 Wh 145.4% condition: 68.7/99.9 Wh (69%)
           model: LGC-LGC3.0 DELL J7KGM29 status: Full
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) arch: Ivy Bridge rev.9 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10366
           clock speeds: max: 3300 MHz 1: 1242 MHz 2: 1512 MHz 3: 1392 MHz 4: 1253 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.9.0-4-amd64
Network:   Card-1: Intel 82579LM Gigabit Network Connection
           driver: e1000e v: 3.2.6-k port: f060 bus-ID: 00:19.0
           IF: eno1 state: down mac: <filter>
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: up 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.4G (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: 49.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 203 Uptime: 5 min Memory: 956.7/7893.3MB
           Init: SysVinit runlevel: 5 Gcc sys: 6.3.0 Client: Shell (bash 4.4.121) inxi: 2.3.43

Posted: **Mon Nov 06, 2017 3:38 pm**

@Shay2, I'm not certain but there may be a bug in the installer if you pick the user name "demo". It's possible this was fixed a while ago. Or it may just be a figment of my imagination.

Posted: **Mon Nov 06, 2017 4:11 pm**

dolphin_oracle wrote:
Stevo wrote:This isn't restricted to MX 17, but I scaled up the desktop icon size on the live session to see if the "Installer" text would stop being ellipsisized, plus I have an HDPI 1080 screen and like bigger icons, and the installer icon changed to a generic text icon. So it's not scalable. I don't know what's a better solution, an SVG icon or pngs in a range of sizes.
semi-related - mx-tweak now has a function for allowing longer file names on the desktop (no ellipses).

Yes, I was testing that, but they still get truncated if the icon is too small, so that's why the scaling up.

Posted: **Mon Nov 06, 2017 4:13 pm**

@ BitJam
Not the name I used. Was sure surprised to see it pop up whenever I boot up or reboot.

Posted: **Mon Nov 06, 2017 4:16 pm**

Shay2 wrote:@ BitJam
Not the name I used. Was sure surprised to see it pop up whenever I boot up or reboot.

did you "save home changes" when you installed? and what app is that?

Posted: **Mon Nov 06, 2017 4:25 pm**

Installer does some string replacements when it renames demo to whatever name the users chooses, I wonder if it fails for blueman-services.

Posted: **Mon Nov 06, 2017 4:28 pm**

@shay2, in your home directory try running this command and see if anything interesting shows up:

Code: Select all

grep demo $(find . -type f)

My guess is something got configured when you were running live, the configuration hard coded "/home/demo" in a file and now it is giving you trouble. The above command might point us to the configuration file.

Posted: **Mon Nov 06, 2017 4:40 pm**

Code: Select all

$ grep demo $(find . -type f)
grep: ./.mozilla/firefox/Crash: No such file or directory
grep: Reports/InstallTime20171024165158: No such file or directory
grep: ./.conky/MX-TeejeeTech/CPU: No such file or directory
grep: Panel: No such file or directory
grep: (2-core).jpg: No such file or directory
grep: ./.conky/MX-TeejeeTech/CPU: No such file or directory
grep: Panel: No such file or directory
grep: (6-core): No such file or directory
grep: ./.conky/MX-TeejeeTech/Process: No such file or directory
grep: Panel.jpg: No such file or directory
grep: ./.conky/MX-TeejeeTech/CPU: No such file or directory
grep: Panel: No such file or directory
grep: (6-core).jpg: No such file or directory
grep: ./.conky/MX-TeejeeTech/Process: No such file or directory
grep: Panel: No such file or directory
grep: ./.conky/MX-TeejeeTech/CPU: No such file or directory
grep: Panel: No such file or directory
grep: (2-core): No such file or directory
grep: ./.conky/MX-TeejeeTech/CPU: No such file or directory
grep: Panel: No such file or directory
grep: (4-core): No such file or directory
grep: ./.conky/MX-TeejeeTech/CPU: No such file or directory
grep: Panel: No such file or directory
grep: (4-core).jpg: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/bg.png: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/SysInfo: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/SysInfo.png: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/bg2.png: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/Clock.png: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/fonts/Caviar_Dreams.ttf: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/fonts/Caviar_Dreams_Bold.ttf: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/Clock: No such file or directory
grep: ./.conky/MX-Torn: No such file or directory
grep: Paper: No such file or directory
grep: Clone/source.txt: No such file or directory
grep: ./.conky/MX-Asq/infini/Creative: No such file or directory
grep: Commons: No such file or directory
grep: Attribution-No: No such file or directory
grep: Derivative: No such file or directory
grep: Works.txt: No such file or directory
grep: ./.conky/MX-Asq/MX-Clock/infini/Creative: No such file or directory
grep: Commons: No such file or directory
grep: Attribution-No: No such file or directory
grep: Derivative: No such file or directory
grep: Works.txt: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/conkyrc2core: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/weather: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/weather_raw: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/conkyrc2core.png: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/clock01_rings.lua: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/fonts/AvantGarde_LT_Medium.ttf: No such file or directory
grep: ./.conky/MX-core: No such file or directory
grep: blue/fonts/Radio_Space.ttf: No such file or directory
Binary file ./.cache/mozilla/firefox/v1ja4c0v.default/cache2/entries/C3BE29F53D0514D14F659CF4CE5E51338BC65568 matches
grep: ./.config/autostart/keyboard: No such file or directory
grep: switcher.desktop: No such file or directory
Binary file ./.config/dconf/user matches

Posted: **Mon Nov 06, 2017 4:54 pm**

Opps. I wasn't expecting spaces in file names. That's why there are so many error messages. This command should work better:

Code: Select all

 find .  -type f -print0 | xargs -0 grep demo

Coming at it from the other direction, did you ever try to connect a bluetooth device?

Posted: **Mon Nov 06, 2017 5:00 pm**

Blue tooth, never.

Code: Select all

$  find .  -type f -print0 | xargs -0 grep demo
Binary file ./.cache/mozilla/firefox/v1ja4c0v.default/cache2/entries/C3BE29F53D0514D14F659CF4CE5E51338BC65568 matches
./.bash_history:grep demo $(find . -type f)
Binary file ./.config/dconf/user matches

Posted: **Mon Nov 06, 2017 5:24 pm**

Started getting more errors, so I re-installed with Time Zone selected and did not save desktop changes.
I see no errors yet, which is nice.

Prefer antix conky. Much prefer it.

Posted: **Mon Nov 06, 2017 6:47 pm**

Prefer antix conky. Much prefer it.

You can use it on MX, of course. It'd be kind of interesting to see how it worked.

Posted: **Mon Nov 06, 2017 7:35 pm**

I am using mx 17beta1 LIVE HD in a specific partition. I do not have access as a common user to the folder / Live that is in the partition with a lot of space. The folder /home /demo / Live-usb-storage / is created automatically and is on the ram and is very small.
Please could you make SOMETHING in the iso so that you had permission to write, Thanks.

Posted: **Mon Nov 06, 2017 7:41 pm**

You can use it on MX, of course. It'd be kind of interesting to see how it worked

It worked great in prior version.

Posted: **Mon Nov 06, 2017 7:47 pm**

CaputAlista wrote:I am using mx 17beta1 LIVE HD in a specific partition. I do not have access as a common user to the folder / Live that is in the partition with a lot of space. The folder /home /demo / Live-usb-storage / is created automatically and is on the ram and is very small.
Please could you make SOMETHING in the iso so that you had permission to write, Thanks.

On a live usb, /home/dem/live-usb-storage accesses the remainder of the space on the device that the iso is created on.

How did you make your hd partiton into a live device?

Posted: **Mon Nov 06, 2017 7:56 pm**

title MX
rootnoverify (hd0,7) -----partition in external hd
find --set-root /win81/isos/MX.iso
map /win81/isos/MX.iso (0xff)
map --hook
kernel (hd0,7)/antiX/vmlinuz
initrd (hd0,7)/antiX/initrd.gz
boot

Posted: **Mon Nov 06, 2017 7:58 pm**

the initrd or vmlinuxz maybe configure the previlges

Posted: **Mon Nov 06, 2017 8:48 pm**

Actually you are booting a readonly file system. Basically a dvd on your disk. I doubt the live-usb storage feature is being enabled this way, which is why it shows up the way it does.

I honestly don't know how to deal with that. A frugal install onto your partition would be closer to what you want i think.

Posted: **Mon Nov 06, 2017 9:46 pm**

CaputAlista wrote:I am using mx 17beta1 LIVE HD in a specific partition. I do not have access as a common user to the folder / Live that is in the partition with a lot of space. The folder /home /demo / Live-usb-storage / is created automatically and is on the ram and is very small.
Please could you make SOMETHING in the iso so that you had permission to write, Thanks.

We allow you to boot directly from an iso file but as you are seeing, doing so disables almost all of our special features. The same restrictions would occur if you used "dd" to make a live-usb or if you booted from a live-dvd.

As dolphin_oracle said, you may be able to do a frugal install to that partition which would give you easy access to all of that space. If you have a usb stick handy then you should be able to use live-usb-maker (command line or gui) to clone your current live system to that usb stick and make it a live-usb. You will have all of the special features available on that live-usb. If you want them available on the hard drive then boot the live-usb and do a frugal install (via the F5 Persist menu in the legacy bootloader or via a text menu selection in the live uefi bootloader) to that partition. It should put everything it needs in a single directory on that partition with a name like "antiX-Frugal-4.9.0-4-amd64". It will boot directly into the frugal install when you do it. Better still, it will create a file called "grub.entry" in that directory that you can add to your grub.cfg to boot into the frugal install.

Summary:

Boot into your current MX-17.b1 system, insert a usb stick and run live-usb-maker
Boot from the live-usb you just created and do a frugal install to the HD partition.
Copy the file "grub.entry" file into your grub.cfg

You may even be able to do the frugal install directly when you boot your current MX-17.b1 system but we offer no guarantees that it will work.

Posted: **Mon Nov 06, 2017 10:49 pm**

Used the live-usb-maker in MX 16 to create a live USB from the x64 beta 1 iso.

My Acer E-15 E5-575G-53VG would not boot from this USB until I switched off UEFI and went to legacy boot, in contrast to MX 16, which had the liveUSB boot with both UEFI and Secure Boot enabled.

Once I got it to boot, I got the black error box on the GRUB wallpaper that Jerry showed. Escaping that, I got to the text screen where I could type "live", and then the boot proceeding normally. I installed to a 10 GB scratch partition. The installer icon scaled correctly here when I increased its size, so maybe that was a false alarm. I did not install GRUB, since I will use the GRUB from the main MX 16 install.

After rebooting to MX 16 and running update-grub, I rebooted MX 17 normally. It's running the modesetting driver for the Skylake 520 Intel video. As in stock MX 16, there is some video tearing when scrolling text in Firefox. The compositor makes no difference with this. If I can't get the tearfree option to work with a 20-intel.conf file using the modesetting driver, I'll try with the xorg intel 915 driver that fixed it in MX 16.

I see we are using the same predictable, yet complex, network interface names that standard Stretch is using.

Code: Select all

ifconfig -a

shows them if you have to let something know what interface to monitor.
I ran the Nvidia driver installer for the Optimus Nvidia graphics. After a reboot, "optirun inxi -G" showed that the Bumblebee switching was working (unlike some people on the Debian forum that had to go to a backports kernel to get it to work...maybe the kernel, maybe PEBKAC)

I also saw that the Nvidia settings program now shows up in the XFCE settings manager, and actually opens up without some obscure flags, unlike MX 16. However, if this creates an xorg.conf file that specifies Nvidia, that'll nuke my GUI, since Optimus uses the Intel GPU for display. I haven't tested that yet, but will do so soon.

Posted: **Mon Nov 06, 2017 11:29 pm**

@stevo, unfortunately, there are two versions of MX-17.b1_x64.iso. The live legacy bootloader (syslinux with gfxboot, not Grub) was fixed in the latest version so it sounds like you used the earlier version. I used live-usb-maker to make a live-usb from this iso file:

Code: Select all

b61af97f7a17032f70fef68a2626fb76  MX-17.b1_x64.iso

I was able to boot UEFI in secure boot mode on a Dell XPS-13 and on an Acer-ES1-511. The legacy syslinux bootloader also worked as expected on both systems.

Posted: **Tue Nov 07, 2017 3:25 am**

I tested the sendsigs fix on my finniky Lenovo E330 and got a clean shutdown. Before testing, I set my bios to EFI boot only, no legacy and had a blank un-initialised SSD to start with. Created a Beta 1 64-bit flash drive and booted without issue.

Install with auto-partition, encryption selected for /home and swap, grub installed to ESP, installation was very quick and rebooted to a nice clean desktop. Swapped out sendsigs and rebooted, no hanging at shutdown, rebooted cleanly every time. Rechecked 3 more times, no hangs at shutdown. Swapped back to the sendsigs provided with Beta1 and immediate hang on shutdown.

Contents of the diff output between the 2 sendsig files below

Code: Select all

16c16
< PROTECT_LIST="^(mount.|ntfs-3g|wpa_supplicant|udevd|systemd-udevd)"
---
> PROTECT_LIST="^(/sbin/mount.ntfs|mount.ntfs|mount.fuse|mount.cifs|ntfs-3g|/sbin/mount.ntfs-3g|rpcbind|/sbin/wpa_supplicant|udevd|systemd-udevd)"
30,40d29
< 
<     local live_prog full_live live_dir=/live
<     read live_dir 2>/dev/null < /etc/live/live-dir
<     for live_prog in live-umount umount-live; do
<         full_live=$live_dir/bin/$live_prog
<         [ -x $full_live ] || continue
<         # Don't use exec here so the rest of sendsigs code runs
<         $full_live --run-scripts </dev/console >/dev/console
<         break
<     done
< 
43c32
<     #pgrep  "$PROTECT_LIST"
---
>     #pgrep -f "$PROTECT_LIST"
45c34
<     for pid in $(pgrep "$PROTECT_LIST"); do
---
>     for pid in $(pgrep -f "$PROTECT_LIST"); do
48a38,47
>     echo "omit list: " $OMITPIDS
> 
> 	for omitfile in /run/sendsigs.omit; do
> 		if [ -e $omitfile ]; then
> 			for pid in $(cat $omitfile); do
> 				OMITPIDS="${OMITPIDS:+$OMITPIDS }-o $pid"
> 			done
> 		fi
> 	done
> 
89d87
<

Posted: **Tue Nov 07, 2017 3:30 am**

Remaster failure running from live-usb, I was trying to remaster the sendsigs into a bootable USB to see if that would help with accessing encrypted partitions from a live boot device.
I lost my logfile, but kept a screenshot.

Remaster-stall.png

Posted: **Tue Nov 07, 2017 3:35 am**

Grab handles on screen borders can be a bit hard to grab. Has the padding been applied as per earlier versions?

Posted: **Tue Nov 07, 2017 4:17 am**

m_pav wrote:Remaster failure running from live-usb,....

i had the same problem, highlighted earlier. apparently there two versions of mx17-b1 (mentioned by bitjam).
the mx17-b1 version, i downloaded is from sourceforge (had the same md5/sig as bitjam), the other must be either from mxlinux webpage or linuxtracker.

Posted: **Tue Nov 07, 2017 4:37 am**

Some feedbacks on MX 17 beta1

I tested quickly MX17 beta1 in VirtualBox, and here are my feedbacks. Not a lot of them, but the ones that jumped to my eyes.

1) There is no icons in LibreOffice by default. When you go to LibreOffice options and appearance section, you can read that icon theme is on "helpimg" by default.

2) I cannot install any single translation package using simplified MX installer applications. Terminal windows is opening, and no matter which repository I select (either stable or mx repo), nothing is done.

I had to use Synaptic and install missing packages by hand.

3) After mx update has finished its work, you can see a menu with all its options. You cannot exit it without clicking on quit option :(

I know this is not a big list, but besides this, I did not see or face any big bugs.

Hope it helps!

Have a good day.

Posted: **Tue Nov 07, 2017 5:01 am**

FredBezies wrote:Some feedbacks on MX 17 beta1

I tested quickly MX17 beta1 in VirtualBox, and here are my feedbacks. Not a lot of them, but the ones that jumped to my eyes.

1) There is no icons in LibreOffice by default. When you go to LibreOffice options and appearance section, you can read that icon theme is on "helpimg" by default.

2) I cannot install any single translation package using simplified MX installer applications. Terminal windows is opening, and no matter which repository I select (either stable or mx repo), nothing is done.

I had to use Synaptic and install missing packages by hand.

3) After mx update has finished its work, you can see a menu with all its options. You cannot exit it without clicking on quit option :(

I know this is not a big list, but besides this, I did not see or face any big bugs.

Hope it helps!

Have a good day.

Thanks!

was libreoffice set to "helpimg", or to "(automatic) helpimg"?

the default is supposed to be galaxy, which is what it is on my system here, but you are not the first person to report that particular bug.

***edit*** its a bug in libreoffice 5.4 series. (https://bugs.documentfoundation.org/sho ... ?id=108406) helpimg isn't even actually a theme.

Posted: **Tue Nov 07, 2017 6:03 am**

hellow Mr Bit jam. i am the guy that you help directly with initr file custom. In mx15 only create a directory live and the other version create live usb folder and live folder. But live usb folder has permission and live not. usb live folder is small. and if i download file is small.
mx 15 works.

Posted: **Tue Nov 07, 2017 6:07 am**

'Edit as Root' option is not working in thunar.
"Open root Thunar here' is functioning.

Posted: **Tue Nov 07, 2017 6:34 am**

dr-kart wrote:'Edit as Root' option is not working in thunar.
"Open root Thunar here' is functioning.

Confirmed. An oversight. Go to Edit>Configure Custom actions and double click on Edit as Root. Change leafpad to featherpad.

Posted: **Tue Nov 07, 2017 6:38 am**

Thanks, I confirm that. The custom action needs to be changed. Thunar > Edit > Configure custom actions. Click on the Edit as Root entry and the the pencil icon to edit, change "leafpad" to "featherpad"

Posted: **Tue Nov 07, 2017 6:47 am**

dolphin_oracle wrote:[reports]

Thanks!

was libreoffice set to "helpimg", or to "(automatic) helpimg"?

the default is supposed to be galaxy, which is what it is on my system here, but you are not the first person to report that particular bug.

***edit*** its a bug in libreoffice 5.4 series. (https://bugs.documentfoundation.org/sho ... ?id=108406) helpimg isn't even actually a theme.

It is (automatic) helpimg. And also this is not my theme on my archlinux installation. Nasty bug, indeed.

Posted: **Tue Nov 07, 2017 6:49 am**

FredBezies wrote:
dolphin_oracle wrote:[reports]

Thanks!

was libreoffice set to "helpimg", or to "(automatic) helpimg"?

the default is supposed to be galaxy, which is what it is on my system here, but you are not the first person to report that particular bug.

***edit*** its a bug in libreoffice 5.4 series. (https://bugs.documentfoundation.org/sho ... ?id=108406) helpimg isn't even actually a theme.
It is (automatic) helpimg. And also this is not my theme on my archlinux installation. Nasty bug, indeed.

thanks for confirming.

Posted: **Tue Nov 07, 2017 7:51 am**

Jerry3904 wrote:Thanks, I confirm that. The custom action needs to be changed. Thunar > Edit > Configure custom actions. Click on the Edit as Root entry and the the pencil icon to edit, change "leafpad" to "featherpad"

And custom actions are untranslated in MX for a long time (translations are available since at least 2015)

Posted: **Tue Nov 07, 2017 8:09 am**

Other French localization problems (tested LIVE) for the record:

1) during first part of boot, starts in FR but when that switch occurs text goes back to EN
2) FR flag appears in NA, but only one keyboard is activated so it should not appear
3) menu > MX Tools: Tweak has no name or description, Repo Manager no name, and Conky no description
4) the MX Tools Help buttons open the EN version in FF

Some of this we know about already

Posted: **Tue Nov 07, 2017 8:34 am**

For the FR keyboard stuff, output of the following commands would be helpfull.

Code: Select all

cat /etc/default/keyboard

grep XKBLAYOUT /etc/default/keyboard | grep ,

grep XkbDisable /home/$USER/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml |grep false

grep XkbVariant /home/$USER/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml |grep ,

grep XkbLayout /home/$USER/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml |grep ,

Posted: **Tue Nov 07, 2017 8:39 am**

There are many typos, missing translations (in fact existing but not integrated). I will try to make a summary if that can help.

Posted: **Tue Nov 07, 2017 8:47 am**

cyrilus31 wrote:There are many typos, missing translations (in fact existing but not integrated). I will try to make a summary if that can help.

feel free.

I should mention that in the case of the custom actions in thunar, Xfce does not have a built in way to provide localization of those items.

Posted: **Tue Nov 07, 2017 8:51 am**

One other thing on the FR LIVE screen: the menu items under some of the Functions listed at the bottom have "off" or "none" after FR selected and everything else switches.

Posted: **Tue Nov 07, 2017 10:20 am**

Jerry3904 wrote:Other French localization problems (tested LIVE) for the record:

1) during first part of boot, starts in FR but when that switch occurs text goes back to EN

Which switch? The custom antiX/MX part of the live boot should be translated but the Debian stuff is not. Perhaps this is what you are seeing.

Posted: **Tue Nov 07, 2017 10:34 am**

Looks very good so far ! At the level of a Warren Woodford beta.

I downloaded from source forge, the md5 was good. I then burned to a USB with the Antix tools.
The boot to the live session was smooth. All seemed to be working. eth0 detected and works OTB. Sound works OTB, without having to select the generic. Videos play in youtube. I could access my data drive, so I installed over my MX16.1 . It was fast fromthe USB.

All things above are still working. Samba picked up the window share, and I could log into that (with the windows password).
Sleep mode works and wakes up quickly. I updated grub, and the antix 17 install is picked up correctly, and I can boot to that.
I added a bunch of packages with synaptic, all working so far (audacity, scid, eboard, k3b, ksnip...many more)

As for the big conky, a bit too big for me. I really like the antix conky, off to the side, less intrusive.

Code: Select all

$ inxi -F
System:    Host: Ryzen Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: N/A
           UEFI [Legacy]: American Megatrends v: 0902 date: 09/08/2017
CPU:       Hexa core AMD Ryzen 5 1600X Six-Core (-HT-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 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Gallium 0.4 on NV106 version: 4.3 Mesa 13.0.6
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.9.0-4-amd64
Network:   Card: Intel I211 Gigabit Network Connection driver: igb
           IF: enp38s0 state: up speed: 100 Mbps duplex
Drives:    HDD Total Size: 2250.5GB (29.4% used)
           ID-1: /dev/nvme0n1 model: Samsung_SSD_960_EVO_250GB size: 250.1GB
           ID-2: /dev/sda model: WDC_WD2002FAEX size: 2000.4GB
Partition: ID-1: / size: 39G used: 4.7G (13%) fs: ext4 dev: /dev/nvme0n1p1
           ID-2: /home size: 73G used: 108M (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: 41.0
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 287 Uptime: 11:08 Memory: 1070.0/16048.3MB Client: Shell (bash) inxi: 2.3.40

Posted: **Tue Nov 07, 2017 11:11 am**

As for the big conky, a bit too big for me. I really like the antix conky, off to the side, less intrusive.

You mean we shouldn't use it for default? Just want to make sure that you realize there are over 35 conkies available, some of which are more technical and over to the side (and you can always move them anyway).

We're running a separate thread on the conkies, and would appreciate your input.

Posted: **Tue Nov 07, 2017 11:43 am**

I am still testing the beta 1. More stuff like USB sticks, USB hard disks with ntfs...so far it looks good. [Edited] Checked USB mounting, and external drive ntfs read and write. All were working.

I wonder for the developers, what goes into selecting the kernel version? MX-17 has the 4.9 kernel, while antix has the 4.10. What are the reasons for selecting one over the other? If I install an antix kernel into MX, what do I miss? What are the risks, of broken stuff. I am still testing my hardware, searching for that stability. I don't know if I should install the nvidia driver. In MX 16, that apparantly helped avoid mouse and KB freezes, but I haven't run this MX-17 long enough to see if it is stable under noveau.

<MODERATOR: I removed the conky comments since they have been duplicated in the other thread.>

Posted: **Tue Nov 07, 2017 12:59 pm**

Installed on my Thinkpad X230 (all Intel) and it runs well. Added/removed some programs as I always do (all from repos) and then went to make a snapshot. The first time it aborted at about 35% and game a message that there isn't enough space available (there's over 45 GB). The next time it was at the end writing the ISO file when it also aborted due to not enough space.

Palemoon is also acting strange and has suddenly closed a number of times. If I try to import bookmarks from HTML it will close everytime.

Posted: **Tue Nov 07, 2017 1:18 pm**

BitJam wrote:@stevo, unfortunately, there are two versions of MX-17.b1_x64.iso. The live legacy bootloader (syslinux with gfxboot, not Grub) was fixed in the latest version so it sounds like you used the earlier version. I used live-usb-maker to make a live-usb from this iso file:
Code: Select all
b61af97f7a17032f70fef68a2626fb76  MX-17.b1_x64.iso
I was able to boot UEFI in secure boot mode on a Dell XPS-13 and on an Acer-ES1-511. The legacy syslinux bootloader also worked as expected on both systems.

Ahh, that's why. I used the very first deltas to create the iso files. I'm now using the zsync files to convert those to the standard releases.

Posted: **Tue Nov 07, 2017 2:19 pm**

'Snapshot' failed on a legacy machine with the disk space error. (There is plenty of space!)

The last few lines of the output is attached.

Chris

Posted: **Tue Nov 07, 2017 2:30 pm**

chrispop99 wrote:'Snapshot' failed on a legacy machine with the disk space error. (There is plenty of space!)

The last few lines of the output is attached.

Thanks Chris! That log file was extremely useful! The out of disk space error message is bogus.

The problem is in iso-template.tgz. The file /boot/grub/efi.img is missing. It is used for UEFI booting on dd live-usbs. I may need to coordinate with dolphin_oracle (or others) on making iso-template.tgz.

Posted: **Tue Nov 07, 2017 2:37 pm**

BitJam wrote:
chrispop99 wrote:'Snapshot' failed on a legacy machine with the disk space error. (There is plenty of space!)

The last few lines of the output is attached.
Thanks Chris! That log file was extremely useful! The out of disk space error message is bogus.

The problem is in iso-template.tgz. The file /boot/grub/efi.img is missing. It is used for UEFI booting on dd live-usbs. I may need to coordinate with dolphin_oracle (or others) on making iso-template.tgz.

yep, I probably made the template wrong. but if that's all it is, we can issue an update for that one.

**edit** looking at things, I most certainly broke it when trying to incorporate that latest initrd. We will get it fixed.

Posted: **Tue Nov 07, 2017 2:38 pm**

Testing the 32 bit version on a Thinkpad laptop and in VBox. Screen is 15'. One I think that may have been missed.

Installer blurb in left hand pane is distorted. Font size too big, perhaps?

Posted: **Tue Nov 07, 2017 2:45 pm**

m_pav wrote:Grab handles on screen borders can be a bit hard to grab. Has the padding been applied as per earlier versions?

The only "window-managers" I know of on the ISO with fatter borders are the greybird-accessibilty one plus the two default-hdpi ones that are built into xfce-4.12. I'd like to get a few more into the ISO, myself.

Posted: **Tue Nov 07, 2017 2:53 pm**

anticapitalista wrote:Testing the 32 bit version on a Thinkpad laptop and in VBox. Screen is 15'. One I think that may have been missed.

Installer blurb in left hand pane is distorted. Font size too big, perhaps?

we've been trying to make the installer window resizable (it wasn't originally), and its caused some problems with that text box. sometimes just resizing the window will snap it back into place.

Posted: **Tue Nov 07, 2017 2:55 pm**

anticapitalista wrote:Testing the 32 bit version on a Thinkpad laptop and in VBox. Screen is 15'. One I think that may have been missed.

Installer blurb in left hand pane is distorted. Font size too big, perhaps?

Yes, I notice that myself. If I resize the installer window, that gets the text to wrap around correctly, though.

Posted: **Tue Nov 07, 2017 3:04 pm**

Opened conky manager and unchecked everything.

Copied .conkyrc from Antix to a thumbdrive, then copied to ~/home/my name/
Started it up and

Posted: **Tue Nov 07, 2017 3:27 pm**

No need to double post. The post in the conky thread is sufficient.

Posted: **Tue Nov 07, 2017 3:28 pm**

richb wrote:No need to double post. The post in the conky thread is sufficient.

I goofed and posted here first. Sorry!

Posted: **Tue Nov 07, 2017 4:01 pm**

Stevo wrote:
anticapitalista wrote:Testing the 32 bit version on a Thinkpad laptop and in VBox. Screen is 15'. One I think that may have been missed.

Installer blurb in left hand pane is distorted. Font size too big, perhaps?
Yes, I notice that myself. If I resize the installer window, that gets the text to wrap around correctly, though.

Yes, I saw that too, but ...

1. how many new users will know that 'trick' when installing MX to hard drive?
2. it shouldn't happen. So, maybe reverting the relevant changes made to the installer would be better.

Posted: **Tue Nov 07, 2017 4:05 pm**

Yes, something like that would certainly grate on a certain reviewer!

Posted: **Tue Nov 07, 2017 4:18 pm**

anticapitalista wrote:
Stevo wrote:
anticapitalista wrote:Testing the 32 bit version on a Thinkpad laptop and in VBox. Screen is 15'. One I think that may have been missed.

Installer blurb in left hand pane is distorted. Font size too big, perhaps?
Yes, I notice that myself. If I resize the installer window, that gets the text to wrap around correctly, though.
Yes, I saw that too, but ...

1. how many new users will know that 'trick' when installing MX to hard drive?
2. it shouldn't happen. So, maybe reverting the relevant changes made to the installer would be better.

I've got a fix for it.

some of our users have HiDPI screens, and some of the text entry fields are too small unless we can resize the installer.

Posted: **Tue Nov 07, 2017 4:36 pm**

dolphin_oracle wrote:
anticapitalista wrote:
Stevo wrote:
Yes, I notice that myself. If I resize the installer window, that gets the text to wrap around correctly, though.
Yes, I saw that too, but ...

1. how many new users will know that 'trick' when installing MX to hard drive?
2. it shouldn't happen. So, maybe reverting the relevant changes made to the installer would be better.
I've got a fix for it.

some of our users have HiDPI screens, and some of the text entry fields are too small unless we can resize the installer.

Good as reverting should not be an option. I found the re-size a good option on the installer.

Posted: **Tue Nov 07, 2017 4:56 pm**

dolphin_oracle wrote:
anticapitalista wrote:Testing the 32 bit version on a Thinkpad laptop and in VBox. Screen is 15'. One I think that may have been missed.

Installer blurb in left hand pane is distorted. Font size too big, perhaps?
we've been trying to make the installer window resizable (it wasn't originally), and its caused some problems with that text box. sometimes just resizing the window will snap it back into place.

I could not replicate that on the build machine, I will have to test that a bit more, it might be something that show up in the Qt version of the MX17.

It should be something easy to fix once I figure out where the problem is, I appreciate that people are so cavalier with "let's revert", but it was a bit of a pain to make the installer resizeable, so I would not be so quick to revert.

Posted: **Tue Nov 07, 2017 5:01 pm**

cavalier to revert?

You forgot the

perhaps? and maybe

Posted: **Tue Nov 07, 2017 5:30 pm**

Yeah, I always forget that.

Posted: **Tue Nov 07, 2017 5:38 pm**

chrispop99 wrote:'Snapshot' failed on a legacy machine with the disk space error. (There is plenty of space!)

The last few lines of the output is attached.

Chris

thanks to BJ, we have a updated mx-iso-template heading its way to tim for the repo.

Posted: **Tue Nov 07, 2017 6:17 pm**

Running 32 bit live in VBox, I noticed 2 instances of yad running using 34 MB RAM (root terminal type ps_mem.py). I haven't opened anything except the root terminal to type in ps_mem.py.

32 bit RAM usage is much, much higher than MX-16.1 (c360 MB compared to IIRC an idle of under 200MB for MX-16.1)

Posted: **Tue Nov 07, 2017 6:58 pm**

anticapitalista wrote:Running 32 bit live in VBox, I noticed 2 instances of yad running using 34 MB RAM (root terminal type ps_mem.py). I haven't opened anything except the root terminal to type in ps_mem.py.

32 bit RAM usage is much, much higher than MX-16.1 (c360 MB compared to IIRC an idle of under 200MB for MX-16.1)

Probably the usb-Unmounter notification icon. That's the only yad thing running all the time.

64 bit useage is a lot higher too. although pretty close to what I've seen on debian with similar services running.

there is more stuff running in 17 vs 16.1, but not enough to account for the ram usage. some of this stuff is just heavier this go around.

a5 was worse on 64 bit. the b1 features a slightly newer kernel, and it helped ram usage a little (at least here).

Posted: **Tue Nov 07, 2017 8:20 pm**

FredBezies wrote:Some feedbacks on MX 17 beta1

I tested quickly MX17 beta1 in VirtualBox, and here are my feedbacks. Not a lot of them, but the ones that jumped to my eyes.

2) I cannot install any single translation package using simplified MX installer applications. Terminal windows is opening, and no matter which repository I select (either stable or mx repo), nothing is done.

I had to use Synaptic and install missing packages by hand.

Have a good day.

thanks for trying these! I think its a problem with the libreoffice sets. We will get that updated (they worked with 5.2, but not with 5.3).

Posted: **Tue Nov 07, 2017 9:00 pm**

sent fixed (I hope) language packs up for updates. I may have installed more language packs than the average person tonight.

Posted: **Tue Nov 07, 2017 9:02 pm**

That'll help!

Posted: **Tue Nov 07, 2017 11:50 pm**

dolphin_oracle wrote:
FredBezies wrote:Some feedbacks on MX 17 beta1

thanks for trying these! I think its a problem with the libreoffice sets. We will get that updated (they worked with 5.2, but not with 5.4).

As I understand the present Libre Office situation, 5.3 is the stable version for most users. 5.4 is still being developed and perhaps
not suitable as an MX default application.

However, I am using LO 5.4.2.2 without (yet) any problems.

Posted: **Wed Nov 08, 2017 1:44 am**

Installed Mx-17 Beta 1 on my system

Code: Select all

System:    Host: cherubim Kernel: 4.9.0-4-686 i686 bits: 32 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_386 Horizon November 6, 2017
Machine:   Device: desktop Mobo: MICRO-STAR model: MS-7507 v: 1.0 serial: N/A
           BIOS: American Megatrends v: V3.1 date: 03/01/2008
CPU:       Dual core Intel Core2 Duo E4500 (-MCP-) cache: 2048 KB
           clock speeds: max: 2218 MHz 1: 2218 MHz 2: 2218 MHz
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@59.89hz
           OpenGL: renderer: Mesa DRI Intel 945G x86/MMX/SSE2 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.9.0-4-686
Network:   Card: Realtek RTL8101/2/6E PCIE Fast/Gigabit Ethernet controller driver: r8169
           IF: ens33 state: up speed: 100 Mbps duplex: full mac: 00:1d:92:a2:a1:ee
Drives:    HDD Total Size: 160.0GB (4.4% used)
           ID-1: /dev/sda model: WDC_WD1600AABS size: 160.0GB
Partition: ID-1: / size: 27G used: 4.8G (19%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 2.05GB used: 0.93GB (46%) fs: swap dev: /dev/sda1
Sensors:   System Temperatures: cpu: 58.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 188 Uptime: 41 min Memory: 463.2/996.6MB Client: Shell (bash) inxi: 2.3.40

Pros i Found during to my observation---

*Excellent theme with beautiful wallpapers i like them
*MX Tweak team is really good for changing some settings it makes things much easier
*Papirus icon theme is really good
*Thanks for adding Numix theme
*Conky is nice with more settings to change the color
*No issues with LIBRE office and GIMP everything is opening well
*Notifications settings are nice and the themes for notifications are really looking good
* Chromium Black Boxes issue solved this time may be it is because of update

Here are the cons i found with my system:----

*Mx apt updater when i click on it nothing is being displayed instead synaptic is opening if i double click
*Found one issue with conky when i drag the conky on to the left the screen the icons on the desktop are disappearing
*Found another issue with conky when i syncronise my clock with internet and after starting system if the time is changed according to my network conky is moving the position on desktop during time change
*advert blocking is not blocking youtube videos ads and some ads are being blocked in the browser however an empty white box with can't connect to the website is being displayed
*The system is slow when compared to MX-16.1 may be my system getting old :-)
*Chromium is updated with this chromium i couldn't understand it is taking time to open newtab whereas in mx-16.1 i didn't found the issue and is fast

Suggestion:-

If possible add startup MX-16 logo instead of normal startup screen if possible
I couldn't understand MX is little bit slowed on my pc may be due to my hard ware or Beta i couldn't understand
If possible add little more themes and remove some XFCE old themes if possible

Thanks for Bringing Beautiful OS i Congratulate those who worked hard for this project from my bottom of my heart

Posted: **Wed Nov 08, 2017 3:51 am**

Wine installation appears unsuccessful via Package Manager or via MX Package Manager testing... wine staging...not usually a problem I experience

Synaptic Package Manager list check boxes lack obvious contrast to the unfamiliar?

Bluetooth error message upon desktop loading as noted in an earlier post/screenshot:
I have been using bluetooth connections a bit lately but find pairing unreliable so far, MX-16 included.

Otherwise, some dialogues (eg, MX Conky) are displaying text in a blurry manner reminiscent of Wine applications.

Wifi dongle requires some unplugging and re-plugging to initiate.

Code: Select all

System:    Host: mx1 Kernel: 4.7.0-0.bpo.1-amd64 x86_64 (64 bit) Desktop: Xfce 4.12.2
           Distro: MX-16.1_x64 Metamorphosis 8 June 2017
Machine:   Device: desktop System: LENOVO product: 7522RU3 v: ThinkCentre A58
           Mobo: LENOVO model: 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: 2136 MHz 2: 2403 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           GLX Renderer: Mesa DRI Intel G41 GLX Version: 2.1
Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.7.0-0.bpo.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 (46.1% used)
           ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 30G used: 7.8G (28%) fs: ext4 dev: /dev/sda9
           ID-2: /home size: 34G used: 8.5G (27%) fs: ext4 dev: /dev/sda8
           ID-3: 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: 196 Uptime: 3:21 Memory: 1186.4/3921.2MB Client: Shell (bash) inxi: 2.3.21

Posted: **Wed Nov 08, 2017 4:10 am**

Today's update included a fixed mx-iso-template, to allow Snapshot to work properly.

I updated, ran Snapshot, and it successfully created an ISO.

Chris

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

I'm testing the 64bit version in a Vbox. The MX Package Installer generates a "Granted permissions without asking for password" message, the same happens when installing codecs. Is this "normal" behaviour? And if so, how do I change that?

Posted: **Wed Nov 08, 2017 5:29 am**

wizd3m wrote:I'm testing the 64bit version in a Vbox. The MX Package Installer generates a "Granted permissions without asking for password" message, the same happens when installing codecs. Is this "normal" behaviour? And if so, how do I change that?

The way MX-Linux is set up is that if needed, it asks for the root password once per session, and allows root operations from then until you logout. (Many other distros do the same; it is considered the most convenient way for desktop systems used primarily in home environs.)

For you to have accessed the Package Installer and received that message means you had already entered the password during that session, and is normal.

What is it you want to change? If you just want to stop that message being shown, there is a check box on the message for that very purpose.

If on the other hand you want to make it necessary to request the root password every time it is needed, you should ask outside this thread.

Chris

Posted: **Wed Nov 08, 2017 5:31 am**

Thanks Chris, the last option is the one I want.

Posted: **Wed Nov 08, 2017 6:46 am**

tascoast wrote:Wine installation appears unsuccessful via Package Manager or via MX Package Manager testing... wine staging...not usually a problem I experience

what is the failure. seems to install fine for me here from the "Popular Apps" tab.

Posted: **Wed Nov 08, 2017 7:16 am**

dolphin_oracle wrote:
tascoast wrote:Wine installation appears unsuccessful via Package Manager or via MX Package Manager testing... wine staging...not usually a problem I experience

what is the failure. seems to install fine for me here from the "Popular Apps" tab.

I tried installing several times with MX Package Manager and it downloaded and installed, according to the terminal window, including a 'Y' conformation to begin the process, but refused to 'go grey' in MX Package Manager. I'll do a fresh install soon enough in any case and hope for better luck.

I am most interested in bluetooth for now and find blueman missing something that has allowed me to pair and stream directly to hearing aids (using MX-16) via an accessory bluetooth device that ultimately sends the sound via FM and an antenna loop, forming a necklace of sorts in close proximity to the aids.

In short, it kinda replaces the function of typical earbud/mic or similar but provides a far superior sound, being direct to ears. Also can be used to watch or listen to other streams on PC, or android phone and music player, for instance. EasyTek ...

Posted: **Wed Nov 08, 2017 7:43 am**

tascoast wrote:
dolphin_oracle wrote:
tascoast wrote:Wine installation appears unsuccessful via Package Manager or via MX Package Manager testing... wine staging...not usually a problem I experience

what is the failure. seems to install fine for me here from the "Popular Apps" tab.
I tried installing several times with MX Package Manager and it downloaded and installed, according to the terminal window, including a 'Y' conformation to begin the process, but refused to 'go grey' in MX Package Manager. I'll do a fresh install soon enough in any case and hope for better luck.

that may be a failure to to grey out in mx-packageinstaller. check

Code: Select all

apt-cache policy wine-staging

to see if its installed. Also, if you use the "Popular Apps" tab, you should get an "other" category in the menu with wine stuff in it.

Posted: **Wed Nov 08, 2017 7:46 am**

tascoast wrote:
dolphin_oracle wrote:
tascoast wrote:I am most interested in bluetooth for now and find blueman missing something that has allowed me to pair and stream directly to hearing aids (using MX-16) via an accessory bluetooth device that ultimately sends the sound via FM and an antenna loop, forming a necklace of sorts in close proximity to the aids.

In short, it kinda replaces the function of typical earbud/mic or similar but provides a far superior sound, being direct to ears. Also can be used to watch or listen to other streams on PC, or android phone and music player, for instance. EasyTek ...

Have you paired the device? I just tried pairing with my cellphone's audio, and it was a bit weird. I added the package pulseaudio-module-bluetooth after doing a web search on the problem, and would like you to try that, reboot, and start again.

Posted: **Wed Nov 08, 2017 11:38 am**

I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.

Posted: **Wed Nov 08, 2017 11:42 am**

ferlop wrote:I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.

Not sure how much it consumes on your system ,on mine very little, 4 core AMD, but you can try turning off the conky and see what results. MX Conky and click stop.

Posted: **Wed Nov 08, 2017 1:26 pm**

A question; if an install with encryption is done, is the ability to subsequently change a user to autologin using MX User Manager disabled?

I'm guessing this is the case, and it seems sensible to do so. User Manager still toggles the relevant line in /etc/lightdm/lightdm.conf, so how is autologin prevented in this case?

Chris

Posted: **Wed Nov 08, 2017 1:32 pm**

chrispop99 wrote:A question; if an install with encryption is done, is the ability to subsequently change a user to autologin using MX User Manager disabled?

I'm guessing this is the case, and it seems sensible to do so. User Manager still toggles the relevant line in /etc/lightdm/lightdm.conf, so how is autologin prevented in this case?

Chris

I think you can actually use autologin, although we disable by default in the installer. I've been meaning to try. My current install has an encrypted home.

Of course, enabling autologin more or less defeats the purpose of encrypting in the first place. but that requires a root level password, so the presumption is that's what you really want to do.

Posted: **Wed Nov 08, 2017 1:35 pm**

I've only tested from the DVD - but am expecting a new laptop to arrive tomorrow which will get b1 on it from the outset (I believe there was an upgrade path to final from 16 betas - but no probs if I need to reinstall). From a day's playing around, everything works flawlessly on my 5 or 6 year laptop, with the usual exception of manipulation of my camera. Thunar just doesn't seem to handle cameras but it's easily solved by keeping either PCManFM or Nemo installed and using that for initial import or drag and drop. Apart from being able to report no faults from the DVD, I'm loving the new looks (of all 3 themes in Tweak) and the addition of GThumb. If you'd added the iridium browser you'd have pretty much replicated my normal set-up! Looking forward to installing and I'll let you know how it goes.

Posted: **Wed Nov 08, 2017 1:47 pm**

RobWigham wrote:I've only tested from the DVD - but am expecting a new laptop to arrive tomorrow which will get b1 on it from the outset (I believe there was an upgrade path to final from 16 betas - but no probs if I need to reinstall). From a day's playing around, everything works flawlessly on my 5 or 6 year laptop, with the usual exception of manipulation of my camera. Thunar just doesn't seem to handle cameras but it's easily solved by keeping either PCManFM or Nemo installed and using that for initial import or drag and drop. Apart from being able to report no faults from the DVD, I'm loving the new looks (of all 3 themes in Tweak) and the addition of GThumb. If you'd added the iridium browser you'd have pretty much replicated my normal set-up! Looking forward to installing and I'll let you know how it goes.

Thunar connects flawlessly to my Canon Ixus camera, and to my Android phone in order to access the photos on it.

Have you tried Shotwell, available from the MX Package Installer, to connect to your camera, and manage your photos?

Chris

Posted: **Wed Nov 08, 2017 2:09 pm**

Trivial!

Personal opinion only, but turning on User Image in LightDM Greeter settings makes the login screen look much better.

Chris

Posted: **Wed Nov 08, 2017 2:16 pm**

I've tried Shotwell, Chris, and it makes download and import from the camera better - if not good. My camera is a Panasonic which is not on the gphoto2 supported cameras list, but what's interesting is that other FMs will do drag and drop flawlessly from and between the camera folders (something I need) but Thunar will not. I can access the camera but it will literally take 5 minutes just to scroll a little down the folder. It's been suggested elsewhere in these forums that it might be a Tumbler issue but I've not had the time to check that out - much easier just to use Nemo. Thanks for the suggestion though!

Posted: **Wed Nov 08, 2017 2:45 pm**

chrispop99 wrote:Trivial!

Personal opinion only, but turning on User Image in LightDM Greeter settings makes the login screen look much better.

Chris

I agree, and the Art Team has to look at that anyway before Final

Posted: **Wed Nov 08, 2017 4:47 pm**

First look live on desktop. UEFI boot, localized. Boot screen appearance good, font for text settings very clear. What does 'Console columns' do? Accepted all other defaults.

Welcome screen layout fine. First ever Conky on my machines - attractive, but DMY & monitor legends are black on dark grey - almost invisible, but bug my eyes as I look around.

LibreOffice - window edges hard to grab, but corner OK. Font rendering in documents (DejaVu Sans) poor - font metrics/kerning wrong. System fonts in applications and on desktop fine.

[13 updates at this point - installed.] Firefox - logged on to Forum. Forum appearance very clear but text in posts poorly rendered. I installed Iridium (I've been using it for about a week) and post text is good.

Installed GnuCash - all OK. Sound and video fine in VLC and all function keys work as they should.

Overall, Beta is good for me. Install and test on other machines will have to wait until next week.

Phil

Posted: **Wed Nov 08, 2017 5:19 pm**

Just did fresh install and can not see LibreOffice Writer icons https://snag.gy/rQLEJO.jpg but text only.

Posted: **Wed Nov 08, 2017 5:27 pm**

Thanks. I think that's been covered earlier in the post if you want to take a look.

Posted: **Wed Nov 08, 2017 5:31 pm**

My bad. Thank you Jerry.

Posted: **Wed Nov 08, 2017 5:33 pm**

No no, didn't mean it that way. It's very hard to know what is in this long thread.

Posted: **Wed Nov 08, 2017 5:49 pm**

Gaer Boy wrote: What does 'Console columns' do? Accepted all other defaults.

We will select a console font size so there will be roughly that many columns of console text. The default value is 120 so we select a font size so there are roughly 120 columns of text.

This has several advantages over the tradition method of one-font-size-fits-all, which results in teeny tiny fonts on HDPI displays. Our default of 120 columns works well on resolution from 1024x768 to 1920x1080 and beyond. I believe the console frame buffer is disabled by default in legacy boot on MX so the console font size won't get set until a modesetting driver kicks. For legacy booting in antiX we set the default framebuffer size to 1024x768. For UEFI booting (both antiX and MX), we usually start out at the maximum resolution so you are getting the benefit of reasonably sized fonts from the get-go. This got rid of the need of a bunch of boot loader entries to set the screen resolution. If the screen resolution changes when a mode setting driver kicks in, the font size (on the screen) should stay roughly the same. The selected console font size should carry over to installed systems. If you want to change the console font size, there is a clunky choose-console-width program available in b1. I hope the easier to use select-console-width will make it onto b2.

The goal was to have usable consoles OOTB on a wide range of hardware. The default console font made it very hard to use the consoles on my xps-13. Now they are a joy to use. I don't know of any other distros that do this. We went through three of four iterations of software to improve the console font size. The key concept was to make the number of columns in the console roughly fixed.

I really think we should do something like this for X-windows too and select a reasonable font size/scale/DPI based on the screen resolution. Starting at some resolution, say 1280x1024 (or something larger) we can scale the font size up as the resolution goes up so the size of the fonts on the screen stay relatively constant. This should give users with HDPI displays a very workable system OOTB. When automatically selecting a font size, it is usually better to err on the side of being too big rather than too small. It is a joy to have a usable system boot live OOTB. It is extremely annoying when everything is so teeny tiny it is hard to get to the adjustment to make things bigger.

Posted: **Wed Nov 08, 2017 6:53 pm**

danielson wrote:can not see LibreOffice Writer icons

Just go to "Options" and change it

Posted: **Wed Nov 08, 2017 7:04 pm**

Jerry3904 wrote:
tascoast wrote:
dolphin_oracle wrote:
Have you paired the device? I just tried pairing with my cellphone's audio, and it was a bit weird. I added the package pulseaudio-module-bluetooth after doing a web search on the problem, and would like you to try that, reboot, and start again.

Adding pulseaudio-module-bluetooth did make a big difference and I was able to connect previously paired devices.
(it was nice to watch a movie yesterday direct to the ears, with really clear speech being received)

For Wine, I seem to have most things installed but not Wine staging and expected winecfg in a terminal to do the usual things with ms corefonts etc. It mostly seems stuck at the last post as it were, not creating a menu entry, but I'll take others' success as a local glitch for now.

Posted: **Wed Nov 08, 2017 7:29 pm**

That's excellent, I'm really glad that worked. We will be sure to add that to the next version.

Posted: **Wed Nov 08, 2017 9:49 pm**

Have we decided against qBittorrent as the included torrent client?

Posted: **Thu Nov 09, 2017 1:08 am**

I haven’t even had time to download and try the beta yet, but the kernel version does concern me a bit with my Ryzen boards.

What newer alternative kernel should I be trying with them... the antiX 4.10?

Posted: **Thu Nov 09, 2017 4:20 am**

Confused which MX repo to choose in mx-repo-manager now? They give different errors in output.

(while yad (0.38.2-1 => 0.38.2-1) is to be updated)
E: Failed to fetch http://iso.mxrepo.com/antix/stretch/dis ... ents-amd64 404 Not Found
E: Failed to fetch http://iso.mxrepo.com/mx/repo/dists/str ... tents-i386 404 Not Found
or
E: Failed to fetch http://it.mxrepo.com/antix/stretch/dist ... ents-amd64 404 Not Found

On the other hand: mxrepo.com shows no fetching errors but there is no update for yad.

Posted: **Thu Nov 09, 2017 9:42 am**

No sound here. It works on MX 16.1.
====================================

System: Host: mx1 Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine: Device: desktop Mobo: MICRO-STAR model: MS-7253 v: 1.0 serial: N/A
BIOS: Phoenix v: V1.7 date: 10/23/2007
CPU: Dual core AMD Athlon 64 X2 4200+ (-MCP-) cache: 1024 KB
clock speeds: max: 2200 MHz 1: 1000 MHz 2: 1000 MHz
Graphics: Card: NVIDIA NV44 [GeForce 6200 TurboCache]
Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1680x1050@59.95hz
OpenGL: renderer: GeForce 6200 TurboCache/PCIe/SSE2 version: 2.1.2 NVIDIA 304.135
Audio: Card VIA VT8237A/VT8251 HDA Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network: Card-1: VIA VT6102/VT6103 [Rhine-II] driver: via-rhine
IF: enp0s18 state: down mac: 00:1d:92:6f:e7:23
Card-2: D-Link System DGE-528T Gigabit Ethernet Adapter driver: r8169
IF: enp4s5 state: up speed: 100 Mbps duplex: full mac: e4:6f:13:aa:80:c1
Drives: HDD Total Size: 500.1GB (3.5% used)
ID-1: /dev/sdb model: MAXTOR_STM325031 size: 250.1GB
ID-2: /dev/sda model: ST3250310AS size: 250.1GB
Partition: ID-1: / size: 129G used: 8.7G (8%) fs: ext4 dev: /dev/sdb3
ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
ID-3: swap-2 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2
Sensors: System Temperatures: cpu: 56.0C mobo: N/A gpu: 52C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 184 Uptime: 14 min Memory: 927.8/2003.4MB Client: Shell (bash) inxi: 2.3.40

Posted: **Thu Nov 09, 2017 10:16 am**

SwampRabit,

Earlier in the thread I asked about the kernel also.

The antix 17 uses 4.10. Why the difference?
I guess I really don't understand these issues.

In MX 17, what happens if I install the antix 17 4.10 kernel. What happens or won't work?

Or later liquorix 4.13. I had some problems with the antix install with an antix 4.13 kernel attempt, but that is probably my inexperience or something with the nvidia driver selection. I still have not figured it out yet.

But back to MX 17, I had a hard lock up last night as I have observed earlier with this Ryzen board. After 2 days uptime, I came down to the machine and it had a blank screen, no cursor, no log in, just blank. Yet the fans were spinning, LEDs illuminated on the board, but KB and mouse totally unresponsive. So I hit reset and installed the nvidia driver withe the MX tools. It took a loooong time, I was worried, but eventually it completed successfully, so I rebooted. I now have the nvidia driver. This helped with the up time in the antix installation.

We will see how the stability is now.

Posted: **Thu Nov 09, 2017 10:21 am**

ldsemerchen

I am not at my MX machine (on Win 7 professionally now), so I cannot point exactly to where the menues are.

But there is a control panel, where you can select the default sound card. In this beta the install picked up mine correctly, so I did not need to change it, but pole around on the menus to find the control panel ( I am mixing my MX and antix in my mind now, as I am testing both), or look in the MX 16 manual.

Probably Jerry or someone will point you to the right area.

Then you can select the default sound card, and it should work.

Also sometimes check the little speaker icon on the panel, right click it, you might need to increase the volume.

Posted: **Thu Nov 09, 2017 10:22 am**

entropyfoe wrote:SwampRabit,

Earlier in the thread I asked about the kernel also.

The antix 17 uses 4.10. Why the difference?
I guess I really don't understand these issues.

In MX 17, what happens if I install the antix 17 4.10 kernel. What happens or won't work?

Or later liquorix 4.13. I had some problems with the antix install with an antix 4.13 kernel attempt, but that is probably my inexperience or something with the nvidia driver selection. I still have not figured it out yet.

But back to MX 17, I had a hard lock up last night as I have observed earlier with this Ryzen board. After 2 days uptime, I came down to the machine and it had a blank screen, no cursor, no log in, just blank. Yet the fans were spinning, LEDs illuminated on the board, but KB and mouse totally unresponsive. So I hit reset and installed the nvidia driver withe the MX tools. It took a loooong time, I was worried, but eventually it completed successfully, so I rebooted. I now have the nvidia driver. This helped with the up time in the antix installation.

We will see how the stability is now.

basically mx17 uses the default debian kernel. the 4.9 kernel series is also the latest LTS kernel series, with the linux kernel devs commited to (6?) several years of updates.

You *should* be able to use the antiX 4.10 kernels as well.

Posted: **Thu Nov 09, 2017 10:32 am**

I ran the MX nvidia installer on optimus laptop. During the install a message indicating a conflict with nouveau that would be most likely corrected with a rebbot after install. The install concluded successfully. Rebooted and still no nvidia driver. The nvidia blacklist file in /etc/modprobe.d does have nouveau blacklisted. Do I need a boot cheat?

Posted: **Thu Nov 09, 2017 10:39 am**

richb wrote:I ran the MX nvidia installer on optimus laptop. During the install a message indicating a conflict with nouveau that would be most likely corrected with a rebbot after install. The install concluded successfully. Rebooted and still no nvidia driver. The nvidia blacklist file in /etc/modprobe.d does have nouveau blacklisted. Do I need a boot cheat?

post your inxi -F output.

note that by defuault, the intel or modesetting driver should be in place on an optimus machine until you use the primusrun or optirun commands to launch an app.

also, you should NOT have an xorg.conf file.

Posted: **Thu Nov 09, 2017 10:48 am**

Dolphin Oracle and richb,

I did the nvidia install using the MX tool last night.

I also saw the noveau warning, and on reboot I DID get the nvidia driver. I can't remember the number now, I think it was 375.82-1-deb901.

I also saw a warning about no xorg.conf.

After reboot all seems normal.

Posted: **Thu Nov 09, 2017 10:54 am**

dolphin_oracle wrote:
richb wrote:I ran the MX nvidia installer on optimus laptop. During the install a message indicating a conflict with nouveau that would be most likely corrected with a rebbot after install. The install concluded successfully. Rebooted and still no nvidia driver. The nvidia blacklist file in /etc/modprobe.d does have nouveau blacklisted. Do I need a boot cheat?
post your inxi -F output.

note that by defuault, the intel or modesetting driver should be in place on an optimus machine until you use the primusrun or optirun commands to launch an app.

also, you should NOT have an xorg.conf file.

Code: Select all

Host: mx1 Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: laptop System: Acer product: Aspire V5-572G v: V2.06 serial: N/A
           Mobo: Acer model: Dazzle_CX v: Type2 - A01 Board Version serial: N/A
           UEFI [Legacy]: Insyde v: V2.06 date: 05/22/2013
Battery    BAT1: charge: 39.2 Wh 89.3% condition: 43.9/53.4 Wh (82%)
CPU:       Dual core Intel Core i5-3337U (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2700 MHz 1: 2500 MHz 2: 2361 MHz 3: 2582 MHz 4: 2531 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.99hz
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 3.3 Mesa 13.0.6
Audio:     Card Intel 7 Series/C216 Family High Definition Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network:   Card-1: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k
           IF: wlp3s0 state: up mac: 2c:d0:5a:eb:3e:cc
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           IF: enp4s0f1 state: down mac: 08:9e:01:a4:28:8e
Drives:    HDD Total Size: 256.1GB (3.2% used)
           ID-1: /dev/sda model: SanDisk_SDSSDP25 size: 256.1GB
Partition: ID-1: / size: 117G used: 5.7G (6%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 2.16GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 51.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 210 Uptime: 1 min Memory: 938.6/11901.0MB Client: Shell (bash) inxi: 2.3.40

On the MX 16.1 install I recall the Graphics info showing the nvidia driver which led me to believe it was not active. Perhaps faulty memory. There is no xorg.conf.

Posted: **Thu Nov 09, 2017 10:58 am**

that looks right to me. you can try that

Code: Select all

optirun glxgears

I think to see if it kicks in.

Posted: **Thu Nov 09, 2017 10:59 am**

entropyfoe wrote:Dolphin Oracle and richb,

I did the nvidia install using the MX tool last night.

I also saw the noveau warning, and on reboot I DID get the nvidia driver. I can't remember the number now, I think it was 375.82-1-deb901.

I also saw a warning about no xorg.conf.

After reboot all seems normal.

can you post your /var/log/ddm.log file for comparison.

Posted: **Thu Nov 09, 2017 11:07 am**

dolphin_oracle wrote:that looks right to me. you can try that
Code: Select all
optirun glxgears
I think to see if it kicks in.

It does kick. But I would expect a faster frame rate than when run without optirun. That has been my experience in the past on this machine.

Code: Select all


 optirun glxgears
298 frames in 5.0 seconds = 59.530 FPS
300 frames in 5.0 seconds = 59.988 FPS
300 frames in 5.0 seconds = 59.988 FPS
primus: warning: dropping a frame to avoid deadlock
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 32 requests (32 known processed) with 0 events remaining.
primus: warning: dropping a frame to avoid deadlock
primus: warning: timeout waiting for display worker
richard@mx1:~
$ glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
316 frames in 5.0 seconds = 63.069 FPS
300 frames in 5.0 seconds = 59.990 FPS
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 702 requests (456 known processed) with 0 events remaining.
richard@mx1:~

Posted: **Thu Nov 09, 2017 11:12 am**

entropyfoe wrote:ldsemerchen

I am not at my MX machine (on Win 7 professionally now), so I cannot point exactly to where the menues are.

But there is a control panel, where you can select the default sound card. In this beta the install picked up mine correctly, so I did not need to change it, but pole around on the menus to find the control panel ( I am mixing my MX and antix in my mind now, as I am testing both), or look in the MX 16 manual.

Probably Jerry or someone will point you to the right area.

Then you can select the default sound card, and it should work.

Also sometimes check the little speaker icon on the panel, right click it, you might need to increase the volume.

I can't hear any sound with my speakers plugged in my PC's backend, it did work without any setting on MX-16.1. By the way, when I plugged my USB earphones, I can switch to it and hear the sound.

Posted: **Thu Nov 09, 2017 11:18 am**

Another problem on my old laptop. Before the login screen started, I have got a 4'38" black screen. Just the same as my Debian Stretch installation experience. And the conky is unreadable like below:

https://mega.nz/#!wioxmbyQ!IPuKkX4G5c3l ... dl7GMuuZ0k

============
System: Host: mxfuji Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine: Device: laptop System: FUJITSU product: LifeBook T4220 serial: N/A
Mobo: FUJITSU model: FJNB1D4 serial: N/A
BIOS: FUJITSU // Phoenix v: Version 1.18 date: 02/23/2009
Battery CMB1: charge: 31.4 Wh 97.2% condition: 32.3/56.2 Wh (58%)
CPU: Dual core Intel Core2 Duo T8300 (-MCP-) cache: 3072 KB
clock speeds: max: 2401 MHz 1: 1600 MHz 2: 2000 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1024x768@60.00hz
OpenGL: renderer: Mesa DRI Intel 965GM version: 2.1 Mesa 13.0.6
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network: Card-1: Marvell 88E8055 PCI-E Gigabit Ethernet Controller driver: sky2
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 00:17:42:c1:c5:19
Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection driver: iwl4965
IF: wlp12s0 state: down mac: f6:77:44:e0:7c:be
Drives: HDD Total Size: 120.0GB (10.7% used)
ID-1: /dev/sda model: FUJITSU_MHY2120B size: 120.0GB
Partition: ID-1: / size: 106G used: 8.2G (9%) fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
Sensors: System Temperatures: cpu: 60.0C mobo: 26.8C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 196 Uptime: 9 min Memory: 943.0/1995.2MB Client: Shell (bash) inxi: 2.3.40

Posted: **Thu Nov 09, 2017 11:22 am**

richb wrote:It does kick. But I would expect a faster frame rate than when run without optirun.

Try:

Code: Select all

optirun vblank_mode=0 glxgears

Posted: **Thu Nov 09, 2017 11:35 am**

ldsemerchen wrote:Another problem on my old laptop. Before the login screen started, I have got a 4'38" black screen. Just the same as my Debian Stretch installation experience. And the conky is unreadable like below:

https://mega.nz/#!wioxmbyQ!IPuKkX4G5c3l ... dl7GMuuZ0k

After my post above. I found the conky ran normal after a period of time.

https://mega.nz/#!dzBTmIob!vQzNGtyQegU- ... 9ritUj1J1I

Posted: **Thu Nov 09, 2017 11:41 am**

Code: Select all

 can you post your /var/log/ddm.log file for comparison.

Yup, tonight when back in front of the machine.

Posted: **Thu Nov 09, 2017 11:45 am**

ldsemerchen

Is there an hdmi sound card or device showing?

Sometimes those need to be turned off or de-selected.

Posted: **Thu Nov 09, 2017 12:50 pm**

kmathern wrote:
richb wrote:It does kick. But I would expect a faster frame rate than when run without optirun.
Try:
Code: Select all
optirun vblank_mode=0 glxgears

Must be an error in the code

Code: Select all

[ 1939.715915] [ERROR]Error running "vblank_mode=0": No such file or directory

Posted: **Thu Nov 09, 2017 1:26 pm**

Finally had a chance to test the liveUSB grub.cfg update on the T100CHI (baytrail mixed-mode UEFI.) and it works great on my troublesome device (see viewtopic.php?f=107&t=42863). I made a stock MX17b1(64 bit) liveUSB with unetbootin. Many thanks for the update. I hope to find some time soon to remaster with a custom kernel and then install.

Posted: **Thu Nov 09, 2017 2:16 pm**

richb wrote:
kmathern wrote:
richb wrote:It does kick. But I would expect a faster frame rate than when run without optirun.
Try:
Code: Select all
optirun vblank_mode=0 glxgears
Must be an error in the code
Code: Select all
[ 1939.715915] [ERROR]Error running "vblank_mode=0": No such file or directory

The vblank_mode=0 thing works for me without the optirun part (don't have a Nvidia GPU), maybe try putting some quotes around it:

Code: Select all

 optirun 'vblank_mode=0 glxgears'

Posted: **Thu Nov 09, 2017 2:19 pm**

The problem is that optirun is looking for a command, not an environment variable. Quotes won't help but this might work:

Code: Select all

vblank_mode=0 optirun  glxgears

Posted: **Thu Nov 09, 2017 2:20 pm**

ferlop wrote:I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.

Me too experienced my system is slow after installing mx-17 beta on my pc and reverted back to MX- 16.1 may be due to alpha version i think so or may be my hardware species are becoming old but in mx-16.1 i din't found any lagging

Posted: **Thu Nov 09, 2017 2:47 pm**

kmathern wrote:
richb wrote:
kmathern wrote:
Try:
Code: Select all
optirun vblank_mode=0 glxgears
Must be an error in the code
Code: Select all
[ 1939.715915] [ERROR]Error running "vblank_mode=0": No such file or directory
The vblank_mode=0 thing works for me without the optirun part (don't have a Nvidia GPU), maybe try putting some quotes around it:
Code: Select all
 optirun 'vblank_mode=0 glxgears'

Does not work with optirun but does alone.

Posted: **Thu Nov 09, 2017 2:52 pm**

richb wrote:Does not work with optirun but does alone.

Did you try BitJam's way ?

Posted: **Thu Nov 09, 2017 3:24 pm**

kmathern wrote:
richb wrote:Does not work with optirun but does alone.
Did you try BitJam's way ?

That command to disable the refresh sync only works on xorg drivers like Intel and maybe the xorg AMD drivers. The correct syntax for the Nvidia nonfree driver is

Code: Select all

__GL_SYNC_TO_VBLANK=1 optirun glxgears

But glxgears is not a good benchmark, and will show a lower rate for the Nvidia card for reasons that seem related to Bumblebee overhead. The Unigine benchmarks show better frame rates for my Nvidia GPU.

One benchmark that works a lot better is to install virtualgl and use glxspheres on 32-bit and glxspheres64 on 64, but I still have to build it for MX 17...the way I quick-check if Bumblebee is working is

Code: Select all

inxi -G

vs

Code: Select all

optirun inxi -G

Posted: **Thu Nov 09, 2017 4:43 pm**

Code: Select all

optirun inxi -G
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.99hz
           OpenGL: renderer: GeForce GT 720M/PCIe/SSE2 version: 4.5.0 NVIDIA 375.82

That is what I would expect to see for the OpenGL renderer. So it looks like everything is as expected.
I did not see Bitjam's solution until now. That did indeed work. And the result is an order of magnitude increase in frame rate, from about 60 fps to 1000 fps

Posted: **Thu Nov 09, 2017 5:05 pm**

But isn't that 1000 fps a lot slower than the integrated GPU? My Intel GPU shows a 10X better framerate!

Here is the latest virtualgl: https://drive.google.com/open?id=1GEVdo ... mBjoYDMKec

You only need to install the virtualgl deb for your release and architecture, then you get the glxspheres benchmark on 32 and glxspheres64 on 64-bit. They show the Nvidia GPU as faster without that VBLANK setting...

Posted: **Thu Nov 09, 2017 5:11 pm**

Stevo wrote:But isn't that 1000 fps a lot slower than the integrated GPU?

No it is 60 for the integrated intel.

Here is the latest virtualgl: https://drive.google.com/open?id=1GEVdo ... mBjoYDMKec

You only need to install the virtualgl deb for your release and architecture, then you get the glxspheres benchmark on 32 and glxspheres64 on 64-bit.

Thanks. I am not on the laptop right now. But will get it when I am. By the way I remembered glxspheres is a better comparison. It will be interesting to see how that fares.

Posted: **Thu Nov 09, 2017 8:15 pm**

richb wrote:
Stevo wrote:But isn't that 1000 fps a lot slower than the integrated GPU?
No it is 60 for the integrated intel.

Here is the latest virtualgl: https://drive.google.com/open?id=1GEVdo ... mBjoYDMKec

You only need to install the virtualgl deb for your release and architecture, then you get the glxspheres benchmark on 32 and glxspheres64 on 64-bit.
Thanks. I am not on the laptop right now. But will get it when I am. By the way I remembered glxspheres is a better comparison. It will be interesting to see how that fares.

Similar numbers with glxspheres64

Posted: **Thu Nov 09, 2017 8:23 pm**

entropyfoe wrote:ldsemerchen

Is there an hdmi sound card or device showing?

Sometimes those need to be turned off or de-selected.

No hdmi sound card. I found something strange: Some program (for ex. Telegram) ran but I couldn't change it's output device to USB earphones but some could (for ex. Clementine).

Posted: **Thu Nov 09, 2017 8:50 pm**

ldsemerchen wrote:
entropyfoe wrote:ldsemerchen

Is there an hdmi sound card or device showing?

Sometimes those need to be turned off or de-selected.
No hdmi sound card. I found something strange: Some program (for ex. Telegram) ran but I couldn't change it's output device to USB earphones but some could (for ex. Clementine).

After I install 'volti', do some configuration and remove it, it works now.

Posted: **Thu Nov 09, 2017 8:51 pm**

To Dolphin Oracle and richb, here is the log file you requested after my successful install last night with the MX tool. Maybe I have slow repos , but it took a long time, I almost thought it was borked or frozen, but it completed successfully as indicated. After the install the relevant section of inxi is

System: Host: Ryzen Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine: Device: desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: N/A
UEFI [Legacy]: American Megatrends v: 0902 date: 09/08/2017
CPU: Hexa core AMD Ryzen 5 1600X Six-Core (-HT-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

And at the end of the file it appears I do have an xorg.conf ! (though it is pretty bare)

Code: Select all

I: Set the RESUME variable to override this.
New X configuration file written to '/etc/X11/xorg.conf'
Finished
Press <Enter> to exit

That's a great code line, Press enter to exit.

And here is /var/log/ddm.log

Code: Select all

creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 11/08/2017 22:20:46
===================================
Candidate is:  375.82-1~deb9u1
Installed is:  (none)
Would you like to check debian-backports for a later version?

Yes or No?

1: Yes
2: No

Enter Number of selection
Ok...
Candidate is:  375.82-1~deb9u1
Installed is:  (none)
Need driver: nvidia-driver (375.82-1~deb9u1)
NVIDIA packages to install are  nvidia-driver nvidia-settings nvidia-kernel-dkms libgl1-nvidia-glx:i386 nvidia-xconfig
Press <Enter> to continue or Ctrl-c to exitFrontend: 
Nvidia command = apt-get install --reinstall -y --force-yes  $ BP nvidia-driver nvidia-settings nvidia-kernel-dkms libgl1-nvidia-glx:i386 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
Need to get 471 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 build-essential amd64 12.3 [7,346 B]
Get:2 http://mxrepo.com/mx/repo stretch/non-free amd64 firmware-linux-nonfree all 20170823-1mx17+1 [14.9 kB]
Get:3 http://ftp.us.debian.org/debian stretch/main amd64 linux-headers-4.9.0-4-amd64 amd64 4.9.51-1 [449 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Fetched 471 kB in 14s (32.0 kB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(R....
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 231121 files and directories currently installed.)
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Preparing to unpack .../firmware-linux-nonfree_20170823-1mx17+1_all.deb ...
Unpacking firmware-linux-nonfree (20170823-1mx17+1) over (20170823-1mx17+1) ...
Preparing to unpack .../linux-headers-4.9.0-4-amd64_4.9.51-1_amd64.deb ...
Unpacking linux-headers-4.9.0-4-amd64 (4.9.51-1) over (4.9.51-1) ...
Setting up build-essential (12.3) ...
Setting up linux-headers-4.9.0-4-amd64 (4.9.51-1) ...
Setting up firmware-linux-nonfree (20170823-1mx17+1) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  gcc-6-base:i386 glx-alternative-mesa glx-alternative-nvidia glx-diversions
  libbsd0:i386 libc6:i386 libegl-nvidia0 libegl-nvidia0:i386
  libegl1-glvnd-nvidia libegl1-glvnd-nvidia:i386 libgcc1:i386
  libgl1-nvidia-glx libgldispatch0-nvidia libgldispatch0-nvidia:i386
  libgles-nvidia1 libgles-nvidia1:i386 libgles-nvidia2 libgles-nvidia2:i386
  libgles1-glvnd-nvidia libgles1-glvnd-nvidia:i386 libgles2-glvnd-nvidia
  libgles2-glvnd-nvidia:i386 libglx-nvidia0 libglx-nvidia0:i386
  libglx0-glvnd-nvidia libglx0-glvnd-nvidia:i386 libnvidia-cfg1
  libnvidia-cfg1:i386 libnvidia-eglcore libnvidia-eglcore:i386
  libnvidia-glcore libnvidia-glcore:i386 libnvidia-ml1 libopengl0-glvnd-nvidia
  libopengl0-glvnd-nvidia:i386 libx11-6:i386 libxau6:i386 libxcb1:i386
  libxdmcp6:i386 libxext6:i386 nvidia-alternative nvidia-driver-bin
  nvidia-driver-libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386
  nvidia-egl-common nvidia-egl-icd nvidia-egl-icd:i386
  nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-support
  nvidia-legacy-check nvidia-modprobe nvidia-persistenced nvidia-support
  nvidia-vdpau-driver update-glx xserver-xorg-video-nvidia
Suggested packages:
  glibc-doc:i386 locales:i386
Recommended packages:
  nvidia-vulkan-icd nvidia-vulkan-icd:i386
The following NEW packages will be installed:
  gcc-6-base:i386 glx-alternative-mesa glx-alternative-nvidia glx-diversions
  libbsd0:i386 libc6:i386 libegl-nvidia0 libegl-nvidia0:i386
  libegl1-glvnd-nvidia libegl1-glvnd-nvidia:i386 libgcc1:i386
  libgl1-nvidia-glx libgl1-nvidia-glx:i386 libgldispatch0-nvidia
  libgldispatch0-nvidia:i386 libgles-nvidia1 libgles-nvidia1:i386
  libgles-nvidia2 libgles-nvidia2:i386 libgles1-glvnd-nvidia
  libgles1-glvnd-nvidia:i386 libgles2-glvnd-nvidia libgles2-glvnd-nvidia:i386
  libglx-nvidia0 libglx-nvidia0:i386 libglx0-glvnd-nvidia
  libglx0-glvnd-nvidia:i386 libnvidia-cfg1 libnvidia-cfg1:i386
  libnvidia-eglcore libnvidia-eglcore:i386 libnvidia-glcore
  libnvidia-glcore:i386 libnvidia-ml1 libopengl0-glvnd-nvidia
  libopengl0-glvnd-nvidia:i386 libx11-6:i386 libxau6:i386 libxcb1:i386
  libxdmcp6:i386 libxext6:i386 nvidia-alternative nvidia-driver
  nvidia-driver-bin nvidia-driver-libs nvidia-driver-libs:i386
  nvidia-driver-libs-i386:i386 nvidia-egl-common nvidia-egl-icd
  nvidia-egl-icd:i386 nvidia-installer-cleanup nvidia-kernel-common
  nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check nvidia-modprobe
  nvidia-persistenced nvidia-settings nvidia-support nvidia-vdpau-driver
  nvidia-xconfig update-glx xserver-xorg-video-nvidia
0 upgraded, 63 newly installed, 0 to remove and 0 not upgraded.
Need to get 50.8 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-installer-cleanup amd64 20151021+4 [19.3 kB]
Get:2 http://ftp.us.debian.org/debian stretch/contrib amd64 update-glx amd64 0.7.4 [7,772 B]
Get:3 http://ftp.us.debian.org/debian stretch/contrib amd64 glx-alternative-mesa amd64 0.7.4 [8,184 B]
Get:4 http://ftp.us.debian.org/debian stretch/contrib amd64 glx-diversions amd64 0.7.4 [10.3 kB]
Get:5 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-legacy-check amd64 375.82-1~deb9u1 [176 kB]
Get:6 http://ftp.us.debian.org/debian stretch/contrib amd64 glx-alternative-nvidia amd64 0.7.4 [9,246 B]
Get:7 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-alternative amd64 375.82-1~deb9u1 [173 kB]
Get:8 http://ftp.us.debian.org/debian stretch/non-free amd64 libnvidia-glcore amd64 375.82-1~deb9u1 [6,421 kB]
Get:9 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-support amd64 20151021+4 [20.1 kB]
Get:10 http://ftp.us.debian.org/debian stretch/non-free amd64 libgl1-nvidia-glx amd64 375.82-1~deb9u1 [574 kB]
Get:11 http://ftp.us.debian.org/debian stretch/main i386 gcc-6-base i386 6.3.0-18 [180 kB]
Get:12 http://ftp.us.debian.org/debian stretch/main i386 libgcc1 i386 1:6.3.0-18 [48.0 kB]
Get:13 http://ftp.us.debian.org/debian stretch/main i386 libc6 i386 2.24-11+deb9u1 [2,466 kB]
Get:14 http://ftp.us.debian.org/debian stretch/non-free i386 libnvidia-glcore i386 375.82-1~deb9u1 [6,834 kB]
Get:15 http://ftp.us.debian.org/debian stretch/main i386 libxau6 i386 1:1.0.8-1 [20.9 kB]
Get:16 http://ftp.us.debian.org/debian stretch/main i386 libbsd0 i386 0.8.3-1 [86.5 kB]
Get:17 http://ftp.us.debian.org/debian stretch/main i386 libxdmcp6 i386 1:1.1.2-3 [26.7 kB]
Get:18 http://ftp.us.debian.org/debian stretch/main i386 libxcb1 i386 1.12-1 [138 kB]
Get:19 http://ftp.us.debian.org/debian stretch/main i386 libx11-6 i386 2:1.6.4-3 [771 kB]
Get:20 http://ftp.us.debian.org/debian stretch/main i386 libxext6 i386 2:1.3.3-1+b2 [55.2 kB]
Get:21 http://ftp.us.debian.org/debian stretch/non-free i386 libgl1-nvidia-glx i386 375.82-1~deb9u1 [562 kB]
Get:22 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-egl-common amd64 375.82-1~deb9u1 [172 kB]
Get:23 http://ftp.us.debian.org/debian stretch/non-free amd64 libgldispatch0-nvidia amd64 375.82-1~deb9u1 [214 kB]
Get:24 http://ftp.us.debian.org/debian stretch/non-free amd64 libegl1-glvnd-nvidia amd64 375.82-1~deb9u1 [197 kB]
Get:25 http://ftp.us.debian.org/debian stretch/non-free amd64 libnvidia-eglcore amd64 375.82-1~deb9u1 [6,353 kB]
Get:26 http://ftp.us.debian.org/debian stretch/non-free amd64 libegl-nvidia0 amd64 375.82-1~deb9u1 [336 kB]
Get:27 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-egl-icd amd64 375.82-1~deb9u1 [171 kB]
Get:28 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-driver-libs amd64 375.82-1~deb9u1 [171 kB]
Get:29 http://ftp.us.debian.org/debian stretch/non-free amd64 libnvidia-ml1 amd64 375.82-1~deb9u1 [550 kB]
Get:30 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-driver-bin amd64 375.82-1~deb9u1 [254 kB]
Get:31 http://ftp.us.debian.org/debian stretch/non-free amd64 xserver-xorg-video-nvidia amd64 375.82-1~deb9u1 [3,186 kB]
Get:32 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-vdpau-driver amd64 375.82-1~deb9u1 [699 kB]
Get:33 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-kernel-common amd64 20151021+4 [10.3 kB]
Get:34 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-modprobe amd64 375.26-1 [16.4 kB]
Get:35 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-kernel-support amd64 375.82-1~deb9u1 [172 kB]
Get:36 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-kernel-dkms amd64 375.82-1~deb9u1 [6,763 kB]
Get:37 http://ftp.us.debian.org/debian stretch/non-free amd64 nvidia-driver amd64 375.82-1~deb9u1 [466 kB]
Get:38 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-settings amd64 375.66-1 [882 kB]
Get:39 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-xconfig amd64 375.26-1 [82.1 kB]
Get:40 http://ftp.us.debian.org/debian stretch/non-free i386 libnvidia-eglcore i386 375.82-1~deb9u1 [6,731 kB]
Get:41 http://ftp.us.debian.org/debian stretch/non-free i386 libegl-nvidia0 i386 375.82-1~deb9u1 [302 kB]
Get:42 http://ftp.us.debian.org/debian stretch/non-free i386 libgldispatch0-nvidia i386 375.82-1~deb9u1 [209 kB]
Get:43 http://ftp.us.debian.org/debian stretch/non-free i386 libegl1-glvnd-nvidia i386 375.82-1~deb9u1 [195 kB]
Get:44 http://ftp.us.debian.org/debian stretch/non-free i386 libgles1-glvnd-nvidia i386 375.82-1~deb9u1 [179 kB]
Get:45 http://ftp.us.debian.org/debian stretch/non-free i386 libgles-nvidia1 i386 375.82-1~deb9u1 [187 kB]
Get:46 http://ftp.us.debian.org/debian stretch/non-free amd64 libgles1-glvnd-nvidia amd64 375.82-1~deb9u1 [180 kB]
Get:47 http://ftp.us.debian.org/debian stretch/non-free amd64 libgles-nvidia1 amd64 375.82-1~deb9u1 [188 kB]
Get:48 http://ftp.us.debian.org/debian stretch/non-free amd64 libgles2-glvnd-nvidia amd64 375.82-1~deb9u1 [182 kB]
Get:49 http://ftp.us.debian.org/debian stretch/non-free amd64 libgles-nvidia2 amd64 375.82-1~deb9u1 [193 kB]
Get:50 http://ftp.us.debian.org/debian stretch/non-free i386 libgles2-glvnd-nvidia i386 375.82-1~deb9u1 [181 kB]
Get:51 http://ftp.us.debian.org/debian stretch/non-free i386 libgles-nvidia2 i386 375.82-1~deb9u1 [192 kB]
Get:52 http://ftp.us.debian.org/debian stretch/non-free i386 libglx0-glvnd-nvidia i386 375.82-1~deb9u1 [192 kB]
Get:53 http://ftp.us.debian.org/debian stretch/non-free i386 libglx-nvidia0 i386 375.82-1~deb9u1 [408 kB]
Get:54 http://ftp.us.debian.org/debian stretch/non-free amd64 libglx0-glvnd-nvidia amd64 375.82-1~deb9u1 [193 kB]
Get:55 http://ftp.us.debian.org/debian stretch/non-free amd64 libglx-nvidia0 amd64 375.82-1~deb9u1 [422 kB]
Get:56 http://ftp.us.debian.org/debian stretch/non-free amd64 libnvidia-cfg1 amd64 375.82-1~deb9u1 [226 kB]
Get:57 http://ftp.us.debian.org/debian stretch/non-free i386 libnvidia-cfg1 i386 375.82-1~deb9u1 [227 kB]
Get:58 http://ftp.us.debian.org/debian stretch/non-free i386 libopengl0-glvnd-nvidia i386 375.82-1~deb9u1 [195 kB]
Get:59 http://ftp.us.debian.org/debian stretch/non-free amd64 libopengl0-glvnd-nvidia amd64 375.82-1~deb9u1 [197 kB]
Get:60 http://ftp.us.debian.org/debian stretch/non-free i386 nvidia-egl-icd i386 375.82-1~deb9u1 [171 kB]
Get:61 http://ftp.us.debian.org/debian stretch/non-free i386 nvidia-driver-libs i386 375.82-1~deb9u1 [171 kB]
Get:62 http://ftp.us.debian.org/debian stretch/non-free i386 nvidia-driver-libs-i386 i386 375.82-1~deb9u1 [171 kB]
Get:63 http://ftp.us.debian.org/debian stretch/contrib amd64 nvidia-persistenced amd64 375.26-2 [20.5 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Fetched 50.8 MB in 22min 26s (37.7 kB/s)
Selecting previously unselected package nvidia-installer-cleanup.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(....
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 231121 files and directories currently installed.)
Preparing to unpack .../nvidia-installer-cleanup_20151021+4_amd64.deb ...
Unpacking nvidia-installer-cleanup (20151021+4) ...
Selecting previously unselected package update-glx.
Preparing to unpack .../update-glx_0.7.4_amd64.deb ...
Unpacking update-glx (0.7.4) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_0.7.4_amd64.deb ...
Unpacking glx-alternative-mesa (0.7.4) ...
Setting up nvidia-installer-cleanup (20151021+4) ...
Selecting previously unselected package glx-diversions.
(Reading database ... 
(Reading database ... 5%
(...
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 231236 files and directories currently installed.)
Preparing to unpack .../glx-diversions_0.7.4_amd64.deb ...
Unpacking glx-diversions (0.7.4) ...
Selecting previously unselected package nvidia-legacy-check.
Preparing to unpack .../nvidia-legacy-check_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-legacy-check (375.82-1~deb9u1) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../glx-alternative-nvidia_0.7.4_amd64.deb ...
Unpacking glx-alternative-nvidia (0.7.4) ...
Setting up nvidia-legacy-check (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-alternative.
(Reading database ... 
(Reading database ... 5%
...
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 231266 files and directories currently installed.)
Preparing to unpack .../00-nvidia-alternative_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-alternative (375.82-1~deb9u1) ...
Selecting previously unselected package gcc-6-base:i386.
Preparing to unpack .../01-gcc-6-base_6.3.0-18_i386.deb ...
Unpacking gcc-6-base:i386 (6.3.0-18) ...
Selecting previously unselected package libgcc1:i386.
Preparing to unpack .../02-libgcc1_1%3a6.3.0-18_i386.deb ...
Unpacking libgcc1:i386 (1:6.3.0-18) ...
Selecting previously unselected package libc6:i386.
Preparing to unpack .../03-libc6_2.24-11+deb9u1_i386.deb ...
Unpacking libc6:i386 (2.24-11+deb9u1) ...
Selecting previously unselected package libnvidia-glcore:i386.
Preparing to unpack .../04-libnvidia-glcore_375.82-1~deb9u1_i386.deb ...
Unpacking libnvidia-glcore:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-support.
Preparing to unpack .../05-nvidia-support_20151021+4_amd64.deb ...
Unpacking nvidia-support (20151021+4) ...
Selecting previously unselected package libxau6:i386.
Preparing to unpack .../06-libxau6_1%3a1.0.8-1_i386.deb ...
Unpacking libxau6:i386 (1:1.0.8-1) ...
Selecting previously unselected package libbsd0:i386.
Preparing to unpack .../07-libbsd0_0.8.3-1_i386.deb ...
Unpacking libbsd0:i386 (0.8.3-1) ...
Selecting previously unselected package libxdmcp6:i386.
Preparing to unpack .../08-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Unpacking libxdmcp6:i386 (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:i386.
Preparing to unpack .../09-libxcb1_1.12-1_i386.deb ...
Unpacking libxcb1:i386 (1.12-1) ...
Selecting previously unselected package libx11-6:i386.
Preparing to unpack .../10-libx11-6_2%3a1.6.4-3_i386.deb ...
Unpacking libx11-6:i386 (2:1.6.4-3) ...
Selecting previously unselected package libxext6:i386.
Preparing to unpack .../11-libxext6_2%3a1.3.3-1+b2_i386.deb ...
Unpacking libxext6:i386 (2:1.3.3-1+b2) ...
Selecting previously unselected package libgl1-nvidia-glx:i386.
Preparing to unpack .../12-libgl1-nvidia-glx_375.82-1~deb9u1_i386.deb ...
Unpacking libgl1-nvidia-glx:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libnvidia-glcore:amd64.
Preparing to unpack .../13-libnvidia-glcore_375.82-1~deb9u1_amd64.deb ...
Unpacking libnvidia-glcore:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libgl1-nvidia-glx:amd64.
Preparing to unpack .../14-libgl1-nvidia-glx_375.82-1~deb9u1_amd64.deb ...
Unpacking libgl1-nvidia-glx:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-egl-common.
Preparing to unpack .../15-nvidia-egl-common_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-egl-common (375.82-1~deb9u1) ...
Selecting previously unselected package libgldispatch0-nvidia:amd64.
Preparing to unpack .../16-libgldispatch0-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking libgldispatch0-nvidia:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libegl1-glvnd-nvidia:amd64.
Preparing to unpack .../17-libegl1-glvnd-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking libegl1-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libnvidia-eglcore:amd64.
Preparing to unpack .../18-libnvidia-eglcore_375.82-1~deb9u1_amd64.deb ...
Unpacking libnvidia-eglcore:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libegl-nvidia0:amd64.
Preparing to unpack .../19-libegl-nvidia0_375.82-1~deb9u1_amd64.deb ...
Unpacking libegl-nvidia0:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-egl-icd:amd64.
Preparing to unpack .../20-nvidia-egl-icd_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-egl-icd:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-driver-libs:amd64.
Preparing to unpack .../21-nvidia-driver-libs_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-driver-libs:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libnvidia-ml1:amd64.
Preparing to unpack .../22-libnvidia-ml1_375.82-1~deb9u1_amd64.deb ...
Unpacking libnvidia-ml1:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-driver-bin.
Preparing to unpack .../23-nvidia-driver-bin_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-driver-bin (375.82-1~deb9u1) ...
Selecting previously unselected package xserver-xorg-video-nvidia.
Preparing to unpack .../24-xserver-xorg-video-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking xserver-xorg-video-nvidia (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-vdpau-driver:amd64.
Preparing to unpack .../25-nvidia-vdpau-driver_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-vdpau-driver:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-kernel-common.
Preparing to unpack .../26-nvidia-kernel-common_20151021+4_amd64.deb ...
Unpacking nvidia-kernel-common (20151021+4) ...
Selecting previously unselected package nvidia-modprobe.
Preparing to unpack .../27-nvidia-modprobe_375.26-1_amd64.deb ...
Unpacking nvidia-modprobe (375.26-1) ...
Selecting previously unselected package nvidia-kernel-support.
Preparing to unpack .../28-nvidia-kernel-support_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-kernel-support (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-kernel-dkms.
Preparing to unpack .../29-nvidia-kernel-dkms_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-kernel-dkms (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-driver.
Preparing to unpack .../30-nvidia-driver_375.82-1~deb9u1_amd64.deb ...
Unpacking nvidia-driver (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-settings.
Preparing to unpack .../31-nvidia-settings_375.66-1_amd64.deb ...
Unpacking nvidia-settings (375.66-1) ...
Selecting previously unselected package nvidia-xconfig.
Preparing to unpack .../32-nvidia-xconfig_375.26-1_amd64.deb ...
Unpacking nvidia-xconfig (375.26-1) ...
Selecting previously unselected package libnvidia-eglcore:i386.
Preparing to unpack .../33-libnvidia-eglcore_375.82-1~deb9u1_i386.deb ...
Unpacking libnvidia-eglcore:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libegl-nvidia0:i386.
Preparing to unpack .../34-libegl-nvidia0_375.82-1~deb9u1_i386.deb ...
Unpacking libegl-nvidia0:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libgldispatch0-nvidia:i386.
Preparing to unpack .../35-libgldispatch0-nvidia_375.82-1~deb9u1_i386.deb ...
Unpacking libgldispatch0-nvidia:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libegl1-glvnd-nvidia:i386.
Preparing to unpack .../36-libegl1-glvnd-nvidia_375.82-1~deb9u1_i386.deb ...
Unpacking libegl1-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles1-glvnd-nvidia:i386.
Preparing to unpack .../37-libgles1-glvnd-nvidia_375.82-1~deb9u1_i386.deb ...
Unpacking libgles1-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles-nvidia1:i386.
Preparing to unpack .../38-libgles-nvidia1_375.82-1~deb9u1_i386.deb ...
Unpacking libgles-nvidia1:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles1-glvnd-nvidia:amd64.
Preparing to unpack .../39-libgles1-glvnd-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking libgles1-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles-nvidia1:amd64.
Preparing to unpack .../40-libgles-nvidia1_375.82-1~deb9u1_amd64.deb ...
Unpacking libgles-nvidia1:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles2-glvnd-nvidia:amd64.
Preparing to unpack .../41-libgles2-glvnd-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking libgles2-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles-nvidia2:amd64.
Preparing to unpack .../42-libgles-nvidia2_375.82-1~deb9u1_amd64.deb ...
Unpacking libgles-nvidia2:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles2-glvnd-nvidia:i386.
Preparing to unpack .../43-libgles2-glvnd-nvidia_375.82-1~deb9u1_i386.deb ...
Unpacking libgles2-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libgles-nvidia2:i386.
Preparing to unpack .../44-libgles-nvidia2_375.82-1~deb9u1_i386.deb ...
Unpacking libgles-nvidia2:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libglx0-glvnd-nvidia:amd64.
Preparing to unpack .../45-libglx0-glvnd-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking libglx0-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libglx-nvidia0:amd64.
Preparing to unpack .../46-libglx-nvidia0_375.82-1~deb9u1_amd64.deb ...
Unpacking libglx-nvidia0:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libglx0-glvnd-nvidia:i386.
Preparing to unpack .../47-libglx0-glvnd-nvidia_375.82-1~deb9u1_i386.deb ...
Unpacking libglx0-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libglx-nvidia0:i386.
Preparing to unpack .../48-libglx-nvidia0_375.82-1~deb9u1_i386.deb ...
Unpacking libglx-nvidia0:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libnvidia-cfg1:amd64.
Preparing to unpack .../49-libnvidia-cfg1_375.82-1~deb9u1_amd64.deb ...
Unpacking libnvidia-cfg1:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package libnvidia-cfg1:i386.
Preparing to unpack .../50-libnvidia-cfg1_375.82-1~deb9u1_i386.deb ...
Unpacking libnvidia-cfg1:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libopengl0-glvnd-nvidia:i386.
Preparing to unpack .../51-libopengl0-glvnd-nvidia_375.82-1~deb9u1_i386.deb ...
Unpacking libopengl0-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package libopengl0-glvnd-nvidia:amd64.
Preparing to unpack .../52-libopengl0-glvnd-nvidia_375.82-1~deb9u1_amd64.deb ...
Unpacking libopengl0-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-egl-icd:i386.
Preparing to unpack .../53-nvidia-egl-icd_375.82-1~deb9u1_i386.deb ...
Unpacking nvidia-egl-icd:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-driver-libs:i386.
Preparing to unpack .../54-nvidia-driver-libs_375.82-1~deb9u1_i386.deb ...
Unpacking nvidia-driver-libs:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-driver-libs-i386:i386.
Preparing to unpack .../55-nvidia-driver-libs-i386_375.82-1~deb9u1_i386.deb ...
Unpacking nvidia-driver-libs-i386:i386 (375.82-1~deb9u1) ...
Selecting previously unselected package nvidia-persistenced.
Preparing to unpack .../56-nvidia-persistenced_375.26-2_amd64.deb ...
Unpacking nvidia-persistenced (375.26-2) ...
Setting up nvidia-kernel-common (20151021+4) ...
Processing triggers for mime-support (3.60) ...
Setting up libnvidia-eglcore:amd64 (375.82-1~deb9u1) ...
Setting up libgldispatch0-nvidia:amd64 (375.82-1~deb9u1) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up nvidia-support (20151021+4) ...
Setting up update-glx (0.7.4) ...Re: MX-17 Beta 1 Feedback Thread
Setting up gcc-6-base:i386 (6.3.0-18) ...
Setting up libnvidia-glcore:amd64 (375.82-1~deb9u1) ...
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Setting up nvidia-xconfig (375.26-1) ...
Setting up nvidia-egl-common (375.82-1~deb9u1) ...
Setting up nvidia-modprobe (375.26-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up glx-alternative-mesa (0.7.4) ...
Setting up libopengl0-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Setting up glx-diversions (0.7.4) ...
Processing triggers for glx-alternative-mesa (0.7.4) ...
update-alternatives: using /usr/lib/mesa-diverted to provide /usr/lib/glx (glx) in auto mode
Setting up glx-alternative-nvidia (0.7.4) ...
Processing triggers for glx-alternative-nvidia (0.7.4) ...
Setting up nvidia-alternative (375.82-1~deb9u1) ...
Processing triggers for nvidia-alternative (375.82-1~deb9u1) ...
update-alternatives: using /usr/lib/nvidia/current to provide /usr/lib/nvidia/nvidia (nvidia) in auto mode
Setting up libgl1-nvidia-glx:amd64 (375.82-1~deb9u1) ...
[?1049h[1;24r[4l[?25l(B[m[37m[40m[1;24r[H[2J[1;1H[97m[44m[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K
[K[1;1H[37mPackage configuration[6;3H[30m[47m┌─────────────────┤ [31mConfiguring libgl1-nvidia-glx:amd64[30m ├─────────────────┐[7;3H│                                                                         │[97m[40m [8;3H[30m[47m│ Conflicting nouveau kernel module loaded                                │[97m[40m [9;3H[30m[47m│                                                                         │[97m[40m [10;3H[30m[47m│ The free nouveau kernel module is currently loaded and conflicts with   │[97m[40m [11;3H[30m[47m│ the non-free nvidia kernel module.                                      │[97m[40m [12;3H[30m[47m│                                                                         │[97m[40m [13;3H[30m[47m│ The easiest way to fix this is to reboot the machine once the           │[97m[40m [14;3H[30m[47m│ installation has finished.                                              │[97m[40m [15;3H[30m[47m│                                                                         │[97m[40m [16;3H[30m[47m│                                 [37m[41m<Ok>[30m[47m                                    │[97m[40m [17;3H[30m[47m│                                                                         │[97m[40m [18;3H[30m[47m└─────────────────────────────────────────────────────────────────────────┘[97m[40m [19;4H                                                                           [16;38H[?12l[?25h[24;1H[37m(B[m[39;49m
[K
[?1049lSetting up libglx0-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Setting up nvidia-kernel-support (375.82-1~deb9u1) ...
Setting up nvidia-settings (375.66-1) ...
Setting up nvidia-vdpau-driver:amd64 (375.82-1~deb9u1) ...
Setting up libegl1-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Setting up libegl-nvidia0:amd64 (375.82-1~deb9u1) ...
Setting up libnvidia-cfg1:amd64 (375.82-1~deb9u1) ...
Setting up libgles1-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Setting up libnvidia-ml1:amd64 (375.82-1~deb9u1) ...
Setting up libgles-nvidia1:amd64 (375.82-1~deb9u1) ...
Setting up xserver-xorg-video-nvidia (375.82-1~deb9u1) ...
Setting up nvidia-driver-bin (375.82-1~deb9u1) ...
Setting up nvidia-persistenced (375.26-2) ...
Setting up libgles2-glvnd-nvidia:amd64 (375.82-1~deb9u1) ...
Setting up libglx-nvidia0:amd64 (375.82-1~deb9u1) ...
Setting up nvidia-egl-icd:amd64 (375.82-1~deb9u1) ...
Setting up libgles-nvidia2:amd64 (375.82-1~deb9u1) ...
Setting up nvidia-driver-libs:amd64 (375.82-1~deb9u1) ...
Processing triggers for nvidia-alternative (375.82-1~deb9u1) ...
update-alternatives: updating alternative /usr/lib/nvidia/current because link group nvidia has changed slave links
Setting up nvidia-kernel-dkms (375.82-1~deb9u1) ...
Loading new nvidia-current-375.82 DKMS files...
Building for 4.9.0-4-amd64
Building initial module for 4.9.0-4-amd64
Done.

nvidia-current:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.9.0-4-amd64/updates/dkms/

nvidia-current-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.9.0-4-amd64/updates/dkms/

nvidia-current-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.9.0-4-amd64/updates/dkms/

nvidia-current-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.9.0-4-amd64/updates/dkms/

depmod...

DKMS: install completed.
Setting up nvidia-driver (375.82-1~deb9u1) ...
Setting up libc6:i386 (2.24-11+deb9u1) ...
Setting up libbsd0:i386 (0.8.3-1) ...
Setting up libnvidia-cfg1:i386 (375.82-1~deb9u1) ...
Setting up libxdmcp6:i386 (1:1.1.2-3) ...
Setting up libxau6:i386 (1:1.0.8-1) ...
Setting up libgcc1:i386 (1:6.3.0-18) ...
Setting up libnvidia-eglcore:i386 (375.82-1~deb9u1) ...
Setting up libgldispatch0-nvidia:i386 (375.82-1~deb9u1) ...
Setting up libgles2-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Setting up libnvidia-glcore:i386 (375.82-1~deb9u1) ...
Setting up libegl1-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Setting up libegl-nvidia0:i386 (375.82-1~deb9u1) ...
Setting up libgles-nvidia2:i386 (375.82-1~deb9u1) ...
Setting up libgles1-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Setting up libgles-nvidia1:i386 (375.82-1~deb9u1) ...
Setting up libxcb1:i386 (1.12-1) ...
Setting up libopengl0-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Setting up libx11-6:i386 (2:1.6.4-3) ...
Setting up nvidia-egl-icd:i386 (375.82-1~deb9u1) ...
Setting up libxext6:i386 (2:1.3.3-1+b2) ...
Setting up libgl1-nvidia-glx:i386 (375.82-1~deb9u1) ...
Setting up libglx0-glvnd-nvidia:i386 (375.82-1~deb9u1) ...
Setting up nvidia-driver-libs:i386 (375.82-1~deb9u1) ...
Setting up libglx-nvidia0:i386 (375.82-1~deb9u1) ...
Setting up nvidia-driver-libs-i386:i386 (375.82-1~deb9u1) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for update-glx (0.7.4) ...
Processing triggers for glx-alternative-nvidia (0.7.4) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-4-amd64
cryptsetup: WARNING: failed to detect canonical device of /dev/sda7
I: The initramfs will attempt to resume from /dev/nvme0n1p2
I: (UUID=4ce88423-c5cf-4a69-b6d4-1d9fcafa7353)
I: Set the RESUME variable to override this.
New X configuration file written to '/etc/X11/xorg.conf'
Finished
Press <Enter> to exit

Posted: **Thu Nov 09, 2017 10:40 pm**

richb wrote:
Stevo wrote:But isn't that 1000 fps a lot slower than the integrated GPU?
No it is 60 for the integrated intel.

Here is the latest virtualgl: https://drive.google.com/open?id=1GEVdo ... mBjoYDMKec

You only need to install the virtualgl deb for your release and architecture, then you get the glxspheres benchmark on 32 and glxspheres64 on 64-bit.
Thanks. I am not on the laptop right now. But will get it when I am. By the way I remembered glxspheres is a better comparison. It will be interesting to see how that fares.

You also have to run the test for the Intel GPU with this command so you won't get 60 fps:

Code: Select all

vblank_mode=0 glxgears

Posted: **Thu Nov 09, 2017 11:22 pm**

Glmark2 can help with some quick GPU testing too, it “was” in the testing repo if I remember right.

Posted: **Fri Nov 10, 2017 4:17 am**

BitJam wrote:
Gaer Boy wrote: What does 'Console columns' do? Accepted all other defaults.
We will select a console font size so there will be roughly that many columns of console text. The default value is 120 so we select a font size so there are roughly 120 columns of text....

Thanks for the detailed explanation. The default worked fine for me.

Phil

Posted: **Fri Nov 10, 2017 5:39 am**

You also have to run the test for the Intel GPU with this command so you won't get 60 fps:

Indeed, about 7800 fps

Found this explanation on an Ubuntu site. Accurate?

vblank_mode=0 tells the graphic card to ignore the refresh rate of your monitor and just try to reach the maximux fps it's capable off.

You usually don't want this, because it causes tearing and wastes battery life without any benefits (you can't view more then, in your case, 60fps because your monitor isn't able to change what's displaying more than 60 times every second).

You might sometimes want this (in online shooters such as cs:go for example) because otherwise you will have a lot of input lag. It's a trade-off, input lag vs. screen tearing.

I think optirun sets vblank_mode=0 by default, so it doesn't change whether you specify it or not. primusrun doesn't and it too caps at 60 fps without vblank_mode=0.

Posted: **Fri Nov 10, 2017 8:57 am**

MX17 b1 is working very nicely out of the box on my laptop - much better than 16 was.
As I reported with MX17 a5 the server in the MX Package Installer does not work. It opens momentarily then asks if you want to exit. MX16 had php5.6.x MX17 has php7.x

Code: Select all

$ inxi -F
System:    Host: Loretta Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: laptop System: ASUSTeK product: X550LA v: 1.0 serial: N/A
           Mobo: ASUSTeK model: X550LA v: 1.0 serial: N/A
           UEFI: American Megatrends v: X550LA.403 date: 11/26/2013
Battery    BAT0: charge: 33.1 Wh 97.2% condition: 34.1/37.8 Wh (90%)
CPU:       Dual core Intel Core i5-4200U (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2600 MHz 1: 1041 MHz 2: 897 MHz 3: 972 MHz 4: 897 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.06hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 3.3 Mesa 13.0.6
Audio:     Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel
           Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: enp2s0f1 state: down mac: e0:3f:49:d6:e7:7d
           Card-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
           IF: wlp3s0f0 state: up mac: 54:35:30:21:fa:95
           Card-3: Atmel
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 500.1GB (3.8% used)
           ID-1: /dev/sda model: HGST_HTS545050A7 size: 500.1GB
Partition: ID-1: / size: 39G used: 5.7G (16%) fs: ext4 dev: /dev/sda11
           ID-2: /home size: 58G used: 1019M (2%) fs: ext4 dev: /dev/sda12
           ID-3: swap-1 size: 12.58GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
Sensors:   System Temperatures: cpu: 30.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 209 Uptime: 2 min Memory: 484.3/5855.9MB Client: Shell (bash) inxi: 2.3.40

Posted: **Fri Nov 10, 2017 9:09 am**

peregrine wrote:MX17 b1 is working very nicely out of the box on my laptop - much better than 16 was.
As I reported with MX17 a5 the server in the MX Package Installer does not work. It opens momentarily then asks if you want to exit. MX16 had php5.6.x MX17 has php7.x

Code: Select all

$ inxi -F
System:    Host: Loretta Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: laptop System: ASUSTeK product: X550LA v: 1.0 serial: N/A
           Mobo: ASUSTeK model: X550LA v: 1.0 serial: N/A
           UEFI: American Megatrends v: X550LA.403 date: 11/26/2013
Battery    BAT0: charge: 33.1 Wh 97.2% condition: 34.1/37.8 Wh (90%)
CPU:       Dual core Intel Core i5-4200U (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2600 MHz 1: 1041 MHz 2: 897 MHz 3: 972 MHz 4: 897 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.06hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 3.3 Mesa 13.0.6
Audio:     Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel
           Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: enp2s0f1 state: down mac: e0:3f:49:d6:e7:7d
           Card-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
           IF: wlp3s0f0 state: up mac: 54:35:30:21:fa:95
           Card-3: Atmel
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 500.1GB (3.8% used)
           ID-1: /dev/sda model: HGST_HTS545050A7 size: 500.1GB
Partition: ID-1: / size: 39G used: 5.7G (16%) fs: ext4 dev: /dev/sda11
           ID-2: /home size: 58G used: 1019M (2%) fs: ext4 dev: /dev/sda12
           ID-3: swap-1 size: 12.58GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
Sensors:   System Temperatures: cpu: 30.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 209 Uptime: 2 min Memory: 484.3/5855.9MB Client: Shell (bash) inxi: 2.3.40

got it, thanks!

Posted: **Fri Nov 10, 2017 9:10 am**

dolphin_oracle wrote:

peregrine wrote:MX17 b1 is working very nicely out of the box on my laptop - much better than 16 was.
As I reported with MX17 a5 the server in the MX Package Installer does not work. It opens momentarily then asks if you want to exit. MX16 had php5.6.x MX17 has php7.x

Code: Select all

$ inxi -F
System:    Host: Loretta Kernel: 4.9.0-4-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: laptop System: ASUSTeK product: X550LA v: 1.0 serial: N/A
           Mobo: ASUSTeK model: X550LA v: 1.0 serial: N/A
           UEFI: American Megatrends v: X550LA.403 date: 11/26/2013
Battery    BAT0: charge: 33.1 Wh 97.2% condition: 34.1/37.8 Wh (90%)
CPU:       Dual core Intel Core i5-4200U (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2600 MHz 1: 1041 MHz 2: 897 MHz 3: 972 MHz 4: 897 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.06hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 3.3 Mesa 13.0.6
Audio:     Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel
           Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: enp2s0f1 state: down mac: e0:3f:49:d6:e7:7d
           Card-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
           IF: wlp3s0f0 state: up mac: 54:35:30:21:fa:95
           Card-3: Atmel
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 500.1GB (3.8% used)
           ID-1: /dev/sda model: HGST_HTS545050A7 size: 500.1GB
Partition: ID-1: / size: 39G used: 5.7G (16%) fs: ext4 dev: /dev/sda11
           ID-2: /home size: 58G used: 1019M (2%) fs: ext4 dev: /dev/sda12
           ID-3: swap-1 size: 12.58GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
Sensors:   System Temperatures: cpu: 30.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 209 Uptime: 2 min Memory: 484.3/5855.9MB Client: Shell (bash) inxi: 2.3.40

got it, thanks!

by the way, if you are up to day, there should be a /var/log/mxpi.log file with all the info from your session. if you could post that, it will save me a lot of time.

Posted: **Fri Nov 10, 2017 9:24 am**

I will be glad to help. I have MX17b1 installed on two laptops. On the HP I tried the MXPI unsuccessfully and on the ASUS I manually installed the server. I do not see a /var/log/mxpi.log file.

Posted: **Fri Nov 10, 2017 9:26 am**

peregrine wrote:I will be glad to help. I have MX17b1 installed on two laptops. On the HP I tried the MXPI unsuccessfully and on the ASUS I manually installed the server. I do not see a /var/log/mxpi.log file.

ok, the version on b1 didn't originally have a log, so maybe the updated one hasn't landed yet. I've got it installed on my system at home, testing out the logging feature.

Don't worry about it for this one...you gave me enough to track it down easy enough.

Posted: **Fri Nov 10, 2017 9:40 am**

I thought this info might be useful from my server install

MariaDB is recommended over MySQL. As a matter of fact, if you try to install MySQL on Debian 9 using the following command, it will install MariaDB and set MariaDB as the default database server.

Code: Select all

apt install mysql-server mysql-client

Be glad to test when the time comes

Posted: **Fri Nov 10, 2017 9:56 am**

peregrine wrote:I thought this info might be useful from my server install
MariaDB is recommended over MySQL. As a matter of fact, if you try to install MySQL on Debian 9 using the following command, it will install MariaDB and set MariaDB as the default database server.
Code: Select all
apt install mysql-server mysql-client
Be glad to test when the time comes

ok, so should we go ahead and change the file to MariaDB then? Probably, or the uninstall info might not work correctly. But does that make sense on your end?

Here's the current list (corrected for php 7) that "local web server" installs. Could you provide any comment?

Code: Select all

apache2
apache2-utils
apache2-mpm-prefork
php7.0
php7.0-common
mysql-server
mysql-common
libapache2-mod-php7.0
php7.0-mysqll
phpmyadmin

Posted: **Fri Nov 10, 2017 10:27 am**

replied in dev forum

Posted: **Fri Nov 10, 2017 6:04 pm**

Screenfetch not installed by default, huh? And when it is, we get the Debian logo. We've talked about this in the past, I remember, but I don't recall if we ever ended up with anything definite.

Posted: **Fri Nov 10, 2017 6:38 pm**

Jerry3904 wrote:Screenfetch not installed by default, huh? And when it is, we get the Debian logo. We've talked about this in the past, I remember, but I don't recall if we ever ended up with anything definite.

Most of the discussion in the past has been about Neofetch...I don't think we did a custom version for Mx 17 yet.

Posted: **Fri Nov 10, 2017 6:42 pm**

Does any user know about neofetch? Screenfetch is pretty widely known IMO

Posted: **Fri Nov 10, 2017 6:56 pm**

Yes, but Neofetch is actively developed and shows the MX logo...at least with the version I just backported from Buster: https://drive.google.com/open?id=1C2ReX ... E8wIwyIPSY

I think that Neofetch also is getting better known. Maybe we could add something that runs neofetch when they invoke screenfetch.

Posted: **Fri Nov 10, 2017 8:42 pm**

here 'tis on MX17b1

ScreenshotEDIT.png

Posted: **Sat Nov 11, 2017 4:03 am**

I installed 17beta1 on my Toshiba-Satellite Laptop, which is UEFI .
Sorry to say, after the successfull installation, the grub-menu (some call it boot-menu) takes about 45 seconds to appear.
( I have other distros on the laptop and win10 too, so I need the grub-menu to select the OS I want to start )

Before this installation, when I pressed the power-button of the laptop to start it, there appeared the toshiba screen for about 2 seconds, then the grub-menu appeared instantly.

Now I press the power-button and the toshiba screen appears for about 2 seconds, then for a split second there seems to be happening something which normally shows the grub-menu, but now nothing happens, the screen remains grey for about 45 seconds and only then the grub-menu appears.

I am afraid something is messed up and I must wipe the harddrive and format it in order to make completely new installations of win10 and the linux distros. This would take many hours.

I hope you can help me to avoid this. Thank you.

The inxi -F is from MX-16.1 which I installed too, hoping the new installed grub from it would fix the problem, but it didn't fix it.
Anyways, the info about this laptop is the same as it would be with mx-17

Code: Select all

inxi -F
System:    Host: laptop Kernel: 4.7.0-0.bpo.1-amd64 x86_64 (64 bit) Desktop: Xfce 4.12.2
           Distro: MX-16.1_x64 Metamorphosis 8 June 2017
Machine:   Device: laptop System: TOSHIBA product: SATELLITE C850-19D v: PSCBWE-03200WGR
           Mobo: Intel model: PLCSF8 v: Type2 - Board Version
           UEFI: Insyde v: 6.80 date: 10/01/2013
CPU:       Dual core Intel Celeron B830 (-MCP-) cache: 2048 KB 
           clock speeds: max: 1800 MHz 1: 799 MHz 2: 799 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.07hz
           GLX Renderer: Mesa DRI Intel Sandybridge Mobile GLX Version: 3.0 Mesa 12.0.3
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.7.0-0.bpo.1-amd64
Network:   Card-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce
           IF: wlan0 state: down mac: 20:16:d8:65:02:84
           Card-2: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 70:54:d2:47:e1:f0
Drives:    HDD Total Size: 320.1GB (7.5% used)
           ID-1: /dev/sda model: TOSHIBA_MQ01ABD0 size: 320.1GB
Partition: ID-1: / size: 26G used: 6.0G (25%) fs: ext4 dev: /dev/sda8
           ID-2: swap-1 size: 5.12GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 50.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 185 Uptime: 1:38 Memory: 718.6/3836.2MB Client: Shell (bash) inxi: 2.3.11

Posted: **Sat Nov 11, 2017 7:35 am**

Did Grub work correctly when you were running Live?

Posted: **Sat Nov 11, 2017 8:23 am**

If you are booting uefi, them the former grub installs and windows bootloader should still be present in the esp partition. You can use your uefi setup (bios) to choose which one to boot. Oldmlinux grubs will only work if the former linux installs are still present but the windows ones should work.

It is also sometimes beneficial to remove bootloader you arent using.

Posted: **Sat Nov 11, 2017 9:34 am**

Will this beta will receive future updates ? I'm interested in being à tester but a bit lazy to install again each Times.

Posted: **Sat Nov 11, 2017 9:42 am**

monsieurzik wrote:Will this beta will receive future updates ? I'm interested in being à tester but a bit lazy to install again each Times.

There may be updates for a given test release, but there will not be an upgrade path from one version to the next.

Don't install unless you are prepared for things to break, and are prepared to reinstall when the next beta comes out.

You can still help by testing live however.

Chris

Posted: **Sat Nov 11, 2017 9:47 am**

monsieurzik wrote:Will this beta will receive future updates ? I'm interested in being à tester but a bit lazy to install again each Times.

its actually received several already. However, some of the live features and some odds and ends might not be in an update without getting the next beta iso.

Posted: **Sat Nov 11, 2017 11:13 am**

dolphin_oracle wrote:If you are booting uefi, them the former grub installs and windows bootloader should still be present in the esp partition. You can use your uefi setup (bios) to choose which one to boot. Oldmlinux grubs will only work if the former linux installs are still present but the windows ones should work.

It is also sometimes beneficial to remove bootloader you arent using.

Sorry, it must be because I am not english, but I don't grasp what you are trying to tell me.

During installation of MX-17 and later MX-16.1 on this uefi-laptop, the installer asked me where I want the grub to be installed. It had 3 options. MBR , Root and esp.
Since I installed about 100 different distros on this laptop in order to test them, I know that grub must go into esp, therefore I chose that.
The installation ended successfully.

In the boot-menu which appears after start, I can chose which OS I want to boot.
There is Win10, LinuxMint 17.3, LinuxMint 18.2, Peppermint-8, MX-16.1 and MX-17beta-1 .

Each does start correctly when I chose it.

The problem is that it takes about 45 seconds until the boot-menu appears.
The installer of MX-17beta-1 ruined something in my laptop.
Because before I installed it, the boot-menu appeared after 2 seconds since I press the power-button.
The first 2 seconds, the logo screen from Toshiba appeared, then immediately the boot-menu.
Now it is not immediately, but takes 45 seconds.
That is my problem.

I hope that I expressed it in an understandable way because in the past I ran into problems because of the words I used.
boot-menu, grub-menu or something and that caused misunderstandings.
Somewhere in a tutorial of Toshiba they used the name "GNU GRUB menu", maybe that is the correct word, I don't know.

I made a screenshot from the Toshiba tutorial which shows the grub-boot-menu which in my case appears much too late.

Posted: **Sat Nov 11, 2017 11:38 am**

When you installed MX, did you format swap partition or select the "no swap or using existing swap" option?
In your boot or grub menu, which distro/OS is listed first?

Posted: **Sat Nov 11, 2017 11:45 am**

I selected the "no swap or using existing swap" option.

In the grub menu MX16.1 is listed first because I installed it after the installation of MX17beta-1.

Posted: **Sat Nov 11, 2017 11:50 am**

The /var/log/boot file may tell you something. You can post it here and perhaps someone will see an anomaly.

Posted: **Sat Nov 11, 2017 12:11 pm**

Here is the /var/log/boot file.
Never saw that file before.
From what I understand of it, the log is started when I select an OS from the grub-boot-menu and press "Enter", because from there to the login-screen it takes 25 seconds on my laptop.
So the big lag of more than 40 seconds happens before the log is started and therefore not recorded.
Maybe there is a log somewhere for that gap ?

Code: Select all

Sat Nov 11 08:52:22 2017: [....] Setting parameters of disc: (none)^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:22 2017: [....] Setting preliminary keymap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:24 2017: [....] Activating swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:24 2017: [....] Checking root file system...fsck from util-linux 2.25.2
Sat Nov 11 08:52:24 2017: rootMX16: clean, 195378/1708784 files, 1254692/6833152 blocks
Sat Nov 11 08:52:24 2017: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:24 2017: [....] Cleaning up temporary files... /tmp^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:24 2017: [....] Starting early crypto disks...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [^[[36minfo^[[39;49m] Loading kernel module lp.
Sat Nov 11 08:52:25 2017: [^[[36minfo^[[39;49m] Loading kernel module ppdev.
Sat Nov 11 08:52:25 2017: [^[[36minfo^[[39;49m] Loading kernel module parport_pc.
Sat Nov 11 08:52:25 2017: [^[[36minfo^[[39;49m] Loading kernel module loop.
Sat Nov 11 08:52:25 2017: [^[[36minfo^[[39;49m] Loading kernel module ecryptfs.
Sat Nov 11 08:52:25 2017: [^[[36minfo^[[39;49m] Loading kernel module fuse.
Sat Nov 11 08:52:25 2017: [....] Setting up LVM Volume Groups...  No volume groups found
Sat Nov 11 08:52:25 2017: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Starting remaining crypto disks...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Activating lvm and md swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Checking file systems...fsck from util-linux 2.25.2
Sat Nov 11 08:52:25 2017: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Mounting local filesystems...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Activating swapfile swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Cleaning up temporary files...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:25 2017: [....] Skip starting firewall: ufw (not enabled)...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:25 2017: [....] Setting kernel variables ...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:26 2017: Running 0dns-down to make sure resolv.conf is ok...done.
Sat Nov 11 08:52:26 2017: [....] Configuring network interfaces...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:26 2017: [....] Starting rpcbind daemon...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:27 2017: [....] Starting NFS common utilities: statd idmapd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:27 2017: [....] Cleaning up temporary files...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:27 2017: [....] Setting up ALSA...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:27 2017: [^[[36minfo^[[39;49m] Setting console screen modes.
Sat Nov 11 08:52:27 2017: ^[[9;30]^[[14;30][....] Setting up console font and keymap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:28 2017: [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:28 2017: [....] Setting sensors limits^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:28 2017: INIT: Entering runlevel: 5
Sat Nov 11 08:52:28 2017: [^[[36minfo^[[39;49m] Using makefile-style concurrent boot in runlevel 5.
Sat Nov 11 08:52:29 2017: Setting battery charge thresholds...done.
Sat Nov 11 08:52:29 2017: [....] Not starting NFS kernel daemon: no exports. ...^[[?25l^[[?1c^[7^[[1G[^[[33mwarn^[[39;49m^[8^[[?25h^[[?0c ^[[33m(warning).^[[39;49m
Sat Nov 11 08:52:29 2017: [....] Starting acpi_fakekey daemon...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:29 2017: [....] Starting enhanced syslogd: rsyslogd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:29 2017: [....] Starting anac(h)ronistic cron: anacron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:29 2017: [....] Starting ACPI services...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:29 2017: [....] Starting deferred execution scheduler: atd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:30 2017: [....] Starting periodic command scheduler: cron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:30 2017: [....] Starting cgroup management daemon: cgmanager[....] Starting cgroup management proxy daemon: cgproxy^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:30 2017: [....] Starting Common Unix Printing System: cupsd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:31 2017: [....] Starting CUPS Bonjour daemon: cups-browsed^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:32 2017: [....] Starting system message bus: dbus^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:32 2017: [....] Starting bluetooth: bluetoothd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:32 2017: [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:32 2017: [....] Starting Light Display Manager: lightdm^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:32 2017: [....] Starting NTP server: ntpd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:33 2017: [....] Starting network connection manager: NetworkManager^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:33 2017: [....] Loading cpufreq kernel modules...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone (acpi-cpufreq).
Sat Nov 11 08:52:37 2017: [....] CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 08:52:37 2017: [....] Starting NetBIOS name server: nmbd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:37 2017: [....] Starting virtual private network daemon:^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:37 2017: [....] saned disabled; edit /etc/default/saned^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 08:52:37 2017: SpamAssassin Mail Filter Daemon: disabled, see /etc/default/spamassassin
Sat Nov 11 08:52:38 2017: [....] Starting SMB/CIFS daemon: smbd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:31 2017: [....] Setting parameters of disc: (none)^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:31 2017: [....] Setting preliminary keymap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:35 2017: [....] Activating swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:35 2017: [....] Checking root file system...fsck from util-linux 2.25.2
Sat Nov 11 18:19:35 2017: rootMX16: clean, 230287/1708784 files, 1953572/6833152 blocks
Sat Nov 11 18:19:35 2017: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:36 2017: [....] Cleaning up temporary files... /tmp^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:36 2017: [....] Starting early crypto disks...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [^[[36minfo^[[39;49m] Loading kernel module lp.
Sat Nov 11 18:19:37 2017: [^[[36minfo^[[39;49m] Loading kernel module ppdev.
Sat Nov 11 18:19:37 2017: [^[[36minfo^[[39;49m] Loading kernel module parport_pc.
Sat Nov 11 18:19:37 2017: [^[[36minfo^[[39;49m] Loading kernel module loop.
Sat Nov 11 18:19:37 2017: [^[[36minfo^[[39;49m] Loading kernel module ecryptfs.
Sat Nov 11 18:19:37 2017: [^[[36minfo^[[39;49m] Loading kernel module fuse.
Sat Nov 11 18:19:37 2017: [....] Setting up LVM Volume Groups...  No volume groups found
Sat Nov 11 18:19:37 2017: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Starting remaining crypto disks...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Activating lvm and md swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Checking file systems...fsck from util-linux 2.25.2
Sat Nov 11 18:19:37 2017: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Mounting local filesystems...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Activating swapfile swap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Cleaning up temporary files...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:37 2017: [....] Skip starting firewall: ufw (not enabled)...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: [....] Setting kernel variables ...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:37 2017: Running 0dns-down to make sure resolv.conf is ok...done.
Sat Nov 11 18:19:38 2017: [....] Configuring network interfaces...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:38 2017: [....] Starting rpcbind daemon...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:39 2017: [....] Starting NFS common utilities: statd idmapd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:39 2017: [....] Cleaning up temporary files...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:39 2017: [....] Setting up ALSA...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:39 2017: [^[[36minfo^[[39;49m] Setting console screen modes.
Sat Nov 11 18:19:39 2017: ^[[9;30]^[[14;30][....] Setting up console font and keymap...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:39 2017: [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:39 2017: [....] Setting sensors limits^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:39 2017: INIT: Entering runlevel: 5
Sat Nov 11 18:19:39 2017: [^[[36minfo^[[39;49m] Using makefile-style concurrent boot in runlevel 5.
Sat Nov 11 18:19:39 2017: [....] Starting acpi_fakekey daemon...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:39 2017: [....] Not starting NFS kernel daemon: no exports. ...^[[?25l^[[?1c^[7^[[1G[^[[33mwarn^[[39;49m^[8^[[?25h^[[?0c ^[[33m(warning).^[[39;49m
Sat Nov 11 18:19:39 2017: Setting battery charge thresholds...done.
Sat Nov 11 18:19:40 2017: [....] Starting enhanced syslogd: rsyslogd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:40 2017: [....] Starting cgroup management daemon: cgmanager[....] Starting ACPI services...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:41 2017: [....] Starting anac(h)ronistic cron: anacron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:42 2017: [....] Starting deferred execution scheduler: atd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:42 2017: [....] Starting cgroup management proxy daemon: cgproxy^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:43 2017: [....] Starting periodic command scheduler: cron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:43 2017: [....] Starting Common Unix Printing System: cupsd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:43 2017: [....] Starting CUPS Bonjour daemon: cups-browsed^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:44 2017: [....] Starting system message bus: dbus^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:44 2017: [....] Starting bluetooth: bluetoothd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:45 2017: [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:45 2017: [....] Starting NetBIOS name server: nmbd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:45 2017: [....] Starting Light Display Manager: lightdm^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:46 2017: [....] Starting network connection manager: NetworkManager^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:46 2017: [....] Loading cpufreq kernel modules...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone (acpi-cpufreq).
Sat Nov 11 18:19:46 2017: [....] Starting NTP server: ntpd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:46 2017: [....] CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Sat Nov 11 18:19:46 2017: [....] Starting virtual private network daemon:^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:46 2017: [....] saned disabled; edit /etc/default/saned^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Sat Nov 11 18:19:47 2017: SpamAssassin Mail Filter Daemon: disabled, see /etc/default/spamassassin
Sat Nov 11 18:19:47 2017: [....] Starting SMB/CIFS daemon: smbd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.

Posted: **Sat Nov 11, 2017 12:30 pm**

I do not see anything untoward in there, but thinking about it that logs after the grub screen,

Posted: **Sat Nov 11, 2017 1:20 pm**

berlin59 wrote:
dolphin_oracle wrote:If you are booting uefi, them the former grub installs and windows bootloader should still be present in the esp partition. You can use your uefi setup (bios) to choose which one to boot. Oldmlinux grubs will only work if the former linux installs are still present but the windows ones should work.

It is also sometimes beneficial to remove bootloader you arent using.
Sorry, it must be because I am not english, but I don't grasp what you are trying to tell me.

During installation of MX-17 and later MX-16.1 on this uefi-laptop, the installer asked me where I want the grub to be installed. It had 3 options. MBR , Root and esp.
Since I installed about 100 different distros on this laptop in order to test them, I know that grub must go into esp, therefore I chose that.
The installation ended successfully.

In the boot-menu which appears after start, I can chose which OS I want to boot.
There is Win10, LinuxMint 17.3, LinuxMint 18.2, Peppermint-8, MX-16.1 and MX-17beta-1 .

Each does start correctly when I chose it.

The problem is that it takes about 45 seconds until the boot-menu appears.
The installer of MX-17beta-1 ruined something in my laptop.
Because before I installed it, the boot-menu appeared after 2 seconds since I press the power-button.
The first 2 seconds, the logo screen from Toshiba appeared, then immediately the boot-menu.
Now it is not immediately, but takes 45 seconds.
That is my problem.

I hope that I expressed it in an understandable way because in the past I ran into problems because of the words I used.
boot-menu, grub-menu or something and that caused misunderstandings.
Somewhere in a tutorial of Toshiba they used the name "GNU GRUB menu", maybe that is the correct word, I don't know.

I made a screenshot from the Toshiba tutorial which shows the grub-boot-menu which in my case appears much too late.

With uefi, grub gets installed to the esp, as you've noted. However, unlike with legacy boots, the old grubs are NOT overwritten, just the latest grub is given boot priority. All the little grub efi files aRe still present on the esp partiton unused but taking up space. The boot priority is stored in what's call nvram or non-volatile ram.

The esp partition is typically between 100 amd 250 mbs. If you've been distro hopping and installing many many distros, as you seem to indicate, it is very possibe that the partition is full or that the nvram is full, which can cause very bizarre boot issues before grub even launches. (I had a kernel crash flood my nvram with jibberrish so I know).

I don't know if either is your problem, but it is worth a try to use your uefi-bios-setup to remove the old unsed bootloader entries that you aren't using.

Posted: **Sat Nov 11, 2017 1:41 pm**

it is worth a try to use your uefi-bios-setup to remove the old unsed bootloader entries that you aren't using.

Thank you very much for the help.

The question for me is: how to do it ?
A link to a tutorial would be enough and I will try everything I can.

In the meanwhile I had the idea to install Peppermint-8 on the partition where I have LinuxMint 17.3 installed.
Why ?
Because usually when doing a new install of an OS, later at start of the laptop, this new installed OS is on top of all others in the grub-boot-menu and therefore is the default OS which will boot after 5 seconds (MX distros), others have 10 seconds.

But strange enough, the new installed Peppermint-8 , although the installation went through without any errors, is not on top of the grub-menu. And even more strange, P-8 was for some reason not able to install it's own grub-menu, but still the MX-16.1 grub menu is there and still MX-16.1 is on top and starts after 5 seconds if I do not select another OS.

Something is wrong, because such a behavior I had only when I installed Solus-3 distro. It grabbed the whole startup process and did not allow anything else to select than itself and Win10.
It was a long fight to get rid of Solus-3.

Another special distro is Deepin from China. A nice distro, but it grabs the boot-procedure in a similar way and keeps its own grub-menu although I installed several other distros to get it straightened out.

I cannot tell you how often I had to use the boot-repair-disk on this uefi-laptop.

Maybe it is about a big difference in Ubuntu-based distros and Debian based ones ?
I think so because problems with booting and grub-menu happened only with Debian-distros like Sparky, Deepin and now MX. (Solus-3 is different because it is coded on its own as far as I understand)

All the Ubuntu-based distros managed the uefi-architecture without problems. When I installed a new distro, it got its own grub-menu to be the one which appears and it is the default OS.

Just to inform you about my experiences.
Anyway, maybe the bug this time is caused by what you say. Some overflow of space in the esp.
I am curious now to find the fault.

Otherwise I am afraid I have to zero the harddrive and begin from scratch. A long journey.

Just in case it might help, I used efibootmgr.
It shows that even after the installation of P-8, somehow MX did not allow P-8 to change the boot sequence.
It occupies the first 2 places and keeps Ubuntu on the 3rd place.
I know that all Ubuntu-based distros write their info into that Ubuntu-efi-entry.

Code: Select all

sudo efibootmgr -v
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0007,0006,0001,0004,0000,0005,2003,2001,2002
Boot0000* Windows Boot Manager	HD(1,800,100000,577f146a-067a-4454-8c62-4cd08e9d7677)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0001* ubuntu	HD(1,800,100000,577f146a-067a-4454-8c62-4cd08e9d7677)File(\EFI\ubuntu\shimx64.efi)
Boot0002* EFI Network 0 for IPv6 (70-54-D2-47-E1-F0) 	ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(7054d247e1f0,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000RC
Boot0003* EFI Network 0 for IPv4 (70-54-D2-47-E1-F0) 	ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(7054d247e1f0,0)RC
Boot0004  Windows Boot Manager	HD(1,800,100000,577f146a-067a-4454-8c62-4cd08e9d7677)File(\EFI\ubuntu\shimx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0005* Ubuntu	HD(1,800,100000,577f146a-067a-4454-8c62-4cd08e9d7677)File(\EFI\ubuntu\grubx64.efi)RC
Boot0006* MX17	HD(1,800,100000,577f146a-067a-4454-8c62-4cd08e9d7677)File(\EFI\MX17\grubx64.efi)
Boot0007* MX16	HD(1,800,100000,577f146a-067a-4454-8c62-4cd08e9d7677)File(\EFI\MX16\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

With the efibootmgr I changed the boot-sequence.
Made the Ubuntu boot-entry the default one.
Then sudo update-grub and restart.
Now the laptop shows the Peppermint-8 grub-menu as desired.

But still it takes more than 40 seconds until the grub-menu appears on the screen.

Posted: **Sat Nov 11, 2017 2:42 pm**

Do the usual solutions not work when uefi is involved? 1) boot to a Linux distro and run update-grub as root; 2) boot to the live USB and use Boot Repair.

Posted: **Sat Nov 11, 2017 2:53 pm**

Jerry3904 wrote:Do the usual solutions not work when uefi is involved? 1) boot to a Linux distro and run update-grub as root; 2) boot to the live USB and use Boot Repair.

The boot sequence is now fixed.

With boot-repair there is nothing to fix anymore except maybe removing all installed linux distros.
But I am afraid that will not help me much.
I predict that after a new installation of MX or an ubuntu-based distro, my problem will not be solved.
Because the problem is the gap of 45 seconds from seeing the Toshiba screen to the grub-menu.

I intend to use tomorrow to clean the harddrive and format it as gpt with the needed esp, then installing win10 and then a linux distro. Spent already too many hours today on this, I am tired.

Posted: **Sat Nov 11, 2017 4:28 pm**

berlin59 wrote:
Jerry3904 wrote:Do the usual solutions not work when uefi is involved? 1) boot to a Linux distro and run update-grub as root; 2) boot to the live USB and use Boot Repair.
The boot sequence is now fixed.

With boot-repair there is nothing to fix anymore except maybe removing all installed linux distros.
But I am afraid that will not help me much.
I predict that after a new installation of MX or an ubuntu-based distro, my problem will not be solved.
Because the problem is the gap of 45 seconds from seeing the Toshiba screen to the grub-menu.

I intend to use tomorrow to clean the harddrive and format it as gpt with the needed esp, then installing win10 and then a linux distro. Spent already too many hours today on this, I am tired.

Its not likely your entire harddrive. the esp is a actual fat formatted partition, usually hidden but it is there. you really owe it to your self to see if its full, or if you can remove the old entries from inside the bios setup program of your pc. this will be different for each pc, but likely accessed by hitting either some key while the "Toshiba" is visible before the grub boot menu, or if you run "update-grub" after an mx install, there might be a "setup" entry in your grub menu.

if the nvram is full, formatting and reinstalling WILL NOT FIX IT. if its just the esp, reformating the entire drive is still overkill. Use your PC's bios-setup utility first to try to remove old grub bootloaders efi files before taking those drastic steps.

Posted: **Sat Nov 11, 2017 5:37 pm**

dolphin_oracle,
I agree. It would be overkill.
I installed the gnome-disk-utility and there I can see the efi partition.
537 MB — 416 MB frei (22,4% belegt)
So the esp is not full.

About removing old grub bootloaders I will try to do that now.
Since I am familiar with the Bios-setup screen on my laptop, I rather think there is no way to change something from there.
I will try to google "nvram full" or something similar and give feedback about it.

Posted: **Sat Nov 11, 2017 5:48 pm**

berlin59 wrote:dolphin_oracle,
I agree. It would be overkill.
I installed the gnome-disk-utility and there I can see the efi partition.
537 MB — 416 MB frei (22,4% belegt)
So the esp is not full.

About removing old grub bootloaders I will try to do that now.
Since I am familiar with the Bios-setup screen on my laptop, I rather think there is no way to change something from there.
I will try to google "nvram full" or something similar and give feedback about it.

on my laptop, the feature is something in the "boot order" area, and I just hit the "delete" key to remove both the entry from the list, which also removes it from nvram and the esp for that matter.

If this isn't the problem, then you aren't out anything. If this fixes your issue, then you've saved yourself a lot of headache.

Posted: **Sat Nov 11, 2017 6:19 pm**

dolphin_oracle wrote:
berlin59 wrote:dolphin_oracle,
I agree. It would be overkill.
I installed the gnome-disk-utility and there I can see the efi partition.
537 MB — 416 MB frei (22,4% belegt)
So the esp is not full.

About removing old grub bootloaders I will try to do that now.
Since I am familiar with the Bios-setup screen on my laptop, I rather think there is no way to change something from there.
I will try to google "nvram full" or something similar and give feedback about it.
on my laptop, the feature is something in the "boot order" area, and I just hit the "delete" key to remove both the entry from the list, which also removes it from nvram and the esp for that matter.

If this isn't the problem, then you aren't out anything. If this fixes your issue, then you've saved yourself a lot of headache.

The other way yo remove them is with efibootmanager. In a root terminal. The delete key in the bios screen did not work for me.

Code: Select all

efibootmgr

It will list all the bootable systems. The first column is the boot number
Then

Code: Select all

efibootmgr -b x -B

Where x is the number of the entry you want to delete. Be careful and make sure you are deleting the right one.

Posted: **Sat Nov 11, 2017 6:47 pm**

richb,
I already used efibootmgr to delete some of the entries. It worked fine, I hit the correct ones.

I am experimenting with the boot-repair-disk right now. If that doesn't solve my problem, I will go the hard way and format the whole harddisk and install everything from scratch.
If that doesn't help, I am done and will let go.

Posted: **Sat Nov 11, 2017 7:25 pm**

With boot-repair-disk I first tried to remove all Kernels and reinstall the latest Kernel for the Peppermint-8 OS on sda6.
It never finished, so I closed the program and used the OS-remover for Peppermint-8 on sda4.
That installed the grub new into the esp I hope.

After restart, the gap of 45 seconds was gone.
The Toshiba screen appeared and after 2 seconds, within a split-second the grub-menu appeared.
It says GNU GRUB Version 2.02 beta2-36ubuntu3.9
The menu was a big surprise because there are old and rotten entries from Solus-3. The entry for Peppermint is missing

What else is there ?
- Windows UEFI bootmgfw.efi
- Windows Boot UEFI loader
- EFI/goofiboot/goofibootx64.efi
- EFI/ubuntu/fbx64.efi
- EFI/ubuntu/fwupx64.efi
- EFI/ubuntu/mmx64.efi
- EFI/ubuntu/MokManager.efi
- Windows Boot Manager (on /dev/sda1)
- MX-16.1 Metamorphosis (16.1) (on /dev/sda8)
Advanced options for ...
and MX 17 Horizon ... with advanced options

I thought I had cleaned the goofiboot entry long time ago, it is from Solus-3, but now it shows up again ?

And all the ubuntu-entries ?

Do you have an idea how to clean this mess up ?

Posted: **Sat Nov 11, 2017 7:56 pm**

I cannot vouch for this but it sounds like this is what happened to you.

Now you should also delete the ubuntu subdirectory in the EFI partition to prevent the UEFI firmware from restoring the entry into the BootOrder.

Procedure is in the second post.

https://askubuntu.com/questions/63610/h ... -menu-uefi

Posted: **Sat Nov 11, 2017 8:36 pm**

Thank you very much to all who helped me.

I don't know how and why I got to the solution, but it is there.
richb, your comment came too late, sorry.

I googled and found somebody who said I should edit the files in /etc/grubd .
I found the file "25_custom" there where I deleted the entries which did not work in the grub-menu. entries like goofibootx64.efi
or fbx64.efi etc.

Then after sudo update-grub and restart, they were gone in the grub-menu.

If you ask me why they weren't there not before I asked for help ( they were not present in the MX-16 nor in the MX-17 grub-menu ), I think I know the answer.
These old entries were on the partition where LinuxMint 18.2 is installed, they sat there in that grubd-folder inside the 25_custom file all the time. But this OS was not the default OS from which the grub-menu was displayed, therefore it only showed up after I experimented with boot-repair-disk, not knowing exactly what it did.

Obviously not the way others than me should experiment on their machines.

But the laptop is not my production machine, for that I have the PC which has the old fashioned MBR and not Uefi.
No distro ever caused problems on that PC, they all manage the grub perfectly.

Thanks again for your kind help.
I appreciate it very much.

For me this problem is solved now.

Posted: **Sun Nov 12, 2017 11:54 am**

richb wrote:
ferlop wrote:I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.
Not sure how much it consumes on your system ,on mine very little, 4 core AMD, but you can try turning off the conky and see what results. MX Conky and click stop.

Hello.

My computer is a very old one: desktop Dell Optiplex 5200 with a 3,4 GHZ Dual Core Processor, 4 GB Ram.

The MX16.1 live session and the HDD installation: flows between 230-240 MB of ram after starting.

The MX-17 testing (alphas and beta 1): more than 600 MB of ram. Even when conky is disabled it never reaches that low value of ram consumption as the 16.1 does.

MX-17 is not so fast and smooth oppening applications as MX-16.1.

I've got a laptop Lenovo T61 (very old one as well): I am going to do the same job to verify the performance.

Thanks for your answer

Posted: **Sun Nov 12, 2017 12:07 pm**

ferlop wrote:
richb wrote:
ferlop wrote:I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.
Not sure how much it consumes on your system ,on mine very little, 4 core AMD, but you can try turning off the conky and see what results. MX Conky and click stop.

Hello.

My computer is a very old one: desktop Dell Optiplex 5200 with a 3,4 GHZ Dual Core Processor, 4 GB Ram.

The MX16.1 live session and the HDD installation: flows between 230-240 MB of ram after starting.

The MX-17 testing (alphas and beta 1): more than 600 MB of ram. Even when conky is disabled it never reaches that low value of ram consumption as the 16.1 does.

MX-17 is not so fast and smooth oppening applications as MX-16.1.

I've got a laptop Lenovo T61 (very old one as well): I am going to do the same job to verify the performance.

Thanks for your answer

The devs have been looking at this. More to follow.

Posted: **Sun Nov 12, 2017 12:36 pm**

There has been some discussion here and elsewhere about the default image viewer. This is important to me as it's something I use a lot. I don't like gThumb at all, for numerous reasons, and I don't like Mirage (MX-16 default) because it has no print facility. The best I had come up with was the Gnome Image Viewer (EOG), but that has no resizing option.

I've spent some time this weekend testing a number of image viewers, and unless I've missed something obvious, I've found one that I think does pretty much everything.

It's 'Nomacs', and it's in the Testing repo.

It has printing capability, does cropping, resizing, and a reasonably comprehensive amount of image manipulation. It will also open PSD files (native Photoshop), something few other viewers do. It has been stable during my limited testing. In spite of how comprehensive it is, speed is very good. It is much faster at opening an image on an ancient Pentium M laptop than gThumb.

It would be great if others could test this, and offer their opinions.

Chris

Posted: **Sun Nov 12, 2017 1:03 pm**

Could not find Nomacs in the test repo, but found it in the default repo.

Just too a quick look. I particularly like the scroll wheel zoom feature. It looks like more of an image manipulation program rather than an image viewer. I do not find that a negative.

Posted: **Sun Nov 12, 2017 1:29 pm**

does anyone notice this or not;
open any apps and close it, does not stay at it's last closed location.
turn off conky, apps will then opens at it's last closed location.

Posted: **Sun Nov 12, 2017 2:13 pm**

richb wrote:I cannot vouch for this but it sounds like this is what happened to you.

Now you should also delete the ubuntu subdirectory in the EFI partition to prevent the UEFI firmware from restoring the entry into the BootOrder.
Procedure is in the second post.

https://askubuntu.com/questions/63610/h ... -menu-uefi

richb,
sorry for giving another feedback after telling everybody that the old uefi-entries are gone.
They are not gone, it only seemed to be so.

After using boot-repair-disk (of course from an usb-live-stick) to remove an OS from my Toshiba uefi-laptop, the new grub-menu showed all the old entries again.

So I followed exactly the procedure you suggested.
I definitely was able to delete the old entries in the efi-partition.

Later on I used boot-repair-disk again and after that the new grub-menu has them all back.
I wonder where these old entries are stored.
Somewhere the update-grub after a new grub-install into the esp must grab them.

Edit: I think I got it now.
Not with a live-usb linux, but from within LinuxMint. Although efi-partition is mounted, with sudo I was able to make a directory and mount sda1 there, sda1 = my esp.
Then I removed everything which looked nasty to me. In strange folders I found the solus3-files again and other files which I removed.
After the final sudo update-grub and restart, the grub-menu now is clean. All the old entries are gone.
Mission accomplished.

Posted: **Mon Nov 13, 2017 7:00 am**

This post in the Italian forum raises a question (G trans):

For pure curiosity I tested live version 17 beta. I would like to point out this anomaly: in the launch of the MX-16 live, the presence of wifi networks was immediately reported, so that time before, I could install the distro with the wifi connection only. It should be kept in mind that I have the b43 card, which has always caused problems with various distro. When launching the live MX-17 beta, however, wifi is not detected, although b43-fwcutter has already been installed. I should have connected to the ethernet network for installation. Of course I let it go because I did not care to waste time. I bring anomaly to developers' attention for any controls.

I will test on my only laptop later todeay that has b43 (and b44).

EDIT: works fine on my Dell 700m