Compatibility

Not sure this is working properly, respond if you can read it.

Yes, you can, or else you can choose the option to try first and then install from there.

Yes just got the dinner message, have fun :D:D you've earned it!

3-4 hrs works fine for me. Read here first I'll have some extra material.

Cheers

BTW and what Stan said.

It's good. I can get your input through email on my phone. Keep the chatter coming
 


The email thing seems spotty sometimes, as Wizard noted earlier. But you can load up a browser on the phone too and refresh the page here (assuming your phone does that stuff).
 
Sorry Stan, been busy as a blue-arsed fly between two Xenial Unities, and burning a stick.

Persistence does not seem to like me at the moment, not with Unetbootin nor Multiboot USB. So I dd'ed it straight onto a stick, and been practising chrooting from the stick into the install and I believe I am ready if we need that avenue.

My 16.04 in the Garage (this computer, my Acer) does not have the microcode and code tool even listed in SPM, which is likely to do with the Universe Repo not being checked. The one in the Laundry (Toshiba Satellite) DOES have them both listed, and installed.

Problem with the Acer is that when I try to enable Universe &c, it goes all gooey on me, so as I have /dev/sda38 or 39 free at the moment, I will install another one on there and see if that resolves the problem.

When Ubiquity gets to the point of calling on os-prober to configure the bootloader, that part will take 20 mins or more detecting my 45 partitions, so I'll move computers in the interim.

Can I assist you in any way, Wizard? I can boot Ubuntu on DVD also if there's anything I can do.

Learnt something new, that I can be in the middle of a Post and click reply to yours and have it inserted ... must be why Newbies are always putting in long quotes? Can you tell I'm autistic? o_O

And yes by all means if you wish. I am just about flat out of DVDs (have plenty of CDs) and you may see something I miss. If we act as each other's wingman we make a good team :D

BTW I don't think I know (or have forgotten :rolleyes:) what State you are from or your time zone, that might help

Cheers Wizard

2nd BTW - @harbottleaudio ... Cody, if you start installing, as Stan said, use the whole drive, but if the options to encrypt or use LVM are offered (& not grayed out) DON'T choose either of them, OK?
 
hi im back
#2 install from the dvd.
I always use the whole drive
situation is the same... asking for a boot device or to install a boot device and restart the computer after OS has been installed
 
You still around, or gone to bed?

If you've gone to bed, don't answer me :p

I'll get out of this stick and come back here in 5

Wiz
 
Cool, OK to go or do you want to sleep?

Wiz
 
Which one gets you into the DVD?
 
OK got that, gimme 5-10 & I'll have instructions

Edit - I'll have to ignore you so I can finish the Post and post it, regrets
 
OK I'm back so I'll outline our best option at the moment and that is chrooting with your DVD into the install itself. We can take as a given the following has been effected, if not accurate, correct me:
  1. You have a working medium, the DVD-R, which carries a closed session of a burned Ubuntu 16.04.3 'Xenial Xerus' with a Unity Desktop Environment, 64-bit
  2. The .iso from which you burned the DVD was verified, although I haven't asked you, unless I missed it, how you verified it?
  3. The install has completed, and when you reboot your htpc, you get a message about
  4. ... asking for a boot device or to install a boot device and restart the computer after OS has been installed
chroot aka ChRoot simply involves us using an Ubuntu Live medium to go into the Ubuntu install that's not working and do good voodoo just as if we were working within a working install.

We can often fix it this way. If not, we go to plan e) None of the above, lol.

The message you're getting indicates that Linux agrees the install is there, but it cannot find where to boot from. (Likely)

INSTRUCTIONS

1. Boot the DVD, and choose "try Ubuntu"

2. When you are in, go to Settings (cog icon on launcher at left) and choose Brightness and Lock

3. There, choose Never for Dim Screen, then exit

4. Go to Dash top left corner, start to type in Terminal, open Terminal

5. Icon will appear in Launcher, right click it and choose Lock to Launcher

6. In Terminal type and enter the following, and examine the output

Code:
sudo fdisk -l  #that's a lowercase L

and

sudo blkid # that's like block ID

and

df -Th

These will give you "The State of the Nation".

It is likely you will have your small r root as /dev/sda1, that is your partition full of system files.

What I am particularly interested in is if during the install process you chose somewhere specific for your bootloader to be installed, eg /dev/sda2 or whatever.

If done as a separate partition, we will factor that in later. It would be a very small partition, perhaps 300MB or less, formatted as vfat, that is FAT32, not as EXT4, the native Linux format. It will be referred to as ESP and/or EFI.

I'll proceed, until I need to adapt, or not.

Once we have got where the install is, we can type in the following:

7.
Code:
sudo mount /dev/sdXY /mnt
... where XY is X a letter and Y a number eg sudo mount /dev/sda1

You will just be returned to the prompt unless something is wrong.

8. ONLY if you have made a separate boot partition will you then enter

Code:
sudo mount /dev/sdXY /mnt/boot

Note with this and 7. the space between mount and /dev and ..XY and /mnt - The output from Step 6. will reveal whether Step 8 is needed.

9. We now need to mount some virtual filesystems, in order (one includes a subfolder) as follows

Code:
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done

Note the spaces and the small I's (ayes)

Next we actually chroot, fasten your seatbelts.

10. sudo chroot /mnt

Code:
sudo chroot /mnt

Grub is not installed properly so we'll try this (with no number, it is just to the partition)

Code:
grub-install /dev/sdX
... that is likely "/dev/sda", no number. We don't need "sudo" with this because when we chrooted, you became captial R Root and sudo is unnecessary.

Now Grub is hopefully installed. So we will update it.

Code:
update-grub

This may take a few secs and spool off some length of output.

If no errors were reported, we are finished as chroot, so we will exit it, by pressing Ctrl-d, it will show "exit" and return you to the DVD's Live prompt.

Hold your breath and type with or without "sudo"

Code:
reboot

You may be told to remove the medium and press Enter.

Let me know how you go.

Wizard
 
May have not factored something in at Step 10.

If entering

grub-install /dev/sdX

generates an error about efi, enter

sudo mount /dev/sdXY where XY is where your EFI System Partition was revealed. The re-enter

grub-install /dv/sdX and proceed from there.

Wizard out
 


Top