[Solved] Inconsistency detected by ld.so: ../sysdeps/x86_64/...

I just did a fresh install of Arch, ran "pacman -Syy" and it returned the error:
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 466: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
Any Ideas? The only relevant thread I found was this one in German (which I don't speak): https://bbs.archlinux.de/viewtopic.php?id=18115
Last edited by Thal3s (2012-01-08 00:19:48)

I had this same problem after a fresh install. Barely had anything installed apart from xorg, awesome, xf86-video-ati, luakit, chromium, vim, and deja-fonts. I reinstalled all packages (see: https://bbs.archlinux.org/viewtopic.php?pid=263443) and it seems to have fixed it. Not sure if this is hardware related or not, I haven't had a chance to test yet. hope this helps someone.

Similar Messages

Error in Mapping of Data for Scrambling Rule due to Inconsistency detected in Mapping Engine PIFD

Hi all,
We are performing an HCM Data scrambling, however, in Package Setting phase, we are encountering error in mapping of data for scrambling rule, saying there are inconsistency detected in mapping Engine PIFD.
We have already implemented and checked below SAP notes, but still no luck.
1854557 - Missing PIFD objects or mappings after LT AddOn install.
1665861
- TDMS 4.0 - Collective note for Scrambling
Please advise how to fix the issue? Project is at stand still due to this.
OSS message already opened.
Thanks and regards,
Philip

Hi
This is bug 5195315, which looks to be fixed in a 10.2 patch. If you can pick up the latest 10.2 patch there is like 3 years of fixes worth picking up.
Cheers
David

Error -23011 occurred at LabVIEW Analysis ODE Solver/inconsistency in dimensions of X(0), F and X!

Hi,
I have been trying to simulate ODE but getting following error:
Error -23011 occurred at LabVIEW Analysis ODE Solver/inconsistency in dimensions of X(0), F and X!.
The screenshot of the code is attached.
Please let me know if anyone knows the reason of having this error.
Thank you.
-HB
Solved!
Go to Solution.
Attachments:
Screen Shot 2014-12-02 at 09.58.08.png ‏60 KB

Hi,
I have added another code which includes the "simple chemical reaction" which I am trying to model using ODE in LabVIEW, but I am continously having the same problem.
Kindly see the attachment and try to help me out solving this issue. I couldn't found this kind of error listed on NI forum.
Thank you.
Regards
Hasan
Attachments:
test_hb.vi ‏22 KB

[SOLVED] Problem with Vuze and Java RE x86_64

Hello all !
First of all, sorry if this issue was posted before, but find no related issue similar to mine.
Using pacman, I successfully installed JRE (version 6u16-1-x86_64) and Vuze (version 4.2.0.8-1, former Azureus), but Vuze doesn't want to start.
Running the Vuze's executable in the gnome-terminal, I notice messages from vuze informing it can't find Java executable ("Java exec not found in PATH, starting auto-search..." AND "OOPS, unable to locate java exec in /usr/java/latest /usr/java /usr/lib/jvm/latest /usr/lib/jvm hierarchy") and therefore cannot start the Vuze UI. I also tried but failed in verify the version of Java with the command "java -version" due to command not found.
What is the best approach to fix this problem with Java 64 bits?
Thanks in advance
Last edited by josephg (2009-09-28 18:55:56)

peart wrote:Just log out and back in, most likely. There are scripts in /etc/profile.d/ that need to be run to set up your java environment. They get run automatically when you log in.
Yep, perfect answer - issue solved. Thanks a lot!

[SOLVED] Touchpad detected as keyboard

Since some week back, most probably because of some update my touchpad stopped working correctly. It's like all the extra functions are gone since there is no scrolling, no tapfunction, and it's extremly sensitive.
I've read some of the threads on the forum and tried the solutions but found nothing to work. What I've tried:
1. Comment out the touchpad in /etx/X11/xorg.conf.d/10-evdev.conf
2. Remove /etc/X11/xorg.conf
3. Update udev to 168
4. None of the changes I make to /etc/X11/xorg.conf.d/10-synaptics.conf seem to have any effect at all on the touchpad.
The configuration now is:
/etc/X11/xorg.conf.d/10-evdev.conf
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "synaptic"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
/etx/X11/xorg.conf.d/10-synaptic.conf
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchDevicePath "/dev/input/event*"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "VertEdgeScroll" "on"
EndSection
And the lines from xorg log containing synaptic:
[ 705.427] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 705.427] (**) Sleep Button: Applying InputClass "evdev touchpad catchall"
[ 705.427] (**) Sleep Button: Applying InputClass "touchpad catchall"
[ 705.427] (II) LoadModule: "synaptics"
[ 705.428] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 705.428] (II) Module synaptics: vendor="X.Org Foundation"
[ 705.428] compiled for 1.10.0, module version = 1.4.0
[ 705.428] Module class: X.Org XInput Driver
[ 705.428] ABI class: X.Org XInput driver, version 12.2
[ 705.428] (II) Using input driver 'synaptics' for 'Sleep Button'
[ 705.428] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 705.428] (**) Sleep Button: always reports core events
[ 705.428] (**) Option "Device" "/dev/input/event4"
[ 705.560] (--) Sleep Button: invalid x-axis range. defaulting to 1615 - 5685
[ 705.560] (--) Sleep Button: invalid y-axis range. defaulting to 1729 - 4171
[ 705.560] (--) Sleep Button: invalid pressure range. defaulting to 0 - 256
[ 705.560] (--) Sleep Button: invalid finger width range. defaulting to 0 - 16
[ 705.560] (**) Option "VertEdgeScroll" "on"
[ 705.560] (**) Option "TapButton1" "1"
[ 705.560] (**) Option "TapButton2" "2"
[ 705.560] (**) Option "TapButton3" "3"
[ 705.666] (--) Sleep Button: no supported touchpad found
[ 705.666] (EE) Sleep Button Unable to query/initialize Synaptics hardware.
[ 705.720] (EE) PreInit returned 11 for "Sleep Button"
[ 705.720] (II) UnloadModule: "synaptics"
[ 705.720] (II) Unloading synaptics
[ 705.827] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event7)
[ 705.827] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev keyboard catchall"
[ 705.827] (II) Using input driver 'evdev' for 'SynPS/2 Synaptics TouchPad'
[ 705.827] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 705.827] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 705.827] (**) SynPS/2 Synaptics TouchPad: Device: "/dev/input/event7"
[ 705.853] (--) SynPS/2 Synaptics TouchPad: Found 3 mouse buttons
[ 705.853] (--) SynPS/2 Synaptics TouchPad: Found absolute axes
[ 705.853] (--) SynPS/2 Synaptics TouchPad: Found x and y absolute axes
[ 705.853] (--) SynPS/2 Synaptics TouchPad: Found absolute touchpad.
[ 705.853] (II) SynPS/2 Synaptics TouchPad: Configuring as touchpad
[ 705.853] (**) SynPS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
[ 705.853] (**) SynPS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 705.853] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event7"
[ 705.853] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[ 705.853] (II) SynPS/2 Synaptics TouchPad: initialized for absolute axes.
[ 705.853] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 705.853] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
[ 705.853] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 705.853] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 705.854] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 705.854] (II) No input driver/identifier specified (ignoring)
[ 705.854] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
[ 705.854] (II) No input driver/identifier specified (ignoring)
Last edited by Larsson (2011-04-29 12:09:08)

