- Arch-general - lists.archlinux.org

[arch-general] virtualbox-archlinux-modules depends on kernel26
by Aljosha Papsch 24 Jul '11

24 Jul '11

Hi, virtualbox-archlinux-modules still depends on kernel26. I wanted to copy the package directory from the abs tree, but it's not there. How is this possible? (Of course I synced it before) Aljosha

3 4

[arch-general] git bisect module against -ARCH kernel
by Matthew Monaco 24 Jul '11

24 Jul '11

I'm trying to bisect an issue with the microphone not working on my usb webcam. See the forum posting [1]. I cloned the Linus' git tree and checked out v2.6.39. I zcat /proc/config.gz > .config and did a make modules. I did this to get the symbol table and all that set up correctly. After that, I did git bisect start v2.6.39 v2.6.38 -- sound/usb (Everything worked fine in 2.6.38). Then for each iteration I intended to do make ${MAKEFLAGS} M=sound/usb. This rebuilds snd-usb-audio.ko just fine, but when I copy it to updates, gzip it, and run depmod, I cannot load it because modprobe says it's an invalid format. My only guess is that this has something to do with a version string somewhere, but I kept assuring it was 2.6.39 in Makefile (no extraversion). Any other ideas? [1] https://bbs.archlinux.org/viewtopic.php?id=121607

2 1

[arch-general] dmraid - Array failed - installed new pair of drives - any shortcuts for reinstall on new array?
by David C. Rankin 23 Jul '11

23 Jul '11

Guys, I thought I would drop a line and see if anyone had done this recently. On a server I had a 2 disk array of 750G drives. One failed and I ran with a degraded array until the new pair of drives arrived. I installed the new drives and moved the good disk from the failed array to /dev/sdc. I rebooted, marked /dev/sdc (the sata disk in the BIOS) as bootable and deleted the old array and created a new one in the BIOS (for the new drives) and the box booted right up on the old drive. Where I'm needing help is reconfiguring dmraid. Currently, the box is still booting using the old dmraid designation for the degraded array even though I deleted the array in the BIOS. (which is pretty amazing). Here is how the system is currently running: 19:29 nirvana:~> df -h Filesystem Size Used Avail Use% Mounted on udev 10M 0 10M 0% /dev run 10M 152K 9.9M 2% /run /dev/mapper/nvidia_ddddhhfhp5 23G 13G 9.4G 57% / shm 1.9G 0 1.9G 0% /dev/shm /dev/mapper/nvidia_ddddhhfhp10 608G 380G 198G 66% /home /dev/mapper/nvidia_ddddhhfhp7 122M 34M 82M 30% /boot /dev/mapper/nvidia_ddddhhfhp8 23G 6.0G 16G 28% /var /dev/mapper/nvidia_ddddhhfhp9 33G 8.1G 23G 27% /srv What I need to do is install Arch on the new array and then get rid of the dmraid config on the old drive so it just runs as /dev/sdc. After I have the base Arch install on the new array, I can simply move the information from /dev/sdc to the new array. Is there any shortcut to install Arch since I have the old install currently running? Or is it just easier to stick the install CD in and go through the base install on the new disks and then copy the old /var/cache/pacman/pkg to the new arrays to complete the package install with local packages? I'm fairly sure the dmraid designation with the old drive will take care of itself when I do the install on the new array, but I'm not certain. Any pointers or hints? Thanks -- David C. Rankin, J.D.,P.E.

1 1

Re: [arch-general] Creating an Arch chroot on a non-Arch
by Aurélien Chabot 23 Jul '11

23 Jul '11

There is some premade stuff on archlinux.fr : http://wiki.archlinux.fr/Install_chroot ( google translate will do the job if you don't understand french ) Here is the script use to create the chroot : http://calimeroteknik.free.fr/arch-guide/install-chroot.sh Aurélien Chabot

1 0

Re: [arch-general] [arch-dev-public] kernel 3.0 changes
by Heiko Baums 23 Jul '11

23 Jul '11

Am Sat, 23 Jul 2011 17:18:46 +0200 schrieb Tobias Powalowski <tobias.powalowski(a)googlemail.com>: > But I don't know exactly how pacman will handle the replace. pacman does nothing. I tried it with my linux-fbcondecor package which I took from your SVN linux package. pacman just let my kernel26-fbcondecor package installed and installs linux-fbcondecor parallel. I think if you want pacman to uninstall kernel26 you need to add a conflicts=('kernel26') to the linux PKGBUILD. But I'm not sure if this is necessary. And for that reason I would suggest not to creating the symlinks to the old image names. Better let the people edit their bootloader config. If they won't do this they'll just boot their old kernel26 if they didn't uninstall it before. So nobody will get an unbootable system. Heiko

1 0

Re: [arch-general] Panic - no sound devices after upgrade
by Fons Adriaensen 23 Jul '11

23 Jul '11

On Sat, Jul 23, 2011 at 01:14:30AM +0200, Adrian Knoth wrote: > > > If you want to try out Adrian's patch, I uploaded a kernel with the > > > patch applied here: > > > <https://dev.archlinux.org/~tomegun/kernel26-2.6.39.1.3-1.1-i686.pkg.tar.xz>. > > > > Installed on two machines so far, more tomorrow. > > Seems to have solved the problem :-) :-) > > Good to know. I'll wait for your final confirmation and then commit it. One problem: the gain settings have changed, now having a range of 0..64. How do these values map to the internal ones (0..0xffff) ? I *hope* there is value corresponding to EXACTLY 0x8000 (gain = 1) !!! The reason is that MADI is bit-exact and is used to tranport other values than just audio samples. This works of course only with exact unity gain. BTW, why was this change made ? For pro users (are there other of this card) this is a regression. Ciao, -- FA

1 0

Re: [arch-general] [signoff] dash 0.5.7-1
by Grigorios Bouzakis 23 Jul '11

23 Jul '11

Pierre Schmitz wrote: > On Thu, 21 Jul 2011 10:29:15 -0500, Dan McGee wrote: >> Upstream new release. >> >> -Dan > > Imho the base group could be removed as it is not needed by anything. > Its been requested : https://bugs.archlinux.org/task/22483 PS. For the filesystem package but relevant: https://bugs.archlinux.org/task/23746 Greg -- () against html e-mail | usenet & email communication netiquette /\ www.asciiribbon.org | www.netmeister.org/news/learn2quote.html

1 0

[arch-general] Creating an Arch chroot on a non-Arch system?
by Magnus Therning 23 Jul '11

23 Jul '11

Is there something available out there that makes it easy to create an Arch chroot on a non-Arch system, e.g. Ubuntu or Fedora? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus(a)therning.org jabber: magnus(a)therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay

5 5

[arch-general] PKGBUILD.proto improvements
by C Anthony Risinger 22 Jul '11

22 Jul '11

i wanted to share a couple of loose thoughts on the standard practices for PKGBUILDs ... specifically development ones ... with an immediate focus on git ones (for this instance, but applies to any) awhile back i tried to make a super cheap way of doing git checkouts for builds: https://bbs.archlinux.org/viewtopic.php?id=86366 (and this would have worked if i would have thought to make git use itself as an alternative object pool ...) ... the motivation of this message is to encourage adding some routines to the makepkg library, similar to msg/msg2/warning/etc, to handle development checkouts. basically i see people using _gitroot and _gitname for different stuff ... namely _gitname. i'd like to see a routine that pulls the repo to a known location so it doenst get blown away every update, and so the user doesnt have to manually manage this. everyone does it differently, puts the repository in all sorts of different locations/etc, and it just isnt very pretty IMO. ... so, i suggest a permanent setup based off my out setup and experiences, in reference of this PKGBUILD in particular: http://aur.archlinux.org/packages/pyjamas-engine-pythonwebkit/PKGBUILD ) allow _git* variables to be altered by the environment ) add _gitspec variable which supercedes _gitname for checkout stage (so you can do relative checkouts or SHA1 based checkouts) ... in the routine ... ) use a targeted fetch command instead of a blind clone. not only is this more flexible, but it can significantly reduce download size (for kernel its a ~50% reduction IIRC). the methoud from my builds are very simple, greatly resembling --mirror mode in git, but ONLY for the exact branch you are building ) store repositories in a known list of locations. my PKGBUILD searches these: /var/abs/PKGBUILD.devel/${pkgname}.git /var/abs/local/PKGBUILD.devel/${pkgname}.git ${SRCDEST}/PKGBUILD.devel/${pkgname}.git ${startdir}/PKGBUILD.devel/${pkgname}.git ~/PKGBUILD.devel/${pkgname}.git ... and chooses the first one that already exists (PKGBUILD.devel location only BEFORE appending repo name), OR the first one with write access to parent dir (it will create PKGBUILD.devel for you if it can). i personally used the first one (/var/abs/PKGBUILD.devel), with `chmod 1777` to sticky bit it like /tmp. this not only allows for reuse, but also allows for safely+easily+consistently bind-mounting into a chroot for use with mkchrootpkg ... ) use a proxy mechanism in the event a repository is found but it is read-only. this lets you read-only bind mount a repo (think mkchrootpkg), and it will simply create a new repository, copy the refs, and setup the object directory as an alternative for the proxy repo. thus the proxy has the ability to download new objects as needed, but starts from the same spot as the bind-mounted repo. these techniques save me a great deal of time and pain. that package in particular is a custom webkit build, requiring over 1GB to clone ... mkchrootpkg tried to blow it away once, bit it was read-only :-) ... i intend to possibly improve on this process by reducing a targeted fetch to a *shallow* targeted fetch , ie. the minimum amount of objects required to build. i have seen "clones" go down to 50%, sometimes even 10% or less, by using this over a naive `git clone $xyz`. i'd like to see *something* adopted so we can end the madness :-) ... below are a couple key excerpts from the noted PKGBUILD, for your reference. C Anthony ------------------------------------------------- [locate repo] ------------------------------------------------- # Devel directory fragment : ${_dir_devel:=PKGBUILD.devel} # Local/custom repo? if [[ -z ${_gitrepo} ]]; then search=(/var/abs{,/local}/"${_dir_devel}" "${SRCDEST%%/}/${_dir_devel}" "${startdir%%/}/${_dir_devel}" ~/"${_dir_devel}") for d in "${search[@]%%/}"; do if [[ -e ${d} ]] || [[ ! -e ${d} && -w ${d%/*} ]]; then mkdir -p "${d}" 2>&- && _gitrepo_proxy="${srcdir}/${pkgname}.git" && _gitrepo="${d}/${pkgname}.git" && break fi done fi ------------------------------------------------- [create new repo, or new proxy, if needed] ------------------------------------------------- mkdir -p "${w}" if [[ ! -e ${g}/objects ]]; then msg "[git] Creating NEW repository ... " git --git-dir="${g}" --work-tree="${w}" init elif [[ ! -w ${g}/objects ]]; then warning "[git] Repository read-only, setting up proxy ... " git --git-dir="${_gitrepo_proxy}" --work-tree="${w}" init echo "${g}/objects" > "${_gitrepo_proxy}/objects/info/alternates" cp -r "${g}/refs" "${_gitrepo_proxy}" g="${_gitrepo_proxy}" fi ------------------------------------------------- [perform targeted fetch] ------------------------------------------------- msg "[git] Syncing ... ${_gitroot} -> ${g}" git --git-dir="${g}" --work-tree="${w}" fetch -fu "${_gitroot}" "+${_gitname}:${_gitname}" msg "[git] Reading ... ${_gitspec:-${_gitname}} -> ${w}" git --git-dir="${g}" --work-tree="${w}" read-tree --reset -u "${_gitspec:-${_gitname}}" -------------------------------------------------

3 4

Re: [arch-general] Panic - no sound devices after upgrade
by Tom Gundersen 22 Jul '11

22 Jul '11

On Thu, Jul 21, 2011 at 4:01 PM, Adrian Knoth <adi(a)drcomp.erfurt.thur.de> wrote: > On 07/21/11 15:00, Tom Gundersen wrote: > > Hi! > >>>>>>> * The driver for my card (RME HDSP MADI, snd_hdpsm) is loaded. >>>>> [ 48.057757] HDSPM: unknown firmware revision cc > >> firmware revision is 0xCC, which is not recognised. If your card is >> MADI, the kernel expects the firmware revision to be 0xD2 (or starting >> in 3.0, it also accepts 0xCF). > > Exactly. > >> I guess this can be fixed easily by adding your firmware revision to >> the list of accepted revs. > > I hope so, too. Please try the attached patch. Fons (or anyone else who could reproduce the problem), If you want to try out Adrian's patch, I uploaded a kernel with the patch applied here: <https://dev.archlinux.org/~tomegun/kernel26-2.6.39.1.3-1.1-i686.pkg.tar.xz>. Cheers, -t

2 2