There's not much help I can give. But I've added some comments below.
On 11/29/05, Adam Felix Bogacki <[EMAIL PROTECTED]> wrote:
Are you sure there is no way you could get 2.6.5 back up and running rather than trying to compile and boot a new kernel on an already-broken system based on 2.6.14 as you tried below?
...
...
swapon / swapoff
You can use it on files too. (Also see mkswap - not that I think you need it here, though).
Do you have an /etc/rc.d/rc.sysinit file or similar?
You can see how the bootup shell script uses swapon and the 'mount' command to do stuff (like mounting root dir read-only before going read-write).
If you mean runlevel 1, then is your networking script file ('network') in /etc/rc1.d (or similar) prefixed with a K or an S? On my system it is a 'K' - which means any networking will be killed (an 'S' means it will be started if not already on). Runlevel 1 on my system has a lot of K's and not a lot of S's. (The shell script file that manages changes in runlevels on my system is /etc/rc/rc.d.)
You can start your rc* scripts manually using something like
./XXXnetwork start ( or 'restart')
(in the directory the file is in or just go to init.d). There's also often /sbin/service (in redhat at least)
Also, telinit can be used to change runlevels. (see man page) Might be better to run that than starting up stuff in isolation. However, it looks like all your /etc/rc* scripts are failing to run which probably relates to your mount problem -- really, really not sure..
This may relate to the sysinit file I was mentioning about above (or it may not).
There is a cryptic note in my sysinit file saying that contrary to standard usage, file systems are NOT unmounted in single user mode. Anyway, this hints to the fact that changing runlevels may not only change the services but may possibly also change what is mounted.
Only other things I can think of are:
mount -a
will try to mount everything in fstab.
mount -a -t no<comma-list of file system types>
will mount all available systems except those types that come after 'no'. You might see stuff like that in your sysinit file.
Check /etc/mtab to see what was mounted at startup and any other invocations of 'mount' that you ran after that.
Check /proc/mounts to see mounts...
Dumb question: you did start it? (as per a previous comment above).
Are your interfaces up? (ifconfig)
You really sure you can't resurrect your old system?I found I had a kernel problem after trying to install dependencies for
'scribes' in succession when on reboot
I could not get back into my 2.6.5 linux drive.An early error message was ..
Error inserting genrtc
(lib/modules.2.6.5-1-686/kernel/drivers/char/genrtc.ko): Device or
resource busy.
/etc/init.d/syslog start
.. and later
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
Are you sure there is no way you could get 2.6.5 back up and running rather than trying to compile and boot a new kernel on an already-broken system based on 2.6.14 as you tried below?
...
After a bit of fiddling with /etc/lilo.conf I finally manged to boot
into my own drive with the following messages
which I reproduce manually in some detail in the hope that they mean
something to someone ..
---------------------------------------------------------------------------------------------------------------------------------------
Not running depmod because /lib/modules/2.6.14 is not writable
Loading modules ..
grep: error while loading shared libraries libpcre.so.3: cannot open
shared object file: No such file or directory
FATAL: Could not load /lib/modules/2.6.14/modules.dep: No such file or
directory
Creating device-mapper files
[screen moves .........]
/etc/rc5.d/S19autofs: line33: basename: command not found
.......
...
Debian GNU/Linux testing/unstable Tux tty1
Tux login: adam
Password:
-----------------------------------------------------------------------------------------------------------------
.. so I was in on tty1 at run-level 1
I quickly found that only my Linux root and WinXP partitions were
auto-mounted - both specified in /etc/lilo.conf
- and I had to manually mount all other partitions except swap (which I
could not quite work out how to do).
swapon / swapoff
You can use it on files too. (Also see mkswap - not that I think you need it here, though).
Do you have an /etc/rc.d/rc.sysinit file or similar?
You can see how the bootup shell script uses swapon and the 'mount' command to do stuff (like mounting root dir read-only before going read-write).
Finally,
Tux: /home/adam/linux-2.6.14# make modules_install
if [ -r System.map -a -x /sbin/depmod ] ; then /sbin/depmod -ae -F
System.map 2.6.14; fi
Tux: /lib/modules# ls
0.0.0 2.4.18-bf2.4 2.4.25-1-686 2.6.14 2.6.5-1-686
Tux: /lib/modules/2.6.14# ls
build modules.ccwmap modules.inputmap modules.seriomap source
modules.dep modules.isapnpmap modules.symbols
kernel modules.alias modules.ieee1394map modules.pcimap modules.usbmap
.............
As it now stands, I can boot into WinXP on which this is written and
2.6.14 at will
but the latter is text mode (init 1), I have to mount other partitions
manually,
have no access to the internet preventing a dist-upgrade, and no X-server.
If you mean runlevel 1, then is your networking script file ('network') in /etc/rc1.d (or similar) prefixed with a K or an S? On my system it is a 'K' - which means any networking will be killed (an 'S' means it will be started if not already on). Runlevel 1 on my system has a lot of K's and not a lot of S's. (The shell script file that manages changes in runlevels on my system is /etc/rc/rc.d.)
You can start your rc* scripts manually using something like
./XXXnetwork start ( or 'restart')
(in the directory the file is in or just go to init.d). There's also often /sbin/service (in redhat at least)
Also, telinit can be used to change runlevels. (see man page) Might be better to run that than starting up stuff in isolation. However, it looks like all your /etc/rc* scripts are failing to run which probably relates to your mount problem -- really, really not sure..
/etc/fstab exists and I don't understand why it does not mount all
partitions at start-up.
This may relate to the sysinit file I was mentioning about above (or it may not).
There is a cryptic note in my sysinit file saying that contrary to standard usage, file systems are NOT unmounted in single user mode. Anyway, this hints to the fact that changing runlevels may not only change the services but may possibly also change what is mounted.
Only other things I can think of are:
mount -a
will try to mount everything in fstab.
mount -a -t no<comma-list of file system types>
will mount all available systems except those types that come after 'no'. You might see stuff like that in your sysinit file.
Check /etc/mtab to see what was mounted at startup and any other invocations of 'mount' that you ran after that.
Check /proc/mounts to see mounts...
I have correctly AFAIK set up /etc/init.d/network but there is no
internet connection.
Dumb question: you did start it? (as per a previous comment above).
Are your interfaces up? (ifconfig)
I feel I've achieved something but have not yet arrived at a working system.
Daniel
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
