Sorry, I should have mentioned - I use XP Home, the serial port is enabled in the BIOS, the Epia 4-in-1 drivers are loaded and seem to be working, the port is setup and recognized by Windows. But no data is flowing. Woe is me.
After using this mobo for a while and having trouble connecting touchscreen, OBDII and gps using the onboard serial port, I've determined that it is indeed the board that is bad. I was always assuming that the thing I was plugging in was not working, either a bad driver, plug, etc.
The first indication was when I plugged in the serial touchscreen controller and it wouldn't work. Of course this was just after I had installed the Xenarc into my dash. So I assumed that I had done something to the touchscreen during the install. I bought a new usb controller and everything was fine.
Then I tried to plug my OBDII reader into the serial port. Same thing - it wouldn't work and I assumed a bad driver or reader. But when I hauled my desktop down to the garage and plugged it in there, it worked. hmmm
Serial gps - same thing - no workee.
I also tried to get the second serial port on the EPIA working. Guess what - it wouldn't. Which I expected after reading the Via forums.
So I've replaced the EPIA with a microATX, but it ticks me off that this EPIA has no serial ports that can work, probably from the day I bought it, and I never realized. Does anybody else have this problem and if so how did you fix it?
*******************************
*******************************
Sorry, I should have mentioned - I use XP Home, the serial port is enabled in the BIOS, the Epia 4-in-1 drivers are loaded and seem to be working, the port is setup and recognized by Windows. But no data is flowing. Woe is me.
*******************************
*******************************
i have the same problems on my m9000 com2. com1 works though...
good thing i got a m10000 for free recently ... haven't set it up yet though
Car: 2000 Toyota Celica GT-S
Mods: Yep
Carputer: VIA M9000 | Opus 150 | 512MB PC2100 | 60GB Notebook HD | Slim/Slot DVD/CDRW | Audigy2NX | Xenarc 700TSV | (2) DSCustoms DS700HRS (in trunk) | SMC USB 802.11b | CoPilot | DLink FM tuner | Cliffnet
OK so I guess I solved my own problem. Flashed the newest BIOS (1.13) and loaded the newest 4-1 drivers. Now everything is working - Comm 1 is OK and I no longer get BSOD when my Dlink radio driver loads.
So, out with the microATX and back in with the Epia.
*******************************
*******************************
I keep hearing about how com2 doesnt work for people. Mine works great with my Creative Remote and the latest bios flash. I guess for once I got a good one!
2005 Ford Focus ST
Have you used the right adapter cable for COM2. VIA does not use the common serial wiring scheme. Therefore one must use a special cable (I believe 1:1 from IDC pinout to SubD pinout). There should be more info on this subject on the forums.Originally Posted by 00CericaRuss
white bream working on a trilogy: CARGO - UNIGO - MERGO
CARGO = the Car Computer
Intel Celeron M, [P]SDC, uBlox GPS, GPRS, WLAN, Silabs FM, RDS, TMC,
Dual-audio, Onecable TFT, Microsize: 45 x 108 x 168mm (1.8 x 4.3 x 6.6")
hrm.. not sure.... i'm gonna definately get it working on my new m10k cuz my usb gps takes way too long to get sync and i have too many serial devices i wanna use
Car: 2000 Toyota Celica GT-S
Mods: Yep
Carputer: VIA M9000 | Opus 150 | 512MB PC2100 | 60GB Notebook HD | Slim/Slot DVD/CDRW | Audigy2NX | Xenarc 700TSV | (2) DSCustoms DS700HRS (in trunk) | SMC USB 802.11b | CoPilot | DLink FM tuner | Cliffnet
Bookmarks