Re: Unable to boot new buster installation (SOLVED)
On 6/12/20 9:25 PM, David Wright wrote: On Fri 12 Jun 2020 at 14:22:03 (-0700), Gary L. Roach wrote: On 6/11/20 1:24 AM, Dominique Dumont wrote: On mercredi 10 juin 2020 19:53:53 CEST Gary L. Roach wrote: The sequence of events on boot up are Bios screen, Debian Window with OS selection, Boot up sequence, login/password ( Xorg not running), startx -> error window. So to answer your question, the message is after login/password. Right.. Looks like there's no display manager installed. Depending on your favorite environment, could you install one of sddm, lxdm or gdm ? On my side, I used sddm. Question: Where is the file that contains the display setup (ie refresh rate, resolution.) This can be set in /etc/X11/xorg.conf in some cases (e.g. for nvidia hardware). Now, most of the required information is retrieved from hardware by Xorg. xorg.conf can usually be removed (except with nvidia driver). Where would randr get its information if Xorg was running? >From Xorg process. I would have responded sooner but have been hit with a severe case of Vertigo. No problem. I think I have finally found the problem. Running "journalct -xb" and running down the listing, I found that I was missing a Radeon video driver. The driver is non-free and the installation disk doesn't setup the sources.list for non-free downloads. So I'm in a catch 22 situation. When I install the net-install buster disk and switch to recover mode the network is not available and without the network I can't get the firmware I need to get the system started. I've tried the debian-live-10.40-amd64-kde+non-free disk and found it very confusing. In short, it didn't work either. There is a firmware package "firmware-amd-graphics"in the debian suit but without network access I can't get at it. If anyone could tell me how to start the network in rescue mode it would help. Why is the network shut down in rescue mode in the first place. I can't quite follow why you need rescue mode. After the login/password ( Xorg not running) in your sequence above, just don't run startx. Then edit the sources list, adding non-free to it. Now run apt or apt-get to update, and install the package. $ sudo apt-get update $ sudo apt-get install firmware-amd-graphics I've attached my sources.list as a pattern, though you can leave out the lines starting with deb-src. Cheers, David. Thanks for the reply. I have finally solved this problem. First, if I let the OS load normally, I get the video error message and the system locks up. If I use rescue mode there is no network access. Catch 22. The actual problem was that I was missing the proper firmware for my Radeon video card. I finally found this by running "journalctl -xb" which lists all of the steps in the boot process. The error showed up in bright red on my system. Since the firmware is non-free and the normal net-install disk doesn't add contrib and non-free to the sources.list, I was stuck until I found the debian-live disks. I used the debian-live-10.40-amd64-xxx-+non-free disk. When the first choice screen pops up do not select the debian-live choice but the normal debian installation. This disk adds contrib and non-free to the sources.list. Booting this up allowed me to download the firmware I needed. Problem solved. Gary R
Re: Unable to boot new buster installation
On Fri 12 Jun 2020 at 14:22:03 (-0700), Gary L. Roach wrote: > On 6/11/20 1:24 AM, Dominique Dumont wrote: > > On mercredi 10 juin 2020 19:53:53 CEST Gary L. Roach wrote: > > > The sequence of events on boot up are Bios screen, Debian Window with OS > > > selection, Boot up sequence, login/password ( Xorg not running), startx > > > -> error window. So to answer your question, the message is after > > > login/password. > > Right.. Looks like there's no display manager installed. Depending on your > > favorite environment, could you install one of sddm, lxdm or gdm ? > > > > On my side, I used sddm. > > > > > Question: Where is the file that contains the display setup (ie refresh > > > rate, resolution.) > > This can be set in /etc/X11/xorg.conf in some cases (e.g. for nvidia > > hardware). Now, most of the required information is retrieved from hardware > > by > > Xorg. xorg.conf can usually be removed (except with nvidia driver). > > > > > Where would randr get its information if Xorg was > > > running? > > >From Xorg process. > > > > > I would have responded sooner but have been hit with a severe case of > > > Vertigo. > > No problem. > > > I think I have finally found the problem. Running "journalct -xb" and > running down the listing, I found that I was missing a Radeon video > driver. The driver is non-free and the installation disk doesn't setup > the sources.list for non-free downloads. So I'm in a catch 22 > situation. When I install the net-install buster disk and switch to > recover mode the network is not available and without the network I > can't get the firmware I need to get the system started. I've tried > the debian-live-10.40-amd64-kde+non-free disk and found it very > confusing. In short, it didn't work either. There is a firmware > package "firmware-amd-graphics"in the debian suit but without network > access I can't get at it. > > If anyone could tell me how to start the network in rescue mode it > would help. Why is the network shut down in rescue mode in the first > place. I can't quite follow why you need rescue mode. After the login/password ( Xorg not running) in your sequence above, just don't run startx. Then edit the sources list, adding non-free to it. Now run apt or apt-get to update, and install the package. $ sudo apt-get update $ sudo apt-get install firmware-amd-graphics I've attached my sources.list as a pattern, though you can leave out the lines starting with deb-src. Cheers, David. # buster # deb cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64 NETINST 20190706-10:23]/ buster contrib main non-free #deb cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64 NETINST 20190706-10:23]/ buster contrib main non-free deb http://deb.debian.org/debian/ buster main non-free contrib deb-src http://deb.debian.org/debian/ buster main non-free contrib deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free # buster-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main contrib non-free deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual.
Re: Unable to boot new buster installation
On 6/11/20 1:24 AM, Dominique Dumont wrote: On mercredi 10 juin 2020 19:53:53 CEST Gary L. Roach wrote: The sequence of events on boot up are Bios screen, Debian Window with OS selection, Boot up sequence, login/password ( Xorg not running), startx -> error window. So to answer your question, the message is after login/password. Right.. Looks like there's no display manager installed. Depending on your favorite environment, could you install one of sddm, lxdm or gdm ? On my side, I used sddm. Question: Where is the file that contains the display setup (ie refresh rate, resolution.) This can be set in /etc/X11/xorg.conf in some cases (e.g. for nvidia hardware). Now, most of the required information is retrieved from hardware by Xorg. xorg.conf can usually be removed (except with nvidia driver). Where would randr get its information if Xorg was running? >From Xorg process. I would have responded sooner but have been hit with a severe case of Vertigo. No problem. All the best Dod I think I have finally found the problem. Running "journalct -xb" and running down the listing, I found that I was missing a Radeon video driver. The driver is non-free and the installation disk doesn't setup the sources.list for non-free downloads. So I'm in a catch 22 situation. When I install the net-install buster disk and switch to recover mode the network is not available and without the network I can't get the firmware I need to get the system started. I've tried the debian-live-10.40-amd64-kde+non-free disk and found it very confusing. In short, it didn't work either. There is a firmware package "firmware-amd-graphics"in the debian suit but without network access I can't get at it. If anyone could tell me how to start the network in rescue mode it would help. Why is the network shut down in rescue mode in the first place. Gary R
Re: Unable to boot new buster installation
On 2020-06-10 22:13, Gary L. Roach wrote: On 6/10/20 12:10 PM, Henning Follmann wrote: On Wed, Jun 10, 2020 at 10:53:53AM -0700, Gary L. Roach wrote: On 6/10/20 5:17 AM, Dominique Dumont wrote: On dimanche 7 juin 2020 21:14:20 CEST Gary L. Roach wrote: I recently up graded this system to Bullseye and then ran into trouble with the lack of Qt4 and had to re-install Buster. The installation went fine until kde desktop tried to start. The system froze with the following message: The current input timing is not supported by the monitor display. Pleas change your input timing to 1920x1200@60Hz or any other monitor listed timing as per the monitor specifications. Is the login/password window showing up ? Does this message show before or after logging in ? I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor worked fine before and still works fine on another computer. I tried both xrandr and compiz in Recovery Mode. In both cases I got "Can't open display". In recovery mode, xorg is not running so xrandr has no X server to connect to. HTH The sequence of events on boot up are Bios screen, Debian Window with OS selection, Boot up sequence, login/password ( Xorg not running), startx -> error window. So to answer your question, the message is after login/password. I hope this gives you some incite to my problem. I tried the other suggestions with no results. Question: Where is the file that contains the display setup (ie refresh rate, resolution.) Where would randr get its information if Xorg was running? That might be actually your issue here. If you at one point created a xorg.conf (check "man xorg.conf" for all possible locations) it might get in your way. By default a modesetting server is started which collects the monitor's EDID information and sets the modeline automagically. Would you try moving any existing xorg.conf out of the way and starting xorg without? -H Interesting that using locate I could not find a copy of xorg.conf anywhere in my system. There is a /usr/share/X11/xofg.conf.d/ directory that has the following files: If anything has changed I run "/usr/bin/updatedb" as root before locate. mick -- Key ID4BFEBB31
Re: Unable to boot new buster installation
On mercredi 10 juin 2020 19:53:53 CEST Gary L. Roach wrote: > The sequence of events on boot up are Bios screen, Debian Window with OS > selection, Boot up sequence, login/password ( Xorg not running), startx > -> error window. So to answer your question, the message is after > login/password. Right.. Looks like there's no display manager installed. Depending on your favorite environment, could you install one of sddm, lxdm or gdm ? On my side, I used sddm. > Question: Where is the file that contains the display setup (ie refresh > rate, resolution.) This can be set in /etc/X11/xorg.conf in some cases (e.g. for nvidia hardware). Now, most of the required information is retrieved from hardware by Xorg. xorg.conf can usually be removed (except with nvidia driver). > Where would randr get its information if Xorg was > running? >From Xorg process. > I would have responded sooner but have been hit with a severe case of > Vertigo. No problem. All the best Dod
Re: Unable to boot new buster installation
On 6/10/20 12:10 PM, Henning Follmann wrote: On Wed, Jun 10, 2020 at 10:53:53AM -0700, Gary L. Roach wrote: On 6/10/20 5:17 AM, Dominique Dumont wrote: On dimanche 7 juin 2020 21:14:20 CEST Gary L. Roach wrote: I recently up graded this system to Bullseye and then ran into trouble with the lack of Qt4 and had to re-install Buster. The installation went fine until kde desktop tried to start. The system froze with the following message: The current input timing is not supported by the monitor display. Pleas change your input timing to 1920x1200@60Hz or any other monitor listed timing as per the monitor specifications. Is the login/password window showing up ? Does this message show before or after logging in ? I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor worked fine before and still works fine on another computer. I tried both xrandr and compiz in Recovery Mode. In both cases I got "Can't open display". In recovery mode, xorg is not running so xrandr has no X server to connect to. HTH The sequence of events on boot up are Bios screen, Debian Window with OS selection, Boot up sequence, login/password ( Xorg not running), startx -> error window. So to answer your question, the message is after login/password. I hope this gives you some incite to my problem. I tried the other suggestions with no results. Question: Where is the file that contains the display setup (ie refresh rate, resolution.) Where would randr get its information if Xorg was running? That might be actually your issue here. If you at one point created a xorg.conf (check "man xorg.conf" for all possible locations) it might get in your way. By default a modesetting server is started which collects the monitor's EDID information and sets the modeline automagically. Would you try moving any existing xorg.conf out of the way and starting xorg without? -H Interesting that using locate I could not find a copy of xorg.conf anywhere in my system. There is a /usr/share/X11/xofg.conf.d/ directory that has the following files: 10-amdgpu.conf 10-quirks.conf 10-radeon.conf 40-libinput.conf 70-wacon,conf I searched through all of the directories that were listed in the man xorg.conf help page and found nothing. Gary R.
Re: Unable to boot new buster installation
On Wed, Jun 10, 2020 at 10:53:53AM -0700, Gary L. Roach wrote: > On 6/10/20 5:17 AM, Dominique Dumont wrote: > > On dimanche 7 juin 2020 21:14:20 CEST Gary L. Roach wrote: > > > I recently up graded this system to Bullseye and then ran into trouble > > > with the lack of Qt4 and had to re-install Buster. The installation > > > went fine until kde desktop tried to start. The system froze with the > > > following message: > > > > > > The current input timing is not supported by the monitor > > > display. Pleas change your input timing to 1920x1200@60Hz or any other > > > monitor listed timing as per the monitor specifications. > > Is the login/password window showing up ? > > > > Does this message show before or after logging in ? > > > > > I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor > > > worked fine before and still works fine on another computer. I tried > > > both xrandr and compiz in Recovery Mode. In both cases I got "Can't open > > > display". > > In recovery mode, xorg is not running so xrandr has no X server to connect > > to. > > > > HTH > > > > > > > > > The sequence of events on boot up are Bios screen, Debian Window with OS > selection, Boot up sequence, login/password ( Xorg not running), startx -> > error window. So to answer your question, the message is after > login/password. > > I hope this gives you some incite to my problem. I tried the other > suggestions with no results. > > Question: Where is the file that contains the display setup (ie refresh > rate, resolution.) Where would randr get its information if Xorg was > running? > That might be actually your issue here. If you at one point created a xorg.conf (check "man xorg.conf" for all possible locations) it might get in your way. By default a modesetting server is started which collects the monitor's EDID information and sets the modeline automagically. Would you try moving any existing xorg.conf out of the way and starting xorg without? -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: Unable to boot new buster installation
On 6/10/20 5:17 AM, Dominique Dumont wrote: On dimanche 7 juin 2020 21:14:20 CEST Gary L. Roach wrote: I recently up graded this system to Bullseye and then ran into trouble with the lack of Qt4 and had to re-install Buster. The installation went fine until kde desktop tried to start. The system froze with the following message: The current input timing is not supported by the monitor display. Pleas change your input timing to 1920x1200@60Hz or any other monitor listed timing as per the monitor specifications. Is the login/password window showing up ? Does this message show before or after logging in ? I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor worked fine before and still works fine on another computer. I tried both xrandr and compiz in Recovery Mode. In both cases I got "Can't open display". In recovery mode, xorg is not running so xrandr has no X server to connect to. HTH The sequence of events on boot up are Bios screen, Debian Window with OS selection, Boot up sequence, login/password ( Xorg not running), startx -> error window. So to answer your question, the message is after login/password. I hope this gives you some incite to my problem. I tried the other suggestions with no results. Question: Where is the file that contains the display setup (ie refresh rate, resolution.) Where would randr get its information if Xorg was running? I would have responded sooner but have been hit with a severe case of Vertigo. Gary R
Re: Unable to boot new buster installation
On dimanche 7 juin 2020 21:14:20 CEST Gary L. Roach wrote: > I recently up graded this system to Bullseye and then ran into trouble > with the lack of Qt4 and had to re-install Buster. The installation > went fine until kde desktop tried to start. The system froze with the > following message: > > The current input timing is not supported by the monitor > display. Pleas change your input timing to 1920x1200@60Hz or any other > monitor listed timing as per the monitor specifications. Is the login/password window showing up ? Does this message show before or after logging in ? > I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor > worked fine before and still works fine on another computer. I tried > both xrandr and compiz in Recovery Mode. In both cases I got "Can't open > display". In recovery mode, xorg is not running so xrandr has no X server to connect to. HTH
Re: Unable to boot new buster installation
On 2020-06-07 20:14, Gary L. Roach wrote: Hi all, I recently up graded this system to Bullseye and then ran into trouble with the lack of Qt4 and had to re-install Buster. The installation went fine until kde desktop tried to start. The system froze with the following message: The current input timing is not supported by the monitor display. Pleas change your input timing to 1920x1200@60Hz or any other monitor listed timing as per the monitor specifications. I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor worked fine before and still works fine on another computer. I tried both xrandr and compiz in Recovery Mode. In both cases I got "Can't open display". I have full access to the file system in Recovery Mode. Any suggestions will be sincerely appreciated. Gary R I'd start here. https://wiki.debian.org/Xorg#Edit_xorg.conf mick -- Key ID4BFEBB31
Re: Unable to boot new buster installation
On 08.06.20 01:49, Gary L. Roach wrote: On 6/7/20 12:14 PM, Gary L. Roach wrote: Hi all, I recently up graded this system to Bullseye and then ran into trouble with the lack of Qt4 and had to re-install Buster. The installation went fine until kde desktop tried to start. The system froze with the following message: The current input timing is not supported by the monitor display. Pleas change your input timing to 1920x1200@60Hz or any other monitor listed timing as per the monitor specifications. I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor worked fine before and still works fine on another computer. I tried both xrandr and compiz in Recovery Mode. In both cases I got "Can't open display". I have full access to the file system in Recovery Mode. Any suggestions will be sincerely appreciated. Gary R Unfortunately I have no idea about how to solve your problem. You maybe want to ask also on this list as well: debian-...@lists.debian.org ? Good Luck! Marco.
Re: Unable to boot new buster installation
On 6/7/20 12:14 PM, Gary L. Roach wrote: Hi all, I recently up graded this system to Bullseye and then ran into trouble with the lack of Qt4 and had to re-install Buster. The installation went fine until kde desktop tried to start. The system froze with the following message: The current input timing is not supported by the monitor display. Pleas change your input timing to 1920x1200@60Hz or any other monitor listed timing as per the monitor specifications. I'm using a Dell U2412M monitor on an AMD 64 4 core system. The monitor worked fine before and still works fine on another computer. I tried both xrandr and compiz in Recovery Mode. In both cases I got "Can't open display". I have full access to the file system in Recovery Mode. Any suggestions will be sincerely appreciated. Gary R
