Archiso-live 20091024 Release
Changes since last release:
* Using testing repo. This is cause i have a menu option in the english menu to test open source 3d mesa drivers. I have tested and it works almost everything with crashing X. Some of FPS may crash X if you try using open source 3d drivers. (ex. nexiuz)
* Using the new squashfs 4.0 with lzma now. It came out this way so its very new. I’m also able to make modules alot faster now with this too.
* Removed open source 3d drivers for nvidia so there is no conflict with the drm r6xx-r7xx drivers.
root password is ArchLinux
arch password is arch
Everything is up2date as of 2:00 PM EST on 20091024.
Here is the iso, md5, and package list.
Package changes here.
First of all nice work.
Second I have question can your livecd work in persistent mode or can archiso script use it?
@Jack
There is a persistent mode but its best to not use it on a fat32 device. You will have to format your usb stick to ext2 or make a xfs file.
This could help you. Link.
The official archiso scripts don’t have a persistent mode.
Can you help me choose? I have to make livecd with tpm emulator and save changes to some host or pendrive and what is the easest way to do that? ‘Archiso’, ‘Larch’, ‘Linux Live! Scripts’ ? Can you recomend something ?
@Jack
The best way would be to format your usb to ext2 then install my iso using unetbootin. From there you can added changes=foldername or something in your boot options. This would be the simple way of doing.
There other way would be make modules of the programs and putting them in archiso-live/modules folder. It wouldn’t help you with keeping the settings but you would at least have the programs there no matter what.
How to make modules:
‘pacman -Sy’
‘arch2lzm pkg package’ or ‘arch2lzm local package’ since ttm has to be compiled best to use the last command to make the module. After this you can added it to /your/usbstick/path/archiso-live/modules folder.
The first option is better for you. Just remember that writing the usb stick to much could cause it die young.
Thank you, is there way to make your scritp work with grub not with isolinux ?
@Jack
I don’t have menu.lst for grub to be used with my build script. Grub support is in the script but it only works if you added -b grub to mkarchiso script. I will see about adding a menu.lst file and added the boot menu type into the config file to make it easier since right now you will have to edit the build script.
Thanks! Good Job!
Installed great. I can’t seem to get shaman or pacman to work at all. What am I doing wrong?
This is what I get when I right click the shaman icon and choose update repo’s
“It looks like the system policy prevents you from doing this action, or you failed or refused to authenticate. Please contact your system administrator for further details”
@siacs
This maybe because its shaman is not running as root. I may added another .desktop file to overlay so shaman can work in user. But i heard of problems with shaman so I’m not sure if it thats a go idea.
You can run shaman in shell with ‘sudo shaman’ without quotes. This should make it work.
sudo shaman says it can’t run as root. Evem if I do a pacman -S nano in a terminal it won’t do anything. Shaman will start up but just won’t do anything as user (will not run as root) IF I go to settings and change something the ok button will not select. Update data base is not clickable etc. You mentioned something about a .desktop file.
@siacs
There has been lot of problems with shaman. So its best to not use it.
You need to update the database before you can install anything. Try ‘sudo pacman -Sy nano’ without quotes.
this is out of xsession-errors
User agent is: “shaman/1.2.1 (Linux i686) aqpm/1.3.3.2″
Shaman registered on the System Bus as “:1.62″
Service org.archlinux.shaman successfully exported on the System Bus.
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
polkit-read-auth-helper: cannot lookup group info for gid 102
–> UNSETENV HTTP_PROXY
–> UNSETENV FTP_PROXY
Populating Repo column
Getting local packages
Log file is: /var/log/pacman.log
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
refinePkgView
The left TextBox is over, let’s do the ComboBox
Show all packages
thunar-vfs-font-thumbnailer-1: Could not open the input file: broken file
Agh! Something has gone badly wrong here with the poor old ThinkPad R51. Won’t boot with any option, including safe grfx. Weird. It runs through all the preliminaries but when it tries to put up the window manager it just goes somewhere . . . not sure where. Not putting up signs of kernel panic, but refuses to respond to keyboard. The chipset is the rather sad Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02). Ho hum. I thought this was over. Not sure who is to blame here, I expect Intel will do as prime suspect.
@gnomic
The best way to test if its intel or xorg-server 1.7 fault is to use the 20091010 verison. There is a new intel driver in archlinux repo that will be release in the next iso.
The safe graphics option only goes to xorg-server auto detection without the xorg.conf file. So its still using the intel driver instead of using vesa driver.
Erm, love your work and so, but why would you do that wrt the ‘safe’ option, especially given the current problems with Intel? Or why not provide a vesa option, which I assumed the safe boot would be, as it most commonly is. I missed 20091010 and am extremely limited in what I can d/l. Wish this issue (ie broken Intel grfx) would just go away, am missing why it keeps on being broken. How hard can it be? (albeit speaking as one who couldn’t write a driver to save my life).
@gnomic
The next release will make noxconf a vesa option. I made a simple xorg.conf.vesa file that will be rename to xorg.conf when noxconf is used at boot now.
I’m not releasing a iso today since its bug fix day. I will have to wait until tomorrow to do the iso.
Video: Intel 82855GM. Can’t boot without enabled KMS. Vesa – black screen + system hang up; default option — just system hang up…
Can u add an option, that will enable KMS? (options i915 modeset=1)?