EvilZone
General Tech => Operating System => : hppd December 25, 2013, 06:52:47 PM
-
I was getting tired of windows 8 so I decided it would be a nice time to install Arch and learn linux the propper way. So I disabled secure boot and fast boot. Made Sure AHCI was enabled, then I put in the USB drive and booted my pc. It gave the first menu and when I chose to boot arch it gave a couple errors. Something along the lines of
tg3: Problem fetching invariants of chip aborting arch
(this must be something with my wireless so I think it doesn't matter for booting and should be fixe later)
and
usb 1 10 string descriptor 0 malformed (err =-61) arch boot
Then tries to load the hard drive I think (I see SDA a couple of times on the screen) and after like 1 second the screen turns black. I have googled this problem but most people only get these errors after they have installed their OS not while booting.
I have tried useing a different USB but it doesn't change shit. Also something peculiar is that windows sees my 8gig stick as 30.9 meg after burning the iso to it.
Details of lappy:
i7-4702mq
120Gb SSD + 500 GB HDD
Acer Nplify 802.11 a/g/n +BT 4.0
GeForce gt 750M
It would be greatly appreciated if you could help me resolve this problem. Right now I'm looking trough my house to find an empty cd..
-
How did you create the usb boot ?
Basic thing to make sure is if you checked the md5 checksum ? I can't stress that enough.
Might be hardware, in case you can use certain parameters to disable hardware/features on boot.
Look at hardware at a later point , I know there are issues with secure boot.
.
How far does it boot? Did you check any logs?
-
I made it with win32disk imager the problem might lay there. (Although it used to work with other distro's). The md5's match, and I don't know what else I can change about the hardware
God dammit I tried to format the drive. Apperently burning the iso has corrupted it, can't even format anymore. Same problem with my other one, damn this is fucked up
EDIT: This seems to be a common problem with win32 Disk Imager..
Aight I was able to fix my usb, I'm going to try it once with archbang and see if that works.
Staff note: edit your posts for once, ugh....! I thought it automatically added to the previous post thx for fixing
-
I made it with win32disk imager the problem might lay there. (Although it used to work with other distro's). The md5's match, and I don't know what else I can change about the hardware
God dammit I tried to format the drive. Apperently burning the iso has corrupted it, can't even format anymore. Same problem with my other one, damn this is fucked up
EDIT: This seems to be a common problem with win32 Disk Imager..
Aight I was able to fix my usb, I'm going to try it once with archbang and see if that works.
Staff note: edit your posts for once, ugh....! I thought it automatically added to the previous post thx for fixing
Nothing to worry about, USB is fine just needs repartitioning.
And you use what for burning the iso to the key ?
Something like unetbootin or do it from a live boot something.
Your making this hard on yourself with weird windows tools.
-
I used win32 disk imager. I tried it with Unetbootin to same fcking error. So it must be my hardware. Damn you Arch! I'm not gonna give up before I can even start the installation.. Could it be because the filesystem of the usb was FAT32? It works in a virtualbox.. Going to try writing it from a live cd I have laying around..
EDIT: SHit, this old mint doesn't want to accept my wireless card/ mouse and doesn't want to open gParted.. Trying on another laptop, I'm starting to suspect that Acer tries to make it extra hard to use Linux on their devices..
-
I've said it a hundred times on a hundred different threads. The dd utility is the only way to successfully create an Arch usb, at least for me. Kind of frustrating because you need a *nix to use the dd utility, and you need the dd utility to get a linux. I had a NON-live Kali usb which I used to use the dd command. Huge pain in the ass, but it's the only thing that's ever worked for me.
-
Thanks lucid, I'm doing that at this very moment. The reason I didn't do this earlier is because my computer was acting fucking weird with the live cd and I lost my kali usb somewhere..
I guess alot of people have this problem, 14 guests are watching :D
Aight it's ready going to let you know if it worked.
Edit: Nope it didn't work, back to google.
It also said something about no cacheing mode page present.
By the way the boot menu isn't the way it should be with the Arch logo and stuff just plaintext. In my vm it looks like it should be.
And it isn't the stick it works on another pc