Re: VIA 686B/Data Corruption FAQ
> http://www.viahardware.com/686bfaq.shtm > > Couldn't find a mention of this in the archives, but those interested in > the VIA chipset issues should check this out. The page contains the > following officail statement from VIA: Yeah I've seen it, but they won't tell people what is in it which is useless to non windows people. The whole procedure is quite complex because the fixups depend which PCI cards you have (eg ES137x 'SB PCI 64/SB PCI 128' cards don't work with the base set of fixups but apparently use a different set) Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA 686B/Data Corruption FAQ
http://www.viahardware.com/686bfaq.shtm Couldn't find a mention of this in the archives, but those interested in the VIA chipset issues should check this out. The page contains the following officail statement from VIA: Yeah I've seen it, but they won't tell people what is in it which is useless to non windows people. The whole procedure is quite complex because the fixups depend which PCI cards you have (eg ES137x 'SB PCI 64/SB PCI 128' cards don't work with the base set of fixups but apparently use a different set) Alan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
VIA 686B/Data Corruption FAQ
http://www.viahardware.com/686bfaq.shtm Couldn't find a mention of this in the archives, but those interested in the VIA chipset issues should check this out. The page contains the following officail statement from VIA: The data corruption error, which some web sites and people have reported with the 686b Southbridge, is caused by incorrect bios registry setting to the Northbridge. These bios settings were made by motherboard manufacturers, in an attempt to fix a conflict with the Sound Blaster Live Value cards. Information has been provided to all motherboard manufacturers on how to correctly resolve both the data corruption error and the Sound Blaster Live conflict. The patch released by VIA in the 4in1 4.31 drivers replicates the correct bios settings. We provided this patch to make sure as many people got a fix to their Sound Blaster Live problems as soon as possible. Most motherboard manufacturers have now corrected their bios and the patch is not necessarily needed although it will not harm any VIA based system if installed. -- Gareth - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
VIA 686B/Data Corruption FAQ
http://www.viahardware.com/686bfaq.shtm Couldn't find a mention of this in the archives, but those interested in the VIA chipset issues should check this out. The page contains the following officail statement from VIA: The data corruption error, which some web sites and people have reported with the 686b Southbridge, is caused by incorrect bios registry setting to the Northbridge. These bios settings were made by motherboard manufacturers, in an attempt to fix a conflict with the Sound Blaster Live Value cards. Information has been provided to all motherboard manufacturers on how to correctly resolve both the data corruption error and the Sound Blaster Live conflict. The patch released by VIA in the 4in1 4.31 drivers replicates the correct bios settings. We provided this patch to make sure as many people got a fix to their Sound Blaster Live problems as soon as possible. Most motherboard manufacturers have now corrected their bios and the patch is not necessarily needed although it will not harm any VIA based system if installed. -- Gareth - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
