Tiny Core Linux
General TC => General TC Talk => Topic started by: Taarka on February 23, 2017, 05:25:32 AM
-
Hi!
Preface
The PC I wanted to have TC on is an old AMILO Mini Ui 3520 notebook, which has a faulty built-in keyboard. There are only two USB ports on it so to have an external mouse (for convenience) and a working keyboard, I bought a wireless keyboard-mouse combo USB dongle (Logitech K220).
The problem
The keyboard part of the peripheral works without a problem, but the mouse has a weird issue. I can move the pointer and click on UI elements that expect a single-click interaction. However when I try to navigate the path selector dialog (where I have to double-click) it does not respond. It's like the second event is being dropped.
At first I ignored the problem and wanted to browse the filesystem in terminal, but after opening one I noticed that something is very wrong. If I click inside the terminal a question-mark character will appear. I guess some non-ASCII keyboard key event is fired along with the mouse event.
Troubleshooting
- I tried using a generic wired USB mouse and keyboard and those work without a problem.
- I removed the batteries from the keyboard part, but the mouse still did not work as expected. (I wanted to rule out some stuck key or similar issue)
- The keyboard and mouse work perfectly on other PCs (Debian, Arch and Windows), so the hardware is not at fault.
- The touchpad works correctly regardless of the peripherals being connected or not.
- I have not found a report/question about an exactly same issue online, but I've tried a few things suggested for similar problems: legacy USB setting in BIOS, psmouse.proto=imps...
- I wanted to see what events X is processing, but there is no xev utility...
Conclusion
I've had my fair share of hardware compatibility issues using a variety of distors, but never have I expected to get stuck at a not working "basic" mouse. I don't know what or how to debug to get ahead.
I'm looking forward to hearing some insight or any ideas really.
Thanks in advance,
Taarka
-
What version and architecture of tinycore are you using?
Are you using Xvesa, Xfbdev or Xorg?
-
Are you using Xvesa.tcz? using Xorg-7.7.tcz instead may help.
xev is provided by Xorg-7.7-bin.tcz.
-
I've downloaded the CorePlus version of TinyCore this morning (7.2). It's the x86 architecture. So maybe it's not apparent from my original post, but I'm very new to TC. I wanted to fiddle around with the install and remastering tool to get a grip on how things work.
Xvesa is the first extension that gets loaded on boot, but I'm not sure how to check what else TC has loaded... /var/log is virtually empty.
How can I instruct TC to load Xorg instead of Xvesa?
-
To download
tce-load -w Xorg-7.7
To make it the default, you can either use the Apps GUI or edit
/etc/sysconfig/tcedir/onboot.lst
Then reboot.
To learn how TC works: http://tinycorelinux.net/book.html
-
I exited to prompt and
tce-load -wi Xorg-7.7
startxnow mouse works correctly. Wow was this simple yet not evident at all? (maybe only for me...)
I'll keep the book close from now on as well. Many thanks!
Taarka
-
Xorg is smarter than Xvesa.
-
..but much, much bigger ;)