Recently I installed Fedora 15 on a standalone system to do some testing. This system has ASUS motherboard with a single integrated Atheros 8131 Gigabit Ethernet NIC. Here is the relevant output from ipconfig -a: p33p1 Link encap:Ethernet HWaddr E0:CB:4E:1A:F6:D5 inet addr:192.168.0.114 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::e2cb:4eff:fe1a:f6d5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:62680 errors:0 dropped:0 overruns:0 frame:0 TX packets:37533 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:94004479 (89.6 MiB) TX bytes:2446588 (2.3 MiB) Interrupt:44 I expected to see eth0; instead the NIC was named p33p1. The lsmod utility showed that the correct kernel module, i.e. atl1c.ko, was
Have you an Intel BIOS-based motherboard? Have you installed Fedora 16 only to find that your system will not boot and you end up an the GRUB2 rescue prompt wondering what to do? The solution is simple and I will explain it to you in a moment. The problem is due to the way the Intel BIOS developers choose to implement their code based on their understanding of the PMBR (Protective MBR) GPT specification. If you want to read this specification in full, you need to read Section 5 of the UEFI 2.3 specification together with T13 EDD-4 revision 2.
As people start experimenting with Fedora 16 (Verne), many are encountering the concept of of a GPT (GUID Partition Table), the GRUB2 multiboot utility and the concept of a BIOS Boot partition for the first time. Here is how Fedora 16 Beta set up the partitions on a 8Gb disk when all defaults were selected: # parted /dev/vda GNU Parted 3.0 Using /dev/vda Welcome to GNU Parted! Type ‘help’ to view a list of commands. (parted) p Model: Virtio Block Device (virtblk) Disk /dev/vda: 8590MB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags
Now that Fedora 16 (Verne) is in beta, many early adapters are encountering GRUB2, GPT and BIOS Boot partitions for the first time. The concept behind a BIOS Boot partition is not something particularly new. On BIOS-based computers, boot loaders images are larger than can be fitted on a single disk block or two. To overcome this inherent limitation, boot loaders are often split into a number of stages. For instance, GRUB Legacy has Stage1 code that lives in bytes 0 to 445 of the MBR, i.e. LBA0 (Logical Block Address), of a disk, and other code that lives in
This post discusses how to upgrade your Fedora 16 system from a MBR partitioned boot disk booted using GRUB Legacy to a GPT partitioned disk booted using GRUB2 and a BIOS Boot partition. For the purpose of this post I set up a 8Gb SPICE guest, installed Fedora 15 and then upgraded the guest to Fedora 16 Beta using the following commands: # rpm –import https://fedoraproject.org/static/A82BA4B7.txt # yum -y update yum # yum clean all # yum -y –releasever=16 –disableplugin=presto distro-sync Here is what the boot disk looks like after the upgrade from Fedora 15 to Fedora 16 Beta had