Xorg segfaults on iMac G3 with Rage 128 Pro

[Paul Wise]

My system is up to date as of April 15, 2023; I'm running kernel
6.1.0-7-powerpc with Mesa 22.3.6. Does anyone how to fix this problem?

I think you will need to do some debugging, there are some tips here:

https://x.org/wiki/Development/Documentation/ServerDebugging/

[Ben Westover]

Hi,

Post by Paul Wise
https://x.org/wiki/Development/Documentation/ServerDebugging/

I'm probably doing something wrong (never used gdb before), but Xorg
closes almost instantly after I run it so there's not enough time to
launch gdb before it's already segfaulted. It sounds like these tips are
for when Xorg launches and runs for a bit but crashes when a specific
action is performed.

[Paul Wise]

Post by Ben Westover
I'm probably doing something wrong (never used gdb before), but Xorg
closes almost instantly after I run it so there's not enough time to
launch gdb before it's already segfaulted. It sounds like these tips are
for when Xorg launches and runs for a bit but crashes when a specific
action is performed.

There is also the case where you launch Xorg via gdb and then run it.

$ gdb `which Xorg`
(gdb) run
(gdb) bt full

Also, you will need to either install dbgsym packages beforehand
(possibly using find-dbgsym-packages from debian-goodies), or install
and enable libdebuginfod-common to let gdb auto-download debug symbols.

Apart from running Xorg in gdb directly, another method is to install
systemd-coredump, enable the Xorg Option NoTrapSignals to disable Xorg
handling its own crashes, then load the crash dump file into gdb using
`sudo coredumpctl debug`.

PS: I'm subscribed, no need to CC me.

[Luke Kenneth Casson Leighton]

Hello,

Post by Paul Wise
There is also the case where you launch Xorg via gdb and then run it.
$ gdb `which Xorg`
(gdb) run
(gdb) bt full

Perfect! I was able to get a full backtrace, which is attached. Here's
Program received signal SIGSEGV, Segmentation fault.
432 ../../src/r128_output.c: No such file or directory.
(gdb) bt full
info = 0x776ed0
bios_header = <error reading variable bios_header (Cannot

access memory at address 0x48)>

offset = <optimized out>
i = 2
void R128GetConnectorInfoFromBIOS(ScrnInfoPtr pScrn, R128OutputType

*otypes)

{
R128InfoPtr info = R128PTR(pScrn);
uint16_t bios_header, offset;
uint32_t i;
for (i = 0; i < R128_MAX_BIOS_CONNECTOR; i++) {
otypes[i] = OUTPUT_NONE;
}
/* non-x86 platform */
if (!info->VBIOS) {
otypes[0] = OUTPUT_VGA;
}
bios_header = R128_BIOS16(0x48);

almost certainly a NULL pointer from this macro

There's more after this, but it seems to crash at that last line,
failing to read the memory at 0x48 to get the BIOS' connector info.

see how 0x48 is the same there this tells us R128_BIOS16
takes a NULL address somehow.

l.

[Paul Wise]

Post by Luke Kenneth Casson Leighton

        /* non-x86 platform */
        if (!info->VBIOS) {
            otypes[0] = OUTPUT_VGA;
        }
        bios_header = R128_BIOS16(0x48);

almost certainly a NULL pointer from this macro

These are the macro definitions.

#define R128_BIOS8(v) ((info->VBIOS[(v)]))
#define R128_BIOS16(v) ((info->VBIOS[(v)]) | \
(info->VBIOS[(v) + 1] << 8))
#define R128_BIOS32(v) ((info->VBIOS[(v)]) | \
(info->VBIOS[(v) + 1] << 8) | \
(info->VBIOS[(v) + 2] << 16) | \
(info->VBIOS[(v) + 3] << 24))

Please try these gdb commands once you hit the crash point:

print info
print info.VBIOS
print info->VBIOS
print info->VBIOS[0x48]
print info->VBIOS[0x49]

[Ben Westover]

