On Fri, 2006-05-26 at 12:58, Helge Hafting wrote:
> Alexander E. Patrakov wrote:
> > Helge Hafting wrote:
> >> "Which of the two keyboards to read, which of the three screens to use
> >> for messages" is not a problem. The kernel would use whatever devices
> >> is associated with the primary console - any extra devices would be
> >> left alone.
> >> The console is normally one particular keyboard (or possibly all of
> >> them),
> >> and /dev/fb0 in case of graphical console. Other framebuffers are
> >> not the primary console.
> >
> > I am not sure how this can be achievable, assuming that udev is
> > responsible for loading framebuffer modules. Since it loads them in
> > parallel, the registration order is essentially random. See the
> > following Debian bugs about other subsystems:
> So what? In that case, it is essentially random _which_ display you
> get your PANIC on, but you will get it on one of them.
>
> Of course this case is easily fixed by loading the preferred
> framebuffer driver before running udev. That way, it grabs
> /dev/fb0 before anything else.
Well, the oops/panic should probably be displayed on all fbdevs anyway.
Xav
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
