xboxscene.org forums

Pages: 1 ... 7 8 [9] 10 11 ... 13

Author Topic: Pbl Should Be Fixed  (Read 570 times)

Raebis

  • Archived User
  • Newbie
  • *
  • Posts: 20
Pbl Should Be Fixed
« Reply #120 on: June 30, 2004, 12:21:00 PM »
QUOTE (•°ºo ßlåckMårk oº°• @ Jun 30 2004, 08:37 PM)
.
.
the dash boot is E:/newdash/newdash.xbe
My dude is… I need to mod my dash path or .xbe name for work properly with your PBL version?
.
.

The bios that your PBL loads (xboxrom.bin) determines what dashboard to launch. If you use the same bios file as you were previosuly using, then you shouldn't have a problem.


QUOTE
pbl 1.4.1 WORKS with the HD cables (at least for me)

Good to know. What brand is your cable? Is it the MS High Definition AV Pack? And you are sure that your xbox has the Focus encoder and not the older Conexant?
Logged

rizza

  • Recovered User
  • Newbie
  • *
  • Posts: 8
Pbl Should Be Fixed
« Reply #121 on: June 30, 2004, 12:51:00 PM »
QUOTE (Tomilius @ Jun 30 2004, 09:27 PM)
Oh, I didn't mention the benefit of this golden egg... It works around screen corruption. biggrin.gif

It certainly does.  Excellent find!

On the PBL XDK porting, as I mentioned earlier, I have it working but only when launched from a debug BIOS.  It hangs when calling the 2bl with retail bioses.  After some searching, I found I am not alone in having this problem.  "Undead" from Team Assembly reported the same problem a while ago.  See this.  Since Team Assembly never released anything and undead never posted a fix, I have to assume he never found one.  There has to be a way, but it is tricky apparently.
Logged

Tomilius

  • Archived User
  • Full Member
  • *
  • Posts: 104
Pbl Should Be Fixed
« Reply #122 on: June 30, 2004, 01:02:00 PM »
Thanks for your efforts, rizza. I'm sure there is a way, and I'm sure you'll find it.
Logged

ldots

  • Archived User
  • Hero Member
  • *
  • Posts: 822
Pbl Should Be Fixed
« Reply #123 on: June 30, 2004, 01:14:00 PM »
QUOTE (Tomilius @ Jun 30 2004, 09:27 PM)
Oh, I didn't mention the benefit of this golden egg... It works around screen corruption. biggrin.gif

That's really strange???

I also stumbled across this command in the BootVgaInitialization code of PBL 1.3 yesterday also, and put in a return in this routine right after this was called. I still get some screen corruption. Different kind - greenish corruption. So I didn't make any further notice of this. Do you just get a black screen after issuing this?
Logged

Chicken Scratch Boy

  • Archived User
  • Hero Member
  • *
  • Posts: 1054
Pbl Should Be Fixed
« Reply #124 on: June 30, 2004, 01:31:00 PM »
@rizza i remember that PBL sets a some debug or dev flags in the bios or eeprom before it goes to work, i mentioned this earier but i didnt see a reply....

@ldots can the greenish corruption be the background of the dash? do you see the honeycomb? or the trademark curving of the texture?
Logged

rizza

  • Recovered User
  • Newbie
  • *
  • Posts: 8
Pbl Should Be Fixed
« Reply #125 on: June 30, 2004, 02:05:00 PM »
QUOTE (Chicken Scratch Boy @ Jun 30 2004, 10:31 PM)
@rizza i remember that PBL sets a some debug or dev flags in the bios or eeprom before it goes to work, i mentioned this earier but i didnt see a reply....

Well, before porting to XDK, I stripped PBL to the bare essentials, recompiled it, and verified it still works from a retail kernel.  I then made the few modifications needed to get the stripped down version to compile under the XDK.  It works under a debug but not a retail kernel.  I.e., anything special PBL sets that makes it work I have already ported to XDK.  It just doesn't work outside of the debug kernel.  It fails when it calls the 2bl, though it appears to have loaded the 2bl and is calling the right address for it etc.  It just hangs up there.  I'm at a loss as to why at this point.
Logged

Chicken Scratch Boy

  • Archived User
  • Hero Member
  • *
  • Posts: 1054
Pbl Should Be Fixed
« Reply #126 on: June 30, 2004, 02:13:00 PM »
well the thing is, these flags would not need to be set from a dev enviroment, so it whould work from one without this portion of the code working or existing

so i think you either cut this part out by accident or it isnt fuctioning properly
Logged

ldots

  • Archived User
  • Hero Member
  • *
  • Posts: 822
Pbl Should Be Fixed
« Reply #127 on: June 30, 2004, 02:14:00 PM »
QUOTE (Tomilius @ Jun 30 2004, 11:05 PM)
Nope. The IoOutputByte thing wasn't what was making my RF adapter go off... it was the fb_clear(). But that doesn't mean there isn't a way to kill the video still!

