Peter 'Shaggy' Haywood <
phay...@alphalink.com.au> writes:
> Groovy hepcat Mike Spencer was jivin' in alt.os.linux.slackware on Mon,
> 13 Feb 2023 04:44 pm. It's a cool scene! Dig it.
>
>> I do a text login, startx from keyboard, twm from ~/.xinitrc
>>
>> After a complete Slack 15 install (except no KDE):
>>
>> + X starts and works as expected
>>
>> + CTRL-ALT-F[2-6] goes to a console that works as expected.
>>
>> + ALT-F7 does *not* return me to X. ALT-F1 returns me to X
>> instead of the console screen from which startx was run.
>>
>> + When X returns, colors are a horrible, unusable mess.
>>
>> Restarting twm with its icon manager option doesn't fix it.
>>
>> Killing gpm (that I don't want anyhow) doesn't fix it.
>
> That's a text mode mouse driver. Why did you think killing it would
> fix X?
Because the gpm manpage says it may interfere with X.
> And if you don't want it, why are you running it?
Because an oversight at install left /etc/rc.d/rc.gpm executable.
>> I don't understand what I see happening in Xorg.0.log. Is that a clue?
>
> How should we know? You haven't shown us what you are seeing there,
> except for a few lines about input devices. (See below.)
Those are the lines that appeared after console switch and return,
>> What is that about VESA mode when returning to X from console?
>
> Yes; show us Xorg.0.log - the whole thing. We're not mind readers,
> y'know.
I'll defer dumping a 100K file to the group for now. Eliminating
kernel param nomodeset from lilo.conf fixes the X color mess but
reverts all consoles to tiny, unreadable type.
If there's solution to the teeny console font, I'm good.
If not, I'll post the Xorg log in full and ping you to look at it.
It's long because with nomodeset, it appears that X spends a lot of
effort looking for a vesa mode it likes without complete success.
Interpreting Xorg.log is above my pay grade.