You are not logged in.
Yes, I only installed "base". ...
Just tested the i686-core image.
No Problems.
Offline
now that the new kernel is out, shouldn't the new iso be officially released?
Offline
Patience, grasshopper
you can always try the RC and pacman -Syu
Offline
i know, but since things have changed, ie. rc.conf and I still am a linux n00b, its easyer to wait,
especially since I am patient
I'm just wondering if something is happening or not..
Offline
I think 'soon' is the closest answer you're gonna get. Just don't ask how long 'soon' is.
Some devs choose not to set firm dates so that if the situation arises that they cannot meet this deadline (as happens alot due to various reasons) they don't get loads of crap from demanding people. Keeps it simpler, though of course if you do this then about a third of all ISO announcement threads are filled with people asking when the next ISO is going to be released (followed every so often by a post from me complaining about such posts). well, guess there just ain't a winning situation here
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
I just downloaded the latest RC ISO and attempted to boot with the Boot ArchLive. It started to boot, then I ended up with a kernel panic. The error message mentioned something about 'Lost CPU context'. This is on a Core 2 Quad Core Q6600 box.
Offline
I think 'soon' is the closest answer you're gonna get. Just don't ask how long 'soon' is.
Some devs choose not to set firm dates so that if the situation arises that they cannot meet this deadline (as happens alot due to various reasons) they don't get loads of crap from demanding people. Keeps it simpler, though of course if you do this then about a third of all ISO announcement threads are filled with people asking when the next ISO is going to be released (followed every so often by a post from me complaining about such posts). well, guess there just ain't a winning situation here
That's pretty much correct. I've got a neat idea though, let's set the bar low and then impress everyone by doing it way ahead of schedule. Sooooo... an approximate date for the next release should be May 2010.
The suggestion box only accepts patches.
Offline
dyscoria wrote:I think 'soon' is the closest answer you're gonna get. Just don't ask how long 'soon' is.
Some devs choose not to set firm dates so that if the situation arises that they cannot meet this deadline (as happens alot due to various reasons) they don't get loads of crap from demanding people. Keeps it simpler, though of course if you do this then about a third of all ISO announcement threads are filled with people asking when the next ISO is going to be released (followed every so often by a post from me complaining about such posts). well, guess there just ain't a winning situation here
That's pretty much correct. I've got a neat idea though, let's set the bar low and then impress everyone by doing it way ahead of schedule. Sooooo... an approximate date for the next release should be May 2010.
maybe it's too optimistic
edit: mispelling (in 4 words)
Last edited by _Marco_ (2008-05-31 21:37:54)
Offline
Just don't announce your releases with soon™, this is already reserved by aMule...;)
(Seriously, we will actually release 2.2.1 soon™.)
Offline
I just downloaded the latest RC ISO and attempted to boot with the Boot ArchLive. It started to boot, then I ended up with a kernel panic. The error message mentioned something about 'Lost CPU context'. This is on a Core 2 Quad Core Q6600 box.
2008.04-RC installed fine on my Q6600 box on the 16th of May, only tricky part for me was noting which partitions had what uuids as I used a seperate boot partition for /boot(ext2), /var(reiserfs), / (jfs)and several more for specific storage with their own labels(all jfs), it took me two installation attempts, chose the wrong partition for root(during grub installation) on the first one, so I took notes on the second attempt, rofl
Offline
Endperform wrote:I just downloaded the latest RC ISO and attempted to boot with the Boot ArchLive. It started to boot, then I ended up with a kernel panic. The error message mentioned something about 'Lost CPU context'. This is on a Core 2 Quad Core Q6600 box.
2008.04-RC installed fine on my Q6600 box on the 16th of May, only tricky part for me was noting which partitions had what uuids as I used a seperate boot partition for /boot(ext2), /var(reiserfs), / (jfs)and several more for specific storage with their own labels(all jfs), it took me two installation attempts, chose the wrong partition for root(during grub installation) on the first one, so I took notes on the second attempt, rofl
Maybe I got a bad burn or something. I'm redownloading and reburning now... Hopefully that will solve it.
Offline
Ok, it helps if I fully read the error message. It still panics, but only because it can't find the CDROM... not sure what to do. Part of me thinks I should just use the older installer and see if that helps.
Offline
A kind of offtopic, but the latest RC ISO that I had with me helped me few days ago to boot an unbootable Windows installation with admin password forgotten (so I can't use the repair console - another admin-level user was used, the MBR was taken away by grub, and linux partitions were just reformatted from windows - reckless).
That is to say - there are other useful features in it, besides the ability to install Arch.
Space invaders are nice too
If everything else fails, read the manual.
Offline
I have downloaded from a different mirror the latest .img file I could find. the md5sum's checked out just fine. I proceeded to put the image onto my usb key using Neotuli's method and then booted it on my test computer. The results, thus far, are exactly the same as what I encountered previously with the same image file I had downloaded last week from a different mirror. Below are the resulting errors when I went to install the packages:
Resolving dependencies.... Warning: Dependency cycle detected Warning: bash will be installed before its glibc dependency Warning: db will be installed before its coreutils dependency Error:: failed to commit (corrupted package) Error: md5:/var/cache/pacman/gcc-libs-4.3.0-1-i686 Error: md5:/var/cache/pacman/gcc-4.3.0-1-i686 Can't get md5 checksum for gcc-libs-4.3.0-1 ... can't get checksum for gcc-4.3.0-1
I kept the logs from the aborted installation in case anyone could make use of them. I hope this helps debug the issue.
I can second MoonSwan's problem. Tried to install arch-ftp-install-2008.04-rc-i686.img from USB drive, failed on the same account. Cycle dependency plus corrupt gcc-libs and gcc. When I tried to look at the files "by hand" in a virtual terminal, I got an i/o error. I would have thought my usb-drive is broken if MoonSwan hadn't had the same problem on the very same files. Md5 was fine, as in his case. dd worked without a warning. Booting went perfectly.
Had to do an FTP-install instead, but if I was more adept at Linux/Arch, I'd have tried to fix this problem rather than just cry about it.
Offline
Somethings I had problems with on the new images as the compared to the "Don't Panic" Release was hal wasn't mounting my floppy even when I identified it right in fstab. Also I tryed to install catalyst and I couldn't so I tryed pacman -Syu because catalyst required most of those updates but it still wouldn't install. Some things with the Don't Panic release were right on and I was able to do everything until I tryed to do a reinstall back in Febuary. Then things got confusing and somewhat difficult.
Offline
MoonSwan wrote:I have downloaded from a different mirror the latest .img file I could find. the md5sum's checked out just fine. I proceeded to put the image onto my usb key using Neotuli's method and then booted it on my test computer. The results, thus far, are exactly the same as what I encountered previously with the same image file I had downloaded last week from a different mirror. Below are the resulting errors when I went to install the packages:
Resolving dependencies.... Warning: Dependency cycle detected Warning: bash will be installed before its glibc dependency Warning: db will be installed before its coreutils dependency Error:: failed to commit (corrupted package) Error: md5:/var/cache/pacman/gcc-libs-4.3.0-1-i686 Error: md5:/var/cache/pacman/gcc-4.3.0-1-i686 Can't get md5 checksum for gcc-libs-4.3.0-1 ... can't get checksum for gcc-4.3.0-1
I kept the logs from the aborted installation in case anyone could make use of them. I hope this helps debug the issue.
I can second MoonSwan's problem. Tried to install arch-ftp-install-2008.04-rc-i686.img from USB drive, failed on the same account. Cycle dependency plus corrupt gcc-libs and gcc. When I tried to look at the files "by hand" in a virtual terminal, I got an i/o error. I would have thought my usb-drive is broken if MoonSwan hadn't had the same problem on the very same files. Md5 was fine, as in his case. dd worked without a warning. Booting went perfectly.
Had to do an FTP-install instead, but if I was more adept at Linux/Arch, I'd have tried to fix this problem rather than just cry about it.
Exactly same problem here... with usb key (I also checked the md5sum of the iso, it was ok).
I guess I will have to go with FTP install... argh I have to configure my Wifi !!!!
Offline
Please file a bug report with details.
Offline
Yeah I will do that but I don't have much details except what MoonSwan reported !
FTP install went well though ! It's really weird that this problem seems to concern only people with usb keys !!!
Offline
Yeah I will do that but I don't have much details except what MoonSwan reported !
FTP install went well though ! It's really weird that this problem seems to concern only people with usb keys !!!
Provide all details listed in the 3 agreeing accounts and a link to the posts.
Offline
Had to reinstall Arch Linux today (circumstances not important, wasn't because I had b0rken my box) and went for the i686 2008.04-RC `ftp install` CD. No problems [Intel Pentium Dual Core T2060 ; ATI Radeon Mobility X1400; Broadcom BCM4401-B0 (wired) + Broadcom BCM94311MCG (wireless) <- as reported by `lspci`.] except for:
#1. Not sure I'm too thrilled about UUID
#2. How the heck to you exit Space Invaders !?
Offline
#1: Don't like UUID's in your fstab, change it. no biggie.
#2: You don't xD
[home page] -- [code / configs]
"Once you go Arch, you must remain there for life or else Allan will track you down and break you."
-- Bregol
Offline
Another point which is a little bit disappointing is that, after logging as root on archlive, pacman does not work since it tries to sync with internet repositories. In my case I had to install some packages to setup my wifi (no ethernet connection) and I was unable to do that. How to you tell pacman to sync with CD/usb key repository ?
It is weird because I swear that I could install everything yesterday without an internet connection but maybe it's because I launched the setup script and I used pacman after trying to install packages from the cd.
One last thing is that km is no longer installed and nothing is said in the welcome message to change keyboard layout !
Good job anyway
Offline
Why does almost nobody like the new UUID's? I was waiting for UUID's to become default in the Arch installation. For people who don't like UUID's or don't see the benefit of it: try installing Archlinux without UUID's on a box with two SATA-controllers, both having disks connected to them. At the first boot, /dev/sda may be harddisk 1 from controller 1, the second boot it may be harddisk 1 from controller 2, the third time harddisk 2 from controller 1, the fourth time something else again.... you get the point. When having multiple controllers, one can not be sure that a harddisk will have the same name in /dev after a reboot, so one needs a unique identifier for each disk. There is persistent /dev names, but it needs some work. There are also LABEL's and UUID's, which can both be assigned to a partition. UUID's are created by default on every partition (except for swap on some distro's) and are guaranteed to be unique. LABEL's can be readable names defined by yourself, to identify your partitions, for example to label a certain partition "root" and another "swap" and yet another "home".
I think it is great to use UUID's by default, because switching from UUID's to /dev-naming is easy. The other way around (that would be from /dev-naming to UUID's) is a little bit more tricky, because you need to run "blkid" to find the UUID from a partition, then you need to type it into both fstab and menu.lst (or with >> of course).
Offline
Why does almost nobody like the new UUID's?
Because almost everyone prefer appearance over functionality.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
We have a bunch of knuckleheads like Linus Torvalds hacking away at the kernel, trying to bang a boat into a swiss army knife. That's why we need UUID's.
This is not an Arch issue, and in fact, the Arch devs have been aware of this issue for ages and have been pushing users to utilize persistent device naming. It's only responsible for them to provide a default method which will assure a usable system after installation.
If you don't like or don't need UUID, you can always change your fstab.
Offline