1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.POWERP

  • 5.14 fails to boot early on a PowerBook

    From Riccardo Mottola@21:1/5 to All on Mon Sep 27 23:50:02 2021
    Hi,

    I upgraded the kernel only PowerBook G4 (late model) and it doesn't
    boot. Quickly after exiting OF:

    root: recovering journal
    root: clean, 373541/5865472 files, 5215323/23437500 blocks

    and stays there forever.

    If I take the old 5.10 kernel it still boots. No "Recovering journal"
    message is issued. The "root: clean" is issued a little later - but it
    boots!

    Anybody tried 5.14 on PowerBooks? I will wait before upgrading my iBook
    too then.

    Riccardo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kristofferfin@tuta.io@21:1/5 to All on Tue Sep 28 01:00:01 2021
    The problem only occurs on the G4 (mini and mdd) at least in my case.

    Terv,
    Kristoffer--
    Wiadomość wysłana za pomocą serwisu Tutanota, oferującego bezpieczną i wolną od reklam usługę e-mail:
    https://tutanota.com

    <html>
    <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div><br></div><div>The problem only occurs on the G4 (mini and mdd) at least in my case.<br></div><div dir="auto"><br></div><div dir="auto">Terv,<br></div><div dir="auto">Kristoffer</div><div>-- <br></div><div> Wiadomość wysłana za pomocą serwisu
    Tutanota, oferującego&nbsp;bezpieczną i wolną od reklam usługę e-mail: <br></div><div> https://tutanota.com<br></div> </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stan Johnson@21:1/5 to Riccardo Mottola on Tue Sep 28 02:00:01 2021
    Hello,

    On 9/27/21 3:48 PM, Riccardo Mottola wrote:
    Hi,

    I upgraded the kernel only PowerBook G4 (late model) and it doesn't
    boot. Quickly after exiting OF:

    root: recovering journal
    root: clean, 373541/5865472 files, 5215323/23437500 blocks

    and stays there forever.

    If I take the old 5.10 kernel it still boots. No "Recovering journal"
    message is issued. The "root: clean" is issued a little later - but it
    boots!

    Anybody tried 5.14 on PowerBooks? I will wait before upgrading my
    iBook too then.

    Riccardo


    Have you tried the latest 5.14.8 kernel from www.kernel.org?

    Which G4 PowerBook are using?

    The "recovering journal" message could be a correction from a previous
    failed boot. Are you able to access the system over a network when the
    screen hangs?  If yes, does "dmesg" report anything interesting? Have
    you tried "video=ofonly" on the kernel command line in case there's a
    problem with the video driver? Can you send a link to the ".config" file
    that you used to compile the kernel (or send it as an attachment)?

    -Stan

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Paul Adrian Glaubitz@21:1/5 to Riccardo Mottola on Tue Sep 28 09:20:02 2021
    Hello!

    On 9/27/21 23:48, Riccardo Mottola wrote:
    I upgraded the kernel only PowerBook G4 (late model) and it doesn't boot. Quickly after exiting OF:

    root: recovering journal
    root: clean, 373541/5865472 files, 5215323/23437500 blocks

    and stays there forever.

    I don't have access to my Powerbook G4 at the moment as I'm not at home.

    Please bisect the kernel yourself or anyone else.

    Thanks,
    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Riccardo Mottola@21:1/5 to Stan Johnson on Wed Oct 6 01:10:01 2021
    Hi Stan,


    On 28/09/2021 01:49, Stan Johnson wrote:
    Which G4 PowerBook are using?


    To my knowledge it is one of the absolutely latest PowerBook models,
    with USB keyboard (lots of issues!).


    multix@Auryn:~$ cat /proc/cpuinfo
    processor       : 0
    cpu             : 7447A, altivec supported clock           : 1666.666000MHz
    revision        : 1.2 (pvr 8003 0102)
    bogomips        : 73.72

    timebase        : 18432000
    platform        : PowerMac
    model           : PowerBook5,7
    machine         : PowerBook5,7
    motherboard     : PowerBook5,7 MacRISC3 Power Macintosh
    detected as     : 287 (PowerBook G4 17")
    pmac flags      : 0000001a
    L2 cache        : 512K unified
    pmac-generation : NewWorld
    Memory          : 2048 MB


    To my knowledge this is the swan chant of G4 and Apple Laptops.


    The "recovering journal" message could be a correction from a previous
    failed boot. Are you able to access the system over a network when the
    screen hangs?  If yes, does "dmesg" report anything interesting? Have
    you tried "video=ofonly" on the kernel command line in case there's a
    problem with the video driver? Can you send a link to the ".config" file
    that you used to compile the kernel (or send it as an attachment)?


    I tried video=ofonly, but got no improvement

    However, I just updated and I see there is a minor update revision of
    the kernel and this has a long lag, doesn't show many messages on screen
    except an error, but it boots  5.14.0-2-powerpc

    The error I see (which could be where the older kernel was hanging) is
    the error I find in dmesg below:

    Some errors about ROM locations... I guess OF has no BIOS.

    [   18.922123] [drm] radeon kernel modesetting enabled.
    [   18.922229] checking generic (b8008000 151800) vs hw (b8000000 8000000) [   18.922240] fb0: switching to radeondrmfb from OFfb ATY,Jasper
    [   18.923193] Console: switching to colour dummy device 80x25
    [   18.923237] checking generic (bc008000 5a000) vs hw (b8000000 8000000) [   18.923242] fb1: switching to radeondrmfb from OFfb ATY,Jasper
    [   18.924123] radeon 0000:00:10.0: vgaarb: deactivate vga console
    [   18.924284] radeon 0000:00:10.0: enabling device (0006 -> 0007)
    [   18.925319] [drm] initializing kernel modesetting (RV350
    0x1002:0x4E50 0x1002:0x4E50 0x00).
    [   18.925334] [drm] Forcing AGP to PCI mode
    [   18.925388] radeon 0000:00:10.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x8080
    [   18.925409] radeon 0000:00:10.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x8080
    [   18.925416] [drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a
    BIOS ROM
    [   18.925928] [drm] Using device-tree clock info
    [   18.925934] [drm] Generation 2 PCI interface, using max accessible memory [   18.925940] radeon 0000:00:10.0: VRAM: 128M 0x00000000B8000000 - 0x00000000BFFFFFFF (128M used)
    [   18.925947] radeon 0000:00:10.0: GTT: 512M 0x0000000098000000 - 0x00000000B7FFFFFF
    [   18.925984] [drm] Detected VRAM RAM=128M, BAR=128M
    [   18.925990] [drm] RAM width 128bits DDR
    [   18.926093] [drm] radeon: 128M of VRAM memory ready
    [   18.926102] [drm] radeon: 512M of GTT memory ready.
    [   18.926132] [drm] GART: num cpu pages 131072, num gpu pages 131072
    [   18.930268] [drm] radeon: 1 quad pipes, 1 Z pipes initialized
    [   18.930299] [drm] PCI GART of 512M enabled (table at 0x0000000003300000). [   18.930399] radeon 0000:00:10.0: WB enabled
    [   18.930410] radeon 0000:00:10.0: fence driver on ring 0 use gpu addr 0x0000000098000000
    [   18.930783] [drm] radeon: irq initialized.
    [   18.930819] [drm] Loading R300 Microcode

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)