MX-17 Beta 1 Feedback Thread

Message
Author
User avatar
m_pav
Developer
Posts: 1390
Joined: Sun Aug 06, 2006 3:02 pm

Re: MX-17 Beta 1 Feedback Thread

#271 Post by m_pav »

Looks like a tumbler type daemon is hogging resources again. I had an issue un-mounting a USB device with a large 1.8GB car audio firmware file after copying its contents to my SSD. Copy process happened at 95MBPS, so it was over in moments, but after leaving it for 6-7 minutes while taking a phone call, when I tried to umount the device from Thunar which was only reading from the device, not writing to it, the following displayed.

I found the old tumbler script, copied it to /usr/local/bin, set permissions to root and marked it executable, added it to startup, rebooted and no more issues.
Screenshot.png
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD FX 6100 CPU, nVidia, 8Gb, 3.25TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs

User avatar
stsoh
Posts: 183
Joined: Sun Aug 20, 2017 10:11 am

Re: MX-17 Beta 1 Feedback Thread

#272 Post by stsoh »

any kind soul, pls explain how/instruction to using delta3 to upgrade 17b1 to 17b2. thanks from a newbie.
MX-17.1_x64 Horizon, G41M-P33 Combo (MS-7592), Pentium E5400 (2706 MHz), 8Gb RAM (984 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.
Accepted Linux when i found MX-Linux in 2016.

User avatar
richb
Administrator
Posts: 10322
Joined: Wed Jul 12, 2006 2:17 pm

Re: MX-17 Beta 1 Feedback Thread

#273 Post by richb »

stsoh wrote:any kind soul, pls explain how/instruction to using delta3 to upgrade 17b1 to 17b2. thanks from a newbie.
From the wiki https://mxlinux.org/wiki/system/xdelta

Code: Select all

xdelta3 -d -s fromfile patchname.delta tofile
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
stsoh
Posts: 183
Joined: Sun Aug 20, 2017 10:11 am

Re: MX-17 Beta 1 Feedback Thread

#274 Post by stsoh »

does it upgrade 17b1 on my hd to 17b2?
i'm try to use the MX-17_b1_to_b2_x64_mark_2.delta file to upgrade.
MX-17.1_x64 Horizon, G41M-P33 Combo (MS-7592), Pentium E5400 (2706 MHz), 8Gb RAM (984 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.
Accepted Linux when i found MX-Linux in 2016.

User avatar
Jerry3904
Administrator
Posts: 21881
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-17 Beta 1 Feedback Thread

#275 Post by Jerry3904 »

No, it upgrades the B1 ISO to the B2 ISO. With so many changes from Beta 1 to Beta 2, including a new kernel, there is no easy upgrade path.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
richb
Administrator
Posts: 10322
Joined: Wed Jul 12, 2006 2:17 pm

Re: MX-17 Beta 1 Feedback Thread

#276 Post by richb »

I am not recommending this, but it worked for me. I used xdelta to create the b2 ISO from the b1 ISO. I then installed to SSD with b1 installed saving home. All my config files hence were available in b2. Any apps you added will have to be reinstalled, but will pick up their config files already on disk. For example I had compiz installed on bi and configured. Of course it was not installed on b2, Installing compiz picked up its config file and operated as it was in b1.
I have used this procedure starting at a5 going to b2. I give no guarantee and some anomaly may exist that I have not found. So user beware. The safest way is to install from scratch. That is the recommend procedure.

EDIT: This procedure may also invalidate any b2 testing. So as a tester one should verify results in a fresh install, say in a virtual machine before posting any issues.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
stsoh
Posts: 183
Joined: Sun Aug 20, 2017 10:11 am

Re: MX-17 Beta 1 Feedback Thread

#277 Post by stsoh »

thanks for all the feedback.
MX-17.1_x64 Horizon, G41M-P33 Combo (MS-7592), Pentium E5400 (2706 MHz), 8Gb RAM (984 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.
Accepted Linux when i found MX-Linux in 2016.

User avatar
richb
Administrator
Posts: 10322
Joined: Wed Jul 12, 2006 2:17 pm

Re: MX-17 Beta 1 Feedback Thread

#278 Post by richb »

This thread is being closed since Beta 2 has been released.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
Jerry3904
Administrator
Posts: 21881
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-17 Beta 1 Feedback Thread

#279 Post by Jerry3904 »

And thanks to everybody who contributed!
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
JackC
Posts: 1
Joined: Fri Feb 16, 2018 11:40 am

Re: MX-17 Beta 1 Feedback Thread - 2 screens?

#280 Post by JackC »

My first effort on the forum; apologies in advance for beginners' blunders.

Paste of the machine in question :
System: Host: mx1 Kernel: 4.7.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.2
Distro: MX-16_x64 Metamorphosis 12 December 2016
Machine: Device: laptop System: Hewlett-Packard product: HP Pavilion dm4 Notebook PC v: 048E100000242B10000020000 serial: N/A
Mobo: Hewlett-Packard model: 146A v: 58.28 serial: N/A
BIOS: Hewlett-Packard v: F.26 date: 02/14/2011
Battery BAT0: charge: 45.4 Wh 100.0% condition: 45.4/45.4 Wh (100%)
CPU: Dual core Intel Core i5 M 430 (-MT-MCP-) cache: 3072 KB
clock speeds: max: 2267 MHz 1: 1333 MHz 2: 1466 MHz 3: 2267 MHz 4: 1466 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
Resolution: 1024x768@60.00hz, 1440x900@60.02hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile version: 2.1 Mesa 12.0.3
Audio: Card Intel 5 Series/3400 Series High Def. Audio driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.7.0-0.bpo.1-amd64
Network: Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: d8:d3:85:36:1d:ae
Card-2: Broadcom BCM4313 802.11bgn Wireless Network Adapter driver: wl
IF: wlan0 state: down mac: 00:26:82:8d:e2:d6
Drives: HDD Total Size: 320.1GB (1.9% used)
ID-1: /dev/sda model: Hitachi_HTS72503 size: 320.1GB
Partition: ID-1: / size: 20G used: 5.6G (31%) fs: ext4 dev: /dev/sda8
Sensors: System Temperatures: cpu: 41.0C mobo: 39.0C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 193 Uptime: 1:10 Memory: 650.1/2809.3MB Client: Shell (bash) inxi: 2.3.54

End of paste of the machine in question.

The problem:
When I try to boot into MX-17 64-bit (from a USB key, which has worked fine on other machines), I get a result pretty much identical to Mauser, with the XFCE wallpaper with the mouse (animal!) on it. Printscreen shows me a wide image which has the good MX-17 screen on the left, and attached on its right the XFCE wallpaper - I can't attach the screenimage here, because I have no way of saving it. My machine is a portable from which the original (broken) screen has been removed, and I use it with a screen attached to the VGA plug. Can it be that MX-17 is seeing a phantom screen where the original broken screen was, like people who feel pain 'in' an amputated limb??
The machine works fine with MX-16 (currently installed). It also works fine with Antix-17. Also, on a whim, I just tried MX-17 32-bit; same result as with the 64-bit version, but when I tried with 'Failsafe', 'Safe video' or 'nomodeset' from the boot menu, it worked OK. (The same experiments with the 64-bit version did not work.)

The question:
Generally, what's going on? And, specifically, can I safely install, say, the 32-bit version with 'nomodeset', or is this risky?

Thanks in advance for any info.

Locked

Return to “General”