suse 7.2 still wont install.. new info..still trying...
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
suse 7.2 still wont install.. new info..still trying...
hi there, if anyonecan help me....that would be so great! when i run yast2 to install, once the installation starts, the screen goes black and then i get a message saying that an "error occured during installation!" I have been trying to fix this for days.... trying everyones suggestions, with no luck yet. maybe you can help..... heres what i know so far:
this is what came up after hitting control alt f3 and f4 during the installation:
xlib extension "render" missing on disp "0:0" yast2: line 289 182 terminated (errno=9)
and
modprobe: cant locate module block - major 80 //then 104 &105
out of memory: killed process 182 (w2bignfat) //then 183 & 184
vfs: cannot open root device "" or 8:01
please append a correct "root=" boot option
kernel panic: vfs: unable to mount root fs on 08:01
// <---stuff after that is just my shorthand
by the way, i ran FIPS and it said it was unable to run because some files were in the last cylinder. I checked for mirorsav and image.idx but did not find them. i turned off my virtual memory which i hear could also be the problem, and i also deleted norton which i was also told could be causing the problem. none of this helped to install linux. how can i find those files that are in my last cylinder so i can get rid of them?
About mirrorsav.fil and image.idx.
Could it be ure running anything like Stacker, SuperStor, Doublespace, any backup, disk mirroring or Anti-virus software on Windoze? mirrorsav.fil and image.idx are hidden files, so be sure to check their properties. then theres an app called ShowFat that sposed to show all files (never used it tho). Im sticking with Partition Magic. Its commercial, costs a few bucks but its worth it, really saves u some headaches when moving around/creating partitions.
have u tried adding a root="(partition name here)" to the install prompt?
also tried using text/expert mode instead of graphical install?
if theres a choice for video cards on startup, choose something way conventional like generic 640x480 so it wont have to deal with exotic video cards.
Did you ever find the solution? I am having the same problem.
Here is my setup:
---------------------------
I recently bought the SuSE Linux 7.2 professional edition
At installation, the first menu pops up and then the kernel loads, from there my screen blanks out, it is a blank screen with no error messages. This happens regardless of what option I use, text only or the GUI.
I also have the SuSE 6.0 CDs and when I try the install I get the error message, "VFS: cannot open root device 08:01 ... Kernel panic: VFS unable to mount root fs 08:01"
I have read some forum posting about this error that is associated with the RAMdisk initializting and looking for the the "initrd" file in /boot or /dev/sda1". But I still feel a little clueless here.
I am using the ASUS CUX4V-D which is dual P3 board, I have 2 CPUs (each 1 GHz), One GIG strip of memory with ECC, 40 GIG EIDE IBM hard drive, Gainward CardExpert Geforce3 video card, a foppy disk drive, and a ASUS CD-ROM. All this componets are functional and have been tested with a different O/S.
I know that the hardware is not broken because I have
a removable hard drive set up, and my second hard
drive I have Windows 2000 professional as my O/S. My Second hard drive which I am trying to install a LINUX on is brand new and I know I can install another MS windows O/S with this drive
I am a newbie with the full set-up installation of LINUX, but I am familiar and I do work in UNIX environment so I am not completely blind or clueless. But deaking at the kernel level, I am unsure from here.. I need step by step instructions on how to fix this.
It may be a bit of a kluge, but you might want to look at using a boot/install floppy set and install it with the old console menus rather than the GUI setup. I know there's a way to get it to do so from a CD-ROM/DVD but I haven't installed SuSE form a CD since 6.0. If you have the manuals there should be a hint in there about this. You can get a lot more diagnostic information from that approach than the GUI. Once you make the boot floppy you should be able to install using the CD-ROM as the source.
Judging by the contents of your initial thread it looks like your CD-ROM is getting lost after the initial boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.