Modify

Opened 5 years ago

Closed 5 years ago

#12905 closed defect (worksforme)

OpenWRT fails to boot when CONFIG_EXT4_FS is selected in kernel on brcm47xx

Reported by: shinton@… Owned by: developers
Priority: high Milestone: Chaos Calmer 15.05
Component: kernel Version: Trunk
Keywords: asus rt-n16 brm47xx brcm4716 ext4 Cc: hauke

Description

Device: ASUS RT-N16
Target: Broadcom bcm947xx
Profile: Broadcom SoC, All Ethernet, bcm43xx wifi (wl, proprietary)

System fails to boot when ext4 is selected in make openwrt/kernel_menuconfig. Hangs at "starting program at 0x80001000".

Attachments (0)

Change History (7)

comment:1 Changed 5 years ago by hauke

Did you selected ext4 as root file system (under "Target Images") or only as a kernel module?

comment:2 Changed 5 years ago by anonymous

Ext4 was selected in the kernel itself by running make openwrt/kernel_menuconfig under Filesystems and not as a module. The idea is that the filesystem support is baked into the kernel itself and does not require a module. It has previously worked up until this point.

comment:3 Changed 5 years ago by hauke

  • Resolution set to invalid
  • Status changed from new to closed

This is an unsupported change and you probably changed something else.

comment:4 Changed 5 years ago by anonymous

It used to work just find under George's patchset.

comment:5 Changed 5 years ago by anonymous

  • Resolution invalid deleted
  • Status changed from closed to reopened

To the devs: Why not try it for yourself before dismissing this? Quite simply run make menuconfig and select the device and target that I selected and then run make kernel_menuconfig and select ext4 under filesystems. There is a bug in the openwrt software causing this error.

comment:6 Changed 5 years ago by nlh

In "George's" patchset, all of the correct kernel config options were likely baked into "target/linux/brcm4716/config-3.x". When you run "make kernel_menuconfig", and look closely at what it is doing, it overwrites your existing .config with the combination of "target/linux/generic/config-3.x" and "target/linux/brcm47xx/config-3.x". Any thing added by the profile selection would probably be missing, and you would need to add that all in manually I expect. Seems like it should have still booted, but the ethernet driver would likely be missing, and possibly more.

Why not just add the module the expected way via "make menuconfig", go to "Kernel modules"->"Filesystems", and select "kmod-fs-ext4"? Granted it is still built as a module, but it is built into the image (if you select it properly) and is loaded automatically at boot. This works for me.

comment:7 Changed 5 years ago by hauke

  • Resolution set to worksforme
  • Status changed from reopened to closed

This works for me and non of new the config options selected by CONFIG_EXT4_FS seam to have an influence on the boot process, you probably broke your image someway different.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.