Iso updated with kernel rebuild include MMC_SDHCI_ACPI / MMC_RICOH_MMC, hope fix disk issue.
https://mirror.slitaz.org/iso/current/slitaz-current-core.iso
Iso updated with kernel rebuild include MMC_SDHCI_ACPI / MMC_RICOH_MMC, hope fix disk issue.
https://mirror.slitaz.org/iso/current/slitaz-current-core.iso
Bonsoir shann,
just to say thank you so much. I just tried your new rebuilt current-core.iso by extracting the iso, placed the rootfs.gz and the vmlinuz file into my bodhi boot folder. booted into the grub bootloader and put the necessary commands into.
I am really impressed. I got the mmc cards and the usb recognized. your prior mentioned method for activating the wifi module, I could start the internet and now I am writing from the booted SliTaz current.
It is a pleasure to get step by step into this amazing system.
Now I will try to get further to get all my other wanted stuff running.
But what would you recommend. Should I stay now with this current version? Should I go for the current64 version, as my processor is a 64bit processor? Is the roling version with the 3.16.55 Linux kernel still recommended?
The mouse still falls asleep after a view seconds when I do not move it or don't press any button on the keyboard. There is no sound yet and the touch screen doesn't work. But at the moment, this is nor the most important thing.
I'm so glad. You really do a fantastic job. How can I show my gratitude for all the efforts?
Hi aniguenni,
It's pleasure to read this :)
Thanks a lot, for me that you can use SliTaz on your device is enought.
At the moment, not all work, no sound and touch screen but it's just question time ;).
About current, current64 or rolling question
- rolling use old stack but works very weel
- current/current64 use more recent stack and have 64bits full support.
current version is based on rolling when i create new wok for upgrade stack.
Unfortunately we can't upgrade smooth rolling, when i try to upgrade rolling with current repository, break many thinks.
current and current64 (full 64bit) work for daily use but for me need more polish again.
Infact at least for current can't be boot under 768Mo of ram for liveCD (no problem to run with 128Mo on disk) compare to rolling/4.0, of course current include more recent stuff but i see as bad news.
I work also to generate 5in1 iso for current, base need 128Mo to be boot correctly :/
For sound and touchscreen, i think work with bodhi right ?
can you please post dmesg and lsmod return command in file and add it as attachments ?
thanks
dmesg > dmesg_bodhi
lsmod > lsmod_bodhi
lspci > lspci_bodhi
Bonsoir shann,
thank you again for your quick replys.
Attached you'll find the relevant outputs ...
Hi aniguenni,
Thanks very much, very interesting, on lsmod_bodhi i see lot of modules we don't have.
First pass i notice and add this :
`
+CONFIG_INPUT_AXP20X_PEK=m
+CONFIG_AXP20X_POWER=m
+CONFIG_AXP288_FUEL_GAUGE=m
+CONFIG_MFD_AXP20X=m
+CONFIG_MFD_AXP20X_I2C=m
+CONFIG_SND_SOC_TOPOLOGY=y
+CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m
+CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m
+CONFIG_SND_SOC_SOF_TOPLEVEL=y
+CONFIG_SND_SOC_SOF_PCI=m
+CONFIG_SND_SOC_SOF_ACPI=m
+CONFIG_SND_SOC_SOF=m
+CONFIG_SND_SOC_RL6231=m
+CONFIG_SND_SOC_RT5640=m
+CONFIG_SND_SOC_RT5645=m
+CONFIG_EXTCON_AXP288=m
+CONFIG_KXCJK1013=m
+CONFIG_AXP288_ADC=m
`
Continue to read lsmod / dmesg / lspci bodhi to not miss modules.
I see on dmesg current, that firmware miss for intel_sst_acpi firmware/install/lib/firmware/intel/fw_sst_0f28.bin.
I check and see not include on any firmware-* packages, think if firmware missing, audio not work correctly :/.
I can create firmware-intel that include all firmware from intel folder but size is big 56.5M.
aniguenni,
I update iso on my space for slitaz-current64-core64-grub2.iso.
https://people.slitaz.org/~shann/slitaz-current64-stuff/slitaz-current64-core64-grub2.iso
Normally include necessary modules, hope better support.
Hi aniguenni,
Hope you fine.
This week-end i discover a strange feature, for a friend's parents i install SliTaz current64 on middle computer i reconditionned (Pentium G630, 4Go DDR3, 300Go HDD).
They use mouse and keyboard, both are in usb, after few seconds, disabled, need to type or click on mouse to come back.
After search see kernel autosuspend usb port to power save.
I need to add usbcore.autosuspend=-1
on GRUB_CMDLINE_LINUX_DEFAULT line to disable this, in case unnecessary to pc tower ;).
I remind your issue and think it's same.
Edit /etc/default/grub, adjust line and regenerate grub.cfg file.
For liveCD when you have selected language edit with tab "SliTaz Live" entry to add usbcore.autosuspend=-1
at end of line
In live mode, could be adjust directly with this command
echo -1 >/sys/module/usbcore/parameters/autosuspend
Dear Shann,
first of all, i'm sorry for the delay of my answer. On the weekend I was playing around with your last created iso. I was impressed, that we got such a big step ahead by recognizing my baytrail board :-)
For to boot this iso I had to change the bootia32 again. But now I can boot from ventoy usb stick in grub mode.
It takes a while, till the boot starts. But this was almost the same as before.
The system works quite well. Even the touch screen now gets recognized.
What I still have to figure out is to get the sound to work. The battery doesn't get recognized. And the backlight of the screen I would like to adjust (maybe with RandR?).
Funny - the more I play again with this amazing os, I remember, what I did on tne former SliTaz-4.0 and cooking many years ago ;-)
You really do a great job and I'm absolutely impressed of your work.
Your last hint on your last post is exactly what I have had. With adding the commands above there are no semi-"freezes" anymore. Thank you again for all of your activity and spendig so much time to help me so much. Without your assistance and help, I never ever would get to this result.
And I have so much fun to play with SliTaz (like DistroWatch says "put the fun back into computing"). That's what I feel now :-D
The system runs very smooth and speedily.
So after you created the last iso ,... does it mean, I should stay with the 64bit version because of better support for the future?
P.S.: sorry for my bad english, but my french is even worse, infact not existing :-)
Hi aniguenni,
No problem, we have each own life :).
I can't blame you, myself my english is not perfect.
Yes, once we found miss modules and add it, it's easier to run correctly on device.
Nice to read systemw work and touch screen recognized, for battery and backlight need to check maybe modules missing again.
I remember, HGT, Ceel and alanyih already report that backlight not work on current.
Thanks a lot, already say knowledge should be share, i remember when discover SliTaz with 3.0 version in 2011.
I'm not do better support for x86_64 or 32 bit version of current, it's same.
At time i don't update kernel config, linux-slitaz.config need to be sync with linux-slitaz.config64.
But if your device support and run smoothly with 64bits current version, i recommend to use it.
At least, avoid Y2038 bug :P, it's on my todo to do work for Y2038 on 32bits version
You must log in to post.