Temporarily solved the problem. It was as I suspected, the touchpad was detected as a keyboard and therefor loaded the evdev driver as seen in xorg.log. So I changed the /etx/X11/xorg.conf.d/10-synaptic.conf to match keyboard instead and only for the specific event named in xorg.log.
So /etx/X11/xorg.conf.d/10-synaptic.conf:
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event7"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3
Option "VertEdgeScroll" "on"
EndSection
Last edited by Larsson (2011-04-29 12:08:21)

[Solved] Cannot detect camera with udev, only with HAL.

I have removed HAL as I realize it is being deprecated and HAL also created issues with frequent 2-3 second HDD access. I have managed to get udev and pcmanfm to detect and mount pen drives using the udev wiki and new rules.
However, my digital camera is not detected, nor even assigned a device name (unless I use HAL).
Output from "tail -f /var/log/messages.log" after insertion of camera:
Jul 31 15:49:02 eagle kernel: usb 1-4: new high speed USB device using ehci_hcd and address 9
Note udev does NOT assign even a device name. The camera is also not detected via "lsusb". Therefore, without a device name I cannot use:
# udevadm info -a -p $(udevadm info -q path -n [device name])
to even begin writing udev rules.
EDIT and PS: I have copied the /lib/gphoto ruleset file to /etc/udev/rules.d and restarted udev to no effect as well.
EDIT(2): This problem is now "partly" solved. I can detect the camera using "gphoto2" command line, but only as root, so the problem appears to be a udev permission problem, which for some reason HAL did not have.
EDIT(3): Added myself to "camera" group, copied permissions line to libgphoto rules in /etc/udev/rules.d as per camera wiki and problem solved.
It seems that changing over to udev at the moment is not exactly straight forward. I still cannot get automounting of CDROM drive either - but will get there eventually. (I hope udev becomes more user friendly than HAL, because at the moment HAL wins on that front!).
Last edited by lagagnon (2010-07-31 23:55:51)

Search the forums. There is already a thread on this today.
https://bbs.archlinux.org/viewtopic.php?id=180443

[SOLVED]Cannot detect battery or power supply before a power event

The system cannot detect my battery (or AC adapter) since boot, and before a power event
like the following: (the acpi command provides no output)
$ acpi
After I do one of the below
1. plug in AC adapter
2. remove AC adapter
3. cover my screen and uncover my screen
4. drain my battery to low power (probably 15% or 20%)
The system can detect my battery/AC
like the following:
$ acpi
Battery 0: Charging, 61%, 01:18:24 until charged
$ acpi
Battery 0: Discharging, 61%, 05:17:15 remaining
Is this a bug or solved issue?
or should I update my bios?
NOTE: This issue does not exist in Windows (8.1), on the same machine
The laptop is Dell Inspiron 14 7437, without touchscreen
Last edited by dvw10984 (2014-07-21 20:07:37)

I'm glad I could help!
To complete the answer on whether it's a bug or not, it has to do with your BIOS expecting Windows rather than Linux. So you need to tell it that Linux is running and without the parameter, the kernel will return false if asked whether Linux is running. This causes some features to just simply not work.
If adding that parameter makes the screen's backlight to not work, you may want to add "acpi_backlight=vendor" to it also, but it actually caused my computer to not boot and seemed to not make a difference (probably should have mentioned that).
Last edited by markzz (2014-07-22 04:17:18)

[SOLVED] Setting up virtualbox & wine and on x86_64

Hello again
Ok so this should be my last annoying noob post, I have 64-bit Arch setup correctly with gnome and everything. However, I still have a few questions starting with how do I install virtualbox & wine on x86_64? I tried to install virtualbox with pacman -S virtualbox_bin 3.1.2-1 and that didn't work and I haven't even made an attempt with wine yet. Can I safely install a bin32 version of wine? - The wiki didn't make that very clear.
Additionally, I have copied a lot of backup data to my home folder that belongs to the user 'root'. Is there a way that I can, via command line make everything in my home belong to my user?
Last edited by dcj123 (2009-12-29 02:40:31)

anonymous_user wrote:
Both programs can be found in the AUR:
http://aur.archlinux.org/packages.php?ID=9753
http://aur.archlinux.org/packages.php?ID=7915
You can install yaourt first and then use it to install other packages from AUR:
http://wiki.archlinux.org/index.php/Yaourt
ok thanks, I am just going to assume that its safe to install wine bin32. In the mean time, if I chown username my home folder will that change the ownership of every sub-directory/file?
Edit: Found it, thanks anonymous_user.
chown -hvR user /home/user
Solved
Last edited by dcj123 (2009-12-29 02:40:08)

[SOLVED] Inconsistency in the Xorg config.

