tsw
Members-
Posts
21 -
Joined
-
Last visited
tsw's Achievements
New Here (1/7)
0
Reputation
-
I have tried that. I have even tried deleting my .mozilla/firefox and generating a new profile...still same problem. I have now created 5 new users, Flash and embedded video works without problems for them, but for my primary user still not working. Here is a question: When opening a Flash or embedded video what files do these programs use? I mean there must be a config file somewhere that is read by these programs which is causing this problem. I should also add that I have used this /home partition over a few installations. That is to say I have not formatted this partition. I have tried however to get rid of any old config files but, still this problem remains for the primary user. What the heck is going on? Regards, Thomas
-
I hate to bump this, but nobody has any ideas?
-
Hi All, I am having a strange problem with Flash player and embedded video in Mandriva 2008.1 x86-64. I cannot get this to work as the primary user. Things such as U-tube or really any other video will not play. This all works fine under root, also, I have set up a few other users and there is no problem there either. So it is just me, the primary user, having this problem. I have even moved the primary user's profile of Firefox from user to user to see if maybe there was a problem with the config files or something. However, this is not the problem as Flash player and embedded vids work for all users except the primary user. I really have no idea even where to start looking for an answer. Any help would be greatly appreciated. Regards, Thomas
-
Thanks devries, That did the trick. The kernel compiled without a hitch and the tvcard is working well. In the past, when I would try to customize a kernel, the config would always be messed. Your tip to < type make xconfig, click file, open and go to /boot and select 'config' > was what I always missed. Always did it by hand and missed something important. Thanks again for the time. thomas
-
Thanks for the reply. It seems that this would be a solution, however I have never patched a kernel before and in all honesty have had little luck in compiling a custome kernel. I followed the directions from the post in "tips and tricks" http://www.mandrakeusers.org/index.php?showtopic=4597 for applying a patch, but after applying the patch what the heck am I suppose to do. I have been using linux for about a year now, but this whole kernel business still leaves me feeling like a complete newb. Any suggestions? Thanks in advance, Thomas
-
I have recently purchased a wintvGO card by Hauppauge because i heard that they work very well with Linux. I am guessing that they changed the tuner type because the tuner on my card is not supported by the v4l2 bttv driver. If anyone has this card and has a clue as to how I can configure the module I would appreciate it. thanks in advance Thomas Here are the specs of the card. Model 44981 Rev. E199 Serial #7574860 Tuner Formats: (M/N) Tuner Audio: Mono Video Formats: NTSC ( M 443 ) PAL ( B G H I D K M N NCOMBO ) SECAM ( L L' ) Audio Outputs: External External Inputs: 0 S-Video Inputs: 0 Teletext: Yes (Software) Radio: None Decoder: BT878 Tuner Model: TCL 2002N_5H IR: Blaster EEprom Contents: 84 09 00 04 20 77 00 40 4c 95 73 00 73 05 00 02 84 08 00 06 b5 af 00 00 59 16 95 72 07 70 73 09 0e 7f 73 0a 08 63 72 0b 00 72 0f 03 72 10 01 72 11 00 79 76 less /usr/src/linux-2.6.8.1-12mdk/Documentation/video4linux/CARDLIST.tuner tuner=0 - Temic PAL (4002 FH5) tuner=1 - Philips PAL_I (FI1246 and compatibles) tuner=2 - Philips NTSC (FI1236,FM1236 and compatibles) tuner=3 - Philips (SECAM+PAL_BG) (FI1216MF, FM1216MF, FR1216MF) tuner=4 - NoTuner tuner=5 - Philips PAL_BG (FI1216 and compatibles) tuner=6 - Temic NTSC (4032 FY5) tuner=7 - Temic PAL_I (4062 FY5) tuner=8 - Temic NTSC (4036 FY5) tuner=9 - Alps HSBH1 tuner=10 - Alps TSBE1 tuner=11 - Alps TSBB5 tuner=12 - Alps TSBE5 tuner=13 - Alps TSBC5 tuner=14 - Temic PAL_BG (4006FH5) tuner=15 - Alps TSCH6 tuner=16 - Temic PAL_DK (4016 FY5) tuner=17 - Philips NTSC_M (MK2) tuner=18 - Temic PAL_I (4066 FY5) tuner=19 - Temic PAL* auto (4006 FN5) tuner=20 - Temic PAL_BG (4009 FR5) or PAL_I (4069 FR5) tuner=21 - Temic NTSC (4039 FR5) tuner=22 - Temic PAL/SECAM multi (4046 FM5) tuner=23 - Philips PAL_DK (FI1256 and compatibles) tuner=24 - Philips PAL/SECAM multi (FQ1216ME) tuner=25 - LG PAL_I+FM (TAPC-I001D) tuner=26 - LG PAL_I (TAPC-I701D) tuner=27 - LG NTSC+FM (TPI8NSR01F) tuner=28 - LG PAL_BG+FM (TPI8PSB01D) tuner=29 - LG PAL_BG (TPI8PSB11D) tuner=30 - Temic PAL* auto + FM (4009 FN5) tuner=31 - SHARP NTSC_JP (2U5JF5540) tuner=32 - Samsung PAL TCPM9091PD27 tuner=33 - MT20xx universal tuner=34 - Temic PAL_BG (4106 FH5) tuner=35 - Temic PAL_DK/SECAM_L (4012 FY5) tuner=36 - Temic NTSC (4136 FY5) tuner=37 - LG PAL (newer TAPC series) tuner=38 - Philips PAL/SECAM multi (FM1216ME MK3) tuner=39 - LG NTSC (newer TAPC series) tuner=40 - HITACHI V7-J180AT tuner=41 - Philips PAL_MK (FI1216 MK) tuner=42 - Philips 1236D ATSC/NTSC daul in tuner=43 - Philips NTSC MK3 (FM1236MK3 or FM1236/F) tuner=44 - Philips 4 in 1 (ATI TV Wonder Pro/Conexant) tuner=45 - Microtune 4049 FM5
-
Thanks to everyone who helped with this little problem. It was a bugger. All of the permissions checked out but still did not work. So I decided to try a new kernel. Last night I upgraded to the 2.6.8.rc2 kernel which was a joy all its own (hi memory support, nvidia support, and of course matching kernel source). Once I got that kernel running lm_sensors now works. This is great. Oviously the problem was with the 2.6.3 kernel, perhaps not properely loading procfs/sysfs correctly. In any case it feels good to rejoin the world of apps-working-properly! Thanks again for your time and assistance. tsw
-
I ran those commands and mine looks identical to yours, but still get: [root@gusto tsw]# /usr/bin/sensors -s it87-isa-0290: Can't access procfs/sysfs file for writing; Run as root? And when "sensors" ran I get this: [root@gusto devices]# sensors it87-isa-0290 Adapter: ISA adapter ERROR: Can't get IN0 data! ERROR: Can't get IN1 data! ERROR: Can't get IN2 data! ERROR: Can't get IN3 data! ERROR: Can't get IN4 data! ERROR: Can't get IN5 data! ERROR: Can't get IN6 data! ERROR: Can't get IN7 data! ERROR: Can't get IN8 data! ERROR: Can't get FAN1 data! ERROR: Can't get FAN2 data! ERROR: Can't get FAN3 data! ERROR: Can't get TEMP1 data! ERROR: Can't get TEMP2 data! ERROR: Can't get TEMP3 data! eeprom-i2c-0-51 Adapter: SMBus Via Pro adapter at 5000 Memory type: DDR SDRAM DIMM Memory size (MB): 512 eeprom-i2c-0-50 Adapter: SMBus Via Pro adapter at 5000 Memory type: DDR SDRAM DIMM Memory size (MB): 512 I do not want to give up on this project, but perhaps it is time. I just do not get it!!!! Thanks for the help tsw
-
Yes, without a doubt. First I 'modprobe -r' the modules. Then 'urpme lm_sensors.' A quick 'updatedb'. Followed by a 'locate lm_sensors' which resultes in: [root@gusto tsw]# locate lm_sensors [root@gusto tsw]# So, to the best of my knowledge all previously installed versions of lm_sensors are always removed before I try either a redo or a different version #. tsw
-
command from console is $ XFdrake. I think coverup is right. The graphics card is not set correctly. Just experienced this my self-- huge screen resolution and all. Once I got the card configured I was able to enjoy my new computer. You should be able to do the same. If your graphics chipset is not supported ( and it might not be if it is new-market ) you should be able to get by using the 'vesa' driver or perhaps the 'vga' driver in the x86 section of XFdrake. For me, my chipset was not supported (via km400) and the 'vesa' driver yeilded average performance. I ended up buying a used nvidia card for like 40 bucks and it works great. good luck tsw
-
Thanks for the post devries. I had already found that stuff and it did not do the trick. I'll keep searching. tsw
-
Yes, this puzzles me as well. The first package I used was the rpm form Mandrake. As you can tell it did not work properely. I also tried to downgrade to version 2.8.6 form the Mandrake repository. Same results. Version 2.8.5 have not found yet. Yeah the whole: [root@gusto tsw]# /usr/bin/sensors -s it87-isa-0290: Can't access procfs/sysfs file for writing; Run as root? I think it the problem but I have no idea what it means. As I wrote before it is not a permissions problem as far as I can tell. A quick check of /var/sys/log did not show much, but I will check again after I get some rest. Here is the meat of my /ect/sysconfig/lm_sensors. Is this correct? # List the modules that are to be loaded for your system # # Generated by sensors-detect on Tue Aug 10 04:19:34 2004 MODULE_0=i2c-viapro MODULE_1=i2c-isa MODULE_2=eeprom MODULE_3=it87 Thanks for the posts folks. It at least gives another direction. tsw
-
Thanks for responding. I have been using Madrake for about a year now and have a pretty good understanding of the basics of linux. That is what is frustrating about this little bugger. A google search for i2c-proc gave me this: http://www.ussg.iu.edu/hypermail/linux/ker...305.3/1639.html It seems that this module is no longer a separate compile option in the 2.6.** kernels. So this leads me to believe that the main problem as to why the program will not respond is this: [root@gusto tsw]# /usr/bin/sensors -s it87-isa-0290: Can't access procfs/sysfs file for writing; Run as root? Since the sensor cannot access the proper files there is no way for it to report what is going on with the machine. I have tried changing permissions for /proc and /sys ( where sysfs is mounted ) however these changes do not take effect. Might you have an idea how I can configure either /proc or /sys to be writable? Thank you, tsw
-
Mandrake 10 official AMD XP2400 machspeed V2MDMP 512 RAM kernel: 2.6.3.7mdk Hello has anyone gotten lm_sensors to work properly with mandrake 10 and the 2.6.3.7 kerenl. I have done suggested steps many times over. Sensors-detect will detect sensors and I copy the lines it asks to copy over to the rc.d files. However, when I run /usr/bin/sensors -s I get this error: [root@gusto tsw]# /usr/bin/sensors -s it87-isa-0290: Can't access procfs/sysfs file for writing; Run as root? I am running it as root by the way. What the f is up? And yes my board and cpu have sensor capabilities. AMD or Machspeed (i forget which company) has a windows monitoring program that came with the set. It seems to work well in windoze, I however do not work so well in windows so I would like to get this figured out. Further, according to the lm_sensors home page the km400 chipsets of the mobo have proven to be supported. From the lm_sensors home page (http://www2.lm-sensors.nu/~lm78/FAQ.txt) I got this information: 4.20 Sensors says 'Can't access /proc file' (release 2.6.0 and later) Did you 'modprobe i2c-proc'? Check 'lsmod'. (release 2.5.5 and earlier) Did you 'modprobe sensors'? Check 'lsmod'. If you did 'sensors -s', did you run it as root? Do you have /proc support in your kernel (is /proc there?) The 2.6.3.7mdk kernel has proc support doesn't it? When I tried to 'modprobe i2c-proc' I get the following error: # modprobe i2c-proc FATAL: Module i2c-proc not found. A urpmi search for file names containing 'i2c-proc' returns a healthy list of 2.4.** kernels: kernel-2.4.25.2mdk kernel2.4-marcelo kernel24-tmb-2.4.25-2.tmb.1mdk etc.... Does this mean that the 'i2c-proc' module is not supported in the mandrake 2.6.** kernels? I really do not have a clue? As you can probably tell. /proc support is enabled in kernel. Then there is also this line that makes no sense to me: Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): YES Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors for initialization at boot time. The file 'prog/init/lm_sensors.init ' is no where to be found on my machine. KSensors is also installed and when ran will read CPU information such as cpu speed, cpu state, and RAM usage, but not CPU TEMP (in which I am most interested) nor will it read CPU VOLTAGE. If anyone has had any success with this program please enlightenment me. I have hit a brick wall. Thanks in advance for any assistance. regards tsw
-
Thanks to everyone who replied. This problem is resolved. It was entirely hardware related. The new motherboard that I installed had a short in it. Amazing what a little misdirected electricity can accomplish. The board was replaced and everything is working as it should. tsw