You are not logged in.
I have been attempting to create the USB installation disk and have been running into quite a lot of trouble. Every time I try to create the usb disk using the standard method (being dd if=./arch.iso of=/dev/sdb) it always creates a disk with a recursive partition on /dev/sdb. Perhaps it's my laptop which cannot handle this but my system cannot boot off a disk with this characteristic. This happens regards of using the net or core install (or archboot for that matter).
I had a small amount of success by manually installing the arch files onto a manually partitioned disk but the process started failing when attempting to mount some of the sfs files.
I have been trying to bend my brain to this problem all day and would very much like any feedback or solution people could offer. Unity is annoying me and I really want to get back into Arch world :-(
Thanks!
Brian
Offline
Thats true, isohybrid is a hack that does this "recursive" thing.
All you need to do using the better method (non-dd) is:
Create the partition sdX1 on /dev/sdX, mark as active, format with FAT or EXT2/3/4 then:
dd bs=440 count=1 conv=notrunc if=/usr/lib/syslinux/mbr.bin of=/dev/sdX # Or just: cat /usr/lib/syslinux/mbr.bin > /dev/sdX
dosfslabel /dev/sdX1 ARCH_201108 # If sdX1 is FAT
e2label /dev/sdX1 ARCH_201108 # If sdX1 is EXT2/3/4
mount archlinux-2011.08.19-netinstall-i686.iso /mnt/iso
mount /dev/sdX1 /mnt/usb
cp -r /mnt/iso/arch /mnt/usb
extlinux -i /mnt/usb/arch/boot/syslinux #This works for FAT too :)
umount /mnt/usb
umount /mnt/iso
Last edited by djgera (2011-12-01 01:11:25)
Offline
I tried the above method and had some success but I ran into trouble when loading the arch install environment. The process froze when attempting to mount the "root-something.fs.sfs" at which point I threatened my computer with a thousand lashes and still it refused to unfreeze. Any thoughts on what could be causing this?
Offline
Weird, can you provide an screenshot? how is your machine, CPU/RAM?
Do you try any of latest testisos? http://releng.archlinux.org/
Offline
I will go ahead and try it again and take a snapshot but I just discovered that the HP BIOS does not handle isohybrid images so that offers some insight but not a work around.
Offline
Ok, so I tried the above method (plus remembering to mark the partition with the bootable flag) and this time it failed while attempting to mount the cowspace thingy. I think I am going to try to use my CD bay tomorrow when I return to work to hopefully get around these issues, but I am not optimistic since I also tried using a USB CD drive and ran into the same problem presumably due to the fact that the BIOS still cannot work with a isohybrid CD.
Offline
Ok, so I tried the above method (plus remembering to mark the partition with the bootable flag) and this time it failed while attempting to mount the cowspace thingy. I think I am going to try to use my CD bay tomorrow when I return to work to hopefully get around these issues, but I am not optimistic since I also tried using a USB CD drive and ran into the same problem presumably due to the fact that the BIOS still cannot work with a isohybrid CD.
I don't see an error here.
Offline
It does not report any errors, it simply locks up and does not continue beyond the point in the snapshot.
Offline
Just for the record, I grabbed my CD bay from work and burnt the iso to an actual CD and tried that and got a bit further although it still fails, only this time it hangs a couple of lines further down when mounting a different sfs file.
Offline
The saga continues.... Just for to go through the motions, I just installed arch on a virtual machine without any issues so I am sure that the iso can work under the some circumstances.
Offline
maybe something goes bad between your hardware/firmware vs kernel. You have tested any of latest testisos?
Also try booting with bootparam: ignore_loglevel
Offline
Downloading the lastest and greatest test iso now, I will let you know.
Offline
Ran the 2011.12.01 and it hung up on the command i2x_register_adapter if that means anything to you.
Offline
kernel panic? i2c_register_adapter
Try bootparm:
modprobe.blacklist=i2c-core
Offline
Any thoughts on how to set a boot parameter?
Offline
Press [Tab] to edit options in syslinux then add it in such line
Offline
It exhibits the same behavior at the same point.
Offline
Alright, so I have gotten some progress. I have figured it is the display which is not working. When I assume that we are at the command prompt and type "reboot" it does so, so clearly there is something going on with the display drivers. So now I suppose I have to get into Kernel Mode Setting which I know next to nothing about so I guess it is time to educate myself.
Offline
I am happy to say that I have made this post from a working arch install. The issue was an with the nouveau driver which I blacklisted and everything else was straightforward. So the issue was the video framebuffer crapped out mid boot and yielded a red herring situation.
Thanks for all the help!
Offline
I am happy to say that I have made this post from a working arch install. The issue was an with the nouveau driver which I blacklisted and everything else was straightforward. So the issue was the video framebuffer crapped out mid boot and yielded a red herring situation.
Thanks for all the help!
Maybe I am having the same problem... how did you exactly resolve it?
Offline
brianbourke75 wrote:I am happy to say that I have made this post from a working arch install. The issue was an with the nouveau driver which I blacklisted and everything else was straightforward. So the issue was the video framebuffer crapped out mid boot and yielded a red herring situation.
Thanks for all the help!
Maybe I am having the same problem... how did you exactly resolve it?
Check if you're not blacklisting the graphics driver.
Offline
zhangxiao wrote:brianbourke75 wrote:I am happy to say that I have made this post from a working arch install. The issue was an with the nouveau driver which I blacklisted and everything else was straightforward. So the issue was the video framebuffer crapped out mid boot and yielded a red herring situation.
Thanks for all the help!
Maybe I am having the same problem... how did you exactly resolve it?
Check if you're not blacklisting the graphics driver.
Hmm... how to do that
Offline
Try searching the wiki e.g. https://wiki.archlinux.org/index.php/Ke … acklisting
Offline
Try searching the wiki e.g. https://wiki.archlinux.org/index.php/Ke … acklisting
Thanks... I read the Wiki page. However what i don't get is how should I check the blacklisting before boot up? I did not add any bootparam so there is no blacklisting i guess...?
Offline
You can boot a liveCD and inspect the configs.
Offline