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 danicamp...@gmail.com:
Try to uninstall/disable splashutils.
On Mon, Aug 13, 2012 at 9:04 PM, Fabio Erculiani lx...@sabayon.org wrote:
Are you
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 joost.r...@sabayonlinux.org:
Remove the vga=773 parameter?
On Mon, Aug 13, 2012 at 9:59 PM, Danilo Pianini
danilo.pian...@gmail.com wrote:
I have not such
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.
--
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
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
Try to uninstall/disable splashutils.
On Mon, Aug 13, 2012 at 9:04 PM, Fabio Erculiani lx...@sabayon.org 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
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
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 danilo.pian...@gmail.com
I confirm that
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
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
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
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
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
2012/7/30 Fabio Erculiani lx...@sabayon.org:
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
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 if
Please do not use HTML in your emails.
About the * WARNING : xdm has already been started warning...
well... just restart it, no?
--
Fabio Erculiani
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 sabayon...@gmail.com:
Ooooh...
At prompt
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,
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
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
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 the
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
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
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) first mail
New download (same ISO) the X-server doesn' start as reported
2012/7/28 Fabio Erculiani lx...@sabayon.org:
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
On Sat, Jul 28, 2012 at 6:34 PM, Danilo Pianini
danilo.pian...@gmail.com wrote:
2012/7/28 Fabio Erculiani lx...@sabayon.org:
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
The issue looks like this:
https://bugs.freedesktop.org/show_bug.cgi?id=25607
--
Fabio Erculiani
Definitely. It's there since three years :|
2012/7/28 Fabio Erculiani lx...@sabayon.org:
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:
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
2012/7/28 Fabio Erculiani lx...@sabayon.org:
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
30 matches
Mail list logo
