CubieBoard Forum

Hi I am using the 3.2 kernel and the stock driver unloads due to some error. The same kernel works fine on cubieboard2. Was wondering is the emac on the CubieTruck different than the one from Cubieboard2?

Quote from: cubieplayer on June 24, 2014, 12:52:54 am

Quote from: ratin on June 23, 2014, 11:34:03 am

Quote from: cubieplayer on June 23, 2014, 05:42:25 am

Quote from: bmarkham on May 02, 2014, 10:18:25 am
Hi!

I downloaded the Cubian Desktop r1 SD image for A20 cubieboard.  It works very nicely except ... it seems at random, even if I just leave it sitting alone for an hour or so, it will completely lock up.

The screen is just a blank screen of light blue.  Unresponsive to keyboard.

Can't get in via ssh either.

The only light on is the power light when it hangs.  When it hangs, it can be turned off with the power button but otherwise seems unresponsive. 

Any ideas? 

Thank you!

This is a known issue, only happens on A20. Checkout https://github.com/cubieplayer/Cubian/issues/319

Hi Cubieplayer, Have you tried the updated fex settings with the SD boot loader?

We only needs to change script.bin, is it related to u-boot?

yes u-boot reads that file, and I have seen the Nand boot loader does not honor the settings, while SD boot loader does (you put the script.bin in SD boot partition)

Quote from: cubieplayer on June 23, 2014, 05:42:25 am

Quote from: bmarkham on May 02, 2014, 10:18:25 am
Hi!

I downloaded the Cubian Desktop r1 SD image for A20 cubieboard.  It works very nicely except ... it seems at random, even if I just leave it sitting alone for an hour or so, it will completely lock up.

The screen is just a blank screen of light blue.  Unresponsive to keyboard.

Can't get in via ssh either.

The only light on is the power light when it hangs.  When it hangs, it can be turned off with the power button but otherwise seems unresponsive. 

Any ideas? 

Thank you!

This is a known issue, only happens on A20. Checkout https://github.com/cubieplayer/Cubian/issues/319

Hi Cubieplayer, Have you tried the updated fex settings with the SD boot loader?

Quote from: cubieplayer on June 23, 2014, 05:42:25 am

Quote from: bmarkham on May 02, 2014, 10:18:25 am
Hi!

I downloaded the Cubian Desktop r1 SD image for A20 cubieboard.  It works very nicely except ... it seems at random, even if I just leave it sitting alone for an hour or so, it will completely lock up.

The screen is just a blank screen of light blue.  Unresponsive to keyboard.

Can't get in via ssh either.

The only light on is the power light when it hangs.  When it hangs, it can be turned off with the power button but otherwise seems unresponsive. 

Any ideas? 

Thank you!

This is a known issue, only happens on A20. Checkout https://github.com/cubieplayer/Cubian/issues/319

If the PMU voltage outputs (from AXP209) are too conservative, it can have problem with various chips on the board, depending on their tolerance level. What appears to be least tolerant is the DRAM chip. And Nand chip is the second one I think. I think thats why lowering the DRAM speed fixed the problem.
Well its known issue but apparently not well known What I am afraid of is after 3 months of testing and confirming that this probem went away, now it will require another level of testing with the new FEX settings.

Quote from: qiozas on June 21, 2014, 11:01:59 am
Finally problem SOLVED!!!

After reformat partition and do many other things to find out what was causing the problem, finally a colleague advised me to try power CT with an additional power supply.

Old power installation:
=======================================
                                                             |-> CT
power 12V 6A <-> "CT HDD Addon"  <-|
                                                             |-> HD SATA 3.5"
=======================================

Working power installation:
=======================================
power 5V 3A   <-> CT
power 12V 6A <-> "CT HDD Addon"  <->  HD SATA 3.5"
=======================================

It looks like output USB power adapters of "CT HDD Addon" is a crap. It cannot provide Amperes required by CT, even if power supply supports much more Amperes than CT and Hard Disk needed. 

