On Sun, 27 Nov 2011 03:07:38 -0600, Jonathan Nieder wrote: > Hi, > > Camaleón reports[1]: That's me. >> cards are recognized when insterted into the embedded reader but still >> seeing the weird message when booting. > [...] >> root@stt300:~# uname -a >> Linux stt300 3.2.0-rc3 #1 SMP Sat Nov 26 12:29:30 CET 2011 i686 >> GNU/Linux >> >> 01:00.1 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5288 (rev 01) >> Subsystem: Hewlett-Packard Company Device 148a (...) >> [ 355.088042] rts_pstor 0000:01:00.1: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. >> [ 370.892028] rts_pstor 0000:01:00.1: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. > > Known problem? Any ideas for tracking it down? > > More details at [1]. Thanks, it's great to see the progress of this > driver. > > Regards, > Jonathan > > [1] http://bugs.debian.org/637813 Mmm, still no replies :-) Okay, it seems now dmesg is less verbose and no more "vpd r/w failed...". Now I can only see: [ 6.795461] rts_pstor: module is from the staging directory, the quality is unknown, you have been warned. [ 6.799510] Initializing Realtek PCIE storage driver... [ 6.799594] rts_pstor 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 6.799740] Resource length: 0x10000 [ 6.799802] Original address: 0x93000000, remapped address: 0xf8500000 [ 6.799815] pci->irq = 17 [ 6.799822] rtsx_acquire_irq: chip->msi_en = 0, pci->irq = 17 [ 6.799894] rts_pstor 0000:01:00.1: setting latency timer to 64 [ 6.875690] iTCO_vendor_support: vendor-support=0 [ 6.996366] scsi4 : SCSI emulation for PCI-Express Mass Storage devices [ 6.996628] rts_pstor: waiting for device to settle before scanning [ 7.996164] rts_pstor: device scan complete [ 7.996461] scsi 4:0:0:0: Direct-Access Generic- xD/SD/M.S. 1.00 PQ: 0 ANSI: 0 CCS [ 7.996625] Bad LUN (0:1) [ 7.996937] Bad target number (1:0) [ 7.997233] Bad target number (2:0) [ 7.997527] Bad target number (3:0) [ 7.997817] Bad target number (4:0) [ 7.998106] Bad target number (5:0) [ 7.998398] Bad target number (6:0) [ 7.998689] Bad target number (7:0) Although messages look harmless I wonder if they can be safely ignored. Greetings, -- Camaleón _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