Hi! After eight years with the same CRT monitor i decided to buy a LCD one. It's a wonderful Philips 190WV and it only costed 130eur. The problem is that i can't get it to work at 1440x900 pixels, the recommended resolution. I have test it with my MacBook Pro and it's working ok in that very resolution. This is my Xorg.conf
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
# PS/2 Mouse not detected
# Serial Mouse not detected
InputDevice "USB Mouse" "CorePointer"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc:unscaled"
FontPath "/usr/share/fonts/X11/75dpi:unscaled"
FontPath "/usr/share/fonts/X11/100dpi:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/Speedo"
FontPath "/usr/share/fonts/X11/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/X11/cyrillic"
# FontPath "/usr/share/fonts/X11/latin2/75dpi"
# FontPath "/usr/share/fonts/X11/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/latex-ttf-fonts"
EndSection
Section "Module"
# Comments: see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346408
Load "dbe" # Double Buffering Extension, very important.
Load "dri" # This shouldn't be available choice if user has selected driver vga, vesa or nv.
Load "glx" # GLX Extension.
Load "freetype" # Freetype fonts.
Load "type1" # Type 1 fonts
Load "record" # Developer extension, usually not needed
# Load "extmod" # This is okay, but if you look into "man xorg.conf" you'll find option NOT to include DGA extension with extmod, and for a good reason.. DGA causes instability as it access videoram without consulting X about it.
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
# Load "speedo" # Speedo fonts, this module doesn't exist in Xorg 7.0.17
# The following are deprecated/unstable/unneeded in Xorg 7.0
# Load "ddc" # ddc probing of monitor, this should be never present, as it gets automatically loaded.
# Load "GLcore" # This should be never present, as it gets automatically loaded.
# Load "bitmap" # Should be never present, as it gets automatically loaded. This is a font module, and loading it in xorg.conf makes X try to load it twice.
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
VendorName "PHL"
ModelName "PHLc014"
HorizSync 30 - 83
VertRefresh 55 - 75
EndSection
Section "Device"
Option "sw_cursor"
Identifier "Card0" Driver "vesa"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth 24
Modes "1440x900" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1440x900" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Besides, i have tried the Knoppix LiveCD and it's not getting that resolution either. Could be the driver? Any suggestion is greatly appreciated. Thanks in advance...
Last edited by enr1x (2010-01-08 19:29:15)

Yes, it was the driver. Solved

[Solved] Inconsistency in device naming concerning mount/fstab

This is not a problem that needs to be solved, but rather a gap in my understanding of a mechanism.
I have several partitions mounted in my fstab, they are identified by UUID.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump><pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
UUID=0767c51a-0ba8-405e-ac98-106182fe4d83 /tmp ext4 noexec,rw,noatime,nodiratime 0 2
UUID=0ba14b78-1b36-4857-92ae-8b1ca41264b6 /boot ext2 defaults 0 1
UUID=4eb07abb-25b0-4683-badf-8d556b536d9c / ext4 defaults 0 1
UUID=e3fe5429-379b-4b6d-a01e-e30aa85784e2 /home ext4 defaults 0 1
UUID=e7fda340-ca00-4c4c-b42e-cfba13a3abbe swap swap defaults 0 0
UUID=e3ae11a4-b602-4ea2-bbf7-8c8c9dea52a6 /mnt/Esther ext4 defaults,rw,noatime,nodiratime 0 2
UUID=55525a1b-386b-4390-8f47-b078b0b2c06e /mnt/Ballamb ext4 defaults,rw,noatime,nodiratime 0 2
UUID=b71cfb8d-a4eb-4ded-a65b-fbc2db102332 /mnt/Galbadia ext4 defaults,rw,noatime,nodiratime 0 2
When all drives are mounted, they show up as mounted by device name (/dev/sd*), only / is displayed as mounted by UUID.
$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=386283,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdc2 on /tmp type ext4 (rw,noexec,noatime,nodiratime)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext4 (rw)
/dev/sdb1 on /mnt/Esther type ext4 (rw,noatime,nodiratime)
/dev/sdc1 on /mnt/Ballamb type ext4 (rw,noatime,nodiratime)
/dev/sdd1 on /mnt/Galbadia type ext4 (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/xy/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=xy)
$ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
udev 10M 0 10M 0% /dev
run 10M 192K 9,9M 2% /run
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c 68G 8,5G 56G 14% /
shm 1,5G 4,0K 1,5G 1% /dev/shm
/dev/sdc2 289G 194M 274G 1% /tmp
/dev/sda1 251M 17M 222M 7% /boot
/dev/sda4 849G 62G 745G 8% /home
/dev/sdb1 1,8T 1,5T 223G 88% /mnt/Esther
/dev/sdc1 1,1T 223G 810G 22% /mnt/Ballamb
/dev/sdd1 1,8T 390G 1,4T 23% /mnt/Galbadia
Now I feel the urge to know why. Neither the mount nor the fstab manfile gave me insight on this one. So, what's behind this?
Last edited by Awebb (2011-10-08 17:51:26)