Post by Paul Wise
These are the macro definitions.
#define R128_BIOS8(v) ((info->VBIOS[(v)]))
#define R128_BIOS16(v) ((info->VBIOS[(v)]) | \
(info->VBIOS[(v) + 1] << 8))
#define R128_BIOS32(v) ((info->VBIOS[(v)]) | \
(info->VBIOS[(v) + 1] << 8) | \
(info->VBIOS[(v) + 2] << 16) | \
(info->VBIOS[(v) + 3] << 24))
print info
print info.VBIOS
print info->VBIOS
print info->VBIOS[0x48]
print info->VBIOS[0x49]

(gdb) print info
$1 = (R128InfoPtr) 0x776ed0
(gdb) print info.VBIOS
$2 = (uint8_t *) 0x0
(gdb) print info->VBIOS
$3 = (uint8_t *) 0x0
(gdb) print info->VBIOS[0x48]
Cannot access memory at address 0x48
(gdb) print info->VBIOS[0x49]
Cannot access memory at address 0x49

[Paul Wise]

Post by Ben Westover
(gdb) print info
$1 = (R128InfoPtr) 0x776ed0
(gdb) print info.VBIOS
$2 = (uint8_t *) 0x0

If you add a return statement like this, does that fix the crash?

/* non-x86 platform */
if (!info->VBIOS) {
otypes[0] = OUTPUT_VGA;
return;
}

[Ben Westover]

Hello,

Post by Paul Wise
If you add a return statement like this, does that fix the crash?
/* non-x86 platform */
if (!info->VBIOS) {
otypes[0] = OUTPUT_VGA;
return;
}

Yes, it no longer segfaults. It goes past the point where it previously
crashed, but now I have a new error:

(WW) R128(0): Static buffer allocation failed -- need at least 36864 kB video memory
(II) R128(0): Filling in EXA memory info
(II) R128(0): Setting up EXA callbacks
(II) R128(0): Initializing 2D acceleration engine...
(II) R128(0): Initializing EXA driver...
(EE) EXA(0): ExaDriverRec::offScreenBase must be <= ExaDriverRec::memorySize
(EE) R128(0): EXA Acceleration initialization failed.
(II) R128(0): Acceleration disabled.
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 0

Is this something I can fix, or does modern Xorg just need more VRAM?

Thanks,

[Paul Wise]

On Sun, 2023-05-07 at 20:20 -0400, Ben Westover wrote:
...

     (EE) AddScreen/ScreenInit failed for driver 0
Is this something I can fix, or does modern Xorg just need more VRAM?

I don't know enough about the Xorg codebase to answer this.
It would be a good idea to ask on the upstream mailing lists.
Please report back here about any results that you get though.

https://xorg.freedesktop.org/wiki/XorgMailingLists/

[John Paul Adrian Glaubitz]

Hi!

Hello,

Post by Paul Wise
If you add a return statement like this, does that fix the crash?
/* non-x86 platform */
if (!info->VBIOS) {
otypes[0] = OUTPUT_VGA;
return;
}

Yes, it no longer segfaults. It goes past the point where it previously

I didn't read through the whole thread, but if this was actually a change
to the upstream code when we don't have the latest version of the r128
driver in Debian, it should be reported upstream.

Adrian

[Luke Kenneth Casson Leighton]

Post by Ben Westover
Is this something I can fix, or does modern Xorg just need more VRAM?

try 640x480 and/or 16bpp.

l.

[Martina Hřebcová]

Hi,

after several years I want to install Debian Sid again on my Powermac G5
Quad  and AmigaOne X1000.

Please, what is the right steps for installing on Powermac G5?


1. I tried debian-11.0.0-ppc64-NETINST-1.iso from
/cdimage/ports/snapshots/2022-12-09

but there is no hfs tools and installation fail


2. I tried debian-11.0.0-ppc64-NETINST-1.iso from
/cdimage/ports/current, dated 2022-03-28

installation works ( with some issues with expired keys, which can be
solved ) but in section "configuring grub-ieee1275" it hangs:

- /target/boot/grub is mounted, hfs formated, rw, and there is some
other files, so is writable for sure

- last syslog messsages are:

 Creating config file /etc/default/grub with new version

 Installing for powerpc-ieee1275 platform