My advice is to use 1 power adapter for CT and an additional power adapter for "CT HDD Addon" (only needed if you need Hard Disk SATA 3.5").

Regards,
Adrianos Dadis.

Sorry that you had to find this solution all on your own, another sample of great support provided by cubitech!
On a side note, I have been using a 3.5 inch SSHD drive with cubieboard2 and have not yet seen this problem. I have seen the AXP chip is screwing up after a hard power shutdown in the middle of running though, with an older 3.3 kernel.
For 3TB you can use GPT with Ext4..

Quote from: FR3D on June 20, 2014, 07:47:56 am
Hi guys,
I did a little research on the board and apparently the board will be use PowerVR G6230 (Rogue) which apparently have better kernel support and support 4k. good news? like most comment posted I totally  agree about how Cubietech doin their business with little to none software support (though their hardware is the best value you could find) but it still gives it a disadvantage because doesnt matter how good the hardware is the software cant execute it, it becomes no use. As of posting this I also find out that third party company had just made a base board for the Cubietruck finally. So now thankfully we have some support from third party. One question for kernel expert could the next model support windows?

Reading your post, I am confused, how does the baseboard help to fix day to day problems we find with the Cubieboards, the lack of support and long term stable operation of Cubie boards can only be guaranteed by a knowledgeable software team. What cubietech is doing is putting some reference designs thru fabs and calling it a product and let open source community figure out everything on their own, not spending a dime on the software development means most proceeds from sales becomes profits since manufacturing these boards probably minimal once you have the fabs infrastructure setup.

Quote from: ratin on June 17, 2014, 04:18:01 am

Quote from: rose28357 on June 16, 2014, 08:16:38 pm
No, CB2 has a 100 MBit interface.
Bug the gmac driver contains also an emac driver for 100MBit. So it is a universal driver for CB2 and CT.

Gotcha, I saw "gmac driver disabled" message in the kernel, and did not see the gmac entries in my fex. Perhaps adding only the gmac related fex entries described in this thread will load the driver.

Just updating here, although I got sunxi_gmac driver to load, its unable to get a DHCP address. I am not so thrilled to get this working anyway since it does not buy anything to use the gmac driver on a CB2 which has the 10/100 mbps

I have been seeing this annoying message and consequently init process hanging for goodd 2/3 minutes.  I disabled all but the ttys0, tty1 and tty2 and disabled the auto-login. So currently a "Permission Denied" message is printed on the console for tty1 and normal login is enabled via tty2. However during boot, it throws those respawning / terminated messages. Has anybody else experienced it? I wonder it has to do with disabling the auto-login.

Try adding this in your xorg.conf

Section "ServerFlags"
    Option         "BlankTime" "0"
    Option         "StandbyTime" "0"
    Option         "SuspendTime" "0"
    Option         "OffTime" "0"
EndSection

Quote from: rose28357 on June 16, 2014, 08:16:38 pm
No, CB2 has a 100 MBit interface.
Bug the gmac driver contains also an emac driver for 100MBit. So it is a universal driver for CB2 and CT.

Gotcha, I saw "gmac driver disabled" message in the kernel, and did not see the gmac entries in my fex. Perhaps adding only the gmac related fex entries described in this thread will load the driver.

does cb2 have a gmac (gigabit mac) to use the gmac driver on?

any patch for /proc/cpuinfo serial number fix?

Quote from: jiv on June 06, 2014, 03:45:52 am
did you checked with TTL?

It was the AXP 209 , going into a weird state. The problem gone away with new kernel, I noticed it doesn't send the config timing data to the AXP PMU anymore like older kernel did

"Serial          : 0000000000000000"

Any idea why Serial is shown as 000000
with older kernel it used to be a 32 digit hex number like this 04c2d3575350484880808955165165c1

Also in /proc/cpuinfo , Serial is set to 0000000000000000
but it used to be a valid cpu ID on 3.3.0+ kernel