From: Andrew D Kirch <trelane@trelane.net>
To: evolution@lists.ximian.com, linux-kernel@vger.kernel.org
Subject: sync'ing evolution with 2.6/udev
Date: Thu, 22 Apr 2004 16:21:44 -0500 [thread overview]
Message-ID: <1082668904.16612.8.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]
This is a bit of an odd cross post, but please stick with me if you
will...
I am attempting to add a USB cradle (Visor Prism if anyone cares) with
Evolution. /var/log/messages gives me the following output:
Apr 22 16:01:36 localhost kernel: usb 2-2: new full speed USB device
using address 10
Apr 22 16:01:37 localhost usb.agent[29165]: ... no modules for USB
product 82d/100/100
Apr 22 16:01:42 localhost kernel: usb 2-2: USB disconnect, address 10
I'm not seeing a device mapped to /dev (watch 'ls -aslR | wc -l') during
a sync doesn't show a change in total files. This means I've not got a
device to bind the cradle to ie /dev/ttyUSBN.
My hardware follows:
Athlon 64 3200+
Gigabyte G7VNXP
1024mb PC-3200ddr
Nvidia GeForce FX 5700
running:
Linux gentoo64 2.6.5 #1 Wed Apr 21 10:56:50 EST 2004 x86_64 4 GNU/Linux
/proc/modules:
ohci_hcd 17348 0 - Live 0xffffffffa037b000
uhci_hcd 29088 0 - Live 0xffffffffa0372000
via_rhine 18888 0 - Live 0xffffffffa036c000
mii 4544 1 via_rhine, Live 0xffffffffa0369000
r8169 10692 0 - Live 0xffffffffa0365000
parport_pc 36672 0 - Live 0xffffffffa035b000
parport 37708 1 parport_pc, Live 0xffffffffa0350000
nvidia 2564596 0 - Live 0xffffffffa00dc000
ide_scsi 14724 0 - Live 0xffffffffa00d7000
i2c_viapro 6732 0 - Live 0xffffffffa00d4000
i2c_isa 2432 0 - Live 0xffffffffa00d2000
adm1021 12168 0 - Live 0xffffffffa00ce000
eeprom 7048 0 - Live 0xffffffffa00cb000
it87 21580 0 - Live 0xffffffffa00c4000
i2c_sensor 2688 3 adm1021,eeprom,it87, Live 0xffffffffa00c2000
snd_emu10k1_synth 7040 0 - Live 0xffffffffa00bf000
snd_emu10k1 85924 1 snd_emu10k1_synth, Live 0xffffffffa00a9000
snd_ac97_codec 64196 1 snd_emu10k1, Live 0xffffffffa0098000
snd_emux_synth 36736 1 snd_emu10k1_synth, Live 0xffffffffa008e000
snd_seq_virmidi 6208 1 snd_emux_synth, Live 0xffffffffa008b000
snd_seq_midi_emul 8576 1 snd_emux_synth, Live 0xffffffffa0087000
snd_hwdep 7944 2 snd_emu10k1,snd_emux_synth, Live 0xffffffffa0084000
snd_util_mem 3968 2 snd_emu10k1,snd_emux_synth, Live 0xffffffffa0082000
snd_seq_midi 7104 0 - Live 0xffffffffa007f000
snd_rawmidi 20896 3 snd_emu10k1,snd_seq_virmidi,snd_seq_midi, Live
0xffffffffa0078000
ide_tape 34272 0 - Live 0xffffffffa006e000
st 37476 0 - Live 0xffffffffa0063000
sbp2 21960 0 - Live 0xffffffffa005c000
ohci1394 30404 0 - Live 0xffffffffa0053000
ieee1394 98264 2 sbp2,ohci1394, Live 0xffffffffa003a000
usb_storage 67328 0 - Live 0xffffffffa0028000
hid 23808 0 - Live 0xffffffffa0021000
ehci_hcd 24836 0 - Live 0xffffffffa0019000
usbcore 95856 7 ohci_hcd,uhci_hcd,usb_storage,hid,ehci_hcd, Live
0xffffffffa0000000
Let me know if more detail will help, or if further crossposting is
unwanted (apologies)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-04-22 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 21:21 Andrew D Kirch [this message]
2004-04-22 23:30 ` sync'ing evolution with 2.6/udev Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1082668904.16612.8.camel@localhost \
--to=trelane@trelane.net \
--cc=evolution@lists.ximian.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox