|
Bugzilla – Full Text Bug Listing |
| Summary: | tiny-nvidia-install doesn't work | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Takashi Iwai <tiwai> |
| Component: | X11 3rd Party | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | aritger, ro, werner |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | proxy related patch | ||
Andy, tiny-nvidia-installER is the nvidia-installer built from "nvidia-installer-1.0.7.tar.gz" with a minimal patch, which limits the installer to allow only the "--update" option, since we don't ship the complete package. Anyway, the nvidia-installer executable of version 1.0-7676 has the same problem. I can ping "download.nvidia.com" and connect and login to ftp://download.nvidia.com. Hmm ... Is this sth. you can reproduce? Looks like gethostbyname() in snarf.c:190 fails - for whatever reasons - on SuSE 10.0 Beta1. It works fine on 9.3. That is strange that gethostbyname doesn't work. Does the full installer have the same problem? You could run something like `nvidia-installer --latest --ui=none` to test. At first I was going to suggest there was something wrong with your system network config, but if you can access ftp://download.nvidia.com through other means, that must not be the problem. What if you use the IP address instead? `nvidia-installer -m ftp://216.228.115.13 -l --ui=none` Created attachment 46254 [details]
proxy related patch
In some case proxy seems to be empty. Maybe because of some "*proxy*" env.
variables, which have empty setting. This patch fixes it for me.
The full installer has the same problem. Using "nvidia-installer -m ftp://216.228.115.13 -l --ui=none" didn't help. Could you please comment on the patch? The patch seems reasonable to me; I'll make a similar change to nvidia-installer. So the problem goes away if you unset FTP_PROXY, SNARF_PROXY, and PROXY envvars? > The patch seems reasonable to me; I'll make a similar change to > nvidia-installer. Thanks for considering to apply the patch. > So the problem goes away if you unset FTP_PROXY, SNARF_PROXY, and PROXY > envvars? My proxy settings: http_proxy= ftp_proxy= gopher_proxy= https_proxy= no_proxy=localhost Only ftp_proxy needs to be unset to get the (non-patched) installer working again. fixed for Beta3. Andy, when you have a offical patch ready, please let me know and attach it. Thanks. Just so that I understand: for some reason, in SuSE 10, an environment variable named "FTP_PROXY" will be set for all users, but default to an empty string? I certainly think nvidia-installer should be made more robust to handle this case, but at what point is this environment variable being set? Why? Right. The defaults (for root) seem to be: 9.3: no_proxy=localhost 10.0: http_proxy= ftp_proxy= gopher_proxy= https_proxy= no_proxy=localhost This seems to be a new feature/bug of 10.0. Rudi, could you comment on this? Probably I was wrong. These proxy settings are only done, when PROXY_ENABLED in /etc/sysconfig/proxy is set to "yes". Default is "no". But I think many users do this. I wonder whether it makes sense to set these proxy env. variables at all when these are empty anyway ... Werner, what do you think ? we could probably catch that case ... |
tiny-nvidia-install doesn't work with beta1. When started with --update, it shows ERROR: Unable to connect to (unknown host) after return is pressed, ERROR: Unable to determine most recent NVIDIA Linux-x86 driver version. and quits. The version is: x11-tools-0.1-12