On Sun, 2009-02-22 at 17:17 +0100, Holger Gross wrote:
> i use the serial console, no other output is given.
Oh, so the kernel doesn't even begin to boot?
> now i m trying something of
> http://www.nabble.com/kexec-on-mips---anyone-has-it-working--tt17485898.html#a17485898
Maybe I didn't quite
i use the serial console, no other output is given.
now i m trying something of
http://www.nabble.com/kexec-on-mips---anyone-has-it-working--tt17485898.html#a17485898
Am 22.02.2009 17:14, schrieb Brian J. Murrell:
> On Sun, 2009-02-22 at 14:56 +0100, Holger Gross wrote:
>
>> now the kernel lo
On Sun, 2009-02-22 at 14:56 +0100, Holger Gross wrote:
> now the kernel loads, but does not boot:
>
> br-lan: port 1(eth0.0) entering disabled state
> Starting new kernel
> Will call new kernel at 0029d000
> Bye ...
Do you have a serial console on your device? I don't yet. My
TTL-to-RS232 level
now the kernel loads, but does not boot:
br-lan: port 1(eth0.0) entering disabled state
Starting new kernel
Will call new kernel at 0029d000
Bye ...
Am 17.02.2009 19:14, schrieb Brian J. Murrell:
> On Tue, 2009-02-17 at 18:36 +0100, Holger Gross wrote:
>
>> Hi,
>>
>> i have the same problem
On Tue, 2009-02-17 at 18:36 +0100, Holger Gross wrote:
> Hi,
>
> i have the same problem using kexec with buffalo whr g54s openwrt rc2
> kernel 2.4:
>
> kexec_load failed: Success
> entry = 0x298000 flags = 0
> nr_segments = 2
> segment[0].buf = 0x2ac37008
> segment[0].bufsz = 27307b
> s
Hi Holger,
Le Tuesday 17 February 2009 18:36:40 Holger Gross, vous avez écrit :
> Hi,
>
> i have the same problem using kexec with buffalo whr g54s openwrt rc2
> kernel 2.4:
2.4 kernel ? are you sure ? If so, you will not be able to kexec into a new
kernel, this is a 2.6 specific feature.
>
> k
Hi,
i have the same problem using kexec with buffalo whr g54s openwrt rc2
kernel 2.4:
kexec_load failed: Success
entry = 0x298000 flags = 0
nr_segments = 2
segment[0].buf = 0x2ac37008
segment[0].bufsz = 27307b
segment[0].mem = 0x1000
segment[0].memsz = 297000
segment[1].buf = 0x45633
On Fri, 2009-02-06 at 23:45 -0500, Brian J. Murrell wrote:
> I have an asus wl500gp that I'm trying to kexec a kernel on. I had
> written about this before but have another bit of info and I'm hoping it
> rings a bell for someone so that I don't have to through the painful
> process of printk() in
Hi Brian,
Le Saturday 07 February 2009 05:45:44 Brian J. Murrell, vous avez écrit :
> I have an asus wl500gp that I'm trying to kexec a kernel on. I had
> written about this before but have another bit of info and I'm hoping it
> rings a bell for someone so that I don't have to through the painfu
I have an asus wl500gp that I'm trying to kexec a kernel on. I had
written about this before but have another bit of info and I'm hoping it
rings a bell for someone so that I don't have to through the painful
process of printk() instrumenting the kernel and flashing new kernels
with more and more
10 matches
Mail list logo
