Unsolved
This post is more than 5 years old
9 Posts
0
30914
January 25th, 2013 15:00
Problem with my m11x
I have a Alienware m11x R2.
I started off by having the same problems as the ones in this thread
http://en.community.dell.com/owners-club/alienware/f/3746/p/19485731/20284537.aspx#20284537
and my BIOS was't detecting my HDD, so i went out to buy a SSD believing it was my HDD, but it still ends up coming up with this error even when i try to boot up to install the OS.
"Atheros pcie ethernet controller v2.0.2.6(09/28/2010)
check cable connection!
PXE-MOF:exiting intel pxe rom.
no bootable device-insert boot disk and press any key."
any ideas?
0 events found
No Events found!


damaya01
9 Posts
0
January 25th, 2013 15:00
I forgot to say that after i installed the new SSD it does read it? So i'm guessing it's not the interposer right?
Tesla1856
10 Wizard
•
17.6K Posts
•
70.3K Points
0
January 25th, 2013 16:00
Be sure "USB Boot" is enabled in BIOS.
Again, check the order of bootable devices.
Be sure to turn off "Network Boot" to remove that variable (also, just gets in the way).
damaya01
9 Posts
0
January 25th, 2013 16:00
.
damaya01
9 Posts
0
January 25th, 2013 16:00
How do I disable the network boot? In the boot tab I can only switch the order. There's a network tab that has blue tooth, wireless network, or wwan and I can only enable or disable?
Tesla1856
10 Wizard
•
17.6K Posts
•
70.3K Points
0
January 25th, 2013 16:00
If drives work in other computers or maybe with USB dock, seems to me, it would have to be something in the computer.
As in the other thread ... either the interposer or motherboard is bad. It might just be the interposer is not making a good connection.
damaya01
9 Posts
0
January 25th, 2013 16:00
Well I'm trying to boot off a usb done it before on other laptops but it goes straight to that error?
damaya01
9 Posts
0
January 25th, 2013 16:00
Yea so it can't be the interposer because the bios is reading my new ssd?
Tesla1856
10 Wizard
•
17.6K Posts
•
70.3K Points
0
January 25th, 2013 16:00
AndrewSi
4 Apprentice
•
901 Posts
0
January 26th, 2013 07:00
I have come across this exact problem before, although I dont think it was a M11x, it has happened on several occasssions on different Alienware laptops and each time I have been able to fix it by simply resetting the system BIOS to default and restarting