MX-23 beta 2 feedback thread

Message
Author
User avatar
gRegNfo
Posts: 35
Joined: Sat Jun 10, 2023 6:30 am

Re: MX-23 beta 2 feedback thread

#531 Post by gRegNfo »

@maci01

Can you check your hardware fits this driver?
I managed to solve it. You can message me if you want guidlines

https://github.com/ivanovborislav/rtl8812au
fehlix wrote: Sun Jul 09, 2023 4:11 pm
Stevo wrote: Sun Jul 09, 2023 3:45 pm

I'm sorry, but I can't see any error...those messages are what we get with a successful module build and install!
This issue is about the reported broken pipe "Error" within the dkms script itself at line 2497 with /sbin/dkms.
They do use "smart" logic to check whether /proc is mounted or not:

Code: Select all

# The <(cmd) idiom does not work if /proc is not mounted
if [ ! -e <(echo) ]; then
    warn $"dkms will not function properly if /proc is not mounted."
fi
I guess something changed in bash - but despite bash's broken pipe the test seems to work.
ASUS Laptop N56VB 1080p
i7-3630QM 2.40GHz Ivy Bridge
16GB DDR3 1600 MHz
2TB HW/SSD RAID-0 SATA3
Intel HD4000 IVB GT2
NVIDIA GK107M GeForce GT-740M 2GB VRAM
Intel Centrino WiFi-N 2230
Qualcomm Atheros AR8161 Gigabit
Intel 7 C210/C216/HM76 Express Chipset

Wallon
Posts: 336
Joined: Wed Oct 21, 2020 4:08 pm

Re: MX-23 beta 2 feedback thread

#532 Post by Wallon »

Dear developers,

A developer reacted by telling me that I shouldn't use Rufus.
He asked me to recreate a Live USB key with the "MX Live USB Maker" program to install the MX Fluxbox 23 ISO beta 2.
I downloaded the ISO again.
I used the "GtkHash" program to check the MD5 and SHA256.
I burned the ISO on a Live USB key with "MX Live USB Maker".
The Live USB key works very well.

Language selection [fr_BE], time zone selection Brussels.
The Azerty keyboard for Belgium is recognised in Geany.
The 3 icons (Videos, Software, Install MX) don't work.

I have restarted the Live USB key.

Language selection [fr], Paris time zone selection.
The Azerty keyboard for France is recognised in Geany.
The 3 icons (Videos, Software, Install MX) don't work.

So there's no difference between Rufus and MX Live USB Maker.

Will there be a new MX Fluxbox 23 ISO version beta 3 ?

Best regards,
Wallon

rbeltz48
Posts: 61
Joined: Mon Jan 28, 2019 9:10 am

Re: MX-23 beta 2 feedback thread

#533 Post by rbeltz48 »

To: Eadwine Rose
Re: Post #492 regarding unintelligible audio with VLC

Here's the output when running VLC through the Terminal, both initializing and then trying to run the .3gp video file in question. Video is OK but audio is garbled both with VLC and also with Dragon Player. However, the file runs AOK with Mint 21.2.

rick@rick-testing:~/Desktop
$ vlc
VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
[000055b08b6a3550] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Gtk-Message: 10:15:52.822: Failed to load module "gail"

** (vlc:27223): WARNING **: 10:15:52.833: (../atk-adaptor/bridge.c:1105):atk_bridge_adaptor_init: runtime check failed: (root)
[000055b08b73de00] main playlist: playlist is empty

libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[00007fdb5c00c0b0] avcodec decoder: Using OpenGL/VAAPI backend for VDPAU for hardware decoding
[mpeg4 @ 0x7fdb5c050780] Failed setup for format vdpau: hwaccel initialisation returned error.
[00007fdb5c00c0b0] avcodec decoder error: existing hardware acceleration cannot be reused
[00007fdb244abb50] gl gl: Initialized libplacebo v4.208.0 (API v208)
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[00007fdb24136ed0] gl gl: Initialized libplacebo v4.208.0 (API v208)
rick@rick-testing:~/Desktop

User avatar
Eadwine Rose
Administrator
Posts: 14444
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-23 beta 2 feedback thread

#534 Post by Eadwine Rose »

@Stevo a vaapi issue above? Cannot remember if you ever saw my post with the tip to downgrade a package to solve the error.. No idea with post # that was anymore though.

edit: viewtopic.php?p=729379#p729379
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

Wallon
Posts: 336
Joined: Wed Oct 21, 2020 4:08 pm

Re: MX-23 beta 2 feedback thread

#535 Post by Wallon »

Dear developers,

I have installed MX Linux KDE beta 2 in [fr_BE] on USB key (format "f2fs")

All is good.

I noticed that the SHA256 and MD5 checks on the SourceForge website do not match the ISO.

Best regards,
Wallon

User avatar
mklym
Posts: 111
Joined: Fri May 03, 2019 11:54 am

Re: MX-23 beta 2 feedback thread

#536 Post by mklym »

Code: Select all

System:
  Kernel: 6.1.0-9-686-pae [6.1.27-1] arch: i686 bits: 32 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-686-pae root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_beta2_386 Libretto June 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Matsushita product: CF-29LTQGZBM v: 004 serial: <superuser required>
  Mobo: Matsushita model: CF29-4 v: 001 serial: <superuser required> BIOS: Phoenix K.K.
    v: 4.00L11 date: 07/19/2005
