Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

[budr]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

I just installed alpha 2 from lucid alternate dated 1/14. It installed OK, but doesn't seem to see my mouse. I can log in and get to a desktop, but even at the kdm login screen the cursor doesn't follow mouse movements.

I have a logitech wireless mouse & keyboard. Login worked and I can alt-F2 and get a konsole, so it sees the keyboard OK, just no mouse. I didn't spend a lot of time trying to troubleshoot. Didn't see anything obvious in .xsession-errors or in the logs. Just wondering anyone else has run into this.

[Rog131]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

KMS problems with the Kernels 2.6.32-10 & 2.6.32-11

Older Ati Radeon


When booting with the 2.6.32-10 & 2.6.32-11 kernels the start is ending to the text mode log in. When trying to launch the KDE with the "startx" the screen will turn black.

A bug report > Bug #509273: [Lucid] KMS doesn't work properly with old Radeon cards.


Adding the "nomodeset" to the kernel line is "fixing" the problem at here.

Temporary - Press e (edit) when in the Grub2 screen and add the nomodeset after the "quiet splash"

Permanent - /1/ "for GRUB 2: edit /etc/default/grub and add nomodeset to GRUB_CMDLINE_LINUX, then run sudo update-grub"


/1/ > Karmic Koala Release Notes

[nuno]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

Permanent - /1/ "for GRUB 2: edit /etc/default/grub and add nomodeset to GRUB_CMDLINE_LINUX, then run sudo update-grub"

I find a PITA to disable KMS/plymouth in Lucid. It's very hard to do without side effects. Just adding the nomedeset kernel parameter seems to work, but you loose the text consoles after you logout from the first X session: just a blank screen afterwards. Another problem is loosing the boot logs... However, AFAIK this is the best method yet.

I'm trying to find a way to disable plymouth without side effects on radeon hardware.

[kubicle]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

Just adding the nomedeset kernel parameter seems to work, but you loose the text consoles after you logout from the first X session: just a blank screen afterwards.

I haven't seen that (using radeon with "nomodeset"), but I don't have plymouth installed (and I load the radeonframebuffer [radeonfb] and framebufferconsole [fbcon] modules at boot so I'm not using a "stock" setup)

I'd recommend trying to uninstall plymouth first to see if the issue is caused by it. It has caused some issues with virtual terminals (on my machine, plymouth, when installed, bumped the first X session to tty8 instead of tty7, for example)

[nuno]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

Just adding the nomedeset kernel parameter seems to work, but you loose the text consoles after you logout from the first X session: just a blank screen afterwards.

I haven't seen that (using radeon with "nomodeset"), but I don't have plymouth installed (and I load the radeonframebuffer [radeonfb] and framebufferconsole [fbcon] modules at boot so I'm not using a "stock" setup)

I'd recommend trying to uninstall plymouth first to see if the issue is caused by it. It has caused some issues with virtual terminals (on my machine, plymouth, when installed, bumped the first X session to tty8 instead of tty7, for example)

The base system depends on libplymouth. You may have removed the plymouth package, but try to remove the lib and see the scary messages ;-)

Besides the "mountall: cannot connect to plymouth" there's no boot log and no messages on screen. Useless for debugging.

For me plymouth is a big no no, specially in a server and/or LTS release like lucid.

[kubicle]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

The base system depends on libplymouth. You may have removed the plymouth package, but try to remove the lib and see the scary messages ;-)

Well, that's why I said to try removing plymouth and not libplymouth, but I probably should have pointed that out more clearly :P

Besides the "mountall: cannot connect to plymouth" there's no boot log and no messages on screen. Useless for debugging.

Did you boot with the default "quiet" and "splash" boot options. Removing them might give you more boot messages.

[nuno]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

Yes, I did try.

removing "quiet" makes the kernel display it's messages and it works;
removing splash should disable the boot splash. In Lucid it doesn't matter because upstart is silent by default. You can add --verbose (or is it --debug?) to the kernel options but that makes upstart (the new init) way too verbose.

In Lucid you can forget about the standard text initialization.

To me it's a major bug. And plain useless! The cherry on top it's Lucid LTS status :|

[Rog131]

Re: Alpha 1/2 Hickups (Xorg/Mesa/Radeon)

Update 2010-02-06

Now the KMS is working here without the "nomodeset" option.