Hi Ray,

So the bootleader still seems to work fine, but Arch dies partway through bootup?

Judd;

Thanks for handling this item and the best to you with the big upgrade activity.

I have tried to upgrade many times via -Syu with no success.

I then tried to generate kernel2612-custom and boot it instead.

The results were identical, failed to reach desktop...only reach Arch0.7 wombat log-in where keyboard failed to enter single keystrokes (usb).

I then downloaded kernel26-2.6.13.2-1.tar.bz2, modified the kernel to custom install cramfs=y using ABS elements derived from wiki and previous trials (kernel-install and such, config).

I ran makepkg PKGBUILD and it generated the Kernel26132-custom.

This kernel is Udev so lilo was changed for the image root=/dev/hda3.

The result was a good install and the system is up and running. The cramfs is operating from the initial install.
I note today that cramfs is now in the PKGBUILD as =m, per tpowa for which I asked some months back but was turned away. Iceram received a good response for which I am grateful.

The upgrade problem seems not to have a solution. I have reservations about trying to upgrade to the new release from the vanilla kernel based on past experience.

I have in the past upgraded well with Syu up to and including kernel2.6.11 but all attempts to move up to 2.6.12.2-1 have failed, even from the kernel generated by arch0.7CD (automatic partitioned).

My posts have been threaded and many hours lost in fighting this problem, using Knoppix to aid in addressing the forum.

I have two kernels in pacman -Q generated as -custom which tried to permit kernel2.6.12.2 to reach desktop but neither permits the result.

I ran ABS via download with PKGBUILD generated by you, attempted -custom build (about six patches included, four I deleted, the last four listed) but the result after the build was not a custom ID.

I then performed the PKGBUILD with the wiki verbose PKGBUILD (rename) and obtained a -custom ID for 2.6.12.2 as previously stated, it is one of the two in pacman -Q.

If I attempt to utilize arch 0.7CD for repair, two approaches are possible. Use it with chroot or boot.... vmlinuz root=/dev/discs/disc0/part3.

It seems that internet access is lost in either of these approaches. In the vmlinuz case, module installs are lost..all is confusion. Entry of the usual /etc/rc.d/network start produces error..no module for etho...obviously.

I am pleased that kernel 2.6.13.2 has loaded as a -custom install but a bit chagrined that all the effort has been overcome by tpowa.

It has been months of effort!!!!

I mentioned uname -r while in chroot, it seems that is the ID of the CD kernel which I realized after reflection.

When I first upgraded from vanilla, I had 46 or so pkgs load along with the kernel. Which of these caused the difficulty, if it were another) I haven't a clue!

The first encounter with the problem was not from the vanilla but from a later upgrade. Now it also occurs with a new install in vanilla format.

I have made a big comment..I hope it is understandable and I appreciate your response.