Eric Malkowski <e...@bvwireless.net> wrote: >Hey Kyle- > >pcie_aspm=off got me to installing a Fedora 17 "minimal" install (does >210 packages) to a pair of 2.5" drives I've got in there w/ the HD >mount >kit. I set it up with 3 x RAID-1 partitions for boot, swap, and root >filesystem (probably don't need swap, but plenty of disk space). > >I'm suspecting this will succeed which will be good.
The only other trick is that you'll have to re-adjust the grub config post install. The pcie_aspm=off will not carry through to the installed system. --Kyle > >Since aspm appears to be power management related stuff I really don't >care about power with this -- it's to be a firewall and forward packets > >all day! Something I read was saying performance should be fine w/o >aspm enabled. > >Thanks for the tip. > >In case anyone else runs into it -- when pxebooting on fedora 17 >(unlike >earlier releases) you have to specify a repo path on the kernel cmdline > >or you'll boot up and get a "dracut: unable to process initqueue" error > >and dropped to the shell. So a successful pxelinux.cfg directory setup > >for my box looks like this (note the repo= line and the pcie_aspm=off) >where I downloaded the kernel and ramdisk from a mirror and named them >with the .f17 extensions: > >DEFAULT f17 > >LABEL f17 > KERNEL vmlinuz.f17 > APPEND initrd=initrd.img.f17 pcie_aspm=off >repo=http://dl.fedoraproject.org/pub/fedora/linux/releases/17/Fedora/i386/os/ > >console=ttyS0,115200 text > >I obviously also upped my console serial speed to 115,200 bps. > >The vnc graphical install is working very well for this. >Just need to now figure out how to install grub2 on 2nd MBR if the >install doesn't automagically do it and test out deliberate disk >failure >so I'll know I can replace a disk down the road and know that it will >boot with either disk. I'm using 2 x Western digital Scorpio black 160 > >gig 2.5" drives 7200 RPM. > >-Eric Malkowski > > >On 07/05/2012 10:04 PM, Kyle Brantley wrote: >> On 7/5/2012 5:53 PM, Eric Malkowski wrote: >>> Hey all- >>> >>> Got a shiny new net6501 I'm trying to install Fedora on. Tried >Fedora >>> 17 and ran into this problem: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=625776 >>> >>> Towards the end of the bug report is a reference to this mailing >list: >>> >>> "It looks like this is also impacting RHEL (CentOS). >>> >>> >http://lists.soekris.com/pipermail/soekris-tech/2011-October/017822.html >>> >>> The piece of hardware mentioned in that thread (the Soekris net6501) > >>> has four 82574 NICs, and is headless. PXE is the primary method of >>> installation, so this prevents it from being installed at all. Even >>> if installed via an alternative method, then I wind up with four >>> useless NICs." >>> >> Yup, that's my comment. >> >>> It is fixed in 3.5-rc1 (see tail end of bug report) and there is a >>> rawhide kernel RPM for it, but rawhide doesn't seem to have any >>> initrd.img built up to go with that kernel (the usual "images" >directory >>> to get pxe stuff isn't in the download area for Fedora as far as I >>> can tell. >> They don't typically rebuild the install packages for these types of >> bugfixes in Fedora -- I'd expect to see it in F18. >>> If no one's gotten fedora working, anyone have any success with >CentOS? >>> As you can tell I'm a Fedora / Redhat fan. >> The RHEL 6.3 release notes indicates that the relevant driver >(e1000e) >> was updated, so I hope that the fix was included with this. Note that > >> booting with pcie_aspm=off allows you to install CentOS6 / RHEL6 / >etc >> with the 6.0-6.2 install media, but I have high hopes that the 6.3 >> kernel and initrd will fix it properly. >>> Thanks. >>> >>> >>> >>> _______________________________________________ >>> Soekris-tech mailing list >>> Soekris-tech@lists.soekris.com >>> http://lists.soekris.com/mailman/listinfo/soekris-tech >> --Kyle _______________________________________________ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
