Jump to content


Photo

You Having Trouble With Xboxhdm V1.9's Options


  • Please log in to reply
28 replies to this topic

#1 Musashi

Musashi

    X-S X-perience

  • Members
  • PipPip
  • 359 posts
  • Location:the Under World
  • Interests:Halo, Halo 2, other videogames, and my girlfriend.
  • Xbox Version:v1.4
  • 360 version:v3.1 (opus)

Posted 09 January 2005 - 04:49 AM

Im writing this tutorial for all those of us who dont/didn't seem to find a way to run xboxhdm 1.9's options 1 and 2.

I will explain what to edit on some files to make xboxhdm boot in failsafe mode and allow you to use the distro.

First Id like to give thanks to Ldots for his great work and helpful tools (which I like to modify).

Now let's start with the tut:

-You first need to Decompress (using winzip or winrar) the xboxhdm_v1.9.zip archive to a folder (EX: C:\Documents and Settings\Owner\Desktop\XboxHDMaker\).

-Once the decompression process is complete, using the example above, go to:C:\Documents and Settings\Owner\Desktop\XboxHDMaker\xboxhdm\linux\isolinux\.

-Once you are in the folder, open the isolinux.cfg file with notepad or wordpad, and you should see the following:
CODE
default 1
prompt 1
timeout 300
display message.txt
label 1
 kernel /isolinux/fatxImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq vga=0x317
label 2
 kernel /isolinux/fatxImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq
label 3
 kernel /isolinux/lockImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq vga=0x317
label 4
 kernel /isolinux/memdisk
 append initrd=FREEBOOT.IMG



Now you must erase this and paste the following code:


CODE
default 1
prompt 1
timeout 300
display message.txt
label 1
 kernel /isolinux/fatxImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq vga=0x317
label 3
 kernel /isolinux/fatxImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq
label 4
 kernel /isolinux/lockImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq vga=0x317
label 5
 kernel /isolinux/memdisk
 append initrd=FREEBOOT.IMG
label 2
 kernel /isolinux/fatxImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=100000 rw root=/dev/ram pci=biosirq vga=normal atapicd


-You're now done with this file, save it and close the text editor. You must now open the following document within the same folder: message.txt

-You will now be presented with this:
CODE
 
  _  __ __         _  __    __  ______     __  ___      __            
 | |/ // /_  ____ | |/ /   / / / / __ \   /  |/  /___ _/ /_____  _____
 |   // __ \/ __ \|   /   / /_/ / / / /  / /|_/ / __ `/ //_/ _ \/ ___/
/   |/ /_/ / /_/ /   |   / __  / /_/ /  / /  / / /_/ / ,< /  __/ /    
/_/|_/_.___/\____/_/|_|  /_/ /_/_____/  /_/  /_/\__,_/_/|_|\___/_/    
                                         __
                        ____ _____  ____/ /
                       / __ `/ __ \/ __  /
                      / /_/ / / / / /_/ /  
                      \__,_/_/ /_/\__,_/  
                                                __              __
  ________  _________ _   _____  _______  __   / /_____  ____  / /
 / ___/ _ \/ ___/ __ \ | / / _ \/ ___/ / / /  / __/ __ \/ __ \/ /
/ /  /  __/ /__/ /_/ / |/ /  __/ /  / /_/ /  / /_/ /_/ / /_/ / /  
/_/   \___/\___/\____/|___/\___/_/   \__, /   \__/\____/\____/_/  
                                   /____/                        
                                           
      1) Boot VGA console with xbox-drive utilities (default)
      2) Boot text-console with xbox-drive utilities
      3) Boot linux with locking/unlocking utilities
      4) Boot to DOS with HD unlock tools
         (use with caution. Passwd log-files are not saved after reboot)


And replace it with this:

CODE

  _  __ __         _  __    __  ______     __  ___      __            
 | |/ // /_  ____ | |/ /   / / / / __ \   /  |/  /___ _/ /_____  _____
 |   // __ \/ __ \|   /   / /_/ / / / /  / /|_/ / __ `/ //_/ _ \/ ___/
