Fedora Core Five Borked!

[Harold Hallikainen]

> On Mon, 2006-06-26 at 10:21 -0700, Harold Hallikainen wrote:
>> > On Mon, 2006-06-26 at 05:37 -0700, Harold Hallikainen wrote:
>> >> > My FC5 system died. It won't boot. It gets to a line that says:
>> >> >
>> >> > device-mapper: 4.6.0-ioctl (2006-02-17) initialised:
>> >> dm-devel at redhat.com
>> >> >
>> >> > and just hangs. The system has mirrored sata_sil disks, with a
>> couple
>> >> IDE
>> >> > disks and a DVD/RW drive.
>> >> >
>> >> > Apparently, from my testing and messing around, it's after a
>> nightly
>> >> yum
>> >> > update that the system quit booting. I reinstalled twice now. The
>> >> sytem
>> >> > rebooted and worked fine, then I did
>> >> >
>> >> > yum update
>> >> >
>> >> > which updated over 600 packages and the system wouldn't boot the
>> next
>> >> time
>> >> > I
>> >> > tried to reboot. So, this time I haven't updated it and it's booted
>> >> > several
>> >> > times just fine. I think I'll go ahead and let it update, then not
>> >> shut it
>> >> > down until a few more updates of things... I did find a google (one
>> >> hit)
>> >> > that
>> >> > stated something about using devel repos. There's one for fedora,
>> >> which
>> >> > I've
>> >> > renamed and I suspect that might be my problem, so may do an update
>> >> > without
>> >> > those enabled.
>> >> >
>> >> > So, what's the general concensus, if any, on this issue?
>> >> >
>> >> > TIA,
>> >> >
>> >> > Karl
>> >>
>> >>
>> >> I earlier posted a question asking about a Linux equivalent of Norton
>> >> Ghost (thanks for the responses!). Instead of patiently waiting for
>> >> responses and saving an image of the hard drive in my laptop, I went
>> >> ahead
>> >> and tried an FC5 update. After the install, it complained about some
>> PCI
>> >> problem (I had problems like this previously with kernel updates) and
>> it
>> >> would not run the X server. I could not "update" back to FC4, so I'm
>> now
>> >> doing a fresh install. So... guess it doesn't work with everything!
>> This
>> >> is an HP Athalon laptop.
>> >
>> > I might be able to help here.  I have an HP ZV6116US Athlon-64 laptop.
>> > The "can't reserve PCI blah" stuff is innocuous...don't worry about
>> it.
>> > As to your X problem, it's most likely the nVidia driver.  Make sure
>> you
>> > install the livna nVidia driver.  If you use the livna fglrx driver
>> for
>> > x86_64, note that it is borked, but X will run without GL acceleration
>> > despite the message that's generated.
>> >
>>
>> Thanks Rick! When the "can't reserve PCI" stuff first started showing up
>> (after an FC4 kernel update), my wireless ndiswrapper stuff stopped
>> working. I went back to a previous version of the kernel and the errors
>> went away and the wireless started working. On video, I've been able to
>> use the ATI driver. The machine is something in the ZV6000 series (they
>> don't put the full model number on the case), but I'll have to look at
>> the
>> exact model when I get home. Do you have FC5 working on your machine
>> (including wireless)?
>
> Oh, gawd, right, it's the ATI chipset...NOT the nVidia.  My mistake.  I
> also have a normal Athlon machine with nVidia and I got confused.  The
> fglrx stuff still holds true on X86_64.
>
> As far as the wifi is concerned, I use ndiswrapper--not the bc43xx
> driver.  In my experience, the bc43xx driver has major issues with
> WEP/WPL and managed networks.  I don't think it's quite "ready for
> prime time".

I've been messing with FC5 some more on my HP laptop (after I messed up
the FC4 installation again). Anyway, it does seem to support the ATI
chipset at high resolution without loading the driver from ATI. I tried
putting in ndiswrapper, and it complained during make about not finding
some source (I'm at work, and the machine is at home, so this is from
memory). The ndiswrapper documentation says something about setting up a
link into the kernel source, but I haven't been able to figure out exactly
what needs to be done there yet. Looking into it, though, I did find that
FC5 apparently natively supports the Broadcom wifi chipset (which is
probably what you discussed above, but I did not recognize it at the
time). So far, I've only found message board documentation on the native
driver. Is there any more documentation on it? Or, what did you add to get
ndiswrapper to make?

THANKS!

Harold


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!