You are not logged in.
minimax would it need rebuilding to work with 64 ?
I used frugal cd as an example ....
you got any links for iso (arch) I'll take a look
Mr Green
Offline
if you do that then people won't be able to chroot to compile their own kernel and stuff. Make sure the kernel that the cd boots is 64bit too! Then the fs of the cd can be 32bit.
Offline
if you do that then people won't be able to chroot to compile their own kernel and stuff. Make sure the kernel that the cd boots is 64bit too! Then the fs of the cd can be 32bit.
I don't know eaxactly what you mean. Right now we should be thankfull if we will find a less comlicated way to get it on the hard disc. And it should help repairing the bootloader.
Adding a third 64bit kernel is no problem. But I'm not sure if it would allow you to access the rest of the 32bit cd. Watch my experiences above.
Wait a few minutes. I'm just uploading my next attempt. It's just the 32Bit base-iso from archlinux where I replaced all packages. But I'm not sure if we need it at all. If that will work a simple ftp installation should do it right now using the existing archlinux 32bit iso. Although the main mirror http://arch64.org is beeing rejected you should be able to use ftp.xentac.net and /amd64/current/ for directory. I'm wondering if anybody hasn't tried it yet
Offline
give us a minute I'll burn it ...when you have uploaded it ;-)
Mr Green
Offline
Offline
what i'm saying is that you can have a 32bit userland and everything on the cd, but if the kernel is also 32bit then people will not be able to chroot into their system from the cd after its installed. So, you need to have a 64bit kernel with support for running 32bit apps. That way the userland can be 32bit and people will be able to chroot into their system too.
Offline
Mr. Green has tested it. It boots but pacman.static claims not working. That was a 64bit version. Now I've put back the 32bit one. Uploading BETA4 right now. Hope that will fix it.
But Mr. Green was not able to catch a package list trying a ftp install from Xentacs server. Anybody else got the package list downloading? What server and path is needed?
Offline
Offline
ok so I got server path wrong, just checked it shold be /amd64 not /amd64/current so it may work
will d/l beta4 & test :-)
Mr Green
Offline
Ok BETA4 .... loads packages ok ... hotplug missing from packages .....but I just removed it & it loads base ok
loading kernel gives chroot error
FTP ..... path to package list does not work .. I assume its the name of file thats problem
Another iso to test ouch!!!
Mr Green
Offline
ToDos for BETA4:
1. hotplug is still in the package list (and if you select all packages) it complains that it can't be found. (Deselecting it helps! :-))
2. lilo is not on the package list and can't be used as a bootloader (it complains: no lilo.conf, is it installed?)
3. While installing the kernel:
installing kernel26... done.
chroot: cannot execute /bin/bash: exec format error
/mnt/sbin/ldconfig: 1: Syntax error: "(" unexpected
Package installation complete
It might work, but I can't test it, because I can't use grub on my system configuration...
Regards,
Moritz
PS: @AndyRTR: GREAT WORK SO FAR!!!!
Offline
@Moritz .....
I wondered if qemu may help if you create a hard disc img & install to that testing would be quicker.... less burns lol
Yes hotplug & kernel ... well we may need a 64 kernel on install CD to be able to chroot (create initrd)
FTP install is looking for packages.txt on ftp.xentac.net its called packages-list
but we are getting closer
Great Work
/me o7 you
Mr Green
Offline
downloading it now.
Offline
MrGreen: probably, but everybody else would do it the way I do, so I may find another thing you won't (i.e. Volume Id is wrong...)
FTP installation does not work for me: pacman could not be found.
Offline
My thoughts about our problem with ldconfig.
- The install-cd is 32bit and will probably stay 32bit for a while.
- The installation works, all packages will be extracted to /mnt so the 64bit system is fine.
- After installing a new/the kernel ldconfig needs to be run. For that the setup uses the following command (only guessed, but probably right):
/mnt/sbin/chroot /mnt /sbin/ldconfig
/sbin/ldconfig is /mnt/sbin/ldconfig, so it's 64bit binary.
Running this binary in a 32bit-system won't work (remember, even if we chroot, we're still 32bit)
I think a static ldconfig might work at this situation. The installer should do this:
cp /arch/pkg/setup/ldconfig.static /mnt/sbin
/mnt/sbin/chroot /mnt /sbin/ldconfig.static
rm /mnt/sbin/ldconfig.static
My problem at the moment: I don't know how to build a static ldconfig, because it's part of glibc and so far it won't compile a static binary for me...
My two cents,
Moritz
Offline
would having a 64 bit kernel help (on iso) .... ? boot using that then install
Seems we have a 32/64 problem would it be better to start from scratch & build a 64 iso
thoughts
Mr Green
Offline
well you can still use a 32bit userland for the cd, but the kernel needs to be 64bit with IA32 emulation support. From what andytr told me though, that doesn't seem to work.
Offline
Just a small step: I've done a BETA5 iso where the lilo and hotplug issues should be fixed. Try it out. Now we will have to fix the chroot issue!
Offline
BETA6 should improve ftp install giving you right paths for our 2 mirrors. A packages.txt will be created by a cronjob from now on so that you can install everytime straight the latest packages.
http://arch64.org/packages/iso/arch-0.7 … 4-base.iso
Test it. If that is ok we should now concentrate on the chroot issue. Please post me more output from the installer. I haven't found so far where the chroot happens.
AndyRTR
Offline
umm, I don't know how else to say this, but are you sure that iso was 64-bit? I noticed that uname -a said it was i686, then I threw it into an older p4 system and it had no problem booting it.
Edit: My bad, I didn't notice that the installer was switched to a 32-bit version, simply saw the thread and read it backwards to get the latest release. I thought it was like the old one. I'll go back to my corner now.
=> Now known as jb
Offline
Ok Beta6 loads packages ok (CD) ..
Kernel will install (but no initrd! chroot)
Guess you could chroot in from a 64bit distro to kick start kernel lol
would an stock initrd26-full.img transfered to /boot work .? that matches iso kernel?
or does mkinitrd need to run to set up correctly?
Mr Green
Offline
I can put whatever you want on the cd into a seperate directory. So you can try to get it work. Once you now how to deal I can try to put it into the installer. It's a bash script.
I've asked Judd about the chroot/ldconfig issue. Let's see, if he can help us again.
Offline
For now I don't see a good way to go with a 32bit ISO cd. So we have to start again with a pure 64bit one. Moritz will help me.
I want ask all our Arch64 packagers to help shorten our package ToDo list :!:
Offline
This is the first iso completly using our 64bit binaries. Busybox has been updated. A new kernel is included. Only one common kernel including sata drivers built in, scsi drivers build as modules.
It's known that dhcpd is not working from within the installer. I could so "dhcpd restart" on command line but I don't know if it will work. I guess ftp installation wouldn't be possible too.
So test it and report bugs that you will find. Post them on the arch ports mailing list, here or at IRC #archlinux64.
A BIG thanks goes to Moritz aka mo|arch who has done a fabulous job. He's made a nice build script that helps a lot for building the cd and makes testing easier.
CU
AndyRTR
Offline
I'm testing the beta 7 iso, problems :
- no reiserfs in the menu to fomat partition only ext2/3
- no dhcp
- no network even with manual configuration ( even when modprobe the right module always have the Link encap: UNSPEC like on arch 0.7.1 iso :shock: )
- no way to install base :
warning: cannot find chroot binary - unable to run scriptlets
Wishlist :
- loadkeys
- no more devfsd in base (useless)
Regards
-=<>=-
Archlinux French site : http://www.archlinux.fr
Offline