UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
yep now I got an even bigger project and just think it all because of my undoing! I do appreciate a the links to, when I get this sorted you'll be the first to know! And considering you are the only one to try and help me, lol, have a good one Mike, stay safe and keep on keeping on, let you know soon my friend, thanks again, AK
Hey Mike I think I may have gotten somewhere, I was able to open the command prompt with the letter C. I'm trying to follow the guidelines you set forth but I'm still new to this, I don't get this because I'm great at rooting and unlocking bootloader's on Android devices but this code on Ubuntu is confusing me because so of it is right along with the Linux code our phones have, I have hit TAB to get possible commands, this gonna take some time I feel, but hey, this is a hobby of mine minus storm chasing!
grub is the boot loader which basically is a small program that starts the process of loading the operating system. Shell commands like sudo and fdisk do not work within grub.
Did you find the partition with the /boot directory as shown in the link I posted?
I found a lot man, examples are (hd0), (hd0,1), (prco), (hd0,msdos2), (hd0,msdos1), (hd1), (hd1,msdos5), (hd1.msdos1) is all of the individual ones I have to do like the SET PREFIX=(HD1)/GRUB
SET ROOT=(HD1)
INSMOD LINUX
shits blowing my mind because I went through all those in exactly the same fashion with no avail can you help a little bit more maybe
Here's the rest of my inputs...
INSMOD NORMAL
NORMAL
I'm not getting to "NORMAL" because it says can't find command etc, I'll snap a pic and crop it to 256mb
Can I just text you the pictures, trying to crop down to 256mb is proving to be a high task, my number, we 2 cool cats out business is our business, it's like Las Vegas in here want happens in Vegas stays in Vagas.
Since you are getting your computer tomorrow it would be much easier to just wait. Load antiX on the USB drive and start fresh.
We really do not know the condition of the data or partitions on the drive at the moment and we can't boot from the USB drive either.
The purpose of linuxquestions.org is to share knowledge. No texting. Please remove your phone number. It is possible that nefarious people will start spamming you.
Well even said if true, I'm going to be at this all night now, it's got me mad, frustrated, happy because I'm learning even more and how to implement correct procedure and what's in place of what each other is so that's pretty cool I don't want to stay up all night but I think it's going to happen because I started something I want to finish it even though my computer is going to be here tomorrow I'm being a little anal retentive on it got to get it got to get it right good thing about instant gratification it's not instant LOL buddy
I believe the reason you can't boot is that grub can not find /boot which is why you see the "grub rescue >" command line prompt. normal is a module i.e normal.mod which is normally located in the /boot/grub. This could be that grub did not install correctly or that something failed with installing Ubuntu. Without being able to boot from USB we can not confirm either way.
The reason I suggested using antiX instead of Ubuntu 16 is that the latter is unsupported, you will not be able to easily install other programs and there are security vulnerabilities with out of date software. antiX IMHO is a good choice for older PCs with limited RAM.
Was able boot into tty1, I remembered my username, I read that even though you can't see the password and just type it in, hence *where I'm at now* still boggled on what to do next? It looks like I'm good to go except correct code implementation, I can use SUDO now, so please advise if you don't mind.
I will try that just as soon as i can, my brain is on semi-overload, lol, I was kinda hoping not to have to use my new computer for this, that's why I am doing what I am on the old HP, gotta admit 17 years for a laptop with zero upgrades is not to bad huh? Only thing I did was convert the Windows XP to Win7 and just that not to long ago, say 3 weeks ago. but yes I'm going to read the other links you sent plus maybe call upon you again for any problems that may arise??
Man it looked all good when I ran that command and It so called "fixed" it but basically I got a bootloop right back to where I started, does that sound like something else is wrong to or what? I'm at a loss of words, it took me over 12 hours on time sorting this out and from the help from you, but basically all I have done is remember my username and password!?? Darn I thought I could have done this without the help from my new computer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.