NodeFirstUnitarian updates
3 views
Skip to first unread message
Russell Senior
Apr 30, 2017, 7:55:17 PM4/30/17
to ops list
A while ago, I noticed problems with the old Soekris net4826 devices
with booting problems, particularly from a warm boot. This didn't
show up in my test bed. The primary difference between the test bed
and the deployed devices was that I have serial consoles on the test
bed. Checking that, it was indeed the source of the problem. Grub
was hanging at the boot menu if there was no serial console connected.
We saw this at First Unitarian and (iirc) at one of the devices on
NodeMississippi.
Yesterday, I was supposed to be doing something else, so instead spent
some time chasing down this problem, partly documented here:
https://bugs.lede-project.org/index.php?do=details&task_id=744
I tried a series of images I built, and had to go back a couple years
ago before I found one that worked without a serial console connected.
After poking around a bit, I made a wild if slightly educated guess
that CONFIG_GRUB_CONSOLE might be related. I tried turning that off,
and presto-chango, problem solved. So, after some testing in my
basement, early this morning, I updated the image on
ap2.firstunitarian.ptp (the Soekris net4826 that is on the bell tower
at First Unitarian Church). It came back up cleanly, and I think we
can conclude that problem is probably solved.
That's all.
--
Russell Senior, President
rus...@personaltelco.net
with booting problems, particularly from a warm boot. This didn't
show up in my test bed. The primary difference between the test bed
and the deployed devices was that I have serial consoles on the test
bed. Checking that, it was indeed the source of the problem. Grub
was hanging at the boot menu if there was no serial console connected.
We saw this at First Unitarian and (iirc) at one of the devices on
NodeMississippi.
Yesterday, I was supposed to be doing something else, so instead spent
some time chasing down this problem, partly documented here:
https://bugs.lede-project.org/index.php?do=details&task_id=744
I tried a series of images I built, and had to go back a couple years
ago before I found one that worked without a serial console connected.
After poking around a bit, I made a wild if slightly educated guess
that CONFIG_GRUB_CONSOLE might be related. I tried turning that off,
and presto-chango, problem solved. So, after some testing in my
basement, early this morning, I updated the image on
ap2.firstunitarian.ptp (the Soekris net4826 that is on the bell tower
at First Unitarian Church). It came back up cleanly, and I think we
can conclude that problem is probably solved.
That's all.
--
Russell Senior, President
rus...@personaltelco.net
Russell Senior
May 1, 2017, 6:03:10 AM5/1/17
to ops list
>>>>> "Russell" == Russell Senior <rus...@personaltelco.net> writes:
Russell> A while ago, I noticed problems with the old Soekris net4826
Russell> devices with booting problems, [...]
NodeMississippi net4826 devices (that are connected): metrix-west,
metrix-commons and metrix-ballroom, have also been updated as of a few
minutes ago. The monitor-link.sh infrastructure needed some updating,
since some of the sysfs/debugfs interface files I had been using were
removed upstream. So much for not breaking userspace. ;-)
Anyway, it's working again. Maybe slightly better than before, but I'm
not claiming too much.
The last metrix, metrix-ed, has been offline for a while. We had high
hopes of updating some of the hardware on the network a year or so ago,
but the project kind of stalled. Maybe with the upcoming summer
weather, we can take another run at it, and maybe get Ed back online at
the same time.
Russell> A while ago, I noticed problems with the old Soekris net4826
Russell> devices with booting problems, [...]
NodeMississippi net4826 devices (that are connected): metrix-west,
metrix-commons and metrix-ballroom, have also been updated as of a few
minutes ago. The monitor-link.sh infrastructure needed some updating,
since some of the sysfs/debugfs interface files I had been using were
removed upstream. So much for not breaking userspace. ;-)
Anyway, it's working again. Maybe slightly better than before, but I'm
not claiming too much.
The last metrix, metrix-ed, has been offline for a while. We had high
hopes of updating some of the hardware on the network a year or so ago,
but the project kind of stalled. Maybe with the upcoming summer
weather, we can take another run at it, and maybe get Ed back online at
the same time.
Reply all
Reply to author
Forward
0 new messages