Re: Bullseye installation problem (with Matrox GPU)
> I did a little more experimenting and learned my G550 doesn't need > nomodeset for the MGA X driver to work, but it only produces 1920x1080 > on my 2560x1440 screen, and xrandr still can't identify output names. You can trying playing with "modelines" where you reduce the screen refresh rate to 30Hz to keep the "dot frequency" below the card's limit. Contrary to CRT, current displays tend not to need as high a refresh rate to avoid flicker. Of course a lower refresh rate may encounter other problems (e.g. your display may simply refuse to display it). Stefan
Re: Bullseye installation problem (with Matrox GPU)
Felix Miata wrote: > > https://www.phoronix.com/scan.php?page=news_item=Linux-5.10-Matrox-G200 > > > I did a little more experimenting and learned my G550 doesn't need nomodeset > for > the MGA X driver to work, but it only produces 1920x1080 on my 2560x1440 > screen, > and xrandr still can't identify output names. I believe that the DAC on the G550 is only good up to 2048x1536 (DVI) or 1600x1200 (VGA). It was pretty good when it was introduced 20 years ago, and not too bad when the PCIe version was made 15 years ago. -dsr-
Re: Bullseye installation problem (with Matrox GPU)
Andrew M.A. Cater composed on 2021-07-06 22:30 (UTC): > On Tue, Jul 06, 2021 at 04:26:52PM -0400, Felix Miata wrote: >> I do have the MGA driver xserver-xorg-video-mga dysfunctional on (an AGP) >> G550 in >> i686 Bullseye by disabling KMS via nomodeset on, and adding iomem=relaxed >> to, the >> kernel command line, without installing firmware-misc-nonfree. The >> dysfunction is >> the screen blanks momentarily at random times, but is otherwise normal as >> long as >> xrandr is not needed to configure the screen. Installing >> firmware-misc-nonfree >> doesn't help. > Good news, then - apparently 5.10 now supports this better with KMS and will > also support the non-server G200 on Matrox cards > https://www.phoronix.com/scan.php?page=news_item=Linux-5.10-Matrox-G200 > I did a little more experimenting and learned my G550 doesn't need nomodeset for the MGA X driver to work, but it only produces 1920x1080 on my 2560x1440 screen, and xrandr still can't identify output names. # lsmod | egrep 'mga|video' # xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r xrandr: Failed to get size of gamma for output default Screen 0: minimum 400 x 270, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 60.00* # inxi -SGay System: Host: a-865.ij.net Kernel: 5.10.0-7-686 i686 bits: 32 compiler: gcc v: 10.2.1 parameters:...noresume mitigations=auto consoleblank=0 iomem=relaxed Desktop: Trinity R14.0.11 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 vt: 3 dm: startx Distro: Debian GNU/Linux 11 (bullseye) Graphics: Device-1: Matrox Systems Millennium G550 driver: N/A alternate: matroxfb_base bus-ID: 01:00.0 chip-ID: 102b:2527 class-ID: 0300 Display: server: X.Org 1.20.11 driver: loaded: mga unloaded: fbdev,modesetting,vesa display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 81 s-size: 602x343mm (23.7x13.5") s-diag: 693mm (27.3") Monitor-1: default res: 1920x1080 hz: 60 OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.4 compat-v: 3.1 direct render: Yes # lsmod | egrep -i 'mga|video' # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Bullseye installation problem (with Matrox GPU)
On Tue, Jul 06, 2021 at 04:26:52PM -0400, Felix Miata wrote: > Andrew M.A. Cater composed on 2021-07-06 12:56 (UTC): > > > Try installing firmware-misc-nonfree which will pull in > > firmware-amd-graphics > > I think. > > > I normally install firmware-linux-free firmware-linux-nonfree > > firmware-misc-nonfree - that covers all bases. > > > The AMD firmware is not in the standard firmware-linux-nonfree, from memory. > > > It's installed on my HP Microserver which is also Matrox G200 > > > Matrox has absolutely nothing to do with AMD except that they both "provide" > (manufacture?) graphics devices. If your HP G200e is working, then so should > Chris' be able to as well. > You may be right - but I found that installing the AMD frimware solved something for me. I've two HP Microserver Gen 8 machines here. Fonts maybe. > The G200e is a special evolution of the original G200/G400/G450/G550/G650 > series > that last I knew was no longer supported upstream since KMS matured. AFAIK, > the > G200e was supposedly the only chip supported by MGA X driver patches intended > to > keep X viable on HP servers without anyone willing to provide kernel support > for > KMS on Matrox. > > I do have the MGA driver xserver-xorg-video-mga dysfunctional on (an AGP) > G550 in > i686 Bullseye by disabling KMS via nomodeset on, and adding iomem=relaxed to, > the > kernel command line, without installing firmware-misc-nonfree. The > dysfunction is > the screen blanks momentarily at random times, but is otherwise normal as > long as > xrandr is not needed to configure the screen. Installing firmware-misc-nonfree > doesn't help. > -- > Evolution as taught in public schools is, like religion, > based on faith, not based on science. > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata > Good news, then - apparently 5.10 now supports this better with KMS and will also support the non-server G200 on Matrox cards https://www.phoronix.com/scan.php?page=news_item=Linux-5.10-Matrox-G200 All the best, as ever, Andy Cater
Re: Bullseye installation problem (with Matrox GPU)
Andrew M.A. Cater composed on 2021-07-06 12:56 (UTC): > Try installing firmware-misc-nonfree which will pull in firmware-amd-graphics > I think. > I normally install firmware-linux-free firmware-linux-nonfree > firmware-misc-nonfree - that covers all bases. > The AMD firmware is not in the standard firmware-linux-nonfree, from memory. > It's installed on my HP Microserver which is also Matrox G200 Matrox has absolutely nothing to do with AMD except that they both "provide" (manufacture?) graphics devices. If your HP G200e is working, then so should Chris' be able to as well. The G200e is a special evolution of the original G200/G400/G450/G550/G650 series that last I knew was no longer supported upstream since KMS matured. AFAIK, the G200e was supposedly the only chip supported by MGA X driver patches intended to keep X viable on HP servers without anyone willing to provide kernel support for KMS on Matrox. I do have the MGA driver xserver-xorg-video-mga dysfunctional on (an AGP) G550 in i686 Bullseye by disabling KMS via nomodeset on, and adding iomem=relaxed to, the kernel command line, without installing firmware-misc-nonfree. The dysfunction is the screen blanks momentarily at random times, but is otherwise normal as long as xrandr is not needed to configure the screen. Installing firmware-misc-nonfree doesn't help. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Bullseye installation problem
On Tuesday, 6 July 2021 11:45:10 BST you wrote: > Thanks for the reply > > > Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I > > normally > > > use a netinst CD created locally from the jigdo image (amd64). > > I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH > > server several times over the last few days, using different netinst CD's, > > and > > > each time the installation appears to be faultless until I try to boot the > > new > > > installation. I just want to be able to login locally, do a small amount > > of > > configuration, and then login remotely over the network. The GRUB display > > is normal, but then the SVGA monitor only shows a single message about > > > > VMX outside text (disabled by BIOS) > > > > before the monitor complains that the video is out of range and gives > > up > > > > Is firmware for your graphics device installed? > > I always use the "unofficial" installer with firmware, so it was > > firmware-bullseye-DI-rc2-amd64-netinst.iso > > and > > firmware-bullseye-DI-rc2-amd64-i386-netinst.iso > > > Try working around the immediate problem by appending nomodeset to the > > kernel command line via E key at Grub menu. For most graphics chips, > > nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X > > drivers, enabled KMS, so using it is little but a crutch to enable > > reconfiguration and troubleshooting [1]. > > > > What is output from > > > > lspci -nnk | grep -A3 VGA > > This is the output from the working buster 10.10.0 installation: > lspci -nnk | grep -A3 VGA > 0a:02.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. > MGA G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02) > Subsystem: Hewlett-Packard Company ProLiant DL140 G3 [103c:31fa] > Kernel driver in use: mgag200 > Kernel modules: mgag200 > > I am not desperate to get bullseye installed at the moment as I can still > use buster 10.10.0, but the release team want to prepare the full release > soon. I see that someone has already reported an issue with (I think) a > virtual different HP machine, which may not be identical. > I have full access (from the running buster 10.10.0 installation) to / for > the rc2 installation, including all the logs from the boot attempt, but all > I could do at the time was to select a Ctl-Alt-f3 terminal, login blind as > root, and do a shutdown. > I can even swap discs and re-install 10.10.0 to use the machine to avoid re- > formatting any of the current partitions, which would change UUID's for the > current 10.10.0, swapping the discs back for further testing. > The AMD firmware is not in the standard firmware-linux-nonfree, from memory. > All best, > Andy C. > It's installed on my HP Microserver which is also Matrox G200 Thanks for the info, I have assumed no op, hopefully re-installed again for the last time, and done some remote admin.
Re: Bullseye installation problem
On Tue, Jul 06, 2021 at 11:45:10AM +0100, Chris Bell wrote: > Thanks for the reply > > > Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I > normally > > use a netinst CD created locally from the jigdo image (amd64). > > I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH > > server several times over the last few days, using different netinst CD's, > and > > each time the installation appears to be faultless until I try to boot the > new > > installation. I just want to be able to login locally, do a small amount of > > configuration, and then login remotely over the network. The GRUB display > > is > > normal, but then the SVGA monitor only shows a single message about > > > VMX outside text (disabled by BIOS) > > > before the monitor complains that the video is out of range and gives up > > > > Is firmware for your graphics device installed? > > I always use the "unofficial" installer with firmware, so it was > > firmware-bullseye-DI-rc2-amd64-netinst.iso > > and > > firmware-bullseye-DI-rc2-amd64-i386-netinst.iso > > > Try working around the immediate problem by appending nomodeset to the > > kernel command line via E key at Grub menu. For most graphics chips, > > nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X > > drivers, enabled KMS, so using it is little but a crutch to enable > > reconfiguration and troubleshooting [1]. > > > What is output from > > lspci -nnk | grep -A3 VGA > > This is the output from the working buster 10.10.0 installation: > lspci -nnk | grep -A3 VGA > 0a:02.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA > G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02) > Subsystem: Hewlett-Packard Company ProLiant DL140 G3 [103c:31fa] > Kernel driver in use: mgag200 > Kernel modules: mgag200 > > I am not desperate to get bullseye installed at the moment as I can still use > buster 10.10.0, but the release team want to prepare the full release soon. > I see that someone has already reported an issue with (I think) a virtual > different HP machine, which may not be identical. > I have full access (from the running buster 10.10.0 installation) to / for > the > rc2 installation, including all the logs from the boot attempt, but all I > could do at the time was to select a Ctl-Alt-f3 terminal, login blind as > root, > and do a shutdown. > I can even swap discs and re-install 10.10.0 to use the machine to avoid re- > formatting any of the current partitions, which would change UUID's for the > current 10.10.0, swapping the discs back for further testing. > > Try installing firmware-misc-nonfree which will pull in firmware-amd-graphics I think. I normally install firmware-linux-free firmware-linux-nonfree firmware-misc-nonfree - that covers all bases. The AMD firmware is not in the standard firmware-linux-nonfree, from memory. All best, Andy C. It's installed on my HP Microserver which is also Matrox G200 Andy C.
Re: Bullseye installation problem
Thanks for the reply > Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I normally > use a netinst CD created locally from the jigdo image (amd64). > I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH > server several times over the last few days, using different netinst CD's, and > each time the installation appears to be faultless until I try to boot the new > installation. I just want to be able to login locally, do a small amount of > configuration, and then login remotely over the network. The GRUB display is > normal, but then the SVGA monitor only shows a single message about > VMX outside text (disabled by BIOS) > before the monitor complains that the video is out of range and gives up > Is firmware for your graphics device installed? I always use the "unofficial" installer with firmware, so it was firmware-bullseye-DI-rc2-amd64-netinst.iso and firmware-bullseye-DI-rc2-amd64-i386-netinst.iso > Try working around the immediate problem by appending nomodeset to the > kernel command line via E key at Grub menu. For most graphics chips, > nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X > drivers, enabled KMS, so using it is little but a crutch to enable > reconfiguration and troubleshooting [1]. > What is output from > lspci -nnk | grep -A3 VGA This is the output from the working buster 10.10.0 installation: lspci -nnk | grep -A3 VGA 0a:02.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02) Subsystem: Hewlett-Packard Company ProLiant DL140 G3 [103c:31fa] Kernel driver in use: mgag200 Kernel modules: mgag200 I am not desperate to get bullseye installed at the moment as I can still use buster 10.10.0, but the release team want to prepare the full release soon. I see that someone has already reported an issue with (I think) a virtual different HP machine, which may not be identical. I have full access (from the running buster 10.10.0 installation) to / for the rc2 installation, including all the logs from the boot attempt, but all I could do at the time was to select a Ctl-Alt-f3 terminal, login blind as root, and do a shutdown. I can even swap discs and re-install 10.10.0 to use the machine to avoid re- formatting any of the current partitions, which would change UUID's for the current 10.10.0, swapping the discs back for further testing.
Re: Bullseye installation problem
Chris Bell composed on 2021-07-05 18:22 (UTC+0100): > Machine HP Proliant ML150 with 5GB RAM and currently a single HDD. I normally > use a netinst CD created locally from the jigdo image (amd64). > I have tried to install both basic bullseye rc1 and bullseye rc2 with SSH > server several times over the last few days, using different netinst CD's, > and > each time the installation appears to be faultless until I try to boot the > new > installation. I just want to be able to login locally, do a small amount of > configuration, and then login remotely over the network. The GRUB display is > normal, but then the SVGA monitor only shows a single message about > VMX outside text (disabled by BIOS) > before the monitor complains that the video is out of range and gives up Is firmware for your graphics device installed? Try working around the immediate problem by appending nomodeset to the kernel command line via E key at Grub menu. For most graphics chips, nomodeset blocks a requirement of most AMD, Intel and NVidia GPUs X drivers, enabled KMS, so using it is little but a crutch to enable reconfiguration and troubleshooting [1]. What is output from lspci -nnk | grep -A3 VGA [1] https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Installation_Obstacles -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
