Re: GRUB prompt after F29 to F30 upgrade

This morning I got the dreaded grub prompt on boot. Took me 3 hours to understand what https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade was talking about. I did a bunch of searching and trying things out before I hit upon the configfile grub command.

Re: Can not install mariadb Error: Transaction check error: ....

Thanks, that worked On Sat, Sep 26, 2015 at 8:07 AM, Jon Ingason wrote: > Den 2015-09-26 kl. 16:42, skrev Rich Emberson: > > # dnf install mariadb mariadb-server > > Last metadata expiration check performed 0:19:25 ago on Sat Sep 26 > > 07:14:08 2015. >

Can not install mariadb Error: Transaction check error: ....

Seems like a rather fundmental problem: $ uname -a Linux medusa 4.1.7-200.fc22.x86_64 #1 SMP Mon Sep 14 20:19:24 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep -i mariadb # dnf install mariadb mariadb-server Last metadata expiration ch

Re: F22: KDE to Gnome?

Well, after decades of KDE my solution was: dnf groupinstall Xfce Xfce works On Tue, Aug 11, 2015 at 3:14 PM, Rich Emberson wrote: > Upgraded from F20 KDE environment using > fedup --network 22 --product=nonproduct > > and X/KDE has rendering/refresh/redraw issues. > Applicat

F22: KDE to Gnome?

Upgraded from F20 KDE environment using fedup --network 22 --product=nonproduct and X/KDE has rendering/refresh/redraw issues. Application widgets and KDE pop menus are not draw, or, at best some edge or corner is drawn. In an xterm, the line being entered is drawn, but nothing else - move the w

Re: fedup 20 -> 22 -> improper X rendering

te machine. So, somehow Fedora 22's nouveau-based rendering seems to have an issue .. or something On Sat, Aug 8, 2015 at 6:42 PM, Rich Emberson wrote: > I used to update: > > fedup --network 22 --product=nonproduct > > Coming up in graphical target as default.target, KD

Re: fedup 20 -> 22 -> improper X rendering

I might add that logging in remotely to this machine and then launching an X-application that displays on the remote machine works. So, it seems to be purely a X rendering issue on the machine, the X protocol works fine. Richard On Sat, Aug 8, 2015 at 6:42 PM, Rich Emberson wrote: > I used

Re: fedup 20 -> 22 -> improper X rendering

3.3.7-1.fc22 x86_64 kmod-libs 21-1.fc22 x86_64 kmod 21-1.fc22 x86_64 On Sun, Aug 9, 2015 at 4:34 AM, fedora2015 wrote: > On 08/08/2015 09:42 PM, Rich Emberson wrote: > >> I used to update: >> > fedup --network 22 --product=nonproduct >> >> Coming up in graphic

fedup 20 -> 22 -> improper X rendering

I used to update: > fedup --network 22 --product=nonproduct Coming up in graphical target as default.target, KDE X does not render properly. With right click I a small box appears under the cursor, navigating to what I guess is the first menu item, I can start a console. A box appears. I click int

Closure: fedup 20 -> 21 -> No Mouse or Keyboard

Review my post from previous week or so for background First Laptop: Having failed to upgrade Fedora 22 using fedup on my KDE-base Fedora 20, I reinstalled Fedora 20. I downloaded the Workstation Live dvd twice, each time it passed the 256sha and both time the burned dvd passed the media test ..

FAIL: Thunderbird: Replying to thread

I use gmail. When I reply to a thread using Thunderbird, the response never shows up, but, if I include the email of the person who wrote the thread I am responding to, that person gets the email. On the other hand, if I log in to my gmail account, the I can post a response, that that response ap

fedup 20 -> 21 -> xinit -> KDE -> No mouse/keyboard input

Thanks for the suggestion. Contents of /var/cache/akmods/akmods.log START 2015/07/25 16:06:18 akmods: Checking kmods exist for 4.0.8-200.fc21.x86_64 2015/07/25 16:06:18 akmods: Building and installing nvidia-340xx-kmod 2015/07/25 16:06:18 akmods: Building RPM using the command '/bin/akmodsbuild --

fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory

Still no mouse or keyboard. Don't know if this is the problem. from /var/log/Xorg.0.log START [96.019] (II) Loading sub module "fb" [96.019] (II) LoadModule: "fb" [96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so [96.030] (II) Module fb: vendor="X.Org Foundation" [96.030]

fedup 20 -> 21 -> xinit -> KDE -> No mouse/keyboard input

So, I am now at the point where xinit (calling startkde) has the KDE screen appearing, but ... The pointer-cursor appears but can not be moved by the mouse, and (after some timeout and the login screen appears) keyboard entry fails. What does one do to enable both the mouse and keyboard. Thanks

fedup 20 -> 21 -> xinit -> error setting MTRR

What is causing the MTRR error in the xinit output? cat /proc/mtrr reg00: base=0x0 (0MB), size= 4096MB, count=1: write-back reg01: base=0x1 ( 4096MB), size= 1024MB, count=1: write-back reg02: base=0x0c000 ( 3072MB), size= 1024MB, count=1: uncachable Part of xinit output

fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly

Also see MTRR issue below. On 07/25/2015 07:01 PM, Ed Greshko wrote: You're a KDE user and quite a bit has changed. One question and one suggestion Q. Just for information... Are you using kdm or sddm as your display manager? How does one find which display manager is being used? Sugg

fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly

Again, fedora upgrades using fedup ... Starting with Fedora 20, did ... stuff ... > fedup --network 21 --product=nonproduct ... stuff ... > fedup --network 22 --product=nonproduct So, now rebooted and it started. I have all my machines in multi-user mode just in case there is an issue wit

fedup 20 -> 21 -> No X

Ah, fedora upgrades using fedup ... Starting with Fedora 20, did > yum update and then > fedup --network 21 --product=nonproduct Took a while but there were no issues but remember, as root > export PATH=$PATH:$HOME/bin:/sbin:/usr/sbin or use > su - to become root otherwise fedup has an iss

Re: SOLVED mdadm: Cannot get exclusive access to /dev/md127

Thanks for the help! cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 did the trick. Steps Remove entry from /etc/fstab # vi /etc/fstab then following sequence of commands: # lsof +d /raid1/ # lsof +D /raid1/ # df # mount # cryptsetup luksClose luks-ab8911f9-b3a4-4f33

Re: mdadm: Cannot get exclusive access to /dev/md127

Tried: # wipefs -a /dev/md127 which did not word, so I next tried: # wipefs -f -a /dev/md127 /dev/md127: 6 bytes were erased at offset 0x (crypto_LUKS): 4c 55 4b 53 ba be and then # mdadm -S /dev/md127 mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounte

Re: mdadm: Cannot get exclusive access to /dev/md127

Thanks - wipefs fails see below # dmsetup ls luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 (253:9) luks-35719a97-5898-4420-9a56-1576ffdc6db3 (253:1) luks-c80d9988-30f6-42cf-a9b7-89ee3408eccb (253:6) luks-03c06df8-f9b9-4f0d-847e-79a7ed527888 (253:0) luks-a2ebb2b0-527d-47f3-83ef-

mdadm: Cannot get exclusive access to /dev/md127

I've got a two disk raid and I want to it and convert the disks to some non-raid usage. The raid was never used and has no data. Also, the raid disks are encrypted along with the rest of the disk in the machine. When I try to stop raid I get the following: # mdadm --stop /dev/md127 mdadm: Cannot

Re: Dell U2913WM 2560 x 1080

Asus NVIDIA EN7300GT DVI Max Resolution 2560 x 1600 On 03/20/2014 07:30 PM, Ed Greshko wrote: On 03/21/14 09:36, Rich Emberson wrote: Thinking about getting a Dell UltraSharp 29 Ultrawide Monitor U2913WM but I've not found anyone on the net saying that they've been able to configure

Dell U2913WM 2560 x 1080

Thinking about getting a Dell UltraSharp 29 Ultrawide Monitor U2913WM but I've not found anyone on the net saying that they've been able to configure X to take advanage of its size and resolution. Dell says they only support MS. Anyone using one with Fedora using one of these and how to register i

fedora 20 firewalld multicast DLNA

Setting up a media server on a Fedora 20 box. It must have reception of multicast messages enabled. If I do a 'iptables -F' blowing away the firewall, then the media server sees the smart tv and the smart tv sees the media server. Given the default firewall that comes with Fedora 20 and firewalld,

f19->f20 fedup: reboot freezes at: Mounted /boot.

Used: fedup --network 20 Fedup exited without error. (Had to use the https://fedoraproject.org/wiki/Commo...Upgrade_issues Upgrade fails if /var is a separate partition ) Got GRUB menu titled System Upgrade. began upgrade no plymouth bo

Authorization failed: Failed to obtain authentication

About a week ago I updated my version of fedora16 on both my laptop and server. After that update, every 5 minutes I would get a Notification popup stating: Authorization failed with reason: Failed to obtain authentication At the time I did not do anything figuring that it might be some bug in fed

f17 yum update failure

After upgrading from f16 to f17 a couple of weeks ago using preupgrade and then doing an initial 'yum update', everything worked fine - the yum update worked. This weekend tried to do a yum update on either my lagtop or server and I get the same error condition: --> Processing Dependency: libxapi

f15 sync slow after couple of days

When I first start my machine, a sync takes less than a second and compiling a small Java project takse 34 seconds. After running for two days, a sync takes 25 to 30 seconds (and running sync just after a sync still takes that long) and compiling the same Java project takes 5 to 8 minutes. Wher

ERROR with rpm_check_debug vs depsolve:

I got the following when using Yum this weekend. I posted the message to http://yum.baseurl.org/report but have gotten no response. Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: kernel-uname-r = 2.6.38.3-18.fc15.x86_64 is needed by (installed) kmod-nvidia-2.6.38.3-18.fc15.x86_64-

14->15 upgrade comments

Last weekend I upgraded (using preupgrade) both my laptop and development box from 14 to 15. Both are x86_64 machines. On the laptop, twice now while rebooting the system has crashed with a stacktrace on the screen. Both times it occurred while the blue, light- blue and white progress bars were ma

Fedora 13 AdobeReader_enu nss-softokn-freebl multiple version conflict

Yesterday I installed Fedora 13, first on my laptop and then my main machine. Both are 64bit with nvidia cards. On the laptop everything went as expected, but on the big box I could not install AdobeReader_enu. When I try: yum install AdobeReader_enu I get the error message: Transaction Check