View Single Post
  #2   (View Single Post)  
Old 4th October 2011
jggimi's Avatar
jggimi jggimi is online now
More noise than signal
Join Date: May 2008
Location: USA
Posts: 7,414

The gyrations you have in your steps are unnecessary. Such things are normally used to mitigate the risk of loss of the GENERIC kernel in the event of an untimely cessation of the OS due to power failure or a hardware disruption during a cp(1) or mv(1). The RAMDISK kernels typically do not need this.

If you are having trouble booting the new snapshot's RAMDISK kernel, there are only three possibilities:
  1. A bad download, or a bad file at your mirror. This may be confirmed or ruled out by using the SHA256 file from another mirror with sha256(1).
  2. A bad kernel. This could be a newer function or section of code that manifests as an unbootable kernel for you. The fix is to wait for a newer snapshot to be built, and see if a newer kernel has the same problem.
  3. Some sort of problem with your hardware that becomes uncovered by a new feature of this kernel.
The least common cause is #3. You can test #1 yourself. That leaves #2.

Wait for the next snapshot. If a newer snapshot has the same problem, you can report it to the bugs@ mailing list. (The project's bug reporting system is currently offline, and is not expected to return.)

Be sure to read both and before Emailing bugs@.
Reply With Quote