Beiträge von pumo

BIG thanks Bistr-o-math it works with setting that you gave !!
I didn't notice different bios, but it doens't matter it works now
I am just curious but why I didn't see MS-6340 in nvram-wakeup-mb.c file ?

it "almost" works, minutes and seconds go right but everything else resets to default settings (I mean whole bios)
I use nvram-wakeup 0.97

[root@localhost root]# cat guess-directisa/guess-error.log
$Id: guess.c,v 1.22 2004/03/04 08:38:14 bistr-o-math Exp $
Opened file 31.23.59.59+ readonly...
Opened file 11.12.13.14+ readonly...
Opened file 01.00.00.00+ readonly...
Opened file 01.00.00.00- readonly...
Couldn't read byte 0x80 from 31.23.59.59+
Assuming size of files 128 bytes
guess: Opening /dev/mem in O_RDONLY mode...
guess: _DMI_ table found: base: 0xF0800, size: 0x3A2, count: 32
guess: data block   1 at offset 0x000: type   0, size 0x013 ( 19)
guess: found string "Award Software International, Inc."
guess: found string "6.00 PG"
guess: found string "01/14/2002"
guess: data block   2 at offset 0x04A: type   1, size 0x019 ( 25)
guess: data block   3 at offset 0x092: type   2, size 0x008 (  8)
guess: found string "MICRO-STAR INTERNATIONAL CO., LTD"
guess: found string "MS-6340(VT8363)"
guess: found string ""
guess: data block   4 at offset 0x0D1: type   3, size 0x00D ( 13)
guess: data block   5 at offset 0x0E7: type   4, size 0x020 ( 32)
guess: data block   6 at offset 0x121: type   5, size 0x014 ( 20)
guess: data block   7 at offset 0x137: type   6, size 0x00C ( 12)
guess: data block   8 at offset 0x14B: type   6, size 0x00C ( 12)
guess: data block   9 at offset 0x15F: type   7, size 0x013 ( 19)
guess: data block  10 at offset 0x182: type   7, size 0x013 ( 19)
guess: data block  11 at offset 0x1A5: type   8, size 0x009 (  9)
guess: data block  12 at offset 0x1BD: type   8, size 0x009 (  9)
guess: data block  13 at offset 0x1D7: type   8, size 0x009 (  9)
guess: data block  14 at offset 0x1E7: type   8, size 0x009 (  9)
guess: data block  15 at offset 0x1F8: type   8, size 0x009 (  9)
guess: data block  16 at offset 0x209: type   8, size 0x009 (  9)
guess: data block  17 at offset 0x21A: type   8, size 0x009 (  9)
guess: data block  18 at offset 0x22F: type   8, size 0x009 (  9)
guess: data block  19 at offset 0x250: type   9, size 0x00D ( 13)
guess: data block  20 at offset 0x262: type   9, size 0x00D ( 13)
guess: data block  21 at offset 0x274: type   9, size 0x00D ( 13)
guess: data block  22 at offset 0x286: type   9, size 0x00D ( 13)
guess: data block  23 at offset 0x298: type   8, size 0x009 (  9)
guess: data block  24 at offset 0x2A8: type  13, size 0x016 ( 22)
guess: data block  25 at offset 0x2F9: type  16, size 0x00F ( 15)
guess: data block  26 at offset 0x30A: type  17, size 0x015 ( 21)
guess: data block  27 at offset 0x32F: type  17, size 0x015 ( 21)
guess: data block  28 at offset 0x354: type  19, size 0x00F ( 15)
guess: data block  29 at offset 0x365: type  20, size 0x013 ( 19)
guess: data block  30 at offset 0x37A: type  20, size 0x013 ( 19)
guess: data block  31 at offset 0x38F: type  32, size 0x00B ( 11)
guess: data block  32 at offset 0x39C: type 127, size 0x004 (  4)
guess: Following DMI entries found:
guess:  - Mainboard vendor:   "MICRO-STAR INTERNATIONAL CO., LTD"
guess:  - Mainboard type:     "MS-6340(VT8363)"
guess:  - Mainboard revision: ""
guess:  - BIOS vendor:        "Award Software International, Inc."
guess:  - BIOS version:       "6.00 PG"
guess:  - BIOS release:       "01/14/2002"
    checking 0x3F: 0x3B 0x0E 0x00 0x00
    checking 0x40: 0x3B 0x0D 0x00 0x00
    checking 0x41: 0x17 0x0C 0x00 0x00
    checking 0x47: 0x30 0x30 0x30 0x10
    checking 0x51: 0x1F 0x0B 0x01 0x01
    checking 0x6E: 0xE3 0x69 0x38 0x18
