astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] Astlinux-users Digest, Vol 230, Issue 4

[Gonzalo I. <gon...@ho...>]

Thanks anyway for all these years of fun and entertainment and for your dedication to this project which made it possible.

Whenever Astlinux reach EOL it will be still worth using it as a second life for analog phones and old boxes on isolated environments.

Regards.

Re: [Astlinux-users] New AstLinux installations are no longer recommended ???

[Michael K. <mic...@ip...>]

I will most certainly second that.

Regards
Michael Knill

From: Dan Ryson <da...@ry...>
Date: Thursday, 12 March 2026 at 10:25 pm
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] New AstLinux installations are no longer recommended ???


All,

This seems like a good time for me to express thanks to Lonnie and all the AstLinux developers for their decades of hard work, professionalism, and dedication.  Your efforts are greatly appreciated.

Dan

On Wednesday, 11-03-2026 at 17:58 David Kerr wrote:

I recently (within last month) bought myself a Unifi Cloud Gateway Fiber... it replaced my Astlinux as the household gateway.  I made this switch with a heavy heart, I've been a huge supporter of Astlinux, I have used it since 2008, I've contributed fixes and enhancements to it, I maintain my own fork for my personal use, it has provided me hours of enjoyment (yes, I love coding).

But... as I get older and consider the future I felt the time had come to switch to a commercial solution.  For years there was no commercial solution that came close to the flexibility that Astlinux offered, but that is no longer the case.  Unifi gateway is very powerful and can do everything I was using Astlinux for and more.  There are others, I picked Unifi because I already use their WiFi AP's and switches.

There are some things that I was running on Astlinux that I now run in separate servers (proxmox containers), e.g. web server.  And I have "simplified" my VoIP by directly registering my phones with voip.ms<http://voip.ms> (I am considering running Unifi Talk... but you need at least one of their proprietary phones before you can add other generics).

Lonnie has been carrying the weight of keeping Astlinux up-to-date for years.  And I am sure this was hard for him.  But I suspect his rationale was very similar to mine.

David.


On Wed, Mar 11, 2026 at 4:10 PM Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote:

> On Mar 11, 2026, at 2:59 PM, Steve Barlow <ste...@gm...<mailto:ste...@gm...>> wrote:
>
> Please have a look here....
>
> https://www.astlinux-project.org/about.html
>
> It is saying:
>
> AstLinux Now:
> After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended.
> Comments please...
> Steve

Not sure what is unclear.

Updating existing installations is encouraged, but consider other solutions when starting "new".

Lonnie



_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.

Re: [Astlinux-users] New AstLinux installations are no longer recommended ???

[Lonnie A. <li...@lo...>]

> --
> After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended.
> --

I have been asked to clarify the wording.

"Deprecation" [1] does not mean ending updates/security fixes, updates/security fixes will continue for some (unspecified) period of time.

Why? I'm pushing 70 years old. There are other reasons as well.

AstLinux's core is in the same era as Debian 11 'bullseye' which is also considered deprecated.  Similarly, new Debian 11 deployments are no longer recommended.

"EOL" [2] would imply no updates.  That is *not* currently the case at 2026-03-01.

Lonnie

[1] "Deprecation refers to the discouragement of using a particular technology, feature, or practice. It often indicates that something is considered inferior compared to newer alternatives."

[2] "End of Life (EOL) refers to the stage in a product's lifecycle when it is no longer sold or supported by the manufacturer, meaning it will not receive updates, patches, or new features."

Re: [Astlinux-users] New AstLinux installations are no longer recommended ???

[Dan R. <da...@ry...>]

All,

This seems like a good time for me to express thanks to Lonnie and all
the AstLinux developers for their decades of hard work,
professionalism, and dedication.  Your efforts are greatly
appreciated.    

Dan

On Wednesday, 11-03-2026 at 17:58 David Kerr wrote:



 



I recently (within last month) bought myself a Unifi Cloud Gateway
Fiber... it replaced my Astlinux as the household gateway.  I made
this switch with a heavy heart, I've been a huge supporter of
Astlinux, I have used it since 2008, I've contributed fixes and
enhancements to it, I maintain my own fork for my personal use, it has
provided me hours of enjoyment (yes, I love coding). 
  
But... as I get older and consider the future I felt the time had
come to switch to a commercial solution.  For years there was no
commercial solution that came close to the flexibility that Astlinux
offered, but that is no longer the case.  Unifi gateway is very
powerful and can do everything I was using Astlinux for and more. 
There are others, I picked Unifi because I already use their WiFi AP's
and switches. 
  
There are some things that I was running on Astlinux that I now run in
separate servers (proxmox containers), e.g. web server.  And I have
"simplified" my VoIP by directly registering my phones with voip.ms
[1] (I am considering running Unifi Talk... but you need at least one
of their proprietary phones before you can add other generics). 
  
Lonnie has been carrying the weight of keeping Astlinux up-to-date for
years.  And I am sure this was hard for him.  But I suspect his
rationale was very similar to mine. 
  
David. 
   


On Wed, Mar 11, 2026 at 4:10 PM Lonnie Abelbeck 
	*  wrote: 


> On Mar 11, 2026, at 2:59 PM, Steve Barlow  wrote:
> 
> Please have a look here....
> 
> https://www.astlinux-project.org/about.html
> 
> It is saying:
> 
> AstLinux Now:
> After over 21 years (2026-03-01), AstLinux is considered deprecated.
New AstLinux installations are no longer recommended.
> Comments please...
> Steve

