RE: Bug#527265: Strange QLA1040 firmaware load error with 2.6.30 from testing
- To: <firstname.lastname@example.org>, "'Michael Cree'" <email@example.com>
- Cc: <firstname.lastname@example.org>
- Subject: RE: Bug#527265: Strange QLA1040 firmaware load error with 2.6.30 from testing
- From: "Uwe Schindler" <email@example.com>
- Date: Fri, 16 Oct 2009 11:20:40 +0200
- Message-id: <E26020FC0FB7464E8E867404951EF817@VEGA>
- In-reply-to: <BA36D4BEF0BE4D338B4AC6C628FBBAAB@VEGA>
- References: <DC98C5B952C5476EBEE912FAA42E078D@VEGA> <592743DC797B4CDF90A8584CFB53E5F2@VEGA> <4A90CFC8.firstname.lastname@example.org> <BA36D4BEF0BE4D338B4AC6C628FBBAAB@VEGA>
With the latest testing 2.6.30-2 kernel package, the error disappeared, the
firmware loads correctly.
> > >> Just one question: Is the firmware always needed or can I uninstall
> > >> qlogic-firmware package again? Does the controller has an eprom or
> > it
> > >> only works with driver-provided firmware? As the firmware does not
> > to
> > >> be loaded correctly, is it really needed?
> > >>
> > When I first tried the Debian 2.6.30 kernel the kernel locked up when
> > initialising the qlogic driver as I had completely forgotten about the
> > firmware. After installing qlogic-firmware driver it then booted fine.
> > Given I was running a kernel that included the firmware prior to running
> > the Debian kernel that is suggestive that the firmware is reloaded on
> > every boot.
> Which is strange, because the SRM console and its I/O functions used by
> aboot also use the SCSI controller to boot the kernel/initrd from my SCSI
> ZIP disk (the root partition is on a large SATA disk with a SIL controller
> initialized later from the initrd. Because of that, I think the system
> start without a firmware, but /boot and the CD-ROM mounts would be
> Maybe the firmware gets lost, when the PCI bus and the device is reset.
> This is why I asked.