[opensuse-arm] Kiwi problem for raspberry pi image
Hi, Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition. Any idea why? So that we could fix it? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it?
Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot? That's how we boot the chromebook, and it makes life a lot easier. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25 January 2013 13:34, Alexander Graf <agraf@suse.de> wrote:
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it?
Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier.
How would one set that up within kiwi or whatever? I think that may be the solution to getting the Snowball working. The only working image I have is from over a year ago. -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 14:41, Andrew Wafaa wrote:
On 25 January 2013 13:34, Alexander Graf <agraf@suse.de> wrote:
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it?
Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier.
How would one set that up within kiwi or whatever? I think that may be the solution to getting the Snowball working. The only working image I have is from over a year ago.
Check out the chromebook image description and kiwi patch. You need a "jump partition" which kiwi leaves free for you to use. Then you create a special jump FS in your u-boot-install script. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier.
Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Guillaume
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier.
Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack.
Sure, but that does not mean that /boot needs to be on FAT, right? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 25/01/2013 14:45, Alexander Graf a écrit :
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier. Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Sure, but that does not mean that /boot needs to be on FAT, right?
Not sure I understand what you mean. Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this bootloader is looking for kernel image on the FAT partition, so we need to have it their. I thought what was done with OMAP at the beginning was a FAT boot partition which was mounted on /boot folder from ext3 partition. Guillaume
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 14:53, Guillaume Gardet wrote:
Le 25/01/2013 14:45, Alexander Graf a écrit :
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier. Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Sure, but that does not mean that /boot needs to be on FAT, right?
Not sure I understand what you mean. Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this bootloader is looking for kernel image on the FAT partition, so we need to have it their.
Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition. That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi. That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition. Hence, /boot can be ext3. You need a jump partition with * closed source binary bootloader * u-boot
I thought what was done with OMAP at the beginning was a FAT boot partition which was mounted on /boot folder from ext3 partition.
On OMAP, we are completely FAT-free by now, since we can store the intermediate loader in a hard sector offset on the SD card. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 25/01/2013 15:00, Alexander Graf a écrit :
On 25.01.2013, at 14:53, Guillaume Gardet wrote:
Le 25/01/2013 14:45, Alexander Graf a écrit :
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier. Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Sure, but that does not mean that /boot needs to be on FAT, right? Not sure I understand what you mean. Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this bootloader is looking for kernel image on the FAT partition, so we need to have it their. Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi.
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition.
Hence, /boot can be ext3. You need a jump partition with
* closed source binary bootloader * u-boot
Ok, so we should add another boot stage with u-boot. Ok, I understand what you want to do. Will kiwi install u-boot in the FAT partition? Is there some value added with u-boot except this workaround? Otherwise, we will get a longer boot time for "nothing".
I thought what was done with OMAP at the beginning was a FAT boot partition which was mounted on /boot folder from ext3 partition. On OMAP, we are completely FAT-free by now, since we can store the intermediate loader in a hard sector offset on the SD card.
Yes, I know. I was talking about the state at the beginning for reference. Guillaume
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 25/01/2013 15:07, Guillaume Gardet a écrit :
Le 25/01/2013 15:00, Alexander Graf a écrit :
On 25.01.2013, at 14:53, Guillaume Gardet wrote:
Le 25/01/2013 14:45, Alexander Graf a écrit :
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
> Hi, > > Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. > All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition. > > Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier. Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Sure, but that does not mean that /boot needs to be on FAT, right? Not sure I understand what you mean. Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this bootloader is looking for kernel image on the FAT partition, so we need to have it their. Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi.
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition.
Hence, /boot can be ext3. You need a jump partition with
* closed source binary bootloader * u-boot
Ok, so we should add another boot stage with u-boot. Ok, I understand what you want to do. Will kiwi install u-boot in the FAT partition?
Is there some value added with u-boot except this workaround? Otherwise, we will get a longer boot time for "nothing".
I would like to add that there is no serial available on the Pi for playing with u-boot. :( Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
El 25/01/13 11:24, Guillaume Gardet escribió:
I would like to add that there is no serial available on the Pi for playing with u-boot. :(
Yes there is.. here is mine https://lh6.googleusercontent.com/-96xHLAsxtfU/UNzMJ44fO4I/AAAAAAAAALs/2s6eA... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 15:24, Guillaume Gardet wrote:
Le 25/01/2013 15:07, Guillaume Gardet a écrit :
Le 25/01/2013 15:00, Alexander Graf a écrit :
On 25.01.2013, at 14:53, Guillaume Gardet wrote:
Le 25/01/2013 14:45, Alexander Graf a écrit :
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit : > On 25.01.2013, at 14:30, Guillaume Gardet wrote: > >> Hi, >> >> Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. >> All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition. >> >> Any idea why? So that we could fix it? > Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot? > > That's how we boot the chromebook, and it makes life a lot easier. Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Sure, but that does not mean that /boot needs to be on FAT, right? Not sure I understand what you mean. Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this bootloader is looking for kernel image on the FAT partition, so we need to have it their. Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi.
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition.
Hence, /boot can be ext3. You need a jump partition with
* closed source binary bootloader * u-boot
Ok, so we should add another boot stage with u-boot. Ok, I understand what you want to do. Will kiwi install u-boot in the FAT partition?
Is there some value added with u-boot except this workaround? Otherwise, we will get a longer boot time for "nothing".
I would like to add that there is no serial available on the Pi for playing with u-boot. :(
There's no need to play with it for end users. Also, u-boot supports graphics in general, so eventually I would imagine there will be a graphical u-boot that users can then play with again. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 25.01.2013 15:24, schrieb Guillaume Gardet:
I would like to add that there is no serial available on the Pi for playing with u-boot. :(
Yes, there is. I don't know if U-Boot does support it, but the RPi certainly has a serial console port. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
El 25/01/13 13:31, Stefan Seyfried escribió:
Am 25.01.2013 15:24, schrieb Guillaume Gardet:
I would like to add that there is no serial available on the Pi for playing with u-boot. :(
Yes, there is. I don't know if U-Boot does support it, but the RPi certainly has a serial console port.
Yeah, as you can see in the pic I posted, there is the pin configuration connected to a USB serial cable, it worked just fine. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 25/01/2013 17:34, Cristian Rodríguez a écrit :
El 25/01/13 13:31, Stefan Seyfried escribió:
Am 25.01.2013 15:24, schrieb Guillaume Gardet:
I would like to add that there is no serial available on the Pi for playing with u-boot. :(
Yes, there is. I don't know if U-Boot does support it, but the RPi certainly has a serial console port.
Yeah, as you can see in the pic I posted, there is the pin configuration connected to a USB serial cable, it worked just fine.
Yes there are some pins available for UART, but nothing out of the box. :( Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, Jan 25, 2013 at 05:54:38PM +0100, Guillaume Gardet wrote:
I would like to add that there is no serial available on the Pi for playing with u-boot. :(
Yes, there is. I don't know if U-Boot does support it, but the RPi certainly has a serial console port.
Yeah, as you can see in the pic I posted, there is the pin configuration connected to a USB serial cable, it worked just fine.
Yes there are some pins available for UART, but nothing out of the box. :(
Be careful, you can brick your device if connecting the UART pins directly to a serial cable (wrong Voltage). You need a level converter (e.g. MAX 232). I am writing this just for safety. You all know that, i assume. Johannes -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, friends. I suggest to use the MAX2323 as this chip can be operated with 3.3 V available e.g. from pins at the Raspberry Pi. It operates with 100KHz, the capacitors should have a value of 100 nF. I draws approx. 6-8 mA at idle. Regards Edgar, DJ3PU, from Munich Am 28.01.2013 18:03, schrieb Johannes Poehlmann:
On Fri, Jan 25, 2013 at 05:54:38PM +0100, Guillaume Gardet wrote:
I would like to add that there is no serial available on the Pi for playing with u-boot. :( Yes, there is. I don't know if U-Boot does support it, but the RPi certainly has a serial console port.
Yeah, as you can see in the pic I posted, there is the pin configuration connected to a USB serial cable, it worked just fine. Yes there are some pins available for UART, but nothing out of the box. :( Be careful, you can brick your device if connecting the UART pins directly to a serial cable (wrong Voltage). You need a level converter (e.g. MAX 232).
I am writing this just for safety. You all know that, i assume.
Johannes
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 15:07, Guillaume Gardet wrote:
Le 25/01/2013 15:00, Alexander Graf a écrit :
On 25.01.2013, at 14:53, Guillaume Gardet wrote:
Le 25/01/2013 14:45, Alexander Graf a écrit :
On 25.01.2013, at 14:41, Guillaume Gardet wrote:
Le 25/01/2013 14:34, Alexander Graf a écrit :
On 25.01.2013, at 14:30, Guillaume Gardet wrote:
> Hi, > > Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem. > All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition. > > Any idea why? So that we could fix it? Do you really need the /boot folder to be vfat? Couldn't you live with a FAT jump partition that contains u-boot and then boots the kernel from an ext3 /boot?
That's how we boot the chromebook, and it makes life a lot easier. Raspberry Pi must have a FAT partition with a binary bootloader which init the board and loads directly the kernel image. So, FAT boot partition is mandatory... :( RPi has lots of proprietary/closed soft which does not help to hack. Sure, but that does not mean that /boot needs to be on FAT, right? Not sure I understand what you mean. Rom bootloader loads closed binary bootloader from FAT partition to RAM and then this bootloader is looking for kernel image on the FAT partition, so we need to have it their. Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi.
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition.
Hence, /boot can be ext3. You need a jump partition with
* closed source binary bootloader * u-boot
Ok, so we should add another boot stage with u-boot. Ok, I understand what you want to do. Will kiwi install u-boot in the FAT partition?
This bit you would have to do yourself in the u-boot-install script.
Is there some value added with u-boot except this workaround? Otherwise, we will get a longer boot time for "nothing".
The biggest value added is that we have a boot script that's generic across the board with a /boot file system that is proven to work well with all our scripts.
I thought what was done with OMAP at the beginning was a FAT boot partition which was mounted on /boot folder from ext3 partition. On OMAP, we are completely FAT-free by now, since we can store the intermediate loader in a hard sector offset on the SD card.
Yes, I know. I was talking about the state at the beginning for reference.
There's a reason we moved away from it :) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 25.01.2013 15:00, schrieb Alexander Graf:
Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi.
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition.
Why would we want to do it differently from every other RPi distribution out there? All the HOWTOs tell you to edit cmdline.txt and config.txt, and now we come with our openSUSE boot process and do it differently just because our tools are broken? And we'd even waste some boot time :-) -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 25.01.2013, at 17:29, Stefan Seyfried wrote:
Am 25.01.2013 15:00, schrieb Alexander Graf:
Nonono. The Rom bootloader loads the closed source binary loader from a FAT partition. This bootloader looks for a binary to execute from a FAT partition.
That binary could just as well be https://github.com/gonzoua/u-boot-pi/tree/rpi.
That u-boot could then read a boot.scr from an ext3 partition and load the kernel+initrd from an ext3 partition.
Why would we want to do it differently from every other RPi distribution out there?
All the HOWTOs tell you to edit cmdline.txt and config.txt, and now we come with our openSUSE boot process and do it differently just because our tools are broken?
No, we do it differently because the point of a distribution is consistency across the distribution. If you come from a beagle board, you want to be able to work with a raspberry pi. Chances are a lot less that you come from Debian on raspberry pi to openSUSE on raspberry pi. If you are on Debian, we lost you already ;). Alex
And we'd even waste some boot time :-)
That time should be negligible. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (7)
-
Alexander Graf -
Andrew Wafaa -
Cristian Rodríguez -
Edgar Dombrowski -
Guillaume Gardet -
Johannes Poehlmann -
Stefan Seyfried