| View previous topic :: View next topic |
| Author |
Message |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3918
|
 Posted: Tue Jul 13, 2021 8:17 pm Post subject: Some uncertainties on RPI install |
 |
|
Hi Guys
Recently someone gave me a RPI 4 model B.
I am following the Wiki on installation but it seems a bit outdated.
I feel uncertain about so many things...
Like for example:
Which tarball do i need?
Which CFLAGS should I use?
Is VIDEO_CARDS="vc4" proper?
And INPUT_DEVICES...?
Why should I download a copy of the portage tree and not run emerge --sync?
Should I not
eselect profile set?
I am planning to use the qemu chroot method..
Any precious advice is most welcome.
Do i need grub?
How large should the /boot partition be?
Do I have to assign it any flags?
Do I need swap?
I am leaning towards
sys-kernel/raspberrypi-image
Should I emerge the 9999 version?
Oh my God.So many questions,yet the Wiki is very frugal and possibly outdated.
I am a bit lost.
Any pointers would be so refreshing.......
Thanks a lot for your attention and tolerance.
_________________
|
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Tue Jul 13, 2021 10:50 pm Post subject: |
|
|
alamahant
| Quote: | | Which tarball do i need? |
That depends. The Pi4 can run 32 bit or 64 bit ARM code but arm64 does not support multilib.
The 64 bit kernel can run either userland.
For 32 bit, use the armv7a talball. For 64 bit use the armv8a tarball.
| Quote: | | Which CFLAGS should I use? |
That depends on your tarball.
VIDEO_CARDS="vc4" is for all the Pis except the 4. Its v3d for the Pi4.
INPUT_DEVICES is standard.
| Quote: | Why should I download a copy of the portage tree and not run emerge --sync?
Should I not
eselect profile set? |
Yes, do that.
| Quote: | | I am planning to use the qemu chroot method.. |
The Pi 4 isn't too shabby a build box but keep it out of thermal throttling. Cross distcc helps. A qemu chroot is slow. Its the emergency fallback.
The Pis have there own boot method. It does not involve EFI or grub.
The boot code runs on the GPU. The CPU is held reset until after the kernel and initrd (if any) are loaded.
| Quote: | How large should the /boot partition be?
Do I have to assign it any flags? |
128M should be big enough for boot. It used to need the bootable flag.
Everyone needs swap. :)
Get the stable Pi Foundation kernel. The -9999 will be the tip of the Pi kernel repo. That's not a good place to start.
The mainline sources have reasonable Pi 4 support now too but go there after you have found your feet.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Tue Jul 13, 2021 10:51 pm Post subject: |
|
|
Moved from Installing Gentoo to Gentoo on ARM.
It's one of these.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3918
|
| Posted: Wed Jul 14, 2021 12:30 am Post subject: |
|
|
Thanks a lot Neddy.
I did a test run--my first with pi.
So Before committing to a Gentoo install I tried it first with Devuans's arm64 image.
I used
| Code: |
zcat <image.zip> | sudo dd of=/dev/sdd bs=64k oflag=dsync status=progress
|
So I got two partitions /boot and /root
I didnt have a means to chroot so I just hacked my way into /etc/shadow creating root passwd etc and edited sshd_config to allow root login with password.
I dont yet have a mini hdmi-to-hdmi cable so i needed ssh.
And
It worked!
I couldnt believe it...
You will not believe the memory usage.
| Code: |
MiB Mem : 3743.4 total, 3600.6 free, 63.8 used, 79.0 buff/cache
MiB Swap: 1024.0 total, 1024.0 free, 0.0 used. 3615.3 avail Mem
|
Tomorrow I am off with the Gentoo installation.
I think I will use the arm64 tarball.
And possibly a new micro sd.
I can have different micro sd for different oses..
Its kind of really cool.
Very very positive impressions from RPI.
_________________
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Wed Jul 14, 2021 8:12 pm Post subject: |
|
|
alamahant,
That's one of these.
I only have /boot on the SD card. Everything else is on a USB3 attached SSD, which was left over from an upgrade.
The SD card is slow compared to a real HDD on USB3.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Wed Aug 18, 2021 9:37 pm Post subject: |
|
|
alamahant,
That all looks good.
Can you put your dmesg onto a pastebin please?
What screen resolution do you use?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3918
|
| Posted: Wed Aug 18, 2021 10:23 pm Post subject: |
|
|
Neddy
I opened this
https://forums.gentoo.org/viewtopic-t-1141117-highlight-.html
If I made an error plz feel free to merge them.
There is a dmesg in my above thread and other pertaining info.
I FOUND IT!!!
In make.conf
VIDEO_CARDS="v4c v3d"
That is I appended v3d.
Now it works flawlessly.
Now only wifi does not work.
rc.log says "inittialized but inactive"
I am a little confused on how to use
sys-firmware/raspberrypi-wifi-ucode
together with
linux-firmware
Thank you so much.......
_________________
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Thu Aug 19, 2021 4:48 pm Post subject: |
|
|
alamahant,
If sys-firmware/raspberrypi-wifi-ucode and linux-firmware both provide the same files they normally block one another.
Install linux-firmware. That will get you a /etc/portage/savedconfig/sys-kernel/linux-firmware-* file.
Edit your /etc/portage/savedconfig/sys-kernel/linux-firmware-* file to remove the files provided by sys-firmware/raspberrypi-wifi-ucode.
Install linux-firmware again. This time the files to be provided by sys-firmware/raspberrypi-wifi-ucode will not be installed and sys-firmware/raspberrypi-wifi-ucode can be installed.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Gentoo on ARM
