Re: apt-get update error libswt-mozilla-gtk-3.1-jni
Lennart Sorensen spiffera, alle 21:58, giovedì 9 febbraio 2006 circa: --force should not be used unless you know what you are doing. I think so. :) maybe i should say: read manpage first... So: Niclas, read 'man dpkg' !! :) If something like this happens, it is a bug and should be filed as one. If packages conflict, uninstall one of them, or don't upgrade until the maintainer fixes the bug. Using --force leaves the system in a somewhat broken state where in the future removing one of the packages that had a file conflict may cause the file to be removed even though the other packages still says it is installed and may require it. So it is a very very bad idea. i don't think so. :) this happen a lot of time when you dist-upgrade debian, or other debian-based system. In particular if you use testing, or unstable, like (i think) almost all writing here. bye! -- -gaspa- --- Powered by Debian GNU/Linux and Debian GNU/Hurd -- HomePage: iogaspa.altervista.org ---
multi wireless-profile
Hi, I use my notebook at home and office with wireless. Obviously at home I have different ESSID and different PSK to office. And so, at start, Debian searches last ESSID/PSK insert in configuration files. Is it possible have multiple profiles for wireless connection (and so choice at start profile required) to avoid manual configuration everytime? Thanks, Giulio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: multi wireless-profile
On Saturday 11 February 2006 09:37, antongiulio05 wrote: Hi, I use my notebook at home and office with wireless. Obviously at home I have different ESSID and different PSK to office. And so, at start, Debian searches last ESSID/PSK insert in configuration files. Is it possible have multiple profiles for wireless connection (and so choice at start profile required) to avoid manual configuration everytime? Thanks, Giulio you need to look at wpasupplicant. It will allow connection to different ESSIDs with specific key requirements. David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fglrx with xorg 6.9.0
Christophe Dupre wrote: Hi, I used to have fglrx working under XFree86 but when I switched to x.org it stopped working. Fair enough. I went to flavio's webpage, but I think it says I need x.org = 6.8.2. As anyone manage to install fglrx with x.org 6.9.0 I just did this yesterday from ATI's installer available from their website. ATI's installer can create packages for debian automatically, or it can extract its files (to let you patch them) and then let you run a script that builds debian packages. So here's the instructions: $ ./ati-driver-installer-8.12.7-x86_64.run --extract fglrx-tmp $ cd fglrx-tmp $ cd common/lib/modules apply the patch from http://lkml.org/lkml/2005/12/11/26 which lets the kernel module work with Kernel 2.6.15 $ cd - $ fakeroot ./packages/Debian/ati-packager.sh --buildpkg sid # rm -rf /usr/src/modules/fglrx /usr/src/fglrx.tar.bz2 dpkg -i the debs, use module-assistant to build the kernel module and you're good to go. (Don't forget to modprobe -r fglrx; modprobe fglrx before you start X again.) NOTE: it is no longer necessary to patch the fglrx directory to tell it that Debian/sid uses X.org 6.9.0. ATI already knows this and the current version of the installer knows it too. --Ken Bloom -- I usually have a GPG digital signature included as an attachment. See http://www.gnupg.org/ for info about these digital signatures. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: multi wireless-profile
On Sat, Feb 11, 2006 at 09:47:41AM +, David Goodenough wrote: On Saturday 11 February 2006 09:37, antongiulio05 wrote: I use my notebook at home and office with wireless. Obviously at home I have different ESSID and different PSK to office. And so, at start, Debian searches last ESSID/PSK insert in configuration files. Is it possible have multiple profiles for wireless connection (and so choice at start profile required) to avoid manual configuration everytime? you need to look at wpasupplicant. It will allow connection to different ESSIDs with specific key requirements. Alternatively you could use whereami. It allows you to configure anything you like based on various tests eg which ESSID is available, what IP address you were assigned via DHCP, etc. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing ifort 9 with alien
Rohit Kumar Mehta wrote:
Hi I am trying to install the Intel Fortran compiler on a Debian AMD64
workstation.
I read Daniel Grimwood's instructions here:
http://groups.google.com/group/linux.debian.ports.x86-64/browse_thread/thread/ea3f29040f74d8ce/c6fa52724b1fecf4?q=intel+fortranrnum=3#c6fa52724b1fecf4
and followed them faithfully, but have had no luck.
/proc/cpuinfo shows dual Intel Xeon 3.6 GHZ cpus and Debian AMD64
installed on it ok. Also /proc/cpuinfo has the following line:
address sizes : 36 bits physical, 48 bits virtual
I am using Sarge which right now only has alien 8.52
So I cd into the uncompressed directory and do issue the command:
amd64:/scratch/ifortran/l_fc_c_9.0.031# alien -gsk
intel-iforte9-9.0-031.em64t.rpm
Directory intel-iforte9-9.0 prepared.
Then I replace em64t with amd64 in debian/control and issue the command:
amd64:/scratch/ifortran/l_fc_c_9.0.031/intel-iforte9-9.0# debian/rules
binary
dh_testdir
dh_testdir
dh_testroot
dh_clean -k -d
dh_installdirs
dh_installdocs
dh_installchangelogs
find . -maxdepth 1 -mindepth 1 -not -name debian -print0 | \
xargs -0 -r -i cp -a {} debian/intel-iforte9
dh_compress
dh_makeshlibs
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcprts.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcxa.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcxaguard.so:
File format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifcore.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifcoremt.so:
File format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifport.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libunwind.so: File
format not recognized
dh_installdeb
dh_shlibdeps
/usr/bin/ldd: line 95: /usr/bin/lddlibc4: cannot execute binary file
dpkg-shlibdeps: failure: ldd on
`debian/intel-iforte9/opt/intel/fce/9.0/bin/codecov' gave error exit
status 1
dh_shlibdeps: command returned error code 256
make: [binary-arch] Error 1 (ignored)
dh_gencontrol
dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `intel-iforte9' in
`../intel-iforte9_9.0-031_amd64.deb'.
Can anyone help me? I am much obliged.
Thanks,
Rohit
Untar the attached. Place .tar.gz files from intel for your desired
compilers (ICC9 or IFort9) into target. Run the buildisolinux script -
it'll generate a .iso with repackaged (non-RPM) packages, and a simple
install script.
We use this at work.
icc.tgz
Description: application/compressed-tar
Re: ACPI with AMD64
Hi, after some time of searching in the acpi mailling lists I've found the following message: http://article.gmane.org/gmane.linux.acpi.devel/16431 So it seems as if these states are disabled by the mainboard manufactures, great! - snip -- Hello, I've recently discovered that my system didn't seem to go into C2/C3 states. In fact, they're not even recognized : # cat /proc/acpi/processor/CPU0/info processor id:0 acpi id: 0 bus mastering control: no power management:no throttling control: no limit interface: no # cat /proc/acpi/processor/CPU0/power active state:C1 max_cstate: C8 bus master activity: states: *C1: type[C1] promotion[--] demotion[--] latency[000] usage[] Would you happen to know why the Cx states are not seen ? Also, isn't there supposed to be bus mastering control available ? My mainboard is a Asus A7N8X rev 1.xx (nforce2). The kernels I tried with no success in whatever case are 2.4.29 and 2.6.15.2. Unfortunately, google doesn't seem to know much about this problem... Hi! Please try to do something like this: root at porygon:~/# cat /proc/acpi/fadt |acpitbl |grep P_LVL P_LVL2_LAT: 190 P_LVL3_LAT: 1900 If you will see more than 100 in the first line and more than 1000 in the second one, your Cx states are blocked by BIOS. My example is from ASUS A7V8X, which may be similar. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug filing advice needed: package uninstallable on amd64 only
Abiword is uninstallable on AMD64. It appears that the library package libenchant1c2 has been replaced by the package libenchant1c2a. This new package is available for AMD64; but the AMD64 Abiword port, and *only* the AMD64 port of Abiword, still has a dependency on the older libenchat1c2, which is no longer available. I'm curious what the proper way to proceed with this is. File a bug against Abiword with an AMD64 tag? Something else? Is it OK for us to file non-wishlist bugs of this sort, given that we're not yet an official port? Thanks, -c -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug filing advice needed: package uninstallable on amd64 only
Le 11.02.2006 17:08:09, [EMAIL PROTECTED] a écrit : Abiword is uninstallable on AMD64. It appears that the library package libenchant1c2 has been replaced by the package libenchant1c2a. This new package is available for AMD64; but the AMD64 Abiword port, and *only* the AMD64 port of Abiword, still has a dependency on the older libenchat1c2, which is no longer available. I'm curious what the proper way to proceed with this is. File a bug against Abiword with an AMD64 tag? Something else? Is it OK for us to file non-wishlist bugs of this sort, given that we're not yet an official port? I have filled a bug sometimes ago without the mention of amd64 #345498. It has been closed. The maintainer told me it has been fixed by a NMU. So, probably a NMU is needed also for amd64. Thanks, Jean-Luc pgpQHp8KaLuJi.pgp Description: PGP signature
Re: ACPI with AMD64
On 2/11/06, Thimo Eichstaedt [EMAIL PROTECTED] wrote: Hi, after some time of searching in the acpi mailling lists I've found the following message: http://article.gmane.org/gmane.linux.acpi.devel/16431 So it seems as if these states are disabled by the mainboard manufactures, great! I thought that since my motherboard (Asus A8N-E) supports CoolQuiet, it will have at least C2 enabled. I was wrong. IMHO there should have been a BIOS option to turn it on/off, but there isn't. I updated the BIOS to the latest (1010), but it still says throttling and C2 isn't supported. (I understand why they ship motherboards with C2 turned off, it is said it hurts performance) I had a similar situation with an AthlonXP + MS8188E motherboard, but there were programs that could enable C2 support (fvcool, athcool, etc.). It had a little impact on performance (IDE performance), but there I had to use C2, otherwise my CPU would have been too hot. I looked at those programs again, they support nforce2, but nothing is said about nforce4. I could try to enable C2 by telling these programs that my chipset is nforce2, but it would probably break something, as in nforce4 those registers might be somewhere else. There could be a workaround for enabling C2: you could try to change the ACPI_PROCESSOR_MAX_C2_LATENCY in include/acpi/processor.h, and recompile the kernel. However without enabling C2 on the motherboard I doubt it will have any effect. That limit is there with a purpose. Did anybody succeed in enabling C2 on a motherboard with nforce4 chipset? However on my Athlon XP I had throttling even without using athcool (if I recall correctly). Why isn't throttling supported on the Athlon64? Is there a way to enable it? How does the kernel detect if throttling is available? root at porygon:~/# cat /proc/acpi/fadt |acpitbl |grep P_LVL P_LVL2_LAT: 190 P_LVL3_LAT: 1900 P_LVL2_LAT: 101 P_LVL3_LAT: 1001 If you will see more than 100 in the first line and more than 1000 in the second one, your Cx states are blocked by BIOS. Yeap, it is blocked by BIOS. Edwin
Re: Bug filing advice needed: package uninstallable on amd64 only
[EMAIL PROTECTED] schrieb: Abiword is uninstallable on AMD64. It appears that the library package libenchant1c2 has been replaced by the package libenchant1c2a. This new package is available for AMD64; but the AMD64 Abiword port, and *only* the AMD64 port of Abiword, still has a dependency on the older libenchat1c2, which is no longer available. I'm curious what the proper way to proceed with this is. File a bug against Abiword with an AMD64 tag? Something else? Is it OK for us to file non-wishlist bugs of this sort, given that we're not yet an official port? Thanks, -c I also filled a bug sometime ago: #346533 I think the maintainer just forget to change the deps and is too lazy to change it. We have to live with the sarge version until its fixed. greets Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Perl is broken: Can't locate overload.pm
With recent update of my debian-amd64/unstable I've got perl broken. Now it reports error like debconf: Perl may be unconfigured (Can't locate overload.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/Template.pm line 331. Does anybody see this? Any suggestions on how to fix the problem? Thanks, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Perl is broken: Can't locate overload.pm
Max [EMAIL PROTECTED] writes: With recent update of my debian-amd64/unstable I've got perl broken. Now it reports error like debconf: Perl may be unconfigured (Can't locate overload.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/Template.pm line 331. Does anybody see this? Any suggestions on how to fix the problem? downgrade perl-modules back to version 5.8.8-1 (it was still in the archive yesterday when i ran into the same problem. you will have to install it manually with dpkg) and then put it on hold until perl catches up with it. --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
console-common missing a depends?
Hi, Got this with todays update. Looks like some perl stuff is now required in console common and its not in a dependency... Errors were encountered while processing: console-common E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up console-common (0.7.55.1) ... Can't locate overload.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/Template.pm line 331. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 331. Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8. Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7. Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10. Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7. Compilation failed in require at /usr/share/debconf/frontend line 6. BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6. Ed Tomlinson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Perl is broken: Can't locate overload.pm
Thanks! btw, I've found the following bugreport regarding this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352297 Max Alex Romosan wrote: Max [EMAIL PROTECTED] writes: With recent update of my debian-amd64/unstable I've got perl broken. Now it reports error like debconf: Perl may be unconfigured (Can't locate overload.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/Template.pm line 331. Does anybody see this? Any suggestions on how to fix the problem? downgrade perl-modules back to version 5.8.8-1 (it was still in the archive yesterday when i ran into the same problem. you will have to install it manually with dpkg) and then put it on hold until perl catches up with it. --alex-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fglrx with xorg 6.9.0
Cyril Chaboisseau wrote: Le 10 February vers 16:24, Romnea Kolap Pin écrivait: You can download the fglrx driver 8.21.7 from the ati webpage which support X.org http://x.org/ 6.9. you can even find a newest version version : 8.22.5 but according to this page http://www2.ati.com/drivers/linux/linux_8.22.5.html it is only compatible with XOrg 6.7 or 6.8; XFree86 version 4.1, 4.2, or 4.3 Looks like a typo to me. I haven't heard of their previous versions supporting XOrg 6.7 and v8.12.7 specifically supports 6.9, so it would be an odd regression to not support it now. 8.22.5 claims to support Linux 2.6.15 without needing patches. -- I usually have a GPG digital signature included as an attachment. See http://www.gnupg.org/ for info about these digital signatures.
