MX-17 Beta 2 Feedback

Locked
Message
Author
caprea
Posts: 146
Joined: Sat Aug 23, 2014 7:01 am

Re: MX-17 Beta 2 Feedback

#61 Post by caprea »

Can confirm the 375.82-8~bpo9+1 nvidia builds perfectly against the 4.13.0-0.bpo.1-amd64 -kernel.

What didn't work at all is the grub-customizer. Did anyone else try?
It mixed all up and many lines were double in the bootscreen.
I had to reboot into antix and did an "sudo grub-install /dev/sda" to resolve.

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

Re: MX-17 Beta 2 Feedback

#62 Post by Jerry3904 »

I tried it, renaming the name of the default, rebooted, all good. Are you sure you waited until it was saved (takes a while)?
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

caprea
Posts: 146
Joined: Sat Aug 23, 2014 7:01 am

Re: MX-17 Beta 2 Feedback

#63 Post by caprea »

I didn't try to rename the default, I used the up-arrow,which worked in MX 16
O.K.,there are three systems with some different kernels, so I have many lines.
Sure waited until it was saved.

User avatar
tascoast
Posts: 441
Joined: Sat Aug 06, 2011 4:58 am

Re: MX-17 Beta 2 Feedback

#64 Post by tascoast »

I've just installed MX-17 b2, Grub to MBR, and then customised Grub without issues being noted above.
(Wifi dongle was detected quickly during live boot, although was quite slow to activate upon booting from HDD. b1 seemed to require some re-plugging in, by comparison)
Inspiron 15 5000-5593- (i7-1065G7) MX 23..2 AHS/MX-21//W10 - Lenovo ThinkCentre A58 4GBRAM (64-bit), MX-23.2/MX21.3./antiX 23/Mint 21.3, Ubuntu 22.04.4, openSUSE Tumbleweed,

User avatar
Stevo
Developer
Posts: 12841
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-17 Beta 2 Feedback

#65 Post by Stevo »

The backported 304xx and 340xx Nvidia legacy drivers are now in the main MX 17 repo for testing with the 4.13 kernels. They are also in the testing repo for MX 15, since we don't have kernels in main that needs those ones.

User avatar
Stevo
Developer
Posts: 12841
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-17 Beta 2 Feedback

#66 Post by Stevo »

dr-kart wrote:
Stevo wrote:...main 375.82 Nvidia driver has no problem with the 4.13 kernel

Yes. Got no problem with it on 4.13 kernel.
Since backported nvidia driver appears to me bit newer I choose the one with 375.82-8~bpo9+1 name. Not from main repo. And what's the difference between those main's and bpo's versions?

Code: Select all

Graphics:  Card: NVIDIA GK106 [GeForce GTX 650 Ti] bus-ID: 01:00.0 chip-ID: 10de:11c6
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GTX 650 Ti/PCIe/SSE2
           version: 4.5.0 NVIDIA 375.82 Direct Render: Yes
You can look at the package's changelogs at packages.debian.org to see what the differences are. They share the same original source version, so any changes will be Debian patches or packaging changes. Looks like most of it is stuff that won't affect us with Mesa 13, concerning many troubles with the Vulkan variant packages for Mesa 17 upstream--they messed up with a -4 in stretch-backports and had to fix it with yet another version.

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

Re: MX-17 Beta 2 Feedback

#67 Post by Jerry3904 »

Tried it on my Dell 700m, on which everything through the MX-16x series worked.

1) had to try the cheat "forcepae" to even start
2) once it entered runlevel 5, screen went completely black; waited a few minutes, then pressed the power button once, and it finished booting to the desktop.
3) wifi enabled and light on, but "device is not ready"
4) installed without problem
6) hung on exiting, had to power down manually << this usually happens
7) on rebooting without USB, saw that forcepae had been retained as a cheat -- very nice!
8) hung again part way through runlevel 5, pushing power button, Ctrl-C or Ctrl-Alt-F1 did not help.
9) finally used the power button to end
Too bad, this is the first MX Linux release I could not use on this machine. (BTW: same thing with B1)
Here is an inxi report from an earlier time:

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 3.16.0-4-586 i686 (32 bit) Desktop: Xfce 4.12.2
           Distro: MX-15-a3_386-mx Fusion 10 October 2015
Machine:   System: Dell product: Inspiron 700m v: -1
           Mobo: DELL SYSTEM model: Inspiron 700m v: Rev.A
           Bios: Phoenix v: A02 date: 02/01/05
CPU:       Single core Intel Pentium M (-UP-) cache: 2048 KB
           speed: 1600 MHz (max)
Graphics:  Card: Intel 82852/855GM Integrated Graphics Device
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1280x800@65.28hz
           GLX Renderer: Mesa DRI Intel 852GM/855GM x86/MMX/SSE2
           GLX Version: 1.3 Mesa 10.3.2
Audio:     Card Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
           driver: snd_intel8x0
           Sound: Advanced Linux Sound Architecture v: k3.16.0-4-586
Network:   Card-1: Broadcom BCM4306 802.11b/g Wireless LAN Controller
           driver: b43-pci-bridge
           IF: wlan0 state: up mac: 00:0b:7d:18:92:4b
           Card-2: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth0 state: down mac: 00:0f:1f:b1:d6:13
Drives:    HDD Total Size: 48.0GB (4.7% used)
           ID-1: /dev/sda model: HTS548040M9AT00 size: 40.0GB
           ID-2: USB /dev/sdb model: Cruzer_Glide size: 8.0GB
Partition: ID-1: swap-1 size: 1.21GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 58.0C mobo: 43.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 121 Uptime: 10 min Memory: 229.7/1245.3MB
           Client: Shell (bash) inxi: 2.2.25
 
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
ldsemerchen
Posts: 34
Joined: Thu Nov 09, 2017 10:17 am

Re: MX-17 Beta 2 Feedback

#68 Post by ldsemerchen »

Beta2 MX Select Sound: When I choose another sound divice, it always sound from PC's speaker when I applied it and "Test current sound card". Beta1 is OK.

Image

Audio: Card-1 Intel 7 Series/C216 Family High Def. Audio Controller driver: snd_hda_intel
Card-2 C-Media Audio Adapter (Planet UP-100 Genius G-Talk) driver: USB Audio
Card-3 Microsoft LifeCam VX-3000 driver: USB Audio
Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp

User avatar
dolphin_oracle
Developer
Posts: 20024
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX-17 Beta 2 Feedback

#69 Post by dolphin_oracle »

Just so folks are aware, at some point a lightdm upgrade is going to come down. during the upgrade, you may be asked what to do with a script in /etc/init.d/ (/etc/init.d/lightdm) . Please accept the change and let us know any ill effects.

this update should allow the run level 3 (boot code 3) to work to get to a console without starting X.

thanks, and remember...beta beta beta!

**edit***

This should work be default on the next iso build, but testers on the current b2 build will need to run

Code: Select all

sudo update-rc.d lightdm remove
sudo update-rc.d lightdm defaults
to be able to use the "3" boot code.

<MOD: corrected the typo (-rcd.) in the second command>
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

danielson

Re: MX-17 Beta 2 Feedback

#70 Post by danielson »

stsoh wrote:17b2 is awesome........ :number1:
Isn't it funny how words get twisted around over time?
Awe-some = Some awe ;
Awful = Full of awe.

Having jumped around for a long time from distro to distro, and most recently, to be greatly impressed with the outcome of Solus 3 and then Ubuntu Budgie (which i find fuller) but now... this MX-17 b2!
The latter has really put me in crisis!
Here's one more hand to lift that cup higher to cheer the devs on! :)

Locked

Return to “General”