Jump to content

Lycurgus

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Getting closer. The Ubuntu image worked until I did 1 simple command: apt-get update && apt-get upgrade After which it told me this The following packages will be upgraded: apt apt-transport-https apt-utils base-files bind9-host console-setup console-setup-linux distro-info-data dnsmasq-base dnsutils eject hostapd init init-system-helpers keyboard-configuration klibc-utils libapparmor1 libapt-inst2.0 libapt-pkg5.0 libbind9-140 libc-bin libc-dev-bin libc6 libc6-dev libdns-export162 libdns162 libgssapi-krb5-2 libhogweed4 libicu55 libisc-export160 libisc160 libisccc140 libisccfg140 libk5crypto3 libklibc libkrb5-3 libkrb5support0 liblwres141 libmysqlclient20 libnettle6 libnm0 libpci3 libxml2 linux-firmware linux-libc-dev locales makedev multiarch-support mysql-common nano network-manager ntp pciutils resolvconf sudo wget This may also be the reason why it failed to boot after only configuring Samba and a NTFS partition to automount. I forgot that I always apt-get update && apt-get upgrade on fresh images. Will update this post when I have more info. Edit: Things have gotten confusing now. As a test I again upgraded the system and rebooted: it came back just fine Then after automounting the NTFS partition it refuses to boot again.. So it's neither upgrading or configuring that's the culprit. It's not the SD card either, as the Ubuntu image doesn't throw any errors about it, and ofcourse I already checked those.. Next step is to try out official images and see if the problem persists. And if it does, then maybe the Odroid is defective.
  2. This is bad. After only configuring Samba and automount an NTFS partition it started doing the exact same thing after issuing a reboot command. I double checked the checksum of the image, nothing strange there. Will try with an Ubuntu image, hopefully with more luck.
  3. So after plowing through previous logfiles/bash history, comparing with the vanilla install on the spare SD card and reverting everything back... It still doesn't work. I'm afraid I'll have to do everything over again. This sucks.
  4. @zador.blood.stained 2nd question: I ordered 2 SD cards a month ago. One was laying as a spare, which i burned an image of the latest Debian legacy on. Yes changed card. 1st point: Both cards have that issue. Used the program H2testw to confirm the cards are not broken. Could be a board issue, but got the Odroid also for about a month. Edit: a quick Google shows it is a harmless compatibility issue https://forum.odroid.com/viewtopic.php?f=117&t=8919
  5. Well I guess since no one here can/want to help me , I'll use this thread to document my progress. Maybe someone somewhere will stumble upon it and would help him out. I found out how to enable kernel output to show on the serial console. In boot.ini I changed the following as told by @zador.blood.stained here I set setenv verbosity from 1 to 7, which gave me kernel output. The last few lines are the following: So it seems the kernel is stuck doing something with it's network settings. It can get a link and IP address however. I vaguely remember (i messed this up a week ago, only just now did I get a UART-USB) changing something with the network settings. I'll see if I can revert everything back to default. PS. On a separate note, I just noticed that the kernel spent some 90 seconds creating swap. As soon as I get everything working again, I'll disable swap. 2GB RAM is enough for my purposes.
  6. Just a small update. I had a spare SD card laying around and decided to use legacy Debian for Odroid C2. By default the image doesn't spit out kernel lines on the serial console (see spoiler at end of post.) This means that in my case the kernel got stuck halfway through, but I can't see where exactly. If anyone can provide me with info to enable dmesg style logs on serial console, that would be great. At this point it's still less time salvaging the previous install instead of beginning from start.
  7. When I changed some settings to my network config, my Odroid doesn't boot anymore. Even changing the settings back doesn't make it boot again. Has anyone had this happen before? I hooked up my UART and this is the result, it never proceeds with starting the kernel (see spoiler below)
  8. Before I was able to manually send CEC commands to my tv with cec-client. However I'm not sure how it works with Linux kernel CEC implementation. I know /dev/input0 is the node for CEC, I just have no idea what to do in this case. In case of cec-client, I would use the website cec-o-matic, but is there also a site like this for the kernel implementation of CEC? The reason I want this, is because I need to power on a tv with a remote using the odroid.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines