You are not logged in.
Hi Arch community,
Arch Linux (archboot creation tool) 2013.03-4, "2k13-R1" has been released.
Homepage and for more information on archboot:
http://wiki.archlinux.org/index.php/Archboot
Summary:
- major update/cleanup on all components
Hybrid image files and torrents are provided, which include
i686 and/or x86_64 core repository. Please check md5sum before using it.
Hybrid image file is a standard CD-burnable image and also a raw disk image.
- Can be burned to CD(RW) media using most CD-burning utilities.
- Can be raw-written to a drive using 'dd' or similar utilities.
This method is intended for use with USB thumb drives.
Please get it from your favorite arch linux mirror:
https://downloads.archlinux.de/iso/archboot/2013.03/
<yourmirror>/iso/archboot/2013.03/
/boot for PXE/Rescue files are provided here:
https://downloads.archlinux.de/iso/arch … 13.03/boot
<yourmirror>/iso/archboot/2013.03/boot
Changelog:
GENERAL:
- kernel 3.8.4 / LTS kernel 3.0.70
- pacman 4.0.3 usage
- RAM recommendations: 768 MB
- major update/cleanup on all components
Kernel changes:
- bump to latest 3.8.x series and bump lts to latest 3.0.x series
Environment changes:
- updated pacman mirrorlist
- replaced netcfg with netctl
- removed ide-legacy hook
- replaced arch_virtio, arch_fw with block hook
- replaced usbinput with keyboard hook
- replaced dbus-core with dbus
- bump to latest mkinitcpio code
- bump syslinux from 4.x to 5.0
- removed bind and dnsutils
- blacklist floppy module during boot
setup changes:
- replaced netcfg network setup with netctl
- always install netctl instead of netcfg
- replaced gummiboot-efi with gummiboot
- removed initscripts compat mode
- always install systemd-sysvcompat
- updated gummiboot install routine
- updated refind install routine
- removed persistent soundcard and network hack,
systemd handles everything now.
- no need to add hostname to /etc/hosts anymore
quickinst changes:
- removed initscripts compat mode
- removed rc.conf hint
- removed double check on ntfs
Further documentation can be found on-disk and on the wiki.
Thanks to all beta testers, which reported bugs during this development period.
Have fun!
greetings
tpowa
Last edited by tpowa (2013-03-23 19:22:43)
Offline
Does it have systemd 198, which by default mounts the esp to /boot? (http://cgit.freedesktop.org/systemd/systemd/tree/NEWS)
Offline
It has systemd 198 on it. Though I cannot test any uefi related stuff. You need to try what it does.
Offline
The code below worked perfectly with the previous version of Archboot but with this new version it does not add the boot entry to the NVRAM and there are no error messages. Any idea why that might be?
echo "initrd=\EFI\arch\initramfs-linux.img root=/dev/mapper/vgTESTDrive-lvRoot cryptdevice=/dev/md33:vgTESTDrive add_efi_memmap pcie_aspm=force quiet" | iconv -f ascii -t ucs2 | efibootmgr --create --write-signature --gpt --disk /dev/sdd --part 1 --label "-=[[[TESTING]]]=- 2013-03-20 22:25:42" --loader '\EFI\arch\vmlinuz-linux.efi' --append-binary-args -
Offline
RAM recommendations: 768 MB
That surprised me. I'm running VPS with 352 MB RAM: nginx, php-fpm, mysql, openvpn, prosody, tor, polipo, dnsmasq, and on top of that 100MB RAM eater Redmine. And I'm quite fine.
In my opinion 768MB sounds scary.
Offline
It's archboots design to need so much RAM;
initrd.img=100MB
kernel image= 2MB
+ decompressed size
with 768 it works, you can try with less memory but it will probably fail.
Offline
I didn't copy ready instalation. I'm using XEN-HVM. Provider mounted Arch ISO in my virtual cd-rom, so I've used archboot.
But I know, there are more things to consider, so you're right. 768MB recommendation for archboot sounds reasonable.
Offline
I'm new here. I set up Arch a little less than a week ago. Is it recommended that we mirror these changes? I know arch is all about giving power to the users and I know that I don't have to if I don't want to, but should I?
The netcfg to netctl is what grabbed my attention.
Last edited by MagicSkyFairy (2013-03-21 08:04:00)
I have wasted atleast a second of your time by making you read my signature.
Offline
It just means that in the install routine netctl is used instead of netcfg. If you already have a running system you don't need to reinstall.
Soon netcfg will be dropped from [core] and replaced with netctl. It's just that this version already supports this change, which will happen soon.
Offline
It fails for me when trying to install using wifi.
I chose to setup the network in the installer menu, I selected the wireless interface w*, then wireless, essid not hidden, encrypted, and then WPA.
And it returns to the menu ! I can't event type the passphrase, so it is not a wrong passphrase issue.
Network is not configured and then the rest of the installation fails.
Used 2013.03-3 x86_64 iso, on a usb-stick. Thinkpad T500,
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
Nothing appears in the log on VT7.
Hope it helps...
Fred
Offline
Sorry to report the bug here, but I had a look at:
http://archlinux.mirrors.ovh.net/archli … Readme.txt
"If you find a bug, please mail the archboot developer directly.
- Arch Linux Bugtracker: http://bugs.archlinux.org"
But there is no bug reported in Arch bug tracker, about archboot.
I searched archboot in "Search this project for"...
It seems weird no bug is reported, and then I don't know if I need to fill a bug report...
Fred
Offline
It's not very often that bug entries about archboot are listed on normal bug tracker.
The forum thread or mailing me about issues is ok.
I'll take a look at it, the code changed to netctl usage so could be that I missed something on that.
You can still use the CD mode to install, all packages are only 4 days old on image.
Offline
Error located and fixed on archboot git. New image files will appear soon on mirrors.
Offline
Cool, I just download 2013.03-4 and tested.
The issue is solved, and I've been able to configure the network fine.
However, please find hereafter the results of my tests.
- When booting install media with LTS kernel, then it may be good to install LTS kernel ?
latest kernel (3.8) were installed instead.
- When installing grub (BIOS/grub-bios), I had only the choice between /dev/sda (target drive) and /dev/sdb (USB boot drive).
Would it be possible to be presented the option to install grub in a partition (ex: /dev/sdX) ?
For testing reason, I installed Arch with archboot on another partition, as I am chainloading from another "main" partition.
- After the installation, network is not working, AND /etc/netctl is empty...
So I wonder if it is normal, as this new version of Archboot seems to provide...netctl :-)
I made 2 installations:
- 1st with the following groups: base, base-devel, all xfce4, all xorg
The result was a system with no graphical Interface, and startx not able to start X
- 2nd with only base and base-devel, which results in a bootable system with empty /etc/netctl.
Well, Archboot seems not able to provide what I was expecting, and I will use classical installation process with pacstrap etc...
Good luck for Archboot, and I hope this feedback will help you.
Cheers
Fred
Offline
I try to install to a LVM already created but in every step that imply check RAID the archscript stuck and never continue
at the end of 2 min I decide kill it
This affect any LVM created previous to any step that imply the routine of check RAID, LVM and etc
meng, this was the bugiest Archboot??? (Real Question, no joke)
Well, I suppose that this is somekind of signature, no?
Offline
Thanks for your report.
- LTS kernel should be indeed installed if booting LTS kernel, this is a real bug.
The routine has not changed since quite some time, have to look at it.
- I think only allowing full devices on bootloader was intentional and is not a bug.
- No netctl interfaces on intalled media is a real bug.
- Archboot will never configure X for you, as no other archlinux install media will do this.
Offline
I try to install to a LVM already created but in every step that imply check RAID the archscript stuck and never continue
at the end of 2 min I decide kill itThis affect any LVM created previous to any step that imply the routine of check RAID, LVM and etc
meng, this was the bugiest Archboot??? (Real Question, no joke)
The main LVM activation and rules have changed, i'll look into that. If you don't use a already created LVM does it work?
Offline
Jristz wrote:I try to install to a LVM already created but in every step that imply check RAID the archscript stuck and never continue
at the end of 2 min I decide kill itThis affect any LVM created previous to any step that imply the routine of check RAID, LVM and etc
meng, this was the bugiest Archboot??? (Real Question, no joke)
The main LVM activation and rules have changed, i'll look into that. If you don't use a already created LVM does it work?
I never get how make a LVM using the fancy menu, maybe lack of propper adverticenmentsor was me??
but I receive the bug only whit the only precence of a LVM on a partition (not mount not activated only existing), maybe I have (only 1 usb mounted) 1 hd and 2 usb.
Well, I suppose that this is somekind of signature, no?
Offline
- When booting install media with LTS kernel, then it may be good to install LTS kernel ?
latest kernel (3.8) were installed instead.
Fixed in archboot git syslinux changed boot parameter names.
- When installing grub (BIOS/grub-bios), I had only the choice between /dev/sda (target drive) and /dev/sdb (USB boot drive).
Would it be possible to be presented the option to install grub in a partition (ex: /dev/sdX) ?
For testing reason, I installed Arch with archboot on another partition, as I am chainloading from another "main" partition.
For grub it is recommended to use a grub boot partition.
You can use syslinux for installing to a partition.
- After the installation, network is not working, AND /etc/netctl is empty...
So I wonder if it is normal, as this new version of Archboot seems to provide...netctl :-)
Please tell me what you have done, on my virtual machine all works as it should.
You need to setup your connection with installer and choose autoconfiguration yes on system configuration.
Last edited by tpowa (2013-03-25 08:33:47)
Offline
but I receive the bug only whit the only precence of a LVM on a partition (not mount not activated only existing), maybe I have (only 1 usb mounted) 1 hd and 2 usb.
How did you manage to not have an activated lvm after boot? Normally archboot enables lvm devices during bootup.
Offline
For grub it is recommended to use a grub boot partition.
You can use syslinux for installing to a partition.
I only use syslinux when creating a bootable usbstick install. Never on the buil-in hdd.
True you get a warning when using grub-install to install in a partition, but if partitions are well created (ex. with gparted), chainloading is working that way
# grub-install --force /dev/sda7
Please tell me what you have done, on my virtual machine all works as it should.
You need to setup your connection with installer and choose autoconfiguration yes on system configuration.
Installation on /dev/sda7, swap on /dev/sda5.
Wireless: interface w*, enter essid, not hidden, wpa, accept dhcpd (in core) because working.
Then packages installed are just group _base_ and _base-devel_
Wait for __ages__ for all the packages to be browsed.
Then the system installs well, reboot.
And the result is a system with no /etc/netctl.
Fred
Offline
I only use syslinux when creating a bootable usbstick install. Never on the buil-in hdd.
True you get a warning when using grub-install to install in a partition, but if partitions are well created (ex. with gparted), chainloading is working that way
# grub-install --force /dev/sda7
Seems this is now possible again, there were times where it errors out all the time, I can consider readding this in a future release.
Wait for __ages__ for all the packages to be browsed.
This needs only ages if you use [extra] repository too.
And the result is a system with no /etc/netctl.
Ah now I understand why, you use ftp installation and netctl is still in testing repositoy and cannot be installed.
This will fixup itself when netctl will move out of testing repository.
Offline
Nothing appears in the log on VT7.
Fixed in git to mention to check journalctl -xn instead of tty7.
Offline
This needs only ages if you use [extra] repository too.
True ! No need to activate [extra] for a base install; I installed the full monty just before, and I checked [extra] for the 2nd installation.
My mistake.
Ah now I understand why, you use ftp installation and netctl is still in testing repositoy and cannot be installed.
This will fixup itself when netctl will move out of testing repository.
Well, I did a net install, don't know if I used http or ftp, but the installation was done using netinstall.
I wonder how you were able to get netctl installed, with netinstall in [testing] repo, before you release ?
Even with if using a virtual machine...
Fixed in git to mention to check journalctl -xn instead of tty7.
Well, VT7 is great, is there a way to continue displaying logs to VT7 ?
Instead of using journalctl on another VT.
Most people are used to switch to another VT to get logs (Debian syndrom ? ;-))
I am kiding, journalctl sounds fine, I'm not yet used to systemd and all the reintented wheels...
Fred
Offline
Well, I did a net install, don't know if I used http or ftp, but the installation was done using netinstall.
I wonder how you were able to get netctl installed, with netinstall in [testing] repo, before you release ?
Even with if using a virtual machine...
Normally I only test CD mode and not FTP mode. This was my mistake. It will solve itself in a few days.
Well, VT7 is great, is there a way to continue displaying logs to VT7 ?
Instead of using journalctl on another VT.
Well netctl is systemd based so there have to be a way to log to a vt that I don't know at the moment.
Offline