FitPC first generation

Help with booting MiniMyth

Moderator: Pablo

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

FitPC first generation

Post by jbassett » Tue Sep 15, 2009 11:13 am

Hello

The boot process proceeds until it attempts to load the sound driver (seems the FitPC has a cs5535/cs5536 sound chip). At this point boot up stops and just displays the message:

the audio driver does not appear to be loaded
init failed. check '/var/log/messages' for further details

When I check messages there is no extra info.

lspci output for sound adapter info:

00:0f.3 Multimedia Audio Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] Audio (rev 01)

To try to rectify this I have downloaded the kernel version from kernel.org (2.6.30.4) and used that to build a module for the soundcard. when modprobing this I get:

FATAL: Error inserting snd_cs5535audio (/lib/modules/2.6.30.4/kernel/sound/pci/snd-cs5535audio.ko): Unknown symbol in module, or unknown parameter see dmesg)

DMESG states:

snd_cs5535audio: unknown symbol __tracepoint_kmalloc
snd_cs5535audio: unknown symbol kmalloc_caches

Any help greatly appreciated.

Thankyou

Jason
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Tue Sep 15, 2009 4:31 pm

Another thought:

I may be way out here, but would I stand more chance of my module loading if I compiled it using the same configuration for the kernel that was used to build the actual kernel in use on the 2.6.30.4 release of Minimyth?

In which case, I would need the .config file for the kernel build? Where would I obtain this?

Jason
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: FitPC first generation

Post by Pablo » Tue Sep 15, 2009 4:53 pm

I have added the sound module to the MiniMyth. The change has been committed to SVN and will be in the next build.

There are two problems that you might encounter when trying to build an ALSA module: (1) you may not be using a compatible kernel configuration and (2) you may not be compiling a compatible ALSA driver. The reason for (2) is that MiniMyth uses the out-of-tree ALSA drivers when possible because they are more current.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Tue Sep 15, 2009 5:25 pm

That was damn quick, thankyou!

This is why I love Open Source.
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: FitPC first generation

Post by Pablo » Thu Sep 17, 2009 6:13 am

The latest test version 0.21.0-70b3 contains the changes. Could you give it a try and let me know whether or not get any further?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Mon Sep 21, 2009 4:16 pm

Finally got around to testing this out after being away the weekend. I carried out the same procedure as with the old version, but now I am getting the following message at boot time:

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

J
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: FitPC first generation

Post by Pablo » Mon Sep 21, 2009 4:26 pm

jbassett wrote:Finally got around to testing this out after being away the weekend. I carried out the same procedure as with the old version, but now I am getting the following message at boot time:

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

J
This sounds as though the initrd (root file system) is being truncated/corrupted.
What method are you using to boot?
Does the screen show that the initrd is being transferred?
What is your boot line? In particular, does it have ramdisk_size=96000?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Mon Sep 21, 2009 6:06 pm

Fixed that issue. Had some files in wrong location.

Now it says:

Unmatched (in regex: marked by <-- HERE in m/^(<--HERE PAL(-(MIN)?|NTSC-(443|J"M)
init failed. check '/var/log/messages' for further details

J

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Mon Sep 21, 2009 6:19 pm

Using MM_X_DRIVER='geode' almost gets me into X. It has stopped on the blue boot up screen stating "Starting X...".

On the plus side, from console, echoing to /dev/dsp does create noise and the kernel modules are loaded for the sound system.

J
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Tue Sep 22, 2009 12:02 am

UPDATE:

I am able to telnet into the minimyth frontend and as root I execute "Xorg" which brings up a solid black screen on the client. I then execute "xinit" as minimyth user which causes a X to appear on the screen. Running mythfrontend from the telnet session causes mythfrontend to load but it states:

"Cannot find (ping) database host 172.16.1.180 on the network".

So, it does load X, only not automatically at boot time, but mythfrontend cannot see my backed. I do have another frontend running fine from my Macbook so the backend seems to be configured correctly.

Using the telnet session, "ping: icmp open socket: Operation not permitted" is the response of a ping to anything on or outside of my network. ifconfig shows the correct ip of 172.16.1.50 though.

EDIT: Had to turn off the 'check for ping' setting to get mythfrontend to load properly. Seems root was able to use ping but minimyth user was not. Still not loading X at boot automatically though, I have to telnet in to start X and mythfrontend.

J
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: FitPC first generation

Post by Pablo » Tue Sep 22, 2009 1:17 am

In order to help figure out why it is not auto-configuring the geode driver, could you post the output of

Code: Select all

lspci -mn
Your problems with Xorg and ping sound like the these applications are not suid. This usually happens when the NFS tarball was not extracted as root. Are you using the NFS tarball.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Tue Sep 22, 2009 6:02 pm

Hello

Yes I am using NFS tarball, but I extracted this as root (I am in the bad habit of doing everything as root except surfing and letter writing).

lspci -mn output:

00:01.0 "0600" "1022" "2080" -r33 "1022" "2080"
00:01.1 "0300" "1022" "2081" "1022" "2081"
00:01.2 "1010" "1022" "2082" "1022" "2082"
00:0d.0 "0200" "10ec" "8139" -r10 "10ec" "8139"
00:0e.0 "0200" "10ec" "8139" -r10 "10ec" "8139"
00:0f.0 "0601" "1022" "2090" -r03 "1022" "2090"
00:0f.2 "0101" "1022" "209a" -r01 -p80 "1022" "209a"
00:0f.3 "0401" "1022" "2093" -r01 "1022" "2093"
00:0f.4 "0c03" "1022" "2094" -r02 -p10 "1022" "2094"
00:0f.5 "0c03" "1022" "2095" -r02 -p20 "1022" "2095"

J
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: FitPC first generation

Post by Pablo » Wed Sep 23, 2009 4:47 am

jbassett wrote:Hello

Yes I am using NFS tarball, but I extracted this as root (I am in the bad habit of doing everything as root except surfing and letter writing).
Do ping and Xorg show up as suid?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

jbassett
Member
Posts: 21
Joined: Tue Sep 15, 2009 10:44 am
Location: Thurrock, Essex, England
Contact:

Re: FitPC first generation

Post by jbassett » Wed Sep 23, 2009 1:06 pm

No they were not showing suid, I have since set suid and X and mythfrontend are now appearing and the menu is usable. Now when I select a recording or live tv, I get thrown out of mythfrontend and and get the following messages:

Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
2009-09-23 13:05:09.262 VideoOutputXv: XVideo Adaptor Name: 'AMD Geode LX'
mythfrontend: Fatal IO error: client killed
mythfrontend: Fatal IO error: client killed
Segmentation fault
[1] + Killed Xorg
Corrilan IT Consultancy Ltd
http://www.corrilan.com
01375 403508
enquiries@corrilan.com

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: FitPC first generation

Post by Pablo » Thu Sep 24, 2009 1:30 am

I believe the best thing is to first figure out why SUID was broken. There are other programs that are SUID. In addition, there are some static device nodes that are created. If the reason for the SUID failure was lack of root access (the only cause I have seen so far), then none of the programs requiring SUID would be SUID and none of the static device nodes would have been created.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

Post Reply