Couldn't guess checksum addresses (out of 0).

and nvram-wakeup.conf :

################################################
##  Mainboard autodetection information:
##
##    - Mainboard vendor:   "MICRO-STAR INTERNATIONAL CO., LTD"
##    - Mainboard type:     "MS-6340(VT8363)"
##    - Mainboard revision: ""
##    - BIOS vendor:        "Award Software International, Inc."
##    - BIOS version:       "6.00 PG"
##    - BIOS release:       "01/14/2002"


addr_sec         = 0x3F
addr_min         = 0x40
addr_hour        = 0x41
addr_stat        = 0x47
shift_stat       = 5
addr_day         = 0x51
addr_stat        = 0x6E   # but differs somewhere else
shift_stat       = 5

sorry writing english but I don't speak german,
dbox.network have allready added it to CVS ?
or could I get nvram-wakeup-mb.c file ?
I have MSI MS-6340 motherboard and I ran guess-helper and nvram just mess my bios setting so it loads defaults...

I did try that recording.c from here, it didn't compile, but I did check same file in my VDR machine. And now it works !!

I did these changes, commented lines which follows text THIS from line 708 to line 755, there is one return false, but it wasn't commented in file that found here.

bool cRecordings::ScanVideoDir(const char *DirName)
{
  DIR *d = opendir(DirName);
  if (d) {
     struct dirent *e;
     while ((e = readdir(d)) != NULL) {
           if (strcmp(e->d_name, ".") && strcmp(e->d_name, "..")) {
              char *buffer;
              asprintf(&buffer, "%s/%s", DirName, e->d_name);
              struct stat st;
              if (stat(buffer, &st) == 0) {
                 if (S_ISLNK(st.st_mode)) {
                    free(buffer);
                    buffer = ReadLink(buffer);
                    if (!buffer)
                       //return false;   THIS
                    if (stat(buffer, &st) != 0) {
                       LOG_ERROR_STR(DirName);
                       //return false;   THIS
                       }
                    }
                 if (S_ISDIR(st.st_mode)) {
                    if (endswith(buffer, deleted ? DELEXT : RECEXT)) {
                       cRecording *r = new cRecording(buffer);
                       if (r->Name())
                          Add(r);
                      else
                          delete r;
                       }
                    else if (!ScanVideoDir(buffer))
                       return false;
                    }
                 }
              else {
                 LOG_ERROR_STR(DirName);
                 //return false;   THIS
                 }
              free(buffer);
              }
           }
     closedir(d);
    }
  else {
     LOG_ERROR_STR(DirName);
     //return false;   THIS
     }
  return true;
}

i did compile :
make NO_KBD=1

and my /video directory is on mounted from my linux servers NFS mount.

is it a bug or what might be wrong, when shutting down vdr machine it loses older all recordings from list.
I checked and recordings exist in /video -directory.

My installation is:
- vdr 1.3.11 with vdr-1.3.11-enAIO-1.3.diff.gz and - - - -
- vdr-1.3.11-subtitles-0.3.3-and-ttxtsubs-0.0.5.diff.gz patches.
- dxr3 plugin 0.23pre1 with uncommented usleep
- text2skin 0.7
- DVB subtitles 0.3.3

nova-t card and hollywood+

Zitat

Original von Austrian Coder
You have to uncomment the 2 usleeps in file "dxr3outputthread".
Remove"// " before the "usleep" entries.

To this and you will be happy

Thanks guys !
it works
I haven't even try yet with em8300 cvs version, and I don't know should I repair working version...
now there is em8300 driver version 0.14+dvb 1.1.1+ vdr 1.3.11 +vdr-dxr3plugin 0.23pre1

Hello, I will try by evening when I get home.
But I will report then
pre1 what I did try was here:
http://www.vobs.at/hs-wolfurt/…n/vdr-dxr3-0.2.3-pre1.tgz

i am using fedora core1 with 2.4.22ntpl kernel, dvb card is hauppauge nova-t.

