You are not logged in.
So we are having a bit of a trouble building ArchBang using ArchISO-git package. I tried with testing enabled and disabled and hence I think the problem is elsewhere. When i boot I get the message:
Waiting 30 seconds for /dev/archiso
and after a while it drops me off to ramfs$ prompt!
The Makefile is the plain Makefile found here: http://wiki.archlinux.org/index.php/Archiso#Makefile
Last edited by sHyLoCk (2010-02-22 05:15:34)
Offline
That is very interesting. Let me check that out. It is a hook problem and you can see exactly where it fails "mounting /dev/loop0 on /tmpfs/blahblah". This might be a problem introduced by the new mkinitcpio. You can look into the hook though and see what might cause it. I'm almost sure that it is a command with a flag that was valid in klibc that no longer is valid.
Offline
Well, we have also problems with the new mkinitcpio so we where forced to use old pkgs to get our release done. We had those hooks:
HOOKS="base udev pata scsi sata usb firmware larch1 larch2___aufs___ larch3"
firmware is known to not work anymore. autodetect should be added. Will wait some days then I take it on and recheck the issues I have with mkinitcpio.
visit chakra-project.org to get latest Chakra GNU/Linux
Offline
Removed fw, added autodetect still problem persists!
HOOKS="base archiso-early udev archiso autodetect pata scsi sata usb filesystems usbinput"
While trying with an older archiso version, I get the previous error of ramfs$
Any other ideas?
Offline
Well, we have also problems with the new mkinitcpio so we where forced to use old pkgs to get our release done. We had those hooks:
HOOKS="base udev pata scsi sata usb firmware larch1 larch2___aufs___ larch3"
firmware is known to not work anymore. autodetect should be added. Will wait some days then I take it on and recheck the issues I have with mkinitcpio.
Where do you get the information that autodetect should be added? Has something changed about autodetect?
larch: http://larch.berlios.de
Offline
Note: As of the current date, the archiso in extra is not up-to-date enough to follow this guide and its usage is therefore not recommended.
From wiki page!
Mr Green
Offline
We over at the ArchServer project are having problems with ArchISO also (www.archserver.org). I'll let you know if we find a workaround. Keep us posted on your progress too!
Offline
Thanks. I'm over there at AS as well. Not active but will let you guys know if I find some thing. Same with chakra.
Trying out different ways like downgrading the system and using pacman -S from local repos. Let's see if that works.
Offline
@sHyLoCk
I updated my archiso-live scripts to support busybox like 3 weeks ago. I had more problems compiling busybox then updating the scripts. I have it working anyway.
http://github.com/godane/archiso-live
I hope this helps.
I'm working on a live cds based on Archlinux. http://godane.wordpress.com/
Offline
godane, shylock, other image-building-guys.
it would be useful if you could subscribe to the arch-releng mailing list and discuss your issues there.
I've been having similar issues, and the ML seems like the most appropriate place to discuss these things in a certral place
http://mailman.archlinux.org/pipermail/arch-releng
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
@ Shylock
Larch 5.3 suffers from the exact same problem, and it definitely has to do with the new mkinitcpio.
See more here:
Offline
releng builds boot fine btw. using the latest mkinitcpio from core and archiso from git
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Offline
The hook has been renamed to archiso_early, careful!
Offline
Still, any system made from archISO is not bootable.
Suffering from this same error.
Tried it again with today's git snapshot.
Offline
Me too.
For now we are using larch7 for building our ArchBang105. It works fine.
I've been using larch 5.3 for many months now and I am familiar with it.
IMHO, using larch7 is a waste of time. Why:
- It is not as configurable as larch5.3 is.
- GUIs are buggy, unpredictable, and inflexible.
- Gradgrind eventually will abandon it, as he did with larch5.3.
Offline
current archiso git requires unreleased mkinitcpio 0.9.3 (use git for now) or reset archiso git to commit 22f91073
Offline
pacman -S devtools
mkarchroot /tmp/pichicho base
mkarchroot -r bash /tmp/pichicho
pacman -S git squashfs-tools syslinux devtools cdrkit make asciidoc
cd /tmp
git clone git://projects.archlinux.org/mkarchiso.git
git clone git://projects.archlinux.org/archiso.git
cd mkarchiso
make install
cd ../archiso/archiso
make install
cd ../configs/syslinux-iso/
make net-iso
Last edited by djgera (2010-02-20 15:33:30)
Offline
Commit 22f91073 works with current mkinitcpio and produces working bootable media.
Bye-bye non-functional larch7.
Offline
Guys help me keep the wiki article up to date when you find that stuff changes and you know how to update it so it works.
Offline