LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-03-2010, 03:41 PM   #1
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Rep: Reputation: 15
upgrade and no startx


I'm running Slackware current, and just did a slackpkg upgrade.

I can't startx. I get the following

FATAL: Error inserting i915 (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format
(EE) intel(0): No kernel modesetting driver detected.
(EE) Screen(s) found, but none have a usable cofiguration

Any help with this would be appreciated as I currently cannot use my Slackware.

Donald
 
Old 03-03-2010, 03:48 PM   #2
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 122

Rep: Reputation: 38
Quote:
Originally Posted by DonaldUK View Post
I'm running Slackware current, and just did a slackpkg upgrade.

I can't startx. I get the following

FATAL: Error inserting i915 (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format
(EE) intel(0): No kernel modesetting driver detected.
(EE) Screen(s) found, but none have a usable cofiguration

Any help with this would be appreciated as I currently cannot use my Slackware.

Donald

use -generic kernel, not -huge

Last edited by conraid; 03-03-2010 at 03:50 PM.
 
Old 03-03-2010, 03:51 PM   #3
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
I've tried that with no success. What I did was cd to /boot then ln -sf vmlinuz-generic-2.6.33 vmlinuz and tried startx with the same lack of success as before.

Donald
 
Old 03-03-2010, 03:52 PM   #4
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 122

Rep: Reputation: 38
Quote:
Originally Posted by DonaldUK View Post
I've tried that with no success. What I did was cd to /boot then ln -sf vmlinuz-generic-2.6.33 vmlinuz and tried startx with the same lack of success as before.

Donald
but you've created the initrd and run lilo again?
 
Old 03-03-2010, 03:56 PM   #5
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
Thanks Conraid.

Forgive my lack of detailed skill here.

OK, I've run mkinitrd and then /sbin/lilo - still the same lack of success.

Donald
 
Old 03-03-2010, 04:00 PM   #6
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 122

Rep: Reputation: 38
Quote:
Originally Posted by DonaldUK View Post
Thanks Conraid.

Forgive my lack of detailed skill here.

OK, I've run mkinitrd and then /sbin/lilo - still the same lack of success.

Donald

must restart at this point

you must boot using the generic kernel

Forgive my English


attention to have created initrd right and you change lilo.conf with initrd=/boot/initrd.gz before launch lilo

read /boot/README.initrd

Last edited by conraid; 03-03-2010 at 04:01 PM.
 
Old 03-03-2010, 04:05 PM   #7
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
Aaaaarhgh!

Now I reboot and get a kernel panic -

No filesystem could mount root, tried: romfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,9)

Help!

Donald
 
Old 03-03-2010, 04:07 PM   #8
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 122

Rep: Reputation: 38
Quote:
Originally Posted by DonaldUK View Post
Aaaaarhgh!

Now I reboot and get a kernel panic -

No filesystem could mount root, tried: romfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,9)

Help!

Donald
You must change lilo.conf

read /boot/README.initrd

http://slackware.osuosl.org/slackwar.../README.initrd
but with 2.6.33 (-smp if you use it)

Last edited by conraid; 03-03-2010 at 04:10 PM.
 
Old 03-03-2010, 04:15 PM   #9
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
I have an old version of Ubunutu on the same machine and so can boot that to get access to my Slackware files. I open kedit to get at the /boot/README.txt. I can see a link to the file and try to open it but get a message saying that the file does not exist.

What do I have to change in /etc/lilo.conf?

Thank you for be patient with me!

Donald
 
Old 03-03-2010, 04:21 PM   #10
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 122

Rep: Reputation: 38
Quote:
Originally Posted by DonaldUK View Post
I have an old version of Ubunutu on the same machine and so can boot that to get access to my Slackware files. I open kedit to get at the /boot/README.txt. I can see a link to the file and try to open it but get a message saying that the file does not exist.

What do I have to change in /etc/lilo.conf?

Thank you for be patient with me!

Donald

have you created an correct initrd?
http://slackware.osuosl.org/slackwar.../README.initrd

if yes, you must write in lilo.conf

initrd = /boot/initrd.gz

after
image = /boot/vmlinuz
line

and after launch lilo
but now you have to do chroot mode

my English does not allow me to help you better, i'm sorry

Last edited by conraid; 03-03-2010 at 04:22 PM.
 
Old 03-03-2010, 04:30 PM   #11
razb
LQ Newbie
 
Registered: Oct 2009
Location: Ukraine
Distribution: Slackware
Posts: 9

Rep: Reputation: 1
Try this with huge kernel:
_http://www.linuxquestions.org/questions/slackware-14/ati-in-current-upgrade-792578/page4.html#post3884551
It works perfectly )
 
Old 03-03-2010, 04:35 PM   #12
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
Perhaps I am doing something wrong. From Ubuntu I altered the lilo.conf then did chroot /mnt/Slackware and did /sbin/lilo. Rebooted and tried to boot Slackware - got the same kernel panic.

DOnald
 
Old 03-03-2010, 04:36 PM   #13
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 122

Rep: Reputation: 38
Quote:
Originally Posted by DonaldUK View Post
Perhaps I am doing something wrong. From Ubuntu I altered the lilo.conf then did chroot /mnt/Slackware and did /sbin/lilo. Rebooted and tried to boot Slackware - got the same kernel panic.

DOnald

have you created an correct initrd?
 
Old 03-03-2010, 04:36 PM   #14
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
razb

How do I downgrade my module-init-tools from ubuntu and how can I get out of my kernel panic?

Donald
 
Old 03-03-2010, 04:38 PM   #15
DonaldUK
Member
 
Registered: Apr 2004
Posts: 106

Original Poster
Rep: Reputation: 15
Conraid

How do I know if I've made a correct initrd?

Should I try again and what command? mkinitrd but with what options?

Donald
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Init 4 wont startx after upgrade... Alexvader Slackware 2 01-28-2010 11:51 AM
[SOLVED] Intel card - upgrade to 13.0 - cannot startx? quanta Slackware 8 09-01-2009 04:58 AM
(nvidia) First startx = blank screen, second startx = works ?!? BuckRogers01 Linux - Hardware 2 04-07-2006 05:26 PM
Bug / Xwindows / startx : xinit works but startx crash www.rzr.free.fr Linux - Software 4 10-17-2004 08:06 AM
Upgrade XFree86, now can't startx Texicle Linux - Newbie 1 03-01-2003 11:59 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:07 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration