>Right, this is still the same data as in your first reply. You can try
>
>flash_unlock -i /dev/mtd1 0 1
>
>. Looking at the device tree no other reason for the flash being RO
>sticks out. The chip has a write-protect input, maybe its status can be
>read out with the RDSR command, but I don't see h
On Sun, 26 Feb 2017 10:45:03 +0100, Uwe Kleine-König wrote:
>>> Without having checked every byte, this looks okish. Is this NAND or NOR
>>> memory?
>>
>> Looks to me like it's NOR:
>I'd something like this:
>
>dd if=/dev/zero of=zero bs=10240 count=1
>flashcp -v zero /dev/mtd1
>memtool md -s /d
On Sat, 25 Feb 2017 22:21:22 +0100, Uwe Kleine-König wrote:
>Without having checked every byte, this looks okish. Is this NAND or NOR
>memory?
Looks to me like it's NOR:
$ cat /sys/class/mtd/mtd?/type |uniq
nor
>If it's NAND, can you please do:
Is there a different test I can do with NOR memor
On Fri, 24 Feb 2017 22:21:58 +0100, Uwe Kleine-König wrote:
>That message is generated in the verify step. So the data that should be
>written to your device cannot be read back.
Yes, that's what I thought. My fear is that the flash chip may have gone bad,
but that would surprise me, since I hav
On Fri, 24 Feb 2017 10:52:39 +0100, Andreas Innerlohninger wrote:
>Did you try to flash kernel and initrd again? (I think 'flash-kernel' without
>arguments
>should do it.)
I did, first with no arguments and then with --force 3.2.0-4-kirkwood
(because that version of the kernel is still installed
On Fri, 24 Feb 2017 10:52:39 +0100, Andreas Innerlohninger wrote:
>Did you try to flash kernel and initrd again? (I think 'flash-kernel' without
>arguments
>should do it.)
I did, first with no arguments and then with --force 3.2.0-4-kirkwood
(because that version of the kernel is still installed
I just did an apt-get upgrade to apply the DSA-3791-1 security update from
two days ago, and flash-kernel produced this warning for both the kernel and
initramfs:
File does not seem to match flash data.
I'm now afraid to reboot this box (a QNAP TS-119P+ NAS) in case corrupt
kernel and initrd im
On Fri, 10 Feb 2017 14:15:28 -0800, Martin Michlmayr wrote:
>> Aside from the problem of how to set kernel parameters on QNAP
>> devices, the SECURITY_APPARMOR kernel option is not enabled on armel
>> kernels due to size restrictions on some machines.
>
>I should have made it clearer that "some ma
On Fri, 10 Feb 2017 14:06:20 -0800, Martin Michlmayr wrote:
>> I don't know about that specific board, but in general, you can edit
>> /etc/default/flash-kernel and add the command line parameters there,
>> then run flash-kernel and reboot.
>
>That won't work with the QNAP devices which don't use
Hi, folks.
How do I add arguments to the kernel boot command line for Debian Jessie on
a Marvell Kirkwood device?
I want to use AppArmor on a QNAP NAS, and the wiki says I need to enable the
appropriate LSM with kernel args apparmor=1 security=apparmor, but I don't
know how to configure this on D
10 matches
Mail list logo
