Missing kernel module sg.ko

[Mark Kahrs]

60 -rw-r--r-- 1 root root 55184 2009-04-01 18:47 /lib/modules/2.6.27-11-generic/kernel/drivers/scsi/sg.ko

ls: cannot access /lib/modules/2.6.28-11-generic/kernel/drivers/scsi/sg.ko: No such file or directory

Without this module, no SCSI scanners are operable.

ProblemType: Bug
Architecture: i386
CurrentDmesg: [ 91.396041] eth0: no IPv6 routers present
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=35efb560-08c2-43c5-b666-12c628c0a81b
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=41ceb349-7c8b-46cd-ade6-d0954cd67fe4 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux

[Mark Kahrs (mark-kahrs)]

OK, know this: the sg.c file is still in the latest kernel distribution. If I compile it and load it (I get one warning) then it complains about a bad parameter (and won't load).

Is this why it wasn't distributed?

[MiniMaxR (ubuntu-maximini-world)]

Same problem here, no sg.ko in 2.6.28-11.42-generic thus my scanner is not working. :-(

[Claus007 (claus-ilginnis-deactivatedaccount)]

same here trying to compile kernel on my own
linux-2.6.29.4

this module is only missing in the 64Bits environment !
and only since jaunty

[Leann Ogasawara (leannogasawara)]

The sg driver is built into the kernel, not as a module:

ogasawara@emiko:~/ubuntu-jaunty/debian/config$ grep -rn "CONFIG_CHR_DEV_SG" *
amd64/config:394:CONFIG_CHR_DEV_SG=y
i386/config:416:CONFIG_CHR_DEV_SG=y

Are there any error messages in your dmesg output or syslog after you attempt to use the scanner?

[Mark Kahrs (mark-kahrs)]

Yes, this is true. However, why...

1). Wasn't sg.c removed from /usr/src/linux/drivers/scsi?

2). Wasn't this announced in the changes in Jaunty? All of us who use
SCSI based scanners were used to using modprobe to insert sg.ko.
And now all of a sudden, it changed without any notification. Or did
I miss that?

n.b. It is still necessary to write to /proc/scsi/scsi but you have
to do that anyway.

On Mon, Jun 15, 2009 at 7:00 PM, Leann
Ogasawara<email address hidden> wrote:
> The sg driver is built into the kernel, not as a module:
>
> ogasawara@emiko:~/ubuntu-jaunty/debian/config$ grep -rn "CONFIG_CHR_DEV_SG" *
> amd64/config:394:CONFIG_CHR_DEV_SG=y
> i386/config:416:CONFIG_CHR_DEV_SG=y
>
> Are there any error messages in your dmesg output or syslog after you
> attempt to use the scanner?
>
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Incomplete
>
> --
> Missing kernel module sg.ko
> https://bugs.launchpad.net/bugs/365791
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Incomplete
>
> Bug description:
> 60 -rw-r--r-- 1 root root 55184 2009-04-01 18:47 /lib/modules/2.6.27-11-generic/kernel/drivers/scsi/sg.ko
>
> ls: cannot access /lib/modules/2.6.28-11-generic/kernel/drivers/scsi/sg.ko: No such file or directory
>
> Without this module, no SCSI scanners are operable.
>
> ProblemType: Bug
> Architecture: i386
> CurrentDmesg: [   91.396041] eth0: no IPv6 routers present
> DistroRelease: Ubuntu 9.04
> HibernationDevice: RESUME=UUID=35efb560-08c2-43c5-b666-12c628c0a81b
> Lsusb:
>  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: System Manufacturer System Name
> Package: linux-image-2.6.28-11-generic 2.6.28-11.42
> ProcCmdLine: root=UUID=41ceb349-7c8b-46cd-ade6-d0954cd67fe4 ro quiet splash
> ProcEnviron:
>  PATH=(custom, user)
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
> SourcePackage: linux
>

[MiniMaxR (ubuntu-maximini-world)]

You are right, the sg module is compiled into the kernel and is used for my scanner. Strange, i could bet that this wasn't the case some days before. However, my scanner can now be accessed as device /dev/sg3. But only as rood because the group is set to root instead of scanner:
$ ls -al /dev/sg3
crw-rw---- 1 root root 21, 3 2009-06-21 18:57 /dev/sg3

In /lib/udev/rules.d/70-acl.rules I have found the rule
KERNEL=="sg[0-9]*", ATTRS{type}=="3", ATTRS{vendor}=="HP|EPSON|Epson", ENV{ACL_SCANNER}="1"
which should match, type and vendor are correct. But I am not familiar with udev and how the environment variable ACL_SCANNER is used or can be configured. Any hints?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]