Battery:
  ID-1: BATA charge: 14.4 Wh (27.0%) condition: 53.4/84.9 Wh (62.9%) volts: 11.6 min: 11.1
    model: Panasonic CF-VZSU29A type: Li-ion serial: <filter> status: charging
CPU:
  Info: model: Intel Pentium M bits: 32 arch: M Dothan built: 2003-05 process: Intel 90nm family: 6
    model-id: 0xD (13) stepping: 8 microcode: 0x20
  Topology: cpus: 1x cores: 1 smt: <unsupported> cache: 2 MiB note: check
  Speed (MHz): 1600 min/max: 600/1600 scaling: driver: acpi-cpufreq governor: ondemand core:
    1: 1600 bogomips: 3191
  Flags: nx pae sse sse2
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics vendor: Matsushita driver: i915
    v: kernel arch: Gen-3 code: Intel 130nm built: 2004-05 ports: active: LVDS-1 empty: VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:2592 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: intel
    unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99") s-diag: 338mm (13.3")
  Monitor-1: LVDS-1 mapped: LVDS1 res: 1024x768 hz: 60 size: N/A modes: 1024x768
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: i915 (: 915GM) direct-render: Yes
Audio:
  Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio vendor: Matsushita driver: snd_intel8x0
    v: kernel bus-ID: 00:1e.2 chip-ID: 8086:266e class-ID: 0401
  API: ALSA v: k6.1.0-9-686-pae status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Marvell 88E8053 PCI-E Gigabit Ethernet vendor: Matsushita driver: sky2 v: 1.30 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 11ab:4362 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel PRO/Wireless 2915ABG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq
    modules: wl bus-ID: 06:02.0 chip-ID: 8086:4223 class-ID: 0280
  IF: eth1 state: down mac: <filter>
Drives:
  Local Storage: total: 27.96 GiB used: 17.96 GiB (64.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: THNSNB030GMCJ size: 27.96 GiB block-size:
    physical: 512 B logical: 512 B speed: <unknown> type: SSD serial: <filter> rev: 0202 scheme: MBR
Partition:
  ID-1: / raw-size: 27.95 GiB size: 27.34 GiB (97.83%) used: 17.96 GiB (65.7%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 1024 MiB used: 340.2 MiB (33.2%) priority: -2 file: /swapfile
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 2046 libs: 1035 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.it.ubc.ca/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 184 Uptime: 46m wakeups: 6 Memory: 1.46 GiB used: 1.09 GiB (74.5%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Unit runs good without any major issues. VLC works with no errors. I was just streaming some SuperCars from Oz in 720p and it was smooth without artifacts, tearing, etc.
I did notice that the QSI shows "Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors." but I have a terminal open running watch on sensors w/2 sec refresh showing 61.8C after watching the stream.
One thing that I have noticed is that when the screensaver, w/the default settings, kicks in the only way I can get out of it is ctrl+alt+backspace and then log back into my account.
CF-29LTQ, CF-30FCS, CF-31SBM, CF-52GUN, CF-53AAG, HP Z420

Life's Journey is not to arrive safely at the grave in a well preserved body, but rather to skid in sideways totally worn-out shouting 'Woo Hoo! What a ride!'

User avatar
daemonspudguy
Posts: 31
Joined: Tue Jun 20, 2023 6:12 pm

Re: MX-23 beta 2 feedback thread

#537 Post by daemonspudguy »

What is considered the default wallpaper for MX-23 beta 2? I've been using the Tangram wallpaper but I'm curious which is default. Also, I would personally suggest shipping 16:9 aspect ratio wallpapers as well because it's way more common than 16:10 in this day and age.

User avatar
dolphin_oracle
Developer
Posts: 22034
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 beta 2 feedback thread

#538 Post by dolphin_oracle »

daemonspudguy wrote: Mon Jul 10, 2023 1:06 pm What is considered the default wallpaper for MX-23 beta 2? I've been using the Tangram wallpaper but I'm curious which is default. Also, I would personally suggest shipping 16:9 aspect ratio wallpapers as well because it's way more common than 16:10 in this day and age.
the wallpaper that is on beta2 is default. it should be in your desktop settings as "default.png".
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.

User avatar
maci01
Posts: 2
Joined: Sun Jul 09, 2023 4:44 am

Re: MX-23 beta 2 feedback thread

#539 Post by maci01 »

@gRegNfo

It is elderly NTB asus x571G intel630/nv1050 mobile. I tried connecting BT headphones and they work. It was probably really just a message about a bad module loading. Sorry for the alarm and thank you for your time. Have a nice evening.

User avatar
dadada
Posts: 1
Joined: Mon Jul 10, 2023 2:32 pm

Re: MX-23 beta 2 feedback thread

#540 Post by dadada »

Hi.
I am currently using Mx-23. The question is, which version? I know that I downloaded the beta one and had it installed. I was enjoying using that. Later I downloaded beta two with intentions of checking it out for you (and of course myself.) I am not certain if I installed it. I don't think so.
Is there someway to check which beta I am using? Or is beta one updated to beta two anyway, by way of updates?
Thanks for your attention.

Locked

Return to “General”