Clean install on iMac 2006 leads to Kernel panic (error in init line 225)

Forum › Forums › Orphaned Posts › antiX-17 “Heather Heyer, Helen Keller” › Clean install on iMac 2006 leads to Kernel panic (error in init line 225)

  • This topic has 6 replies, 3 voices, and was last updated Jan 3-8:14 am by ohh.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • January 1, 2019 at 5:19 pm #14945
    Member
    Thomas Ganter

      Hello world & a Happy New Year!

      I spent most of today trying to install antix 17.3.1 on a white Intel Core Duo iMac (2006). I tried base and full images, and 386 and x64 flavours.

      Each time I can boot from the live CD after some GRUB2 command line tinkering (the Mac won’t boot off the thumb drive without) manually setting the linux / initrd paths.

      After installing antiX from the live system however, I never (!) get beyond the Kernel Panic approx 6.6 seconds into booting.

      See Screenshot attached.

      I posted the same also to the antiX Bugtracker (Link to Bugtracker).

      Greetings,
      –Thomas

      Attachments:
      1. antix-Kernel-Panic-Screenshots-reduced.pdf
      January 2, 2019 at 6:00 am #14950
      Member
      ohh
        Helpful
        Up
        0
        ::

        I have a 2007 imac that I use for my main desktop, running antiX 17.3 the problem with the booting is best explained by:

        https://mattgadient.com/2016/07/11/linux-dvd-images-and-how-to-for-32-bit-efi-macs-late-2006-models/

        I have used the .isomacprog on several ditros that would not boot on my imac, but after conversion they all
        booted fine.

        cheers,
        ohh

        Every matter requires prior knowledge.

        - Du Mu
        The Art of War

        January 2, 2019 at 9:19 am #14959
        Member
        delix02
          Helpful
          Up
          0
          ::

          Most likely you must modify the GRUB2 files after the installation again.
          Boot your life system, mount the hard disk of the Mac and check and modify the entries in /boot/grub and /etc/grub.d

          It’s often a good idea to use the UUID of the hard disk instead the /dev/sd??

          • This reply was modified 4 years, 4 months ago by delix02.
          January 2, 2019 at 10:45 am #14962
          Member
          Thomas Ganter
            Helpful
            Up
            0
            ::

            Hi ohh,

            thanks, but just for clarification:
            My problem is not booting the live CD.
            That I already could do.

            Modifying the ISO with the tool mentioned on the site did not yield a different result (would not boot automatically of the USB, and after installation the Mac did enter Kernel Panic with the same symptoms as in the Screenshots).

            But merci a lot for the effort.
            Any other hints I could persue?

            –Thomas

            January 2, 2019 at 11:07 am #14964
            Member
            Thomas Ganter
              Helpful
              Up
              0
              ::
              delix02 wrote:

              Most likely you must modify the GRUB2 files after the installation again.
              Boot your life system, mount the hard disk of the Mac and check and modify the entries in /boot/grub and /etc/grub.d

              Hi delix02,

              exactly which of the entries would you recommend modifying?
              I may be a novice, but it very much looks to me the initial ram disk seems to have the problem, as the error seems to happen prior to activation of the root file system. But then again, I might be mistaken …

              [… some searching, find’ing, less’ing, grep’ing, sudo’ing and vi’ing later …]

              OK, made it.
              I found the mysterious line 225 which tried to run a /scripts/boot script not existing in the initramfs-init script in /usr/share. Understanding the comments therein and changing boot=boot into boot=local in the grub.cfg file solveds it (for now).

              Thanks for the hint!

              Now the question is, is this a problem in the initial install, in the installer script, or merely bad luck?

              Greetings,
              –Thomas

              January 2, 2019 at 11:16 am #14966
              Member
              delix02
                Helpful
                Up
                0
                ::

                Congrats !
                Guess it is a matter of your specific constellation.

                • This reply was modified 4 years, 4 months ago by delix02.
                January 3, 2019 at 8:14 am #14987
                Member
                ohh
                  Helpful
                  Up
                  0
                  ::

                  Thomas,

                  Did you see:

                  https://antixlinux.com/serious-bug-installing-antix-17-3-full-and-base-versions/

                  cheers,
                  ohh

                  Every matter requires prior knowledge.

                  - Du Mu
                  The Art of War

                • Author
                  Posts
                Viewing 7 posts - 1 through 7 (of 7 total)
                • You must be logged in to reply to this topic.