Jump to content

Timed out waiting for device dev-ttyGS0.device


Recommended Posts

Posted

Hi Experts,

 

I am using Armbian Ubuntu Xenial image on Orange Pi Zero and I get following Failure during boot after which it starts rebooting itself.

 

[ TIME ] Timed out waiting for device dev-ttyGS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyGS0.

 

THIS HAPPENS ONLY WHEN WIFI (SSID) CONFIGURED IN THE IMAGE IS POWERED OFF. IF WIFI ROUTER IS ON, IT SUCCESSFULLY GOES TO THE LOGIN PROMPT.

 

Is there specific boot sequence that cause this failure when WiFi is not available. Any workaround please?

Posted (edited)

Providing Failure and Successful scenario logs. Hope this will help to identify the problem. We need login prompt irrespective WiFi AP is up or down.

 

Logs of Failure When WiFi Router was off 

  Reveal hidden contents

Successful boot Log with Login Prompt when WiFi Router was On

  Reveal hidden contents

 

 

Edited by Igor
added code under spoilers
Posted
  On 12/15/2017 at 2:10 AM, gailu said:

No clue?? Any pointer?

Expand  


Yes, but I am afraid it is not much you can do. Try modern kernel or use the board with a decent wireless chip. It is virtually impossible to find worse than this one. Most of the people stopped wasting time on anything related to Orangepi zero xradio chip/driver. A long time ago and especially on the old EOL kernel. 

Posted

I understand that no one is interested to support this. But I am sure that someone could advise based on log how to stop reboot when. specifically following logs where reboot is triggered

 

[ TIME ] Timed out waiting for device dev-ttyGS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyGS0.
[ SKIP ] Ordering cycle found, skipping Journal Socket
[ SKIP ] Ordering cycle found, skipping File...2eba-571d-4583-8873-97f09353655c
[  OK  ] Stopped Update UTMP about System Runlevel Changes.
         Stopping Save/Restore Sound Card State...
[  OK  ] Stopped target Graphical Interface.
[  OK  ] Stopped target Sound Card.
         Stopping Authenticate and Authorize Users to Run Privileged Tasks...
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily Cleanup of Temporary Directories.
[  OK  ] Stopped target Multi-User System.
[  OK  ] Stopped Terminate Plymouth Boot Screen.
         Stopping LSB: Advanced IEEE 802.11 management daemon...
         Stopping System Logging Service...
         Stopping LSB: Set sysfs variables from /etc/sysfs.conf...
         Stopping LSB: Starts LIRC daemon....
[  OK  ] Stopped target Login Prompts.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Removed slice system-getty.slice.
[  OK  ] Stopped Serial Getty on ttyS0.

 

Posted

A websearch  did bring me here last week. Now I'm back to report my observation.

 

The slow startup plus the

 

[ TIME ] Timed out waiting for device dev-ttyGS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyGS0.

 

appears to me when I have systemd-networkd enabled.

 

The  issue seems to be that systemd-networkd waits for all network interfaces it is told about.

 

For quick startup and avoidance of the time-out, I have changed  /etc/systemd/network/10-foo-lan3.network


 

[Match]
Name=lan3

[Network]
LinkLocalAddressing=no
Bridge=lan

 

into


 

[Match]
Name=lan3

[Link]
RequiredForOnline=no

[Network]
LinkLocalAddressing=no
Bridge=lan

 

So the trick seems to be the

[Link]
RequiredForOnline=no

 

I do read it as    don't wait for interface lan3 getting link.

 

Because I have more simular interfaces as lan3, I have set there also RequiredForOnline=no

 

 

Regards

Geert Stappers

 

Looking forward to see  yes, that link RequiredForOnline=no worked for me also.

Posted (edited)

Oh, I didn't mention in my previous post that I do use systemd-networkd and have Network-Manager disabled.

 

With the various files in /etc/systemd/network sets systemd-networkd network configuration as IP address.

 

Edited by stappers
added what sd-nwd does for me
Posted
  On 1/1/2020 at 3:39 PM, stappers said:

Oh, I didn't mention in my previous post that I do use systemd-networkd and have Network-Manager disabled.

Expand  


This has nothing to do with networking.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines