Re: [arch-general] X fails to start with intel card after latest kernel update
Is KMS enabled? On Sat, Oct 10, 2009 at 2:39 AM, David C. Rankin drankina...@suddenlinkmail.com wrote: On Friday 09 October 2009 06:24:06 am Jan de Groot wrote: On Fri, 2009-10-09 at 12:53 +0200, Damjan Georgievski wrote: After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are: 02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff grep (EE) Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module i810 (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) this is not important looking at you log file it seems that X did start just fine And it exited fine also, so it's not X related. I must have posted the Xorg from the wrong arch box. Here is what I'm seeing: (WW) intel(0): No outputs definitely connected, trying again... (II) intel(0): Output VGA disconnected (WW) intel(0): Unable to find initial modes (EE) intel(0): No valid modes. (II) UnloadModule: intel (II) UnloadModule: vgahw (II) Unloading /usr/lib/xorg/modules//libvgahw.so (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- Flávio Coutinho da Costa
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
On Fri, Oct 9, 2009 at 8:06 PM, Hussam Al-Tayeb ht990...@gmail.com wrote: Hi, I'm having a problem with disk encryption using luks. I have my /home disk (on a separate disk 'sdb') encrypted using luks. I have this in /etc/cryptsetup home /dev/sdb1 ASK and this in /etc/fstab /dev/mapper/home /home ext4 defaults,user_xattr 0 1 Suddenly today, it won't accept the passphrase on boot. I'm sure that I'm entering it correctly. It took me 32 tries the first time and many more the second reboot after kernel 2.6.31.3 update. The annoying thing is that archlinux only takes three tries then fails and I have to reboot to try again. Any idea please? I'm 100% sure I'm entering the passphrase correctly. I don't have another operating system installed or anything and I go back to work in a few days so looking for a new distribution or operating system is not a favorable option. I really need help please :/ [r...@lars hussam]# cryptsetup status /dev/mapper/home /dev/mapper//dev/mapper/home is active: cipher: aes-cbc-essiv:sha256 keysize: 128 bits device: /dev/sdb1 offset: 1032 sectors size: 156295290 sectors mode: read/write Make sure that /dev/sdb1 is the partition you think it is, and the disks haven't switched device nodes. :)
Re: [arch-general] New PKGBUILD for libtorrent-rasterbar
Jeff Horelick wrote: Hey all, libtorrent-rasterbar is pretty out of date (2 months and 2 package versions), so here's a PKGBUILD for the new version. I bumped the pkgver (obviously), added python to the dependency list since we *ARE* building the python bindings... Do the python packages need to be depends, or can they just be makedepends? Just curious, I don't use this myself. T.
Re: [arch-general] /dev/tty* borked ...
On Fri, Oct 9, 2009 at 2:20 PM, Thomas Bächler tho...@archlinux.org wrote: Xavier schrieb: Unfortunately we can no longer check the cvs repo afaik. We cannot see earlier than April 2008 : http://repos.archlinux.org/viewvc.cgi/udev/trunk/PKGBUILD?view=log I am also curious to know how did that file stay. Why wasn't it tracked and removed by pacman ? The old cvs-arch and cvs-core are still around somewhere, but not public. So since we still have no information about that /etc/udev/rules.d/udev.rules file, it seems it could potentially be on all old arch systems (2007 or older). Should the kernel post_upgrade either display a warning or just remove that file automatically ? A warning could be safer if a user used this file for custom rules.
Re: [arch-general] /dev/tty* borked ...
Xavier wrote: On Fri, Oct 9, 2009 at 2:20 PM, Thomas Bächler tho...@archlinux.org wrote: Xavier schrieb: Unfortunately we can no longer check the cvs repo afaik. We cannot see earlier than April 2008 : http://repos.archlinux.org/viewvc.cgi/udev/trunk/PKGBUILD?view=log I am also curious to know how did that file stay. Why wasn't it tracked and removed by pacman ? The old cvs-arch and cvs-core are still around somewhere, but not public. So since we still have no information about that /etc/udev/rules.d/udev.rules file, it seems it could potentially be on all old arch systems (2007 or older). Should the kernel post_upgrade either display a warning or just remove that file automatically ? A warning could be safer if a user used this file for custom rules. My current Arch Linux was (re)installed last time in 2005 and only updated after that. I don't have /etc/udev/rules.d/udev.rules . I must have removed it manually. I think some time ago there was an announcement or discussion about this on this list, but I'm not sure. Armando
[arch-general] PKGBUILD
I am constructing a PKGBUILD for a package and I know some of the variables have been depreciated Has $startdir been removed if so what is it new equiv. Thanks
[arch-general] confirm LTS kernel / usb printer permission issues
I have a permission issue when using the kernel26-lts with my usb printer. The device doesn't always get lp group. Especially when I switch it off and on again. Then new cups 1.4.x can't find the printer. With kernel 2.6.30 and 2.6.31 the group is always set well. I already asked a few udev upstream devs without a solution so far. See http://www.spinics.net/lists/hotplug/msg02798.html It would be nice if some of you could try confirming my problem and maybe you can help me to find the reason why it fails on my server. Thanks. -Andy
[arch-general] Overly large fonts in X11 after rebooting
For some reason when I turned my laptop on today and started X, all my fonts were larger than normal. The only one that seems to have the stayed has been my console font, but even that feels a bit off (however, I'm not too worried about that, it could be that I'm sitting slightly closer than normal; the rest are most certainly measurably larger, though). The only difference between now and previously is that I don't have my external monitor plugged in, but my resolution didn't change, and I've used this computer without the external before without problems. It's just simply bigger; I turned down the GTK font, which seems to have worked for some apps (like firefox and pidgin), but the fonts are unbearably large for some websites: http://logik.li/images/screenshots/arrakis/large_fonts_in_some_places.png A few months ago I had a similar problem with certain sites having large fonts, and never really managed to solve it, one day after reinstalling it just went away and never came back until now. This was probably related. This is what similar sites used to look like: http://logik.li/images/screenshots/arrakis/let_me_show_you.png (and when they used to be bad: http://logik.li/images/screenshots/arrakis/126-negative_what_log-p.png ) So, anyone have any ideas about what I should do? -- Samuel Baldwin - logik.li
Re: [arch-general] Overly large fonts in X11 after rebooting
On Sat, Oct 10, 2009 at 6:05 PM, Samuel Baldwin recursive.for...@gmail.com wrote: For some reason when I turned my laptop on today and started X, all my fonts were larger than normal. The only one that seems to have the stayed has been my console font, but even that feels a bit off (however, I'm not too worried about that, it could be that I'm sitting slightly closer than normal; the rest are most certainly measurably larger, though). The only difference between now and previously is that I don't have my external monitor plugged in, but my resolution didn't change, and I've used this computer without the external before without problems. It's just simply bigger; I turned down the GTK font, which seems to have worked for some apps (like firefox and pidgin), but the fonts are unbearably large for some websites: http://logik.li/images/screenshots/arrakis/large_fonts_in_some_places.png A few months ago I had a similar problem with certain sites having large fonts, and never really managed to solve it, one day after reinstalling it just went away and never came back until now. This was probably related. This is what similar sites used to look like: http://logik.li/images/screenshots/arrakis/let_me_show_you.png (and when they used to be bad: http://logik.li/images/screenshots/arrakis/126-negative_what_log-p.png ) So, anyone have any ideas about what I should do? Check the DPI of your display (with xdpyinfo). Probably the lack of the external monitor made it come up differently. I dealt with this by fixing the XFT DPI value to 96, which is what most fonts are designed for, and what most software that cares, expects it to be. This can be done by setting the X property xft.dpi to 96.
Re: [arch-general] Overly large fonts in X11 after rebooting
2009/10/10 Ray Kohler ataraxia...@gmail.com: Check the DPI of your display (with xdpyinfo). Probably the lack of the external monitor made it come up differently. I dealt with this by fixing the XFT DPI value to 96, which is what most fonts are designed for, and what most software that cares, expects it to be. This can be done by setting the X property xft.dpi to 96. arrakis^~% xdpyinfo| grep -E 'resol|dimens' dimensions:1680x1050 pixels (331x210 millimeters) resolution:129x127 dots per inch Not good? Where should I set xft.dpi? (Sorry, I haven't twiddled with X much besides xorg.conf and .Xdefaults, is it either of those?) -- Samuel Baldwin - logik.li
Re: [arch-general] Overly large fonts in X11 after rebooting
On Sat, Oct 10, 2009 at 6:21 PM, Samuel Baldwin recursive.for...@gmail.com wrote: 2009/10/10 Ray Kohler ataraxia...@gmail.com: Check the DPI of your display (with xdpyinfo). Probably the lack of the external monitor made it come up differently. I dealt with this by fixing the XFT DPI value to 96, which is what most fonts are designed for, and what most software that cares, expects it to be. This can be done by setting the X property xft.dpi to 96. arrakis^~% xdpyinfo| grep -E 'resol|dimens' dimensions: 1680x1050 pixels (331x210 millimeters) resolution: 129x127 dots per inch Not good? Where should I set xft.dpi? (Sorry, I haven't twiddled with X much besides xorg.conf and .Xdefaults, is it either of those?) Yes, put it in .Xdefaults and do whatever you normally do after changing that file. Case matters: Xft.dpi: 96
Re: [arch-general] PKGBUILD
Stefan Husmann wrote:
Baho Utot schrieb:
Thorsten Toepper wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224
On Sat, 10 Oct 2009 16:08:02 -0400
Baho Utot baho-u...@columbus.rr.com wrote:
I am constructing a PKGBUILD for a package and I know some of the
variables have been depreciated
Has $startdir been removed if so what is it new equiv.
Thanks
Using $pkgdir and $srcdir is more welcome than using
$startdir/{src,pkg}
Not if you're writing a log file and makepkg -c is used.
If all these variables are defined, they all can be used. The question
is, for what purpose. Having a logfile in $startdir sounds reasonable
to me.
Files which are needed to compile a package should go to $srcdir,
files that should be in the resulting package should got to $pkgdir.
In general, you should never use $startdir. There is no guarantee that
$stardir/src = $srcdir or similarly with $pkgdir. In fact that
definitely does not hold with split packages. If you want to log the
build, use makepkg -L.
I can not think of a valid reason to use $startdir.
Allan
Re: [arch-general] [arch-dev-public] [signoff] xfsprogs-3.0.3-1
Hi! anyone uses xfs? thanks Please signoff. I'm using XFS, what should I do for obtaining a valid signoff? Thanks Dario Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
Re: [arch-general] [arch-dev-public] [signoff] xfsprogs-3.0.3-1
Dario wrote: Hi! anyone uses xfs? thanks Please signoff. I'm using XFS, what should I do for obtaining a valid signoff? Use the xfsprogs package from [testing] and see if everything still works. It should be safe to upgrade only that package from the [testing] repo. If it works, send a message here saying so and what architecture you use. Allan
Re: [arch-general] PKGBUILD
Allan McRae wrote:
Stefan Husmann wrote:
Baho Utot schrieb:
Thorsten Toepper wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224
On Sat, 10 Oct 2009 16:08:02 -0400
Baho Utot baho-u...@columbus.rr.com wrote:
I am constructing a PKGBUILD for a package and I know some of the
variables have been depreciated
Has $startdir been removed if so what is it new equiv.
Thanks
Using $pkgdir and $srcdir is more welcome than using
$startdir/{src,pkg}
Not if you're writing a log file and makepkg -c is used.
If all these variables are defined, they all can be used. The
question is, for what purpose. Having a logfile in $startdir sounds
reasonable to me.
Files which are needed to compile a package should go to $srcdir,
files that should be in the resulting package should got to $pkgdir.
In general, you should never use $startdir. There is no guarantee
that $stardir/src = $srcdir or similarly with $pkgdir. In fact that
definitely does not hold with split packages. If you want to log the
build, use makepkg -L.
I can not think of a valid reason to use $startdir.
Allan
Ok here is your valid reason
./configure --prefix=/usr --shared --libdir=/lib || return 1
make || return 1
make check 21 | tee $startdir/check-log
make DESTDIR=${pkgdir} install || return 1
rm -v $pkgdir/lib/libz.so || return 1
install -d -m 0755 $pkgdir/usr/lib || return 1
ln -sfv ../../lib/libz.so.1.2.3 $pkgdir/usr/lib/libz.so || return 1
Re: [arch-general] PKGBUILD
Baho Utot wrote:
Allan McRae wrote:
Stefan Husmann wrote:
Baho Utot schrieb:
Thorsten Toepper wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224
On Sat, 10 Oct 2009 16:08:02 -0400
Baho Utot baho-u...@columbus.rr.com wrote:
I am constructing a PKGBUILD for a package and I know some of the
variables have been depreciated
Has $startdir been removed if so what is it new equiv.
Thanks
Using $pkgdir and $srcdir is more welcome than using
$startdir/{src,pkg}
Not if you're writing a log file and makepkg -c is used.
If all these variables are defined, they all can be used. The
question is, for what purpose. Having a logfile in $startdir sounds
reasonable to me.
Files which are needed to compile a package should go to $srcdir,
files that should be in the resulting package should got to $pkgdir.
In general, you should never use $startdir. There is no guarantee
that $stardir/src = $srcdir or similarly with $pkgdir. In fact that
definitely does not hold with split packages. If you want to log the
build, use makepkg -L.
I can not think of a valid reason to use $startdir.
Allan
Ok here is your valid reason
./configure --prefix=/usr --shared --libdir=/lib || return 1
make || return 1
make check 21 | tee $startdir/check-log
make DESTDIR=${pkgdir} install || return 1
rm -v $pkgdir/lib/libz.so || return 1
install -d -m 0755 $pkgdir/usr/lib || return 1
ln -sfv ../../lib/libz.so.1.2.3 $pkgdir/usr/lib/libz.so || return 1
Not valid. Use makepkg -L to log the entire build process. In the
future, there will be a check() function, so you will then get separate
logs for build(), check() and package().
Re: [arch-general] PKGBUILD
Allan McRae wrote:
Baho Utot wrote:
Allan McRae wrote:
Stefan Husmann wrote:
Baho Utot schrieb:
Thorsten Toepper wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224
On Sat, 10 Oct 2009 16:08:02 -0400
Baho Utot baho-u...@columbus.rr.com wrote:
I am constructing a PKGBUILD for a package and I know some of
the variables have been depreciated
Has $startdir been removed if so what is it new equiv.
Thanks
Using $pkgdir and $srcdir is more welcome than using
$startdir/{src,pkg}
Not if you're writing a log file and makepkg -c is used.
If all these variables are defined, they all can be used. The
question is, for what purpose. Having a logfile in $startdir sounds
reasonable to me.
Files which are needed to compile a package should go to $srcdir,
files that should be in the resulting package should got to $pkgdir.
In general, you should never use $startdir. There is no guarantee
that $stardir/src = $srcdir or similarly with $pkgdir. In fact
that definitely does not hold with split packages. If you want to
log the build, use makepkg -L.
I can not think of a valid reason to use $startdir.
Allan
Ok here is your valid reason
./configure --prefix=/usr --shared --libdir=/lib || return 1
make || return 1
make check 21 | tee $startdir/check-log
make DESTDIR=${pkgdir} install || return 1
rm -v $pkgdir/lib/libz.so || return 1
install -d -m 0755 $pkgdir/usr/lib || return 1
ln -sfv ../../lib/libz.so.1.2.3 $pkgdir/usr/lib/libz.so || return 1
Not valid. Use makepkg -L to log the entire build process. In the
future, there will be a check() function, so you will then get
separate logs for build(), check() and package().
It would do what I require to log the entire build...
This is not the future, I am still stuck in current time
make check is valid.
I don't want to pollute the check log file with the build information.
All I want to pick through is the testing info.
On the example the build and check logs are small, care to look at the
check log for glibc?
Hint it is over 7800 lines just for the check, good luck looking at that
plus the entire build in one file.
Re: [arch-general] [arch-dev-public] [signoff] xfsprogs-3.0.3-1
Hi! In data domenica 11 ottobre 2009 02:32:20, Allan McRae ha scritto: Use the xfsprogs package from [testing] and see if everything still works. It should be safe to upgrade only that package from the [testing] repo. If it works, send a message here saying so and what architecture you use. Ok. I've tried the safe progs with expected results and no problems of any sort (safe = the programs that don't do something radical as xfs_mdrestore). I'm running arch i686. For me, it's all right. Hope this helps:) ciao! Dario Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
Re: [arch-general] Overly large fonts in X11 after rebooting
On Sat, Oct 10, 2009 at 06:21:00PM -0400, Samuel Baldwin wrote: 2009/10/10 Ray Kohler ataraxia...@gmail.com: Check the DPI of your display (with xdpyinfo). Probably the lack of the external monitor made it come up differently. I dealt with this by fixing the XFT DPI value to 96, which is what most fonts are designed for, and what most software that cares, expects it to be. This can be done by setting the X property xft.dpi to 96. arrakis^~% xdpyinfo| grep -E 'resol|dimens' dimensions:1680x1050 pixels (331x210 millimeters) resolution:129x127 dots per inch Not good? Where should I set xft.dpi? (Sorry, I haven't twiddled with X much besides xorg.conf and .Xdefaults, is it either of those?) i have an acer aspire 4720 laptop and i also was having problems with large fonts.this link [1] helped me. I also manually unchecked the option allow pages to choose their own fonts under firefox-edit-preferences-content-advanced. [1]http://wiki.archlinux.org/index.php/Acer_Aspire_One#Setting_dpi
Re: [arch-general] Overly large fonts in X11 after rebooting
Excellent, the dpi trick worked perfectly. I wonder why it fiddled with it... glad it's all working now though, thank you! I might try the trick with the other sites chosing fonts as well, some people have horrid taste. -- Samuel Baldwin - logik.li
