April 2007 - WLUG - wlug.mailman3.com

Re: [Wlug] "Filesize limit exceeded" error

by Aaron Haviland

Richard Klein wrote, on Apr 01, 2007 at 14:04 EDT: > Chuck Noyes wrote: > > Hi All, > > > > I'm trying to copy a 7.9GB tgz file to an external USB drive. The > > external drive is 500GB. About half way through the cp process, I get > > the error message: > > > > 8119 file size limit exceeded cp maui-Sun.tgz /media/My\ Book/chuck/ > > > > There's plenty of space on the USB drive. I'm running 'edgy eft' on a > > laptop. > > > > Any ideas on what might be going on here?? > > > > TIA, > > What's the file system on the external drive? FAT32? My guess is that > you're exceeding the file size limit of that file system. Indeed. FAT16 can only support files up to 2GB, and FAT32 can only support files up to 4GB. I haven't heard of a FAT64 yet, but NTFS can support files up to 1 exabyte (1x10^6 terabytes). (Or was that exbibyte...?) -- Aaron Haviland

April 1, 2007

Re: [Wlug] "Filesize limit exceeded" error

by Richard Klein

Chuck Noyes wrote: > Hi All, > > I'm trying to copy a 7.9GB tgz file to an external USB drive. The > external drive is 500GB. About half way through the cp process, I get > the error message: > > 8119 file size limit exceeded cp maui-Sun.tgz /media/My\ Book/chuck/ > > There's plenty of space on the USB drive. I'm running 'edgy eft' on a > laptop. > > Any ideas on what might be going on here?? > > TIA, What's the file system on the external drive? FAT32? My guess is that you're exceeding the file size limit of that file system. -- Rich

April 1, 2007

"Filesize limit exceeded" error

by Chuck Noyes

Hi All, I'm trying to copy a 7.9GB tgz file to an external USB drive. The external drive is 500GB. About half way through the cp process, I get the error message: 8119 file size limit exceeded cp maui-Sun.tgz /media/My\ Book/chuck/ There's plenty of space on the USB drive. I'm running 'edgy eft' on a laptop. Any ideas on what might be going on here?? TIA, -- -Chuck

April 1, 2007

Re: [Wlug] DSL testing

by Keith Wright

> From: Eric Stein <eastein(a)WPI.EDU> > > At my parent's house, the DSL was going slowly until > we added DSL splitters. Adding them improved > performance drastically. Did you install them yourself, or call for help? Where did you get them? Do they come in different kinds, or can I get an ADLS splitter and know I have one? Why did you need more than one (as implied by your use of plural)? I think my ISP wants to add one outside the house next to the NID (box with terminals to screw the phone lines to). I don't even think there is one on this old house. I assume that then there must be new holes drilled in the outside wall of the house to run the digital cable alongside the voice/analog wires into the house. I don't see why the splitter can not go a few feet farther down the wire, inside the house. Less drilling, no rain on the splitter, the only downside seems to be about ten feet of the old wire stays there, but is that worse than what comes off the telephone pole? -- Keith

April 1, 2007

Re: [Wlug] Seeking help with a USB barcode scanner

by Keith Wright

> From: Jamie Guinan <guinan(a)bluebutton.com> > > > > I tried your "od -x" trick on each of these to no avail. I > > pointed the barcode scanner at some arbitrary barcodes, and it > > beeped and turned off the red light, but nothing appeared on my > > screen as a result of the "od -x". > > > > Are there other possibilities to consider? > > At this point I'd start putting printk's and turning on DEBUGs in > the kernel source. For starters, If you get to the point of modifying the kernel source, can you be far from wanting an oscilloscope on the pins? -- Keith

April 1, 2007

Re: [Wlug] Seeking help with a USB barcode scanner

by Jamie Guinan

> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi Everybody, > > Jamie Guinan wrote: > > > >> See if "evdev" is loaded, then try reading the various > >> /dev/input/event* nodes. > > Yes, evdev is loaded and I see some /dev/input/event* nodes. The unique > ones for this device (that show up when I plug in the device) are event3 > and event4. Also, I see mouse1 and ts1. > > > > >> I have a USB keyboard here. Oh neat, under 2.6.19, they even give you > >> a path that matches the device ids, > > > >> # od -x /dev/input/by-id/usb-1241_1203-event-kbd > >> (tap tap tap...) > >> 0000000 92a9 460e 0000 0000 36dc 000b 0000 0000 > >> 0000020 0001 001c 0000 0000 92a9 460e 0000 0000 > >> 0000040 36e0 000b 0000 0000 0000 0000 0000 0000 > >> ... > > In /dev/input/by-id, I see: > usb-Cypress_Cypress_PS.2_Keyboard-event-{kbd,mouse} > usb-Cypress_Cypress_PS.2_Keyboard-mouse > > I tried your "od -x" trick on each of these to no avail. I pointed the > barcode scanner at some arbitrary barcodes, and it beeped and turned off > the red light, but nothing appeared on my screen as a result of the "od -x". > > Are there other possibilities to consider? At this point I'd start putting printk's and turning on DEBUGs in the kernel source. For starters, drivers/usb/input/hid-core.c:hid_input_report() drivers/usb/input/hid-input.c:hidinput_configure_usage() I typically do something like this, $ make $ make modules_install INSTALL_MOD_PATH=$(pwd)/tmp (don't go installing under /lib just yet) $ rmmod foo $ insmod ./tmp/..../foo.ko [ unplug, replug, dmesg, tail messages, rinse, repeat ] -Jamie

April 1, 2007