On Wed, 20 Feb 2008 07:57:23 +0100, Norbert Preining <[EMAIL PROTECTED]> wrote:
> > that you did, after taking care of detection and initialization.
> > Look at his dmesg in comment #44 in this:
>
> Yes, that looks very similar.
Someone reported on the bug that a firmware update exists to
On Wed, 20 Feb 2008 07:57:23 +0100, Norbert Preining [EMAIL PROTECTED] wrote:
that you did, after taking care of detection and initialization.
Look at his dmesg in comment #44 in this:
Yes, that looks very similar.
Someone reported on the bug that a firmware update exists to resolve
the
On Do, 14 Feb 2008, Pete Zaitcev wrote:
> that you did, after taking care of detection and initialization.
> Look at his dmesg in comment #44 in this:
Yes, that looks very similar.
> > - changing the penultimage argument in the usb_stor_huawei_e220_init
> > function from 0x1 to 0 stopped this
On Do, 14 Feb 2008, Pete Zaitcev wrote:
that you did, after taking care of detection and initialization.
Look at his dmesg in comment #44 in this:
Yes, that looks very similar.
- changing the penultimage argument in the usb_stor_huawei_e220_init
function from 0x1 to 0 stopped this
> Ok, did new tests with 2.6.24-rc2:
> - with plain kernel the usb-storage modules attaches and detaches
> permanently a virtual cd drive, I stopped after 30+ iterations.
afais this is caused by hal.
when i stop hal this bouncy behaviour stops.
also it doesn't happen if you put your huawei on
Ok, did new tests with 2.6.24-rc2:
- with plain kernel the usb-storage modules attaches and detaches
permanently a virtual cd drive, I stopped after 30+ iterations.
afais this is caused by hal.
when i stop hal this bouncy behaviour stops.
also it doesn't happen if you put your huawei on
On Fri, 16 Nov 2007 14:22:56 +0100, Norbert Preining <[EMAIL PROTECTED]> wrote:
> > > The difference with huaweiAktBbo.c seems that kernel uses a nonzero
> > > length.
> > > Can you try zero length with the kernel? It's the second argument to the
> > > last.
> >
> > I tried with the git patch
On Fri, 16 Nov 2007 14:22:56 +0100, Norbert Preining [EMAIL PROTECTED] wrote:
The difference with huaweiAktBbo.c seems that kernel uses a nonzero
length.
Can you try zero length with the kernel? It's the second argument to the
last.
I tried with the git patch plus changing the
Dear Pete, dear all,
On Mi, 31 Okt 2007, preining wrote:
> On Di, 30 Okt 2007, Pete Zaitcev wrote:
> > The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
> > Can you try zero length with the kernel? It's the second argument to the
> > last.
>
> I tried with the git
Dear Pete, dear all,
On Mi, 31 Okt 2007, preining wrote:
On Di, 30 Okt 2007, Pete Zaitcev wrote:
The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
Can you try zero length with the kernel? It's the second argument to the
last.
I tried with the git patch plus
On Di, 30 Okt 2007, Pete Zaitcev wrote:
> > printk(KERN_ERR "ENTERING usb_stor_huawei_e220_init!\n");
> > at the beginning of the function but it never showed up in my log files.
> > So it seems that the UNUSUAL_DEV entry does not match.
>
> This doesn't seem to be possible, considering the
On Di, 30 Okt 2007, Pete Zaitcev wrote:
printk(KERN_ERR ENTERING usb_stor_huawei_e220_init!\n);
at the beginning of the function but it never showed up in my log files.
So it seems that the UNUSUAL_DEV entry does not match.
This doesn't seem to be possible, considering the
On Di, 30 Okt 2007, Pete Zaitcev wrote:
> This doesn't seem to be possible, considering the /proc/bus/usb/devices
> that you posted. I would rather suspect that you forgot to perform
> some step in your kernel installation, and end using a stale
> usb-storage module.
No.
$ uname -r
2.6.23
$ cd
On Wed, 31 Oct 2007 07:23:56 +0100, Norbert Preining <[EMAIL PROTECTED]> wrote:
> Hmm, in addition I added a
> printk(KERN_ERR "ENTERING usb_stor_huawei_e220_init!\n");
> at the beginning of the function but it never showed up in my log files.
> So it seems that the UNUSUAL_DEV entry does
On Mi, 31 Okt 2007, preining wrote:
> On Di, 30 Okt 2007, Pete Zaitcev wrote:
> > The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
> > Can you try zero length with the kernel? It's the second argument to the
> > last.
>
> I tried with the git patch plus changing the
On Di, 30 Okt 2007, Pete Zaitcev wrote:
> The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
> Can you try zero length with the kernel? It's the second argument to the last.
I tried with the git patch plus changing the penultimage argument from
0x1 to 0.
The switch of
On Tue, 30 Oct 2007 22:22:13 +0100, Norbert Preining <[EMAIL PROTECTED]> wrote:
> I tried the attached patch which I found on the usb list, but it didn't
> work, the cdrom was still always found, and it was
> connected/disconnected permanently.
The difference with huaweiAktBbo.c seems that
On Di, 30 Okt 2007, Pete Zaitcev wrote:
> Please post your /proc/bus/usb/devices. Maybe it just fails to match.
Here is the relevant part:
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 25 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1003
On Tue, 30 Oct 2007 20:09:45 +0100, Norbert Preining <[EMAIL PROTECTED]> wrote:
> Is this a regression from 2.6.20, or is it supposed to work?
Please post your /proc/bus/usb/devices. Maybe it just fails to match.
-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Di, 30 Okt 2007, Chuck Ebbert wrote:
> Did you see commit d853d872c14b9adc4adad29e56cd378b291f86e0 ?
2.6.23 + this commit exhibits the same problems I describe before ...
permanent disconnect/connect problems. Not even using the mentioned
program does switch the usb modem into the right mode.
On Tue, 30 Oct 2007 21:47:20 +0100
Norbert Preining <[EMAIL PROTECTED]> wrote:
> Hi Kristoffer,
>
> thanks for the feedback.
>
> On Di, 30 Okt 2007, Kristoffer Ericson wrote:
> > Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla
> > kernel. It has worked fine for me since
On Di, 30 Okt 2007, Chuck Ebbert wrote:
> Did you see commit d853d872c14b9adc4adad29e56cd378b291f86e0 ?
No, where can I see that one?
I tried the attached patch which I found on the usb list, but it didn't
work, the cdrom was still always found, and it was
connected/disconnected permanently.
On 10/30/2007 04:47 PM, Norbert Preining wrote:
> Hi Kristoffer,
>
> thanks for the feedback.
>
> On Di, 30 Okt 2007, Kristoffer Ericson wrote:
>> Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla kernel.
>> It has worked fine for me since 2.6.21.
>
> Strange. I rebuilt the
Hi Kristoffer,
thanks for the feedback.
On Di, 30 Okt 2007, Kristoffer Ericson wrote:
> Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla kernel.
> It has worked fine for me since 2.6.21.
Strange. I rebuilt the kernel, compiled the usb serial and options into
the kernel,
Greetings,
Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla kernel. It
has worked fine for me since 2.6.21.
The lights give you a hint what mode its in. Green = usb_storage, Dark-blue =
MODEM_slow, bright-blue = MODEM_fast (3G).
If the light is green after reboot, I need to
Dear all,
I recently got an Huawei E220 usb modem. Reading a bit on the net I
found that:
The Huaweii E220 modem is a composite USB device: in fact it acts like a
mass storage device, and also as three serial communication ports. The
Linux's developers dealt with this ignoring the mass
Dear all,
I recently got an Huawei E220 usb modem. Reading a bit on the net I
found that:
The Huaweii E220 modem is a composite USB device: in fact it acts like a
mass storage device, and also as three serial communication ports. The
Linux's developers dealt with this ignoring the mass
Greetings,
Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla kernel. It
has worked fine for me since 2.6.21.
The lights give you a hint what mode its in. Green = usb_storage, Dark-blue =
MODEM_slow, bright-blue = MODEM_fast (3G).
If the light is green after reboot, I need to
Hi Kristoffer,
thanks for the feedback.
On Di, 30 Okt 2007, Kristoffer Ericson wrote:
Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla kernel.
It has worked fine for me since 2.6.21.
Strange. I rebuilt the kernel, compiled the usb serial and options into
the kernel, while
On 10/30/2007 04:47 PM, Norbert Preining wrote:
Hi Kristoffer,
thanks for the feedback.
On Di, 30 Okt 2007, Kristoffer Ericson wrote:
Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla kernel.
It has worked fine for me since 2.6.21.
Strange. I rebuilt the kernel,
On Di, 30 Okt 2007, Chuck Ebbert wrote:
Did you see commit d853d872c14b9adc4adad29e56cd378b291f86e0 ?
No, where can I see that one?
I tried the attached patch which I found on the usb list, but it didn't
work, the cdrom was still always found, and it was
connected/disconnected permanently.
On Tue, 30 Oct 2007 21:47:20 +0100
Norbert Preining [EMAIL PROTECTED] wrote:
Hi Kristoffer,
thanks for the feedback.
On Di, 30 Okt 2007, Kristoffer Ericson wrote:
Im using a Huawei E220 USB modem, currently running 2.6.22.5 vanilla
kernel. It has worked fine for me since 2.6.21.
On Di, 30 Okt 2007, Chuck Ebbert wrote:
Did you see commit d853d872c14b9adc4adad29e56cd378b291f86e0 ?
2.6.23 + this commit exhibits the same problems I describe before ...
permanent disconnect/connect problems. Not even using the mentioned
program does switch the usb modem into the right mode.
On Tue, 30 Oct 2007 20:09:45 +0100, Norbert Preining [EMAIL PROTECTED] wrote:
Is this a regression from 2.6.20, or is it supposed to work?
Please post your /proc/bus/usb/devices. Maybe it just fails to match.
-- Pete
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
On Di, 30 Okt 2007, Pete Zaitcev wrote:
Please post your /proc/bus/usb/devices. Maybe it just fails to match.
Here is the relevant part:
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 25 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1003 Rev=
On Tue, 30 Oct 2007 22:22:13 +0100, Norbert Preining [EMAIL PROTECTED] wrote:
I tried the attached patch which I found on the usb list, but it didn't
work, the cdrom was still always found, and it was
connected/disconnected permanently.
The difference with huaweiAktBbo.c seems that kernel
On Di, 30 Okt 2007, Pete Zaitcev wrote:
The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
Can you try zero length with the kernel? It's the second argument to the last.
I tried with the git patch plus changing the penultimage argument from
0x1 to 0.
The switch of the
On Mi, 31 Okt 2007, preining wrote:
On Di, 30 Okt 2007, Pete Zaitcev wrote:
The difference with huaweiAktBbo.c seems that kernel uses a nonzero length.
Can you try zero length with the kernel? It's the second argument to the
last.
I tried with the git patch plus changing the penultimage
On Wed, 31 Oct 2007 07:23:56 +0100, Norbert Preining [EMAIL PROTECTED] wrote:
Hmm, in addition I added a
printk(KERN_ERR ENTERING usb_stor_huawei_e220_init!\n);
at the beginning of the function but it never showed up in my log files.
So it seems that the UNUSUAL_DEV entry does not
On Di, 30 Okt 2007, Pete Zaitcev wrote:
This doesn't seem to be possible, considering the /proc/bus/usb/devices
that you posted. I would rather suspect that you forgot to perform
some step in your kernel installation, and end using a stale
usb-storage module.
No.
$ uname -r
2.6.23
$ cd
40 matches
Mail list logo
