Attempting to install Pop OS on a Surface Pro

Pages (3): 1 2 3 Next

Papyrule
Senior Member

560

04-11-2016, 08:14 PM

You’ve got Pop-OS running on your Surface Pro, but some features aren’t working without a custom kernel. The Jakeday kernel you installed is there, yet the touchscreen and other tools remain unresponsive. Seek advice on troubleshooting or alternatives.

Papyrule

04-11-2016, 08:14 PM #1

GameBoosh
Senior Member

470

04-11-2016, 09:10 PM

You haven't finished yet—installing the kernel isn't enough. You must explicitly instruct Pop_OS to utilize it, such as by adding a bootloader entry. Do you have GRUB or systemd-boot installed?

GameBoosh

04-11-2016, 09:10 PM #2

You haven't finished yet—installing the kernel isn't enough. You must explicitly instruct Pop_OS to utilize it, such as by adding a bootloader entry. Do you have GRUB or systemd-boot installed?

CoconutSlayer
Member

208

04-12-2016, 01:10 AM

I'm not certain if that's the standard setting.

CoconutSlayer

04-12-2016, 01:10 AM #3

I'm not certain if that's the standard setting.

Chengster
Junior Member

04-12-2016, 01:34 AM

Check bootctl status to see if it reports issues or missing entries, indicating grub is likely active. Review the boot configuration to confirm systemd-boot is in use.

Chengster

04-12-2016, 01:34 AM #4

Check bootctl status to see if it reports issues or missing entries, indicating grub is likely active. Review the boot configuration to confirm systemd-boot is in use.

IPS10
Senior Member

623

04-19-2016, 04:13 AM

System details show firmware version 2.60 with MSFT 1.00 and Secure Boot turned off. Setup mode is configured as setup, using product systemd-boot 240. Key features include boot counting, menu timeout adjustments, one-shot controls, and default entry management. ESP location points to a specific disk partition. Boot loader information lists systemd-bootx64.efi for Windows Boot Manager.

IPS10

04-19-2016, 04:13 AM #5

Pixelplayer145
Member

168

04-20-2016, 12:41 PM

You can insert a boot entry after this page.

Pixelplayer145

04-20-2016, 12:41 PM #6

You can insert a boot entry after this page.

aussieboy28
Member

04-22-2016, 05:18 PM

You can locate the downloaded image by checking your file system paths or using a directory listing command. Regarding the article, it might help to review the steps slowly and ask specific questions about each part. It’s normal to feel confused if the setup wasn’t clearly explained.

aussieboy28

04-22-2016, 05:18 PM #7

Streiyn
Posting Freak

768

04-23-2016, 05:42 AM

I understand the frustration with systemd-boot versus grub. Could you share the relevant sections of the .conf file located in /etc/loader/entries? That will help me provide a clearer explanation.

Streiyn

04-23-2016, 05:42 AM #8

I understand the frustration with systemd-boot versus grub. Could you share the relevant sections of the .conf file located in /etc/loader/entries? That will help me provide a clearer explanation.

iSurvive
Member

180

05-13-2016, 05:01 AM

The system reports it can't find the loader directory.

iSurvive

05-13-2016, 05:01 AM #9

The system reports it can't find the loader directory.

GorkemCB
Member

05-13-2016, 07:52 AM

#10

The wiki refers to the correct location as esp/loader/entries. This is the Efi system partition mount point, typically /boot. Adjusting your path accordingly should resolve the issue.

GorkemCB

05-13-2016, 07:52 AM #10

The wiki refers to the correct location as esp/loader/entries. This is the Efi system partition mount point, typically /boot. Adjusting your path accordingly should resolve the issue.

Pages (3): 1 2 3 Next