[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#256113: problem with mkinitrd on AMD64, 2.6.7



On Mon, 2004-08-09 at 14:44 +0100, Martin Michlmayr wrote:
> * tbm <tbm@cyrius.com> [2004-08-04 17:41]:
> > * Harald Dunkel <harald.dunkel@t-online.de> [2004-08-02 09:05]:
> > > The problem is that sometimes /proc/scsi does not contain the module
> > > name for my swap device. 'sata_sil' does not appear in /proc/scsi. I
> > > don't know why its not there, but this is not important. Without
> > > sata_sil in loadmodules my PC won't boot.
> > 
> > This sounds like a bug Andres Salomon reported recently.  Andres and
> > Harald, can you please show what your /proc/scsi contains?


dilinger@toaster:~$ ls -l  /proc/scsi/
total 0
-r--r--r--  1 root root 0 2004-08-09 10:36 device_info
dr-xr-xr-x  2 root root 0 2004-08-09 10:36 sata_sis
-r--r--r--  1 root root 0 2004-08-09 10:36 scsi
dr-xr-xr-x  2 root root 0 2004-08-09 10:36 sg
dilinger@toaster:~$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST380013AS       Rev: 3.18
  Type:   Direct-Access                    ANSI SCSI revision: 05
dilinger@toaster:~$ for f in /proc/scsi/sata_sis/*; do echo $f; cat $f;
done
/proc/scsi/sata_sis/0
The driver does not yet support the proc-fs

/proc/scsi/sata_sis/1
The driver does not yet support the proc-fs

dilinger@toaster:~$ for f in /proc/scsi/sg/*; do echo $f; cat $f; done
/proc/scsi/sg/allow_dio
0
/proc/scsi/sg/debug
dev_max(currently)=32 max_active_device=1 (origin 1)
 def_reserved_size=32768
/proc/scsi/sg/def_reserved_size
32768
/proc/scsi/sg/device_hdr
host    chan    id      lun     type    opens   qdepth  busy    online
/proc/scsi/sg/devices
0       0       0       0       0       1       1       0       1
/proc/scsi/sg/device_strs
ATA             ST380013AS              3.18
/proc/scsi/sg/version
30531   3.5.31 [20040513]


-- 
Andres Salomon <dilinger@voxel.net>

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: