fvdw-sl on WD My Cloud

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 7:41 pm

in /etc/inittab line 61 you see this

# Example how to put a getty on a serial line (for a terminal)
#
T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100

disable that line
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 7:42 pm

matt_max wrote:I think it is related to the lack of eth interface.

why do you think that ?
serial interface doesn't need a ethernet interface
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby matt_max » Mon Aug 22, 2022 7:51 pm

fvdw wrote:
matt_max wrote:I think it is related to the lack of eth interface.

why do you think that ?
serial interface doesn't need a ethernet interface

I think that system cannot check for new firmware (there is no eth0 interface and no network connection) and this job respawning to fast and exiting prematurely. :scratch
Or maybe System is failing to run "/sbin/getty ttyS0". This could be because:
    - we do not have /sbin/getty
    - or it depends on libraries which are not present
    - or ttyS0 does not exist or cannot be opened.
Last edited by matt_max on Mon Aug 22, 2022 7:56 pm, edited 3 times in total.
matt_max
Donator VIP
Donator VIP
 
Posts: 124
Joined: Fri Apr 03, 2015 9:56 am
Location: Warsaw, Poland

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 7:53 pm

I found this
18.6 ... respawning too fast: disabled for 5 minutes
What's happening

You see a message on the console like: "Getty respawning too fast: disabled for 5 minutes". Instead of "Getty" it may display a label (such as: Id "S2") where S2 is the label for the line in /etc/inittab from where from where getty was called.

When getty starts up, it tries to send a login message to the serial port. But if there is something seriously wrong, getty will be immediately killed. Since the /etc/inittab file line for getty says to "respawn", getty is started again, only to be killed again, etc. Thus getty respawns over and over. But the operating system intervenes and stops this nonsense (for 5 minutes). The following sections show possible causes and fixes.

Getty line in /etc/inittab file incorrect

Make sure the the line which calls getty in /etc/inittab is correct. A typo in "ttySx" (or "DTxxxx" for uugetty) or in "getty" may cause this problem.

No modem control signal

If the terminal doesn't send the PC a CD signal on one of the pins of the serial port, getty will be killed unless the "local" option has been used with getty. So a quick fix is to just use a "local" option (-L for agetty, "CLOCAL" in /etc/gettydefs for ps_getty).

Another approach is to determine why CD is not being asserted. In many cases the cable to the terminal simply doesn't have a wire for the CD pin so you must use the "local" option. If there is a wire for the CD pin then there may not be any signal on it until the terminal is powered on. Note that the CD pin signal is sometimes supplied by the DTR pin of the terminal (or the PC) by using jumper wires inside the connector.

No such serial device

If the device (such as /dev/ttyS2) is bogus (doesn't physically exist or has been disabled), then getty will be killed. You may use "scanport" (Debian only ??) and/or "setserial" to probe for the device or try another ttyS. Perhaps the device has been disabled in the CMOS. See "Serial-HOWTO".

No serial support

Linux provides serial support either by selecting it when compiling the kernel or by loading the serial module: serial.o. This "respawning" error happens if serial support has neither been built into the kernel nor provided by a serial module. You many use the "lsmod" command to see if the serial module is loaded. To see if serial support is built into the kernel, check a kernel configuration file (in /boot, in the source tree, etc.)

Key shorted

Another possible cause of getty respawning too rapidly is if a keyboard key is shorted. This gives the same result as if the key was continuously held down. With auto-repeat enabled, this "types" thousands of characters to the login prompt. Look for a screen filled with all the same character (in some cases, with 2 or more different characters).

seems the respawn line is required, we need to check if the kernel gets as console ttyS0
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 8:05 pm

the system doesn't hang but the serial console is disabled
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 8:10 pm

Anyhow the new kernel has a problem there are several errors in the kernel output , so put back the original kernel and enble again the line in /etc/inittab to see if you can use chroot command

sorry to keep you busy but for me this is also new field, takes always a while to figure out boot processes
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby matt_max » Mon Aug 22, 2022 9:24 pm

Take your time. I'm really happy that I can help and better understand what is going on during booting process. Maybe we can adopt fvdw firmware for other owners of WD Mycloud NAS.
Chroot is still not available
Code: Select all
WDMyCloud:~# chroot /chroot /etc/init.d/rcS
Killed
matt_max
Donator VIP
Donator VIP
 
Posts: 124
Joined: Fri Apr 03, 2015 9:56 am
Location: Warsaw, Poland

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 9:38 pm

thx for patience so far and assisting with trials really appreciate and yes it would be nice if we could add wd cloud to the supported devices. We will continue th trial

PS in parrallel I think I am going to buy a second hand wd cloud without disk, they are rather cheap that might help to speed up trials. Also compiler is running to compile a new kernel . seems that the last one had a problem with the otg module (related to usb) I changed setting so that it afterwards must be loaded as module and not included in the kernel. I also made some other modifications in the kernel such as support for software floating point. I will post it tommorow.
But still if we cannot get the armv5 binaries running on this cpu then we have a issue as code of fvdw-sl is compiled in armv5 code. However because it runs just fine on an armada 370 I see no reason why it will not run on thios armade comcerto as it is also an armv7 cpu.
This is it for tonight ;)
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby fvdw » Mon Aug 22, 2022 9:39 pm

matt_max wrote:Take your time. I'm really happy that I can help and better understand what is going on during booting process. Maybe we can adopt fvdw firmware for other owners of WD Mycloud NAS.
Chroot is still not available
Code: Select all
WDMyCloud:~# chroot /chroot /etc/init.d/rcS
Killed


...but the message about /bin/bash disappeared...
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl on WD My Cloud

Postby Mijzelf » Tue Aug 23, 2022 7:00 am

I think you both missed my post: viewtopic.php?f=4&t=3635&start=40#p36992
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

PreviousNext

Return to Development

Who is online

Users browsing this forum: No registered users and 10 guests