I see, thought I had gone crazy there since I still saw the corruption  laugh.gif
The fb_clear() works against the corruption but requires Vga to be initialized. That brings us back to the s-video problem  sad.gif
Logged

jaNN0

  • Archived User
  • Newbie
  • *
  • Posts: 25
Pbl Should Be Fixed
« Reply #128 on: June 30, 2004, 02:23:00 PM »
hmm. sorry if this is off topic, but ive read almost all the faqs in here, but i cant find a tut on how to downgrade my dashto 4920 to run the font exploits using the hotswap trick (if theres such a thing), cuz theres no way i can ftp to the xbox, i have no memory card soo ya... justholla t me aight.... peace up-atown
Logged

Tomilius

  • Archived User
  • Full Member
  • *
  • Posts: 104
Pbl Should Be Fixed
« Reply #129 on: June 30, 2004, 04:32:00 PM »
What's going on here!? I'm obviously not a very reliable source anymore thanks to Linux being so weird. I tried everything again. fb_clear() IS different than IoOutputByte(0x80d3, 5). fb_clear() does NOT make my RF adapter light go off. IoOutputByte(0x80d3, 5) does. IoOutputByte(0x80d3, 5) disables video output until it is re-enabled with IoOutputByte(0x80d3, 4). For some reason, it still seems that this does not stop screen corruption! So weird! I wish I had a cable so I could easily test for myself all of this... but for me with my SCART, output stays off until the BIOS loads the XBE. ldots, try again... maybe put it up near the top of mainthread and put a wait_ms(2000); right after it...
Logged

Tomilius

  • Archived User
  • Full Member
  • *
  • Posts: 104
Pbl Should Be Fixed
« Reply #130 on: June 30, 2004, 05:24:00 PM »
QUOTE
IoOutputByte(0x80d3, 5);  // definitively kill video out using an ACPI control pin
Logged

rizza

  • Recovered User
  • Newbie
  • *
  • Posts: 8
Pbl Should Be Fixed
« Reply #131 on: June 30, 2004, 06:14:00 PM »
QUOTE (Chicken Scratch Boy @ Jun 30 2004, 11:13 PM)
well the thing is, these flags would not need to be set from a dev enviroment, so it whould work from one without this portion of the code working or existing

so i think you either cut this part out by accident or it isnt fuctioning properly

AFAICT, there are no such flags set in the PBL code.    The closest thing I can think of is the "I2CTransmitByteGetReturn" stuff, but AFAICT from stepping through the code that is working fine.  I really didn't cut/change much of anything out of the highly-stripped PBL.  The extra code automatically added by the XDK must be where the problem lies, and there's not an easy solution to that.
Logged

Tomilius

  • Archived User
  • Full Member
  • *
  • Posts: 104
Pbl Should Be Fixed
« Reply #132 on: June 30, 2004, 08:02:00 PM »
QUOTE (ldots @ Jun 30 2004, 10:14 PM)
That's really strange???

I also stumbled across this command in the BootVgaInitialization code of PBL 1.3 yesterday also, and put in a return in this routine right after this was called. I still get some screen corruption. Different kind - greenish corruption. So I didn't make any further notice of this. Do you just get a black screen after issuing this?

Try the new beta. It does some testing so you can see the effects IoOutputByte has on your Xbox... Greenish corruption. Yeah, that's weird. Again, make sure the command is right before the ASM code that sends the BIOS control. And try the beta biggrin.gif
Logged

anjilslaire

  • Archived User
  • Sr. Member
  • *
  • Posts: 296
Pbl Should Be Fixed
« Reply #133 on: June 30, 2004, 08:08:00 PM »
smile.gif
Logged

Tomilius

  • Archived User
  • Full Member
  • *
  • Posts: 104
Pbl Should Be Fixed
« Reply #134 on: June 30, 2004, 08:15:00 PM »
QUOTE (anjilslaire @ Jul 1 2004, 05:08 AM)
No go. I don't gt corruption, but all output goes dead. I get "About to blank the screen, please stand by... fb_clear;" then a blue video screen ( like nothing hooked to my tv.)

Then, I get "Done. Sticking with IoOutputByte... AND fb_clear()" Then another blue "dead video" screen, and nothing.

Tried with and without
AutoDetectVideo false
NoVideo false

Note: this is not being tested as an app, but a "true" hard boot. Thanks to ldots' 1.5.1, I can boot tray open to easily reset my pbl files smile.gif

The output going dead is the point... lol.. that's actually the "solution" to screen corruption. It SHOULD go back when your dashboard is loaded.

Oh, also, did it crash? Did you try pressing the eject button and seeing if it reset?

And don't run this from a QuickReboot. Some people don't have problems with it, but I think it has something to do with using Dual-Habibi or the like. But oh how wrong I could be! In fact, I'm almost certain I'm wrong about that. I'm not right about anything that I'm not absolutely sure I'm right about. Hehe.
Logged
Pages: 1 ... 7 8 [9] 10 11 ... 13
« previous next »