Jump to content

cibomato

Members
 View Profile  See their activity

  • Posts

    45

  • Joined

  • Last visited

 Content Type 

Posts posted by cibomato

    change commit setting when using hdd?

    in Allwinner sunxi

    Posted

    Hi,

     

    I'm using an hdd at my cubietruck and moved the root-fs to hdd. Now I'm wondering, whether it would be better, to change the commit settings in /etc/fstab to a lower value than 600? 

    I assume, the 600 was meant for data on a flash storage in order to reduce the writes on it!? But in order to keep "things in sync", shouldn't I better reduce it? Or delete the whole commit option?

     

    What do you mean?

     

    Thanks and best regards,

    Jochen

    0

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    If it's the same problem than by me, after booting up debian-3.8-wheezy-3.4.107 (or whatever system works) you should first make shure, that the system date&time is correct:

    date

    If it's not correct, you can set it with:

    date -s "26 JUN 2015 19:20:21"

    and control once again with date, that it's correct now.

     

    After that, you should check date&time of the hwclock:

    hwclock --show

    If it's not correct (or you do it anyway), you can set the hwclock date&time to the system date&time via:

    hwclock --systohc --localtime

    and doublecheck afterwards once again with hwclock --show, that this was successful.

     

     

    After that I was able to shut down the system, copy the image I like to sdcard and boot from it.

    Everything was discovered (rtc, eth0,...), dhcp worked and got an IP and the system came up without a problem.

     

    Hope this helps you too! Let us know.

     

    Cheers,

    Jochen

    0

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    GOT IT !!!

     
    It was the f***ed-up rtc indeed! Let me explain:
     
    I simplified my experiment from above:
     
    - installed debian-3.8-wheezy-3.4.107 --> ok (eth0 is ok, ping heise.de works)
    - survives reboot / halt and power-on / halt and dis-/reconnect power --> everything ok
     
    Then upgrade to kernel 4.0.5 as described in your faq and then:
    - reboot 
     
    --> System boots till login screen (!!!) but eth0 isn't set up! No ping possible!
    dmesg | grep rtc
    2085-06-25 (NOT ok)
    date

    Fr 20. Mai 13:37:52 CET 1949 (NOT ok)

    hwclock --show

    hwclock: The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).

     
    So, all date/time and clocks are wrong! Now I've set the correct date manually:
    date -s "25 JUN 2015 21:00:10"
    date

    ok!

     

    But hwclock / rtc is still going wrong:

    hwclock --show

    (NOT ok)

     

    So, I've now set hwclock to system date via:

    hwclock --systohc --localtime

    And voilà:

    hwclock --show
     --> ok (!)
     
    reboot
    --> eth0 comes up !!!! ping ok!
    date --> ok
    hwclock --show --> ok
     
    halt and power on
    date : ok ping ok
     
    halt power dis-reconmnect
    --> ok
     
    Then I removed sdcard, copied debian-4.0-wheezy-4.1 on it, put it back in and reset
     
    And..................
    Tatataaaaaaa, it doesn't complain about rtc, it recognizes eth0 and boots normally!
     
    Repeated that with new installation of  debian 3.9-jessie-4.0.5, also works like a charm!
     
     
    I'm happy!
     
    Hope, that this is helpful for you other guys, too!!!
    2

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    Cubietruck_Debian_3.8_wheezy_3.4.107 working fine for me but can't boot from SSD. After nand-sata-install rootfs on SSD but booting only from SD-card.

     

    Disconnect battery and AC power adaptor but 4.1 still not booting...

    As far as I understood, bootloader always has to stay on sdcard or nand, so therefore you have to let the sdcard inserted even if root-fs is on hdd/sdd!? So that should be ok. Or didn't I get you right?

     

    Debian-3.8-wheezy-3.4.107 is also the only image working for me. 

     

    @Igor: I did powercycle the cubietruck completely (plug-off and back in the powerchord). Same effect as Ctrl/Alt/Del. x.4.0.5 nor 4.1 does boot.

     

    How to enter u-boot commandline? I'd like to try resetting date and time before booting. But when I press a key in order to interrupt autmatic booting, nothing happens!? Afterwards, when boot hangs, the keyboard is detected and e.g. Ctrl+Alt+Del works.

    0

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    Nope, Debian-4.0-whezzy-4.1 doesn't boot either....

     

    Same as above:

     

    DHCPDISCOVER takes less than a second (!?) and then it says:

    - Unable to set up timer: unexpected error

    - Failed to bring up eth0

     

    Then some seconds later it hangs forever at "Enabling ramlog....."

     

     

    One more idea: could my problems come from power supply? I've got a 5V/2,5A-USB-Power-Supply. Could this be to weak with sata-hdd attached?

    Will try it while sata-hdd deattached... 

    [Edit]: with hdd deattached and w/o keyboard --> still the same...

    0

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    Seems like Kernel 4.0.5 causes the problem, regardless if it's wheezy or jessie. Here's what I did:

     

    - copied/installed Debian-3.9-wheezy-3.4.107  --> ok

    - moved root to hdd --> ok

    - apt-get update && apt-get upgrade && apt-get dist-upgrade --> ok

    - Upgrade to Jessie as described in the faq --> ok

    - configured fixed ip --> ok

     

    So, then I am on Jessie with Kernel 3.4.107 now. Everything is fine, also after a reboot.

    But then I updated the kernel as described in the faq to 4.0.5. After the next reboot it hangs:

     

    Welcome to Debian GNU/Linux 8 (jessie)!
     
    [ TIME ] Timed out waiting for device dev-mmcblk0p1.device.
    [DEPEND] Dependency failed for /media/mmc
    [DEPEND] Dependency failed for Local File Systems.
    [DEPEND] Dependency failed for /boot.

     

    Any idea?

     

    Thanks and best regards,

    Jochen

    0

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    ...since it was working well all the time.

     

     

    I don't think it's related. Nothing has been change system wise. If your Ethernet is not up you can login via console eventually.

     

     

    It's very strange because like I posted above, this same image already has worked for the same (my) cubietruck and the system was up for the last 9 days. LAN worked fine.

     

    Now I messed up the system somehow and therefore I decided to do a complete clean reinstall from scratch again (copy image to sdcard, boot and write root partition to hdd).

    But now I encounter this problem. That's why I was asking, whether the image has changed since then (downloaded it again yesterday). But if image and hardware are still exactly the same, something else must have happened!?

     

    I don't understand too, what rtc / system date and time should have to do with initialisation of eth0 but that's what seemed to be the solution for different people writing in this thread: http://forum.solid-run.com/linux-on-cubox-i-and-hummingboard-f8/unable-to-configure-eth0-on-debian-jessi-t525.html

     

    As one of them said "...I Set the date and Ethernet was working OK, after cutting the power the clock reset again (which is fine) and ethernet was again unusable(which is NOT fine)....", so did I (cutting the power off).

     

    What do you mean with login via console? I've already attached a USB-Keyboard but can't switch to another tty at this stage.

     

    Many thanks in advance for your effort since I do have some linux experience but I'm quite new to the ARM/cubietruck stuff.

     

    Best regards,

    Jochen

     

    [Edit]:

     

    Debian-3.9-wheezy-3.4.107 is booting. Rebooting and also cutting off the power completely is no problem, boots up again... Strange! But I'd like to have Kernel 4.x

     

    Debian-3.9-jessie-4.0.5 doesn't boot. Hangs immediately at "This is Debian 8 (jessie)"

    Ubuntu-3.9-4.0.5 doesn't boot. Hangs 3 mins at "brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO 3166 code" then continues but hangs forever at "System will reboot automatically. Please wait!"

     

    What else could I test?

     

    [/Edit]

    0

    cubietruck hangs at boot with debian-3.8-wheezy-4.0.4

    in Allwinner sunxi

    Posted

    Have you changed something in the debian-3.9-wheezy-4.0.5-image between June 11th and today?

    I had to re-setup my cubietruck from scratch and therefore I downloaded the same (?) image (which worked before) again, copied it to sdcard and fired the cubie up:

     

    now it hangs again but at a different position:

     

    right at the beginning it says: "warning - bad CRC, using default environment"

    I'm not sure, whether this has something to do with my boot-problem?

     

    Short time later the DHCPDISCOVER takes less than a second (!?) and then it says:

    - Unable to set up timer: unexpected error

    - Failed to bring up eth0

     

    Then some seconds later it hangs forever at "Enabling ramlog....."

     

    Thanks and best regards,

    Jochen

     

    P.S.: I've googled and found some hints, that it could be tied to wrong date and time (http://forum.solid-run.com/linux-on-cubox-i-and-hummingboard-f8/unable-to-configure-eth0-on-debian-jessi-t525.html) or here (http://www.gpio.com.au/faq/hummingboard-dhcp-fails-to-get-an-ip-address-failed-to-bring-up-eth0″/) but how to set the correct date when I have no running system?

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept