You are not logged in.
hm... good. but:
I think installer must create fstab and grub/menu.lst using persistent device naming. it's solve many problem during kernel upgrade.
Offline
zeus, persistent naming has other disadvantages so "must" is the wrong term, the new iso uses correct module loading to ensure persistent names.
Offline
Somehow the hdd got fsck'ed after first boot saying something about a timestamp in the future and that /dev/sdaX was not checked for about 43000 days. After that, the system rebooted automatically and doing the same on the next boot, but the third boot was clean then... Beside this, the installation worked flawless...
Confirmed. I had exactly the same experience on a .8 install this afternoon. The message was to the effect that the disk had not been checked in 4300 days (not, if I recall correctly, 43000) with .1 per cent non-contiguous on hda3 and 6.5 per cent on hda1. This happened twice, with a future time stamp the second time and a unilateral reboot, but there was no issue on the third boot. This is on a computer on which .8 has been installed a couple of times without this happening. The difference this time, which may or may not be relevant, is that it happened after a pacman/package upgrade.
If the developers are interested, I could go into the logs to see if the precise messages are there.
Offline
funkyou wrote:Somehow the hdd got fsck'ed after first boot saying something about a timestamp in the future and that /dev/sdaX was not checked for about 43000 days. After that, the system rebooted automatically and doing the same on the next boot, but the third boot was clean then... Beside this, the installation worked flawless...
Confirmed. I had exactly the same experience on a .8 install this afternoon. The message was to the effect that the disk had not been checked in 4300 days (not, if I recall correctly, 43000) with .1 per cent non-contiguous on hda3 and 6.5 per cent on hda1. This happened twice, with a future time stamp the second time and a unilateral reboot, but there was no issue on the third boot. This is on a computer on which .8 has been installed a couple of times without this happening. The difference this time, which may or may not be relevant, is that it happened after a pacman/package upgrade.
If the developers are interested, I could go into the logs to see if the precise messages are there.
Fresh install here, on a virgin notebook which came with windows xp preinstalled. I can also search and post my logs if someone is interested.
want a modular and tweaked KDE for arch? try kdemod
Offline
I think installer must create fstab and grub/menu.lst using persistent device naming. it's solve many problem during kernel upgrade.
to live is to die
Offline
zeus, persistent naming has other disadvantages so "must" is the wrong term, the new iso uses correct module loading to ensure persistent names.
What kind of problems? I use fs labels everywhere (fstab, grub menu.lst), for swap and data partitions, and all is great.
There was a minor problem when resumeing from hibernation (I use my own suspend2 patched kernel), when the initramfs wouldn't recognize the swap partition (the suspend process whould change the magic label), but brain0 solved that with a small patch to vol_id.
ps. brain0 did you send that patch upstream?
Offline
I am encountering VERY sparse udev segfaults (maybe one time every twenty-five boots, or less), which do not appear after resetting the machine.
I'm using custom 2.6.19-1, which is identical to official but with the r1000 patch omitted (with that patch included hal strangles my 8168 network interface down to unacceptable speeds when loaded).
Microshaft delenda est
Offline
Hello,
after latest pacman -Syu and new kernel my system cannot boot any longer, it stucks 1-2 seconds after lilo screen :cry:
Offline
Hello,
after latest pacman -Syu and new kernel my system cannot boot any longer, it stucks 1-2 seconds after lilo screen :cry:
What are 2-3 last lines you see before it stucks?
to live is to die
Offline
123456789 wrote:Hello,
after latest pacman -Syu and new kernel my system cannot boot any longer, it stucks 1-2 seconds after lilo screen :cry:What are 2-3 last lines you see before it stucks?
loading arch ................................ .................
That's it, after that death!
Offline
you installed 0.8a2 and then did a pacman -Syu
or you had 0.7.2 and did a pacman -Syu?
I don't use lilo, but with the new 0.8a2 installation cd I had no problems
with my 0.7.2 installation once kernel 2.6.19 made its presence I had a few problems until I fixed my menu.lst in grub
Offline
loading arch ................................ .................
That's it, after that death!
Are you sure you didn't forget to run lilo after upgrade?
to live is to die
Offline
123456789 wrote:loading arch ................................ .................
That's it, after that death!
Are you sure you didn't forget to run lilo after upgrade?
I didn't, but why should i at that case?
Offline
Romashka wrote:Are you sure you didn't forget to run lilo after upgrade?
I didn't, but why should i at that case?
You must run lilo after kernel upgrade.
I also think you didn't read pacman's output carefully.
Now you have to rescue a system with a broken boot loader.
to live is to die
Offline
123456789 wrote:Romashka wrote:Are you sure you didn't forget to run lilo after upgrade?
I didn't, but why should i at that case?
You must run lilo after kernel upgrade.
I also think you didn't read pacman's output carefully.Now you have to rescue a system with a broken boot loader.
Hi Romashka, thanx for your prompt reply.
Actually, before kernel 2.6.18 lilo was automatically executed.
I've used above URL quite often it's quite usefull!
Offline
Hi Romashka, thanx for your prompt reply.
Actually, before kernel 2.6.18 lilo was automatically executed.
AFAIK this is not true. Lilo was never executed automatically.
Anyway, 123456789, we flooded entire page here, let stop this.
to live is to die
Offline
123456789 wrote:Hi Romashka, thanx for your prompt reply.
Actually, before kernel 2.6.18 lilo was automatically executed.AFAIK this is not true. Lilo was never executed automatically.
Partially i agree to what you say.
However, after lots of kernel uogrades i had never executed lilo, although the output of pacman has always encouraged me to do so!
I omitted the execution of lilo once or twice for testing purposes and after i realized everything was OK i continued to do so, until the latest kernel upgrade (probably) caused that "malfunction".
Offline
0.8 installation worked beautifully (especially hwd)
Offline
launched new ISO's should show up soon
ftp://ftp.archlinux.org/other/0.8/i686/
base-0.8-20070115-i686.iso current-0.8-20070115-i686.iso ftp-0.8-20070115-i686.iso
everything mentioned here should be fixed:
http://bugs.archlinux.org/task/6031
have fun thanks for testing
try to break it
greetings
tpowa
Offline
ftp://ftp.archlinux.org/other/0.8/x86_64/ images are also done now. give the mirrors some time to sync.
Offline
oups! then in this post: http://bbs.archlinux.org/viewtopic.php?p=221882#221882
i should have said 0.8a1.1 forgive me
downloading it now!
and I thought we wouldn't have another alpha/beta until pacman3... hehehe, new stuff to play with
thanks everybody
Offline
awesome stuff i'm trying the i686 base iso
current-0.8-20070115-i686.iso
but it says packages attr and acl can't be found. i checked in /src/arch.. and they're not there. thx
Offline
Same here. On an Ide-legacy install, "Install packages" failed with the message that there was a failure to retrieve attr and acl.
Offline
Hi
sorry for the broken aplha2 yesterday, acl and attr needed to be in base for successfull installs, should be fixed now
try to break alpha3 now, thanks
ISOs are on the way to the mirrors so please be patient until they are synced.
ftp://ftp.archlinux.org/other/0.8/i686/
ftp://ftp.archlinux.org/other/0.8/x86_64
everything mentioned here should be fixed:
http://bugs.archlinux.org/task/6031
greetings
tpowa
Offline
lol
we forgive you
downloading the Alpha3 now (and trying to find an empty cd or something...)
Offline