Dell M140 w/ iATKOS v7 - Solutions?

[Arisian]

Hey everyone,

 

I could just just a bit of advice here. I've looked just about everywhere I could to find an answer for this as well as stayed up way to late a few nights in a row.

 

In short, here's the issue.

 

I have a Dell M140 and Im trying to install iATKOS v7 on it. It has a busted CDROM, but I have booted and installed from a flash drive successfully.

 

Nonetheless, once it installs and boots, it freezes at the Apple Screen and stops communicating w/ the HD. Ive read and tried many things in an attempt (like trying to hit a golf ball w/ a BB gun from 200 yards) to try and resolve this.

 

Nonetheless,

Ive included a screen of the verbose logging.

I'd very much appreciate some help. Ive done this in the past and had no problems, but never w/ a Dell laptop.

 

I feel like Im close but maybe Im not!

 

Thanks in advance,

Brian

[Arisian]

Hey everyone,

 

I could just just a bit of advice here. I've looked just about everywhere I could to find an answer for this as well as stayed up way to late a few nights in a row.

 

In short, here's the issue.

 

I have a Dell M140 and Im trying to install iATKOS v7 on it. It has a busted CDROM, but I have booted and installed from a flash drive successfully.

 

Nonetheless, once it installs and boots, it freezes at the Apple Screen and stops communicating w/ the HD. Ive read and tried many things in an attempt (like trying to hit a golf ball w/ a BB gun from 200 yards) to try and resolve this.

 

Nonetheless,

Ive included a screen of the verbose logging.

I'd very much appreciate some help. Ive done this in the past and had no problems, but never w/ a Dell laptop.

 

BTW, THE VERSION is 10.5.7. Im going to try a few different kernels and see if that helps at all.

 

Would till appreciate some help

heh

 

I feel like Im close but maybe Im not!

 

Thanks in advance,

Brian

[vilpostus]

The infamous Kernel Panic. Need a different kernel. Install a different kernel(s) then customizing installation. e.g. voodoo or voodoo970. Though may install it after the install but it's more "tricky". Now then you have a different kernel installed boot it with -v voodoo or -v voodoo970 flag.

[Arisian]

hope this doesnt come across as super noobish.

 

Nonetheless, Ive copied several kernels over to the root folder of my install disk and have tried to flag them by calling it w/ "kernel name" -v.

 

That being said, It seems like the kernel is ALWAYS trying to boot to my firewire port rather than actual drive (even though ive changed the boot plist to rd=disk0).

 

Im slightly annoyed at the bios that Dell uses for this machine, it's def. the worst i've ever seen, esp since I can't set HD primary and slv...)

 

Am I doing something incorrect here?

 

Thanks so much for your reply:)

 

Brian

[vilpostus]

Actually kernel flag should look like this

-v voodoo

Without any "". Another thing. Then you install a kernel, don't forget to set the right permissions for it.

sudo -s
chmod -R 644 /kernel_name
chown -R root:wheel /kernel_name

or it will not boot properly.

 

About booting from firewire. rd= flag must look like this rd=disk2s2. Where 2 is a disk to boot s2 is a partition to boot. Usually this is displayed at darwin prompt e.g. then you type boot flags. It looks like this hd2,2. That it would be disk2s2. Or hd0,1=disk0s1

 

There is an important thing about installing a boot loader e.g. Chameleon. Ever you install it to an EFI partition or to OS X partition. It is important to know where the bootloader resides to set the right boot partition/disk.

 

I'd suggest to boot with UUID flag. E.g. UUID=xxxxxxxxxxx Where xxxxxx is the disk the OS X is installed to, ID name, assigned by an OS X. You can know that by booting to install disk/flash drive>Disk Utility>select disk>i button (info).