Amahi Server won't (re)boot after install (weird error msg)

[hec1152]

Hi,

I'm trying to bring up standalone Amahi server per instructions on website. I've successfully done this under Virtualbox so I'm well practiced at running thru all the steps. After a routine install when everything went flawlessly, I came to the end for the reboot before going into the finished installation. For reasons unknown during reboot, the machine hangs (reproducible) with the following error message:

Welcome to Fedora
Starting udev:modprobe:FATAL: Error inseting CX88-dvb (lib/modules/2.6.35.6-45.fc14.i386/kernel/drivers/media/video/cx88-dvb.ko): No such device

Where do I go from here?

Thanks in advance
HEC

[hec1152]

After looking at this for a while and with the aid of Google I think I found the source of the problem. Turns out the PC I was using had a TV card in it from the previous installation. When I removed that and reinstalled Fedora, etc. I got past the start of the reboot up. But it still won't boot up. Now it stops shortly after this message

ip6tables: Applying firewall rules: modprobe: FATAL: Error inserting ipv6 (lib/modules/2.6.35.6-45.fc14.i686/kernel/net/ipv6/ipv6.ko): Cannot allocated memory

There are a sequence of other messages after this before everything stops at:

Bringing up interface eth0 [OK]

After this, pressing Esc results in a loop thru the above error message sequence.

I'm not enough of a Linux guru to figure this one out. But I will look on Google and hopefully someone will come to my aid.

[radioz]

Do you have a TV card installed?
It sounds like some type of device driver problem.
Try installing the system without the card installed and then install it later.

[hec1152]

There's no TV card when this message occured. Had that problem in another circumstance but removed it and now I have this problem. Only aftermarket card in the system is generic Soundblaster. Nothing else.

This is frustrating as I've done everything I can think of here to include running in Virtualbox VM (similar configuration). But I can't seem to get to the point where I can really use Amahi because of this problem. Out of ideas and options to try, so I'd appreciate some suggestions.

[hec1152]

There's no TV card when this message occured. Had that problem in another circumstance but removed card and now I have this problem instead. Only aftermarket card in the system is generic Soundblaster. Nothing else.

This is frustrating as I've done everything I can think of here to include running in Virtualbox VM (similar configuration). But I can't seem to get to the point where I can really use Amahi because of this problem. Out of ideas and options to try, so I'd appreciate some suggestions. (runs in VM okay but have a problem with that which I've posted in networking section. Decided not to bother with that but instead to use on standalone machine and put into 24x7 operation on my home network. But this problem precludes that).

[radioz]

Take a look at /var/log/messages to see if there were any earlier errors.
What type of network card do you have?

(Sorry for my last post, I must have not refreshed my screen before responding to your earlier post)

[hec1152]

Hate to show my ineptitude but I'm not enough of a Linux user to figure out how to do this. Problem is that I need to access the hard drive with the installation to get to the /etc directory and look at it's contents per your suggestion but I can't do that since the system won't boot. Thought I was competent enough to boot from Live Knoppix CD and then find only hard drive attached, mount it, and access it, but I seem to have overestimated my capabilities as I can't seem to get to the drive. How would you recommend I do this? I can boot up into Knoppix (or any Live CD) and have access to the hard drive if only I know what Linux commands to use to find my way around. I'll keep working on this to see the obvious, but in case I'm still stuck when you read this, I would appreciate a little guidance.

EDIT: tried to see error messages as Amahi system tried to boot off hard drive. Looks like the first error message is right after the mounting of local file systems occurs ok. First indication of error message is the one I posted above about ip6tables..... System just seems to loop early in process of mounting the filesystems after displaying the above message. Not much of interest after that since the same set of messages sequences starting with Checking File Systems just loops. Not much help.

[hec1152]

I'm not sure this is right, but I've managedto get recovery CD working using Fedora. So now I can see what I guess are the partitions created by Amahi install one of which is "vg_amahi-lv_root". The recovery CD system has that mounted as /mnt/sysimage. When I look inside that I can find the var directory but it contains no logs subdirectory. Nor can I find any trace of the messages file. Only thing under /root is .bash_historyand .profile FWIW. So now I'm really confused else I don't know where I am in Amahi's directory/partition structure. Anyway, I'm over my head now but at least I think I can get to system drive using Bash command line from Fedora Recovery console. Now what?

[radioz]

What is the output of 'ls /mnt/sysimage/var' ? That should be the /var from your installation.

And then 'ls -lrt /mnt/sysimage/var/log'. Lets see whats is in that directory in time-sorted order.

[hec1152]

okay. This is what shows when I move to the sysimage/var/log and then issue 'ls -lrt'

Jun 16 ppp
Jul 14 prelink
Jul 21 bittorrent
Sep 17 cups
Oct 1 ntpstats
Oct 4 sssd
Dec 26 tallylog
Dec 26 samba
Dec 26 spooler
Dec 26 mail
Dec 26 lastlog
Dec 26 anaconda.syslog
Dec 26 anaconda.log
Dec 26 anaconda.xlog
Dec 26 anaconda.yum.log
Dec 26 anaconda.storage.log
Dec 26 ConsoleKit
Dec 26 wpa_supplicant.org
Dec 26 greyhole.log
Dec 26 maillog
Dec 26 Xorg.9.log
Dec 26 gdm
Dec 26 pm-powersave.log
Dec 26 audit
Dec 26 setroubleshoot
Dec 26 yum.log
Dec 26 hda-updates.log
Dec 26 cron
Dec 26 httpd
Dec 26 passenger-analytics
Dec 26 mysqld.log
Dec 26 Xorg.0.log
Dec 26 dmesg.old
Dec 26 btmp
Dec 26 dmesg
Dec 26 secure
Dec 26 boot.log
Dec 26 messages
Dec 26 wtmp

I looked at messages file and dmesg file via 'More'. Too much stuff although I could see discovery of hard files, usb devices (e.g. mouse), soundcard, etc but nothing that I could identify in all the messages as an obvious error message or anything informative. Guess I just don't know what I'm looking for.

One thing I did try was to turn off the ip6tables in the rescue setup since the error messages seem to involve that. Didn't really help except that looping stop and machine eventually just hung. Again, I'm not sure I know what I'm really doing but just thought I'd note that.

P.S. I'm doing all this from Rescue mode booted off Fedora DVD. Running commands in bash shell.

What now?