- This topic has 7 replies, 3 voices, and was last updated Aug 31-2:21 am by ghostnik11.
-
Posts
-
ghostnik11
Hi i installed antix 19.2/3 on my 2 in 1 tablet (asus t100ta). i installed root to the micro sd card and then put kernel in a different location that way i would be able to start antix without having to use a usb micro sd card converter. everything was working well until i did a sudo apt-get upgrade and accidentally told the system to update the kernel but the system didn’t realize that i placed the kernel in another location. Its located on mmcblk1p3. meanwhile root is on mmcblk2p1 i think. so now i can boot into antix but get stuck with just a command prompt since slim x won’t start. i tried fix-broken install but it keeps saying linux-image-4.19.0-6-amd64 have unmet dependencies and etc.
Anonymous
hi ghostnik11,
from grub menu can you scroll down to advanced options and boot to previous kernel?
and see if it works?hi ghostnik11,
from grub menu can you scroll down to advanced options and boot to previous kernel?
and see if it works?Hi so i tried that but it doesn’t work. it still just boots to login and then after i put in my info it just remain in command prompt mode. with slim x failing to start. Is there a way i can remove linux-image-4.19.0-6 from the system? Also i tried using live antix usb with boot repair but it kept giving me an error saying ext2 doesn’t allow embedding when i tried to have it use mmcblk1p3 as an option.
by the way mmcblk1p3 is ext4. so i don’t understand why boot repair didnt work.
by the way mmcblk1p3 is ext4
bootrepair relies on the output provided by lsblk command.
Does the following indeed report ext4 ?
/bin/lsblk -o FSTYPE>>>> kept giving me an
errorwarning saying ext2 doesn’t allow embeddinggrepped the sourcecode for the bootrepair program and found zero occurrences of “embed”,
so I websearched “emmc linux ext2 doesn’t allow embedding” and learned the following:You are getting the warning because you are installing grub to a partition instead of the MBR. This means grub can not be embedded in the unused space between the MBR and the first partition. Instead it has to have the list of blocks that /boot/grub/core.img resides in placed into the MBR. This setup is subject to being broken by things like defrag and so is not recommended, hence the warning. Since it is only a warning, you can ignore it.
i tried using live antix usb with boot repair
If you can access the emmc while booted from antiX live usb, howabout just copy//move the “not found” kernel to the expected location. Hold off removing the extra kernel until after the system hs been brought back to bootable condition, eh.
by the way mmcblk1p3 is ext4
bootrepair relies on the output provided by lsblk command.
Does the following indeed report ext4 ?
/bin/lsblk -o FSTYPE>>>> kept giving me an
errorwarning saying ext2 doesn’t allow embeddinggrepped the sourcecode for the bootrepair program and found zero occurrences of “embed”,
so I websearched “emmc linux ext2 doesn’t allow embedding” and learned the following:You are getting the warning because you are installing grub to a partition instead of the MBR. This means grub can not be embedded in the unused space between the MBR and the first partition. Instead it has to have the list of blocks that /boot/grub/core.img resides in placed into the MBR. This setup is subject to being broken by things like defrag and so is not recommended, hence the warning. Since it is only a warning, you can ignore it.
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 65.1M 1 loop /snap/gtk-common-themes/1515
loop1 7:1 0 260.7M 1 loop /snap/kde-frameworks-5-core18/32
loop2 7:2 0 162.9M 1 loop /snap/gnome-3-28-1804/145
loop3 7:3 0 55.5M 1 loop /snap/core18/1988
loop4 7:4 0 290.4M 1 loop /snap/vlc/1700
loop5 7:5 0 55.5M 1 loop /snap/core18/1997
loop6 7:6 0 77.4M 1 loop /snap/dosbox-x/776
loop7 7:7 0 219M 1 loop /snap/gnome-3-34-1804/66
loop8 7:8 0 217.9M 1 loop /snap/gnome-3-34-1804/60
loop9 7:9 0 144.1M 1 loop /snap/epiphany/70
loop10 7:10 0 295.3M 1 loop /snap/vlc/2103
loop11 7:11 0 77.4M 1 loop /snap/dosbox-x/748
loop12 7:12 0 144.1M 1 loop /snap/epiphany/76
loop13 7:13 0 99.2M 1 loop /snap/core/10859
loop14 7:14 0 18.1M 1 loop /snap/ubuntu-budgie-welcome/313
loop15 7:15 0 161.4M 1 loop /snap/gnome-3-28-1804/128
loop16 7:16 0 99.2M 1 loop /snap/core/10958
loop17 7:17 0 108.1M 1 loop /snap/goldendictionary/1
loop18 7:18 0 17.8M 1 loop /snap/ubuntu-budgie-welcome/282
loop19 7:19 0 64.8M 1 loop /snap/gtk-common-themes/1514
mmcblk2 179:0 0 59.5G 0 disk
├─mmcblk2p1 179:1 0 57.5G 0 part
└─mmcblk2p2 179:2 0 2G 0 part
mmcblk1 179:8 0 29.1G 0 disk
├─mmcblk1p1 179:9 0 512M 0 part /boot/efi
├─mmcblk1p2 179:10 0 27.4G 0 part /
└─mmcblk1p3 179:11 0 1.2G 0 part
mmcblk1boot0 179:16 0 4M 1 disk
mmcblk1boot1 179:24 0 4M 1 disk/bin/lsblk -o FSTYPE
FSTYPE
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfs
squashfsext4
swapvfat
ext4
ext4i tried using live antix usb with boot repair
If you can access the emmc while booted from antiX live usb, howabout just copy//move the “not found” kernel to the expected location. Hold off removing the extra kernel until after the system hs been brought back to bootable condition, eh.
So i checked out the link you gave and tried to link the /boot (located on dev/mmcblk1p3) to root (located on dev/mmcblk2p1). When i get to chroot i get errors.
Also i tried to install a new kernel 4.19.184-antix.1-amd64-smp (from terminal) and when i try to run that kernel. it freezes but i think its because when i tried to install it, it never placed the initrd.img for that version. Which i can not understand why it didn’t do it. i used the regular “deb i” command. What am i missing?
Because currently i can’t get X to start. i can boot into one of the other kernels but i can’t start X and so thats why its so hard. i only get a command prompt asking me to log in.
so i finally figured out how to get my system back up and running. So skidoo link helped me be able to get to enter the system even though it was only as far as the tty1 screen. But that’s okay because after that i was able to figure out a way to turn on wifi from the tty1 screen and then from that i was able to run dpkg reinstall kernel 4.19.0.6-amd. After that, i just looked up the command to install X. so that i could get back the GUI. And then reboot and my system was back and much more faster with kernel 4.19.0.6.
Just wanted to say thanks for all the help from skidoo and others, it took a little while but with the help of y’all i was able to troubleshoot and solve the problem.
- This reply was modified 1 year, 8 months ago by ghostnik11. Reason: solved!!!
- This reply was modified 1 year, 8 months ago by Brian Masinick. Reason: Skidoo
- You must be logged in to reply to this topic.
