Hi! My problem with X after updating to 10.1 Alpha2 was not with fontconfig, but with the lack of the 'radeon' driver... Is this the correct place to find out what to do? jupiter:~ # rpm -qa | grep kernel kernel-smp-nongpl-2.6.14_rc5_git5-20051027163336 kernel-smp-2.6.14_rc5_git5-20051027163336 kernel-update-tool-0.9-13 jupiter:~ # -- Jorge Godoy <jgodoy@gmail.com>
Hi all ! Jorge Godoy schrieb:
My problem with X after updating to 10.1 Alpha2 was not with fontconfig, but with the lack of the 'radeon' driver... Is this the correct place to find out what to do?
jupiter:~ # rpm -qa | grep kernel kernel-smp-nongpl-2.6.14_rc5_git5-20051027163336 kernel-smp-2.6.14_rc5_git5-20051027163336 kernel-update-tool-0.9-13 jupiter:~ #
The "radeon" driver usually is contained in one of the Xorg-RPMs and is not shipped in a seperate RPM. And if it would be a kernel module and have its own RPM the RPM's name would start with "km_" ... That has been the case for former "fglrx" drivers (which had a seperate "km_fglrx" RPM for the kernel module. But that is history since a few weeks ... In an SUSE 10.0 environment you will find the driver as /usr/X11R6/lib/modules/drivers/radeon_drv.o and the DRI module is located in /usr/X11R6/lib/modules/dri/radeon_dri.so Hope this helps ! Never give up ! Best regards, Reinhard.
Reinhard Gimbel <opensuse@dragonfly7.de> writes:
Hi all !
Jorge Godoy schrieb:
My problem with X after updating to 10.1 Alpha2 was not with fontconfig, but with the lack of the 'radeon' driver... Is this the correct place to find out what to do? jupiter:~ # rpm -qa | grep kernel kernel-smp-nongpl-2.6.14_rc5_git5-20051027163336 kernel-smp-2.6.14_rc5_git5-20051027163336 kernel-update-tool-0.9-13 jupiter:~ #
The "radeon" driver usually is contained in one of the Xorg-RPMs and is not shipped in a seperate RPM. And if it would be a kernel module and have its own RPM the RPM's name would start with "km_" ...
How can I find which one? Neither YaST nor Apt return me a match for the radeon_drv.o file...
That has been the case for former "fglrx" drivers (which had a seperate "km_fglrx" RPM for the kernel module. But that is history since a few weeks ...
In an SUSE 10.0 environment you will find the driver as /usr/X11R6/lib/modules/drivers/radeon_drv.o and the DRI module is located in /usr/X11R6/lib/modules/dri/radeon_dri.so
Hope this helps !
I think there's more than just that. With my old setup I had: godoy@jupiter:~> locate radeon /lib/modules/2.6.13.2-2-smp/kernel/drivers/char/drm/radeon.ko /lib/modules/2.6.13.2-2-smp/kernel/drivers/video/aty/radeonfb.ko /usr/include/linux/radeonfb.h /usr/lib/directfb-0.9.22/gfxdrivers/libdirectfb_radeon.la /usr/lib/directfb-0.9.22/gfxdrivers/libdirectfb_radeon.so /usr/lib/perl5/vendor_perl/5.8.7/i586-linux-thread-multi/linux/radeonfb.ph /usr/lib/xine/plugins/1.1.0/vidix/radeon_vid.so /usr/share/sax/profile/radeon /usr/X11R6/lib/modules/dri/radeon_dri.so /usr/X11R6/lib/modules/drivers/radeon_drv.o godoy@jupiter:~> With the new setup, after my upgrade with YaST and the 5 CD set: godoy@jupiter:~> locate radeon /lib/modules/2.6.14-rc5-git5-20051027163336-smp/kernel/drivers/char/drm/radeon.ko /lib/modules/2.6.14-rc5-git5-20051027163336-smp/kernel/drivers/video/aty/radeonfb.ko /usr/include/linux/radeonfb.h /usr/lib/directfb-0.9.23/gfxdrivers/libdirectfb_radeon.la /usr/lib/directfb-0.9.23/gfxdrivers/libdirectfb_radeon.so /usr/lib/perl5/vendor_perl/5.8.7/i586-linux-thread-multi/linux/radeonfb.ph /usr/lib/xine/plugins/1.1.0/vidix/radeon_vid.so /usr/share/sax/profile/radeon /usr/X11R6/lib/modules/dri/radeon_dri.so godoy@jupiter:~> Is it possible that this is a packaging problem with xorg-x11-Mesa (this is the package that provides the radeon_dri.so file above)?
Never give up !
I can't. ;-) If I don't solve that, I'll have this crappy image on my notebook... :-) If I decide going back to the older kernel, I'd have problems with ACPI... I can choose either be fried or be toasted... :-) Thanks for your help, -- Jorge Godoy <jgodoy@gmail.com>
Hi all ! Jorge Godoy wrote: [...]
How can I find which one? Neither YaST nor Apt return me a match for the radeon_drv.o file...
[...]
In an SUSE 10.0 environment you will find the driver as /usr/X11R6/lib/modules/drivers/radeon_drv.o and the DRI module is located in /usr/X11R6/lib/modules/dri/radeon_dri.so
[...]
I think there's more than just that. With my old setup I had:
godoy@jupiter:~> locate radeon /lib/modules/2.6.13.2-2-smp/kernel/drivers/char/drm/radeon.ko /lib/modules/2.6.13.2-2-smp/kernel/drivers/video/aty/radeonfb.ko /usr/include/linux/radeonfb.h /usr/lib/directfb-0.9.22/gfxdrivers/libdirectfb_radeon.la /usr/lib/directfb-0.9.22/gfxdrivers/libdirectfb_radeon.so /usr/lib/perl5/vendor_perl/5.8.7/i586-linux-thread-multi/linux/radeonfb.ph /usr/lib/xine/plugins/1.1.0/vidix/radeon_vid.so /usr/share/sax/profile/radeon /usr/X11R6/lib/modules/dri/radeon_dri.so /usr/X11R6/lib/modules/drivers/radeon_drv.o godoy@jupiter:~>
With the new setup, after my upgrade with YaST and the 5 CD set:
godoy@jupiter:~> locate radeon /lib/modules/2.6.14-rc5-git5-20051027163336-smp/kernel/drivers/char/drm/radeon.ko /lib/modules/2.6.14-rc5-git5-20051027163336-smp/kernel/drivers/video/aty/radeonfb.ko /usr/include/linux/radeonfb.h /usr/lib/directfb-0.9.23/gfxdrivers/libdirectfb_radeon.la /usr/lib/directfb-0.9.23/gfxdrivers/libdirectfb_radeon.so /usr/lib/perl5/vendor_perl/5.8.7/i586-linux-thread-multi/linux/radeonfb.ph /usr/lib/xine/plugins/1.1.0/vidix/radeon_vid.so /usr/share/sax/profile/radeon /usr/X11R6/lib/modules/dri/radeon_dri.so godoy@jupiter:~>
O.k., the *main* driver "radeon_drv.o" file isn't there. That's for sure ...
Is it possible that this is a packaging problem with xorg-x11-Mesa (this is the package that provides the radeon_dri.so file above)?
No, I don't think so. It might be more a problem of xorg-x11-server. This RPM usually contains all the *_drv.o files.
I can't. ;-) If I don't solve that, I'll have this crappy image on my notebook... :-) If I decide going back to the older kernel, I'd have problems with ACPI...
BTW: Which version of (open)SUSE are you using ? Maybe I missed that ... Never give up ! Best regards, Reinhard.
Reinhard Gimbel <opensuse@dragonfly7.de> writes:
No, I don't think so. It might be more a problem of xorg-x11-server. This RPM usually contains all the *_drv.o files.
OK.
I can't. ;-) If I don't solve that, I'll have this crappy image on my notebook... :-) If I decide going back to the older kernel, I'd have problems with ACPI...
BTW: Which version of (open)SUSE are you using ? Maybe I missed that ...
10.1 Alpha2. My xorg-x11-server is at version 6.8.2-109. -- Jorge Godoy <jgodoy@gmail.com>
Hi all ! Jorge Godoy wrote:
Reinhard Gimbel <opensuse@dragonfly7.de> writes:
No, I don't think so. It might be more a problem of xorg-x11-server. This RPM usually contains all the *_drv.o files.
OK.
[...]
BTW: Which version of (open)SUSE are you using ? Maybe I missed that ...
10.1 Alpha2. My xorg-x11-server is at version 6.8.2-109.
With 10.0-GM it is 6.8.1-100.2 You might need to file a bug in bugzilla ... Never give up ! Best regards, Reinhard.
Hello, Am Freitag, 28. Oktober 2005 16:54 schrieb Jorge Godoy:
My problem with X after updating to 10.1 Alpha2 was not with fontconfig, but with the lack of the 'radeon' driver... Is this the correct place to find out what to do?
jupiter:~ # rpm -qa | grep kernel kernel-smp-nongpl-2.6.14_rc5_git5-20051027163336 kernel-smp-2.6.14_rc5_git5-20051027163336 kernel-update-tool-0.9-13
I guess you are talking about the radeon driver _for X_. If I'm correct, you should have a look at the xorg-x11-server package - at least in 10.0 the radeon driver is there ;-) Regards, Christian Boltz -- Das soll jetzt wirklich keine Arroganz sein, aber es macht keinen Sinn, das Haus abzureissen, weil du den Hausschlüssel vergessen hast. :-) [Ratti in suse-linux]
Am Freitag 28 Oktober 2005 16:54 schrieb Jorge Godoy <jgodoy@gmail.com>:
My problem with X after updating to 10.1 Alpha2 was not with fontconfig, but with the lack of the 'radeon' driver... Is this the correct place to find out what to do?
Hi Jorge, the radeon works quite well for me.
10.1 Alpha2. My xorg-x11-server is at version 6.8.2-109.
10.1 Alpha2 xorg-x11-server 6.8.2-107 I will update to 109 and see... -- mdc
Am Samstag 29 Oktober 2005 16:56 schrieb meister@netz00.com:
My problem with X after updating to 10.1 Alpha2 was not with fontconfig, but with the lack of the 'radeon' driver... Is this the correct place to find out what to do?
Am Freitag 28 Oktober 2005 16:54 schrieb Jorge Godoy <jgodoy@gmail.com>: the radeon works quite well for me.
10.1 Alpha2. My xorg-x11-server is at version 6.8.2-109. 10.1 Alpha2 xorg-x11-server 6.8.2-107 I will update to 109 and see...
Hi, the result: installation broken. I tried to update via YaST (update if newer version available), but lot's of packages YaST wanted to update was not available. Midway in the update the X-server died and also YaST, rendering the system in an unuseable state. So I deleted the partition: in the end all my tries to make Linux (SuSE 9.3,10.0,10.1a[12], Fedora4, Debian testing) work on my laptop failed. I think it is build for windows, it works with windows, so I will use windows on it. -- mdc
Hi ! meister@netz00.com schrieb:
the result: installation broken. I tried to update via YaST (update if newer version available), but lot's of packages YaST wanted to update was not available. Midway in the update the X-server died and also YaST, rendering the system in an unuseable state. So I deleted the partition: in the end all my tries to make Linux (SuSE 9.3,10.0,10.1a[12], Fedora4, Debian testing) work on my laptop failed. I think it is build for windows, it works with windows, so I will use windows on it.
Which kind of notebook you own ? In principal any of the distributions mentioned above should run on your notebook. Have you tried to run some test programs e.g. memory test application as shipped on SuSE medias ? Never give up ! Best regards, Reinhard.
meister@netz00.com writes:
Hi,
the result: installation broken. I tried to update via YaST (update if newer version available), but lot's of packages YaST wanted to update was not available. Midway in the update the X-server died and also YaST, rendering the system in an unuseable state. So I deleted the partition: in the end all my tries to make Linux (SuSE 9.3,10.0,10.1a[12], Fedora4, Debian testing) work on my laptop failed. I think it is build for windows, it works with windows, so I will use windows on it.
Same problem here this weekend. I went back to 10.0... :-( I'll give a try later, when I have less things from work. -- Jorge Godoy <jgodoy@gmail.com>
participants (4)
-
Christian Boltz -
Jorge Godoy -
meister＠netz00.com -
Reinhard Gimbel