AirPrime 5220 1xEVDO PC Card

AirPrime 5220 1xEVDO PC Card

[Ian Pilcher]

I have an AirPrime 5220 EVDO card from Verizon Wireless.  The good news
is that I basically works under Linux (http://www.ka9q.net/5220.html).
The bad news is that it's necessary to manually load the usbserial
module and create the device node.

Here is the dmesg output when I insert the card:

ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ohci_hcd 0000:03:00.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:03:00.0 to 64
ohci_hcd 0000:03:00.0: irq 11, pci mem f8bf6000
ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ohci_hcd 0000:03:00.0: wakeup
usb 4-1: new full speed USB device using address 2
usb 4-1: device not accepting address 2, error -110
usb 4-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
usb 4-1: new full speed USB device using address 4

As you can see, the OHCI module gets loaded properly, but the usbserial
module does not get loaded.

Here is the lspci output for the card:

03:00.0 USB Controller: Agere Systems (former Lucent Microelectronics)
                 USS-312 USB Controller (rev 10) (prog-if 10 [OHCI])
         Subsystem: Agere Systems (former Lucent Microelectronics)
                         USS-312 USB Controller
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
                         ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
                         <TAbort- <MAbort- >SERR- <PERR-
         Latency: 64 (750ns min, 21500ns max)
         Interrupt: pin A routed to IRQ 11
         Region 0: Memory at 40800000 (32-bit, non-prefetchable)
                         [size=4K]
         Capabilities: [50] Power Management version 2
                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
                                 PME(D0-,D1+,D2+,D3hot+,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=1 PME-

And here's what lsusb says about it:

Bus 004 Device 004: ID 0f3d:0112
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            0 (Defined at Interface level)
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0        16
   idVendor           0x0f3d
   idProduct          0x0112
   bcdDevice            0.01
   iManufacturer           1 AirPrime, Incorporated
   iProduct                2 AirPrime CDMA Wireless PC Card
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           62
     bNumInterfaces          2
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0xc0
       Self Powered
     MaxPower              100mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           3
       bInterfaceClass       255 Vendor Specific Class
       bInterfaceSubClass    255 Vendor Specific Subclass
       bInterfaceProtocol    255 Vendor Specific Protocol
       iInterface              4 Data Interface
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               none
           Usage Type               Data
         wMaxPacketSize     0x0010  bytes 16 once
         bInterval             128
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x8a  EP 10 IN
         bmAttributes            2
           Transfer Type            Bulk
           Synch Type               none
           Usage Type               Data
         wMaxPacketSize     0x0040  bytes 64 once
         bInterval               0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x0b  EP 11 OUT
         bmAttributes            2
           Transfer Type            Bulk
           Synch Type               none
           Usage Type               Data
         wMaxPacketSize     0x0040  bytes 64 once
         bInterval               0
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        1
       bAlternateSetting       0
       bNumEndpoints           2
       bInterfaceClass       255 Vendor Specific Class
       bInterfaceSubClass    255 Vendor Specific Subclass
       bInterfaceProtocol    255 Vendor Specific Protocol
       iInterface              4 Data Interface
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x82  EP 2 IN
         bmAttributes            2
           Transfer Type            Bulk
           Synch Type               none
           Usage Type               Data
         wMaxPacketSize     0x0040  bytes 64 once
         bInterval               0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x05  EP 5 OUT
         bmAttributes            2
           Transfer Type            Bulk
           Synch Type               none
           Usage Type               Data
         wMaxPacketSize     0x0040  bytes 64 once
         bInterval               0
   Language IDs: (length=4)
      0409 English(US)

As you can see, bInterface class is set to 255 (Vendor Specific Class).
I assume that this is why the usbserial module isn't loaded.  When I
manually load usbserial, specifying the vendor and product, it works,
and I get the following dmesg output:

drivers/usb/serial/usb-serial.c: USB Serial support registered for
                 Generic
usbserial_generic 4-1:1.0: Generic converter detected
usb 4-1: Generic converter now attached to ttyUSB0
usbserial_generic 4-1:1.1: Generic converter detected
usb 4-1: Generic converter now attached to ttyUSB1
usbcore: registered new driver usbserial_generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0

I've also turned udev logging on, and the following entries appear in
the syslog:

udev[3626]: creating device node '/dev/<NULL>1'
udev[3624]: creating device node '/dev/<NULL>0'

Sure enough, my /dev directory now has:

crw-------  1 root root 0, 0 Apr 27 12:17 /dev/<NULL>0
crw-------  1 root root 0, 1 Apr 27 12:17 /dev/<NULL>1

Note that, ignoring the messed up names, the major device numbers are
incorrect.  I've verified this by symlinking /dev/modem to <NULL>0 and
attempting to make a connection; kppp reports that it can't open the
modem.  If I manually 'mknod /dev/ttyUSB0 c 188 0' and symlink
/dev/modem to ttyUSB0, I can connect with kppp.

So my questions (finally!):

1.  How can I get the hotplug system to load the usbserial module,
     specifying the vendor and product, when this card is inserted.
     I've tried adding "usbserial 0x0003 0x0f3d 0x0112 ..." to
     /etc/hotplug/usb.usermap, but it did not appear to have any
     effect.

2.  How can I get udev to create the proper device nodes when usbserial
     loads.

TIA!

-- 
====================================
Ian Pilcher                                        i.pilcher@comcast.net
====================================



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Greg KH]

On Wed, Apr 27, 2005 at 12:34:36PM -0500, Ian Pilcher wrote:
> I have an AirPrime 5220 EVDO card from Verizon Wireless.  The good news
> is that I basically works under Linux (http://www.ka9q.net/5220.html).
> The bad news is that it's necessary to manually load the usbserial
> module and create the device node.

You mean the generic usb-serial drivr works for this device?  Nice.

Short answer, you can't automatically load the generic usb-serial driver
for any devices.  Use the modules /etc/ files to do it for you at boot
time.

Long answer, write a very tiny usb-serial driver that uses these
vendor/product device ids.  Then it will be automatically loaded
properly.  Someone has done this for another type of device in the
latest -mm kernel if you want an example of this.

> I've also turned udev logging on, and the following entries appear in
> the syslog:
> 
> udev[3626]: creating device node '/dev/<NULL>1'
> udev[3624]: creating device node '/dev/<NULL>0'
> 
> Sure enough, my /dev directory now has:
> 
> crw-------  1 root root 0, 0 Apr 27 12:17 /dev/<NULL>0
> crw-------  1 root root 0, 1 Apr 27 12:17 /dev/<NULL>1

Yeah, that's a kernel bug, sorry, haven't gotten around to fixing it
yet...  Nothing udev can do there to help you :(

thanks,

greg k-h


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Greg KH]

On Wed, Apr 27, 2005 at 11:00:24AM -0700, Greg KH wrote:
> Long answer, write a very tiny usb-serial driver that uses these
> vendor/product device ids.  Then it will be automatically loaded
> properly.  Someone has done this for another type of device in the
> latest -mm kernel if you want an example of this.

Oh, that was just too easy, here's a patch, let me know if this driver
works for you.

thanks,

greg k-h
------------

USB: add a driver for the AirPrime CDMA Wireless PC card.

Easier than trying to use the generic usb-serial driver.

Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>


---
 drivers/usb/serial/Kconfig    |    9 ++++++
 drivers/usb/serial/Makefile   |    1 
 drivers/usb/serial/airprime.c |   63 ++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 73 insertions(+)

--- /dev/null	1970-01-01 00:00:00.000000000 +0000
+++ gregkh-2.6/drivers/usb/serial/airprime.c	2005-04-27 11:16:29.000000000 -0700
@@ -0,0 +1,63 @@
+/*
+ * AirPrime CDMA Wireless Serial USB driver
+ *
+ * Copyright (C) 2005 Greg Kroah-Hartman <gregkh@suse.de>
+ *
+ *	This program is free software; you can redistribute it and/or
+ *	modify it under the terms of the GNU General Public License version
+ *	2 as published by the Free Software Foundation.
+ */
+
+#include <linux/kernel.h>
+#include <linux/init.h>
+#include <linux/tty.h>
+#include <linux/module.h>
+#include <linux/usb.h>
+#include "usb-serial.h"
+
+static struct usb_device_id id_table [] = {
+	{ USB_DEVICE(0xf3d, 0x0112) },
+	{ },
+};
+MODULE_DEVICE_TABLE(usb, id_table);
+
+static struct usb_driver airprime_driver = {
+	.owner =	THIS_MODULE,
+	.name =		"airprime",
+	.probe =	usb_serial_probe,
+	.disconnect =	usb_serial_disconnect,
+	.id_table =	id_table,
+};
+
+static struct usb_serial_device_type airprime_device = {
+	.owner =		THIS_MODULE,
+	.name =			"airprime",
+	.id_table =		id_table,
+	.num_interrupt_in =	NUM_DONT_CARE,
+	.num_bulk_in =		NUM_DONT_CARE,
+	.num_bulk_out =		NUM_DONT_CARE,
+	.num_ports =		2,
+};
+
+static int __init airprime_init(void)
+{
+	int retval;
+
+	retval = usb_serial_register(&airprime_device);
+	if (retval)
+		return retval;
+	retval = usb_register(&airprime_driver);
+	if (retval)
+		usb_serial_deregister(&airprime_device);
+	return retval;
+}
+
+static void __exit airprime_exit(void)
+{
+	usb_deregister(&airprime_driver);
+	usb_serial_deregister(&airprime_device);
+}
+
+module_init(airprime_init);
+module_exit(airprime_exit);
+MODULE_LICENSE("GPL");
--- gregkh-2.6.orig/drivers/usb/serial/Makefile	2005-04-27 11:15:48.000000000 -0700
+++ gregkh-2.6/drivers/usb/serial/Makefile	2005-04-27 11:16:29.000000000 -0700
@@ -11,6 +11,7 @@
 
 usbserial-objs	:= usb-serial.o generic.o bus.o $(usbserial-obj-y)
 
+obj-$(CONFIG_USB_SERIAL_AIRPRIME)		+= airprime.o
 obj-$(CONFIG_USB_SERIAL_BELKIN)			+= belkin_sa.o
 obj-$(CONFIG_USB_SERIAL_CP2101)			+= cp2101.o
 obj-$(CONFIG_USB_SERIAL_CYBERJACK)		+= cyberjack.o
--- gregkh-2.6.orig/drivers/usb/serial/Kconfig	2005-04-27 11:15:48.000000000 -0700
+++ gregkh-2.6/drivers/usb/serial/Kconfig	2005-04-27 11:16:29.000000000 -0700
@@ -53,6 +53,15 @@
 	  support" be compiled as a module for this driver to be used
 	  properly.
 
+config USB_SERIAL_AIRPRIME
+	tristate "USB AirPrime CDMA Wireless Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use a AirPrime CDMA Wireless PC card.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called airprime.
+
 config USB_SERIAL_BELKIN
 	tristate "USB Belkin and Peracom Single Port Serial Driver"
 	depends on USB_SERIAL


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Ian Pilcher]

Greg KH wrote:
> Oh, that was just too easy, here's a patch, let me know if this driver
> works for you.

GOOD NEWS:

The driver works.  It's loaded automatically when I insert the card, and
the /dev/ttyUSB* devices are created with the correct major numbers.

BAD NEWS:

Two "bogus" /dev/ttyUSB* devices are also created.

When I manually load usbserial, sysfs contains:

     /sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0000:03:00.0/
         usb4/4-1/
             4-1:1.0/ttyUSB0
             4-1:1.1/ttyUSB1

I believe that this is correct.  Windows XP shows two ports:

     AirPrime CDMA Wireless Modem: USB\Vid_0f3d&Pid_0112&MI_00
     AirPrime Control Port: USB\Vid_0f3d&Pid_0112&MI_01

When the airprime driver is loaded, sysfs contains:

     /sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0000:03:00.0/
         usb4/4-1/
             4-1:1.0/ttyUSB0
                     ttyUSB1
             4-1:1.1/ttyUSB2
                     ttyUSB3

I tried using kppp to make a connection with all of these ports.
ttyUSB0 works, just like ttyUSB0 with the generic driver.  ttyUSB2 hangs
at "Initializing Modem...", just like ttyUSB1 with the generic driver.
(This makes sense since this is the "Control Port", not the modem port.)

Trying to connect with ttyUSB1 or ttyUSB3 causes a kernel oops.

-- 
====================================
Ian Pilcher                                        i.pilcher@comcast.net
====================================



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[David Brownell]

On Wednesday 27 April 2005 5:57 pm, Ian Pilcher wrote:
> 
> Two "bogus" /dev/ttyUSB* devices are also created.
> 
> When I manually load usbserial, sysfs contains:
> 
>      /sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0000:03:00.0/
>          usb4/4-1/
>              4-1:1.0/ttyUSB0
>              4-1:1.1/ttyUSB1
> 
> I believe that this is correct.  Windows XP shows two ports:
> 
>      AirPrime CDMA Wireless Modem: USB\Vid_0f3d&Pid_0112&MI_00
>      AirPrime Control Port: USB\Vid_0f3d&Pid_0112&MI_01

Sounds like this device is sort of like a hacked CDC ACM ... where
the control interface is separated from the data one, but they
must be used together.  So, like the cdc-acm driver, there would
be only one .../ttyUSBn file.  Not two, or four ... ;)

