in initrd "exec sh /dev/console 2>&1" does not respond to keyboard
David Mathog
mathog at caltech.edu
Fri Mar 1 01:46:59 UTC 2019
On 27-Feb-2019 18:13, Michael Conrad wrote:
> Well, just a guess, but I'd say your problem is with kernel device
> drivers for input. Usually people have the basic text showing up on
> their console and the complaints are about how to get ^C and other
> tty-specific features to work while using /dev/console. Your problem
> sounds more like the Linux virtual console subsystem isn't connecting
> to your input devices. I'd suggest poking around in the input drivers
> section of the config and make sure things are compiled as "=y" and
> not as modules.
Well, in 3 different kernels there were:
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_KEYBOARD=y
but only 2 of the 3 work, the third one ignores input. Oddly 3.10.108
was the one originally giving me problems, so rebuilt it using "menu
oldconfig" starting from the config-3.10.0-957.5.1.el7.x86_64 from
Centos 7 and then 3.10.108 worked. But the 3.10.108 kernel had problems
with xfs. So built kernel 3.14.78, starting from the last good 3.10.108
config, and that kernel does not respond (but xfs works!)
Regards,
David Mathog
mathog at caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech
>
> On 2/27/2019 8:44 PM, David Mathog wrote:
>> On 27-Feb-2019 17:37, Michael Conrad wrote:
>>> On 2/27/2019 6:00 PM, David Mathog wrote:
>>>> On 27-Feb-2019 14:01, David Mathog wrote:
>>>>> This is really frustrating! Perhaps there is some kernel parameter
>>>>> for 3.10.108 kernels which needs to be set (or unset)??? These are
>>>>> built into the kernel, seems like they should be enough
>>>>>
>>>>> CONFIG_HID=y
>>>>> CONFIG_HID_GENERIC=y
>>>>> CONFIG_USB_HID=y
>>>>> CONFIG_USB_SUPPORT=y
>>>>> CONFIG_USB_COMMON=y
>>>>> CONFIG_USB=y
>>>>
>>>> It is definitely the kernel. If the custom (based on "make
>>>> menuconfig" of boel)
>>>> 3.10.108 kernel is replaced with a stock Centos 7 kernel then
>>>>
>>>
>>> What do you get from "grep CONSOLE .config" in each of the two
>>> kernels ?
>>
>> The one where the keyboard does not work:
>>
>> # CONFIG_NETCONSOLE is not set
>> CONFIG_VT_CONSOLE=y
>> CONFIG_HW_CONSOLE=y
>> # CONFIG_VT_HW_CONSOLE_BINDING is not set
>> CONFIG_SERIAL_8250_CONSOLE=y
>> CONFIG_SERIAL_CORE_CONSOLE=y
>> CONFIG_VGA_CONSOLE=y
>> CONFIG_DUMMY_CONSOLE=y
>>
>> The one where where the keyboard does work:
>>
>> CONFIG_NETCONSOLE=m
>> CONFIG_NETCONSOLE_DYNAMIC=y
>> CONFIG_CONSOLE_TRANSLATIONS=y
>> CONFIG_VT_CONSOLE=y
>> CONFIG_VT_CONSOLE_SLEEP=y
>> CONFIG_HW_CONSOLE=y
>> CONFIG_VT_HW_CONSOLE_BINDING=y
>> CONFIG_SERIAL_8250_CONSOLE=y
>> CONFIG_SERIAL_CORE_CONSOLE=y
>> CONFIG_CONSOLE_POLL=y
>> # CONFIG_LP_CONSOLE is not set
>> CONFIG_VIRTIO_CONSOLE=m
>> CONFIG_VGA_CONSOLE=y
>> CONFIG_DUMMY_CONSOLE=y
>> CONFIG_FRAMEBUFFER_CONSOLE=y
>> CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
>> CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
>> CONFIG_USB_SERIAL_CONSOLE=y
>> # CONFIG_PSTORE_CONSOLE is not set
>> CONFIG_KGDB_SERIAL_CONSOLE=y
>>
>> That said, there are a zillion other differences...
>>
>> Thanks,
>>
>> David Mathog
>> mathog at caltech.edu
>> Manager, Sequence Analysis Facility, Biology Division, Caltech
>> _______________________________________________
>> busybox mailing list
>> busybox at busybox.net
>> http://lists.busybox.net/mailman/listinfo/busybox
>
>
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
More information about the busybox
mailing list