antiX-23-beta1-runit-full (64bit) for testing

[Forum Admin anticapitalista]

Helpful

Up

0

::

Wallon wrote:

I don’t understand why I don’t have the same Belgian keyboard on antiX 21/22 and antiX 23.
I have 2 installations of antiX 23 on 2 computers (desktop/laptop). It’s the same on both computers.
I compared the /etc/default/keyboard file of antiX 21/22 and antiX 23. It’s the same script. However, I don’t have the same keyboards!

Is there another file to check?

Give us an example so we can see if we can reproduce the problem.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Wallon]

Helpful

Up

0

::

Dear anticapitalista,

For the right apostrophe to put in the translations, on a Belgian linux keyboard, you do Shift + AltGr + B and you get

the typographic apostrophe ’ (turned to the left)

I found a copy of my Linux keyboard on the web. I put the image on the forum. This image corresponds exactly to antiX 22.

In antiX 23, with the same keys, it is another apostrophe turned to the right. I have to use another combination with antiX 23, it is Shift + AltGr + N.
I could not find on the web an image of a Belgian Linux keyboard with these symbols.

Best regards,
Wallon

Attachments:

1. 

   KB_AZERTY_BE_Linux.png
   

[Member Wallon]

Helpful

Up

0

::

Dear anticapitalista,

Concerning the Belgian azerty keyboard, I also checked in the dmesg log if my “Microsoft Wired Keyboard 600” on my desktop was detected. The kernel does detect my keyboard. I think there is no firmware problem.

Best regards,
Wallon

[Member Robin]

Helpful

Up

0

::

@Wallon
Please check whether you have the very same settings in antiX control centre → System → Set System wide Keyboard layout
Click the “+” button to add keyboard layouts. When selecting “French” you’ll find in the lower pulldown menu lots of “Variants” of the french keyboard. Maybe you need to select another variant for your keyboard to get the key assigning right?

Französisch (AFNOR-standardisiertes AZERTY)
Französisch (AZERTY)
Französisch (Alternative, veraltet)
Französisch (Alternative, veraltet, mit Sun Akzenttasten)
Französisch (Alternative, veraltet, ohme Akzenttasten)
Französisch (Bepo, ergonomisch, Dvorak-ähnlich)
Französisch (Dvorak)
Französisch (Macintosh)
Französisch (Sun Typ 6/7)
Französisch (...)
...

Windows is like a submarine. Open a window and serious problems will start.

[Member Wallon]

Helpful

Up

0

::

Dear Robin,

This is the first thing I did, I tested all possible combinations of the system keyboard in the control centre.

Cordialement,
Wallon

[Moderator Brian Masinick]

Helpful

Up

0

::

This device, TOSHIBA product: Satellite L45, definitely works with the 6.1.18-antix.1-amd64-smp image, but I believe I had problems with the 5.10 image; will check again.

One of my other old devices, a Lenovo Thinkpad X201 DEFINITELY DOES work with both kernels; I’ll check this system and the other Thinkpad T510 to ensure which kernels work properly. I’ll reply again with one or more notes in a while, confirming each detail.

EDIT: The Toshiba Satellite L45 STARTS booting with the 5.10.173 kernel; when I enable boot messages, the system boots normally until it gets into the X server phase, and it even BEGINS there, but along the way there appear to be files and or directories missing and it hangs. Attempts to find any logs with details about specifically what is happening, unfortunately, have been fruitless, whereas logs of 6.1.8 appear and are clean, very normal. I wish I could find more, but I’ve spent a couple of hours going between the two kernels and have found zero pieces of solid details about the hang before the X server displays the desktop.

Brian Masinick wrote:

Here’s another device that works

inxi -b
System:
  Host: antix23 Kernel: 6.1.18-antix.1-amd64-smp arch: x86_64 bits: 64
    Desktop: IceWM v: 3.3.2 Distro: antiX-23-beta1-runit_x64-full Grup Yorum 21
    March 2023
Machine:
  Type: Laptop System: TOSHIBA product: Satellite L45 v: PSL48U-01S004
    serial: <superuser required>
  Mobo: TOSHIBA model: Satellite L45 v: 1.0 serial: <superuser required>
    BIOS: American Megatrends v: 1.50 date: 08/21/2007
Battery:
  ID-1: BAT0 charge: 25.8 Wh (100.0%) condition: 25.8/44.0 Wh (58.5%)
CPU:
  Info: dual core Intel Pentium Dual T2310 [MCP] speed (MHz): avg: 798
    min/max: 800/1467
