--- On Sun, 4/1/12, sf...@users.sourceforge.net <sf...@users.sourceforge.net> wrote:
> From: sf...@users.sourceforge.net <sf...@users.sourceforge.net> > Subject: Re: 3.3 kernel issue (?) > To: "Yioryos Asprobounitis" <mavrot...@yahoo.com> > Cc: aufs-users@lists.sourceforge.net > Date: Sunday, April 1, 2012, 10:45 AM > > Yioryos Asprobounitis: > > Thank you for your prompt response. > > The data you requested (and I have) is attached. > > Ok, and how did you specify the path > "/lib/firmware/usb8633.bin"? > According to > olpc-2.6/drivers/net/wireless/libertas/if_usb.c, the > driver searches > - "libertas/usb8388_olpc.bin" > - "libertas/usb8388_v9.bin" > - "libertas/usb8388_v5.bin" > - "libertas/usb8388.bin" > - "usb8388.bin" > - "libertas/usb8682.bin" > by default, and doesn't know about usb8633.bin. Correct, but usb8388.bin and the firmware for the XO-1.5 wifi (sd8686) are the _only_ files in /lib/firmware in these builds. Also would be hard to understand why copying this file to the middle layer make it now "discoverable" and "selectable". > But the behaviour may be changed if you correctly specify > the firmware > path. I don't know how to do it though. > > > > > Also I'd suggest you to check the whiteouts (or > diropq) on > > > the upper branch. > > > > could not see anything strange. Should I be looking for > something specific? > > If there exists a whiteout (whose name begins with ".wh."), > the it may > hide the lower files. You should check it on > /initrd/pup_rw. > For example, > # find /initrd/pup_rw -name '.wh.*' Yes, I did that when I said "nothing strange". Also I have the same inability to find the firmware, even at first boot with only the lower ro and the upper rw branches, so whiteouts should not be the issue, I think. > > > J. R. Okajima > ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