Please, first of all, what is the right last working installation .iso
for ppc64 be ?

And are there needed some additional workarounds ( like were with grub
in times of debian 10 / powerprogress.org ) ?


thanks


Martina

[John Paul Adrian Glaubitz]

Hello!

Post by Martina Hřebcová
after several years I want to install Debian Sid again on my Powermac G5
Quad  and AmigaOne X1000.
https://cdimage.debian.org/cdimage/ports/snapshots/2023-05-14/

PS: Please always post into a new thread when starting a new topic.

Adrian

[Martina Hřebcová]

Post by John Paul Adrian Glaubitz
Hello!

Post by Martina Hřebcová
after several years I want to install Debian Sid again on my Powermac G5
Quad  and AmigaOne X1000.

Many thanks! I will try al let know.

Post by John Paul Adrian Glaubitz

Post by Martina Hřebcová
https://cdimage.debian.org/cdimage/ports/snapshots/2023-05-14/

PS: Please always post into a new thread when starting a new topic.
Adrian

Martina

[Martina Hřebcová]

"Hello!

Post by Martina Hřebcová
after several years I want to install Debian Sid again on my Powermac G5
Quad  and AmigaOne X1000.
https://cdimage.debian.org/cdimage/ports/snapshots/2023-05-14/

"



Tried just now, and installation of base system ends with error:

"An error was returned while tryingto install zstd package onto the target
system."




Tested on Powermac G5 Quad core. Sysylog is in attachment.

Please, may I post it somewhere, or is ir OK this way?







 
"
PS: Please always post into a new thread when starting a new topic.

Adrian
"



Martina

[John Paul Adrian Glaubitz]

Post by Martina Hřebcová
after several years I want to install Debian Sid again on my Powermac G5
Quad and AmigaOne X1000.
https://cdimage.debian.org/cdimage/ports/snapshots/2023-05-14/

"An error was returned while tryingto install zstd package onto the target system."
Tested on Powermac G5 Quad core. Sysylog is in attachment.
Please, may I post it somewhere, or is ir OK this way?

When exactly does this problem occur? After installing the base system?

Adrian

[John Paul Adrian Glaubitz]

Hello!

Post by Martina Hřebcová
Tested on Powermac G5 Quad core. Sysylog is in attachment.
Please, may I post it somewhere, or is ir OK this way?

May 15 17:23:37 in-target: Reading package lists...
May 15 17:23:37 in-target:
May 15 17:23:37 in-target: Building dependency tree...
May 15 17:23:37 in-target:
May 15 17:23:37 in-target: Reading state information...
May 15 17:23:37 in-target:
May 15 17:23:37 in-target: Package zstd is not available, but is referred to by another package.
May 15 17:23:37 in-target: This may mean that the package is missing, has been obsoleted, or
May 15 17:23:37 in-target: is only available from another source
May 15 17:23:37 in-target:
May 15 17:23:37 in-target: E
May 15 17:23:37 in-target: :
May 15 17:23:37 in-target: Package 'zstd' has no installation candidate
May 15 17:23:37 in-target:
May 15 17:23:37 base-installer: error: exiting on error base-installer/kernel/failed-package-install
May 15 17:24:27 init: starting pid 289, tty '/dev/tty2': '-/bin/sh'

The issue is this change [1], so we need to use the latest version of debian-cd
to create the installation images. However, since the latest version of debian-cd
currently doesn't work with Debian Ports, I need to fix that first.

Adrian

Post by Martina Hřebcová
[1] https://salsa.debian.org/installer-team/base-installer/-/commit/0500cbb5d95dc19c9b322ad475b0d80b2629d1c0

[John Paul Adrian Glaubitz]

Hi!

Post by John Paul Adrian Glaubitz
The issue is this change [1], so we need to use the latest version of debian-cd
to create the installation images. However, since the latest version of debian-cd
currently doesn't work with Debian Ports, I need to fix that first.

OK, it was enough to disable firmware support in the CD configuration for now which
isn't so much of a problem since it doesn't fully work at the moment anyway as it
needs server-side support in the archive.

Post by John Paul Adrian Glaubitz
https://cdimage.debian.org/cdimage/ports/snapshots/2023-05-16/

Thanks,
Adrian

[Martina Hřebcová]

Post by Ben Westover

Post by John Paul Adrian Glaubitz
The issue is this change [1], so we need to use the latest version of debian-cd
to create the installation images. However, since the latest version of debian-cd
currently doesn't work with Debian Ports, I need to fix that first.
OK, it was enough to disable firmware support in the CD configuration for now which
isn't so much of a problem since it doesn't fully work at the moment anyway as it
needs server-side support in the archive.
https://cdimage.debian.org/cdimage/ports/snapshots/2023-05-16/

Many thanks! I will test today or at least tomorrow evening and let you
know.

Post by Ben Westover
Thanks,
Adrian

Martina

[John Paul Adrian Glaubitz]

Hello Martina!

-Installing GRUB bootloader stucked ( grub-ieee1275 ). No fail, but no
response.

The process itself hangs as you can see in the kernel log:

May 16 20:29:35 kernel: [ 2538.468104] INFO: task kworker/2:1:68 blocked for more than 120 seconds.
May 16 20:29:35 kernel: [ 2538.468114] Not tainted 6.1.0-9-powerpc64 #1 Debian 6.1.27-1
May 16 20:29:35 kernel: [ 2538.468118] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 16 20:29:35 kernel: [ 2538.468121] task:kworker/2:1 state:D stack:0 pid:68 ppid:2 flags:0x00000800
May 16 20:29:35 kernel: [ 2538.468131] Workqueue: events_long .flush_mdb [hfs]
May 16 20:29:35 kernel: [ 2538.468148] Call Trace:
May 16 20:29:35 kernel: [ 2538.468151] [c00000000782b380] [0000000000000002] 0x2 (unreliable)
May 16 20:29:35 kernel: [ 2538.468160] [c00000000782b570] [c00000000001aa40] .__switch_to+0x1d0/0x2d0
May 16 20:29:35 kernel: [ 2538.468171] [c00000000782b620] [c000000000df6570] .__schedule+0x360/0xc30
May 16 20:29:35 kernel: [ 2538.468182] [c00000000782b700] [c000000000df6eac] .schedule+0x6c/0x130
May 16 20:29:35 kernel: [ 2538.468190] [c00000000782b780] [c000000000df6ffc] .io_schedule+0x4c/0x80
May 16 20:29:35 kernel: [ 2538.468199] [c00000000782b800] [c000000000df7e40] .bit_wait_io+0x20/0xc0
May 16 20:29:35 kernel: [ 2538.468208] [c00000000782b880] [c000000000df7bd8] .__wait_on_bit_lock+0xf8/0x180
May 16 20:29:35 kernel: [ 2538.468218] [c00000000782b930] [c000000000df7d1c] .out_of_line_wait_on_bit_lock+0xbc/0x100
May 16 20:29:35 kernel: [ 2538.468227] [c00000000782ba10] [c0000000005d64dc] .__lock_buffer+0x5c/0x80
May 16 20:29:35 kernel: [ 2538.468235] [c00000000782ba90] [c008000000e3a170] .hfs_mdb_commit+0x310/0x440 [hfs]
May 16 20:29:35 kernel: [ 2538.468246] [c00000000782bb50] [c008000000e3bd64] .flush_mdb+0x74/0xf0 [hfs]
May 16 20:29:35 kernel: [ 2538.468256] [c00000000782bbe0] [c00000000019e9a0] .process_one_work+0x2b0/0x580
May 16 20:29:35 kernel: [ 2538.468264] [c00000000782bc90] [c00000000019eed0] .worker_thread+0x260/0x5f0
May 16 20:29:35 kernel: [ 2538.468271] [c00000000782bd70] [c0000000001acb10] .kthread+0x120/0x130
May 16 20:29:35 kernel: [ 2538.468280] [c00000000782be10] [c00000000000d3d8] .ret_from_kernel_thread+0x58/0x60
May 16 20:29:35 kernel: [ 2538.468304] INFO: task grub-install:23819 blocked for more than 120 seconds.
May 16 20:29:35 kernel: [ 2538.468308] Not tainted 6.1.0-9-powerpc64 #1 Debian 6.1.27-1
May 16 20:29:35 kernel: [ 2538.468311] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 16 20:29:35 kernel: [ 2538.468313] task:grub-install state:D stack:0 pid:23819 ppid:23691 flags:0x00002000
May 16 20:29:35 kernel: [ 2538.468320] Call Trace:
May 16 20:29:35 kernel: [ 2538.468323] [c000000004183460] [c000000004183ab0] 0xc000000004183ab0 (unreliable)
May 16 20:29:35 kernel: [ 2538.468331] [c000000004183650] [c00000000001aa40] .__switch_to+0x1d0/0x2d0
May 16 20:29:35 kernel: [ 2538.468340] [c000000004183700] [c000000000df6570] .__schedule+0x360/0xc30
May 16 20:29:35 kernel: [ 2538.468349] [c0000000041837e0] [c000000000df6eac] .schedule+0x6c/0x130
May 16 20:29:35 kernel: [ 2538.468357] [c000000004183860] [c000000000e00304] .schedule_timeout+0x194/0x1e0
May 16 20:29:35 kernel: [ 2538.468365] [c000000004183930] [c000000000df821c] .__wait_for_common+0x13c/0x350
May 16 20:29:35 kernel: [ 2538.468374] [c000000004183a10] [c0000000001a06e8] .__flush_work.isra.0+0x1c8/0x3c0
May 16 20:29:35 kernel: [ 2538.468381] [c000000004183af0] [c008000000e3801c] .hfs_file_fsync+0xbc/0x110 [hfs]
May 16 20:29:35 kernel: [ 2538.468391] [c000000004183b80] [c0000000005c9640] .vfs_fsync_range+0x70/0xe0
May 16 20:29:35 kernel: [ 2538.468400] [c000000004183c10] [c0000000005c9c54] .__se_sys_fsync+0x54/0xa0
May 16 20:29:35 kernel: [ 2538.468407] [c000000004183c90] [c00000000002be1c] .system_call_exception+0x15c/0x2e0
May 16 20:29:35 kernel: [ 2538.468416] [c000000004183e10] [c00000000000cb54] system_call_common+0xf4/0x258
May 16 20:29:35 kernel: [ 2538.468425] --- interrupt: c00 at 0x7fffa3632684
May 16 20:29:35 kernel: [ 2538.468430] NIP: 00007fffa3632684 LR: 000000013c9f74b0 CTR: 0000000000000000
May 16 20:29:35 kernel: [ 2538.468433] REGS: c000000004183e80 TRAP: 0c00 Not tainted (6.1.0-9-powerpc64 Debian 6.1.27-1)
May 16 20:29:35 kernel: [ 2538.468437] MSR: 900000000000d032 <SF,HV,EE,PR,ME,IR,DR,RI> CR: 22082882 XER: 00000000
May 16 20:29:35 kernel: [ 2538.468460] IRQMASK: 0
May 16 20:29:35 kernel: [ 2538.468460] GPR00: 0000000000000076 00007fffed7e74d0 00007fffa3737200 0000000000000006
May 16 20:29:35 kernel: [ 2538.468460] GPR04: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
May 16 20:29:35 kernel: [ 2538.468460] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
May 16 20:29:35 kernel: [ 2538.468460] GPR12: 0000000000000000 00007fffa38fd520 0000000000000008 00007fffa3731bf0
May 16 20:29:35 kernel: [ 2538.468460] GPR16: 000000013cab7418 00000001629c22c0 000000013ca97f58 0000000000000009
May 16 20:29:35 kernel: [ 2538.468460] GPR20: 0000000153023d70 000000013ca23800 0000000153022e30 000000013ca21e08
May 16 20:29:35 kernel: [ 2538.468460] GPR24: 0000000153022e90 000000013ca1efc0 0000000000000006 0000000153024df0
May 16 20:29:35 kernel: [ 2538.468460] GPR28: 0000000000000006 0000000000000005 0000000153022e90 0000000000000005
May 16 20:29:35 kernel: [ 2538.468544] NIP [00007fffa3632684] 0x7fffa3632684
May 16 20:29:35 kernel: [ 2538.468548] LR [000000013c9f74b0] 0x13c9f74b0

