Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About churchnill

  • Rank
    New Here
  1. churchnill

    msec logs

    Would someone mind having a look at these &amp; telling me if i have anything to worry about please?<br />I have altered the way msec runs as i was having trouble accessing my second hard drive without having to put root password in each time, some i understand like the files that have installed from mandriva up dates other bits just confuse me, two files attached<br /><br />Thank you<br /><br />Richard msec1.txt msec0.txt
  2. Cheers, that will do the trick Download & now using thank you very much Richard
  3. Yeah that's that "thingy" i couldn't remember its name :-) It does the job but its to busy for me & mess's with my eyes. the one built in with kaffeine does the job but im looking for a stand alone one thats a bit more configurable than what kaffeine offers as i also use vlc for viewing freeview, but thanks for the reply. Richard
  4. Hi folks Can anyone recommend a TV guide that actually works under Mandriva 2010 apart from that nasty looking java type thingy? I have tried gtvg & gshowtv & no joy with either, i used to use klear on the previous version of Mandriva but that does not work with kde4. the xmltv grabbers do not seem to work correctly, i can grab the data from the console and save the file as xmltv but it never loads correctly always get a error invalid xmltv run from console ive supplied the log gtvg.txt
  5. I am now, ooops, silly me, i thought on reboot mandriva automagically puts new kernel at top of list, but the v4l side of it only goes as far as, from what i can make out the v4l-dvb-kernel-latest etc only patches the kernel, so it is only patching the & not the or the or So now with the defaulted to boot i got my green light on, now just to suss out the scanning. At least i know what's sort of going on, i might stand a fighting chance of getting this box working correctly. Bus 002 Device 003: ID 10b8:0bb9 DiBcom DiBcom USB DVB-T reference design (MOD300) (warm) description: Generic USB device product: MOD3000 BOX vendor: DiBcom SA physical id: 1 bus info: usb@2:1 version: 0.01 capabilities: usb-1.00 configuration: driver=dvb_usb_dibusb_mb maxpower=500mA speed=12.0MB/s I'm glad to be back at this stage & know how & why i couldn't on further reboots, basically me being a plank and nots reading what's in front of my eyes. lsmod as requested casual is attached (sussed it in the end) lsmod.txt
  6. Hi cheers for the reply Yeah i did realise they where firmware but i get my wordings mixed, knew i done it just couldn't be bothered to change it as i thought everyone would know what i meant lol sorry for my laziness :-) sometimes call the firmware drivers as well, i am easily confused, its because i am a blonde and that's my excuse. Yup i got the plf repository and also have both those two firmwares in lib/firmware, also have dvb-firmware-usb installed, but alas still no joy, what is bugging me is the fact after i installed the v4l-dvb-testing-kernel-desktop-latest and rebooted the usb box was picked up & green light came on, so firmware was loaded but didn't scan correctly, but since shutting down and rebooting today it is not being detected again and has gone back to the old ID's etc in my original post, its not making a lot of sense, well to me at least :-)
  7. After rebooting, i tried several kernels that are installed and box not lighting up no more, that v4l-dvb- kernel seems to gone walk abouts [richard@localhost ~]$ rpm -qa|grep kernel nvidia96xx-kernel-desktop586-latest-96.43.13-1.20091209.7mdv2010.0 lzma-kernel-desktop586-latest-4.43-1.20091209.28mdv2010.0 kernel-desktop586- lzma-kernel- nvidia-current-kernel-desktop-latest-185.18.36-1.20091209.4mdv2010.0 hsfmodem-kernel- broadcom-wl-kernel-desktop586-latest- squashfs-lzma-kernel- kernel-desktop- squashfs-lzma-kernel-desktop586-latest-3.3-1.20091209.11mdv2010.0 nvidia173-kernel-desktop586-latest-173.14.20-1.20091209.7mdv2010.0 rt3090-kernel-desktop586-latest- squashfs-lzma-kernel- nvidia-current-kernel- nvidia96xx-kernel- v4l-dvb-testing-kernel-desktop-latest-0-1.20091024.0.hg12407.1mdv2010.0 psb-kernel- hsfmodem-kernel- nvidia96xx-kernel- broadcom-wl-kernel- nvidia173-kernel- vboxadditions-kernel- slmodem-kernel- kernel-firmware-20090604-4mnb2 lzma-kernel- kernel-desktop586-devel-latest- kernel-desktop586-devel- fglrx-kernel- nvidia-current-kernel- broadcom-wl-kernel- kernel-desktop586-devel- vboxadditions-kernel-desktop586-latest-3.0.8-1.20091209.1mdv2010.0 fglrx-kernel-desktop586-latest-8.650-1.20091209.1mdv2010.0 kernel-desktop- madwifi-kernel- madwifi-kernel- kernel-desktop586-latest- hcfpcimodem-kernel-desktop586-latest-1.19-1.20091209.1mdv2010.0 psb-kernel-desktop586-latest-4.41.1-1.20091024.4mdv2010.0 kernel-firmware-extra-20090723-1mnb2 slmodem-kernel-desktop586-latest-2.9.11-1.20091209.0.20080817.4.1mdv2010.0 v4l-dvb-testing-kernel- hcfpcimodem-kernel- nvidia-current-kernel-desktop586-latest-185.18.36-1.20091209.4mdv2010.0 nvidia-current-kernel- hsfmodem-kernel-desktop586-latest- nvidia173-kernel- rt3090-kernel- squashfs-lzma-kernel-3.3-11mdv2010.0 kernel-desktop586- hcfpcimodem-kernel- fglrx-kernel- slmodem-kernel- nvidia-current-kernel- vboxadditions-kernel- madwifi-kernel-desktop586-latest-0.9.4-1.20091209.4.r4068mdv2010.0 richard@localhost ~]$ cat /boot/grub/menu.lst timeout 5 color black/cyan yellow/cyan gfxmenu (hd0,0)/boot/gfxmenu default 0 title linux kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 resume=UUID=274e5c1e-ec80-47cf-85d5-e212f635246f splash=silent vga=788 initrd (hd0,0)/boot/initrd.img title linux-nonfb kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 resume=UUID=274e5c1e-ec80-47cf-85d5-e212f635246f initrd (hd0,0)/boot/initrd.img title failsafe kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 failsafe initrd (hd0,0)/boot/initrd.img title desktop586 kernel (hd0,0)/boot/vmlinuz- BOOT_IMAGE=desktop586_2.6.31.5-1mnb root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 resume=UUID=274e5c1e-ec80-47cf-85d5-e212f635246f splash=silent vga=788 initrd (hd0,0)/boot/initrd- title desktop586 kernel (hd0,0)/boot/vmlinuz- BOOT_IMAGE=desktop586_2.6.31.6-1mnb root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 resume=UUID=274e5c1e-ec80-47cf-85d5-e212f635246f splash=silent vga=788 initrd (hd0,0)/boot/initrd- title desktop kernel (hd0,0)/boot/vmlinuz- BOOT_IMAGE=desktop_2.6.31.5-1mnb root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 resume=UUID=274e5c1e-ec80-47cf-85d5-e212f635246f splash=silent vga=788 initrd (hd0,0)/boot/initrd- title desktop kernel (hd0,0)/boot/vmlinuz- BOOT_IMAGE=desktop_2.6.31.6-1mnb root=UUID=442cd2cb-53bd-4427-b904-2aac7ac07d62 resume=UUID=274e5c1e-ec80-47cf-85d5-e212f635246f splash=silent vga=788 initrd (hd0,0)/boot/initrd- [richard@localhost ~]$ ls -la /boot total 39452 drwxr-xr-x 3 root root 4096 2009-12-17 13:03 ./ drwxr-xr-x 22 root root 4096 2009-12-17 13:02 ../ -rw-r--r-- 1 root root 440 2009-11-14 20:11 boot.backup.sda lrwxrwxrwx 1 root root 28 2009-12-17 13:02 config -> config- -rw-r--r-- 1 root root 108085 2009-10-23 06:58 config- -rw-r--r-- 1 root root 108018 2009-10-23 05:33 config- -rw-r--r-- 1 root root 108029 2009-12-08 21:26 config- -rw-r--r-- 1 root root 107962 2009-12-08 20:49 config- -rwxr-xr-x 1 root root 623104 2009-11-14 20:11 gfxmenu* drwxr-xr-x 2 root root 4096 2009-12-16 15:32 grub/ -rw------- 1 root root 6214559 2009-12-16 14:37 initrd- -rw------- 1 root root 6217540 2009-11-14 19:56 initrd- -rw------- 1 root root 6214004 2009-12-16 15:32 initrd- -rw------- 1 root root 6219023 2009-12-10 13:48 initrd- lrwxrwxrwx 1 root root 35 2009-12-10 13:48 initrd-desktop586.img -> initrd- lrwxrwxrwx 1 root root 32 2009-12-16 15:32 initrd-desktop.img -> initrd- lrwxrwxrwx 1 root root 32 2009-12-16 15:32 initrd.img -> initrd- lrwxrwxrwx 1 root root 36 2009-12-17 13:03 kernel.h -> /boot/kernel.h- -rw-r--r-- 1 root root 1493 2009-12-16 15:16 kernel.h- -rw-r--r-- 1 root root 1493 2009-12-10 11:32 kernel.h- -rw-r--r-- 1 root root 1493 2009-12-17 13:03 kernel.h- -rw-r--r-- 1 root root 1493 2009-12-16 10:30 kernel.h- -rw-r--r-- 1 root root 172436 2009-10-23 06:58 symvers- -rw-r--r-- 1 root root 172436 2009-10-23 05:33 symvers- -rw-r--r-- 1 root root 172149 2009-12-08 21:26 symvers- -rw-r--r-- 1 root root 172149 2009-12-08 20:49 symvers- lrwxrwxrwx 1 root root 32 2009-12-17 10:54 System.map -> System.map- -rw-r--r-- 1 root root 1272231 2009-10-23 06:58 System.map- -rw-r--r-- 1 root root 1272272 2009-10-23 05:33 System.map- -rw-r--r-- 1 root root 1272219 2009-12-08 21:26 System.map- -rw-r--r-- 1 root root 1272260 2009-12-08 20:49 System.map- -rw-r--r-- 1 root root 256 2009-11-14 20:11 uk-latin1.klt lrwxrwxrwx 1 root root 29 2009-12-16 15:32 vmlinuz -> vmlinuz- -rw-r--r-- 1 root root 2152896 2009-10-23 06:58 vmlinuz- -rw-r--r-- 1 root root 2152480 2009-10-23 05:33 vmlinuz- -rw-r--r-- 1 root root 2152880 2009-12-08 21:26 vmlinuz- -rw-r--r-- 1 root root 2152368 2009-12-08 20:49 vmlinuz- lrwxrwxrwx 1 root root 29 2009-12-16 15:32 vmlinuz-desktop -> vmlinuz- lrwxrwxrwx 1 root root 32 2009-12-10 13:48 vmlinuz-desktop586 -> vmlinuz- Just tried running this root@localhost richard]# urpmi v4l-dvb-testing-kernel-desktop-latest Package v4l-dvb-testing-kernel-desktop-latest-0-1.20091024.0.hg12407.1mdv2010.0.i586 is already installed Sorry about long post was not sure how to upload the .txt files
  8. I just went into the grub menu to have a look & there is no v4l-dvb kernel mentioned at all, although i did download and install from command line with urpmi v4l-dvb-testing-kernel-desktop-latest & on reboot its picked up the box although the box does not scan correctly it is lighting up, so firmware is being loaded. this is strange is it not? No mention of the v4l-dvb-testing-kernel-desktop-latest in the grub, but that don't explain how the box now lights up? It also told me there where no proprietary drivers for my nvidia card on reboot which also indicated that i had booted into the new kernel, but alas no mention of the new kernel with uname -r There is also no mention in the grub menu. Im more confused now than when i started, what with the usb box being a dodgy one with its id's but alas it would seem people have got it running so will do some research this evening, couldn't get any done yesterday in the end & now with this mystery with the kernel.
  9. Well what a bag of worms this has thrown up :-) OK, ran urpmi v4l-dvb-testing-kernel-desktop-latest and all went ok, rebooted to new kernel, one warning on reboot in to new kernel regarding nvidia drivers but thats not relevant but apart from that it rebooted into the new kernel with the green light on the usb box lit up, all excited i first done a lsusb to check ID 10b8:0bb9 DiBcom DiBcom USB DVB-T reference design (MOD300) (warm) Which i didn't think to much about as i knew this box was a problematic with its Id's according to linuxtv so i thought have a look at what driver it loaded up with lshw usb description: Generic USB device product: MOD3000 BOX vendor: DiBcom SA physical id: 1 bus info: usb@2:1 version: 0.01 capabilities: usb-1.00 configuration: driver=dvb_usb_dibusb_mb maxpower=500mA speed=12.0MB/s So i thought all looks good except it was not the module i was expecting to see, i as expecting to see one of either of these dvb-usb-dibusb- dvb-usb-dibusb-an2235-01.fw So next up is to run w_scan, which runs with no errors but on the same token it doesn't lock onto any channels, tried kaffeine scan and the snr meter doesn't move & signal strength doesn't move. I must point out i also have another usb stick dvb-t that i use, i took the aerial lead from back of that and put into usb box so i know there is not a issue with any cables or connections as they already work with other usb stick. But i am trying to get another dvb-t tuner on here so i can record & watch different channels. Back to the kernel then, i assumed this kernel had faulty enabled but alas not richard]# cat /boot/config-`uname -r` | grep -i faulty # CONFIG_MD_FAULTY is not set # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set but then has it loaded the right kernel? i expected it to be named v4l-dvb-testing-kernel-desktop-latest $ uname -r Anyways its one step closer than it was yesterday, so still hope yet. Any ideas anyone? Start a new thread? I'm off to do some searching & researching, in the mean time if anyone has the answer please do tell :-) Cheers folks Richard
  10. Thanks for the replies folks, I did check the kernel config yesterday and it is not set but ran the code just to be sure cat /boot/config-`uname -r` | grep -i faulty # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set That is using the kernel uname -r tux99, that is something i would love to have a go at is build a customized kernel, but alas i am not brave enough to try that one out not unless i got someone to walk me through it, i wouldn't mind if i had a spare box that i could try on my own so it wouldn't matter if i cocked up but both boxes have a lot of data i can ill afford to lose, not that i expect i would lose any data as i am all backed up to another external hard drive. I think for the moment i best try ianw1974 & david's option of trying a different kernel, downloading the latest v4l dvb testing kernel desktop latest, will let ya all know how it goes later today. Although im still open to do a kernel recompile or what ever needs to be done to change the option in the kernel im using if its at all possible even and if someone could either point me in the right direction of a howto or any one willing to write up a howto specfic for a mandriva install? Just a thought, trying to expand myself, but never really found any howto's on kernels & config, compiling,recompiling etc etc that i could find easy & straight forward to follow or there are always differences between the one im following and what is actually reflected on the system im using. Anyways im home & free in a couple of hours so will get cracking with downloading the latest as described in ianw1974 post. Cheers folks will keep ya updated on how it goes Richard-
  11. Hi folks I never done anything with a kernel before, im used to using the cli and getting in there and getting stuff done but thus far i have yet to attempt anything that incurs editing the kernel or kernel config recompiling kernel. I have mandriva 2010 installed all up-to-date using the My problem is i have purchased a artec t1 dvb-t usb box which i thought was supported "out the box" how wrong was i, turns out after further investigating the box has a dibcom 3000-m b122a dvb chip, panasonic tuner & cypress chip when i plug it in it loads the usbtest module, using lsusb the box is identified as ID 0547:2235 Anchor Chips, Inc. AN2235 EZUSB-FX Microcontroller, which further reading at linuxtv tells me its "broken devices where sold with cold id: 0547:2235 . You will need to enable CONFIG_DVB_USB_DIBUSB_MB_FAULTY in the kernel .config to catch those".http://www.linuxtv.org/wiki/index.php/Artec so now I not sure which firmware it needs although it needs either one of two that I can see, going by the panasonic tuner it uses dvb-usb-dibusb- or if its not that one and it is defo the broken ones it is this firmware dvb-usb-dibusb-an2235-01.fw But i have no clue how to go about doing the kernel edit and keeping all my current settings as well with just those two changes, I dont suppose it is as simple as going into kernel.config and editing? lol no I didn't think so, i do look at the file and saw the bits i need to edit but as it says in the file "DO NOT EDIT" Can some kind soul talk me through it please? Ive read up a lot on doing it but as this is my first ever time and i couldnt find anything directly specific to what i needed to do i sooner have someone guide for my first time please please go on you know you wanna help me out here its xmas its the season to be joyful, no offence to anyone that does not celebrate xmas. Cheers folks, am keeping my fingers crossed ta Richy EDIT- forgot to mention i aslo tried blacklisting usbtest but still loads
  • Create New...