Aktuelles
Digital Eliteboard - Das Digitale Technik Forum

Registriere dich noch heute kostenlos, um Mitglied zu werden! Sobald du angemeldet bist, kannst du auf unserer Seite aktiv teilnehmen, indem du deine eigenen Themen und Beiträge erstellst und dich über deinen eigenen Posteingang mit anderen Mitgliedern unterhalten kannst! Zudem bekommst du Zutritt zu Bereichen, welche für Gäste verwehrt bleiben

Registriere dich noch heute kostenlos, um Mitglied zu werden! Sobald du angemeldet bist, kannst du auf unserer Seite aktiv teilnehmen, indem du deine eigenen Themen und Beiträge erstellst und dich über deinen eigenen Posteingang mit anderen Mitgliedern unterhalten kannst! Zudem bekommst du Zutritt zu Bereichen, welche für Gäste verwehrt bleiben

BeagleBone Black Image

    Nobody is reading this thread right now.
AW: Re: AW: Re: AW: BeagleBone Black Image

Please show the output of following commands with dhcp on
Code:
ifconfig
route
cat /etc/resolv.conf
I only use static address without any problems.
 
Zuletzt bearbeitet von einem Moderator:
As you ask, from the BBB (internal) in DHCP-mode on;
login as: root
root@192.168.1.11's password:
=================================
= =
= O S C A M - S E R V E R =
= =
=================================
root@oscam-server:~# ifconfig

eth0 Link encap:Ethernet Hardware Adresse 1c:ba:8c:a2:38:18
inet Adresse:192.168.1.11 Bcast:192.168.1.255 Maske:255.255.255.0
inet6-Adresse: fe80::1eba:8cff:fea2:3818/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:222 errors:0 dropped:0 overruns:0 frame:0
TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:18405 (17.9 KiB) TX bytes:10822 (10.5 KiB)
Interrupt:172

lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:65536 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@oscam-server:~# route

Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
default mijnmodem.kpn 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0

root@oscam-server:~# cat /etc/resolv.conf

nameserver 192.168.1.254
 
Zuletzt bearbeitet von einem Moderator:
AW: Re: BeagleBone Black Image

Please try this:
Code:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.88
netmask 255.255.255.0
gateway 192.168.1.254
Are you sure that BBB is the only device with this ip address ?
 
Zuletzt bearbeitet von einem Moderator:
@supamicha, thanks for quick reply.
Will give it a try tonight.

Tonight, the BBB wit new snapshot works perfectly.
But it was stopped this morning.


