On Sat, Feb 19, 2011 at 11:06:04PM +0000, Jurij Smakov wrote: > On Thu, Feb 10, 2011 at 10:49:39AM +0000, Richard Mortimer wrote: > > [Cc'd to 611...@bugs.debian.org] > > > > On 10/02/2011 08:36, Jurij Smakov wrote: > > >On Wed, Feb 09, 2011 at 11:07:49PM +0000, Richard Mortimer wrote: > > >>On 09/02/2011 21:43, Jurij Smakov wrote: > > ... snip ... > > >>> > > >>>http://www.wooyd.org/debian/squeeze/ > > >>> > > ... > > > > > >Sure, I have just uploaded a netboot image to the same location. > > > > > >>>If you have encountered problems during Squeeze installation, please > > >>>test this image and report the results, as a positive confirmation of > > >>>fixes on a variety of different systems is essential for getting all > > >>>these fixes into the first Squeeze point release. > > >>> > > >>I did spot a couple of issues with the installer when I gave squeeze > > >>a try a couple of weeks back. I only got chance to file an > > >>installation report about one of them > > >>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611314 > > >>Its not a massive show stopper and has an easy workaround but if > > >>that can be fixed then it will make others lives easier. > > > > > >Yeah, this bug was pointed out to me just yesterday. I don't know > > >what's going on there yet, it appears that the PCI IDs of your > > >card match the ones which are supported by the driver, so if module is > > >not loaded at all there is probably something wrong with udev. At a > > >point where it says it cannot detect the disks, can you drop back to > > >shell and see whether the driver actually isn't loaded (as opposed to > > >being loaded but failing to find the disks anyway)? Maybe there is > > >something relevant showing up in dmesg or /var/log/messages? > > > > > >If not, I'll try to come up with some udev debugging commands to try > > >and understand why this detection is failing. > > > > I tested with your netboot image and it exhibits the same behaviour > > as the official installer. The sym53c8xx driver does get loaded > > automatically. I'm pretty sure that this is a timing issue. I > > confirmed that all of the /dev/sd* files were present along with > > /dev/disk/* entries. > > Ok, I think the magic happens in the disk_found() function in > disk-detect.sh [0]. It looks like it will retry up to 3 times to see > whether devices have showed up (with list-devices disk), sleeping 2 > seconds between attempts... If it takes up to 7 seconds for driver to > initialize itself, we might be cutting it just a bit too short. > Unfortunately, I don't see how we can test it easily, as neither > netboot image nor miniiso contain the udebs, they are downloaded off > the network.
Hm, if expert install mode offers an opportunity to drop to shell after udebs are downloaded, then we can probably replace the udeb containing disk-detect.sh with a modified one. Can you check whether it's possible? -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
