Not sure exactly whether to try to bugzilla or not,... my F14 alpha issues are all kind of vague, weird stuff that's hard to pin down.
I'm running an eeepc 901.
I've made a bootable usb using the liveusb creator. things kinda more or less work. specifically, the rt2860sta wireless works. for a while. then it quits. only way I found to make it work again is to reboot. the NM applet doesn't say it's disconnected, but it doesn't work.
when I try to run yum update (or the gui updater) it tries to update over 300 packages, runs for HOURS and HOURS (probably a combination of a slow computer and a slow USB flash drive). somewhere early in the downloads the wireless goes down so I have to plug in a wired network, then it proceeds. hours and hours (and hours) later it's still futzing around doing cleanups. I left it for a day and a half (I did say it was slow) where it seemed to be stuck, still saying it was cleaning up but no visible activity I could find.
gave up, rebooted. now the flash drive won't boot.
ok, so using a different approach I did a fresh install on the usb flash drive--boot up the live CD and choose "install to hard drive". choose the flash drive. fine. installs. reboots. (I've also actually done a real install onto the usb flash drive with F13 beta, which worked fine, so I believe this method is legitimate.)
same problems. after a bit of network activity wireless goes down. never mind, just use wired network. trying to run all the updates takes forever (and ever, amen). may or may not ever complete. resulting system either won't boot, or when it does, no network is enabled. can't start network, only device is 'lo'.
went around this 3 or 4 times before giving up. tried the LXDE spin, just for fun. no difference.
Good news is that the built in rt2860sta driver works fine, for a while, which in F13 it never did at all.
tried using yum update with a list of things to update, by installing 25 or 30 at a time to see if I could get it updated in chunks, since doing all 330 of them didn't work. after the second batch, that was the time a reboot had no visible network.
I'd like to assist by reporting bugs against all this, but it's a little hard for me to find concrete things to report, here.
Anyone else seen such problems? Or suggestions for dealing with them?