Hi.
I’m experimenting with running a Jetson TX2 with another Linux distribution. In my case this is Crux Linux. I used rootfs from this distribution, and the system start was fine. The problem is just that the keypad will turn on after the prompt has started in about 30 seconds. I compiled the kernel using the make tegra18_defconfig configuration from L4T 28.1.
Where to find solutions?
Note: If I’m in the wrong forum, do not respond to this message.
Do you have a separate numeric keypad? Or are you saying the regular keyboard waits too long to enable? Are you using the GUI, or text-only console?
Is the rootfs entirely from Crux? If so, then you wouldn’t be using the NVIDIA hardware-accelerated drivers and X11 would be a software-only rendered GUI without the GPU helping. This would be quite slow.
Hi linuxdev
I use only a text console, a classic keyboard, and a rootfs of Crux-Arm 64bit. It is a minimal rootfs without an X and GUI interface. The last result of activating bash promnt after activating the keyboard is 55 seconds. Personally, I do not mind but I think keyboard activation should be before bash promnt.
Maybe there is a mistake in Crux not using systemd but sysvinit. Or udev.rules ???
I would have to wonder how you know the keyboard isn’t active before a bash prompt? Are you going by something like the caps lock LED? What is it you want to do with the keyboard prior to bash prompt?
I have no knowledge of Crux, but it shouldn’t matter if it is sys V or systemd unless there is some error in setup. Often when something mysteriously takes a long time to boot it is because some service is waiting and then timing out. A big example would be if WiFi were configured and it tried some network configuration and waited for the first attempt to time out before moving on. If you have a boot log with time stamps you might look to see if one particular event took a long pause.
I was wrong to say. When appears on the monitor, the keyboard is not active. I added an init script to enable +num leds.
which shows me at the light status. So when the keypad is lit, the keyboard is active.
I’m adding a link to a video demo - YouTube
It’s from your cellphone. No quality, however, shows how long the keyboard activates.
That looked fairly “normal”, but I don’t know what Crux does for boot. Is there a “/var/log/boot.log” or dmesg output with timestamps? I couldn’t actually see a keyboard light, and I don’t know where you added code to set num lock. Please add details about how num lock is enabled.
Keep in mind that in part you are seeing boot log information on the first tty. The actual login is separate and the two interleave and display simultaneously on the same terminal. If you were to go to an alternate console (such as via ALT-F2), then your login prompt wouldn’t show as much from system messages. The login terminal and the system messages run in separate threads and despite looking as though they are a single program they are independent (and timing may not be what it looks like).
The outputs listed below
May 5 16:18:37 ishi syslogd 1.5.1: restart.
May 5 16:18:37 ishi dhcpcd[342]: dev: loaded udev
May 5 16:18:37 ishi dhcpcd[342]: no interfaces have a carrier
May 5 16:18:37 ishi dhcpcd[342]: forked to background, child pid 385
May 5 16:18:37 ishi dhcpcd[385]: dummy0: waiting for carrier
May 5 16:18:37 ishi net: dev: loaded udev
May 5 16:18:37 ishi dhcpcd[385]: eth0: waiting for carrier
May 5 16:18:37 ishi net: no interfaces have a carrier
May 5 16:18:37 ishi net: forked to background, child pid 385
May 5 16:18:38 ishi dhcpcd[385]: wlan0: waiting for carrier
May 5 16:18:38 ishi dhcpcd[385]: dummy0: carrier acquired
May 5 16:18:38 ishi dhcpcd[385]: DUID 00:01:00:01:22:7f:62:e2:fe:92:06:80:b1:bc
May 5 16:18:38 ishi dhcpcd[385]: dummy0: IAID 00:af:be:0b
May 5 16:18:38 ishi dhcpcd[385]: dummy0: adding address fe80::5b27:93bd:a288:12d3
May 5 16:18:38 ishi dhcpcd[385]: wlan0: carrier acquired
May 5 16:18:38 ishi dhcpcd[385]: wlan0: IAID 4b:8d:11:e7
May 5 16:18:38 ishi dhcpcd[385]: wlan0: adding address fe80::cb6c:c8f6:441:31ec
May 5 16:18:38 ishi /usr/sbin/gpm[408]: *** info [daemon/startup.c(136)]:
May 5 16:18:38 ishi /usr/sbin/gpm[408]: Started gpm successfully. Entered daemon mode.
May 5 16:18:38 ishi /usr/sbin/gpm[408]: O0o.oops(): [daemon/old_main.c(58)]:
May 5 16:18:38 ishi /usr/sbin/gpm[408]: Could not open /dev/input/mouse0.
May 5 16:18:38 ishi dhcpcd[385]: dummy0: soliciting an IPv6 router
May 5 16:18:38 ishi dhcpcd[385]: wlan0: soliciting an IPv6 router
May 5 16:18:38 ishi dhcpcd[385]: wlan0: soliciting a DHCP lease
May 5 16:18:39 ishi dhcpcd[385]: dummy0: soliciting a DHCP lease
May 5 16:18:40 ishi dhcpcd[385]: eth0: carrier acquired
May 5 16:18:40 ishi dhcpcd[385]: eth0: IAID 4b:8d:11:e9
May 5 16:18:40 ishi dhcpcd[385]: eth0: adding address fe80::14da:9a63:d670:1f5a
May 5 16:18:41 ishi dhcpcd[385]: eth0: soliciting an IPv6 router
May 5 16:18:41 ishi dhcpcd[385]: eth0: rebinding lease of 192.168.0.45
May 5 16:18:41 ishi dhcpcd[385]: eth0: probing address 192.168.0.45/24
May 5 16:18:43 ishi dhcpcd[385]: wlan0: probing for an IPv4LL address
May 5 16:18:46 ishi dhcpcd[385]: eth0: leased 192.168.0.45 for 3600 seconds
May 5 16:18:46 ishi dhcpcd[385]: eth0: adding route to 192.168.0.0/24
May 5 16:18:46 ishi dhcpcd[385]: eth0: adding default route via 192.168.0.1
May 5 16:18:48 ishi dhcpcd[385]: wlan0: using IPv4LL address 169.254.81.182
May 5 16:18:48 ishi dhcpcd[385]: wlan0: adding route to 169.254.0.0/16
May 5 16:18:50 ishi dhcpcd[385]: dummy0: no IPv6 Routers available
May 5 16:18:51 ishi dhcpcd[385]: wlan0: no IPv6 Routers available
May 5 16:18:53 ishi dhcpcd[385]: eth0: no IPv6 Routers available
May 5 16:18:39 ishi kernel: [ 6.694175] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
May 5 16:18:39 ishi kernel: [ 6.694188] VFS: Mounted root (ext4 filesystem) on device 8:4.
May 5 16:18:39 ishi kernel: [ 6.695508] devtmpfs: mounted
May 5 16:18:39 ishi kernel: [ 6.695798] Freeing unused kernel memory: 1164K (ffffffc0010fa000 - ffffffc00121d000)
May 5 16:18:39 ishi kernel: [ 6.695821] Freeing alternatives memory: 96K (ffffffc00121d000 - ffffffc001235000)
May 5 16:18:39 ishi kernel: [ 6.698797] btb inv war enabled
May 5 16:18:39 ishi kernel: <30>[ 6.803546] udevd[260]: starting version 3.2.5
May 5 16:18:39 ishi kernel: <30>[ 6.822749] udevd[261]: starting eudev-3.2.5
May 5 16:18:39 ishi kernel: [ 6.888257] tegra-pcie 10003000.pcie-controller: 4x1, 1x1 configuration
May 5 16:18:39 ishi kernel: [ 6.897513] tegra-pcie 10003000.pcie-controller: PCIE: Enable power rails
May 5 16:18:39 ishi kernel: [ 6.907051] tegra-pcie 10003000.pcie-controller: probing port 0, using 4 lanes
May 5 16:18:39 ishi kernel: [ 6.918515] tegra-pcie 10003000.pcie-controller: probing port 2, using 1 lanes
May 5 16:18:39 ishi kernel: [ 7.003890] CAN device driver interface
May 5 16:18:39 ishi kernel: [ 7.007538] dhd_module_init in
May 5 16:18:39 ishi kernel: [ 7.007566] tegra_net_perf_init: cannot get wifi sclk
May 5 16:18:39 ishi kernel: [ 7.007631] found wifi platform device bcmdhd_wlan
May 5 16:18:39 ishi kernel: [ 7.008724] wifi_platform_get_country_code_map: could not get country_code_map
May 5 16:18:39 ishi kernel: [ 7.008726] wifi_plat_dev_drv_probe:platform country code map is not available
May 5 16:18:39 ishi kernel: [ 7.008750] Power-up adapter 'DHD generic adapter'
May 5 16:18:39 ishi kernel: [ 7.008755] wifi_platform_set_power = 1
May 5 16:18:39 ishi kernel: [ 7.083605] ^I Message RAM Configuration
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| base addr |0x0c312000|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| sidfc_flssa |0x00000000|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| xidfc_flesa |0x00000040|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| rxf0c_f0sa |0x000000c0|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| rxf1c_f1sa |0x00000300|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| rxbc_rbsa |0x00000540|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| txefc_efsa |0x00000780|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| txbc_tbsa |0x00000800|
May 5 16:18:39 ishi kernel: [ 7.083605] ^I| tmc_tmsa |0x00000c80|
May 5 16:18:39 ishi kernel: [ 7.136433] Release 3.2.0 from 19.12.2014
May 5 16:18:39 ishi kernel: [ 7.142167] net can0: mttcan device registered (regs=ffffff80025fc000, irq=427)
May 5 16:18:39 ishi kernel: [ 7.152216] ^I Message RAM Configuration
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| base addr |0x0c322000|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| sidfc_flssa |0x00000000|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| xidfc_flesa |0x00000040|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| rxf0c_f0sa |0x000000c0|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| rxf1c_f1sa |0x00000300|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| rxbc_rbsa |0x00000540|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| txefc_efsa |0x00000780|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| txbc_tbsa |0x00000800|
May 5 16:18:39 ishi kernel: [ 7.152216] ^I| tmc_tmsa |0x00000c80|
May 5 16:18:39 ishi kernel: [ 7.204254] Release 3.2.0 from 19.12.2014
May 5 16:18:39 ishi kernel: [ 7.206784] wifi_platform_bus_enumerate device present 1
May 5 16:18:39 ishi kernel: [ 7.216041] net can1: mttcan device registered (regs=ffffff800265e000, irq=428)
May 5 16:18:39 ishi kernel: [ 7.224556] wifi_platform_bus_enumerate device present 0
May 5 16:18:39 ishi kernel: [ 7.231685] F1 signature read @0x18000000=0x17214354
May 5 16:18:39 ishi kernel: [ 7.241572] F1 signature OK, socitype:0x1 chip:0x4354 rev:0x1 pkg:0x2
May 5 16:18:39 ishi kernel: [ 7.250022] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
May 5 16:18:39 ishi kernel: [ 7.258503] wifi_platform_prealloc: failed to alloc static mem section 7
May 5 16:18:39 ishi kernel: [ 7.266812] wifi_platform_get_mac_addr
May 5 16:18:39 ishi kernel: [ 7.274302] CFG80211-ERROR) wl_setup_wiphy : Registering Vendor80211
May 5 16:18:39 ishi kernel: [ 7.282641] wl_create_event_handler(): thread:wl_event_handler:124 started
May 5 16:18:39 ishi kernel: [ 7.282648] CFG80211-ERROR) wl_event_handler : tsk Enter, tsk = 0xffffffc07a7e1a70
May 5 16:18:39 ishi kernel: [ 7.300456] dhd_attach(): thread:dhd_watchdog_thread:125 started
May 5 16:18:39 ishi kernel: [ 7.308163] dhd_attach(): thread:dhd_dpc:126 started
May 5 16:18:39 ishi kernel: [ 7.314826] dhd_attach(): thread:dhd_rxf:127 started
May 5 16:18:39 ishi kernel: [ 7.321062] dhd_deferred_work_init: work queue initialized
May 5 16:18:39 ishi kernel: [ 7.329420] Dongle Host Driver, version 1.201.82 (r)
May 5 16:18:39 ishi kernel: [ 7.329420] Compiled in drivers/net/wireless/bcmdhd on May 3 2018 at 11:56:08
May 5 16:18:39 ishi kernel: [ 7.344285] tegra_sysfs_register
May 5 16:18:39 ishi kernel: [ 7.348695] Register interface [wlan0] MAC: 00:04:4b:8d:11:e7
May 5 16:18:39 ishi kernel: [ 7.348695]
May 5 16:18:39 ishi kernel: [ 7.362421] dhd_prot_ioctl : bus is down. we have nothing to do
May 5 16:18:39 ishi kernel: [ 7.369927] sdhci-tegra 3440000.sdhci: Tuning already done, restoring the best tap value : 20
May 5 16:18:39 ishi kernel: [ 7.380681] wifi_platform_set_power = 0
May 5 16:18:39 ishi kernel: [ 7.413353] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
May 5 16:18:39 ishi kernel: [ 7.600100] EXT4-fs (sda4): re-mounted. Opts: discard
May 5 16:18:39 ishi kernel: [ 7.616940] EXT4-fs (sda4): re-mounted. Opts: discard
May 5 16:18:39 ishi kernel: [ 7.637700] Adding 8388604k swap on /dev/sda3. Priority:-1 extents:1 across:8388604k SS
May 5 16:18:39 ishi kernel: [ 7.832757] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
May 5 16:18:39 ishi kernel: [ 8.245724] tegra-pcie 10003000.pcie-controller: link 0 down, retrying
May 5 16:18:39 ishi kernel: [ 8.256000] tegra-pcie 10003000.pcie-controller: link 0 down, ignoring
May 5 16:18:39 ishi kernel: [ 8.666371] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
May 5 16:18:39 ishi kernel: [ 8.686845] mousedev: PS/2 mouse device common for all mice
May 5 16:18:39 ishi kernel: [ 9.017366] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 5 16:18:39 ishi kernel: [ 9.021036]
May 5 16:18:39 ishi kernel: [ 9.021036] Dongle Host Driver, version 1.201.82 (r)
May 5 16:18:39 ishi kernel: [ 9.021036] Compiled in drivers/net/wireless/bcmdhd on May 3 2018 at 11:56:08
May 5 16:18:39 ishi kernel: [ 9.021047] wl_android_wifi_on in
May 5 16:18:39 ishi kernel: [ 9.021051] wifi_platform_set_power = 1
May 5 16:18:39 ishi kernel: [ 9.051031] ip_tables: (C) 2000-2006 Netfilter Core Team
May 5 16:18:39 ishi kernel: [ 9.078779] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
May 5 16:18:39 ishi kernel: [ 9.291376] mmc1: queuing unknown CIS tuple 0x80 (5 bytes)
May 5 16:18:39 ishi kernel: [ 9.357733] sdhci-tegra 3440000.sdhci: Tuning already done, restoring the best tap value : 20
May 5 16:18:39 ishi kernel: [ 9.359023] F1 signature read @0x18000000=0x17214354
May 5 16:18:39 ishi kernel: [ 9.362543] F1 signature OK, socitype:0x1 chip:0x4354 rev:0x1 pkg:0x2
May 5 16:18:39 ishi kernel: [ 9.363022] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
May 5 16:18:39 ishi kernel: [ 9.413609] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
May 5 16:18:39 ishi kernel: [ 9.455723] dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)
May 5 16:18:39 ishi kernel: [ 9.455952] Enabling wake69
May 5 16:18:39 ishi kernel: [ 9.456924] wifi_platform_get_mac_addr
May 5 16:18:39 ishi kernel: [ 9.458486] Firmware up: op_mode=0x0005, MAC=00:04:4b:8d:11:e7
May 5 16:18:39 ishi kernel: [ 9.463964] dhd_preinit_ioctls pspretend_threshold for HostAPD failed -23
May 5 16:18:39 ishi kernel: [ 9.468277] Firmware version = wl0: Dec 12 2017 15:09:35 version 7.35.221.34 (r679642) FWID 01-e35dbe99
May 5 16:18:39 ishi kernel: [ 9.470568] dhd_interworking_enable: failed to set WNM info, ret=-23
May 5 16:18:39 ishi kernel: [ 9.470770] tegra_sysfs_on
May 5 16:18:39 ishi kernel: [ 9.490023] tegra-pcie 10003000.pcie-controller: link 2 down, retrying
May 5 16:18:39 ishi kernel: [ 9.500422] tegra-pcie 10003000.pcie-controller: link 2 down, ignoring
May 5 16:18:39 ishi kernel: [ 9.500436] tegra-pcie 10003000.pcie-controller: PCIE: no end points detected
May 5 16:18:39 ishi kernel: [ 9.500781] tegra-pcie 10003000.pcie-controller: PCIE: Disable power rails
May 5 16:18:39 ishi kernel: [ 9.558943] dhd_ndo_add_ip: ndo ip addr add failed, retcode = -23
May 5 16:18:39 ishi kernel: [ 9.558952] dhd_inet6_work_handler: Adding host ip for NDO failed -23
May 5 16:18:40 ishi kernel: [ 12.255091] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
May 5 16:18:40 ishi kernel: [ 12.256143] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 5 16:18:43 ishi kernel: [ 14.966824] protocol 0003 is buggy, dev wlan0
May 5 16:18:45 ishi kernel: [ 16.636028] protocol 0003 is buggy, dev wlan0
May 5 16:18:46 ishi kernel: [ 18.280220] protocol 0003 is buggy, dev wlan0
May 5 16:18:48 ishi kernel: [ 20.289438] protocol 0003 is buggy, dev wlan0
May 5 16:18:50 ishi kernel: [ 22.294548] protocol 0003 is buggy, dev wlan0
May 5 16:19:32 ishi kernel: [ 63.950865] xhci-tegra 3530000.xhci: cannot find firmware....retry after 1 second
May 5 16:19:33 ishi kernel: [ 64.953130] xhci-tegra 3530000.xhci: Firmware timestamp: 2017-12-07 10:50:08 UTC, Version: 55.09 release
May 5 16:19:33 ishi kernel: [ 64.954808] xhci-tegra 3530000.xhci: xHCI Host Controller
May 5 16:19:33 ishi kernel: [ 64.954833] xhci-tegra 3530000.xhci: new USB bus registered, assigned bus number 1
May 5 16:19:33 ishi kernel: [ 64.955632] xhci-tegra 3530000.xhci: hcc params 0x0184fd25 hci version 0x100 quirks 0x00010810
May 5 16:19:33 ishi kernel: [ 64.955659] xhci-tegra 3530000.xhci: irq 59, io mem 0x03530000
May 5 16:19:33 ishi kernel: [ 64.955774] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 5 16:19:33 ishi kernel: [ 64.955780] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 5 16:19:33 ishi kernel: [ 64.955784] usb usb1: Product: xHCI Host Controller
May 5 16:19:33 ishi kernel: [ 64.955788] usb usb1: Manufacturer: Linux 4.4.38-test xhci-hcd
May 5 16:19:33 ishi kernel: [ 64.955792] usb usb1: SerialNumber: 3530000.xhci
May 5 16:19:33 ishi kernel: [ 64.956088] hub 1-0:1.0: USB hub found
May 5 16:19:33 ishi kernel: [ 64.956113] hub 1-0:1.0: 4 ports detected
May 5 16:19:33 ishi kernel: [ 64.974923] xhci-tegra 3530000.xhci: xHCI Host Controller
May 5 16:19:33 ishi kernel: [ 64.974964] xhci-tegra 3530000.xhci: new USB bus registered, assigned bus number 2
May 5 16:19:33 ishi kernel: [ 64.975108] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
May 5 16:19:33 ishi kernel: [ 64.975113] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 5 16:19:33 ishi kernel: [ 64.975117] usb usb2: Product: xHCI Host Controller
May 5 16:19:33 ishi kernel: [ 64.975120] usb usb2: Manufacturer: Linux 4.4.38-test xhci-hcd
May 5 16:19:33 ishi kernel: [ 64.975124] usb usb2: SerialNumber: 3530000.xhci
May 5 16:19:33 ishi kernel: [ 64.975350] hub 2-0:1.0: USB hub found
May 5 16:19:33 ishi kernel: [ 64.975370] hub 2-0:1.0: 3 ports detected
May 5 16:19:33 ishi kernel: [ 64.975755] tegra-xotg xotg: otg: host 3530000.xhci registered
May 5 16:19:33 ishi kernel: [ 65.266790] usb 1-2: new high-speed USB device number 2 using xhci-tegra
May 5 16:19:33 ishi kernel: [ 65.311312] usb 2-1: new SuperSpeed USB device number 2 using xhci-tegra
May 5 16:19:34 ishi kernel: [ 65.336892] usb 2-1: New USB device found, idVendor=0bda, idProduct=0411
May 5 16:19:34 ishi kernel: [ 65.336900] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 5 16:19:34 ishi kernel: [ 65.336906] usb 2-1: Product: 4-Port USB 3.0 Hub
May 5 16:19:34 ishi kernel: [ 65.336912] usb 2-1: Manufacturer: Generic
May 5 16:19:34 ishi kernel: [ 65.337394] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
May 5 16:19:34 ishi kernel: [ 65.342380] hub 2-1:1.0: USB hub found
May 5 16:19:34 ishi kernel: [ 65.343147] hub 2-1:1.0: 4 ports detected
May 5 16:19:34 ishi kernel: [ 65.404832] usb 1-2: New USB device found, idVendor=0bda, idProduct=5411
May 5 16:19:34 ishi kernel: [ 65.404844] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 5 16:19:34 ishi kernel: [ 65.404851] usb 1-2: Product: 4-Port USB 2.0 Hub
May 5 16:19:34 ishi kernel: [ 65.404858] usb 1-2: Manufacturer: Generic
May 5 16:19:34 ishi kernel: [ 65.405676] hub 1-2:1.0: USB hub found
May 5 16:19:34 ishi kernel: [ 65.406557] hub 1-2:1.0: 4 ports detected
May 5 16:19:34 ishi kernel: [ 65.678789] usb 1-2.2: new low-speed USB device number 3 using xhci-tegra
May 5 16:19:34 ishi kernel: [ 65.788360] usb 1-2.2: New USB device found, idVendor=1a2c, idProduct=0c23
May 5 16:19:34 ishi kernel: [ 65.788370] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 5 16:19:34 ishi kernel: [ 65.788376] usb 1-2.2: Product: USB Keyboard
May 5 16:19:34 ishi kernel: [ 65.788382] usb 1-2.2: Manufacturer: USB
May 5 16:19:34 ishi kernel: [ 65.788554] usb 1-2.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
May 5 16:19:34 ishi kernel: [ 65.788573] usb 1-2.2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
May 5 16:19:34 ishi kernel: [ 65.791981] input: USB USB Keyboard as /devices/3530000.xhci/usb1/1-2/1-2.2/1-2.2:1.0/0003:1A2C:0C23.0001/input/input4
May 5 16:19:34 ishi kernel: [ 65.847007] hid-generic 0003:1A2C:0C23.0001: input,hidraw0: USB HID v1.10 Keyboard [USB USB Keyboard] on usb-3530000.xhci-2.2/input0
May 5 16:19:34 ishi kernel: [ 65.850412] input: USB USB Keyboard as /devices/3530000.xhci/usb1/1-2/1-2.2/1-2.2:1.1/0003:1A2C:0C23.0002/input/input5
May 5 16:19:34 ishi kernel: [ 65.902936] hid-generic 0003:1A2C:0C23.0002: input,hidraw1: USB HID v1.10 Device [USB USB Keyboard] on usb-3530000.xhci-2.2/input1
May 5 16:19:34 ishi kernel: [ 65.974793] usb 1-2.3: new low-speed USB device number 4 using xhci-tegra
May 5 16:19:34 ishi kernel: [ 66.081867] usb 1-2.3: New USB device found, idVendor=15d9, idProduct=0a41
May 5 16:19:34 ishi kernel: [ 66.081878] usb 1-2.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
May 5 16:19:34 ishi kernel: [ 66.081886] usb 1-2.3: Product: USB Mouse
May 5 16:19:34 ishi kernel: [ 66.082104] usb 1-2.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
May 5 16:19:34 ishi kernel: [ 66.085085] input: USB Mouse as /devices/3530000.xhci/usb1/1-2/1-2.3/1-2.3:1.0/0003:15D9:0A41.0003/input/input6
May 5 16:19:34 ishi kernel: [ 66.085256] hid-generic 0003:15D9:0A41.0003: input,hidraw2: USB HID v1.10 Mouse [USB Mouse] on usb-3530000.xhci-2.3/input0
May 5 16:19:35 ishi kernel: [ 67.096953] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 5
May 5 16:19:35 ishi kernel: [ 67.096962] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work ignore firmware MBOX_CMD_DEC_SSPI_CLOCK request
May 5 16:21:02 ishi kernel: [ 154.254794] usb 1-2.4: new high-speed USB device number 5 using xhci-tegra
May 5 16:21:03 ishi kernel: [ 154.370232] usb 1-2.4: New USB device found, idVendor=0930, idProduct=6545
May 5 16:21:03 ishi kernel: [ 154.370245] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 5 16:21:03 ishi kernel: [ 154.370254] usb 1-2.4: Product: DataTraveler 2.0
May 5 16:21:03 ishi kernel: [ 154.370261] usb 1-2.4: Manufacturer: Kingston
May 5 16:21:03 ishi kernel: [ 154.370267] usb 1-2.4: SerialNumber: 408D5C15AFB8B070390DD084
May 5 16:21:03 ishi kernel: [ 154.370930] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
May 5 16:21:03 ishi kernel: [ 154.371071] usb-storage 1-2.4:1.0: USB Mass Storage device detected
May 5 16:21:03 ishi kernel: [ 154.375291] scsi host2: usb-storage 1-2.4:1.0
May 5 16:21:04 ishi kernel: [ 155.377621] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6
May 5 16:21:04 ishi kernel: [ 155.378212] sd 2:0:0:0: [sdb] 15249408 512-byte logical blocks: (7.81 GB/7.27 GiB)
May 5 16:21:04 ishi kernel: [ 155.378514] sd 2:0:0:0: [sdb] Write Protect is off
May 5 16:21:04 ishi kernel: [ 155.378520] sd 2:0:0:0: [sdb] Mode Sense: 45 00 00 00
May 5 16:21:04 ishi kernel: [ 155.378815] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 5 16:21:04 ishi kernel: [ 155.457290] sdb: sdb1
May 5 16:21:04 ishi kernel: [ 155.458972] sd 2:0:0:0: [sdb] Attached SCSI removable disk
May 5 16:21:19 ishi kernel: [ 170.603469] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
All is working as expected. This is just a case of how your init is set to bring up different parts of the system…it isn’t that USB is disabled, nor is it that the keyboard is disabled/enabled. It’s that the console function which watches and responds to the keyboard is not started until the rest of the system is started.
Runlevels differ among distributions, and can be customized even within a distribution. Some of those treat interactive keyboard the same even if other parts differ, e.g., “single user” with and without networking often both exist…but on some systems networking may not exist, or there may be no definition of a run level for single user without networking. I’ll call that single user. When multiple persons can log in it becomes multi-user.
Take care to note that multi-user might or might not allow network logins. There may instead be multiple text terminals and no networking…there is no exact definition across all variants of Linux.
The basic flow though is that your system will turn on most of what needs to run first. Then it will allow a console login locally for one person. Then login locally will be added for multiple persons (e.g., ALT-F1 through ALT-F6). Then one of those local logins in text mode will be respawned for GUI mode (the text getty is replaced by a GUI login manager).
Until a login level is reached there is no interaction in the normal sense. The presence of logging information during boot is not the same as having reached the ability to log in…that boot information is a separate program sharing the same monitor.
You would have to change init and runlevels to change this. Crux may have some sort of runlevel editor or document which could say to skip parts of boot, or even re-order parts…I don’t know what Crux does. But don’t mistake the lack of a program accepting keyboard events for whether or not the keyboard is functioning…until login programs exist you can refer to the saying that “the lights are on, but nobody is home”. You can knock on the door all you want, but nobody will answer if nobody is home (keyboard lights are not changed as on/off by the keyboard…they are changed by software responding to the correct key down/up event).
Thank you for your patience. I will direct other questions to the Crux Linux forum.
There’s a long gap here. It’s likely waiting to try to bring up wlan0 before proceeding.
If that is the case, you should be able to configure that device as being plug-and-play rather than wait-for-boot.
That should make boot go faster.
Hi snarky.
Thank you for the tip.
I will start the wlan0 configuration.
Hi linuxdev and snarky.
The solution is in the sample root file system. I added the 50-firmware.rules rule to Crux /lib/udev/udev.d/. The keyboard is now active.
Quote from 50-firmware.rules:
Thanks you for your time and support