I recently decided to upgrade my old Dell Dimension 4100, and after
changing my RAM, HDD, video card, etc. I decided to upgrade the
processor, it has the best Coppermine PIII available, but this is only
1.1 GHz, and 256k L2, so I figured I would get an upgrade adapter, the
only one I could find however was a Lin-Lin socket 370 fc-pga to fc-
pga 2 adapter, which I figured would be fine to upgrade to a Tualatin
PIII SL6BY. However, Upon using the adapter as originally configured
(original jumper settings), I turned the comp on to find that the
system wouldn't boot, and i received a diagnostic light code in which
only the "b" light was illuminated with a green LED, which according
to the Dell documentation (http://support.dell.com/support/edocs/
systems/dzuul/codemess.htm#diagnostic_codes), means that a "PCI bus
failure has occurred". However this seems unlikely, as I had not
altered the PCI cards configuration in anyway, and even after removing
all of them from the system, I received the same error. After
returning to the previous CPU, My system booted properly, and since I
have seen reports of people being successfully able to get this to
work with the same adapter, CPU, and Dimension, I am confused as to
what I am doing wrong. I would be most appreciative of advice given
from someone who has used this adapter with the same mo-bo i am using
(basically an intel i815), or even better, someone who has used it on
a dimension 4100, or even with the same processor. Any and all help is
appreciated, so please post away!
>I recently decided to upgrade my old Dell Dimension 4100, and after
>changing my RAM, HDD, video card, etc. I decided to upgrade the
>processor, it has the best Coppermine PIII available, but this is only
>1.1 GHz, and 256k L2, so I figured I would get an upgrade adapter, the
>only one I could find however was a Lin-Lin socket 370 fc-pga to fc-
>pga 2 adapter, which I figured would be fine to upgrade to a Tualatin
>PIII SL6BY.
The tualatins only went up to 1.4GHz, didn't they? I
wouldn't hope for a noticable performance increase with this
upgrade, but since you seem to have the adapter and
processor anyway...
>However, Upon using the adapter as originally configured
>(original jumper settings),
It's been a few years, sorry but I can't recall the
originally configured jumper settings.
does it look right? I can't know if there is only one
version of the lin-lin adapter. I might even have one
around here somewhere but as I wrote above it's been a few
years so I've no idea where it might be.
Surprisingly I remember where the box is from one I had so I
have the original jumper sheet. The box doesn't say
"Lin-Lin" though, it's branded as "August" and the end reads
"370 CPU Celeron III Converter Slocket", though normally a
slocket adapter meant slot to socket adapter so their
engrish isn't so hot. The jumper settings for mine look
identical to the above linked picture except on two sides of
a little piece of white cardboard, though from what I
vaguely recall I had used the adapter to overclock a
Tualatin Celeron 1.1 to a little under 1.5GHz so I can't be
certain if the different jumper setting for Intel chipsets
works in general let alone on your specific i815 board but I
would think they should since you wrote that others had done
this upgrade presumably with the same adapter.
>I turned the comp on to find that the
>system wouldn't boot, and i received a diagnostic light code in which
>only the "b" light was illuminated with a green LED, which according
>to the Dell documentation (http://support.dell.com/support/edocs/
>systems/dzuul/codemess.htm#diagnostic_codes), means that a "PCI bus
>failure has occurred". However this seems unlikely, as I had not
>altered the PCI cards configuration in anyway, and even after removing
>all of them from the system, I received the same error.
Forget about this for the time being, you definitely need to
have the jumpers on the adapter right to get a Tualatin to
work in a non-officially-supportive motherboard.
I think I vaguely recall that some of the other jumper
settings not illustrated may be for FSB and voltage ID
purposes but it's been awhile, I could be wrong about that.
> After
>returning to the previous CPU, My system booted properly, and since I
>have seen reports of people being successfully able to get this to
>work with the same adapter, CPU, and Dimension, I am confused as to
>what I am doing wrong. I would be most appreciative of advice given
>from someone who has used this adapter with the same mo-bo i am using
>(basically an intel i815), or even better, someone who has used it on
>a dimension 4100, or even with the same processor. Any and all help is
>appreciated, so please post away!
If it doesn't work with the jumper settings shown above,
does it do anything differently like a beep code?
Re: Lin-Lin Upgrade Adapter on Dell Dimension 4100
On Thu, 14 Aug 2008 23:22:31 -0400, kony <spam@spam.com>
wrote:
<snip>
>...though from what I
>vaguely recall I had used the adapter to overclock a
>Tualatin Celeron 1.1 to a little under 1.5GHz so I can't be
>certain if the different jumper setting for Intel chipsets
>works in general let alone on your specific i815 board but I
>would think they should since you wrote that others had done
>this upgrade presumably with the same adapter.
What I meant to write was that I'd used the adapter on
boards with different chipsets like Via 694x, can't recall
ever trying one on an i815 based board.
You might also want to write down any non-default bios
settings and clear CMOS while AC power is off to the system.
Pull the battery for a few minutes if there's no jumper.
Thanks for the help, I changed my adapter jumper settings to match
those that were shown in the link that you gave me (not the pic, but
the thread), and I set it for 1.45V, and 133 FSB, I also pulled the
CMOS battery for 5 minutes while unplugged, but I still get the same
error light, and with no beep code, I appreciate your help though, and
I will go over it again when I have more time. Thanks!
>On Aug 14, 11:32*pm, kony <s...@spam.com> wrote:
>> On Thu, 14 Aug 2008 23:22:31 -0400, kony <s...@spam.com>
>> wrote:
>>
>>
>>
>> >See this,
>>
>> >http://img88.imageshack.us/img88/305...uctions2kp.jpg
>>
>> I forgot to link the thread this pic was posted in, it has
>> other related info.
>>
>> http://discussions.hardwarecentral.c...d.php?t=172281
>
>Kony,
>
>Thanks for the help, I changed my adapter jumper settings to match
>those that were shown in the link that you gave me (not the pic, but
>the thread), and I set it for 1.45V, and 133 FSB, I also pulled the
>CMOS battery for 5 minutes while unplugged, but I still get the same
>error light, and with no beep code, I appreciate your help though, and
>I will go over it again when I have more time. Thanks!
I don't know what the lowest voltage is your board supports,
if all else fails I'd jumper to 1.5V as that was one lower
limit some VRM controllers had.
I'd also try jumpering as if it were a Via chipset. Next I
might try leaving the unique Intel jumper on the left side
on and adding either of the unique Via jumpers, then the
other unique via jumper, then all 3. I don't know if this
might cause any harm, nor how important this system is to
you since it works ok with the 1.1GHz CPU.
I'd also look into getting, updating to the last bios
version if it's not running that, before making jumper
settings changes again.
That's about all I can think of. You might Google search
for owners of 815 boards running Tualatins and see if you
can find a way to directly ask one of them, email or a PM in
a website forum or something, though your usenet post isn't
old yet, maybe someone will come along with another idea.
I assume you have a fair level of confidence that the
Tualatin processor is good? I was also assuming your old P3
had 133MHz FSB, that it wouldn't be that you might have
PC100 memory in which isn't working with a Tualatin using
133MHz FSB/Memory Bus? If your board has over/underclocking
jumpers it might not hurt to try clocking it at 66 or 100MHz
temporarily to see if it'll then post with the Tualatin in.
Re: Lin-Lin Upgrade Adapter on Dell Dimension 4100
ravinvar@gmail.com wrote:
> I recently decided to upgrade my old Dell Dimension 4100, and after
> changing my RAM, HDD, video card, etc. I decided to upgrade the
> processor, it has the best Coppermine PIII available, but this is only
> 1.1 GHz, and 256k L2, so I figured I would get an upgrade adapter, the
> only one I could find however was a Lin-Lin socket 370 fc-pga to fc-
> pga 2 adapter, which I figured would be fine to upgrade to a Tualatin
> PIII SL6BY. However, Upon using the adapter as originally configured
> (original jumper settings), I turned the comp on to find that the
> system wouldn't boot, and i received a diagnostic light code in which
> only the "b" light was illuminated with a green LED, which according
> to the Dell documentation (http://support.dell.com/support/edocs/
> systems/dzuul/codemess.htm#diagnostic_codes), means that a "PCI bus
> failure has occurred". However this seems unlikely, as I had not
> altered the PCI cards configuration in anyway, and even after removing
> all of them from the system, I received the same error. After
> returning to the previous CPU, My system booted properly, and since I
> have seen reports of people being successfully able to get this to
> work with the same adapter, CPU, and Dimension, I am confused as to
> what I am doing wrong. I would be most appreciative of advice given
> from someone who has used this adapter with the same mo-bo i am using
> (basically an intel i815), or even better, someone who has used it on
> a dimension 4100, or even with the same processor. Any and all help is
> appreciated, so please post away!
The Lin-Lin has jumpers, some of which control Vcore VID value,
and the others control the CPU input clock (BSEL two bit code = 66,100,133MHz).
So you have to set those appropriately. The documentation on
the back of the box is misleading, and there are articles in
web forums, with the information that people have gathered
on it.
(Examples of two generations of voltage regulators. Use the first
two docs, as a reference on Vcore values and VID bits.)
There are two bits of info for the Lin-Lin jumpers. You can find the
"standard table" floating around, but it doesn't tell the whole story.
Basically, what this table shows, is which signals to ground, to
set the four bit VID code and the two bit BSEL code, without referring
to what the processor is sending. So all of these codes are "override
codes", choosing to ground a signal (by using a jumper) or not ground
a signal (by not using a jumper at all with the signal being controlled).
Override codes. Broken into two sets. First set controls Vcore.
Second set controls BSEL. The two sets are independent of one
another. Take the 2.05V as an example. To override the processor voltage
request, and force 0000 binary code, requires four jumpers to ground
four signals. In the case of 1.35V, the code is 1110, and only one
jumper is needed to assert the single logic 0 needed. The other three
VID signals are allowed to float to logic 1.
BSEL is a two bit code, sent from the processor to the clock generator chip.
66MHz must be binary 00, requiring two grounding jumpers. 133MHz must be binary 11,
and for that, no jumpers are installed, resulting in the two signals floating to
logic 1.
In the post here, someone traced the pins not used. The remaining pins
are "passthru" pins, that would pass the value the processor is sending.
The processor is coded for the Vcore VID it needs to run, and also
controls the BSEL pins, to set the CPU input clock.
http://www.bp6.com/board/viewtopic.p...r=asc&start=75
*******
"bardos, when you jumper a1-2, a4-5 and a7-8 you are allowing the VIDx signals to
pass from the CPU for autodetect....reason you saw a 1.30 when you boot is that
you didn't pass VID3 for autodetect, you floated it.
I probed my lin lin today... A1, A4, A7, B1, B4, B7 allow the passthru of the
adjacent signals (when jumpered) to the CPU to allow auto detection of voltages
and fsb. The lin lin box instructions then interpret :
For FCPGA1 (cel2 or p3 cu), on PPGA board, use auto detect.
For FCPGA2 on FCPGA boards , examples are for setting 1.5v (intel board)and 1.45v
(VIA/SIS) respectively with fsb=100
A3, A6, A9, B3, B6, B9 tie adjacent signal to Vss
i.e. a logical 0 for the intel VIDx table in the intel datasheets
B2 = VID3
A5 = VID2
A2 = VID1
A8 = VID0
B5= BSEL0
B8 = BSEL1
*******
So, for the six named signals (four VID logic signals, selecting 16
different voltage values, and two BSEL signals selecting 66,100,133),
each three pin section looks like this. The following circuit is repeated
six times, and uses a total of 18 jumper pegs on the Lin-Lin.
+
|
Pullup_resistor (makes logic 1,
| if no jumper is used)
Passthru_from_processor ----------X |
X----+----> To motherboard (VID to Vcore,
Logic_0_grounding_the_signal -----X BSEL to clockgen)
options - no jumper (force logic 1)
- upper X to center X (passthru)
- lower X to center X (force logic 0)
The voltage regulator on the motherboard, must be designed for
the task. Voltage regulators of that era came in two types.
Ones that delivered voltages as low as 1.8V (not suited to
running a Tualatin), and ones that offered more of the
Vcore VID table values all the way to 1.5V (suitable for
Tualatin). I expect your Vcore regulator is OK for this.
(The two Intersil documents above, are examples of the two possible
types of Vcore regulators used back then.)
(On my motherboard, I changed to a pin compatible regulator
chip, so I could get 1.5V, but it was a pretty dangerous
soldering mod. I accidentally removed an unused copper pad
while doing the mod, but the board still worked with the
Tualatin when I was finished.)
So one symptom that an upgrader can see, is a "black screen
and no beeps". When that happens, it means the Vcore regulator
is the 1.8V type, and when the VID bit pattern for a voltage
less than 1.8V is fed to it, the output is set to zero volts
for safety. In that case, there is no damage to the processor.
Another issue, is BIOS recognition of the processor. In that
era, there were issues with the multiplier value locked inside
the processor, and certain higher multiplier values could cause
a problem when the BIOS parses the CPU type during POST.
One suggested test for a BIOS/multiplier problem, is to force
the CPU input clock to 66MHz. Apparently, that will allow
some of the BIOS multiplier problems to be bypassed, so you can at
least prove that the voltage issue is OK. (You're testing at 66MHz,
to prove that the processor works.) So, on your Lin-Lin,
you're going to have to dig up the proper documentation for the
Ax-Bx jumpers, so that you can set the thing to 66MHz.
On my 440BX motherboard, I installed the latest BIOS available, and
that had a fix for the multiplier problem. But the BIOS did not
have the microcode patch for the Tualatin (not really a big deal),
and I fixed that with the CTMC package (heise.de). It means taking
a 2KB microcode file from another BIOS, and using a built-in feature
of the BIOS, to store the new microcode in a "volatile" location
in the BIOS EEPROM chip. As long as you didn't screw around with
changing the processor to different models, the microcode would
stay put. The microcode patch would remove any warning message
seen during the BIOS POST sequence, about no microcode being
present for the processor. WinXP has a microcode loader, so
at least for that OS, a microcode is loaded once WinXP is booted.
Other than that, I couldn't find an article that addressed your
exact configuration. On my computer, I used an Upgradeware Slot-T
adapter, as my computer is a slot 1 and needs a different adapter.
Re: Lin-Lin Upgrade Adapter on Dell Dimension 4100
On Fri, 15 Aug 2008 00:47:36 -0400, Paul <nospam@needed.com>
wrote:
>The voltage regulator on the motherboard, must be designed for
>the task. Voltage regulators of that era came in two types.
>Ones that delivered voltages as low as 1.8V (not suited to
>running a Tualatin), and ones that offered more of the
>Vcore VID table values all the way to 1.5V (suitable for
>Tualatin). I expect your Vcore regulator is OK for this.
>(The two Intersil documents above, are examples of the two possible
>types of Vcore regulators used back then.)
It would have to go lower than 1.8V since the board is
capable of Coppermines. Generally the 1.8V limit was only
seen on 440BX and older Intel chipset boards, unless some
third party (like PCChips) tried to be extremely frugal in
their design.
>On my 440BX motherboard, I installed the latest BIOS available, and
>that had a fix for the multiplier problem. But the BIOS did not
>have the microcode patch for the Tualatin (not really a big deal),
>and I fixed that with the CTMC package (heise.de). It means taking
>a 2KB microcode file from another BIOS, and using a built-in feature
>of the BIOS, to store the new microcode in a "volatile" location
>in the BIOS EEPROM chip. As long as you didn't screw around with
>changing the processor to different models, the microcode would
>stay put. The microcode patch would remove any warning message
>seen during the BIOS POST sequence, about no microcode being
>present for the processor. WinXP has a microcode loader, so
>at least for that OS, a microcode is loaded once WinXP is booted.
>
>(I haven't checked to see if it is still here.)
>ftp://ftp.heise.de/pub/ct/ctsi/ctmc10.zip
>
>Other than that, I couldn't find an article that addressed your
>exact configuration. On my computer, I used an Upgradeware Slot-T
>adapter, as my computer is a slot 1 and needs a different adapter.
>
>Hope that gives you a few ideas,
> Paul
Another thought is whether it is worth the bother, if the
Tualatin can be sold then there's a fair amount of
performance increase possible going with a newer set of
parts. Generally the PC(133?) memory could be reused
reasonably through an Athlon XP era board or today DDR2 is
dirt cheap, a fairly large performance increase could be had
if only there is the willingness to devote $120 to a board,
CPU and memory combo though at this date a bit more
searching might be needed to find something with an AGP slot
instead of integrated video, and yet today's integrated
video isn't so much of a compromise over what was available
in the P3 era.
Re: Lin-Lin Upgrade Adapter on Dell Dimension 4100
Thanks to both of you! I eventually messed around with the jumpers,
setting the voltage to 1.55V and the FSB to 133, while flashing my
bios to the intel version as instructed by the powerleap website.
Everything is working great now so thanks for the help!
>Thanks to both of you! I eventually messed around with the jumpers,
>setting the voltage to 1.55V and the FSB to 133, while flashing my
>bios to the intel version as instructed by the powerleap website.
>Everything is working great now so thanks for the help!
That's good to hear, and thanks for replying back with the
solution (some people don't).
Lin-Lin Upgrade Adapter on Dell Dimension 4100 
Linear Mode
