Hi, I have a PHILIPS CD-RW/DVD-ROM SCB5265 and I have problems reading of some DVDs. I found two different firmware updates which contains .exe files: TD17 (5/1/2007): http://ftp.us.dell.com/rmsd/PHILIPS-SCB5265-TD17.zip TD19 (12/13/2005): http://ftp.us.dell.com/rmsd/SCB5265_fwTD19.zip If I set up the IDE SCSI emulation, the firmware updater can recognize my CD-RW/DVD-ROM drive. # rmmod ide-cd # modprobe -k ide-scsi The dmesg now contains the following lines: SCSI subsystem initialized ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device scsi0 : SCSI host adapter emulation for IDE ATAPI devices scsi 0:0:0:0: CD-ROM PHILIPS CDRW/DVD SCB5265 TX01 PQ: 0 ANSI: 0 sr0: scsi-1 drive sr 0:0:0:0: Attached scsi CD-ROM sr0 sr 0:0:0:0: Attached scsi generic sg0 type 5 However, while the firmware updater starts and recognizes the drive prints some error messages: $ wine --version wine-0.9.47 $ wine PHILIPS-SCB5265-TD19.EXE fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for adapter 0. fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for adapter 1. fixme:aspi:SendASPI32Command ASPI: Partially implemented SC_HA_INQUIRY for adapter 2. err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 1\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 2\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 3\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 4\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 5\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 6\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 7\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 1\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 2\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 3\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 4\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 5\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 6\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 7\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 1\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 2\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 3\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 4\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 5\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 6\Logical Unit Id 0 err:aspi:SCSI_GetDeviceName Could not open HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 7\Logical Unit Id 0 My question is that how complete is the ASPI implementation in wine? May the firmware update work under wine, or we are far from this state? Thanks, M?rton N?meth
On Saturday October 27 2007 05:30, N?meth M?rton wrote:> My question is that how complete is the ASPI implementation in wine? > May the firmware update work under wine, or we are far from this state?Direct hardware access doesn't work on WINE. For example, you cannot record CD or DVD using Windows software under WINE. However, you can record CD or DVD using VMWare (it has free trial for 30 days - more than enough to update firmware). VirtualBox or QEmu (both are free) maybe will work too but I never tested them for that purpose. Actually, I never used VMWare for updating firmware in SCSI/IDE/SATA device but I think this should work too - probably as good as CD/DVD writing. Anyway, there is no harm to try this. You can download VMWare at http://vmware.com . Use of sophisticated virtual machines is the only way in your case. Another alternative is to use DOS executables for update (many vendors have them as an alternative) with FreeDOS but this will require reboot; and this is only way if you havn't a copy of Windows CD/DVD (it is needed for virtual machine).
L. Rahyen wrote:> Direct hardware access doesn't work on WINE.An ASPI Call isn't "Direct hardware access". "Direct hardware access" works under wine if you are root and if you allow the accessed hardware ports in wine. However since Win95 no programm uses direct hardware access. The programs use drivers, and you can't run these drivers in wine.> For example, you cannot record CD or DVD > using Windows software under WINE.You can. Whether wine's ASPI is suitable for a firmware update, you will not know until you try. This may leave you with a bricked firmware, if things go wrong. Bye -- Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
(Don't forget to answer to the list so others can see the discussion.) On Saturday October 27 2007 22:31, Anurag Mishra wrote:> On 10/27/07, L. Rahyen <research at science.su> wrote: > > Last time I tried was about a year ago and it doesn't worked with > > few different programs for CD/DVD recording. Unfortunately I'm not aware > > of any improvements in this area so I didn't try since. Can you give an > > example of Windows program which can burn CD/DVD on WINE? Thanks. > > > Infra Recorder. (Recent entry in AppDB. I haven't tested) > > http://appdb.winehq.org/objectManager.php?sClass=version&iId=9503Thanks.
On Saturday October 27 2007 05:30, N?meth M?rton wrote:> I have a PHILIPS CD-RW/DVD-ROM SCB5265 and I have problems reading of some > DVDs. I found two different firmware updates which contains .exe files:I have problems reading of some DVDs too for a long time so I decided to try to update firmware on my ASUS DRW-1608P using Windows update utility on Linux. My model is completely different but see below how I did it - it may help you too.> My question is that how complete is the ASPI implementation in wine? > May the firmware update work under wine, or we are far from this state?After some investigation I can say that WINE has pretty good ASPI implementation. And it is possible to update firmware using it but you need to run the utility as root and it may take long time (at least in my case and I don't think that this is WINE or Linux fault).> $ wine --version > wine-0.9.47 > $ wine PHILIPS-SCB5265-TD19.EXEAs I have said try to run as root instead. Does this work for you? In my case when I ran update utility as root (if I try to run it as simple user it simply fails with strange error), it took about 10-15 minutes for progress bar to appear. Then it took a lot of time to transfer the firmware (maybe 30-40 minutes). But at the end update was successful! So this works with WINE perfectly at least for me. I also have tested VMWare with Windows XP x64. But Windows never worked with DMA correctly for me (in fact many years ago my brother have used Windows on my computer before he finally switched to Linux and DMA never worked in Windows even on real hardware so disk/cd access was terribly slow) and without it utility for firmware update doesn't work of course (at least according to VMWare warning that DMA should be enabled in the guest). Have no idea why Windows don't want to use DMA for DVD drive by default and how this can be fixed or how I can enable it (maybe it is possible to install additional updates or tweak something in registry, I'm not sure; anyway, this isn't an issue for me because my everyday use of VMWare is limited for running professional Autodesk products like 3ds max and AutoCAD and that's all). I havn't tested 32-bit Windows XP in VMWare. Anyway, WINE with Linux (which has perfect support for DMA) works with no problem. It is really great to see that it is possible to update firmware in my DVD drive using WIndows update utility on Linux with WINE! Useful note: you can use hdparm -I /dev/hda (where /dev/hda is the device file for your DVD drive) to see what version of firmware you have.