Quick the @supamicha snapshot from august loaded and saw this;
root@oscam-server:~# apt-get install fake-hwclock

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Vorgeschlagene Pakete: ntp
Die folgenden Pakete werden aktualisiert (Upgrade): fake-hwclock
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 117 nicht aktualisiert.
15 nicht vollständig installiert oder entfernt.
Es müssen noch 0 B von 6.358 B an Archiven heruntergeladen werden.
Nach dieser Operation werden 15,4 kB Plattenplatz zusätzlich benutzt.
libc-bin (2.19-11) wird eingerichtet ...
(Lese Datenbank ... 22020 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../fake-hwclock_0.8_all.deb ...
Entpacken von fake-hwclock (0.8) über (0.5) ...
Trigger für man-db (2.6.7.1-1) werden verarbeitet ...
libasan1:armhf (4.9.1-18) wird eingerichtet ...
libatomic1:armhf (4.9.1-18) wird eingerichtet ...
libgmp10:armhf (2:6.0.0+dfsg-6) wird eingerichtet ...
libgomp1:armhf (4.9.1-18) wird eingerichtet ...
libubsan0:armhf (4.9.1-18) wird eingerichtet ...
kmod (18-3) wird eingerichtet ...
libc-dev-bin (2.19-11) wird eingerichtet ...
linux-libc-dev:armhf (3.16.5-1) wird eingerichtet ...
libc6-dev:armhf (2.19-11) wird eingerichtet ...
binutils (2.24.90.20141014-1) wird eingerichtet ...
cpp-4.9 (4.9.1-18) wird eingerichtet ...
libgcc-4.9-dev:armhf (4.9.1-18) wird eingerichtet ...
gcc-4.9 (4.9.1-18) wird eingerichtet ...
zlib1g-dev:armhf (1:1.2.8.dfsg-2) wird eingerichtet ...
fake-hwclock (0.8) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/init.d/fake-hwclock wird installiert ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Trigger für libc-bin (2.19-11) werden verarbeitet ...
As you know, I use in rc.local;
#!/bin/sh -e
#
# rc.local
shutdown -r 05:00
exit 0

In the new snapshot you will use already the latest fake-hwclock.
Could maybe my shutdown line disturb the parameters or configuration of static IP and clock functions in your latest snapshot ?
 
Zuletzt bearbeitet von einem Moderator:
AW: Re: BeagleBone Black Image

BBB has no hardware clock and when you put shutdown in your rc.local and fake-hwclock sets wrong time at system start i think it is possible that your bone hangs up.
Try to start a small script in rc.local which starts shutdown after syncing time from ntp. Why do you need a restart every day ?

I use static ip in my bone and i have no problems with it. I do not think it is a time problem.
 
Re: AW: Re: BeagleBone Black Image

Indeed, it is not time problem.
Yesterday evening, the newest snapshot with the simpel static lines flashed into the BBB; :emoticon-0169-dance
address 192.168.1.88
netmask 255.255.255.0
gateway 192.168.1.254

Till this morning the new snapshot works like a charm until I try a cold reboot only. (after 8 hours from start)
From that moment the new snapshot (without "reboot" into rc.local ! :D ) the BBB starts again and again.
Reason for test was the free-memory decreasing from 440 to 358 Mb, with the august snapshot it is always
from 440 to 390 MB in a day (the reason why the restart each day)

Directly flashed with the august snapshot (the 2014-10-17 snapshot don't works as I told already) and works
still perfectly during 9 hours (reboot 3x and 2x coldboot as a test). (August snapshot works Okay from the begin
until this week !)

Could you give an advise how to improve or find the problem ??
Thanks in advance.

BBB is for sure the only device with IP 192.168.1.88 (same IP as I use for the snapshot of august)
 
Zuletzt bearbeitet:
AW: Re: AW: Re: BeagleBone Black Image

I have no idea why you have these problems. My BBB works without any perfect without any problems.
 
@supamiche, it's something with the boot........... that will be different since your latest two updates 2014-10-17 and 2014-11-22.

Again, the snapshot version of 2014-8-10 will be superb, it works still without any problems !!!
Do you have an another version of the (2Gb) BBB maybe ? It will be really strange that my version of the BBB works perfectly
with all your SnapShot(s) from the beginning (january) until August. And your two latest SnapShot(s) it goes wrong after a reboot.

Pls, could you try a cold (power) and also a normal reboot ?
Thanks in advance.
 
Zuletzt bearbeitet:
AW: BeagleBone Black Image

Differences are:
- kernel update (source : )
- uboot update (/boot/uboot/MLO, /boot/uboot/u-boot.img - source : )
- packages update (apt-get update && apt-get dist-upgrade)
- oscam (oscambuild)
- maybe oscam build or restart script (/usr/local/bin/oscambuild, /usr/local/bin/oscamrestart)

Cold and warm boot are ok (reboot, shutdown -r now, switch off power supply)

Can you try your reboot with crontab (/etc/crontab) like this :
Code:
55 4    * * *    root    /usr/local/bin/autorestart >/dev/null 2>&1
/usr/local/bin/autorestart
Code:
#!/bin/bash
sleep 300
reboot
exit 0

I think this will prevent your reboot loop.
 
Zuletzt bearbeitet:
@supamicha, it seems to be the solution. :emoticon-0168-drink

After installation your latest snapshot all tryouts of reboot (reboot, shutdown -r now, switch off power supply) works very good !:emoticon-0157-sun:

I'll come back within 1 or 2 days with the final story of the youngest SnapShot and the improvement/solution you gave.
 
@supamicha, a first look at the BBB gives nothing ...... Oscam switched-off with the latest SnapShot (with your try from yesterday and without (!) "shutdown -r 05:00" in rc.local)

The oscamrestart with old line "systemctl restart oscam.service" was changed into;
#!/bin/bash
sleep 300
reboot
exit 0

Don't we need longer the line "systemctl restart oscam.service" ?
Why you will test the sleep for 5 minutes ? instead the each night reboot ?
 
Noboddy said this :emoticon-0133-wait:

In your reply you proposed and I replaced instead of assembly of the lines.
You mean I''ll think;

#!/bin/bash
systemctl restart oscam.service
sleep 300
reboot
exit 0
 
@supamicha, sorry for the stupid mistake :emoticon-0179-headb :emoticon-0179-headb :emoticon-0179-headb from my side.
I'll understand the extra lines :emoticon-0169-danceyou mean. You prevent the loop with a sleep of 5 minutes. (1 minute also okay ?)

If this test is okay, what will be the best way to force each night the reboot automatically ?
 
Zurück
Oben