Re: Trying to start Xorg on a vanilla bullseye on rpi4

2022-11-05 Thread Tim Woodall

On Fri, 4 Nov 2022, Tim Woodall wrote:


I've tried updating the kernel to bullseye-backports but that hasn't
helped.

It's using the modesetting driver. Putting nomodeset on the kernel
commandline and that doesn't work.

Forcing X11 to use the fbdev device does start but doesn't find any
outputs.



I tried switching to use the uefi boot - which has the nice feature that
grub works. But that is worse:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1280, current 1920 x 1280, maximum 1920 x 1280
default connected 1920x1280+0+0 0mm x 0mm
   1920x1280 78.00*




Re: Trying to start Xorg on a vanilla bullseye on rpi4

2022-11-04 Thread Tim Woodall

On Thu, 3 Nov 2022, Tim Woodall wrote:


On Thu, 3 Nov 2022, Andrew M.A. Cater wrote:


On Thu, Nov 03, 2022 at 06:12:56PM +, Tim Woodall wrote:

Hi,

I have a vanilla installation of debian bullseye on a rpi4



Just going to check: this is a Debian image from gwolf and 
https://raspi.debian.net/ and not a Raspberry Pi OS image from Raspberry Pi 
foundation?



It's a home built image but only with stock debian packages installed. I
don't believe those images have X setup, but if they do then I'll try
one which might give me a clue what I've done wrong.


The image is 32 bit or 64 bit?


64 bit



I've tried updating the kernel to bullseye-backports but that hasn't
helped.

It's using the modesetting driver. Putting nomodeset on the kernel
commandline and that doesn't work.

Forcing X11 to use the fbdev device does start but doesn't find any
outputs.

If I set the output of the second monitor to 1920x1080 I can move it
around the 4K first monitor

The following is enough to get Xorg to start with two screens connected:

Section "Screen"
Identifier "Screen 0"
SubSection "Display"
Virtual 3840 2160
EndSubSection
EndSection

Setting the Virtual to anything bigger and Xorg fails to start.

I don't know how to create two device sections - this doesn't work:

Section "Device"
Identifier "vc4-0"
Driver "modesetting"
Screen 0
EndSection

Section "Device"
Identifier "vc4-1"
Driver "modesetting"
Screen 1
EndSection

I'm not sure what I should put for BusId - it doesn't show up in lspci

This fails with:
(EE) 
Fatal server error:
(EE) no screens found(EE) 
(EE)


adding BusID "card0" and I get:
(EE) 
Fatal server error:

(EE) Cannot run in framebuffer mode. Please specify busIDsfor all 
framebuffer devices
(EE)




Re: Trying to start Xorg on a vanilla bullseye on rpi4

2022-11-03 Thread Tim Woodall

On Thu, 3 Nov 2022, Andrew M.A. Cater wrote:


On Thu, Nov 03, 2022 at 06:12:56PM +, Tim Woodall wrote:

Hi,

I have a vanilla installation of debian bullseye on a rpi4



Just going to check: this is a Debian image from gwolf and 
https://raspi.debian.net/ and not a Raspberry Pi OS image from Raspberry Pi 
foundation?


It's a home built image but only with stock debian packages installed. I
don't believe those images have X setup, but if they do then I'll try
one which might give me a clue what I've done wrong.


The image is 32 bit or 64 bit?


64 bit


[Only because there is consistent confusion - if it really is Debian, we
can likely do more].



Which doesn't really tell me a lot...

If I start with one screen connected and then plug in the other then I
get a mirrored display whan I start the second output with xandr. But
any attempt to use xrandr to move them fails.


Does anyone have any ideas of what I need to do to get this working?

Even just being able to start X without having to unplug a screen would be a
start.

Tim.



All best, as ever,

Andy Cater






Re: Trying to start Xorg on a vanilla bullseye on rpi4

2022-11-03 Thread Andrew M.A. Cater
On Thu, Nov 03, 2022 at 06:12:56PM +, Tim Woodall wrote:
> Hi,
> 
> I have a vanilla installation of debian bullseye on a rpi4
> 

