Re: [vox-tech] usb woes
turns out that USB hard drives are accessed via scsi device files. never knew that. well, supposedly they do. someone had one at the IF today, but we never did get it working... pete begin Erik Mullinix [EMAIL PROTECTED] Im so used to suse. It allows me to check on devices like windows.. only it works. Disreguard my babble please As im trying to find the info i had to back it up and it isnt getting found. I was using an olderversion/kernal. And wonder if this version has changed anything. ;-( Im not a programmer. so please excuse me when I dont do things like you. - Original Message - From: Peter Jay Salzman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, February 17, 2002 2:55 AM Subject: Re: [vox-tech] usb woes begin Erik Mullinix [EMAIL PROTECTED] When I went through the device management for my mouse (usb) and tried my scanner. it was coming up under the scsi device list. but unnaccessable innicialy.Did you know suse has a nice scanner utility ? device management? what's device management? are we talking about windows or linux? there appears to be no evidence that the kernel is mis-managing the devices. at least, none that i can see. maybe this is a windows (or suse) thing? i dunno. it's just hard to believe the linux would misregister hardware. especially hardware plugged into completely different ports. and I dont have it overclocked. I think there is a problem with the chipset controls for the pci buss. wierd. did you know that there were bad problems of people selling over rated celeron chips? apic errors are very rare. except when a CPU is run at a speed faster than its rating. i forget the details, but there are websites out there that can tell you if you have a mislabelled celeron. even fox news ran a story on this about 3 years ago. pete ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech -- Enron..safe legal abortion..civil liberty..repealing ICBM treaty..deficit.. What's worse? Screwing an intern or screwing an entire country? PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
On Mon, Feb 18, 2002 at 01:45:36AM -0800, Peter Jay Salzman wrote: turns out that USB hard drives are accessed via scsi device files. Yep. My CF card reader (which connects via USB) appears as /dev/sda1 -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
On Mon, Feb 18, 2002 at 01:57:12AM -0800, nbs wrote: On Mon, Feb 18, 2002 at 01:45:36AM -0800, Peter Jay Salzman wrote: turns out that USB hard drives are accessed via scsi device files. Yep. My CF card reader (which connects via USB) appears as /dev/sda1 PS - Interestingly, the CF cards themselves appear as IDE drives on the Zaurus (eg, /dev/hda1 :) ) (And the SD card appears as /dev/mmcda1 ... and the 'RAM' filesystem appears as /dev/mtdblock1 ) Wacky wacky :) -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
Im so used to suse. It allows me to check on devices like windows.. only it works. Disreguard my babble please As im trying to find the info i had to back it up and it isnt getting found. I was using an olderversion/kernal. And wonder if this version has changed anything. ;-( Im not a programmer. so please excuse me when I dont do things like you. - Original Message - From: Peter Jay Salzman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, February 17, 2002 2:55 AM Subject: Re: [vox-tech] usb woes begin Erik Mullinix [EMAIL PROTECTED] When I went through the device management for my mouse (usb) and tried my scanner. it was coming up under the scsi device list. but unnaccessable innicialy.Did you know suse has a nice scanner utility ? device management? what's device management? are we talking about windows or linux? there appears to be no evidence that the kernel is mis-managing the devices. at least, none that i can see. maybe this is a windows (or suse) thing? i dunno. it's just hard to believe the linux would misregister hardware. especially hardware plugged into completely different ports. and I dont have it overclocked. I think there is a problem with the chipset controls for the pci buss. wierd. did you know that there were bad problems of people selling over rated celeron chips? apic errors are very rare. except when a CPU is run at a speed faster than its rating. i forget the details, but there are websites out there that can tell you if you have a mislabelled celeron. even fox news ran a story on this about 3 years ago. pete ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
hi erik, ok, other than the fact that (juding by your apic errors) you probably overclock your cpus, this didn't say much. why do you think the USB devices show up as scsi devices? pete begin Erik Mullinix [EMAIL PROTECTED] Pete. My system is a dual celeron 500. i do have some issues with APIC and sound.. but not services or devices. SCSI subsystem driver Revision: 1.00 request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted (snip) usb.c: registered new driver usbdevfs usb.c: registered new driver hub uhci.c: USB UHCI at I/O 0xa000, IRQ 19 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected uhci.c: :USB Universal Host Controller Interface driver eth1: Setting half-duplex based on MII#1 link partner capability of 0081. -- Enron..safe legal abortion..civil liberty..repealing ICBM treaty..deficit.. What's worse? Screwing an intern or screwing an entire country? PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
Heya. Ive been finding that the USB sometimes comes accross as a SCSI device. Dont know why. but it is and my dual Celeron 500 is using it. Dont know the particulars but I hope this sends you in the right direction. hello all, i have *never* played with usb at all. last night was my first attempt, (just bought a handspring visor prism) and i'm afraid it failed. here's what i did: 1. compiled 2.5.1 with the following options: CONFIG_USB (Support for USB) CONFIG_USB_DEBUG (USB verbose debug messages) CONFIG_USB_UHCI (UHCI: Intel, PIIX4, VIA, ...) CONFIG_USB_SERIAL_VISOR (USB Handspring Visor / Palm m50x) this is on an dual celeron 550, so i believe UHCI is correct. 2. created the appropriate device files: crw-rw-rw- root root 188, 0 Feb 14 23:41 /dev/ttyUSB0 crw-rw-rw- root root 188, 1 Feb 14 23:41 /dev/ttyUSB1 crw-rw-rw- root root 188, 2 Feb 14 23:43 /dev/ttyUSB2 crw-rw-rw- root root 188, 3 Feb 14 23:43 /dev/ttyUSB3 lrwxrwxrwx root root 12 Feb 14 23:43 /dev/pilot - /dev/ttyUSB1 lrwxrwxrwx root root 12 Feb 14 23:52 /dev/visor - /dev/ttyUSB1 3. after rebooting, here were the assigned IRQ's: CPU0 CPU1 0: 12128 0 XT-PIC timer 1: 81 0 XT-PIC keyboard 2: 0 0 XT-PIC cascade 5: 4 0 XT-PIC soundblaster 8: 2 0 XT-PIC rtc 10: 0 0 XT-PIC usb-uhci 11: 33 0 XT-PIC eth0 12: 10 0 XT-PIC PS/2 Mouse 14: 29553 0 XT-PIC ide0 15: 6227 0 XT-PIC ide1 4. here's dmsg output: usb.c: registered new driver hub usb-uhci.c: $Revision: 1.268 $ time 17:52:42 Feb 14 2002 usb-uhci.c: High bandwidth mode enabled PCI: Assigned IRQ 11 for device 00:07.2 usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 usb.c: kmalloc IF cddbcb00, numif 1 usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1 usb.c: USB device number 1 default language ID 0x0 Product: USB UHCI Root Hub SerialNumber: d000 hub.c: USB hub found hub.c: 2 ports detected hub.c: standalone hub hub.c: ganged power switching hub.c: global over-current protection hub.c: Port indicators are not supported hub.c: power on to power good time: 2ms hub.c: hub controller current requirement: 0mA hub.c: port removable status: RR hub.c: local power source is good hub.c: no over-current condition exists hub.c: enabling power on all ports usb.c: hub driver claimed interface cddbcb00 usb-uhci.c: v1.268:USB Universal Host Controller Interface driver usb.c: registered new driver serial usbserial.c: USB Serial Driver core v1.4 usbserial.c: USB Serial support registered for Handspring Visor/Palm 4.0 usbserial.c: USB Serial support registered for Sony Clié 3.5 visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.7 so this all looks great, doesn't it? looks perfect. how here is where the problems begin. 1. it's my understanding that there should be a file /proc/bus/usb. this file is missing. i _thought_ it should be created upon successful initialization of usb.c. but it's simply not there. 2. when I settle the visor into the cradle: hub.c: Cannot enable port 2 of hub 1, disabling port. hub.c: Maybe the USB cable is bad? of course, it's _possible_ that the cable is bad, but i seriously doubt it. i'm trying to set the visor up on rhonda's windows machine right now, but i'm nearly certain it will work. 3. ever since compiling usb into my kernel, the system hangs when i reboot or halt. during the reboot/halt sequence, when sending TERM to all processes the system just hangs. hitting return puts a newline onto the console, so i assume the kernel is just fine and dandy. it's probably waiting for something to happen. perhaps if i waited long enough, something would time out. but i haven't waited more than than 3 minutes (too impatient). in any event, it shouldn't be doing this. 4. hotsyncing, of course, doesn't work. the visor reports that it can't connect to the computer (with coldsync. i assume the same thing will happen using pilot-link. these problems are kernel problems, not application problems). at the same time, the kernel prints alot of debugging info and finally says it's disabling the usb port. i'd like to concentrate on problem 1; it seems more fundamental than the other problems, but at this point, i'm stuck other than to try this on another system. ANY advice, thoughts or streams of consciousness would be appreciated. thanks, pete ___
Re: [vox-tech] usb woes
begin Erik Mullinix [EMAIL PROTECTED] Heya. Ive been finding that the USB sometimes comes accross as a SCSI device. Dont know why. but it is and my dual Celeron 500 is using it. what exactly do you mean? you access usb devices using scsi device files? or your usb devices get registered by scsi drivers? can you post dmesg (or lsmod)? pete -- Enron..safe legal abortion..civil liberty..repealing ICBM treaty..deficit.. What's worse? Screwing an intern or screwing an entire country? PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
On Fri, 15 Feb 2002, Peter Jay Salzman wrote: hello all, i have *never* played with usb at all. last night was my first attempt, (just bought a handspring visor prism) and i'm afraid it failed. [...] 4. here's dmsg output: [...] Product: USB UHCI Root Hub SerialNumber: d000 hub.c: USB hub found hub.c: 2 ports detected [...] 1. it's my understanding that there should be a file /proc/bus/usb. this file is missing. i _thought_ it should be created upon successful initialization of usb.c. but it's simply not there. Dunno. 2. when I settle the visor into the cradle: hub.c: Cannot enable port 2 of hub 1, disabling port. hub.c: Maybe the USB cable is bad? of course, it's _possible_ that the cable is bad, but i seriously doubt it. i'm trying to set the visor up on rhonda's windows machine right now, but i'm nearly certain it will work. Note that the driver said it had detected two ports in your hub. If you have ports in both the front and back of your computer, try using only the front ports or only the back ports. That is, unplug all cables but the one you are working with if possible. --- Jeff NewmillerThe . . Go Live... DCN:[EMAIL PROTECTED]Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] usb woes
i have only been able to get jpilot working, but it does work very well :-) Rusty On Friday 15 February 2002 20:42, you wrote: On Fri, 15 Feb 2002, Peter Jay Salzman wrote: i still can't sync the visor though. coldsync segfaulted. recompiled it with -g, did a backtrace, found a null pointer dereference and sent a bug report to the developers. Are you using the PalmOS sync programs? I've read they're flaky, if it works at all, when using USB connections. Apparently you can get serial connectors that work. If you get it working, let me know -- I could use syncing on my Clie :) btw, i found the problem with the /proc/bus/usb entries, or lack thereof. i needed to set CONFIG_USB_DEVICEFS is not set and then mount the device filesystem in fstab: none /proc/bus/usb usbdevfs default0 0 After mounting /proc/bus/usb, what does usbview show? -Mark ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
