Jump to content

Start looking at 5.3.y

martinayotte
 Share

Recommended Posts

martinayotte

martinayotte

Posted
Posted

I've made my first build for OPiPC+ with 5.3.0-rc3 ...

Things are not looking very good : Wifi 8189fs is crashing, but eth0 is working.

I will investigate more ...

Werner

Werner

Posted
Posted

I tried to build an image for the OPi 1+ using megis orangepi-5.3 branch but did not even compile without any changes to the patches. Could not find the cause yet.

martinayotte

martinayotte

Posted
  • Author
Posted
  On 8/9/2019 at 4:44 PM, Werner said:

did not even compile without any changes to the patches. Could not find the cause yet.

Expand  

I didn't got any compile error, only one patch rejected, but because already present in 5.3.y.

 

One more thing I found with my OPiPC+ experiment : reboot doesn't restart, it stall at "reaching restart", but U-Boot "restarting" never appears ...

(a bit like the early days of H6, but OPiPC+ is H3 and never got this issue)

 

Now trying again with 5.2.6 to figure out when bugs has been introduced ...

 

EDIT: 5.2.6 still look good ...

 

EDIT2: Same behaviours with OPiPlus2E 5.3.0-rc3 image ...

 

EDIT3: Doing an OPiZeroPlus2-H5 images : No Wifi problem, and since no crash, "reboot" work properly, so, maybe related ...

1
Werner

Werner

Posted
Posted

Nice. Started my daily build process, lets see what we have after two or three hours.

martinayotte

martinayotte

Posted
  • Author
Posted
  On 8/14/2019 at 2:08 PM, Werner said:

lets see what we have after two or three hours.

Expand  

In my case, I've done the tour of my AllWinner's garden : OPiPC+, OPiOne, OPiZero, OPi+2E, OPiPC2, OPi3, OPiOne+, OPiZero+2, OPiWin, OPiPrime, Pine64 and OlinuxinoA64. :lol:

2
Igor

Igor

Posted
Posted

Nightly builds are ... building and will be out in 1-2h.

guidol

guidol

Posted
Posted
  On 8/14/2019 at 1:42 PM, martinayotte said:

Commit for the 5.3.y switch is now done !

Expand  

At dinner time I did try to compile for the OPi PC2 and the kernel doesnt build....but now in the evening it does compile fine with kernel 5.3 ;) Thanks!

guidol

guidol

Posted
Posted

My Opi R1 doenst like the enw compiled image

Armbian_5.93_Orangepi-r1_Debian_buster_dev_5.3.0-rc3

 

Couldnt connect via SSH and teh serial gadget via MicroUSB doenst repond :(
Have to check tomorrow via USB-TTL-console....

guidol

guidol

Posted
Posted
  On 8/15/2019 at 6:14 PM, guidol said:

My Opi R1 doenst like the enw compiled image

Armbian_5.93_Orangepi-r1_Debian_buster_dev_5.3.0-rc3

Have to check tomorrow via USB-TTL-console....

Expand  

here the serial-boot-console log:

  Reveal hidden contents

 

[BUT WAIT]

while copying the output from the serial console and doing some other stuff the login prompt does appear ;)

Debian Buster with Armbian Linux ttyS0

orangepi login: 

 

So here also the armbianmonitor -u

System diagnosis information will now be uploaded to http://ix.io/1RQA

 

Seems to be some problem with the 8189es network driver....

 

Yesterday - I think - I also waited some minutes, but got no DHCP-IP-Request.

guidol

guidol

Posted
Posted
  On 8/15/2019 at 6:14 PM, guidol said:

My Opi R1 doenst like the enw compiled image

Armbian_5.93_Orangepi-r1_Debian_buster_dev_5.3.0-rc3

Expand  

Strange - my OPi R1 doenst also like the mainline

Armbian_5.93_Orangepi-r1_Debian_buster_next_4.19.67

Many TimeOuts of services and CPU-stalling :(

[EDIT]

4.19.67 mainline is now running - problem was the attached OPi Zero NAS-Hat

Without the NAS-Hat (which wasnt a problem in the past) the mainline does boot fine.

 

but the 5.3 stays with the exception while booting.

guidol

guidol

Posted
Posted
  On 8/16/2019 at 2:51 PM, martinayotte said:

When you did your build, did you have this commit already ?

https://github.com/armbian/build/commit/a89842487398157cf91487acb414ccfe42a16331

Expand  

Your commit seems to be 6 days old.
The first compile was around 6 hours ago and I did recompile now the same image.
While booting I got the following error-messages in boot-log:
 

  Reveal hidden contents

 but system came up including the 2 network-interfaces:
armbianmonitor -u
more messages while booting could be found at:
System diagnosis information will now be uploaded to http://ix.io/1RUh

 

 

Igor

Igor

Posted
Posted

It actually crashed for me too, but so far I was not able to recreate. On NEXT branch, not on DEV.

guidol

guidol

Posted
Posted
  On 8/16/2019 at 5:14 PM, guidol said:

 but system came up including the 2 network-interfaces

Expand  

@martinayotte network-interfaces are only available with network-manager.

if I only use ipupdown they wont be ready :(

BTW: reboot doenst work because it wouldnt restart and hang at the restart-message:

[  OK  ] Reached target Final Step.
[  OK  ] Started Reboot.
[  OK  ] Reached target Reboot.
 

martinayotte

martinayotte

Posted
  • Author
Posted
  On 8/16/2019 at 5:14 PM, guidol said:

The first compile was around 6 hours ago and I did recompile now the same image.

Expand  

I've compile it too on my side, and I got the 8189fs crash too. I've even tested 5.3.0-rc3 kernel with 5.0.0 DT, but crash still there.

So, that must be something else directly in the kernel.

I will now try building a 5.2.y and 5.1.y kernels to narrow the issue ...

martinayotte

martinayotte

Posted
  • Author
Posted

I think I figured out : my commit of 6 days ago was for 8189fs and 8723cs, but not 8189es !

I will create a new patch for that one ...

 

EDIT : Oh ! @Igor Where the 8189es sources comes from ? I didn't found a patch for it neither than a git clone ...

EDIT2 : I've founded the patch, I was a bit blind earlier ...

Igor

Igor

Posted
Posted
  On 8/16/2019 at 6:16 PM, martinayotte said:

Where the 8189es sources comes from ? I didn't found a patch for it neither than a git clone ...

Expand  


I don't recall. Perhaps by email from Xunlong ? :) ES is missing from DEV. They are inside NEXT branch only.

martinayotte

martinayotte

Posted
  • Author
Posted
  On 8/16/2019 at 7:12 PM, Igor said:

OK. I will also add all of them here later/over weekend: 

Expand  

If you turn those patch into "git clone" in compilation-prepare.sh, remember that we failed to use some patching on them since they are cloned AFTER patching phase ...

(remember that we tried to get this order reversed a month ago, but you decided to revert it)

Otherwise, the "git clone" would need to be done from Armbian branches to keep controls of them ... :P

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept