On Jun 2, 2008, at 7:16 AM, James Cameron wrote:
> On Mon, Jun 02, 2008 at 08:22:40PM +1000, Martin Langhoff wrote:
>> That makes bit more sense. A bad pci connection... but I'm not sure
>> why it didn't come up with the right ip addr. I do wonder whether the
>> fedora tools have anything to auto
On May 30, 2008, at 5:34 PM, Anna wrote:
>>> The other weird device thing involved the second NIC. The first
>>> one gets recognized as eth0 just fine. However, the second one is
>>> seen as dummy0. I put the hardware address for the second NIC in
>>> both /etc/sysconfig/olpc-scripts/ifcfg-
On Mon, Jun 02, 2008 at 08:22:40PM +1000, Martin Langhoff wrote:
> That makes bit more sense. A bad pci connection... but I'm not sure
> why it didn't come up with the right ip addr. I do wonder whether the
> fedora tools have anything to automagically define a "device affinity"
> once it's seen a
What is the HW? Output of dmesg, lsmod and lspci should help here.
Perhaps the IDE/SATA bus is misconfigured at the BIOS or you have a
CDROM drive as master in the first channel?
Something _must_ be appearing as sda, what is it?
Sorry for the lack of promptness, but they didn't invit
On Mon, May 26, 2008 at 6:06 AM, Anna <[EMAIL PROTECTED]> wrote:
> Instead of the prompt to pick the timezone, I got an error about
> anaconda not finding an sda device. After some messing around, I
> realized the hard drive was being seen as sdb.
What is the HW? Output of dmesg, lsmod and lspci
Friday afternoon, I installed 163 on another machine at Glen Iris. At
first I thought the problem was with 163, so I gave 161 a go, but still
had the same error so I persevered on with 163.
Instead of the prompt to pick the timezone, I got an error about
anaconda not finding an sda device. Af
