under /var/log are also the old logs from the last start e.g. Xorg.0.log.old
If you has a second computer you can connect with ssh to the other and look whats going on.
Announcement
Collapse
No announcement yet.
AMD Releases UVD Video Decode Support For R600 GPUs
Collapse
X
-
Originally posted by Nille View PostCan you look at the logs?
About the udev error, I can't see anything on dmesg (booting with ro 3)
This is the dmesg with the radeon module loaded
And this is the original one
How can I collect better logs?
Leave a comment:
-
Originally posted by CGarces View PostI have added the "radeon" module to /etc/modules and now X server start correctly, but the system not works.
After enter on graphic mode keyboard and mouse not respond (on console before startx works ok) .
Leave a comment:
-
Originally posted by droste View PostThe "radeon" kernel module seems to be missing in your 3.18 kernel.
After enter on graphic mode keyboard and mouse not respond (on console before startx works ok) .
The 1? error that I see during boot is "udev requires hotplug support not started" but I'm not sure is is related or not. The same error not happens with 3.14
The Debian Kernel is from experimental, not unstable. I'll keep trying to run it, but maybe I need to wait for a unstable version of 3.18
Leave a comment:
-
Originally posted by CGarces View Post[...]
The system works OK with the mesa update and my current kernel (3.14) but not enter into X with 3.18
[...]
Any help?
This command:
Code:dmesg | grep -E "drm|radeon"
[...]
[ 5.235010] [drm] Initialized drm 1.1.0 20060810
[ 5.242091] [drm] radeon kernel modesetting enabled.
[...]
[ 6.320494] [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 0
[...]
Leave a comment:
-
I'm trying to test the uvd support, using Debian.
Last version of Mesa 3D from testing (10.3.2) + kernel 3.18 from sid
The system works OK with the mesa update and my current kernel (3.14) but not enter into X with 3.18
I have the Xorg log and dmesg
The error that I see in the logs is:
[ 15.651] (II) [KMS] drm report modesetting isn't supported.
[ 15.651] (EE) Screen 0 deleted because of no matching config section.
[ 15.651] (II) UnloadModule: "radeon"
[ 15.651] (EE) Device(s) detected, but none match those in the config file.
But I have no idea about how fix it.
Any help?
Leave a comment:
-
Leave a comment:
-
Originally posted by pali View PostAh this naming problem.... Somebody should write names in total order ;-) to make everything clear.
And there is also group naming like NI, SI, CIK, etc. to raise confusion , but it is perfectly clear when you know it
Leave a comment:
Leave a comment: