amaurer's profile - activity

overview network karma followed questions activity

2018-07-12 23:18:18 -0600	commented question	Keyboard doesn't work once booted into Live USB @hello Possibly -- I don't actually have a wired mouse / keyboard. So I'll try goofing around with kernel parameters for
2018-07-12 20:08:38 -0600	asked a question	Keyboard doesn't work once booted into Live USB Keyboard doesn't work once booted into Live USB I have a wireless keyboard / mouse combo that worked on my desktop runni
2017-03-11 23:24:22 -0600	received badge	● Famous Question (source)
2016-11-28 02:08:02 -0600	received badge	● Popular Question (source)
2016-11-28 02:08:02 -0600	received badge	● Notable Question (source)
2016-03-26 16:47:52 -0600	asked a question	How to Boot Live USB on New Asus Desktop I'm stumped. I got a new Asus desktop computer and want to boot into Fedora. (Goal is to install Fedora, but let's take baby steps.) Here's what I've done: Disabled Secure boot according to this guide: http://www.technorms.com/45538/disabl... Disabled Fast Boot Now, when I try to boot into a (freshly made) Fedora 23 Live USB from BIOS, the picture of a Fedora symbol shows up, fills up, and then stays there indefinitely, just like a normal boot. Then the fedora symbol stays on the screen indefinitely. What else must I do to boot a Fedora 23 Live USB?
2016-03-23 20:49:10 -0600	commented question	What is this new button in the settings menu? Have you tried clicking it? GNOME wouldn't have a "do something unfixable to my OS" button placed right there.
2016-02-18 10:38:47 -0600	received badge	● Student (source)
2016-02-15 01:19:45 -0600	asked a question	GNOME Command to increase / decrease screen brightness I recently bought a chromebook that is now running Fedora. To get the brightness keys working, I installed `xbacklight`, and have set shortcuts to commands that run `xbacklight -inc 3` and `xbacklight -dec 3`, and it gets the job done.* This, I realize, actually has a couple drawbacks. First, the little GNOME overlay showing screen brightness doesn't pop up the way volume does. Second, running `xbacklight` seems to take more processing power than whatever the default command is. If I run the command multiple times quickly, whatever else I'm doing tends to lag. So I'm looking for a way to implement the default behavior. An ideal answer would be: A native GNOME command that replaces `xbacklight -inc 3` or whatever. A command that calls the usual `ALT + F7` or `ALT + F8` keystrokes without remapping the function keys. *Actually, decreasing took a little more scripting since I didn't want the screen to turn off all the way when it got to 0 brightness.
2016-02-08 13:13:05 -0600	answered a question	No Sound on Toshiba Chromebook 2 Check out James Fu's answer here: https://plus.google.com/+JamesFuBEEFC... You need a copy of the chromebook's default asound.state file. Turn off alsa, copy that to the correct location, and edit the pulseaudio file telling it to turn off speakers when headphones are attached. Works like a charm!
2016-02-06 13:16:29 -0600	asked a question	No Sound on Toshiba Chromebook 2 Hi, I just got a Toshiba Chromebook 2 essentially by following this guide. During the Fedora 23 install I had to manually add a root and swap partition to get the computer booting, so that's fine, but there was one pesky thing left over once it started booting -- there's no sound. Sound works fine through the HDMI port, just not through the built-in speakers. There is a fix for Ubuntu and Arch Linux, using a modified asound.state file, found at the bottom of the webpage above. My question is: does anyone know of a fix for this, or does anyone know where I could get started to figure out what's wrong?