2009.02 ISO Release

From http://www.archlinux.org/news/434/
Aaron Griffin wrote:
We proudly announce the release of the new Arch Linux installation images, version 2009.02. It took us quite a while, but we think the result is worth it: we added some cool new things and ironed out some long-lasting imperfections.
2009.02 comes with the following features:
- Kernel 2.6.28
- Ext4 support. Installation can be done on a ext4 root partition.
- Rescue and maintenance capabilities for Ext4 root partitions
- Fallback ISOs with the ISOLINUX bootloader, for those that have
  trouble booting Grub-based images
- Several bugfixes in the installer
- Brought the included documentation up-to-date
- Inclusion of AIF (Arch Linux Installation Framework), the next
  generation installer, currently under development.
If you encounter any problems, you can check for bug reports (or file a new one) under the "Release Engineering" project
For more info about the releng team and how to get in touch with us, see the announcement
What's next?
Our goal is to bring coordinated releases following the rhythm of kernel releases, in order to provide optimal hardware support.  The roadmap (and current open bugs) of the next release (which will be based on 2.6.29) can be found on the bug tracker
Download the new release
EDIT: From http://www.archlinux.org/news/435/
The original archlinux-2009.02-ftp-i686.img USB image was broken, a new image (archlinux-2009.02-2-ftp-i686.img) has been uploaded. We are sorry for any inconvenience this may have caused you.
With one image broken, we also had to create new torrents: We now use a single torrent per file again and added more mirrors to the webseeds. All seeders should stop seeding the old torrent and get the new ones.
Last edited by brain0 (2009-02-18 10:43:10)

z0phi3l wrote:Using the new x64 ISO, had one of my smoothest Arch installs yet
Conversely, last night I had the least smooth Arch install I've ever had using the same x64 iso. (First time with x64) While installing kde and then several media players like kaffeine, smplayer and gxine I had at least 5 pacman crashes related to a downloaded file being corrupt. Even opera was reported as being corrupt!
Rerunning the commands eventually got things installed but it slowed down things considerably when things bombed out during what should have been a simple but long download and install process.
Could the corrupt file issues have been caused by the servers getting hammered with the new release?