- Dave


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Matthew Dharm]

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

On Wed, Apr 27, 2005 at 07:57:21PM -0500, Ian Pilcher wrote:
> Greg KH wrote:
> >Oh, that was just too easy, here's a patch, let me know if this driver
> >works for you.
> 
> GOOD NEWS:
> 
> The driver works.  It's loaded automatically when I insert the card, and
> the /dev/ttyUSB* devices are created with the correct major numbers.
> 
> BAD NEWS:
> 
> Two "bogus" /dev/ttyUSB* devices are also created.

I'm more used to looking at /proc/bus/usb/devices than lsusb, but it looks
to me like your device has two interfaces (usb-level interfaces, that is).

The driver Greg wrote looks for a compatible interface to bind to.  The way
it specified what type of interface, both advertised interfaces qualify.

Then, it specified two serial-level interfaces for each usb-level
interface you bind to.  Thus, 4 interfaces.

I think the first thing to do is change the driver to .num_ports = 1 --
that will get you down to just 2 /dev/ttyUSB nodes.  Try that, and then see
what happens when you try to talk to the various /dev/ttyUSB nodes.

Next, we may want to think about how to talk to that control interface.
But, that's out of my expertise.  You may want to use something like
minicom (instead of kppp) to debug with.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

You suck Stef.
					-- Greg 
User Friendly, 11/29/97

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: AirPrime 5220 1xEVDO PC Card

[Greg KH]

On Wed, Apr 27, 2005 at 07:57:21PM -0500, Ian Pilcher wrote:
> Greg KH wrote:
> >Oh, that was just too easy, here's a patch, let me know if this driver
> >works for you.
> 
> GOOD NEWS:
> 
> The driver works.  It's loaded automatically when I insert the card, and
> the /dev/ttyUSB* devices are created with the correct major numbers.

Yeah!

> BAD NEWS:
> 
> Two "bogus" /dev/ttyUSB* devices are also created.

Boo!

Can you try the patch below to see if it fixes the issue?

> Trying to connect with ttyUSB1 or ttyUSB3 causes a kernel oops.

What is the oops message?

thanks,

greg k-h

--- gregkh-2.6.orig/drivers/usb/serial/airprime.c	2005-04-27 11:20:26.000000000 -0700
+++ gregkh-2.6/drivers/usb/serial/airprime.c	2005-04-27 22:11:08.000000000 -0700
@@ -36,7 +36,7 @@
 	.num_interrupt_in =	NUM_DONT_CARE,
 	.num_bulk_in =		NUM_DONT_CARE,
 	.num_bulk_out =		NUM_DONT_CARE,
