Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
> > basically, even on the new 8601, you can autodetect all you want but some > settings seem to not work. Very frustrating. I'll have to look and see > what hooks are in there, I no longer remember. Since I'm in that code currently copying and looking for my 440bx port. I noticed that the IO_BASE for the smbus in x_early_smbus_init.c is set to 5000. This will suffer the same problems that my 440bx V1 had where this io base will conflict with a device in the PCI IO allocations. I would suggest you move that to an address < 1000. -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
On Fri, 21 Jan 2005, Al Hooton wrote: > Ron: What do you believe is involved in updating raminit.c for the > vt8601 northbridge in order to auto-detect CL of 2 or 3? What about > updating it to auto-detect PC100/PC133? I'm not familiar with the > register interfaces in the vt8601, I've never seen the specs. What were > the chipset bugs you had to work around with the #defines for these two > settings back when the code was first put together? basically, even on the new 8601, you can autodetect all you want but some settings seem to not work. Very frustrating. I'll have to look and see what hooks are in there, I no longer remember. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
On Fri, 2005-01-21 at 10:11 -0800, Al Hooton wrote: > (yet?). At this point, I'm curious as to whether this lspci output > matches the EPIA 800 boards you have running LB in-house? Hold off on that request. I've gotten through LB to my payload. Mark's pointer to the defines at the top of raminit.c were the clue. Turns out I have CAS latency 2 sdram in this particular box, but I hadn't bothered to notice that. Ron: What do you believe is involved in updating raminit.c for the vt8601 northbridge in order to auto-detect CL of 2 or 3? What about updating it to auto-detect PC100/PC133? I'm not familiar with the register interfaces in the vt8601, I've never seen the specs. What were the chipset bugs you had to work around with the #defines for these two settings back when the code was first put together? Thanks to everyone that lent a hand! Now, I'm off to figure out why filo can't see my ide drives... 8^( -Al -- Al Hooton al-at-hootons-dot-org Maintainer of the linux-based open-source project Parapin. http://www.sf.net/projects/parapin/ ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
On Fri, 2005-01-21 at 10:03 -0700, Ronald G. Minnich wrote: > well, send me an lspci so i can be double sure I have these boards, and we > will take a look next week. I'm sorry to see you're having trouble. Thanks, Ron. I know you guys are busy, I'm not asking for a lot of help (yet?). At this point, I'm curious as to whether this lspci output matches the EPIA 800 boards you have running LB in-house? Who knows, maybe VIA has done a rev 2 (3, 4...?) of these boards and we'll have to figure out what they did. On the other hand, if the board matches yours, then there is just something going on that I still don't grok (much more likely... 8^)=). I'm going to pursue the path suggested by Mark Wilkinson as well (PC100 vs PC133 issue), I'll post back to the list if I find anything that way. --- [EMAIL PROTECTED] al]$ lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10) 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. VT82x UHCI USB 1.1 Controller (rev 1e) 00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1e) 00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51) 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) --- -Al -- Al Hooton al-at-hootons-dot-org Maintainer of the linux-based open-source project Parapin. http://www.sf.net/projects/parapin/ ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
On Fri, 21 Jan 2005 [EMAIL PROTECTED] wrote: > Depending on the values from the factory bios, you may need to alter the > definitions of DIMM_PC133 and DIMM_CL2 at the top of raminit.c to get > you going. or fix that code so it does the right thing ... that code is derived from my really old code of 5 years ago, and at the time I was working my way around bugs in the chipset. The chipsets seem largely fixed now, so it's time to do the SPD dance correctly. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
well, send me an lspci so i can be double sure I have these boards, and we will take a look next week. I'm sorry to see you're having trouble. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
Hi Al,
Quoting Al Hooton <[EMAIL PROTECTED]>:
On Thu, 2005-01-20 at 09:45 -0700, Ronald G. Minnich wrote:
I'm quite certain it is memory, this is always the scenario with this type
of output. I may still be wrong, but I doubt it. Certain problems occur
over and over again, and this looks to be one of them. Can you be sure
that your northbridge setup is duplicating fuctory bios?
Short form: is *anybody* currently taking a CVS download, and
successfully building/running for an EPIA 800 target? If so, please let
me know -- I'm beating my head against some kind of wierdness that I
have not yet grokked, and I'm wondering if something has broken since
the last know time this worked.
The short form answer is yes and no. I have a mostly current EPIA cvs
download,
that despite my best efforts at code tidying, continues to build and run every
now and again.
From reading the thread here, it looks like you are getting to the
bottom of the
code in northbridge/via/vt8601/raminit.c
i'd suggest trying this
just before the
print_err("vt8601 done.");
line, add
dumpnorth(north);
and compare the register settings against the lspci -xxx -s 0:0.0
You may need to tweek your logging level to get output from dumpnorth.
The important registers are 0x64->0x66, 0x68, 0x69
I had similer troubles (hanging at vt8601 done) until i did this. Turned out I
had PC133 memory and the config was setting up for PC100
Depending on the values from the factory bios, you may need to alter the
definitions of DIMM_PC133 and DIMM_CL2 at the top of raminit.c to get you
going.
Mark.
This message was sent using ISPMailNow.com
___
Linuxbios mailing list
Linuxbios@clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
On Thu, 2005-01-20 at 09:45 -0700, Ronald G. Minnich wrote: > I'm quite certain it is memory, this is always the scenario with this type > of output. I may still be wrong, but I doubt it. Certain problems occur > over and over again, and this looks to be one of them. Can you be sure > that your northbridge setup is duplicating fuctory bios? Short form: is *anybody* currently taking a CVS download, and successfully building/running for an EPIA 800 target? If so, please let me know -- I'm beating my head against some kind of wierdness that I have not yet grokked, and I'm wondering if something has broken since the last know time this worked. Long form: I edited auto.c to launch a mem test as suggested, but it didn't provide any further info -- everything passed, the maps/ranges look good, etc. I've got the cmos_util tools, and am certain my cmos is in good shape. I'm getting started in the normal image now, and have logging up at 9. After vt8601 init, the jump to LB just hangs. At one point I had things so warped I flushed it and started over with a fresh download from CVS, making no changes other than to use a payload of /etc/hosts, just to see if I could get through LB. No joy -- it still hangs after vt8601 init. I know it's possible to get an LB image that runs on this board, because I've downloaded the one from cwlinux, and it works fine (epia.rom of 21-Dec-2002). It just doesn't do what I want, and I'd like to know that I can build/tweak mine when necessary. Besides, I'm starting to think that something has broken in CVS since that image was built for the epia target, and it would be good to figure out what's broken (if something is). Anybody who is successfully building/running for the EPIA 800 target, please let me know. Thanks, Al ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
