Hi,
Arch install is graceful.After "pacman -S xorg gnome", the startx
brought me to gnome.
everygthing seem fine till I quited X by Ctrl+Alt+BackSpace, After a
while i tried to re-startx and just had no response. No message is
shown and the X won't show up.The .xinitrc is clean, and the xorg.con
Hi!
Il Wednesday 07 May 2008 21:40:29 Michal Soltys ha scritto:
> In most simple words - when you compile your kernel, exclude
> 'ATA/ATAPI/MFM/RLL support' completely.
>
> Make sure 'SCSI device support' is in sane condition, and select
> whatever you need from 'Serial ATA (prod) and Parallel ATA
I had this same exact problem while either upgrading or installing a
package(s) and I simply removed it (which I was almost sure would break
something anyway) and reran pacman and it seemed to work fine. Although
I probably wouldnt recommend doing it because it could possibly affect
one package dif
Carotinho wrote:
Hi!
The main question is: how can I obtain the "right" behaviour from my own
compiled kernel? Is this due to some misconfiguration of the kernel at
compile-time, or is it obtained through some other kind of magic?
The real problem here is that I cannot give a name to this pro
Xavier wrote:
Lukáš Jirkovský wrote:
Hi
I don't know if it's bug or feature, but it makes me crazy. It begun
probably after some pacman upgrade.
I'm using blowfish passwords with my archlinux, so my
/lib/libcrypt.so.1 points to libxcrypt.so.1 instead of libcrypt-2.7.so
from glibc. In my pacman.c
Lukáš Jirkovský wrote:
Hi
I don't know if it's bug or feature, but it makes me crazy. It begun
probably after some pacman upgrade.
I'm using blowfish passwords with my archlinux, so my
/lib/libcrypt.so.1 points to libxcrypt.so.1 instead of libcrypt-2.7.so
from glibc. In my pacman.conf I have NoEx
I found this in the Official Arch Linux Install Guide on the wiki:
"With the current kernel, an important change has been introduced pertaining
to the ATA/IDE subsystem. The new pata (Parallel ATA) drivers replace the
legacy IDE subsystem, and one important change is that the naming scheme for
IDE
At a guess, it sounds like arch is loading a module that's a specific
driver for your chipset, while your own kernel is using the generic
ata drivers. Take a look at the output of hwd, lspci and such. You
also might get some mileage out of googling your motherboard, or poke
around on the forums (
Hi!
I'm sure this is an already answered question, but the problem is that I don't
know which could be the question whose answer I'm in need of:)
After this prologue, the problem is:
The currently running system, with the Arch-supplied 2.6.24 kernel, has the
disk devices all mapped to a /dev/sd
Hi
I don't know if it's bug or feature, but it makes me crazy. It begun
probably after some pacman upgrade.
I'm using blowfish passwords with my archlinux, so my
/lib/libcrypt.so.1 points to libxcrypt.so.1 instead of libcrypt-2.7.so
from glibc. In my pacman.conf I have NoExtract = lib/libcrypt.so
10 matches
Mail list logo
