May 2010 - Arch-releng - lists.archlinux.org

[arch-releng] [Patch] Official_Arch_Linux_Install_Guide
by Volker 28 May '10

28 May '10

Hello! I think stumbled across a typo, a missing word and a wrong path in the official Install guide. Can someone check if that's correct? Subject: [PATCH] Typos and little correction Fix a typo, a missing word, and correct the path to the installation guide on release media in the info, which is actually /usr/share/aif/docs not /arch. (See the message you get when you run the 2010.05 live media and log in.) --- doc/official_installation_guide_en | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/official_installation_guide_en b/doc/official_installation_guide_en index 01688f6..946a42d 100644 --- a/doc/official_installation_guide_en +++ b/doc/official_installation_guide_en @@ -7,7 +7,7 @@ Patches/comments are welcome on the arch [releng mailing list](http://www.archlinux.org/mailman/listinfo/arch-releng) or mail to dieter(a)archlinux.org -This guide is available in the /arch directory of release media and on +This guide is available in the /usr/share/aif/docs directory of release media and on [The arch wiki](http://wiki.archlinux.org/index.php/Official_Arch_Linux_Install_Guide) **Related articles** @@ -619,7 +619,7 @@ ever want to use. The majority of your everyday modules will be loaded later on by udev, during the init process. By default, mkinitcpio.conf is configured to autodetect all needed modules for -IDE, SCSI, or SATA systems through so-called HOOKS. The installed should +IDE, SCSI, or SATA systems through so-called HOOKS. The installer should also have inserted hooks like crypt, lvm, keymap and usbinput if relevant. This means the default initrd should work for almost everybody. You can edit mkinitcpio.conf and remove the subsystem HOOKS @@ -834,7 +834,7 @@ You'll notice that in the early userspace (the part that comes after the bootloader) the hooks (as defined in mkinitcpio.conf) needed to get your root filesystem are run. If you have lvm, it will run the lvm hook. If you use encryption, it will -the keymap and encrypt hooks so you can enter your password to decrypt the +run the keymap and encrypt hooks so you can enter your password to decrypt the volume. Once the system is booted, login as root. By default the password is empty -- 1.7.1 Also the wiki page would look much better without the <code> tags that markdown put there. ;) Altogether the new interactive installer is great, especially the support for encryption and LVM, thanks! Greetings, Volker

3 3

[arch-releng] A question about the ArchIso system
by Keith Hinton 20 May '10

20 May '10

Hi all. I was curious how the Archiso system got started? You release-team folks must enjoy making new releases. Do you folks start the process as soon as a "official release" is made from the Arch repository? I know the general process, thanks to Dieter. What I am so curious about is if anything can be done (while not a developer) I am able, to test various things-and although most of it occurs in a VM, I am able to report specific feedback. Is it testers that the Arch-release team lacks to make the process a bit easier? What I'd like to do is see how I might be ble to help you folks out. No, I don't have any hardware to give you folks-I'm not giving you my Windows laptop to Arch with. :) I could give it to you, but nah. :D Even though the machine is an Intel 2 core duel processor at 2.80GHZ, 4GB of RAM, 64-bit ready, 64KB primary cache, USB2, with an Intel WiFi link 5100 AGN wireless card, and such. It is, a wonderful box. But like I mentioned, sorry-I'm using it presently, and I'm not ready yet to give it up. But if it's testers that you lack, then I might be able to help. I'm also good at looking for typos in documentation and reporting them-and could do those as bugs. :) Even typos are bugs if you ask me. :) While not software bugs, of course. Another good question is what system does the Arch Linux team have in place to insure that Arch will boot on any machine? Hardware is so widely differing between so many PCs, and so on. How do you know if Arch will run on a given machine in general? That's an interesting one. Hope ou folks have a great day, and thanks for the release! Please keep up the great work on your ArchIso system Dieter, as it appears that you lead that effort. Thanks to you, your efforts in ArchIso, including Thomases efforts to fix things with it, have enabled us TalkingArch Users to role our own snapshots thanks to ArchIso-git, so please keep up the work on that! Dieter: I suggest that you deserve a break. Get back to the project you have been neglecting for a while. Stop letting projects falling behind-stop getting worse with life, :). Let Thomas take over Aaron's tasks for a while, I'm sure Aaron himself needs a break too, what with publishing so many ArchLinux news entries, and speaking of that, Hey! Aaron, where is the next edition of the Arch Linux magazine anyways? Thought that you released those things each month? :D Don't forget to announce the next official snapshot release of Arch. Though if users wished to build there own Iso images of Arch Dieter, couldn't they do so without needing to wait for you folks, and just pull in AIF, and other various packages? If Archiso does indeed take a snapshot of the repo as it is, perhaps it pulls in AIF, no matter what version that's at. If you ask me, you Arch-release folks and kernel devs should take a break for the next 1 thousand years! LOL I am kidding-I know that can't happen. :) And Dieter, please don't quit the Arch project. I was teasing you about your personal issues with regards to niglecting projects, though I was serious though, take a break. :) Archiso should not be too hard for others to assist you on-Thomas himself has proven it, and hasn't Chris Brannon done some work on that as well? Hey Chris, if you read this, why not take over Archiso for the next 500 years! LOL just kidding buddy! Have fun, and happy Arch-development to all. Regards, --Keith P.s. Please send my comments to the kernel developers about taking that crazy break I suggested-I'd love to see there reactions to this funny message. Hope you folks get a huge laugh (more than one hopefully.)

2 1

[arch-releng] 2010.05 announcement draft
by Dieter Plaetinck 16 May '10

16 May '10

please provide feedback. I have the feeling I'm forgetting something. Btw the plan is to do the release monday may 17th around 20:00 UTC, so there's not much time! 2010.05 snapshots. Less is more... Hi all, New installation media are vailable. Their size and quantity has shrunken quite a bit but the usefulness has only gone up. Here's a list of notable changes, which will explain everything: Archiso: * all iso files can be burned onto CD's as well as written to media like usb sticks (isohybrid) * more then half of the packages in core are now xz compressed * next to the single-arch files we provide dual-Arch images which can be used as 32 or 64bit medium * use isolinux bootloader exclusively (for booting the live media) * snapshot of current core, including kernel 2.6.33.4-1, pacman-3.3.3-5 and glibc-2.11.1-3 * updated memtest * support for PXE booting * provide wpa_supplicant * support libvirt AIF: * ability to choose if you want uuid/labels/devicefiles for blockdevices; automatically applied in menu.lst, fstab, etc * split off UI library into separate <a href="http://github.com/Dieterbe/libui-sh">libui-sh</a> project * support virtio blockdevices * allow user to specify additional custom arguments for mkfs and the like Other then this, quite some bugs have been fixed again, mostly in AIF. And of course, the <a href="http://wiki.archlinux.org/index.php/Official_Arch_Linux_Install_Guide">Official installation guide</a> has been updated to reflect these changes. Thanks to everyone who contributed, this release took a long time but I think it's worth it. <a href="http://www.archlinux.org/download/">Download</a>

1 0

[arch-releng] final testing images
by Dieter Plaetinck 16 May '10

16 May '10

new images are done. version: 2010.05.13 these are the images I want to rename to an official 2010.05 release after testing. http://build.archlinux.org/isos/Changelog http://build.archlinux.org/isos/ how should they be tested? for every file, that is: archlinux-2010.05.13-core-dual.iso archlinux-2010.05.13-core-i686.iso archlinux-2010.05.13-core-x86_64.iso archlinux-2010.05.13-netinstall-dual.iso archlinux-2010.05.13-netinstall-i686.iso archlinux-2010.05.13-netinstall-x86_64.iso I want to get a report from someone that an installation went fine. what kind of install doesn't really matter. manual, automatic, autoprepare, net/core whatever. this has been tested enough before, so any kind of install with each single image. On top of that, I want: A) confirmation for virtio_pci and virtio_blk on the install ISO's initramfs http://bugs.archlinux.org/task/19401?project=6 B) at least one installation performed from a usb stick, using any of the above images. So if you test: send a reply mentioning which file you tested, and optionally if you can confirm A/B thanks for you help, Dieter

