Fedora + Phosh for PinePhone
#51
(02-03-2021, 05:10 PM)nas Wrote:
(02-03-2021, 07:15 AM)dawg161 Wrote: When I was using fedora this summer, there was an option on the phosh login screen to select phosh or gnome-shell, and I can't seem to do that anymore. Does anyone know how to re enable that?

You need a display manager, eg lightdm or gdm.

Something like below but maybe lightdm.conf needs an entry for the greeter... I can't remember all the steps so try gdm first.

dnf install gdm (or dnf install lightdm lightdm-gtk)
systemctl disable phosh
reboot
Thanks for the reply- I think I'm close but not quite there yet.
gdm didn't work as it just gave me a virtual terminal (obviously no onscreen keyboard there.)
lightdm seems so close- I followed the instructions in your other post and I'm at the login screen, but I can't get the virtual keyboard to come up. I try and select it from the accessibility menu and nothing comes up. I'll try again and if I have success I'll post what i put in the lightdm configuration. All that said, last summer's image the phosh login screen came with a little gear under the 7 and an option to choose session, so I wonder if there's some way to configure phosh to do this.
  Reply
#52
(02-06-2021, 07:35 AM)dawg161 Wrote: gdm didn't work as it just gave me a virtual terminal (obviously no onscreen keyboard there.)

I missed a couple steps before disabling the phosh service - you can select the keyboard from accessibility button at top right on gdm login but will be oversized unless rescaled beforehand.

gsettings set org.gnome.desktop.interface scaling-factor 1
sudo systemctl enable gdm.service -f

Quote:lightdm seems so close- I followed the instructions in your other post and I'm at the login screen, but I can't get the virtual keyboard to come up.

For lightdm, I would say to check you installed the onboard keyboard package.

dnf install onboard
  Reply
#53
OK I think I figured this out.

phosh isn't missing anything- the image from this summer had the really similar lightdm-mobile-greeter.

So if anyone else is having this trouble, the fix is simple


Code:
sudo dnf install lightdm-mobile-greeter
systemctl disable phosh
sudo reboot


nas I appreciate the help- and thanks for the pinephone fedora team- I really think this is one of the most compelling pinephone projects.
  Reply
#54
Thanks for the Fedora image, njha.

I'm trying to get wireguard set up but it looks like the kernel module is missing.

Is there a package that provides it, or am I gonna have to build it myself?

If I do have to build it myself, where can I find the headers for megi-kernel?
  Reply
#55
(04-24-2021, 07:23 AM)mr2dave Wrote: Thanks for the Fedora image, njha.

I'm trying to get wireguard set up but it looks like the kernel module is missing.

Is there a package that provides it, or am I gonna have to build it myself?

If I do have to build it myself, where can I find the headers for megi-kernel?
You can compile the kernel yourself from its repo at https://megous.com/git/linux/
You will need to enable Wireguard I assume.
I run a custom compiled kernel on my PinePhone with many extra features enabled.
  Reply
#56
My favorite distro on the pinephone, using phosh, gnome 40, or mate with a bluethooth keyboard-touchpad, love it.
Just wondering about f2fs partition, I couldnt resize it even following instructions from the dev, had to create an empty partition taking the right space on emmc then copied as root all data from sdcard root partition... Is there a way to flash to emmc normally with all space beeing used like with debian or manjaro?
  Reply
#57
So, I'm attempting to use the Fedora "minimal" images from ftp://pine.warpspeed.dk/nightly/pinephone/ .
The F34 images seem to boot and work perfectly on my pinephone.
The F35 images don't boot at all. It seems like the boot partition is different between the two:

F35 (note EFI):
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 1230847 1228800 600M ef EFI (FAT-12/16/32)
/dev/sdb2 1230848 3327999 2097152 1G 83 Linux
/dev/sdb3 3328000 12582911 9254912 4.4G 83 Linux

F34:
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 1230847 1228800 600M 83 Linux
/dev/sdb2 1230848 3327999 2097152 1G 83 Linux
/dev/sdb3 3328000 12582911 9254912 4.4G 83 Linux

Any advice? Thanks!
  Reply
