This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Vogtinator
Pages: 1 ... 49 50 [51] 52 53 ... 83
751
« on: June 17, 2013, 03:30:20 pm »
ext3, ext4 and probably btrfs, although you want to use ext4. It's still the most common format.
752
« on: June 17, 2013, 03:26:52 pm »
You format your usb drive (or a partition on it) and copy the contents of the buildroot image onto it. Then you can boot from it using "root=/dev/sda<partition>" as param.
753
« on: June 17, 2013, 02:47:29 am »
You can download the buildroot busyboxconfig image, which is called "initrd.tns" on download.
Then you can insert "initrd Linux/initrd.tns" in your bootscript to boot from the initrd.
754
« on: June 16, 2013, 04:14:48 pm »
... or what? The only buildroot image that you can use as initrd is busyboxconfig. And the buildroot is just a usb stick format for the TI's like NTFS for computers or what? Nope, buildroot is the content. The filesystem the initrd has is ext4, the other ones (tar.bz2) are tar-archives.
755
« on: June 16, 2013, 04:06:07 pm »
Short answer: No
Long answer: No MMU, too little RAM, too little ROM
756
« on: June 16, 2013, 10:31:43 am »
Strange, I didn't have to change my /etc/fstab, although I'm using ext4 as well.
There were only two lines saying "can't mount as ext2, trying ext3" and "can't mount as ext3, trying ext4"..
757
« on: June 16, 2013, 10:10:45 am »
You can't use the xconfig as initrd. It won't fit in RAM, so decompressing fails. The only buildroot image that you can use as initrd is busyboxconfig. The other ones are intended to be untar'd onto an USB drive or similiar (NFS root  )
758
« on: June 12, 2013, 04:23:51 pm »
You can try USB OTG, in the wiki you'll find a kernel boot param which will enable it. Good luck!
759
« on: June 12, 2013, 03:34:12 pm »
It prints IO errors, try to reformat the usb drive.
Edit: Got confused about storages
760
« on: June 12, 2013, 03:03:53 pm »
That looks very nice!
Does it run fast even with textures?
761
« on: June 12, 2013, 02:49:45 pm »
Do you have the most recent versions of kernel, ramdisk and bootloader?
Your bootscript should be like
kernel Linux/zImage.tns
initrd Linux/initrd.tns
cmdline root=/dev/ram
boot
762
« on: June 12, 2013, 01:43:54 pm »
Is the getty error reproducable?
763
« on: June 12, 2013, 12:24:49 pm »
#But linux is still "loading" after 2 hours. Thats very strange# That is indeed very strange. Could you post your exact configuration after you tried to download the newest files (bootloader, kernel and ramdisk)? And for the numbering error, it was gparted's fault because my partition was physically the second one but it was still called sdc3 on my computer. Why does it number partitions in the order you add them to queue ? I know, thats the only reason I use YaST also for partitioning.
764
« on: June 12, 2013, 10:19:28 am »
(guess what, there was a partition numbering error and I was actually mounting a swap partition) The exact same problem (IIRC) two guys already had. It's No.1 of booting issues  But it keeps spamming it can't find /sbin/getty.  That's not good at all. /sbin/getty should exist. You should be able to mount the initrd and check it. Maybe your download is corrupted or I screwed the auto builds up.
765
« on: June 11, 2013, 03:37:24 pm »
The log looks fine to me, so it's time for a new toolchain
Pages: 1 ... 49 50 [51] 52 53 ... 83
|
Show Posts
