On my Radeon HD 5450 S10 KDE works as expected.
--
Fabio Erculiani
Yes Daniele, it works. By the way I tested with the very latest
dailies, and they fail on every HD4 hardware I tested.
2012/8/13 Daniele Campana :
> Try to uninstall/disable splashutils.
>
>
> On Mon, Aug 13, 2012 at 9:04 PM, Fabio Erculiani wrote:
>>
>> Are you sure this is not related to "v
IT WORKS with vga=773. It does not with the default (vga=791) - unless
the user promptly presses F2 during the boot.
2012/8/14 Joost Ruis :
> Remove the vga=773 parameter?
>
> On Mon, Aug 13, 2012 at 9:59 PM, Danilo Pianini
> wrote:
>> I have not such parameter.
>>
>> desktopcesena danysk # cat /
Remove the vga=773 parameter?
On Mon, Aug 13, 2012 at 9:59 PM, Danilo Pianini
wrote:
> I have not such parameter.
>
> desktopcesena danysk # cat /proc/cmdline
> BOOT_IMAGE=/kernel-genkernel-x86_64-3.5.0-sabayon ro init=/linuxrc
> vga=773 console=tty1 dokeymap keymap=it
> resume=swap:/dev/mapper/v
I have not such parameter.
desktopcesena danysk # cat /proc/cmdline
BOOT_IMAGE=/kernel-genkernel-x86_64-3.5.0-sabayon ro init=/linuxrc
vga=773 console=tty1 dokeymap keymap=it
resume=swap:/dev/mapper/vg_desktopcesena-lv_swap
real_resume=/dev/mapper/vg_desktopcesena-lv_swap dolvm
root=/dev/mapper/vg
Try to uninstall/disable splashutils.
On Mon, Aug 13, 2012 at 9:04 PM, Fabio Erculiani wrote:
> Are you sure this is not related to "video=vesafb:ywrap,mtrr:3" ?
> Can you try to remove this parameter from the boot command line?
>
> --
> Fabio Erculiani
>
>
Are you sure this is not related to "video=vesafb:ywrap,mtrr:3" ?
Can you try to remove this parameter from the boot command line?
--
Fabio Erculiani
Have you tried with an HD4xxx series hardware? I guess those cards are
the only affected. I only have this 4870 with me, but another user had
the same issue with a 4250. I found a workaround, btw: booting with
vga=773 works for me. It seems those cards have some sort of problem
switching from 1024x
I have bought a cheapo Radeon HD5450 (which is both supported by fglrx
and radeon) and I tried to boot the latest amd64G DAILY ISO image
(forcing the OSS drivers with the "noproprietary" boot flag).
All good here on this hardware, GNOME Shell works, XBMC works, KMS is
automatically enabled.
--
F
That's weird: if I promptly press F2 during the boot, the booting
process is fine (no GPU loockup).
Any idea on what might cause this thing?
2012/8/1 Danilo Pianini :
> 2012/8/1 Daniele Campana
>>
>> Have you tried changing virtual terminal after the module loads?
>
>
>
> Yep, no way. Screen is c
2012/8/1 Daniele Campana
> Have you tried changing virtual terminal after the module loads?
>
Yep, no way. Screen is corrupted till the boot phase. As Fabio spotted, I
have a GPU lookup, so there's something with this radeon driver and my GPU.
I'll try to recompile them and see.
--
Ing. Dott.
GPU lockup (waiting for 0x0004 last fence id 0x0001)
Read your own logs. There is a problem with your GPU and the radeon
kernel module apparently, this does not invalidate the solution.
--
Fabio Erculiani
Have you tried changing virtual terminal after the module loads?
I'm also experiencing the "black screen" while booting, but it's simply
because when the module loads you are dropped into another vt (I can't
imagine why they do so).
You should be able to switch to tty1 where you can see the boot pr
Correction: the problem with OpenGL was something in my KWin config.
Putting KWin at default and re-enabling the effects worked. The problem
with the black screen still stands, but it is not worse than the previous
situation.
2012/8/1 Danilo Pianini
> I confirm that adding "radeon" to /etc/conf.
2012/7/30 Fabio Erculiani :
> I've been able to put my hands on Daniele's laptop and these are the results.
> Adding "radeon" to /etc/conf.d/modules fixes the issue for him, and
> I'm sure it does for everybody.
Any other particular setting? Which driver version did you use? This
hadn't worked for
I've been able to put my hands on Daniele's laptop and these are the results.
Adding "radeon" to /etc/conf.d/modules fixes the issue for him, and
I'm sure it does for everybody.
Given this, I could be able to implement a workaround to the mess they
(deliberately?) created.
gpu-detector is already
This would be bad for many many users :(
What about fglrx used with nomodeset forced? I will have a system with
HD6 series in a week and a half. Can somebody test something before?
What about a choice box on the installer? So we can equip the live dvd
with ati and install fglrx on demand during in
At this point, I am for removing ati-drivers (fglrx) from our Live
images and force radeon.modeset=1 by default.
This won't break current installations nor new ones. Users will be
able to install ati-drivers and switch to them more-or-less easily (I
can write a quick howto guide on the wiki, or you
2012/7/30 Fabio Erculiani :
> If this won't work, I would be forced to do some hackery in
> xf86-video-ati pkg_postinst() (I am thinking about detecting the
> absence of ati-drivers and then forcing radeon.modeset=1 into users'
> grub.cfg & grub.conf).
I'll try the patch ASAP. IMHO, a better check
The patched ebuild is this: xf86-video-ati-6.14.4-r1.ebuild
Please pay attention to emerge THIS version from the sabayon-distro
overlay and LOOK for:
* Applying xf86-video-ati-6.14.4-fix-kms-drm-detection-fdo-32981.patch
... [ ok ]
--
Fabio Erculiani
Danilo and others,
I pushed a patched ebuild for x11-drivers/xf86-video-ati to the
sabayon-distro overlay.
The patch is the one mentioned in fdo bug #32981.
Could you emerge it and see if it does any good?
It should *hopefully* address the chicken/egg issue we've seen so far.
If this won't work, I
What??
Look at your xorg and see if you are loading fglrx: I guess you are
not. I don't think AMD forgot to remove their support from the driver.
Moreover, look at dmesg and Xorg.0.log to realize which driver is
actually loaded.
2012/7/29 sabayonino :
> Ooooh...
>
> At prompt "eselect opengl list"
Ooooh...
At prompt "eselect opengl list" is set to xorg-x11
I tried to switch to "ati" and restart xdm ...
KDM starts !
I don't understand :|
ATI-RADEON HD 4570 + ati-drivers 12.6 O_O
Please do not use HTML in your emails.
About the "* WARNING : xdm has already been started" warning...
well... just restart it, no?
--
Fabio Erculiani
Il 28/07/2012 18:20, devel-requ...@lists.sabayon.org ha scritto:
Ok, got it.
sabayonino, does this happen only live and perhaps only after the
first boot once installed?
Can you test these three things separately?
1.
- Boot the Live image with "gentoo=nox"
- /etc/init.d/xdm start
- report i
@ Fabio : I will try your suggestions as soon as possible
@ Danilo : I tried "radeon.modeset=1" but without success.
OpenGL is set to xorg-x11
With Sabayon 64-Core and Radeon4.x series was fixed with last upgrade
(kernel,xorg-server and xf86-video-ati) but I have "xdm" set to
"default" runle
2012/7/28 Fabio Erculiani :
Note: the system in which I have a HD2-4xxx installed is a production
system: I cannot mess it up, and this will slow down my testing
process. Sabayonino: if you can help by testing, please do it :)
> Solution 1:
> Drop ati-drivers from Live images and force radeon.mod
Danilo, would you be able to test that patch (if it applies).
I don't see many solutions to this problem...
Solution 1:
Drop ati-drivers from Live images and force radeon.modeset=1 via cmdline
Solution 2:
Drop ati-drivers from Live images and enable CONFIG_DRM_RADEON_KMS by
default. Forcing ati-d
Definitely. It's there since three years :|
2012/7/28 Fabio Erculiani :
> The issue looks like this:
> https://bugs.freedesktop.org/show_bug.cgi?id=25607
>
> --
> Fabio Erculiani
>
--
Ing. Dott. Danilo Pianini
Site: http://www.danilopianini.org/
Phone: +39 320 41 36 573
Skype: dany.sk
2012/7/28 Fabio Erculiani :
> What do you mean with "messed up everything"? Can you elaborate?
Random colors flickering, no shell, no X. I had to remove it in order
to be able to boot correctly.
--
Ing. Dott. Danilo Pianini
Site: http://www.danilopianini.org/
Phone: +39 320 41 36 573
Skype: dan
The issue looks like this:
https://bugs.freedesktop.org/show_bug.cgi?id=25607
--
Fabio Erculiani
On Sat, Jul 28, 2012 at 6:34 PM, Danilo Pianini
wrote:
> 2012/7/28 Fabio Erculiani :
>> Also (Danilo),
>> is your radeon.ko loaded by udev or by X?
>> Just boot without X (and without radeon.modeset=1 in /proc/cmdline)
>> and see if radeon is loaded and kms is enabled (dmesg will tell you).
>
> re
2012/7/28 Fabio Erculiani :
> Also (Danilo),
> is your radeon.ko loaded by udev or by X?
> Just boot without X (and without radeon.modeset=1 in /proc/cmdline)
> and see if radeon is loaded and kms is enabled (dmesg will tell you).
removed xdm from boot runlevel
restarted (with radeon.modeset=1 in
2012/7/28 Fabio Erculiani :
> Danilo,
> have you tried to run "eselect opengl set xorg-x11"? Just wondering if
> it does any good.
I have not, but I guess gpu-configuration did it for me when I
switched. Do you want me to run it?
> radeon.ko is supposed to be loaded with modeset=1
> Do you have s
How comes, you did mention that everything was working great. What did
you test then?
-- Fabio Erculiani
Sorry Fabio.
Permissions problem was solved . I think my first downlowd was corrupted
(but md5 was ok)
New download (same ISO) the X-server doesn' start as reported previously.
I th
Also (Danilo),
is your radeon.ko loaded by udev or by X?
Just boot without X (and without radeon.modeset=1 in /proc/cmdline)
and see if radeon is loaded and kms is enabled (dmesg will tell you).
--
Fabio Erculiani
Danilo,
have you tried to run "eselect opengl set xorg-x11"? Just wondering if
it does any good.
radeon.ko is supposed to be loaded with modeset=1
Do you have something like this below:
"[drm] radeon kernel modesetting enabled." ?
--
Fabio Erculiani
Ok, got it.
sabayonino, does this happen only live and perhaps only after the
first boot once installed?
Can you test these three things separately?
1.
- Boot the Live image with "gentoo=nox"
- /etc/init.d/xdm start
- report if xdm starts.
2.
- Boot the Live image with "gentoo=nox"
- all on
I did, it worked. Then there was an upgrade for the kernel, I guess
that something has changed due to the KMS messing up fglrx. After that
problem was solved, a new issue appeared on the foss video driver - I
only experienced it after the weekly updates.
2012/7/28 Fabio Erculiani :
> How comes, yo
How comes, you did mention that everything was working great. What did
you test then?
--
Fabio Erculiani
Currently, our xf86-video-ati does not work correctly.
See http://bugs.sabayon.org/show_bug.cgi?id=3497
Restarting xdm should workaround the thing, however we seriously need
a fix (no pre-HD5xxx Radeon card works OOTB with Sabayon).
2012/7/27 sabayonino :
> Sabayon-K-64-daily (20120712)
>
> Ok.I
Hi
I'm trying last daily K-64 (20120725)
I can't startx
Drivers and OpenGL are set but rc.log show "sabayonuser" permissions wrong
(ATI HD-4570)
If i try to switch root-->sabayonuser I got :
"Could not determine user name" (Italian : Impossibile determinare il
proprio nome utente)
xdm or
42 matches
Mail list logo
