Forum › Forums › New users › New Users and General Questions › cli-installer not letting me install to emmc
- This topic has 27 replies, 5 voices, and was last updated Apr 2-12:44 pm by anticapitalista.
-
AuthorPosts
-
March 30, 2020 at 12:38 am #34036Member
703m
I’m given the error: “mmcblk0p1 invalid, retry” the partition is ext4, any ideas to why this isn’t working?
March 30, 2020 at 2:38 am #34038Forum Admin
anticapitalista
::It only installs to ‘normal’ drives. Sorry.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 30, 2020 at 4:38 am #34039Member
Xecure
::It only installs to ‘normal’ drives. Sorry.
When did this happen? When antiX 19 launched (after Beta) I was able to install it on my cheap chinese tablet, that has eMMC drive. Did something change in antiX 19.1 and 19.2 that made it impossible to do so?
I’m given the error: “mmcblk0p1 invalid, retry” the partition is ext4, any ideas to why this isn’t working?
I don’t know if this still applies to the newer antiX versions, but antiX 17 and 19.0 could install (GUI install, no idea if cli too) but what I did (what I remember):
0. Create partitions with Gparted.
1. Launch antiX live system (to RAM) and, once everything is working, unmount every drive (I used Gparted to do so to make sure) and unplug USB device.
2. Launch antiX GUi installer and proceed with installation
2.5 If installation failed, then unmount everything again, including all internal partitions using Gparted after launching GUI installer.
3. Installation ends.I think the automounting gave me trouble while installing. It has been many months sisnce so my memory isn’t very good about what I had to do, but I have proof you can install antiX on an eMMC device. The tablet I use daily for reading runs antiX very fast and very well.
I will try checking in a few days, once I backup everuthing, If I can still install the newest antiX 19.2 full on it and report back.
- This reply was modified 3 years, 1 month ago by Xecure. Reason: Adding screenshot
Attachments:
antiX Live system enthusiast.
General Live Boot Parameters for antiX.March 30, 2020 at 5:05 am #34042Forum Admin
anticapitalista
::@Xecure – the first post is about the cli-installer. (Title – cli-installer not letting me install to emmc)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 30, 2020 at 5:48 am #34043Member
Xecure
::My mistake. Sorry for the misunderstanding.
Thanks, anticapitalista, for all your hard work.antiX Live system enthusiast.
General Live Boot Parameters for antiX.March 30, 2020 at 5:49 am #34044Forum Admin
Dave
::🙁 indeed the cli install used to blindly let you install to whatever was specified. You may be able to get around this by booting a live session then adding symlinks where /dev/hda1 points to /dev/mmcblk0p1. If I recall correctly as root in terminal.
ln -s /dev/mmcblk0p1 /dev/hda1
Do this for each of the partitions that you will be installing to. Then run the cli-installer and specify /dev/hda1 as the device to install to.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
March 30, 2020 at 6:33 am #34046Forum Admin
anticapitalista
::It is possible to install apps before running the installer.
So anyone can actually install their ‘desktop’ before running the installer.
This *should* work.eg for antiX-core (since it comes with wireless drivers)
1. Boot live-usb (with or without persistence)
2. login as root
3. Use ceni to set up network
3. apt update
4. apt install xorg antix-installer jwm (I chose jwm since it is tiny)
5. startx
6. open a terminal and type sudo minstall and follow the instructions
7. If you want to set keyboard as shown on the first screen, you also need to install fskbsetting
8. Enjoy!Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 30, 2020 at 12:10 pm #34051Member703m
::The system link worked, however grub doesn’t automatically load. I can only access the grub menu through the boot rescue menu on the live disk, otherwise I get sent to bios.
March 30, 2020 at 12:40 pm #34052Forum Admin
Dave
::You should now be able to run a live session and do a grub repair. I think this is in the control centre if running the full version. Otherwise you can do it manually. From my memory mount the installed location via
mkdir /mnt/install
mount /dev/mmcblk0p1 /mnt/install
Then bind mount the sys, proc, and dev via
mount -o bind /sys /mnt/install/sys
And likewise for the others.
Then open the install via chroot and update grub via
chroot /mnt/install
update-grub
grub-install /dev/mmcblk0
Then exit and unmount all the mounts and hopefully when you reboot it is ok.Edit:
If you can boot into the install you may only need to do the grub install. Boot into the install and run
grub-install /dev/mmcblk0
update-grub
And rebootEdit2:
The disk might not have the boot flag set. Iirc this can be done via
parted /dev/mmcblk0
Then at the (parted) prompt
set 1 boot on- This reply was modified 3 years, 1 month ago by Dave.
- This reply was modified 3 years, 1 month ago by Dave.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
March 30, 2020 at 2:03 pm #34056Forum Admin
anticapitalista
::The system link worked, however grub doesn’t automatically load. I can only access the grub menu through the boot rescue menu on the live disk, otherwise I get sent to bios.
Good to hear.
Could you clarify if you are using net or core version (or any other).
ThanksPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 30, 2020 at 2:13 pm #34057Member703m
March 30, 2020 at 2:22 pm #34058Member703m
::Edit:Nevermind this, just a little typo error
- This reply was modified 3 years, 1 month ago by 703m.
- This reply was modified 3 years, 1 month ago by 703m.
March 30, 2020 at 2:35 pm #34062Member703m
::I tried both sets of instructions and still get sent to bios, all commands worked without errors. Is it possible that the problem is with the bios at this point?
March 30, 2020 at 2:52 pm #34063Member
Xecure
::Can you change the boot order of partitions from the Bios? If you can, set the partition containing grub (it may be an individual partition or the root containing partition.
Edit2:
The disk might not have the boot flag set. Iirc this can be done via
parted /dev/mmcblk0
Then at the (parted) prompt
set 1 boot onDave’s instructions for setting the boot flag to the disk using terminal.
Make sure the boot flag is set. You can also check this running an antiX full live USB and checking in Gparted, for example, that the disk or the correct partition has the flag.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.March 30, 2020 at 2:52 pm #34069Forum Admin
Dave
::Is it indeed a bios of eufi? If the latter perhaps you will need to specify the install in the eufi boot settings… I am not overly familiar with this, other than installing grub to the root partition instead of the device and specifying no secure boot and to boot that partition in the eufi settings
Edit:
Does eufi need a fat partition? I cannot recall. Perhaps someone with more knowledge on eufi could chime in if needed?- This reply was modified 3 years, 1 month ago by Dave.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
-
AuthorPosts
- You must be logged in to reply to this topic.
