[arch-general] Difference between mkarchroot and arch-chroot
Can someone elaborate on the difference between mkarchroot and arch-chroot? Basically, i want a chrooted environment for testing some program. Alternatively, is there any other better way to create an isolated environment, apart from chroot and VMs.
Re: [arch-general] Difference between mkarchroot and arch-chroot
Am 15.01.2013 09:38, schrieb gt: Can someone elaborate on the difference between mkarchroot and arch-chroot? Basically, i want a chrooted environment for testing some program. Alternatively, is there any other better way to create an isolated environment, apart from chroot and VMs. mkarchroot creates a new system root. If you want to test a program in an isolated environment, I suggest you look into systemd-nspawn. If you want more security, libvirt-lxc may be your friend (it seems lxc is broken in many ways and doesn't work right with systemd, libvirt-lxc however seems to be fine, I tested neither). signature.asc Description: OpenPGP digital signature
Re: [arch-general] Difference between mkarchroot and arch-chroot
On Tue, Jan 15, 2013 at 10:13:58AM +0100, Thomas Bächler wrote: mkarchroot creates a new system root. If you want to test a program in an isolated environment, I suggest you look into systemd-nspawn. If you want more security, libvirt-lxc may be your friend (it seems lxc is broken in many ways and doesn't work right with systemd, libvirt-lxc however seems to be fine, I tested neither). Thank you. I will take a look at them.
Re: [arch-general] rEFInd 0.6.4 + linux 3.7.2-1 fail to boot
Em 15-01-2013 05:24, Bill Sun escreveu: Just a thought: Did you forget to copy the generated kernel image of the 3.7.2 to the EFI partition? No. If so, would the kernel booted and failed to complete boot process due to mismatch between kernel image/initramfs and installed modules. But the kernel does not even begin starting, stopping just after option is selected in rEFInd and message Starting vmlinuz-linux ...options of rEFInd is printed. -- http://www.google.com/profiles/andre.vmatos signature.asc Description: OpenPGP digital signature
Re: [arch-general] Difference between mkarchroot and arch-chroot
On Tue, Jan 15, 2013 at 9:38 AM, gt static.vor...@gmx.com wrote: Can someone elaborate on the difference between mkarchroot and arch-chroot? Basically, i want a chrooted environment for testing some program. Alternatively, is there any other better way to create an isolated environment, apart from chroot and VMs. arch-chroot — chrooting into an existing environment, using on the Arch install medium to get to your brand new root you pacstrap’d ten seconds ago (or for recovery of an existing root). mkarchroot — creating a brand new Arch Linux environment/root. So, two different things when you think about it. -- Kwpolska http://kwpolska.tk stop html mail | always bottom-post www.asciiribbon.org | www.netmeister.org/news/learn2quote.html GPG KEY: 5EAAEA16
[arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update
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 4GBsame 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. -- mike c
Re: [arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update
On 15-01-2013 21:57, Mike Cloaked 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) This seems to be a FreeDOS floppy. If you can mount that image and have a look inside you can probably find the firmware file itself, the flasher program and probably the command used to launch it (look inside autoexec.bat). 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 4GBsame 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. You could try downloading freedos, installing it to a usbkey and check if it boots, if it does it is a matter of adding the flasher program, the firmware file and launch it the same way it is launched in the original image. -- Mauro Santos
Re: [arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update
On Tue, Jan 15, 2013 at 10:16 PM, Mauro Santos registo.maill...@gmail.comwrote: 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) This seems to be a FreeDOS floppy. If you can mount that image and have a look inside you can probably find the firmware file itself, the flasher program and probably the command used to launch it (look inside autoexec.bat). I guess that is possible - though I would have to look up how to open up the img file. You could try downloading freedos, installing it to a usbkey and check if it boots, if it does it is a matter of adding the flasher program, the firmware file and launch it the same way it is launched in the original image. I did try using unetbootin to make a freedos usbkey using freedos from the standard list in the available options within unetbootin but the key I prepared would not boot! I don't know if it is critical to put the partition table into the key in a particular way - but I tried using gparted and making a standard msdos partition table followed by making a new partition which was fat32 with boot and lba labels. I have seen some articles which have the old 63 sector start point for the first partition on the usbkey - but again when I tried that the key would not get recognised by the arch system when I plugged it in. So is there any magic incantation in formatting the usbkey in the first place before putting writing the MBR and placing the syslinux boot files and image files in the key? If using grub2 via grub-install on the key is there any magic incantation for that ? I guess if I can get freedos to boot on the key I may be closer to getting something going! (Or getting sysylinux to boot - either would be a solution) Thanks -- mike c
Re: [arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update
On 15-01-2013 22:35, Mike Cloaked wrote: On Tue, Jan 15, 2013 at 10:16 PM, Mauro Santos registo.maill...@gmail.comwrote: 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) This seems to be a FreeDOS floppy. If you can mount that image and have a look inside you can probably find the firmware file itself, the flasher program and probably the command used to launch it (look inside autoexec.bat). I guess that is possible - though I would have to look up how to open up the img file. Have you tried to just mount that /mnt/iso/boot/isolinux/boot2880.img file? Try with 'mount -o loop /mnt/iso/boot/isolinux/boot2880.img /path/to/mountpoint' You could try downloading freedos, installing it to a usbkey and check if it boots, if it does it is a matter of adding the flasher program, the firmware file and launch it the same way it is launched in the original image. I did try using unetbootin to make a freedos usbkey using freedos from the standard list in the available options within unetbootin but the key I prepared would not boot! I don't know if it is critical to put the partition table into the key in a particular way - but I tried using gparted and making a standard msdos partition table followed by making a new partition which was fat32 with boot and lba labels. I have seen some articles which have the old 63 sector start point for the first partition on the usbkey - but again when I tried that the key would not get recognised by the arch system when I plugged it in. So is there any magic incantation in formatting the usbkey in the first place before putting writing the MBR and placing the syslinux boot files and image files in the key? If using grub2 via grub-install on the key is there any magic incantation for that ? I guess if I can get freedos to boot on the key I may be closer to getting something going! (Or getting sysylinux to boot - either would be a solution) I really meant installing freedos to the usbkey, no syslinux involved there. You can probably do the install step from a virtual machine by allowing it access to the whole usbkey. Then you just need to copy the flasher program and the firmware file to the root and run it from there. -- Mauro Santos
[arch-general] Encryption passphrase has to be entered twice
Hi, I've recently installed Arch on a friend's machine, which happens to be a MacBook Pro. After some initial problems with the EFI setup, it now works basically great. However there is a strange problem during the boot process. The system is fully encrypted (based on the layout recommended in the Wiki), so during the boot process you'll get asked for the passphrase. However the correct passphrase isn't recognized the first time, but it has to be entered a second time. The passphrase is pretty easy for now, just to make sure mistyping is not a problem. We tested this several times, and it consequently refuses to accept the passphrase given at the first attempt. I've had to include the usbinput hook into the initramfs as the keyboard is attached via USB. However I can't think that this is a problem, as I've used the usbinput hook on other machines without a problem. Has anyone experienced something like this already? What might be the problem here? How can I debug this? I thought of rewriting the encrypt hook to output the entered passphrase, but before fiddling around with it, maybe there is something obvious I've missed here? Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
[arch-general] powernow-k8 fails to load with linux 3.7.2
Hi, I just installed linux 3.7.2 from [testing] on an AMD system and noticed that powernow-k8 is not loaded. As a result, the CPU is stuck at the maximum frequency because ondemand governor is inactive. The precise model is AMD PhenomII X4 955, and modprobe error is: -- % modprobe -vv powernow-k8 modprobe: INFO: custom logging function 0x40ab40 registered modprobe: INFO: Failed to insert module '/lib/modules/3.7.2-1-ARCH/kernel/drivers/cpufreq/powernow-k8.ko.gz': No such device modprobe: ERROR: could not insert 'powernow_k8': No such device modprobe: INFO: context 0x21c91b0 released insmod /lib/modules/3.7.2-1-ARCH/kernel/drivers/cpufreq/powernow-k8.ko.gz -- Meanwhile, linux 3.6.11 works fine. Notice also, that acpi_cpufreq 3.7.2 is fine on a INtel core2duo machine. Is it only me, or others have seen this too? Thanks, -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D signature.asc Description: PGP signature
Re: [arch-general] Difference between mkarchroot and arch-chroot
On Tue, Jan 15, 2013 at 06:08:01PM +0100, Kwpolska wrote: On Tue, Jan 15, 2013 at 9:38 AM, gt static.vor...@gmx.com wrote: Can someone elaborate on the difference between mkarchroot and arch-chroot? arch-chroot — chrooting into an existing environment, using on the Arch install medium to get to your brand new root you pacstrap’d ten seconds ago (or for recovery of an existing root). mkarchroot — creating a brand new Arch Linux environment/root. So, two different things when you think about it. Yup, I got it later on. Was a bit stupid question, now I think about it :P Anyway, since Thomas mentioned systemd-nspawn, and it seems to do the same stuff as arch-chroot, I was wondering what are the differences between the two, and would arch-chroot be deprecated in the future?
Re: [arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update
Mike Cloaked mike.cloa...@gmail.com on Tue, 2013/01/15 21:57:
[...]
If anyone can help advise on how to make a bootable usbkey to execute this,
I would really appreciate it.
I do have the same drive and I updated the firmware booting the image off
grub. All just need is a working grub (2.0 here) installation and syslinux
(for memdisk). (Though doing it with syslinux should work as well.)
The grub.cfg should have a config section that looks like this:
menuentry Update Crucial M4 {
set root='(hd0,1)'
linux16 /memdisk floppy
initrd16 /boot2880.img
}
If the files are in place (probably in /boot/) the image should boot and you
can successfully update the drives firmware.
Mounting the boot image, modifying it or installing freedos is not necessary.
--
main(a){char*c=/*Schoene Gruesse */B?IJj;MEH
CX:;,b;for(a/*Chris get my mail address:*/=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c ./sig*/b/42*2-3)*42);}
signature.asc
Description: PGP signature