Similar Messages

  • 2007.08 Don't Panic Isos released, installation feedback

    Hi Arch community,
    5th August, 23:00 CEST (Central European Summer Time)
    Arch Linux Don't-Panic 2007.08 ISO release
    Get Archlinux ISOs in /iso/2007.08/{i686,x86_64}
    on your favorite mirror.
    http://wiki.archlinux.org/index.php/Mirrors
    or
    http://www.archlinux.org/download/
    Please don't forget to check md5sums.
    It's mostly a 2.6.22.x Iso with some fixes to last Linuxtag Isos.
    Changelog to last Duke-Linuxtag2007 installation ISO:
    - kernel 2.6.22.1 usage
    - fixed: update mkinitcpio for new .22 firewire layout
    - fixed: update hwdetect for new rtc_sys and firewire stuff
    - Memory requirements bumped to 128MB!
    - Serial console support in install environment
    - USB Keyboard issues fixed
    Setup changes:
    - fixed: "" around CONSOLEFONT and CONSOLEMAP
    - fixed: dhcp rc.conf entry
    - fixed: not generated glibc locales
    for fixed bugs reference:
    http://bugs.archlinux.org/task/7410
    greetings
    tpowa
    Last edited by tpowa (2007-08-05 20:57:38)

    Installation feedback:
    I installed Arch in virtualbox on a Windows XP host and after it initially hung up on boot (enabling acpi and apic was necessary), everything worked fine.
    I was very pleased to see the pacman mirror selection dialog, apart from a "missing" pacman -Sy (I wondered why I couldn't install xfce4...everything was set up perfectly and it took me a while until I realized, that the local package database only includes the current repository) there was no need for post-configuration for the base system. I haven't checked for rankmirrors this time, but
    Setting up X and xfce4 was done quickly and I had no further problems.
    I was using the FTP-install-image.
    Edit: Stay away from Safari for windows, it will not send or copy text fields containing a '[' or ']', it just cuts away everything following this character.
    Last edited by wuischke (2007-08-06 19:36:03)

  • 2007.08-2 Isos released, installation feedback

    Hi Arch community,
    Arch Linux 2007.08-2, "Don't Panic" has been released.
    This is the first release to use our new repo layout.
    There are two ISOs, ftp and core.
    Changelog:
    GENERAL:
    - kernel 2.6.22.9 usage
    - disabled arch_addons hook by default, it is now triggered by arch-addons
      boot parameter
    - RAM usage has increased, these are the new recommendations:
      - 256 MB (FTP-ISO,CORE-ISO arch boot image)
      - 96 MB (CORE-ISO lowmem boot image)
    FIXES:
    - fixed the nasty /dev mount bug
    - fixed the /dev/ttyS0 errors if no serial port is installed in the system
    - fixed repositories in install environment to fit to both architectures
    - fixed km to not show broken chars after exit
    - fixed grub installing with xfs filesystem
    - fixed package clearing if setup option was chosen
    NEW ITEMS:
    - added pptpclient to install environment
    - added sdparm to install environment
    - added all free wireless drivers to install environment
    - added intel wireless drivers to install environment which will be activated
      by intel-wireless boot parameter
    - added hosts.deny and hosts.allow to config editing dialog
    - added licenses to install environment
    - added new lowmem boot image to core iso
      stripped everything out that is not necessary for installation
    As usual check md5sum before using the images and also be aware of the new
    RAM recommendations the images have.
    Have fun
    greetings
    tpowa

    I think I did it as it should be:
    1. /arch/setup
    2. km
    3. following the menu order
    3.1. Network configuration --> no problem
    3.2. cfdisk --> no problem
    3.3. allowing the partitions + formatting them (reiserfs)--> no problem   (but not sure it formatted: it went so fast)
    3.4. choosing packages --> chose base packages and did not change anything (about 98MB of download) --> no problem
    3.5. kernel installation --> no problem
    3.6. system configuration --> /etc/rc.conf (was good configured, so no modification) and /etc/fstab (had to add hard disk's partitions, /dev/sda2 for windows vista, /dev/sda3 for swap, dev/sda5 for / and /dev/sda6 for /home
    3.7. installing the boot loader (grub), editing /boot/grub/menu.lst and put grub on the MBR --> no problem
    3.8. reboot
    and my system restarted with opensuse10.3 grub, partitions were not changed (my suse is working ext3fs), and my old system was here back and healthy
    I'll have a new try this evening, just to be sure I did not forget something.
    I have userd arch for more than 2 years now and installed it at least 10 times without problem (or with problems I could resolve on my own) but I never had this "non-installation" problem

  • 2007.11-0.4 Isos released, installation feedback

    Hi
    i just placed the new "Core Dump" TEST ISO
    to the mirrors eg:
    ftp://ftp.archlinux.org/other/rc-iso/2007.11/
    1 week testing should be enough,
    I tested them in kvm-qemu and didn't find an issue.
    Changelog:
    GENERAL:
    - kernel 2.6.23.1 usage
    - RAM usage has been revisited, these are the new recommendations:
         * FTP ISO, CORE ISO: arch boot image
           160 MB RAM x86_64/i686 (all packages selected)
         * CORE ISO: lowmem boot image
           96  MB RAM x86_64 (all packages selected)
           85  MB RAM i686   (all packages selected)
           64  MB RAM i686   (only base packages selected)
    FIXES:
    - fixed intel wireless automatic module loading (arch boot image)
    - fixed auto prepare of harddisk (lowmem boot image)
    As usual check md5sum before using the images and also be aware of the new
    RAM recommendations the images have.
    Have fun
    greetings
    tpowa

    The installation went fine.
    just three little things:
    1) I got this message a couple of times:
    "INIT: Id "c0" respawning too fast: disabled for 5 minutes"
    Somewhere on the forum I read that you would try to fix that message, although it's not a real issue, it doesn't look nice either.
    2) I remember this from the other iso's too:
    When I deselect iwlwifi-drivers and install ipw3945-drivers instead, still iwlwifi gets added to the MODULES-line in rc.conf instead of ipw3945; so I have to replace iwlwifi with ipw3945 in the MODULES-line and add the deamon ipw3945d to the DEAMONS-line.
    It's not too much of a bother but it would be better if fixed I suppose, there are quite a lot of people that still need those drivers.
    3) It seems that, in time, a little configuration of the 'Install Packages' part of the installation went wrong.
    From the 'Official Arch Installation Guide' when it comes to the point of 'Package Selection':
    (...)you have the opportunity to specify whole package groups from which you'd generally like to install packages, then fine-tune your coarse selection by (de)selecting individual packages from the groups you have chosen. (...)
    The "Select all packages by default?" question can be easily misunderstood; Basically you are asked whether you want all the packages in the categories you just chose to be selected or not. If you select YES, the whole list of packages contained in the chosen categories will be displayed and selected, and your job will be to deselect what you do not want. If you select NO, the same list of packages will displayed, but only packages of the BASE category will be selected, and you'll have to explicitly select any other packages you want to install.
    With my installations till now, cause I need the ipw3945 driver for example, I always need to check base, lib and support categories. At the question "Select all packages by default?" I always choose NO, but after that I will have to select all base packages myself, so the pre-selection of all base packages is gone somehow. I don't know for how long this is going on cause I am still very newbie.
    That's all I think I hope you did well on you exams; I'm getting behind at university with all this arch-stuff to play with
    Last edited by ibendiben (2007-11-22 19:43:21)

  • 2007.05 Duke ISOs released, installation feedback

    Hi Archlinux Community,
    17th May, 16:10 CEST (Central European Summer Time)
    it's done final 2007.05 Duke ISOs for i686 and x86_64 are ready
    Get Archlinux ISOs in /iso/2007.05/{i686,x86_64} on your favorite mirror.
    Download_Wiki:
    http://wiki.archlinux.org/index.php/Mirrors
    or
    Download_Homepage:
    http://www.archlinux.org/download/
    Please don't forget to check md5sums.
    Torrents are already up and seeded.
    Metalink packages will be prepared soon.
    Changelog to last Voodoo installation ISO:
    - pacman3 usage
    - kernel 2.6.21.1 usage
    Setup changes:
    - soundcards are now also ordered by hwdetect
    - rsync has been added to installation environment
    - proxy support during ftp installation
    - selection to copy installation network setup to final installed system
    - selection about keeping package cache during cd/ftp installation
    - selection of primary pacman sync server added
    - fixed grub installing on software raid devices
    Bug collector of fixed showstoppers is here:
    http://bugs.archlinux.org/task/6767
    I would like to thank you all, who assisted in testing
    and of course finding/fixing bugs, you users/devs simply rock.
    Happy installing and have fun.
    greetings
    tpowa

    Today I installed Duke on my machine, I mentioned two little bumps:
    - Installation via ftp-iso (25MB) doesnt work. Downloading the packages from base doesn't start, but synchronising the package database with the mirrors (I tested it with different ones) works fine before.  There were no error message or something like this, it just happend nothing ... Anyway, I downloaded the base-isos and installed Duke with them. Works fine.
    - While starting XFCE I run into problems with /tmp. By default, it is not writable for every user. Why? Of course, it is easy to fix, but in Voodoo there was no need for that, /tmp was writable for everyone. Is there any reason for this change or is it only a little bug?
    Last edited by Usul (2007-05-17 22:44:34)

  • Latest pacth update on SAP HR(2009 budjet release)

    Hi Folks,
                          we are at the current 26 patch level for SAP HR. Now my client would lillke to migrate to the latest pacth level that is 46. So when we migrate to the 46 level what are all the implications we would likely to have on the current system. So please reply back. thanks

    As long as you are in the same SAP version before and after the patch (e.g. you are already in ECC6) you should not expect major problem as this is not a major upgrade. You just need to test major business processes e.g. run pa30 of some infotypes, try hire pernr, run time evaluation, payroll, pre-dme, dme, some statutory report. You should be covered. You can anticipate what changes is included in the patch by reading the patch notes. By this you can concentrate more on testing these areas.

  • 2009.04-1 archboot "Schlumpi" hybrid image and torrent file released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2009.04-1, "Schlumpi" has been released.
    To avoid confusion, this is not an official arch linux iso release!
    Check Readme.txt file for more information on archboot.
    ftp://ftp.archlinux.org/iso/archboot/Readme.txt
    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:
    ftp://ftp.archlinux.org/iso/archboot/2009.04/
    <yourmirror>/iso/archboot/2009.04/
    Changelog:
    GENERAL:
    - kernel 2.6.29.1 usage
    - pacman 3.2.2 usage
    - RAM  recommendations:
         * arch or arch64 boot image
           256 MB RAM i686/x86_64 (all packages selected, with swap partition)
         * lowmem or lowmem64 boot image
           96 MB RAM i686/x86_64 (all packages selected, with swap partition)
    FIXES:
    - fixed network settings in rc.conf on ftp install and dhcp
    - fixed use mirror from ftp install
    - fixed broken memtest binary
    - fixed broken dmraid
    New Setup Features:
    - Added consistent menu dialog switching
    - Added software raid, lvm2 and luks encrytpion creation support to setup
    - Added new autoconfiguration of mkinitcpio.conf
    - Added ntfs creation support in CD installation
      (uses ntfs-3g, which is not supported in ftp installation mode!)
    - Added root password dialog instead of plain shell dialog
    - Added ext4 support
    Environment changes:
    - added virtio kernel modules for virtualization
    - added crda for correct wireless support
    - added ntfs-3g support
    KNOWN ISSUES:
    - iwlwifi-3945-ucode and ipw2100-fw is not complete.
      Reason: One firmware file is missing.
      Workaround:
      - mount image and install firmware from image file.
        eg. cdrom:
        mount /dev/cdrom /src
        pacman -U /src/core-$(uname -m)/pkg/iwlwifi-3945-ucode-15.28.2.8-1-$(uname-m).pkg.tar.gz
        pacman -U /src/core-$(uname -m)/pkg/ipw2100-fw-3.1-2-$(uname-m).pkg.tar.gz
    - grub cannot detect correct bios boot order.
      It may happen that hd(x,x) entries are not correct,
      thus first reboot may not work.
      Reason: grub cannot detect bios boot order.
      Fix: Either change bios boot order or change menu.lst to correct entries
      after successful boot.
      This cannot be fixed it's a restriction in grub!
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2009-04-25 13:28:59)

    Could you include dhclient in the next iteration of the boot image?
    I'm testing the boot image in virtualbox and dhcpcd can't get a proper configuration using dhcp, everything is correct except the dns servers.
    I believe this may be due to a change (or bug) in vbox but what is curious is that dhclient can get everything right. I've seen threads where other people report having problems with dhcpcd and dhclient working properly (with physical machines I believe). dhclient would be there only as a fallback and would need to be invoked from the command line so it doesn't force any change in the setup scheme.

  • 2011.02-2 archboot "2k11-R1" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2011.02-1, "2k11-R1" 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 full UEFI bootloader support with new grub2 packages.
    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.02/
    <yourmirror>/iso/archboot/2010.12/
    /boot for PXE/Rescue files are provided here:
    https://downloads.archlinux.de/iso/arch … 11.02/boot
    <yourmirror>/iso/archboot/2011.02/boot
    Changelog:
    General:
    - kernel 2.6.37.1 / LTS kernel 2.6.32.29
    - pacman 3.4.3 usage
    - RAM recommendations: 320 MB
    Kernel changes:
    - bump to latest .37 series and bump lts to latest .32 series
    Environment changes:
    - updated to latest syslog-ng 3.2.x
    - updated clamav
    - updated pacman mirrorlist
    - cleanup in hooks and remove redundant code
    - replaced grub by grub2
    setup changes:
    - many internal changes, like use bash test and use brackets for all variables
    - added UEFI bootloader
    - move syslinux and extlinux in one bootloader menu
    - some dmraid fixes
    - add new grub2/grub2-efi package support
    - allow nilfs2 for grub2
    - allow dmraid for grub2
    - install filesystem package, for detected filesystems
    - install dmraid package, if dmraid device is detected
    - fixed cryptsetup device reset
    - some cryptsetup menu additions
    - changed default encryption mode to
      aes-cbc-essiv:sha256 -s 128
    - don't use rootflags, if not necessary
    hwdetect changes:
    - none
    quickinst changes:
    - none
    KNOWN ISSUES:
    - FTP installation mode:
      None
    - CD installation mode:
      None
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2011-02-20 18:14:19)

    steve___ wrote:
    It says:
    Welcome to GRUB! (screen refreshes and these two flash flash on the screen:)
    NO SUITABLE MODE FOUND
    NO VIDEO MODE ACTIVATED
    I choose "Arch Linux (i686) archboot" and get:
    Booting a command list
    After approximately 30 second it times out and the computer reboots
    When grub2 menu loads, highlight the option you want and edit the menu the menu adding these lines to the top of the command list
    rmmod efi_gop
    insmod efi_uga
    set gfxmode=auto
    set gfxpayload=keep
    before "linux ..." line and tell me whether you are getting boot messages on screen. Also archboot grub2-efi menu should show no fallback entries (there aren't any. It should show
    I did this and see no change.  I get the above message of "Booting a command list"
    Can you try removing nomodeset in the "linux ..." line in "Arch Linux (i686) archboot" (edit mode) along with adding the above lines, and reboot.
    Also type in grub2 prompt
    grub> set
    and tell me what it it show for _EFI_ARCH= , i386 or x86_64 .
    It says "i386".
    You have 32-bit EFI, which is very old. You need to remove efi booting support from archboot. Extract archboot iso to any dir. Install extra/{libisoburn,libisofs,libburn} packages. Cd into the extracted dir and run
    xorriso -as mkisofs -rock -joliet \
    -max-iso9660-filenames -omit-period \
    -omit-version-number -allow-leading-dots \
    -relaxed-filenames -allow-lowercase -allow-multidot \
    -volid "ARCHBOOT" \
    -eltorito-boot boot/syslinux/isolinux.bin \
    -eltorito-catalog boot/syslinux/boot.cat \
    -no-emul-boot -boot-load-size 4 -boot-info-table \
    -output ../archboot.iso ./
    Last night I booted an old CD, 2009.08.  I did the install and tried to use grub2 as the bootloader with no success.  I tried both the 'grub2-bios' and 'grub2-efi-i386' installing them to /dev/sda.  On reboot I don't get a grub prompt, just the message "No bootable device -- insert boot disk and press any key".
    What was the exact error? Did you read http://wiki.archlinux.org/index.php/GRUB2 instructions?
    I may give up after this, use the 2009.08 boot CD and try to use the grub/MBR method as I was using.  The reason I decided to try grub2 was I just installed an SSD.  In the archwiki grub2 it suggests "By default, Apple's firmware switches SATA drives into IDE mode (not AHCI mode) when booting any OS besides Mac OS. It is easy to switch back to AHCI if you are using GRUB2 with an Intel SATA controller."  This can be done by setting:
    setpci -d 8086:27c4 90.b=40
    in /etc/grub/grub/cfg
    I understand these questions are OT, but I thought I'd ask:
    1) Does GPT have any other advantage than setting the starting sector to 2048?  I was thinking of using fdisk to do this along with grub (not grub2) -- Are there any flaws in my ignorance?
    2) Do you know if it's possible to set AHCI mode with grub?
    1) Using fdisk itself was a mistake. Macs use GPT and you should have used gdisk (available in archboot iso and latest releng test isos  http://releng.archlinux.org/isos/).
    2) No idea about AHCI. Like I said I don't have a Mac to try these things.

  • 2011.05-2 archboot "2k11-R2" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2011.05-2, "2k11-R2" 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.2
    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.05/
    <yourmirror>/iso/archboot/2011.05/
    /boot for PXE/Rescue files are provided here:
    https://downloads.archlinux.de/iso/arch … 11.05/boot
    <yourmirror>/iso/archboot/2011.05/boot
    Changelog:
    GENERAL:
    - kernel 2.6.38.6 / LTS kernel 2.6.32.40
    - pacman 3.5.2 usage
    - RAM recommendations: 320 MB
    Kernel changes:
    - bump to latest .38 series and bump lts to latest .32 series
    Removed features:
    - clamav removed
    Environment changes:
    - merged in latest initscripts and mkinitcpio changes
    - updated pacman mirrorlist
    - added cifs-utils, eject and file to environment
    - switched to krb5 and dropped heimdal
    setup changes:
    - allow btrfs for grub2
    hwdetect changes:
    - none
    quickinst changes:
    - none
    KNOWN ISSUES:
    - FTP installation mode:
      None
    - CD installation mode:
      None
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2011-05-17 05:23:58)

    Angus_Yann wrote:Archboot is really awesome! And I have two pieces of suggestion which may help.
    1. Don't know it's my USB stick's problem or whaterever, it cannot mount core-*/pkg direction automatically. So I can only install via net for I really don't know how to mount manually.
    2. Actually I suddenly forget what to say. Hmmm, maybe it's a little bit complex for a newbie for there's not enough resources available to guide. Because some part of the installation is different from the official one.
    OK, that's all. And thanks for bringing us Archboot.
    1. I gave you already an answer in my previous post, I don't know why your drive is not mounted autumatically the setup routine has a function to mount cd drive and usb drives.
    ls /dev/sd* would be interesting or ls /dev/mmc*
    2. It's not that different all is mentioned on the wiki imho, if something is missing just raise your questions here and I try to fix things, if needed.
    Enjoy Arch and of course archboot

  • 2011.07-2 archboot "2k11-R4" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2011.07-2, "2k11-R4" 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, plain bugfix release.
    KNOWN ISSUE  READ 1ST:
    If you use this ISO or 2k11-R3 please delete these 2 files:
    /tmp/install/etc/modprobe.d/blacklist_net.conf
    /tmp/install/etc/modprobe.d/blacklist_sound.conf
    before you reboot to your real system.
    Or remove the files from your existing system:
    /etc/modprobe.d/blacklist_net.conf
    /etc/modprobe.d/blacklist_sound.conf
    else you will end up with no network or sound.
    Please also cleanup /etc/rc.conf file MODULES= array
    Sorry for the inconvience, blacklisting and loading of modules changed,
    next version will not suffer from this anymore.
    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.07/
    <yourmirror>/iso/archboot/2011.07/
    /boot for PXE/Rescue files are provided here:
    https://downloads.archlinux.de/iso/arch … 11.07/boot
    <yourmirror>/iso/archboot/2011.07/boot
    Changelog:
    GENERAL:
    - kernel 2.6.39.3 / LTS kernel 2.6.32.43
    - 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:
    - tcp_wrappers removed
    Environment changes:
    - merged in latest mkinitcpio changes
    - removed i386-efi install media boot support
    hwdetect changes:
    - none
    setup changes:
    - added ro bootoptions to all bootloaders
    - changed cdrom package installation to use the squashfs tarballs
    quickinst changes:
    - none
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2011-08-07 20:46:09)

    broken pipe wrote:yes encrypted lvm, msdos partition table created with fdisk. i install this setup ~once in two month, 1.5mb are reserved in front of the first partition. even when i chroot into the installation and reinstall the mbr again, it doesn't work. but after the syslinux installation it works now
    Post the output of
    sudo /sbin/grub_bios-install --boot-directory=/boot --no-floppy --recheck --debug /dev/<your device>
    EDIT 1: Also what is the file size of /boot/grub/core.img ? The gap after 512 byte MBR region should be able to accommodate the core.img file.
    EDIT 2: Maybe we should take this to a new thread since this problem seems to be independent of Archboot.
    Last edited by skodabenz (2011-07-30 19:15:26)

  • 2011.08-2 archboot "2k11-R5" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2011.08-2, "2k11-R5" 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:
    - merge in linux 3.0 changes, plain bugfix release.
    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.08/
    <yourmirror>/iso/archboot/2011.08/
    /boot for PXE/Rescue files are provided here:
    https://downloads.archlinux.de/iso/arch … 11.08/boot
    <yourmirror>/iso/archboot/2011.08/boot
    Changelog:
    GENERAL:
    - kernel 3.0.1 / LTS kernel 2.6.32.44
    - pacman 3.5.3 usage
    - RAM recommendations: 320 MB
    Kernel changes:
    - bump to latest 3.0 series and bump lts to latest .32 series
    Removed features:
    - none
    Environment changes:
    - removed hwdetect module loading, all is done by udev now
    - removed vmware detection hook, old and not needed anymore
    - new ide_blacklist hook for ide-legacy usage
    hwdetect changes:
    - code cleanup
    - removed module blacklisting
    - added udev rule generation for persistent network names
    - added modprobe.conf file generation for persistent sound cards
    setup changes:
    - changed everything for linux 3.0
    quickinst changes:
    - changed everything for linux 3.0
    Known Issue:
    - creating swapspace bigger than 2GB is broken!
      use LTS kernel for swapspace bigger than 2GB, will be fixed in 2011.09!
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2011-08-16 08:08:06)

    adee wrote:
    zenlord wrote:
    Installation went without a hiccup. BTRFS for /.
    THX!
    Without fsck? Is that safe?
    The system that was installed is only used as a printserver for someone's 3rd printer - It's more of a testcase than a critical production-system
    BTW: I had to revisit the system because it appeared that grub2 was installed, but the timeout was not set, so grub2 would wait until a key was pressed. Running a
    '# grub-mkconfig -o /boot/grub/grub.cfg'
    was enough to get it to work, but it probably means something did go wrong with the install, which means there is still room for improvement (albeit veeeeeery little )

  • 2011.10-1 archboot "2k11-R6" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2011.10-1, "2k11-R6" 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:
    - Only use one lzma initrd for each architecture, plain bugfix release.
    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.10/
    <yourmirror>/iso/archboot/2011.10/
    /boot for PXE/Rescue files are provided here:
    https://downloads.archlinux.de/iso/arch … 11.10/boot
    <yourmirror>/iso/archboot/2011.10/boot
    Changelog:
    GENERAL:
    - kernel 3.0.6 / LTS kernel 2.6.32.46
    - pacman 3.5.4 usage
    - RAM recommendations: 320 MB
    Kernel changes:
    - bump to latest 3.0 series and bump lts to latest .32 series
    Removed features:
    - none
    Environment changes:
    - added smartmontools, dnsmasq, lftp, openconnect, speedtouch, nmap, tcpdump, weechat packages.
    - added Hyper-V ( hv_ ) kernel modules
    - updated pacman mirrorlist
    hwdetect changes:
    - none
    setup changes:
    - use cgdisk for GPT partitioning
    quickinst changes:
    - none
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2011-10-27 07:52:40)

    the.ridikulus.rat wrote:
    Is this problem occurring in latest Archboot iso or in some earlier version? The latest one had few changes in the way initramfs is created (one initramfs per arch, not one per kernel). Can you boot into the latest archboot and check whether
    /lib/modules/3.0-ARCH/kernel/drivers/firmware/efivars.ko.gz
    file exists?
    Also can you post the output of
    # dmesg | grep -i EFI
    from within archboot?
    It is the latest Archboot (2011.10-1) and /lib/modules/3.0-ARCH/kernel/drivers/firmware/efivars.ko.gz doesn't exist.
    dmesg | grep -i EFI shows the following:
    [ 0.000000] Command line: BOOT_IMAGE=/boot/vm64 ro add_efi_memmap none=UEFI_ARCH_x86_64 radeon.modeset=0
    [ 0.000000] EFI v2.10 by American Megatrends
    [ 0.000000] Kernel-defined memdesc doesn't match the one from EFI!
    [ 0.000000] EFI: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
    [ 0.000000] EFI: mem01: type=7, attr=0xf, range=[0x0000000000008000-0x000000000007f000) (0MB)
    [ 0.000000] EFI: mem02: type=4, attr=0xf, range=[0x000000000007f000-0x0000000000080000) (0MB)
    [ 0.000000] EFI: mem03: type=3, attr=0xf, range=[0x0000000000080000-0x00000000000a0000) (0MB)
    [ 0.000000] EFI: mem04: type=2, attr=0xf, range=[0x0000000000100000-0x00000000003de000) (2MB)
    [ 0.000000] EFI: mem05: type=7, attr=0xf, range=[0x00000000003de000-0x0000000001000000) (12MB)
    [ 0.000000] EFI: mem06: type=2, attr=0xf, range=[0x0000000001000000-0x0000000001100000) (1MB)
    [ 0.000000] EFI: mem07: type=4, attr=0xf, range=[0x0000000001100000-0x000000000136b000) (2MB)
    [ 0.000000] EFI: mem08: type=3, attr=0xf, range=[0x000000000136b000-0x000000000136f000) (0MB)
    [ 0.000000] EFI: mem09: type=4, attr=0xf, range=[0x000000000136f000-0x000000000139d000) (0MB)
    [ 0.000000] EFI: mem10: type=3, attr=0xf, range=[0x000000000139d000-0x000000000139f000) (0MB)
    [ 0.000000] EFI: mem11: type=4, attr=0xf, range=[0x000000000139f000-0x00000000013a0000) (0MB)
    [ 0.000000] EFI: mem12: type=3, attr=0xf, range=[0x00000000013a0000-0x00000000013a8000) (0MB)
    [ 0.000000] EFI: mem13: type=4, attr=0xf, range=[0x00000000013a8000-0x00000000013ae000) (0MB)
    [ 0.000000] EFI: mem14: type=3, attr=0xf, range=[0x00000000013ae000-0x00000000013b1000) (0MB)
    [ 0.000000] EFI: mem15: type=4, attr=0xf, range=[0x00000000013b1000-0x00000000013b2000) (0MB)
    [ 0.000000] EFI: mem16: type=3, attr=0xf, range=[0x00000000013b2000-0x00000000013b5000) (0MB)
    [ 0.000000] EFI: mem17: type=4, attr=0xf, range=[0x00000000013b5000-0x00000000013bb000) (0MB)
    [ 0.000000] EFI: mem18: type=3, attr=0xf, range=[0x00000000013bb000-0x00000000013bc000) (0MB)
    [ 0.000000] EFI: mem19: type=4, attr=0xf, range=[0x00000000013bc000-0x00000000013bd000) (0MB)
    [ 0.000000] EFI: mem20: type=3, attr=0xf, range=[0x00000000013bd000-0x00000000013be000) (0MB)
    [ 0.000000] EFI: mem21: type=4, attr=0xf, range=[0x00000000013be000-0x00000000013c0000) (0MB)
    [ 0.000000] EFI: mem22: type=3, attr=0xf, range=[0x00000000013c0000-0x00000000013c1000) (0MB)
    [ 0.000000] EFI: mem23: type=4, attr=0xf, range=[0x00000000013c1000-0x00000000013c9000) (0MB)
    [ 0.000000] EFI: mem24: type=3, attr=0xf, range=[0x00000000013c9000-0x00000000013cc000) (0MB)
    [ 0.000000] EFI: mem25: type=4, attr=0xf, range=[0x00000000013cc000-0x00000000013d6000) (0MB)
    [ 0.000000] EFI: mem26: type=3, attr=0xf, range=[0x00000000013d6000-0x00000000013db000) (0MB)
    [ 0.000000] EFI: mem27: type=4, attr=0xf, range=[0x00000000013db000-0x00000000013e6000) (0MB)
    [ 0.000000] EFI: mem28: type=3, attr=0xf, range=[0x00000000013e6000-0x00000000013ec000) (0MB)
    [ 0.000000] EFI: mem29: type=4, attr=0xf, range=[0x00000000013ec000-0x00000000013ed000) (0MB)
    [ 0.000000] EFI: mem30: type=3, attr=0xf, range=[0x00000000013ed000-0x00000000013f4000) (0MB)
    [ 0.000000] EFI: mem31: type=4, attr=0xf, range=[0x00000000013f4000-0x00000000013ff000) (0MB)
    [ 0.000000] EFI: mem32: type=3, attr=0xf, range=[0x00000000013ff000-0x0000000001400000) (0MB)
    [ 0.000000] EFI: mem33: type=4, attr=0xf, range=[0x0000000001400000-0x0000000001b8d000) (7MB)
    [ 0.000000] EFI: mem34: type=3, attr=0xf, range=[0x0000000001b8d000-0x0000000001b8f000) (0MB)
    [ 0.000000] EFI: mem35: type=4, attr=0xf, range=[0x0000000001b8f000-0x0000000001bc3000) (0MB)
    [ 0.000000] EFI: mem36: type=3, attr=0xf, range=[0x0000000001bc3000-0x0000000001bc5000) (0MB)
    [ 0.000000] EFI: mem37: type=4, attr=0xf, range=[0x0000000001bc5000-0x0000000001bcd000) (0MB)
    [ 0.000000] EFI: mem38: type=3, attr=0xf, range=[0x0000000001bcd000-0x0000000001be8000) (0MB)
    [ 0.000000] EFI: mem39: type=4, attr=0xf, range=[0x0000000001be8000-0x0000000001bf7000) (0MB)
    [ 0.000000] EFI: mem40: type=3, attr=0xf, range=[0x0000000001bf7000-0x0000000001c0a000) (0MB)
    [ 0.000000] EFI: mem41: type=4, attr=0xf, range=[0x0000000001c0a000-0x0000000001c0c000) (0MB)
    [ 0.000000] EFI: mem42: type=3, attr=0xf, range=[0x0000000001c0c000-0x0000000001c0f000) (0MB)
    [ 0.000000] EFI: mem43: type=4, attr=0xf, range=[0x0000000001c0f000-0x0000000001c10000) (0MB)
    [ 0.000000] EFI: mem44: type=3, attr=0xf, range=[0x0000000001c10000-0x0000000001c16000) (0MB)
    [ 0.000000] EFI: mem45: type=4, attr=0xf, range=[0x0000000001c16000-0x0000000001c17000) (0MB)
    [ 0.000000] EFI: mem46: type=3, attr=0xf, range=[0x0000000001c17000-0x0000000001c24000) (0MB)
    [ 0.000000] EFI: mem47: type=4, attr=0xf, range=[0x0000000001c24000-0x0000000001c28000) (0MB)
    [ 0.000000] EFI: mem48: type=3, attr=0xf, range=[0x0000000001c28000-0x0000000001c2a000) (0MB)
    [ 0.000000] EFI: mem49: type=4, attr=0xf, range=[0x0000000001c2a000-0x0000000001c2c000) (0MB)
    [ 0.000000] EFI: mem50: type=3, attr=0xf, range=[0x0000000001c2c000-0x0000000001c2d000) (0MB)
    [ 0.000000] EFI: mem51: type=4, attr=0xf, range=[0x0000000001c2d000-0x0000000001c35000) (0MB)
    [ 0.000000] EFI: mem52: type=3, attr=0xf, range=[0x0000000001c35000-0x0000000001c4e000) (0MB)
    [ 0.000000] EFI: mem53: type=4, attr=0xf, range=[0x0000000001c4e000-0x0000000001c51000) (0MB)
    [ 0.000000] EFI: mem54: type=3, attr=0xf, range=[0x0000000001c51000-0x0000000001c59000) (0MB)
    [ 0.000000] EFI: mem55: type=4, attr=0xf, range=[0x0000000001c59000-0x0000000001c60000) (0MB)
    [ 0.000000] EFI: mem56: type=3, attr=0xf, range=[0x0000000001c60000-0x0000000001c67000) (0MB)
    [ 0.000000] EFI: mem57: type=4, attr=0xf, range=[0x0000000001c67000-0x0000000001c7c000) (0MB)
    [ 0.000000] EFI: mem58: type=3, attr=0xf, range=[0x0000000001c7c000-0x0000000001c87000) (0MB)
    [ 0.000000] EFI: mem59: type=4, attr=0xf, range=[0x0000000001c87000-0x0000000001c89000) (0MB)
    [ 0.000000] EFI: mem60: type=3, attr=0xf, range=[0x0000000001c89000-0x0000000001c90000) (0MB)
    [ 0.000000] EFI: mem61: type=4, attr=0xf, range=[0x0000000001c90000-0x0000000001c91000) (0MB)
    [ 0.000000] EFI: mem62: type=3, attr=0xf, range=[0x0000000001c91000-0x0000000001c95000) (0MB)
    [ 0.000000] EFI: mem63: type=4, attr=0xf, range=[0x0000000001c95000-0x0000000001cb4000) (0MB)
    [ 0.000000] EFI: mem64: type=3, attr=0xf, range=[0x0000000001cb4000-0x0000000001cb7000) (0MB)
    [ 0.000000] EFI: mem65: type=4, attr=0xf, range=[0x0000000001cb7000-0x0000000001cbf000) (0MB)
    [ 0.000000] EFI: mem66: type=3, attr=0xf, range=[0x0000000001cbf000-0x0000000001cc3000) (0MB)
    [ 0.000000] EFI: mem67: type=4, attr=0xf, range=[0x0000000001cc3000-0x0000000001cd0000) (0MB)
    [ 0.000000] EFI: mem68: type=3, attr=0xf, range=[0x0000000001cd0000-0x0000000001cd1000) (0MB)
    [ 0.000000] EFI: mem69: type=4, attr=0xf, range=[0x0000000001cd1000-0x0000000001cd4000) (0MB)
    [ 0.000000] EFI: mem70: type=3, attr=0xf, range=[0x0000000001cd4000-0x0000000001cdb000) (0MB)
    [ 0.000000] EFI: mem71: type=4, attr=0xf, range=[0x0000000001cdb000-0x0000000001cdd000) (0MB)
    [ 0.000000] EFI: mem72: type=3, attr=0xf, range=[0x0000000001cdd000-0x0000000001ce2000) (0MB)
    [ 0.000000] EFI: mem73: type=4, attr=0xf, range=[0x0000000001ce2000-0x0000000001ce3000) (0MB)
    [ 0.000000] EFI: mem74: type=3, attr=0xf, range=[0x0000000001ce3000-0x0000000001d38000) (0MB)
    [ 0.000000] EFI: mem75: type=4, attr=0xf, range=[0x0000000001d38000-0x0000000001d44000) (0MB)
    [ 0.000000] EFI: mem76: type=3, attr=0xf, range=[0x0000000001d44000-0x0000000001d45000) (0MB)
    [ 0.000000] EFI: mem77: type=4, attr=0xf, range=[0x0000000001d45000-0x0000000001d46000) (0MB)
    [ 0.000000] EFI: mem78: type=3, attr=0xf, range=[0x0000000001d46000-0x0000000001d49000) (0MB)
    [ 0.000000] EFI: mem79: type=4, attr=0xf, range=[0x0000000001d49000-0x0000000001d51000) (0MB)
    [ 0.000000] EFI: mem80: type=3, attr=0xf, range=[0x0000000001d51000-0x0000000001d55000) (0MB)
    [ 0.000000] EFI: mem81: type=4, attr=0xf, range=[0x0000000001d55000-0x0000000001d57000) (0MB)
    [ 0.000000] EFI: mem82: type=3, attr=0xf, range=[0x0000000001d57000-0x0000000001d59000) (0MB)
    [ 0.000000] EFI: mem83: type=4, attr=0xf, range=[0x0000000001d59000-0x0000000001d6a000) (0MB)
    [ 0.000000] EFI: mem84: type=3, attr=0xf, range=[0x0000000001d6a000-0x0000000001d6c000) (0MB)
    [ 0.000000] EFI: mem85: type=4, attr=0xf, range=[0x0000000001d6c000-0x0000000001d6e000) (0MB)
    [ 0.000000] EFI: mem86: type=3, attr=0xf, range=[0x0000000001d6e000-0x0000000001d70000) (0MB)
    [ 0.000000] EFI: mem87: type=4, attr=0xf, range=[0x0000000001d70000-0x0000000001d71000) (0MB)
    [ 0.000000] EFI: mem88: type=3, attr=0xf, range=[0x0000000001d71000-0x0000000001d72000) (0MB)
    [ 0.000000] EFI: mem89: type=4, attr=0xf, range=[0x0000000001d72000-0x0000000001d77000) (0MB)
    [ 0.000000] EFI: mem90: type=3, attr=0xf, range=[0x0000000001d77000-0x0000000001d7b000) (0MB)
    [ 0.000000] EFI: mem91: type=4, attr=0xf, range=[0x0000000001d7b000-0x0000000002257000) (4MB)
    [ 0.000000] EFI: mem92: type=3, attr=0xf, range=[0x0000000002257000-0x000000000225b000) (0MB)
    [ 0.000000] EFI: mem93: type=4, attr=0xf, range=[0x000000000225b000-0x000000000225d000) (0MB)
    [ 0.000000] EFI: mem94: type=3, attr=0xf, range=[0x000000000225d000-0x000000000225f000) (0MB)
    [ 0.000000] EFI: mem95: type=4, attr=0xf, range=[0x000000000225f000-0x0000000002262000) (0MB)
    [ 0.000000] EFI: mem96: type=3, attr=0xf, range=[0x0000000002262000-0x0000000002265000) (0MB)
    [ 0.000000] EFI: mem97: type=4, attr=0xf, range=[0x0000000002265000-0x0000000002270000) (0MB)
    [ 0.000000] EFI: mem98: type=3, attr=0xf, range=[0x0000000002270000-0x0000000002272000) (0MB)
    [ 0.000000] EFI: mem99: type=4, attr=0xf, range=[0x0000000002272000-0x000000000227b000) (0MB)
    [ 0.000000] EFI: mem100: type=3, attr=0xf, range=[0x000000000227b000-0x0000000002288000) (0MB)
    [ 0.000000] EFI: mem101: type=4, attr=0xf, range=[0x0000000002288000-0x000000000228a000) (0MB)
    [ 0.000000] EFI: mem102: type=3, attr=0xf, range=[0x000000000228a000-0x000000000228b000) (0MB)
    [ 0.000000] EFI: mem103: type=4, attr=0xf, range=[0x000000000228b000-0x0000000002290000) (0MB)
    [ 0.000000] EFI: mem104: type=3, attr=0xf, range=[0x0000000002290000-0x0000000002292000) (0MB)
    [ 0.000000] EFI: mem105: type=4, attr=0xf, range=[0x0000000002292000-0x0000000002298000) (0MB)
    [ 0.000000] EFI: mem106: type=3, attr=0xf, range=[0x0000000002298000-0x000000000229d000) (0MB)
    [ 0.000000] EFI: mem107: type=4, attr=0xf, range=[0x000000000229d000-0x00000000022a5000) (0MB)
    [ 0.000000] EFI: mem108: type=3, attr=0xf, range=[0x00000000022a5000-0x00000000022a9000) (0MB)
    [ 0.000000] EFI: mem109: type=4, attr=0xf, range=[0x00000000022a9000-0x00000000022d5000) (0MB)
    [ 0.000000] EFI: mem110: type=3, attr=0xf, range=[0x00000000022d5000-0x00000000022e6000) (0MB)
    [ 0.000000] EFI: mem111: type=4, attr=0xf, range=[0x00000000022e6000-0x000000000258c000) (2MB)
    [ 0.000000] EFI: mem112: type=3, attr=0xf, range=[0x000000000258c000-0x0000000002590000) (0MB)
    [ 0.000000] EFI: mem113: type=4, attr=0xf, range=[0x0000000002590000-0x0000000002592000) (0MB)
    [ 0.000000] EFI: mem114: type=3, attr=0xf, range=[0x0000000002592000-0x0000000002594000) (0MB)
    [ 0.000000] EFI: mem115: type=4, attr=0xf, range=[0x0000000002594000-0x0000000002596000) (0MB)
    [ 0.000000] EFI: mem116: type=3, attr=0xf, range=[0x0000000002596000-0x0000000002598000) (0MB)
    [ 0.000000] EFI: mem117: type=4, attr=0xf, range=[0x0000000002598000-0x000000000275d000) (1MB)
    [ 0.000000] EFI: mem118: type=3, attr=0xf, range=[0x000000000275d000-0x000000000276d000) (0MB)
    [ 0.000000] EFI: mem119: type=4, attr=0xf, range=[0x000000000276d000-0x0000000002772000) (0MB)
    [ 0.000000] EFI: mem120: type=3, attr=0xf, range=[0x0000000002772000-0x0000000002775000) (0MB)
    [ 0.000000] EFI: mem121: type=4, attr=0xf, range=[0x0000000002775000-0x000000000277a000) (0MB)
    [ 0.000000] EFI: mem122: type=3, attr=0xf, range=[0x000000000277a000-0x000000000277c000) (0MB)
    [ 0.000000] EFI: mem123: type=4, attr=0xf, range=[0x000000000277c000-0x0000000002780000) (0MB)
    [ 0.000000] EFI: mem124: type=7, attr=0xf, range=[0x0000000002780000-0x0000000002781000) (0MB)
    [ 0.000000] EFI: mem125: type=3, attr=0xf, range=[0x0000000002781000-0x0000000002783000) (0MB)
    [ 0.000000] EFI: mem126: type=7, attr=0xf, range=[0x0000000002783000-0x0000000002787000) (0MB)
    [ 0.000000] EFI: mem127: type=4, attr=0xf, range=[0x0000000002787000-0x000000000278b000) (0MB)
    [ 0.000000] EFI: mem128: type=7, attr=0xf, range=[0x000000000278b000-0x000000000279c000) (0MB)
    [ 0.000000] EFI: mem129: type=4, attr=0xf, range=[0x000000000279c000-0x0000000002840000) (0MB)
    [ 0.000000] EFI: mem130: type=7, attr=0xf, range=[0x0000000002840000-0x000000000285a000) (0MB)
    [ 0.000000] EFI: mem131: type=4, attr=0xf, range=[0x000000000285a000-0x0000000002b12000) (2MB)
    [ 0.000000] EFI: mem132: type=7, attr=0xf, range=[0x0000000002b12000-0x0000000002b2c000) (0MB)
    [ 0.000000] EFI: mem133: type=4, attr=0xf, range=[0x0000000002b2c000-0x0000000002ba3000) (0MB)
    [ 0.000000] EFI: mem134: type=7, attr=0xf, range=[0x0000000002ba3000-0x0000000002bbe000) (0MB)
    [ 0.000000] EFI: mem135: type=4, attr=0xf, range=[0x0000000002bbe000-0x0000000002bd9000) (0MB)
    [ 0.000000] EFI: mem136: type=7, attr=0xf, range=[0x0000000002bd9000-0x0000000002caa000) (0MB)
    [ 0.000000] EFI: mem137: type=1, attr=0xf, range=[0x0000000002caa000-0x0000000002d7b000) (0MB)
    [ 0.000000] EFI: mem138: type=7, attr=0xf, range=[0x0000000002d7b000-0x000000002d6c0000) (681MB)
    [ 0.000000] EFI: mem139: type=2, attr=0xf, range=[0x000000002d6c0000-0x0000000032b58000) (84MB)
    [ 0.000000] EFI: mem140: type=7, attr=0xf, range=[0x0000000032b58000-0x000000008fccf000) (1489MB)
    [ 0.000000] EFI: mem141: type=2, attr=0xf, range=[0x000000008fccf000-0x00000000bf1fc000) (757MB)
    [ 0.000000] EFI: mem142: type=10, attr=0xf, range=[0x00000000bf1fc000-0x00000000bf245000) (0MB)
    [ 0.000000] EFI: mem143: type=9, attr=0xf, range=[0x00000000bf245000-0x00000000bf24e000) (0MB)
    [ 0.000000] EFI: mem144: type=6, attr=0x800000000000000f, range=[0x00000000bf24e000-0x00000000bf302000) (0MB)
    [ 0.000000] EFI: mem145: type=10, attr=0xf, range=[0x00000000bf302000-0x00000000bf305000) (0MB)
    [ 0.000000] EFI: mem146: type=7, attr=0xf, range=[0x00000000bf305000-0x00000000bf306000) (0MB)
    [ 0.000000] EFI: mem147: type=6, attr=0x800000000000000f, range=[0x00000000bf306000-0x00000000bf30a000) (0MB)
    [ 0.000000] EFI: mem148: type=0, attr=0xf, range=[0x00000000bf30a000-0x00000000bf551000) (2MB)
    [ 0.000000] EFI: mem149: type=5, attr=0x800000000000000f, range=[0x00000000bf551000-0x00000000bf55d000) (0MB)
    [ 0.000000] EFI: mem150: type=0, attr=0xf, range=[0x00000000bf55d000-0x00000000bf560000) (0MB)
    [ 0.000000] EFI: mem151: type=6, attr=0x800000000000000f, range=[0x00000000bf560000-0x00000000bf561000) (0MB)
    [ 0.000000] EFI: mem152: type=7, attr=0xf, range=[0x00000000bf561000-0x00000000bf562000) (0MB)
    [ 0.000000] EFI: mem153: type=5, attr=0x800000000000000f, range=[0x00000000bf562000-0x00000000bf563000) (0MB)
    [ 0.000000] EFI: mem154: type=0, attr=0xf, range=[0x00000000bf563000-0x00000000bf573000) (0MB)
    [ 0.000000] EFI: mem155: type=10, attr=0xf, range=[0x00000000bf573000-0x00000000bf57b000) (0MB)
    [ 0.000000] EFI: mem156: type=5, attr=0x800000000000000f, range=[0x00000000bf57b000-0x00000000bf580000) (0MB)
    [ 0.000000] EFI: mem157: type=6, attr=0x800000000000000f, range=[0x00000000bf580000-0x00000000bf592000) (0MB)
    [ 0.000000] EFI: mem158: type=5, attr=0x800000000000000f, range=[0x00000000bf592000-0x00000000bf5a2000) (0MB)
    [ 0.000000] EFI: mem159: type=6, attr=0x800000000000000f, range=[0x00000000bf5a2000-0x00000000bf5a5000) (0MB)
    [ 0.000000] EFI: mem160: type=10, attr=0xf, range=[0x00000000bf5a5000-0x00000000bf7a8000) (2MB)
    [ 0.000000] EFI: mem161: type=4, attr=0xf, range=[0x00000000bf7a8000-0x00000000bf8e7000) (1MB)
    [ 0.000000] EFI: mem162: type=3, attr=0xf, range=[0x00000000bf8e7000-0x00000000bfb65000) (2MB)
    [ 0.000000] EFI: mem163: type=4, attr=0xf, range=[0x00000000bfb65000-0x00000000bfb70000) (0MB)
    [ 0.000000] EFI: mem164: type=3, attr=0xf, range=[0x00000000bfb70000-0x00000000bfb72000) (0MB)
    [ 0.000000] EFI: mem165: type=6, attr=0x800000000000000f, range=[0x00000000bfb72000-0x00000000bfef4000) (3MB)
    [ 0.000000] EFI: mem166: type=4, attr=0xf, range=[0x00000000bfef4000-0x00000000bff00000) (0MB)
    [ 0.000000] EFI: mem167: type=7, attr=0xf, range=[0x0000000100001000-0x000000041f000000) (12783MB)
    [ 0.000000] EFI: mem168: type=11, attr=0x8000000000000001, range=[0x00000000e0000000-0x00000000f0000000) (256MB)
    [ 0.000000] EFI: mem169: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    [ 0.000000] EFI: mem170: type=11, attr=0x8000000000000001, range=[0x00000000fec10000-0x00000000fec11000) (0MB)
    [ 0.000000] EFI: mem171: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed01000) (0MB)
    [ 0.000000] EFI: mem172: type=11, attr=0x8000000000000001, range=[0x00000000fed40000-0x00000000fed45000) (0MB)
    [ 0.000000] EFI: mem173: type=11, attr=0x8000000000000001, range=[0x00000000fed61000-0x00000000fed71000) (0MB)
    [ 0.000000] EFI: mem174: type=11, attr=0x8000000000000001, range=[0x00000000fed80000-0x00000000fed90000) (0MB)
    [ 0.000000] EFI: mem175: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
    [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vm64 ro add_efi_memmap none=UEFI_ARCH_x86_64 radeon.modeset=0
    [ 12.642285] efifb: probing for efifb
    [ 12.642575] efifb: framebuffer at 0xc0000000, mapped to 0xffffc90023700000, using 1920k, total 1920k
    [ 12.642577] efifb: mode is 800x600x32, linelength=3200, pages=1
    [ 12.642579] efifb: scrolling: redraw
    [ 12.642581] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 12.645422] fb0: EFI VGA frame buffer device
    [ 13.543402] Refined TSC clocksource calibration: 2595.278 MHz.

  • 2012.01-1 archboot "2k12-R1" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2012.01-1, "2k12-R1" 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:
    - pacman4 introduction, new LTS 3.0.x kernel and uefi shell
    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/2012.01/
    <yourmirror>/iso/archboot/2012.01/
    /boot for PXE/Rescue files are provided here:
    https://downloads.archlinux.de/iso/arch … 12.01/boot
    <yourmirror>/iso/archboot/2012.01/boot
    Changelog:
    GENERAL:
    - kernel 3.2.1 / LTS kernel 3.0.17
    - pacman 4.0.1 usage
    - RAM recommendations: 512 MB
    Kernel changes:
    - bump to latest 3.2.x series and bump lts to latest 3.0.x series
    Removed features:
    - None
    Environment changes:
    - added pacman4
    - bumped lts kernel
    - added kmod insted of module-init-tools
    - synced with latest mkinitcpio changes
    - added uefi shell
    hwdetect changes:
    - added fsck hook
    - added shutdown hook
    setup changes:
    - adopt pacman4 changes
    - adopt lts kernel changes
    - added btrfs compression option
    - allow btrfs on lts kernel
    - added separate /usr detection
    - fixed manual mounting of install media
    - try to detect (using dmidecode) whether the UEFI boot has occured in a Mac
    quickinst changes:
    - adopt pacman4 changes
    - adopt lts kernel changes
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2012-01-28 10:45:14)

    clu wrote:
    DoubleEdit: This issue is apparently solved in grub r3807
    10:34 < CIA-133> GNU GRUB: Vladimir 'phcoder' Serbinenko <[email protected]> * r3807 grub/ (4 files in 3 dirs): (log message trimmed)
    10:34 < CIA-133> GNU GRUB: * grub-core/disk/scsi.c (grub_scsi_read_capacity): Renamed to ...
    10:34 < CIA-133> GNU GRUB: (grub_scsi_read_capacity10): ... this.
    10:34 < CIA-133> GNU GRUB: (grub_scsi_read_capacity16): New function.
    10:34 < CIA-133> GNU GRUB: (grub_scsi_open): Use read_capacity16 if read_capacity10 returned
    10:34 < CIA-133> GNU GRUB: 0xffffffff.
    10:34 < CIA-133> GNU GRUB: Fix off-by-one error.
    No. Thats not the fix. That message is for devs in the irc channel to know that the bzr repo has been updated with a new commit (which may/may not be relevant to the issue discussed). I have compiled grub2-efi-x86_64 r3804 (needs few changes in the PKGBUILD) but that alone is not enough for updating the grub2 code in Archboot, especially if you don't know how Archboot's grub2 is setup or how grub2 uefi booting works internally.
    To update the iso:
    Download the files from http://db.tt/gZT4rifS .
    Extract Archboot iso to (EXTDIR) (replace EXTDIR with actual extracted dir path)
    Replace (EXTDIR)/efi/boot/bootx64.efi , (EXTDIR)/efi/grub2/grub2_uefi.bin , (EXTDIR)/efi/shell/shellx64.efi (optional) with the corresponding downloaded files.
    Install extra/libisoburn and core/syslinux packages and run (to generate new iso - copy paste with relevant paths modified)
    xorriso -as mkisofs \
    -iso-level 3 -rock -joliet \
    -max-iso9660-filenames -omit-period \
    -omit-version-number -allow-leading-dots \
    -relaxed-filenames -allow-lowercase -allow-multidot \
    -volid "ARCHBOOT" \
    -p "prepared by custom" \
    -eltorito-boot boot/syslinux/isolinux.bin \
    -eltorito-catalog boot/syslinux/boot.cat \
    -no-emul-boot -boot-load-size 4 -boot-info-table \
    -eltorito-alt-boot --efi-boot efi/grub2/grub2_uefi.bin -no-emul-boot \
    -isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin \
    -output ./archboot.iso (EXTDIR)
    Burn the iso to a cd and try again. AFAIK this issue does not occur with USB right?
    Last edited by the.ridikulus.rat (2012-01-30 18:41:59)

  • 2010.10-1 archboot "2k10-R7" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2010.10-1, "2k10-R7" 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:
    - added u(efi) booting support
    - bugfix release with latest kernels
    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:
    http://www.archlinux.de/?page=GetFileFr … ot/2010.10
    <yourmirror>/iso/archboot/2010.10/
    Changelog:
    GENERAL:
    - kernel 2.6.35.7 / LTS kernel 2.6.32.23
    - pacman 3.4.1 usage
    - RAM recommendations: 320 MB
    Kernel changes:
    - bump to latest .35 series and bump lts to latest .32 series
    Removed features:
    - None
    Environment changes:
    - added u(efi) booting support
      Big thank you to "Keshav P R " <skodabenz at rocketmail dot com>
    - updated pacman mirrorlist file
    - updated to vim 7.3
    - updated clamav
    - add more binaries from e2fsprogs
    - added chntpw
    hwdetect changes:
    - none
    setup changes:
    - more 4k sector drives fixes
    - removed fdisk calling, use parted all the way
    - fix dmraid list devices
    - some btfs code changes
    - fix btrfs submount permissions
    - added more extlinux checks
    - don't allow ntfs as root fs
    - add automatic bootflag fot ext/syslinux
    - fix extlinux on gpt devices
    quickinst changes:
    - none
    KNOWN ISSUES:
    - FTP installation mode:
      None
    - CD installation mode:
      None
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2010-10-03 05:45:21)

    tpowa: Here is a small checklist for grub2 efi implementation in the setup script:
    Note: I have used efi/uefi interchangebly below - referring to both efi 1.x and uefi 2.x in both macs and non-mac systems.
    Check whether the system uses uefi or bios.
    If bios, ask for which bootloader to install
    If uefi, grub2 is the only option.
    Check for the firmware arch. All non-mac uefi systems use x86_64 firmware without exception. Only Intel macs need firmware arch detection.
    I created a workaround for this in the grub.cfg script for the archboot iso. You can use dmesg in archboot booted using efi to find out the firmware arch
    dmesg | grep EFI_ARCH_x86_64 - if true then UEFI x86_64 firmware
    dmesg | grep EFI_ARCH_i386 - if true then UEFI i386 firmware
    or something like
    if [ -d /sys/firmware/efi/ ] || [ -d /proc/efi/ ]
    then
    if [ "$(uname -m)" == "x86_64" ]
    then
    <install grub2-efi-x86_64>
    elif [ "$(uname -m)" == "i686" ]
    then
    <install grub2-efi-i386>
    fi
    else
    <install any bios bootloader>
    fi
    If sure of uefi but unsure of the architecture, go for grub2-efi-x86_64 (even in macs).
    Request the user to convert the system to GPT if MBR is found. I recommend this even for bios installs as GPT is more robust with many features useful even for <2TB disks.
    Since GPT is a part of UEFI spec, I suggest making this compulsory for efi booting and optional for bios booting.. I have not come across uefi systems using MBR disks for booting although the uefi spec makes no such restriction.
    Because of this reason, I propose that archboot should ask the user whether he/she wants to convert the drive to GPT.
    If someone is dualbooting Windows and Linux and wants to use UEFI, then GPT is the only option (Windows restiction) - see http://www.insanelymac.com/forum/lofive … hp/t186440 for instructions on how to convert Windows boot to UEFI-GPT.
    This MBR to GPT can be done using sgdisk (scripting equivalent of gdisk) with out data loss. But systems using LVM and other such stuff (which I do not understand) need to be careful.
    Check whether an efi system partition is present in the system otherwise create one. The order of the partition in the partition table is immaterial. Even in case of Windows dual boot - position of EFISYS part in the table is immaterial.
    EFI SYSTEM PARTITON Requirements:
    Size           - Min 100 MB, Ideal 200 MB
    Filesystem     - FAT32 (FAT16 may also work - not NTFS or HFS or HFS+ or ext2/3/4 or any other file system)
    Partition type - GNU Parted's "boot" flag in GPT disks or EF00 type code in GPT fdisk (aka gdisk) or 0xEF partition type in MBR disks
    Need not be the first partition in the drive/disk
    Should not be in a extended-logical partition in a MBR disk (I have not personally confirmed this - all my disks are GPT) - not to be bother if MBR to GPT conversion is applicable
    Should not be in lvm or any such fancy stuff - partition should be accessible by the (U)EFI firmware
    In UEFI booting, Bios Boot partition (bios_grub in Parted) is not involved - that is used only for BIOS-GPT booting using GRUB2.
    Grub2 or any bios based bootloader previously installed may need to be reinstalled. It is possible to boot linux using grub2-efi and grub2-bios in the same system. Just make sure Bios Boot partition is also installed.
    For a sample partition layout of my system booting both through bios and uefix86_64
    GPT fdisk (gdisk) version 0.6.11
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 625142448 sectors, 298.1 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 625142414
    Partitions will be aligned on 1-sector boundaries
    Total free space is 18 sectors (9.0 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 40 401623 196.1 MiB EF00 EFI_SYSTEM_PART
    2 401624 483543 40.0 MiB EF02 BIOS_BOOT_GRUB2
    3 483544 2488472 979.0 MiB FFFF
    4 17260760 17832149 279.0 MiB FFFF
    5 17832150 112197959 45.0 GiB 0700 MS_WINDOWS_7_x64_RTM
    6 112197960 206563769 45.0 GiB 0700 DATA_3
    7 206563770 258179514 24.6 GiB FFFF LINUX_x64
    8 258179515 258998714 400.0 MiB FFFF Linux_Boot_GRUB2_BIOS
    9 258998720 290455199 15.0 GiB FFFF
    10 290455200 457370549 79.6 GiB 0700 DATA_1
    11 457370550 625137344 80.0 GiB 0700 DATA_2
    12 625137352 625142414 2.5 MiB FFFF
    13 2488473 17260759 7.0 GiB 8200 Linux swap
    Once the EFISYS partition is created, mount it at /boot/efi (standard efisys mountpoint used by Fedora/Redhat since Fedora 12) or at /efi or any other mountpoint.
    Install the grub2-efi into the efisys partition at /boot/efi/EFI/grub2 or to any other dir of your choice.
    Run the grub2_efi_x86_64-install or grub2_efi_i386-install script from grub2-common package with instructions from the post_install scripts of the grub2-efi package(s).
    Create the grub.cfg file similar to the one created for grub2-bios but with "nomodeset add_efi_memmap" kernel options added to each linux menu entry.
    Still something missing will be added to this same post as edits.
    tpowa: I tried to read through the archboot setup script but I didn't understand the many functions that you have used. I think there should be a common grub2 function for GPT conversion and generating grub.cfg, and 1 separate function each for grub2-bios and grub2-efi.
    I also invite other uefi users to add any thing you guys want that is missing in this list. Grub2 upstream devs officially support only UEFI 2.x x86_64 firmware so that rules out many mac users (efi 1.1) and i386 uefi firmware (if theres any one at all).
    Last edited by skodabenz (2010-10-08 14:26:56)

  • 2010.07-1 archboot "2k10-R5" ISO hybrid image released

    Hi Arch community,
    Arch Linux (archboot creation tool) 2010.07-1, "2k10-R5" 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:
    - Many new setup features, like btrfs, label and extlinux support.
    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:
    http://www.archlinux.de/?page=GetFileFr … ot/2010.07
    <yourmirror>/iso/archboot/2010.07/
    Changelog:
    GENERAL:
    - kernel 2.6.34.1 / LTS kernel 2.6.32.16
    - pacman 3.4.0 usage
    - RAM recommendations: 320 MB
    Kernel changes:
    - bump to latest .34 series and bump lts to .32 series
    Removed features:
    - None
    Environment changes:
    - Change to isolinux menu on boot
    - Added more isolinux features on boot menu
    - intel wireless now provided out of the box
    hwdetect changes:
    - added btrfs support
    setup changes:
    - added btrfs support
    - added extlinux bootloader support
    - added label namescheme support
    - add automatic hostname to hosts file
    - better automatic activation of complex devices like lvm,raid, dmraid.
    - better support for cciss, ida, rd and mmcblk devices
    - fixed grub2 install issues on lvm devices
    - a lot of internal function cleanup
    quickinst changes:
    - fixed media installation
    KNOWN ISSUES:
    - FTP installation mode:
      None
    - CD installation mode:
      None
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa
    Last edited by tpowa (2010-07-31 06:45:46)

    tpowa wrote:Architecture = auto ok i'll add this, normally pacman should fallback to uname -r then and continue.
    You are not able to boot the image or you are not able to boot the system?
    Sorry about the lack of detail and clarity in my last post, I wrote it in a hurry as I was running out the door.  The image booted fine into the x86_64 menu option from a flash drive which was loaded using UNetbootin on Windows.  The system will not boot to the newly installed OS.  It fails very early, usually around CPU initialization, with a hard reset.  I'm going to try Grub 0.97 instead of Grub2 and see if that helps.
    As for my previously mentioned mountpoint problem, during setup->Prepare Hard Drive->Set Filesystem Mountpoints, I get these messages on stderr:
    basename: extra operand '/dev/sdc'
    Try 'basename --help' for more information.
    sed: -e expression #1, char 0: no previous regular expression
    sed: -e expression #1, char 0: no previous regular expression
    sed: -e expression #1, char 0: no previous regular expression
    ...(about 10 of those messages)...
    Before getting a menu listing /dev/loop0 as the only available partition.  After selecting that, I get more of the same messages on stderr and a menu listing /dev/loop[0-7] and /dev/sr0 for partitions.
    I'm guessing that this is because of the quotes around $(finddisks) in findpartitions() on line 524.  Removing them seems to fix things in any case.
    I'll post updates here after I try installing without Grub2.
    *UPDATE*
    I've successfully booted after ditching Grub2 for plain old Grub.  I'm using btrfs for root and home with no problems so far.
    Last edited by JoelHough (2010-07-22 22:57:15)

Maybe you are looking for

  • How to block creating Billing document if no accounting doc generated

    Hi, In Brazil, after create Billing Document a new document called Nota Fiscal is also created. But I can't allow creating Billing Document and Nota Fiscal if i have a problem during the releasing process of the Accounting Document. How Could I to do

  • Will my IPod Touch 5G work with my iTunes?

    Just ordered a new ipod touch 5g from ebay and i was wonderind if it will work with the old imac that i have. Iam using a 17-inch 2006 iMac with 1.83GHz Core Duo CPU, 1GB RAM (that i upgraded myself), OSX 10.6, and iTunes 10.1

  • Problem with build.xml (not compiling)

    Hi I am not sure if this is an ANT specific question or a general XML question. DO forgive me for being naive I wrote this ant build.xml file for my web applications and I find that it simply refuses to compile any classes. I am sure I am doing somet

  • IPhone: NavigationController Back Button

    The back button on a navigationController is supposed to be automatic, right? I have a table view hierarchy with a navigation controller that has two table views. I can click on a cell in the root view and it does the transition to the next view. How

  • Uploading data in to info cube.

    Hi I am new to APO. I was able to create infocube and all that stuff. but was not able to upload data in to info cube, Can some one explain me the process of uploading data in to info cube. Regards Deepu