-	.num_ports =		2,
+	.num_ports =		1,
 };
 
 static int __init airprime_init(void)


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Ian Pilcher]

Greg KH wrote:
> Can you try the patch below to see if it fixes the issue?

That works.  (Matthew Dharm suggested the same change.)

AFAICT, this driver is fully functional now.  Less than 24 hours!

> What is the oops message?

Not sure that it matters, but here you go:

Unable to handle kernel NULL pointer dereference at virtual address 00000008
printing eip:
f8c48a4c
*pde = 3255d067
Oops: 0002 [#1]
Modules linked in: ppp_deflate zlib_deflate ppp_async crc_ccitt 
ppp_generic slhc airprime usbserial ohci_hcd parport_pc lp parport md5 
ipv6 ds ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables vfat 
fat dm_mod yenta_socket pcmcia_core uhci_hcd hw_random snd_intel8x0m 
snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer 
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 
aes_i586 airo e100 mii floppy ext3 jbd
CPU:    0
EIP:    0060:[<f8c48a4c>]    Not tainted VLI
EFLAGS: 00010282   (2.6.9-5.EL.root.evdo)
EIP is at usb_serial_generic_open+0x6e/0xef [usbserial]
eax: f8c48e7e   ebx: f8c48e7e   ecx: c0000480   edx: 00000000
esi: f6af9800   edi: f27f5000   ebp: f7f4dc00   esp: f306ded4
ds: 007b   es: 007b   ss: 0068
Process kppp (pid: 3847, threadinfoó06d000 taskó1aebd0)
Stack: f7f4dc00 f611dfc0 f27f5000 00000000 f8c472d5 f1cca480 ffffffed 
f1cca480
        f27f5000 00000100 c0216a87 00008902 0bc00001 f27f5000 00000001 
f306d000
        f7f4de04 f662a714 00000000 c016c6c4 f1cca480 00000001 f1cca480 
f662a714
Call Trace:
  [<f8c472d5>] serial_open+0x95/0xd9 [usbserial]
  [<c0216a87>] tty_open+0x132/0x34a
  [<c016c6c4>] chrdev_open+0x325/0x3b9
  [<c01614e8>] dentry_open+0xbd/0x180
  [<c0161425>] filp_open+0x36/0x3c
  [<c011af55>] recalc_task_prio+0x128/0x133
  [<c01d8e46>] direct_strncpy_from_user+0x3e/0x5d
  [<c01618e9>] sys_open+0x31/0x7d
  [<c0301bfb>] syscall_call+0x7/0xb
Code: a1 00 00 00 0f b6 45 20 8b 33 8b 55 1c 8b 0e c1 e0 0f c1 e1 08 09 
c1 8b 43 04 81 c9 80 00 00 c0 8b 98 e8 00 00 00 b8 7e 8e c4 f8 <c7> 42 
08 00 00 00 00 85 db 0f 44 d8 89 72 34 c7 42 04 3c 4b 24

(I'm pretty sure this translates to, "The hardware you just tried to
access doesn't exist.")

Thanks for your help!

-- 
====================================
Ian Pilcher                                        i.pilcher@comcast.net
====================================



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Linas Vepstas]

On Thu, Apr 28, 2005 at 07:26:14AM -0500, Ian Pilcher was heard to remark:
> 
> >What is the oops message?
> 
> Not sure that it matters, but here you go:
> 
> Unable to handle kernel NULL pointer dereference at virtual address 00000008

Yes, well, harmless user actions shouldn't oops kernels; it matters.

--linas


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: AirPrime 5220 1xEVDO PC Card

[Ian Pilcher]

Linas Vepstas wrote:
> Yes, well, harmless user actions shouldn't oops kernels; it matters.

It doesn't matter now, because the driver has been fixed.

-- 
====================================
Ian Pilcher                                        i.pilcher@comcast.net
====================================



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel