Re: Fwd: Fwd: X stopped working with 5.14 on iBook

Andreas Schwab, schwab@linux-m68k.org
On my iBook G4, X is working alright with 5.15 and CONFIG_USER_NS=y.

The attached config file is the same as the current default Debian config file, with the Debian certificate information removed.

To duplicate the X11 error on the G4 Cube:

-----
$ git reset --hard
$ git remote update
$ git checkout v5.15
$ cp ../config-5.10.0-8-powerpc .config
$ ./scripts/config -d DEBUG_INFO
$ ./scripts/config -e LOCALVERSION_AUTO
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux modules
$ fgrep CONFIG_USER_NS .config
CONFIG_USER_NS=y
$ strings vmlinux | grep Linux.version
Linux version 5.15.0 (johnson@ThinkPad) (powerpc-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.37) #144 Thu Nov 4 10:17:33 MDT 2021
--> After installing vmlinux and modules, X fails on the G4 Cube.
-----
$ ./scripts/config -d USER_NS
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig vmlinux modules
$ fgrep CONFIG_USER_NS .config
# CONFIG_USER_NS is not set
$ strings vmlinux | grep Linux.version
Linux version 5.15.0 (johnson@ThinkPad) (powerpc-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.37) #145 Thu Nov 4 11:32:02 MDT 2021
--> After installing vmlinux and modules, X works on the G4 Cube.
-----
I get the same results with v5.15-rc7.
-----

On the Cube,
# dmesg | grep -i aty
[    0.000000] Kernel command line: root=/dev/sda12 ro video=aty128fb:1024x768-32@60
[    4.057110] aty128fb 0000:00:10.0: enabling device (0086 -> 0087)
[    4.057515] aty128fb 0000:00:10.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x1111
[    4.057579] aty128fb: ROM failed to map
[    4.057597] aty128fb: BIOS not located, guessing timings.
[    4.057628] aty128fb: Rage128 PF PRO AGP [chip rev 0x1]
[    4.303733] fb0: ATY Rage128 frame buffer device on Rage128 PF PRO AGP

If you are not able to duplicate the above results on a system with a video card similar to aty128fb, then the problem may be with Xorg or Debian.

While I do have "Xorg X server - core server 2:1.20.11-1" installed on the Cube, I also have other X-related installations that may be relevant (note particularly xserver-xorg-video-radeon):

# dpkg --list | grep xorg
ii xserver-xorg                1:7.7+23    powerpc X.Org X server
ii xserver-xorg-core           2:1.20.11-1 powerpc Xorg X server - core server
ii xserver-xorg-input-all      1:7.7+23    powerpc X.Org X server -- input driver metapackage
ii xserver-xorg-input-libinput 1.1.0-1     powerpc X.Org X server -- libinput input driver
ii xserver-xorg-input-wacom    0.34.99.1-1 powerpc X.Org X server -- Wacom input driver
ii xserver-xorg-legacy         2:1.20.11-1 powerpc setuid root Xorg server wrapper
ii xserver-xorg-video-all      1:7.7+23    powerpc X.Org X server -- output driver metapackage
ii xserver-xorg-video-amdgpu   19.1.0-2    powerpc X.Org X server -- AMDGPU display driver
ii xserver-xorg-video-ati      1:19.1.0-2  powerpc X.Org X server -- AMD/ATI display driver wrapper
ii xserver-xorg-video-fbdev    1:0.5.0-1   powerpc X.Org X server -- fbdev display driver
ii xserver-xorg-video-nouveau  1:1.0.17-1  powerpc X.Org X server -- Nouveau display driver
ii xserver-xorg-video-radeon   1:19.1.0-2  powerpc X.Org X server -- AMD/ATI Radeon display driver
ii xserver-xorg-video-vesa     1:2.5.0-1   powerpc X.Org X server -- VESA display driver

Please let me know if you need any additional information.

thanks

-Stan