On Mon, 17 Jan 2005 21:39:34 +0100, Alexandr Malusek wrote:

Sunny writes:

...

...

Does dvd+rw-mediainfo (SUSE 9.2, dvd+rw-tools-5.21.4.10.8-2) provide reliable information? In my case, it reports:

$ dvd+rw-mediainfo /dev/dvd INQUIRY: [PLEXTOR ][DVDR PX-712A ][1.05] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R Media ID: YUDEN000/T01 Current Write Speed: 8.0x1385=11080KB/s Write Speed #0: 8.0x1385=11080KB/s Write Speed #1: 6.0x1385=8310KB/s Write Speed #2: 4.0x1385=5540KB/s Write Speed #3: 2.4x1385=3324KB/s ...

Yes, the media advertises itself as 8x. But it may be defective. Or the drive may not write properly at this speed. The short answer is - most probably bad media.

Now I see it's a bit more complicated. The label clearly states 1-4x speed (an image is at http://www.maxell.eu.com/, unfortunately there is no direct link to the web page) but the Maxell's compatibility list states that Plextor PX-708A can use 8x speed. New DVD drives, namely my Plextor PX-712A, is not listed there. The Plextor's web page http://www.plextor.be/technicalservices/technology/recmedia.asp?choice=Suppo... states that Maxell's DVD+R(4X) can be written at the 8x speed. So the information provided by dvd+rw-mediainfo was correct. I'll try to burn one more DVD+R at the 8x speed.

Anyway, I'm puzzled where the 8x speed comes from. Is it stored on the disc or does the firmware provide the speed? It guess the latter is true since some drives can only use the 4x speed.

-- A.M.

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

It seems it comes from the firmware. At least I remember reading something like this on growisofs site, regarding some speed change problems they had with plextor drives and bad media database. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85

Ros Hills wrote:

Hi All, I hope someone can help me because I don't seem able to find anything in the archives.

I have just moved from 56k modem to a USB Speedtouch 330 ADSL modem (silver model) and upgraded to Suse 9.2 Pro. The modem works fine in Win2000 on the same machine.

I followed the instructions at: http://linux-usb.sourceforge.net/SpeedTouch/suse-9.1-pers.html

and all seemed to work perfectly until I attempted to activate it with the commands below (as root)...

linux:/home/ros # modem_run -k -f /etc/ppp/KQD6_3.012 linux:/home/ros # pppd call speedtch Plugin pppoatm.so loaded. PPPoATM plugin_init PPPoATM setdevname - remove unwanted options PPPoATM setdevname_pppoatm - SUCCESS:0.38 connect(0.38): Resource temporarily unavailable

My guess is that you've got modem_run working OK, but maybe the drivers are wrong: I used files ZZZLP1.eni and ZZZLP2.eni. The way I got it to work was to use the speedtouch 1.3 driver from http://speedtouch.sourceforge.net/index.php?/download.en.html combined with the kernel module, which is included in SuSE 9.1. speedtouch-1.3: Download speedtouch-1.3.tar.bz2 from http://speedtouch.sourceforge.net/index.php?/download.en.html to a directory (say ~/src). Open a Konsole (or xterm or similar) $ cd ~/src $ tar jxvf speedtouch-1.3.tar.bz2 $ cd speedtouch-1.3 $ ./configure If you get warnings here, install compilers, linkers, etc., from the SuSE CDs using YaST - try package groups, development, or search for whatever appears to be missing. $ make $ su (and enter root password) # make install This creates the program /usr/local/sbin/modem_run, which you need later. Note: I altered a couple of the programs and found that this would allow me genuinely to hotplug the modem. I was guessing a bit, but the following may help: save http://www.uyea.btinternet.co.uk/patch as a file ~/src/patch $ cd ~/src $ tar jxvf speedtouch-1.3.tar.bz2 $ cd speedtouch-1.3 $ patch -p1 < ../patch $ ./configure etc. You may also find it helpful to do the $ ./configure as $ ./configure --enable-debug --enable-syslog then when testing, you can see the output in the system log view (YaST=>misc) or from a konsole as root with # tail -f /var/log/messages You now need the modem microcode. It comes in the form of two files: ZZZLP1.eni and ZZZLP2.eni. This makes it easier to google for or to find if you download the drivers from Thomson (http://www.speedtouch.com/support.htm). If you installed on a dual boot system, you can probably find them in /windows/C/Program Files/Thomson/SpeedTouch USB/Bin I created a new directory # mkdir /etc/ppp/peers/speedtouch and copied the two files there as a convenient location for them. Now you can test if the modem actually does anything when you try to load the microcode: as root (all on one line) # /usr/local/sbin/modem_run -a /etc/ppp/peers/speedtouch/ZZZLP1.eni -f /etc/ppp/peers/speedtouch/ZZZLP2.eni -k -v 1 You should see some new information on the system log, some flashing lights on the modem and both eyes should turn yellow-green (initial the frog is winking red in the right eye)

I get the error as above and seem to be unable to find any guidance on what is wrong.

If all of that works, you need (at least on 9.1) a couple of extra changes to make it all work correctly. First, set pppoatm as a module loaded on boot: YaST>System>/etc/sysconfig editor - System + Kernel - MOSULES_LOADED_ON_BOOT. Just type in 'pppoatm' without the quotes. This loads pppoatm at boot time so that the modem can initialise automatically. Second, to get it to run automatically, you should create a hotplug script. Mine contains the following lines: (the bits between the ============ - watch out for line-wrapping - the bit starting if .. should be two lines, the first ending with \) ======================================================================= #!/bin/bash case $ACTION in add) echo "Uploading speedtouch microcode (/etc/hotplug/usb/speedtch)" if /usr/local/sbin/modem_run -a /etc/ppp/peers/speedtouch/ZZZLP1.eni \ -f /etc/ppp/peers/speedtouch/ZZZLP2.eni -k -v 1; then echo "Speedtouch microcode loaded" else echo "Speedtouch microcode not loaded" fi ;; remove) : ;; esac ======================================================================= I saved this as root as /etc/hotplug/usb/speedtch. It should be executable (I think); so do # chmod +x /etc/hotplug/usb/speedtch to make sure. That should have dealt with the microcode. The next part is getting a connection. IIRC, YaST was fine: YaST=>Network=>DSL=>configure and use default settings or follow suggestions. You should use PPPOATM and I chose hotplug as the device activation and 0.38 for the VPI/VCI (btinternet) You'll have to fill in the provider's details. Test with kinternet (which will need some reconfiguring if you haven't removed te seetings for the old modem) or $ cinternet -i dsl0 --start -- JDL