Today was the day to install f20 on my Lenovo x120e. I had two drives
to work with: an old 320Gb HD and a new 240Gb SSD.
I thought I would be smart and hibernate my system with the current
drive (f17). Don't know why I did not just poweroff. Something major
went wrong and now that drive will not boot up. So building the new
drive became imperative.
Short and long of it see bugzilla reports: 1006304, 1033749, & 1046482.
I am up and running with i386 on the 320Gb HD. I was using x86_64 with
f17. At least I have an installation and I can access my emails and
figure out how to get x86_64 on the SSD.
The problems writing the bootloader MAY be due to USB problems I have
observed on this system. ~5 months ago, I was no longer able to write
USB sticks or SD cards (in the SD slot). I have been able to write to
USB HD and USB CD and DVD. Or at least it seems so.
How can I determine if I really do have USB problems and have to buy new
hardware?
With all the attempts to install, I spent a lot of time with the
installation and have a couple of small strange behaviours to report:
In setting the location from New York to Detroit, if I did not get
Detroit the 1st time or even when back to try and select something else,
I lost the down arrow to scroll beyond the 'a's. I had to type Detroit
in on the location bar. This was consistant behaviour. Had enough
times doing this step.
If I selected my local repo, Updates became not an option. Regardless if
I used the DVD install (i386 and x86_64) or the netinstal (only tried
x86_64), consistantly this became greyed out. I could not provide the
URL for where I have my local updates repo. It did not matter if I added
repo=url to the boot line, or did it in the GUI. The moment I selected
my own http URL, I lost updates.
As far as adding repo= to the boot line, i386 and x86_64 work
differently! But I suspect you know that. tab with i386 and 'e' with
x86_64.
Sometimes when I selected LVM for the partitioning, the LVM partition
name would be 'fedora_19'. I left it like that in this install that
finally worked and here is what df has to say for itself:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/fedora_19-root 29G 4.8G 23G 18% /
devtmpfs 1.3G 0 1.3G 0% /dev
tmpfs 1.3G 164K 1.3G 1% /dev/shm
tmpfs 1.3G 1016K 1.3G 1% /run
tmpfs 1.3G 0 1.3G 0% /sys/fs/cgroup
tmpfs 1.3G 44K 1.3G 1% /tmp
/dev/sda1 477M 96M 352M 22% /boot
/dev/mapper/fedora_19-home 257G 32G 212G 14% /home
Some times it used the host name. Depended on what steps I took to get
to setting up the LVM partition.
In summary of what is important:
Why have my installs to the SSD failed (writing bootloader).
Why can I not provide my updates URL.
thank you
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
