Re: Bug#306476: quick question about Bug#306476
On Monday 27 February 2006 04:21, Randall Wayth wrote: To get to this point, I had also tried the latest etch cd installer which uses a 2.6 kernel. This installer failed at other points (I had to modprobe esp and it couldn't mount the disk after partitioning, and something else too...) but what was useful was that it told me that the module for the scsi controller was called esp. Since this is an sbus system, not pci, there doesn't appear to be an equivalent of lspci which would have solved my problem immediately. (If there is such a thing, please let me know.) There is actually. Recent sparc images include 'prtconf' and use that to detect sbus devices. So all's well that ends well. If you think that the failure to load the correct scsi driver modules during the detect cdrom phase is a bug, then I'll be happy to submit one. No need to open a new bug, just keep following up to this one. Could you please try an install using the latest daily image [1], which is the candidate for the installer's Beta2 release. See if the CDROM is detected and the esp driver is loaded automatically. If it does not work, could you send us the output of prtconf? You can also try to add a line 'set -x' in /bin/discover-sbus before hardware detection [2]. That should give you debugging output in /var/log/syslog that shows what's happening. You can stop before partitioning, so no need to overwrite your exiting installation for this test. TIA, Frans Pop [1]http://cdimage.debian.org/cdimage/daily-builds/etch_d-i/arch-latest/sparc/iso-cd/ [2] Boot the installer with 'install debconf/priority=medium' and, before the step to detect cdrom hardware, switch to VT2 and edit that script using nano. pgpVembFEVKBG.pgp Description: PGP signature
Re: Bug#306476: quick question about Bug#306476
Hi Jim and Frans, Thanks very much for the follow-up and suggestions. For the sake of creating a useful record I'll let you know what happened here. I ended up getting this working using the standard sarge minimal-cd net installer, which was the thing that failed in the first place. To get it working, after the detect and mount cdrom phase failed, I went into a shell and did modprobe esp. This then starts the in-built scsi card and detects the cdrom and hard disk. I then exited the shell, tried the detect cdrom step again, and the rest of the install proceeded normally. (I also needed to know that the network controller was a Happy Meal card). To get to this point, I had also tried the latest etch cd installer which uses a 2.6 kernel. This installer failed at other points (I had to modprobe esp and it couldn't mount the disk after partitioning, and something else too...) but what was useful was that it told me that the module for the scsi controller was called esp. Since this is an sbus system, not pci, there doesn't appear to be an equivalent of lspci which would have solved my problem immediately. (If there is such a thing, please let me know.) So all's well that ends well. If you think that the failure to load the correct scsi driver modules during the detect cdrom phase is a bug, then I'll be happy to submit one. Cheers, Randall. P.S I did all this using the serial terminal on the back of the box since it has no graphics card. That works fine when connected to a terminal with minicom (in this case an Ultra10 running linux), but you must turn off all flow control. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#306476: quick question about Bug#306476
On Friday 24 February 2006 03:52, Randall Wayth wrote: Thanks for this info. I actually tried the latest etch cd yesterday but it failed also (to mount the CD) even though it seems to explicity handle SCSI cdrom devices. (At least one gets that impression from the messages that come up that it does.) So I wonder now exactly what the problem is? I have no experience with SCSI CD-ROM drives. The daily builds of the installer have lspci. The output of that may help to determine what type of controller you have (and thus what driver you need). For the rest, trying things manually from VT2 is a good idea as it will show you any error messages better then when commands are run within the installer. SunBlade 100 systems are notorious though. I tried installing one at a developers meeting recently and ran into the weirdest problems which were not even consistently reproducible. I did succeed in installing from CD some times, but at other times had errors halfway through the installation. The only really successful installation reports we've had, have been with netboot installs. It seems to me there is a serious kernel or driver bug somewhere that someone who has both the hardware and skills needs to trace... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#306476: quick question about Bug#306476
On Fri, Feb 24, 2006 at 12:18:59PM +0100, Frans Pop wrote: SunBlade 100 systems are notorious though. I tried installing one at a developers meeting recently and ran into the weirdest problems which were not even consistently reproducible. I did succeed in installing from CD some times, but at other times had errors halfway through the installation. The only really successful installation reports we've had, have been with netboot installs. I remember when I bought my sunblade 100 there were 2 type of solaris boot disks in the package, one special was for the sunblade 100, the other would fail half-way through. Anyway the cdrom stopped working when it was just after warranty, and since then it has installed debian by net boot several times with no problems. jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
