2 Jul
2018
2 Jul
'18
10:07 a.m.
On Sunday 01 July 2018 21:48:27 William Morder wrote:
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
On Sunday 01 July 2018 18:03:13 Gene Heskett wrote:
It might be a good idea, and it may not. But the fact is that I have 5
machines here still running wheezy and one jessie, which wheezy is now
officially EOL even for security stuff. Until the lcnc crew have made up
a jessie or stretch installer, So the likelyhood of my playing with this
is quite low.
The jessie install is quite stable, but I have a rock64 running stretch
that while its 20x faster than a pi, has problems with the login screen
that in 6+ months, has not been fixed, so there is no way I could
honestly say stretch is stable. Reboots after an update are a try this
and see if it works, then try that, each one taking a full 10 second
powerdown to get it to even try to reboot.
Until you finally get the ducks in order and a successful login can be
done. That same rock64 runs jessie perfectly from power restoration to
the next power failure. That I'd call stable.
On Sunday 01 July 2018 20:47:58 William Morder
wrote:
You should be able to get it by installing through apt:
sudo apt-get install sysv-rc-conf
Then I will send you a screenshot of my own run levels, or somebody
else can do so; or you can do some research on how to set the run
levels in sysv-rc-conf.
I seem to recall that you could make some of these changes through the
Trinity Control Center, but sysv-rc-conf is much easier, so long as
you are careful. A lot of things can slow down your machine, because
they are configured to run at startup when you don't need them; while
other things that you want, like your sound system, might be disabled.
Bill
On Sunday 01 July 2018 17:23:52 Gene Heskett
wrote:
That is not findable on this wheezy machine. On Sunday 01 July 2018 19:58:34 Gene Heskett
wrote:
> On Sunday 01 July 2018 19:16:01 dep wrote:
> > /home/dep/trinity/share/config/ etc....
>
> I have that file, its owned by me:me and is rw only for me.
> And contains:
> DVI-I-1=
> DefaultProfile=
> EnableICC=false
> HDMI-1=
> VGA-1=
>
> No clue what could have sneezed and screwed it up, but there
> it is.
>
> No clue of the effect of setting some of those options might
> be. And no manpage. So your guess is likely better than mine.
Oh, I just found one thing that has not been fixed, I have audio
during boot until tdm starts after I log in. After login, I
still have to do an "alsactl restoreRETURN" before I have any
sound. Can this be fixed?
I use ALSA, and it starts when I boot up.
Have you messed with this toy?
sudo sysv-rc-conf > Be
careful, if you haven't used that before; although I suspect
> that you know it. Don't make changes there unless you know what to
> do.
>
> Also, look in
> Trinity Control Center / Sound & Multimedia / Sound System
> Both parts,
> General / Hardware
> ought to be examined.
>
> Bill
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting