Unfortunately I can't incorporate the linked project into the current Attitude Adjustment builds.  The current stable version is using kernel 3.3 and the project you linked is only tested against kernel 3.8 and 3.9.  I can look into adding it into the builds once I start work on a version of OpenWRT that uses a kernel that matches the requirements of the project you've linked.

Any idea why this is happening?

Jul 16 02:46:59 Router kern.warn kernel: [17435.252222] EXT4-fs warning (device sda2): ext4_end_bio:250: I/O error writing to inode 18910 (offset 2826240 size 123904 starting block 434153)
Jul 16 02:46:59 Router kern.err kernel: [17435.252309] sd 6:0:0:0: rejecting I/O to offline device
Jul 16 02:46:59 Router kern.err kernel: [17435.252354] Buffer I/O error on device sda2, logical block 400858
Jul 16 02:46:59 Router kern.warn kernel: [17435.252401] EXT4-fs warning (device sda2): ext4_end_bio:250: I/O error writing to inode 18910 (offset 2949120 size 1024 starting block 434154)
Jul 16 02:46:59 Router kern.err kernel: [17435.253884] sd 6:0:0:0: rejecting I/O to offline device
Jul 16 02:46:59 Router kern.err kernel: [17435.253962] sd 6:0:0:0: rejecting I/O to offline device
Jul 16 02:46:59 Router kern.err kernel: [17435.254044] sd 6:0:0:0: rejecting I/O to offline device
Jul 16 02:46:59 Router kern.err kernel: [17435.254106] sd 6:0:0:0: rejecting I/O to offline device
Jul 16 02:46:59 Router kern.err kernel: [17435.254178] sd 6:0:0:0: rejecting I/O to offline device
Jul 16 02:46:59 Router kern.err kernel: [17435.254233] sd 6:0:0:0: rejecting I/O to offline device

I thought my USB stick was failing when I saw this so I started from scratch on my spare stick.  Six hours later, the above happens.

I can only presume that something is crashing USB so its unable to access the USB stick any more giving the illusion that the USB stick is faulty.  Oh how I hate USB.

I've only seen this when a disk or controller goes bad. Have you tried another USB port or USB controller?
dmesg should have some good info on what is going on as well.

My build does include a variety of storage options beyond USB (such as sata). You might try a different storage tech if it is an option.

Yeah I tried in different USB ports and it still happened.  For now I have removed the least important USB devices to see what happens and so far its going okay.  So perhaps my first suspect was right that its the last USB ethernet adapter I added.  It does run quite hot and the first few times I plugged it in, it didn't work, so its not beyond reason to suspect its defective.

That is one big drag of using USB sticks, if any USB device starts playing up for whatever reason it seems to cause the whole subsystem to go awol.  But I really don't want to use a HDD due to the noise and heat they give off plus as I said before it makes upgrading somewhat more complicated.

Ideally I would use a small 4GB SATA SSD with two copies of OpenWRT on there, if I could easily switch between them.  Thing is small SSDs aren't particularly cheap unless you get them from China where you can't be sure you got a real or counterfeit one.

I assume there is some way I can manually hack together a working system using the individual kernel and filesystem images and use GRUB to boot between two different installations?

I wonder if the new device is drawing too much power when combined with the others.  If it causes too much power draw it could cause the USB stick to be under-powered and it would result in similar errors to what you are seeing. A powered USB hub for just the ethernet adapters (or USB drive) might solve the issue.  It would also isolate the network cards from the USB disks power wise.

You could use a sata <> sd card adapter possibly as well.  It would allow you to keep a similar setup as two usb drives.

You can setup grub to boot between two different installs on the same drive, but it would require selecting the right install at boot or remembering to update grub to boot the right filesystem when you switch between them.  Grub is a pretty flexible loader and supports advanced configurations.  If you search for "grub2 grub.cfg" and similar you'll find good examples.

I'm not sure at all what it was but it seems to have gone away even with both USB ethernet adapters plugged in.  I will just keep an eye on it and avoid plugging my phone in to top up as perhaps that was causing a problem (though no idea why, its been working fine for months).

I have an Acer AOD270 netbook, datasheet/specifications @ http://us.acer.com/ac/en/US/content/mod … .SGA0D.066
Everything works apart from the 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) . I've installed kmod-b43. admin/network/iface_add doesn't detect the wireless device and iwconfig doesn't either.
Logs show:
[   31.804677] b43: Unknown symbol bcma_core_disable (err 0)
[   31.804894] b43: Unknown symbol bcma_core_pll_ctl (err 0)
[   31.805004] b43: Unknown symbol bcma_driver_unregister (err 0)
[   31.805137] b43: Unknown symbol bcma_core_enable (err 0)
[   31.805251] b43: Unknown symbol bcma_core_is_enabled (err 0)
[   31.805373] b43: Unknown symbol bcma_chipco_gpio_control (err 0)
[   31.805515] b43: Unknown symbol __bcma_driver_register (err 0)
[   31.805630] b43: Unknown symbol bcma_core_set_clockmode (err 0)
[   31.805769] b43: Unknown symbol bcma_core_dma_translation (err 0)
[   31.805958] b43: Unknown symbol bcma_core_pci_irq_ctl (err 0)
[   31.806071] b43: Unknown symbol bcma_chipco_pll_write (err 0)

Could be this bug? https://dev.openwrt.org/ticket/13551#no1

Hope someone is able to help me get wireless going?

Ta

I've install a Intel WiFi Link 5100, it works in Ubuntu but not with OpenWrt. Any ideas to help me get wireless going? Ta

Are you wanting that for use as an Access Point or Client (connecting to wireless broadband)?

Last I checked the Intel cards didn't work in AP mode, its why I was very strict about picking Atheros as they are pretty much the only manufacturer where every chipset is readily supported.  Although I was surprised recently to find an old RealTek USB 802.11g adapter I had lying around actually worked so I could move all my old g devices off my n AP.

Anyway I believe you need kmod-iwlagn installed to get the card detected.  Then at the console of your router (or via SSH) try "iw list" and see what is under "Supported interface modes".  On my Atheros its:

The important bit is that AP is supported.

The problem with iwlagn is that the kernel config in mcrosson's build lacks CONFIG_PCI_MSI=y which is present in generic OpenWrt x86 builds.

Ironically I think that might have been to get my Intel Gigabit Ethernet card to work properly as some versions of the chipset seem to have problems with MSI and annoyingly it was the on-board chipset on my DN2800MT.

Is MSI really mandatory for iwlagn?

Yip, seems it is a PCI problem rather than a wireless card problem.

I'm next buying a RALINK RT3592BC8 for NZD 10. As I have 3 identical netbooks for different locations (all bought cheaply from auction) I can use the Intel card in one of them and enjoy the faster speeds compared to the Broadcom standard... not a big issue.

Hoping the RALINK RT3592BC8 works otherwise will wait for an Atheros to come on auction.

I used the mcrosson's build as it actually booted on my laptop, but it really would be great if PCI worked.
The generic OpenWrt x86 didn't want to boot on the laptop.

Oh this stupid bloody forum logged me out while I was typing my reply.

I'm a little confused actually as according to Wikipedia "While PCIe is software compatible with legacy interrupts it requires MSI or MSI-X."  That would imply that with MSI disabled my router shouldn't be working at all.  I wonder how its getting round this as it clearly says in the logs that the driver is falling back to legacy interrupts.

Not sure why you would be having problems getting an Atheros card though, mine were cheap direct from China on eBay.  I was a little wary of that at first but they both work perfectly.

This is correct, I purposfully disabled MSI-X stuff in the kernel.

That is correct, I disabled MSI-X in order for your Intel card to start working.

That wouldn't surprise me.

Getting a card that you know is 100% region compatible and does *exactly* what you expect it to do can be a real PITA.  Not all cards are sold under the right model, some can vary a little in the same model line but different revisions, etc.  It can be a real pain to get multiple WiFi cards working together too.

Is it all PCI devices, or just the WiFi cards?

I just noticed you have kmod-video-gspca-core in your repo but are lacking the actual gspca camera drivers.  Is there a particular reason for this? 

Compared to ATTITUDE ADJUSTMENT (12.09, r36088) you are missing:

kmod-video-gspca-conex - 3.3.8-1 - The Conexant Camera Driver (conex) kernel module.
kmod-video-gspca-etoms - 3.3.8-1 - The Etoms USB Camera Driver (etoms) kernel module.
kmod-video-gspca-finepix - 3.3.8-1 - The Fujifilm FinePix USB V4L2 driver (finepix) kernel module.
kmod-video-gspca-gl860 - 3.3.8-1 - gl860 webcam support
kmod-video-gspca-jeilinj - 3.3.8-1 - The JEILINJ USB Camera Driver (jeilinj) kernel module.
kmod-video-gspca-konica - 3.3.8-1 - The Konica USB Camera Driver (konica) kernel module.
kmod-video-gspca-m5602 - 3.3.8-1 - The ALi USB m5602 Camera Driver (m5602) kernel module.
kmod-video-gspca-mars - 3.3.8-1 - The Mars USB Camera Driver (mars) kernel module.
kmod-video-gspca-mr97310a - 3.3.8-1 - The Mars-Semi MR97310A USB Camera Driver (mr97310a) kernel module.
kmod-video-gspca-ov519 - 3.3.8-1 - The OV519 USB Camera Driver (ov519) kernel module.
kmod-video-gspca-ov534 - 3.3.8-1 - The OV534 USB Camera Driver (ov534) kernel module.
kmod-video-gspca-ov534-9 - 3.3.8-1 - The OV534-9 USB Camera Driver (ov534_9) kernel module.
kmod-video-gspca-pac207 - 3.3.8-1 - The Pixart PAC207 USB Camera Driver (pac207) kernel module.
kmod-video-gspca-pac7311 - 3.3.8-1 - The Pixart PAC7311 USB Camera Driver (pac7311) kernel module.
kmod-video-gspca-se401 - 3.3.8-1 - The SE401 USB Camera Driver kernel module.
kmod-video-gspca-sn9c20x - 3.3.8-1 - The SN9C20X USB Camera Driver (sn9c20x) kernel module.
kmod-video-gspca-sonixb - 3.3.8-1 - The SONIX Bayer USB Camera Driver (sonixb) kernel module.
kmod-video-gspca-sonixj - 3.3.8-1 - The SONIX JPEG USB Camera Driver (sonixj) kernel module.
kmod-video-gspca-spca500 - 3.3.8-1 - The SPCA500 USB Camera Driver (spca500) kernel module.
kmod-video-gspca-spca501 - 3.3.8-1 - The SPCA501 USB Camera Driver (spca501) kernel module.
kmod-video-gspca-spca505 - 3.3.8-1 - The SPCA505 USB Camera Driver (spca505) kernel module.
kmod-video-gspca-spca506 - 3.3.8-1 - The SPCA506 USB Camera Driver (spca506) kernel module.
kmod-video-gspca-spca508 - 3.3.8-1 - The SPCA508 USB Camera Driver (spca508) kernel module.
kmod-video-gspca-spca561 - 3.3.8-1 - The SPCA561 USB Camera Driver (spca561) kernel module.
kmod-video-gspca-sq905 - 3.3.8-1 - The SQ Technologies SQ905 based USB Camera Driver (sq905) kernel module.
kmod-video-gspca-sq905c - 3.3.8-1 - The SQ Technologies SQ905C based USB Camera Driver (sq905c) kernel module.
kmod-video-gspca-stk014 - 3.3.8-1 - The Syntek DV4000 (STK014) USB Camera Driver (stk014) kernel module.
kmod-video-gspca-stv06xx - 3.3.8-1 - The STV06XX USB Camera Driver (stv06xx) kernel module.
kmod-video-gspca-sunplus - 3.3.8-1 - The SUNPLUS USB Camera Driver (sunplus) kernel module.
kmod-video-gspca-t613 - 3.3.8-1 - The T613 (JPEG Compliance) USB Camera Driver (t613) kernel module.
kmod-video-gspca-tv8532 - 3.3.8-1 - The TV8532 USB Camera Driver (tv8532) kernel module.
kmod-video-gspca-vc032x - 3.3.8-1 - The VC032X USB Camera Driver (vc032x) kernel module.
kmod-video-gspca-zc3xx - 3.3.8-1 - The ZC3XX USB Camera Driver (zc3xx) kernel module.

More specifically though, I was looking for kmod-video-gspca-ov534 or perhaps kmod-video-gspca-ov534-9 as I'm not sure the difference.  I was just going to stick my Playstation Eye on the router to get a video stream of the bird feeder in the back garden.   As such, its not VITALLY important, it was just a quick free solution.

I probably missed setting the right values in defconfig and the like.  I have a note to take a closer look at this once I get some free time.  Hopefully soon, but I'm not sure when exactly.  I'm getting married mid September so I'm a bit short on free time these days.

Excuses excuses

Congratulations!

Hi, how would I go about testing this for you?

What does the output of "lspci" at the command line give?

Is there any chance of getting the PPP patches described on http://monki.org.uk/blog/2013/04/14/pat … r-bt-fttc/ to work on your build?

I'm a bit surprised they do not include this support as standard on OpenWRT seeing as its not going to hurt anything even if its rarely used.

New build is up: rf812a21d6fb7c61d7806904a707fe36282deb1ac

Includes a number of web cam drivers that were requested by @Alex

I will look into it soon ish.  It will likely be a bit as I get married in less than 2 weeks and will be "dark" for a few weeks.

Are there any kernel changes or can I effectively install the web cam drivers on the previous build?

mcrosson, can you add usbip* and kmod-usbip* packages? And busybox with modprobe support, please?

There were a few kernel changes.  I would recommend a "proper" upgrade for the web cam drivers.

I'll double check the modprobe support in busybox.  I thought that was already enabled.  I'll also look into usbip and see if it can be enabled easily. 

Right now I'm working on getting Yubikey and PAM support going in OpenWRT and once it is done I'll be publishing a new release.  No ETA's, still a bit busy at home but I'm making progress with the builds.