Graphics:
  Device-1: Intel Mobile GM965/GL960 Integrated Graphics driver: i915
    v: kernel
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: crocus
    gpu: i915 resolution: 1280x800~60Hz
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel 965GM (CL)
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
    driver: 8139too
  Device-2: Realtek RTL8187B Wireless Adapter type: USB driver: rtl8187
Drives:
  Local Storage: total: 119.24 GiB used: 5.24 GiB (4.4%)
Info:
  Processes: 137 Uptime: 32m Memory: 1.92 GiB used: 1.18 GiB (61.7%)
  Shell: Bash inxi: 3.3.26

• This reply was modified 1 month ago by Brian Masinick. Reason: 5.10.173 hangs, no details found

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

My two Thinkpad models, the X201 and the T510 work correctly with BOTH antiX 23 Beta 1 kernels.

ping -c2 yahoo.com
PING yahoo.com (98.137.11.163): 56 data bytes
64 bytes from 98.137.11.163: icmp_seq=0 ttl=48 time=82.614 ms
64 bytes from 98.137.11.163: icmp_seq=1 ttl=48 time=85.219 ms
--- yahoo.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 82.614/83.916/85.219/1.303 ms
[antix23]/home/masinick: > inxi -b
System:
  Host: antix23 Kernel: 5.10.173-antix.1-amd64-smp arch: x86_64 bits: 64
    Desktop: IceWM v: 3.3.2 Distro: antiX-23-beta1-runit_x64-full Grup Yorum 21
    March 2023
Machine:
  Type: Laptop System: LENOVO product: 43843AU v: ThinkPad T510
    serial: <superuser required>
  Mobo: LENOVO model: 43843AU serial: <superuser required> BIOS: LENOVO
    v: 6MET61WW (1.24 ) date: 06/07/2010
Battery:
  ID-1: BAT0 charge: 0% condition: N/A/103.5 Wh volts: 7.5 min: 11.1
CPU:
  Info: dual core Intel Core i5 M 520 [MT MCP] speed (MHz): avg: 2538
    min/max: 1199/2400
Graphics:
  Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel
  Device-2: Lenovo Integrated Webcam [R5U877] type: USB driver: uvcvideo
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: crocus
    gpu: i915 resolution: 1366x768~60Hz
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK)
Network:
  Device-1: Intel 82577LM Gigabit Network driver: e1000e
  Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi
Drives:
  Local Storage: total: 119.24 GiB used: 6.56 GiB (5.5%)
Info:
  Processes: 172 Uptime: 3m Memory: 3.62 GiB used: 1 GiB (27.7%) Shell: Bash
  inxi: 3.3.25

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

To summarize my antiX 23 Beta 1 testing with my various computers:

1) My new HP-14 laptop, 2021 manufactured, works only with very late Version 5 kernels and Version 6 kernels, but it does NOT load Wi-Fi modules when booting the 5.10 kernels, so it’s not usable with any of them.

2) My Dell Inspiron 5558 laptop will work with many different kernels, but it has always had issues with Debian and antiX 5.10 kernels; on rare occasions I can coax them to work, but it is too much effort. All other kernels and features, however, work VERY well. EXCEPT for the one kernel issue, this system is perfect with antiX; it always works with modern equipment and it’s usually pretty hospitable to older things too; for instance, I’ve used 4.9, 4.14, and 4.19 kernels with it in the past, and all 5 series kernels except for 5.10.*.

3) My freebies that I’ve acquired from various places work well with antiX too, but they’re much slower than the hardware above. The HP Pavilion Slimline D5000 series desktop works with all of the kernel software and in general Beta testing, performed adequately with no surprises. The Lenovo X201 was used quite a bit in both Alpha and Beta tests, and all kernels and applications worked as expected, other than the common reported issues. The Lenovo Thinkpad T510, which I’m using now, has been performing the same tasks I’ve done previously with the X201. The one system in this group that had issues with the kernel was once again with the 5.10.173 kernel, documented in post #104221.

--
Brian Masinick

[Member olsztyn]

Helpful

Up

0

::

Brian Masinick wrote:

EDIT: The Toshiba Satellite L45 STARTS booting with the 5.10.173 kernel; when I enable boot messages, the system boots normally until it gets into the X server phase, and it even BEGINS there, but along the way there appear to be files and or directories missing and it hangs. Attempts to find any logs with details about specifically what is happening, unfortunately, have been fruitless, whereas logs of 6.1.8 appear and are clean, very normal.

