rock64, date is UTC, how to make EST (s/b UTC-5)

[Gene Heskett]

I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop

What am I missing?

[Alan Corey]

Delete the /etc/localtime symlink, replace it with one pointing to
/usr/share/zoneinfo/EST5EDT

There's no raspi-config equivalent I've found, Armbian has one. I
just dumped the Ayufan Stretch Minimal onto a new SD too.

OK, run
dpkg-reconfigure locales
There's probably more than 1 way

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?
--
Cheers, Gene Heskett
--
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[Gene Heskett]

Post by Alan Corey
Delete the /etc/localtime symlink, replace it with one pointing to
/usr/share/zoneinfo/EST5EDT
There's no raspi-config equivalent I've found, Armbian has one. I
just dumped the Ayufan Stretch Minimal onto a new SD too.
OK, run
dpkg-reconfigure locales

I've done that many times, options were and are set correctly, but no
effect on LANG, LANGUAGE & a couple others. And I've "export LANG=en_US"
and such as root with zero effect that I can see as the user.

Post by Alan Corey
There's probably more than 1 way

Yes see a previous msg about dpkg-reconfigure tzdata, worked exactly for
the time displayed as localtime.

These things don't have a clock, so they use fake-hwclock, so I turned on
ntp.conf logging and that looks like its doing well. But since its not
pestering the level one servers, just debians, I left that be. The diff
is likely measured in micro-seconds.


Now, if I could just figure out which of 262 hits that apt-file find
reports to install pdftex from, maybe I could build the realtime kernels
docs, theres a failure in building the networking.pdf because whats
installed apparently isn't compatible, but 40+ other docs that do use
it, build just fine. And the makefile does not compress vmlinux to
vmlinuz. I've not determined the syntax for that, nor to make the initrd
file. The plain make -j3 after a make clean is about 85 minutes, but I
think its making some stuff not needed. This is working not on the sd
card, but on a 120GB SSD as a work drive. Plugged into a usb-sata
adapter, its around 6x faster than a 7200 rpm rusty glass drive.

But so much stuff is different from x86 it gets confusing. I got the
proper command and made it a 1 line script to add the missing gateway to
the routeing tables, so its on the net ok now if I run that after a
reboot. That helps considerably.

Thanks Alan.

[Alan Corey]

On Sun, 22 Jul 2018 11:43:38 -0400

Post by Gene Heskett
These things don't have a clock, so they use fake-hwclock, so I
turned on ntp.conf logging and that looks like its doing well. But
since its not pestering the level one servers, just debians, I left
that be. The diff is likely measured in micro-seconds.

Actually the Rock64 does have a hardware clock, there's just no battery
so it's not useful. In the schematics somewhere it shows how to hook a
single lithium cell up.

See dmesg | grep rtc

If you were using it portable or off-grid that would be important.

I haven't built a Linux kernel in 10 years or so, used to do it
routinely in OpenBSD and FreeBSD. Did it once in Linux because the
default one at the time wouldn't use more than 2 GB of RAM or
something. That was i386.

My locale stuff didn't change until I'd rebooted, now it shows:

LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

I've tried setting parts manually, never seems to work.

[Gene Heskett]

Post by Alan Corey
On Sun, 22 Jul 2018 11:43:38 -0400

Post by Gene Heskett
These things don't have a clock, so they use fake-hwclock, so I
turned on ntp.conf logging and that looks like its doing well. But
since its not pestering the level one servers, just debians, I left
that be. The diff is likely measured in micro-seconds.

Actually the Rock64 does have a hardware clock, there's just no
battery so it's not useful. In the schematics somewhere it shows how
to hook a single lithium cell up.
See dmesg | grep rtc
If you were using it portable or off-grid that would be important.
I haven't built a Linux kernel in 10 years or so, used to do it
routinely in OpenBSD and FreeBSD. Did it once in Linux because the
default one at the time wouldn't use more than 2 GB of RAM or
something. That was i386.
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
I've tried setting parts manually, never seems to work.

But I have to go to the thing to reboot it, some security knucklehead has
decided it doesn't fully boot until user 1000 is logged in from its own
keyboard. Even then X needing stuff is not available from an ssh login.
That I think might be related to the fact that user 1000 is hard coded
into the install, which IMO is a huge mistake. I've tried to change
that on 2 of these little credit card things, but thats impossible to do
correctly so everything just works. So I have to put up with the
username miss-match, and goto its own keyboard to run anything that
needs X. That sort of stuff is usually found on the ground behind the
male of the bovine specie. And I'm getting less and less inclined to
stfu about it. Surely this first user can be created at first boot after
writing a new image to the sd card it boots from?

Can I make an alias on this machine so user pi or user rock64=gene as far
as this X accepting the output of an ssh -Y ***@picnc and/or an ssh -Y
***@rock64 for instance?

[Alan Corey]

Sorry about all the partial posts, that was Claws mail. I thought it was
saving backups but it was posting them. Saw it a few days ago with someone
else in some list.

It's not that hard to do autologin as any user you want, don't have it
handy.

Sent from my Motorola XT1527

Post by Gene Heskett

Post by Alan Corey
On Sun, 22 Jul 2018 11:43:38 -0400

Post by Gene Heskett
These things don't have a clock, so they use fake-hwclock, so I
turned on ntp.conf logging and that looks like its doing well. But
since its not pestering the level one servers, just debians, I left
that be. The diff is likely measured in micro-seconds.

Actually the Rock64 does have a hardware clock, there's just no
battery so it's not useful. In the schematics somewhere it shows how
to hook a single lithium cell up.
See dmesg | grep rtc
If you were using it portable or off-grid that would be important.
I haven't built a Linux kernel in 10 years or so, used to do it
routinely in OpenBSD and FreeBSD. Did it once in Linux because the
default one at the time wouldn't use more than 2 GB of RAM or
something. That was i386.
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
I've tried setting parts manually, never seems to work.

But I have to go to the thing to reboot it, some security knucklehead has
decided it doesn't fully boot until user 1000 is logged in from its own
keyboard. Even then X needing stuff is not available from an ssh login.
That I think might be related to the fact that user 1000 is hard coded
into the install, which IMO is a huge mistake. I've tried to change
that on 2 of these little credit card things, but thats impossible to do
correctly so everything just works. So I have to put up with the
username miss-match, and goto its own keyboard to run anything that
needs X. That sort of stuff is usually found on the ground behind the
male of the bovine specie. And I'm getting less and less inclined to
stfu about it. Surely this first user can be created at first boot after
writing a new image to the sd card it boots from?
Can I make an alias on this machine so user pi or user rock64=gene as far
--
Cheers, Gene Heskett
--
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[Gene Heskett]