Not sure what is unclear.

Updating existing installations is encouraged, but consider other
solutions when starting "new".

Lonnie



_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

    



Links:
------
[1] http://voip.ms

Re: [Astlinux-users] New AstLinux installations are no longer recommended ???

[Edson W. <eds...@vi...>]

Em 11/03/2026 03:59 PM, Steve Barlow escreveu:
> Please have a look here....
> 
>  https://www.astlinux-project.org/about.html
> 
>  It is saying:
> 
>  _AstLinux Now:_
>  _After over 21 years (2026-03-01), AstLinux is considered deprecated.
> __New AstLinux installations are no longer recommended._
>  Comments please...
>  Steve
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> pa...@kr....
> After over 21 years (2026-03-01), AstLinux is considered deprecated. 
> New AstLinux installations are no longer recommended.
-- 

Why is that? It's super compatible with all our hardware...!?!?


A persistência é o caminho do êxito.
Charles Chaplin

Re: [Astlinux-users] New AstLinux installations are no longer recommended ???

[David K. <da...@ke...>]

I recently (within last month) bought myself a Unifi Cloud Gateway Fiber...
it replaced my Astlinux as the household gateway.  I made this switch with
a heavy heart, I've been a huge supporter of Astlinux, I have used it since
2008, I've contributed fixes and enhancements to it, I maintain my own fork
for my personal use, it has provided me hours of enjoyment (yes, I love
coding).

But... as I get older and consider the future I felt the time had come to
switch to a commercial solution.  For years there was no commercial
solution that came close to the flexibility that Astlinux offered, but that
is no longer the case.  Unifi gateway is very powerful and can do
everything I was using Astlinux for and more.  There are others, I picked
Unifi because I already use their WiFi AP's and switches.

There are some things that I was running on Astlinux that I now run in
separate servers (proxmox containers), e.g. web server.  And I have
"simplified" my VoIP by directly registering my phones with voip.ms (I am
considering running Unifi Talk... but you need at least one of their
proprietary phones before you can add other generics).

Lonnie has been carrying the weight of keeping Astlinux up-to-date for
years.  And I am sure this was hard for him.  But I suspect his rationale
was very similar to mine.

David.


On Wed, Mar 11, 2026 at 4:10 PM Lonnie Abelbeck <li...@lo...>
wrote:

>
> > On Mar 11, 2026, at 2:59 PM, Steve Barlow <ste...@gm...> wrote:
> >
> > Please have a look here....
> >
> > https://www.astlinux-project.org/about.html
> >
> > It is saying:
> >
> > AstLinux Now:
> > After over 21 years (2026-03-01), AstLinux is considered deprecated. New
> AstLinux installations are no longer recommended.
> > Comments please...
> > Steve
>
> Not sure what is unclear.
>
> Updating existing installations is encouraged, but consider other
> solutions when starting "new".
>
> Lonnie
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....

Re: [Astlinux-users] New AstLinux installations are no longer recommended ???

[Lonnie A. <li...@lo...>]

> On Mar 11, 2026, at 2:59 PM, Steve Barlow <ste...@gm...> wrote:
> 
> Please have a look here....
> 
> https://www.astlinux-project.org/about.html
> 
> It is saying:
> 
> AstLinux Now:
> After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended.
> Comments please...
> Steve

Not sure what is unclear.

Updating existing installations is encouraged, but consider other solutions when starting "new".

Lonnie

[Astlinux-users] New AstLinux installations are no longer recommended ???

[Steve B. <ste...@gm...>]

Please have a look here....

https://www.astlinux-project.org/about.html

It is saying:

AstLinux Now:
After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended.
Comments please...
Steve

[Astlinux-users] Announcing AstLinux Release: 1.5.13

[Lonnie A. <li...@lo...>]

Announcing AstLinux Release: 1.5.13

More Info: AstLinux Project
https://www.astlinux-project.org/

Changes to supported firmware builds:
* Previous 'ast16se' and 'ast18' firmware branches are no longer updated.
* New 'ast18se' firmware branch, Asterisk 18.x built --without-pjproject and --without-dahdi
* Previous 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and --with-dahdi

AstLinux 1.5.13 Highlights:
* Asterisk Versions: 18.26.4, 20.18.2
* Linux Kernel 5.10.249-cip69, security and bug fixes
* RUNNIX, version bump to runnix-0.6.25
* OpenSSL, version 1.1.1w, security fixes: CVE-2025-68160, CVE-2025-69418, CVE-2025-69419, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796
* libcurl (curl) version bump to 8.17.0
* libpng, version bump to 1.6.55, security fixes: CVE-2025-64505, CVE-2025-64506, CVE-2025-64720, CVE-2025-65018, CVE-2025-66293, CVE-2026-22695, CVE-2026-22801, CVE-2026-25646
* libsodium, version bump to 1.0.21, security fix
* avahi, version 0.6.32, security fixes: CVE-2021-3468, CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473, CVE-2024-52616, CVE-2024-52615, CVE-2025-68276, CVE-2025-68468, CVE-2025-68471, CVE-2026-24401
* expat, version bump to 2.7.4, security fixes: CVE-2026-24515, CVE-2026-25210
* fping, version bump to 5.5
* iperf3, version bump to 3.20
* netsnmp, version 5.9.4, security fix: CVE-2025-68615
* pcre2, new package, version 10.47, newer though incompatible API from older pcre
* php, version 7.2.34, add security fixes: CVE-2025-14177, CVE-2025-14178, GHSA-www2-q4fc-65wf
* sqlite, version bump to 3.51.2
* strongSwan, version 5.5.3, security fix: CVE-2025-62291
* unbound, version bump to 1.24.2, security fix: CVE-2025-11411
* unixodbc, version bump to 2.3.14
* ca-certificates, update trusted root certificates 2025-12-02
* mac2vendor, oui.txt database snapshot 2026-01-16
* Time Zone Database update, tzdata2025c and php-timezonedb-2025.3
* Asterisk '18se' (stable edition) version 18.26.4 is the last Asterisk 18.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes
* Package upgrades providing important security and bug fixes

Full ChangeLog:
https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.13/docs/ChangeLog.txt

All users are encouraged to upgrade, read the ChangeLog for the details.

AstLinux Project

Re: [Astlinux-users] Start without Asterisk?

[David K. <da...@ke...>]

Thank you, this works.

David.

On Thu, Feb 19, 2026 at 6:31 PM Michael Knill <
mic...@ip...> wrote:

> Yep works well. I have used it on lots of my gateway only boxes.
>
> Regards
>
> Michael Knill
>
>
> *From: *Michael Keuter <li...@mk...>
> *Date: *Friday, 20 February 2026 at 4:47 am
> *To: *ast...@li... <
> ast...@li...>
> *Subject: *Re: [Astlinux-users] Start without Asterisk?
>
> Hi David,
>
> simple, add this to your „user.conf“:
>
> ASTERISK_DAHDI_DISABLE="yes"
>
> Sent from a mobile device.
>
> Michael Keuter
>
> Am 19.02.2026 um 17:48 schrieb David Kerr <da...@ke...>:
>
> 
> Is there a way to have astlinux boot up without automatically starting
> Asterisk?
>
> Thanks
> David
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....

Re: [Astlinux-users] Start without Asterisk?

[Michael K. <mic...@ip...>]

Yep works well. I have used it on lots of my gateway only boxes.

Regards
Michael Knill

From: Michael Keuter <li...@mk...>
Date: Friday, 20 February 2026 at 4:47 am
To: ast...@li... <ast...@li...>
Subject: Re: [Astlinux-users] Start without Asterisk?

Hi David,

simple, add this to your „user.conf“:

ASTERISK_DAHDI_DISABLE="yes"

Sent from a mobile device.

Michael Keuter

Am 19.02.2026 um 17:48 schrieb David Kerr <da...@ke...>:


Is there a way to have astlinux boot up without automatically starting Asterisk?

Thanks
David
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Start without Asterisk?

[Michael K. <li...@mk...>]

Hi David,

simple, add this to your „user.conf“:

ASTERISK_DAHDI_DISABLE="yes"

Sent from a mobile device.

Michael Keuter

> Am 19.02.2026 um 17:48 schrieb David Kerr <da...@ke...>:
> 
> 
> Is there a way to have astlinux boot up without automatically starting Asterisk?
> 
> Thanks
> David
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] Start without Asterisk?

[David K. <da...@ke...>]

Is there a way to have astlinux boot up without automatically starting
Asterisk?

Thanks
David

Re: [Astlinux-users] Certificate authority files missing

[Michael K. <mic...@ip...>]

Oh man. Of course! That was the problem.
Thanks so much Lonnie.


Regards

Michael Knill



From: Lonnie Abelbeck <li...@lo...>
Date: Wednesday, 4 February 2026 at 10:37 pm
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Certificate authority files missing

Check your sip.conf file, for ACME certs you only need:
--
# grep -r '/sip-tls/' /etc/asterisk/
/etc/asterisk/sip.conf:tlscertfile=/mnt/kd/ssl/sip-tls/keys/server.crt
/etc/asterisk/sip.conf:tlsprivatekey=/mnt/kd/ssl/sip-tls/keys/server.key
--

Possibly you have 'tlscafile' defined, and the self-signed CA is no longer valid.

Lonnie



> On Feb 4, 2026, at 12:26 AM, Michael Knill <mic...@ip...> wrote:
>
> Sorry Lonnie
>
> Here is the error Im getting after an Asterisk reload:
>
> [Feb  4 17:13:48] ERROR[17736]: tcptls.c:524 __ssl_setup: TLS/SSL CA file(/mnt/kd/ssl/sip-tls/keys/ca.crt)/path() error
> [Feb  4 17:13:48] ERROR[17736]: tcptls.c:126 write_openssl_error_to_log: 23216157824768:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/mnt/kd/ssl/sip-tls/keys/ca.crt','r')
> 23216157824768:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
> 23216157824768:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:crypto/x509/by_file.c:199:
>
> I tried the 'openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer’ and it seemed to show the correct info.
>
> Strange!
>
> Regards
> Michael Knill
>   From: Lonnie Abelbeck <li...@lo...>
> Date: Wednesday, 4 February 2026 at 6:23 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Certificate authority files missing
>
> Hi Michael,
>
> I have not seen and issues related to SIP-TLS certificates.
>
> When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"
>
> <Screenshot 2026-02-03 at 10.39.37 AM.png>
>
>
> The ACME, Let's Encrypt cert gets installed and the service is restarted.
>
> You can test what is the issuer from the localhost shell
>
> ## HTTPS
> $ openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
>
> ## SIP-TLS
> $ openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
>
> $ ls -l /mnt/kd/ssl/sip-tls/keys/
> total 8
> -rw-r--r--    1 root     root          3620 Dec 21 01:18 server.crt
> -rw-------    1 root     root          1679 Dec 21 01:18 server.key
>
> There are no ca.crt or ca.key files since they are ACME, only self-signed needs those files.
>
> What Asterisk error are you getting?
>
> The SIP-TLS self-signed cert can be generated, but with warnings of overwriting the Let's Encrypt version.
>
> Lonnie
>
>
>
>
> > On Feb 2, 2026, at 8:02 PM, Michael Knill <mic...@ip...> wrote:
> >
> > Hi Team
> >
> > An email from my developer.
> >
> > Regards
> > Michael Knill
> >   From: Matthew Knill <mat...@ip...>
> > Date: Tuesday, 3 February 2026 at 12:51 pm
> > To: Michael Knill <mic...@ip...>
> > Subject: Certificate authority files missing
> >
> > We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.
> >   I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…
> >   Regards,
> > Matthew Knill
> >   _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
>   _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Certificate authority files missing

