On 01/08/2014 02:42 PM, Adam Williamson wrote:
On Wed, 2014-01-08 at 11:38 -0800, Adam Williamson wrote:
On Wed, 2014-01-08 at 14:29 -0500, Robert Moskowitz wrote:
On 01/08/2014 02:14 PM, Adam Williamson wrote:
On Tue, 2014-01-07 at 15:06 -0500, Robert Moskowitz wrote:
On 01/07/2014 01:03
On Jan 9, 2014, at 6:11 AM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/08/2014 02:42 PM, Adam Williamson wrote:
On Wed, 2014-01-08 at 11:38 -0800, Adam Williamson wrote:
On Wed, 2014-01-08 at 14:29 -0500, Robert Moskowitz wrote:
On 01/08/2014 02:14 PM, Adam Williamson wrote:
On
On Thu, 2014-01-09 at 08:11 -0500, Robert Moskowitz wrote:
The other place you can change the parameters is in /etc/default/grub .
Finally took the time to make the change and NO /etc/default/grub
If it doesn't exist, you can create it and settings in it will be
respected.
And no manpage for blkid.
There is a man page for blkid. It is part of:
util-linux-2.24-2.fc20.x86_64
If the man page is missing, perhaps other missing pieces contribute to
the problem. For example, swapon is also in util-linux.
--
test mailing list
test@lists.fedoraproject.org
To
On 01/08/2014 09:15 AM, Richard Ryniker wrote:
And no manpage for blkid.
There is a man page for blkid. It is part of:
util-linux-2.24-2.fc20.x86_64
If the man page is missing, perhaps other missing pieces contribute to
the problem. For example, swapon is also in util-linux.
ARGH!!!
I
On Mon, 2014-01-06 at 16:40 -0500, Robert Moskowitz wrote:
The process to create a user in the 'firstboot' environment did not
allow for tagging the user to be an adminstrator. How do I do that?
Fedora's initial-setup, which you get anywhere other than GNOME, has a
checkbox.
GNOME's has no
On Tue, 2014-01-07 at 15:06 -0500, Robert Moskowitz wrote:
On 01/07/2014 01:03 PM, Chris Murphy wrote:
On Jan 7, 2014, at 8:13 AM, Robert Moskowitz r...@htt-consult.com wrote:
Booting is a bit strange. It starts with the Penguin on top and a large
font, and then switches off the Penguin
On 01/08/2014 02:12 PM, Adam Williamson wrote:
On Mon, 2014-01-06 at 16:40 -0500, Robert Moskowitz wrote:
The process to create a user in the 'firstboot' environment did not
allow for tagging the user to be an adminstrator. How do I do that?
Fedora's initial-setup, which you get anywhere
On 01/08/2014 02:14 PM, Adam Williamson wrote:
On Tue, 2014-01-07 at 15:06 -0500, Robert Moskowitz wrote:
On 01/07/2014 01:03 PM, Chris Murphy wrote:
On Jan 7, 2014, at 8:13 AM, Robert Moskowitz r...@htt-consult.com wrote:
Booting is a bit strange. It starts with the Penguin on top and a
On Wed, 2014-01-08 at 14:29 -0500, Robert Moskowitz wrote:
On 01/08/2014 02:14 PM, Adam Williamson wrote:
On Tue, 2014-01-07 at 15:06 -0500, Robert Moskowitz wrote:
On 01/07/2014 01:03 PM, Chris Murphy wrote:
On Jan 7, 2014, at 8:13 AM, Robert Moskowitz r...@htt-consult.com wrote:
Booting
On Wed, 2014-01-08 at 11:38 -0800, Adam Williamson wrote:
On Wed, 2014-01-08 at 14:29 -0500, Robert Moskowitz wrote:
On 01/08/2014 02:14 PM, Adam Williamson wrote:
On Tue, 2014-01-07 at 15:06 -0500, Robert Moskowitz wrote:
On 01/07/2014 01:03 PM, Chris Murphy wrote:
On Jan 7, 2014, at
On 01/06/2014 06:22 PM, Chris Murphy wrote:
On Jan 6, 2014, at 4:08 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/06/2014 05:57 PM, Chris Murphy wrote:
On Jan 6, 2014, at 2:40 PM, Robert Moskowitz r...@htt-consult.com wrote:
On reboot, it took some time with all sorts of messages.
On Jan 7, 2014, at 11:03 AM, Chris Murphy li...@colorremedies.com wrote:
So we need another bug filed to see if anaconda team can do efibootmgr pretty
much dead last, because if it fails as the last thing done, there's still a
good chance the system is bootable. At least, it's a better
On 01/07/2014 01:18 PM, Chris Murphy wrote:
On Jan 7, 2014, at 11:03 AM, Chris Murphy li...@colorremedies.com wrote:
So we need another bug filed to see if anaconda team can do efibootmgr pretty
much dead last, because if it fails as the last thing done, there's still a
good chance the
On 01/06/2014 06:22 PM, Chris Murphy wrote:
On Jan 6, 2014, at 4:08 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/06/2014 05:57 PM, Chris Murphy wrote:
On Jan 6, 2014, at 2:40 PM, Robert Moskowitz r...@htt-consult.com wrote:
On reboot, it took some time with all sorts of messages.
On 01/07/2014 01:03 PM, Chris Murphy wrote:
On Jan 7, 2014, at 8:13 AM, Robert Moskowitz r...@htt-consult.com wrote:
Booting is a bit strange. It starts with the Penguin on top and a large font, and
then switches off the Penguin and a smaller font. I never get the Fedora logo that I
have
On Tue, Jan 07, 2014 at 02:49:13PM -0500, Robert Moskowitz wrote:
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]:
/dev/fedora_19/swap: read failed after 0 of 4096 at 4096:
Input/output error
Jan 07 12:07:38 lx120e.htt-consult.com swapon[328]: swapon:
/dev/sda4: swapon failed: Device or
On 01/07/2014 05:49 PM, Michal Jaegermann wrote:
On Tue, Jan 07, 2014 at 02:49:13PM -0500, Robert Moskowitz wrote:
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]:
/dev/fedora_19/swap: read failed after 0 of 4096 at 4096:
Input/output error
Jan 07 12:07:38 lx120e.htt-consult.com swapon[328]:
On Ter, 2014-01-07 at 18:08 -0500, Robert Moskowitz wrote:
On 01/07/2014 05:49 PM, Michal Jaegermann wrote:
On Tue, Jan 07, 2014 at 02:49:13PM -0500, Robert Moskowitz wrote:
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]:
/dev/fedora_19/swap: read failed after 0 of 4096 at 4096:
On Tue, Jan 07, 2014 at 06:08:58PM -0500, Robert Moskowitz wrote:
On 01/07/2014 05:49 PM, Michal Jaegermann wrote:
Are you sure that swap is not already in use? What 'swapon -s' has to
say?
]# swapon -s
FilenameTypeSizeUsedPriority
/dev/sda4
On 01/07/2014 07:26 PM, Michal Jaegermann wrote:
On Tue, Jan 07, 2014 at 06:08:58PM -0500, Robert Moskowitz wrote:
On 01/07/2014 05:49 PM, Michal Jaegermann wrote:
Are you sure that swap is not already in use? What 'swapon -s' has to
say?
]# swapon -s
FilenameType
On 01/05/2014 04:04 PM, Chris Murphy wrote:
On Jan 5, 2014, at 1:33 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just did a test and it failed. :(
I updated the firmware. Rebooted twice. Did NOT go into Bios setup. Booted
the f20 x86_64 netinstal CD and it failed at the same point.
On Jan 6, 2014, at 8:40 AM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/05/2014 04:04 PM, Chris Murphy wrote:
On Jan 5, 2014, at 1:33 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just did a test and it failed. :(
I updated the firmware. Rebooted twice. Did NOT go into Bios
On 01/06/2014 02:27 PM, Chris Murphy wrote:
On Jan 6, 2014, at 8:40 AM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/05/2014 04:04 PM, Chris Murphy wrote:
On Jan 5, 2014, at 1:33 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just did a test and it failed. :(
I updated the
On 01/06/2014 02:27 PM, Chris Murphy wrote:
On Jan 6, 2014, at 8:40 AM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/05/2014 04:04 PM, Chris Murphy wrote:
On Jan 5, 2014, at 1:33 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just did a test and it failed. :(
I updated the
On Jan 6, 2014, at 2:40 PM, Robert Moskowitz r...@htt-consult.com wrote:
On reboot, it took some time with all sorts of messages. Failed on my swap
(though once running 'free' shows the swap space). selinux having to do its
thing and taking some time.
OK at this point you're running
On 01/06/2014 05:57 PM, Chris Murphy wrote:
On Jan 6, 2014, at 2:40 PM, Robert Moskowitz r...@htt-consult.com wrote:
On reboot, it took some time with all sorts of messages. Failed on my swap
(though once running 'free' shows the swap space). selinux having to do its
thing and taking some
On Jan 6, 2014, at 4:08 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 01/06/2014 05:57 PM, Chris Murphy wrote:
On Jan 6, 2014, at 2:40 PM, Robert Moskowitz r...@htt-consult.com wrote:
On reboot, it took some time with all sorts of messages. Failed on my swap
(though once running
On 01/03/2014 02:27 PM, Adam Williamson wrote:
On Fri, 2014-01-03 at 14:23 -0500, Robert Moskowitz wrote:
(disclaimer: never trust the monkey, I know a bit more about UEFI than
the average monkey but not everything.)
So why is the install failing?
We don't know yet, but Chris is on the
On Jan 5, 2014, at 1:33 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just did a test and it failed. :(
I updated the firmware. Rebooted twice. Did NOT go into Bios setup. Booted
the f20 x86_64 netinstal CD and it failed at the same point. I copied all
the logs and will upload
On 01/05/2014 04:04 PM, Chris Murphy wrote:
On Jan 5, 2014, at 1:33 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just did a test and it failed. :(
I updated the firmware. Rebooted twice. Did NOT go into Bios setup. Booted
the f20 x86_64 netinstal CD and it failed at the same point.
On 01/03/2014 08:01 PM, Chris Murphy wrote:
On Jan 3, 2014, at 12:23 PM, Robert Moskowitz r...@htt-consult.com wrote:
So why is the install failing?
The install fails because the efibootmgr command to write to NVRAM via the
kernel fails. And the reason why the kernel is failing to write to
On Jan 4, 2014, at 6:24 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just tried to come out of suspend mode from over the sabbath, and the system
was hung. No response. So I powered off and rebooted. Nothing. Panic time;
did I brick it? I unpluged the VGA and USB kydb/mouse
On 01/04/2014 08:32 PM, Chris Murphy wrote:
On Jan 4, 2014, at 6:24 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just tried to come out of suspend mode from over the sabbath, and the system
was hung. No response. So I powered off and rebooted. Nothing. Panic time;
did I brick it? I
On 01/04/2014 08:32 PM, Chris Murphy wrote:
On Jan 4, 2014, at 6:24 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just tried to come out of suspend mode from over the sabbath, and the system
was hung. No response. So I powered off and rebooted. Nothing. Panic time;
did I brick it? I
On Sat, 2014-01-04 at 18:32 -0700, Chris Murphy wrote:
On Jan 4, 2014, at 6:24 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just tried to come out of suspend mode from over the sabbath, and the
system was hung. No response. So I powered off and rebooted. Nothing.
Panic time;
On 01/05/2014 01:01 AM, Adam Williamson wrote:
On Sat, 2014-01-04 at 18:32 -0700, Chris Murphy wrote:
On Jan 4, 2014, at 6:24 PM, Robert Moskowitz r...@htt-consult.com wrote:
Just tried to come out of suspend mode from over the sabbath, and the system
was hung. No response. So I powered
On Tue, 2013-12-31 at 20:23 -0500, Robert Moskowitz wrote:
On 12/31/2013 08:00 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to delete
all of the NVRAM entries, and hope that in
On 01/03/2014 02:07 PM, Adam Williamson wrote:
On Tue, 2013-12-31 at 20:23 -0500, Robert Moskowitz wrote:
On 12/31/2013 08:00 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to
On Fri, 2014-01-03 at 14:23 -0500, Robert Moskowitz wrote:
(disclaimer: never trust the monkey, I know a bit more about UEFI than
the average monkey but not everything.)
So why is the install failing?
We don't know yet, but Chris is on the right track looking into it.
When we had the big
On 01/03/2014 02:27 PM, Adam Williamson wrote:
On Fri, 2014-01-03 at 14:23 -0500, Robert Moskowitz wrote:
(disclaimer: never trust the monkey, I know a bit more about UEFI than
the average monkey but not everything.)
So why is the install failing?
We don't know yet, but Chris is on the
On Jan 3, 2014, at 12:23 PM, Robert Moskowitz r...@htt-consult.com wrote:
So why is the install failing?
The install fails because the efibootmgr command to write to NVRAM via the
kernel fails. And the reason why the kernel is failing to write to NVRAM is
uncertain because there's nothing
I did the testing as you suggested and opened up a kernel bug report.
On 01/01/2014 04:26 PM, Chris Murphy wrote:
On Jan 1, 2014, at 1:07 PM, Chris Murphy li...@colorremedies.com wrote:
efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
And see if you get an error; and
On 01.01.2014 20:11, Robert Moskowitz wrote:
Oh, Here is my system info:
Lenovo x120e
UEIF Bios ver8FET32WW (1.16) (date 2011-11-03)
Embedde Ctlr Ver8FHT21WW (1.09)
Mach Type0611AH9
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/8fuj10uc.txt
…
CHANGES IN
Some testing today from f20 live x86_64 DVD
On 12/31/2013 08:00 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to delete all of
the NVRAM entries, and hope that in a reboot or two,
On Jan 1, 2014, at 12:11 PM, Robert Moskowitz r...@htt-consult.com wrote:
I got the same with efibootmgr -v:
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0006,0007,0008,0009
Boot Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Rescue and Recovery
On Jan 1, 2014, at 1:07 PM, Chris Murphy li...@colorremedies.com wrote:
efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
And see if you get an error; and you can also reissue efibootmgr -v to see
if that entry is now in NVRAM to confirm.
No errors and no change to
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1006304
In additional info, include computer model and firmware revision. And then
attach your program.log, anaconda-tb,
On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1006304
In additional info, include computer model and firmware revision. And
On Dec 31, 2013, at 5:27 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to delete all
of the NVRAM entries, and hope that in a reboot or two, it does sufficient
garbage collection that you can then try another installation.
On 12/31/2013 07:34 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:27 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
On 12/31/2013 08:00 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to delete all of
the NVRAM entries, and hope that in a reboot or two, it does sufficient garbage
collection that
53 matches
Mail list logo