#58
(06-22-2021, 09:37 AM)ppuser1998 Wrote: So, I'm attempting to use the Fedora "minimal" images from ftp://pine.warpspeed.dk/nightly/pinephone/ .
The F34 images seem to boot and work perfectly on my pinephone.
The F35 images don't boot at all.  It seems like the boot partition is different between the two:

F35 (note EFI):
Device      Boot      Start          End    Sectors  Size    Id Type
/dev/sdb1    *          2048  1230847  1228800  600M ef EFI (FAT-12/16/32)
/dev/sdb2          1230848  3327999  2097152    1G  83 Linux
/dev/sdb3          3328000 12582911  9254912  4.4G  83 Linux

F34:
Device      Boot      Start            End  Sectors      Size  Id  Type
/dev/sdb1  *          2048    1230847  1228800  600M  83 Linux
/dev/sdb2        1230848    3327999  2097152      1G  83 Linux
/dev/sdb3        3328000  12582911  9254912    4.4G  83 Linux

Any advice?  Thanks!

HUH ?!? That sounds like something is wrong with the build system; very sorry about that.
Thx for the report - I'll look into this asap.
  Reply
#59
(06-22-2021, 05:38 PM)Alho Wrote:
(06-22-2021, 09:37 AM)ppuser1998 Wrote: So, I'm attempting to use the Fedora "minimal" images from ftp://pine.warpspeed.dk/nightly/pinephone/ .
The F34 images seem to boot and work perfectly on my pinephone.
The F35 images don't boot at all.  It seems like the boot partition is different between the two:

F35 (note EFI):
Device      Boot      Start          End    Sectors  Size    Id Type
/dev/sdb1    *          2048  1230847  1228800  600M ef EFI (FAT-12/16/32)
/dev/sdb2          1230848  3327999  2097152    1G  83 Linux
/dev/sdb3          3328000 12582911  9254912  4.4G  83 Linux

F34:
Device      Boot      Start            End  Sectors      Size  Id  Type
/dev/sdb1  *          2048    1230847  1228800  600M  83 Linux
/dev/sdb2        1230848    3327999  2097152      1G  83 Linux
/dev/sdb3        3328000  12582911  9254912    4.4G  83 Linux

Any advice?  Thanks!

HUH ?!? That sounds like something is wrong with the build system; very sorry about that.
Thx for the report - I'll look into this asap.

Thanks - Will report back once a new image is available.
  Reply
#60
(06-23-2021, 02:20 PM)ppuser199 Wrote: Thanks - Will report back once a new image is available.

New build up (F35). Logs seems to indicate it should be ok now.
New F34 build will be available in a few hours.

All untested (aka nightlies) feedback very welcome
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Office applications for the Pinephone Peter Gamma 2 527 09-05-2024, 09:22 AM
Last Post: Peter Gamma
  Struggle to install LibreOffice on the PinePhone Peter Gamma 50 35,092 07-26-2024, 10:35 PM
Last Post: Peter Gamma
  Why does Pine64 sabotage office on the Pinephone? Peter Gamma 5 980 07-04-2024, 07:34 AM
Last Post: Kevin Kofler
  Which word processor to choose for the Pinephone? Peter Gamma 16 5,275 06-22-2024, 07:28 AM
Last Post: Peter Gamma
  Samba share on the Pinephone? Peter Gamma 0 639 06-16-2024, 10:26 PM
Last Post: Peter Gamma
  Possible Free Backup Carrier for PinePhone PineFone 0 449 06-13-2024, 03:45 PM
Last Post: PineFone
  Using Signal on PinePhone in mid-2023? dante404 47 22,278 05-03-2024, 02:19 AM
Last Post: dragonhospital
  Slarm64 on PinePhone [Unofficial Slackware ARM - 64 bit] acid andy 38 32,709 04-23-2024, 10:29 AM
Last Post: donchurch
Wink PINEPHONE not booting Touchwood 2 1,205 02-23-2024, 07:27 AM
Last Post: Touchwood
  Slack on PinePhone Adam Seline 5 6,477 12-20-2023, 07:20 AM
Last Post: nickolas

Forum Jump:


Users browsing this thread: 7 Guest(s)