|
can't use sgfxi cause of wget-error
Out of X and as root I get something like the following when running sgfxi:
:: Code :: the options --inet6-only and --inet4-only are together not allowed:: Code :: Updating sgfxi now using the default server
ERROR: (198) The url/file: sgfxi failed to download - wget error. Exiting script now. wget normally works in my system, so I dont know if this is an error caused by sgfxi. There is no /var/log/sgfxi.log -file only a /var/log/smxi.log smxi is working without errors. Back to top |
|
neither option is used in sgfxi, that's all I can tell you.
Back to top |
|
Yes , I also think the error is in wget. Strange is , I never have problems using wget, only with sgfxi, and there is no /var/log/sgfxi.log
Orderd a nvidia card , when the card is there I will try to install the driver over smxi, hope this works. Thank you for your great work, I often used it and until now it allways was perfect! :: Code :: inxi -bxxx
System: Host: antix1 Kernel: 4.4.0-antix.1-amd64-smp x86_64 (64 bit gcc: 5.3.1) Desktop: IceWM 1.3.8+githubmod+20150914+fa3fdef dm: slim Distro: antiX-14-a3-RD_x64-full Killah P 11 October 2014 Machine: Mobo: Gigabyte model: B85M-HD3 v: x.x Bios: American Megatrends v: F12 date: 08/13/2015 CPU: Quad core Intel Core i5-4430 (-MCP-) speed/max: 1747/3200 MHz Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0412 Display Server: X.Org 1.18.2 drivers: intel (unloaded: fbdev,vesa) Resolution: 1280x1024@85.02hz GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 11.1.2 Direct Rendering: Yes Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 Card-2: Qualcomm Atheros AR9227 Wireless Network Adapter driver: ath9k bus-ID: 04:00.0 chip-ID: 168c:002d Drives: HDD Total Size: 320.1GB (8.8% used) Info: Processes: 171 Uptime: 22 min Memory: 638.6/7870.9MB Init: systemd v: 229 runlevel: 5 default: 5 Gcc sys: 5.3.1 alt: 4.8/4.9 Client: Shell (bash 4.3.421 running in xfce4-terminal) inxi Back to top |
|
It's unlikely to be a sgfxi error.
It could be, but it's more likely that something sgfxi does with wget is triggering the error. smxi runs sgfxi internally, but when it starts sgfxi, it updates it using a different logic. So if smxi starts sgfxi, and if sgfxi does not start and exits with wget error, and if no logs, that means that wget is failing for some reason on the very first test sgfxi runs to update itself if required, to get the remote version file. sgfxi does not run this test if it's started by smxi, since smxi will already have updated sgfxi before starting it. However, smxi runs the same basic update tests when it starts, so there should be little difference between the two. no log files for sgfxi, which would be /var/log/sgfxi/... means it has failed before logging begins. Which is quite early, by the way, in the script execution. I've over the years seen various networking errors causing such issues, sometime in the router, sometimes the isp, but the specific ipv4/ivp6 commands are not used anywhere in smxi/sgfxi, so if you see those errors, that's the cause probably, but it's not sgfxi, or shouldn't be. If you find different let me know exactly what it is and I'll fix it. Back to top |
|
For what it's worth, I used sgfxi a few days ago on a system, everything was fine.
Also just tested it now re starting it, no problems. Back to top |
|
All times are GMT - 8 Hours |