Tiny Core Linux
Tiny Core Base => CorePlus => Topic started by: micka on January 27, 2018, 03:13:46 AM
-
Hi !
Want to give a try to TC on my ASUS X205TA.
After downloading "TinyCore-current.iso" and "burn it" on a usb stick (unetbootin), nothing happen at startup :o
I noticed that TC is not like other distrib, and also that ASUS X205TA need a "special" 32bits boot file :
https://openclassrooms.com/forum/sujet/guide-installer-linux-sur-asus-x205ta
So I create /efi/boot/bootia32.efi and now I have a grub> command line at boot :)
I type :
1. set root=(hd0,1) // My disk and partition file where TC is installed by unetbootin
2. linux /ubnkernel
3. initrd /ubninit
4. boot
TC boot and after few seconds, it freeze :
(https://image.noelshack.com/minis/2018/04/6/1517040565-img-20180127-081040.png) (https://www.noelshack.com/2018-04-6-1517040565-img-20180127-081040.jpg)
What I'm I doing wrong ?
Thx for your help.
;)
-
It does not look frozen, it looks like a normal text boot with verbose messages. Try pressing enter.
-
Nothing happen when pressing enter or typing something.
Just like if there is no keyboard.
Only thing that "doing something" is when I remove/insert the usb stick. It prints a dmesg like :
usb 1-2.2: USB disconnect, device number 4
usb 1-2.2: new high-speed USB device number 5 using xhci_hcd .....
-
Just tried to connect an external usb keyboard.
It's recognise and when pressing enter, I got a prompt (tc@box:~$) :)
Seems the problem is that TC don't recognise the ASUS X205TA keyboard...
Someone can help on this ?
-
Problem with ASUS X205TA keyboard driver.
https://patchwork.kernel.org/patch/8734321
How can I apply it in TC ?
-
You could set up the tinycore kernel source, apply the patch, recompile the kernel and remaster to include the patched driver in rootfs.gz or core.gz
-
That patch is so old, it's already included in both tc 8.x and 9.x kernels. Please check if hid_asus is listed in lsmod output; if not, run "sudo modprobe hid_asus".
-
hid_asus not listed in lsmod.
I tried sudo modprobe hid_asus :
modprobe: module hid_asus not found in modules.dep
How can I add it ?
Thx
-
Tried that : https://github.com/vlasenko/hid-asus-dkms#asus-hid-fte100-dkms-driver (https://github.com/vlasenko/hid-asus-dkms#asus-hid-fte100-dkms-driver)
but : dkms not found, aborting...
-
Checking modules.dep return "nothing" :
cat /lib/modules/4.8.17-tinycore/modules.dep | grep hid_asus
and in kernel/drivers/hid,
ls | grep asus
return "nothing"
Seems that patch has been included in Kernel version 4.10 or later... (https://github.com/vlasenko/hid-asus-dkms (https://github.com/vlasenko/hid-asus-dkms))
-
Juanito, how can I do that (tutorial) ?
Sounds fun :D
-
That's a "-" not an"_" - using corepure64 9.0alpha2:
$ cat /lib/modules/*/modules.dep | grep hid-a
kernel/drivers/hid/hid-aureal.ko.gz:
kernel/drivers/hid/hid-axff.ko.gz: kernel/drivers/input/ff-memless.ko.gz
kernel/drivers/hid/hid-a4tech.ko.gz:
kernel/drivers/hid/hid-appleir.ko.gz:
kernel/drivers/hid/hid-alps.ko.gz:
kernel/drivers/hid/hid-asus.ko.gz:
kernel/drivers/hid/hid-accutouch.ko.gz:
kernel/drivers/hid/hid-apple.ko.gz:
-
First of all, thanks for your attention ;)
On CorePlus and TinyCore 8.x, no hid-asus nor hid_asus.
Tried corepure64 9.0alpha2 and effectively hid-asus is present.
As suggested by curaga, at startup, no hid_asus in
lsmod | grep asus
So, I run
sudo modprobe hid_asus
and
sudo modprobe hid-asus
Both command return nothing and my keyboard still not recognize.
When I check
dmesg | grep asus
No message on th fact that hid-asus or hid_asus was loaded.
What am I doing wrong ?
-
'seems to work for me:
$ sudo modprobe hid-asus
$ lsmod | grep hid
hid_asus 12288 0
-
Sorry, YES Juanito, I got this too...
But my keyboard still not be recognized... and nothing in dmesg...
-
For info, I just tried a live Debian kernel 4.9.0-4-amd64 and keyboard ok
-
Ok, so TC's not debian, but have you tried using any of these boot parameters alone or together temporarily (ie, pressing TAB at the initial boot to change / add them...
nolapic <--- usually my first light duty option
noapic
noacpi <----- overkill usually. Not recommended unless you KNOW you need it.
acpi_os= <--- yep, nothing after the = sign
acpi_os=\"Linux\" <---- yep, all that escaping and quotes are in the proper place...
(to see if the acpi_os Linux is accepted, also use "syslog" as a boot parameter too and look at /var/log/message
There are many more generic linux options you can try. Those above are my most go-to options for cranky hardware. Just throwing this out in case it helps.
-
My apologies for some errors here...
I inadvertently dropped the "i" from the acpi lines. Thus one of the above lines should read:
acpi_osi=
And, as tested again with TC none of that fancy escaping is needed either if you add a specific osi like:
acpi_osi=Linux
And if you also use the syslog kernel parameter at boot time, the results can be found in /var/log/messages. I left off the trailing s in the filename.
Sorry about that - had to clean it up. I'll direct a generic query about this in a different thread....