Results 1 to 10 of 12

Thread: G4 Kernel Upgrade (will not boot new kernel)

Hybrid View

  1. #1
    Join Date
    Sep 2007
    Location
    Milwaukee, WI
    Beans
    268
    Distro
    Ubuntu Development Release

    G4 Kernel Upgrade (will not boot new kernel)

    Alright,
    I'm trying to get my G4 off of OS X for its primary OS. I have a working Debian install on a 40 GB IDE drive (kernel is custom 2.6.26). I am trying to update the kernel to 2.6.39.1, but I cannot get the new kernel to boot.

    I'm sure I should post this elsewhere, but I've had good luck here with fellow PPC Mac users before.

    Anyway, when I point yaboot to my new kernel, it prints out about two lines (the usual "Elf32...." blah blah blah), then flashes to a white screen that looks like open firmware. The only thing this screen says is:

    Code:
    done
    found display     : /pci@f000000/NVDA,Parent@10/NVDA,Display-A@0, opening...
    And that's it. System hangs from there...

    I'm not sure what to make of it. I feel like the nvidiafb should take over, and I've got it compiled in the kernel as a module (just like the working 2.6.26 kernel on this machine), but nothing happens. I've never seen the white open firmware screen outside of..well, open firmware.

    I can post any files necessary...until then I'll just keep fiddling with the kernel configuration, rebuilding and trying it out.

  2. #2
    Join Date
    Jan 2008
    Location
    Netherlands
    Beans
    2,930
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: G4 Kernel Upgrade (will not boot new kernel)

    chroot into your sytem and check the symbolic links in /boot
    and check them against yaboot.conf. Also don't forget to issue a ybin -v whenever you change the yaboot.conf file. Make sure your open firmware path to your device is correct as well.

    http://mac.linux.be/content/yaboot
    Linux on your Apple Mac │ iLinux
    http://mac.linux.be
    http://www.mintppc.org

  3. #3
    Join Date
    Sep 2007
    Location
    Milwaukee, WI
    Beans
    268
    Distro
    Ubuntu Development Release

    Re: G4 Kernel Upgrade (will not boot new kernel)

    I issued ybin -v when I first built the kernel and put it in /boot. Each time I rebuild though, I've been renaming it to the same thing, so yaboot doesn't really need to be updated, right?

    As for the open firmware path, the hard drive will boot using the old (2.6.26) kernel, so I assume everything is fine with the OF path.

    What do you mean by checking the sym links?

  4. #4
    Join Date
    Jan 2008
    Location
    Netherlands
    Beans
    2,930
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: G4 Kernel Upgrade (will not boot new kernel)

    the entries you have should link to the right kernel, so vmlinux should be linked to your new kernel image if that is the default one for example, I hope you understand what I mean.
    Linux on your Apple Mac │ iLinux
    http://mac.linux.be
    http://www.mintppc.org

  5. #5
    Join Date
    Sep 2007
    Location
    Milwaukee, WI
    Beans
    268
    Distro
    Ubuntu Development Release

    Re: G4 Kernel Upgrade (will not boot new kernel)

    I used the method described here for compiling/installing the kernel. I've never gotten the "make install" command to work for me, so I just copied vmlinux and initrd (appended with version info to differentiate from the other vmlinux/initrd) over to /boot and then I added an entry in yaboot.conf that points to them.

    Is there more I have to do? I don't remember doing anything with links last time around (this is the first time booting this machine to linux in over a year...I'm a bit rusty).

  6. #6
    Join Date
    Jan 2008
    Location
    Netherlands
    Beans
    2,930
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: G4 Kernel Upgrade (will not boot new kernel)

    It looks like you did the right thing.
    Linux on your Apple Mac │ iLinux
    http://mac.linux.be
    http://www.mintppc.org

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •