0 Members and 7 Guests are viewing this topic.
oh, i have some problems with the final steps,root@noobnonin-GN670AA-ABM-SG3110LA:~/linux# make zimage -j HOSTLD scripts/kconfig/confscripts/kconfig/conf --silentoldconfig Kconfigmake: arm-none-eabi-gcc: Command not foundmake: *** No rule to make target `zimage'. Stop.root@noobnonin-GN670AA-ABM-SG3110LA:~/linux# mv arch/arm/boot/zimage zimage.tnsmv: cannot stat `arch/arm/boot/zimage': No such file or directoryroot@noobnonin-GN670AA-ABM-SG3110LA:~/linux#
kernel linux/zImage.tnsinitrd linux/initrd.tnsboot
Am I missing something ?
By the way, the -j option forkbombed my pc. I recommand to use -j8 instead.
It's probably a good idea to take a look at this. I'm not sure if this will work, but this will certainly help you get a working ARM compiler on your Linux box.
does it means its working and i dont have wifi? or does it means that it still doesnt recognize my dongle?
QuoteAm I missing something ?Yes, you need the bootscript from tangrs.You don't give the kernel the parameter "root=/dev/sda" or "root=/dev/sda1".
If you want to use an initrd, use tangrs first bootloader script, before USB was working.I think it was "root=/dev/mem".
kernel linux/zImage.tnsinitrd linux/initrd.tnscmdline root=/dev/ramboot
Does your kernel support initrds?Which output format did you choose for buildroot?
I did not choosed any format. What should I specify in order to generate an initrd that the kernel will launch like you managed to do today?
(even if the framebuffer doesn't work)
Quote (even if the framebuffer doesn't work)I don't think the initrd and framebuffer problem are related..I could really have tested the wrong kernel the whole time *embarrassed*
And I'm too lazy to change the version number every 10 minutes..
QuoteAnd I'm too lazy to change the version number every 10 minutes..Add an automated script that adds a timestamp to the version number so you don't have to?