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

Bug#249649: marked as done (Debian installer: Installer don't detect my IBM ServeRAID 3L SCSI controller)

Your message dated Wed, 08 Sep 2010 03:58:37 +0000
with message-id <E1OtBnx-000609-To@ravel.debian.org>
and subject line Closing old installation report #249649
has caused the Debian Bug report #249649,
regarding Debian installer: Installer don't detect my IBM ServeRAID 3L SCSI controller
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
249649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=249649
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: Debian installer
Severity: normal


I have a IBM ServeRAID 3L SCSI controller, with 2 scsi disk
I use it on my desktop at home

I have install Debian Sarge by 2 floppy, with network as source
The hardware auto-detect don't found my controller
At the time to part the disks, the controller is hidden, but
if i go on alt-f2 console and do 'insmod ips' and
return to the partiotion disk stage, the installer see
the controller, and it allow me to work on scsi disks

the 'insmod ips' solve the problem, that it!


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-k7
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro

# lspci -v
[...]
0000:00:0d.0 SCSI storage controller: IBM SCSI RAID Adapter [ServeRAID] (rev 0d)
        Subsystem: IBM ServeRAID-3x
        Flags: bus master, medium devsel, latency 32, IRQ 9
        I/O ports at b000 [size=256]
        Memory at d3000000 (32-bit, non-prefetchable) [size=1M]
        Expansion ROM at <unassigned> [disabled] [size=32K]
        Capabilities: [40] Vital Product Data
[...]

# dmesg
[...]
May 17 12:18:25 area51 kernel: SCSI subsystem driver Revision: 1.00
May 17 12:18:25 area51 kernel: PCI: Found IRQ 9 for device 00:0d.0
May 17 12:18:25 area51 kernel: PCI: Sharing IRQ 9 with 00:05.0
May 17 12:18:25 area51 kernel: scsi0 : IBM PCI ServeRAID 6.11.07  Build 2224 <ServeRAID 3L>
May 17 12:18:25 area51 kernel: blk: queue c1934194, I/O limit 4095Mb (mask 0xffffffff)
May 17 12:18:25 area51 kernel: Vendor: IBM       Model: SERVERAID Rev: 1.00
May 17 12:18:25 area51 kernel: Type:   Direct-Access ANSI SCSI revision: 02
May 17 12:18:25 area51 kernel: blk: queue c1934294, I/O limit 4095Mb (mask 0xffffffff)
May 17 12:18:25 area51 kernel: Vendor: IBM       Model: SERVERAID Rev: 1.00
May 17 12:18:25 area51 kernel: Type:   Direct-Access ANSI SCSI revision: 02
May 17 12:18:25 area51 kernel: blk: queue c1934394, I/O limit 4095Mb (mask 0xffffffff)
May 17 12:18:25 area51 kernel: Vendor: IBM       Model: SERVERAID Rev: 1.00
May 17 12:18:25 area51 kernel: Type:   Processor ANSI SCSI revision: 02
May 17 12:18:25 area51 kernel: blk: queue c1934494, I/O limit 4095Mb (mask 0xffffffff)
May 17 12:18:25 area51 kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
May 17 12:18:25 area51 kernel: Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
May 17 12:18:25 area51 kernel: SCSI device sda: 35565568 512-byte hdwr sectors (18210 MB)
May 17 12:18:25 area51 kernel: Partition check:
May 17 12:18:25 area51 kernel: /dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 >
May 17 12:18:25 area51 kernel: SCSI device sdb: 35565568 512-byte hdwr sectors (18210 MB)
May 17 12:18:25 area51 kernel: /dev/scsi/host0/bus0/target1/lun0: p1
May 17 12:18:25 area51 kernel: Journalled Block Device driver loaded
[...]

do you need other info ?

bye

--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: