You are not logged in.
Pages: 1
I saw the 0.5 beta ISO available for download, so I gave it a shot. I tried the CD-Rom installation on a standard Dell desktop. Everything appeared to go well until after the packages installed. Then it failed to install the kernel. It looked like the CD had been unmounted after the packages installed, so I manually mounted it and installed the kernel, then completed the installation. Lilo failed to install on the boot partition. I guess I jumped the gun a little with 0.5.
What lies before us, and what lies behind us are tiny matters compared to what lies within us. RW Emerson.
Offline
Yea, you snuck in there before we were ready for you.
The updated iso should work just fine for you. Sorry you wasted a download.
Offline
Grrr, I wasted ten bucks for an 3 hour download and a double espresso in an internet cafe for this download. Curse you!
Is that the only thing fixed in the updated ISO? If it is I can merely assume that it works well when documenting the process and not waste the money and time again.
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
Thanks for the quick update.
Having discovered Arch a couple of months ago, I have really come to like it a lot. Kudos to all the people making it happen, and keeping it alive. So far I have replaced both Gentoo and Redhat installations with Arch, and never regretted it for an instant.
IMHO the only weakness is with the installation. The setup script works (usually), and obviously has taken a lot of time and effort, which I appreciate. But it's prone to error, and requires more technical knowledge than some other distributions. Doesn't bother me, but may be enough to deter others.
A recurring problem with the Arch installs is the failure of Lilo to properly write the MBR, resulting in the infamous '40' displays when you try to boot. I will download the ISO again and try various installations on a couple of different machines. If I still have problems with this, I may tackle the setup script myself.
Hrose
What lies before us, and what lies behind us are tiny matters compared to what lies within us. RW Emerson.
Offline
I've found that the L40 errors are fixed with the 'lba32' line in lilo.conf. It's in the default lilo.conf now, but wasn't before.
Offline
And if lba32 alone doesnt help, you should try telling LILO more about the BIOS mapping of the boot drive with the disk anb bios options, ie.
boot=/dev/discs/disc0/disc
disk=/dev/discs/disc0/disc bios=0x80
[...]
I needed that a few times to get it to correctly map a SCSI boot drive and even for some old IDE drives.
Yes, this is included in the docs now.
Greets,
Dennis
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
The bios option seems to have fixed it.
lba32 had no effect either way.
What lies before us, and what lies behind us are tiny matters compared to what lies within us. RW Emerson.
Offline
Heh, I'm so totally sick of LILO and the installer by now.. I've installed 0.4 and 0.5 like.. what.. a flooglepopillion times or something, with all kinds of weird SCSI and IDE mixtures to find out where potential problems lie that need to be written down somewhere. And all I could really write down was "Wow, that's too complex, you're on your own!". Somehow frustrating.
Greets,
Dennis
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
FYI, 0.5 will have support for both grub and lilo, with grub now being default.
Offline
hum grub default ? ho well guess im using the 0.4 iso forever
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GU/ d- s: a- C L U P+ L+++ E--- W+
N 0+ K- W-- !O !M V-- PS+ PE- V++ PGP T 5 Z+ R* TV+ B+
DI-- D- G-- e-- h! r++ z+ z*
------END GEEK CODE BLOCK------
Offline
but it supports both!!! (well it sounds like it) lol
Hapy.
Offline
downloaded, checked iso, burnt, checked CD. all ok
attempted an install.
pacman does not install anything, that means no bash, no make = no kernel compile.
dead in the water here.
read all arch docs online.
any ideas?
PS I swear by grub and swear at lilo
Off to using Peanut and Slackware, no hard feelings but I need my CD to burn, PDA and scanner to connect and arch won't do it.
[img]http://www.flightsimhq.org/images/war-is-bushit_s.jpg[/img]
Offline
Does this problem occur for anyone else with 0.5beta3?
galen: Can you give me any more details? Did the package selection portion work fine? What does the pacman log say after the failed install?
Offline
Any hApy's right. Both bootloaders are supported in 0.5, and the lilo L40 errors seem to be fixed in 22.5.6.1.
So everyone's happy, right? Riiiiiggghhht?
Offline
0.5b3
/etc/pacman.conf does not exist
Package selection screen is fine, can select and unselect.
Mounts, defines and builds filesystems just fine.
Off to using Peanut and Slackware, no hard feelings but I need my CD to burn, PDA and scanner to connect and arch won't do it.
[img]http://www.flightsimhq.org/images/war-is-bushit_s.jpg[/img]
Offline
Thanks, galen. With supa's help I was able to reproduce the problem. 0.5beta4 is ready with the fix.
Hopefully this will be the last beta release.
Offline
thank you,
high speed access coming today! Hope to be in the 0.5 ranks soon and go Nova instead of Postal. hehe
Off to using Peanut and Slackware, no hard feelings but I need my CD to burn, PDA and scanner to connect and arch won't do it.
[img]http://www.flightsimhq.org/images/war-is-bushit_s.jpg[/img]
Offline
Pages: 1