View Full Version : Broke again - no x possible.
3rd April 2009, 07:33 AM
I downloaded and updated kernel-PAE-2.6.29-1.46.
blank screen for xorg
w/wo Plymouth, w/wo selinux=0, w/wo (3, startx)
even tried xdriver=nv
ok, bad kernel or nouveau for this kernel.
rebooted in to old kernel,
same thing (w/wo list)
wget new nouveau drv 21
nothing but black screen.(w/wo list )
3rd April 2009, 02:21 PM
ok, I missed some updates.
After those I was able to startx
kernel-PAE line for 18.104.22.168-37
using nouveau 21
I'll try kernel 46 later.
P.S. This includes the new rpm 4.7.0 beta1.9
3rd April 2009, 04:30 PM
Is it recommended to try nomodeset for the Intel chipsets or is it just an nVidia thing?
I tried the 46 kernel from koji and had the same issue, the circular lock, that I posted earlier. I couldn't find any other applicable packages that might play a role in this for me...
3rd April 2009, 08:28 PM
The list for Apr 03rd came out.
Some of those updates may apply. (like initscripts, gnome-keyring, libselinux)
I thoht these were for APR 02nd as the list for both days was blank.
I don't know the status of intel drv for F11 but Kernel-22.214.171.124-15 is working with intel 865 for F10.
3rd April 2009, 09:19 PM
I booted into kernel-126.96.36.199-46 with 3 nomodset
This kernel is about the same change level as 188.8.131.52-15 for F10
I am not getting an locks on either, just the pulseaudio , networkmanager stuff and a couple of nouvea messages.on F11, F10 is pretty clean.
So with today's updates the 46 and intel should work without any kernel line commands. (If it doesn't, then that would be a bug to report.
3rd April 2009, 10:56 PM
I had the same results as before. Applied today's updates, then tried to boot the PAE kernel, lock-up.
Added selinux 0 3 and ran startx, lock-up.
Added selinux 0 3 nomodeset and ran startx, lock-up.
It's still not fixed for Intel hardware...
3rd April 2009, 11:04 PM
Well, it is slightly different, no more circular lock message. Nomodeset yields thousands of this line:
Apr 3 17:51:04 localhost kernel: reserve_memtype: calling reserve_ram_pages_type for 0x32d99000 0x32d9a000 16
I'll try without nomodeset and see if I get anything...
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.