[Lonnie A. <li...@lo...>]

Check your sip.conf file, for ACME certs you only need:
--
# grep -r '/sip-tls/' /etc/asterisk/
/etc/asterisk/sip.conf:tlscertfile=/mnt/kd/ssl/sip-tls/keys/server.crt
/etc/asterisk/sip.conf:tlsprivatekey=/mnt/kd/ssl/sip-tls/keys/server.key
--

Possibly you have 'tlscafile' defined, and the self-signed CA is no longer valid.

Lonnie

 

> On Feb 4, 2026, at 12:26 AM, Michael Knill <mic...@ip...> wrote:
> 
> Sorry Lonnie
> 
> Here is the error Im getting after an Asterisk reload:
> 
> [Feb  4 17:13:48] ERROR[17736]: tcptls.c:524 __ssl_setup: TLS/SSL CA file(/mnt/kd/ssl/sip-tls/keys/ca.crt)/path() error
> [Feb  4 17:13:48] ERROR[17736]: tcptls.c:126 write_openssl_error_to_log: 23216157824768:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/mnt/kd/ssl/sip-tls/keys/ca.crt','r')
> 23216157824768:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
> 23216157824768:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:crypto/x509/by_file.c:199:
> 
> I tried the 'openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer’ and it seemed to show the correct info.
> 
> Strange!
> 
> Regards
> Michael Knill
>   From: Lonnie Abelbeck <li...@lo...>
> Date: Wednesday, 4 February 2026 at 6:23 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Certificate authority files missing
> 
> Hi Michael,
> 
> I have not seen and issues related to SIP-TLS certificates.
> 
> When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"
> 
> <Screenshot 2026-02-03 at 10.39.37 AM.png> 
> 
> 
> The ACME, Let's Encrypt cert gets installed and the service is restarted.
> 
> You can test what is the issuer from the localhost shell
> 
> ## HTTPS
> $ openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
> 
> ## SIP-TLS
> $ openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
> 
> $ ls -l /mnt/kd/ssl/sip-tls/keys/
> total 8
> -rw-r--r--    1 root     root          3620 Dec 21 01:18 server.crt
> -rw-------    1 root     root          1679 Dec 21 01:18 server.key
> 
> There are no ca.crt or ca.key files since they are ACME, only self-signed needs those files.
> 
> What Asterisk error are you getting?
> 
> The SIP-TLS self-signed cert can be generated, but with warnings of overwriting the Let's Encrypt version.
> 
> Lonnie
> 
> 
> 
> 
> > On Feb 2, 2026, at 8:02 PM, Michael Knill <mic...@ip...> wrote:
> >
> > Hi Team
> >
> > An email from my developer.
> >
> > Regards
> > Michael Knill
> >   From: Matthew Knill <mat...@ip...>
> > Date: Tuesday, 3 February 2026 at 12:51 pm
> > To: Michael Knill <mic...@ip...>
> > Subject: Certificate authority files missing
> >
> > We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.
> >   I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…
> >   Regards,
> > Matthew Knill
> >   _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
>   _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Certificate authority files missing

[Michael K. <mic...@ip...>]

Sorry Lonnie

Here is the error Im getting after an Asterisk reload:

[Feb  4 17:13:48] ERROR[17736]: tcptls.c:524 __ssl_setup: TLS/SSL CA file(/mnt/kd/ssl/sip-tls/keys/ca.crt)/path() error
[Feb  4 17:13:48] ERROR[17736]: tcptls.c:126 write_openssl_error_to_log: 23216157824768:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/mnt/kd/ssl/sip-tls/keys/ca.crt','r')
23216157824768:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
23216157824768:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:crypto/x509/by_file.c:199:

I tried the 'openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer’ and it seemed to show the correct info.

Strange!


Regards

Michael Knill



From: Lonnie Abelbeck <li...@lo...>
Date: Wednesday, 4 February 2026 at 6:23 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Certificate authority files missing

Hi Michael,

I have not seen and issues related to SIP-TLS certificates.

When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"

[cid:e6e...@au...]



The ACME, Let's Encrypt cert gets installed and the service is restarted.

You can test what is the issuer from the localhost shell

## HTTPS
$ openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -issuer
...
issuer=C = US, O = Let's Encrypt, CN = R12

## SIP-TLS
$ openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer
...
issuer=C = US, O = Let's Encrypt, CN = R12

$ ls -l /mnt/kd/ssl/sip-tls/keys/
total 8
-rw-r--r--    1 root     root          3620 Dec 21 01:18 server.crt
-rw-------    1 root     root          1679 Dec 21 01:18 server.key

There are no ca.crt or ca.key files since they are ACME, only self-signed needs those files.

What Asterisk error are you getting?

The SIP-TLS self-signed cert can be generated, but with warnings of overwriting the Let's Encrypt version.

Lonnie




> On Feb 2, 2026, at 8:02 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Team
>
> An email from my developer.
>
> Regards
> Michael Knill
>   From: Matthew Knill <mat...@ip...>
> Date: Tuesday, 3 February 2026 at 12:51 pm
> To: Michael Knill <mic...@ip...>
> Subject: Certificate authority files missing
>
> We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.
>   I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…
>   Regards,
> Matthew Knill
>   _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....



_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Certificate authority files missing

[Lonnie A. <li...@lo...>]

Hi Michael,

I have not seen and issues related to SIP-TLS certificates.

When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"

[Astlinux-users] Certificate authority files missing

[Michael K. <mic...@ip...>]

Hi Team

An email from my developer.


Regards

Michael Knill



From: Matthew Knill <mat...@ip...>
Date: Tuesday, 3 February 2026 at 12:51 pm
To: Michael Knill <mic...@ip...>
Subject: Certificate authority files missing

We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.

I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…

Regards,
Matthew Knill

Re: [Astlinux-users] Asterisk crash on ACME update

[Michael K. <mic...@ip...>]

Thanks Lonnie

Looks like its in the not care category.


Regards

Michael Knill



From: Lonnie Abelbeck <li...@lo...>
Date: Friday, 9 January 2026 at 4:11 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Asterisk crash on ACME update

Hi Michael,

It looks like the safe_asterisk restart occurred within 1 second, and is only an issue when the ACME cert is renewed (~60 days).

Updating to a newer Asterisk version appears to be the solution.

Lonnie



> On Jan 7, 2026, at 5:50 PM, Michael Knill <mic...@ip...> wrote:
>
> Seeing this on multiple systems when ACME deploys new certificates. Im using Astlinux version 1.5.1.1 with Asterisk 16.
> See attached log.
>
> From my research, I believe this is a bug in earlier versions of Asterisk with queue’s which I am targeting to update but just wondering how hard it would be to do an immediate restart rather than 'restart when convenient’ which should overcome the issue?
>
> Or I could just not care as Safe Asterisk restarts it anyway.
>
> Regards
>  Michael Knill
> Managing Director
>  D: +61 2 6189 1360
> P: +61 2 6140 4656
> E: mic...@ip...
> W: ipcsolutions.com.au
>   <image001.png>Smarter Business Communications
>   <Astlinux Crash ACME Update.txt>_______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....




_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Asterisk crash on ACME update

[Lonnie A. <li...@lo...>]

Hi Michael,

It looks like the safe_asterisk restart occurred within 1 second, and is only an issue when the ACME cert is renewed (~60 days).

Updating to a newer Asterisk version appears to be the solution.

Lonnie



> On Jan 7, 2026, at 5:50 PM, Michael Knill <mic...@ip...> wrote:
> 
> Seeing this on multiple systems when ACME deploys new certificates. Im using Astlinux version 1.5.1.1 with Asterisk 16.
> See attached log.
> 
> From my research, I believe this is a bug in earlier versions of Asterisk with queue’s which I am targeting to update but just wondering how hard it would be to do an immediate restart rather than 'restart when convenient’ which should overcome the issue?
> 
> Or I could just not care as Safe Asterisk restarts it anyway.
> 
> Regards
>  Michael Knill
> Managing Director
>  D: +61 2 6189 1360
> P: +61 2 6140 4656
> E: mic...@ip...
> W: ipcsolutions.com.au
>   <image001.png>Smarter Business Communications
>   <Astlinux Crash ACME Update.txt>_______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] Asterisk crash on ACME update

[Michael K. <mic...@ip...>]

Seeing this on multiple systems when ACME deploys new certificates. Im using Astlinux version 1.5.1.1 with Asterisk 16.
See attached log.

>From my research, I believe this is a bug in earlier versions of Asterisk with queue’s which I am targeting to update but just wondering how hard it would be to do an immediate restart rather than 'restart when convenient’ which should overcome the issue?


Or I could just not care as Safe Asterisk restarts it anyway.


Regards



Michael Knill

Managing Director



D: +61 2 6189 1360<tel:+61261891360>

P: +61 2 6140 4656<tel:+61261404656>

E: mic...@ip...<mailto:mic...@ip...>

W: ipcsolutions.com.au<https://ipcsolutions.com.au/>



 [Icon  Description automatically generated]

Smarter Business Communications

Re: [Astlinux-users] Lanner NCA-1510

[Lonnie A. <li...@lo...>]

> On Nov 17, 2025, at 6:12 PM, aut...@gm... wrote:
> 
> Thanks Lonnie, here is the output from when I try to install from a USB drive:APIC: Switch to symmetric I/O mode setup
> ------------[ cut here ]------------
> kernel BUG at arch/x86/kernel/apic/apic.c:1599!
> invalid opcode: 0000 [#1] PREEMPT SMP
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.241-cip64-astlinux #1
> Hardware name: Default string Default string/Default string, BIOS 5.13 02/06/2025

You do not have anything plugged into the M.2 slot, correct?

You can search the interwebs for "invalid opcode: 0000" and see similar results.  Often a hardware issue, possibly a BIOS issue.  I see the RAM is soldered on the NCA-1510 board.

I personally have never encountered this "invalid opcode: 0000" error before.

I suppose testing another Linux distro could be the next step to debug this.  Though I'm not sure what change could fix this for AstLinux.

Lonnie

Re: [Astlinux-users] Lanner NCA-1510

[<aut...@gm...>]

Thanks Lonnie, here is the output from when I try to install from a USB
drive:



Version 2.19.1266. Copyright (C) 2025 American Megatrends, Inc.
NCA-1510 BIOS V1.16(02/06/2025)
Press <Tab> or <DEL> to enter setup.Syslinux 6.03 (EFI; )
                                                         Copyright (C)
2011-2014

#######################################
#     AstLinux ISO UEFI Installer     #
#######################################

install)  Install Menu (default)


Loading /runnix/runnix... ok
Loading /runnix/runnix.img...ok
Linux version 5.10.241-cip64-astlinux (build@build)
(x86_64-unknown-linux-gnu-gcc (crosstool-NG 1.25.0) 9.4.0, GNU ld
(crosstool-NG 1.25.0) 2.35.1) #1 SMP PREEMPT Thu Oct 30 13:07:53 CDT 2025
Command line: BOOT_IMAGE=/runnix/runnix initrd=/runnix/runnix.img
root=/dev/ram0 ro init=/runnix runimg=auto libata.dma=3 rootdelay=8
console=ttyS0,115200n8
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000003e2dffff] usable
BIOS-e820: [mem 0x000000003e2e0000-0x000000003e2fffff] reserved
BIOS-e820: [mem 0x000000003e300000-0x00000000784bafff] usable
BIOS-e820: [mem 0x00000000784bb000-0x00000000784cafff] reserved
BIOS-e820: [mem 0x00000000784cb000-0x000000007d494fff] usable
BIOS-e820: [mem 0x000000007d495000-0x000000007df73fff] reserved
BIOS-e820: [mem 0x000000007df74000-0x000000007df83fff] ACPI data
BIOS-e820: [mem 0x000000007df84000-0x000000007e3b7fff] ACPI NVS
BIOS-e820: [mem 0x000000007e3b8000-0x000000007f33afff] reserved
BIOS-e820: [mem 0x000000007f33b000-0x000000007f7fffff] usable
BIOS-e820: [mem 0x000000007f800000-0x000000007fffffff] reserved
BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000027fffffff] usable
NX (Execute Disable) protection: active
extended physical RAM map:
reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
reserve setup_data: [mem 0x0000000000100000-0x000000003e2dffff] usable
reserve setup_data: [mem 0x000000003e2e0000-0x000000003e2fffff] reserved
reserve setup_data: [mem 0x000000003e300000-0x0000000077483017] usable
reserve setup_data: [mem 0x0000000077483018-0x0000000077496857] usable
reserve setup_data: [mem 0x0000000077496858-0x0000000077497017] usable
reserve setup_data: [mem 0x0000000077497018-0x00000000774aa857] usable
reserve setup_data: [mem 0x00000000774aa858-0x00000000774ab017] usable
reserve setup_data: [mem 0x00000000774ab018-0x00000000774be857] usable
reserve setup_data: [mem 0x00000000774be858-0x00000000774bf017] usable
reserve setup_data: [mem 0x00000000774bf018-0x00000000774d2857] usable
reserve setup_data: [mem 0x00000000774d2858-0x00000000784bafff] usable
reserve setup_data: [mem 0x00000000784bb000-0x00000000784cafff] reserved
reserve setup_data: [mem 0x00000000784cb000-0x000000007d494fff] usable
reserve setup_data: [mem 0x000000007d495000-0x000000007df73fff] reserved
reserve setup_data: [mem 0x000000007df74000-0x000000007df83fff] ACPI data
reserve setup_data: [mem 0x000000007df84000-0x000000007e3b7fff] ACPI NVS
reserve setup_data: [mem 0x000000007e3b8000-0x000000007f33afff] reserved
reserve setup_data: [mem 0x000000007f33b000-0x000000007f7fffff] usable
reserve setup_data: [mem 0x000000007f800000-0x000000007fffffff] reserved
reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved
reserve setup_data: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
reserve setup_data: [mem 0x0000000100000000-0x000000027fffffff] usable
efi: EFI v2.60 by American Megatrends
efi: ACPI 2.0=0x7df7c000 ACPI=0x7df7c000 TPMFinalLog=0x7e386000
SMBIOS=0x7f20e000 SMBIOS 3.0=0x7f20d000 ESRT=0x7c2d5d98 MEMATTR=0x7c1f0018
TPMEventLog=0x7df7a018
SMBIOS 3.0.0 present.
DMI: Default string Default string/Default string, BIOS 5.13 02/06/2025
tsc: Detected 1600.000 MHz processor
last_pfn = 0x280000 max_arch_pfn = 0x400000000
x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
last_pfn = 0x7f800 max_arch_pfn = 0x400000000
found SMP MP-table at [mem 0x000fcdf0-0x000fcdff]
esrt: Reserving ESRT space from 0x000000007c2d5d98 to 0x000000007c2d5dd0.
Using GB pages for direct mapping
Secure boot disabled
RAMDISK: [mem 0x774d3000-0x7799cfff]
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x000000007DF7C000 000024 (v02 ALASKA)
ACPI: XSDT 0x000000007DF7C098 0000B4 (v01 ALASKA A M I    01072009 AMI
 00010013)
