> On 5/22/05, linux user <linuxusr@xxxxxxxxxxxx> wrote: > > > I was able to overcome this problem regarding FC3 x86_64 installation > > > and a buggy x server. > > > 1. First I performed the initial full install. > > > 2. booted into init 3 or single user mode after installation. > > > > Great. How can this be done? > > At the GRUB boot prompt, press a key to show the menu, then press 'a' > on the Fedora boot line and the type " 3" (space, 3) and press enter > to boot. I'm not sure how this affects the "first boot" sequence. Ok. I messed up your instructions. Rather than appending to boot options, I was trying to 'c' command it. The boot goes fine, when I follow your instructions. > > > > 3. without initiating the graphic mode performed up2date from root > > > command line. > > > > Is that it? Type "up2date" at the prompt in single user mode? > > I think you have to run it with an option for no X, or run up2date-nox > I think. There is also yum which will accomplish the same thing "yum > -y update" The -y tells it to go ahead and update without prompting > you so you can go away and let it finish. It will take a while. If > you can wait, you might just want to wait the couple weeks for FC4 to > come out : ). I couldn't get up2date to work properly, so I used the yum command you provided. It appears to be working fine. I'll let you know how it goes. Thanks for your help! > > A note. The "buggy x server" must just be a buggy driver for > particular card(s), since my FC3 x86_86 install went just fine and X > worked just fine for me on my nVidia 440 Go. I have no idea what kind > of support there is for the S3 card you have. The differences between > i386 and x86_64 that you have noted do seem strange, though. > > Jonathan > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >
