On Tue, Mar 01, 2005 at 09:41:29PM +0100, Kay Sievers wrote:
> On Tue, 2005-03-01 at 21:26 +0100, Marco d'Itri wrote:
> >reassign 297481 kernel-image-2.6.8-i386
> >thanks
> >
> >On Mar 01, Kay Sievers <[EMAIL PROTECTED]> wrote:
> >
> >> This kernel will not work correctly with managed events. It ha
On Tue, 2005-03-01 at 21:26 +0100, Marco d'Itri wrote:
>reassign 297481 kernel-image-2.6.8-i386
>thanks
>
>On Mar 01, Kay Sievers <[EMAIL PROTECTED]> wrote:
>
>> This kernel will not work correctly with managed events. It has holes in
>> the sequence numbers. You need at least 2.6.10 if I remember
At Tue, 1 Mar 2005 19:24:04 +0100,
Marco d'Itri wrote:
> Which version of udev are you using?
It got upgraded with everything else, so now on 0.054-1.
cheers,
Simon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassign 297481 udev
thanks
On Mar 01, Simon Guest <[EMAIL PROTECTED]> wrote:
> Is this then a bug in udev (for which I see you are also the Debian
> maintainer)? Is there anything else you need from me?
Which version of udev are you using?
--
ciao,
Marco
signature.asc
Description: Digital s
At Tue, 1 Mar 2005 18:39:34 +0100,
Marco d'Itri wrote:
>
> On Mar 01, Simon Guest <[EMAIL PROTECTED]> wrote:
> > Yes, using udev. Does this help to explain it?
> Maybe. Try to comment the line in /etc/init.d/udev which updates
> /proc/sys/kernel/hotplug and reboot.
OK, this fixed my problem.
I
On Mar 01, Simon Guest <[EMAIL PROTECTED]> wrote:
> > Are you using udev?
> Yes, using udev. Does this help to explain it?
Maybe. Try to comment the line in /etc/init.d/udev which updates
/proc/sys/kernel/hotplug and reboot.
--
ciao,
Marco
signature.asc
Description: Digital signature
At Tue, 1 Mar 2005 00:43:49 +0100,
Marco d'Itri wrote:
> I do not know what -2 means, but I see that it fails after the timeout
> so I think that the agent is not even trying to upload the firmware.
>
> What happens if you unload and then reload the module?
It does the same, i.e. fails in the sam
On Feb 28, Simon Guest <[EMAIL PROTECTED]> wrote:
> Feb 28 22:31:38 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG
> Network Connection
> Feb 28 22:31:48 localhost kernel: ipw2200: ipw-2.2-boot.fw load failed:
> Reason -2
I do not know what -2 means, but I see that it fails after
Package: hotplug
Version: 0.0.20040329-17
Severity: normal
I've been using ipw2200 successfully with the previous hotplug
version, 0.0.20040329-16. Following a dist-upgrade, my hotplug was
upgraded to 0.0.20040329-17, and after the next reboot, my ipw2200
wireless driver could no longer get its f
9 matches
Mail list logo