What partition layout did you use? Did you keep the HFS boot partition as suggested by the installer?

If I skip installation of grub, do somebody know where I can find tested
grub package? Or I try do it manually with .iso grub directory.

There is no tested grub package as the packages are constantly updated.

Your issue could be a hardware problem, too. I will give it a try inside QEMU later.

Adrian

[John Paul Adrian Glaubitz]

Hi Martina!

Yes, I am used HFS ( not+) partition, with /boot/grub mountpoint. And
ext4 / partition.
In evening I will check also ext2 /boot/grub partition, and also try
install all together to single / ext4 partition, if installer allows it.
Of course, Mac will not boot in this case, but at least I can try whole
installation process.

That does not work. /boot/grub must be an HFS partition, otherwise the
installation of the GRUB bootloader will fail. I recommend using the
default partition layout for the time being.

Post by John Paul Adrian Glaubitz

If I skip installation of grub, do somebody know where I can find tested
grub package? Or I try do it manually with .iso grub directory.

There is no tested grub package as the packages are constantly updated.

OK I will try some things manually.

Post by John Paul Adrian Glaubitz
Your issue could be a hardware problem, too. I will give it a try inside QEMU later.

Yes it could. My Powermac Quad has now issues with thermal calibration,
I have to check and clean everything. Fortunatelly it has no coolant
leakage. But other hardware like disk controllers woks fine under OSX
and MorphOS.

