Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael K. <mic...@ip...> - 2018-08-02 21:23:00
|
Awesome thanks Lonnie and Michael for this. Very excited.
PS I did win the large customer so I will be putting the Qotom Q530G6 into production (fingers crossed).
I will need to test out VRRP before I deploy it though so this will have to happen later. I think we should include a sync script with the VRRP Doco as its pretty pointless without it.
Its easy to rsync the config files but the database is a little harder. I do have a script to do it though.
So maybe the sync could be this process all done from the backup server:
1) Rsync all /mnt/kd files from the primary with some exclusions e.g. gui.network.conf, keepalived.conf and probably some others
2) Extract database contents from primary
3) Stop Asterisk
4) Vacuum database directly with SQLite
5) Write in database contents
6) Start Asterisk
Theoretically, pretty much all the configuration except for network parameters should be identical. Asterisk will use the virtual address for everything.
What do you think?
Regards
Michael Knill
On 3/8/18, 2:00 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Announcing Pre-Release Version: astlinux-1.3-3829-2f4ee0
The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.
-- Linux Kernel 3.16.57, security and bug fixes.
-- Asterisk 13 version bump to 13.22.0
New Documentation Topics:
VRRP High Availability Daemon (keepalived) -- https://doc.astlinux-project.org/userdoc:tt_high_availability
Qotom Q530G6 Core i3-6100U Fanless Appliance -- https://doc.astlinux-project.org/userdoc:board_qotom_q530g6
Linode KVM -- https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode
Updated Documentation Topics:
WAN Failover -- https://doc.astlinux-project.org/userdoc:tt_wan_failover#example4g_lte_modem_failover
These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project.
The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...
AstLinux Project -> Development
https://www.astlinux-project.org/dev.html
While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems.
If you should come across an issue, please report back here.
AstLinux Team
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2018-08-02 16:00:29
|
Announcing Pre-Release Version: astlinux-1.3-3829-2f4ee0 The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 3.16.57, security and bug fixes. -- Asterisk 13 version bump to 13.22.0 New Documentation Topics: VRRP High Availability Daemon (keepalived) -- https://doc.astlinux-project.org/userdoc:tt_high_availability Qotom Q530G6 Core i3-6100U Fanless Appliance -- https://doc.astlinux-project.org/userdoc:board_qotom_q530g6 Linode KVM -- https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode Updated Documentation Topics: WAN Failover -- https://doc.astlinux-project.org/userdoc:tt_wan_failover#example4g_lte_modem_failover These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2018-07-05 14:08:29
|
Announcing Pre-Release Version: astlinux-1.3-3800-b752f5 The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 3.16.57, security and bug fixes. -- Asterisk 13 version bump to 13.21.1 New Documentation Topics: Linode KVM -- https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode Updated Documentation Topics: WAN Failover -- https://doc.astlinux-project.org/userdoc:tt_wan_failover#example4g_lte_modem_failover These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2018-05-24 22:31:18
|
Announcing AstLinux Release: 1.3.3 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.3.3 Highlights: * Asterisk Versions: 11.25.3, 13.20.0 * Upgrade to Linux Kernel 3.16.54, including the RUNNIX bootloader, security and bug fixes * Added DNS-TLS support, via new getdns/stubby package * New command "system-vendor" to identify common hardware, also displayed in the web interface Status Tab * Zabbix upgrade adds TLS encryption support, now requires a Zabbix server with version 3.0 or greater * Fossil package, major upgrade, adds numerous enhancements to the look and feel of the web interface Fossil tab * util-linux package, major upgrade, providing common system commands * Web Interface enhancements and package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.3/docs/ChangeLog.txt All users are encouraged to upgrade. AstLinux Team |
|
From: David K. <da...@ke...> - 2018-05-18 01:39:30
|
Ah, ok did not know that. That would be worth testing to see if my UPS works with that. David On Thu, May 17, 2018 at 8:45 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Now if the UPS has not drained itself completely before power comes > back, the power never goes out, so AstLinux never comes back up. > > > That is what this option (when enabled) in the Network tab is for > -- > Kill Power on the UPS after a Powerfail Shutdown: [enabled] > -- > > It may depend on your UPS to properly come alive when the line power is > restored. > > Lonnie > > > > > On May 17, 2018, at 7:14 PM, David Kerr <Da...@Ke...> wrote: > > > > So, on the topic of shutdown.... The problem is that if AstLinux shuts > down, there is no way to bring it back up again remotely... at least not > that I know of. I have to physically go to the box, pull the power and > plug it back in again (or press a reset switch). Now if the UPS has not > drained itself completely before power comes back, the power never goes > out, so AstLinux never comes back up. > > > > So I think what I want is to let AstLinux keep running until the UPS > dies completely. It is ungraceful, but it is unlikely to cause much harm. > A fsck run at reboot will probably occur. > > > > Reading up on upsmon I think I have two options. In upsmon.conf I could > change NOTIFYFLAG LOBATT to just syslog and not exec the NOTIFYCMD > script... which is where I suspect the shutdown is triggered (I've not > checked that though). Or I think I could set MINSUPPLIES to 0 (zero) which > tells upsmon that it is acceptable to have less than one UPS available. > > > > I've not tested either of these yet, but thought I would post here and > get reactions. > > > > David. > > > > > > > > > > > > On Thu, May 17, 2018 at 11:01 AM, Michael Keuter <li...@mk...> > wrote: > > > > > Am 17.05.2018 um 16:50 schrieb Michael Keuter <li...@mk... > >: > > > > > >> > > >> Am 17.05.2018 um 16:31 schrieb Michael Keuter <li...@mk... > >: > > >> > > >> > > >>> Am 17.05.2018 um 16:12 schrieb David Kerr <da...@ke...>: > > >>> > > >>> Starting a thread among developers on this topic to record some > observations. Now on day two of no power or internet and having got WAN > failover working yesterday I have some observations... > > >> > > >> Hopefully the power gets back soon … > > >> > > >>> Status page still shows my eth0 IPv4 address, which is > 192.168.100.10 issued by my cable modem as external network down. > > >>> > > >>> WAN failover status shows 192.168.100.1 as (bogus) primary gateway > and 172.20.10.1 as accurate. But what is needed is external IP address. > > >>> > > >>> My ddclient uses eth0 as the external IPv4 address. So my dynamic > DNS updates are all failing/bogus. Either I change to use an external site > to determine my IP, or I do something in WAN failover script to change what > ddclient does. Any thoughts as to best approach? I want something > automatic that will work whether using primary or failover. > > >> > > >> Some of that stuff can be automated with the optional Action script: > > >> https://doc.astlinux.org/userdoc:tt_wan_failover# > action_script_optional > > >> > > >>> I turn off my generator overnight and run network from a large UPS. > According to syslog Astlinux decided to shutdown at 6am when upsmon > determined low battery. I think it was at 20% left, but at that level I > still have 90-120 minutes of runtime left. Is there a setting to change > when Astlinux does the shutdown? > > >> > > >> I guess in "/etc/ups/upsmon.conf" (but no idea which is the right > parameter). You can create your own file in "/mnt/kd/". > > > > > > I think I was wrong: https://networkupstools.org/ > docs/man/ups.conf.html > > > Pay attention to the "ignorelb", "default.<variable>" and > "override.<variable>" parameters. > > > > > > Checkout this command in CLI to get the values: > > > > > > ---- > > > upsc ups@localhost > > > battery.charge: 100 > > > battery.charge.low: 10 > > > battery.charge.warning: 50 > > > ... > > > ... > > > ---- > > > > Update: There's even more :-): > > > > upsrw ups@localhost > > [battery.charge.low] > > Remaining battery level when UPS switches to LB (percent) > > Type: STRING > > Maximum length: 10 > > Value: 10 > > > > You can also set variables with "upsrw", e.g. in "/mnt/kd/rc.elocal". > You need the username and password from "/etc/ups/upsd.users". > > > > Michael > > > > http://www.mksolutions.info > > > > > > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2018-05-18 00:45:16
|
> Now if the UPS has not drained itself completely before power comes back, the power never goes out, so AstLinux never comes back up. That is what this option (when enabled) in the Network tab is for -- Kill Power on the UPS after a Powerfail Shutdown: [enabled] -- It may depend on your UPS to properly come alive when the line power is restored. Lonnie > On May 17, 2018, at 7:14 PM, David Kerr <Da...@Ke...> wrote: > > So, on the topic of shutdown.... The problem is that if AstLinux shuts down, there is no way to bring it back up again remotely... at least not that I know of. I have to physically go to the box, pull the power and plug it back in again (or press a reset switch). Now if the UPS has not drained itself completely before power comes back, the power never goes out, so AstLinux never comes back up. > > So I think what I want is to let AstLinux keep running until the UPS dies completely. It is ungraceful, but it is unlikely to cause much harm. A fsck run at reboot will probably occur. > > Reading up on upsmon I think I have two options. In upsmon.conf I could change NOTIFYFLAG LOBATT to just syslog and not exec the NOTIFYCMD script... which is where I suspect the shutdown is triggered (I've not checked that though). Or I think I could set MINSUPPLIES to 0 (zero) which tells upsmon that it is acceptable to have less than one UPS available. > > I've not tested either of these yet, but thought I would post here and get reactions. > > David. > > > > > > On Thu, May 17, 2018 at 11:01 AM, Michael Keuter <li...@mk...> wrote: > > > Am 17.05.2018 um 16:50 schrieb Michael Keuter <li...@mk...>: > > > >> > >> Am 17.05.2018 um 16:31 schrieb Michael Keuter <li...@mk...>: > >> > >> > >>> Am 17.05.2018 um 16:12 schrieb David Kerr <da...@ke...>: > >>> > >>> Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... > >> > >> Hopefully the power gets back soon … > >> > >>> Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. > >>> > >>> WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. > >>> > >>> My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. > >> > >> Some of that stuff can be automated with the optional Action script: > >> https://doc.astlinux.org/userdoc:tt_wan_failover#action_script_optional > >> > >>> I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? > >> > >> I guess in "/etc/ups/upsmon.conf" (but no idea which is the right parameter). You can create your own file in "/mnt/kd/". > > > > I think I was wrong: https://networkupstools.org/docs/man/ups.conf.html > > Pay attention to the "ignorelb", "default.<variable>" and "override.<variable>" parameters. > > > > Checkout this command in CLI to get the values: > > > > ---- > > upsc ups@localhost > > battery.charge: 100 > > battery.charge.low: 10 > > battery.charge.warning: 50 > > ... > > ... > > ---- > > Update: There's even more :-): > > upsrw ups@localhost > [battery.charge.low] > Remaining battery level when UPS switches to LB (percent) > Type: STRING > Maximum length: 10 > Value: 10 > > You can also set variables with "upsrw", e.g. in "/mnt/kd/rc.elocal". You need the username and password from "/etc/ups/upsd.users". > > Michael > > http://www.mksolutions.info > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: David K. <da...@ke...> - 2018-05-18 00:15:21
|
So, on the topic of shutdown.... The problem is that if AstLinux shuts down, there is no way to bring it back up again remotely... at least not that I know of. I have to physically go to the box, pull the power and plug it back in again (or press a reset switch). Now if the UPS has not drained itself completely before power comes back, the power never goes out, so AstLinux never comes back up. So I think what I want is to let AstLinux keep running until the UPS dies completely. It is ungraceful, but it is unlikely to cause much harm. A fsck run at reboot will probably occur. Reading up on upsmon I think I have two options. In upsmon.conf I could change NOTIFYFLAG LOBATT to just syslog and not exec the NOTIFYCMD script... which is where I suspect the shutdown is triggered (I've not checked that though). Or I think I could set MINSUPPLIES to 0 (zero) which tells upsmon that it is acceptable to have less than one UPS available. I've not tested either of these yet, but thought I would post here and get reactions. David. On Thu, May 17, 2018 at 11:01 AM, Michael Keuter <li...@mk...> wrote: > > > Am 17.05.2018 um 16:50 schrieb Michael Keuter <li...@mk...>: > > > >> > >> Am 17.05.2018 um 16:31 schrieb Michael Keuter <li...@mk...>: > >> > >> > >>> Am 17.05.2018 um 16:12 schrieb David Kerr <da...@ke...>: > >>> > >>> Starting a thread among developers on this topic to record some > observations. Now on day two of no power or internet and having got WAN > failover working yesterday I have some observations... > >> > >> Hopefully the power gets back soon … > >> > >>> Status page still shows my eth0 IPv4 address, which is 192.168.100.10 > issued by my cable modem as external network down. > >>> > >>> WAN failover status shows 192.168.100.1 as (bogus) primary gateway and > 172.20.10.1 as accurate. But what is needed is external IP address. > >>> > >>> My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS > updates are all failing/bogus. Either I change to use an external site to > determine my IP, or I do something in WAN failover script to change what > ddclient does. Any thoughts as to best approach? I want something > automatic that will work whether using primary or failover. > >> > >> Some of that stuff can be automated with the optional Action script: > >> https://doc.astlinux.org/userdoc:tt_wan_failover#action_script_optional > >> > >>> I turn off my generator overnight and run network from a large UPS. > According to syslog Astlinux decided to shutdown at 6am when upsmon > determined low battery. I think it was at 20% left, but at that level I > still have 90-120 minutes of runtime left. Is there a setting to change > when Astlinux does the shutdown? > >> > >> I guess in "/etc/ups/upsmon.conf" (but no idea which is the right > parameter). You can create your own file in "/mnt/kd/". > > > > I think I was wrong: https://networkupstools.org/docs/man/ups.conf.html > > Pay attention to the "ignorelb", "default.<variable>" and > "override.<variable>" parameters. > > > > Checkout this command in CLI to get the values: > > > > ---- > > upsc ups@localhost > > battery.charge: 100 > > battery.charge.low: 10 > > battery.charge.warning: 50 > > ... > > ... > > ---- > > Update: There's even more :-): > > upsrw ups@localhost > [battery.charge.low] > Remaining battery level when UPS switches to LB (percent) > Type: STRING > Maximum length: 10 > Value: 10 > > You can also set variables with "upsrw", e.g. in "/mnt/kd/rc.elocal". You > need the username and password from "/etc/ups/upsd.users". > > Michael > > http://www.mksolutions.info > > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2018-05-17 21:01:23
|
David, Thanks for the explanation, more comments inline ... > On May 17, 2018, at 3:09 PM, David Kerr <Da...@Ke...> wrote: > > Lonnie, > My cable modem has an internal LAN address of 192.168.100.1. If there is no external internet connection then the modem issues a IP address in the 192.168.100.x range, and itself as the gateway, by DHCP to the internal client. Thus the internal client has a valid private network address and can access the modem status page. If there is an external connection then the modem issues the IP address and gateway as provided by the cable company through DHCP. It retains 192.168.100.1 as its own address so if that range is routed through eth0 then clients can still access the modem's status page. > > So, when I say that the WAN failover status primary gateway is bogus then what I mean is that it is no longer a valid gateway from my ISP, but rather just the modem itself which has no external connection. > > Some observations... 1) when the modem issues a 192.168.100.x address it provides a lease time of 30 seconds. This results in 2 lines into syslog from udhcpc every 30 seconds. Yuk. Noisy yes, but working as designed, and I understand why the lease is so short when "offline" waiting to establish a public lease. > 2) monitoring for gateway changing to a specific IP (in my case 192.168.100.1) would be another way to detect that primary WAN link had failed. For your current case, but there are many different situations when the Primary WAN can fail ... failed at your ISP's node, a cable cut beyond your head-end, etc... AstLinux's heuristic is to fping a couple IPv4's and switch then they all fail, return back when the fping's succeed. In my past testing on my main box, the only annoying thing when WAN Failover is active all the time is if a very short outage (say 30 seconds) causes a switch which can be 2 minutes or so before it returns back to the Primary ... in those special cases I would prefer it would not switch, but until we have a heuristic to predict the future :-) it is what it is. Lonnie > > David. > > > > > > On Thu, May 17, 2018 at 11:33 AM, Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > First, a 4G/LTE Modem in bridge mode behaves just like a cable modem, which is ideal with AstLinux ... the WiFi client to iPhone tethering method leaves the public IP address unknown to the local interface ... workable but not ideal. I'm not sure what you mean that "WAN failover status shows 192.168.100.1 as (bogus) primary gateway" > > > My ddclient uses eth0 as the external IPv4 address. > > The simplest is to use a public server to determine your IPv4 address when using WAN Failover. > > or "service dynamicdns stop" when switching to failover if you don't want to expend the extra traffic on updating your dynamic DNS. > > > > Is there a setting to change when Astlinux does the shutdown? > > I seem to recall that when the UPS goes to a "critical" level then AstLinux does a shutdown, the accuracy of that number can vary a lot per the age of the battery. If you want to ride the UPS down you could just "service ups stop" temporally. > > The /etc/ups/*.conf files are auto-generated unless if a matching /mnt/kd/ups/*.conf file exists. Samples are in /stat/etc/ups/ > > Saying that, what Michael suggested is good info as well, configuring the UPS itself. > > Finally, if you really want your AstLinux box to power-down before the UPS powers off with safety, any margin less than 10-20% will be too low as the UPS battery ages. > > > Lonnie > > > > > > On May 17, 2018, at 9:12 AM, David Kerr <Da...@Ke...> wrote: > > > > Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... > > > > Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. > > > > WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. > > > > My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. > > > > I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? > > > > Thoughts? > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: David K. <da...@ke...> - 2018-05-17 20:10:19
|
Lonnie, My cable modem has an internal LAN address of 192.168.100.1. If there is no external internet connection then the modem issues a IP address in the 192.168.100.x range, and itself as the gateway, by DHCP to the internal client. Thus the internal client has a valid private network address and can access the modem status page. If there is an external connection then the modem issues the IP address and gateway as provided by the cable company through DHCP. It retains 192.168.100.1 as its own address so if that range is routed through eth0 then clients can still access the modem's status page. So, when I say that the WAN failover status primary gateway is bogus then what I mean is that it is no longer a valid gateway from my ISP, but rather just the modem itself which has no external connection. Some observations... 1) when the modem issues a 192.168.100.x address it provides a lease time of 30 seconds. This results in 2 lines into syslog from udhcpc every 30 seconds. Yuk. 2) monitoring for gateway changing to a specific IP (in my case 192.168.100.1) would be another way to detect that primary WAN link had failed. David. On Thu, May 17, 2018 at 11:33 AM, Lonnie Abelbeck <li...@lo... > wrote: > Hi David, > > First, a 4G/LTE Modem in bridge mode behaves just like a cable modem, > which is ideal with AstLinux ... the WiFi client to iPhone tethering method > leaves the public IP address unknown to the local interface ... workable > but not ideal. I'm not sure what you mean that "WAN failover status shows > 192.168.100.1 as (bogus) primary gateway" > > > My ddclient uses eth0 as the external IPv4 address. > > The simplest is to use a public server to determine your IPv4 address when > using WAN Failover. > > or "service dynamicdns stop" when switching to failover if you don't want > to expend the extra traffic on updating your dynamic DNS. > > > > Is there a setting to change when Astlinux does the shutdown? > > I seem to recall that when the UPS goes to a "critical" level then > AstLinux does a shutdown, the accuracy of that number can vary a lot per > the age of the battery. If you want to ride the UPS down you could just > "service ups stop" temporally. > > The /etc/ups/*.conf files are auto-generated unless if a matching > /mnt/kd/ups/*.conf file exists. Samples are in /stat/etc/ups/ > > Saying that, what Michael suggested is good info as well, configuring the > UPS itself. > > Finally, if you really want your AstLinux box to power-down before the UPS > powers off with safety, any margin less than 10-20% will be too low as the > UPS battery ages. > > > Lonnie > > > > > > On May 17, 2018, at 9:12 AM, David Kerr <Da...@Ke...> wrote: > > > > Starting a thread among developers on this topic to record some > observations. Now on day two of no power or internet and having got WAN > failover working yesterday I have some observations... > > > > Status page still shows my eth0 IPv4 address, which is 192.168.100.10 > issued by my cable modem as external network down. > > > > WAN failover status shows 192.168.100.1 as (bogus) primary gateway and > 172.20.10.1 as accurate. But what is needed is external IP address. > > > > My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS > updates are all failing/bogus. Either I change to use an external site to > determine my IP, or I do something in WAN failover script to change what > ddclient does. Any thoughts as to best approach? I want something > automatic that will work whether using primary or failover. > > > > I turn off my generator overnight and run network from a large UPS. > According to syslog Astlinux decided to shutdown at 6am when upsmon > determined low battery. I think it was at 20% left, but at that level I > still have 90-120 minutes of runtime left. Is there a setting to change > when Astlinux does the shutdown? > > > > Thoughts? > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2018-05-17 15:33:20
|
Hi David, First, a 4G/LTE Modem in bridge mode behaves just like a cable modem, which is ideal with AstLinux ... the WiFi client to iPhone tethering method leaves the public IP address unknown to the local interface ... workable but not ideal. I'm not sure what you mean that "WAN failover status shows 192.168.100.1 as (bogus) primary gateway" > My ddclient uses eth0 as the external IPv4 address. The simplest is to use a public server to determine your IPv4 address when using WAN Failover. or "service dynamicdns stop" when switching to failover if you don't want to expend the extra traffic on updating your dynamic DNS. > Is there a setting to change when Astlinux does the shutdown? I seem to recall that when the UPS goes to a "critical" level then AstLinux does a shutdown, the accuracy of that number can vary a lot per the age of the battery. If you want to ride the UPS down you could just "service ups stop" temporally. The /etc/ups/*.conf files are auto-generated unless if a matching /mnt/kd/ups/*.conf file exists. Samples are in /stat/etc/ups/ Saying that, what Michael suggested is good info as well, configuring the UPS itself. Finally, if you really want your AstLinux box to power-down before the UPS powers off with safety, any margin less than 10-20% will be too low as the UPS battery ages. Lonnie > On May 17, 2018, at 9:12 AM, David Kerr <Da...@Ke...> wrote: > > Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... > > Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. > > WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. > > My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. > > I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? > > Thoughts? > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2018-05-17 15:01:30
|
> Am 17.05.2018 um 16:50 schrieb Michael Keuter <li...@mk...>: > >> >> Am 17.05.2018 um 16:31 schrieb Michael Keuter <li...@mk...>: >> >> >>> Am 17.05.2018 um 16:12 schrieb David Kerr <da...@ke...>: >>> >>> Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... >> >> Hopefully the power gets back soon … >> >>> Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. >>> >>> WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. >>> >>> My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. >> >> Some of that stuff can be automated with the optional Action script: >> https://doc.astlinux.org/userdoc:tt_wan_failover#action_script_optional >> >>> I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? >> >> I guess in "/etc/ups/upsmon.conf" (but no idea which is the right parameter). You can create your own file in "/mnt/kd/". > > I think I was wrong: https://networkupstools.org/docs/man/ups.conf.html > Pay attention to the "ignorelb", "default.<variable>" and "override.<variable>" parameters. > > Checkout this command in CLI to get the values: > > ---- > upsc ups@localhost > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 50 > ... > ... > ---- Update: There's even more :-): upsrw ups@localhost [battery.charge.low] Remaining battery level when UPS switches to LB (percent) Type: STRING Maximum length: 10 Value: 10 You can also set variables with "upsrw", e.g. in "/mnt/kd/rc.elocal". You need the username and password from "/etc/ups/upsd.users". Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2018-05-17 14:50:51
|
> Am 17.05.2018 um 16:31 schrieb Michael Keuter <li...@mk...>: > > >> Am 17.05.2018 um 16:12 schrieb David Kerr <da...@ke...>: >> >> Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... > > Hopefully the power gets back soon … > >> Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. >> >> WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. >> >> My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. > > Some of that stuff can be automated with the optional Action script: > https://doc.astlinux.org/userdoc:tt_wan_failover#action_script_optional > >> I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? > > I guess in "/etc/ups/upsmon.conf" (but no idea which is the right parameter). You can create your own file in "/mnt/kd/". I think I was wrong: https://networkupstools.org/docs/man/ups.conf.html Pay attention to the "ignorelb", "default.<variable>" and "override.<variable>" parameters. Checkout this command in CLI to get the values: ---- upsc ups@localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 ... ... ---- >> Thoughts? > > Michael Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2018-05-17 14:32:11
|
> Am 17.05.2018 um 16:12 schrieb David Kerr <da...@ke...>: > > Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... Hopefully the power gets back soon … > Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. > > WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. > > My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. Some of that stuff can be automated with the optional Action script: https://doc.astlinux.org/userdoc:tt_wan_failover#action_script_optional > I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? I guess in "/etc/ups/upsmon.conf" (but no idea which is the right parameter). You can create your own file in "/mnt/kd/". > Thoughts? Michael http://www.mksolutions.info |
|
From: David K. <da...@ke...> - 2018-05-17 14:12:59
|
Starting a thread among developers on this topic to record some observations. Now on day two of no power or internet and having got WAN failover working yesterday I have some observations... Status page still shows my eth0 IPv4 address, which is 192.168.100.10 issued by my cable modem as external network down. WAN failover status shows 192.168.100.1 as (bogus) primary gateway and 172.20.10.1 as accurate. But what is needed is external IP address. My ddclient uses eth0 as the external IPv4 address. So my dynamic DNS updates are all failing/bogus. Either I change to use an external site to determine my IP, or I do something in WAN failover script to change what ddclient does. Any thoughts as to best approach? I want something automatic that will work whether using primary or failover. I turn off my generator overnight and run network from a large UPS. According to syslog Astlinux decided to shutdown at 6am when upsmon determined low battery. I think it was at 20% left, but at that level I still have 90-120 minutes of runtime left. Is there a setting to change when Astlinux does the shutdown? Thoughts? |
|
From: Lonnie A. <li...@lo...> - 2018-04-27 16:21:41
|
Announcing Pre-Release Version: astlinux-1.3-3721-36d261 The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 3.16.54, security and bug fixes. -- getdns/stubby, new package, version 1.4.1/0.2.2, encrypts local DNS queries forwarded to upstream recursive DNS-TLS servers http://doc.astlinux-project.org/userdoc:tt_dns_tls_proxy -- zabbix, version bump to 3.0.14, adds TLS encryption support Note: Now requires a Zabbix server with version 3.0 or greater. -- system-vendor, new command to identify common hardware. -- Fossil, version bump to 2.5, adds numerous enhancements to the look and feel of the web interface. -- util-linux, major version bump to 2.28.2 -- Asterisk 13 version bump to 13.20.0 These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2018-03-27 18:36:45
|
Announcing Pre-Release Version: astlinux-1.3-3665-8d0097 The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 3.16.54, security and bug fixes. -- zabbix, version bump to 3.0.14, adds TLS encryption support Note: Now requires a Zabbix server with version 3.0 or greater. -- system-vendor, new command to identify common hardware. -- Fossil, version bump to 2.5, adds numerous enhancements to the look and feel of the web interface. -- util-linux, major version bump to 2.28.2 -- Asterisk 13 version bump to 13.20.0 These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2018-03-01 16:48:36
|
Announcing Pre-Release Version: astlinux-1.3-3622-e3aee4 The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 3.16.54, security and bug fixes. -- zabbix, version bump to 3.0.14, adds TLS encryption support Note: Now requires a Zabbix server with version 3.0 or greater. -- Asterisk 13 version bump to 13.19.2 These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development http://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2018-01-24 14:11:25
|
Announcing AstLinux Release: 1.3.2 More Info: AstLinux Project http://www.astlinux-project.org/ AstLinux 1.3.2 Highlights: • Asterisk Versions: 11.25.3, 13.18.5 • Upgrade to Linux Kernel 3.16.51, including the RUNNIX bootloader • Added WireGuard VPN support, an extremely simple yet fast and modern VPN • Command "acme-client" adds --deploy-hook "custom" which executes the script "/mnt/kd/acme-deploy-custom.script" • New command "empty" with similar functionality to "expect", allows scripting interactive sessions • Web Interface enhancements and package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.2/docs/ChangeLog.txt All users are encouraged to upgrade. AstLinux Team |
|
From: Michael K. <mic...@ip...> - 2018-01-22 19:23:06
|
Thanks Lonnie
Good to know.
Regards
Michael Knill
On 23/1/18, 4:25 am, "Lonnie Abelbeck" <li...@lo...> wrote:
On Jan 21, 2018, at 10:43 PM, Michael Knill <mic...@ip...> wrote:
> Hi Devs
>
> Found a bug with ipsec.php where a $ in the preshare key will not get written into /etc/psk.txt
> Simple workaround but it caught me out ☹
>
> Regards
> Michael Knill
Yes, shell special characters are not allowed (stripped) in the IPSEC_PSK_ASSOCIATIONS structure, that decision was make long-long ago before I was actively involved with AstLinux.
We do support shell special characters (properly escaped) in a few select cases, such as for these rc.conf variables:
--
PPPOEPASS
SMTP_PASS
DDPASS
UPS_MONITOR_PASS
--
But that solution does not easily translate to the IPSEC_PSK_ASSOCIATIONS case.
Though, I'm not aware of a "simple" workaround other than choosing a new password, possibly from the output of "openssl rand -base64 33"
Lonnie
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2018-01-22 17:25:16
|
On Jan 21, 2018, at 10:43 PM, Michael Knill <mic...@ip...> wrote: > Hi Devs > > Found a bug with ipsec.php where a $ in the preshare key will not get written into /etc/psk.txt > Simple workaround but it caught me out ☹ > > Regards > Michael Knill Yes, shell special characters are not allowed (stripped) in the IPSEC_PSK_ASSOCIATIONS structure, that decision was make long-long ago before I was actively involved with AstLinux. We do support shell special characters (properly escaped) in a few select cases, such as for these rc.conf variables: -- PPPOEPASS SMTP_PASS DDPASS UPS_MONITOR_PASS -- But that solution does not easily translate to the IPSEC_PSK_ASSOCIATIONS case. Though, I'm not aware of a "simple" workaround other than choosing a new password, possibly from the output of "openssl rand -base64 33" Lonnie |
|
From: Michael K. <mic...@ip...> - 2018-01-22 04:43:24
|
Hi Devs Found a bug with ipsec.php where a $ in the preshare key will not get written into /etc/psk.txt Simple workaround but it caught me out ☹ Regards Michael Knill |
|
From: Kordován S. <ko...@gm...> - 2018-01-17 12:45:25
|
Hello List, I have read some treads about the subject but I did not get answer to my question. I would like to add a new channel driver to asterisk. I am working on a modified chan_dongle channel driver for gsm modems (Huawei and SimCom). Can somebody send a howto? Regards, Szabolcs |
|
From: Josh A. <jm...@ho...> - 2018-01-11 23:21:26
|
No worries, thanks for helping me add the rootdelay! I'll have to switch to other hardware for this build I'm working on, but I'll keep the t5700 around if any other ideas emerge. ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Thursday, January 11, 2018 6:01 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports Hi Josh, I don't know what to tell you then, over all these years I have not seen such behavior. Possibly try a different HP t5700 thinclient if you can ? Lonnie On Jan 11, 2018, at 4:53 PM, Josh Alberts <jm...@ho...> wrote: > Hi Lonnie, > > Unfortunately, the problem remains even with the rootdelay=10. I know I successfully added the delay because I see a message "waiting 10 sec before mounting root device". > > Josh > > From: Lonnie Abelbeck <li...@lo...> > Sent: Thursday, January 11, 2018 9:53 AM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > Josh, > > Ignore the WiKi docs about externally mounting the USB drive, adding rootdelay=10 as described to the KCMD line in the .run.conf file should work for you. > > Lonnie > > > > On Jan 11, 2018, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: > > > Lonnie, > > > > I'm running this off the thinclient's internal flash drive, so unfortunately, it looks like this won't help me out. > > > > After going through the build process and upgrading, I can confirm that the changes I made don't cut out the error message I described. Even if it had, Michael's message makes me believe this wouldn't have solved my problem. > > > > From: Lonnie Abelbeck <li...@lo...> > > Sent: Thursday, January 11, 2018 8:48 AM > > To: AstLinux Developers Mailing List > > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > Hi Josh, > > > > Yes, if your flash storage is internally connected via USB then no rootdelay could explain what you are seeing. Here is a WiKi reference ... > > > > Boot via USB Flash Storage > > https://doc.astlinux-project.org/userdoc:boot-usb-storage userdoc:boot-usb-storage [AstLinux Documentation]<https://doc.astlinux-project.org/userdoc:boot-usb-storage> doc.astlinux-project.org For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > userdoc:boot-usb-storage [AstLinux Documentation] > doc.astlinux-project.org > For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > > > userdoc:boot-usb-storage [AstLinux Documentation] > > doc.astlinux-project.org > > For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > > > > > > Add rootdelay=10 as described to the KCMD line in the .run.conf file. If you can't remove the flash and mount it as described in the WiKi on a successful boot from the AstLinux CLI ... > > -- > > mount -o rw,remount /oldroot/cdrom > > ## edit the /oldroot/cdrom/os/astlinux-nnnnnn.run.conf file > > mount -o ro,remount /oldroot/cdrom > > -- > > > > Or since you build your own "geni586" image, you could edit on your build system "project/astlinux/board/geni586/runnix.conf" file and without a clean build you can simply > > -- > > ./scripts/build > > -- > > and install the new image. > > > > Lonnie > > > > > > On Jan 11, 2018, at 7:10 AM, Josh Alberts <jm...@ho...> wrote: > > > > > That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? > > > > > > > > > From: Michael Keuter <li...@mk...> > > > Sent: Thursday, January 11, 2018 5:37 AM > > > To: AstLinux Developers Mailing List > > > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > > > > > > > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > > > > > > > Hello again, > > > > > > > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > > > > > > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > > > > > > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > > > > > > > project/runnix-iso/geni586/linux.config > > > > project/runnix/geni586/linux.config > > > > project/astlinux/geni586/linux-smp.config > > > > > > > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > > > > > > > Josh > > > > > > Hi Josh, > > > > > > I don't think that has something to do with the PS/2 ports. > > > I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: > > > > > > ---- > > > [ 0.448889] usbcore: registered new interface driver ums-sddr55 > > > [ 0.449653] usbcore: registered new interface driver ums-usbat > > > [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. > > > [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 > > > [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA > > > [ 0.481907] ata1.00: configured for PIO4 > > > [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 > > > ---- > > > > > > Maybe your storage medium has temporary issues … > > > > > > Michael > > > > > > http://www.mksolutions.info Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2018-01-11 23:02:04
|
Hi Josh, I don't know what to tell you then, over all these years I have not seen such behavior. Possibly try a different HP t5700 thinclient if you can ? Lonnie On Jan 11, 2018, at 4:53 PM, Josh Alberts <jm...@ho...> wrote: > Hi Lonnie, > > Unfortunately, the problem remains even with the rootdelay=10. I know I successfully added the delay because I see a message "waiting 10 sec before mounting root device". > > Josh > > From: Lonnie Abelbeck <li...@lo...> > Sent: Thursday, January 11, 2018 9:53 AM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > Josh, > > Ignore the WiKi docs about externally mounting the USB drive, adding rootdelay=10 as described to the KCMD line in the .run.conf file should work for you. > > Lonnie > > > > On Jan 11, 2018, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: > > > Lonnie, > > > > I'm running this off the thinclient's internal flash drive, so unfortunately, it looks like this won't help me out. > > > > After going through the build process and upgrading, I can confirm that the changes I made don't cut out the error message I described. Even if it had, Michael's message makes me believe this wouldn't have solved my problem. > > > > From: Lonnie Abelbeck <li...@lo...> > > Sent: Thursday, January 11, 2018 8:48 AM > > To: AstLinux Developers Mailing List > > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > Hi Josh, > > > > Yes, if your flash storage is internally connected via USB then no rootdelay could explain what you are seeing. Here is a WiKi reference ... > > > > Boot via USB Flash Storage > > https://doc.astlinux-project.org/userdoc:boot-usb-storage > userdoc:boot-usb-storage [AstLinux Documentation] > doc.astlinux-project.org > For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > > > userdoc:boot-usb-storage [AstLinux Documentation] > > doc.astlinux-project.org > > For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > > > > > > Add rootdelay=10 as described to the KCMD line in the .run.conf file. If you can't remove the flash and mount it as described in the WiKi on a successful boot from the AstLinux CLI ... > > -- > > mount -o rw,remount /oldroot/cdrom > > ## edit the /oldroot/cdrom/os/astlinux-nnnnnn.run.conf file > > mount -o ro,remount /oldroot/cdrom > > -- > > > > Or since you build your own "geni586" image, you could edit on your build system "project/astlinux/board/geni586/runnix.conf" file and without a clean build you can simply > > -- > > ./scripts/build > > -- > > and install the new image. > > > > Lonnie > > > > > > On Jan 11, 2018, at 7:10 AM, Josh Alberts <jm...@ho...> wrote: > > > > > That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? > > > > > > > > > From: Michael Keuter <li...@mk...> > > > Sent: Thursday, January 11, 2018 5:37 AM > > > To: AstLinux Developers Mailing List > > > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > > > > > > > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > > > > > > > Hello again, > > > > > > > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > > > > > > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > > > > > > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > > > > > > > project/runnix-iso/geni586/linux.config > > > > project/runnix/geni586/linux.config > > > > project/astlinux/geni586/linux-smp.config > > > > > > > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > > > > > > > Josh > > > > > > Hi Josh, > > > > > > I don't think that has something to do with the PS/2 ports. > > > I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: > > > > > > ---- > > > [ 0.448889] usbcore: registered new interface driver ums-sddr55 > > > [ 0.449653] usbcore: registered new interface driver ums-usbat > > > [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. > > > [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 > > > [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA > > > [ 0.481907] ata1.00: configured for PIO4 > > > [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 > > > ---- > > > > > > Maybe your storage medium has temporary issues … > > > > > > Michael > > > > > > http://www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > > www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > www.mksolutions.info > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > > Astlinux-devel mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Josh A. <jm...@ho...> - 2018-01-11 22:53:34
|
Hi Lonnie, Unfortunately, the problem remains even with the rootdelay=10. I know I successfully added the delay because I see a message "waiting 10 sec before mounting root device". Josh ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Thursday, January 11, 2018 9:53 AM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports Josh, Ignore the WiKi docs about externally mounting the USB drive, adding rootdelay=10 as described to the KCMD line in the .run.conf file should work for you. Lonnie On Jan 11, 2018, at 8:47 AM, Josh Alberts <jm...@ho...> wrote: > Lonnie, > > I'm running this off the thinclient's internal flash drive, so unfortunately, it looks like this won't help me out. > > After going through the build process and upgrading, I can confirm that the changes I made don't cut out the error message I described. Even if it had, Michael's message makes me believe this wouldn't have solved my problem. > > From: Lonnie Abelbeck <li...@lo...> > Sent: Thursday, January 11, 2018 8:48 AM > To: AstLinux Developers Mailing List > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > Hi Josh, > > Yes, if your flash storage is internally connected via USB then no rootdelay could explain what you are seeing. Here is a WiKi reference ... > > Boot via USB Flash Storage > https://doc.astlinux-project.org/userdoc:boot-usb-storage userdoc:boot-usb-storage [AstLinux Documentation]<https://doc.astlinux-project.org/userdoc:boot-usb-storage> doc.astlinux-project.org For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > userdoc:boot-usb-storage [AstLinux Documentation] > doc.astlinux-project.org > For production AstLinux installations, it is recommended to use flash storage connected off IDE, SATA or mSATA controllers, if at all possible. > > > Add rootdelay=10 as described to the KCMD line in the .run.conf file. If you can't remove the flash and mount it as described in the WiKi on a successful boot from the AstLinux CLI ... > -- > mount -o rw,remount /oldroot/cdrom > ## edit the /oldroot/cdrom/os/astlinux-nnnnnn.run.conf file > mount -o ro,remount /oldroot/cdrom > -- > > Or since you build your own "geni586" image, you could edit on your build system "project/astlinux/board/geni586/runnix.conf" file and without a clean build you can simply > -- > ./scripts/build > -- > and install the new image. > > Lonnie > > > On Jan 11, 2018, at 7:10 AM, Josh Alberts <jm...@ho...> wrote: > > > That's an interesting point, Michael. Do you think adding a "rootdelay" might help? If so, is it possible to add something to the KCMD line in the .run.conf file in an already-built environment? > > > > > > From: Michael Keuter <li...@mk...> > > Sent: Thursday, January 11, 2018 5:37 AM > > To: AstLinux Developers Mailing List > > Subject: Re: [Astlinux-devel] Boot Occasionally Freezing While Probing PS/2 Ports > > > > > > > Am 11.01.2018 um 04:25 schrieb Josh Alberts <jm...@ho...>: > > > > > > Hello again, > > > > > > I made a custom build for an HP t5700 thinclient with a Transmeta Crusoe processor. I got that figured out (thanks again, Michael!) but occasionally the machine gets hung up on booting, and this is the last thing on the screen: > > > > > > i8042: PNP: No PS/2 controller found. Probing ports directly. > > > > > > This thinclient has no PS/2 ports, so I figured I could just go ahead and try to remove PS/2 support to solve this issue. I commented out all of the lines under "Hardware I/O ports" in the following files that seemed relevant for my geni586 build: > > > > > > project/runnix-iso/geni586/linux.config > > > project/runnix/geni586/linux.config > > > project/astlinux/geni586/linux-smp.config > > > > > > Then, I went ahead and rm -rf'd my output folder and ran scripts/build geni586. Is this the proper method to remove PS/2 support? Moreover, should this approach solve my problem? Since it's an intermittent issue, it would be great to get some outside input rather than convincing myself after a few successful reboots that I've solved the problem. Thanks! > > > > > > Josh > > > > Hi Josh, > > > > I don't think that has something to do with the PS/2 ports. > > I looked at dmesg on my old Soekris net5501 (also no PS/2 ports): the same message as yours occurs, but then directly after it the CF card is loaded: > > > > ---- > > [ 0.448889] usbcore: registered new interface driver ums-sddr55 > > [ 0.449653] usbcore: registered new interface driver ums-usbat > > [ 0.451065] i8042: PNP: No PS/2 controller found. Probing ports directly. > > [ 0.479585] ata1.00: CFA: SanDisk SDCFH-1024, HDX 4.09, max MWDMA2 > > [ 0.480841] ata1.00: 2001888 sectors, multi 0: LBA > > [ 0.481907] ata1.00: configured for PIO4 > > [ 0.493398] scsi 0:0:0:0: Direct-Access ATA SanDisk SDCFH-10 4.09 PQ: 0 ANSI: 5 > > ---- > > > > Maybe your storage medium has temporary issues … > > > > Michael > > > > http://www.mksolutions.info Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen - mit Asterisk - mk ... > www.mksolutions.info<http://www.mksolutions.info> Individuelle Telefonie-Lösungen - mit Asterisk - mk ...<http://www.mksolutions.info/> www.mksolutions.info Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > Individuelle Telefonie-Lösungen auf Basis von Asterisk - aus Hamburg. Mehr Komfort, mehr Service, geringere Kosten. Als Komplettsystem oder als Erweitung einer ... > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
28 messages has been excluded from this view by a project administrator.