I installed 1.3.11 because 1.2.6 has very slooow channel change,with dxr3 plugin 0.23pre1 (0.22 didn't turn at all) and dvb driver 1.1.1 but it it horrible, vdr take 99% CPU (with 1.2.6 3-5%) and picture was like 1fps. radio channel runs almost fine CPU 30%. Channels do change fast.

Reason maybe em800 driver 0.14 ?
cvs drivers doesn't install and I get same error like here:

http://www.vdr-portal.de/board/thread.php?threadid=17185&sid=

but I don't speak german at all and with babelfish i translated it in english and remove old em8300.h and copied new from cvs version -> same error...

Yesterday I tested many times to upgrade 1.2.6 with elchi 4d and OSD did disappear. and I got it work when installed vdr 1.26 again.

I also tried 1.3.11 with dxr3 plugin 0.23pre(0.22 didn't turn at all) and dvb driver 1.1.1 but it was horrible, vdr take 99% CPU and picture was like 1fps.
Reason maybe em800 driver ?

thanks UFO !
I did make vdr with no_kpd=1 and remote=lirc
and I did install newest lirc 0.7 pre4, so now it works!

little disapoitment with channel change, when I get used to fast channel zap with my satellite box dreambox (also linux).

but is reason for slow zap, is it hollywood+ ?

yes KBD ofcourse...
but it even doesn't take key presses from keyboard...
How do I disable keyboard support ?

Zitat

Original von UFO

That's fine. So it should basically work.
Which version of the remote plugin are you using?

vdr-remote-0.3.1.tgz

Zitat

Original von UFO
Please remove all remote-event0 entries (if any) from remote.conf and restart vdr.
If vdr does not run as root, check the permission settings of /dev/input/event0.

CU
Oliver

i did remove, i did try also move whole file other place and start vdr but allways when it starts first start "Learning Remote Control Keys (KBP)" and not (event0) which I get couple times...

edit: also tried ./vdr -Pdxr3 -P"remote -i autodetect"

but it will work ? how?

if I run ./evtest /dev/input/event0 it receives remotecontrols key presses...

my lsmod when dvb drivers loaded:

Module Size Used by Not tainted
ttusb_dec 18823 0 (unused)
dvb-ttusb-budget 23924 0 (unused)
dvb-ttpci-budget-ci 7468 0 (unused)
ttpci-eeprom 2728 0 [dvb-ttpci-budget-ci]
saa7146_vv 42524 0
saa7146 14112 0 [dvb-ttpci-budget-ci saa7146_vv]
mt312 7244 0
cx24110 8228 0
grundig_29504-491 5284 0
grundig_29504-401 6060 0
tda1004x 15376 1
ves1820 6560 0
stv0299 9900 0 (unused)
alps_tdmb7 5384 0
alps_tdlb7 7640 0
ves1x93 6640 0
dvb-core 51488 0 [ttusb_dec dvb-ttusb-budget dvb-ttpci-budget-ci mt312 cx24110 grundig_29504-491 grundig_29504-401 tda1004x ves1820 stv0299 alps_tdmb7 alps_tdlb7 ves1x93]
video-buf 16128 0 [saa7146_vv]
v4l2-common 4864 0 [saa7146_vv]
v4l1-compat 14344 0 [saa7146_vv]
videodev 8288 0 [saa7146_vv]
em8300 44164 0 (autoclean)
adv717x 4064 0 (unused)
i2c-algo-bit 8776 2 (autoclean) [em8300]
i2c-core 19172 0 (autoclean) [adv717x i2c-algo-bit]
soundcore 6500 1 (autoclean) [em8300]
evdev 5792 0
autofs 13236 0 (autoclean) (unused)
e100 55300 1
sg 35852 0 (autoclean) (unused)
scsi_mod 107080 1 (autoclean) [sg]
mousedev 5428 0 (unused)
hid 24356 0 (unused)
input 5824 0 [dvb-ttpci-budget-ci evdev mousedev hid]
usb-uhci 25964 0 (unused)
usbcore 78368 1 [ttusb_dec dvb-ttusb-budget hid usb-uhci]
ext3 70532 2
jbd 51732 2 [ext3]

Hi,
I have installed vdr 1.2.6 with dvb driver 1.1.0 and dxr3.
I can't get hauppauges remotecontrol to work because there is no /proc/av7110_ir

when starting vdr with:
./vdr -Pdxr3 -P"remote i /dev/input/event0"
it just logs /var/log/messages:

Jul 3 17:17:45 vdr vdr[3613]: starting plugin: remote
Jul 3 17:17:45 vdr vdr[3613]: remote-event0: unable to open '/proc/av7110_ir': No such file or directory
Jul 3 17:17:45 vdr vdr[3613]: ERROR: /proc/av7110_ir: No such file or directory

av7110_ir was in proc with dvb 1.0.1 driver, but doesn't regognize hauppauges remote control...

any ideas how I get it work ?