View Full Version : Latest kernel with no Display
STEVE555
4th March 2009, 03:05 PM
Hi to all,
I iam using Fedora 11 Rawhide Alpha,my graphics card is a Nvidia Geforce 6800Gt with 256Mb of memory,my monitor is a A.D.I Microscan G1000.
I am currently using the git versions of drm ,mesa and the nouveau driver.
My problem is this,when I try to boot into my latest kernel(2.6.29-0.179.rc6.git5.fc11.i586) at the top of my list,it loads but I don't get the KDM login manager,just a black screen and I can't even select a tty to login to.
The kernel that I'm booting into(2.6.29-0.176.rc6.git5.fc11) is booting fine.I've just ran yum clean all and yum update,and it's offering me the latest kernel(2.6.29-0.197.rc7.fc11) but I darernt update,or I won't be able to boot into KDE!
I've tried to recompile my git version of drm,and it installs fine,but when I try to issue the command: make -C linux-core,I get this message:
make: *** No rule to make target `../shared-core/drm_pciids.txt', needed by `drm_pciids.h'. Stop.
It has built with tyhat command before.
I do want to use Fedora with the latest kernel that has been provided.Does anybody know of a workaround I can use? any help would be greatly appreciated.
Regards,
STEVE555.
SlowJet
4th March 2009, 03:20 PM
w or wo (nouveau.modeset=1)
176
nv
179, 196, 197
They tried some stuff, it was broke, they tried to fix it, ...
There will be many more tries.
SJ
RalphCC
4th March 2009, 03:20 PM
It sounds a little like the problem I have just had , where SELinux was enforcing. Need to set to permissive and relabel.
I was using Gnome though.
SlowJet
4th March 2009, 03:32 PM
It's not SELinuxYou just needed a relabel due to some other reason.
The latest selinux-policy does block the lateset kerloops though. (big woop, it will get fixed)
SJ
STEVE555
4th March 2009, 03:42 PM
Thanks for the information guys,I'm not sure what the relabel for selinux-policy is though.
Slowjet,is it safe to install the latest kernel yet? or shall I hang on unitl later on tonight or tomorrow morning?
Regards,
Steve555
SlowJet
4th March 2009, 04:02 PM
Linux Jovette-14.WinProxy 2.6.29-0.197.rc7.fc11.i686.PAE #1 SMP Tue Mar 3 23:01:42 EST 2009 i686 i686 i386 GNU/Linux
It works fine (with nv) but it would work better with today's updates for xorg, udev, keyboard stuff, mesa, lots of updates coming soon.
see the devl and/or test list
SJ
STEVE555
4th March 2009, 11:21 PM
Hi everyone,here's an update,
I booted into my 2.6.159 kernel and edited my xorg.conf and changed my driver name from nouveau to nv and then rebooted.The good news is that it was a success.I could get to the desktop using the latest 2.6.197 kernel.
So while I was there,I recompiled and installed the DRM I'm using from git,and afterwards,I cd'ed to linux-core and ran depmod drm.ko,depmod nouveau.ko and then depmod -a to see if the latest kernel could use those modules.I then changed my driver name from nv back to nouveau in my xorg.conf and looged out.
The bad news is when I logged out,I got the kernel boot sequence::( the screen was freezing on me again.
The messages seem to stop at loading atd if that's any help.So I'm writing this reply back in my 2.6.159 kernel,I do hope there will be a fix soon.
Regards,
STEVE555
AdamW
5th March 2009, 12:09 AM
It's a known bug in the latest Rawhide kernel, it'll hopefully be fixed in future kernels. For now, booting back to an older Rawhide kernel should avoid it.
SlowJet
5th March 2009, 03:19 AM
Ding! End of round 203.
What the heck are those compile junkies thinking?
SJ
AdamW
5th March 2009, 11:32 PM
"Gotta use all that big iron for something!", is my guess :)
I built a 203 kernel for my laptop (not really because I wanted that particular kernel, I'm testing something that I had to rebuild a kernel to test). It dies immediately on boot. More time in the oven required :P
STEVE555
7th March 2009, 08:21 PM
Hi everyone,I have some great news.
Afters todays updates(19:00 GMT,as I live in the U.K) the latest kernel(2.6.29-0.207.rc7.fc11.i586) can boot to the desktop:) I have tried a warm re-boot and a cold boot,and everything seems to be ok now.
I would like to say a big thank you to the developers who have made this happen.
The only thing I'm a little concerned about are these warning messages I see during the boot process:
Entering non-interactive startup
ip6tables: Applying firewall rules: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
Starting RPC idmapd: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
[60G[[0;32m OK [0;39m]
Regards,
STEVE555
SlowJet
9th March 2009, 06:54 AM
nouveau working for these on (MX, x86)
kernel-PAE-2.6.29-0.207.rc7.fc11.i686
mkinitrd-6.0.80-1.fc11.i586
kerneloops-0.12-4.fc11.i586
selinux-policy-3.6.8-1.fc11.noarch
policycoreutils-2.0.62-4.fc11.i586
rpm-4.7.0-0.beta1.2.fc11.i586
xorg-x11-drv-nouveau-0.0.12-9.20090309gited9bd88.fc11.i586
xorg-x11-drv-evdev-2.2.0-1.fc11.i586
SJ
AdamW
9th March 2009, 10:24 PM
steve555: those messages are harmless for now, don't worry about 'em.
slowjet: what's your graphics card exactly? Would be useful data for the developers.
SlowJet
9th March 2009, 11:29 PM
engine mx
nv = nv11
Brand = Hercules Profit II mx
32MB 4xAGP
Very old, may be going on 7 years.
Also works with kernel-PAE- 218 rc7-git2
SJ
SlowJet
10th March 2009, 06:51 AM
nouveau 12.10 is much better yet.
Screens transition pretty smoothly.
Plymouth leaves earlier, mouse pointer on dark screen show within a fraction of a second,
splash screen, logon - maybe 4 seconds.
Then about a few seconds a complete Gnome screen (panels and icons in correct places,)
finally, within a fraction of a second the network popup saying it is connected. (before this that popup was done and gone, never showing. So much faster boot up due to faster X.)
SJ
leigh123linux
10th March 2009, 10:28 AM
Hi everyone,I have some great news.
Afters todays updates(19:00 GMT,as I live in the U.K) the latest kernel(2.6.29-0.207.rc7.fc11.i586) can boot to the desktop:) I have tried a warm re-boot and a cold boot,and everything seems to be ok now.
I would like to say a big thank you to the developers who have made this happen.
The only thing I'm a little concerned about are these warning messages I see during the boot process:
Entering non-interactive startup
ip6tables: Applying firewall rules: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
Starting RPC idmapd: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-visor, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.dist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/floppy-pnp, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/anaconda, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
[60G[[0;32m OK [0;39m]
Regards,
STEVE555
You can stop the error by renaming the listed files.
i.e
/etc/modprobe.d/blacklist
becomes
/etc/modprobe.d/blacklist.conf
Post this from the non working system.
lsmod |grep nouveau
and
modprobe nvidia
STEVE555
10th March 2009, 11:30 PM
Hi leigh123@linux,
Thanks for the advice. I have renamed the files in /etc/modprobe.d with a .conf extension.Here is the information from the command prompts you've provided:
lsmod |grep nouveau
nouveau 363324 1
drm 166332 2 nouveau
i2c_core 18284 3 i2c_sis96x,nouveau,drm
[root@x1-6-00-c9-00-02-c6-36 ~]#
and:
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
FATAL: Module nvidia not found.
You have new mail in /var/spool/mail/root
I have to add the outputs are from the latest kernel that is working(2.6.29-0.215.rc7.fc11.i586 #1 SMP)
I have tried to do a depmod drm.ko from the linux-core folder from the drm folder I have compiled from the git repository,and I get this error message:linux-core]# modprobe drm.ko
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
FATAL: Module drm.ko not found.Which is basically the same message from modprobe nvidia.
I am waiting patiently for the developers to fix module-init-tools,I'm sure it will be sorted soon.
I can't run those commands from a non-working kernel.When I booted into one of those,it just stopped at loading atd.I couldn't get to a tty or nothing.I had to do a hard reset on the front of my p.c when that happened.I'm just glad for the moment that the latest kernel is working fine.
Regards,
STEVE555
smirko
13th March 2009, 08:15 PM
Hi,
Loading kernel modules works differently.
Modprobe requires you to put just the name of the module, not the file name itself.
Basically, ditch the file extension and it should give you another message. Or, if you're lucky - no message ;-)
And that would mean your module was loaded.
Let us know if it worked.
Regards
S
STEVE555
13th March 2009, 09:07 PM
Hi smirko,
Thank you very much indded fro the advice,it did the trick! I had no idea that modprobe now only requires the module name.I will look further into it via google.
Regards,
STEVE555
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.