In most cases it's a memory module problem and it's not unusual that the
problem shows with some operating systems only.

I have also iMac G5 stored in basement, so I can try installation here.
But later, my daughter is getting married this weekend :-)))

Testing on a different machine is definitely a very good idea!

PS: All the best for your daughter's marriage!

Adrian

[Martina Hřebcová]

Hi Adrian!

Post by John Paul Adrian Glaubitz

In evening I will check also ext2 /boot/grub partition, and also try
install all together to single / ext4 partition, if installer allows it.
Of course, Mac will not boot in this case, but at least I can try whole
installation process.

That does not work. /boot/grub must be an HFS partition, otherwise the
installation of the GRUB bootloader will fail. I recommend using the
default partition layout for the time being.

Thanks, it saves my time. I have another idea - I haven't check the size
of my /boot/grub partiton.

I used old grub partition from times when Debian drops yaboot. ( Debian
9 probably). Maybe this new grub version requires more space.

Post by John Paul Adrian Glaubitz

Yes it could. My Powermac Quad has now issues with thermal calibration,
I have to check and clean everything. Fortunatelly it has no coolant
leakage. But other hardware like disk controllers woks fine under OSX
and MorphOS.

In most cases it's a memory module problem and it's not unusual that the
problem shows with some operating systems only.

Powermac ASD firmware diagnostics shows all RAM modules OK. But it is
good point - I can try installation with only two other modules - i.e. 4GB

Post by John Paul Adrian Glaubitz

I have also iMac G5 stored in basement, so I can try installation here.
But later, my daughter is getting married this weekend :-)))

Testing on a different machine is definitely a very good idea!
PS: All the best for your daughter's marriage!

Many thanks !!!

Post by John Paul Adrian Glaubitz
Adrian

Martina

[John Paul Adrian Glaubitz]

Post by Martina Hřebcová

Post by John Paul Adrian Glaubitz

In evening I will check also ext2 /boot/grub partition, and also try
install all together to single / ext4 partition, if installer allows it.
Of course, Mac will not boot in this case, but at least I can try whole
installation process.

That does not work. /boot/grub must be an HFS partition, otherwise the
installation of the GRUB bootloader will fail. I recommend using the
default partition layout for the time being.

Thanks, it saves my time. I have another idea - I haven't check the size
of my /boot/grub partiton.
I used old grub partition from times when Debian drops yaboot. ( Debian
9 probably). Maybe this new grub version requires more space.

