Topic: [IMPL] New Via LAN drivers
Via Velocity version 3:
http://www.viaarena.com/default.aspx?Pa … bCatID=130
Rhine and others version 3.67:
http://www.viaarena.com/default.aspx?Pa … bCatID=124
You are not logged in. Please login or register.
Via Velocity version 3:
http://www.viaarena.com/default.aspx?Pa … bCatID=130
Rhine and others version 3.67:
http://www.viaarena.com/default.aspx?Pa … bCatID=124
hi
do you have hardware that requires these?
HWID's available for the hardware?
I almost posted this in the Graphics Driver forum. I have hardware that uses this driver:
Shuttle SK22G2, North Bridge: VIA K8M890CE, South Bridge: VIA VT8237R+, VIA Rhine II Fast Ethernet Adapter
===========
PCI devices
===========PCI\D347PRT\0000 : D347PRT SCSI Controller
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&2411E6FE&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&2411E6FE&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&2411E6FE&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&2411E6FE&0&C3: PCI standard host CPU bridge
PCI\VEN_1106&DEV_0336&SUBSYS_00000000&REV_00\3&2411E6FE&0&00: VIA Standard Host Bridge
PCI\VEN_1106&DEV_0571&SUBSYS_30801297&REV_06\3&2411E6FE&0&79: VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_1336&SUBSYS_00000000&REV_00\3&2411E6FE&0&01: VIA Standard Host Bridge
PCI\VEN_1106&DEV_2336&SUBSYS_00000000&REV_00\3&2411E6FE&0&02: VIA Standard Host Bridge
PCI\VEN_1106&DEV_3038&SUBSYS_30801297&REV_81\3&2411E6FE&0&80: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30801297&REV_81\3&2411E6FE&0&81: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30801297&REV_81\3&2411E6FE&0&82: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_30801297&REV_81\3&2411E6FE&0&83: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3044&SUBSYS_30441106&REV_80\3&2411E6FE&0&50: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1106&DEV_3059&SUBSYS_C5E01297&REV_60\3&2411E6FE&0&8D: Realtek AC'97 Audio for VIA (R) Audio Controller
PCI\VEN_1106&DEV_3065&SUBSYS_01021019&REV_78\3&2411E6FE&0&90: VIA Rhine II Fast Ethernet Adapter
PCI\VEN_1106&DEV_3104&SUBSYS_30801297&REV_86\3&2411E6FE&0&84: VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3149&SUBSYS_30801297&REV_80\3&2411E6FE&0&78: VIA Serial ATA Controller - 3149
PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&2411E6FE&0&88: VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_3230&SUBSYS_30801297&REV_11\4&17BB0CCE&0&0008: VIA Chrome9 HC IGP
PCI\VEN_1106&DEV_3336&SUBSYS_00000000&REV_00\3&2411E6FE&0&03: VIA Standard Host Bridge
PCI\VEN_1106&DEV_4336&SUBSYS_00000000&REV_00\3&2411E6FE&0&04: VIA Standard Host Bridge
PCI\VEN_1106&DEV_5336&SUBSYS_00000000&REV_00\3&2411E6FE&0&05: VIA I/O APIC Interrupt Controller
PCI\VEN_1106&DEV_7336&SUBSYS_00000000&REV_00\3&2411E6FE&0&07: VIA Standard Host Bridge
PCI\VEN_1106&DEV_A238&SUBSYS_00000000&REV_00\3&2411E6FE&0&10: VIA PCI to PCI Bridge Controller
PCI\VEN_1106&DEV_B188&SUBSYS_00000000&REV_00\3&2411E6FE&0&08: VIA CPU to AGP2.0/AGP3.0 Controller
PCI\VEN_1106&DEV_C238&SUBSYS_00000000&REV_00\3&2411E6FE&0&18: VIA PCI to PCI Bridge Controller
PCI\VEN_14F1&DEV_8800&SUBSYS_C1111461&REV_05\3&2411E6FE&0&58: Multimedia Video Controller
PCI\VEN_14F1&DEV_8801&SUBSYS_C1111461&REV_05\3&2411E6FE&0&59: Multimedia Controller
PCI\VEN_14F1&DEV_8802&SUBSYS_C1111461&REV_05\3&2411E6FE&0&5A: Multimedia Controller
30 matching device(s) found.
Yes, I have an Abit KV8-Pro mainboard. I use the gigabit controller.
I just posted the topic to let you all know that they were updated.
===========
PCI devices
===========
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&13C0B0C5&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&13C0B0C5&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&13C0B0C5&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&13C0B0C5&0&C3: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_0041&SUBSYS_0000270F&REV_A1\4&26E5F5CD&0&0008: NVIDIA GeForce 6800
PCI\VEN_1102&DEV_0004&SUBSYS_00511102&REV_03\3&13C0B0C5&0&58: Creative SB Audigy
PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_00\3&13C0B0C5&0&5A: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_03\3&13C0B0C5&0&59: Creative Game Port
PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&13C0B0C5&0&00: VIA Standard Host Bridge
PCI\VEN_1106&DEV_0571&SUBSYS_1413147B&REV_06\3&13C0B0C5&0&79: VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&13C0B0C5&0&01: VIA Standard Host Bridge
PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&13C0B0C5&0&02: VIA Standard Host Bridge
PCI\VEN_1106&DEV_3038&SUBSYS_1413147B&REV_81\3&13C0B0C5&0&80: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_1413147B&REV_81\3&13C0B0C5&0&81: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_1413147B&REV_81\3&13C0B0C5&0&82: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_1413147B&REV_81\3&13C0B0C5&0&83: VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3104&SUBSYS_1413147B&REV_86\3&13C0B0C5&0&84: VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3119&SUBSYS_1413147B&REV_11\3&13C0B0C5&0&70: VIA Networking Velocity-Family Giga-bit Ethernet Adapter
PCI\VEN_1106&DEV_3149&SUBSYS_1413147B&REV_80\3&13C0B0C5&0&78: VIA Serial ATA Controller - 3149
PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&13C0B0C5&0&88: VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&13C0B0C5&0&03: VIA Standard Host Bridge
PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&13C0B0C5&0&04: VIA Standard Host Bridge
PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&13C0B0C5&0&07: VIA Standard Host Bridge
PCI\VEN_1106&DEV_B188&SUBSYS_00000000&REV_00\3&13C0B0C5&0&08: VIA CPU to AGP Controller
Last edited by Ton80 (2007-04-28 23:32:47)
Hi
That is good, this way it can be tested by requestee and "google hits"
'I' will let you know when we have a test pack.
'I' -can be- team member whom took task.
Last edited by jtdoom (2007-04-29 06:26:48)
Yes, I have an Abit KV8-Pro mainboard. I use the gigabit controller.
I just posted the topic to let you all know that they were updated.
Just because there is an update does not mean that it should get added.
Some times new drivers create more problems than they solve.
If a driver already exists in a pack there must be a valid reason to upgrade. (if it ain't broke don't fix it)
It is worth considering if it solves a problem or it adds support for more HWID's
So we need someone with the actual hardware to test a updated pack to see if it works before we release it
(IE if you dont have the hardware or are not willing to test a pack don't bother asking)
so normaly we require HWIDS and a reason to add.
"because there IS a new one" is not a reason!
true all, too true.
ok then . The new driver works fine. Well this project is no good to me if it's not kept up to date.
Think about it. What the heck is the point of taking the time to slipstream old drivers AND then having to install new drivers on top of them after a windows install? Isn't that wasting time and defeating the whole goal of this project? <scratching my head in confusion>. But hey it's your project.
Edit: Why the heck are Via win98-ME driver files included in the current LAN pack??? Isn't the purpose of this project to create an Ultimate XP install disc??? So if there are wasted space taken up in Via what are the others like now? Guys/gals space is premium on a 700 MB disc with all the addons from RyanVM.
Last edited by Ton80 (2007-04-30 00:58:30)
The Goal is to support All Hardware for x86 5.x 32 bit OS's.
if you
slipstream old drivers AND then having to install new drivers on top of them
then there must be a reason you "HAVE to install new drivers on top of them "
(Just because they exist does not require you to HAVE to update them)
(if somebody came out with an updated floppy disk driver I doubt i'd install it)
As I said because it's newer - does not mean - it's better. there is this thing they call BUGs!
hey look here! new drivers! doesnt help you or us.
It might be better - if it is it will be added. The only way we know if its better is if we see problems, or lack there of.
If New HWID's exist then it's guaranteed.
The goal is to have the best driverpacks, meaning the most compatable and reliable drivers.
Those may not necessarily be the newest, but, they just might be!
We need the research of users to prove new drivers.
what are your HWID's and your issue - that is how we decide.
If there is no benefit, then a new driver is not needed?
(Your driver got tested and is ready for release isn't it?)
Last edited by OverFlow (2007-04-30 09:22:33)
Ok I understand your point. It's just sounded at first as the same old excuse I keep hearing for not updating stuff from others. I apologize for any uselessness on this.
I'll try to help if I can but this is my only machine so I can't waste time rebuilding an install every week. There is just too much that I use and do everyday.
This is getting off topic but to be honest, I've got to disagree. We are a small group of testers, just because we are not aware of any bugs in existing drivers it doesn't mean they aren't there. You've got a point in that new drivers can contain issues but on the whole every newer driver I install is almost always without issue. They could improve performance for example. Without fail drivers do improve over time.
So does that mean we are now going to test every single driver (if the HWIDs remain the same) and then if it is "better" (some magic method that if we like it, then it goes) then it gets put in?
Just my 2p anyway.
I said it and I am sticking to it...
If it aint broke dont fix it...
why spend hours updating stuff that is working perfectly as is????
we are a small group of testers - that is my point too
the existing drivers in the packs however have been tested by thousands of people.
so what is better one that has been tested by thousands of people or an unknown?
Just so you can try to create a problem is the only answer i can come up with.
(if there was a performance increase that would be considered a valid reason
however he didn't say that his HDD was faster after the driver upgrade did he?)
better isn't a magic decision - if it adds HWID's then its worth it. if it addresses an existing issue then its worth it.
because there is a new one is not valid period....
and yes i think every driver that gets put in the pack should be tested - don't you?
what good is a driver pack that doesn't work???
because we are a small testing team is reinforcement of my point. a driver that is known good and tested by thousands of users is prefered to an unknown unless there is a GOOD reason.
a tested known good driver with no problems doesnt need to be replaced with an unknown quantity .
Last edited by OverFlow (2007-05-01 07:59:20)
Hi Ton80
if install worked with the older LAN pack, and the newer update adds HWIDs you cannot test, then it just a matter of time before someone with unsupported HWID makes a request to use the newer one.
there are times that an update drops support for some but not all older HWIDS supported in its pre-decessor.
Suppose we updated it and your kit no longer installs.
OK.. I know, we look at the list of supported devices, and sometimes have to add an udate AND keed the predecessor IN.
This still requires that somebody whom says he has the hardware has to test it.
This can be done with a spare hard disk, just like most testers here do.
This seems to be a discussion of "If it ain't broke, then don't update." VS "Keep it as up-to-date as possible.". I support the latter. Why?
1) Because it often avoids problems that only arise after some time. I.e. version 2 can be working just fine, but version 3 might add better performance or (more likely) fix some bugs. Note that for many drivers, we don't get changelogs. So we can assume, that if the .inf file didn't change, it was bug fixes. And as wel all know, bug fixes are of critical importance.
2) It's true that we can't always (actually not even often) verify updated drivers, simply because we don't have all the devices. But in general, updated device drivers do not create more problems, they solve problems. See 1).
So, in my opinion, updates are important.
Implemented
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.023 seconds, 11 queries executed ]