KDM Problem (??) - New KDE BSOD-Like Feature?

[tkteo]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Mesa update without the problematic commit should be uploaded to karmic repositories soon:
https://lists.ubuntu.com/archives/ka...er/010941.html

[tkteo]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Oops. I think I'd better warn people that with the most recent kernel update linux 2.6.31-13.45, setting "radeon.modeset=1" makes my system unable to boot to the kdm login screen.

[molostoff]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Oops. I think I'd better warn people that with the most recent kernel update linux 2.6.31-13.45, setting "radeon.modeset=1" makes my system unable to boot to the kdm login screen.

I have booted successufully with new kernel.

Then with this new kernel I have removed modeset from grub and from module config, and rebooted ok. At this moment console is fine, kde effects - ok, except I havnt tested it for speed, but functional part works.

Only repo from ppa:ubuntu-x-swat/x-updates still in sources.

[sblass]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

I have booted successufully with new kernel.

Then with this new kernel I have removed modeset from grub and from module config, and rebooted ok. At this moment console is fine, kde effects - ok, except I havnt tested it for speed, but functional part works.

Ahhhh, life is good. I, too, have updated this A.M., and system is extremely zippy with new kernel and Mesa.

Much thanks to all thread contributors along the odyssey.

[hteles]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Hi,

mine is too damn slow with desktop effects turned on but at least it's stable now.
BTW, why can't i switch to a virtual terminal anymore

lspci -vv
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE)
    Subsystem: Acer Incorporated [ALI] Device 0066               
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- 
    Latency: 0, Cache Line Size: 32 bytes                                
    Interrupt: pin A routed to IRQ 16                                  
    Region 0: Memory at c0000000 (32-bit, prefetchable) [size=256M]                   
    Region 1: I/O ports at 3000 [size=256]                                
    Region 2: Memory at b0100000 (32-bit, non-prefetchable) [size=64K]                  
    [virtual] Expansion ROM at b0120000 [disabled] [size=128K]                      
    Capabilities: [50] Power Management version 2                            
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)          
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-                         
    Capabilities: [58] Express (v1) Endpoint, MSI 00                           
        DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <4us            
            ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset-                   
        DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-              
            RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+                     
            MaxPayload 128 bytes, MaxReadReq 128 bytes                      
        DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-             
        LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <2us      
            ClockPM- Suprise- LLActRep- BwNot-                          
        LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+               
            ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-                    
        LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-     
    Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-           
        Address: 0000000000000000 Data: 0000                            
    Capabilities: [100] Advanced Error Reporting <?>                           
    Kernel modules: radeon

[hteles]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Spoke too soon

After some Xorg updates right now everything is really fast again and virtual terminals are back

[molostoff]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Spoke too soon

After some Xorg updates right now everithing is really fast again and virtual terminals are back

Yes, too soon, updates revert back the situation, but I still stay with radeon-kms params (returned them back).

Could you tell what x/radeon parameters (or none of them - just clean install) you use ?

[hteles]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Hi,

plain system, no xorg.conf, radeon driver.

[tkteo]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

And I have turned off both Radeon KMS and desktop effects for now. Will play around with enabling desktop effects after I, ahem, focus on my job. :P

[hteles]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

Better do it

[molostoff]

Re: KDM Problem (??) - New KDE BSOD-Like Feature?

And I have turned off both Radeon KMS and desktop effects for now. Will play around with enabling desktop effects after I, ahem, focus on my job. :P

Effects are speedy now as it was before, radeon.modeset is still should be set in grub kernel options.