Topic: New Xbox V1.6b ? (Read 503 times)

shepd · « **Reply #60 on:** November 04, 2004, 01:26:00 PM »

Just tested... grounding BT on the Aladdin XT consumes 111 micro-amps of current. That's 0.000111 A. All is normal.

Chancer · « **Reply #61 on:** November 04, 2004, 02:16:00 PM »

Its not going to be easy to tell whats going off as everyone who has a problem with a 1.6 install is now going to post in here and blame it on a new board revision or anything else when some of the problems will be down to the actual install work carried out or inherrent problems with the design of certain chips. the chips in question will be well known as many people have had problems posted all over these forums.
I just did my 11th Crystal in 2 weeks (UK) and no problems to report DuoX 2 chips M8.16 bios.

nachomans · « **Reply #62 on:** November 04, 2004, 11:03:00 PM »

hippo · « **Reply #63 on:** November 05, 2004, 09:18:00 AM »

Lurrch · « **Reply #64 on:** November 05, 2004, 10:43:00 AM »

MIC · « **Reply #65 on:** November 05, 2004, 01:15:00 PM »

I decided to install a Duox2 but same problem..freeze and dash crash somes time.

The only things that work is: dvd (original or backup) WORKING 90% of the time!

Chancer · « **Reply #66 on:** November 05, 2004, 01:26:00 PM »

blackout_19 · « **Reply #67 on:** November 05, 2004, 01:55:00 PM »

Does this sound familiar.... from March 2003

New Release: XECUTER2 BIOS 4976.02
>> From the nfo:

Bug Fix Release.
Many people having issues with the Xbox freezing sporadically on bootup. This should fix
the problem - apologies for the bug.

Edit: I'm not saying it's xecuters fault this time, just that this was a very similar, bios caused situation.

shepd · « **Reply #68 on:** November 05, 2004, 09:54:00 PM »

I thought you were talking about BT. It is what you said. I don't care to blow up an XBOX, I won't be grounding out the lframe signal. That's just stupid.

If that's what you're talking about, I'm with ya.

RoboChicken · « **Reply #69 on:** November 05, 2004, 11:47:00 PM »

Info on the one I'm working on:

- Problem: No video from Cromwell
- Version: 1.6/7??
- Yellow PE
- Hynix RAM, 433A, HY5DU283222AQ-5, Korea
- Xcalibur X01203-003, A-B01, 0433FG5773.1, AA Taiwan
- Xyclops X01202-002, A-A02, 0435CN7576.R1, AA Taiwan
- MCPX X3 FG0544.1 0432D3, C Korea
- Toshiba Samsung DVD-ROM drive (I hear these don't read cd-r's)
- X2.6 pin header installed
- I haven't tried any other chips or tried a preflashed one yet

Man... this week sucks balls. First these new PStwos start blowing their lasers out and now this with the Xbox.

Someone take side by side shots of top and bottom of mobo - for both original 1.6 and fucker 1.6

.

Xconsole · « **Reply #70 on:** November 06, 2004, 12:05:00 AM »

Simplified as i read it: Your machine have Hynix RAM-chips. There are no correct timing-values for those chips in the M8_16-BIOS. Therefore machine will lock up randomly since data written to memory gets corupted.
M8_16 works with Samsung-RAM-chips.

Thus, there are no "1.6B" och "1.7", just ordinary 1.6:es with memory from a different (probably cheaper) manufacturer.

If this theory is correct, I am sure someone will be able to come out with a fixed BIOS in the very near future.

Xconsole · « **Reply #71 on:** November 06, 2004, 01:00:00 AM »

Well, it might ... but beware that the RAM-chips are the ones, two on each side of the board, with a very high pin-count.

It would be a total nightmare to even think about desoldering the old ones.
Soldering on a couple of new ones, like when you put chips in the empty places on version 1.0 - 1.5-boards can be done, but to remove it, no, not without special tools ...

or a lot of force.

You could of course just cut away the legs to get the chip off, and then desolder all the small disconnected legs and clean it up.

Finding new RAM would be a bit of a problem though, but not an impossiblility.

And also, it might give problems later on. If what I read is correct, there may be info in the EEPROM regarding the exact type of memory on the board. Change the chips, and they would not be treated right by a BIOS that respects those EEPROM-values.

So, in short: Don't even consider it. It would be a lot easier, not to mention a lot less of psychic suffering, just to go out and buy new boxes till you find one that works.

The other ones you either keep for the day a working BIOS is released, or you sell them on Ebay.

Xconsole · « **Reply #72 on:** November 06, 2004, 01:09:00 AM »

If you would read the front-page news, or any of the other places it have been written, it says something about a wastly expanded RAM-timing table in the retail kernel for the 1.6-boxes. All of them, not just the "new" 1.6:es.

It also says something about the EvoX M8 only having an older table in it ...

That would be a reason the retail kernel works in them all, and the M8 doesn't.

Then again, I don't know, I just read it, process it in my mind, and write a lot of wird stuff here when I should be doing better things

FallsInc · « **Reply #73 on:** November 06, 2004, 01:10:00 AM »

new info on x-s main page says that its the ram timing problems. its not evox's fault, its the new kernal has alot more shit crammed into it. they just need to fix up m8 to include the new info in the newer kernal. i'm too tired to go into detail or give a link... you all can find it

Xconsole · « **Reply #74 on:** November 06, 2004, 06:38:00 AM »

Yoshihiro have updated the M8-BIOS

Author Topic: New Xbox V1.6b ? (Read 503 times)