Michel,
Thanks for the suggestion, this particular driver was being loaded from
/etc/modules.d, however even when I moved it into /etc/modules-boot.d it
still doesn't create /dev/ttyGS0 in time for procd to start the console.
I'll try fiddling around with the load order to see if I can get it
wo
On 15-01-09 09:51 AM, Karl Palsson wrote:
"Stam, Michel [FINT]" wrote:
This, to me, seems the most logical solution, as consoles should be
available to the init process early on during boot, and not hot-plugged
in afterwards. Do you agree?
Well, I don't. What about a usb serial port? I'd
Am Freitag, 9. Januar 2015, 17:51:48 schrieb Karl Palsson:
>
> "Stam, Michel [FINT]" wrote:
> > This, to me, seems the most logical solution, as consoles should be
> > available to the init process early on during boot, and not hot-plugged
> > in afterwards. Do you agree?
>
>
> Well, I don't.
"Stam, Michel [FINT]" wrote:
> This, to me, seems the most logical solution, as consoles should be
> available to the init process early on during boot, and not hot-plugged
> in afterwards. Do you agree?
Well, I don't. What about a usb serial port? I'd like to plug in the
usb cable, providin
Hello Owen,
I was wondering, is the kernel driver for your console not placed in
/etc/modules-boot.d ?
/sbin/init executes procd, but prior to doing this executes kmodloader
to load all modules in /etc/modules-boot.d. If your module is mentioned
in this directory, this should load your console dr
Hi,
I'm not sure if this is a bug with procd's implementation of inittab or
if I'm just doing something wrong in my inittab. However, we have a
board that has multiple serial console ports, one of which relies on a
kernel module and procd refuses to start a console on the second port.
What se
