:: Quote :: drb re the package version mismatch, make SURE to post the versions, I'm not seeing any version mismatch today. h2, As you say, they are both the same version now at 3.11.1-3 - the fail was when one was 3.11.1-2 and the other was 3.1.1-2+b1 drb Back to top |
|||||
oh, ok, I'll update the version detection to handle the +b1, though my experience is that usually that isn't a version mismatch... except when it is. I've always found it odd that a distro made by people who are so fond of rules would allow such a loose interpretation of what constitutes a version mismatch, but that's Debian, so we have to adjust to it.
Back to top |
|||||
hi
not many ppl would swap between Debian and liq kernels but you may like to see if this is a bug or not 1) I attempted to add liq sources and got this screenshot using smxi today 5/June/2011 09:00 WST (Perth Australia) FWIW I used a package called fbgrab and used fbgrab -C 1 /pathway/filename.png the key component I can duplicate in a booted up system as is :: Code :: W: GPG error: http://liquorix.net sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3EFF4F272FB2CD802) I believe one solution already exists at liquorix.net/ which is :: Code :: apt-get install '^liquorix-([^-]+-)?keyring.?'but I for me, appears as :: Code :: apt-get install '^liquorix-([^-]+-)?keyring.?'
Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'liquorix-archive-keyring' for regex '^liquorix-([^-]+-)?keyring.?' Note, selecting 'liquorix-keyring' for regex '^liquorix-([^-]+-)?keyring.?' Note, selecting 'liquorix-keyrings' for regex '^liquorix-([^-]+-)?keyring.?' liquorix-archive-keyring is already the newest version. liquorix-keyring is already the newest version. liquorix-keyrings is already the newest version. The following packages were automatically installed and are no longer required: libdvbpsi6 xli Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 79 not upgraded. but a repeat of apt-get update shows that did not work 3) Instead I looked at www.thelinuxdaily.com/2010/02/how-to-fix-public-key-is-not-available-message/ and used :: Code :: gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 3EFF4F272FB2CD80
gpg: requesting key 2FB2CD80 from hkp server wwwkeys.eu.pgp.net gpg: keyserver timed out gpg: keyserver receive failed: keyserver error AND gpg --keyserver http://pgp.mit.edu --recv-keys 3EFF4F272FB2CD80 gpg: requesting key 2FB2CD80 from http server pgp.mit.edu gpgkeys: no key data found for http://pgp.mit.edu/ gpg: no valid OpenPGP data found. gpg: Total number processed: 0 I am not an expert on gpg and I have port 11371 enabled in my modem/router firewall and previously been able to import keys regards Back to top |
|||||
ok better success in a terminal with
:: Code ::
gpg --recv-key 3EFF4F272FB2CD80 && gpg -a --export 3EFF4F272FB2CD80 | apt-key add - gpg: requesting key 2FB2CD80 from hkp server keys.gnupg.net gpg: key 2FB2CD80: public key "Steven Barrett <damentz@gmail.com>" imported gpg: Total number processed: 1 gpg: imported: 1 OK Back to top |
|||||
hi
current smxi says don't do a update and look at sidux forums. AND various sites....I smile as I know what you may mean is ....aptosid? 2) You may need to mention the "user scripts and dragons sub-forum." which details some issues for Nvidia? hope that helps Back to top |
|||||
Would like just to report two things that seem to be not working as expected.
In this system I installed sgfxi 4.17.27 (from June 21) and now I have 4.17.28 The first thing is that every time when I ran sgfxi it didn't accuse its own version and downloaded sgfxi again. The text output was something like "sgfxi local version - remote version 4.17.28" etc. That is, it sees the local version only as a dash and always downloads sgfxi again (even if it's already the latest version). The other thing is that it didn't work when I had only xserver-xorg-core (/usr/bin/Xorg) and I had to install xserver-xorg (/usr/bin/X) for it to work. That was sgfxi version 4.17.27. I didn't test 4.17.28 in this respect as I had xserver-xorg installed already. *edit- note that package xserver-xorg isn't by no means as "bloated" as package xorg so it isn't really much problem to install it (although it isn't really needed). I'm just saying what I saw. But it is easier to build a minimal system only with xserver-xorg-core (xserver-xorg depends on xorg's input and video drivers so one has to make sure to install the ones he needs beforehand so the package won't pull them all). Back to top |
|||||
I'll assume I made an upload error on sgfxi / version file, that's fixed now, tested and working.
I think I updated sgfxi as you noted to check for either X or Xorg version, so it should work with just xserver-xorg-core now. Back to top |
|||||
aus9, wow, that message is old, I'll see if I can find it in the warnings and update that, heh.
Back to top |
|||||
inxi: Sensors: System Temperatures: cpu: 36.0C mobo: 38.0C gpu: 0.0:42C
gpu: 0.0:42C if can help the output of: nvidia-smi -q :: Code ::
==============NVSMI LOG============== Timestamp : Wed Aug 10 10:06:54 2011 Driver Version : 280.13 Attached GPUs : 1 GPU 0000:04:00.0 Product Name : GeForce GT 220 Display Mode : N/A Persistence Mode : Disabled Driver Model Current : N/A Pending : N/A Serial Number : N/A GPU UUID : N/A Inforom Version OEM Object : N/A ECC Object : N/A Power Management Object : N/A PCI Bus : 4 Device : 0 Domain : 0 Device Id : 0A2010DE Bus Id : 0000:04:00.0 Fan Speed : 60 % Memory Usage Total : 1023 Mb Used : 140 Mb Free : 882 Mb Compute Mode : Default Utilization Gpu : N/A Memory : N/A Ecc Mode Current : N/A Pending : N/A ECC Errors Volatile Single Bit Device Memory : N/A Register File : N/A L1 Cache : N/A L2 Cache : N/A Total : N/A Double Bit Device Memory : N/A Register File : N/A L1 Cache : N/A L2 Cache : N/A Total : N/A Aggregate Single Bit Device Memory : N/A Register File : N/A L1 Cache : N/A L2 Cache : N/A Total : N/A Double Bit Device Memory : N/A Register File : N/A L1 Cache : N/A L2 Cache : N/A Total : N/A Temperature Gpu : 41 C Power Readings Power State : N/A Power Management : N/A Power Draw : N/A Power Limit : N/A Clocks Graphics : N/A SM : N/A Memory : N/A Back to top |
|||||
that looks right to me.
if nvidia driver, the command is: nvidia-settings -c :0.0 -q GPUCoreTemp First line shows the temp. If it's nouveau driver, the temp is in the output of sensors. Back to top |
|||||
All times are GMT - 8 Hours
|