Yast hangs at 99% downloaded - aria2c can't parse progress line [11.3]

I’ve just upgraded to 11.3, as a result, the suse-supplied video driver runs very slowly (screen-saver updates about 2 fps, to give you an idea) On 11.2, I had installed nvidia’s native driver and things were just fine, so I tried to install the latest nvidia driver again, but I’m getting a hard hang with Yast – at 99% downloaded, yast stops responding (“abort” doesn’t respond, but an external “kill” signal works)

Finally getting the bright idea of checking the y2log file, I see the following:

[timestamp] <2> sysname [zypp] MediaAria2c.cc(getFileCopy):445 aria2c reported a file, but no progress data available
[timestamp] <3> sysname [zypp] MediaAria2c.cc(getFileCopy):391 Can’t parse progress line ‘#1 SIZE:26.1MiB/26.1MiB(100%) CN:1]’
[timestamp] <3> sysname [zypp] MediaAria2c.cc(getFileCopy):391 Can’t parse progress line ‘#1 SIZE:26.1MiB/26.1MiB(100%) CN:1]’

these three lines are repeated every second

I’m sure there are some fingers to be pointed [nvidia’s ftp server is borked; aria2c is clueless, etc] but that does not help me - what do I need to do to convince this “aria2c” program that the file has, in fact, completely downloaded so that the installation process can continue?

Here is some information on loading the nVidia driver in openSUSE 11.3:

You should look at this document before proceeding on…

SDB:Configuring graphics cards - openSUSE

Then, take a look at the procedure I use to install the nVidia driver as I install openSUSE 11.3:

  1. During the install, when you have the option to change your booting setup, I add nomodeset to the kernel load command for the normal load/start of openSUSE. This kernel startup option is already present for the Failsafe selection for openSUSE.
  2. During the first start of openSUSE, I download the latest nVidia Video driver to the downloads folder.
  3. I change/save the System/Kernel option NO_KMS_IN_INITRD from “No” to “Yes” in the /etc/sysconfig Editor in Yast.
  4. I do an update of openSUSE on the first run of openSUSE and then a restart/reboot.
  5. In grub OS selection I add the command line option “3” to the openSUSE start line so that I just go to the run level three terminal prompt.
  6. I login in as root and change to the /home/user/Downloads folder.
  7. I run/install the NVIDIA video driver using “sh ./NVIDIA-Linux-x86_64-256.53.run” and answer all questions as appropriate for my system.
  8. Type in reboot at terminal prompt to restart the system with new video driver.

Thank You,

Thanks - yes, I’m aware that I can manually download and install the driver, but that wasn’t the question (I should have known I should not have left that herring on the plate…) the question was what do I need to do to convince this “aria2c” program that the file has, in fact, completely downloaded so that the installation process can continue?

after all, if this problem happens with at least one repository, there is the possibility it may happen with another (I’ve seen this problem for two different packages on that same repository so far, so yes, I’m leaning to this being a problem at nVidia’s end, but you and I both know the chances of them admitting such…)

So afbbsuid you are trying to install the nVidia video driver through the nVidia Repository and YaST hangs in the process while using aria2 program to download these files, is that correct? I am sorry I did not read through your message properly.

I have not tried to use this nVidia repository method under openSUSE 11.3 due to some other issues in its setup which are supposed to also work properly when added as a repository. I can only say that such issues often heal themselves after a day or so if the problem is on the nVidia server and never if the problem is on your PC.

I still suggest you go the manual method all of the way and bypass nVidia’s repository, where the problem may never be fixed in time for your usage. This is just my opinion and I do hope you find the solution that you seek.

Thank You,

On 2010-09-06 21:06, afbbsuid wrote:
>
> I’ve just upgraded to 11.3, as a result, the suse-supplied video driver
> runs very slowly (screen-saver updates about 2 fps, to give you an idea)
> On 11.2, I had installed nvidia’s native driver and things were just
> fine, so I tried to install the latest nvidia driver again, but I’m
> getting a hard hang with Yast – at 99% downloaded, yast stops
> responding (“abort” doesn’t respond, but an external “kill” signal
> works)
>
> Finally getting the bright idea of checking the y2log file, I see the
> following:
>
> [timestamp] <2> sysname [zypp] MediaAria2c.cc(getFileCopy):445
> aria2c reported a file, but no progress data available
> [timestamp] <3> sysname [zypp] MediaAria2c.cc(getFileCopy):391
> Can’t parse progress line ‘#1 SIZE:26.1MiB/26.1MiB(100%) CN:1]’
> [timestamp] <3> sysname [zypp] MediaAria2c.cc(getFileCopy):391
> Can’t parse progress line ‘#1 SIZE:26.1MiB/26.1MiB(100%) CN:1]’
>
> these three lines are repeated every second
>
> I’m sure there are some fingers to be pointed [nvidia’s ftp server is
> borked; aria2c is clueless, etc] but that does not help me - what do I
> need to do to convince this “aria2c” program that the file has, in fact,
> completely downloaded so that the installation process can continue?

Aria2c is a special downloader program. It can download from several sites at the same time,
monitoring if a mirror is not working and switch to another one. It can also check if the download
is correct and re-download again all or part to get a guaranteed correct download. For this it needs
to be provided with what is called a “metalink”. The opensuse redirector provides such data. I don’t
know what features are used, though.

However, it can fail on some situations. For instance, some people have reported problems when used
from sites with some proxies. Perhaps there is something on the nvidia site that makes it fail.

However, it can be disabled: I think it is “ZYPP_ARIA2C=0” in the environment.

Like, in a terminal:

su -
ZYPP_ARIA2C=0 yast2 sw_single

I think there is a configuration setting somewhere, but I can’t find it now.

I suggest you try disabling it. If it works, then you should report this in Bugzilla, so that
somebody can investigate the real cause and how to avoid it in the future, if possible.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))

There does seem to be an issue with Nvidia’s FTP server - with the ZYPP_ARIA2C=0 parameter, the download reaches 100%, but fails as follows:

[zypp++] MediaCurl.cc(doGetFileCopy):1116 URL: ftp://download.nvidia.com/opensuse/11.3/x86_64/x11-video-nvidiaG02-256.53-16.1.x86_64.rpm
…]
[YCP] PackageCallbacks.ycp:1960 Downloading ftp://download.nvidia.com/opensuse/11.3/x86_64/x11-video-nvidiaG02-256.53-16.1.x86_64.rpm to /var/adm/mount/AP_0x00000009/x86_64/x11-video-nvidiaG02-256.53-16.1.x86_64.rpm

[zypp] MediaCurl.cc(doGetFileCopy):1210 curl error: 28: FTP response timeout, temp file size 27410432 byte.

[zypp] PathInfo.cc(unlink):670 unlink /var/adm/mount/AP_0x00000009/x86_64/x11-video-nvidiaG02-256.53-16.1.x86_64.rpm.new.zypp.A1B4pw
[zypp] Exception.cc(log):133 MediaCurl.cc(evaluateCurlCode):928 THROW: MediaCurl.cc(evaluateCurlCode):928: Download (curl) error for ‘ftp://download.nvidia.com/opensuse/11.3/x86_64/x11-video-nvidiaG02-256.53-16.1.x86_64.rpm’:
[zypp] Exception.cc(log):133 Error code: User abort
[zypp] Exception.cc(log):133 Error message: FTP response timeout

so it seems the final handshake between the FTP server and client doesn’t arrive, which gives yast a headache…

so, it seems for this package at least, I’ll have to go back to the full manual process (a shame, really, 'cause I was all jazzed that this finally worked in 11.2) OTOH, this at least points to a (potential) problem w/aria2c if the sending FTP server doesn’t play nice…

So at least you figured out what was wrong afbbsuid. I understand the desire to use the repository method, but if you want to load the very latest nVidia version, you have to stick with the manual mode it would seem. Have a good day afbbsuid and thanks for letting us know of the final outcome to the problem.

Thank You,