Post by Gene Heskett

Post by Alan Corey
On Sun, 22 Jul 2018 11:43:38 -0400

Post by Gene Heskett
These things don't have a clock, so they use fake-hwclock, so I
turned on ntp.conf logging and that looks like its doing well. But
since its not pestering the level one servers, just debians, I
left that be. The diff is likely measured in micro-seconds.

Actually the Rock64 does have a hardware clock, there's just no
battery so it's not useful. In the schematics somewhere it shows
how to hook a single lithium cell up.

Presumably the usual cr2032? I could more than likely extract a carrier
from an old mobo.

Post by Gene Heskett

Post by Alan Corey
See dmesg | grep rtc
If you were using it portable or off-grid that would be important.
I haven't built a Linux kernel in 10 years or so, used to do it
routinely in OpenBSD and FreeBSD. Did it once in Linux because the
default one at the time wouldn't use more than 2 GB of RAM or
something. That was i386.
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
I've tried setting parts manually, never seems to work.

But I have to go to the thing to reboot it, some security knucklehead
has decided it doesn't fully boot until user 1000 is logged in from
its own keyboard. Even then X needing stuff is not available from an
ssh login. That I think might be related to the fact that user 1000 is
hard coded into the install, which IMO is a huge mistake. I've tried
to change that on 2 of these little credit card things, but thats
impossible to do correctly so everything just works. So I have to put
up with the username miss-match, and goto its own keyboard to run
anything that needs X. That sort of stuff is usually found on the
ground behind the male of the bovine specie. And I'm getting less and
less inclined to stfu about it. Surely this first user can be created
at first boot after writing a new image to the sd card it boots from?
Can I make an alias on this machine so user pi or user rock64=gene as

[Jim MacKenzie]

Just a heads-up, you actually will want it to be EDT (UTC-4), unless your
area doesn't observe daylight saving time. Fortunately, Debian will take
care of this for you.

I just do dpkg-reconfigure tzdata (as root, or you can add 'sudo' to the
start if you use sudo) and choose a city or region that observes the same
time zone (plus DST if applicable - not all regions observe it, like mine).

Jim

-----Original Message-----
From: Gene Heskett [mailto:***@shentel.net]
Sent: Sunday, July 22, 2018 10:35 AM
To: debian-***@lists.debian.org
Subject: Re: rock64, date is UTC, how to make EST (s/b UTC-5)

Post by Alan Corey
On Sun, 22 Jul 2018 11:43:38 -0400

Post by Gene Heskett
These things don't have a clock, so they use fake-hwclock, so I
turned on ntp.conf logging and that looks like its doing well. But
since its not pestering the level one servers, just debians, I left
that be. The diff is likely measured in micro-seconds.

Actually the Rock64 does have a hardware clock, there's just no
battery so it's not useful. In the schematics somewhere it shows how
to hook a single lithium cell up.
See dmesg | grep rtc
If you were using it portable or off-grid that would be important.
I haven't built a Linux kernel in 10 years or so, used to do it
routinely in OpenBSD and FreeBSD. Did it once in Linux because the
default one at the time wouldn't use more than 2 GB of RAM or
something. That was i386.
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
I've tried setting parts manually, never seems to work.

But I have to go to the thing to reboot it, some security knucklehead has
decided it doesn't fully boot until user 1000 is logged in from its own
keyboard. Even then X needing stuff is not available from an ssh login.
That I think might be related to the fact that user 1000 is hard coded into
the install, which IMO is a huge mistake. I've tried to change that on 2 of
these little credit card things, but thats impossible to do correctly so
everything just works. So I have to put up with the username miss-match, and
goto its own keyboard to run anything that needs X. That sort of stuff is
usually found on the ground behind the male of the bovine specie. And I'm
getting less and less inclined to stfu about it. Surely this first user can
be created at first boot after writing a new image to the sd card it boots
from?

Can I make an alias on this machine so user pi or user rock64=gene as far as
this X accepting the output of an ssh -Y ***@picnc and/or an ssh -Y
***@rock64 for instance?


--
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>

[Gene Heskett]

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?

The traditional command for that was tzconfig, but these days it will
tell you to run dpkg-reconfigure something...
dpkg-reconfigure tzdata

Worked a treat, thank you.

[Alan Corey]

