Maxplayer14

[root@localhost moodin]# rpm -qa | grep qt3 libqt3-3.3.5-10.2006.SoS qt3-common-3.3.5-10.2006.SoS Was trying this... export QTDIR-/usr/qt/3/ bash: export: `QTDIR-/usr/qt/3/': not a valid identifier

KBFX is the first thing and Moodin (Engine) + Themes.

Ok, man I have been working on this for a whole day now and no matter what I do I can't get this thing working. I have been trying to compile 2 things since yesterday evening and I keep having the same problem. I have done everything I can think of, I have read every forum, and tried everything but I still get the same error every time I try a /configure. checking for Qt... configure: error: Qt (>= Qt 3.0) (headers and libraries) not found. Please check your installation! I have everything I need installed it looks like. Qt3, Qt3 Devel. I have tried everything I can think of, so I am here asking for any suggestions. Thanks ahead of time. Jason

Don't know, but I do know I can boot sorta fine (besides a stall at GDM login) with kernel 2.6.7-1.mm.7mdk. That is the one I am currenlty booting to, although that one problem with that, but that is x related not kernel related like my bigger problem.

By the way my old kernel was 2.4.26-1mt.

Ok these are the entries from yesterday from syslog were it freezes. Apr 12 13:42:58 dhcppc5 kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64 Apr 12 13:42:58 dhcppc5 kernel: intel8x0_measure_ac97_clock: measured 49580 usecs Apr 12 13:42:58 dhcppc5 kernel: intel8x0: clocking to 48000 Apr 12 13:42:58 dhcppc5 alsa: succeeded Apr 12 13:43:00 dhcppc5 alsa: Doing alsactl to restore mixer settings: succeeded[/QUOTE] Then I let it sit like you suggested and of course rebooted so the next entry [CODE]pr 12 14:46:01 dhcppc5 shutdown: shutting down for system reboot Apr 12 14:46:01 dhcppc5 init: Switching to runlevel: 6 It even says succedded on logs. Now this is what a succesfull boot one of my kernels. Apr 12 14:47:04 dhcppc5 alsa: succeeded Apr 12 14:47:05 dhcppc5 alsa: Doing alsactl to restore mixer settings: succeeded Apr 12 14:47:05 dhcppc5 sound: Loading mixer settings succeeded Apr 12 14:47:06 dhcppc5 xfs: xfs startup succeeded Any suggestions now, lol?

OK, I let it sit at the "Doing alsactl to restore mixer settings [OK]" for 45 minutes already and nothing. Do you think whatever it is starting next is having the problems? I says the alsactl restore mixer settings is OK like it completed that. This happens on the latest Kernel. I can still boot to the old one, it just sits for 5 minutes before it actually logs in to KDE.

Yes I am using 10.1. I have given it what seem like 10 minutes, but you know what I got time. Let me try it again. See what we get. BRB

Okay, I did my first kernel upgrade since I have been using linux today. I just used urpmi to get and install the kernels. (maybe I messed up doing that) I have installed now Kernel 2.6.7-1.mm.7mdk and the newest for mandrake (this one I installed by rpm) 2.6.8.1.12mdk. If I boot up to 2.6.7 it boots wonderfull. I get to GDM and login, this is where it sits for about 5 minutes then it logs into KDE just fine. If I boot up using the 2.6.8.1.12mdk it will hand on the "doing alsactl to restore mixer settings" it even shows OK beside it in the verbose mode but it will not go any further. Any suggestions to either one of these problems? [moved from Software by spinynorman]

thebrix and most the mirrors on it seem to work for me. They aren't full repositories though, they are just custom built rpms for certain apps.

Do you have main, contrib, jpackeg, and plf? Another thing you might want to do is add 2 off each. I have 2 mirrors set up for each of mine. Also make sure that you do a urpmi.update -a, this will update the list files so everything is current.

You may need to update again. I didn't have that problem when i upgraded. I didn't have the looping login problem, but I installed GDM which fixed that.

I have them as mirrors. I think yesterday there was some problems connecting just because I got some errors. But usually I connect ok.

You did a new installation because of that? I fixed it without a problem. Basically boot to console to drakconf, change your Display manger.

Fixed now, thanks for reply. This is what I did. mv /home/username/.kde /home/username/.kde-old