On Wed, Dec 31, 2008 at 12:37:21PM +0900, John Summerfield wrote:
On first boot, I tried to configure the network - I had copied fhe firmware into place before rebooting after the install), but the text-mode network install doesn't understand wireless.
Not entirely true but indeed a default way to do that is through a NetworkManager (a.k.a. NetworkMangler) and that assumes a graphic environment. It is always possible to bring wireless up using iwconfig and/or wpa_supplicant but this is relatively "low level".
Note, I've not seen any documentation of how to do this for Fedora,
'man iwconfig' (with a section "SEE ALSO") and 'man wpa_supplicant'.
I was quite surprised though to find it's eth0 in F10 (at least some of the time), it used to be eth1
Something else already took eth0. Do you have a wired interface on this board? Names and assignments can be changed but they are written "automagically" in udev rules and kept for later. Dig a bit in files in /etc/udev/rules.d/ and you will find that out.
These don't look good to me: [mi] EQ overflowing. The server is probably stuck in an infinite loop.
Aha! Intel graphics, right? Known bug. https://bugzilla.redhat.com/show_bug.cgi?id=469292 For now create a skeleton xorg.conf with a help of 'Xorg -configure' and add an option "NoAccel" to it. Details in the reference bug report (and I was hit by it too). A display slows down but it works.
BTW - some desktop heads are stuck with an idea that forcing gdm on the first console, for some illusory gains but a lot of extra troubles, is a good thing to do. As a result 'chvt 1' "does not work" as you do not have getty running there; but it is not difficult to find a text console with 'chvt 2' or a bit higher.
I have to have this system running, Mrs S requires it.
It will run; even quite well if not perfect but try less emotional approach and search bugzilla for troubles. I do have similar requirements. :-)
... but I plan on trying CentOS5 first.
You are likely to bump into wireless issues.
Michal