Just going to check: this is a Debian image from gwolf and 
https://raspi.debian.net/ and not a Raspberry Pi OS image from Raspberry Pi 
foundation?

The image is 32 bit or 64 bit?

[Only because there is consistent confusion - if it really is Debian, we
can likely do more].

> 
> Which doesn't really tell me a lot...
> 
> If I start with one screen connected and then plug in the other then I
> get a mirrored display whan I start the second output with xandr. But
> any attempt to use xrandr to move them fails.
> 
> 
> Does anyone have any ideas of what I need to do to get this working?
> 
> Even just being able to start X without having to unplug a screen would be a
> start.
> 
> Tim.
>

All best, as ever,

Andy Cater 



Trying to start Xorg on a vanilla bullseye on rpi4

2022-11-03 Thread Tim Woodall

Hi,

I have a vanilla installation of debian bullseye on a rpi4

But I cannot get X to start with two 4K screens attached.


The error (entire log below) is
[   707.980] (II) modeset(0): Output HDMI-1 connected
[   707.980] (II) modeset(0): Output HDMI-2 connected
[   707.980] (II) modeset(0): Using spanning desktop for initial modes
[   707.980] (II) modeset(0): Output HDMI-1 using initial mode 3840x2160 +0+0
[   707.980] (II) modeset(0): Output HDMI-2 using initial mode 3840x2160 +3840+0
[   707.980] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[   707.980] (==) modeset(0): DPI set to (96, 96)
[   707.980] (II) Loading sub module "fb"
[   707.981] (II) LoadModule: "fb"
[   707.981] (II) Loading /usr/lib/xorg/modules/libfb.so
[   707.982] (II) Module fb: vendor="X.Org Foundation"
[   707.982]compiled for 1.20.11, module version = 1.0.0
[   707.982]ABI class: X.Org ANSI C Emulation, version 0.4
[   707.983] (II) UnloadModule: "fbdev"
[   707.983] (II) Unloading fbdev
[   707.983] (II) UnloadSubModule: "fbdevhw"
[   707.983] (II) Unloading fbdevhw
[   707.999] (EE) 
Fatal server error:

[   707.999] (EE) AddScreen/ScreenInit failed for driver 0
[   707.999] (EE) 
[   707.999] (EE)


Which doesn't really tell me a lot...

If I start with one screen connected and then plug in the other then I
get a mirrored display whan I start the second output with xandr. But
any attempt to use xrandr to move them fails.



root@test17:~# xrandr --output HDMI-2 --mode 3840x2160 --panning 3840x2160+0+0
root@test17:~# xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 7680 x 7680
HDMI-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 600mm x 340mm
   3840x2160 27.26*+  30.0025.0024.0029.9723.98
   2560x1440 59.95
   1920x1080 60.0059.9430.0029.97
   1920x1080i60.0059.94
   1600x900  60.00
   1280x1024 60.02
   1280x800  59.91
   1280x720  60.0059.94
   1024x768  60.00
   800x600   60.32
   720x480   60.0059.94
   640x480   60.0059.94 
HDMI-2 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm

   3840x2160 27.26*+  30.0030.0025.0024.0029.9723.98
   2560x1440 59.95
   1920x1080 60.0060.0059.9430.0024.0029.9723.98
   1920x1080i60.0059.94
   1600x900  60.00
   1280x1024 60.02
   1280x800  59.91
   1280x720  60.0059.94
   1024x768  60.00
   800x600   60.32
   720x480   60.0059.94
   640x480   60.0059.94


root@test17:~# xrandr --output HDMI-2 --mode 3840x2160 --panning 
3840x2160+3840+0
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  7 (RRSetScreenSize)
  Serial number of failed request:  35
  Current serial number in output stream:  36
root@test17:~#


Does anyone have any ideas of what I need to do to get this working?

Even just being able to start X without having to unplug a screen would be a
start.

Tim.