You are not logged in.
Except the bootloader issues everything else looks fixed now. So I invite you all to look at page 6 of this thread where I've posted the related installer part.
Perhaps its just personal preference for me, but don't you think it would be better to post new threads than keep a long one going like this? Its difficult to find relevant information in long threads, I find.
Dusty
Offline
I suppose we could split this thread into one posting about new releases and another that is about issues and troubleshooting.
Offline
Mr Green
Offline
Just uploading RC5 isos. A small but important kernel fix should solve the bootloader issues.
EDIT:
Offline
I'll be doing considerably more now now I'm back online. After major network issues the last week or so I *think* it's all good to go. We'll see...
Offline
Alright, I just installed with RC5 and can confirm that GRUB works with Arch64 now. It would seem that most bugs with the setup process have been worked out and that we can now start to focus attention to porting PKGBUILDs and other not-so-installer-related issues.
I must say congrats AndyRTR and all others involved. This is really starting to shape up into a great Arch port. My plan is to try and keep just Arch64 as my day to day OS and try and find some bugs.
Offline
Alright, I just installed with RC5 and can confirm that GRUB works with Arch64 now.
That's good. If somebody else can confirm this for lilo I think I can make the RC5 our first official release ISO.
It would seem that most bugs with the setup process have been worked out and that we can now start to focus attention to porting PKGBUILDs and other not-so-installer-related issues.
I must say congrats AndyRTR and all others involved. This is really starting to shape up into a great Arch port. My plan is to try and keep just Arch64 as my day to day OS and try and find some bugs.
I have removed arch32 from my pc. If we don't break too much while updating packages arch64 is as much stable as arch32 is. But I'm sure there are some porting related bugs left.
AndyRTR
Offline
Ok I can confirm that lilo is working now on RC5 ;-)
o7
Mr Green
Offline
But I'm sure there are some porting related bugs left.
Right now, I'm having problems with configure running correctly when trying to build libstroke. I get a problem with host system x86_64-unknown-linux-gnu not known. Passing --host=${CHOST} doesn't solve the problem b/c x86_64-pc-linux-gnu isn't known either. This works fine with some builds but not with others and I'm not sure if there is a good way to correct this problem. My development skills have been traditionally limited to Windows, so I'm not the best with open source build systems.
Also, I've been deprived of cafeine lately b/c of a possible heart issue, so I'm not quite as sharpe as usual.
Offline
Ok, then let's wait a few days more. If no new errors occur I want to make RC5 our final ISO.
I'm not sure if we should call it "0.7.1" as it is far beyond the arch32 ISO from last autumn. I'm at all not sure if we should follow the arch32 release cycle there. It will always take some time to port all the stuff. So I suggest to call the ISOs by release time. Our first one would be called "04/2006".
There will be a base iso and the ftp-only and I hope a full current cd. Only thing we have to decide is if we will keep hotplug or if we will drop it. As I haven't seen any 64bit distribution having a kernel24 and I think arch32 will soon drop kernel24 I suggest to drop hotplug at all.
Offline
sounds cool to me ... 8)
Mr Green
Offline
On a positive note, synce had been busted for me on Arch32 since the last kernel upgrade but seems to compile and work fine on Arch64. Go figure.
Offline
RC5 works fine for me too.. I've tested the base ISO...both reiserfs/xfs work, and LILO worked fine too. I haven't tested GRUB.
andy: drop hotplug. don't think twice about it
I think using dates for our releases would be a good idea too, at least until the port is finalized.
Offline
RC5 works fine for me too.. I've tested the base ISO...both reiserfs/xfs work, and LILO worked fine too. I haven't tested GRUB.
andy: drop hotplug. don't think twice about it
I think using dates for our releases would be a good idea too, at least until the port is finalized.
there you are my friend lol.....
@ganja Now that RC5 is working I think I'll reinstall again ;-)
Mr Green
Offline
Yes, I want to reinstall also, but this time I'm going to zero-fill hard disc to ensure that there are no leftover grub bits from my 32-bit install.
I also agree with the date based versioning system. This port will never be a verbatim copy of 32-bit arch and we will probably go through a few revisions before all is good for every single user. Perhaps we could eventually sync the versioning and coordinate with the Arch32 developers, but for now that isn't an option. The step of an inital release is important and should draw more users, which should also add more bug reports.
Offline
...This port will never be a verbatim copy of 32-bit arch and we will probably go through a few revisions before all is good for every single user. Perhaps we could eventually sync the versioning and coordinate with the Arch32 developers, but for now that isn't an option.
Reading the mailing list will tell you other plans
Offline
Ah, that clears up alot. I should probably subscribe to that mailing list
Offline
Congrats on Arch64's first release iso... I notice that 04/2006 is currently on the ftp server over at Arch64.org.
Offline
New ISOs for testing available: http://www.archlinux.org/~andyrtr/
Read also the post on the arch-port mailing list!
AndyRTR
Offline
New ISOs for testing available: http://www.archlinux.org/~andyrtr/
Read also the post on the arch-port mailing list!
AndyRTR
Grub appears not to work. It locks up after GRUB.
--
JSkier
Offline
There were no changes for months now. It's still the same on i686 statically built package. Any output on the tty5 or tty12 ? Can you fix it with booting the iso to rescue mode like in the Wiki written? Maybe it's more safe to boot the cd with "arch noapic" option.
Anybody else having this error?
Anything else you need to report? Installation successful at all?
Offline
There were no changes for months now. It's still the same on i686 statically built package. Any output on the tty5 or tty12 ? Can you fix it with booting the iso to rescue mode like in the Wiki written? Maybe it's more safe to boot the cd with "arch noapic" option.
Anybody else having this error?
Anything else you need to report? Installation successful at all?
There is no output. I will use the boot cd and whether or not grub-install works via command line. Weird it didn't have any output.... Unless anyone else has this problem, maybe it's my hard drive; I'll post an update when I get around to looking into this more.
--
JSkier
Offline
Installed GRUB fine from the Arch64 install CD and am currently running only Arch64 on this system. GRUB seems to work fine, with no locking up or failing to boot.
Offline
Installed GRUB fine from the Arch64 install CD and am currently running only Arch64 on this system. GRUB seems to work fine, with no locking up or failing to boot.
I got a segmentation fault when reinstalling grub while using the rescue method to get in my system. I used grub-install hd0 (for the mbr). It still reported a success, however I know thats not the case upon reboot. Is this my hard drive or what? I tried reinstalling grub by copying over the pacman file with a usb stick even, only yielding the same results. I can post the full output of the seg fault later if needed as well.
--
JSkier
Offline
Have you checked the md5sum for the iso?
Offline