Your Toshiba Satellite L45 seems to have almost identical look, specs and composition as my Toshiba Satellite A205. They appear also from the same year (2006 or 2007 depending on when manufactured).
Screen resolution also the same 1280×800.
The only minor difference I see is processor T2310 on yours and T2390 on mine, which is just a minor difference in speed.
However mine works just fine with both kernels, while yours seems to have some issue with kernel 5.10…
This is very strange that almost identical laptops could behave so differently…
One possibility to take into account is antiX 23 Beta update level:

My antiX 23 Beta is what was originally published by anticapitalista but fully updated where it made sense to update. This means:
– I never allow Debian version to replace antiX specific version.
– When updating I do not let replace stable level components with beta level components.

Nothing else comes to my mind that would explain such different behavior of virtually identical laptops…

• This reply was modified 1 month ago by olsztyn.
• This reply was modified 1 month ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator Brian Masinick]

Helpful

Up

0

::

I’m not going to go into much depth when it comes to the Toshiba. For it’s age the equipment looks great, but out of all of my systems, including the HP Pavilion Slimline desktop, the Toshiba is definitely the slug of the group. The only reason it caught my interest and excitement was that one of my early laptops was also a Toshiba; this one is newer, and like I said, “looks great”. Unfortunately that’s about it. I’m planning to recycle this one and donate it to a local organization, possibly the nearby Good Will. They employ plenty of people and if someone can benefit from the unit, the gentleman that donated it to me was equally kind; I’m hoping the right person can make good use of it.

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

The Toshiba and an old HP laptop with a semi-faulty hinge are now in my “donation bag” for whenever I redistribute these resources.

--
Brian Masinick

[Moderator BobC]

Helpful

Up

0

::

I had good luck with the alpha on 5 of my different Dell laptops. I’ve now installed the beta to mt Dell E5540 and I did have a lack of sound in Firefox originally, but I ran the update and upgrade, and saw it brought in a newer Firefox, and sound is now working.

I also got my bluetooth headphones working. I had to make a couple manual configuration changes to get it working, but I really do like having that capability.

One thought. A number of times I’ve made the wrong selection on the install where it says system uses local time, and sometimes I need to check it and other times not. Could we put the actual time values that would be displayed there next to the selection so it would be obvious what the correct choice would be?

Thanks anticapitalista! This is the best beta I’ve ever tried 🙂

[Moderator Brian Masinick]

Helpful

Up

0

::

@BobC: re: “his is the best beta I’ve ever tried 🙂”

I’m not sure that I can say that, because MEPIS, MX Linux, and antiX have always had very good Alpha and Beta testing phases throughout their history.
In all the years I’ve used them, I believe I can recall *one time* when a first Alpha build wouldn’t boot for me; I reported the configuration and the circumstances immediately, and in 24-48 hours there was a solution and that is the last time I can remember such an event.

In our Alpha testing cycle we had pretty good cooperation and coverage; I’m hoping the same has been true for this Beta 1 test.
Regarding Bookworm, the Debian project is proceeding pretty well; I actually saw a “Release Candidate 1” for their installation tool for Bookworm, but I’m not sure this translates into a “Release Candidate” for Bookworm quite yet, but they’re also doing a pretty good job, and in the communications I’ve seen from their project team, the Project Leader and the primary development team members are doing a good job of identifying the most important elements needed to successfully complete the release, so if this continues, the days of Debian having extremely variable, unreliable and unknown schedule dates, if not over, are at least greatly improved.

https://www.debian.org/News/weekly/2022/01/ holds the current schedule. Unfortunately, it looks the same as the LAST TIME I checked:

“March 2023 (2023-03-12): Milestone 3 – Hard Freeze – for key packages and packages without autopkgtests
To be announced: Milestone 4 – Full Freeze”

So we still don’t know when the release will take place. What we DO know is that the installer for the next release is progressing very well and a lot of the code is quite solid, as we can see in our antiX software. That’s it for now.

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

Just to follow up on the previous post, this has ALSO been a VERY GOOD testing cycle; it’s in keeping with some of our very best work, no doubt about it!

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

Also, the message for the transition and toolchain freeze, along with the Milestones 2 and 3 Soft Freeze and Hard Freeze notifications was sent out by
From: Paul Gevers
Date: Thu, 19 Jan 2023 08:18:52 +0000
he freeze contains 3 more milestones:
* 2023-02-12 – Milestone 2 – Soft Freeze
no new packages, delayed migration
* 2023-03-12 – Milestone 3 – Hard Freeze – key packages and packages
without autopkgtests need a manual unblock for migration
* TBA – Milestone 4 – Full Freeze
all packages need a manual unblock for migration

Nothing since then that I’ve seen.

--
Brian Masinick

[Author]

Posts