/   |/ /_/ / /_/ /   |   / __  / /_/ /  / /  / / /_/ / ,< /  __/ /    
/_/|_/_.___/\____/_/|_|  /_/ /_/_____/  /_/  /_/\__,_/_/|_|\___/_/    
                                         __
                        ____ _____  ____/ /
                       / __ `/ __ \/ __  /
                      / /_/ / / / / /_/ /  
                      \__,_/_/ /_/\__,_/  
                                                __              __
  ________  _________ _   _____  _______  __   / /_____  ____  / /
 / ___/ _ \/ ___/ __ \ | / / _ \/ ___/ / / /  / __/ __ \/ __ \/ /
/ /  /  __/ /__/ /_/ / |/ /  __/ /  / /_/ /  / /_/ /_/ / /_/ / /
/_/   \___/\___/\____/|___/\___/_/   \__, /   \__/\____/\____/_/
                                   /____/                        
                                           
      1) Boot VGA console with xbox-drive utilities (default)
      2) Boot console with xbox-drive utilities in failsafe mode
      3) Boot text-console with xbox-drive utilities
      4) Boot linux with locking/unlocking utilities
      5) Boot to DOS with HD unlock tools
         (use with caution. Passwd log-files are not saved after reboot)


-Save and close the file.

-Youre done now, you must now run the "make-iso-win.bat" included in the package to make the bootable cd image. Then burn it and reboot your pc with it inside and run option #2.

Thats it for now, I think it will help some of you who cant boot the first 2 options, but I'm not certain so just test it out. (worked for me)

Once again props beerchug.gif to Ldots for your great application!!!!

Edited by Musashi, 09 January 2005 - 04:52 AM.


#2 Musashi

Musashi

    X-S X-perience

  • Members
  • PipPip
  • 359 posts
  • Location:the Under World
  • Interests:Halo, Halo 2, other videogames, and my girlfriend.
  • Xbox Version:v1.4
  • 360 version:v3.1 (opus)

Posted 09 January 2005 - 12:42 PM

Please reply here with your results, if it didnt work, or if it did.

#3 smithrookie

smithrookie

    X-S Young Member

  • Members
  • Pip
  • 45 posts

Posted 11 January 2005 - 08:35 PM

tried it, wouldn't work for me. Is this a function of the usb keyboard? It hangs on the screen when it gets to the keyboard. Option 3 works and i can unlock and lock, just not get to the functions.
Thanks
SMith


#4 domesticman

domesticman

    X-S Member

  • Members
  • Pip
  • 111 posts

Posted 12 January 2005 - 06:33 PM

This looks sweet, I'll try it tonight if I get a chance...anybody else had any luck with it?

#5 chimpanzee

chimpanzee

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,020 posts

Posted 12 January 2005 - 08:44 PM

I am afraid to say that you haven't explained why the change is needed. option 1 seems to be the same, option 2 adds atapicd. But what is the problem why people can't use these 2 options ? It may solve your problem, not necessary others.

#6 domesticman

domesticman

    X-S Member

  • Members
  • Pip
  • 111 posts

Posted 12 January 2005 - 09:43 PM

This is my problem...the main screen comes up fine and when I try option 1 and 2 I get

"Loading /isolinux/fatximage
Loading initrd.gz ..................................................................................................
...........................................................................................................................
.................................................."

and then it reboots.

Would this fix it?

#7 chimpanzee

chimpanzee

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,020 posts

Posted 12 January 2005 - 09:54 PM

sounds more like pci/irq issue if you see no message from linux.

BTW, if I am not mistaken, it is possible to type your boot options at the boot prompt for isolinux boot loader so a re-burn may not be needed.

#8 DaddyJ

DaddyJ

    X-S Messiah

  • Dev/Contributor
  • PipPipPipPipPipPipPip
  • 3,919 posts
  • Xbox Version:unk
  • 360 version:none

Posted 12 January 2005 - 11:08 PM

QUOTE(domesticman @ Jan 12 2005, 05:14 PM)
This is my problem...the main screen comes up fine and when I try option 1 and 2 I get

"Loading /isolinux/fatximage
Loading initrd.gz ..................................................................................................
...........................................................................................................................
.................................................."

and then it reboots.

Would this fix it?

This is a problem I have seen alot of, More of a PC BIOS/Chipset in-compatiblity, can usually be fixed by updating the PC BIOS, or by turning certain features off, e.g. Set HD's = NONE, and turn off BIOS Cacheing if present.
Also unplugging any un-needed devices, e.g USB and network, can also help.

This little script modification is just changing the video boot mode, witch is usually present in option 1,2,3 - options 3 however has a different kernal and may handle this issue differently. I cannot say this will work, I'm just stating some other instances where this has worked.


BTW : Musashi
This is a great little addition to XboxHDM, Thank You.



Edited by DaddyJ, 12 January 2005 - 11:09 PM.


#9 Musashi

Musashi

    X-S X-perience

  • Members
  • PipPip
  • 359 posts
  • Location:the Under World
  • Interests:Halo, Halo 2, other videogames, and my girlfriend.
  • Xbox Version:v1.4
  • 360 version:v3.1 (opus)

Posted 13 January 2005 - 10:05 PM

DAMN, I miss the "edit" option dry.gif .

To begin with, Ill explain something. This failsafe mode was taken almost entirely from the Knoppix boot cd. But I made an error on the tutorial, some more commands were needed on label 2 (failsafe).

Here they are:
CODE
label 2
 kernel /isolinux/fatxImage
 append initrd=initrd.gz load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=100000 rw root=/dev/ram pci=biosirq vga=normal atapicd nosound noapic noacpi acpi=off noscsi nodma noapm nousb nopcmcia nofirewire noagp nomce nodhcp


This CAN be just writen on the LINUX command line when the boot cd starts as said by Chipanzee, or just reburn another cd-r(w).

Now, what it does, it turns off auto-detect for most hardware leaving only the ones you really need.

DISCLAIMER: This procedure could work for you, but maybe it wont. I cant guarantee this WILL work for you or your PC. dry.gif

Edited by Musashi, 13 January 2005 - 10:19 PM.


#10 chimpanzee

chimpanzee

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,020 posts

Posted 13 January 2005 - 11:16 PM

Just FYI,

not all of the parameters are applicable to xboxhdm as many of them are KNOPPIX specific and means nothing to other distros. The only few that applies to linux kernel are those acpi, pci, irq, dma and noapic stuff.

In fact, 85% of why linux cannot boot is related to these things.

Edited by chimpanzee, 13 January 2005 - 11:16 PM.


#11 domesticman

domesticman

    X-S Member

  • Members
  • Pip
  • 111 posts

Posted 14 January 2005 - 05:22 PM

Haven't got to try this yet...teething baby is cramping my style laugh.gif

QUOTE
Now, what it does, it turns off auto-detect for most hardware leaving only the ones you really need.



Will I need to do something to turn the hardware back on when I'm finished? Sorry if this is a dumb question, but I have 0 understanding of linux, you guys are awesome and this workaround should help a ton a people.

Thanks!


#12 chimpanzee

chimpanzee

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,020 posts

Posted 14 January 2005 - 05:36 PM

it doesn't touch your hardware settings, just use some other ways to detect the hardware stuff, or say for example the noscsi(useless to xboxhdm as far as I know, KNOPPIX only) just tell KNOPPIX to not loading scsi drivers which comflicts with certain notebook LCD(!).

It is perfectly safe to type them on the boot prompt but many have no effect at all for xboxhdm. just try the acpi=off/on which usually solve of of the problems.

#13 domesticman

domesticman

    X-S Member

  • Members
  • Pip
  • 111 posts

Posted 15 January 2005 - 12:57 AM

I'm retarded -

I went home at lunch and started on this and when I saved the isolinux.cfg after pasteing in the new code it's not a .cfg file anymore....is that ok?

I represent 500 dumb noobs....thanks!

#14 domesticman

domesticman

    X-S Member

  • Members
  • Pip
  • 111 posts

Posted 15 January 2005 - 03:29 PM

Well I just tried it with the new file named isolinux instead of isolinux.cfg (properties still has it's type listed as cfg) and the menu sceen showed up correct with the new failsafe option but I still get

"Loading /isolinux/fatximage
Loading initrd.gz ..................................................................................................
...........................................................................................................................
.................................................."
and some new message like "unpacking linux" that goes by too fast

Then it reboots sad.gif



#15 jeanpierre57

jeanpierre57

    X-S Enthusiast

  • Members
  • 1 posts

Posted 20 March 2005 - 06:33 PM

I had the described problem, looked like my PC was frozen after choosing Option 1 or Option 2 of xboxhdm (main screen), keyboard was "cold" and only Power Cycle could bring my system back.

I decided to build another ISO with the "failsafe patch" and it worked beautifully.

You cannot imagine how happy I was.

Thanks for the tip !!!

I now have a Maxtor 120G in my Xbox.

May be you can add that it is preferable to modify the isolinux.cfg with wordpad (not with notepad) because on my system, Worpad shows CR and LF while Notepad doesn't ...

JP




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users