modprobe cfi_cmdset_0002 fails
I am running 2.4.27-vrs1 on an AT91RM9200DK.
I have managed to get the latest MTD code to compile with this kernel version and the kernel boots and executes OK (mostly)
Before I compiled in the new MTD code, the kernel detected my Smartmedia card and the Dataflash. Now it seems to fail.
from dmesg:
...
physmap flash device: 200000 at 10000000
CFI: Found no phys_mapped_flash device at location zero
reset unlock called 555 2aa
Search for id:(1f c0) interleave(1) type(2)
MTD jedec_match(): Check fit 0x00000000 + 0x00200000 = 0x00200000 MTD jedec_match(): check unlock addrs 0x0555 0x02aa
MTD jedec_match(): 0x0555 0x0aaa did not match
reset unlock called 555 aaa
Search for id:(1f c0) interleave(1) type(2)
MTD jedec_match(): Check fit 0x00000000 + 0x00200000 = 0x00200000 MTD jedec_match(): check unlock addrs 0x0555 0x0aaa
MTD jedec_match(): check ID's disappear when not in ID mode reset unlock called 555 aaa
MTD jedec_match(): return to ID mode
MTD jedec_probe_chip(): matched device 0x1f,0xc0 unlock_addrs: 0x0555 0x0aaa
Found: Atmel AT49BV16X
reset unlock called 555 aaaphys_mapped_flash: Found 1 x16 devices at 0x0 in 16-bit bank
The NOR Flash is found OK, and it comes up in /proc/mtd
kmod: failed to exec /sbin/modprobe -s -k cfi_cmdset_0002, errno = 2 Support for command set 0002 not presentgen_probe: No supported Vendor Command Set found
kmod: failed to exec /sbin/modprobe -s -k map_rom, errno = 2
...
Why does modprobe fail here? Shouldn't this already be compiled into the kernel?
regards,
Aras
Quoted 30 lines · Aras Vaichas
I am running 2.4.27-vrs1 on an AT91RM9200DK.
I have managed to get the latest MTD code to compile with this kernel version and the kernel boots and executes OK (mostly)
Before I compiled in the new MTD code, the kernel detected my Smartmedia card and the Dataflash. Now it seems to fail.
from dmesg:
...
physmap flash device: 200000 at 10000000
CFI: Found nophys_mapped_flashdevice at location zero
reset unlock called 555 2aa
Search for id:(1f c0) interleave(1) type(2)
MTDjedec_match(): Check fit0x00000000+0x00200000=0x00200000MTDjedec_match(): check unlock addrs0x05550x02aa
MTDjedec_match():0x05550x0aaadid not match
reset unlock called 555 aaa
Search for id:(1f c0) interleave(1) type(2)
MTDjedec_match(): Check fit0x00000000+0x00200000=0x00200000MTDjedec_match(): check unlock addrs0x05550x0aaa
MTDjedec_match(): check ID's disappear when not in ID mode reset unlock called 555 aaa
MTDjedec_match(): return to ID mode
MTDjedec_probe_chip(): matched device 0x1f,0xc0unlock_addrs:0x05550x0aaa
Found: Atmel AT49BV16X
reset unlock called 555 aaaphys_mapped_flash: Found 1 x16 devices at0x0in 16-bit bank
Quoted 1 line
The NOR Flash is found OK, and it comes up in
/proc/mtd
Yep - looks sane so far.
Quoted 7 lines
kmod: failed to exec
/sbin/modprobe-s -kcfi_cmdset_0002, errno = 2 Support for command set 0002 not presentgen_probe: No supported Vendor Command Set found
kmod: failed to exec/sbin/modprobe-s -kmap_rom, errno = 2
...Why does modprobe fail here? Shouldn't this already be compiled into the kernel?
It's only compiled in if it was selected when you configured your kernel. You can enable it in this menu:
Main Menu
Memory Technology Devices (MTD)
RAM/ROM/Flash chip drivers
Support for AMD/Fujitsu flash chips
It's called CONFIG_MTD_CFI_AMDSTD in .config
Signature · 2 lines
Thayne Harbaugh Linux Networx