- This topic has 56 replies, 10 voices, and was last updated May 6-1:31 pm by kultex.
-
Posts
-
kultex
thanks for all of your help – but I was so busy in those days, that I had no time. Now I am back trying to get the Lattepanda working.
Anticapitalista changed the kernel in 19.1 – so mmc is now early seen, but there is an error:
demo@antix1:~ $ dmesg | grep mmc [ 3.782621] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.804379] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 3.894214] mmc1: new high speed SDIO card at address 0001 [ 3.933164] mmc0: new DDR MMC card at address 0001 [ 3.933679] mmcblk0: mmc0:0001 BIWIN 29.1 GiB [ 3.934002] mmcblk0boot0: mmc0:0001 BIWIN partition 1 4.00 MiB [ 3.934374] mmcblk0boot1: mmc0:0001 BIWIN partition 2 4.00 MiB [ 3.934813] mmcblk0rpmb: mmc0:0001 BIWIN partition 3 4.00 MiB [ 3.938445] mmcblk0: p1 p2 p3 p4 [ 443.596564] mmc2: SDHCI controller on ACPI [80860F14:03] using ADMA [ 443.905783] Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit processor_thermal_device fb_sys_fops syscopyarea sysfillrect mei_txe lpc_ich mei sysimgblt intel_soc_dts_iosf intel_gtt thermal button snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_soc_sst_match snd_soc_core fjes snd_compress intel_hid ac97_bus sparse_keymap snd_pcm_dmaengine snd_pcm snd_timer i2c_designware_platform(+) i2c_designware_core snd i2c_core int3406_thermal soundcore spi_pxa2xx_platform int3400_thermal video pinctrl_cherryview acpi_thermal_rel int3403_thermal acpi_pad int340x_thermal_zone nls_utf8 nls_cp437 hid_generic uas usb_storage sdhci_acpi sdhci mmc_block mmc_core overlay battery fotg210_hcd [ 443.922448] mmc2: error -110 whilst initialising SD cardI dont find something with error -110 – so I will try on another machine…..
I will boot different Intel Atom devices with Antix / MX versions with different kernels and upload dmesg
- This reply was modified 3 years, 1 month ago by kultex.
- This reply was modified 3 years, 1 month ago by kultex.
PDP-8
I went through this same thing on TinyCore64 – the devs and I were knocking heads and I think we found a missing component – the LPSS or low-power-sub-system. The recent TC kernel fixed the issue, maybe the following can help antiX..
So frustrating – I use little mini-pc’s too, and you could actually install and boot to an mmc, but soon after boot, the system doesn’t even know it has one! That LPSS didn’t fire up (or keep the mmc powered up) right after boot. Usually it hung up during grub.
I’ve got a couple of Intel Computesticks that had this issue, along with hockey-puck sized wintel boxes.
Check out this thread on Stack – especially the last comment:
https://unix.stackexchange.com/questions/251376/no-dev-mmcblk0-during-boot
Hopefully this helps, and I’m not just contributing noise because I think I have been down this road before. I think the LPSS subsystem is the key.
anticapitalista
antiX kernels already have it compiled;
CONFIG_X86_INTEL_LPSS=yThese threads suggest a work around ie boot cheat
debug_quirks2="0x10000"https://bugzilla.kernel.org/show_bug.cgi?id=109231
- This reply was modified 3 years, 1 month ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Ah, thanks for compiling lpss in. I’ll have to pull out those sticks and pucks and play around.
Kultex – just a warning – not sure if you are also trying to boot from SD, Micro-SD, or eMMC or all three depending.
But just know that some devices for security reasons, have blocked the ability to boot from micro-sd (supposedly because it is so hard to see if someone has jammed one into a dinky computestick etc). For example, my early Computesticks with only 1gb on board, WILL boot linux from micro-sd. But later versions for security reasons, won’t boot from micro-sd no matter what you do. Just throwing that out so you don’t pull your hair out.
Semi-solution – small sticks and the like all have at least one usb / micro usb port from which one can hang at least a passive 2 or 4 way port on, (need keyboard and mouse at least to set up bluetooth initially usually), and boot antiX from USB on that.
And quite frankly, for the use-cases one will put these to, (light stuff), totally ignoring say the onboard emmc as either a boot device or storage device is *kinda* wasteful I guess, but with prices of monster usb sticks to boot and persist on these days – may not enough to get gray hairs over. But I get it – just throwing this out so you can get your need taken care of at the studio asap.
On the laptop with Celeron N3050 CPU both mmcs (internal + sd/card) are working ok with AntiX 19.1
On the Lattepanda with Atom x5-Z8300 only MX-Linux is ok
demo@mx1:~ $ dmesg | grep mmc [ 3.129875] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.150695] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 3.171314] mmc2: SDHCI controller on ACPI [80860F14:03] using ADMA [ 3.199870] mmc1: new high speed SDIO card at address 0001 [ 3.228371] mmc0: new DDR MMC card at address 0001 [ 3.229203] mmcblk0: mmc0:0001 BIWIN 29.1 GiB [ 3.229717] mmcblk0boot0: mmc0:0001 BIWIN partition 1 4.00 MiB [ 3.230242] mmcblk0boot1: mmc0:0001 BIWIN partition 2 4.00 MiB [ 3.230470] mmcblk0rpmb: mmc0:0001 BIWIN partition 3 4.00 MiB, chardev (246:0) [ 3.235546] mmcblk0: p1 p2 p3 p4 [ 3.734646] mmc2: new ultra high speed SDR104 SDHC card at address aaaa [ 3.735423] mmcblk2: mmc2:aaaa SL32G 29.7 GiB [ 3.737788] mmcblk2: p1I am at the moment struggling with the kernel – whats the easiest way to get the MX-kernel to Antix-19.1 live USB?
- This reply was modified 3 years, 1 month ago by kultex.
anticapitalista
Which version of MX linux and which kernel?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
MX 19.1 with the original kernel from the iso – it was 4.19. something…
its the machine of my woman – so I can just work, when she does not need it…
@PDP-8
I will boot from USB, because my Atom have all 3.0 USB and I want to put /home to the SD-Card. But I am interested, to make an Iso, that boots also from internal eMMC, to get new life for those 1 or 2 GB Windows tablets.
To use internal eMMC for /home is not recommended, because if the eMMC or the device crashes, your data is lost……
Ok, call me impressed by booting antiX 19.1 on several Computesticks with the default 4.9 antiX kernel, no freezes on my Atoms and space-fm easily sees the internal mmc, so suppose I could do an install to those if I wanted. Nice job devs!
I dig the repurposing thing, but as I get lazy as I get older, I just leave the emmc alone, and boot via usb. Plus since I also play with SBC’s, like Armbian supported boards, I do the boot to ram on sdcards, and sometimes need a windows tool to get REALLY formatted properly, like the sd-card associaton formatter (currently at 5.01 – it can reach the internal controllers, unlike generic o/s formatting does.)
https://www.sdcard.org/downloads/formatter/
Hmm… I’ll have to put an sd-card into a usb-reader, do a live-usb creator to the sd-card now hiding as usb, and then remove and reboot from the sd-card. And boot antix persistence to ram – modern sdcards should last quite awhile that way.
Anyway, I’m getting a bit OT, but I think antiX makes a GREAT distro for the small little intel / amd boxes now matter how one wants to boot or operate it.
anticapitalista
On the laptop with Celeron N3050 CPU both mmcs (internal + sd/card) are working ok with AntiX 19.1
On the Lattepanda with Atom x5-Z8300 only MX-Linux is ok
demo@mx1:~ $ dmesg | grep mmc [ 3.129875] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.150695] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 3.171314] mmc2: SDHCI controller on ACPI [80860F14:03] using ADMA [ 3.199870] mmc1: new high speed SDIO card at address 0001 [ 3.228371] mmc0: new DDR MMC card at address 0001 [ 3.229203] mmcblk0: mmc0:0001 BIWIN 29.1 GiB [ 3.229717] mmcblk0boot0: mmc0:0001 BIWIN partition 1 4.00 MiB [ 3.230242] mmcblk0boot1: mmc0:0001 BIWIN partition 2 4.00 MiB [ 3.230470] mmcblk0rpmb: mmc0:0001 BIWIN partition 3 4.00 MiB, chardev (246:0) [ 3.235546] mmcblk0: p1 p2 p3 p4 [ 3.734646] mmc2: new ultra high speed SDR104 SDHC card at address aaaa [ 3.735423] mmcblk2: mmc2:aaaa SL32G 29.7 GiB [ 3.737788] mmcblk2: p1I am at the moment struggling with the kernel – whats the easiest way to get the MX-kernel to Antix-19.1 live USB?
If you want to try the kernel used by MX-19.1,
apt install linux-headers-4.19.0-6-amd64 linux-headers-4.19.0-6-common linux-image-4.19.0-6-amd64-unsignedYou then need to remaster and afterwards (before rebooting) use live-usb-maker to change default kernel to the one used in MX.
BTW have you tried a 4.19 antiX kernel?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I did this, but I end up all the time with a blank screen, as soon as I boot. First I thought, I am to stupid the remaster tool, but no way, whatever I tried. With 4.19 antix kernel no problem to remaster.
In the meantime I am a step further. Its this problem: https://bugzilla.kernel.org/show_bug.cgi?id=102791
So the question is, what is the difference between the MX-4.19 kernel, which is pure debian and the 4.19 antix kernel, tht causes that problem?
I was wrong – the remaster tool does not work with GPT-mode (UEFI-mode). I can boot on the Lattepanda only, when I flash the antiX image with rufus in GPT-mode, because I am not able to turn off uefi mode on the Lattepanda.
anticapitalista – maybe you can provide a iso with 4.19 antix kernel for testing…..
in the meantime, I think, there is a way on the lattepanda, that I can boot it warm – I have to flash the bios back to the original bios….
anticapitalista
anticapitalista – maybe you can provide a iso with 4.19 antix kernel for testing…..
antiX-base with 4.19.100 kernel (64 bit)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
@anticapitalista !!! thx a lot !!!
root@antix1:/home/demo# dmesg | grep mmc [ 2.050987] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 2.064586] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 2.131310] mmc1: new high speed SDIO card at address 0001 [ 2.145115] mmc0: new DDR MMC card at address 0001 [ 2.146523] mmcblk0: mmc0:0001 BIWIN 29.1 GiB [ 2.147511] mmcblk0boot0: mmc0:0001 BIWIN partition 1 4.00 MiB [ 2.148483] mmcblk0boot1: mmc0:0001 BIWIN partition 2 4.00 MiB [ 2.149244] mmcblk0rpmb: mmc0:0001 BIWIN partition 3 4.00 MiB, chardev (240:0) [ 2.155375] mmcblk0: p1 p2 p3 p4 [ 14.456632] mmc2: SDHCI controller on ACPI [80860F14:03] using ADMA [ 15.124393] mmc2: new ultra high speed SDR104 SDHC card at address aaaa [ 15.126184] mmcblk2: mmc2:aaaa SL32G 29.7 GiB [ 15.128379] mmcblk2: p1now I am able to try to get /home on the SD-card
- You must be logged in to reply to this topic.
