[linux-usb-devel] Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Oliver Neukum wrote: > > I meant I didn't know the name to number translation. > > Sorry, ENOENT. Ok. > > For the next tests, I think it would be best to remove the 3 printks I added > > to show beginning, u->status, and ending. Spews too much stuff =) > > Please do so and try removing and reattaching the cable. I removed the printks that were spewing lines that are now no longer useful. I left the ones that are in the block for the if statement. There is no change when I unplug and replug the ethernet cable. The link light on the device does go off. Is it possible that the hardware cannot report link state? -- Lab tests show that use of micro$oft causes cancer in lab animals --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Oliver Neukum wrote:
> Very well.
>
> > Results (after ifconfig up, ethernet cable was plugged in at the time):
> > Jun 14 20:50:25 gonzales kernel: [80756.691742] kaweth: begin callback
> > Jun 14 20:50:25 gonzales kernel: [80756.691754] kaweth: u->status: 0
> > Jun 14 20:50:25 gonzales kernel: [80756.691759] kaweth: Link state change.
> > kaweth->linkstate: 0 act_state: 2
> > Jun 14 20:50:25 gonzales kernel: [80756.691764] kaweth: netif_carrier_off
>
> OK, that should not happen.
>
> Could you remove the "!" at 'if (!act_state) {' and retest?
> The documentation I got says that it should be there, but who knows
> how accurate it is for all devices.
Ok, I removed the ! and it now says "netif_carrier_on" and still blasting
the messages. I'm unable to ping the other end when configured.
> > Jun 14 20:50:25 gonzales kernel: [80756.691769] kaweth: new link state: 2
> > Jun 14 20:50:25 gonzales kernel: [80756.691776] kaweth: end callback
> >
> > the next thing was:
> > Jun 14 20:50:25 gonzales kernel: [80756.819793] kaweth: begin callback
> > Jun 14 20:50:25 gonzales kernel: [80756.819800] kaweth: u->status: 0
> > Jun 14 20:50:25 gonzales kernel: [80756.819807] kaweth: end callback
> > many times, last occurence:
> > Jun 14 20:50:36 gonzales kernel: [80767.576134] kaweth: begin callback
> > Jun 14 20:50:36 gonzales kernel: [80767.576143] kaweth: u->status: 0
> > Jun 14 20:50:36 gonzales kernel: [80767.576157] kaweth: end callback
> >
> > then I ifconfig down since it was spewing that information:
> > Jun 14 20:50:36 gonzales kernel: [80767.618157] kaweth: begin callback
> > Jun 14 20:50:36 gonzales kernel: [80767.618172] kaweth: u->status: -2
> >
> > I assume it didn't print the end since the status was -2 (not sure what -2
> > is)
>
> Killing the URB due to ifconfig.
I meant I didn't know the name to number translation.
For the next tests, I think it would be best to remove the 3 printks I added
to show beginning, u->status, and ending. Spews too much stuff =)
--
Lab tests show that use of micro$oft causes cancer in lab animals
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Here's my modified int_callback:
static void int_callback(struct urb *u, struct pt_regs *regs)
{
struct kaweth_device *kaweth = u->context;
int act_state;
printk(KERN_INFO "kaweth: begin callback\n");
printk(KERN_INFO "kaweth: u->status: %d\n", u->status);
switch (u->status) {
case 0: /* success */
break;
case -ECONNRESET: /* unlink */
case -ENOENT:
case -ESHUTDOWN:
return;
/* -EPIPE: should clear the halt */
default:/* error */
goto resubmit;
}
/* we check the link state to report changes */
if (kaweth->linkstate != (act_state = ( kaweth->intbuffer[STATE_OFFSET]
printk(KERN_INFO "kaweth: Link state change. kaweth->linkstate: %d act_state:
kaweth->linkstate, act_state);
if (!act_state) {
printk(KERN_INFO "kaweth: netif_carrier_on\n");
netif_carrier_on(kaweth->net);
} else {
printk(KERN_INFO "kaweth: netif_carrier_off\n");
netif_carrier_off(kaweth->net);
}
kaweth->linkstate = act_state;
printk(KERN_INFO "kaweth: new link state: %d\n", act_state);
}
resubmit:
kaweth_resubmit_int_urb(kaweth, GFP_ATOMIC);
printk(KERN_INFO "kaweth: end callback\n");
}
Results (after ifconfig up, ethernet cable was plugged in at the time):
Jun 14 20:50:25 gonzales kernel: [80756.691742] kaweth: begin callback
Jun 14 20:50:25 gonzales kernel: [80756.691754] kaweth: u->status: 0
Jun 14 20:50:25 gonzales kernel: [80756.691759] kaweth: Link state change.
kaweth->linkstate: 0 act_state: 2
Jun 14 20:50:25 gonzales kernel: [80756.691764] kaweth: netif_carrier_off
Jun 14 20:50:25 gonzales kernel: [80756.691769] kaweth: new link state: 2
Jun 14 20:50:25 gonzales kernel: [80756.691776] kaweth: end callback
the next thing was:
Jun 14 20:50:25 gonzales kernel: [80756.819793] kaweth: begin callback
Jun 14 20:50:25 gonzales kernel: [80756.819800] kaweth: u->status: 0
Jun 14 20:50:25 gonzales kernel: [80756.819807] kaweth: end callback
many times, last occurence:
Jun 14 20:50:36 gonzales kernel: [80767.576134] kaweth: begin callback
Jun 14 20:50:36 gonzales kernel: [80767.576143] kaweth: u->status: 0
Jun 14 20:50:36 gonzales kernel: [80767.576157] kaweth: end callback
then I ifconfig down since it was spewing that information:
Jun 14 20:50:36 gonzales kernel: [80767.618157] kaweth: begin callback
Jun 14 20:50:36 gonzales kernel: [80767.618172] kaweth: u->status: -2
I assume it didn't print the end since the status was -2 (not sure what -2 is)
I'm working off a different ethernet card to stay on line while I debug.
--
Lab tests show that use of micro$oft causes cancer in lab animals
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Strange MAC address using ASIX USB to ethernet
David Hollis wrote: > On Sat, 2005-06-11 at 23:34 -0400, Wakko Warner wrote: > > eth1 Link encap:Ethernet HWaddr 00:80:C8:FF:FF:FF > > > > According to the oui table, that's a D-Link. It's definatly not D-Link > > (unless ASIX is part of D-Link, but I kinda doubt it) > > > > If you want to know, I ran this on 2.6.12-rc2 and rc6 > > Try a 'ethtool -e ' and see what shows up in the dump. The > MAC address is stored at offset 0x08 thru 0x0d. If the value you are > getting is the same, then that is what is stored in the eeprom and that > just gets passed thru the stack. 0x 15 00 ec 01 20 12 29 27 00 80 c8 ff ff ff 09 04 Hmm, I guess so. I still just find it odd that I happen to get one with a mac ending in FF:FF:FF =) -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Oliver Neukum wrote: > Am Sonntag, 12. Juni 2005 02:41 schrieb Wakko Warner: > > After doing some testing, I believe a patch that went into rc4 broke kaweth. > > The kaweth driver itself did not change from rc2 through rc6. > > > > As a test, I reverted a patch that went into rc4 which modified > > net/core/link_watch.c. Once I compiled the kernel, my netgear EA101 works > > again. > > > > The above is not cut'n'paste. There was 1 other addition (an include) that > > I removed from the patch inorder to revert it. The patch above was applied > > to 2.6.12-rc6 using -Rp1. This is why I believe that kaweth is broken. > > With my limited understanding of the kernel, it would appear that kaweth > > doesn't support netif_carrier_ok properly. > > Anyway, I found what caused it to break, but at this point, I do not have > > the required knowledge to do a proper fix. > > static void int_callback(struct urb *u, struct pt_regs *regs) > is supposed to handle the link state. Maybe it fails in your case. Could you > add a printk to this callback to check linkstate? I don't believe my case is very specific. I've tested this on 4 different systems with totally different configs. If it is at all specific, I believe it would be with the network adapter itself. I don't have any other usb adapters that use kaweth. Can you tell me where I need to add the printks? -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Strange MAC address using ASIX USB to ethernet
I bought an Intellinet (500913) USB2.0 to Ethernet. I tested it before I bought it. It's currently working, but the MAC address bugs me. (And the fact it doesn't handle 10baseT-HD very well) eth1 Link encap:Ethernet HWaddr 00:80:C8:FF:FF:FF According to the oui table, that's a D-Link. It's definatly not D-Link (unless ASIX is part of D-Link, but I kinda doubt it) If you want to know, I ran this on 2.6.12-rc2 and rc6 -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Wakko Warner wrote:
> After doing some testing, I believe a patch that went into rc4 broke kaweth.
> The kaweth driver itself did not change from rc2 through rc6.
>
> As a test, I reverted a patch that went into rc4 which modified
> net/core/link_watch.c. Once I compiled the kernel, my netgear EA101 works
> again.
>
> The following is the patch that caused it to stop working:
> --- BEGIN PATCH ---
> diff -urN linux-2.6.12-rc3/net/core/link_watch.c
> linux-2.6.12-rc4/net/core/link_watch.c
> --- linux-2.6.12-rc3/net/core/link_watch.c2005-03-01 23:37:30.0
> -0800
> +++ linux-2.6.12-rc4/net/core/link_watch.c2005-05-06 22:59:27.439802792
> -0700
> @@ -74,6 +75,12 @@
> clear_bit(__LINK_STATE_LINKWATCH_PENDING, &dev->state);
>
> if (dev->flags & IFF_UP) {
> + if (netif_carrier_ok(dev)) {
> + WARN_ON(dev->qdisc_sleeping == &noop_qdisc);
> + dev_activate(dev);
> + } else
> + dev_deactivate(dev);
> +
> netdev_state_change(dev);
> }
>
> --- END PATCH ---
> The above is not cut'n'paste. There was 1 other addition (an include) that
> I removed from the patch inorder to revert it. The patch above was applied
> to 2.6.12-rc6 using -Rp1. This is why I believe that kaweth is broken.
> With my limited understanding of the kernel, it would appear that kaweth
> doesn't support netif_carrier_ok properly.
> Anyway, I found what caused it to break, but at this point, I do not have
> the required knowledge to do a proper fix.
Actually, removing the above broke my e1000 card. So I added
dev_activate(dev) back in and all works now!
--
Lab tests show that use of micro$oft causes cancer in lab animals
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Problem found: kaweth fails to work on 2.6.12-rc[456]
After doing some testing, I believe a patch that went into rc4 broke kaweth.
The kaweth driver itself did not change from rc2 through rc6.
As a test, I reverted a patch that went into rc4 which modified
net/core/link_watch.c. Once I compiled the kernel, my netgear EA101 works
again.
The following is the patch that caused it to stop working:
--- BEGIN PATCH ---
diff -urN linux-2.6.12-rc3/net/core/link_watch.c
linux-2.6.12-rc4/net/core/link_watch.c
--- linux-2.6.12-rc3/net/core/link_watch.c 2005-03-01 23:37:30.0
-0800
+++ linux-2.6.12-rc4/net/core/link_watch.c 2005-05-06 22:59:27.439802792
-0700
@@ -74,6 +75,12 @@
clear_bit(__LINK_STATE_LINKWATCH_PENDING, &dev->state);
if (dev->flags & IFF_UP) {
+ if (netif_carrier_ok(dev)) {
+ WARN_ON(dev->qdisc_sleeping == &noop_qdisc);
+ dev_activate(dev);
+ } else
+ dev_deactivate(dev);
+
netdev_state_change(dev);
}
--- END PATCH ---
The above is not cut'n'paste. There was 1 other addition (an include) that
I removed from the patch inorder to revert it. The patch above was applied
to 2.6.12-rc6 using -Rp1. This is why I believe that kaweth is broken.
With my limited understanding of the kernel, it would appear that kaweth
doesn't support netif_carrier_ok properly.
Anyway, I found what caused it to break, but at this point, I do not have
the required knowledge to do a proper fix.
--
Lab tests show that use of micro$oft causes cancer in lab animals
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: kaweth fails to work on 2.6.12-rc[56]
Oliver Neukum wrote: > Am Samstag, 11. Juni 2005 06:11 schrieb Wakko Warner: > > Oliver Neukum wrote: > > > Sorry, I should be more specific. It will print out the error codes > > > internal to the USB layer which are meaningful even if interrupts are > > > shared. > > > Also, are you seeing tx errors in the error count? > > > > Unless I did something wrong, it's apparently not in the USB subsystem. > > > > I have 2.6.12-rc3 and rc4 compiled. Same config file on a test system. > > again, rc3 works, rc4 does not. I booted rc3 and force loaded the usb > > modules from rc4 into rc3. It tainted the kernel, but it worked. > > > > I booted into rc4. I do have ACPI compiled so I added acpi=off. This did > > not work, same problem as before. I left a ping running, the usb controller > > was on IRQ 9. The test system is an old NEC notebook with an Intel chipset > > (thus uhci-hcd usb1.1). I plugged in a Belkin USB2.0 cardbus card (USB1.1 > > is serviced by ohci-hcd) and plugged the ethernet adapter into that. Same > > problem. > > Do you see tx errors? No. Oh oops I forgot to say the ping caused the interrupts to increase. ifconfig showed 1 packet sent but never went up. -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: kaweth fails to work on 2.6.12-rc[56]
Oliver Neukum wrote: > Am Mittwoch, 8. Juni 2005 12:42 schrieb Wakko Warner: > > > have you tried recompiling with debug enabled? > > > It does show the status codes in the interrupt handler. > > > > I have not. ?My keyboard and mouse (on a hub) are plugged in beside the > > kaweth device so they would be on the same interrupt. > > Sorry, I should be more specific. It will print out the error codes > internal to the USB layer which are meaningful even if interrupts are shared. > Also, are you seeing tx errors in the error count? Unless I did something wrong, it's apparently not in the USB subsystem. I have 2.6.12-rc3 and rc4 compiled. Same config file on a test system. again, rc3 works, rc4 does not. I booted rc3 and force loaded the usb modules from rc4 into rc3. It tainted the kernel, but it worked. I booted into rc4. I do have ACPI compiled so I added acpi=off. This did not work, same problem as before. I left a ping running, the usb controller was on IRQ 9. The test system is an old NEC notebook with an Intel chipset (thus uhci-hcd usb1.1). I plugged in a Belkin USB2.0 cardbus card (USB1.1 is serviced by ohci-hcd) and plugged the ethernet adapter into that. Same problem. As far as controllers, ALL except 1 (The cardbus USB2.0) has been some version of Intel. I have tested this on 4 different systems with the same results. An MSI 6163 board, a Supermicro X5DA8 board, a Dell Inspiron 8100, and the NEC Versa FX. The Supermicro is running SMP, but I doubt that matters. At this time, it's late. I'll see about reverting files from rc4 back to rc3 to see which one causes it to work again. -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Re: kaweth fails to work on 2.6.12-rc[56]
David Brownell wrote: > On Tuesday 07 June 2005 11:59 pm, Oliver Neukum wrote: > > Am Mittwoch, 8. Juni 2005 05:11 schrieb Wakko Warner: > > > Wakko Warner wrote: > > > > Seems that it is unable to send packets however I can see packets > > > > coming in. > > > > I downgraded to 2.6.12-rc2 which works. > > Don't forget to report which host controller(s) it fails with, > and which it works with ... See the last message I sent. The host controller did not change, only the kernel version. The .config really didn't change except for the new stuff between rc2 and newer. -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: kaweth fails to work on 2.6.12-rc[56]
Oliver Neukum wrote: > Am Mittwoch, 8. Juni 2005 05:11 schrieb Wakko Warner: > > Wakko Warner wrote: > > > Seems that it is unable to send packets however I can see packets coming > > > in. > > > I downgraded to 2.6.12-rc2 which works. > > > > > > I have not tested rc3 or rc4 yet. ?I am preparing to try rc4. > > > > Just finished testing. > > rc2 works > > rc3 works (fails on aic7xxx with my scsi hardware but rc5 works with my > > scsi hardware) > > rc4 through rc6 do not work. > > Hi, > > have you tried recompiling with debug enabled? > It does show the status codes in the interrupt handler. I have not. My keyboard and mouse (on a hub) are plugged in beside the kaweth device so they would be on the same interrupt. I did notice that the kaweth file itself hasn't changed, but something is different between rc3 and rc4. Someone else asked what host controllers. I tried it on 2 systems. The device itself is USB1. One machine running rc5 used Intel 440bx chipset. I'm not sure what controller it has but I was using the onboard USB which uses uhci. I don't have that machine anymore, it was temporary. I'm currently using this on an Intel E7505 chipset which uses both ehci and uhci (loaded in that order) I used the same configfile from rc2 when I compiled rc3 and rc4 (doing make old config of course). I'll see about testing this later on. I don't have time this morning to look at this. -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Netgear EA101 doesn't work with 2.6.12-rc5
Seems that it is unable to send packets on 2.6.12-rc5. I can see packets coming in. I downgraded to 2.6.12-rc2 which works. Device ID: 0846:1001 Info from /sys: bConfigurationValue: 1 bDeviceClass: 00 bDeviceProtocol: 00 bDeviceSubClass: 00 bMaxPower: 90mA bNumConfigurations: 1 bNumInterfaces: 1 bcdDevice: 0202 bmAttributes: 80 configuration: detach_state: 0 devnum: 8 idProduct: 1001 idVendor: 0846 manufacturer: NETGEAR maxchild: 0 product: NETGEAR EA101 USB Ethernet Adapter speed: 12 version: 1.00 -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Re: USB problems 2.6.10
Greg KH wrote: > On Thu, Mar 24, 2005 at 08:00:46AM -0500, Wakko Warner wrote: > > I have a system that I just updated to 2.6 and USB fails to work after some > > time (~6-8 hours) giving me the "irq 11:nobody cared" message. > > > > This system is a supermicro p3tdde (via chipset) > > I have ACPI and Preempt enabled (which I will disable and try again) > > > > I notice this rather quickly as my keyboard/mouse are on this controller. I > > have an NEC chip USB2.0 card installed which is currently working. > > Can you try 2.6.11 and see if that is better? I went to 2.6.12-rc2 instead. So far it seems to be working. I was unable to test this until yesterday due to my workload. The only problem I have now is the fact that my keyboard has 8 extra keys which only 3 work under 2.6; all 8 keys work fine under 2.4. I ran showkey -s to verify. I see no log messages with 2.6.12-rc2 (I did with 2.6.10) They keyboard is an HP wireless KBR0133. It came as a set with wireless receiver/mouse/keyboard. -- Lab tests show that use of micro$oft causes cancer in lab animals --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Fw: [Bugme-new] [Bug 4461] New: USB disk not recognised
Pete Zaitcev wrote: > On Fri, 8 Apr 2005 15:06:23 -0700 Andrew Morton <[EMAIL PROTECTED]> wrote: > > (It worked in 2.4 kernels..) > > > Apr 8 22:08:19 opc kernel: hub 1-0:1.0: port 1 disabled by hub (EMI?), > > re-enabling... > > Apr 8 22:08:20 opc kernel: usb 1-1: reset full speed USB device using > > uhci_hcd and address 2 > > Apr 8 22:08:20 opc kernel: usb 1-1: device not accepting address 2, error > > -22 > > > The device works fine under 2.4 and Windoze. > > I seriously doubt that the poster does the testing on the same hardware. I have seen this on my laptop with a cardbus usb2.0 card. Either my slots are bad or the card is bad in that it requires power to be applied externally to drive any device (even a usb memory stick). When external power is not applied, I see errors similar to this. -- Lab tests show that use of micro$oft causes cancer in lab animals --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Extra keys not working with 2.6
Please keep me CCd especially because I'm not on inux-input. I'm emailing the USB list since this is a usb keyboard (wireless HP) This keyboard has 8 extra keys on the top row. Under 2.4, all the keys worked fine. Under 2.6 only 2 of those keys are recognised. This is a partial dmesg when pressing the keys: keyboard.c: can't emulate rawmode for keycode 242 keyboard.c: can't emulate rawmode for keycode 241 keyboard.c: can't emulate rawmode for keycode 241 keyboard.c: can't emulate rawmode for keycode 241 keyboard.c: can't emulate rawmode for keycode 241 keyboard.c: can't emulate rawmode for keycode 241 keyboard.c: can't emulate rawmode for keycode 241 keyboard.c: can't emulate rawmode for keycode 240 keyboard.c: can't emulate rawmode for keycode 240 keyboard.c: can't emulate rawmode for keycode 240 keyboard.c: can't emulate rawmode for keycode 240 keyboard.c: can't emulate rawmode for keycode 244 keyboard.c: can't emulate rawmode for keycode 244 keyboard.c: can't emulate rawmode for keycode 244 Under 2.4 and doing showkey -s I get these codes for the keys: Key Press Release 1 46 c6 2 02 82 3 65 e5 4 6c ec 5 45 c5 6 44 c4 7 4c cc 8 4a ca (The keys aren't numbered) How do I fix this so that it works again? (I cannot test this on the PS/2 port. the receiver doesn't support it) -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB problems 2.6.10
Please keep me CCd. I have a system that I just updated to 2.6 and USB fails to work after some time (~6-8 hours) giving me the "irq 11:nobody cared" message. This system is a supermicro p3tdde (via chipset) I have ACPI and Preempt enabled (which I will disable and try again) I notice this rather quickly as my keyboard/mouse are on this controller. I have an NEC chip USB2.0 card installed which is currently working. Dmesg output: irq 11: nobody cared! [] __report_bad_irq+0x2a/0xa0 [] handle_IRQ_event+0x30/0x70 [] note_interrupt+0x70/0xb0 [] __do_IRQ+0x130/0x140 [] do_IRQ+0x46/0x70 === [] common_interrupt+0x1a/0x20 [] __do_softirq+0x4b/0xd0 [] do_softirq+0x4a/0x60 === [] irq_exit+0x39/0x40 [] do_IRQ+0x4d/0x70 [] common_interrupt+0x1a/0x20 [] default_idle+0x0/0x40 [] default_idle+0x2c/0x40 [] cpu_idle+0x42/0x60 [] start_kernel+0x154/0x170 [] unknown_bootoption+0x0/0x1e0 handlers: [] (usb_hcd_irq+0x0/0x70) [] (usb_hcd_irq+0x0/0x70) [] (usb_hcd_irq+0x0/0x70) Disabling IRQ #11 lspci on the chip that handles usb (full available upon request) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge Subsystem: Super Micro Computer Inc: Unknown device 2166 Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2 :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: Super Micro Computer Inc: Unknown device 2166 Flags: bus master, medium devsel, latency 32 I/O ports at d400 [size=16] Capabilities: [c0] Power Management version 2 :00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at d800 [size=32] Capabilities: [80] Power Management version 2 :00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at dc00 [size=32] Capabilities: [80] Power Management version 2 :00:11.4 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e000 [size=32] Capabilities: [80] Power Management version 2 .config (CONFIG_ stripped to save on space =) X86=y MMU=y UID16=y GENERIC_ISA_DMA=y GENERIC_IOMAP=y EXPERIMENTAL=y CLEAN_COMPILE=y LOCK_KERNEL=y LOCALVERSION="" SYSVIPC=y POSIX_MQUEUE=y SYSCTL=y LOG_BUF_SHIFT=15 HOTPLUG=y KOBJECT_UEVENT=y EMBEDDED=y KALLSYMS=y FUTEX=y EPOLL=y SHMEM=y CC_ALIGN_FUNCTIONS=0 CC_ALIGN_LABELS=0 CC_ALIGN_LOOPS=0 CC_ALIGN_JUMPS=0 MODULES=y MODULE_UNLOAD=y MODULE_FORCE_UNLOAD=y OBSOLETE_MODPARM=y KMOD=y STOP_MACHINE=y X86_PC=y MPENTIUMIII=y X86_CMPXCHG=y X86_XADD=y X86_L1_CACHE_SHIFT=5 RWSEM_XCHGADD_ALGORITHM=y X86_WP_WORKS_OK=y X86_INVLPG=y X86_BSWAP=y X86_POPAD_OK=y X86_GOOD_APIC=y X86_INTEL_USERCOPY=y X86_USE_PPRO_CHECKSUM=y SMP=y NR_CPUS=2 PREEMPT=y X86_LOCAL_APIC=y X86_IO_APIC=y X86_TSC=y X86_MCE=y EDD=m HIGHMEM4G=y HIGHMEM=y MTRR=y IRQBALANCE=y HAVE_DEC_LOCK=y PM=y ACPI=y ACPI_BOOT=y ACPI_INTERPRETER=y ACPI_SLEEP=y ACPI_SLEEP_PROC_FS=y ACPI_AC=y ACPI_BUTTON=y ACPI_VIDEO=y ACPI_FAN=y ACPI_PROCESSOR=y ACPI_THERMAL=y ACPI_BLACKLIST_YEAR=0 ACPI_BUS=y ACPI_EC=y ACPI_POWER=y ACPI_PCI=y ACPI_SYSTEM=y PCI=y PCI_GOANY=y PCI_BIOS=y PCI_DIRECT=y PCI_MMCONFIG=y BINFMT_ELF=y STANDALONE=y PREVENT_FIRMWARE_BUILD=y FW_LOADER=m PARPORT=m PARPORT_PC=m PARPORT_PC_CML1=m PARPORT_PC_FIFO=y PARPORT_PC_SUPERIO=y PARPORT_1284=y BLK_DEV_FD=m BLK_DEV_LOOP=m BLK_DEV_CRYPTOLOOP=m BLK_DEV_RAM_COUNT=16 INITRAMFS_SOURCE="" LBD=y CDROM_PKTCDVD=m CDROM_PKTCDVD_BUFFERS=8 IOSCHED_NOOP=y IOSCHED_DEADLINE=y IOSCHED_CFQ=y IDE=y BLK_DEV_IDE=y BLK_DEV_IDEDISK=y IDEDISK_MULTI_MODE=y BLK_DEV_IDESCSI=m BLK_DEV_IDEPCI=y IDEPCI_SHARE_IRQ=y BLK_DEV_IDEDMA_PCI=y IDEDMA_PCI_AUTO=y BLK_DEV_PDC202XX_OLD=y PDC202XX_BURST=y BLK_DEV_PDC202XX_NEW=y PDC202XX_FORCE=y BLK_DEV_VIA82CXXX=y BLK_DEV_IDEDMA=y IDEDMA_AUTO=y SCSI=m SCSI_PROC_FS=y BLK_DEV_SD=m CHR_DEV_ST=m CHR_DEV_OSST=m BLK_DEV_SR=m CHR_DEV_SG=m SCSI_AIC7XXX=m AIC7XXX_CMDS_PER_DEVICE=32 AIC7XXX_RESET_DELAY_MS=500 AIC7XXX_DEBUG_ENABLE=y AIC7XXX_DEBUG_MASK=0 AIC7XXX_REG_PRETTY_PRINT=y SCSI_QLA2XXX=m MD=y BLK_DEV_MD=m MD_RAID0=m MD_RAID1=m MD_RAID10=m MD_RAID5=m MD_RAID6=m BLK_DEV_DM=m DM_CRYPT=m DM_SNAPSHOT=m DM_MIRROR=m DM_ZERO=m NET=y PACKET=m UNIX=y INET=y IP_MULTICAST=y IP_ADVANCED_ROUTER=y IP_MULTIPLE_TABLES=y IP_ROUTE_FWMARK=y IP_ROUTE_MULTIPATH=y IP_ROUTE_VERBOSE=y INET_AH=m INET_ESP=m
Re: [linux-usb-devel] Help with Linksys USB200M
David Hollis wrote: > On Wed, 2005-03-02 at 12:44 -0500, Wakko Warner wrote: > > This might be a stupid question, but you aren't changing the MAC address of > > the nic at one place and not at the other? > > > Not really changing MAC addresses, though it does bring up a good point: > I've often found that you need to recycle the cable modem on RoadRunner > when you connect a different device otherwise it wont give you an > address via DHCP. Part of their way of making you pay more money so you > can have multiple PCs on the connection I suppose. Well the reason I mention this is because I wanted to use a USB nic to do my internet connectivity. My ISP's DSLAM doesn't pickup on new MAC addresses for atmost around 20 minutes (something about the arp cache which didn't make any sense). I figure I'd change the MAC address to the one that my current nic used to get around that. I never could figure out why it didn't work. I thought either my DSL modem didn't like it or something. I never thought that by changing it's MAC that the nic itself would stop working. I guess I can't use this thing for bridging either. I did find out as long as the first 24-bits remain the same (vendor's code), it would work. I just noticed the problem you were having and thought about my experience with a USB nic. -- Lab tests show that use of micro$oft causes cancer in lab animals --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Help with Linksys USB200M
David Hollis wrote: > On Mon, 2005-02-28 at 11:49 -0600, [EMAIL PROTECTED] wrote: > > > I don't have access to a machine running Windows. > > But, I took the device to the office today and tried it on a machine > > running FC2 also. It worked flawlessly. Here at home I'm connecting to > > RoadRunner (high speed cable). Is that the problem? Any suggestions? > > > > Ok, so we do know that the device works. RoadRunner really shouldn't be > an issue, I just wonder if there may be a crossover cable issue (a bit > of a stretch) This might be a stupid question, but you aren't changing the MAC address of the nic at one place and not at the other? -- Lab tests show that use of micro$oft causes cancer in lab animals --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] FWD: Re: USB DVD
I have the debug information at http://veg.animx.eu.org/usb-storage.debug.dvd.txt It's around 190kb in size. - Forwarded message from Greg KH <[EMAIL PROTECTED]> - Date: Fri, 26 Nov 2004 19:28:17 -0800 From: Greg KH <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: USB DVD X-Mailing-List: [EMAIL PROTECTED] On Thu, Nov 25, 2004 at 10:03:13AM -0500, Wakko Warner wrote: > I have a USB DVD writer (I don't think the 'writer' part makes a difference) > that when I attempt to view a DVD Movie, it can't read some of the sectors > (DVD Auth I guess). The same drive internally on ide works. Is a problem > with USB or the enclosure? Odds are it's the enclosure :) But to be sure, can you enable CONFIG_USB_STORAGE_DEBUG and send the resulting log to the linux-usb-devel mailing list? thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - End forwarded message - -- Lab tests show that use of micro$oft causes cancer in lab animals --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: Zio! compactflash doesn't work
> > What about this one: > > Bus 001 Device 002: ID 0781:0005 SanDisk Corp. SDDR-05b (CF II) ImageMate > > CompactFlash Reader > > That is reported to work with the unusual dev patch > > +/* glc: Greg Corcoran -- tested with SDDR-05b */ > +UNUSUAL_DEV( 0x0781, 0x0005, 0x0005, 0x0005, > + "Sandisk", > + "ImageMate SDDR-05b", > + US_SC_SCSI, US_PR_ZIOCF, init_ziocf, > + US_FL_START_STOP | US_FL_SINGLE_LUN), > + > > together with the Zio! driver at sourceforge, maybe > > http://usbat2.sourceforge.net/index.html > > if I recall correctly. I checked the link. Doesn't look like the drive is ready for 2.6 which is what I planned on using this with. The chip on the device definately says "usbat-2". Unfortuantely, I'm not well versed in kernel hacking so I'll have to wait til they port it. -- Lab tests show that use of micro$oft causes cancer in lab animals --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
