You are not logged in.
depmod -a
ok... that worked. But why did i have to type that? why can't this be in the .install file?
and that's still not an answer. At all. If the normal install method were to compile the kernel module when pacman or kminstall or whatever installed it; then we wouldn't need all these different kernel modules for different kernels, which would be easier for the packager and very beneficial for the user who happens to use a custom kernel. What real disadvantages does this pose? anyone? all i see are advantages for everyone.
KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein
Offline
ok... that worked. But why did i have to type that? why can't this be in the .install file?
There's a typo in the install files - it says depmod -A instead of depmod -a.
very beneficial for the user who happens to use a custom kernel. What real disadvantages does this pose? anyone? all i see are advantages for everyone.
1) If you run more than one kernel, then you're going to have to install multiple kernel-driver packages anyway. May as well build packages for the kernels we officially package, and count on those who make custom kernels to be bright enough to make the small changes necessary to the PKGBUILDs to make custom modules for their custom kernels.
2) If you build the module in the .install, then pacman does not know about this file. You would have to go to a bit of trouble to remove the kernel modules installed in this way afterward when running pacman -R kernel_module_pkg. When the package contains nothing BUT a kernel module, this really kinda defeats the purpose of having a package in the first place.
3) We try to do as little post-install as possible - that's just a general policy for building packages. If it can be done at build time, do it at build time.
Offline
@iphitus can you please remove kernel26archck and mkinitramfs from testing, kernel archck is still version 5 and pacman not detecing version 6 coz testing is before extra in pacman.conf, same for mkinitramfs, so i suggest removing both from testing since it's in extra now
Thx
Hmm, just a friendly reminder..
Some PKGBUILDs: http://members.lycos.co.uk/sweiss3
Offline
pm me next time. ill get that outta testing today
Offline
I'm receiving the following error in every boot with the new archck kernel:
umount: /initrd: No such file or directory
umount: /initrd: No such file or directory
Although the pc boots completely I'm curious why this is happening.
Offline
Yup, i know about it.
Offline
I'm receiving the following error in every boot with the new archck kernel:
umount: /initrd: No such file or directory
umount: /initrd: No such file or directoryAlthough the pc boots completely I'm curious why this is happening.
Me too. It's really strange.
Arch - It's something refreshing
Offline
I'm having problems with ipw2200 also, running depmod -a seems to kinda work but then when I try doing anything with the wireless card, it seems to stop responding and I have to restart.
edit: Seems like I had to delete the modules directory, reinstall the kernel package, remove the kernel modules for ieee80211 and ipw2200, then reinstall ieee80211 and ipw2200. Seems to work now...
Offline
I'm having some problems getting this to work.
I did pacman -S ati-drivers and it gave me this:
:: ati-drivers conflicts with ati-fglrx-utils. Remove ati-fglrx-utils? [Y/n]
So I've installed fglrx from source.
I've ran aticonfig and my xorg.conf has changed to this:
Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
It had asked me to add fglrx to the MODULES part to the rc.conf file, which I did, however after a reboot, it complained about the fglrx module being missing.
My Xorg.0.log reports this:
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xf0000000 FBMappedSize: 0x04000000
(==) fglrx(0): Write-combining range (0xf0000000,0x4000000)
And here's what fglrxinfo is reporting:
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.2)
Also, my menu.lst line has this:
initrd /boot/initrd26.img instead of initrd /boot/initramfs-2.6.15-archck.img, because the latter gave me a bunch of errors and wouldn't start up Arch Linux. I'm not sure if the initrd part has anything to do with my ATI driver/module problem.
Xorg 7.0 runs fine so, but it's not 3D accelerated.
Anyone wants to take a stab at it?
This signature just crossed the line.
Offline
I'm having some problems getting this to work.
I did pacman -S ati-drivers and it gave me this:
:: ati-drivers conflicts with ati-fglrx-utils. Remove ati-fglrx-utils? [Y/n]
So I've installed fglrx from source.
If you're using stock kernel, then you want the ati-fglrx and ati-fglrx-utils packages.
You do not want ati-drivers - it's old. Check the versions. They conflict because they're the same app, but ati-fglrx is newer.
After you 'installed from source', did you run depmod -a? That might be why the kernel module is not being found.
Offline
If you're using stock kernel, then you want the ati-fglrx and ati-fglrx-utils packages.
You do not want ati-drivers - it's old. Check the versions. They conflict because they're the same app, but ati-fglrx is newer.
After you 'installed from source', did you run depmod -a? That might be why the kernel module is not being found.
Here's my kernel:
2.6.15-ARCH
Here's what's reported when I installed fglrx from source:
tar xfvz ati-fglrx-8.23.7-2.pkg.tar.gz
.PKGINFO
.FILELIST
.INSTALL
lib/
lib/modules/
lib/modules/2.6.15-archck/
lib/modules/2.6.15-archck/video/
lib/modules/2.6.15-archck/video/fglrx.ko
Yes, I've ran depmod -a afferword, still no luck.
This signature just crossed the line.
Offline
That's bizarre... are you sure you used the right kernel module package? That one looks like it was built for the archck kernel instead of the stock arch kernel...
Offline
I've changed my kernel to 2.6.15-archck and loaded up initramfs-2.6.15-archck.img properly. The boot process still complains about the missing fglrx module in rc.conf. glxgears seems to be improving, although it's not going blazingly fast. Thanks for helping me, Cerebral, you're leading me to the right track.
EDIT:
fglrxinfo now reports:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 8500 DDR Generic
OpenGL version string: 1.3.1050 (X4.3.0-8.23.7)
EDIT2: Despite the complaint with rc.conf, GL screensavers in xscreensaver works fine.
This signature just crossed the line.
Offline
check to see if /lib/modules/2.6.15-archck/video/fglrx.ko exists. If not, pacman -S ati-fglrx-archck then check again.
What do you get with
glxinfo | grep direct
(if you don't have glxinfo on your system, install mesa-apps with pacman)
Offline
check to see if /lib/modules/2.6.15-archck/video/fglrx.ko exists. If not, pacman -S ati-fglrx-archck then check again.
What do you get with
glxinfo | grep direct
(if you don't have glxinfo on your system, install mesa-apps with pacman)
Here's what I got:
direct rendering: Yes
This signature just crossed the line.
Offline
just a note:
Im not sure if you read any of this thread whatsoever, which dissappoints me, the whole point of it was to tell people about the change in the package name.
pacman -S ati-drivers
is not the correct way to install from the repos, as was the whole point of this thread to inform. I stated the new names in this thread, thus:
pacman -S ati-fglrx
is the correct way to install from the repositories.
If you have direct rendering, please re-check your latest X log, upload it to a pastebin (not this thread) if it still has errors. Also check lsmod, fglrx may well already be loaded anyway. If it isnt loaded, but you are getting direct rendering, your system is using the open source drivers,
iphitus
Offline
RaLX wrote:I'm receiving the following error in every boot with the new archck kernel:
umount: /initrd: No such file or directory
umount: /initrd: No such file or directoryAlthough the pc boots completely I'm curious why this is happening.
Me too. It's really strange.
I get this too. Is there any idea on what causes this?
Offline
whargoul wrote:RaLX wrote:I'm receiving the following error in every boot with the new archck kernel:
umount: /initrd: No such file or directory
umount: /initrd: No such file or directoryAlthough the pc boots completely I'm curious why this is happening.
Me too. It's really strange.
I get this too. Is there any idea on what causes this?
I've already said, I know about this issue. Its nothing to worry about. I'll deal with it eventually.
Offline
Well, there we go, that's your problem. The module doesn't exist.
Why do you need to use the old version of the drivers? Try installing:
pacman -S ati-fglrx ati-fglrx-utils
Make sure you remove the old ati-drivers packages first. Since you used the graphical installer, you might need to force (pacman -Sf) the installation.
Also, see this topic (and maybe start replying there instead of here): http://bbs.archlinux.org/viewtopic.php?t=19504
Finally: Paging all forum moderators! Could this thread get closed? It's old and the information within is inaccurate; just serves to confuse the users.
I've forget to mention that I'm not using the stock kernel
so I can't use these packages...
Offline
noise: As root, run abs. Then you can go into /var/abs/extra/modules/ati-fglrx/ and change the PKGBUILD to make a kernel module for the kernel you do use. Then just install ati-fglrx-utils from the repos, and your custom kernel-module package.
Note: the ati-fglrx-utils package is kernel-independent and does not need to be changed.
( note for those confused, noise came from the old "ati-drivers in testing" thread here: http://bbs.archlinux.org/viewtopic.php?t=18944&start=90 )
Offline
ok, now it works
thanks for your patience
Offline
Thanks for the great kernel package. I've noticed that the darch splash image does not load until after the udev deamon has been started (like it would normally be shown in the console). Once this occurs the console is dropped and the silent image begins to progress. Is this a normal behavior?
/path/to/Truth
Offline
Awesome packaging work guys; any idea why I get this error when I run fglrxinfo though?
ERROR: version mismatch - 2D module [8.23.7] incompatible with OGL client module [8.20.
8].
libGL error: InitDriver failed
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.2)
I'm using a custom kernel, but I definitely have everything in there that I need for the ati-drivers to work, because I had them working before installing this package. I adjusted the PKGBUILD for ati-fglrx in the abs tree accordingly, and I installed ati-fglrx-utils too.
I did a system upgrade before installing the packages, so nothing's out of date.
Any ideas?
.oO Komodo Dave Oo.
Offline
Komodo, sounds like you have one version of one file (possibly /usr/lib/libGL.so) and another version of the other files.
Make sure everything's installed to the correct locations, and everything's installed using the same version of the installer from ATI. If everything seems like it should be uptodate, remove ati-fglrx-utils from your system, make sure nothing exists in /usr/X11R6, do a locate for "libGL.so" or maybe some other libs installed by ati-fglrx-utils and make sure no extra libs are loitering around on your system, then reinstall ati-fglrx-utils.
http://arch.pastebin.com/634264 <-- there's a list of all the files installed by the package, incase you want to use it to look for stray files existing somewhere else on your filesystem.
Offline
Cheers for that link Cerebral, very useful. I've had a quick look around to see what needs symlinking, but I'll take a more detailed tour of /usr/lib later.
.oO Komodo Dave Oo.
Offline