Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ODROID XU4 incorrect hardware version #2990

Closed
ponasromas opened this issue Jul 17, 2019 · 10 comments
Closed

ODROID XU4 incorrect hardware version #2990

ponasromas opened this issue Jul 17, 2019 · 10 comments
Labels
Kernel related 🧬 Odroid XU4 Visual 🌹 Issues affecting only the beauty of menus and output, but not the functionality

Comments

@ponasromas
Copy link

ponasromas commented Jul 17, 2019

Creating a bug report/issue

Required Information

  • DietPi version
    G_DIETPI_VERSION_CORE=6
    G_DIETPI_VERSION_SUB=25
    G_DIETPI_VERSION_RC=3
    G_GITBRANCH='master'
    G_GITOWNER='Fourdee

  • Distro version
    stretch

  • Kernel version
    Linux DietPi 4.14.66+ Fix warning when running scp over openssh-server #1 SMP PREEMPT Thu Aug 23 05:59:33 UTC 2018 armv7l GNU/Linux

  • SBC device
    Odroid XU3/XU4/HC1/HC2 (armv7l)

Steps to reproduce

  1. Install latest ODROID XU4 DietPI OS
  2. Perform cat /proc/cpuinfo | grep Hardware
  3. You will get XU3 even if hardware is XU4

Expected behaviour

On original Ubuntu 18.04.1 it shows correct hardware version for ODROID XU4

@MichaIng
Copy link
Owner

MichaIng commented Jul 17, 2019

@ponasromas
Thanks for your report.

Not sure if this is related to the kernel or bootloader or how it is invoked. At least the boot.ini explicitly checks for the model: https://github.com/MichaIng/DietPi/blob/master/boot_xu4.ini#L124

If you find time, could you try with a fresh Meveric image: https://forum.odroid.com/viewtopic.php?f=96&t=30552#p219509

However there will be no or no recognisable effect since those boards are veery similar (according to SOC). Investigation makes sense though, perhaps we can force a re-estimation somehow on first boot.

@ponasromas
Copy link
Author

Can't test it, just setuped production environment :( . Does the hardware detection can impact something meaningful such as performance etc.?

@MichaIng
Copy link
Owner

@ponasromas
Not that I'm aware of. All share the same CPU + GPU with same default clocks.

@Technetium1
Copy link

@MichaIng cat /proc/cpuinfo | grep Hardware
on above linked image:
Hardware : ODROID-XU3

on current Old Stable - DietPi_v6.14_OdroidXU4-ARMv7-Stretch:
Hardware : ODROID-XU3

on Testing - DietPi_OdroidXU4-ARMv7-Buster [2020-02-04 01:11]:
Hardware : ODROID-XU3

I got an error trying to start up the current Testing, I will open a new issue for it. I'm happy to contribute anything that might help here.

@MichaIng
Copy link
Owner

MichaIng commented Feb 11, 2020

@Technetium1
Since the image works very well otherwise on XU3 + XU4 + HC1 + HC2 + MC1, this should be not an issue. Probably the kernel for Ubuntu was slightly adjusted compared to the one maintained by Meveric.

Could you please check: cat /proc/device-tree/model

It should be btw the same "issue" with the original image: https://forum.odroid.com/viewtopic.php?f=96&t=30552

@Technetium1
Copy link

@MichaIng Testing last modified 2020-02-09 23:12:
Hardkernel Odroid XU4 🎊

@MichaIng
Copy link
Owner

@Technetium1
Strange, I actually only fixed some missing ca-certificates/curl issue with the last upload, no kernel changes 🤔: #3376 (comment)
However great if shows the correct hardware now 👍.

@MichaIng MichaIng added this to the v6.29 milestone Feb 13, 2020
@MichaIng MichaIng added the Solution available 🥂 Definite solution has been done label Feb 13, 2020
@MichaIng
Copy link
Owner

I mark this as closed then. Also good to know the new image works fine in general, so we can move this to stable soon.

@Technetium1
Copy link

@MichaIng Just to reiterate, it's only /proc/device-tree/model that shows XU4 correctly, but I do not believe it matters much. I think this can now be closed safely now!

@MichaIng
Copy link
Owner

MichaIng commented Feb 14, 2020

@Technetium1
Ah of course. Yes so that means that as far as the kernel supports it, it detects the different models correctly, uses the right dtb etc. A differentiation within /proc/cpuinfo seems to not have been implemented. But yeah it is visual only and does not matter, simply because the SoC of all boards is the same anyway.

We could report this to Meveric, if this is something he can implement in his kernel packages, else we can forward to hardkernel where it most likely will not be handled at all (no priority): https://forum.odroid.com/viewtopic.php?f=96&t=30552

I mark this as closed, since nothing we can do our side and yeah, visual only 😉.

@MichaIng MichaIng removed the Solution available 🥂 Definite solution has been done label Feb 14, 2020
@MichaIng MichaIng removed this from the v6.29 milestone Feb 14, 2020
@MichaIng MichaIng added the Visual 🌹 Issues affecting only the beauty of menus and output, but not the functionality label Feb 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Kernel related 🧬 Odroid XU4 Visual 🌹 Issues affecting only the beauty of menus and output, but not the functionality
Projects
None yet
Development

No branches or pull requests

3 participants