- Arch-general - lists.archlinux.org

[arch-general] efi boot kernel file sync - is it still necessary for refind?
by Mike Cloaked 28 Jan '13

28 Jan '13

According to https://wiki.archlinux.org/index.php/UEFI_Bootloaders#Sync_EFISTUB_Kernel_i… The recent (and current) version of refind-efi auto-detects efi kernels in /boot and that wiki article says that it is no longer necessary to sync files from /boot/ to /boot/efi/EFI/arch/ Does that mean when first installing arch in a uefi system then it is also no longer necessary to copy the vmlinuz and initramfs files to the EFI /arch/ directory at all? Or is it necessary only once as indicated in the wiki? i.e. is the wiki fully up to date? Thanks. -- mike c

1 1

Re: [arch-general] [arch-dev-public] Silent removal of initscripts?
by G. Schlisio 28 Jan '13

28 Jan '13

Am 28.01.2013 21:28, schrieb Evangelos Foutras: > On 28 January 2013 21:30, Tom Gundersen <teg(a)jklm.no> wrote: >> IMNSHO, it would probably be best to just unequivocally declare the rc >> scripts as dead and unsupported rather than try to play catch-up now. > I agree with this, no half measures. :) > > You made the announcement [1] in early November; title was pretty > clear; time-frame was provided. There's nothing else left to do now > but to drop the initscripts and sysvinit packages. > > [1] https://www.archlinux.org/news/end-of-initscripts-support/ > a new announcement would only make sense for those, who totally slept the whole time. the majority of users sticking with initscripts does not do that because of lack of interest in systemd. my vserver hoster (netcup.de, german provider) does not provide an up-to-date kernel and, although first made aware of the upcoming change in september, now begins beta testing a new virtualization (kvm, linux vserver before). its still some time (up to two month) until i can finally migrate to systemd. i would be very glad, if there was a sysvinit-scripts package for the time beeing. thanks for considering.

1 0

Re: [arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update - RESOLVED
by Mike Cloaked 27 Jan '13

27 Jan '13

On Tue, Jan 15, 2013 at 9:57 PM, Mike Cloaked <mike.cloaked(a)gmail.com>wrote: > If anyone can help or suggest links to solve the following problem I would > appreciate it. > > I have a new system built with an Intel DQ77KB motherboard with a Crucial > mSATA M4 SSD, and a Crucial SATA M4 SSD drive. I want to install arch on > this system and indeed preparing a usbkey with the archiso install media > using dd to write the usbkey boots just fine. > > Also the latest PartedMagic iso written to a usbkey also boots fine so > that I can format the SSD drives (both of them). Looking at the system > profile I can see all the peripherals, including all the RAM and both SSD > drives. > > However before starting the arch install I want to update the firmware on > the SSD drives. This is available from the Crucial website either as a > Windows 7/8 .exe (which I can't use) or a "manual" firmware update file > which is an iso (containing memdisk from syslinux, and a floppy image file > boot2880.img) > > Running the "file" command on the boot2880.img file after loop mounting it > gives: > > # file /mnt/iso/boot/isolinux/boot2880.img > /mnt/iso/boot/isolinux/boot2880.img: x86 boot sector, FREE-DOS Beta 0.9 > Bootloader KERNEL.SYS, code offset 0x3c, OEM-ID "FreeDOS ", sectors/cluster > 2, root entries 240, sectors 5760 (volumes <=32 MB) , sectors/FAT 9, serial > number 0x2b6112fe, label: "BOOTABLE ", FAT (12 bit) > > Writing the iso to a usbkey won't boot - the screen goes blank and nothing > happens when I write the iso to a usbkey with a FAT32 key with the boot > flag. I have tried isolinux and that does not seem to work. I have tried a > bootable grub2 usbkey and that does not work - all are prepared from a > working arch linux laptop. > > I have following numerous "recipes" for making the usbkey from various > sources on the web and none seem to work at all! > > The odd thing is that for syslinux I can't even get a menu item on the > screen when booting the key - nor for grub 2. > > I have used two different makes of usbkey - both 4GB....same result - and > both keys will boot fine with the archiso or PartedMagic. > > I don't know if I am doing something fundamentally stupid but this is > driving me nuts! I have used gparted, as well as fdisk, as well as trying > parted to reformat the usbkeys. Nothing I do seems to work! > > There must be a good step-by-step guide somewhere on how to get a usbkey > with sysylinux to boot the firmware updater - which seems to have a floppy > image file (boot2880.img) and uses memdisk to boot it - though the version > on the iso file is about two year old whereas arch current memdisk in > syslinux is up to date. > > If anyone can help advise on how to make a bootable usbkey to execute > this, I would really appreciate it. > > Thanks in advance. > > I raised this issue above about two weeks ago - and finally tonight resolved the problem. I checked on the Intel site for BIOS updates for my motherboard (DQ77KB) - and it turned out that Intel has in the interim released a new BIOS version 048 which has a bunch of fixes including " Updated VBIOS to fix issue where there is no display in DOS." After installing the new BIOS I was able to update the SSD drive firmware without any problem at all - so it seems that whatever method I tried to boot the firmware update which is DOS based would have failed until the BIOS was updated! So I am a happy bunny again with current Crucial SSD drive firmware! -- mike c

1 0

[arch-general] community/vlock vs core/kbd vlock
by Fredrik Eriksson 25 Jan '13

25 Jan '13

Hi, I used to rely on xautolock + community/vlock for locking my X session, core/kbd however removed community/vlock in favor of its own vlock which lack the functionality I need. Besides -a -a,--all Lock all console sessions and disable VC switching. not working This tty (pts/5) is not a virtual console. The entire console display cannot be locked. I also used -n and -s -n,--new Switch to a new virtual console before locking all console sessions. -s,--disable-sysrq Disable the SysRq mechanism while consoles are locked. This option only works if the -a,--all option given. that the new vlock is lacking. Not wanting to revert to slock I reworked community/vlock into my system in a foul manner I'm not going to mention here. I've also read https://bugs.archlinux.org/task/33134 http://www.spinics.net/lists/util-linux-ng/msg07153.html https://bbs.archlinux.org/viewtopic.php?id=156308 http://forums.fedoraforum.org/archive/index.php/t-203953.html :D I'm not sure what my question should be, really, but I would like to be able to use the 2.2.3 functionality (-ans) without having an ugly hacky setup. Regards, -- Fredrik

2 1

Re: [arch-general] [arch-dev-public] Drop VI from [core] (was Re: Winter Cleanup of [community])
by Paul Gideon Dann 25 Jan '13

25 Jan '13

On Friday 25 Jan 2013 00:14:14 Tom Gundersen wrote: > On Thu, Jan 24, 2013 at 11:45 PM, Allan McRae <allan(a)archlinux.org> wrote: > > There is nothing stopping us dropping vi completely and just putting vim > > on the install media... > > I'd favor that (as a vim user who always gets confused by vi on the > install media). > > -t +1 I do "pacman -S vim" pretty quickly if there's any serious file tweaking to be done on install. I'd be in favour of a more advanced "newby-friendly" editor, too, for people that don't know Vim. Nano is pretty limited. It does make sense to me to have several options available, since we depend on text editing so much for installation. Paul

1 0

[arch-general] Partition/Data rescue
by archlinuxmailings＠gmail.com 25 Jan '13

25 Jan '13

Hi You know the moment where you would turn back the time some seconds only? Well here we are... I got a perfectly running arch on ssd (6 partitions) and an internal hdd (1partition) with a backup usb disk (1partition) connected at a very genious moment! Having done a SD-multiboot setup with several distros I just wanted to test that the last distro added (DBAN Dariks Boot and nume) boots fine. Only little thing to mention was that --autonuke setting at boot loader. Don't ask me what was riding me, maybe tiredness, stupidness, something evil or altogether! As fast as I swiched the system off it erased at least some sectors on each and every disk! Well, DBAN worked. But how can I get back to something running? At least I would like the backup disk running but I am not sure what is the correct way. I don't have another backup and uploading to Amazon S3 was not yet finished, so disaster recovery would have worked only later.... How I hate Murphy today! For the procedure: Testdisk showed me at least 6 possible partitioning (having had one on this disk!) schemes and just creating the partition with fdisk and not touching the filesystem wouldn't give me my TOC back, no? Using gparted would recreate the filesystem resulting in overwritten data? Do I need to use an ext-restoring rool or what is best to try? First copying the data off to a second external disk with "dd"? And then? I would really appreciate some experienced users feedback as some of the missing data means a lot to me although knowing that there are more important things lime health etc. Thanks in advance! emak

2 1

[arch-general] broken system after today upgrade
by arnaud gaboury 24 Jan '13

24 Jan '13

Dear list, testing repo is enabled on my box. Today upgrade of glibc, filesystem and Linux failed and leaves me with an unbootable machine. I boot with Archiso, then mount /, /boot and /user on /mnt/. From this directory, I then #pacman -Syu linux glibc filesystem with no success. Get excv unfound. I downgraded these 3 packages, then try again. It went with no errors. Booting my box leaves me to a Kernel panic with init not found. My grub config is clean and don't know why I should pass any extra kernel parameter. How can I deal with this issue? Thank you for help as my box is my working tool

11 19

[arch-general] [systemd] udevd and udevadm not found in initramfs when using systemd-git
by William Giokas 24 Jan '13

24 Jan '13

All, I rebooted my computer today to test some boot flags only to be greeted with an unbootable machine. Here is a transcript of the boot messages: /init: line 9: systemd-timestamp: not found :: running early hook [udev] /init: line 21: udevd: not found :: running hook [udev] :: Triggering uevents... /init: line 21: udevadm: not found /init: line 21: udevadm: not found /init: line 21: udevadm: not found Waiting 10 seconds for device /dev/sda2... ERROR: device '/dev/sda2' not found. Skipping fsck. ERROR: Unable to find root device '/dev/sda2'. And then I am dropped to a root shell. Attached is my mkinitcpio.conf[1]. This only happens when using an initramfs generated with systemd-git. I built this this image[1] using mkinitcpio 0.12.0.15.g1fb6722. I am also using linux-mainline, but that does not seem to have any effect when downgrading or using a different kernel. If I downgrade systemd to 197, however, rebuild the image and reboot, it goes smoothly. Shutting down my computer cleanly is also an impossibility, as `systemctl poweroff` just hangs with no messages printed. This does not happen with 197. Also attached are the pacman -Ql outputs of my systemd-git[3] and [core]s systemd[4], as well as the mkinitcpio -v output[5]. [1] http://ix.io/46o [2] http://ompldr.org/vaDdobQ/initramfs-linux-mainline.img [3] http://ix.io/46n [4] http://ix.io/46m [5] http://ix.io/46l Thank you, -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F

2 1

Re: [arch-general] Drop VI from [core] (was Re: Winter Cleanup of [community])
by Greg Bouzakis 24 Jan '13

24 Jan '13

Stéphane Gaudreault wrote: > Le 2013-01-24 07:21, Allan McRae a écrit : >> On 24/01/13 22:08, Alexander Rødseth wrote: >>> === [core] === >>> >>> For [core], there are two uneeded orphans, that also aren't make >>> dependencies for any other [core] packages: >>> >>> openldap >>> vi >>> >>> If I may be so bold, maybe vim or another editor (still providing the >>> "vi" command) could take over for the vi package? >> I agree with just dumping vi and moving [vim] to core... But we can not >> put split packages across repos and gvim and deps are not going there so >> that is a no... > > Moving to another thread for clarity. > > +1 to drop vi. I cannot imagine why someone would want to use this crap > ... > > We already have nano in [core], so I think that vim could stay in > [extra] (do we really need 2 text editors in [core] ?). > FWIW this is the original discussion which brought this crippled vi upon us https://bugs.archlinux.org/task/13109 but more importantly https://bugs.archlinux.org/task/13239 Do vim and gvim really have to share the same PKGBUILD? I would be in favour of having a proper modern vim implementation in core no matter what its name would be. The only downside is that vim would need signoffs. I think that if a different PKGBUILD is used for gvim then gvim wouldn't need those as well. Greg

1 0

Re: [arch-general] [arch-dev-public] Drop VI from [core] (was Re: Winter Cleanup of [community])
by Paul Gideon Dann 24 Jan '13

24 Jan '13

On Thursday 24 Jan 2013 11:05:22 Stéphane Gaudreault wrote: > +1 to drop vi. I cannot imagine why someone would want to use this crap ... > > We already have nano in [core], so I think that vim could stay in > [extra] (do we really need 2 text editors in [core] ?). Vi is the standard UNIX text-editor. Many admins rely on the fact that vi is available everywhere. It really should be in core. Also, I know you might be referring to "plain vi", which is a completely different beast to Vim, but the latter (which provides "vi" too) has a *huge* userbase. Calling it crap is just bizarre... Paul

4 3