Now I feel stupid for not searching properly. Solved. Thanks, karol.
EDIT: So, in other words, if the UUID is passed by Grub, it shows as UUID in the system,
http://projects.archlinux.org/mkinitcpi … 3afd7e0001
So it was solved about a year ago? Well...
Last edited by Awebb (2011-05-29 14:12:06)

[SOLVED] install i686 on USB key from x86_64 : how ?

Hi.
As written in the title, I'm trying to install an Arch system on an usb stick, with i686 architecture, from the Arch x86_64 system on my computer.
I would like to do it without copying the iso to an extra usb key.
From the wiki : "If you are already running Arch, simply install arch-install-scripts and proceed with the installation guide just like you would from the iso, [...]"
1) I'm not sure about what it means : can I actually do the install using arch-install-script, without using the iso or the bootstrap image ? Is that correct ?? (english is not my native language).
2) Anyway, it didn't work. So I downloaded the bootstrap(s) image(s).
Tried the i686 one, then the x86_64 one.
For each, I changed the architecture in pacman.conf from "architecture = auto" to "architecture = i686".
[~/tmp] tar xzf ~/downloads/archlinux-bootstrap-2015.03.01-x86_64.tar.gz
[~/tmp] vi root.x86_64/etc/pacman.conf
[~/tmp] vi root.x86_64/etc/pacman.d/mirrorlist
[~/tmp] sudo root.x86_64/bin/arch-chroot root.x86_64/
sh-4.3#
sh-4.3# pacman-key --init
sh-4.3# pacman-key --populate archlinux
sh-4.3# lsblk
sh-4.3# mount /dev/sdc2 /mnt
sh-4.3# pacstrap -c /mnt base base-devel
(I tried with and without the -c option)
will give :
==> Creating install root at /mnt
==> Installing packages to /mnt
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: There are 50 members in group base:
:: There are 25 members in group base-devel:
warning: skipping target: file
warning: skipping target: findutils
warning: skipping target: gawk
warning: skipping target: gettext
warning: skipping target: grep
warning: skipping target: gzip
warning: skipping target: pacman
warning: skipping target: sed
warning: skipping target: texinfo
warning: skipping target: util-linux
warning: skipping target: which
error: failed to prepare transaction (package architecture is not valid)
:: package bash-4.3.033-1-x86_64 does not have a valid architecture
:: package bzip2-1.0.6-5-x86_64 does not have a valid architecture
[same message with coreutils-8.23-1-x86_64 cryptsetup-1.6.6-1-x86_64
and more than 50 other packages, up to sudo-1.8.12-1-x86_64]
Same with the i686 bootstrap image :
[~/tmp] tar xzf ~/downloads/archlinux-bootstrap-2015.03.01-i686.tar.gz
[~/tmp] sudo cp /etc/pacman.d/mirrorlist root.i686/etc/pacman.d/mirrorlist
[~/tmp]♭ sudo root.i686/bin/arch-chroot root.i686/
sh-4.3# pacman-key --init
sh-4.3# pacman-key --populate archlinux
sh-4.3# lsblk
sh-4.3# mount /dev/sdc2 /mnt
sh-4.3# pacstrap /mnt base base-devel
error: failed to prepare transaction (package architecture is not valid)
:: package bash-4.3.033-1-x86_64 does not have a valid architecture
Thanks.
Last edited by Tétrapyle (2015-03-23 21:27:30)

Thanks for your reply. I just updated the whole system.
Then
[~]$ sudo mount /dev/sdc2 /mnt
[~]$ sudo vi /etc/pacman.conf
My system is x86_64. I'm trying to install from that an i686 system.
If I run pacstrap now, it'll run ok but obviously it'll install an x86_64 system.
So, in pacman.conf, I changed Architecture from auto to i686 and I commented out the Multilib lines.
It seems it's not enough.
[~]$ sudo pacstrap -c /mnt
error: failed to prepare transaction (package architecture is not valid)
:: package bash-4.3.033-1-x86_64 does not have a valid architecture
:: package bzip2-1.0.6-5-x86_64 does not have a valid architecture
:: package coreutils-8.23-1-x86_64 does not have a valid architecture
:: package cryptsetup-1.6.6-1-x86_64 does not have a valid architecture
:: package device-mapper-2.02.116-1-x86_64 does not have a valid architecture
:: package dhcpcd-6.7.1-1-x86_64 does not have a valid architecture
:: package pkg-config-0.28-2-x86_64 does not have a valid architecture
:: package sudo-1.8.12-1-x86_64 does not have a valid architecture
==> ERROR: Failed to install packages to new root
Where do these x86_64 come from ? Could it be they stand for the $arch in the Server line from /etc/pacman.d/mirrorlist ?

