Samsung ML-2010 printer and kernel 2.6.22-1-686

[Benjamí Villoslada]

Samsung ML-2010 printer doesn't work with kernel 2.6.22-1-686 due to
CONFIG_USB_SUSPEND=y parameter. I've reported this
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435257

The printer works if I change /sys/module/usbcore/parameters/autosuspend file_

When system start:

# cat /sys/module/usbcore/parameters/autosuspend
2
# echo -n 60 > /sys/module/usbcore/parameters/autosuspend

And thhen printer works (I'm a bit confused, sometimes echo -n 0 worked too).

The question is how I can fix this parameter. I've tried
options usbcore autosuspend=60
in /etc/modpobe.d/options but seems that is ignored.

Thanks.

--
Benjamí
http://blog.bitassa.cat

.

[Ron Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Look at /etc/sysctl.conf to make that value persistent across boots.

- --
Ron Johnson, Jr.
Jefferson LA USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD4DBQFGv2m/S9HxQb37XmcRAlTRAJiO+UPJ4ma5XYQSAM2QGSYFuHIwAJ93l8MT
0JVJAd2e4OoAOKyPx/Evjg==
=/UsA
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Benjamí Villoslada]

El Diumenge 12 Agost 2007, Ron Johnson va escriure:

> Look at /etc/sysctl.conf to make that value persistent across boots.

Added usbcore.autosuspend=60 to etc/sysctl.conf:

- Error in boot log:

------------------------
Sun Aug 12 22:40:14 2007: Setting kernel
variables...error: "usbcore.autosuspend" is an unknown key
Sun Aug 12 22:40:14 2007: ^[[31mfailed.^[[39;49m
------------------------

Is the same error when I try to set usbcore.autosuspend=60
in /boot/grub/menu.lst

Seems that the parameter usbcore.autosuspend exists:

------------------------
# modinfo -p usbcore
autosuspend:default autosuspend delay
use_both_schemes:try the other device initialization scheme if the first one
fails
old_scheme_first:start with the old device initialization scheme
blinkenlights:true to cycle leds on hubs
usbfs_snoop:true to log all usbfs traffic
------------------------

And that is correct to write module.parameter=value

:?

Thanks :)

[Krzysztof Lubański]

On Sun, 2007-08-12 at 23:09 +0200, Benjamí Villoslada wrote:
> El Diumenge 12 Agost 2007, Ron Johnson va escriure:
> > Look at /etc/sysctl.conf to make that value persistent across boots.
>
> Added usbcore.autosuspend=60 to etc/sysctl.conf:
>
> - Error in boot log:
>
> ------------------------
> Sun Aug 12 22:40:14 2007: Setting kernel
> variables...error: "usbcore.autosuspend" is an unknown key
> Sun Aug 12 22:40:14 2007: ^[[31mfailed.^[[39;49m
> ------------------------

/etc/sysctl.conf manages only entries in /proc/sys, not /sys (sysfs).
Try installing 'sysfsutils' package and take a look at /etc/sysfs.conf
then.

--
Regards,
Krzysztof Lubanski

[Ron Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Argh, sorry. I knew something looked odd about /etc/sysctl.conf.

- --
Ron Johnson, Jr.
Jefferson LA USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGv55zS9HxQb37XmcRAgUkAKCevrMKpkOJOqs9ZM+oCWz9vv7RkgCgzciE
EYDe+lkaUScAlARNSGucPak=
=/lDf

[Benjamí Villoslada]

El Dilluns 13 Agost 2007, Krzysztof Lubański va escriure:

> /etc/sysctl.conf manages only entries in /proc/sys, not /sys (sysfs).
> Try installing 'sysfsutils' package and take a look at /etc/sysfs.conf
> then.

Solved!

I've added:

module/usbcore/parameters/autosuspend = -1

to /etc/sysfs.conf

Thanks, Krzysztof and Ron!

Regards,