md kernel panic

[RayBe]

trying to get my md working (asus K8V se deluxe, 1 gig, amd 3200+, connected to 32" crt via component)

what i did:
sudo apt-get update
sudo apt-get upgrade
added my resolution (576i) according to: http://wiki.linuxmce.org/index.php/Custom_Display_Resolutions
changed /usr/pluto/bin/nvidia-install.sh to:http://svn.linuxmce.org/trac.cgi/changeset/23588 and http://svn.linuxmce.org/trac.cgi/changeset/23635
executed /usr/pluto/bin/Diskless_CreateTBZ.sh

and then let the md pxe-boot without interfering and in the end i get:

[ 94.348339] kernel panic - not syncing: Attempted to kill init!

also it still seems to install nvidia 173 driver, don't know how or why.

don't know how to proceed,
could anybody help me out on this one?

br,
Raymond

[l3mce]

What video card are you using?

I would also crush the wifi onboard.

[RayBe]

hi l3mce,

thanks for replying,
i use a nvidia 6600gt agp card and have no wifi-card installed

br,
Raymond

[l3mce]

I believe that board has wifi on-board. It has caused kernel panic before for me.

The 173 driver is being loaded because you have a pre7xxx series card.

* I see I am mistaken, and it just has a proprietary wifi adapter, and one of the models comes with that installed.

I would still creep around the bios and turn off pretty much anything you know you will not be using (ie, cool and quiet... make sure that the chip which the wifi plugin at the end of the board uses is off etc).

[RayBe]

Thanks for your input, i will look into it.
Couldn't it be that the onboard NIC isn't supported?

Br,
Raymond

[l3mce]

Thanks for your input, i will look into it.
Couldn't it be that the onboard NIC isn't supported?

Br,
Raymond

Yes. Absolutely. I was too lazy to look it up and assumed you had. Disable onboard and plug in one you know works.
Or you can try and fix that one with either sk98lin or skge drivers. It says 3com, but it is actually a Marvell driver written for SysKonnect. Probably just a quick add to a .conf file and rebuild the image...

I am lazy and ignorant though. I would disable it and install a cheapy I know works.


I would think you could CD boot and see how kubuntu handles the NIC, if at all.

[RayBe]

Could it be that the cause of the problem is a not propperly installed bluetooth usb dongle?
I have a Sitecom Micro Adapter Bluetooth 2.1 USB CN-516.
Sometimes the MD does boot up (rarely) and then i notice in the webadmin that the bluetooth dongle did not get configured right and also during bootup i get a black screen indicating that there was a device not installed propperly.

anybody any idea?

br,
Raymond

[l3mce]

Could it be that the cause of the problem is a not propperly installed bluetooth usb dongle?
I have a Sitecom Micro Adapter Bluetooth 2.1 USB CN-516.
Sometimes the MD does boot up (rarely) and then i notice in the webadmin that the bluetooth dongle did not get configured right and also during bootup i get a black screen indicating that there was a device not installed propperly.

anybody any idea?

br,
Raymond

I would try booting the MD raw, with nothing plugged in... only plugging in devices after the setup wizard had rooms setup... if you have not already done so.