OK, took a while to find this gem again. In /lib/systemd/system/***@service

In the [Service] section, replace

ExecStart=-/sbin/agetty --noclear %I $TERM
with
ExecStart=-/sbin/agetty --noclear -a root %I $TERM

That's it, very simple. Affects all virtual consoles and X after startx

For X, if you're using lightdm there's a different method, that's
upstairs. I have a Pi with the touch lcd screen which does autologin
as root, had to change a PAM file to do it (in Raspbian).

Post by Gene Heskett

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?

The traditional command for that was tzconfig, but these days it will
tell you to run dpkg-reconfigure something...
dpkg-reconfigure tzdata

Worked a treat, thank you.

It's regrettable that dpkg-reconfigure doesn't have something like a
--list command which summarises the packages to which it may be applied,
or even a --search which works by analogy with apt-cache etc.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]

[Alan Corey]

Autologin for X

Setting GUI login, in
/etc/systemd/system
the symlink default.target
should point to
/lib/systemd/system/graphical.target
instead of multi-user.target

[I think if you've set autologin in the agettty thing it never gets here]

For GUI autologin see /etc/lightdm/lightdm.conf

about 50% of the way through the file under [Seat:*]
autologin-user=root

in /etc/pam.d/lightdm-autologin (if not present you're all set)
under # Allow access without authentication, change
auth required pam_succeed_if.so user != root quiet_success
to
auth required pam_succeed_if.so user = root quiet_success
[just drop the !]

Post by Alan Corey
OK, took a while to find this gem again. In
In the [Service] section, replace
ExecStart=-/sbin/agetty --noclear %I $TERM
with
ExecStart=-/sbin/agetty --noclear -a root %I $TERM
That's it, very simple. Affects all virtual consoles and X after startx
For X, if you're using lightdm there's a different method, that's
upstairs. I have a Pi with the touch lcd screen which does autologin
as root, had to change a PAM file to do it (in Raspbian).

Post by Gene Heskett

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?

The traditional command for that was tzconfig, but these days it will
tell you to run dpkg-reconfigure something...
dpkg-reconfigure tzdata

Worked a treat, thank you.

It's regrettable that dpkg-reconfigure doesn't have something like a
--list command which summarises the packages to which it may be applied,
or even a --search which works by analogy with apt-cache etc.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]

--
-------------
No, I won't call it "climate change", do you have a "reality problem"? - AB1JX
Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach

[Gene Heskett]

On Monday 23 July 2018 09:23:56 Alan Corey wrote:

This may not be the right thread, but I think I just fixed my ssh login
failures on the pi.

It seems an option command (X11ForwardTrusted) was moved from sshd_config
to ssh_config and if it hit that option twice, the server would not
start. I took it back out of sshd_config. So now I have a working shell
into the pi from both on this machine, and the rock64. Life will be
better now.

Many thanks to all that tried to help.

[Gene Heskett]

Post by Gene Heskett

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?

The traditional command for that was tzconfig, but these days it
will tell you to run dpkg-reconfigure something...
dpkg-reconfigure tzdata

Worked a treat, thank you.

It's regrettable that dpkg-reconfigure doesn't have something like a
--list command which summarises the packages to which it may be
applied, or even a --search which works by analogy with apt-cache etc.

And if my well aged wet ram is to be trusted, it used to do a lot more
than it is now, only setting two items in the locales now. Or its been
stripped to do the bare minimum on a rock64/arm64. Dunno which, but its
a dissapointment, just like the networking is broken in that it cannot
apply a gateway to a static setup without doing a separate command with
route once its booted. Putting the gateway address into /e/n/i.d/eth0 is
simply ignored. I even moved it to /e/n/i, no effect. Yesterday I tried
changing the static address, took 3 powerdown reboots to actually get
that to take, and 2 reboots to restore the original which was easier
than editing every /e/hosts file on my local network. A networking
restart totally ignores anything you do in /e/n/i. Sounds crazy and
impossible, but thats how it works here. Depressing is what it is....

[Alan Corey]

Don't really know, on a quick glance I'm not sure where to connect the
battery. But it has a 32 KHz oscillator. The RK805 I think is a chip
on the board, has a clock and several bucks in it. The Rock64
schematic shows it as a power distribution block.

From
http://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf

Looks like it expects 2.8 - 3.5 volts so not a lithium battery. Not
sure if it tries to charge it or not.

You know about their IRC, right?

http://uk.pine64.xyz:9090/?channels=Pine64&uio=MTE9MjE131

Strange URL, there are pine64 and rock64 channels in there.

Post by Gene Heskett

Post by Gene Heskett

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?

The traditional command for that was tzconfig, but these days it
will tell you to run dpkg-reconfigure something...
dpkg-reconfigure tzdata

Worked a treat, thank you.

It's regrettable that dpkg-reconfigure doesn't have something like a
--list command which summarises the packages to which it may be
applied, or even a --search which works by analogy with apt-cache etc.

And if my well aged wet ram is to be trusted, it used to do a lot more
than it is now, only setting two items in the locales now. Or its been
stripped to do the bare minimum on a rock64/arm64. Dunno which, but its
a dissapointment, just like the networking is broken in that it cannot
apply a gateway to a static setup without doing a separate command with
route once its booted. Putting the gateway address into /e/n/i.d/eth0 is
simply ignored. I even moved it to /e/n/i, no effect. Yesterday I tried
changing the static address, took 3 powerdown reboots to actually get
that to take, and 2 reboots to restore the original which was easier
than editing every /e/hosts file on my local network. A networking
restart totally ignores anything you do in /e/n/i. Sounds crazy and
impossible, but thats how it works here. Depressing is what it is....
--
Cheers, Gene Heskett
--
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[Gene Heskett]

Post by Alan Corey
Don't really know, on a quick glance I'm not sure where to connect the
battery. But it has a 32 KHz oscillator. The RK805 I think is a chip
on the board, has a clock and several bucks in it. The Rock64
schematic shows it as a power distribution block.
From
http://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A0
20160921.pdf

I do not see anything there that says battery. And I just checked the
printouts for both bus connectors, no battery called out. That 32khz
crystal is I have to assume, there for clocking the sequencing of system
power for shut down and bootup. Never used off chip from what I can see.

Post by Alan Corey
Looks like it expects 2.8 - 3.5 volts so not a lithium battery. Not
sure if it tries to charge it or not.
You know about their IRC, right?
http://uk.pine64.xyz:9090/?channels=Pine64&uio=MTE9MjE131

Yes, I hit that at least daily. I'm the gene83 there.

Post by Alan Corey
Strange URL, there are pine64 and rock64 channels in there.

Apparently their own irc server.

Thanks Alan.

[Alan Corey]

Yeah, this is maybe the 3rd time I've been on IRC, I guess I've given
up trying to get it to work on my phone. Some of it's interesting
reading. I'm alan01346 on there.

Page 8, "Fig. 1-1 RK805 One Battery Cell Application" is what I meant.
I suppose it's possible it works but most people don't use it so it
isn't well documented. Even in fig 1-1 I can't tell where the battery
is.

It has a sleep mode and an alarm. Page 19 (by xpdf) shows registers
for seconds, minutes, hours, etc. More on page 21-26.

I searched the IRC for battery and found:

26/12/17 01:37
<tl_lim> I can provide circuit how to add 3V battery power to existing
schematic for RTC power
28/02/18 21:23
<Xalius> the white connector is for the RTC battery

Maybe it used to be there, maybe the Pine64 has one, I don't know.
Not sure what I'd use it for, power consumption seems too high for a
portable. But if it's got a clock it makes sense it should have a
battery connector.

Post by Gene Heskett

Post by Alan Corey
Don't really know, on a quick glance I'm not sure where to connect the
battery. But it has a 32 KHz oscillator. The RK805 I think is a chip
on the board, has a clock and several bucks in it. The Rock64
schematic shows it as a power distribution block.
From
http://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A0
20160921.pdf

I do not see anything there that says battery. And I just checked the
printouts for both bus connectors, no battery called out. That 32khz
crystal is I have to assume, there for clocking the sequencing of system
power for shut down and bootup. Never used off chip from what I can see.

Post by Alan Corey
Looks like it expects 2.8 - 3.5 volts so not a lithium battery. Not
sure if it tries to charge it or not.
You know about their IRC, right?
http://uk.pine64.xyz:9090/?channels=Pine64&uio=MTE9MjE131

Yes, I hit that at least daily. I'm the gene83 there.

Post by Alan Corey
Strange URL, there are pine64 and rock64 channels in there.

Apparently their own irc server.
Thanks Alan.
--
Cheers, Gene Heskett
--
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[Gene Heskett]

Post by Alan Corey
Yeah, this is maybe the 3rd time I've been on IRC, I guess I've given
up trying to get it to work on my phone. Some of it's interesting
reading. I'm alan01346 on there.
Page 8, "Fig. 1-1 RK805 One Battery Cell Application" is what I meant.
I suppose it's possible it works but most people don't use it so it
isn't well documented. Even in fig 1-1 I can't tell where the battery
is.
It has a sleep mode and an alarm. Page 19 (by xpdf) shows registers
for seconds, minutes, hours, etc. More on page 21-26.
26/12/17 01:37
<tl_lim> I can provide circuit how to add 3V battery power to existing
schematic for RTC power
28/02/18 21:23
<Xalius> the white connector is for the RTC battery

I would assume this battery is for a ups like function.

And I just noticed something about the armbian release of stretch
available on the pine site. The initial login is as root, meaning one
can probably addusr his own named account as user 1000. This would
solve several problems I believe, so I have that image coming in now,
and if I have time later today I'll burn it to an sd card and give it a
shot. It can't be any worse of a C.F. than the ayufan builds with its
pre-allocated user 1000. Probably defaults to dhcpd for a networking
hookup, and I do have a 2 machine wide server setup in dd-wrt that I can
edit to give it the same address because dd-wrt can bind the address it
hands out to the M.A.C. address of the interface asking for a lease.

In the FWIW dept, I am not powering it thru the coax plug, but tied
directly to the 5v and ground on the headers. Reason? I wasn't sure the
plug I had available to hook up a 5 amp supply was of the correct
polarity. I may verify that with an ohmmeter as the current method looks
like shade tree engineering and could short if miss-handled.

Post by Alan Corey
Maybe it used to be there, maybe the Pine64 has one, I don't know.
Not sure what I'd use it for, power consumption seems too high for a
portable. But if it's got a clock it makes sense it should have a
battery connector.

More than likely a much bigger, rechargeable battery like the pinebook
would use.

Post by Alan Corey

Post by Gene Heskett

Post by Alan Corey
Don't really know, on a quick glance I'm not sure where to connect
the battery. But it has a 32 KHz oscillator. The RK805 I think is
a chip on the board, has a clock and several bucks in it. The
Rock64 schematic shows it as a power distribution block.
From
http://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2
%A0 20160921.pdf

I do not see anything there that says battery. And I just checked
the printouts for both bus connectors, no battery called out. That
32khz crystal is I have to assume, there for clocking the sequencing
of system power for shut down and bootup. Never used off chip from
what I can see.

Post by Alan Corey
Looks like it expects 2.8 - 3.5 volts so not a lithium battery.
Not sure if it tries to charge it or not.
You know about their IRC, right?
http://uk.pine64.xyz:9090/?channels=Pine64&uio=MTE9MjE131

Yes, I hit that at least daily. I'm the gene83 there.

Post by Alan Corey
Strange URL, there are pine64 and rock64 channels in there.

Apparently their own irc server.
Thanks Alan.
--
Cheers, Gene Heskett
--
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[John Holland]

Post by Gene Heskett
shot. It can't be any worse of a C.F. than the ayufan builds with its
pre-allocated user 1000.

Although having a preallocated user 1000 is the standard "Debian Way", the objective being that you can telnet (later SSH) in using that user and then sudo su to get root (fouled up on some versions that don't add user 1000 to sudoers). For quite a long time

The same effect can be achieved by supplementing the user in question with the group sudo. With that there is no need to edit sudoers.

John

[Gene Heskett]

Post by John Holland

Post by Gene Heskett
shot. It can't be any worse of a C.F. than the ayufan builds with
its pre-allocated user 1000.

Although having a preallocated user 1000 is the standard "Debian
Way", the objective being that you can telnet (later SSH) in using
that user and then sudo su to get root (fouled up on some versions
that don't add user 1000 to sudoers). For quite a long time

The same effect can be achieved by supplementing the user in question
with the group sudo. With that there is no need to edit sudoers.
John

But that does not fix the x server being locked and unusable when logged
in from a comfy chair because user 1000 is not the same name. So you
are limited to ncurses at best for a gui. And that sucks somewhere
around 10-35 Torr.

[Gene Heskett]

Post by Gene Heskett

Post by John Holland

Post by Gene Heskett
shot. It can't be any worse of a C.F. than the ayufan builds with
its pre-allocated user 1000.

Although having a preallocated user 1000 is the standard "Debian
Way", the objective being that you can telnet (later SSH) in using
that user and then sudo su to get root (fouled up on some
versions that don't add user 1000 to sudoers). For quite a long
time

The same effect can be achieved by supplementing the user in
question with the group sudo. With that there is no need to edit
sudoers.
John

But that does not fix the x server being locked and unusable when
logged in from a comfy chair because user 1000 is not the same name.
So you are limited to ncurses at best for a gui. And that sucks
somewhere around 10-35 Torr.

Gene, what /exactly/ are you complaining about here? if it's simply
that you can't get a GUI login as root from your system console then
that's a display manager thing which should be fixable.

First I am logging in as user 1000, aka pi on the pi and rock64 on the
rock64. Root logins are disallowed. I can sudo later, but can't run
anything that needs x, getting the can't open display :11 or some such
twaddle error. And I've no clue if ts this wheezy machine, or that
jessie or stretch machine reporting the error I see on my konsole here
on wheezy.

copy/paste quote:

***@coyote:~$ ssh -Y ***@rock64
***@rock64's password:
X11 forwarding request failed on channel 0

Whoever is responsible for that, needs to meet a Louisville Slugger just
above the ear.

I can run any x app, from wheezy on x86 to wheezy on x86, but wheezy to
jessie on the pi is locked out, and wheezy to stretch on the rock64 is
locked out as you can see above.

3 usernames, all user 1000, but that apparently doesn't mean squat to X,
identical user numbers notwithstanding.

That means I must go to that machines keyboard to do anything that needs
X. And that means standing up, and my 83 yo back is killing me in 10
minutes. So it should be understandable that its a very sore point to
me.

With dd-wrt's sharp teeth being the gateway to the internet, security is
the last concern, no one not given the login credentials has been able
to get in, in at least 15 years.

The local net is mine and I am the only user, so why the hell can't I do
what I need to do from a comfy chair?

Good question that. If you know how to fix it, please share.

[Lennart Sorensen]

Post by Gene Heskett
First I am logging in as user 1000, aka pi on the pi and rock64 on the
rock64. Root logins are disallowed. I can sudo later, but can't run
anything that needs x, getting the can't open display :11 or some such
twaddle error. And I've no clue if ts this wheezy machine, or that
jessie or stretch machine reporting the error I see on my konsole here
on wheezy.

Once you su or sudo you no longer have permission to access X. If you
want that use gksudo or kdesudo which handle keeping access to X while
switching to root.

[Lennart Sorensen]

Sudo's -E option very often helps.

Well that still doesn't work because you need the right cookies for X
to work.

With kdesu or kdesudo or gksudo it does work.

[Gene Heskett]

Post by Lennart Sorensen

Post by Gene Heskett
First I am logging in as user 1000, aka pi on the pi and rock64 on
the rock64. Root logins are disallowed. I can sudo later, but can't
run anything that needs x, getting the can't open display :11 or
some such twaddle error. And I've no clue if ts this wheezy
machine, or that jessie or stretch machine reporting the error I see
on my konsole here on wheezy.

Once you su or sudo you no longer have permission to access X. If you
want that use gksudo or kdesudo which handle keeping access to X while
switching to root.

As I keep repeating, x is TOTALLY not available to the common user. I
need to set that up as an auto reply I guess. All the good editors, and
I'm fond of geany, but neither geany, kate nor kwrite are available,
they need x and bailout when they're are denied its use, so I'm stuck
with nano, and its half a screen vertical jump for a scroll drives me
plumb out of my skull, spending 95% of my time looking for the damned
curser. No way in hell you can write good code with that distraction.

I'm running out of patience, everyone is reading what they *think* I
wrote, then answering that question I didn't ask. That is not helpfull
and just confuses the next person that replies to what ought to be a new
thread, its that far from the actual subject.

[Lennart Sorensen]

Post by Gene Heskett
As I keep repeating, x is TOTALLY not available to the common user. I
need to set that up as an auto reply I guess. All the good editors, and
I'm fond of geany, but neither geany, kate nor kwrite are available,
they need x and bailout when they're are denied its use, so I'm stuck
with nano, and its half a screen vertical jump for a scroll drives me
plumb out of my skull, spending 95% of my time looking for the damned
curser. No way in hell you can write good code with that distraction.
I'm running out of patience, everyone is reading what they *think* I
wrote, then answering that question I didn't ask. That is not helpfull
and just confuses the next person that replies to what ought to be a new
thread, its that far from the actual subject.

(Went back and reread the thread...)

When you said you had isses with ssh -Y not allow X connections...

Check that /etc/ssh/sshd_config on the rock64 has these settings:

X11Forwarding yes
X11UseLocalhost no

And that the package 'xauth' is installed.

Either of those missing will prevent ssh from forwarding X connections.

What the name of user 1000 is has nothing to do with it (Only really
NFS has issues with uid's not matching between machines and there are
ways to deal with that too).

[Gene Heskett]

Post by Lennart Sorensen

Post by Gene Heskett
As I keep repeating, x is TOTALLY not available to the common user.
I need to set that up as an auto reply I guess. All the good
editors, and I'm fond of geany, but neither geany, kate nor kwrite
are available, they need x and bailout when they're are denied its
use, so I'm stuck with nano, and its half a screen vertical jump for
a scroll drives me plumb out of my skull, spending 95% of my time
looking for the damned curser. No way in hell you can write good
code with that distraction.
I'm running out of patience, everyone is reading what they *think* I
wrote, then answering that question I didn't ask. That is not
helpfull and just confuses the next person that replies to what
ought to be a new thread, its that far from the actual subject.

(Went back and reread the thread...)
When you said you had isses with ssh -Y not allow X connections...
X11Forwarding yes
X11UseLocalhost no
And that the package 'xauth' is installed.
Either of those missing will prevent ssh from forwarding X
connections.

Do I have to reboot it (the rock64) after makeing everything as above?
Logging out, and back in does not shut the error message off.

***@coyote:~$ ssh -Y ***@rock64
***@rock64's password:
X11 forwarding request failed on channel 0

Post by Lennart Sorensen
What the name of user 1000 is has nothing to do with it (Only really
NFS has issues with uid's not matching between machines and there are
ways to deal with that too).

Well, something is makeing sure I can't do anything from any keyboard but
the machines own keyboard and monitor.

Thanks Lennart, you actually tried to answer my question, and I
appreciate it.

[Tixy]

Post by Gene Heskett

Post by Lennart Sorensen
When you said you had isses with ssh -Y not allow X connections...
X11Forwarding yes
X11UseLocalhost no
And that the package 'xauth' is installed.
Either of those missing will prevent ssh from forwarding X
connections.

Do I have to reboot it (the rock64) after makeing everything as
above?  
Logging out, and back in does not shut the error message off.

I expect you'll need to restart the ssh daemon, e.g as root:

# service ssh restart

Not sure if that works on machines with systemd. You could just reboot
in either case.

[Gene Heskett]

Post by Tixy

Post by Gene Heskett

Post by Lennart Sorensen
When you said you had isses with ssh -Y not allow X connections...
X11Forwarding yes
X11UseLocalhost no
And that the package 'xauth' is installed.
Either of those missing will prevent ssh from forwarding X
connections.

Do I have to reboot it (the rock64) after makeing everything as
above?  
Logging out, and back in does not shut the error message off.

# service ssh restart

And that works, geany now runs on the rock64 from an ssh login!!!.
Now to see if the pi can be fixed, but the second of those two commands
does not exist in /etc/ssh/sshd_config on the pi, even commented out.
And when added, results in a login with no shell prompt. So I used
another login already established to remove that line again, but a ssh
restart, logout and log back in does not get me a shell prompt after
entering the password. So now I am locked out of the pi due to lack of
a shell. But the rock64 now gives me x exports.

Thank you. I'll go reboot the pi and see if that helps as its sshd_config
should be restored to where it started from now. But that is several
hours away as its only 4:22 local time.

Post by Tixy
Not sure if that works on machines with systemd. You could just reboot
in either case.

[Lennart Sorensen]

Post by Gene Heskett
And that works, geany now runs on the rock64 from an ssh login!!!.
Now to see if the pi can be fixed, but the second of those two commands
does not exist in /etc/ssh/sshd_config on the pi, even commented out.
And when added, results in a login with no shell prompt. So I used
another login already established to remove that line again, but a ssh
restart, logout and log back in does not get me a shell prompt after
entering the password. So now I am locked out of the pi due to lack of
a shell. But the rock64 now gives me x exports.

Great. Some progress finally.

[Gene Heskett]

Post by Lennart Sorensen

Post by Gene Heskett
And that works, geany now runs on the rock64 from an ssh login!!!.
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
commented out. And when added, results in a login with no shell
prompt. So I used another login already established to remove that
line again, but a ssh restart, logout and log back in does not get
me a shell prompt after entering the password. So now I am locked
out of the pi due to lack of a shell. But the rock64 now gives me x
exports.

Great. Some progress finally.

Yep, and I've made it work for an armbian install this morning too!

Big grin.

But I had a heck of a time getting a gateway to "stick" thats very
fragile. Seems there is more stuffs now required in /e/n/i.d/eth0 than
before, and no 100% reliable way to get it all started, so while its now
working, I'd have to say its fragile yet using the new way.

But now, moving 15 feet to the pi, trying to do it on the pi, which is
running a jessie install, I've lost the shell after a login. So my
logins are useless. They echo what I type, but nothing see's the return
except the echoing linefeed.

So kind people, whats next to check?

[Gene Heskett]

Post by Gene Heskett

Post by Lennart Sorensen

Post by Gene Heskett
And that works, geany now runs on the rock64 from an ssh login!!!.
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
commented out. And when added, results in a login with no shell
prompt. So I used another login already established to remove that
line again, but a ssh restart, logout and log back in does not get
me a shell prompt after entering the password. So now I am locked
out of the pi due to lack of a shell. But the rock64 now gives me
x exports.

Great. Some progress finally.

Yep, and I've made it work for an armbian install this morning too!
Big grin.
But I had a heck of a time getting a gateway to "stick" thats very
fragile. Seems there is more stuffs now required in /e/n/i.d/eth0
than before, and no 100% reliable way to get it all started, so
while its now working, I'd have to say its fragile yet using the new
way.

Extra stuff /such/ /as/? I find this
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.19/24
# dns-* options are implemented by the resolvconf package, if
installed
dns-nameservers 192.168.1.1
dns-search telemetry.co.uk
to be entirely adequate for /etc/network/interfaces on Raspbian and
Debian Stretch, except possibly for the TinkerBoard I was looking at a
few days ago.

Post by Gene Heskett
But now, moving 15 feet to the pi, trying to do it on the pi, which
is running a jessie install, I've lost the shell after a login. So
my logins are useless. They echo what I type, but nothing see's the
return except the echoing linefeed.
So kind people, whats next to check?

Please describe the problem exactly. Most of us are reading this while
working etc., assume our memory is limited.
Debian or Raspbian Jessie? Main console? Text? GUI? Manual or auto
login? SSH? What shell? and so on.

raspian jessie, manual ssh -Y login from remote machine on same local
subnet/24 with pw's, /bin/bash in the pw file.

I get the pw requester, answer it, get the login blurb I assume
from /etc/issue.net, but then no shell prompt in the remote term
emulator, and a ctrl-d is also ignored. Kill the tab is the only way
out. Thinking I had hit some limit on this machine. or on the pi, I got
exactly the same results from the rock64's keyboard before and after
rebooting the pi.

So whats next?

[Gene Heskett]

Post by Gene Heskett
I get the pw requester, answer it, get the login blurb I assume
from /etc/issue.net, but then no shell prompt in the remote term
emulator, and a ctrl-d is also ignored. Kill the tab is the only way
out. Thinking I had hit some limit on this machine. or on the pi, I
got exactly the same results from the rock64's keyboard before and
after rebooting the pi.
So whats next?

So you get the password prompt which is actually issued by your SSH
client. The two things I'd suggest are (i) if you have one use a shell
session on the local console to run something like ps faux | less so
you can see whether the ssh daemon's stuck running something. Look in
/var/log/messages etc. Try ssh without the -Y then again with the -v
option.
Sorry for being concise, but evening passes and I've spent all day on
RPi OSes and several nay many days trying to sort out throughput
issues... SSH login should /not/ be a problem.

The only thing I can see that sshd related:

/usr/sbin/sshd -D
\ sshd: pi [priv]
\ sshd: ***@pts/1
\ /bin/bash

There was one other entry, clear at the bottom of a lengthy list:
sshd
\ bin/bash but I think that was the terminal I was using. Or is that
the hung one??? dunno.

I hope that effort bears fruit, this and another r-pi 3b has had a habit
of throwing away local keyboard and mouse events. Another reboot might
fix it, and then again it might be worse. But I expect this is a
different breed of horse. I update everything but the kernel (its pinned
as its as close to an RTAI kernel as anyone so far has built for an
r-pi) a couple times a week, and its not bothered me in a few weeks. So
maybe thats been fixed.

Also, setting the keyboard repeat from the gui, only lasts till a reboot,
at which time it goes back up to at least 100/second, maybe more.

Thank you Mark.

[Gene Heskett]

Post by Gene Heskett

So you get the password prompt which is actually issued by your SSH
client. The two things I'd suggest are (i) if you have one use a
shell session on the local console to run something like ps faux |
less so you can see whether the ssh daemon's stuck running
something. Look in /var/log/messages etc. Try ssh without the -Y
then again with the -v option.
Sorry for being concise, but evening passes and I've spent all day
on RPi OSes and several nay many days trying to sort out throughput
issues... SSH login should /not/ be a problem.

/usr/sbin/sshd -D
\ sshd: pi [priv]
\ /bin/bash
sshd
\ bin/bash but I think that was the terminal I was using. Or is
that the hung one??? dunno.

And what does ssh -v tell you?
In the shell session you're using try echo $$ which will give you
the PID of that instance of bash, and then see where that appears in
ps faux output.

I can do that,

Post by Gene Heskett
I hope that effort bears fruit, this and another r-pi 3b has had a
habit of throwing away local keyboard and mouse events. Another
reboot might fix it, and then again it might be worse. But I expect
this is a different breed of horse.

Loading Image...

Chuckle.

But that ps output does appear to imply that you've got a running
shell, so the question might be moving from sshd towards something
silly like an endless loop in your .bashrc

Thats not been touched by me in nearly a year. But I'll go look anyway.

And here is an interesting observation, a lowercase -y works, the
uppercase doesn't:
***@coyote:~/Public/rock64-next-try$ ssh -y ***@picnc
***@picnc's password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Jul 24 17:56:59 2018 from coyote.coyote.den
***@picnc:~ $

But I don't get that final ***@picnc if I use the uppercase -Y. That
ought to help pin it down I'd think. But maybe not, but the manpage
on this machine says its a log path control.

This manpage says ForwardX11Trusted, but it does not exist in that jessie
machine sshd_config

And now with all the fooling around, I can't restart the ssh service on
this machine, getting this error:
***@coyote:~/Public/rock64-next-try$ service ssh start
[....] Starting OpenBSD Secure Shell server: sshdCould not load host
key: /etc/ssh/ssh_host_rsa_key
Could not load host key: /etc/ssh/ssh_host_dsa_key
. ok

I think I'd better quit while I still have a network.
but do they exist?: yes:
***@coyote:~/Public/rock64-next-try$ ls -l /etc/ssh
total 272
-rw-r--r-- 1 root root 242091 Apr 30 2014 moduli
-rw-r--r-- 1 root root 1733 Nov 27 2016 ssh_config
-rw-r--r-- 1 root root 2557 Nov 27 2016 sshd_config
-rw------- 1 root root 668 Feb 3 2015 ssh_host_dsa_key
-rw-r--r-- 1 root root 601 Feb 3 2015 ssh_host_dsa_key.pub
-rw------- 1 root root 227 Feb 3 2015 ssh_host_ecdsa_key
-rw-r--r-- 1 root root 173 Feb 3 2015 ssh_host_ecdsa_key.pub
-rw------- 1 root root 1675 Feb 3 2015 ssh_host_rsa_key
-rw-r--r-- 1 root root 393 Feb 3 2015 ssh_host_rsa_key.pub

So I am lost. Thanks Mark.

[Gene Heskett]

Post by Gene Heskett

Post by Tixy

Post by Gene Heskett

Post by Lennart Sorensen
When you said you had isses with ssh -Y not allow X
connections...
X11Forwarding yes
X11UseLocalhost no
And that the package 'xauth' is installed.
Either of those missing will prevent ssh from forwarding X
connections.

Do I have to reboot it (the rock64) after makeing everything as
above?
Logging out, and back in does not shut the error message off.

# service ssh restart

And that works, geany now runs on the rock64 from an ssh login!!!.

And I have succeeded in making it work all over again on an armbian
install this morning. Big grin. And on this install, I am indeed me as
user 1000!

Post by Gene Heskett
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
there but commented out.

But I have not made it work on the pi, with or without the
X11UseLocalhost no (the default it says)
line, i get a login requestor, enter my pw, and get the login blurb, but
then no shell. I have not rebooted the pi, I guess thats next...

Didn't help, I can login from here, or from the new armbian install on
the rock64, but I get no shell after the signed in blurb. And
the /etc/passwd says I get /bin/bash...

Anybody have an idea on this new development?

[Alan Corey]

So you're running an X session tunneled through ssh and then trying to
log in by ssh inside that? I'm way out of my league here, but what do
you get in response to just typing env? Should show all your
environment variables, including SHELL, TERM, DISPLAY, USER, HOME,
PATH, etc. You may have inherited a weird environment, or an empty
(null) one.

Post by Gene Heskett

Post by Gene Heskett
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
there but commented out.

But I have not made it work on the pi, with or without the
X11UseLocalhost no (the default it says)
line, i get a login requestor, enter my pw, and get the login blurb, but
then no shell. I have not rebooted the pi, I guess thats next...
Didn't help, I can login from here, or from the new armbian install on
the rock64, but I get no shell after the signed in blurb.

Let's try to make some sense of this. You've got /what/ /exactly/
running on the RPi: Raspbian Jessie?
Can you log in using an attached screen/keyboard? As both GUI and text
(i.e. in the latter case using <Ctrl><Alt><F1> to get a text login
prompt)? Can you either login as root or do a sudo su or whatever?
Does ifconfig tell you that the expected interface exists and has the
expected address?

Post by Gene Heskett
And the /etc/passwd says I get /bin/bash...

No it doesn't, it says that it's to use it provided that it's installed.
Does /bin/bash exist? Does the home directory exist (that's a very
common problem)?
Now provided that the above is OK, let's look at SSH which is what I
/think/ you're asking about. Presumably you can ping the RPi and get a
response back (i.e. your route is OK), what /exactly/ happens when you
try to SSH to it? Does ssh -v throw any light on it? Can you try from a
PC rather than your Rock64?
Logging into Raspbian Jessie is something I do on a very regular basis.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]

[Gene Heskett]

Post by Alan Corey
So you're running an X session tunneled through ssh and then trying to
log in by ssh inside that? I'm way out of my league here, but what do
you get in response to just typing env? Should show all your
environment variables, including SHELL, TERM, DISPLAY, USER, HOME,
PATH, etc. You may have inherited a weird environment, or an empty
(null) one.

I'll look at that after I've fed us dinner.

Post by Alan Corey

Post by Gene Heskett

Post by Gene Heskett
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
there but commented out.

But I have not made it work on the pi, with or without the
X11UseLocalhost no (the default it says)
line, i get a login requestor, enter my pw, and get the login
blurb, but then no shell. I have not rebooted the pi, I guess thats
next...
Didn't help, I can login from here, or from the new armbian install
on the rock64, but I get no shell after the signed in blurb.

Let's try to make some sense of this. You've got /what/ /exactly/
running on the RPi: Raspbian Jessie?
Can you log in using an attached screen/keyboard? As both GUI and
text (i.e. in the latter case using <Ctrl><Alt><F1> to get a text
login prompt)? Can you either login as root or do a sudo su or
whatever? Does ifconfig tell you that the expected interface exists
and has the expected address?

Post by Gene Heskett
And the /etc/passwd says I get /bin/bash...

No it doesn't, it says that it's to use it provided that it's
installed. Does /bin/bash exist? Does the home directory exist
(that's a very common problem)?
Now provided that the above is OK, let's look at SSH which is what I
/think/ you're asking about. Presumably you can ping the RPi and get
a response back (i.e. your route is OK), what /exactly/ happens when
you try to SSH to it? Does ssh -v throw any light on it? Can you try
from a PC rather than your Rock64?
Logging into Raspbian Jessie is something I do on a very regular basis.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]

[Gene Heskett]

Post by Gene Heskett

Post by Gene Heskett
Now to see if the pi can be fixed, but the second of those two
commands does not exist in /etc/ssh/sshd_config on the pi, even
there but commented out.

But I have not made it work on the pi, with or without the
X11UseLocalhost no (the default it says)
line, i get a login requestor, enter my pw, and get the login blurb,
but then no shell. I have not rebooted the pi, I guess thats next...
Didn't help, I can login from here, or from the new armbian install
on the rock64, but I get no shell after the signed in blurb.

Let's try to make some sense of this. You've got /what/ /exactly/
running on the RPi: Raspbian Jessie?
Can you log in using an attached screen/keyboard? As both GUI and text
(i.e. in the latter case using <Ctrl><Alt><F1> to get a text login
prompt)? Can you either login as root or do a sudo su or whatever?
Does ifconfig tell you that the expected interface exists and has the
expected address?

Post by Gene Heskett
And the /etc/passwd says I get /bin/bash...

No it doesn't, it says that it's to use it provided that it's
installed. Does /bin/bash exist?

yes

Does the home directory exist (that's
a very common problem)?

yes

Lots of other bash code just runs. And it "/bin/bash" exists/.

Now provided that the above is OK, let's look at SSH which is what I
/think/ you're asking about. Presumably you can ping the RPi and get a
response back (i.e. your route is OK), what /exactly/ happens when you
try to SSH to it? Does ssh -v throw any light on it? Can you try from
a PC rather than your Rock64?

Same exact results logging into it from this box, a 32 bit wheezy, as
uptodate as it can be since support stopped on June 30 I think.
haven't tried the ssh -v, which machine? The output of service ssh
status, on the pi looks legit as its the log of successfull stuff from
the data there.

Since I am careing for an invalid wife, I'd better go fix us something to
eat, later Mark, and thank you.

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>

[Gene Heskett]

Post by Gene Heskett
haven't tried the ssh -v, which machine? The output of service ssh
status, on the pi looks legit as its the log of successfull stuff
from the data there.

On the machine you run ssh on, obviously (That's "ssh" the command,
not "SSH" the protocol etc. :-)

Post by Gene Heskett
Since I am careing for an invalid wife, I'd better go fix us
something to eat, later Mark, and thank you.

Dagnabbit Gene, I wish there weren't two ways of pronouncing that word
:-)

Which word? The invalid is that she is deep enough into copd that her
remaining time is limited, and she cannot quit smoking. Tried several
times, gets bored and goes thru another pack in 5 or 6 hours. On oxygen
obviously.

But she is still a VALID wife, of 29 years this December. Shes 78 and I'm
83 and its obvious to me that I'm fading too. I had a pulmonary embolism
3 years ago, usually fatal, but it did cost me a few IQ points, dammit.
That guy who could pick up 200 lbs in each hand and walk it all over
town 60 years ago? He now has a couple crushed disks in his lower back
and needs help with a 30lb lathe chuck. Don't get old if you can help
it, its not the fun AARP tries to sell you. :(

Take care.

[Lennart Sorensen]

Post by Gene Heskett
Do I have to reboot it (the rock64) after makeing everything as above?
Logging out, and back in does not shut the error message off.
X11 forwarding request failed on channel 0

Restarting sshd would be required.

Post by Gene Heskett

Post by Lennart Sorensen
What the name of user 1000 is has nothing to do with it (Only really
NFS has issues with uid's not matching between machines and there are
ways to deal with that too).

Well, something is makeing sure I can't do anything from any keyboard but
the machines own keyboard and monitor.
Thanks Lennart, you actually tried to answer my question, and I
appreciate it.

Well somehow I missed what the original problem was initially.

[Philip Hands]

Post by John Holland

Post by Gene Heskett
shot. It can't be any worse of a C.F. than the ayufan builds with its
pre-allocated user 1000.

Although having a preallocated user 1000 is the standard "Debian Way", the objective being that you can telnet (later SSH) in using that user and then sudo su to get root (fouled up on some versions that don't add user 1000 to sudoers). For quite a long time

The same effect can be achieved by supplementing the user in question
with the group sudo. With that there is no need to edit sudoers.

Presumably the system had a root password set at first install. That is
what normally determines whether the first user created at install time
is added to the sudo group or not -- having no root password provokes a
user with sudo access, so that there is still some way of becoming root.

If you're doing it by hand, just run this as root (assuming a user 'phil'):

adduser phil sudo

As for the question of remote root ssh access -- by default in the
debian ssh package that is now only allowed using keys, rather than
password, so you need to copy your .pub over to:

/root/.ssh/authorized_keys

on the target system to get in as root.

Cheers, Phil.

[Gene Heskett]

Post by Philip Hands

Post by John Holland

Post by Gene Heskett
shot. It can't be any worse of a C.F. than the ayufan builds with
its pre-allocated user 1000.

Although having a preallocated user 1000 is the standard "Debian
Way", the objective being that you can telnet (later SSH) in using
that user and then sudo su to get root (fouled up on some
versions that don't add user 1000 to sudoers). For quite a long
time

The same effect can be achieved by supplementing the user in
question with the group sudo. With that there is no need to edit
sudoers.

Presumably the system had a root password set at first install. That
is what normally determines whether the first user created at install
time is added to the sudo group or not -- having no root password
provokes a user with sudo access, so that there is still some way of
becoming root.
adduser phil sudo
As for the question of remote root ssh access -- by default in the
debian ssh package that is now only allowed using keys, rather than
/root/.ssh/authorized_keys
on the target system to get in as root.

But I don't want to login as root! I've said as much several times. If I
need to be root, there is always sudo -i for long enough. Like to change
the ownership of a plugin drive so I as user 1000 can build a realtime
kernel as the user. Recommended practice BTW.

Post by Philip Hands
Cheers, Phil.

[Cindy-Sue Causey]

Post by Gene Heskett

Post by Gene Heskett
I have a bunch of locale related errors too.
Was a stretch-minimal install by ayufan, has xfce for desktop
What am I missing?

The traditional command for that was tzconfig, but these days it will
tell you to run dpkg-reconfigure something...
dpkg-reconfigure tzdata

Worked a treat, thank you.

It's regrettable that dpkg-reconfigure doesn't have something like a
--list command which summarises the packages to which it may be applied,
or even a --search which works by analogy with apt-cache etc.

There's always the option of submitting something like that as a
reportbug wishlist item. I verified first using grub-pc. Had to flip
through over 500 bugs (*OUCH!*) to get to the point where you choose
wishlist, but it *is* there in the options regarding a bug report's
severity level.

Cindy :)