We had a complaint recently from a customer that received a server we shipped
out that their monitor just showed a black screen. It turns out that they’d
hooked it up to an ancient POS with 800x600 as its best resolution, and gdm in
CentOS 7 apparently assumes at least 1024x768. It was apparen
On Thu, Feb 21, 2019 at 8:00 PM Warren Young wrote:
> We had a complaint recently from a customer that received a server we
> shipped out that their monitor just showed a black screen. It turns out
> that they’d hooked it up to an ancient POS with 800x600 as its best
> resolution, and gdm in Cen
On Feb 21, 2019, at 4:42 PM, Gianluca Cecchi wrote:
>
> [root@desktop xorg.conf.d]# cat 00-monitor.conf
Thanks! We’ll be building another server next week, so I’ll try this then.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mail
> On Feb 21, 2019, at 4:42 PM, Gianluca Cecchi
> wrote:
>>
>> [root@desktop xorg.conf.d]# cat 00-monitor.conf
Why not just ship it with text mode login and get rid of all the video
problems? With a 800x600 resolution I doubt they can do a lot with the GUI
anyway.
Regards,
Simon
On Feb 21, 2019, at 11:13 PM, Simon Matter via CentOS wrote:
>
>> On Feb 21, 2019, at 4:42 PM, Gianluca Cecchi
>> wrote:
>>>
>>> [root@desktop xorg.conf.d]# cat 00-monitor.conf
>
> Why not just ship it with text mode login and get rid of all the video
> problems? With a 800x600 resolution I do
On Feb 21, 2019, at 12:00 PM, Warren Young wrote:
>
> remotely talking someone through changing ifcfg-noisenoise via nano is a
> minor nightmare, especially now that Confusing Network Device Naming is the
> default.
A relevant war story might help here.
We were upgrading an old CentOS 5 box i
> On Feb 21, 2019, at 12:00 PM, Warren Young wrote:
>>
>> remotely talking someone through changing ifcfg-noisenoise via nano is a
>> minor nightmare, especially now that Confusing Network Device Naming is
>> the default.
>
> A relevant war story might help here.
>
> We were upgrading an old CentO
>> On Feb 21, 2019, at 12:00 PM, Warren Young wrote:
>>>
>>> remotely talking someone through changing ifcfg-noisenoise via nano is
>>> a
>>> minor nightmare, especially now that Confusing Network Device Naming is
>>> the default.
>>
>> A relevant war story might help here.
>>
>> We were upgrading
Simon Matter via CentOS wrote:
>
> One of the reasons why I hate the new naming scheme. It was also easy in
> the past to always monitor eth0, eth1 on a server, now you always have to
> first find out how the devices are named. I don't see progress here, I see
> a step back only. Maybe that's only
Warren Young wrote:
> On Feb 21, 2019, at 12:00 PM, Warren Young wrote:
> So, I logged into it remotely, poked around a bit, and got it to divulge
> the motherboard, CPU, etc. that we’d used on it, and I found that we had
> a nearly-identical box sitting around powered off locally, it having
> gi
On Feb 21, 2019, at 4:42 PM, Gianluca Cecchi wrote:
>
> Create a file 00-monitor.conf under /etc/x11/xorg.conf.d
>
> Something like this below, using conservative range values for horiz and
> vert syncs
This works fine here on our test monitors, with the exception that the first
‘x’ needs to b
Il Ven 1 Mar 2019, 17:28 Warren Young ha scritto:
> On Feb 21, 2019, at 4:42 PM, Gianluca Cecchi
> wrote:
> >
> > Create a file 00-monitor.conf under /etc/x11/xorg.conf.d
> >
> > Something like this below, using conservative range values for horiz and
> > vert syncs
>
> This works fine here on o
12 matches
Mail list logo