ACPI: FACP 0x000000007DF80FD8 000114 (v06 ALASKA A M I    01072009 AMI
 00010013)
ACPI: DSDT 0x000000007DF7C1E0 004DF4 (v02 ALASKA A M I    01072009 INTL
20061109)
ACPI: FACS 0x000000007E3B6080 000040
ACPI: FPDT 0x000000007DF810F0 000044 (v01 ALASKA A M I    01072009 AMI
 00010013)
ACPI: FIDT 0x000000007DF81138 00009C (v01 ALASKA A M I    01072009 AMI
 00010013)
ACPI: MCFG 0x000000007DF811D8 00003C (v01 ALASKA A M I    01072009 MSFT
00000097)
ACPI: WDAT 0x000000007DF81218 0001AC (v01 ALASKA A M I    01072009 MSFT
00010013)
ACPI: APIC 0x000000007DF813C8 000068 (v04 INTEL  TIANO    00000001 MSFT
00000000)
ACPI: BDAT 0x000000007DF81430 000030 (v01                 00000000
 00000000)
ACPI: HPET 0x000000007DF81460 000038 (v01 ALASKA A M I    00000001 MSFT
01000013)
ACPI: UEFI 0x000000007DF81498 000042 (v01 ALASKA A M I    00000002
 01000013)
ACPI: SSDT 0x000000007DF814E0 001901 (v02 PmRef  CpuPm    00003000 INTL
20061109)
ACPI: DMAR 0x000000007DF82DE8 000070 (v01 INTEL  BDW      00000001 INTL
00000001)
ACPI: SPCR 0x000000007DF82E58 000050 (v02 A M I  APTIO V  01072009 AMI.
0005000D)
ACPI: TPM2 0x000000007DF82EA8 000034 (v03 ALASKA A M I    00000001 AMI
 00000000)
ACPI: HEST 0x000000007DF82EE0 0000A8 (v01 INTEL  VND      00000001 INTL
00000001)
ACPI: BERT 0x000000007DF82F88 000030 (v01 INTEL  VND      00000001 INTL
00000001)
ACPI: ERST 0x000000007DF82FB8 000230 (v01 INTEL  VND      00000001 INTL
00000001)
ACPI: EINJ 0x000000007DF831E8 000150 (v01 INTEL  VND      00000001 INTL
00000001)
ACPI: WSMT 0x000000007DF83338 000028 (v01 ALASKA A M I    01072009 AMI
 00010013)
ACPI: Reserving FACP table memory at [mem 0x7df80fd8-0x7df810eb]
ACPI: Reserving DSDT table memory at [mem 0x7df7c1e0-0x7df80fd3]
ACPI: Reserving FACS table memory at [mem 0x7e3b6080-0x7e3b60bf]
ACPI: Reserving FPDT table memory at [mem 0x7df810f0-0x7df81133]
ACPI: Reserving FIDT table memory at [mem 0x7df81138-0x7df811d3]
ACPI: Reserving MCFG table memory at [mem 0x7df811d8-0x7df81213]
ACPI: Reserving WDAT table memory at [mem 0x7df81218-0x7df813c3]
ACPI: Reserving APIC table memory at [mem 0x7df813c8-0x7df8142f]
ACPI: Reserving BDAT table memory at [mem 0x7df81430-0x7df8145f]
ACPI: Reserving HPET table memory at [mem 0x7df81460-0x7df81497]
ACPI: Reserving UEFI table memory at [mem 0x7df81498-0x7df814d9]
ACPI: Reserving SSDT table memory at [mem 0x7df814e0-0x7df82de0]
ACPI: Reserving DMAR table memory at [mem 0x7df82de8-0x7df82e57]
ACPI: Reserving SPCR table memory at [mem 0x7df82e58-0x7df82ea7]
ACPI: Reserving TPM2 table memory at [mem 0x7df82ea8-0x7df82edb]
ACPI: Reserving HEST table memory at [mem 0x7df82ee0-0x7df82f87]
ACPI: Reserving BERT table memory at [mem 0x7df82f88-0x7df82fb7]
ACPI: Reserving ERST table memory at [mem 0x7df82fb8-0x7df831e7]
ACPI: Reserving EINJ table memory at [mem 0x7df831e8-0x7df83337]
ACPI: Reserving WSMT table memory at [mem 0x7df83338-0x7df8335f]
Zone ranges:
  DMA      [mem 0x0000000000001000-0x0000000000ffffff]
  DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
  Normal   [mem 0x0000000100000000-0x000000027fffffff]
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x0000000000001000-0x000000000009ffff]
  node   0: [mem 0x0000000000100000-0x000000003e2dffff]
  node   0: [mem 0x000000003e300000-0x00000000784bafff]
  node   0: [mem 0x00000000784cb000-0x000000007d494fff]
  node   0: [mem 0x000000007f33b000-0x000000007f7fffff]
  node   0: [mem 0x0000000100000000-0x000000027fffffff]
