|
|||||
When you post an issue report, you have to say what the issue is. The log shows nothing obvious, so please say in words what you did,, and why you believe an error occurred, and where that error happened, in the smxi process.
While seeing log files is always good, they are only to help me diagnose the bug/issue reported, which you have as of yet not done. Back to top |
|||||
Sorry.
I installed the latest liquorix kernel, 3.9.5, then used smxi to try to set up the nvidia latest driver. It failed. Back to top |
|||||
show this:
inxi -bxxx and also the link to pastebin of /var/log/sgfxi/sgfxi.log the nvidia failure will not be in the smxi log but the sgfxi.log inxi will show me what your system is. Back to top |
|||||
Hi h2,
The HP linux printing checks are holding packages that don't need to be held; hpijs (and hplip-cups) are now transitional dummy packages. d-u worked fine without the 'hold' Back to top |
|||||
thanks drb, hpijs is removed, hplip-cups was not in group.
Back to top |
|||||
sgfxi script needs to use referrer to download
I don't know if this a recent change but today the sgfxi script was unable to download any fglrx drivers from the amd site.
The contents of the ".zip" files that were downloaded and failed to extract was an html document explaining that links from external sites are forbidden. By changing the $atiRef variable in the sgfxi script to be "--referer=support.ati.com" The download completed successfully (after I cleared the downloaded files from /usr/src/sgfxi-downloads) Back to top |
|||||
Amazing, amd never ceases to prove that they should be avoided.
I'll update that, thanks. [updated] should now work, unless they changed something else. Back to top |
|||||
Hi h2,
How does the driver part of smxi deal with graphic cards? I have an nvidia 210 board and the 343 series drivers have stopped supporting that card. I managed to get the correct driver (340 series) by selecting the latest rather than beta nvidia. In the last kernel upgrade this option brought in a 343 driver and I had to manually select the driver I wanted. Is this a bug in recognising the card or just the beta at some stage becomes the normal driver? drb :: Code :: inxi -v3
System: Host: siductionbox Kernel: 3.16-3.towo-siduction-amd64 x86_64 (64 bit gcc: 4.9.1) Desktop: KDE 4.14.1 (Qt 4.8.6) Distro: siduction 13.1.0 Firestarter - kde - (201305211844) Machine: Mobo: Gigabyte model: M57SLI-S4 Bios: Award v: F14 date: 03/07/2008 CPU: Dual core AMD Athlon 64 X2 5600+ (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 svm) bmips: 4022 clock speeds: max: 2800 MHz 1: 1000 MHz 2: 1000 MHz Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0 Display Server: X.Org 1.16.1 driver: nvidia Resolution: 1920x1080@60.00hz GLX Renderer: GeForce 210/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 340.24 Direct Rendering: Yes Network: Card: NVIDIA MCP55 Ethernet driver: forcedeth port: e400 bus-ID: 00:08.0 IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:16:e6:84:ec:51 Drives: HDD Total Size: 4961.0GB (40.0% used) ID-1: model: WDC_WD3200AAKS ID-2: model: WDC_WD6400AAKS ID-3: model: ST2000DM001 ID-4: model: ST2000DM001 Info: Processes: 198 Uptime: 43 min Memory: 1088.5/3959.6MB Init: systemd runlevel: 5 Gcc sys: 4.9.1 Client: Shell (bash 4.3.251) inxi: 2.2.9 Back to top |
|||||
It's not a bug, I knew nvidia was dropping support and creating a new legacy branch, and it looks like 343 driver is that, another guy is reporting that issue as well, only with a 8000 series.
Please show inxi -Gxxx I need to confirm the chipset id numbers to know what to use to create new legacy. Back to top |
|||||
All times are GMT - 8 Hours
|