I wonder if anyone has successfully installed Fedora-17 through a USB stick? I tried two ways - with the DVD iso, and with the KDE Live CD iso - on two machines, and met the same problem in all 4 cases: only half-a-dozen modules were listed by lsmod, and these did not include the ethernet or WiFi drivers. I believe that this was due to a grub2 problem, though I'm not sure about that. In both cases lspci saw the hardware devices, but they did not appear in /etc/udev/rules.d/ .
It's possible there was a problem with my USB stick, though there was said to be a check in all cases. (I had checksum-med both ISOs.)
I managed to install Fedora-17 on both machines with netinstall.iso on a CD . This went perfectly, after a couple of silly messages about floppies.
On Sun, Jun 3, 2012 at 4:40 PM, Timothy Murphy gayleard@eircom.net wrote:
I wonder if anyone has successfully installed Fedora-17 through a USB stick? I tried two ways - with the DVD iso, and with the KDE Live CD iso - on two machines, and met the same problem in all 4 cases: only half-a-dozen modules were listed by lsmod, and these did not include the ethernet or WiFi drivers. I believe that this was due to a grub2 problem, though I'm not sure about that. In both cases lspci saw the hardware devices, but they did not appear in /etc/udev/rules.d/ .
It's possible there was a problem with my USB stick, though there was said to be a check in all cases. (I had checksum-med both ISOs.)
I managed to install Fedora-17 on both machines with netinstall.iso on a CD . This went perfectly, after a couple of silly messages about floppies.
I dd'ed the full DVD (not the KDE LiveCD) into a 8GB USB and used to to upgrade / fresh install F17 on multiple machines without issues. *
- Gilboa * Beyond the notorious anaconda uses f16 kernel instead of f17 kernel leading to KIA machine.
Gilboa Davara wrote:
I wonder if anyone has successfully installed Fedora-17 through a USB stick? I tried two ways - with the DVD iso, and with the KDE Live CD iso - on two machines, and met the same problem in all 4 cases: only half-a-dozen modules were listed by lsmod, and these did not include the ethernet or WiFi drivers. I believe that this was due to a grub2 problem, though I'm not sure about that. In both cases lspci saw the hardware devices, but they did not appear in /etc/udev/rules.d/ .
I dd'ed the full DVD (not the KDE LiveCD) into a 8GB USB and used to to upgrade / fresh install F17 on multiple machines without issues. *
First, apologies for posting to this newsgroup - I meant to aim for the fedora.general list. However, the systems I was installing were actually both Fedora-17/KDE, so I wasn't too far off.
I used a very cheap 32GB USB stick - maybe that was the cause of my problems ...
I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
On Sun, Jun 3, 2012 at 11:27 PM, Timothy Murphy gayleard@eircom.net wrote:
Gilboa Davara wrote:
but they did not appear in /etc/udev/rules.d/ .
I dd'ed the full DVD (not the KDE LiveCD) into a 8GB USB and used to to upgrade / fresh install F17 on multiple machines without issues. *
First, apologies for posting to this newsgroup - I meant to aim for the fedora.general list. However, the systems I was installing were actually both Fedora-17/KDE, so I wasn't too far off.
I used a very cheap 32GB USB stick - maybe that was the cause of my problems ...
I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
You dd the image into the USB device. The ISO already includes a (weird) partition table. dd if=/xx/FedoraXXX.iso of=/dev/sdX bs=1M
You *may* need to select USB-CD (instead of USB-HDD) in your BIOS boot menu to get it to boot.
- Gilboa
Gilboa Davara wrote:
I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
You dd the image into the USB device. The ISO already includes a (weird) partition table. dd if=/xx/FedoraXXX.iso of=/dev/sdX bs=1M
You *may* need to select USB-CD (instead of USB-HDD) in your BIOS boot menu to get it to boot.
Just to be clear. When I removed /dev/sdb1 (with fdisk) on the USB stick, and dd-ed to /dev/sdb exactly as you suggest, the laptop did boot and I was able to install on my laptop but the resulting system had only half-a-dozen modules installed (according to lsmod). I'm pretty sure the failure had something to do with grub2. I chose the custom layout, incidentally, as I wanted to keep Fedora-16 on another partition.
On Mon, Jun 4, 2012 at 2:45 PM, Timothy Murphy gayleard@eircom.net wrote:
Gilboa Davara wrote:
I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
You dd the image into the USB device. The ISO already includes a (weird) partition table. dd if=/xx/FedoraXXX.iso of=/dev/sdX bs=1M
You *may* need to select USB-CD (instead of USB-HDD) in your BIOS boot menu to get it to boot.
Just to be clear. When I removed /dev/sdb1 (with fdisk) on the USB stick, and dd-ed to /dev/sdb exactly as you suggest, the laptop did boot and I was able to install on my laptop but the resulting system had only half-a-dozen modules installed (according to lsmod). I'm pretty sure the failure had something to do with grub2. I chose the custom layout, incidentally, as I wanted to keep Fedora-16 on another partition.
I think know what happened. Are you sharing boot between F16 and F17 by any chance [1]?
- Gilboa [1] https://bugzilla.redhat.com/show_bug.cgi?id=820351
Gilboa Davara wrote:
I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
Just to be clear. When I removed /dev/sdb1 (with fdisk) on the USB stick, and dd-ed to /dev/sdb exactly as you suggest, the laptop did boot and I was able to install on my laptop but the resulting system had only half-a-dozen modules installed (according to lsmod). I'm pretty sure the failure had something to do with grub2. I chose the custom layout, incidentally, as I wanted to keep Fedora-16 on another partition.
I think I know what happened. Are you sharing boot between F16 and F17 by any chance [1]?
I am. I chose custom layout, and gave /dev/sda2 as /boot, without formatting it.
Basically, I hoped that this would allow me to run Fedora-16 (which I kept on a different partition) as an alternative to Fedora-17.
In fact, when I installed Fedora-17 with netinstall everything worked fine, and I can boot into F-16 or F-17 or Windows, as hoped.
What exactly was my error with the USB stick method? As I mentioned I had the same problem with the DVD iso and with the KDE Live CD (both transferred to the USB stick).
On Tue, Jun 5, 2012 at 3:03 PM, Timothy Murphy gayleard@eircom.net wrote:
Gilboa Davara wrote:
I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
Just to be clear. When I removed /dev/sdb1 (with fdisk) on the USB stick, and dd-ed to /dev/sdb exactly as you suggest, the laptop did boot and I was able to install on my laptop but the resulting system had only half-a-dozen modules installed (according to lsmod). I'm pretty sure the failure had something to do with grub2. I chose the custom layout, incidentally, as I wanted to keep Fedora-16 on another partition.
I think I know what happened. Are you sharing boot between F16 and F17 by any chance [1]?
I am. I chose custom layout, and gave /dev/sda2 as /boot, without formatting it.
Basically, I hoped that this would allow me to run Fedora-16 (which I kept on a different partition) as an alternative to Fedora-17.
In fact, when I installed Fedora-17 with netinstall everything worked fine, and I can boot into F-16 or F-17 or Windows, as hoped.
What exactly was my error with the USB stick method? As I mentioned I had the same problem with the DVD iso and with the KDE Live CD (both transferred to the USB stick).
F17's anaconda installer (or actually, the grub configuration builders) barfs on having the same kernel version on both F16 and F17, causing it to select the wrong kernel for F17 (3.3.7-1.fc16.x86_64). This in-order causes Fedora to oops during either startup or shutdown. In my cases, I encountered this bug on 10/11 machines I installed Fedora on (either new install w/ shared boot or [pre-]upgrade). I solved this problem by forcing grub to load the correct kernel during first-boot [1]. Once up, I rebuilt the grub configuration [2].
- Gilboa [1] Space to get the grub menu, 'e' to edit the grub entry, replace f16 w/ f17 across the board, Ctrl-X to boot. [2] grub2-mkconfig -o /boot/grub2/grub.cfg.
Gilboa Davara wrote:
I think I know what happened. Are you sharing boot between F16 and F17 by any chance [1]?
I am. I chose custom layout, and gave /dev/sda2 as /boot, without formatting it.
Basically, I hoped that this would allow me to run Fedora-16 (which I kept on a different partition) as an alternative to Fedora-17.
In fact, when I installed Fedora-17 with netinstall everything worked fine, and I can boot into F-16 or F-17 or Windows, as hoped.
What exactly was my error with the USB stick method? As I mentioned I had the same problem with the DVD iso and with the KDE Live CD (both transferred to the USB stick).
F17's anaconda installer (or actually, the grub configuration builders) barfs on having the same kernel version on both F16 and F17, causing it to select the wrong kernel for F17 (3.3.7-1.fc16.x86_64). This in-order causes Fedora to oops during either startup or shutdown. In my cases, I encountered this bug on 10/11 machines I installed Fedora on (either new install w/ shared boot or [pre-]upgrade). I solved this problem by forcing grub to load the correct kernel during first-boot [1]. Once up, I rebuilt the grub configuration [2].
Thanks again. That certainly sounds like what happened to me, as grub seemed seriously confused between F16 and F17.
I still find grub2 difficult to configure, and haven't found an entirely satisfactory HOWTO or similar document.
On Sat, Jun 9, 2012 at 3:11 PM, Timothy Murphy gayleard@eircom.net wrote:
Gilboa Davara wrote:
I think I know what happened. Are you sharing boot between F16 and F17 by any chance [1]?
I am. I chose custom layout, and gave /dev/sda2 as /boot, without formatting it.
Basically, I hoped that this would allow me to run Fedora-16 (which I kept on a different partition) as an alternative to Fedora-17.
In fact, when I installed Fedora-17 with netinstall everything worked fine, and I can boot into F-16 or F-17 or Windows, as hoped.
What exactly was my error with the USB stick method? As I mentioned I had the same problem with the DVD iso and with the KDE Live CD (both transferred to the USB stick).
F17's anaconda installer (or actually, the grub configuration builders) barfs on having the same kernel version on both F16 and F17, causing it to select the wrong kernel for F17 (3.3.7-1.fc16.x86_64). This in-order causes Fedora to oops during either startup or shutdown. In my cases, I encountered this bug on 10/11 machines I installed Fedora on (either new install w/ shared boot or [pre-]upgrade). I solved this problem by forcing grub to load the correct kernel during first-boot [1]. Once up, I rebuilt the grub configuration [2].
Thanks again. That certainly sounds like what happened to me, as grub seemed seriously confused between F16 and F17.
I still find grub2 difficult to configure, and haven't found an entirely satisfactory HOWTO or similar document.
I more-or-less returned to the good old lilo days. I automatically rebuild grub2 configuration (grub2-mkconfig -o /boot/grub2/grub.cfg) after every change to system that touches anything remotely close to /boot... Thus far, it worked just fine.
- Gilboa
On Sat, 2012-06-09 at 13:11 +0100, Timothy Murphy wrote:
Gilboa Davara wrote:
I think I know what happened. Are you sharing boot between F16 and F17 by any chance [1]?
I am. I chose custom layout, and gave /dev/sda2 as /boot, without formatting it.
Basically, I hoped that this would allow me to run Fedora-16 (which I kept on a different partition) as an alternative to Fedora-17.
In fact, when I installed Fedora-17 with netinstall everything worked fine, and I can boot into F-16 or F-17 or Windows, as hoped.
What exactly was my error with the USB stick method? As I mentioned I had the same problem with the DVD iso and with the KDE Live CD (both transferred to the USB stick).
F17's anaconda installer (or actually, the grub configuration builders) barfs on having the same kernel version on both F16 and F17, causing it to select the wrong kernel for F17 (3.3.7-1.fc16.x86_64). This in-order causes Fedora to oops during either startup or shutdown. In my cases, I encountered this bug on 10/11 machines I installed Fedora on (either new install w/ shared boot or [pre-]upgrade). I solved this problem by forcing grub to load the correct kernel during first-boot [1]. Once up, I rebuilt the grub configuration [2].
Thanks again. That certainly sounds like what happened to me, as grub seemed seriously confused between F16 and F17.
I still find grub2 difficult to configure, and haven't found an entirely satisfactory HOWTO or similar document.
I had some issues with oopses during shutdown, so after thrashing about for a while I did the following:
cd /boot mv grub grub-save yum reinstall grub2
I conjecture that moving the old grub out of the way may affect how grub2 installs itself, but for whatever reason it appears to have worked.
poc
On 06/04/2012 01:57 AM, Timothy Murphy wrote:
I used a very cheap 32GB USB stick - maybe that was the cause of my problems ... I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
Today I successfully installed F17 (x86_64) from a 4GB USB stick. I dd'ed the DVD ISO image to /dev/sdb (and not sdb1).
A couple of days back, when I tried it the first time, I accidentally started dd-ing to sdb1. Then I aborted the process and then dd'ed to sdb. It was mounting fine and all files were listed, but the PC won't boot from it. I used a Sandisk Cruzer Blade drive which had some weird GPT partition table for some apps that came with it. Anyway, I used 'parted' to remove all partitions and create a new msdos partition table. Then I created a single partition and checked with fdisk if it was fine. Then I dd'ed the DVD iso image and everything worked this time. I don't know what exactly did the trick though!
Syam
On 06/04/2012 07:27 PM, Sonic wrote:
On 06/04/2012 01:57 AM, Timothy Murphy wrote:
I used a very cheap 32GB USB stick - maybe that was the cause of my problems ... I started by dd-ing the DVD iso onto the single partition /dev/sdb1 on the stick. For some reason this did not boot, so I deleted the partition (with fdisk) and dd-ed the iso onto /dev/sdb . Maybe that was my error?
Today I successfully installed F17 (x86_64) from a 4GB USB stick. I dd'ed the DVD ISO image to /dev/sdb (and not sdb1).
A couple of days back, when I tried it the first time, I accidentally started dd-ing to sdb1. Then I aborted the process and then dd'ed to sdb. It was mounting fine and all files were listed, but the PC won't boot from it. I used a Sandisk Cruzer Blade drive which had some weird GPT partition table for some apps that came with it. Anyway, I used 'parted' to remove all partitions and create a new msdos partition table.
Oops.. I forgot to mention that I first 'erased' the disk completely by doing: dd if=/dev/zero of=/dev/sdb
Took way too much time..
Syam
-
Gilboa Davara -
Patrick O'Callaghan -
Sonic -
Timothy Murphy