"Input not supported"

[CJ Master]

I forgot to mention that this happens as soon as X starts, so are those boot parameters changing X?

[CJ Master]

Bump.

[ReemZ]

Your right, it is 1440x900. But it STILL DOESN'T WORK. I even tried safe mode. This is infuriating. I'm re-burning the image in case it burned wrong and that's why... but I doubt it.

Did you do an md5sum? http://wiki.sabayonlinux.org/index.php? ... or_LiveDVD

I don't have another computer to test it on, really.

Family? Mates? School/work? Library? Netpub?

Bump.

Patience, little grasshopper

[Fitzcarraldo]

Man, this is a toughie.

Try pressing F5 and deleting the

Code: Select all

quiet splash=silent,theme:sabayon vga=791

and adding

Code: Select all

nox acpi=off ide=nodma vga=normal noddc

I doubt it too. Here's another boot parameter you could try, both by itself and in combination with the earlier ones:

Code: Select all

acpi=off

No offense, but what would ACPI have to do with what Sabayon project on the screen.

In theory, nothing. However, ACPI in many BIOSs is buggy for Linux, and I though maybe, just maybe, it would help turning it off.

[Vitoriung]

Hi,
I had the same problem, I have monitor ACER AL1916W 1440x900 and card ATI 9600 PRO.
I realized that recent version of "fglrx" driver doesn't support my card anymore.
So it might be your case as well, depends on how old your ATI card is, in that case you need to use "radeon" driver instead.

In theory it should work like this:
Press CTRL-ALT-F1 - it get you to the console, where you can write the command:

Code: Select all

 lsmod | grep fglrx

You you see it's loaded first try to kill X session

Code: Select all

/etc/init.d/xdm stop

if you get error about kdm kill kdm process by

Code: Select all

ps aux | grep kdm
root      6865  0.0  0.0   3640   776 ?        Ss   02:35   0:00 /usr/kde/4.2/bin/kdm


read the pid(6865) and

Code: Select all

kill -9 6865
/etc/init.d/xdm stop

Unload and blacklist fglrx driver

Code: Select all

rmmod fglrx --force
echo "blacklist fglrx >> /etc/modprobe.d/blacklist

Edit your xorg.conf file and replace driver fglrx for radeon

Code: Select all

Section "Device"

    Identifier  "SabayonVga0"
    Driver      "radeon"


You might need to specify your monitor, this setting is for my AL1916:

Code: Select all

Section "Monitor"
    Identifier    "Generic Monitor"
    HorizSync    30.0 - 82.0
    VertRefresh  56.0 - 76.0
    Modeline "1440x900"  106.47  1440 1520 1672 1904  900 901 904 932  -HSync +Vsync
EndSection


Then you can try load the new driver

Code: Select all

modprobe radeon

and run X server

Code: Select all

/etc/init.d/xdm start

I was actually having problem here, because my computer froze completely
But I was successful on the end, because I run the text installation here and went above steps successfully after I booted installed system.

Hope it helps.

[Fitzcarraldo]

The package list in the Press Release for SL 4.1 KDE shows that release has the fglrx driver x11-drivers/ati-drivers-8.593-r11#2.6.29-sabayon, whereas the package list in the Press Release for SL 4.1 GNOME shows that release has the fglrx driver x11-drivers/ati-drivers-8.593-r10#2.6.29-sabayon

Now the -r11 ebuild in the Sabayon overlay uses the ATI Catalyst 9.3 driver from the AMD site but then applies a patch for the ATI Catalyst 9.4 driver which does not support older ATI GPUs. So the -r11 version on the SL 4.1 KDE LiveDVD is not the same version as distributed by AMD. However the -r10 ebuild does not do this. Note that my ATI GPU (Radeon Mobility X1600) is not supported by the Catalyst 9.4 driver but it works fine with the 8.593-r10 ebuild.

So, if you have been booting the SL 4.1 KDE LiveDVD and the GPU did not work, one thing that would be interesting to try would be to boot the SL 4.1 GNOME LiveDVD to see if that would work.

The release notes for the AMD 9.3 Catalyst driver explicitly state that it supports the ATI Radeon Xpress 200 Series, which is the GPU that the OP, CJ Master, is using. (The release notes for the AMD 9.4 Catalyst driver confirm that the ATI Radeon Xpress 200 Series is not supported.)

So either CJ Master is booting a SL 4.1 KDE LiveDVD with a possibly buggy flgrx driver from the Sabayon overlay, or he is booting a SL 4.1 GNOME LiveDVD with a non-buggy fglrx driver that is known to work with his GPU.

Now, in your case Vitoriung, you have an ATI 9600 Pro GPU. The release notes for the Catalyst 9.3 driver indicate that the 9600 Series is supported by that driver; the release notes for the Catalyst 9.4 driver indicate that the 9600 Series is not supported by that driver. So your situation should be the same as CJ Master's (and mine), namely that ati-drivers-8.593-r10 from the Sabayon overlay should work on your PC but ati-drivers-8.593-r11 would not. I notice from the output you pasted that you are using the KDE version of SL. It would be interesting to see what would happen if you booted the SL 4.1 GNOME LiveDVD or, alternatively, installed the correct AMD Catalyst 9.3 driver, i.e. ati-drivers-8.593-r10 rather than the ati-drivers-8.593-r11 that came with the SL 4.1 KDE LiveDVD. I reiterate that, like you, my GPU is also not supported by the Catalyst 9.4 driver; nevertheless it still works fine with the correct Catalyst 9.3 driver (ati-drivers-8.593-r10).

Of course, if you subsequently updated the ati-drivers to a higher version then that would not work because it is the Catalyst 9.4 driver or later.

[Vitoriung]

That's interesting what you said Fitzcarraldo, I didn't check the release notes for Catalyst drivers.
I'd like to test it, but ati-drivers-8.593-r10 are compiled for 2.6.28 kernel, so I'd have to downgrade from 2.6.29.
I'd rather compile them for my current kernel, but when I emerge it I get the package error "blocked by corruption" does it mean Sabayon does not allow to use emerge?
Or I have to remove all installed ati-drivers first? I can still see video/fglrx.ko in the "modprobe -l" list...

I wouldn't expect DVD 4.1 GNOME working either, unless uses older Calalyst drivers, because neither boot option on KDE DVD is working without "Input not supported", even XMBC and it's working on Gnome if I'm not wrong?

[Fitzcarraldo]

Vitoriung, the point is that on the SL 4.1 KDE LiveDVD the fglrx driver is the 8.593-11 version and that is what is installed to your HDD if you use that LiveDVD. It doesn't matter what desktop environment you boot into with that LiveDVD or after you install to your HDD, the driver will still be the -11 version. Unlike the SL 4.1 GNOME LiveDVD which was released earlier than the SL 4.1 KDE LiveDVD and has the -10 version of the driver.

You could, if you were interested, use Portage instead of Entropy to install the 8.593-10 version with the 2.6.29 kernel. That is what I have done, which is why I know that it works. But, to be honest, if you have a working system with the open-source Radeon driver then I wouldn't bother. After all, that driver continues to be developed, whereas you'd be stuck with the closed-source ati-drivers-8.593-r10 version (Catalyst 9.3) if you switched back to the fglrx driver.

The reason you got the error message when you tried merging the 8.593-r10 version is probably because you did not resync with the Portage ebuild repository and Sabayon overlay:

Code: Select all

emerge --sync
layman -S

but the overlay repo recently changed from SVN to Git so you may also need to do:

Code: Select all

layman -d sabayon
layman -a sabayon
layman -S

and it could also be that you need to regenerate the manifest for the package:

Code: Select all

ebuild <path to ebuild directory>/ati-drivers-8.593-r10.ebuild manifest

Unless you are very familiar with Portage I wouldn't bother trying, as you have a working open-source Radeon driver.

I would still be curious to know how CJ Master would fare if he tried booting the SL 4.1 GNOME LiveDVD instead of the SL 4.1 KDE LiveDVD. Of course it could be that his problem has nothing to do with the 8.593-r11 driver from the Entropy repository. But it would be an interesting experiment. I also notice that I did not tell him to try adding the xdriver=ati boot parameter, or xdriver=vesa and so on. These are also things to try when having trouble booting a LiveDVD.

[Vitoriung]

OK,
I've tried Gentoo way, but during emerge I got the error:

Code: Select all

 ati-drivers-8.593 is not yet compatible with 2.6.29 kernels. See bug #264021.


So I give up, everybody who has older ATI card good luck or use radeon driver as I wrote above.

V.

[Fitzcarraldo]

Don't worry. If you have a working installation with the open-source driver then that's fine.

Anyway, just for your information, it looks like you're trying to merge version 8.593 of ati-drivers which is in the main Portage tree, rather than version 8.593-r10 which is in the Sabayon overlay. As you can see from the output from the eix command below, they are two different packages:

Code: Select all

$ eix x11-drivers/ati-drivers
[U] x11-drivers/ati-drivers
     Available versions:  [M]8.27.10-r1!s 8.32.5!s!t (~)8.33.6-r1!s!t [M]8.35.5 [M](~)8.36.5 [M]8.39.4 [M]8.40.4 [M](~)8.452 [M]8.471.3 (~)8.542-r10[1] 8.552-r2 (~)8.552-r3 (~)8.552-r10[1] (~)8.552-r11[1] (~)8.573-r1 (~)8.573-r10!b[1] (~)8.582 (~)8.582-r10!b[1] (~)8.593 (~)8.593-r10[1] (~)8.593-r11[1] (~)8.600-r10[1] {acpi debug distribution doc kernel_linux multilib opengl qt3}
     Installed versions:  8.593-r10!b[1](22:58:10 04/04/09)(acpi distribution kernel_linux -debug)
     Homepage:            http://www.ati.com
     Description:         Ati precompiled drivers for recent chipsets

[1] "sabayon" /usr/local/portage/layman/sabayon
$

Notice that the package ati-drivers-8.593 does not have "[1]" against it, whereas the package ati-drivers-8.593-r10 does. As you can see from the message at the end of the output from the eix command, "[1]" indicates packages that are in the Sabayon overlay.

Just for your information, you would need to perform the following steps as root user in a Terminal/Konsole window to compile the 8.593-r10 version of ati-drivers:

1. The Sabayon overlay was recently changed from a SVN-based repository to a Git-based repository so, if you have not already done this, you would need to delete the overlay and then re-add it:

Code: Select all

layman -d sabayon
layman -a sabayon

2. Now make sure your main Portage tree is up to date:

Code: Select all

emerge --sync

3. Now, just to be sure, make sure all overlays are up to date:

Code: Select all

layman -S

4. Now you can merge the package:

Code: Select all

emerge =x11-drivers/ati-drivers-8.593-r10