Hi Jakub,
thanks, that explains it. I was able to get a somewhat working replacement
by having init start /app/kio instead of bdsh. Still, we should think about
how to solve this in the long term. I created ticket #704 to track this
issue.
Thanks,
Jiri
---------- Původní e-mail ----------
Od: Jakub Jermář <[email protected]>
Komu: [email protected]
Datum: 6. 11. 2017 20:01:21
Předmět: Re: [HelenOS-devel] Why is there no kernel output on ia64/ski?
"Hi Jiri,
On 11/06/2017 11:48 AM, Jiri Svoboda wrote:
> any idea why ia64/ski produces no output from the kernel on the console?
> I.e. we see the message 'Booting the kernel...' and then nothing is seen
> until the userspace console is initialized (and bdsh line pops up). Why
> are there no kernel messages? Looks like there is a kernel console
> driver for ski....
I think this behavior was introduced in mainline,2166:
allow compositor and console to coexist side-by-side, use the input
server as a poor man's seat arbitrator
* kernel console notifies both about the release and grab events
* input server arbitrates the seat selection between kernel console and
any number of user space UIs (currently the console server and the
compositor server)
* input port yield and reclaim methods have been removed (they are used
only on Ski and Niagara, both already need a more generic mechanism for
the kernel/user space cooperation)
* console and compositor server keep track of the kernel console via
the input arbitration
* move the waiting for a character device from init and terminal widget
to getterm
Jakub
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
"
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
