Fedora 21 on mackbook air - no tilde key
by CS DBA
Hi All;
I've installed Fedora 21 KDE spin on a 2015 Macbook air. I installed
the rpmfusion repos and enabled kmod-wl and kernel-devel packages to
enable wireless support. At this point most everything works, the
screen brightness keys, keyboard backlight keys, keyboard volume keys,
etc all work.
However if I press the tilde/back tick key I get a les than sign (<)
and if I press shift-tilde I get a greater than sign (>)
Anyone know how to enable the proper behavior for these keys?
Thanks in advance
8 years, 9 months
Re: Fedora21/22 grub doesn't recognize my raid1/LVM partitions
by John Wright
On Mon Jul 13 18:52:16 UTC 2015 Chris Murphy typed:
>>> So there's the kernel bug, 1225671, that ends up stopping the arrays,
>>> but then there's a misleading message saying there's a problem that's
>>> been corrected, yet clearly not corrected.
>>
>>
>> The exact wording of the message is:
>>
>> 'Unexpected system error. The system has encountered a problem and
>> recovered.'
>
>This is a message in the installer itself? Or is this a GNOME
>notification (a floating thing from the top-center)? I'm going to
>guess it's not in the installer because I've always seen it spit out
>the exact error message into the anaconda.log (or program.log if it's
>a helper program's error) and I don't see that in your attached logs.
>But I also don't see it in the journal either, so... I'm baffled
>exactly what system error it's referring to as well as this supposed
>recovery. GNOME bug... haha.
The precise appearance of the error message is as follows:
A small dark rectangular box appears at the top center of the blue
wallpaper page. The box contains a large frowny-face and the words:
'Oops, sorry, it looks like a problem occurred. If you'd like to help
resolve...'
On mouseover, the box expands to finish the sentence '...the issue,
please send a report.', followed by a darker area at the bottom of
the box containing the word 'Report'. Clicking on 'Report' opens
a large light colored box with the '...encountered a problem and
recovered' message, plus:
Kernel-core
Version 4.04.301.fc22.x86_64
plus boxes labeled 'Details' and 'log'. Clicking on 'log' opens a
window that announces that the bug has already been reported, allows
a login to bugzilla, thus adding my name to the cc for the bug, and
a link to the bug, BZ 1225671.
-jmw-
8 years, 9 months
aeskulap and dicom files
by Gregory P. Ennis
Everyone,
Looks like aeskulap was not included in F22. I had it on F21 and
before. It was a very decent dicom viewer.
Does anyone know why this was not included in F22. It was a good
product.
Greg Ennis
8 years, 9 months
Re: Fedora21/22 grub doesn't recognize my raid1/LVM partitions
by John Wright
On Mon Jul 13 02:19:31 UTC 2015 Chris Murphy typed:
>So there's the kernel bug, 1225671, that ends up stopping the arrays,
>but then there's a misleading message saying there's a problem that's
>been corrected, yet clearly not corrected.
The exact wording of the message is:
'Unexpected system error. The system has encountered a problem and recovered.'
>Does this same kernel call trace happen with Fedora 21's installer? Or
>does it fail for a different reason?
With the F21 installer, there is no error message, and the installer
does find the raid1 array. But it finds it only as one ~ 460 GB
'physical volume'; my existing LVM partitions are not recognized, so
I can't install into them.
>There is a beta release criteria for this:
>
>Hardware and firmware RAID
>The installer must be able to detect and install to hardware or
>firmware RAID storage devices.
>
>And there are test cases, and there's an entry for software raid in
>the test matrix. So it should get tested multiple times per build, and
>there will be a dozen builds pre-alpha, pre-beta, and pre-final. So
>it's a bit surprising this is so easy to hit (the bug report has
>someone hitting it in virtual box).
>
>Obviously this can't be fixed with official media, you could roll your
>own workstation installer compose and instead use kernel 4.0.5 which
>should fix this bug, and then you'd be able to install F22 to this
>existing software raid.
>--
>Chris Murphy
Alas, rolling my own workstation installer is beyond my present skill
level. I must decide whether to wait for Fedora 23, or to back up
everything and let the F22 installer have a crack at creating a new
raid1 array with LVMs on top of it.
Thanks again for the help,
-jmw-
8 years, 9 months
OT Password problem -
by Bob Goodwin
I bought a used Dell Latitude E4310 that I want to replace Windows7 on
with Fedora-22. Unfortunately the BIOS is locked and I do not have the
admin password for it. A phone call to Dell was unproductive and none of
the passwords offered in an on-line application work. Does anyone know
what I can do to access this computer. I can return it, bought through
Newegg, but it looks good so far, in new condition and the price is
right. It even has a working battery.
I considered opening it and removing the bios battery which I assume
would return it to the default conditions which I believe is no password
set.
Any suggestions appreciated,
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-22/64bit LINUX XFCE
8 years, 9 months
Mounting HD from Live CD
by Aaron Gray
How do I mount an old F21 HD which I have lost the password and work
on using a F21 Live CD please ?
Many thanks in advance,
Aaron
8 years, 9 months
To the aeskulap guy
by tangent08＠hushmail.com
You can take the src rpm from Fedora 21 and use the command:
rpmbuild --rebuild src rpm. This generates a version of aeskulap to
Fedora 22. It works in several times.
Edward
8 years, 9 months
Re: Fedora21/22 grub doesn't recognize my raid1/LVM partitions
by John Wright
From: Chris Murphy <lists(a)colorremedies.com>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: Fedora21/22 grub doesn't recognize my raid1/LVM
partitions
Message-ID:
<CAJCQCtQK50A--xCFKWGEASwM2ySJqsKg0BdTq7HQJo+c2m96Og(a)mail.gmail.com>
>There are messages in the storage.log about md126 and md127 being
>degraded. That would be a problem for discovering anything on those,
>even if they come up OK degraded, Anaconda won't install to degraded
>arrays. But I also don't know what messages you get about this, it
>should give an error message rather than silently fail.
Chris,
Thanks for the help!
Speaking of error messages - there _was_ an error message at the
beginning of the install-to-disk process; but I had ignored it since
it said something like 'problem found and corrected', or words to
that effect. (Wipes egg off face.) When I booted the live install
again to get the data you requested, I payed more attention, and it
led me to BZ bug # 1225671, which seems highly apropos.
>Two things to update the bug with. What live media installer does see
>this correctly? Was it Fedora 20 or Fedora 21? Or both? And then also,
>if you boot the Fedora 22 Workstation (live) media, launch the
>installer, go to custom partitioning, drop to shell - capture:
>
>cat /proc/mdstat > mdstat.txt
>mdadm -Dv /dev/md126 > md126.txt
>mdadm -Dv /dev/md127 > md127.txt
>journalctl -b -l -o short-monotonic > journal.log
>
>scp those off machine or cp elsewhere and attach those to the bug too.
>For the mdadm commands, make sure you use the md device designation
>returned by the first command. I'm pretty sure it'll be md126 and
>md127 again, but I suppose that could change on subsequent boots.
>
>Chris Murphy
Fedora 20 installed with no problems from install iso. I have
not tried F 20 live media; only reason I tried the live media
with F 22 was because that was what mostly is available. Also
tried the F 22 server iso, which seemed to recognize and allow
me to select the LVM partitions, but then booted into grub rescue.
Have added the results you suggested to the bug. There is no
output from mdadm /dev/md126 or -127. There are no /dev/md*
entries.
Thanks again, and apologies for not paying attention to that error
message earlier.
-jmw-
8 years, 9 months
