-
Notifications
You must be signed in to change notification settings - Fork 2
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
Building on Fedora Core 25 x64 #1
Comments
Linux v2.6.35.14 booted properly on the PS2, to my surprise. 😄 I borrowed initrd.gz from the BlackRhino Linux Distribution just to start with something and avoid formatting the USB. I’m considering updating to Linux v4.12. |
buildroot linux-dev The compilers are a bit of a mess. There are too many compilers needed right now:
But it seems the compiler built by ./build-toolchain.sh was not found in your path. Using the buildroot compiler is perhaps a much better idea. Do you think you can somehow get linux-dev scripts to use the buildroot compilers? The usb formatting is a personal choise I guess. For more rapid development cycles I suggest loading the kernel from HTTP and copying the kernel to /var/www. And changing the kernelloader config. buildroot linux
Congratulations adn good luck! |
Thanks! I will need to go through all changes eventually. I squashed all commits on your
Your 2.6.35.14 kernel (that works) doesn’t print more than this either, so I suspect there is some patches that need to be applied to get the kernel to continue printing via the network console (ps2link). The frame buffer isn’t initialised so I believe it hangs somewhere very early, but I don’t know where. |
I’ve pushed v4.12 for PS2. It’s on the |
De debug messages stop as soon as the IOP drivers are loaded. I believe you can still get debug messages if you disable the IOP modules, but I'm not sure becouse I don't use ps2link for debugging. For kernel development the best debugging is a serial cable (requires some soldering and a usb-serial converter). I use it all the time, you can also login over the serial cable. Search psx-scene for instructions on how to make such a cable. But nice work already! When I have some time I'll see if I can build your kernel and get some debug messages. |
Thanks Rick, that would be great! I’m somewhat stuck without effective ability to debug at the moment. It seems the shared memory printk for PS2 link patch ported from kernelloader at the top of my branch is causing crashes as well because when I put an |
Some obvious files related to firmware and frame buffer were missing so I’ve updated those now. Some drivers were lost too, will look into them next. |
I believe all important drivers compile in the latest push to ps2-v4.12-squashed. Still no progress on getting the frame buffer to initialise though. |
I tried your kernel but it doesn't compile:
What config are you using? |
Thanks! I’m using arch/mips/configs/ps2_defconfig which I try to keep current on the branch. I can try I’m trying to get http work with kernelloader, but it has issues and mostly hangs ( I’m considering ways to proceed, for example provisionally removing |
A
|
Now kernel and initrd loading via http work. 😄 Apparently one must do “Save Config on MC0” in kernelloader once, and then restart (a couple of times?). Not having a saved config on MC0 seems to be buggy. I briefly replaced SimpleHTTPServer with Nginx but then
|
The defconfig does build. I had the serial driver added to it (you just committed the driver), but there are zero messages from Linux over the serial port. Note that you see a little more messages from the IOP before it crashes.
|
Parts of
I’d guess these are of interest:
|
I backtracked a bit and now have a compiling and booting
and some simpler files. It will take a few moments to resolve this carefully. 😄 |
Yes, I got stuck at 3.8 for a reason. I was actually hoping to reach 3.10 becouse of the long term support. Rebasing one kernel version at a time is probably a better way to see what's changed, and fix it before continuing. |
It turns out most conflicts to v3.9 are whitespace. However, there is a kernel panic during boot (a memory fault). A Git bisect reveals that this happens in exactly v3.9-rc1 commit 64b3122 which is actually a very small change:
|
I've had some trouble compiling the toolchain, too. Both binutils and gcc have some not-so-clear dependencies, where the configure script does not complain but compiliation breaks with misleading errors. Edit: No, I don't... Building toolchain's binutils still fails with
But even after commenting out this struct binutils won't compile - I guess my GCC 6.3 is too new for binutils 2.24. |
First of all, many thanks for putting this together so far! I tried to build a live Linux image using
./build-all.sh
from scratch and had to make a few minor changes:There’s a problem with the upstream hash for
buildroot/package/iperf/iperf.hash
, as explained here.The error
cp: cannot create regular file '../usb-stick/boot-overlay/BOOT/buildrootconfig.txt': No such file or directory
seems to be solved after a manualmkdir usb-stick/boot-overlay/BOOT
. Similarly,cp: cannot create regular file '../linux/firmware/ps2/ps2dev9.irx': No such file or directory Makefile:29: recipe for target '../linux/firmware/ps2/ps2dev9.irx' failed
seems to need a manualmkdir linux/firmware/ps2
.kernelloader/png2rgb/png2rgb.c
needs some simple updates (could be improved) to compile with a newer PNG library:Then I had the error
and so I tried to use the compiler in
buildroot/output/host/usr/bin
instead, via a few symlinks and settingTOOLCHAIN=mipsel
inconfig/config.cfg
(I’m not sure this actually works in practice). Next,seems to be a problem fixed here. Then the error
came up, but it disappeared after running
./build-all.sh
again, which completed the build.I’d like to avoid the final step of formatting the entire USB stick, and instead create a boot file in the existing USB file system. I’ll look into the
./create
script and see if I can figure out how to change that.The text was updated successfully, but these errors were encountered: