Re: [gentoo-user] x86 boot failure
On Thursday 06 May 2010 17:03:54 Dale wrote: Neil Bothwick wrote: On Thu, 06 May 2010 10:03:59 -0500, Dale wrote: Did you mean press e ? No. I don't see anything in the man page about hitting the c key. What does that do? I've used e, b and such but never heard of c. It drops you to the grub command line, it's documented on the GRUB menu screen itself, just after it tells you about e. Oh OK. I didn't reboot and read that part. lol I learned something today. Just hope I will remember it when I need it.;-) 'c' is good as long as the error is only with the GRUB entry. I usually find that on new installs the causes of failure to boot may be deeper and I will need to chroot back into the installation to fix things; e.g. reconfigure the kernel, add drivers and what not. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] x86 boot failure
Are you sure ext[234] is compiled statically into the kernel in this .config? Also the drivers for the EIDE / SATA controller. Missing FS and/or controller drivers will result in a regular kernel boot with a panic at the end, when it's time to mount root and load init. In this case grubs seems to load the kernel image, but the kernel hangs before printing anything. I would check the processor type setting (A 3GHz Celeron should be P4-based) and/or muck around with ACPI. Also try disabling framebuffer drivers and using a plain VGA console. Leave all advanced settings in your bios to their defaults. And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a lot better for that kind of hardware if you do not absolutely need to run 64-bit code for some reason. andrea
Re: [gentoo-user] x86 boot failure
On Fri, 7 May 2010 07:28:00 +0100, Mick wrote: It drops you to the grub command line, it's documented on the GRUB menu screen itself, just after it tells you about e. Oh OK. I didn't reboot and read that part. lol I learned something today. Just hope I will remember it when I need it.;-) 'c' is good as long as the error is only with the GRUB entry. I usually find that on new installs the causes of failure to boot may be deeper and I will need to chroot back into the installation to fix things; e.g. reconfigure the kernel, add drivers and what not. Indeed, but in this case the question was about getting to a grub proompt, and pressing c is a lot simpler than digging out a live CD, rebooting and setting up a chroot. -- Neil Bothwick I couldn't repair your brakes, so I made your horn louder. signature.asc Description: PGP signature
Re: [gentoo-user] x86 boot failure
On Thursday 06 May 2010 12:52:55 Mick wrote: When I get problems like this I usually run grub in a terminal and then use autocompletion to find out what grub sees: root (hd --tab it will list all partitions and hopefully help you find your boot partition. Then search for the kernel image: kernel /boot/ --tab If you have chosen the correct grub root partition you should find your kernel image in there. The problem with that is that grub in a running system may detect the disks in a different order from the booting grub. Better would be to interrupt the boot with e or (as Neil suggested) c. Either will allow you to use the Tab key to find disks, partitions and images. -- Rgds Peter.
Re: [gentoo-user] Re: Kernel upgrade and now LUKS failure.
Am 06.05.2010 20:38, schrieb Stefan G. Weichinger: The main question is still unanswered: Why does pam_mount not work anymore with the given device/key ? additional digging: I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528366 where the poster tries the underlying mount.crypt call. I did that as well and get: # mount.crypt -v -o fsk_cipher=aes-256-cbc,fsk_hash=md5,keyfile=/etc/security/verysekrit.key /dev/VG01/crypthome /mnt/gschwind command: 'readlink' '-fn' '/dev/VG01/crypthome' command: 'readlink' '-fn' '/mnt/gschwind' Password: mount.crypt(crypto-dmc.c:144): Using _dev_dm_0 as dmdevice name crypt_activate_by_passphrase: Operation not permitted which is in fact the error pam_mount throws up : pam_mount(mount.c:64): Errors from underlying mount program: pam_mount(mount.c:68): crypt_activate_by_passphrase: Operation not permitted Downgrade pam_mount from 2.1 to 2.0 ... same error. But it works with pam_mount 1.33 ! I don't know which old bugs I reintroduce to my system by doing this ;-) I think I am gonna file a bug for this now. Stefan
Re: [gentoo-user] x86 boot failure
Hello Andrea, Andrea Conti a...@alyf.net writes: I would check the processor type setting (A 3GHz Celeron should be P4-based) and/or muck around with ACPI. Also try disabling framebuffer drivers and using a plain VGA console. Leave all advanced settings in your bios to their defaults. And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a lot better for that kind of hardware if you do not absolutely need to run 64-bit code for some reason. That is what I thought. I looked into the BIOS: no AHCI support. I edited the genkernel .config and set the various SATA drivers as built-in. There seemed to be nothing wrong with grub or its configuration (I rebuilt it anyway, just in case). In the end I gave up and installed the machine as an amd64. I may know today how that turned out: my install script shuts the machine down at the end and I'll need to get someone to re-boot it for me as I'm not in the office. I'll let you know what happened. Thanks Andrea and everyone else for your help. Roger
Re: [gentoo-user] arping network profile issue
On 05/06/10 03:35, Zhou Rui wrote: Hi folks, I setup a network interface to switch in two different network with different gateways using config_eth0=( arping ), and I can get gateway mac when use arping2 command directly. But the /etc/init.d/net.eth0 start always fails, can you help me to find the issue out? I cant understand what you're trying to achieve. IP will always do the arp for you so just set up the IP level stuff and whatever you're trying to do should work. dns_domain=vm config_eth0=( arping ) AFAICT This means you want to try to find a free address in the 169.254.x.x auto self configuration range - is that what you want? gateways_eth0=( 192.168.1.254,,192.168.1.114 192.168.1.1,,192.168.1.114 ) As none of those addresses are local, they cant be used as a gateway for a 169.254 address.
Re: [gentoo-user] x86 boot failure
On 7 May, Roger Mason wrote: Hello Andrea, Andrea Conti a...@alyf.net writes: I would check the processor type setting (A 3GHz Celeron should be P4-based) and/or muck around with ACPI. Also try disabling framebuffer drivers and using a plain VGA console. Leave all advanced settings in your bios to their defaults. And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a lot better for that kind of hardware if you do not absolutely need to run 64-bit code for some reason. That is what I thought. I looked into the BIOS: no AHCI support. I edited the genkernel .config and set the various SATA drivers as built-in. There seemed to be nothing wrong with grub or its configuration (I rebuilt it anyway, just in case). In the end I gave up and installed the machine as an amd64. I may know today how that turned out: my install script shuts the machine down at the end and I'll need to get someone to re-boot it for me as I'm not in the office. I'll let you know what happened. Thanks Andrea and everyone else for your help. One more hint (that I've got earlier on this list) Boot from a rescue CD (preferably http://www.sysresccd.org/ ) then execute lspci -k it shows you all drivers that have been selected during boot. Good luck, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] x86 boot failure
Helmut Jarausch jarau...@igpm.rwth-aachen.de writes: One more hint (that I've got earlier on this list) Boot from a rescue CD (preferably http://www.sysresccd.org/ ) then execute lspci -k it shows you all drivers that have been selected during boot. Many thanks fir the information. Cheers, Roger
[gentoo-user] Re: Loosing key presses since upgrade to xorg-server-1.7.6
Nikos Chantziaras wrote: evdev? Right, I was trying to avoid that. But you were probably right. I have upgraded to xorg-server-1.8 and switched to evdev for the keyboard and mouse, with udev autodetection. This seems to have solved the issue. Of course, now we'll never know if switching to evdev solved it, or if it was xorg-server-1.8. But I didn't feel like learning the hal-style configuration, only to restart from scratch with udev. Anyway, thanks for the hint. -- Remy signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Re: Kernel upgrade and now LUKS failure.
Am 07.05.2010 10:53, schrieb Stefan G. Weichinger: I think I am gonna file a bug for this now. http://bugs.gentoo.org/show_bug.cgi?id=318865
[gentoo-user] KDE takes ages to show password screen after suspend
Hi, when I suspend my computer, KDE locks the session. This usually happens, when I close my laptop lid. When I open it again, it takes 1 to 20 seconds (seamingly random) untill the login screen appears. During this time, I just see a black screen and a mouse pointer (somewhere), but I cannot move it. If no X server is started, i.e. I'm on the shell, the computer always responds after a second or so when the laptop lid is opened again. Any ideas what causes this or how to fix it? Regards, Roman
snackup (was: Re: [gentoo-user] backup to a cold-swap drive)
Iain Buchanan writes: On Thu, 2010-04-29 at 16:44 +0200, Alex Schuster wrote: using this script, adapted to their needs, I started to rewrite it in a way that it reads a config file, and no modification of the script itself is necessary. If anyone is interested, send me an email. interested! So is it on sourceforge yet ;) Sorry, it took a little longer. I was ill, and then these scripts tend to grow and grow until I am satisfied with them. It's still not perfect, but I think at the moment it does what it should do. Still not on sourceforge, but here: http://www.wonkology.org/utils/snackup The name is silly, but I kinda like it now. A backup utilizing LVM snapshots... snapshot backup... snackup! It needs a config file that is looked up in some default locations, or can be specified with the -c option. Use option -T to generate a template that has information on the syntax and some examples. In short: The config file defines targets you give as arguments to snackup. So 'snackup home' backs up your /home partition, 'snackup etc' creates a .tgz file of your /etc. The config file is sourced, so you can put any bash stuff you want into there, like some shell functions you want to have executed. For example, I want my /var/log/portage/*.log files to be compressed before I backup my /var partition. A target is started by a colon, followed by name, type, source and destination (and optionally more), separated by one or more tab characters. Type can be 'cp', 'dd', 'tar', 'rsync' or 'rdiff'. I only tested dd, tar and rdiff so far, though. The source directory may be prefixed by the volume group and LVM of that partition in order to create an lvm snapshot first. You may add a LUKS key if the partition is encrypted. The source may contain wildcards. In that case, all matching files are backed up to the destination. If the type has a * appended, all matching files are backed up individually. Some examples: : tar kde .kde* /backup/kde.%s Target 'kde' will backup all your .kde* directories to /backup/kde.tar (the %s is replaced by a suffix, usually tar). You need to be in your home directory, otherwise the path will not be found. This is not necessary if you use ~//.kde* instead. : kernels tar*/usr/src//linux-* /backup/src/%f.%s -j - lsf Target 'kernels' will backup your /usr/src/linux-* directories individually - one tar file for each (note the * appendended to the tar target type). The -z option will be passed to the tar command, and the suffix is changed to tgz accordingly. The // denotes that the backup should be done locally from the directory left to the //. Otherwise, the full path would be included in the tar file. : tar etc /etc/backup/etc_%d.%s -j Target 'etc' will tar your /etc directory, compressed with bzip2. The %d will be replaced by the current date. You can change the date format by re-defining a date() shell function. You will get a message about tar removing the leading /, you can avoid it by replacing /etc by ///etc, meaning that your local directroy will be /. : bootdd /dev/sda5 /dev/sdb5 bs=32M Target 'boot' will backup a boot partition with dd. Options like the bs=32M are added directly to the dd command. : homersync system/home::. /backup/home/ Target 'home' will create a LVM snapshot of the /dev/system/home logical volume, mount it and back it up with rdiff-backup. The '.' could also be a / or left off. : var rsync system/var::/ /backup/var/- ziplog Similar, but the command ziplog will be executed before the backup, compressing some log files. It must be defined in the config file. The script has some options: -c file location of config file -C clear destination first -d dummy mode, just show what would be done -f force backup (the initial rdiff-backup may need this) -h show this help -l output to log file, too -L log file (default:/home/wonko/log/snackup.log); may be a directory (add a trailing slash) to create target-specific logs -n luse nice level l (default:10, 0 to turn off) -N luse ionice level l (default:3, 0 to turn off) -o extra options that will added to the actual backup command -s size size of LVM snapshot (default:2G) -S char replace tab as delimiter for targets in config file -T output config file template -v verbose output; may be given multiple times 1: some extra output; 2: add -v to commands; 3: set -xv -V output version information and exit Most important are: -c to specify the location of the config file -d to output what would be done, you will see the final tar / rdiff- backup / whatever command with all its options. -T to see a template. Save it with snackup
Re: [gentoo-user] KDE takes ages to show password screen after suspend
On 7 May 2010 19:33, Roman Naumann roman_naum...@fastmail.fm wrote: Hi, when I suspend my computer, KDE locks the session. This usually happens, when I close my laptop lid. When I open it again, it takes 1 to 20 seconds (seamingly random) untill the login screen appears. During this time, I just see a black screen and a mouse pointer (somewhere), but I cannot move it. If no X server is started, i.e. I'm on the shell, the computer always responds after a second or so when the laptop lid is opened again. Any ideas what causes this or how to fix it? Suspend is that when the computer isn't off just the things stays in memory, isn't? When the contents of the memory is writed to the disk and the machine is get off that is the hibernate function, isn't? It is possible that when you close the lid the contents of memory writed to the disk and reading this few hundred Mbyte - on my laptop KDE is eating ~800 Mbyte memory, the hungry Beast! :) - takes that long time what you mentioned? I'm not a big hacker just I'm thinking over it. :$ -- - - -- Csanyi Andras -- http://sayusi.hu -- Sayusi Ando -- Bízzál Istenben és tartsd szárazon a puskaport!.-- Cromwell
Re: snackup (was: Re: [gentoo-user] backup to a cold-swap drive)
Alex Schuster wo...@wonkology.org wrote: Iain Buchanan writes: On Thu, 2010-04-29 at 16:44 +0200, Alex Schuster wrote: using this script, adapted to their needs, I started to rewrite it in a way that it reads a config file, and no modification of the script itself is necessary. If anyone is interested, send me an email. interested! So is it on sourceforge yet ;) Sorry, it took a little longer. I was ill, and then these scripts tend to grow and grow until I am satisfied with them. It's still not perfect, but I think at the moment it does what it should do. Still not on sourceforge, but here: http://www.wonkology.org/utils/snackup The name is silly, but I kinda like it now. A backup utilizing LVM snapshots... snapshot backup... snackup! It needs a config file that is looked up in some default locations, or can be specified with the -c option. Use option -T to generate a template that has information on the syntax and some examples. In short: The config file defines targets you give as arguments to snackup. So 'snackup home' backs up your /home partition, 'snackup etc' creates a .tgz file of your /etc. The config file is sourced, so you can put any bash stuff you want into there, like some shell functions you want to have executed. For example, I want my /var/log/portage/*.log files to be compressed before I backup my /var partition. A target is started by a colon, followed by name, type, source and destination (and optionally more), separated by one or more tab characters. Type can be 'cp', 'dd', 'tar', 'rsync' or 'rdiff'. I only tested dd, tar and rdiff so far, though. The source directory may be prefixed by the volume group and LVM of that partition in order to create an lvm snapshot first. You may add a LUKS key if the partition is encrypted. The source may contain wildcards. In that case, all matching files are backed up to the destination. If the type has a * appended, all matching files are backed up individually. Some examples: : tar kde .kde* /backup/kde.%s Target 'kde' will backup all your .kde* directories to /backup/kde.tar (the %s is replaced by a suffix, usually tar). You need to be in your home directory, otherwise the path will not be found. This is not necessary if you use ~//.kde* instead. : kernels tar*/usr/src//linux-* /backup/src/%f.%s -j - lsf Target 'kernels' will backup your /usr/src/linux-* directories individually - one tar file for each (note the * appendended to the tar target type). The -z option will be passed to the tar command, and the suffix is changed to tgz accordingly. The // denotes that the backup should be done locally from the directory left to the //. Otherwise, the full path would be included in the tar file. : tar etc /etc/backup/etc_%d.%s -j Target 'etc' will tar your /etc directory, compressed with bzip2. The %d will be replaced by the current date. You can change the date format by re-defining a date() shell function. You will get a message about tar removing the leading /, you can avoid it by replacing /etc by ///etc, meaning that your local directroy will be /. : bootdd /dev/sda5 /dev/sdb5 bs=32M Target 'boot' will backup a boot partition with dd. Options like the bs=32M are added directly to the dd command. : homersync system/home::. /backup/home/ Target 'home' will create a LVM snapshot of the /dev/system/home logical volume, mount it and back it up with rdiff-backup. The '.' could also be a / or left off. : var rsync system/var::/ /backup/var/- ziplog Similar, but the command ziplog will be executed before the backup, compressing some log files. It must be defined in the config file. The script has some options: -c file location of config file -C clear destination first -d dummy mode, just show what would be done -f force backup (the initial rdiff-backup may need this) -h show this help -l output to log file, too -L log file (default:/home/wonko/log/snackup.log); may be a directory (add a trailing slash) to create target-specific logs -n luse nice level l (default:10, 0 to turn off) -N luse ionice level l (default:3, 0 to turn off) -o extra options that will added to the actual backup command -s size size of LVM snapshot (default:2G) -S char replace tab as delimiter for targets in config file -T output config file template -v verbose output; may be given multiple times 1: some extra output; 2: add -v to commands; 3: set -xv -V output version information and exit Most important are: -c to specify the location of the config file -d to output what would be
[gentoo-user] Re: snackup
cov...@ccs.covici.com writes: I have a question -- where would lvm put a snapshot and how could I pass some list of excludes to rdiff-backup. I have an lvm which is taking all the PEs and a snapshot would take up lots of disk space -- or would it. Would I need some free pes to put the snapshot? An LVM snapshot has to be in the same volume group as the LVM. If all your physical extends are full, this will not work I'm afraid. But you can reduce the size of one LVM with lvreduce. Of course you have to resize the file system inside first. This is a little more complicated than extending the size, because you have to specify the size when reducing the file system and the LVM. And the file system has to be unmounted :( Let's say you want to reduce your data partition of 15G to 10G: umount /dev/myvg/data fsck -f /dev/myvg/data resize2fs /dev/myvg/data 9G lvresize -L 10G /dev/myvg/data resize2fs /dev/myvg/data mount /dev/myvg/data The 2nd resize2fs maximizes the size of the fs inside the LVM. I do not know (does anyone else?) if you could skip this and reduce it to 10G in the first resize2fs step. Just to be on the safe side I reduce it a little more, and let it adapt do the reduced LVM size afterwards. The snapshot itself takes nearly no space at all - it only keeps the changes that occur in the LVM while the snapshot is in place. So it grows when you modify the LVM you snapshotted. When you do not much modifications, 15-20% is enough according to the lvcreate man page. And I think I had it much lower without problems. I would expect that it can be really small when you do not change the original LVm much. snackup uses 2G as default, change this with option -s. Of course, when you do large modifications, like creating larger files, this may be too small. Excludes can be given with the -x option (multiple times). And have a look at the config template that snackup -T gives you. Near the bottom, the variable oXclude is defined. It is an array, just change it to your needs. it already excludes things like ccache, kdecache-* directories, */tmp/portage, and the dreaded nepomuk directory fo KDE4 because this sometimes gets really REALLY large here. snackup -x dip -x dap would exclude the stuff already pre-defined and dip and dap. If you want to exclude dip and dap only, call snackup -x -x dip -x dap. But I find it easier to adapt the oXclude array. Wonko
Re: [gentoo-user] Re: snackup
Alex Schuster wo...@wonkology.org wrote: cov...@ccs.covici.com writes: I have a question -- where would lvm put a snapshot and how could I pass some list of excludes to rdiff-backup. I have an lvm which is taking all the PEs and a snapshot would take up lots of disk space -- or would it. Would I need some free pes to put the snapshot? An LVM snapshot has to be in the same volume group as the LVM. If all your physical extends are full, this will not work I'm afraid. But you can reduce the size of one LVM with lvreduce. Of course you have to resize the file system inside first. This is a little more complicated than extending the size, because you have to specify the size when reducing the file system and the LVM. And the file system has to be unmounted :( Let's say you want to reduce your data partition of 15G to 10G: umount /dev/myvg/data fsck -f /dev/myvg/data resize2fs /dev/myvg/data 9G lvresize -L 10G /dev/myvg/data resize2fs /dev/myvg/data mount /dev/myvg/data The 2nd resize2fs maximizes the size of the fs inside the LVM. I do not know (does anyone else?) if you could skip this and reduce it to 10G in the first resize2fs step. Just to be on the safe side I reduce it a little more, and let it adapt do the reduced LVM size afterwards. The snapshot itself takes nearly no space at all - it only keeps the changes that occur in the LVM while the snapshot is in place. So it grows when you modify the LVM you snapshotted. When you do not much modifications, 15-20% is enough according to the lvcreate man page. And I think I had it much lower without problems. I would expect that it can be really small when you do not change the original LVm much. snackup uses 2G as default, change this with option -s. Of course, when you do large modifications, like creating larger files, this may be too small. Excludes can be given with the -x option (multiple times). And have a look at the config template that snackup -T gives you. Near the bottom, the variable oXclude is defined. It is an array, just change it to your needs. it already excludes things like ccache, kdecache-* directories, */tmp/portage, and the dreaded nepomuk directory fo KDE4 because this sometimes gets really REALLY large here. snackup -x dip -x dap would exclude the stuff already pre-defined and dip and dap. If you want to exclude dip and dap only, call snackup -x -x dip -x dap. But I find it easier to adapt the oXclude array. Thanks, very interesting and I will have a look. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Re: Kernel upgrade and now LUKS failure.
Am 07.05.2010 16:24, schrieb Stefan G. Weichinger: Am 07.05.2010 10:53, schrieb Stefan G. Weichinger: I think I am gonna file a bug for this now. http://bugs.gentoo.org/show_bug.cgi?id=318865 Aside from the potential bug: As I store the verysekrit.key on the same hdd as the encrypted device and use the rather simple shadowed password to decrypt that key ... isn't that just plain stupid? The overall security is just as good as my password. Cracking it with john opens the key to decrypting the LUKS-volume ... Yes, if I would store the key on another volume (stick or something) as mentioned in that howto it would make sense but in my case ... *scratches head* ;-) Stefan
Re: [gentoo-user] KDE takes ages to show password screen after suspend
On Friday 07 May 2010 19:26:46 András Csányi wrote: On 7 May 2010 19:33, Roman Naumann roman_naum...@fastmail.fm wrote: Hi, when I suspend my computer, KDE locks the session. This usually happens, when I close my laptop lid. When I open it again, it takes 1 to 20 seconds (seamingly random) untill the login screen appears. During this time, I just see a black screen and a mouse pointer (somewhere), but I cannot move it. If no X server is started, i.e. I'm on the shell, the computer always responds after a second or so when the laptop lid is opened again. Any ideas what causes this or how to fix it? Suspend is that when the computer isn't off just the things stays in memory, isn't? When the contents of the memory is writed to the disk and the machine is get off that is the hibernate function, isn't? It is possible that when you close the lid the contents of memory writed to the disk and reading this few hundred Mbyte - on my laptop KDE is eating ~800 Mbyte memory, the hungry Beast! :) - takes that long time what you mentioned? I'm not a big hacker just I'm thinking over it. :$ I haven't got the answer I'm afraid, but it happens the same here with a desktop machine - no lid. It takes up to 45 seconds for the screen to wake up! The PC starts up immediately, but the screen stays blank. In MSWindows, the screen becomes alive within seconds. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Cannot emerge x11-libs/qt-webkit-4.6.2-r1
For the last week or perhaps more, I have been unable to complete an emerge update of world because x11-libs/qt-webkit-4.6.2-r1 fails. I now have just the following ebuilds that cannot finish because of qt-webkit: Calculating dependencies... done! [ebuild U ] x11-libs/qt-webkit-4.6.2-r1 [4.6.2] USE=dbus%* exceptions kde (-aqua) -debug -pch 0 kB [ebuild U ] kde-base/ksplash-4.4.2-r1 [4.4.2] USE=mmx sse sse2 -3dnow (- altivec) (-aqua) -debug (-kdeenablefinal) (-kdeprefix) -xinerama 0 kB [ebuild R ] kde-base/libplasmagenericshell-4.4.2 USE=(-aqua) -debug (- kdeenablefinal) (-kdeprefix) -test% 0 kB [ebuild U ] kde-base/systemsettings-4.4.2-r1 [4.4.2] USE=handbook opengl usb (-aqua) -debug (-kdeenablefinal) (-kdeprefix) -xinerama 0 kB [ebuild U ] app-cdr/k3b-1.91.0_rc2 [1.70.0_beta1] USE=dvd encode flac handbook%* mad vorbis wav (-aqua) -debug -emovix -ffmpeg (-kdeenablefinal) - lame -musepack -musicbrainz -sndfile -sox -taglib -vcd LINGUAS=fr%* -ast% - be% -bg% -ca% -...@valencia% -cs% -csb% -da% -de% -el% -en_GB% -eo% -es% -et% - eu% -fi% -ga% -gl% -he% -hi% -hne% -hr% -hu% -is% -it% -ja% -km% -ko% -ku% - lt% -mai% -nb% -nds% -nl% -nn% -oc% -pa% -pl% -pt% -pt_BR% -ro% -ru% -se% -sk% -sl% -sv% -th% -tr% -uk% -zh_CN% -zh_TW% 0 kB Total: 5 packages (4 upgrades, 1 reinstall), Size of downloads: 0 kB Near the end of the emerge, the following error occurs: compiling .rcc/release-shared/qrc_WebKit.cpp rm -f libQtWebKit.so.4.6.2 libQtWebKit.so libQtWebKit.so.4 libQtWebKit.so.4.6 linking ../../../../lib/libQtWebKit.so.4.6.2 /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/../../../../x86_64-pc-linux- gnu/bin/ld:obj/release/HTMLParser.o: file format not recognized; treating as linker script /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/../../../../x86_64-pc-linux- gnu/bin/ld:obj/release/HTMLParser.o:1: syntax error collect2: ld returned 1 exit status make: *** [../../../../lib/libQtWebKit.so.4.6.2] Error 1 * ERROR: x11-libs/qt-webkit-4.6.2-r1 failed: * emake failed There was a thread on gentoo forums with this very error listed as solved (https://forums.gentoo.org/viewtopic.php?p=6262495), but the ccache solution suggested there has no effect on my experience of the problem. Anyone have a suggestion on how to proceed? Thanks, -- Jim signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Cannot emerge x11-libs/qt-webkit-4.6.2-r1
FEATURES='-distcc -ccache' MAKEOPTS='-j1' emerge ... Worked for me on multiple systems BillK - Original message - For the last week or perhaps more, I have been unable to complete an emerge update of world because x11-libs/qt-webkit-4.6.2-r1 fails. I now have just the following ebuilds that cannot finish because of qt-webkit: Calculating dependencies... done! [ebuild U ] x11-libs/qt-webkit-4.6.2-r1 [4.6.2] USE=dbus%* exceptions kde (-aqua) -debug -pch 0 kB [ebuild U ] kde-base/ksplash-4.4.2-r1 [4.4.2] USE=mmx sse sse2 -3dnow (- altivec) (-aqua) -debug (-kdeenablefinal) (-kdeprefix) -xinerama 0 kB [ebuild R ] kde-base/libplasmagenericshell-4.4.2 USE=(-aqua) -debug (- kdeenablefinal) (-kdeprefix) -test% 0 kB [ebuild U ] kde-base/systemsettings-4.4.2-r1 [4.4.2] USE=handbook opengl usb (-aqua) -debug (-kdeenablefinal) (-kdeprefix) -xinerama 0 kB [ebuild U ] app-cdr/k3b-1.91.0_rc2 [1.70.0_beta1] USE=dvd encode flac handbook%* mad vorbis wav (-aqua) -debug -emovix -ffmpeg (-kdeenablefinal) - lame -musepack -musicbrainz -sndfile -sox -taglib -vcd LINGUAS=fr%* -ast% - be% -bg% -ca% -...@valencia% -cs% -csb% -da% -de% -el% -en_GB% -eo% -es% -et% - eu% -fi% -ga% -gl% -he% -hi% -hne% -hr% -hu% -is% -it% -ja% -km% -ko% -ku% - lt% -mai% -nb% -nds% -nl% -nn% -oc% -pa% -pl% -pt% -pt_BR% -ro% -ru% -se% -sk% -sl% -sv% -th% -tr% -uk% -zh_CN% -zh_TW% 0 kB Total: 5 packages (4 upgrades, 1 reinstall), Size of downloads: 0 kB Near the end of the emerge, the following error occurs: compiling .rcc/release-shared/qrc_WebKit.cpp rm -f libQtWebKit.so.4.6.2 libQtWebKit.so libQtWebKit.so.4 libQtWebKit.so.4.6 linking ../../../../lib/libQtWebKit.so.4.6.2 /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/../../../../x86_64-pc-linux- gnu/bin/ld:obj/release/HTMLParser.o: file format not recognized; treating as linker script /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/../../../../x86_64-pc-linux- gnu/bin/ld:obj/release/HTMLParser.o:1: syntax error collect2: ld returned 1 exit status make: *** [../../../../lib/libQtWebKit.so.4.6.2] Error 1 * ERROR: x11-libs/qt-webkit-4.6.2-r1 failed: * emake failed There was a thread on gentoo forums with this very error listed as solved (https://forums.gentoo.org/viewtopic.php?p=6262495), but the ccache solution suggested there has no effect on my experience of the problem. Anyone have a suggestion on how to proceed? Thanks, -- Jim
Re: [gentoo-user] arping network profile issue
What I want is finding a gateway out with ARP, and then assign the correct gateway/route table, stuff in the configuration can be found in /etc/conf.d/net.example. BTW, what's IP level stuff meaning? thanks. 2010/5/7 Adam a...@jaftan.com.au On 05/06/10 03:35, Zhou Rui wrote: Hi folks, I setup a network interface to switch in two different network with different gateways using config_eth0=( arping ), and I can get gateway mac when use arping2 command directly. But the /etc/init.d/net.eth0 start always fails, can you help me to find the issue out? I cant understand what you're trying to achieve. IP will always do the arp for you so just set up the IP level stuff and whatever you're trying to do should work. dns_domain=vm config_eth0=( arping ) AFAICT This means you want to try to find a free address in the 169.254.x.x auto self configuration range - is that what you want? gateways_eth0=( 192.168.1.254,,192.168.1.114 192.168.1.1,,192.168.1.114 ) As none of those addresses are local, they cant be used as a gateway for a 169.254 address. -- BR, Zhou Rui
