I’ve updated the Boot Options section.
1 Like
Follow-up: turns out I don’t know how to enable a timestamped syslog (or how to look at it afterwards) but I enabled debug messages during boot, and the system turns out to freeze at this message:
initialize_commpage_syscall(): sysenter/sysexit supported
In fact, with debug messages enabled, it never gets past that point at all. Hope this provides a clue. Thank you!
P.S. This is probably unrelated, but I’m getting the impression that the keyboard has become unreliable, more so than it already was due to those crappy keys. Typing feels as if the system was thrashing, though of course it isn’t; there’s no process holding up the CPU or anything. Will test more.
I dont know is this related to beta6, but my t460s has lost its keyboard few times after upgrade, it is completely dead. Keyboard always comes back right after reboot. It never happened with beta5 and nightlies..
I hope it aint hw failure of some sort, but for test i used live linux couple full days and keyboard worked just fine all time. I checked kb connection also. I can shake laptop all i want when running and it doesnt trigger it.
Is there some logs which i could check after it happens? Sound, mouse and network worked last time it happened, so it isnt total freeze..
I’ve been using a USB keyboard with my T480s, but I get into trouble like this with Iceweasel regularly, post B6. Not only no keyboard input, also can’t “select” the text. This is probably not the same problem, just mentioned it in case.
In Terminal
StyledEdit ~/config/settings/kernel/drivers/kernel
almost at the end there is the disabled option of timestamping of syslog
remove the ‘#’ character before the line where this setting is written – to enable the setting as persistent
Save the file -
Of course you can use ‘pe’ or any editor you like to use.
To see the result →
shutdown -r
After the reboot completed …
-- to print the last 100 lines of syslog
tail -100 /boot/system/var/log/syslog
-- to print the last 100 lines of syslog and continue printing into Terminal (-f)
tail -100f /boot/system/var/log/syslog
1 Like
I currently haven’t been having any problems other then, the ones that are related to the things that I have been doing with my os because i’m notorious with screwing with things and I have been using the nightly images
The input devices - as it turned out in several forum threads - can be attached via several buses. The legacy bus was called PS/2 in case built-in keyboards. Now it can be attached via so called ‘i2c’ - a new development.
i2c bus support and devices’ drivers on it are under development in Haiku.
For me in my Dell WST laptop I have a UEFI BIOS setting to select which protocol use the built-in keyboard (I use the AT setting there, which is the oldest and I assume equals PS/2, if I’m not wrong about it, but there are newer and possibly advanved protocols there. However AT is supported in Haiku surely, so I use with it. At input device preferences - in Haiku - this way I know the AT keyboard is the bult-in keyboard of my laptop.)
Also the vendors can be different, e.g. last year a developer added to Haiku tree a new one – introduced drivers for Elantech input devices, besides the well known and widespread Alps - in case laptops. Elantech drivers still not ironed out in every cases - partly it was disabled if I remember well.
So to know exactly what can be the reason behind your built-in keyboards quirks - you may open a ticket about it, where you can provide syslog file and compare to T460s specification related to keyboard - which bus used to attched or at least which vendor’s product was used in that laptop.
In case Thinkpads - you may turn to the thorough Linux wiki pages to find HW details →
1 Like