Yes, we increased the size of the /boot/grub partition at some point since GRUB
requires more space. So, if possible, I recommend using the default partition
layout that the installer suggests.

Adrian

[Martina Hřebcová]

"> On 5/17/23 10:38, John Paul Adrian Glaubitz wrote:
Yes, we increased the size of the /boot/grub partition at some point since
GRUB
requires more space. So, if possible, I recommend using the default
partition
layout that the installer suggests.
"



Yes!  I had from previous version grub partition size 128 MB and now is
needed at least 256 MB.

Interesting is, that instaling of grub-ieee.. package has no error output,
but simply hangs.


So sorry of false alert, installer now works fine. Thank you very much!





Unfortunatelly system not boots. I see grub screen, can edit, select
whatever. If I select kernel, there is only blinking cursor for few seconds
and then it stops blinkink.

Now I am in a hurry with family matters, but I will return to investigations
next week.




"
Adrian "



Martina

"
"

[Martina Hřebcová]

Post by Martina Hřebcová
Unfortunatelly system not boots. I see grub screen, can edit, select
whatever. If I select kernel, there is only blinking cursor for few
seconds and then it stops blinkink.
Now I am in a hurry with family matters, but I will return to
investigations next week.

P.S. very likely the cause of boot problems is on my side, not installer
one.

If I checked partitions with OSX and then with linux, it differs. And
the difference is in my two grub partitions. Using disk tools from
different OS causes some mismatch.

I will reorganize disks, and for Debian will be dedicated one.

[John Paul Adrian Glaubitz]

Good Morning!

Unfortunatelly system not boots. I see grub screen, can edit, select whatever. If I select kernel, there is only blinking cursor for few seconds and then it stops blinkink.
Now I am in a hurry with family matters, but I will return to investigations next week.

P.S. very likely the cause of boot problems is on my side, not installer one.
If I checked partitions with OSX and then with linux, it differs. And the difference is in my two grub partitions. Using disk tools from different OS causes some mismatch.
I will reorganize disks, and for Debian will be dedicated one.

Those aren’t boot-related issues, but you’re just missing the firmware for your graphics card.

Please boot the machine with “nomodeset” and install the “firmware-graphics-amd” package.

Adrian

[Martina Hřebcová]

Hi Adrian

Post by John Paul Adrian Glaubitz

P.S. very likely the cause of boot problems is on my side, not installer one.
If I checked partitions with OSX and then with linux, it differs. And the difference is in my two grub partitions. Using disk tools from different OS causes some mismatch.
I will reorganize disks, and for Debian will be dedicated one.

Those aren’t boot-related issues, but you’re just missing the firmware for your graphics card.
Please boot the machine with “nomodeset” and install the “firmware-graphics-amd” package.

Thanks for advice, I will do this first.

Post by John Paul Adrian Glaubitz
Adrian

Martina

[Martina Hřebcová]

Hello Adrian,

Post by John Paul Adrian Glaubitz

-Installing GRUB bootloader stucked ( grub-ieee1275 ). No fail, but no
response.

What partition layout did you use? Did you keep the HFS boot partition as suggested by the installer?

Yes, I am used HFS ( not+) partition, with /boot/grub mountpoint. And
ext4 / partition.

In evening I will check also ext2 /boot/grub partition, and also try
install all together to single / ext4 partition, if installer allows it.
Of course, Mac will not boot in this case, but at least I can try whole
installation process.

Post by John Paul Adrian Glaubitz

If I skip installation of grub, do somebody know where I can find tested
grub package? Or I try do it manually with .iso grub directory.

There is no tested grub package as the packages are constantly updated.

OK I will try some things manually.

Post by John Paul Adrian Glaubitz
Your issue could be a hardware problem, too. I will give it a try inside QEMU later.

Yes it could. My Powermac Quad has now issues with thermal calibration,
I have to check and clean everything. Fortunatelly it has no coolant
leakage. But other hardware like disk controllers woks fine under OSX
and MorphOS.

I have also iMac G5 stored in basement, so I can try installation here.
But later, my daughter is getting married this weekend :-)))

Post by John Paul Adrian Glaubitz
Adrian

Martina