On Tue, 2009-02-03 at 22:01 -0500, Stefan Monnier wrote:
>
> Then I don't know what's going on.
Indeed, it is of question isn't it?
> Only one of them is active at any particular time: the first gets killed
> before the seconed is started.
But where, and why is this not happening with a usb-roo
>> ln -sf /rom/etc/init./boot /etc/init.d/boot
> Hrm. But in my case, those files are effectively the same (where
> hotplug counts). See:
> # diff -u /rom/etc/init.d/boot /etc/init.d/boot
> --- /rom/etc/init.d/boot Mon Jun 16 23:08:04 2008
> +++ /etc/init.d/boot Fri Jul 11 00:16:00 2008
>
On Tue, 2009-02-03 at 09:39 -0500, Stefan Monnier wrote:
>
> ln -sf /rom/etc/init./boot /etc/init.d/boot
Hrm. But in my case, those files are effectively the same (where
hotplug counts). See:
# diff -u /rom/etc/init.d/boot /etc/init.d/boot
--- /rom/etc/init.d/bootMon Jun 16 23:08:04
>> I updated my USB (really IDE in my case) rootfs.
> Ahhh. Care to post the patch?
As I said, the "patch" was
ln -sf /rom/etc/init./boot /etc/init.d/boot
>> More specifically, the
>> /etc/init.d/boot script
> The one on the flash, that calls /sbin/mount_root?
The flash is uptodate, the USB
On Mon, 2009-02-02 at 22:01 -0500, Stefan Monnier wrote:
>
> I updated my USB (really IDE in my case) rootfs.
Ahhh. Care to post the patch?
> More specifically, the
> /etc/init.d/boot script
The one on the flash, that calls /sbin/mount_root?
> needs to "killall -q hotplug2" before starting
>
>> A "recent" change to the way hotplug2 is started&killed around
>> pivot_root made me bump into the exact above scenario.
> How did you solve it?
I updated my USB (really IDE in my case) rootfs. More specifically, the
/etc/init.d/boot script needs to "killall -q hotplug2" before starting
hotplu
On Sun, 2009-02-01 at 21:52 -0500, Stefan Monnier wrote:
>
> Here's another guess:
>
> Your USB rootfs is not quite in sync for your firmware rootfs.
Most definitely true.
> So the
> firmware rootfs starts udev (aka hotplug2) and doesn't kill it before
> doing pivot_root, and your USB r
>> > I've just posted some more details to ticket #3152 which is currently
>> > closed. Could somebody with permission to do so, please reopen it?
>> >
>> > Basically, I'm getting:
>> >
>> > b43-phy2: Broadcom 4318 WLAN found
>> > phy2: Selected rate control algorithm 'pid'
>> > Broadcom 43xx dr
On Sun, 2009-02-01 at 16:53 +0100, Hauke Mehrtens wrote:
> Brian J. Murrell wrote:
> > I've just posted some more details to ticket #3152 which is currently
> > closed. Could somebody with permission to do so, please reopen it?
> >
> > Basically, I'm getting:
> >
> > b43-phy2: Broadcom 4318 WLAN
On Sun, 2009-02-01 at 16:47 +0100, Michael Buesch wrote:
> On Sunday 01 February 2009 16:24:49 Brian J. Murrell wrote:
> >
> > b43-phy2: Broadcom 4318 WLAN found
> > phy2: Selected rate control algorithm 'pid'
> > Broadcom 43xx driver loaded [ Features: NLR, Firmware-ID: FW13 ]
> > input: b43-phy2
Brian J. Murrell wrote:
> I've just posted some more details to ticket #3152 which is currently
> closed. Could somebody with permission to do so, please reopen it?
>
> Basically, I'm getting:
>
> b43-phy2: Broadcom 4318 WLAN found
> phy2: Selected rate control algorithm 'pid'
> Broadcom 43xx dr
On Sunday 01 February 2009 16:24:49 Brian J. Murrell wrote:
> I've just posted some more details to ticket #3152 which is currently
> closed. Could somebody with permission to do so, please reopen it?
>
> Basically, I'm getting:
>
> b43-phy2: Broadcom 4318 WLAN found
> phy2: Selected rate contro
I've just posted some more details to ticket #3152 which is currently
closed. Could somebody with permission to do so, please reopen it?
Basically, I'm getting:
b43-phy2: Broadcom 4318 WLAN found
phy2: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: NLR, Firmware-ID
13 matches
Mail list logo
