Re: FC2 versus FC3 -- my own experiences

From: Cal Vanize (forgetthespam_at_finallyfree.com)
Date: 04/21/05 

Date: Wed, 20 Apr 2005 20:52:03 -0500

JDS wrote:
> On Wed, 20 Apr 2005 17:16:41 -0400, General Schvantzkoph wrote:
>
>
>>What kind of hardware do you have? It sounds like you've got some unusual
>>device or chipset that uses a driver that somehow got broken in a recent
>>kernel.
>
>
> Athlon 2200+, 512 MB RAM, 60GB IDE disk drive
>
> This machine was built by pogolinux in 2002 and originally came with
> RHL7.3 installed.
>
> It is not weird hardware, though, I don't think.
>
> Here is lspci output for more info on some devices:
> [jeff@newt jeff]$ /sbin/lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
> 00:05.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
> 00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0c)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
> 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> 00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23)
> 00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23)
> 01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a4)
>
> later, all...
>

I have had FC3 running on VIA (not KT266) and nVidia chipsets using GF2
and FX5200 nVidia video cards without issues. T-bird and Firefox run
fine. In fact, I tried several other distros and kept coming back to
FC3 for performance and stability.

Relevant Pages

  • [PATCH -MM] e1000: rewrite hardware initialization code
    ... This patch contains a major rewrite to the e1000 driver that groups and separates e1000 hardware by chipset family. ... It abstracts the hardware specific code into an API that will allow us to continue to maintain the complex e1000 driver and add new hardware support to it without touching code that affects older chipsets. ...
    (Linux-Kernel)
  • Re: sata_nv issues with MCP51 SATA controller
    ... The motherboard that I'm going to swap to has actually been tested (with MS Windows OS+driver) for more than a day with a disk connected, so if this MB also fails, I think it will be safe to say that the issue is with the sata_nv driver... ... Sounds like a hardware problem, since disabling ADMA is generally the cure-all we use -- it appears to stress the hardware less. ... chipset does not support ADMA in the first place. ...
    (Linux-Kernel)
  • Re: I have tried to fix this on my own but I cant do it without help
    ... Although XP is pretty good about recognizing hardware, ... I would guess that XP needs a driver for this hardware. ... It is hard to imagine that updating the motherboard BIOS (Intel chipset) ... would like to try to install is called Driver Installer Frameworks Tools ...
    (microsoft.public.windowsxp.hardware)
  • Re: Wireless PCI recommendations?
    ... >> atheros and it's madwifi driver. ... found I've ordered board_a only to find that they change to chipset ... Of course chipset B is one of the non-Linux driver chipsets. ... > hardware whose makers are willing to conform to open standards or at ...
    (Fedora)
  • Re: FC2 versus FC3 -- my own experiences
    ... >>device or chipset that uses a driver that somehow got broken in a recent ... > It is not weird hardware, though, I don't think. ...
    (alt.linux)