[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#562205: linux-image-2.6.32-trunk-orion5x: Not more mtd device => impossible to flash new kernel



On 24/12/2009 16:14, Martin Michlmayr wrote:
* Eric Valette<eric.valette@free.fr>  [2009-12-24 00:11]:
Yes it is on a DNS 323. But how will this be fixed? Is it possible to
recreate the mtd devices after having flashed a kernel without proper
in kernel support? Or will you find a way to upload the drivers via
correct modules and recreate the needed devices manually?

It will be fixed in the next kernel upload.  Most people don't run
kernels from unstable so it will be fixed before the package moves to
testing.  If you run a stable from unstable, you have to expect
breakage from time to time.

So you expect people to kill their machine to test for debian maintainers right? If nobody tests, you will not find the bug before it enters testing... Why don't you test on your own before uploading? We are not like on a PC where yo can always find a cdrom and a iso image to recover.

If loading the module doesn't work, I see
two possibilities to recover your machine:

  - maybe you can use kexec to execute a good kernel and then write it
    to flash.

What is the correct procedure and what kernel is supposed to work?


  - use the serial console (as documented on my web page).

So you advice people to do soldering and buying hardware parts.


I'm rather disappointed by the lack of testing that has been done on this kernel.

At least give some direction to fix the problem (kexec, correct kernel, ...)

-- eric







Reply to: