January 2012 - Arch-general - lists.archlinux.org

[arch-general] Warning about kmod replacing modules init tools in testing.
by fredbezies 06 Jan '12

06 Jan '12

I have two computers, both using nvidia driver. My laptop started flawlessly, after I renamed empty file modprobe.conf.pacsave to modprobe.conf in /etc/modprobe.d/ On my desktop computer, all went bad. udevadm trigger doesn't work. I had to downgrade both packages (kmod replaced by modules-init-tools) and mkinitcpio, blacklisting both of them in my /etc/pacman.conf ignorepackage line. My /etc/modprobe.conf is not empty : # # /etc/modprobe.d/modprobe.conf (for v2.6 kernels) # blacklist keucr blacklist usblp For now, I'm blocking upgrade for both package. I opened a bug on archlinux BTS : https://bugs.archlinux.org/task/27846 I know testing can be busted sometimes, but this bust is one the worst I've seen for a year or so. -- Frederic Bezies fredbezies(a)gmail.com

2 2

Re: [arch-general] [arch-dev-public] Signoff report for [testing]
by Marek Otahal 06 Jan '12

06 Jan '12

On Friday 06 of January 2012 15:30:16 Roman Kyrylych wrote: > My bad. Sorry, no working i686 with cryptsetup. > For such cases a user signoff request on arch-general may be useful. > Or just move it without signoff. user sign-off for cryptsetup on i686, 4 partitions on a laptop, running daily. all ok. -- Marek Otahal :o)

1 0

[arch-general] haskell-text out of date
by Cédric Girard 06 Jan '12

06 Jan '12

Hi, haskell-text [1] has been flagged out of date in [extra], mid-November. It has not been updated since. Since this package has no maintainer I'm not sure this has even been noticed. This package is a dependency for the git version of xmobar [2]. cabal2arch gives a working PKGBUILD but I haven't tested the resulting package more than installing it. [1] https://www.archlinux.org/packages/extra/x86_64/haskell-text/ [2] https://aur.archlinux.org/packages.php?ID=44683 -- Cédric Girard

2 2

Re: [arch-general] [arch-dev-public] kmod-3 in [testing]
by Bjørn Øivind Bjørnsen 06 Jan '12

06 Jan '12

On 06/01/12 05:44, Dan McGee wrote: > On Thu, Jan 5, 2012 at 9:41 PM, Dan McGee <dpmcgee(a)gmail.com> wrote: >> On Thu, Jan 5, 2012 at 6:40 PM, Dave Reisner <d(a)falconindy.com> wrote: >>> Hey all, >>> >>> I've just dropped kmod-3 into testing as a replacement for >>> module-init-tools. This is still a young project, but it has a lot of >>> support from active people, and I (as well as Tom) have been working >>> closely with upstream to flesh out and fix bugs. >>> >>> For the most part, you should not notice any difference. kmod was >>> designed as a drop-in replacement for m-i-t, and all the binaries should >>> exist with the (mostly) the same options. Whenever possible, options or >>> features marked deprecated in m-i-t were removed, such as: >>> >>> - parsing of depmod/modprobe config for files not ending in .conf >>> - modprobe's -l, --list options >>> >>> IMPORTANT: In line with the first change, it needs to be pointed out >>> that we will no longer package /etc/modprobe.d/modprobe.conf. This means >>> that if you wrote to that file, it will be .pacsave'd on removal of >>> m-i-t and you must rename it. We will continue to ship what used to be >>> called /etc/depmod.d/depmod.conf, but rename it /lib/depmod.d/search.conf. >>> This will be a read only file -- users should put their own tweaks in >>> /etc/depmod.d. >>> >>> One other thing you might notice is that kmod doesn't currently include >>> man pages. I don't consider this a loss -- the m-i-t manpages did not >>> provide full coverage, nor did the command line help. kmod's binaries >>> all currently have full coverage of options via -h, --help. >>> >>> Lastly, there's an accompanying mkinitcpio update to account for some >>> extra verbosity of kmod's modprobe and depmod tools. You do *not* need >>> to regenerate your initramfs images unless you feel so inclined. >>> >>> Have fun! >> >> Or don't. Not to rain on Dave's parade (this isn't his fault), but >> unless you want to sit at your initrd shell for a half hour >> un-breaking stuff, I'd recommend steering clear of this package and >> sticking with the old but proven module-init-tools. This package >> causes modprobe when called by udev to randomly not load modules or >> something; first noticable with uhci_hcd and my mouse (trivial), later >> with ahci on boot (not cool, not having disk drives). >> >> **Tip**: if you get screwed, call `udevadm trigger` a few times, it >> seems to knock some sense into the system. You can do this in the >> initrd environment too. > > Update- because Dave is awesome, he whipped up some patches and I > tested them that appear to fix the above problem, so the latest kmod > package in [testing] should be safe to test. > > Thanks Dave! > > -Dan I just installed kmod-3-3 from [testing] and tried a reboot, which promptly left me with no rootfs and, oddly enough, no keyboard input in the initrd shell, which made the problem somewhat difficult to debug. However, an additional boot came up fine. I'm going to keep the package around to see if it happens again, but I hardly ever boot this box so it may take a while. This may not be quite ready for [core] just yet ;) Regards, Bjørn Øivind

2 1

[arch-general] Kernel 3.2.1
by Myra Nelson 06 Jan '12

06 Jan '12

This update seems to work fine. Myra -- Life's fun when your sick and psychotic!

1 0

[arch-general] Need a little help getting started with contributing
by Göran Gustafsson 05 Jan '12

05 Jan '12

Hello everyone! I got a few small patches related to esthetical issues that i would like to send upstream so everyone else can enjoy them. I'm a little bit lost on how i should do this. The packages i've edited is initscripts, mkinitcpio and filesystem. When it comes to initscripts and mkinitcpio i've just cloned the git repositories but i'm not sure how i should send the commits upstream. git push doesn't work since i don't have the right permissions. I've only used github to send pull request before so i'm not that confident in git yet. Can i do the same thing with just the git command? Also, does the filesystem package have a git repository i can use too? Any help getting started would gladly be appreciated! :)

5 7

[arch-general] Newbies in Arch [WAS: Suspend seems not to work with nVidia Nouveau driver]
by Oon-Ee Ng 05 Jan '12

05 Jan '12

On Wed, Jan 4, 2012 at 10:58 AM, Jonathan Vasquez <jvasquez1011(a)gmail.com> wrote: > I've been doing things to attract users to Arch. Whether they are > newbs or not, because I want people to learn. As long as you have > willingness and determination to learn, that is the important thing. > The resources are out there, people just need to look, and I'm willing > to add to those resources. > > You aren't adding anything beneficial by telling others that their > comments are equal to troll statements, when this is clearly not true. Attracting users to Arch is not a stated goal, this has been repeated many times in various fora. Arch is only for a certain type of users, those who are willing and able to learn. I'm not knocking your effort, but a quick glance at those resources you've provided indicate that you're trying to make it very easy to get to using Arch, and I don't think that's beneficial for Arch or its community. There are other distributions for 'easy-to-use', Arch should not be that. Not because of any type of elitism, but because Arch's niche is about control and simplicity, and making it 'newbie-friendly' (whatever that means) would compromise that. Splitting the thread (sorry I use gmail, so it won't split for you guys on mutt or whatever) to reduce the 'corruption' of original thread, not that I think it'll make a difference though.

18 30

[arch-general] archiso rebuild
by gt 05 Jan '12

05 Jan '12

Hello folks I was wondering if there is a way to rebuild a custom live disc, using archiso, without having to download all the packages over again. The problem is that after making a few changes to the configuration, mainly inside root-image directory, i want to rebuild the iso. But, running build.sh says that everything is up-to-date. Alternatively, i tried removing the root squashfs file, and ran build.sh again. But, it started downloading ~500MB of packages all over again :( I'll probably have to do some more fine tuning before finalising the iso, and i don't want this to repeat itself. Please help. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

3 4

[arch-general] System a bit broken pacman -Syu exists in filesystem
by Lars Madson 05 Jan '12

05 Jan '12

Hi, My system has two hard drive, one SSD with / and /home/user on two partitions and a HDD mounted on /opt and /var. The HDD failed, and the system works with only the SSD as it was installed like this and then extended to the HDD. Only 3 or 4 weeks of update make a difference between the content of /var and /opt on the SSD and the HDD. Now I'm performing an upgrade of the whole system to get back to normal but all files in /usr are making conflict as the /opt and /var are older and trying to install files that are already there. So I could - but it seems really painful - rename all the conflicting files (they are a lot), if anyone as an idea how to automatize this. Or maybe I would love some kind of option in pacman that would overwrite or ignore those conflicts, I know that's against how pacman is build so I'm asking here. Hope I make sens. thx Laurent

4 6

[arch-general] Battery question about a Firmware Bug in logs.
by Don Juan 05 Jan '12

05 Jan '12

I am running Arch on a Toshiba Qosmio x505-q887. I have tried everything I can find online and in the wikis in setting things up but no matter what I have tried I can not get rid of the message in the logs, though my battery life seems semi reasonable, roughly 1.75hrs on average so far with not much tweaking being done to help extend. Error: [Firmware Bug]: battery: (dis)charge rate invalid. Is this something I should be worried about? Will it screw up my battery in charging and use right now as is? I am not really finding much online in relation to this actual error in the logs. Mostly its people saying that the logs report that the discharge rate is 0% and mine just says discharging and gives no rate or anything. I am fully updated currently, not on testing repos. I also do get 2 other messages in the logs that I am not sure if they are related. [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored From what I read and understand online, is this is of no real concern and I don't need to worry about it. Is this correct in my thinking and understanding? PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug. I have tried doing what it says in the Kernel boot args but it just gives me the same message but saying to do the reverse and use pci=crs. I have not looked much into this one, but don't want to leave out something that may be causing what I am asking. I can send any configs if needed Thanks for anyone's time and effort in helping.

4 12