Bug#283452: No SCSI module support in Debian Installer RC2
reassign 283452 hw-detect retitle 283452 needs a way in expect mode to prompt user to make sure all hardware and modules they want are found and loaded Jack Carroll wrote: > Still running an install as I'm writing this, but I'll give you a > quick summary now. > Turns out that the SCSI modules download during "Loading components > of Debian Installer" and appear in the modules tree, but the entire > .../kernel/drivers/SCSI directory gets deleted during "Detect hardware" or > during the partitioner. Not sure which it was. > > On the next run, I skipped "Free memory (low memory install)" at the > main menu, and went on to "Detecting disks & all other hardware". This > didn't load the aha1542 module, but it didn't delete the SCSI drivers > directory either. > At this point I was able to command > modprobe aha1542 > and get it to load. Then I started the partitioner, and the two SCSI disks > showed up. I created Reiser file systems in their existing partitions and > assigned mount points. > "Install the base system" appeared on the screen, and started up > when I hit . It's still running, and I have to get to bed. > > > So... > The fatal bugs in the partitioner that stopped me on this hardware > as late as RC1 are cleared up now. This is major progress in getting Sarge > to install on old hardware. What's left is some missing pieces in the main > line logic of the installer, which would stop a newbie, but an experienced > user with the right clues (your message above) can work around the problems. > > I'll try to file a more detailed follow-on report to the bug > reporting system thread later in the week. It removes the scsi and other drivers once the partitioner starts up, on systems with low memory, to save memory. So you are able to load the module only before that, as you did above. Probably the code that does this should not run until after the code that checks to see if a hard drive was detected. However, this change would not help you since you have an IDE drive that was detected. > 2. RC2 still doesn't deal gracefully with devices that aren't > auto-detected. It saw my Tulip card and loaded the module, but didn't > detect either of the NE-2000 cards. The ne.o driver was present in the > kernel driver tree, and I was able to load it with a modprobe command. > There needs to be a place, either in the main menu, or after the > program lists the hardware that was detected, where it asks the user > whether there is any additional hardware that wasn't detected. If the > answer is yes, it should list the available drivers for that class of > device, and allow the user to select additional drivers to be loaded. > That's the way it used to be done. Old hardware needs that level of manual > control. Indeed this problem applies not only to ethernet devices but to hard drives. Since I hope to add an explicit hard drive detection step to hw-detect post-sarge, I'll reassign this bug to that package. hw-detect needs to have some way, in expert mode, of listing the detected hardware and prompting the user to see if they want to load any other modules. -- see she jo signature.asc Description: Digital signature
Processed: Re: Bug#283452: No SCSI module support in Debian Installer RC2
Processing commands for [EMAIL PROTECTED]: > reassign 283452 hw-detect Bug#283452: No SCSI module support in Debian Installer RC2 Bug reassigned from package `installation-reports' to `hw-detect'. > retitle 283452 needs a way in expect mode to prompt user to make sure all > hardware and modules they want are found and loaded Bug#283452: No SCSI module support in Debian Installer RC2 Changed Bug title. > Jack Carroll wrote: Unknown command or malformed arguments to command. > > Still running an install as I'm writing this, but I'll give you a Unknown command or malformed arguments to command. > > quick summary now. Unknown command or malformed arguments to command. > > Turns out that the SCSI modules download during "Loading components Unknown command or malformed arguments to command. > > of Debian Installer" and appear in the modules tree, but the entire Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283452: No SCSI module support in Debian Installer RC2
Jack Carroll wrote: > 1.The situation with SCSI modules has deteriorated since RC1. This > time I was unable to bring any SCSI drivers into > /lib/modules/2.4.27-1-386/kernel/drivers from the net-drivers floppy, the > cd-drivers floppy, or the Debian mirror. Why not? These modules are availale on the debian mirror and will be downloaded before the installer needs to access a scsi drive. If that didn't happen, you must be doing something wrong, or using a broken mirror; it works for me. -- see shy jo signature.asc Description: Digital signature
Bug#283452: No SCSI module support in Debian Installer RC2
Package: installation-reports Debian-installer-version: RC2, 20041118 floppy image set uname -a: N/A Date: 11/28/2004 2100 EST Method: How did you install? Network. What did you boot off? Floppy If network install, from where? ftp://debian.uchicago.edu Proxied? No. Connected through masquerading hardware firewall box. Machine: Compaq Deskpro Processor: Pentium 1 133 MHz Memory: 32 MB Root Device: SCSI? Yes. Name of device? /dev/sda3 Root Size/partition table: Unable to access drives in this attempt Output of lspci: :00:00.0 Host bridge: Intel Corp. 430HX - 82439HX TXC [Triton II] (rev 01) :00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 11) :00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01) :00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] :00:0f.0 VGA compatible controller: Cirrus Logic GD 5436 [Alpine] Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [E] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: 1. The situation with SCSI modules has deteriorated since RC1. This time I was unable to bring any SCSI drivers into /lib/modules/2.4.27-1-386/kernel/drivers from the net-drivers floppy, the cd-drivers floppy, or the Debian mirror. As a result, I couldn't even manually load the aha1542 driver with a modprobe command this time. That made it impossible to access any of my hard disks or my CD-ROM drive. The partitioner listed only the IDE device. 2. RC2 still doesn't deal gracefully with devices that aren't auto-detected. It saw my Tulip card and loaded the module, but didn't detect either of the NE-2000 cards. The ne.o driver was present in the kernel driver tree, and I was able to load it with a modprobe command. I was able to use that driver to load driver components from the mirror; except that no SCSI modules were included in the download, or in the list of installer components to select for downloading. There needs to be a place, either in the main menu, or after the program lists the hardware that was detected, where it asks the user whether there is any additional hardware that wasn't detected. If the answer is yes, it should list the available drivers for that class of device, and allow the user to select additional drivers to be loaded. That's the way it used to be done. Old hardware needs that level of manual control. Once the basic functionality is provided to make the names of the available driver modules visible to the user for manual loading, it would be desirable to add some help information to list the product names of hardware devices alongside their driver modules. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
