MX-19 RC1 Feedback thread

Message
Author
User avatar
BitJam
Developer
Posts: 2303
Joined: Sat Aug 22, 2009 11:36 pm

Re: MX-19 RC1 Feedback thread

#261 Post by BitJam »

komer wrote: Mon Oct 21, 2019 11:41 pm when you implement the fix, I will test it. I gotta sleep now. It's 5:30am here. I'm way off my curfew. Have a good night BjtJam :-)
Wow. This Debian sysvinit code hurts my brain.

I've attached a small tarball called xtra.tgz. If you *copy* this tarball to the /antiX/ directory it will add my fix on every live boot. Don't unpack the tarball just copy it.

The plan is simple. If the file /etc/default/keyboard differs from the default version we ship on the iso file then we will call "setupcon -k". When it does this, it will say "Setting up live keyboard layout" on tty1. Sometimes messages fill the screen and scroll off the top. The cheat "tty1off" will disable login on tty1 which saves some lines.

You can also run the script manually after you've booted:

Code: Select all

sudo service setup-keyboard.sh start
You do not have the required permissions to view the files attached to this post.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."

-- Richard Feynman

cigam

Re: MX-19 RC1 Feedback thread

#262 Post by cigam »

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: lang=hu_HU quiet splasht video=SVIDEO-1:d 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19RC1_x64 patito feo October 15  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> Chassis: 
           type: 8 serial: <filter> 
           Mobo: Dell model: 0KU184 serial: <filter> BIOS: Dell v: A19 date: 06/04/2013 
CPU:       Topology: Dual Core model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: D (13) microcode: A4 L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 7979 
           Speed: 798 MHz min/max: 800/2001 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
Graphics:  Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell Latitude D630 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02 
           Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1440x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel 965GM v: 2.1 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:284b 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Broadcom Limited NetXtreme BCM5755M Gigabit Ethernet PCI Express 
           vendor: Dell driver: tg3 v: 3.137 port: 10c0 bus ID: 09:00.0 chip ID: 14e4:1673 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s 
           port: 10c0 bus ID: 0c:00.0 chip ID: 8086:4222 
           IF: wlan0 state: down mac: <filter> 
           Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb bus ID: 1-2:2 
           chip ID: 413c:8140 
Drives:    Local Storage: total: 584.81 GiB used: 25.6 MiB (0.0%) 
           ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: BBF0 scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 410 size: 7.26 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
           ID-3: /dev/sdc type: USB vendor: Samsung model: HM502JX size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> scheme: MBR 
Partition: ID-1: / raw size: N/A size: 1.51 GiB used: 25.6 MiB (1.7%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 58.0 C mobo: N/A sodimm: 51.0 C 
           Fan Speeds (RPM): cpu: 3391 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 187 Uptime: 1m Memory: 1.94 GiB used: 510.6 MiB (25.7%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

User avatar
srq2625
Posts: 188
Joined: Mon Jan 21, 2019 9:40 am

Re: MX-19 RC1 Feedback thread

#263 Post by srq2625 »

Jerry3904 wrote: Mon Oct 21, 2019 1:25 pm @srq2625: as I said, so far I have not been able to replicate this behavior, even with the Panel set to 75 width. If that only happens in a VM but is correct in an installation, it is not much of a problem for us.

We can return to your individual situation after we get MX-19 out the door. When that happens, start a separate thread showing us the steps to take from a clean install of MX-19 to reproduce the problem. Or file that as a bug report (click "Bugs" on the top right menu).
@Jerry3904 : Understood. This does not happen just in a VM. Same exact behavior when installed on bare metal (as the only install on the computer). But, will re-address this after MX-19 is released.

Thanks
AsusTek PRIME B450-Plus
AMD Ryzen 7 2700 (8-Core, 16 threads)
Radeon HD 6570/7570/8550 / R5 230
Realtek RTL8111/8168/8411 - driver: r8169
Samsung SSD 860 EVO 500GB
DDR4 3200MHz CL16 2x8GB

Iguana77

Re: MX-19 RC1 Feedback thread

#264 Post by Iguana77 »

asqwerth wrote: Mon Oct 21, 2019 7:34 am
Iguana77 wrote: Mon Oct 21, 2019 6:57 am

Code: Select all

[MX18]
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard 
           driver: radeon v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: N/A v: N/A direct render: N/A 

Hi this is from live usb>

Code: Select all

[MX19]
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116 
           Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard driver: N/A 
           bus ID: 01:00.0 chip ID: 1002:68a8 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 compat-v: 3.0 
           direct render: Yes 
Video Tweaks:
Detected possible Hybrid Graphics
I don't know enough about video graphics, but it looks like your machine selected and ran with the radeon driver in MX18, but it's using another driver by default in MX19.

You'll have to wait for the experts to give you advice on how to deal with your hybrid graphics.
Thank you for your reply. Whom can I ask for help?

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

Re: MX-19 RC1 Feedback thread

#265 Post by Jerry3904 »

With the release of MX-19, this thread is now closed. Please upgrade to Final before posting further feedback.


Release announcement:
https://forum.mxlinux.org/viewtopic.php?f=131&p=535116

Feedback thread:
https://forum.mxlinux.org/viewtopic.php?f=77&p=535117
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
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

Locked

Return to “General”