Initmem setup node 0 [mem 0x0000000000001000-0x000000027fffffff]
On node 0, zone DMA: 1 pages in unavailable ranges
On node 0, zone DMA: 96 pages in unavailable ranges
On node 0, zone DMA32: 32 pages in unavailable ranges
On node 0, zone DMA32: 16 pages in unavailable ranges
On node 0, zone DMA32: 7846 pages in unavailable ranges
On node 0, zone Normal: 2048 pages in unavailable ranges
ACPI: PM-Timer IO Port: 0x1808
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
ACPI: SPCR: console: uart,io,0x3f8,115200
TSC deadline timer available
smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[mem 0x80000000-0xdfffffff] available for PCI devices
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 1910969940391419 ns
setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
percpu: Embedded 44 pages/cpu s148120 r0 d32104 u1048576
Built 1 zonelists, mobility grouping on.  Total pages: 2058487
Kernel command line: BOOT_IMAGE=/runnix/runnix initrd=/runnix/runnix.img
root=/dev/ram0 ro init=/runnix runimg=auto libata.dma=3 rootdelay=8
console=ttyS0,115200n8
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
mem auto-init: stack:off, heap alloc:off, heap free:off
Memory: 8115596K/8348452K available (8193K kernel code, 592K rwdata, 1308K
rodata, 932K init, 456K bss, 232600K reserved, 0K cma-reserved)
rcu: Preemptible hierarchical RCU implementation.
rcu:    RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
        Trampoline variant of Tasks RCU enabled.
rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
NR_IRQS: 4352, nr_irqs: 440, preallocated irqs: 16
random: crng init done
Console: colour dummy device 80x25
printk: console [ttyS0] enabled
ACPI: Core revision 20200925
clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
79635855245 ns
APIC: Switch to symmetric I/O mode setup
------------[ cut here ]------------
kernel BUG at arch/x86/kernel/apic/apic.c:1599!
invalid opcode: 0000 [#1] PREEMPT SMP
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.241-cip64-astlinux #1
Hardware name: Default string Default string/Default string, BIOS 5.13
02/06/2025
RIP: 0010:0xffffffff8102a95b
Code: bf f0 00 00 00 e8 c7 fc ff ff bf f0 00 00 00 80 e4 fe 89 c6 e8 c2 fc
ff ff 48 8b 05 cf 2e b1 00 ff 90 a0 00 00 00 85 c0 75 02 <0f> 0b 48 8b 05
bc 2e b1 00 41 bd 00 02 00 00 ff 90 b0 00 00 00 bf
RSP: 0000:ffffffff81c03e78 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000fffffdff
RDX: 0000000000000000 RSI: 00000000fffffeff RDI: 0000000000000020
RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000fffffdff
R10: ffffffff81c03d38 R11: ffffffff81c03d30 R12: 000000000000008f
R13: ffffffff81d4f0a0 R14: 000000000000008f R15: 0000000078210e98
FS:  0000000000000000(0000) GS:ffff88827fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88827ffff000 CR3: 0000000003c0a000 CR4: 00000000000000b0
Call Trace:
 ? 0xffffffff814f140c
 ? 0xffffffff81cda219
 ? 0xffffffff81cce87a
 ? 0xffffffff81cc7d8b
 ? 0xffffffff81000111
---[ end trace 0e7f5b15690cd53c ]---
RIP: 0010:0xffffffff8102a95b
Code: bf f0 00 00 00 e8 c7 fc ff ff bf f0 00 00 00 80 e4 fe 89 c6 e8 c2 fc
ff ff 48 8b 05 cf 2e b1 00 ff 90 a0 00 00 00 85 c0 75 02 <0f> 0b 48 8b 05
bc 2e b1 00 41 bd 00 02 00 00 ff 90 b0 00 00 00 bf
RSP: 0000:ffffffff81c03e78 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000fffffdff
RDX: 0000000000000000 RSI: 00000000fffffeff RDI: 0000000000000020
RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000fffffdff
R10: ffffffff81c03d38 R11: ffffffff81c03d30 R12: 000000000000008f
R13: ffffffff81d4f0a0 R14: 000000000000008f R15: 0000000078210e98
FS:  0000000000000000(0000) GS:ffff88827fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88827ffff000 CR3: 0000000003c0a000 CR4: 00000000000000b0
Kernel panic - not syncing: Attempted to kill the idle task!
---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---

Re: [Astlinux-users] Lanner NCA-1510

[Lonnie A. <li...@lo...>]

> On Nov 16, 2025, at 12:47 AM, aut...@gm... wrote:
> 
> The kernel panic happens after I've booted from the USB drive and started the installation process.  The install just stops after a few seconds.  The target drive is untouched, as far as I can tell.
> 
> Would it be helpful to see the console output?

That would help to give context.

I'm wondering if the kernel is actually booting or not, possibly the creation of the bootable USB drive is the issue.

It could be a BIOS configuration issue as well.  Without any context it is hard to diagnose.


PS: Another thought, you mentioned placing a SSD into the M.2 Mini-PCIe slot, that could be causing an issue since that is only made for a WiFi card.

For the Lanner NCA-1510 with AstLinux, you need either the optional 2.5" SATA cable with SSD or install to and run off a USB boot drive [1] [2].

Lonnie

[1] Example: SAMSUNG FIT Plus 3.1 USB Flash Drive, 128GB

[2] https://doc.astlinux-project.org/userdoc:boot-usb-storage

Re: [Astlinux-users] Lanner NCA-1510

[Lonnie A. <li...@lo...>]

> On Nov 16, 2025, at 12:47 AM, aut...@gm... wrote:
> 
> The kernel panic happens after I've booted from the USB drive and started the installation process.  The install just stops after a few seconds.  The target drive is untouched, as far as I can tell.
> 
> Would it be helpful to see the console output?

That would help to give context.

I'm wondering if the kernel is actually booting or not, possibly the creation of the bootable USB drive is the issue.

It could be a BIOS configuration issue as well.  Without any context it is hard to diagnose.

Lonnie