On Mon, 2014-11-17 at 19:13 +, David Edmondson wrote:
> On Mon, Nov 17 2014, Pedro Bulach wrote:
> > I am stuck at a similar situation, where the kernel is loaded but
> > fails to boot the box. A screenshot is attached. I have built upstream
> > kernels 3.17.2 and 3.18-rc4 over the weekend, bot
On Mon, Nov 17 2014, Pedro Bulach wrote:
> On 17 November 2014 17:13, David Edmondson wrote:
>> On Mon, Nov 17 2014, Pedro Bulach wrote:
>>> I am stuck at a similar situation, where the kernel is loaded but
>>> fails to boot the box. A screenshot is attached. I have built upstream
>>> kernels 3.17
On 17 November 2014 17:13, David Edmondson wrote:
> On Mon, Nov 17 2014, Pedro Bulach wrote:
>> I am stuck at a similar situation, where the kernel is loaded but
>> fails to boot the box. A screenshot is attached. I have built upstream
>> kernels 3.17.2 and 3.18-rc4 over the weekend, both with the
On Mon, Nov 17 2014, Pedro Bulach wrote:
> I am stuck at a similar situation, where the kernel is loaded but
> fails to boot the box. A screenshot is attached. I have built upstream
> kernels 3.17.2 and 3.18-rc4 over the weekend, both with the same
> results.
I built a kernel according to the inst
On 17 November 2014 10:43, David Edmondson wrote:
> On Mon, Nov 17 2014, Pedro Bulach wrote:
>> I am stuck at a similar situation, where the kernel is loaded but
>> fails to boot the box. A screenshot is attached. I have built upstream
>> kernels 3.17.2 and 3.18-rc4 over the weekend, both with the
On Mon, Nov 17 2014, Pedro Bulach wrote:
> I am stuck at a similar situation, where the kernel is loaded but
> fails to boot the box. A screenshot is attached. I have built upstream
> kernels 3.17.2 and 3.18-rc4 over the weekend, both with the same
> results.
The image you provided looks like the
On Mon, Nov 17 2014, Ian Campbell wrote:
>> Having built a kernel[1] with CONFIG_FB_SIMPLE and adding the
>> flash-kernel support, I can properly generate the kernel, initrd and dtb
>> images, but the result still doesn't usefully boot.
>>
>> When I run 'bootm ...' there is some text printed by th
On Mon, 2014-11-17 at 08:13 +, David Edmondson wrote:
> On Thu, Nov 13 2014, Pedro Bulach wrote:
> >>> Looking at the Debian kernel configuration, it appears that
> >>> CONFIG_FB_SIMPLE is not enabled in the armmp kernel. This would appear
> >>> to be a requirement for the simplefb variant of u
On Thu, Nov 13 2014, Pedro Bulach wrote:
>>> Looking at the Debian kernel configuration, it appears that
>>> CONFIG_FB_SIMPLE is not enabled in the armmp kernel. This would appear
>>> to be a requirement for the simplefb variant of u-boot (can anyone
>>> confirm?).
>>
>> I think we could pretty saf
On Thu, 2014-11-13 at 11:13 -0200, Pedro Bulach wrote:
> On 13 November 2014 10:12, Ian Campbell wrote:
> >> Looking at the Debian kernel configuration, it appears that
> >> CONFIG_FB_SIMPLE is not enabled in the armmp kernel. This would appear
> >> to be a requirement for the simplefb variant of
On 13 November 2014 10:12, Ian Campbell wrote:
> On Thu, 2014-11-13 at 07:06 +, David Edmondson wrote:
>> On Tue, Nov 11 2014, Pedro Bulach wrote:
>> > setenv bootargs 'cros_legacy console=ttySAC3,115200 debug earlyprintk
>> > root=/dev/sda4 rootfstype=ext4 rootwait rw'
>>
>> Do you have a ser
>> This may be the case. I have two quick questions:
>> 1. is nv u-boot clearly identified in its version string? Or how can
>> I check that?
>
> Using nv_uboot-snow-simplefb.kpart, the version number I see is
> "2011.12-gc1f6280". Nothing in the version string specifically calls out
> that this i
On Thu, 2014-11-13 at 07:06 +, David Edmondson wrote:
> On Tue, Nov 11 2014, Pedro Bulach wrote:
> > setenv bootargs 'cros_legacy console=ttySAC3,115200 debug earlyprintk
> > root=/dev/sda4 rootfstype=ext4 rootwait rw'
>
> Do you have a serial port wired up? I would expect 'console=tty1' for
>
On Tue, Nov 11 2014, Pedro Bulach wrote:
> setenv bootargs 'cros_legacy console=ttySAC3,115200 debug earlyprintk
> root=/dev/sda4 rootfstype=ext4 rootwait rw'
Do you have a serial port wired up? I would expect 'console=tty1' for
simplefb.
Looking at the Debian kernel configuration, it appears tha
On Wed, Nov 12 2014, Pedro Bulach wrote:
> On 12 November 2014 06:40, David Edmondson wrote:
>> Pedro, I don't have any solutions for you, but I'd like to understand
>> better what you have tried.
>>
>> On Tue, Nov 11 2014, Pedro Bulach wrote:
>>> The pending issues are the following:
>>> 1. nv u
On 12 November 2014 07:07, Ian Campbell wrote:
> On Tue, 2014-11-11 at 18:14 -0200, Pedro Bulach wrote:
>> Is this config/kernel supposed to work on this hw?
>
> I tested on arndale when I added the Exynos support to the kernel, I
> don't know how different an xe303c12 is from that or what platfor
On 12 November 2014 06:40, David Edmondson wrote:
> Pedro, I don't have any solutions for you, but I'd like to understand
> better what you have tried.
>
> On Tue, Nov 11 2014, Pedro Bulach wrote:
>> The pending issues are the following:
>> 1. nv u-boot does not load by boot command file
>
> This
On Tue, 2014-11-11 at 18:14 -0200, Pedro Bulach wrote:
> Is this config/kernel supposed to work on this hw?
I tested on arndale when I added the Exynos support to the kernel, I
don't know how different an xe303c12 is from that or what platforms
other folks have tested.
At the very least I'd expec
Pedro, I don't have any solutions for you, but I'd like to understand
better what you have tried.
On Tue, Nov 11 2014, Pedro Bulach wrote:
> The pending issues are the following:
> 1. nv u-boot does not load by boot command file
This is not clear. Do you mean "nv u-boot is not loaded when I boot
Hello to all,
I have been trying to boot debian's kernel vmlinuz-3.16-3-armmp on the
samsung xe303c12 chromebook. Based on bug #759291 there is now support
for the exynos in the kernel.
Currently I can boot with the chos kernel, but I have not yet been
able to boot with the debian kernel, so I tu
20 matches
Mail list logo
