| 1 |
Rich Freeman <rich0@g.o> [17-02-25 15:16]: |
| 2 |
> On Sat, Feb 25, 2017 at 8:59 AM, <Meino.Cramer@×××.de> wrote: |
| 3 |
> > Fernando Rodriguez <cyklonite@×××××.com> [17-02-25 14:36]: |
| 4 |
> >> |
| 5 |
> >> Check the CONFIG_INITRAMFS_SOURCE option. |
| 6 |
> >> |
| 7 |
> > |
| 8 |
> > I will check the configs...may be there is something not readable |
| 9 |
> > (permissions) ... I had copied a lot back and forth (I bought one |
| 10 |
> > of those crappy harddiscs, which became full after a while...;) |
| 11 |
> > |
| 12 |
> |
| 13 |
> Did you actually check the CONFIG_INITRAMFS_SOURCE option? It should |
| 14 |
> be blank. If it is not, then whatever file it points to must exist. |
| 15 |
> It might exist on your host, but not in your chroot. |
| 16 |
> |
| 17 |
> This option builds a kernel with an embedded initramfs, which is not |
| 18 |
> normally something you need. Some Linux live DVDs might use something |
| 19 |
> like this, but normal desktops generally do not. If your .config file |
| 20 |
> originated from one of these that could explain the issue. |
| 21 |
> |
| 22 |
> Even if you wanted an initramfs this isn't the way to go about it. |
| 23 |
> |
| 24 |
> (A bit of trivia, Linux actually ALWAYS has an embedded initramfs, but |
| 25 |
> by default it is empty.) |
| 26 |
> |
| 27 |
> -- |
| 28 |
> Rich |
| 29 |
> |
| 30 |
Hi Rich, |
| 31 |
|
| 32 |
yes the option was set for what reason ever...I will clear that. |
| 33 |
Next question...: Do I need v86d still then? |
| 34 |
|
| 35 |
Another thing which drives me crazy: |
| 36 |
Linux-headers! |
| 37 |
emerge insists of installing linux-headers-4.10. I am runnig |
| 38 |
4.9.12. Unstable is globally set (~amd64). |
| 39 |
|
| 40 |
But giviing |
| 41 |
|
| 42 |
emerge sys-kernel/linux-headers-4.9 |
| 43 |
or |
| 44 |
emerge 'sys-kernel/linux-headers-4.9' |
| 45 |
|
| 46 |
gives me |
| 47 |
|
| 48 |
!!! 'sys-kernel/linux-headers-4.9' is not a valid package atom. |
| 49 |
!!! Please check ebuild(5) for full details. |
| 50 |
|
| 51 |
Even |
| 52 |
|
| 53 |
emerge sys-kernel/linux-headers-4.10 |
| 54 |
or |
| 55 |
emerge 'sys-kernel/linux-headers-4.10' |
| 56 |
|
| 57 |
results in |
| 58 |
|
| 59 |
!!! 'sys-kernel/linux-headers-4.10' is not a valid package atom. |
| 60 |
!!! Please check ebuild(5) for full details. |
| 61 |
|
| 62 |
. I only can do |
| 63 |
|
| 64 |
emerge sys-kernel/linux-headers |
| 65 |
|
| 66 |
but (as mentioned above) it installs 4.10. not 4.9. |
| 67 |
v86d does not compile with 4.10. |
| 68 |
|
| 69 |
ebuild (5) suggests to do, what I have done/written above. |
| 70 |
|
| 71 |
Doing a complete rebuild of the root of years of running |
| 72 |
gentoo is a ....hrmmmmm..... intersting...hrmmm....experience... |
| 73 |
;) |
| 74 |
|
| 75 |
Cheers |
| 76 |
Meino |
Archives