Oh! NO! Got my MAX and it doesn't do busmastering! Argh! Haig, BBCrew! Help!

[M Ragsdale]

Scytale,

You can also try moving your RAM to the DIMM slot closest to your CPU. I know timing problems can cause weird problems, I have done my share of programming, too, and have toyed around with drivers, too.

Matt

[merchant2]

ok i have a bh6 and g400 dual head 2xagp is on and so is bus master no problems, im useing 2 sticks on nec pc100 sdram one 128meg and one 64meg stick. hey anyone know if this memory can take 112 clock ? i can't get this board to run above 103 (464) you think it may just be the cpu holding me back?

------------------
i don't know what im going to bitch about now that the avp patch is out.
p2 350 at 450, 196 meg pc100,10gig hard drive,5xdvd cl drive, xitel p. storm sound, 32meg g400 dualhead, acs 400 altec lansing speakers+yamaha rear, ch throttle, ch force fx, ch pedeals, hp laserjet 4, epson 400 color, ctx vl950 main mag dx17t secondary monitors
other systems k6-2 350 and k6 200.

[Scytale]

Well, I have flashed the MAX, did most of the BIOS tricks, swapped/removed DIMMs, but no success yet.

I don't have another (reliable) power supply available for testing so that will have to wait until I can get my hands on a good one, or when I feel like breaking down my firewall.

To merchant2: It could be either. You may want to try upping the core voltage a notch (don't go higher than 2.3, 2.4 max).

[M Ragsdale]

It is easy to see if your PS is providing the correct voltage when using this board. Look under chipset features in your BIOS. All the values should be very close to their spec. Also, if this does not work, yank out everything from your system except cpu, ram, vid card, and hd; And remove all of the devices from device manager in safe mode, including any double occurances of any devices you see in there. Reboot, make sure you have PD5.13 installed, and see if this works.

Rags

[Gurm]

Scytale:

My G400 standard worked fine on my BH6, and now on my BX6 v2. I'd try:

- Making sure the mobo BIOS is up to date
- Making sure your SCSI BIOS is up to date
- Checking for a SCSI conflict (I had one, with my Diamond Fireport 40!) by removing the SCSI card or trying another one

Basically, check all your hardware. It could be any of those things.

- Gurm

------------------
Sig? SIG? We don't NEED no STINKIN' SIG!

[Haig]

Hi Scytale,

What rev of the motherboard do you have?

Haig

[Manoj Mahtani]

Did you solve your problem Scytale?

[Scytale]

Hi guys. I tried another power supply and it worked fine for at least fifteen minutes using AGP2X+BM. Darn, a fluke.
Then again, surfing the fluke, I did the Tec

[Scytale101]

So we lost some stuff.

Haig, I attempted to reply to your message. GA ate it, and then some.

My BH6 revision number is V1.01 and BIOS is at LN. You mentioned that you didn't use the 66 leads when testing. Since the BH6 doesn't support UltraDMA/66, you got me puzzled there. I tested with both EIDE ports disabled. It doesn't seem to influence things in any way.

Running my P2 at it's default 5x66 didn't solve the problem either. It seemed to slow things down though

I noticed that the MAX has a PCI latency of 64 clocks, which is common. Now if I remember well, Sandra reported the G200 to take quite a bit more, like 128 clocks. (Maybe someone running a G200 could confirm this.)
I think upping the latency setting may be an interesting experiment. I'll see if I can find a recent version of TweakBIOS or something like that to try it.

[Scytale101]

Bah, I set the latency to 128 and it worked great for almost an hour

I did find that my SCSI is taking a hefty 144 clocks. Not nice at all.

[Matrox]

Hi Scytale,

I tried to edit my post right after I submitted but couldn't.

In any case, I wanted to remove the quotes about the 66 headers. What happens if you put your latency to 40?

Haig

[Scytale101]

Hi Haig, the forum seems to be dying again so I hope this will get through.

I tried 40 clocks and I tried other latency timings for different devices and components, but at a certain point the system would crash or stall just the same. Latency setting didn't seem to be much of a factor.
However, I did find a situation where the crash occurred using AGP1X+BM, but I was unable to replicate it and it took a few hours of gaming and benchmarking to encounter it.

I've been wandering around and I found a number of G400 users on the net describing the same crash symptoms (lock up and horizontal lining). I'm sure they'll find you. As my crashes are fairly easy to replicate (that is, when using AGP2X+BM), if you'd like me to test anything I'd be happy to.
I'm quite comfortable using AGP1X (1X, 2X, 4X, it's really not much of an issue, yet), but then again I don't like unfinished puzzles.

Thanks.

[Matrox]

Hi Scytale,

I'll get that BH6 system and try it again.

I'll try it first by reseting the cmos and see what happens.

Also, does your memory support ECC (9 chips)?
If not, disable it in your cmos and see what happens.

If possible, can you post a picture of your motherboard?

I'm hoping that this won't turn into another P2B problem.

Haig

[Scytale101]

Hi again Haig. I'm not using ECC, and it's not configured as such. I'm on LGS 7J (CAS3 PC100), 2x64MB. A lucky buy, because these two DIMMs can do up to 133MHz (CAS3).

I'll try to get you the picture. Thanks for looking into this again. And don't worry, this will never turn into a P2B problem.

[JSD]

Hi All,

I've been trawling the web for days trying to find a solution to exactly the same problem only for a G200. Obviously this problem has been already solved, can somebody point me in the right direction!?

System is a K6-2 300 (3x100)
128Mb PC100
TMC T15VG+
Millenium G200SD (Bios 2.6), driver ver 5.13
Adaptec 2940
SB Live!

No apparent conflicts and everything works well with BM under NT4 SP5. The lockup problem only appears under Win98 at anything over 640x480.

Any help much appreciated!

James