Summary: | sys-kernel/mips-sources - several kernel build errors - ip28 (PATCH) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Barnabás Virágh <cyborgyn> |
Component: | Current packages | Assignee: | Joshua Kinard <kumba> |
Status: | IN_PROGRESS --- | ||
Severity: | normal | CC: | jstein, matoro_gentoo, mips |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | MIPS | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 711900 | ||
Attachments: |
patch to build fix
My kernel config used to build |
Description
Barnabás Virágh
2020-02-24 17:10:23 UTC
Created attachment 615466 [details]
My kernel config used to build
In the meantime, I managed to netboot the kernel with attached patch (also enabled the fbconsole in it first), and now I have console output during boot, so it seems to be working. Though, the kernel goes panic, since it can't initialize SCSI and ethernet driver, thus cannot mount root. But this will be a new bug, I guess. I last tested IP28 (real hardware) out about a year ago with a preliminary netboot image I built. Booted to the netboot userland, and got networking to play a little nice, but touching SCSI virtually killed the machine immediately. This is a known problem of the non-coherent nature of IP28 systems on an R10000 processor. I've never used qemu to emulate that machine target, so I can't speak for any issues there, nor really support any. Real hardware only. Which version of mips-sources did you try? I know I dealt with the renaming of the dma_* functions awhile back, but can't remember if I rolled them into a patch or not. arch/mips64 hasn't existed in ages. It's all merged into arch/mips now. I assume ip28_defconfig has a reference to arch/mips64 in it that needs to be removed or changed. That would need to go upstream via the linux-mips mailing list instead of into mips-sources (though I can look at adding it later after 5.6 is released if I can get Octane running again under 5.6). I'll wager your issue with VDSO might stem from attempting to symlink arch/mips to mips64. If not, then that fix would also need to go upstream instead. (In reply to Joshua Kinard from comment #3) > I last tested IP28 (real hardware) out about a year ago with a preliminary > netboot image I built. Booted to the netboot userland, and got networking > to play a little nice, but touching SCSI virtually killed the machine > immediately. This is a known problem of the non-coherent nature of IP28 > systems on an R10000 processor. I've never used qemu to emulate that > machine target, so I can't speak for any issues there, nor really support > any. Real hardware only. No need to, I don't use qemu-system, just the user land chroot, and only for build. I intend to test on real HW, already netbooted it. > Which version of mips-sources did you try? I know I dealt with the renaming > of the dma_* functions awhile back, but can't remember if I rolled them into > a patch or not. sys-kernel/mips-sources-4.19.79::gentoo (I use on all of my machines 4.19.*, since it is the facto stable on all other archs) Though, I can try out 5.* as well, if needed to. > arch/mips64 hasn't existed in ages. It's all merged into arch/mips now. I > assume ip28_defconfig has a reference to arch/mips64 in it that needs to be > removed or changed. That would need to go upstream via the linux-mips > mailing list instead of into mips-sources (though I can look at adding it > later after 5.6 is released if I can get Octane running again under 5.6). > I'll wager your issue with VDSO might stem from attempting to symlink > arch/mips to mips64. If not, then that fix would also need to go upstream > instead. Most probably you are right. My patch is far from professional or any conformance, I can feel that, since I have no knowledge on linux kernel development in general. I just made it as a quick hack, to be able to compile the kernel at least, and to be an exact reference on where I did find problems, and for myself to be able to step closer to a working Indigo2 Impact 10000 linux machine. Though a more professional/thorough fix would be appreciated. I can help testing it, on real hardware. |