Recent changes to bugs

ezusb.c: possible missing call to fclose ?

2014-06-20T16:47:01.863000Z

[ezusb.c:609]: (error) Resource leak: image
[ezusb.c:817]: (error) Resource leak: image

$ egrep "fopen|fclose" ../BUILD/fxload-2008_10_13/ezusb.c
image = fopen (path, "r");
image = fopen (path, "r");
$

Maybe this code might benefit from some rework.

Mailing list application not working

2013-04-25T10:52:54.548000Z

Hi,

I followed the instructions to apply for the linux-hotplug mailing list,
got a confirmation message from Majordomo@vger.kernel.org saying
Welcome to the linux-hotplug mailing list!

Then I posted a keymap for a machine that isn't yet supported.

Over a week later, I have never received further postings from the mailing list, and my posting has never appeared in the archives, although other postings have since appeared in the archives.

I followed the instructions in the Welcome message, and wrote to
linux-hotplug-approval@vger.kernel.org
but after a week, never heard back.

Please either fix this, or explain to me what prevents my interaction with the list!

The user name was "swhite@...".

Thanks!

Links to subpages on the project www page do not work

2009-02-04T16:53:09Z

All links in the form "?selected=subpage" result in rendering the same page.

Firmware Upload Fails

2006-09-06T13:20:29Z

Sorry that I can't be more exact about the problem, but
here's what's happening.

With >=udev-096 (maybe 095, I never tried it), firmware
upload will work immediately after you (re)install udev
or when the firmware files change. After that, it
seems to be uploading the wrong data, the bcm43xx
driver reports:

Jun 17 12:22:42 powerbook bcm43xx: InitVals
(bcm43xx_initvalXX.fw) file-format error. Please fix
your bcm43xx firmware files.

I'm unsure as to where to look to find the problem, but
094 always works here, so the regression is after that.
If you have any ideas, I'd be happy to test so we can
get this fixed.

Handspring Visor Edge support

2006-05-06T21:24:20Z

I recently updated to Ubuntu Dapper Drake, dusted off
my old Handspring Visor Edge PDA, and attempted to sync
Evolution with the PDA. In doing so I discovered that
/etc/udev/rules.d/60-symlinks.rules is missing:

# Create /dev/pilot symlink for Handspring PDAs
KERNEL=="ttyUSB*", SYSFS{product}=="Handspring*", \ SYMLINK+="pilot"

From /var/log/messages:

May 6 14:23:27 localhost kernel: [4296452.876000] usb
4-2: new full speed USB d evice using uhci_hcd and
address 2
May 6 14:23:27 localhost kernel: [4296453.092000]
usbcore: registered new drive r usbserial
May 6 14:23:27 localhost kernel: [4296453.092000]
drivers/usb/serial/usb-serial .c: USB Serial support
registered for generic
May 6 14:23:27 localhost kernel: [4296453.092000]
usbcore: registered new drive r usbserial_generic
May 6 14:23:27 localhost kernel: [4296453.092000]
drivers/usb/serial/usb-serial .c: USB Serial Driver core
May 6 14:23:27 localhost kernel: [4296453.095000]
drivers/usb/serial/usb-serial .c: USB Serial support
registered for Handspring Visor / Palm OS
May 6 14:23:27 localhost kernel: [4296453.095000]
drivers/usb/serial/usb-serial .c: USB Serial support
registered for Sony Clie 3.5
May 6 14:23:27 localhost kernel: [4296453.096000]
drivers/usb/serial/usb-serial .c: USB Serial support
registered for Sony Clie 5.0
May 6 14:23:27 localhost kernel: [4296453.097000] usb
4-2: Handspring Visor / P alm OS: port 1, is for
Generic use
May 6 14:23:27 localhost kernel: [4296453.097000] usb
4-2: Handspring Visor / P alm OS: port 2, is for
HotSync use
May 6 14:23:27 localhost kernel: [4296453.097000] usb
4-2: Handspring Visor / P alm OS: Number of ports: 2
May 6 14:23:27 localhost kernel: [4296453.100000]
visor 4-2:1.0: Handspring Vis or / Palm OS converter
detected
May 6 14:23:27 localhost kernel: [4296453.100000] usb
4-2: Handspring Visor / P alm OS converter now attached
to ttyUSB0
May 6 14:23:27 localhost kernel: [4296453.101000] usb
4-2: Handspring Visor / P alm OS converter now attached
to ttyUSB1
May 6 14:23:27 localhost kernel: [4296453.101000]
usbcore: registered new drive r visor
May 6 14:23:27 localhost kernel: [4296453.101000]
drivers/usb/serial/visor.c: U SB HandSpring Visor /
Palm OS driver
May 6 14:23:34 localhost kernel: [4296460.170000] usb
4-2: USB disconnect, addr ess 2
May 6 14:23:34 localhost kernel: [4296460.170000]
visor ttyUSB0: Handspring Vis or / Palm OS converter
now disconnected from ttyUSB0
May 6 14:23:34 localhost kernel: [4296460.170000]
visor ttyUSB1: Handspring Vis or / Palm OS converter
now disconnected from ttyUSB1
May 6 14:23:34 localhost kernel: [4296460.170000]
visor 4-2:1.0: device disconn ected

coldpluging and wireless

2005-10-19T07:28:44Z

During boot of my laptop network configuration hangs
for minutes. I traced it to hotplug trying to bring up
the wireless connection.

My /etc/network/interfaces has the entry

auto lo eth1
...
mapping hotplug
script grep
map eth0

It seem wrong for hotplug to try and bring the "non
auto" eth0 during boot - in contradiction to the 'auto'
directive.

I am not sure if this is hotplug fault or not - but
perhaps someone can shed some light on the issue.

Netmod USB support

2005-08-17T11:29:49Z

Whenever I try to connect the Netmod device that acts
as an ISDN modem the acm driver is not loaded for the
device.
It should be "Driver=acm" but it is "Driver=(none)".

The device parameters in the firmware seem to be ok.

Please look below

(Taken from my system with the netmod connected in a
USB port)
(Kernel 2.6.8-2)
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4
Spd=12 MxCh= 0
D: Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS=16
#Cfgs= 1
P: Vendor=0bf1 ProdID=0001 Rev= 1.00
S: Manufacturer=Intracom S.A.
S: Product=NetMod USB
S: SerialNumber=Firmware Ver 1.0
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01
Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=10ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00
Driver=(none)
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

Below is the output I should have according to the manual.

(Taken from the netmod installation manual)
(Kernel 2.2.X)
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12
MxCh= 0
D: Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=0bf1 ProdID=0001 Rev= 1.00
S: Manufacturer=Intracom S.A.
S: Product=NetMod USB
S: SerialNumber=Firmware Ver 1.0
C:* #Ifs= 2 Cfg#= 1 Atr=60 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01
Driver=acm
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl= 10ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00
Driver=acm
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 10ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 10ms

The output from the command
usbmodules -d /proc/bus/usb/001/002
is
cdc-acm

while for

usbmodules -d /proc/bus/usb/001/001
and
usbmodules -d /proc/bus/usb/001/003
is
usbcore.

I have included the output from `cat
/proc/bus/usb/devices` for the specified device.

Further information on the device can be found in
http://netmod.intracom.gr/pdf/pdf_engl/usb_linux_22x_en.pdf

Kind regards,

Fafakos Panayiotis.

Hotplugs fail on Debian

2005-03-21T22:02:58Z

Occasionally hotplugs will fail on debian using the
2.6.x kernel. this could prevent the system from
booting.

Firewire controller problems

2005-01-29T15:06:50Z

The report from Florian Idelberger regarding Firewire
controller problems struck a chord - I was getting the
same problems myself, including the "wait_for_sysfs"
messages, intermittent connectivity, etc.
I use a Maxtor drive to move files between machines - I
never connect my development machine to the internet.
Anyway those connectors aren't the most sturdy and
after repeated use the metal shielding starts to deform
- on the plugs and on the sockets - four pin and six pin.
A small adjustment to the shielding with a pair of
pliers did the trick for me.
It's most apparent if you just try swapping the suspect
connectors and sockets - too lose or too tight a fit
could be a symptom of the problem. Visually there
shouldn't be any gaps, cracks or deformaties in the
shielding (plugs and sockets) apart from those present
as a result of manufacture.

Hope this helps

Philip A. Ashmore (philip_ashmore@hotmail.com)

Music Drive on kernel 2.6.8 and above

2005-01-04T23:02:15Z

Hi!!!

I'm using debian sarge and i have a MusicDrive mp3
player and i used it without problems with kernel 2.6.7
but since i move to kernel 2.6.8 and 2.6.9 i get I/O
errors from the pendrive :S

i read in the web that this is not problem from the
kernel but is a problem with the hotplug system, please
tell me if you can fix this problem, i think if the
MusicDrive device works fine with kernel 2.6.7 is
ridiculus that 2.6.8 and 2.6.9 can't work fine.

Thanks fot the hotplug system is very useful!!!

please reply me to koratsu@gmail.com

Thanks a lot again ;)