7 11

Re: [arch-releng] [arch-general] final final testing images
by Dieter Plaetinck 16 May '10

16 May '10

On Sun, 16 May 2010 20:12:32 +0200 Karol Babioch <karol(a)babioch.de> wrote: > On Sunday 16 May 2010 17:17:28 Dieter Plaetinck wrote: > > So right now, these two things are needed: > > * confirmation that archlinux-2010.05.16-core-x86_64.iso boots fine. > > * confirmation that wireless cards are properly initialised now. > > I've just tried it out using the dual netinstall iso. My Wi-Fi Intel > 5300 AGN gets recognized and I could connect to my WPA encrypted > network. > > I can't tell anything about the installer, as I didn't used it, just > tried out whether my wireless card works. > > Great to see it working, last time I had to mess around with the > ethernet ... Thanks again to all who tested again. so quickly :) no more testing is needed. I will prepare these images for release. Dieter

1 0

[arch-releng] final final testing images
by Dieter Plaetinck 16 May '10

16 May '10

Okay guys, props to Thomas for finding out the problem with the initialization of wireless cards. I built new images, dated 2010.05.16 (aka "final final images" ;)) in which this should be fixed, and which also come with updated core packages, most notably kernel26-2.6.33.4-1 http://build.archlinux.org/isos/ thanks to everyone who tested the 2010.05.13 (or earlier) images. i received confirmation for 4 images with which a boot+installation went fine. for netinstall-dual.iso I only reiceved confirmation that it boots fine (but that's enough, given the other tested images). However i got no feedback for the core-x86_64 image. So right now, these two things are needed: * confirmation that archlinux-2010.05.16-core-x86_64.iso boots fine. * confirmation that wireless cards are properly initialised now. cheers, and stay tuned for a release soonish :) Dieter

1 0

[arch-releng] Formal Apology To All Involved With Last Nights Tempor Outburst
by Keith Hinton 14 May '10

14 May '10

Chris, Sorry for losing my tempor that way. As for accomplishing anything, I failed to do anything and actually waisted a lot of time by blowing up that way on the Arch list-not to mention that you had nothing to do with it. I took all my anger out in dealing with wireless on the CD itself on everyone, and now that I think about it, it was even more stupid to do. Rather childish, actually. I'm a better person than this usually. It won't happen again. Sorry for including you in the blow up, when you have done a good job at providing this project. After all, chances are that if you hadn't undertook something like this, that Arch still would not have the Speakup screen reader, not to mention an accessible installer. I sincerely apologize, and hope that you personally at least, will forgive me for doing what I did to you. I shouldn't have done that to you, Chris, and I never will do that again. I'd also like to send a formal apology to the entire Arch-Linux release-team as well. I realize that everyone of you, especially Dieter, volunteer time to work on Arch, and I shouldn't be slamming any of you with questions such as "Why doesn't this snapshot come out and such" I am greatful to Thomas looking into this though, to see why the CD does do what it does, I do not think the Ndiswrapper module was included in the list I sent to the list, was it? Like I said again, I won't blow up that way again. Thanks all. God Bles. Sincerely, --Keith Hinton

2 1

[arch-releng] LVM Installation Issues
by Lukas Grässlin 13 May '10

13 May '10

Hi there, I tested archlinux-2010.04.19-core-x86_64.iso and have some issues with installing with a lvm: * It would be very very nice if I could say when creating a logical volume: "Take all the free space in the volumegroup" (aka -l100%FREE) * If I type a value greater than the free space in the vg the installer says it encountered errors. Would be better if it is checked, if the value exceeds the free space. At the current state I wouldn't use the Installers capability to create a LVM because it's a bit glitchy. The same is true of the capability of creating dm-crypt volumes. Till now I was not able to set up a working scenario with LVM atop of dm-crypt. The Installers also fails with some errors. (I don't have more information about this yet because it's a bit longer ago. I will retest it) Regards, Lukas

4 15

[arch-releng] Firmware thread update
by Keith Hinton 13 May '10

13 May '10

Hi, although this is not specific to my Intel WiFi Link 5100 AGN wireless card, the following URL shows similar issues, and the primary poster, was having to do exactly what I'm doing with kernel 2.6.33 with regards to: rmmod iwlagn modprobe iwlagn Or: modprobe -r iwlagn modprobe iwlagn Or: insmod iwlagn Either way, I keep aving to do this-even though the module loads at boot from Arches LiveCD. I refuse to install Arch, because I am sure that this will occur on the hard-drive as well. I don't know if Chris enabled the firmware hook in his initrd. Chris, could you please look and upload new releases of the builds (or an X86-64 build for me in some temp directory on your webpage directory if you did not enable the firmware hook? And if there is a newer kernel than what was in your april 2010 snapshots, then could you please update that as well? Having to modprobe all the time is annoying. I gave the URL before URL of my dmesg output with your LiveCD chris (and yes) the firmware Ucode file for my wireless card is there, and the module loads, but the firmware doesn't, is there any chance you forgot to enable that hook? The paste URL for this dmesg output Chris for you to viw for yourself (and you'll see) where rmmodding and modprobing will work-though wlan0 should already be there but I do not think you have enabled firmware in the kernel image stuff-so I suggest reviewing your latest snapshot on your website and seeing if this is the case-or am I the only one with this issue? URL for dmesg output: http://npaste.de/Sx The bug URL is: http://bbs.archlinux.org/viewtopic.php?id=59236 As mentioned above you'll see where the firmware doesn't load. Note: as mentioned in a prior post about the GRML-based distro with kernel 2.6.33, the firmware ucode file for the iwlagn module Chris does automatically load. Perhaps they enabled the firmware hook, and you just may have forgotten? I am sure that even you could have made this mistake. If this is not a difficult thing to resolve, then please, could someone please help? I'll never install Arch again if this is something that will always break my machine when wireless is the only option I have and I need the firmware to just autoload on the liveCD. I do not like this modprobing business whatsoever, and all I need to say at the moment is "screw the Arch Way" of doing things at the moment. Arch is great-but if this is something that is always going to happen, then I don't know what Arch is turning into. I've seen all the interesting kernel related problems lately with busibox and other such things-and at the moment my furstration with simply getting the firmware to load on Chris's TalkingArch CD is driving me up the blasted wall.Arch is great-but as far as this having to even touch modprobe...well this is just not going to be acceptable. Sorry for taking my frustrations out on the entire Arch Linux development/release team, but I seriously don't care at the moment about my politeness at the moment. All I care about is the fact that this is happening, and seems totally unsolvable. Even my best Linux blind friend who has figured out ways around my problems in the passed can't solve this issue- so I'm just hoping that some one in Arch might be able to help. I'm also frustrated because noone on #Arch-Linux seems to be able to help, and the wiki is failing me entirely. Thanks for letting me rant, and once again sorry for taking my frustrations out on Chris who has done so well with TalkingArch and everyone else, but I'm lible for a while to blaim anything and everything on this firmware crap until I know for damnd sure wwhy it does this, and how to smash this issue once and for all. I don't have time to learn C, and also don't know who maintains the Ucode files for ArchLinux, but I hope that someone will look at this list and see if anything can be done in any respect, kernel iwlagn related or firmware, or whatever. If anyone figures out how to resolve this entirely, then great. I just hope that you didn't forget to use the firmware hook Chris-otherwise all my frustrations will have been useless. But I refuse to accept that Arch-specifically is the only distrobution with this problem. I just won't try installing until I know this has been tested and pounded on by everyone in the world with Arch if necessary. Regards, --Keith P.s. That's why I mentioned GRML because if you go to: http://www.grml.org/ and download that CD and boot it up and uname -a on either of the 64-bit or 32-bit versions, the kernel version matches, and dmesg automaticallly has wlan0 with the same firmware loaded-that's why I've brought up that Debian-based distro in that aspect of things. Thank you all so much for whatever help you can provide-but I cannot figure this out.

2 1

[arch-releng] Lsmod output
by Keith Hinton 13 May '10

13 May '10

Hi all, I've decided to attach a text document. If this text document is not attached successfully onto the lists, then I'll paste the results below. I wanted to just get the output as fast as possible, and you folks have my dmesg output on that paste URL. Thanks. --Module list output-- Module Size Used by nls_cp437 5865 1 vfat 9924 1 fat 48460 1 vfat snd_hda_codec_intelhdmi 15636 1 snd_hda_codec_realtek 258661 1 snd_seq_dummy 1439 0 snd_seq_oss 28984 0 i915 291818 1 snd_seq_midi_event 5348 1 snd_seq_oss snd_seq 50397 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_hda_intel 22642 0 drm_kms_helper 23753 1 i915 uvcvideo 60298 0 snd_seq_device 5181 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_hda_codec 68413 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel videodev 38395 1 uvcvideo drm 160140 2 i915,drm_kms_helper snd_hwdep 6244 1 snd_hda_codec snd_pcm_oss 39107 0 v4l1_compat 15610 2 uvcvideo,videodev rtc_cmos 8990 0 i2c_algo_bit 4999 1 i915 snd_pcm 70222 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_mixer_oss 17107 1 snd_pcm_oss v4l2_compat_ioctl32 10417 1 videodev joydev 9800 0 video 18746 1 i915 ac 3091 0 battery 9612 0 rtc_core 14439 1 rtc_cmos wmi 5957 0 snd_timer 19213 2 snd_seq,snd_pcm rtc_lib 1842 1 rtc_core thermal 12079 0 processor 29639 2 button 4746 1 i915 i2c_i801 8550 0 snd 57203 12 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_seq_oss,snd_seq,snd_hda_intel,snd_seq_device,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_timer iTCO_wdt 9157 0 soundcore 6223 1 snd iTCO_vendor_support 1873 1 iTCO_wdt i2c_core 17842 6 i915,drm_kms_helper,videodev,drm,i2c_algo_bit,i2c_i801 output 1916 1 video psmouse 53142 0 intel_agp 28089 1 snd_page_alloc 7097 2 snd_hda_intel,snd_pcm evdev 8852 0 serio_raw 4536 0 speakup_soft 5046 1 pcspkr 1827 0 speakup 84435 1 speakup_soft squashfs 21076 2 loop 15195 4 aufs 166454 1 exportfs 3538 1 aufs udf 83927 1 crc_itu_t 1273 1 udf sg 25333 0 sr_mod 14883 1 cdrom 35860 1 sr_mod sd_mod 26984 2 usb_storage 42489 1 ata_generic 3047 0 uhci_hcd 21684 0 iwlagn 244718 0 ata_piix 20957 1 pata_acpi 3224 0 iwlcore 156728 1 iwlagn mac80211 171772 2 iwlagn,iwlcore r8169 34925 0 cfg80211 126658 3 iwlagn,iwlcore,mac80211 rfkill 15396 1 cfg80211 mii 3834 1 r8169 libata 154643 3 ata_generic,ata_piix,pata_acpi ehci_hcd 34938 0 scsi_mod 94729 5 sg,sr_mod,sd_mod,usb_storage,libata usbcore 144604 5 uvcvideo,usb_storage,uhci_hcd,ehci_hcd --Moudle-output-end-- Attachment of the same file in text format will be sent. It is a .txt file, so have fun reading. Regards, --Keith See if this helps with the firmware issues.

1 0