3.18.20 = 15.05 final!
Topic: Update on Linksys WRT1900AC support
The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Page 378 of 598
Not sure who provided the wiki information and pictures for the Serial Port section but I found it EXTREMELY useful.
I have just incorporated the header and phone jack installation on my WRT1200AC and works great. Next phase of my project is doing the same for my primary WRT1900ACv1.
Big kudos to whoever provided the info.
(Last edited by kirkgbr on 8 Jan 2016, 16:47)
kirkgbr wrote:
roylaprattep wrote:NemoAlex wrote:Hey guys
If you're looking for compiled .ipk file of mwlwifi for CC final, here is a git repository:
https://github.com/NemoAlex/mwlwifi-binNot downgrading package kmod-mwlwifi on root from 3.18.23+10.3.0.14-20151126-1 to 3.18.20+10.3.0.16-20160105-1.
Why?
On WRT1900ACS.
I assume that is an error you are seeing. My guess is that your kernel version is 3.18.23 but the ipk provided by NemoAlex is for kernel version 3.18.20.
Exactly. CC final doesn't support ACS. So I assume you are using Kaloz's build or trunk build.
In this case you have to compile it by yourself.
gufus wrote:
DD-WRT
FYI
http://news.yahoo.com/linksys-dd-wrt-an … 00137.html
the joke must go on 
unless OEM fw will be DD-WRT i seriously doubt it
(Last edited by makarel on 8 Jan 2016, 17:26)
makarel wrote:
gufus wrote:DD-WRT
FYI
http://news.yahoo.com/linksys-dd-wrt-an … 00137.htmlthe joke must go on
unless OEM fw will be DD-WRT i seriously doubt it
FYI (look up WRT1900AC)
http://www.dd-wrt.com/site/support/router-database
DD-WRT is just another user fw option 
"Today we are honoured to have DD-WRT supporting the complete WRT Series of routers. This gives users that have relied on DD-WRT support for their legacy WRT router applications a powerful hardware upgrade path utilizing the latest in AC Wi-Fi technology and Gigabit wired speeds found in the award-winning WRT1900AC, WRT1200AC, and WRT1900ACS routers," said Vince La Duca, product manager, Linksys
(Last edited by gufus on 8 Jan 2016, 18:11)
gufus wrote:
".. the award-winning WRT1900AC, WRT1200AC, and WRT1900ACS routers," said Vince La Duca, product manager, Linksys
this long long.. very long.. unreadable.. better then an adventure, spy, science book.. hollywood material.. this is how starwars began rolf, thread stands for himself(it has become an entity.. the garbage behind fake smiles).. i wont defend it
(Last edited by makarel on 8 Jan 2016, 18:35)
gufus wrote:
DD-WRT
FYI
http://news.yahoo.com/linksys-dd-wrt-an … 00137.html
For the sake of it, what kernel is it running? Plain vanilla or a custom tree? Also, what version? Has anyone over at DD-WRT given credits to Kaloz for constantly pushing Marvell to release new code more often or are they using a different driver?
nitroshift
(Last edited by nitroshift on 8 Jan 2016, 18:45)
nitroshift wrote:
gufus wrote:DD-WRT
FYI
http://news.yahoo.com/linksys-dd-wrt-an … 00137.htmlFor the sake of it, what kernel is it running? Plain vanilla or a custom tree? Also, what version? Has anyone over at DD-WRT given credits to Kaloz for constantly pushing Marvell to release new code more often or are they using a different driver?
nitroshift
Bingo.... I would imagine that the driver is the same...
I remember reading their forum last week, and people were complaining about the same issues we see....
Cheers
My personal advice is to stay with OpenWrt images. The Brainslayer DD-WRT builds result in my WRT1900ACv2 soft bricking, totally unreachable. (recoverable through on/off process)
Kong's build is ok. But I had random factory resets. One morning I woke up and my router was back on Linksys firmware......
Running Arokh's image, no problems at all. Trunk works well too.
Just pushed the mwlwifi update to both CC and trunk branches to add DFS support. Please note using a DFS channel delays the interface bring-up the first time as it has to wait to be sure the channel is clean.
bmork wrote:
But I guess that is just some scaling problem. Those values look suspiciously like Fahrenheit to me, but there could be something else I'm missing.
In any case, it's here if anyone wants to play with this:
https://github.com/bmork/mwlwifi/commit/hwmon
I think it's definitely Fahrenheit, the maths add up, too.
bmork wrote:
I'm not going to submit this for obvious reasons. It's just for fun
Maybe you should 
Just add proper licensing info and co if you do a pull request.
Kaloz wrote:
bmork wrote:But I guess that is just some scaling problem. Those values look suspiciously like Fahrenheit to me, but there could be something else I'm missing.
In any case, it's here if anyone wants to play with this:
https://github.com/bmork/mwlwifi/commit/hwmonI think it's definitely Fahrenheit, the maths add up, too.
bmork wrote:I'm not going to submit this for obvious reasons. It's just for fun
Maybe you should
Thanks for the encouragement, but it will have to wait until the driver is in mainline. This is not the time for new features of any sort.
Kaloz wrote:
...
Maybe you should
+1
(and maybe you can add a conversion to the proper celcius temp?)
(Last edited by JohnnySL on 8 Jan 2016, 22:32)
nitroshift wrote:
gufus wrote:DD-WRT
FYI
http://news.yahoo.com/linksys-dd-wrt-an … 00137.htmlFor the sake of it, what kernel is it running? Plain vanilla or a custom tree? Also, what version?
nitroshift
Using username "root".
Unauthorized access is prohibited!
Security is enabled, and your IP address has been logged.
Authenticating with public key "rsa-key-20120810"
BusyBox v1.24.1 (2016-01-02 01:17:27 CET) built-in shell (ash)
root@AC-DD-WRT_M:~# uname -r
3.18.25
root@AC-DD-WRT_M:~# strings /lib/ath9k/mwlwifi.ko | grep 10.3
10.3.0.15-20151208
10.3.0.15-20151208
root@AC-DD-WRT_M:~#
JohnnySL wrote:
Kaloz wrote:...
Maybe you should
+1
(and maybe you can add a conversion to the proper celcius temp?)
Sure. Pushed it now.
Sorry about the missing license blob. Didn't realize it would be necessary. This was clearly written as an integral part of the mwlwifi driver, which is GPLv2 only. In any case, I've now added minimalistic GPLv2 blobs just to avoid any uncertainty about that.
doITright wrote:
Bingo.... I would imagine that the driver is the same...
Yes.
Anyone here tried to USB-TTL his/her WRT1200AC and tried to change the fw name with this:
setenv firmware_name firmware_image_name.img (the EXACT name of the firmware file name)For me it still asked for the caiman.img and when I renamed the file to that, it worked, so it seems the setenv firmware_name doesn't work on the WRT1200AC.
johan81 wrote:
Anyone here tried to USB-TTL his/her WRT1200AC and tried to change the fw name with this:
setenv firmware_name firmware_image_name.img (the EXACT name of the firmware file name)For me it still asked for the caiman.img and when I renamed the file to that, it worked, so it seems the setenv firmware_name doesn't work on the WRT1200AC.
I have seen something similar once on my 1900AC v1 with the nand problems... so I always check before executing...
This is from memory so spelling could be off a bit:
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.8
setenv firmware_name openwrt.img
saveenv -> optional
printenv ipaddr serverip firmware_name
ping serverip -> if alive then we can flash
run update_both_images or flash_pri_image or flash_alt_image
Cheers
**Edit** full list of u-boot stuff (lots of cool things in there) http://www.denx.de/wiki/DULG/Manual
(Last edited by doITright on 9 Jan 2016, 01:23)
gufus wrote:
doITright wrote:Bingo.... I would imagine that the driver is the same...
Yes.
So? Don't hold back now...
How is the wireless performance compared to DD(4.1.13) or 4.4rc7/8? How stable?
Maybe a true wireless bridge is possible? Doubt it but need to ask
Cheers
NemoAlex wrote:
Hey guys
If you're looking for compiled .ipk file of mwlwifi for CC final, here is a git repository:
https://github.com/NemoAlex/mwlwifi-bin
Hi, Nemo, thx for your commitment to the country... I will also update my mwan3+ss solution on koolshare sooner..
muronghan wrote:
NemoAlex wrote:Hey guys
If you're looking for compiled .ipk file of mwlwifi for CC final, here is a git repository:
https://github.com/NemoAlex/mwlwifi-binHi, Nemo, thx for your commitment to the country... I will also update my mwan3+ss solution on koolshare sooner..
Amazing. You are welcomed.
@Kaloz
When you have a moment can you please save to your downloads folder the latest revision of CC final (with latest driver, fixes, etc) for 1900ac v1?
Cheers! Much appreciated!
Nihilanth wrote:
@Kaloz
When you have a moment can you please save to your downloads folder the latest revision of CC final (with latest driver, fixes, etc) for 1900ac v1?
Cheers! Much appreciated!
Where is this download folder, is it public?
There is something strange going on when I flash the latest trunk firmwares to the WRT1200AC when using Luci, flash through serial with "run flash_pri_image" or "run flash_alt_image". The kernel panics and when switching from boot_part 1 to 2 or the other way around (depending on which part was active), both FW's have been altered!
Though when using the trick to get back to the backup firmware by cycling the power three times, the previous firmware does get loaded! This is very strange, as "setenv boot_part x" should go back to the backup firmware, it seems something isn't programmed right in the latest trunk FWs.
When I flash using "run upgrade_both_images" it does work like it should.
Here is the log after the update using Luci, flash through serial with "run flash_pri_image" or "run_alt_image":
rootdelay=1 rootfstype=jffs2 earlyprintk mtdparts=armada-nand:2048K(uboot)ro,256 K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_ kernel),34m@56m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg)
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 514336K/524288K available (3699K kernel code, 145K rwdata , 968K rodata, 244K init, 173K bss, 9952K reserved, 0K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff800000 ( 496 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0496ed4 (4668 kB)
[ 0.000000] .init : 0xc0497000 - 0xc04d4000 ( 244 kB)
[ 0.000000] .data : 0xc04d4000 - 0xc04f8678 ( 146 kB)
[ 0.000000] .bss : 0xc04f8678 - 0xc0523a7c ( 174 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, s uspend/resume will not work
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 D prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[ 0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[ 0.000000] Switching to timer-based delay loop, resolution 40ns
[ 0.000003] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899 345900ns
[ 0.000011] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycl es: 0xffffffff, max_idle_ns: 76450417870 ns
[ 0.000186] Calibrating delay loop (skipped), value calculated using timer fr equency.. 50.00 BogoMIPS (lpj=250000)
[ 0.000195] pid_max: default: 32768 minimum: 301
[ 0.000251] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000256] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000499] CPU: Testing write buffer coherency: ok
[ 0.000619] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.000647] Setting up static identity map for 0x8280 - 0x82d8
[ 0.000740] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[ 0.000832] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.001374] Booting CPU 1
[ 0.001559] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.001594] Brought up 2 CPUs
[ 0.001602] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[ 0.001606] CPU: All CPU(s) started in SVC mode.
[ 0.003600] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.003694] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma x_idle_ns: 19112604462750000 ns
[ 0.003733] pinctrl core: initialized pinctrl subsystem
[ 0.004131] NET: Registered protocol family 16
[ 0.004681] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.029894] cpuidle: using governor ladder
[ 0.032748] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x : disabling
[ 0.032757] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[ 0.060357] reg-fixed-voltage xhci0-vbus: could not find pctldev for node /so c/internal-regs/pinctrl@18000/xhci0-vbus-pins, deferring probe
[ 0.060992] clocksource: Switched to clocksource armada_370_xp_clocksource
[ 0.061468] NET: Registered protocol family 2
[ 0.061775] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.061803] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.061843] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.061869] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.061884] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.061988] NET: Registered protocol family 1
[ 0.062496] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.062826] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.062835] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORIT Y) (c) 2001-2006 Red Hat, Inc.
[ 0.063327] io scheduler noop registered
[ 0.063336] io scheduler deadline registered (default)
[ 0.063799] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[ 0.064177] irq: Cannot allocate irq_descs @ IRQ43, assuming pre-allocated
[ 0.064363] irq: Cannot allocate irq_descs @ IRQ75, assuming pre-allocated
[ 0.064706] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[ 0.064716] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.064722] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[ 0.064728] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.064962] PCI: bus0: Fast back to back transfers disabled
[ 0.064969] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), rec onfiguring
[ 0.064977] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), rec onfiguring
[ 0.065239] PCI: bus1: Fast back to back transfers disabled
[ 0.065538] PCI: bus2: Fast back to back transfers disabled
[ 0.065604] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe01fffff]
[ 0.065611] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0200000-0xe03fffff]
[ 0.065620] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe00fffff 64bi t pref]
[ 0.065633] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0100000-0xe01fffff 64bi t pref]
[ 0.065643] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.065650] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe01fffff]
[ 0.065659] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0200000-0xe02fffff 64bi t pref]
[ 0.065672] pci 0000:02:00.0: BAR 2: assigned [mem 0xe0300000-0xe03fffff 64bi t pref]
[ 0.065683] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 0.065689] pci 0000:00:02.0: bridge window [mem 0xe0200000-0xe03fffff]
[ 0.065813] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.091303] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy int r )
[ 0.091404] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.131301] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy int r )
[ 0.131477] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.131814] console [ttyS0] disabled
[ 0.151888] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 21, base_baud = 12500000) is a 16550A
[ 0.835429] console [ttyS0] enabled
[ 0.839400] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this de vice
[ 0.847219] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[ 0.853610] nand: AMD/Spansion S34ML01G2
[ 0.857549] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB siz e: 64
[ 0.865159] pxa3xx-nand f10d0000.flash: ECC strength 16, ECC step size 2048
[ 0.872319] Bad block table found at page 65472, version 0x01
[ 0.878366] Bad block table found at page 65408, version 0x01
[ 0.884398] 10 ofpart partitions found on MTD device pxa3xx_nand-0
[ 0.890605] Creating 10 MTD partitions on "pxa3xx_nand-0":
[ 0.896126] 0x000000000000-0x000000200000 : "u-boot"
[ 0.901492] 0x000000200000-0x000000240000 : "u_env"
[ 0.906695] 0x000000240000-0x000000280000 : "s_env"
[ 0.911931] 0x000000900000-0x000000a00000 : "devinfo"
[ 0.917320] 0x000000a00000-0x000003200000 : "kernel1"
[ 0.922769] 0x000001000000-0x000003200000 : "rootfs1"
[ 0.928195] 0x000003200000-0x000005a00000 : "kernel2"
[ 0.933641] 0x000003800000-0x000005a00000 : "ubi"
[ 0.938711] 0x000005a00000-0x000008000000 : "syscfg"
[ 0.944076] 0x000000280000-0x000000900000 : "unused_area"
[ 0.950354] libphy: Fixed MDIO Bus: probed
[ 0.954600] libphy: orion_mdio_bus: probed
[ 0.959726] mvneta f1034000.ethernet eth0: Using random mac address 16:4d:49: f2:90:4d
[ 0.968535] mvneta f1070000.ethernet eth1: Using hardware mac address c0:56:2 7:74:8e:a3
[ 0.977256] NET: Registered protocol family 10
[ 0.982238] NET: Registered protocol family 17
[ 0.986719] bridge: automatic filtering via arp/ip/ip6tables has been depreca ted. Update your scripts to load br_netfilter if you need this.
[ 0.999410] Bridge firewalling registered
[ 1.003457] 8021q: 802.1Q VLAN Support v1.8
[ 1.007720] Registering SWP/SWPB emulation handler
[ 1.013566] UBI: auto-attach mtd7
[ 1.016724] ubi0: attaching mtd7
[ 1.041879] ubi0 error: scan_peb: bad image sequence number 945367345 in PEB 79, expected 1846208327
[ 1.051065] Erase counter header dump:
[ 1.054828] magic 0x55424923
[ 1.058591] version 1
[ 1.061575] ec 1
[ 1.064553] vid_hdr_offset 2048
[ 1.067791] data_offset 4096
[ 1.071036] image_seq 945367345
[ 1.074711] hdr_crc 0x4ea0d89c
[ 1.078473] erase counter header hexdump:
[ 1.082534] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd7, error -22
[ 1.089620] UBI error: cannot attach mtd7
[ 1.093680] mvsw61xx 10.mvsw61xx: Found MV88E6176 at f1072004.mdio-mi:10
[ 1.100594] mvsw61xx 10.mvsw61xx: Using direct addressing
[ 1.106055] hctosys: unable to open rtc device (rtc0)
[ 1.111953] xhci0-vbus: disabling
[ 1.115417] Waiting 1 sec before mounting root device...
[ 2.120995] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19VFS: Ca nnot open root device "(null)" or unknown-block(0,0): error -6
[ 2.133639] Please append a correct "root=" boot option; here are the availab le partitions:
[ 2.142035] 1f00 2048 mtdblock0 (driver?)
[ 2.147119] 1f01 256 mtdblock1 (driver?)
[ 2.152209] 1f02 256 mtdblock2 (driver?)
[ 2.157292] 1f03 1024 mtdblock3 (driver?)
[ 2.162380] 1f04 40960 mtdblock4 (driver?)
[ 2.167463] 1f05 34816 mtdblock5 (driver?)
[ 2.172551] 1f06 40960 mtdblock6 (driver?)
[ 2.177633] 1f07 34816 mtdblock7 (driver?)
[ 2.182720] 1f08 38912 mtdblock8 (driver?)
[ 2.187802] 1f09 6656 mtdblock9 (driver?)
[ 2.192890] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno wn-block(0,0)
[ 2.201188] CPU1: stopping
[ 2.203910] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.0-rc8 #1
[ 2.210115] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 2.216057] Backtrace:
[ 2.218531] [<c001d458>] (dump_backtrace) from [<c001d660>] (show_stack+0x18/ 0x1c)
[ 2.226130] r7:df455f40 r6:00000000 r5:c04e2278 r4:00000000
[ 2.231860] [<c001d648>] (show_stack) from [<c01aa988>] (dump_stack+0x88/0x98 )
[ 2.239115] [<c01aa900>] (dump_stack) from [<c001f7f4>] (handle_IPI+0x110/0x1 a8)
[ 2.246540] r5:00000001 r4:c04f88d4
[ 2.250154] [<c001f6e4>] (handle_IPI) from [<c0009554>] (gic_handle_irq+0x84/ 0x98)
[ 2.257753] r7:df455f40 r6:e080210c r5:c04d6f24 r4:c04e26cc
[ 2.263479] [<c00094d0>] (gic_handle_irq) from [<c000a654>] (__irq_svc+0x54/0 x70)
[ 2.270991] Exception stack(0xdf455f40 to 0xdf455f88)
[ 2.276065] 5f40: 00000001 00000000 00000000 c000b440 df454000 c04d6498 00000 000 00000000
[ 2.284278] 5f60: df455fb0 c0421840 c04d1150 df455f9c df455fa0 df455f90 c001a 400 c001a404
[ 2.292489] 5f80: 60000013 ffffffff
[ 2.295989] r9:c0421840 r8:df455fb0 r7:df455f74 r6:ffffffff r5:60000013 r4:c 001a404
[ 2.303822] [<c001a3c8>] (arch_cpu_idle) from [<c005cb98>] (default_idle_call +0x30/0x34)
[ 2.311950] [<c005cb68>] (default_idle_call) from [<c005cd08>] (cpu_startup_e ntry+0x16c/0x230)
[ 2.320600] [<c005cb9c>] (cpu_startup_entry) from [<c001f4a4>] (secondary_sta rt_kernel+0x150/0x158)
[ 2.329682] r7:c04f88d8
[ 2.332237] [<c001f354>] (secondary_start_kernel) from [<0000960c>] (0x960c)
[ 2.339312] r5:00000051 r4:1f43c06a
[ 2.342925] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Anyone got any idea as why this is happening?
(Last edited by johan81 on 9 Jan 2016, 14:01)
Sorry, posts 9451 to 9450 are missing from our archive.
Page 378 of 598