|
|
 Up |
|
|
  |
Author: Frans PopFrans Pop Date: Jun 12, 2008 14:10
On Thursday 12 June 2008, Dennis Boone wrote:
> Comments/Problems:
> The installer boots fine, and allows me to set keyboard, country
> locale, but cannot detect the CD-ROM
> (/sbus@3,0/SUNW,fas@3,8800000/sd@6,0:f) drive to continue the
> installation.
> +SUNW,fas:FAS-336 ESP SCSI:esp_scsi:initrd
>
> POST/OBP outputs, and syslog are attached.
Thanks for all the info, but I'm afraid that my sparc knowledge is
insufficient here. Let's see if anyone on the debian-sparc list can help.
From the logs I can see that the esp_scsi module does get loaded, but it
does not seem to detect anything at all. Either something is missing
(basic scsi drivers?), or the hardware is just not supported by this
driver. I've googled around a bit but that did not help either.
We sometimes advise to netboot sparc systems where the CD is not
recognized, but that won't help if the harddisk is on the same
bus/controller and needs the same driver.
|
| Show full article (2.10Kb) |
|
| | 9 Comments |
|
|
Author: Gary W. SmithGary W. Smith Date: Jun 12, 2008 15:30
I don't know much about Sun hardware but Target 6 and Target e looks like your SCSI channels are off. Correct me if I'm wrong (which is highly probable here) but shouldn't the Target be either 0/1 for the primary boot device (i.e. the hard disk). I know the older adaptec controllers wouldn't load the bios for the raid controller of there wasn't a drive on 0/1 (but this was some time ago).
HTH,
Gary-
________________________________
From: Frans Pop [mailto:elendil@planet.nl]
Sent: Thu 6/12/2008 2:03 PM
To: 485961@ bugs.debian.org
Cc: drb@ msu.edu; debian-sparc@ lists.debian.org
Subject: Re: Bug#485961: installation-reports: Installer can't locate CD-ROM drive (sparc)
On Thursday 12 June 2008, Dennis Boone wrote: > Comments/Problems:
> The installer boots fine, and allows me to set keyboard, country
> locale, but cannot detect the CD-ROM
> (/sbus@3,0/SUNW,fas@3,8800000/sd@6,0:f) drive to continue the
> installation.
> +SUNW,fas:FAS-336 ESP SCSI:esp_scsi:initrd
>
> POST/OBP outputs, and syslog are attached.
|
| Show full article (5.58Kb) |
|
| | no comments |
|
|
Author: Dennis BooneDennis Boone Date: Jun 12, 2008 16:00
> Two things that may yet help:
> - the output of lsmod after hardware detection (to see if anything
> obvious is not loaded)
After modifying the hw-detect list and having the installer try to find a
CD-ROM, here's the lsmod:
~ # lsmod
Module Size Used by
ide_generic 1408 0 [permanent]
esp_scsi 26256 0
scsi_transport_spi 28288 1 esp_scsi
scsi_mod 173248 2 esp_scsi,scsi_transport_spi
sunhme 34224 0
> - just manually trying to modprobe any driver under
> /lib/modules/../kernel/drivers/scsi and checking dmesg after each for
> some sign of life
After the above, I tried modprobe of:
|
| Show full article (1.42Kb) |
| 2 Comments |
|
|
Author: Dennis BooneDennis Boone Date: Jun 15, 2008 09:10
> Hmm. There is also a sun_esp module, which depends on esp_scsi. I wonder
> if that's the missing link here.
> If you select (in expert mode) openssh-client-udeb as additional
> installer component to install, you can just scp the module from another
> machine.
I'll try this and see what happens. The catch would appear to be that
installer components live on the (as yet undetected) CD, so can't be
loaded to fetch the module.
I've built a modified netinst CD with the module added, which I will try
tomorrow when I'm in the same room with the e3500. Maybe I even built
it correctly. :)
De
|
| |
| 2 Comments |
|
|
Author: Mark Morgan LloydMark Morgan Lloyd Date: Jun 16, 2008 09:50
Frans Pop wrote:
> On Thursday 12 June 2008, Dennis Boone wrote:
>> Comments/Problems:
>> The installer boots fine, and allows me to set keyboard, country
>> locale, but cannot detect the CD-ROM
>> (/sbus@3,0/SUNW,fas@3,8800000/sd@6,0:f) drive to continue the
>> installation.
>> +SUNW,fas:FAS-336 ESP SCSI:esp_scsi:initrd
>>
>> POST/OBP outputs, and syslog are attached.
>
> Thanks for all the info, but I'm afraid that my sparc knowledge is
> insufficient here. Let's see if anyone on the debian-sparc list can help.
>
> From the logs I can see that the esp_scsi module does get loaded, but it
> does not seem to detect anything at all. Either something is missing
> (basic scsi drivers?), or the hardware is just not supported by this
> driver. I've googled around a bit but that did not help either.
>
> We sometimes advise to netboot sparc systems where the CD is not ...
|
| Show full article (4.31Kb) |
| no comments |
|
|
Author: Frans PopFrans Pop Date: Jun 17, 2008 05:30
reassign 485961 linux-kernel-di-sparc-2.6 1.24
tags 485961 pending
thanks
On Sunday 15 June 2008, Dennis Boone wrote:
>> Hmm. There is also a sun_esp module, which depends on esp_scsi. I
>> wonder if that's the missing link here.
>>
>
> I'll try this and see what happens. The catch would appear to be that
> installer components live on the (as yet undetected) CD, so can't be
> loaded to fetch the module.
>
> I've built a modified netinst CD with the module added, which I will
> try tomorrow when I'm in the same room with the e3500. Maybe I even
> built it correctly. :)
After looking at this again I'm fairly certain that this is the real
problem, so I've gone ahead and made the necessary changes. These changes
I made should become effective in daily built installer images as soon as
we switch over to the 2.6.25 kernel.
|
| Show full article (1.22Kb) |
| no comments |
|
|
Author: Dennis BooneDennis Boone Date: Jun 17, 2008 06:00
> After looking at this again I'm fairly certain that this is the real
> problem, so I've gone ahead and made the necessary changes. These
> changes I made should become effective in daily built installer images
> as soon as we switch over to the 2.6.25 kernel. > A confirmation that loading sun_esp does indeed work for you would still
> be very much appreciated of course.
Frans,
Yesterday I successfully booted from my modified netinst CD, manually
loaded the sun_esp and esp_scsi modules, and the installer could then
detect the CD-ROM drive. I could see that drive and the SCSI hard disk
in /proc/scsi/scsi.
As a possibly separate issue, I'm now having trouble getting the
installer to recognize the hard disk. There are several things I need
to try, including moving that drive to SCSI ID 0.
Do you know when the 2.6.25 switch will occur?
Thanks,
De
|
| Show full article (1.03Kb) |
| no comments |
|
|
Author: Frans PopFrans Pop Date: Jun 17, 2008 08:40
On Tuesday 17 June 2008, Dennis Boone wrote:
> Yesterday I successfully booted from my modified netinst CD, manually
> loaded the sun_esp and esp_scsi modules, and the installer could then
> detect the CD-ROM drive. I could see that drive and the SCSI hard disk
> in /proc/scsi/scsi.
Nice.
> As a possibly separate issue, I'm now having trouble getting the
> installer to recognize the hard disk. There are several things I need
> to try, including moving that drive to SCSI ID 0.
Check if it is visible in output of 'dmesg'. You should see the drive and
partitions listed. If it is, you should also see it in /sys/block and the
corresponding block device files in /dev/.
If you have all that, try following commands from an installer debug
shell: 'list-devices disk', 'list-devices partition'. If that lists the
disk and partitions, partman should recognize it too.
> Do you know when the 2.6.25 switch will occur?
Soon, for somewhat flexible values of "soon".
Try a few days after you get the mail that this report is closed.
|
| Show full article (1.19Kb) |
| no comments |
|
|
Author: Dennis BooneDennis Boone Date: Jun 17, 2008 12:00
> As a possibly separate issue, I'm now having trouble getting the
> installer to recognize the hard disk. There are several things I need
> to try, including moving that drive to SCSI ID 0.
False alarm: now that I can get that far, I can see that I seem to have
hard disk hardware problems.
>From my perspective, this issue is solved; I'll try to test a d-i daily
image when they become available.
Thanks all for your help!
De
|
| |
| no comments |
|
|
|
|
|
Author: Mark Morgan LloydMark Morgan Lloyd Date: Jun 25, 2008 04:50
Mark Morgan Lloyd wrote:
>
> Two questions that might possibly help. The first is that I suspect that
> the internal SCSI bus termination isn't particularly robust, I think
> that putting an external (68-pin, SE) terminator on the external SCSI
> connector improves reliability of hardware detection and subsequent
> driver load from initrd. So:
>
> * Is the kernel doing something which affects the electrical interface,
> e.g. glitching auto-termination state during initialisation?
>
> The second thing is that Splackware (Bobware 10.2) is much more reliable
> at detecting disc drives on the internal bus than Debian (Etch, 4.0).
> One particular failure mode I see with Debian and at least some disk
> types is that when it scans for the CD-ROM drive it does /something/
> which causes the hard disc to appear at multiple SCSI IDs including the
> one that the CD is at- which obviously screws things totally. So:
>
> * Is the installer doing something which affects the electrical ...
|
| Show full article (2.16Kb) |
| no comments |
|
RELATED THREADS |
|
|
|
|
