LinuxQuestions.org
Register a domain and help support LQ
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 08-03-2006, 12:17 PM   #16
vharishankar
Senior Member
 
Registered: Dec 2003
Posts: 3,142
Blog Entries: 4

Rep: Reputation: 121Reputation: 121

In which case, you'd probably save a lot of time if you just reinstalled the whole thing rather than figuring out the problem. It's painful I know, but I've had to do this so often that sometimes it's worth just retrying the whole thing from the start and doing it more carefully.

I once wiped out my whole Debian partition because of the awkward device naming scheme of Arch Linux (as it was earlier, now they've moved to udev). One learns by experience as I did to pay a lot more attention to all the configuration options during OS installation... This is just general advice and not targetted at you or anybody in particular btw.

Last edited by vharishankar; 08-03-2006 at 12:20 PM.
 
Old 08-03-2006, 12:22 PM   #17
vharishankar
Senior Member
 
Registered: Dec 2003
Posts: 3,142
Blog Entries: 4

Rep: Reputation: 121Reputation: 121
One further suggestion. Read the grub manual thoroughly if you haven't already. Its documentation is pretty extensive and once you get your head around the naming scheme for devices and partitions, it's pretty easy to figure out.

http://www.gnu.org/software/grub/manual/grub.html
 
Old 08-03-2006, 12:29 PM   #18
thelonius
Member
 
Registered: Aug 2005
Location: Montréal
Distribution: Debian Testing, Slackware 10.2
Posts: 136

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Harishankar
once you get your head around the naming scheme for devices and partitions, it's pretty easy to figure out.

http://www.gnu.org/software/grub/manual/grub.html
the problem must be somewhere in SW, because debian uses the same booting scheme - GNU/Linux, and boots normally.
 
Old 08-03-2006, 01:07 PM   #19
simcox1
Member
 
Registered: Mar 2005
Location: UK
Distribution: Slackware
Posts: 794
Blog Entries: 2

Rep: Reputation: 30
thelonius, where is that kernel from? It's not a standard slackware10.2 kernel. If you used the only 2.6 kernel, in testing, it's 2.6.13. And you do need to use initrd unless you use ext2 file system
 
Old 08-03-2006, 01:09 PM   #20
thelonius
Member
 
Registered: Aug 2005
Location: Montréal
Distribution: Debian Testing, Slackware 10.2
Posts: 136

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by simcox1
thelonius, where is that kernel from? It's not a standard slackware10.2 kernel. If you used the only 2.6 kernel, in testing, it's 2.6.13. And you do need to use initrd unless you use ext2 file system
i downloaded 4 cds from SW mirror site, installation was done from two first cds.

i use ext2 on /.

i definitely need to reinstall the system
 
Old 08-03-2006, 09:11 PM   #21
thelonius
Member
 
Registered: Aug 2005
Location: Montréal
Distribution: Debian Testing, Slackware 10.2
Posts: 136

Original Poster
Rep: Reputation: 15
finally after reinstallation (with quick formatting in ex2 and choosing default kernels) i can boot either directly from grub with 'root' and 'kernel' commands or with lilo run from grub's 'chainloader'.

now i gonna have ulotafan

thank you

Last edited by thelonius; 08-03-2006 at 10:38 PM.
 
Old 08-05-2006, 04:10 AM   #22
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
anyway everything is working u r happy!!!
but many times u blamed slack -and i dont like that it wasn't a slack error
Quote:
i do enter in lilo which proposes me one option - 'Linux'. impossible to see-modify whatever in
lilo... when i boot 'linux', it gives after a shortwhile

VFS: cannot open root device "1604" or unknown-block(22,4) Please append a correct "root=" boot option
but let me ask some questions? is this the slackers way?? i
sdont even need answer

the earlier message comes when there is some error in kernel(usually no file system support), and as far as i know
the kernels u listed were not slackware's and this error wont come if u "run lilo" from slack's root, u could haev atlest try booting into ur hard disk using ur slack first cd
Quote:
but as i say, i cannot modify boot options in lilo
til now i didnt got how u get into slack and run lilo

i have 3 distros booting from slack lilo please dont blame slack, regards
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Dual-booting on an existing WinXP Raid 1 array?? bobbryce Fedora - Installation 1 06-28-2005 02:51 PM
Dual booting with Grub - installing Win 2000 from CD-Rom with an existing SuSe 9.1 Steve2001 Linux - Newbie 3 01-19-2005 11:15 AM
Old installation of GRUB prevents me from using LILO and booting into Slackware! EThitop Slackware 6 12-12-2004 01:07 PM
Problem booting Slackware from GRUB Spooner Slackware 2 03-05-2003 05:47 PM
Installing RH 7.3 w/existing 7.2/Grub/Multiboot bsnuggs Linux - Distributions 6 08-21-2002 08:09 AM


All times are GMT -5. The time now is 01:35 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration