Re: [Mageia-dev] Critical Samsung UEFI bug: "Booting Linux using UEFI can brick Samsung laptops"
Johnny A. Solbu skrev 1.2.2013 06:57: http://www.h-online.com/open/news/item/Booting-Linux-using-UEFI-can-brick-Samsung-laptops-1793958.html "Booting Linux using UEFI just once on various Samsung laptops is enough to permanently stop them working. Several reports have been posted on the Ubuntu bug tracker, but the problem is likely to also be present in other Linux distributions, as it appears to be caused by a kernel driver for Samsung laptops. Kernel developers are currently discussing a change which would disable the driver when booting via UEFI." Mageia is most likely also affected by this. Well, sort of... but it's not so "critical" as we dont support UEFI Installs / boots OOB so far, so people have to to many things manually to boot in UEFI mode. Nevertheless it is fixed upstream in 3.8-rc6, so cauldron/mga3 will be safe after I upload 3.8.0-0.rc6.1.mga3 (probably tonight)... And for mga2 it will be fixed in upcoming upstream 3.4.30. -- Thomas
Re: [Mageia-dev] x11-driver-video-qxl/qemu/libvirt (was Re: Please remove qemu, and qemu-img from Mageia 3.)
On Mon, 04 Feb 2013 18:09:52 -0500, Christiaan Welvaart wrote: On Sun, 3 Feb 2013, David W. Hodgins wrote: During testing of updates to qemu, and x11-driver-video-qxl, it has become very clear that no-one could possibly be using these packages, as they are so slow, as to be useless. Qemu (or rather each qemu-system-*) is an emulator at its core, so slowness is not a huge surprise. You probably wanted to run it in (fast) virtualization mode - use qemu-kvm for that (and the kvm module for your cpu must be loaded to get virtualization working). But running qemu directly is tiresome, try virt-manager - it works about as well as virtualbox even if I need to run it as root. I use virt-manager/qemu-kvm to build+test mga2 updates for iceape, only graphics (spice+vmvga) is slow (but better than vnc+cirrus). Thanks, I'll take a look at virt-manager. Regards, Dave Hodgins
Re: [Mageia-dev] Please remove qemu, and qemu-img from Mageia 3.
On Sun, 03 Feb 2013 04:16:54 -0500, Pascal Terjan wrote: On Sun, Feb 3, 2013 at 9:45 AM, David W. Hodgins wrote: During testing of updates to qemu, and x11-driver-video-qxl, it has become very clear that no-one could possibly be using these packages, as they are so slow, as to be useless. Try loading kvm module and selecting the fast drivers for network/disk/... lsmod|grep kvm kvm_amd55516 0 kvm 413942 1 kvm_amd Whether it's loaded or not doesn't seem to make any difference. If I add the -enable-kvm option, it fails with ... KVM not supported for this target No accelerator found! Checking under htop shows it's clearly cpu bound, using 2 of my 4 cores. The command I used to run qemu was ... qemu-system-x86_64 -cdrom "$Iso" -hda mageia"$Arch".qcow2 -boot d -net nic -net user,net=192.168.10.0/16,host=192.168.10.3 -m 4096 -vga qxl with the Iso and Arch variables set appropriately. Suggestions for faster disk/network options? Given that other people do find it useful, it's obvious there's something wrong either with the options I'm using (or not using), or my hardware or bios settings. Hopefully it's not the hardware. The cpu is an AMD FX(tm)-4170 Quad-Core Processor, with the following flags shown in /proc/cpuinfo ... flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr core arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold Regards, Dave Hodgins
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 2013-02-04 20:27 (GMT) Barry Jackson composed: Felix Miata wrote: http://fm.no-ip.com/Tmp/Linux/Mdv/menu.lst.04-cldrn-gx27b.txt http://fm.no-ip.com/Tmp/Linux/Mdv/etc-default-grub-cldrn-gx27b.txt Only error message I recall is about vga= from Grub2 before first kernel/init messages appear. I was referring to re-testing the use of grub2-menulst2cfg again, since it works perfectly here. If you truly get errors from the grub.cfg produced by it then I would like to report this upstream. I suspect there is something slightly unusual in your menu.lst that it can't handle, so we will need both menu.lst and the output .cfg, plus any error messages that may be useful. First I did urpmi --auto-update, which raised grub2 from -16 to -17. The new grub.cfg generated by grub2-menulst2cfg is identical to the last one it made: http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.05-cldrn-gx27b.txt The two links above are unchanged. Selecting the first stanza, as before, causes: "... doing fast boot mkdir: cannot create directory '/run': File exists ... udevd[99]: could not find module by name='e1000' WARNING: Deprecated config file /etc/modprobe.conf, ... ...resume device not found (ignoring) Waiting for device /dev/root to appear...Could not find /dev/root ... Want me to fall back to /dev/by-id-yada-part21." The root device is in fact /dev/by-id-yada-part22. Since your comments earlier I have decided to split out the theme into a separate package, so that a minimal installation using grub2 will not pull in the font, image etc. I have pushed a new version that Suggests: os-prober in the meantime. urpme os-prober didn't try to remove grub2 this time. :-) So, in future an install of grub2 with --no-suggests will be without a theme or os-prober, and perform as per the modifications I suggested above. Thanks for your constructive comments Felix, :-) -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] x11-driver-video-qxl/qemu/libvirt (was Re: Please remove qemu, and qemu-img from Mageia 3.)
Op dinsdag 5 februari 2013 00:09:52 schreef Christiaan Welvaart: > On Sun, 3 Feb 2013, David W. Hodgins wrote: > > During testing of updates to qemu, and x11-driver-video-qxl, > > it has become very clear that no-one could possibly be using > > these packages, as they are so slow, as to be useless. > > Qemu (or rather each qemu-system-*) is an emulator at its core, so > slowness is not a huge surprise. You probably wanted to run it in (fast) > virtualization mode - use qemu-kvm for that (and the kvm module for your > cpu must be loaded to get virtualization working). But running qemu > directly is tiresome, try virt-manager - it works about as well as > virtualbox even if I need to run it as root. I use virt-manager/qemu-kvm > to build+test mga2 updates for iceape, only graphics (spice+vmvga) is slow > (but better than vnc+cirrus). > > Unfortunately people keep updating libvirt, apparently without testing it > - now it is broken again in cauldron. I need to kill all the qemu-system-* > and qemu-kvm that libvirtd starts one by one before virt-manager can > connect. > > > There are many problems with xorg crashing, mouse pointer not > > being where the pointer is shown, etc. These bugs are described > > in https://bugs.mageia.org/show_bug.cgi?id=8938 > > A month ago I updated the spice packages; I also tried to update > x11-driver-video-qxl (which is part of spice AFAIK) but it did not work at > all. So if you ask for *that* package to be removed, fine with me. > > > Christiaan no, please,... get it working instead :-)
[Mageia-dev] x11-driver-video-qxl/qemu/libvirt (was Re: Please remove qemu, and qemu-img from Mageia 3.)
On Sun, 3 Feb 2013, David W. Hodgins wrote: During testing of updates to qemu, and x11-driver-video-qxl, it has become very clear that no-one could possibly be using these packages, as they are so slow, as to be useless. Qemu (or rather each qemu-system-*) is an emulator at its core, so slowness is not a huge surprise. You probably wanted to run it in (fast) virtualization mode - use qemu-kvm for that (and the kvm module for your cpu must be loaded to get virtualization working). But running qemu directly is tiresome, try virt-manager - it works about as well as virtualbox even if I need to run it as root. I use virt-manager/qemu-kvm to build+test mga2 updates for iceape, only graphics (spice+vmvga) is slow (but better than vnc+cirrus). Unfortunately people keep updating libvirt, apparently without testing it - now it is broken again in cauldron. I need to kill all the qemu-system-* and qemu-kvm that libvirtd starts one by one before virt-manager can connect. There are many problems with xorg crashing, mouse pointer not being where the pointer is shown, etc. These bugs are described in https://bugs.mageia.org/show_bug.cgi?id=8938 A month ago I updated the spice packages; I also tried to update x11-driver-video-qxl (which is part of spice AFAIK) but it did not work at all. So if you ask for *that* package to be removed, fine with me. Christiaan
Re: [Mageia-dev] Freeze push: nautilus-dropbox
Le 04/02/2013 20:40, Damien Lallement a écrit : Please push 1.6.0 (now 1.4.0) as with this new release, it fixes the issue of libz.so included as a static library. So README.urpmi no longuer needed to explain how to remove this file. Done. -- BOFH excuse #223: The lines are all busy (busied out, that is -- why let them in to begin with?).
Re: [Mageia-dev] Freeze push: orage
Le 04/02/2013 20:00, Jani Välimaa a écrit : Hi, please push new orage. It's mainly a bugfix release with some enhancements and translation updates [1]. Done. -- BOFH excuse #268: Neutrino overload on the nameserver
Re: [Mageia-dev] freeze push: perl-Glib-Object-Introspection
Le 04/02/2013 20:38, Thierry Vignaud a écrit : Hi Please let in perl-Glib-Object-Introspection. It's bug fixes, most of whose we already have. Done. -- BOFH excuse #159: Stubborn processes
Re: [Mageia-dev] packages not rebuilt since Mageia 1 with old src.rpm building fine
On Mon, Feb 4, 2013 at 6:08 PM, Pascal Terjan wrote: > Out of the 35 packages not rebuilt since Mageia 1, here is a list of > the 8 which are not detected by autobuild as the old src.rpm builds > fine but not the version in svn or the package is rejected > > New version in svn that was never uploaded > == > > checklink-4.2.1-7.mga1.src.rpm: > - updated by dams to 4.81 on 2012-06-19 > - never uploaded as it requires perl(CSS::DOM) which is not available > > fbreader-0.12.10-5.mga1.src.rpm: > - updated by fwang to 0.99.2 on 2012-09-14 > - never uploaded, I don't know why > > kaption-0.0.9-1.mga1.src.rpm: > - updated to 0.1.1 by dglent on 2012-09-09 > - never uploaded, I don't know why > > transfugdrake-1.9.4-1.mga3.src.rpm: > - updated by ennael to 1.9.5 on 2012-05-02 > - never uploaded, I don't know why > > Rejected, need an exception in rpmlint config > = > > nagios-check_rsync-1.02-5.mga1.src.rpm: > - unexpanded-macro URL %2F2094 > > nagios-check_syncrepl-20080409-8.mga1.src.rpm: > - unexpanded-macro URL %2F2477 > > php-pear-Testing_Selenium-0.3.1-8.mga3.src.rpm: > - php-pear-Testing_Selenium.noarch: W: unexpanded-macro > /usr/share/doc/php-pear-Testing_Selenium/docs/Documentation/26d3399f63abd43a7d72f8c21440dcb0/%%239^%%239105369^footer.tpl.php > %%239 > (and many more files) > > Fails to build, needs to be fixed > = > > xmldb-api-0.1-0.1.2001cvs.1.2.5.mga3.src.rpm: > - requires omquery which seems to no longer exist > - required by ws-jaxme, which is required by plenty of packages > (omegat cxf-xjc-utils dom4j resteasy xmlrpc-common eclipse-mylyn > eclipse-mylyn-builds-hudson omegat cxf-xjc-utils dom4j resteasy > xmlrpc-common eclipse-mylyn-builds-hudson eclipse-mylyn) Actually I had missed the snapshot date change On 2011-06-29, it was updated from 2001 to 20041010 by gil, changing the spec a lot including a new dependency on omquery which was never uploaded The package is dead in Fedora and they removed the support for it in ws-jaxme with http://pkgs.fedoraproject.org/cgit/ws-jaxme.git/tree/ws-jaxme-remove-xmldb.patch
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 2013-02-04 12:23 (GMT) Barry Jackson composed: Felix Miata wrote: On 2013-02-02 10:08 (GMT) Barry Jackson composed: Felix Miata wrote: 3-Grub2 menu uses same awful spindly-looking font responsible in large part for my distaste for *buntu Yes could be a lot better, but it's mainly a choice based on licensing, probably will be improved in the future. What's wrong with nice legible BIOS native fonts? Try commenting out the line in /etc/defaults/grub #GRUB_THEME=... Done on my first edit to the file. and also temporarily rename /boot/grub2/fonts Will try to remember if again presented with graphics mode fonts, which I'm not currently getting due to either GRUB_GFXPOAYLOAD_text and/or GRUB_TERMINAL_OUTPUT=console and/or grub2-menulst2cfg. Run "grub2-mkconfig -o /boot/grub2/grub.cfg" after changing anything in /etc/deafult/grub before rebooting. Is that better for you? Will have to reserve that for after figuring out how to get stanzas sorted acceptably. For now grub2-menulst2cfg as corrected is working better. Even better is using the master bootloader to load kernel and initrd directly, but here I'm trying out Grub2 now that it has advanced to v1.0 status. 6-post ESC, startup messages are inappropriately tiny Sounds like the same issue I used to have when I was using nvidia graphics with nouveau. Using intel I don't see this. # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) Hmm - dunno then - I do see a drop in size which appears to happen after grub2 has handed over to the kernel. I know what's happening, figured out within several months of the kernel devs unleashing KMS into the wild. KMS responds to video= for selecting mode to use for tty framebuffers. But before KMS initializes, the kernel responds to vga= if present as it has for over a decade, replacing the default 80x25 mode with whatever mode the vga= parameter corresponds to. Absent cmdline parameter for graphics mode init theme, quiet, or other means to hide init messages, ttys are set to any supplied vga= framebuffer mode. Shortly after the vga= response, KMS kicks in and switches to the video= mode if present. If no valid video= mode is present, KMS initializes with the EDID-provided PreferredMode, which here would be specified as 1600x1200, corresponding to vga=0x31e (16 bit) or 0x31f (24 bit) if the gfxchip was unsupported by KMS. Initial Grub2 installation isn't preconfigured with with any video=, so without being kicked into a graphics init mode by Plymouth or otherwise, first tty drawing is in 80x25 mode, shortly followed by KMS initializing EDID PreferredMode 1600x1200, which is what results in the tiny text, 75 rows in a 12" vertical space, or about .16"/4.064mm per row, a bit over 11pt, which for me is about 72% of optimal height produced by 1152x864. I use a "bigger" display (21" nominal CRT) to make stuff bigger, not fit more stuff. 7-tty text is too tiny to use (same as startup messages; screen's preferred mode 1600x1200 used instead of legible mode 1152x864) Probably configurable in /etc/defaults/grub but off hand I don't know the variable name - should be in the maunual somewhere. I'm suspecting this is not a grub2 issue but I may be wrong. It's not directly. KMS is using whatever nominal size font is preconfigured for the framebuffers. Whatever physical size font results depends for its context on the EDID-provided video mode and the display's physical size. Framebuffer fonts, except on *buntu, have been preconfigured the same across all other distros I've used AFAICR since before I first began using Linux last century. Grub2's part is that there isn't an installation option here (that I remember) for the user to specify Grub2 pass a video= cmdline option if he doesn't want the EDID PreferredMode used on the ttys. KMS has been around so long I've already forgotten how Mandriva's installer was dealing with the vga= option that was the usual pre-KMS method of sizing framebuffer text. Pre-widescreen displays, vga=791 was pretty typical. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] musical session locations (was: Grub2 vs. Grub Leg...)
On 2013-02-04 12:23 (GMT) Barry Jackson composed: Felix Miata wrote: grub2-menulst2cfg picked up the ones that work in Grub Legacy (vga= ((http://www.kernel.org/doc/Documentation/kernel-parameters.txt)) & video= ((http://www.kernel.org/doc/Documentation/fb/modedb.txt))), which are kernel parameters. They do the same thing loaded via Grub2 as when loaded via Grub Legacy. 8-KDM is on tty2, the location I reserve for certain class of recurring activities, instead of where expected on tty7 Dunno - I have never seen this. Booting with 3 on cmdline and later doing startx or init 5? I think that startx and init are deprecated in favour of proper systemd commands now. Init at shell prompt is shorthand/alias for insanely long non-memorable systemd replacements for telinit/init. Startx may be deprecated, but no one who's told me so has suggested what's supposed to replace it to get 2nd, 3rd & more X sessions going on :1, :2, etc. Startkde never seems to work at a tty prompt. When I'm testing what I often test, startx saves an immense amount of time over going though a login manager, which often wasn't working and why I was using startx in the first place. On current boot I used 3 on cmdline, logged in on tty2 & tty3, did startx on tty3, and found X is running on tty3. On exiting the X session I did init 5. That put KDM on tty1. On openSUSE & Fedora the problem is essentially the same, e.g.: https://bugzilla.novell.com/show_bug.cgi?id=768788 I don't think this is grub2 related. Of course it's not. It's fallout from incomplete migration from sysvinit to systemd. Systemd is designed to not do a significant number of things that sysvinit did do, so things are broken that haven't been modified to do what the functioning init system no longer does, or account for everything the replacement init system does differently. Graphical desktop should default to tty1 now I have predfined uses for ttys 1-6. 7, 8 & 9 are where my X sessions belong, not on 1 and random others making me guess each time what lives where. Tty1 especially needs not to be where X goes, because it's where in help forums everyone dealing with non-working X is told to login to do this and do that to troubleshoot. , however I have seen an issue where it moves to tty7 after stopping and re-starting prefdm.service. I have not checked this recently. More about what systemd doesn't do that init did. Initab reserved ttys 1-6 leaving 7+ free for X sessions. Systemd reserves none and doesn't even start a getty until switch to a tty is made. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 04/02/13 19:18, Felix Miata wrote:
On 2013-02-04 14:27 (GMT) Barry Jackson composed:
Felix Miata wrote:
Nice in theory, but the root device is off by -1. Default menu.lst
cmdline includes root=LABEL=22cauldrn instead of UUID or device name,
which is apparently disregarded by grub 2.
Maybe a limitation of legacy_kernel.
Normally to use labels in grub2 the 'search' command is used without any
reference to the device assignment.
Like:-
menuentry 'Mageia-2 multiboot' {
search --no-floppy --label --set=root mageia-2
multiboot /boot/grub2/i386-pc/core.img
}
menuentry 'Cauldron defkernel' {
legacy_kernel '(hd0,22)/boot/vmlinuz' '(hd0,21)/boot/vmlinuz'
'root=LABEL=22cauldrn' 'splash=verbose' 'noresume' 'video=1152x864'
'vga=794' '3' ''
legacy_initrd '(hd0,22)/boot/initrd' '(hd0,21)/boot/initrd'
}
It works when I s/hd0,21/hd0,22/g.
That syntax is apparently correct, as legacy_kernel needs to know what
the original legacy command was.
I have tested here in a clean mga3 installation and it works for me.
Please re-test and if it fails again please attach the original menu.lst
and the resulting grub.cfg along with any error messages.
It's entirely unclear what "re-test" here means, unless maybe by
incorporating your immediately preceding thread response. Current
behavior of Grub2 menu overall and first grub.cfg stanza is acceptable
having used/using the following:
http://fm.no-ip.com/Tmp/Linux/Mdv/menu.lst.04-cldrn-gx27b.txt
http://fm.no-ip.com/Tmp/Linux/Mdv/etc-default-grub-cldrn-gx27b.txt
http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.06-cldrn-gx27b.txt
Only error message I recall is about vga= from Grub2 before first
kernel/init messages appear.
I was referring to re-testing the use of grub2-menulst2cfg again, since
it works perfectly here.
If you truly get errors from the grub.cfg produced by it then I would
like to report this upstream. I suspect there is something slightly
unusual in your menu.lst that it can't handle, so we will need both
menu.lst and the output .cfg, plus any error messages that may be useful.
Since your comments earlier I have decided to split out the theme into a
separate package, so that a minimal installation using grub2 will not
pull in the font, image etc.
I have pushed a new version that Suggests: os-prober in the meantime.
So, in future an install of grub2 with --no-suggests will be without a
theme or os-prober, and perform as per the modifications I suggested above.
Thanks for your constructive comments Felix,
Barry
Re: [Mageia-dev] perl-doc need by POD::Usage
On Mon, 2013-02-04 at 21:15 +0100, Olivier Thauvin wrote: > If perl must require perl-doc, the split is just useless. > Yes, you should be able to install perl without the doc. Having said that, a possible reason for the split is that they are updated in differing cycles. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Re: [Mageia-dev] perl-doc need by POD::Usage
* Thierry Vignaud (thierry.vign...@gmail.com) wrote: > On 4 February 2013 18:17, Olivier Thauvin wrote: > > It seems perl has been splited into perl and perl-doc, however perl > > package provide POD::Usage which require perldoc to work: > > where were you for the last decade? > > > $ rt --help > > Can't exec "/usr/bin/perldoc": Aucun fichier ou dossier de ce type at > > /usr/lib/perl5/5.16.2/Pod/Usage.pm line 583. > > > > $ urpmf /usr/bin/perldoc > > perl-doc:/usr/bin/perldoc > > > > In order to have POD::Usage (provided by perl itself) perldoc must be > > move into perl package. > > No. > This package must just require it. This package is perl itself: rpm -qf /usr/lib/perl5/5.16.2/Pod/Usage.pm perl-5.16.2-2.mga3 If perl must require perl-doc, the split is just useless. ++ -- Olivier Thauvin CNRS - LATMOS ♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖ pgpXQwhEWObMp.pgp Description: PGP signature
[Mageia-dev] Freeze push: nautilus-dropbox
Please push 1.6.0 (now 1.4.0) as with this new release, it fixes the issue of libz.so included as a static library. So README.urpmi no longuer needed to explain how to remove this file. Cf mga#7695 and mga#3641 Thanks! Dams -- Damien Lallement twitter: damsweb - IRC: damsweb/coincoin
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 2013-02-04 14:27 (GMT) Barry Jackson composed:
Felix Miata wrote:
Nice in theory, but the root device is off by -1. Default menu.lst
cmdline includes root=LABEL=22cauldrn instead of UUID or device name,
which is apparently disregarded by grub 2.
Maybe a limitation of legacy_kernel.
Normally to use labels in grub2 the 'search' command is used without any
reference to the device assignment.
Like:-
menuentry 'Mageia-2 multiboot' {
search --no-floppy --label --set=root mageia-2
multiboot /boot/grub2/i386-pc/core.img
}
menuentry 'Cauldron defkernel' {
legacy_kernel '(hd0,22)/boot/vmlinuz' '(hd0,21)/boot/vmlinuz'
'root=LABEL=22cauldrn' 'splash=verbose' 'noresume' 'video=1152x864'
'vga=794' '3' ''
legacy_initrd '(hd0,22)/boot/initrd' '(hd0,21)/boot/initrd'
}
It works when I s/hd0,21/hd0,22/g.
That syntax is apparently correct, as legacy_kernel needs to know what
the original legacy command was.
I have tested here in a clean mga3 installation and it works for me.
Please re-test and if it fails again please attach the original menu.lst
and the resulting grub.cfg along with any error messages.
It's entirely unclear what "re-test" here means, unless maybe by
incorporating your immediately preceding thread response. Current behavior of
Grub2 menu overall and first grub.cfg stanza is acceptable having used/using
the following:
http://fm.no-ip.com/Tmp/Linux/Mdv/menu.lst.04-cldrn-gx27b.txt
http://fm.no-ip.com/Tmp/Linux/Mdv/etc-default-grub-cldrn-gx27b.txt
http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.06-cldrn-gx27b.txt
Only error message I recall is about vga= from Grub2 before first kernel/init
messages appear.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
[Mageia-dev] Freeze push: orage
Hi, please push new orage. It's mainly a bugfix release with some enhancements and translation updates [1]. [1] http://git.xfce.org/apps/orage/diff/NEWS?id=94cc6faf80df8e017567a2b67710d92dac9c4050
Re: [Mageia-dev] perl-doc need by POD::Usage
On 4 February 2013 18:17, Olivier Thauvin wrote: > It seems perl has been splited into perl and perl-doc, however perl > package provide POD::Usage which require perldoc to work: where were you for the last decade? > $ rt --help > Can't exec "/usr/bin/perldoc": Aucun fichier ou dossier de ce type at > /usr/lib/perl5/5.16.2/Pod/Usage.pm line 583. > > $ urpmf /usr/bin/perldoc > perl-doc:/usr/bin/perldoc > > In order to have POD::Usage (provided by perl itself) perldoc must be > move into perl package. No. This package must just require it.
[Mageia-dev] packages not rebuilt since Mageia 1 with old src.rpm building fine
Out of the 35 packages not rebuilt since Mageia 1, here is a list of the 8 which are not detected by autobuild as the old src.rpm builds fine but not the version in svn or the package is rejected New version in svn that was never uploaded == checklink-4.2.1-7.mga1.src.rpm: - updated by dams to 4.81 on 2012-06-19 - never uploaded as it requires perl(CSS::DOM) which is not available fbreader-0.12.10-5.mga1.src.rpm: - updated by fwang to 0.99.2 on 2012-09-14 - never uploaded, I don't know why kaption-0.0.9-1.mga1.src.rpm: - updated to 0.1.1 by dglent on 2012-09-09 - never uploaded, I don't know why transfugdrake-1.9.4-1.mga3.src.rpm: - updated by ennael to 1.9.5 on 2012-05-02 - never uploaded, I don't know why Rejected, need an exception in rpmlint config = nagios-check_rsync-1.02-5.mga1.src.rpm: - unexpanded-macro URL %2F2094 nagios-check_syncrepl-20080409-8.mga1.src.rpm: - unexpanded-macro URL %2F2477 php-pear-Testing_Selenium-0.3.1-8.mga3.src.rpm: - php-pear-Testing_Selenium.noarch: W: unexpanded-macro /usr/share/doc/php-pear-Testing_Selenium/docs/Documentation/26d3399f63abd43a7d72f8c21440dcb0/%%239^%%239105369^footer.tpl.php %%239 (and many more files) Fails to build, needs to be fixed = xmldb-api-0.1-0.1.2001cvs.1.2.5.mga3.src.rpm: - requires omquery which seems to no longer exist - required by ws-jaxme, which is required by plenty of packages (omegat cxf-xjc-utils dom4j resteasy xmlrpc-common eclipse-mylyn eclipse-mylyn-builds-hudson omegat cxf-xjc-utils dom4j resteasy xmlrpc-common eclipse-mylyn-builds-hudson eclipse-mylyn)
[Mageia-dev] perl-doc need by POD::Usage
Hi, It seems perl has been splited into perl and perl-doc, however perl package provide POD::Usage which require perldoc to work: $ rt --help Can't exec "/usr/bin/perldoc": Aucun fichier ou dossier de ce type at /usr/lib/perl5/5.16.2/Pod/Usage.pm line 583. $ urpmf /usr/bin/perldoc perl-doc:/usr/bin/perldoc In order to have POD::Usage (provided by perl itself) perldoc must be move into perl package. Regards. -- Olivier Thauvin CNRS - LATMOS ♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖ pgpyeJIQ1gu1Z.pgp Description: PGP signature
Re: [Mageia-dev] urpmi counts gone askew
On 4 February 2013 15:36, Barry Jackson wrote: >> Not sure this is worth a bug report, since I doubt I could reproduce >> it, but check out the "package number/total" output in this morning's >> cauldron update: >> > > Yes - same here :\ > > 44/78: libreoffice-kde > # > removing upgraded package libreoffice-base-4.0.0.2-2.mga3.x86_64 >18/-24: libreoffice-base > > then afer a couple of transactions it corrects itself for a while and then > after another few transactions it goes haywire again - etc... That's a side effect to having progress for erasing packages too. There's erase in transactions too when upgrading as rpm make it be an install + 1 erasure. I'll dcommit soon
Re: [Mageia-dev] urpmi counts gone askew
On 04/02/13 14:19, Frank Griffin wrote: Not sure this is worth a bug report, since I doubt I could reproduce it, but check out the "package number/total" output in this morning's cauldron update: Yes - same here :\ 44/78: libreoffice-kde # removing upgraded package libreoffice-base-4.0.0.2-2.mga3.x86_64 18/-24: libreoffice-base then afer a couple of transactions it corrects itself for a while and then after another few transactions it goes haywire again - etc...
Re: [Mageia-dev] urpmi counts gone askew
On Mon, Feb 4, 2013 at 2:19 PM, Frank Griffin wrote: > Not sure this is worth a bug report, since I doubt I could reproduce it, > but check out the "package number/total" output in this morning's cauldron > update: Just a guess, can it be old package removal which are now displayed as installations but with a negative total and another counter?
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 03/02/13 18:05, Felix Miata wrote:
Nice in theory, but the root device is off by -1. Default menu.lst
cmdline includes root=LABEL=22cauldrn instead of UUID or device name,
which is apparently disregarded by grub 2.
Maybe a limitation of legacy_kernel.
Normally to use labels in grub2 the 'search' command is used without any
reference to the device assignment.
Like:-
menuentry 'Mageia-2 multiboot' {
search --no-floppy --label --set=root mageia-2
multiboot /boot/grub2/i386-pc/core.img
}
menuentry 'Cauldron defkernel' {
legacy_kernel '(hd0,22)/boot/vmlinuz' '(hd0,21)/boot/vmlinuz'
'root=LABEL=22cauldrn' 'splash=verbose' 'noresume' 'video=1152x864'
'vga=794' '3' ''
legacy_initrd '(hd0,22)/boot/initrd' '(hd0,21)/boot/initrd'
}
It works when I s/hd0,21/hd0,22/g.
That syntax is apparently correct, as legacy_kernel needs to know what
the original legacy command was.
I have tested here in a clean mga3 installation and it works for me.
Please re-test and if it fails again please attach the original menu.lst
and the resulting grub.cfg along with any error messages.
Barry
[Mageia-dev] urpmi counts gone askew
Not sure this is worth a bug report, since I doubt I could reproduce it, but check out the "package number/total" output in this morning's cauldron update: Preparing... # 1/102: git-core # 2/102: perl-Git # 3/102: git-svn # 4/102: git-email # 5/102: jakarta-commons-httpclient # 6/102: axis # 7/102: git # 8/102: git-cvs # 9/102: git-core-oldies # 10/102: git-prompt # 11/102: git-arch # 12/102: gitk # 13/102: lib64pcsclite1 # 1/-76: git # 2/-76: git-svn # 3/-76: git-email # 4/-76: git-cvs # 5/-76: gitk # 6/-76: git-arch # 7/-76: git-prompt # 8/-76: git-core-oldies # 9/-76: git-core # 10/-76: perl-Git # 11/-76: axis # 12/-76: jakarta-commons-httpclient # 13/-76: lib64pcsclite1 # installing lib64gmpxx4-5.1.0-1.mga3.x86_64.rpm squid-3.2.7-1.mga3.x86_64.rpm lib64gmp10-5.1.0-1.mga3.x86_64.rpm from /mnt/cauldron/x86_64/media/core/release Preparing... # 14/102: lib64gmp10 # 15/102: lib64gmpxx4 # 16/102: squid # 14/-96: lib64gmpxx4 # 15/-96: lib64gmp10 # 16/-96: squid # installing autocorr-es-4.0.0.3-1.mga3.noarch.rpm libreoffice-wiki-publisher-4.0.0.3-1.mga3.x86_64.rpm libreoffice-java-common-4.0.0.3-1.mga3.x86_64.rpm libreoffice-math-4.0.0.3-1.mga3.x86_64.rpm libreoffice-xsltfilter-4.0.0.3-1.mga3.x86_64.rpm libreoffice-langpack-es-4.0.0.3-1.mga3.x86_64.rpm libreoffice-langpack-it-4.0.0.3-1.mga3.x86_64.rpm libreoffice-kde-4.0.0.3-1.mga3.x86_64.rpm libreoffice-langpack-en-4.0.0.3-1.mga3.x86_64.rpm libreoffice-langpack-fr-4.0.0.3-1.mga3.x86_64.rpm libreoffice-base-4.0.0.3-1.mga3.x86_64.rpm libreoffice-graphicfilter-4.0.0.3-1.mga3.x86_64.rpm autocorr-en-4.0.0.3-1.mga3.noarch.rpm libreoffice-pdfimport-4.0.0.3-1.mga3.x86_64.rpm libreoffice-emailmerge-4.0.0.3-1.mga3.x86_64.rpm x11-driver-input-synaptics-1.6.3-1.mga3.x86_64.rpm libreoffice-calc-4.0.0.3-1.mga3.x86_64.rpm libreoffice-ure-4.0.0.3-1.mga3.x86_64.rpm libreoffice-ogltrans-4.0.0.3-1.mga3.x86_64.rpm autocorr-de-4.0.0.3-1.mga3.noarch.rpm libreoffice-impress-4.0.0.3-1.mga3.x86_64.rpm autocorr-it-4.0.0.3-1.mga3.noarch.rpm libreoffice-draw-4.0.0.3-1.mga3.x86_64.rpm libreoffice-presentation-minimizer-4.0.0.3-1.mga3.x86_64.rpm libreoffice-writer-4.0.0.3-1.mga3.x86_64.rpm autocorr-fr-4.0.0.3-1.mga3.noarch.rpm libreoffice-core-4.0.0.3-1.mga3.x86_64.rpm libreoffice-opensymbol-fonts-4.0.0.3-1.mga3.noarch.rpm libreoffice-report-builder-4.0.0.3-1.mga3.x86_64.rpm libreoffice-langpack-de-4.0.0.3-1.mga3.x86_64.rpm libreoffice-pyuno-4.0.0.3-1.mga3.x86_64.rpm from /mnt/cauldron/x86_64/media/core/release Preparing... # 17/102: libreoffice-ure # 18/102: libreoffice-opensymbol-fonts # 19/102: autocorr-fr # 20/102: autocorr-it # 21/102: autocorr-de # 22/102: autocorr-en # 23/102: autocorr-es # 24/102: libreoffice-writer # 25/102: libreoffice-core # 26/102: libreoffice-langpack-es # 27/102: libreoffice-graphicfilter #
Re: [Mageia-dev] proftpd - why was mdv package imported over ours nuking our changes???
2013/1/13 Colin Guthrie > 'Twas brillig, and Bersuit Vera at 12/01/13 19:57 did gyre and gimble: > > Hi all > > > > Excuse my mentor, Juancho alert me, but trust too much on me > > Maybe I trust too much in other distros > > I would like to work with you to learn more about the packaging of > > servers (systemctl etc...) > > I ask thousand excuses again. > > No need for a thousand, just one will do :) > > Like I say, don't worry too much - mistakes happen when learning and we > all learn more from a mistake than anything else :) > > I would like to felicitate you Colin for the way and the quality when handling this. Specially in open source communities, it should be the common behavior, but unfortunately, it does nt happens... always and everywhere. I am proud that you are a member of our community and that i am a member of it too. ;) -- Dimitrios Glentadakis
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 03/02/13 18:05, Felix Miata wrote:
On 2013-02-02 10:08 (GMT) Barry Jackson composed:
Felix Miata wrote:
Good start:
1-/boot/grub2/i386-pc/core.img in a Grub Legacy stanza succeeds
Not good from then on:
1-Grub2 error message due to not finding some png file
You removed the png by using --no-suggests
One cannot remove what is not present. What I did was block installation
of packages that the grub2 package does not declare to be required.
Grub2 should not be configured to show user an error resulting from its
own installation misconfiguration. That looks like a bug.
2-25 item Grub 2.00 menu (grub.cfg:
http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.gx27b-cauldron3-1.txt ).
After selecting a selection from a master bootloader, there's no good
reason to see similar selections as in the previous menu unrelated to
the chosen selection. IOW, when not a master bootloader (i.e.
"chainloaded" via core.img, only Mageia entries attributable to selected
filesystem hosting core.img should be in this menu.
If that is what you want then:-
# urpme os-prober
Why was it installed when I did 'urpmi --no-suggests grub2' if it's not
required?
# urpme os-prober
To satisfy dependencies, the following 2 packages will be removed...
grub2-yada
os-prober-yada...
Right, sorry - I agree - I never really envisaged anyone not wanting
os-prober installed, however it should really be a Suggests - I will
change that.
However I should have pointed out that it can be disabled in
/etc/defaults/grub with
GRUB_DISABLE_OS_PROBER=true
3-Grub2 menu uses same awful spindly-looking font responsible in large
part for my distaste for *buntu
Yes could be a lot better, but it's mainly a choice based on licensing,
probably will be improved in the future.
What's wrong with nice legible BIOS native fonts?
Try commenting out the line in /etc/defaults/grub
#GRUB_THEME=...
and also temporarily rename /boot/grub2/fonts
Run "grub2-mkconfig -o /boot/grub2/grub.cfg"
after changing anything in /etc/deafult/grub before rebooting.
Is that better for you?
4-default menu selection for Cauldron causes this cmdline:
BOOT_IMAGE=/boot/vmlinuz-prv
root=UUID=bbe8a402-5fb1-4247-b372-5bb6cff4e18c ro splash
which is nothing like the default Grub Legacy menu stanza's cmdline
result:
root=LABEL=22cauldrn splash=verbose noresume video=1152x864
vga=794 3
obviously caused by Grub2 installation disregarding content of
pre-existing menu.lst
grub2 does not pay any attention to legacy menu.lst - it's a totally
different, unrelated bootloader.
If you want grub2 to use an existing legacy menu.lst then you can use
grub2-menulst2cfg tool to create a grub.cfg from menu.lst.
Usage: grub2-menulst2cfg [INFILE [OUTFILE]]
Nice in theory, but the root device is off by -1. Default menu.lst
cmdline includes root=LABEL=22cauldrn instead of UUID or device name,
which is apparently disregarded by grub 2.
menuentry 'Cauldron defkernel' {
legacy_kernel '(hd0,22)/boot/vmlinuz' '(hd0,21)/boot/vmlinuz'
'root=LABEL=22cauldrn' 'splash=verbose' 'noresume' 'video=1152x864'
'vga=794' '3' ''
legacy_initrd '(hd0,22)/boot/initrd' '(hd0,21)/boot/initrd'
}
It works when I s/hd0,21/hd0,22/g.
That looks like an upstream bug - I will investigate.
5-semi-legible blue on black graphical progress bar instead of normal
complement of startup messages when splash=verbose
The font colours were chosen to complement the background image which
you chose not to install.
I saw no fonts in that progress bar. I asked for no progress bar.
OK remove the theme as above and set:
GRUB_CMDLINE_LINUX="3"
... for runlevel 3 and just remove the "splash" on that line for verbose
output.
6-post ESC, startup messages are inappropriately tiny
Sounds like the same issue I used to have when I was using nvidia
graphics with nouveau.
Using intel I don't see this.
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02)
Hmm - dunno then - I do see a drop in size which appears to happen after
grub2 has handed over to the kernel.
7-tty text is too tiny to use (same as startup messages; screen's
preferred mode 1600x1200 used instead of legible mode 1152x864)
Probably configurable in /etc/defaults/grub but off hand I don't know
the variable name - should be in the maunual somewhere.
I'm suspecting this is not a grub2 issue but I may be wrong.
grub2-menulst2cfg picked up the ones that work in Grub Legacy (vga=
((http://www.kernel.org/doc/Documentation/kernel-parameters.txt)) &
video= ((http://www.kernel.org/doc/Documentation/fb/modedb.txt))), which
are kernel parameters. They do the same thing loaded via Grub2 as when
loaded via Grub Legacy.
8-KDM is on tty2, the location I reserve for certain class of recurring
activities, instead of where expected on tty7
Dunno - I have never seen this.
Booting with 3 on cmdline and later doing startx or i
Re: [Mageia-dev] Freeze push: gtkhtml 4.6.3
Le 04/02/2013 11:36, Olav Vitters a écrit : Small bugfix release. Seems harmless. Done. -- BOFH excuse #183: filesystem not big enough for Jumbo Kernel Patch
[Mageia-dev] Freeze push: gtkhtml 4.6.3
Small bugfix release. Seems harmless. -- Regards, Olav --- Begin Message --- About gtkhtml = HTML rendering and editing library News Bug Fixes: Bug 689476 - Slow composer open (emoticon and color widget leaks) (Milan Crha) Other Changes: * Fix a memory leak (GtkhtmlFaceAction instance) (Milan Crha) Translations: Rafael Ferreira (pt_BR) ChangeLog = http://download.gnome.org/sources/gtkhtml/4.6/gtkhtml-4.6.3.changes (1.42K) Download http://download.gnome.org/sources/gtkhtml/4.6/gtkhtml-4.6.3.tar.xz (1.01M) sha256sum: 9d655015247dfacf3f153bb6e14bd1bed3a228e7954141771dfe9dca53ac1d58 ___ ftp-release-list mailing list ftp-release-l...@gnome.org https://mail.gnome.org/mailman/listinfo/ftp-release-list --- End Message ---
[Mageia-dev] freeze push: libupnpn
"dear and mighty admins, could you please push latest libupnp release, fixing an impressive number of 8 exploits" ? "OK, guy, be my guest" -- BOFH excuse #84: Someone is standing on the ethernet cable, causing a kink in the cable
Re: [Mageia-dev] freeze push: rpm-4.11.0.1
Le 03/02/2013 23:26, Thierry Vignaud a écrit : On 3 February 2013 15:38, Thierry Vignaud wrote: Please remove *4.11.0.1* from core/release and push rpm-4.11.0.1 into ^^ updates_testing you mean ? indeed (I'd forgot to reset release in the updates_testing build) ping? Done, for the submission part. I can't remove packages from updates_testing myself. -- BOFH excuse #423: It's not RFC-822 compliant.
Re: [Mageia-dev] freeze push: perl-URPM & urpmi
Le 03/02/2013 23:29, Thierry Vignaud a écrit :
Hi
Please let in perl-URPM & urpmi.
Both perl-URPM & urpmi testsuite pass.
new perl-URPM enable urpmi to got unpacking, cpio & script errors from librpm.
new urpmi leverage that in order to report those errors (a long standing issue).
urpmi also reports erasure progress (the "#" "progress bar" which is already
used when installing packages)
Done.
I submitted rpm first, to ensure perl-URPM was built against latest version.
--
BOFH excuse #225:
It's those computer people in X {city of world}. They keep stuffing
things up.
Re: [Mageia-dev] Please remove qemu, and qemu-img from Mageia 3.
Le 04/02/2013 10:25, Bruno Cornec a écrit : Jose Jorge said on Sun, Feb 03, 2013 at 04:39:22PM +0100: So please don't remove it. +1. I use both of them on a very regular basis to build my pkgs without big issue. I think David get the point now, no need for a gazillion additional replies :) -- BOFH excuse #436: Daemon escaped from pentagram
Re: [Mageia-dev] Please remove qemu, and qemu-img from Mageia 3.
Jose Jorge said on Sun, Feb 03, 2013 at 04:39:22PM +0100: > So please don't remove it. +1. I use both of them on a very regular basis to build my pkgs without big issue. Bruno. -- Open Source & Linux Profession Lead EMEA http://opensource.hp.com EMEA Open Source HPISC Chief Technologisthttp://hpintelco.net FLOSS projects: http://mondorescue.org http://project-builder.org Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org
Re: [Mageia-dev] KDE dependencies
On Mon, Feb 04, 2013 at 07:46:31AM +0100, Nicolas Lécureuil wrote: > Le lundi 4 février 2013 01:18:37 Olav Vitters a écrit : > > I suddenly got asked of various KDE dependency questions. > > > > > I tried figuring out what triggered this, but I am not sure. Also not > > sure when I last updated my system. Any way of figuring out what > > triggers all the extra dependencies? > > Please test to update now ( new mlt shouldn't require kde anymore ) Fixed it, thanks! -- Regards, Olav
Re: [Mageia-dev] [Mageia-sysadm] Please remove qemu, and qemu-img from Mageia 3.
Op zondag 3 februari 2013 03:45:59 schreef David W. Hodgins: > During testing of updates to qemu, and x11-driver-video-qxl, > it has become very clear that no-one could possibly be using > these packages, as they are so slow, as to be useless. > > Over 6 hours to do a net install of a kde x86-64 system, > on hardware where that would normally be under 20 minutes. > > There are many problems with xorg crashing, mouse pointer not > being where the pointer is shown, etc. These bugs are described > in https://bugs.mageia.org/show_bug.cgi?id=8938 > > Please drop these useless packages, so we don't have to test > or install security updates for them. > > Thanks, Dave Hodgins i use qemu-img to convert kvm images to vmdk
