[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 5.14 fails to boot early on a PowerBook



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


Reply to: