-
Notifications
You must be signed in to change notification settings - Fork 153
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
Rpi3 support #418
Rpi3 support #418
Conversation
While DT was (too) new in kernel 3.18 it is working properly in kernel 4.4+, so re-enable DT for all Pi's.
Kernel and initramfs are the same as for the rpi2, but to enable the serial console, we need to specify 'enable_uart=1'.
The Hardware field of /proc/cpuinfo doesn't allow us to differentiate enough, while the Revision field does, so switch to that.
…rsions. While the new detection statements also detect other versions (cm, 0), let's deal with that when the need arises.
900092|900093) | ||
rpi_hardware_version="0" | ||
;; | ||
0002|0003|0004|0005|0006|0007|0008|0009|000d|000e|000f|0010|0012|0013|0015) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add |900032
? (#415)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. See new commit.
Looks good to me. |
See debian-pi#415 (comment) for details.
Just tested it. |
Also updated the README.md to include RPi 3B. |
Done. May I just say that I love your work. ;) It is working great for me guys. Well done. This build is absolutely smoking on the RPi3. I will do another complete build of our system from scratch over the weekend just to confirm. |
Did a 2nd pass yesterday. All working well for me. |
Anyone having issues with installing RTC? We just got a new board and are trying to get rtc running to no avail. |
Works well for me, on my new RPi 3B. I built the installer and copied all files in |
# as the statements below disables bluetooth which various/most | ||
# people will prefer over the serial console | ||
echo "# enable the serial console for the installed system" | ||
echo "#device_tree=" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean "enable_uart=1" here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. Thanks for spotting this 👍
Following the build guide I created a build of the latest raspbian-ua-netinst. I run these commands: git clone https://github.com/debian-pi/raspbian-ua-netinst.git Everything run without errors, and created the .zip file. I put it on a microsd and into the rpi3. I only got the rainbow screen. What I'm I doing wrong here? |
Try this:
|
root@debian:~/project# git checkout v1.1.x |
oops, I had to go in the folder. |
I have tried building the image from the branch Anyone else experiencing this? |
Yes, it is a known issue. But I am not sure what the solution will be. |
Please retry with the current v1.1.x branch (w/ #475 merged). |
I just tried a version I compiled yesterday. Bu still get the kernel panic. :(
So I think I am using the right branch/version. |
@CWempe and with UART disabled it works (again)? |
I (normally) do my initial install with a serial console, so I can see what happens, and the It is very likely that we need to switch to properly using the overlay mechanism and figure out how to do things 'the new way'. |
I have these issues open in tabs as they deal with it, but haven't had time to properly go through them: RPi-Distro/repo#31 They may also be dated as I opened those tabs a while ago, but probably worth taking a look |
And indeed. Reboot failed. Disabling the So my suggestion is to disable that line for now, create a new beta release so the new kernel can be tested more broadly which may also fix some issues, and create a new issue to tackle the uart/serial console problem so we can get it working again. |
PR #480 should fix this. |
There are still items to be improved, but it is essentially working on my systems.
One particular point that needs to be improved is the serial console/bluetooth. It is working during install, but during normal boot after the install it is not. And we probably need to add a config option which determines what to do with the UART port as that is either serial or bluetooth, but not both.
But for the time being people can now use the installer on a Pi 3 (but do have to build it themselves for now)
So I'd say this partially fixes issue #375