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

Rpi3 support #418

Merged
merged 6 commits into from
Aug 9, 2016
Merged

Rpi3 support #418

merged 6 commits into from
Aug 9, 2016

Conversation

diederikdehaas
Copy link
Member

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

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)
Copy link
Contributor

@Mausy5043 Mausy5043 Aug 9, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add |900032 ? (#415)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. See new commit.

@Mausy5043
Copy link
Contributor

Mausy5043 commented Aug 9, 2016

Looks good to me.

@Mausy5043
Copy link
Contributor

Just tested it.

@diederikdehaas
Copy link
Member Author

Also updated the README.md to include RPi 3B.

@Mausy5043 Mausy5043 merged commit 75b60b2 into debian-pi:v1.1.x Aug 9, 2016
@diederikdehaas diederikdehaas deleted the rpi3-support branch August 9, 2016 22:15
@cherylquirion
Copy link

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.

@cherylquirion
Copy link

Did a 2nd pass yesterday. All working well for me.

@cherylquirion
Copy link

cherylquirion commented Aug 25, 2016

Anyone having issues with installing RTC? We just got a new board and are trying to get rtc running to no avail.
[Updated] Never mind. User error. :)

@aykevl
Copy link

aykevl commented Sep 2, 2016

Works well for me, on my new RPi 3B. I built the installer and copied all files in bootfs to the root FAT32 partition on the SD card (manually partitioned with gparted at the 4MB erase block offset), as there is no official build yet.
The README needs some updates though, only in the beginning version 3B is mentioned, further down only 1 and 2.

# 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="
Copy link
Contributor

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?

Copy link
Member Author

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 👍

@aristosv
Copy link

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
./build.sh

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.
I put the same microsd on an rpi2 and it worked just fine.

What I'm I doing wrong here?

@Mausy5043
Copy link
Contributor

Try this:

git clone https://github.com/debian-pi/raspbian-ua-netinst.git
git checkout v1.1.x
./build.sh

@aristosv
Copy link

root@debian:~/project# git checkout v1.1.x
fatal: Not a git repository (or any of the parent directories): .git

@aristosv
Copy link

oops, I had to go in the folder.

@m1dnight
Copy link

I have tried building the image from the branch v1.1.x and I get a kernel panic. I would give more information but it scrolls by so fast I can't show much.

Anyone else experiencing this?

@CWempe
Copy link
Contributor

CWempe commented Jul 17, 2017

Yes, it is a known issue.
The workaround is to edit the config.txt.
#472

But I am not sure what the solution will be.
Will down-/upgrading the firmware or kernel solve this?

@Mausy5043
Copy link
Contributor

Please retry with the current v1.1.x branch (w/ #475 merged).

@CWempe
Copy link
Contributor

CWempe commented Jul 19, 2017

I just tried a version I compiled yesterday.
raspbian-ua-netinst-20170718-gite45eac1.zip

Bu still get the kernel panic. :(

git log show this:

commit e45eac12a09f1f8478a62ed320eda4b4d4a1717c
Author: Diederik de Haas <github@cknow.org>
Date:   Sun Jul 16 21:12:08 2017 +0200

    Add HWRNG kernel module back and explicitly load the module. (#479)

    It was built-in with kernel 4.4, but with 4.9 it is once again built as
    a kernel module (like it was before 4.4).

commit 55e2963758778329d77609ffbd17902584536333
Merge: 93d2a91 8bf1b33
Author: Diederik de Haas <github@cknow.org>
Date:   Sat Jul 15 17:41:18 2017 +0200

    Merge pull request #475 from Mausy5043/kernel-4.9

    Change to Raspbian Kernel 4.9

So I think I am using the right branch/version.

@Mausy5043
Copy link
Contributor

@CWempe and with UART disabled it works (again)?

@diederikdehaas
Copy link
Member Author

I (normally) do my initial install with a serial console, so I can see what happens, and the enable_uart=1 prevents the installation from even starting. Disabling that line made the installation start.
Problem is that I have no clue what's currently happening, but I suspect that the reboot will fail as that enables the uart again.

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'.

@diederikdehaas
Copy link
Member Author

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
RPi-Distro/repo#22
raspberrypi/firmware#553

They may also be dated as I opened those tabs a while ago, but probably worth taking a look

@diederikdehaas
Copy link
Member Author

I suspect that the reboot will fail as that enables the uart again.

And indeed. Reboot failed. Disabling the enable_uart=1 and it booted up.

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.

@Mausy5043
Copy link
Contributor

Mausy5043 commented Jul 19, 2017

PR #480 should fix this.
I've added an option enable_uart which is 0 (disabled) by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants