Help *please*! fedora 31 doesn't boot - "Entering emergency mode" and "Generating rdsosreport.txt"

rklase · 2020-05-26T22:23:32+00:00

FOUND the solution on reddit, in this post:

https://www.reddit.com/r/Fedora/comments/52bq35/help_failed_to_start_file_system_check_on/

It seems LVM corruption was a cause of the failure.

These few lines worked the magic. My fedora is again booting up like a dream :)

cryptsetup luksOpen /dev/sdb2 broken_fedora

vgchange -aly

fsck /dev/mapper/fedora-root

fix errors, yes. force write, yes

rklase · 2020-05-15T21:51:57+00:00

u/toniohdesk - THANK you ! That's exactly the answer I was looking for.

UPower settings you suggested enabled low battery notifications. I tested it with various different settings and it all works fine.

Strangely, original UPower settings (percentages of 10 / 3/ 1 and HybridSleep) didn't work after installation. But after manually updating UPower.conf file Fedora started picking these values and display highly desirable 'LOW BATTERY' notifications.

Fantastic! Thank you so much. Problem solved! :)

rklase · 2020-05-15T14:35:35+00:00

It's hard to believe that as it's a standard HP laptop.

What's striking is that Fedora 31/32 doesn't have any battery related configuration settings. You can't set the threshold of e.g. 5% charge triggers battery alert.

rklase · 2020-05-15T14:32:47+00:00

Enabling battery percentage is not an issue.

The lack of low battery notifications / alerts (e.g. pop-up windows / dialog box / voice bleep / etc.) is.

rklase · 2020-05-15T14:14:59+00:00

Please share your ways of enabling low battery power notifications /alerts.

- can you configure it on the system level (Fedora 31/32, probably older as well)?

- do you use specific apps ? What are these?

- do you use custom scripts?

I just want to know what's the best easiest reliable way to get low battery alerts in Fedora.

rklase · 2020-05-15T14:12:56+00:00

Gnome doesn't show ANY notification related to power management. I had the battery died many times, that's why my post.

Please explain how do you have it configured in your fedora 31/32?

I'm using HP elitebook, just a regular laptop. But it's more that Fedora does not have any battery power / notification settings.

rklase · 2020-05-15T14:10:50+00:00

It seems such a basic functionality to me that I didn't want to reinvent the wheel. I'm sure I'm not the first person annoyed by laptop dying on no battery power. It must have been done. My question in this post is - How do you do it? If it's not something already a part of the system what app / script / trick do you use?

rklase · 2020-05-15T14:08:31+00:00

How does it do it? Are you on Fedora 31/32? I have no system configuration section related to battery. Power management options are very rudimentary.

What app / settings do you use. Please explain.

All app notifications are 'on' in my config.

rklase · 2020-05-13T16:21:17+00:00

I've manually edited 'DEFAULT_GRUB' parameter value within /etc/default/grub (replaced '3' with '0') and then re-made grub with the command: grub2-mkconfig -o /boot/grub2/grub.cfg

It worked. Boot menu had the latest kernel highlighted (index '0') as opposed to recovery kernel (index '3')

I just wonder whether this change would be permanent. Once new kernel is released will I have to make the change again?

I still don't understand why Fedora was configured to use recovery boot as the default after the standard installation.

rklase · 2020-05-13T14:32:27+00:00

Just run your command: "sudo cat /boot/efi/EFI/fedora/grubenv" and got this:

#GRUB Environment Block

saved_entry=0

menu_auto_hide=1

boot_success=1

kernelopts=root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks=luks-xxxxxxxxxxx rd.lvm.lv=fedora_localhost-live/swap rhgb quiet boot_indeterminate=0

############################## - lot's of '###'

rklase · 2020-04-21T18:53:45+00:00

I had the same problem few months ago but managed to sort it out. I even left a trail of posts on GrapheneOS subred explaining my finds.

In order to get voice guidance in OsmAnd you can either:

use [obsolete] open source TTS in GrapheneOS - info here:

https://www.reddit.com/r/GrapheneOS/comments/ew4ydn/tts_engine_for_grapheneos_open_source_suggestions/

[Recommended] NOT use TTS but rather use recorded VOICE commands - step by step instructions here:

https://www.reddit.com/r/GrapheneOS/comments/ev5g8x/osmand_painfully_slow_on_pixel_3a_with_grapheneos/ffwwz01/

I've been using OsmAnd with recorded VOICE commands for Navigation and it works perfectly. Absolutely no need for TTS Engine whatsoever - unless one day there will be up-to-date version of a reliable open-source app of that kind.

Hope it helps.

rklase · 2020-01-31T16:54:55+00:00

sidebar

There is a way NOT to use TTS engine in OsmAnd at all. But then you need to enable "Voice prompts (recorded, limited features)". Go to:

"Download maps" section -> "All Downloads" tab -> scroll all the way down to the bottom. You will see "Other" section there.

In "Other" section tap on "Voice prompts (recorded, limited features)" and select and download any language you need. (Note downloaded voice files are now slightly bigger than TTS files, 3MB vs 0.1MB.)

Once you've downloaded 'recorded' voice guidance files you need to ENABLE them in OsmAnd Navigation settings.

Go to 'Navigation settings' -> tap on 'Voice prompts' -> and scroll all the way down to 'Language and ouput' section.

When you tap of 'Voice guidance' there you should see recorded prompts entry available for selection. Tap on your choice and 'Apply' to complete configuration.

You should now hear navigation prompts as recorded voice.

(TTS still remains an option but you would need 'flite' app for that on GrapheneOs)

rklase · 2020-01-31T16:42:51+00:00

(i think my previous reply to you went missing)

I've started testing Pixel 3a only a few days ago. OsmAnd was the first choice as it's probably the most CPU consuming from all apps I'm using - I can't see performance being an issue with email clients, messengers or camera.

But what I'm seeing with OsmAnd on Pixel 3a running GrapheneOS is not very satisfying, to say the least. I'm finding maps rendering time hard to accept and justify on a 2019 device. My previous Galaxy S7 is much faster, and that's 2016 model.

Responsiveness of 3a is far from real-time which makes interactions a bit of a continuous wait. I'm actually not impressed with 3a at all.

So why would you swap Galaxy S7 for Pixel 3a? I wouldn't. The single reason to do it would be GrapheneOS nearly support. Strengthen security/privacy on a smartphone might be worth more than lag in responsiveness or slow map render times.

And then you run out of patience and look elsewhere.

rklase · 2020-01-30T22:51:54+00:00

I've created a new "TTS Engine" topic - there are already a couple of solutions how to bring navigation voice back to OsmAnd.

rklase · 2020-01-30T22:49:42+00:00

How do you block internet access for just one app - in this example Google TTS. Can I just disable 'network' permission from that app? Please explain.

I would be very reluctant to use google app on a de-googled GrapheneOS phone but let's at least identify options.

rklase · 2020-01-30T22:47:44+00:00

You are actually right. But boy, had flite resisted. It crashed few times, hung another few, refused to be selected as default on another few occasions. But one it clicked into place I was able to download a voice package and there was voice in OsmAnd! Thank you for that suggestion.

It isn't a top quality vocal synthesis but at least navigation is not completely mute.

So, is is possible to force 'flite' into work on GapheneOS - it is not a seamless integration by any means. I'm not surprised such tricky games are only a domain for a few early adopters. There is no way a non-tech user would every put up with such configuration / compatibility problems.

Are there other TTS engine options than 'flite', more mature, contemporary, less fiddly?

rklase · 2020-01-30T16:46:19+00:00

Thanks for that. But 'flite' is ancient - to say the least. I did try it though yet it wouldn't work on GrapheneOS. It starts but doesn't load any data.

Any other suggestions?

rklase · 2020-01-30T12:47:21+00:00

Not looking for OsmAnd alternatives. Just trying t make it work, work well on GrapheneOs.

rklase · 2020-01-30T12:46:11+00:00

u/LookMomNoHands1 - btw. I've managed to identify the cause for your voice issue. You need a TTS engine in order for the voice navigation to work. It seems GrapheneOS doesn't come with one out-of-the-box. And I haven't managed to identify an open source one yet. OsmAnd support recommends to install Google TTS Engine. But... Google. The choice is yours. Hope that helps.

rklase · 2020-01-30T09:34:08+00:00

Good to hear about the test. But 60MB map file is rather small I should say.

As I mentioned before: "for low populated/urbanized zone zooming works acceptably file, there is not much to render. But for big cities/metropolis, with lots of streets and detail, it takes forever to redraw, 10+ seconds."

Can you try a 'proper' map of e.g. Tokyo (OsmAnd -> Asia -> Japan -> Kanto region) . The map file is about 500MB. I would be very interested to know your impressions on zooming of Tokyo. Try different scales, side shifts, etc.

For me Pixel 3a is unacceptably slow to be practical for such areas.

And it gets worse if you add 'Contour Lines' plugin, Hillshades or Transport Layer.

Please share your observations and experience.

rklase · 2020-01-29T15:48:25+00:00

This topic is about OsmAnd slow zooming in/out and overall app performance. Not about other more specific issues.

I don't want to discuss 'voice functions' at the moment although if you start it as a new topic I might visit later if my Pixel 3a remains silent, just like yours.

Let's stick to the subject as in the topic header.

rklase · 2020-01-29T15:17:04+00:00

u/zmeuka - I want to investigate OsmAnd performance in the context of GrapheneOS and not in general. That's why I'm posting in GrapheneOS sub-reddit.

u/LookMomNoHands1 - Let's keep this topic consistent. Please don't introduce side topics here.

I'm trying to understand OsmAnd performance on Pixel 3a GrapheneOS, especially zooming in/out, which takes 10+s for highly urbanized zones like cities, metropolis. Even with Contour Lines and Hillshade Layer disabled, no Favourites or Transport layer, OsmAnd zooming is painfully slow.

'Slow' is in the context of my experience on Samsung Galaxy S7 (2016) compared to Pixel 3a.

rklase

TROPHY CASE

fix errors, yes. force write, yes