Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Bootable 64-bit RPi3 Gentoo image (OpenRC/Xfce/VC4) UPDATED
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 17, 18, 19  
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Tue Mar 12, 2019 6:10 pm    Post subject: Reply with quote

salfter wrote:
I'm trying to block the 4.19.* kernel from installing since it has some USB problems described elsewhere. I have this in /etc/portage/package.mask/bcmrpi3-kernel-bis-bin:

Code:
=sys-kernel/bcmrpi3-kernel-bis-bin-4.19.25.20190226


I tried this first:

Code:
>=sys-kernel/bcmrpi3-kernel-bis-bin-4.19


Both of these are ignored when I emerge @world; it keeps wanting to pull in the newer kernel instead of leaving the 4.14.* kernel alone. This is blocking an update of other packages (though I suppose I could get the list of ebuilds to be updated, filter out the kernel update, and do the rest).


It shouldn't be blocking now: I have reduced the minimum kernel version in the metapackage (here) to 4.14.

Try running:
Code:
demouser@pi64 ~ $ sudo emaint sync --repo rpi3

to pick this up, and then hopefully your kernel mask will apply, and you can update @world to downgrade to 4.14.
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
salfter
n00b
n00b


Joined: 02 Jan 2003
Posts: 60

PostPosted: Tue Mar 12, 2019 7:37 pm    Post subject: Reply with quote

Sakaki wrote:
It shouldn't be blocking now: I have reduced the minimum kernel version in the metapackage (here) to 4.14.

Try running:
Code:
demouser@pi64 ~ $ sudo emaint sync --repo rpi3

to pick this up, and then hopefully your kernel mask will apply, and you can update @world to downgrade to 4.14.


I had already synced that version of the ebuild through. It's still trying to upgrade the kernel. After getting a list of packages to upgrade and filtering out sys-kernel/bcmrpi3-kernel-bis-bin, sys-boot/rpi3-64bit-firmware, and dev-embedded/rpi3-64bit-meta (all of which upgrades are masked), it looks like I can update the remaining packages.
Back to top
View user's profile Send private message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Tue Mar 12, 2019 7:52 pm    Post subject: Reply with quote

Hmm, that's strange. What do you get if you run:
Code:
demouser@pi64 ~ $ equery d sys-kernel/bcmrpi3-kernel-bis-bin

_________________
Regards,

sakaki
Back to top
View user's profile Send private message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Wed Mar 13, 2019 1:30 pm    Post subject: Reply with quote

For those who prefer a NOOBS-style installer, the v1.4.1 gentoo-on-rpi3-64bit images are now also available for install through PINN (called gentoo64 (=regular) and gentoo64pt (=pi-top) there).

Best, sakaki

PS: Many thanks to procount for helping me set up my own PINN repository (https://isshoni.org/pinn/os), and kindly linking it into the official set!
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
salfter
n00b
n00b


Joined: 02 Jan 2003
Posts: 60

PostPosted: Wed Mar 13, 2019 10:40 pm    Post subject: Reply with quote

Sakaki wrote:
Hmm, that's strange. What do you get if you run:
Code:
demouser@pi64 ~ $ equery d sys-kernel/bcmrpi3-kernel-bis-bin


Code:
 * These packages depend on sys-kernel/bcmrpi3-kernel-bis-bin:
dev-embedded/rpi3-64bit-meta-1.3.2 (boot-fw ? >=sys-kernel/bcmrpi3-kernel-bis-bin-4.14.44.20180601[with-matching-boot-fw(-),pitop(-)?])
                                   (!boot-fw ? >=sys-kernel/bcmrpi3-kernel-bis-bin-4.14.44.20180601[-with-matching-boot-fw(-)])
Back to top
View user's profile Send private message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Thu Mar 14, 2019 9:30 am    Post subject: Reply with quote

If that's the only dep you have, it should update OK. Try pulling the repo again:
Code:
demouser@pi64 ~ $ sudo emaint sync --repo rpi3

then does
Code:
demouser@pi64 ~ $ emerge -avu rpi3-64bit-meta

work? If not, what does it output as the blocker?
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
salfter
n00b
n00b


Joined: 02 Jan 2003
Posts: 60

PostPosted: Thu Mar 14, 2019 8:38 pm    Post subject: Reply with quote

Sakaki wrote:
If that's the only dep you have, it should update OK. Try pulling the repo again:
Code:
demouser@pi64 ~ $ sudo emaint sync --repo rpi3

then does
Code:
demouser@pi64 ~ $ emerge -avu rpi3-64bit-meta

work? If not, what does it output as the blocker?


Code:

Local copy of remote index is up-to-date and will be used.
This action requires superuser access...
Would you like to add --pretend to options? [Yes/No] y

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 KiB


I believe that's the desired behavior...trying
Code:
sudo emerge -auNDv --keep-going=y @world
now:

Code:

Local copy of remote index is up-to-date and will be used.

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 KiB

!!! The following update has been skipped due to unsatisfied dependencies:

sys-kernel/bcmrpi3-kernel-bis-bin:0

  selected: (sys-kernel/bcmrpi3-kernel-bis-bin-4.14.90.20181222:0/0::rpi3, installed)
  skipped: (sys-kernel/bcmrpi3-kernel-bis-bin-4.19.25.20190226:0/0::rpi3, ebuild scheduled for merge) (see unsatisfied dependency below)

!!! All ebuilds that could satisfy "~sys-boot/rpi3-64bit-firmware-1.20190215[pitop(-)?,-dtbo(+)]" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-boot/rpi3-64bit-firmware-1.20190215::rpi3 (masked by: package.mask)

(dependency required by "sys-kernel/bcmrpi3-kernel-bis-bin-4.19.25.20190226::rpi3" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.



Nothing to merge; quitting.


I didn't get that the first time around, though...I think having --autounmask-write in EMERGE_DEFAULT_OPTS was the source of the problem. Adding --autounmask-keep-masks to EMERGE_DEFAULT_OPTS should keep masked packages masked while still allowing keyword and USE flag changes, which is why I usually have --autounmask-write on my Gentoo boxen.
Back to top
View user's profile Send private message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Thu Mar 14, 2019 9:21 pm    Post subject: Reply with quote

Looks like something you have in /etc/package.mask/... locally is blocking sys-boot/rpi3-64bit-firmware-1.20190215: there's no rpi3-overlay mask affecting that package other than this one:
Code:
# mask erroneously tagged version
=sys-boot/rpi3-64bit-firmware-1.20180417

which obviously doesn't apply in this case.

Do you have any applicable entries in /etc/package.mask/... ?
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
salfter
n00b
n00b


Joined: 02 Jan 2003
Posts: 60

PostPosted: Thu Mar 14, 2019 10:08 pm    Post subject: Reply with quote

/etc/portage/package.mask/ has the following:

Code:
::::::::::::::
/etc/portage/package.mask/avrdude
::::::::::::::
=dev-embedded/avrdude-9999

::::::::::::::
/etc/portage/package.mask/bcmrpi3-kernel-bis-bin
::::::::::::::
>=sys-kernel/bcmrpi3-kernel-bis-bin-4.19.25.20190226

::::::::::::::
/etc/portage/package.mask/mjpg-streamer
::::::::::::::
=media-video/mjpg-streamer-9999

::::::::::::::
/etc/portage/package.mask/rpi3-64bit-firmware
::::::::::::::
>=sys-boot/rpi3-64bit-firmware-1.20190215

::::::::::::::
/etc/portage/package.mask/rpi3-64bit-meta
::::::::::::::
>=dev-embedded/rpi3-64bit-meta-1.4

::::::::::::::
/etc/portage/package.mask/slic3r
::::::::::::::
=media-gfx/slic3r-9999


bcmrpi3-kernel-bis-bin, rpi3-64bit-firmware, and rpi3-64bit-meta would be the files of interest here.
Back to top
View user's profile Send private message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Thu Mar 14, 2019 10:17 pm    Post subject: Reply with quote

So if you remove the files (or move them to another holding directory somewhere):
/etc/portage/package.mask/bcmrpi3-kernel-bis-bin
/etc/portage/package.mask/rpi3-64bit-firmware
/etc/portage/package.mask/rpi3-64bit-meta

can you then update @world?
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
salfter
n00b
n00b


Joined: 02 Jan 2003
Posts: 60

PostPosted: Thu Mar 14, 2019 10:25 pm    Post subject: Reply with quote

Sakaki wrote:
So if you remove the files (or move them to another holding directory somewhere):
/etc/portage/package.mask/bcmrpi3-kernel-bis-bin
/etc/portage/package.mask/rpi3-64bit-firmware
/etc/portage/package.mask/rpi3-64bit-meta

can you then update @world?


The intent with those files is to keep the kernel from being updated to 4.19 until its USB issues are sorted. Removing them would cause the kernel to update to 4.19, which I don't want to have happen.

Everything else is up-to-date AFAIK, so emerge @world shouldn't pull in anything new until other packages are updated.
Back to top
View user's profile Send private message
Sakaki
Apprentice
Apprentice


Joined: 21 May 2014
Posts: 269

PostPosted: Thu Mar 14, 2019 10:33 pm    Post subject: Reply with quote

OK I understand I think.

The problem is that you need to remove the file:
/etc/portage/package.mask/rpi3-64bit-meta

and (if you wish) also:
/etc/portage/package.mask/rpi3-64bit-firmware

Just leave the file:
/etc/portage/package.mask/bcmrpi3-kernel-bis-bin

That should be sufficient.
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM All times are GMT
Goto page Previous  1, 2, 3 ... 17, 18, 19
Page 19 of 19

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum