[josvadolla]

I'm not getting this. Where is the config file to edit to boot the new vmlinux ++ etc. Do you mean we have to compile it with asbestos? I read the asbest os readme from kmeaw git. Saying they are restricted to 16MB RAM, and that you must use the patched kernel from github.

[Ssin]

Guys is there a tutorial in how to do all of this? a link or any think to start a newb.
i instated the Linux with the one image not the one with 10 img it keeps giving me error imag not found... anyways i get the linux running but no internet i don't know how to set it up and then KERNEL V2.6 no idea what to do with it.
please any info to get me started. thanks

[dsapandora]

I was reading my notes from a year ago and I remembered who I did this sutff before...
I manually add these lines to the top-level Makefile, but setting them in the environment should work too:

ARCH=powerpc

CROSS_COMPILE=ppu-

Now you can create a sample configuration file by executing the following command inside the tree:

$ make ps3_defconfig

Then proceed to modify the default configuration to your likings. To ease development, I want my kernels to be as small and easy to install as possible; this reduces the test-build-install-reboot cycle to the minimum (well, not exactly; see below). Therefore I disable all stuff I do not need, which includes modules support. Why? Keeping all the code in a single image will make later installation a lot easier.

Once the kernel is configured, it is time to build it. But before doing so you need to install a helper utility used by the PS3 build code: the Device Tree Compiler (or dtc). Fetch its sources from the git repository that appears in that page, run make to build it and manually install the dtc binary into /usr/local/bin.


Then a vmlinux image will be generated then, you put it whenever you want and Then you modify, the /etc/kboot.conf,
But I see this file is not there anymore...

sudo apt-get install linux-source device-tree-compiler # device-tree-compiler is only needed if you are targeting the PowerPC architecture
************* [ - Post Merged - ] *************

Originally Posted by dsapandora I was reading my notes from a year ago and I remembered who I did this sutff before... I manually add these lines to the top-level Makefile, but setting them in the environment should work too: ARCH=powerpc CROSS_COMPILE=ppu- Now you can create a sample configuration file by executing the following command inside the tree: $ make ps3_defconfig Then proceed to modify the default configuration to your likings. To ease development, I want my kernels to be as small and easy to install as possible; this reduces the test-build-install-reboot cycle to the minimum (well, not exactly; see below). Therefore I disable all stuff I do not need, which includes modules support. Why? Keeping all the code in a single image will make later installation a lot easier. Once the kernel is configured, it is time to build it. But before doing so you need to install a helper utility used by the PS3 build code: the Device Tree Compiler (or dtc). Fetch its sources from the git repository that appears in that page, run make to build it and manually install the dtc binary into /usr/local/bin. Then a vmlinux image will be generated then, you put it whenever you want and Then you modify, the /etc/kboot.conf, But I see this file is not there anymore... sudo apt-get install linux-source device-tree-compiler # device-tree-compiler is only needed if you are targeting the PowerPC architecture

drivers/char/ps3flash.c: In function 'ps3flash_read_write_sectors':
drivers/char/ps3flash.c:50:11: error: too few arguments to function 'ps3stor_read_write_sectors'
/root/linux-2.6-b0fd285/arch/powerpc/include/asm/ps3stor.h:65:12: note: declared here
drivers/char/ps3flash.c: In function 'ps3flash_llseek':
drivers/char/ps3flash.c:108:29: error: 'struct ps3_storage_device' has no member named 'region_idx'
drivers/char/ps3flash.c: In function 'ps3flash_read':
drivers/char/ps3flash.c:138:25: error: 'struct ps3_storage_device' has no member named 'region_idx'
drivers/char/ps3flash.c: In function 'ps3flash_write':
drivers/char/ps3flash.c:207:25: error: 'struct ps3_storage_device' has no member named 'region_idx'
drivers/char/ps3flash.c: In function 'ps3flash_probe':
drivers/char/ps3flash.c:363:24: error: 'struct ps3_storage_device' has no member named 'region_idx'
drivers/char/ps3flash.c:370:24: error: 'struct ps3_storage_device' has no member named 'region_idx'
make[3]: *** [drivers/char/ps3flash.o] Error 1
make[2]: *** [drivers/char] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/root/linux-2.6-b0fd285'
make: *** [debian/stamp/build/kernel] Error 2

[josvadolla]

I got the same error while compiling as well. What I did was to exclude the ps3flash driver. I don't want to be able to write to fllash anyway as it may result in bricked console.

[dsapandora]

I decide to try with the new version that was realesed yesterday, right now I am compiling, and everything for now is looking fine. But I still don't... well About to write in the flash... yeap I hear that is dangerous... I still don't have any idea about what to do in the flash... So I will try without the flash in the new kernel because I get the same error :P

[dsapandora]

Originally Posted by dsapandora I decide to try with the new version that was realesed yesterday, right now I am compiling, and everything for now is looking fine. But I still don't... well About to write in the flash... yeap I hear that is dangerous... I still don't have any idea about what to do in the flash... So I will try without the flash in the new kernel because I get the same error :P

Well I was able to compiled, with make -j1 because the error that I got was because the system get out of memory.

But what to do know

[renzohubi]

Did anybody here successfully boot PS3 Linux using this new kernel (stripped vmlinux, recompile AsbestOS to embed it together with the bootloader)? I tried but resulted in a black screen with no output video signal after stage2 of AsbestOS is launched. My root file system is on an external HDD ext4 format as normal, not stored inside linux.img.