You are not logged in.
Hi Arch community,
Arch Linux (archboot creation tool) 2011.06-1, "2k11-R3" has been released.
To avoid confusion, this is not an official arch linux iso release!
Homepage and for more information on archboot:
http://wiki.archlinux.org/index.php/Archboot
Summary:
- bump to latest kernels and introduce pacman 3.5.3
Hybrid image file and torrent is provided, which include
i686 and 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/2011.06/
<yourmirror>/iso/archboot/2011.06/
/boot for PXE/Rescue files are provided here:
https://downloads.archlinux.de/iso/arch … 11.06/boot
<yourmirror>/iso/archboot/2011.06/boot
Changelog:
GENERAL:
- kernel 2.6.39.1 / LTS kernel 2.6.32.41
- pacman 3.5.3 usage
- RAM recommendations: 320 MB
Kernel changes:
- bump to latest .39 series and bump lts to latest .32 series
Removed features:
- ndiswrapper and tiacx removed
Environment changes:
- merged in latest initscripts, mkinitcpio and udev changes
- detect KMS and activate it during boot process
- fix uefi img inclusion
- added grub2 efi fixes
hwdetect changes:
- adopted blacklisting changes
setup changes:
- added dhclient fallback if dhcpcd fails
- added package information to package selection
- ask if extra repository should be parsed during FTP installation
- added package processing during FTP package selection
- added new blacklisting method for network and soundcards
quickinst changes:
- none
Further documentation can be found on-disk and on the wiki.
Have fun!
greetings
tpowa
Offline
Hi, I had a problem with 2011.5-2 it did not have ntfs-3g and refuse to install . is that problem fixed on 06-1? TIA.
Offline
Hi, I had a problem with 2011.5-2 it did not have ntfs-3g and refuse to install . is that problem fixed on 06-1? TIA.
My new forum user/nick name is "the.ridikulus.rat" .
Offline
I'm sorry I am not a programer that means Nothing to me. Thanks anynway.
Offline
fix ntfsprogs due to package rename
That itself should tell you that its fixed.
Note the lines in red and green. Red means that line has been replaced with the green one. Notice the changes. ntfs-3g has been replaced by ntfs-3g_ntfsprogs because the package was renamed.
Other than that there are no changes.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
this install with mount iso through loop option in grub2?
https://bbs.archlinux.org/viewtopic.php?id=78171&p=2
greetings
Offline
The non LTS kernel/initrd (i686 & x86_64) are getting hanged while booting my Aspire_TimelineX_4820TG Laptop. I think, the problem is related to the kms/vgaswitcheroo (enabling switchable graphics Intel HD & Radeon 5650) which is enabled in the default kernel of this build.
Note: Archlinux default 2.6.39-ARCH works without any problem in the same m/c.
Last edited by archan.paul (2011-06-23 05:41:02)
Offline
Thank you very much. Appreciate the explanation . I did in fact found it fixed when i used. thank you again. It is all up and running now.
Offline
The non LTS kernel/initrd (i686 & x86_64) are getting hanged while booting my Aspire_TimelineX_4820TG Laptop. I think, the problem is related to the kms/vgaswitcheroo (enabling switchable graphics Intel HD & Radeon 5650) which is enabled in the default kernel of this build.
Note: Archlinux default 2.6.39-ARCH works without any problem in the same m/c.
The framebuffer switching can be disabled by adding disablehooks=arch_fb to boot line, if needed.
Offline
To all UEFI users: I have created a wiki at my gitorious account with random UEFI stuff which may be useful for those Dual Booting Archlinux (via Archboot) and Windows x64 in UEFI-GPT setup. https://gitorious.org/tianocore_uefi_du … pages/Home .
My new forum user/nick name is "the.ridikulus.rat" .
Offline
this install with mount iso through loop option in grub2?
https://bbs.archlinux.org/viewtopic.php?id=78171&p=2
greetings
I really don't know what you mean, but if you just want to boot the ISO download the kernel and initrd file from boot subdirectory and make an entry in your bootloader.
It's a perfect recovery system running from your memory.
Offline
sl1pkn07 wrote:this install with mount iso through loop option in grub2?
https://bbs.archlinux.org/viewtopic.php?id=78171&p=2
greetings
I really don't know what you mean, but if you just want to boot the ISO download the kernel and initrd file from boot subdirectory and make an entry in your bootloader.
It's a perfect recovery system running from your memory.
He means the loopback option in grub2. That requires a loopback.cfg file within the iso and may require changes to init system of the iso to recognize kernel parameters pertaining to locating the iso in the disk.
My new forum user/nick name is "the.ridikulus.rat" .
Offline
@tpowa and sl1pkn07:
http://www.sysresccd.org/Sysresccd-manu … sing_Grub2
http://www.supergrubdisk.org/wiki/Loopback.cfg
https://wiki.ubuntu.com/Kernel/Dev/Mult … BootUSBKey
Last edited by skodabenz (2011-06-23 11:26:36)
My new forum user/nick name is "the.ridikulus.rat" .
Offline
There are a few problems due to the epoch ':' (colon) character in grub2 packages now. In the archboot 2011.06-1 iso, ':' have been replaced by '_'. This will lead to pacman not installing those package when called inside the setup script. To override that −input-charset and −output-charset options need to be set in the "xorriso -as mkisofs" commands in the all-in-one script http://www.gnu.org/software/xorriso/man … devel.html .
But the use of colon ':' leads to a even bigger problem when archboot is setup in usb. UEFI firmwares do not support any filesystem other than FAT32/16/12 (according to Spec version 2.31) and FAT32 by default do not use UTF-8 charset, the UEFI spec specifically mention that the FAT filesystem should be case-insensitive, meaning not UTF-8.
It won't be possible to copy the grub2 packages from the iso to the usb (even if a newer iso with −input-charset utf-8 is created that retains the colon in the filenames). Although it is possible to otherwise use archboot from such a FAT formatted usb, without the grub2 packages, it is meaningless to use the usb to boot in UEFI system.
@tpowa: What do you think of this? How to solve this in case of UEFI bootable archboot usb (https://gitorious.org/tianocore_uefi_du … I_boot_USB) ? Relevant Bug report at https://bugs.archlinux.org/task/24270 .
Last edited by skodabenz (2011-06-23 14:57:56)
My new forum user/nick name is "the.ridikulus.rat" .
Offline
There are a few problems due to the epoch ':' (colon) character in grub2 packages now. In the archboot 2011.06-1 iso, ':' have been replaced by '_'. This will lead to pacman not installing those package when called inside the setup script. To override that −input-charset and −output-charset options need to be set in the "xorriso -as mkisofs" commands in the all-in-one script http://www.gnu.org/software/xorriso/man … devel.html .
But the use of colon ':' leads to a even bigger problem when archboot is setup in usb. UEFI firmwares do not support any filesystem other than FAT32/16/12 (according to Spec version 2.31) and FAT32 by default do not use UTF-8 charset, the UEFI spec specifically mention that the FAT filesystem should be case-insensitive, meaning not UTF-8.
It won't be possible to copy the grub2 packages from the iso to the usb (even if a newer iso with −input-charset utf-8 is created that retains the colon in the filenames). Although it is possible to otherwise use archboot from such a FAT formatted usb, without the grub2 packages, it is meaningless to use the usb to boot in UEFI system.
@tpowa: What do you think of this? How to solve this in case of UEFI bootable archboot usb (https://gitorious.org/tianocore_uefi_du … I_boot_USB) ? Relevant Bug report at https://bugs.archlinux.org/task/24270.
@tpowa: How about moving <ARCHBOOT_ISO>/core-{any,x86_64,i686} to a tar or squashfs archive? That might allow us to use any char in package filenames without bothering about filename char restrictions in ISO9660 or FAT32 when creating the iso or setting up the usb.
Last edited by skodabenz (2011-07-01 18:04:29)
My new forum user/nick name is "the.ridikulus.rat" .
Offline
@skodabenz:
Why do we need to move it to an other filesystem type?
I tried booting from usb and i had no issues, is this just UEFI related this problem?
Offline
@skodabenz:
Why do we need to move it to an other filesystem type?
I tried booting from usb and i had no issues, is this just UEFI related this problem?
Did you try installing grub2 package (even grub2-bios) from archboot using the packages in <ISO>/core-* dirs instead of pulling from online repos? Does the setup script succeed in setting up grub2-bios in a test setup.
The script will fail to install grub2 since it expects grub2-common-1:1.99-3-x86_64.pkg.tar.xz while the iso has grub2-common-1_1.99-3-x86_64.pkg.tar.xz (1_1.99 vs 1:1.99 - epoch pkg naming). All mkisofs implementations (including xorriso) will convert any unsupported characters in filenames to underscore while geretaing the iso (according to man pages). The colon char in package name does not work in iso9660, FAT. NTFS and maybe even UDF (most of the non-unix filesystems).
In case you did not notice the Archboot iso has /core-x86_64/pkg/grub2-common-1_1.99-3-x86_64.pkg.tar.xz when it is supposed to have grub2-common-1:1.99-3-x86_64.pkg.tar.xz . If the packages had the colon char still in the filename, while copying the <ARCHBOOT_ISO>/core-* dirs from lets say ext4 (which supports colon in filename) to a bootable FAT16/32 USB the grub2 1.99 packages (and all packages having epoch value set) will not get copied.
I suggest moving the core-* dirs to something like a image file (maybe squashfs or simply tar) which will get loopmounted inside the archboot iso rootfs instead of relying directly on the iso8660 fs of the ISO. The problem is not BIOS or UEFI related. It is related to the issues in the filesystem used to create the bootable media (iso9660 or fat).
My new forum user/nick name is "the.ridikulus.rat" .
Offline
The issue Skodabenz is talking about seems to address a bug I think I found in archboot.
I have tried (unsecessfully) to install archboot 3 times (more?) on my netbook. The issue is always the same, no matter what I do: when it comes time to install packages the sytem fails and says that an error occured, package installation failed. I am then dropped back into the menu and I cannot continue to install anything.
I have tried work-arounds such as selecting different packages or only using the base + devel packages. So far nothing has worked.
I hope this helps you to continue to develop archboot because this is the only time when I have had genuine issues with archboot. I've tried to test the majority of your releases Tpowa and I thank you for them.
Offline
@tpowa: I think https://gist.github.com/1080899 patch will solve the problem. Please generate a new iso and test it. Thanks in advance.
My new forum user/nick name is "the.ridikulus.rat" .
Offline
tpowa, in the Restore Usbstick section of the Archboot wiki page, could you change the sda references to sdX or <yourdevice>?
ᶘ ᵒᴥᵒᶅ
Offline
A strange thing i'm running into with the latest Archboots, i'm not sure whether this is actually caused by Archboot but maybe you guys have a clue:
I have a Macbook Air 3,2 (2010) which i installed Arch on with Archboot last year, chainloading it from refit in bios mode. I now decided to put a newer Archboot version on the stick, tried both the 2011.06 and 05 versions. The stick is recognized by refit and i can select it as a boot device, yet after the light on the stick starts flickering and the system starts booting, the bootmenu of the already installed grub on sda3 is shown instead of the one on the stick. So whatever i do, i can't actually boot the stick itself.
Any ideas?
ᶘ ᵒᴥᵒᶅ
Offline
Some suggestions:
- Is there really a need for i686 version? We do not talk about a official release and I guess nearly everyone is running x86-64 nowadays? At least people experienting with new software and features.
- Would it be possible to include btrfs-zero-log and other tools from btrfs-progs-unstable in a new release? There is still no sign for a official btrfs repair tool and ar least btrfs-zero-log is very useful and prevents one from installing manually inside archboot.
- Please add a dependency for xorriso in the pkg build, the wiki page as well as in archboot-allinone.sh
Last edited by longint (2011-07-17 14:31:24)
Offline
The stick is recognized by refit and i can select it as a boot device, yet after the light on the stick starts flickering and the system starts booting, the bootmenu of the already installed grub on sda3 is shown instead of the one on the stick. So whatever i do, i can't actually boot the stick itself.
Any ideas?
I've seen this problem, not sure of the cause. I think what I did was add an entry to the bootmenu of the already installed grub, hardcoded to boot from the stick. Here's what worked for me (add to grub.cfg):
menuentry "Stick" {
linux (hd1,msdos1)/boot/vm64 reboot=pci
initrd (hd1,msdos1)/boot/initrd64.img
}
BTW thanks for your posts, I have a macbookair3,1. The install's not yet perfect but that's for another thread.
Offline
There are a few problems due to the epoch ':' (colon) character in grub2 packages now.
For the previous archboot I wrote a script to convert it to a disk image for uefi booting on a macbookair3,1. I used two partitions, the second partition was needed because archboot uses some soft links, which are not supported in FAT. Perhaps a similar approach could be taken here?
Script is at http://pastebin.com/CS1qzuJU
Offline
Some suggestions:
- Is there really a need for i686 version? We do not talk about a official release and I guess nearly everyone is running x86-64 nowadays? At least people experienting with new software and features.
- Would it be possible to include btrfs-zero-log and other tools from btrfs-progs-unstable in a new release? There is still no sign for a official btrfs repair tool and ar least btrfs-zero-log is very useful and prevents one from installing manually inside archboot.
- Please add a dependency for xorriso in the pkg build, the wiki page as well as in archboot-allinone.sh
The programs you are reffering to are not in the package, though i can't add them.
Offline