Hi there!

I have a BBIIGG Problem now!

I hope someone is a swaret expert or a bit expirienced...

Since I updated without errors my X-Server won't come up ...

But here's the full story:

Amailo A AMD 3000+ ...made a fresh install of Slack 10.0 this morning. Everything works fine.

Update to kde 3.3 from slackware packages... also fine...

Configure my Desktop to look good, configure vim and some little stuff.

Turned on httpd, samba, mysqld on boot by makeing their startupscripts executable. Still working fine.

Then I ran swaret for the first time ever. I followed the FAQ from swarte-stie and another tut. I edited the /etc/swaret.conf like I read it in the howto... but in the sources section I uncommented a line, like the howto wanted me to, but it pointed to a Slack9.1 ftp-folder on linuxpackes and I changed it to 10.0
The update itself worked fine, without problems. Dependencies were checked and corrected ... everything should be fine..
Here is what I did (did this from an Terminal inside KDE3.3):

$ updatedb
$ swaret --update
$ swaret --upgrade -a
$ swaret --upgrade -a
$ swaret --upgrade -a ( I read it is good to do this a few times to be sure all deps are ok ... they were from the beginning)
$ swaret --dep ( reportet some missing, but said they are fixed)
$ swaret --purge

So, everything seemed ok ...

I rebooted and the System came up without any errors or something like that... but when runlevel 4 was reached and X started the screen suddenly turned back to the console a second before kdm would come onto the monitor.
But no login-prompt. No error messages. dmesg looks clear too.

I logged in as root on another console (strg+alt+F6) and did a startx .. the same result, but a long list of messages... the most interesing seeming part is the second half... here:



...
(EE) Failed to load module "speedo" (module does not exist, 0)
(EE) Failed to load module "Keyboard" (module does not exist, 0)
...
(EE) No Input driver matching 'Keyboard'
No core keyboard

Fatal server error:
failed to initialize core devices

...

XIO: fatal IO error 104 (Connection reset by server) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining



And, when I rebooted I saw an error on the booting sequence...


/lib/modules/2.4.26/kernel/drivers/char/agpagpgart.o.gz Inavlid argument
/lib/modules/2.4.26/kernel/drivers/char/agpagpgart.o.gz Hint: insmod errors can be caused by incorrectr module parameters
...
/lib/modules/2.4.26/kernel/drivers/char/agpagpgart.o.gz insmod agpgart failed


So... long story, eh? Not sleeping? good! .. so... do YOU have a nice idea where that may come from? And what to do againbst that?

Thanks for your time, greetings, Sascha

"(EE) No Input driver matching 'Keyboard'
No core keyboard

Fatal server error:
failed to initialize core devices"

Change the line in xorg.conf that says Driver "Keyboard" to Driver "kbd" this has been discussed a lot here... it's on Slackware's log and on Xorg documentation.

It's also in the changelogs which you should read before updating with swaret.

Ahhh, beat me too it!!

here's a link though:

http://www.slackware.com/changelog/current.php?cpu=i386

For my part, I find 'swaret --upgrade -a' somewhat suicidal...
I much prefer do 'swaret --upgrade' without -a switch, so I can abort upgrade a package that I don't want to.

Hi!

Thanks, that worked perfectly!

But now, running KDE again, I have another problem... the same problem I had 2 days ago and that was the reason why I finally reinstalled slack...

I could not get my sound to work again! Is there something I have to change to?

Have via82xx ... last time the module simply wasn't there... this time it it is renamed to snd-via82xx.o.gz and can not be located!

And why does my console inside kde start a new line while I am typing?

Hell, am I so stupid, is this so buggy or so complicated? :-)

Thanks very much for your help!