[solved] Sound in flash stopped working (alsa, x86_64, rate)

Why?
Sound in flash stopped working (alsa, firefox, x86_64). Tried flashplugin-prerelease from archlinuxfr: nothing different.
Everything worked before I rebooted. I changed nothing else since last reboot. Can't figure out what happened.
Updates among other things:
firefox, xulrunner (firefox I did restart - the new one had sound in flash before I rebooted)
openal, lib32openal (don't think that has anything to do with it?)
libsndfile (that's something entirely different, too, right?)
And a lot of others that don't look related... no Idea how many really, I haven't rebooted in quite a while. Maybe there even was a kernel update since last reboot. Or two.
edit: Also some interactive flash stuff that did work before has stopped working now.
edit2: Chromium doesn't have sound in flash either. Tried recompiling firefox / switching to AUR/firefox-pgo: no change. Everywhere else, sound is working fine. Also, several flash games I tried get stuck / freeze after intro.
Thx!
Last edited by whoops (2011-03-25 07:31:43)

Couldn't find any changes there:
I LC_ALL=C aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
I tried the multilib version and the x86_64 prerelease. Both did work perfectly fine before I rebooted (I tried which one works better recently and couldn't see any real difference). Didn't have trouble with flash for months before this reboot.
I found a few modules I was unfamilliar with were loaded:
snd_seq_os snd_seq_dummy snd_seq_midi_event snd_seq snd_seq_device
... and removed them with rmmod. No change. (I should have restarted alsa at that point I guess just to make sure, those weren't the problem?)
Then I changed the rate in asound.conf to 41000 and restarted alsa - now everything works again! Strangely, no more freezes too (those were reliable).
I remember having had problems with flash not having sound unless I set the rate to 41000 about a year ago. After some updates, I tried again and all rates supported by my sound-card seemed to work. My guess would be regression in whatever fixed that problem... but I don't know.
I'll leave that "unsolved" until I manage to figure out what it really was about.
Last edited by whoops (2011-03-24 22:17:11)

[SOLVED] ruby-panelapplet2 won't compile (i686 & x86_64)

Hi!
I already wrote forum post in 64 bit section, but today I got to i686 machine and the error is the same, that damned package won't compile
Can anyone help getting this compiled? Any hints?
Errors are as follows:
Package 'glipper' has no Name: field
checking for GCC... yes
checking for rb_define_alloc_func() in ruby.h... yes
checking for rb_block_proc() in ruby.h... yes
checking for new allocation framework... yes
checking for attribute assignment... no
checking for libpanelapplet-2.0 version (>= 2.6.0)... yes
checking for G_PLATFORM_WIN32... no
creating rbpanelappletversion.h
creating Makefile
creating Makefile
/tmp/yaourt-tmp-user/aur-ruby-panelapplet2/ruby-panelapplet2/src/ruby-gnome2-all-0.19.1/glib/src/lib/pkg-config.rb:85:in `name': undefined method `[]' for nil:NilClass (NoMethodError)
from /tmp/yaourt-tmp-user/aur-ruby-panelapplet2/ruby-panelapplet2/src/ruby-gnome2-all-0.19.1/glib/src/lib/mkmf-gnome2.rb:165:in `create_pkg_config_file'
from /tmp/yaourt-tmp-user/aur-ruby-panelapplet2/ruby-panelapplet2/src/ruby-gnome2-all-0.19.1/panel-applet/extconf.rb:30:in `<main>'
extconf.rb: Leaving directory 'panel-applet'
That is driving me crazy, coz I can't get SSHMenu work properly and that is one of the tools I use all the time
If someone has that package in x86_64, please send that to me (edzis123[@]inbox.lv). Please remove all numbers and brackets from there
If the package is not available, alternate way is sending the files in the package, I suppose these should be like this (I took sample from i686):
/usr/lib/ruby/site_ruby/1.9.1/panelapplet2.rb
/usr/lib/ruby/site_ruby/1.9.1/x86_64-linux/panelapplet2_main.so
/usr/lib/ruby/site_ruby/1.9.1/x86_64-linux/panelapplet2.so
Thanx in advance.
Last edited by Kirurgs (2010-02-21 21:32:26)

Hi!
After spending quite a lot of time on this, I found the error why I couldn't compile almost any of ruby packages including ruby-gnomepanel2.
To my big surprise, pacman -R glipper fixed the issue and I'm now using sshmenu w/o any issues.
Ruby seems to broke if some additional (possibly incorrect) packages are installed, which it shouldn't!! Uff...
regards
Kirurgs
Last edited by Kirurgs (2010-02-21 21:32:57)

[solved]Cannot detect SD card after update

Hello all,
I frequently mount an SD card using:
$ sudo mount -t vfat -o uid=me,gid=users /dev/sdd1 /media/SD
However, after my latest pacman -Syu, my SD card isn't being detected by fdisk -l.
I tried hooking up an external USB SD card reader, but the result was exactly the same.
I'm terribly sorry that I don't have any idea what broke it (udisks perhaps?)
I'm using 2.6.33-ARCH, and Openbox. The SD card is a Kingston 4 GB SD HC that has always worked in the past and can still be detected on my uIEC/SD device.
Does anybody know how I can fix this?
EDIT: Today's update seems to have fixed the problem (ntfs-3g perhaps?).
Last edited by neilward (2010-04-12 00:44:42)

Hello all,
I frequently mount an SD card using:
$ sudo mount -t vfat -o uid=me,gid=users /dev/sdd1 /media/SD
However, after my latest pacman -Syu, my SD card isn't being detected by fdisk -l.
I tried hooking up an external USB SD card reader, but the result was exactly the same.
I'm terribly sorry that I don't have any idea what broke it (udisks perhaps?)
I'm using 2.6.33-ARCH, and Openbox. The SD card is a Kingston 4 GB SD HC that has always worked in the past and can still be detected on my uIEC/SD device.
Does anybody know how I can fix this?
EDIT: Today's update seems to have fixed the problem (ntfs-3g perhaps?).
Last edited by neilward (2010-04-12 00:44:42)

[SOLVED] Inconsistency within Documentation?

I have ran into a problem at the last part of installation - https://wiki.archlinux.org/index.php/Beginners%27_Guide
For partitioning I chose GPT
cgdisk /dev/sda
sda1 - root
sda2 - home
mkfs.ext4 /dev/sda1
mkfs.ext4 /dev/sda2
mount /dev/sda1 /mnt
mount /dev/sda2 /mnt/home
reached here with no further problems
pacman -S gptfdisk
pacman -S syslinux
syslinux-install_update -ia
All fine up until here
pacman -S gummiboot
gummiboot install
File system /boot is not a FAT EFI System Partition (ESP) file system
:: Run /usr/bin/gummiboot install to make gummiboot your default bootloader
When the guide told me to mkfs.ext4, is this the cause of the conflict (not a FT EFI System Partition?
Thanks in advance.
Last edited by Jimbo (2014-09-14 13:34:24)

You can decide into how many partitions the disk should be split, and for which directory each partition should be used in the system. The mapping from partitions to directories (frequently called 'mount points') is the Partition scheme. The simplest, and not a bad choice, is to make just one huge / partition. Another popular choice is to have a / and a /home partition.
Additional required partitions:
If you have a UEFI motherboard, you will need to create an extra EFI System Partition.
If you have a BIOS motherboard (or plan on booting in BIOS compatibility mode) and you want to setup GRUB on a GPT-partitioned drive, you will need to create an extra BIOS Boot Partition of size 1 or 2 MiB and EF02 type code. Syslinux does not need one.
If you have a requirement for a Disk encryption of the system itself, this must be reflected in your partition scheme. It is unproblematic to add encrypted folders, containers or home directories after the system is installed.
Then the following section is labeled as an example. It could perhaps be more clear, but it is not inconsistent.

[Solved] Inconsistency detected by ld.so: ../sysdeps/x86_64/...

Similar Messages

Maybe you are looking for