You are not logged in.
Have you checked the md5sum for the iso?
Prior to burning the cd the MD5 checked out. Like I said I also downloaded the package from the archlinux.org server and copied it to a usb stick and tried to install it that way as well.
--
JSkier
Offline
Same grub problem over here.
Lilo seems to be working fine, though.
Offline
If you have still i686 archlinux running test this pkgbuild to build the pkg and install it under arch64. Let's see if it helps:
# $Id: PKGBUILD,v 1.20 2006/05/14 17:57:32 uid1016 Exp $
# Maintainer: judd <jvinet>
pkgname=grub
pkgver=0.97
pkgrel=2.1
pkgdesc="A GNU multiboot boot loader"
arch=(i686 x86_64)
url="http://www.gnu.org/software/grub/"
depends=('ncurses')
source=(ftp://alpha.gnu.org/gnu/grub/grub-$pkgver.tar.gz
menu.lst install-grub)
backup=('boot/grub/menu.lst')
md5sums=('cd3f3eb54446be6003156158d51f4884' '3385ef0199d02c3750e4e684728b5aad'
'615101c2fc1bc2204be8eba33cfaf52c')
build() {
cd $startdir/src/$pkgname-$pkgver
# set here wanted destination architecture
#DESTARCH="i686"
DESTARCH="x86_64"
# optimizations break the build -- disable them
CFLAGS="-march=i686 -O1 -pipe"
#arch64 fixes for static build
if [ "$DESTARCH" = "x86_64" ]; then
CFLAGS="$CFLAGS -static"
if [ "$CARCH" != "i686" ]; then
echo "this package has to be build on i686, won't compile on x86_64"
sleep 5
return 1
fi
fi
./configure --prefix=/usr --bindir=/bin --sbindir=/sbin
make || return 1
make DESTDIR=$startdir/pkg install
install -D -m644 ../menu.lst $startdir/pkg/boot/grub/menu.lst
install -D -m755 ../install-grub $startdir/pkg/sbin/install-grub
# symlink for compatibility with the <=0.7 installer
mkdir -p $startdir/pkg/usr/share
ln -s ../lib/grub $startdir/pkg/usr/share/grub
}
Offline
One more thing: ati-fglrx install a module for the 2.6.16 kernel, instead of 2.6.17.
Offline
That has nothing to do with the ISO. The package from extra repo needs only an update.
Offline
No, it has nothing to do with the ISO itself, but it means that the installation process as a whole has a severe problem. If the extra repository is not in sync with the ISO, then what good is it?
(I fixed the package manually and have a working system, so I am not seeking help with that. Just wanted to inform).
As for the grub problem, why do I need to create the package on an i686 machine (or did I get you wrong)?
Elad
Offline
As for the grub problem, why do I need to create the package on an i686 machine (or did I get you wrong)?
Read the comment in the pkgbuild!
Offline
Here is what I get with the new package:
[root@tull ~]# grub-install /dev/hda
/sbin/grub-install: line 458: 2519 Segmentation fault $grub_shell --batch $no_floppy --device-map=$device_map >$log_file <<EOF
root $root_drive
setup $force_lba --stage2=$grubdir/stage2 --prefix=$grub_prefix $install_drive
quit
EOF
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
(fd0) /dev/fd0
(hd0) /dev/hda
Offline
Looks weird. Grub is not perfect. A lot of incompatible hardware and filesystems are known. Maybe you are affected. Read more here: http://savannah.gnu.org/bugs/?group=grub
On one of my systems I can install grub but it won't find the root partition.
So you will have to go with lilo. Hope you will like Arch64 though.
Offline
maybe something similar: http://ninja.linux-phreak.biz/pipermail … 00188.html
Offline
Looks weird. Grub is not perfect. A lot of incompatible hardware and filesystems are known. Maybe you are affected. Read more here: http://savannah.gnu.org/bugs/?group=grub
On one of my systems I can install grub but it won't find the root partition.
So you will have to go with lilo. Hope you will like Arch64 though.
Well what is strange about this is that it worked on the older cd's fine on my laptop. I'll play with some of the older versions and see what they yield. I hate using lilo :?
--
JSkier
Offline
Ok, next shot. I've just finished uploading a new base and ftp iso.
Full current cd will follow later.
Changes:
- glibc linker fixed
- mc/mplayer dependecies fixed
- memtest86+ included as a bootoption
- grub segfault fixed
- minor current updates until 2006-07-24
Please give feedback. This set should soon become our new final isos.
http://www.archlinux.org/~andyrtr/
AndyRTR
Offline
Yeah, this checks out OK. Congrats and stuff!
After selecting packages for installation the screen is dead until installation of pkgs starts -- so a "please be patient while pkgs are copied over" msg, might disuade people from losing patience. (I nearly went into a console to have a probe around!)
Grub installed perfectly on my ide drive (no complications, there!). Very nice precustomisation of menu.lst.
One very small point. On entering "/arch/setup" you have to have already pressed any key so that you are in a shell. You have used the old arch32 instructions which basicaly tells you that you don't have to drop into a shell. So just a bit of tidying there could be useful.
Thanks
Geoff
What the beep was that?
Offline
I have now completed an install on my sata hard drive. Everything is OK.
Grub installs OK (device.map does not get created and there is no problem, so long as one gets hdx right in menu.lst.)
I apologise for my earlier criticisms. the wording for dropping into a shell to run /arch/setup is OK. Likewise, you have a message warning that dependencies could take time to unravel. Don't know why I didn't spot everything properly the first time!
Also, I have used the root=/dev/sda1 recovery option and that is OK.
Looks good!
Geoff
What the beep was that?
Offline
It's out
Offline
It's out
Runs perfectly for me- thanks, good job guys
--
JSkier
Offline
Just completed Arch64 install from 0.7.2 ftp
Everything went fine and even it was only install, everything seemed more responsive than whis Arch32, really
I installed Arch64 on ext3 /dev/sda7 (with swap on /dev/sda11 & /tmp on /dev/sda10), and Grub on (hd0,6)as I modified main grub's menu.lst on /dev/sda3 to chainload arch64's from it.
Next I encountered errors that I believe are misconfiguration in this location --but dunno what exactly.
Here's the point :
When I rebooted I had to edit Grub's arch64 line, adding (hd0,6) before kernel & initrd lines (even if 'root (hd0,6)' is allready present on top). Otherwise Grub autocompletion would show me /dev/sda3 (/boot) files ?? :shock:
At this point I saw that initrd26(-full) images where presents, but no kernel26 images. Even if I went through mkinicpio.conf configuration during installation (looked at it without edititing).
As kernel (hd0,6)/boot/initrd26.img didn't work either, I rebooted into existing arch32 and wanted to chroot into arch64 in order to revue & build mkinitcpio, but I couldn't go complete that as chroot prints
chroot: ne peut exéuter la commande `/bin/bash': Erreur de format pour exec()
Does someone see where I misconfigured something with this basic report ?
Should I better go with formating arch64 partition & go for a new install ?
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
Got it:)
I somehow installed arch64-0.7.2 on top of former beta version
LOL I thought the root partition would be formatted when I selected it, but that didn't happend and there was quite a mess in there : some conf files where updated, others (like rc.conf & fstab) wheren't.
Back in arch32 I formated sda7 & restarted installation. And that time cfdisk & mkinitcpio run. BTW they didn't run / print any message on 1st try.
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
Here we go again: http://archlinux.org/~andyrtr/newisos/
The new ISOs contain all updates until today. Kernel is 2.6.18.2 that brings important new drivers and solves some bugs. It allows me now to install on my new Core2Duo notebook.
Have fun!
AndyRTR
Offline
Great
May I suggest some more "speaking" names for the files ?
There's no "Arch" in them, and since they might be lost in some partitition full of files and ISOs as well as distributed with BT, it'd be usefull if one can recognize them at a glance without searching for a while
EDIT : same thing for tpowa's i686 kind-of-0.7.3 ISOs,
Imagine if every distro would name their files "base.iso", "ftp.iso", "md5sum.txt" & "readme.txt" :shock:
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
Someone may want to help seeding new ISOs on http://www.linuxtracker.org (with some others like mininova & fenopy)
They're unmodified (but their name :
arch64-0.7.2-20061106-x86_64-base.iso
arch64-0.7.2-20061106-x86_64-base.iso.torrent
arch64-0.7.2-20061106-x86_64-ftp.iso
arch64-0.7.2-20061106-x86_64-ftp.iso.torrent)
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline