kut | I am installing the latest iso > usb to my laptop but when I reboot to finish, it acts like I'm missing grub/hdd. I've tried 3-4 times now, tried with ubuntu and now xubuntu, any advise? | 03:53 |
---|---|---|
Bashing-om | kut: Did you tell the installer where to install the boot code too ? What happens if you boot the install with the USB drive plugged in ? | 04:53 |
kut | yes. it boots to the live usb to install it again | 04:53 |
kut | i verified the disk set in bios, turned on uefi and reinstalled, same result. | 04:54 |
Bashing-om | kut: In my bios I can over ride to force boot to the drive that Xubuntu is installed to -- my think'n is that the boot code is installed to the USB drive and not to the install's drive. | 04:56 |
kut | how do i install on the drive not usb | 04:57 |
Bashing-om | kut: I do "manual" installs --- and in the lower right of the installer is the box to set the medium to install the boot code. | 04:58 |
Bashing-om | lower left !** | 04:58 |
kut | ok trying now | 04:58 |
kut | what should it be set to? | 04:59 |
Bashing-om | kut: "fdisk -lu" to know which disk you are installing to ... say it is the 1st Hard drive --- then it will be "sda" that you want the boot code installed to. | 05:03 |
kut | k trying that | 05:06 |
arraybolt3 | kut: quick question, does this happen to be an HP system? Perhaps an Elitebook or a Probook? | 05:07 |
arraybolt3 | Some of those systems have a buggy (or at least seemingly buggy) UEFI that will keep looking for Windows even after an Ubuntu installation. In such cases you can drop to the boot menu during early bootup (using the F12 key probably, or possibly first Esc, then F12) and then select "ubuntu" from the list of boot options. | 05:08 |
arraybolt3 | If that works there's a Customized Boot setting you can use to get the thing to boot automatically. | 05:09 |
* arraybolt3 has one system that is like this | 05:09 | |
xu-help60w | can you load xubuntu on an arm processor | 05:09 |
kut | arraybolt3: yes HP | 05:22 |
kut | windows wasn't installed on it before, kali was. non uefi and uefi give me the same result | 05:25 |
kut | same result when i use manual installation | 05:43 |
Bashing-om | :( | 05:53 |
Vigovski | hello? | 15:44 |
beam | hi | 19:25 |
beam | i have updated from 22.04 to 24.04 several days ago | 19:25 |
beam | everything runs fine so far | 19:25 |
beam | except (maybe two related) issues | 19:26 |
beam | i'm using dmcrypt and my root partition is encrypted | 19:26 |
beam | in 22.04 the prompt for the password was in a proper resolution for my monitors, now it looks like 800x600 | 19:26 |
beam | and if i press ESC the plymouth? screen disappears and more console like prompt is shown | 19:27 |
beam | in 22.04 this prompt also showed the password with asterisks | 19:28 |
beam | now i can see the typed in password in cleartext which is kind of a no go | 19:28 |
beam | and the second issue is that if i use the graphical screen to unlock the harddisk the autologin with lightdm is not working, if the password is typed in the "console" the autologin is working | 19:29 |
beam | any hints from anyone? | 19:30 |
beam | looks like a bug in plymouth | 19:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!