Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: jimmyjohn on July 06, 2019, 07:30:12 AM
-
I am trying to boot the standard Tiny Core 10.1 image from my mini-PC which only has 64bit UEFI available as a boot option. I am able to get it to boot, but once booting is complete I only see a blank/black screen with an underscore in the top left corner. From this screen I am not able to input any commands or take any actions except that by pressing Ctrl-Alt-Delete twice I am able to begin and then watch the text based shutdown process.
Is it possible to correctly boot the 32bit version from a 64bit EFI? If so, what should I try next to get it to work correctly?
-
...
Is it possible to correctly boot the 32bit version from a 64bit EFI? If so, what should I try next to get it to work correctly?
Hello jimmyjohn
Of course it is!!
64 bit EFI is the correct way to install EFI regardless of what OS the boot manager is booting
(https://uploads.tapatalk-cdn.com/20190706/56c3f5610a271cdb707c1566139c5fba.jpg)
This screenshot shows the 64bit EFI and TC 10.1 32 bit system I’m currently booted to
You should create a new installation as in the code below, not copy a bootx64.efi bootloader from another system and expect it to work.
I never have any problems with EFI installations because I use this command to ensure a correct creation and installation of bootx64.efi bootloader
sudo grub-install --target=x86_64-efi --boot-directory=/mnt/sdc2/EFI/BOOT --efi-directory=/mnt/sdc2 --removable
Here's a basic grub2 config file with Home, OPT and TCE persistance
insmod part_gpt
insmod part_msdos
insmod fat
insmod ext2
loadfont unicode
insmod efi_gop
insmod efi_uga
insmod font
insmod gfxterm
set gfxmode=auto
set gfxterm_font=unicode
set gfxpayload=keep
terminal_output gfxterm
#Timeout for menu
set default=0
set timeout=5
menuentry "*** TC-10-Tinycore (on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz noswap tz=GMT loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc10-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"
initrd /boot/rootfs.gz /boot/modules.gz
}
menuentry "Windows 10" --class windows --class os {
search --fs-uuid --no-floppy --set=root DE2F-EF34
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
Additionally, are you attempting to boot from an ISO or a real installation?
Sent from my iPhone using Tapatalk
-
I 'burned' the ISO to a USB and am booting from that. It works when I burn and boot CorePure64, but it does not work when I do the same with the standard TC image. However, even with the CorePure64 image, I have been using the bootx64.efi from the most recent Ubuntu Puppy Linux (bionic) - (EDIT: because the bootx64.efi from the CorePure64 image does not work for me on any of my machines). I have not tried installing it manually yet, I suppose I will give it a try.
-
That sounds like an incompatibility with Xvesa. When you get to that underscore, see if ctrl-alt-backspace helps. Alternatively boot with the "text" bootcode.
Corepure64 uses Xfbdev, and you can also install Xorg as the X server.
-
ctrl-alt-backspace didn't work. I am, however able to boot into the textbased terminal.
-
In my mind this “burn to a usb” installation is not valid.
But putting that aside because you can boot to a command line..
What is the output of “showbootcodes” ?
And what is the result of
tce-load-i Xvesa ?
Assuming a network connection, try installing
Xorg
tce-ab search Xorg-7.7
or
tce-load -wi Xorg-7.7
And let us know results
Sent from my iPhone using Tapatalk
-
Since @curaga suggested an xvesa incompatability, I swapped it out for xfbdev and updated onboot.lst accordingly. That fix worked! I now have a gui TC desktop with the 32bit variant.
My next issue is to get WiFi working since I do not have Ethernet on this device. I had it working in CorePure64, but I think I must have missed one or more of the dependencies when getting them for the 32bit version. ** EDIT: I just confirmed, I am not missing any dependencies from the .tree file and made sure that the firmware is loaded first in the order of things**
Then my last issue before I will be able to frugal install to the Mini-PC is to figure out what I need to get TC to see and be able to mount both the onboard eMMC as well as the built in memory card reader; right now it isn't detecting either!
Thanks for your help so far! I suppose I may need to start a separate thread on the eMMC issue, but if not, any additional help would be greatly appreciated. The only thing I have tried on that so far was to boot with the waitusb=5 option
BTW, in case you still want it the output of showbootcodes is: "BOOT_IMAGE=/boot/vmlinuz loglevel=3 cde vga=791"
That output matches what I have in grub.cfg
-
...
BTW, in case you still want it the output of showbootcodes is: "BOOT_IMAGE=/boot/vmlinuz loglevel=3 cde vga=791"
That output matches what I have in grub.cfg
We still need to know how you
“burned the image to usb”
That is not a normal installation.
More importantly the only reason to use a CDE bootcode is if you’re booting from a CD or an ISO
Also missing is waitusb bootcode
In a typical frugal installation to a USB the extensions directory must be tce not cde and the bootcodes will reflect this along with waitusb=
My view is that almost all problems result from the method of installation.
Sent from my iPhone using Tapatalk
-
I haven't actually installed anything yet, I am just booting from a live USB and am trying to get things to work before I proceed with an installation. I basically just copied and pasted the contents of the ISO to the USB and have been booting it.
-
Copying the contents of the ISO is in fact one method of installing. But know that when you copy the contents of cde directory you must change the name to tce otherwise TC will not find or load your extensions
Sent from my iPhone using Tapatalk
-
Okay. Well, now I am learning! Thanks.
Any ideas on the WiFi issue? I can't find any differences between the functioning 64bit and non-functioning 32bit installs. They both have wifi.tcz with all dependencies as well as firmware-iwlwifi.tcz, and yet the x64 version instantly finds wlan0 where 32bit says it can't find a wlan device.
The specific wlan chip I have is the intel 7265, I know there is a separate firmware for the 7260, but that one didn't work when I tried it, just the normal iwlwifi did.
-
You would probably find the CoreBook http://tinycorelinux.net/corebook.pdf valuable reading..
Look up "Mount Mode" section 1.8 in particular
-
Okay. Well, now I am learning! Thanks.
Any ideas on the WiFi issue? I can't find any differences between the functioning 64bit and non-functioning 32bit installs. They both have wifi.tcz with all dependencies as well as firmware-iwlwifi.tcz, and yet the x64 version instantly finds wlan0 where 32bit says it can't find a wlan device.
The specific wlan chip I have is the intel 7265, I know there is a separate firmware for the 7260, but that one didn't work when I tried it, just the normal iwlwifi did.
First you have to sort out the installation.
When extensions and their dependencies can be reliably saved and found when needed then you can install required extensions and know that they will be available on every reboot.
When troubleshooting Wifi installations it's best to review the output of " dmesg " command. You can upload the output file here
dmesg > ~/dmesg.txt
This will create a file dmesg.txt in your home directory which you can upload here
-
jimmyjohn,
In most cases you must install Grub2 EFI from the 64bit version
An important tip when installing Grug2; boot to the corepure64 installation, mount the grub2 install partition and load the grub2-multi.tcz extension. Then install via this command
sudo grub-install --target=x86_64-efi --boot-directory=/mnt/sdc1/EFI/BOOT --efi-directory=/mnt/sdc1 --removableObviously change the paths (sdx1) as appropriate to your system.
-
Here is the file you requested kind sir :-) In the meantime, I have attempted the adjustments you recommended in regards to proper installation,
but have thus far been unsuccessful in booting beyond the command line and now I have it up and running properly with the tce directory. the issues with wifi not working and eMMC not showing remain. I will keep looking over the documentation and working on it while I wait for further assistance.
Thanks again!
-
Hi jimmyjohn
I noticed you're still bootiing with the cde bootcode??
Kernel command line: BOOT_IMAGE=/boot/vmlinuz loglevel=3 cde vga=791
What is the ouput of
realpath /etc/sysconfig/tcedir
See section 10.1 of the corebook
Also when you can access the wifi extension and all it's dependencies, load it
tce-load -i wifi
then
dmesg > ~/dmesg.txtagain to check which firmware the wifi module is really attempting to load
-
The output of showbootcodes is now: "BOOT_IMAGE=/boot/vmlinuz loglevel=3 waitusb=5 TCE vga=791"
tce-load -i wifi result is: "wifi is already installed!"
And I have attached the new dmesg output
-
The output of showbootcodes is now: "BOOT_IMAGE=/boot/vmlinuz loglevel=3 waitusb=5 TCE vga=791"
Great [emoji106]
But please see section 10.1 of the corebook
tce=sdb1 (Lower case) is acceptable
Then when you’ve fixed up tce bootcode
What is the ouput of
realpath /etc/sysconfig/tcedir
Sent from my iPhone using Tapatalk
-
Also, at first glance I don’t see any registered Wi-Fi device in dmesg. But will check thoroughly after returning home
I’m guessing Wifi is disabled? Try “fn 12” key on keyboard
And download and install pci-utils.tcz extension
Then run this command and upload here
lspci
Sent from my iPhone using Tapatalk
-
realpath is
/mnt/sda1/tce
Initially I tried to use the UUID for the tce directory, as specificed in 10.1 of the corebook, but it didn't work for some reason. Since it is technically valid to not have a tce entry (just potentially slower), I removed it altogether for now.
I have attached the results of lspci. The very last line shows the network controller (Intel 7265). So clearly TC can see it is there. I don't have a keyboard with a function key other than my laptop keyboard, so that one is a bit difficult for me but I don't know why it would be turned off for x86 but not when I boot x64.
-
Ok great
So the driver is not being installed for some reason.
check that wireless-4.19.10-tinycore which contains the driver (iwlwifi I believe) is being loaded
ls /usr/local/tce.installed | grep wireless
-
The firmware extension is firmware-iwlwifi.tcz
this extension should be loaded first, then wifi.tcz which in turn loads wireless-4.19.10-tinycore
-
Some maintenance, while connected via Ethernet first open APPS
then go to Apps menu > Maintenance > Dependencies & Deletions
Then from the Dependencies menu > select "update dep files"
then select "Fetch Missing Dependencies"
In Apps > Maintenance > "Onboot Maintenance"
Check onboot.lst make sure that from the top, firmware-iwlwifi extension is listed before wifi, else fix that
reboot
Then you should get something like this
tc@box:~$ ls /usr/local/tce.installed | grep wireless
wireless-4.19.10-tinycore
wireless_toolstc@box:~$ dmesg | grep iwlwifi
[ 22.843881] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[ 22.846639] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8000C-36.ucode failed with error -2
[ 22.846640] iwlwifi 0000:03:00.0: Falling back to syfs fallback for: iwlwifi-8000C-36.ucode
[ 22.940196] iwlwifi 0000:03:00.0: loaded firmware version 36.9f0a2d68.0 op_mode iwlmvm
[ 22.961629] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[ 23.041719] iwlwifi 0000:03:00.0: base HW address: f4:8c:50:6b:a6:7a
-
I have them listed to load in that order in onboot.lst, but for some reason they weren't loading and neither the firmware nor the wireless-4.19.10-tinycore were showing. However, I downloaded those tcz's once more and deleted and replaced the previous ones and they are all loading and showing up, but wifi is still not finding the wlan. I am going to try and re-download all of the dependencies as well and see if that makes a difference.
I don't have Ethernet on the device :-( I am having to download the tcz's manually
-
I am going to try and re-download all of the dependencies as well and see if that makes a difference.
I don't have Ethernet on the device :-( I am having to download the tcz's manually
Yes this is the problem. You need all *.tcz files and *.tcz.dep file if they exist as listed in
http://repo.tinycorelinux.net/10.x/x86/tcz/wifi.tcz.tree
good luck
-
Well, I re-downloaded and confirmed all of them. Same problem. So I booted leaving all of them off of the onboot.lst, then I manually installed them in dependency order using tce-load, and now it is working! It seems that the 64bit OS automatically loads the dependencies as long as they are in the optional directory, however, the 32bit version does not and needs them each to be listed explicitly.
Anyway, on to the next issue! How to access the eMMC!
Thanks for your help thus far!
-
There's no such difference between 32 and 64-bit. It sounds like a dep file was not downloaded somewhere, a common oversight when downloading manually.
-
Hi jimmyjohn
Here is the tree file with its entries sorted alphabetically and duplicates removed:
tc@box:~/zz$ awk '$1=$1' wifi.tcz.tree | sort -u
libiw.tcz
libnl.tcz
ncursesw.tcz
openssl.tcz
readline.tcz
wifi.tcz
wireless-4.19.10-tinycore.tcz
wireless_tools.tcz
wpa_supplicant.tcz
tc@box:~/zz$Make sure you have both the .tcz files and the .tcz.dep files for each extension that has one.
-
Well, I re-downloaded and confirmed all of them. Same problem. So I booted leaving all of them off of the onboot.lst, then I manually installed them in dependency order using tce-load, and now it is working!
We have been trying to impress upon you that there are many dependencies to download. By now you're probably getting the idea that it's not just having the dependencies, but equally important (if not more so) to have every extension's dep list as well. without the dep lists tce-load will not know to install any deps and herein lies your problem.
Thanks to Rich for kindly sorting the tree file
This is the full list (of 14 files not counting the firmware file) required to get wifi operational, note that some extensions have a " .dep " name extension without these tce-load will not load any of wifi.tcz's dependencies. This is the underlining problem you're experiencing.
libiw.tcz
libnl.tcz
ncursesw.tcz
openssl.tcz
readline.tcz
readline.tcz.dep
wifi.tcz
wifi.tcz.dep
wireless-4.19.10-tinycore.tcz
wireless-4.19.10-tinycore.tcz.dep
wireless_tools.tcz
wireless_tools.tcz.dep
wpa_supplicant.tcz
wpa_supplicant.tcz.dep
1. You can download all the required files listed above. Or If this seems like a daunting task! Then you can
2. download the CorePlus.ISO and copy the needed files from it's cde/optional store.. Or
3. you can connect to the internet somehow and use APPS (the application manager) to update deps as described in an earlier post here.
When you have all the required files in place you can simply
tce-load -i firmware-iwlwifi.tcz
tce-load -i wifi.tcz
then run wifi from either the icon or from the command line
sudo wifi.sh
good luck
-
Thank you both for the recommendations. I was ale to complete this last night and get everything working for WiFi. Now that I can use the apps manager, I don't have to do this manually anymore :-)
Would either of you have any ideas about next steps to take to get TC to recognize the built in eMMC and SD card reader?
I know from the computer's EFI documentation that the eMMC is an embedded bootable device, but the SD card slot is not. I manually installed TC to the eMMC by copying the install from the USB to the eMMC, but I had to use a different bootable linux distro to accomplish this since TC is not showing the eMMC as mountable. Even after that, booting takes me only to a terminal. I have not tried anything with the sd card reader yet, but have started researching.
-
...
Would either of you have any ideas about next steps to take to get TC to recognize the built in eMMC and SD card reader?
I know from the computer's EFI documentation that the eMMC is an embedded bootable device, but the SD card slot is not. I manually installed TC to the eMMC by copying the install from the USB to the eMMC, but I had to use a different bootable linux distro to accomplish this since TC is not showing the eMMC as mountable. Even after that, booting takes me only to a terminal. I have not tried anything with the sd card reader yet, but have started researching.
This question should really be in its own thread, but....
While an eMMC and an SD card is technically not a raw MTD let us know how you get on by installing either of these kernel modules
mtd-4.19.10-tinycore.tcz or
mtd-4.19.10-tinycore64.tcz
Remember this distribution is minimalist and modular, allowing you to build as you like it
Sent from my iPhone using Tapatalk
-
Hi coreplayer2
... This is the full list (of 14 files not counting the firmware file) required to get wifi operational, note that some extensions have a " .dep " name extension without these tce-load will not load any of wifi.tcz's dependencies. This is the underlining problem you're experiencing.
libiw.tcz
libnl.tcz
ncursesw.tcz
openssl.tcz
readline.tcz
readline.tcz.dep
wifi.tcz
wifi.tcz.dep
wireless-4.19.10-tinycore.tcz
wireless-4.19.10-tinycore.tcz.dep
wireless_tools.tcz
wireless_tools.tcz.dep
wpa_supplicant.tcz
wpa_supplicant.tcz.dep
...
Actually, that should be 13 files, there is no wireless-4.19.10-tinycore.tcz.dep file.
-
Hello Rich, You’re right !! but 13 is unlucky and 14 will make him look harder [emoji12]
Sent from my iPhone using Tapatalk
-
I have installed both of the MTD tcz's and have rebooted the computer with them loaded. After doing that I still am only seeing the USB thumb drive as a mountable drive. Also, if you think I should start a new thread for this issue, I am happy to do so, I just didn't want to clutter the forum so I just kept going.
-
I have installed both of the MTD tcz's and have rebooted the computer with them loaded. After doing that I still am only seeing the USB thumb drive as a mountable drive. Also, if you think I should start a new thread for this issue, I am happy to do so, I just didn't want to clutter the forum so I just kept going.
Both??
Load only the one MTD extension for the architecture in use
-
I've also done testing with / without mtd on a variety of hardware for mmcblk devices ... so fire away at a new thread topic!
-
I'm thinking we're barking up the wrong tree here...
the eMMC device should be visible here /dev/mmcblk1
What is the output of this?
sudo fdisk -l
-
I've also done testing with / without mtd on a variety of hardware for mmcblk devices ... so fire away at a new thread topic!
I think it's a bit late for a new thread so you got this
-
Okay, so I did what you suggested @coreplayer2 with no luck. Also
sudo fdisk -l shows only the usb drive used to boot TC. Additionally, I followed all the recommendations in this thread: http://forum.tinycorelinux.net/index.php/topic,21288.15.html (http://forum.tinycorelinux.net/index.php/topic,21288.15.html) to no avail. The op from that thread gave up, but I know there has to be a way because it shows up when I boot other Linux distros.
I also checked ls /dev to see if anything like mmcblk was listed without any luck
-
Hi coreplayer2
... the eMMC device should be visible here /dev/mmcblk1 ...
I don't see any sign of mmc or blk in his dmesg attachment. Is it possible the device is not detected due to him booting EFI?
Maybe some grub module needs to be loaded?
Also noticed this:
efi: EFI v2.40 by INSYDE Corp.
efi: ACPI 2.0=0x7b124014 SMBIOS=0x7a775000 ESRT=0x7a778918
efi: No EFI runtime due to 32/64-bit mismatch with kernel
...
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
efi: Setup done, disabling due to 32/64-bit mismatch
Sorry if I'm off base here, I've never dealt with any of this EFI stuff.
-
efi: EFI v2.40 by INSYDE Corp.
efi: No EFI runtime due to 32/64-bit mismatch with kernel
...
efi: Setup done, disabling due to 32/64-bit mismatch
Sorry if I'm off base here, I've never dealt with any of this EFI stuff.
I'm not sure the EFI run-time statement is part of the issue. The 64 bit TC does not have an EFI error but still does not mount the emmc. In both the 32 and 64bit TC, the mmc_core module is loaded, I checked this as well.
-
I'm fairly sure that grub has to pass hardware information to the kernel, but since I've also never booted off an eMMC card I'm not sure but am reading the manual for now, unless PDP-8 returns in the meantime
the kernel modules are
mmc_block.ko
mmc_core.ko
sdhci.ko
sdhci-pci.ko
-
mmcblk devices may not show up at all depending on hardware with TC.
What exactly is your computer that you are trying this with?
Consider: with a *stock* TinyCorePure64, it will dutifully see and mount both sd and micro sd mmc devices on some devices. It will also see the internal *e*mmc devices. But not on all.
The mtd extension made no difference.
Example: (all either UEFI-ONLY, or forced to uefi-only)
Intel NUC - mmcblk's can be seen and mounted.
Acer netbook / laptop - can be seen and mounted.
Intel Computesticks - NOT seen or mountable.
Some internal efi routines checked for enabling micro-sd. Some setups can disable the micro-sd's. All of that checked.
Example 2:
Computestick 1 - older model win 8.1 version - allows for boot from micro-sd
Computestick 2 - newer model win 10.1 version - does NOT allow for micro-sd boot.
Just saying - it may not be TC's fault that you can't boot from micro-sd on that box - which is what model again?
-
Quick note so we don't go off the rails ..
I'm using YUMI-UEFI successfully on most of my TCpure64 boots.
The op is using a multi-distro piecemeal setup to get his working.
This is important to know I think ... :)
-
Hi coreplayer2
I found a dmesg and lsmod post with the sd and emmc devices detected for a system I believe matches the OPs:
https://forum.libreelec.tv/thread/13647-micro-sd-slot-on-x64-not-being-recognized-reliably/?postID=104702#post104702
-
Thanks Rich, you'd make an incredible detective.
we were very close with the required modules then..
I wish I had an mmc card installed here to work with.
I'm thinking the BIOS should be configured to boot the eMMC as the primary device and
likely it's as simple as providing a kernel bootcode like root=mmcblk**** something like that. but am reading.
-
In case it helps, the PC I am using is the Kangaroo Mobile Desktop. Here is the website with manuals: https://kangaroo-infocus.zendesk.com/hc/en-us/articles/205741276-Kangaroo-Mobile-Desktop-Manuals-Downloads (https://kangaroo-infocus.zendesk.com/hc/en-us/articles/205741276-Kangaroo-Mobile-Desktop-Manuals-Downloads)
@Rich found the right one.
-
Ah, the Kangaroo is similar to my Computesticks.
Consider this data-points or noise ...
1) I can boot Porteus 4.0 from the internal micro-sd card on the older computestick which the manufacturer actually allows to happen. It will also recognize all the *mmc devices. It uses Syslinux 4.06
2) I can put Tinycorepure64 on that micro-sd card, modify/add a section to Porteus' own syslinux 4.06 menu and boot Tinycorepure64 that way identifying the micro-sd card with a UUID.
3) BUT, after boot, one only ends at the ash commandline. Using fdisk -l shows that no filesystems are found.
4) However, if I add an external usb-stick, place my tce directory upon it, and identify it with either a LABEL or UUID, then TCpure64 works just fine - but still no *mmc devices are detected either.
Ie, it seems I can initiate a TCpure64 boot from a micro-sd / mmc device with a syslinux 4.06 bootloader, but once booted, it doesn't know about mmc devices. And, even if booted from an sdX/usb stick, TC won't recognize mmc devices whether one uses the mtd extension or not.
-
Ie, it seems I can initiate a TCpure64 boot from a micro-sd / mmc device with a syslinux 4.06 bootloader, but once booted, it doesn't know about mmc devices. And, even if booted from an sdX/usb stick, TC won't recognize mmc devices whether one uses the mtd extension or not.
This matches my experience thus far. I can install grub, vmlinuz, and core.gz to the eMMC by using a separate distro that shows the eMMC, however, if I boot TC from the eMMC, it boots to the base core console only and does not recognize any eMMC or SD devices.
This makes me wonder if it is something to do with the TC implementation of mmc and sd recognition?
I am going to run a couple of other tests, but any additional help would be excellent. I would prefer to be able to use TC without losing function of both traditional storage mechanisms. I love how TC lest you start tiny and build out exactly what you want/need!
-
@JimmyJohn
I think we're overthinking this..
The mmc is more than 4GB which means it's pre-formatted with NTFS or exFat ? neither of which are supported OOB
Assuming the drive can be seen in Gparted, can run corepure64, load dosfstools, e2fsprogs and GPARTED.
Run sudo Gparted and select your mmc device
Create a new Partition Table = GPT
create two partitions
1. FAT32 @ 200MiB
2 ext2 @ remainder of drive
Then the device should be mountable and be capable of installing Grub2 and TC to.
Good luck
-
@coreplayer2
The device is not visible in GParted. I can see it in GParted when I boot a different distro, such as debian, however, it is not visible in gparted in TC.
That said, I booted a different distro and followed your partitioning instructions, then booted into TC again to see if that made a difference, and unfortunately it is still not showing up :-( Thanks for the idea though! I really thought that might be it as soon as I read it.
-
...
then booted into TC again to see if that made a difference, and unfortunately it is still not showing up :-( Thanks for the idea though! I really thought that might be it as soon as I read it.
Which TC ? corepure64 ?
-
@jimmyjohn
Also is the mmc device listed in the BIOS (assuming it has one) as the primary boot device?
-
@jimmyjohn
Be aware that our hardware, your Kangaroo and my Computestick, show the same behavior, regardless if it is the on-board eMMC formatted as NTFS, or the optional external micro-sd card. formatted with fat32.
All bios/setup has been checked to see if there was anything special blocking mmc devices. There is no option at least on mine to change this at all. Yet Porteus boots and sees it all. ?
BUT, on an Intel NUC, with a stock install booting with an sda, it *can* see mmc devices with a stock install of TinyCore!
So maybe there is something different between hardcore NUC's, and little computesticks and kangaroos. :)
The fuggedaboutit option:
Just use a Sandisk UltraFit usb. Just a nub hanging out, not a big key.
Rarely do I have to access the ntfs windows partition from within TC, and the micro-sd cards are mainly used for pi-core...
-
All bios/setup has been checked to see if there was anything special blocking mmc devices. There is no option at least on mine to change this at all. Yet Porteus boots and sees it all. ?
BUT, on an Intel NUC, with a stock install booting with an sda, it *can* see mmc devices with a stock install of TinyCore!
Hi PDP-8. Any chance of listing the output of LSMOD on either /both of the PC’s whilst the device is visible please
Sent from my iPhone using Tapatalk
-
@jimmyjohn
Also is the mmc device listed in the BIOS (assuming it has one) as the primary boot device?
I tried both 64 and 32 bit versions. Also, yes, the mmc device is listed as the primary boot device in the EFI Bios.
@jimmyjohn
Be aware that our hardware, your Kangaroo and my Computestick, show the same behavior, regardless if it is the on-board eMMC formatted as NTFS, or the optional external micro-sd card. formatted with fat32.
All bios/setup has been checked to see if there was anything special blocking mmc devices. There is no option at least on mine to change this at all. Yet Porteus boots and sees it all. ?
So maybe there is something different between hardcore NUC's, and little computesticks and kangaroos. :)
So, any thoughts as to why multiple other distro's see it all and TC doesn't?
-
Could be a kernel difference (version or config).
-
Sure - here come the lsmods:
For reference..
Intel NUC - usb boot - mmc devices *are visible and mountable* - full sized sd-cards anyway.
Intel NUC - usb boot - mmc devices *can* be seen:
*** USB boot INTEL NUC ***
Module Size Used by Not tainted
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
cpufreq_powersave 12288 0
i915 1003520 2
i2c_i801 16384 0
drm_kms_helper 94208 1 i915
i2c_designware_platform 12288 0
i2c_designware_core 12288 1 i2c_designware_platform
drm 253952 3 i915,drm_kms_helper
iosf_mbi 12288 1 i915
intel_gtt 16384 1 i915
agpgart 28672 2 drm,intel_gtt
i2c_algo_bit 12288 1 i915
squashfs 28672 4
zstd_decompress 65536 1 squashfs
xxhash 12288 1 zstd_decompress
loop 20480 8
wmi_bmof 12288 0
rtsx_pci_sdmmc 16384 0
rtsx_pci_ms 12288 0
mmc_core 73728 1 rtsx_pci_sdmmc
memstick 12288 1 rtsx_pci_ms
video 32768 1 i915
serio_raw 12288 0
backlight 12288 2 i915,video
pcspkr 12288 0
lpc_ich 20480 0
wmi 16384 1 wmi_bmof
xhci_pci 12288 0
xhci_hcd 98304 1 xhci_pci
rtsx_pci 36864 2 rtsx_pci_sdmmc,rtsx_pci_ms
r8169 53248 0
8250_dw 12288 0
mei_me 16384 0
mei 40960 1 mei_me
Intel Computestick - usb boot - mmc devices *cannot* be seen:
** USB boot Intel Computestick **
Module Size Used by Not tainted
cpufreq_conservative 12288 0
cpufreq_userspace 12288 0
cpufreq_powersave 12288 0
i915 1003520 2
drm_kms_helper 94208 1 i915
drm 253952 3 i915,drm_kms_helper
i2c_designware_platform 12288 0
i2c_designware_core 12288 1 i2c_designware_platform
intel_gtt 16384 1 i915
agpgart 28672 2 drm,intel_gtt
i2c_algo_bit 12288 1 i915
squashfs 28672 9
zstd_decompress 65536 1 squashfs
xxhash 12288 1 zstd_decompress
loop 20480 18
ax88179_178a 20480 0
usbnet 20480 1 ax88179_178a
mii 12288 2 ax88179_178a,usbnet
mmc_block 24576 0
video 32768 1 i915
backlight 12288 2 i915,video
pcspkr 12288 0
sdhci_acpi 12288 0
mei_txe 16384 0
sdhci 32768 1 sdhci_acpi
mei 40960 1 mei_txe
mmc_core 73728 3 mmc_block,sdhci_acpi,sdhci
iosf_mbi 12288 2 i915,sdhci_acpi
8250_dw 12288 0
lpc_ich 20480 0
And for good measure:
Intel Computestick - micro sd card boot - using Porteus Syslinux bootloader. (only works with tce directory on external sdX device). MMC devices still *NOT* seen.
** vfat32 micro-usb boot Intel Computestick via Porteus Syslinux bootloader **
Module Size Used by Not tainted
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
cpufreq_powersave 12288 0
i915 1003520 2
i2c_designware_platform 12288 0
i2c_designware_core 12288 1 i2c_designware_platform
drm_kms_helper 94208 1 i915
drm 253952 3 i915,drm_kms_helper
intel_gtt 16384 1 i915
agpgart 28672 2 drm,intel_gtt
i2c_algo_bit 12288 1 i915
squashfs 28672 4
zstd_decompress 65536 1 squashfs
xxhash 12288 1 zstd_decompress
loop 20480 8
mmc_block 24576 0
video 32768 1 i915
backlight 12288 2 i915,video
sdhci_acpi 12288 0
sdhci 32768 1 sdhci_acpi
mei_txe 16384 0
mei 40960 1 mei_txe
mmc_core 73728 3 mmc_block,sdhci_acpi,sdhci
lpc_ich 20480 0
8250_dw 12288 0
iosf_mbi 12288 2 i915,sdhci_acpi
pcspkr 12288 0
Guess it would have been easier for me to run a diff, but I'm pretty much wiped out now. :)
-
Would it be useful if I were to provide the same details that PDP-8 provided while booted into a different distro that can see everything?
-
Hi jimmyjohn
An lsmod and a dmesg might be helpful
-
Okay, I have attached the lsmod and dmesg while booted into kubuntu 19.04. I can see everything with this system as it is running, so let me know if there's anything else I can provide to help solve this conundrum.
-
Thanks
At this point if no one else has any suggestions, I'm thinking your issue is Kernel config related or for some reason the modules we talked about earlier are not getting loaded. Either way I'm ordering a mmc card for my notebook so I'm not doing this blind.
sdhci
mmc_block
In theory these are the controller modules you need to load which exist but are not loaded in your system
We haven't forgotten about you :)
-
Either way I'm ordering a mmc card for my notebook so I'm not doing this blind.
We haven't forgotten about you :)
Thank you so much! I will be patient :-)
-
I just hooked into this thread by finding mention of * YUMI *, not about screens.
My aim is to run some apps-from-the-90s; eg. poplog & mulinux.
Several of us are trying & failing to get poplog running again.
It seems, the easiest way would be to use an OLD linux installation.
So I fetched <Redhat6,2>.rar, which was popular in the 90s.
That expanded to <Rehat6.2>.iso. And a <how2> claimed that:
`dd if=<redhat.iso> <other args> of=/dev/<USBstik!notApartn?>
would make a USBstik:Installer. Which seems absurd and failed.
Of course the MBR was destroyed ?!
Then I ran the latest YUMI on Win10.; but the GUI/Panel has 2 entries
for the <*iso> :-
1. Select which installation, and Win10 will fetch the *.iso;
2. location of *.iso in your dirTree.
I entered item 2 , of course.
The installer-progress-bar looped at 30% and searching errorMesgs
showed it failed to find some strangeNamed file.
Can you confirm & comment on the 2 entries to ID the *.iso ?
Either one would suffice ?
Isn't installing TC to a USBstik from the *.iso CENTRAL KNOWLEDGE
which I lack ?!
-
After/during a sleep I realized that the "conv=fdatasync" for the `dd` cmnd may be
essential. I found that TC [ash-based] can't do it; so I used another installation.
The resulting `dd` of the *.iso to the unPartitioned USBstik lists as a nice DirTree;
but I still can't find how to use it to boot the RedHat6.2.
With the 2 laptops: W8.1 & W10; both can't read the stik & want to reformat it.
At boot time they both show the USBstik in the menu, but jump to "PXE".
---
I'm wondering if my original TC64-ver7 was installed via a *.iso ;
and how to debug this <boot via *.iso on a USBstik> ?
-
It has been a few months now. Has anyone had any luck in diagnosing the emmc issue we had been looking at before?