Page 1 of 2
HELP ?weak or no signal? when turning on TV
Posted: Mon Feb 01, 2010 1:29 pm
by mattberlin
Hi everybody,
My problen is not neccessarily related to SamyGO modifications, but in the same time you guys seem to be the most competent ones and thus maybe able to help me.
I got a LE32B679 (T-CHL6CIPDSEUC). The tv signal comes via DVB-T.
After having been turned off for a longer period (several hours) the TV starts up normally and begins displaying some TV channel. Approximately 30 seconds later the TV stops playing the TV station?s picture and sound. Instead it tells me ?weak or no signal?. Changing the TV stations does not influence this behavior. About 1 minute later the TV returns to normal operation. If the TV is turned off for a short time period only, it starts up as it supposed to.
In the meantime I patched my firmware (0.18) in order to mount some network drives while booting. Basically, the three following scipts are executed. I discovered a strange compartment.
SamyGO.sh
#!/bin/sh
Module="/mtd_rwarea/module"
USB="/dtv/usb/sda1" # USB mount-point
#Enable Telnetd
mount -t devpts devpts /dev/pts
telnetd
sleep 5
#Open back-door for fixing boot-loop situations
sleep 30 # Allow USB stick to settle
if [ -f $USB/usb.sh ];then
sh $USB/usb.sh # USB-File detected
else
#Run normal startup script, if exists
if [ -f /mtd/rw_area/mtd_rwarea.sh ];then
sh /mtd_rwarea/mtd_rwarea.sh
fi
#Run mount script, if exists
if [ -f /mtd_rwarea/premount.sh ];then
sh /mtd_rwarea/premount.sh&
fi
fi
exit
premount.sh
#!/bin/sh
#Mount Virtual USB-Key
insmod /mtd_rwarea/module/dummy_hcd.ko
sleep 5
insmod /mtd_rwarea/module/g_file_storage.ko file=/mtd_rwarea/vusb.image
sleep 5
sh /mtd_rwarea/mount.sh&
exit
mount.sh
USB="/dtv/usb/sda1"
insmod /mtd_rwarea/module/cifs.ko
mkdir -p $USB
mkdir -p $USB/EonMATT
mkdir -p $USB/Fritz
mount -o user=myname,password=1234 -t cifs //192.168.0.2/E $USB/EonMATT
mount -o user=othername,password=12378 -t cifs //192.168.0.1/USBDISKPro-01 $USB/Fritz
echo "[sdd]
Vendor : Linux
Product : Network
Serial : Q80VQLFL
Devpath : 4
Lun : 0
MountDir : /dtv/usb/smb
FileSystem : vfat
">> /dtv/usb/sda1/log
As you can see, the first script starts telnet and then launches the premount script that creates a virtual USB drive. Finally, it launches the mount script. If a USB stick is plugged in, the network drives will be mounted to the USB stick (sda1) and the virtual usb drive (sdb1) will be just there without any use. This is how it normally works.
This morning I turned on the TV with the described behavior above (?no signal or weak signal?). For some reason the virtual usb drive had not been created but the network drives where mounted to the usb stick. This seems a bit odd to me since executing the mount script implies having run the premount script before. But there was no virtual USB device.
This does not really bother me. BUT, might this help us to explain the initial problem where I don?t have a TV signal after having turned on the TV?
Thank?s in advance for your assistance
Re: HELP ?no signal or weak signal? when turning on TV
Posted: Tue Feb 02, 2010 12:03 pm
by mattberlin
Hello again,
today the TV executed the scripts properly during the boot up (Virtual USB drive existant), even though I still had the "no signal or weak signal" message. So, it might have been a coincidence that the two problems appeared in the same time.
Anyway, I'm still stuck with the "no signal or weak signal" thing. So, if anyone of you has an idea, don't hesitate to contribute your thoughts.
Thanks,
Matthias
Re: HELP ?no signal or weak signal? when turning on TV
Posted: Wed Feb 03, 2010 2:34 pm
by erdem_ua
This signal thing is related with your modifications?
Please change older firmware (by menu, after you can switch back without flashing) test it under original FW and watch what it happens.
It might be your Tuner is faulty.
Re: HELP ?no signal or weak signal? when turning on TV
Posted: Wed Feb 03, 2010 9:35 pm
by mattberlin
No, it has been like that since the very beginning. At this time I didn't even know that the modification existed. Before having used dvb-t, the tv was connected to sattelite dish without having had any problems.
Re: HELP ?no signal or weak signal? when turning on TV
Posted: Sun Feb 14, 2010 4:46 pm
by mattberlin
Hi,
today I tried a dvb-c source --> Same problem.
Do you really think that the Tuner might be screwed up?
Re: HELP ?no signal or weak signal? when turning on TV
Posted: Sun Feb 14, 2010 6:03 pm
by erdem_ua
mattberlin wrote:Hi,
today I tried a dvb-c source --> Same problem.
Do you really think that the Tuner might be screwed up?
Yes some thing wrong on your TV. Do you inspect error messages with
dmesg (from shell of your TV linux)?
Anyway, Call technicians... They probably replace the board...
Re: HELP ?no signal or weak signal? when turning on TV
Posted: Sun Feb 14, 2010 6:18 pm
by mattberlin
Code: Select all
<4>[BIF:IN ] ++FSR_BML_Init(nFlag: 0x0)
<4>BML: Registered BML Driver.
<4> --------------------------------
<4> Now we can read /dev/bml0/20 (after=4)
<4>---------------------------------
<4> --------------------------------
<4> Now we can read /dev/bml0/3 (after=0)
<4>---------------------------------
<4>(For Secure boot) app checking thread is created..
<4>(myphj) After generating kernel thread
<4> --------------------------------
<4> Now we can read /bin/authuld (after=0)
<4>---------------------------------
<4>
<4> total read length = 38124
<4> >>> (/bin/authuld) file is successfully authenticated <<<
<4>(0)th waiting.(fd=-2, len=0xfffffff7).
<4>FSR: Registered STL Driver.
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0e)
<4>=================================================
<4> DEVICE NAME: N/A
<4> VERSION: AllInOne-1.0
<4> BUILD DATE: Sep 16 2009 16:08:27
<4>=============== DEVICE INIT START ===============
<4>Osal init success
<4>OsaInitMmap init success
<4>Registered Dbg driver. Major=0xcc27aa80.
<4>Debug init success
<4>MFD init success
<4>Registered AD driver. Major=0xcc27a900.
<4>AD init success
<4>Registered AE driver. Major=0xcc27a840.
<4>AE init success
<4>Registered AIO driver. Major=0xcc27a780.
<4>AIO init success
<4>Tsd init success
<4>Mpeg init success
<4>Registered JPEG driver. Major=0xcc27a480.
<4>Jpeg init success
<4>Incapt init success
<4>Dp init success
<4>GPIO init success
<4>Graphics init success
<4>3D Graphics init success
<4>IR init success
<4>Registered SE driver. Major=0xcb930ce0.
<4>SE init success
<4>PVR Record init success
<4>PVR Playback init success
<4>AVD init success
<4>Sys init success
<4>Ci init success
<4>NRSS init success
<4>
<4>=============== DEVICE INIT DONE ================
<4>SAM_Print Module 0x1 is Enabled, giPrintModule=0x1
<4>SAM_Print Init success
<4>SYS_SET_INITIALIZED_MODULE called
<4>SYS_SET_MEMORYMAP_TABLE called
<4>SYS_SET_SYSTEM_CONFIG called
<4>TsdOpen:the count value is bf4462c0
<4>i2c_master_write: I2C ERR: port 0 write error ================
<4>i2c_master_write: I2C ERR: slave dev 0x4a ================
<4>i2c_master_write: I2C ERR: error status 0x81================
<4>sdp_i2c_ioctl: i2c device start byte not ack
<4>i2c_master_comb_read: I2C ERR: port 0 comb read error ================
<4>i2c_master_comb_read: I2C ERR: slave dev 0xe2 ================
<4>i2c_master_comb_read: I2C ERR: slave not exist or =============
<4>i2c_master_comb_read: I2C ERR: sub address not ack ================
<4>sdp_i2c_ioctl: i2c device start byte not ack
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0d)
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0f)
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,10)
<6>8139too Fast Ethernet driver 0.9.27
<4>PCI: enabling device 0000:00:0a.0 (0140 -> 0143)
<6>eth0: RealTek RTL8139 at 0x6000, 00:12:fb:b3:0d:d8, IRQ 12
<7>eth0: Identified 8139 chip type 'RTL-8100B/8139D'
<6>eth0: link down
<0>usb_fault: version 1.20
<6>usbcore: registered new driver usbfs
<6>usbcore: registered new driver hub
<6>ehci-s5h2x ehci-s5h2x.0: initializing S5H2XXX-SOC USB Controller
<6>ehci-s5h2x ehci-s5h2x.0: S5H2X On-chip EHCI Host controller
<6>ehci-s5h2x ehci-s5h2x.0: new USB bus registered, assigned bus number 1
<6>ehci-s5h2x ehci-s5h2x.0: s5h2x_ehci_setup success
<6>ehci-s5h2x ehci-s5h2x.0: irq 15, io mem 0x30070000
<6>ehci-s5h2x ehci-s5h2x.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
<6>ehci-s5h2x ehci-s5h2x.0: ehci-s5h2x probing completed.
<6>ehci-s5h2x ehci-s5h2x.1: initializing S5H2XXX-SOC USB Controller
<6>ehci-s5h2x ehci-s5h2x.1: S5H2X On-chip EHCI Host controller
<6>ehci-s5h2x ehci-s5h2x.1: new USB bus registered, assigned bus number 2
<6>ehci-s5h2x ehci-s5h2x.1: s5h2x_ehci_setup success
<6>ehci-s5h2x ehci-s5h2x.1: irq 17, io mem 0x30080000
<6>ehci-s5h2x ehci-s5h2x.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb2: configuration #1 chosen from 1 choice
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 1 port detected
<6>ehci-s5h2x ehci-s5h2x.1: ehci-s5h2x probing completed.
<6>ohci-s5h2x ohci-s5h2x.0: S5H2X On-chip OHCI Host controller
<6>ohci-s5h2x ohci-s5h2x.0: new USB bus registered, assigned bus number 3
<6>ohci-s5h2x ohci-s5h2x.0: irq 14, io mem 0x30078000
<6>usb usb3: configuration #1 chosen from 1 choice
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 1 port detected
<6>usb 1-1: new high speed USB device using ehci-s5h2x and address 2
<6>ohci-s5h2x ohci-s5h2x.1: S5H2X On-chip OHCI Host controller
<6>ohci-s5h2x ohci-s5h2x.1: new USB bus registered, assigned bus number 4
<6>ohci-s5h2x ohci-s5h2x.1: irq 16, io mem 0x30088000
<6>usb usb4: configuration #1 chosen from 1 choice
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 1 port detected
<6>usb 1-1: configuration #1 chosen from 1 choice
<6>Initializing USB Mass Storage driver...
<6>usb 2-1: new high speed USB device using ehci-s5h2x and address 2
<6>usb 2-1: configuration #1 chosen from 1 choice
<6>scsi0 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<6>usbcore: registered new driver usb-storage
<6>USB Mass Storage support registered.
<0>rtusb 2870 1.002(1.4.0.0) init --->
<7>
<0>
<0>=== pAd = d30a1000, size = 568816 ===
<0>
<0><-- RTMPAllocAdapterBlock, Status=0
<6>usbcore: registered new driver rt2870
<4>Symbol usb_register_driver is being used by a non-GPL module, which will not be allowed in the future
<4>Please see the file Documentation/feature-removal-schedule.txt in the kernel source tree for more details.
<4>Symbol usb_deregister is being used by a non-GPL module, which will not be al lowed in the future
<4>Please see the file Documentation/feature-removal-schedule.txt in the kernel source tree for more details.
<0>rtusb 0.994 init ====>
<6>usbcore: registered new driver rt73
<5> Vendor: Model: CnMemory Rev: 1100
<5> Type: Direct-Access ANSI SCSI revision: 00
<5>SCSI device sda: 1981440 512-byte hdwr sectors (1014 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 43 00 00 00
<3>sda: assuming drive cache: write through
<5>SCSI device sda: 1981440 512-byte hdwr sectors (1014 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 43 00 00 00
<3>sda: assuming drive cache: write through
<6> sda: sda1
<5>sd 0:0:0:0: Attached scsi removable disk sda
<7>usb-storage: device scan complete
<7>Poller thread started for sda, PID = 429
<3>FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem wil l be case sensitive!
<4><-- RTMPAllocTxRxRingMemory, Status=0
<7>1. Phy Mode = 5
<7>2. Phy Mode = 5
<7>#
<7>3. Phy Mode = 5
<7>MCS Set = ff ff 00 00 01
<7>The UUID Hex string is:<7>bc<7>32<7>9e<7>00<7>1d<7>d8<7>11<7>b2<7>86<7>01<7>0 0<7>12<7>fb<7>2d<7>63<7>00<7>
<7>The UUID ASCII string is:bc329e00-1dd8-11b2-8601-0012fb2d6300!
<4><==== RTMPInitialize, Status=0
<7>0x1300 = 00064300
<4>(1)th waiting.(fd=-2, len=0xfffffff7).
<4>(2)th waiting.(fd=-2, len=0xfffffff7).
<6>dummy_hcd dummy_hcd: USB Host+Gadget Emulator, driver 02 May 2005
<6>dummy_hcd dummy_hcd: Dummy host controller
<6>dummy_hcd dummy_hcd: new USB bus registered, assigned bus number 5
<6>usb usb5: configuration #1 chosen from 1 choice
<6>hub 5-0:1.0: USB hub found
<6>hub 5-0:1.0: 1 port detected
<7>dummy_udc dummy_udc: binding gadget driver 'g_file_storage'
<6>g_file_storage gadget: File-backed for SamyGO, version: 28 November 2005
<6>g_file_storage gadget: Number of LUNs=1
<6>g_file_storage gadget-lun0: ro=0, file: /mtd_rwarea/vusb.image
<7>dummy_hcd dummy_hcd: port status 0x00010101 has changes
<7>dummy_hcd dummy_hcd: port status 0x00010101 has changes
<7>dummy_hcd dummy_hcd: port status 0x00100503 has changes
<6>usb 5-1: new high speed USB device using dummy_hcd and address 2
<7>dummy_hcd dummy_hcd: port status 0x00100503 has changes
<7>dummy_udc dummy_udc: set_address = 2
<6>usb 5-1: configuration #1 chosen from 1 choice
<7>dummy_udc dummy_udc: enabled ep-a (ep1in-bulk) maxpacket 512
<7>dummy_udc dummy_udc: enabled ep-b (ep2out-bulk) maxpacket 512
<6>g_file_storage gadget: high speed config #1
<6>scsi1 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<5> Vendor: Linux Model: File-Stor Gadget Rev: 0302
<5> Type: Direct-Access ANSI SCSI revision: 02
<5>SCSI device sdb: 640 512-byte hdwr sectors (0 MB)
<7>dummy_hcd dummy_hcd: ep ep-a halted, urb c6d7b9c0
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 0f 00 00 00
<3>sdb: assuming drive cache: write through
<5>SCSI device sdb: 640 512-byte hdwr sectors (0 MB)
<7>dummy_hcd dummy_hcd: ep ep-a halted, urb c6d7b9c0
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 0f 00 00 00
<3>sdb: assuming drive cache: write through
<6> sdb: sdb1
<5>sd 1:0:0:0: Attached scsi disk sdb
<7>usb-storage: device scan complete
<3>FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem wil l be case sensitive!
<4>(3)th waiting.(fd=-2, len=0xfffffff7).
<4>
<4>-(4)th waiting:(N:307989)--
<4>
<4> success=23, nonce=307989
<2>Success!! Authuld is completed as Success
<2>Executed
# _comb_read: I2C ERR: slave not exist or =============
-sh: _comb_read:: not found
# <4>i2c_master_comb_read: I2C ERR: sub address not ack ================
-sh: Syntax error: redirection unexpected
# <4>sdp_i2c_ioctl: i2c device start byte not ack
-sh: Syntax error: redirection unexpected
# <4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0d)
-sh: Syntax error: redirection unexpected
# <4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0f)
-sh: Syntax error: redirection unexpected
# <4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,10)
-sh: Syntax error: redirection unexpected
# <6>8139too Fast Ethernet driver 0.9.27
-sh: Syntax error: redirection unexpected
# <4>PCI: enabling device 0000:00:0a.0 (0140 -> 0143)
-sh: Syntax error: redirection unexpected
# <6>eth0: RealTek RTL8139 at 0x6000, 00:12:fb:b3:0d:d8, IRQ 12
-sh: Syntax error: redirection unexpected
# <7>eth0: Identified 8139 chip type 'RTL-8100B/8139D'
-sh: Syntax error: redirection unexpected
# <6>eth0: link down
-sh: Syntax error: redirection unexpected
Thanks for tip. That's the result of dmesg after a boot up without any problems.
As soon as the TV has been turned off for a longer period where I will encounter the problem, I will do another dmesg.
Re: HELP ?weak or no signal? when turning on TV
Posted: Sun Feb 21, 2010 10:29 am
by mattberlin
Hi again,
no I used the dmesg while the TV was displaying "weak or no signal"
Can one of you professionals detect a problem in this log?
Best regards,
Matthias
Code: Select all
<1> (Detailed Information: /sys/selp/vd/lspinfo/summary)
<1>================================================================================
<4>kernel flash type : 1000 MB
<4>fsr: module license 'Samsung Proprietary' taints kernel.
<4>[BIF:IN ] ++FSR_BML_Init(nFlag: 0x0)
<4>BML: Registered BML Driver.
<4> --------------------------------
<4> Now we can read /dev/bml0/20 (after=4)
<4>---------------------------------
<4> --------------------------------
<4> Now we can read /dev/bml0/3 (after=0)
<4>---------------------------------
<4>(For Secure boot) app checking thread is created..
<4>(myphj) After generating kernel thread
<4> --------------------------------
<4> Now we can read /bin/authuld (after=0)
<4>---------------------------------
<4>
<4> total read length = 38124
<4> >>> (/bin/authuld) file is successfully authenticated <<<
<4>(0)th waiting.(fd=-2, len=0xfffffff7).
<4>FSR: Registered STL Driver.
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0e)
<4>=================================================
<4> DEVICE NAME: N/A
<4> VERSION: AllInOne-1.0
<4> BUILD DATE: Sep 16 2009 16:08:27
<4>=============== DEVICE INIT START ===============
<4>Osal init success
<4>OsaInitMmap init success
<4>Registered Dbg driver. Major=0xcc27fa80.
<4>Debug init success
<4>MFD init success
<4>Registered AD driver. Major=0xcc27f900.
<4>AD init success
<4>Registered AE driver. Major=0xcc27f840.
<4>AE init success
<4>Registered AIO driver. Major=0xcc27f780.
<4>AIO init success
<4>Tsd init success
<4>Mpeg init success
<4>Registered JPEG driver. Major=0xcc27f480.
<4>Jpeg init success
<4>Incapt init success
<4>Dp init success
<4>GPIO init success
<4>Graphics init success
<4>3D Graphics init success
<4>IR init success
<4>Registered SE driver. Major=0xcb926ce0.
<4>SE init success
<4>PVR Record init success
<4>PVR Playback init success
<4>AVD init success
<4>Sys init success
<4>Ci init success
<4>NRSS init success
<4>
<4>=============== DEVICE INIT DONE ================
<4>SAM_Print Module 0x1 is Enabled, giPrintModule=0x1
<4>SAM_Print Init success
<4>SYS_SET_INITIALIZED_MODULE called
<4>SYS_SET_MEMORYMAP_TABLE called
<4>SYS_SET_SYSTEM_CONFIG called
<4>TsdOpen:the count value is bf4462c0
<4>i2c_master_write: I2C ERR: port 0 write error ================
<4>i2c_master_write: I2C ERR: slave dev 0x4a ================
<4>i2c_master_write: I2C ERR: error status 0x81================
<4>sdp_i2c_ioctl: i2c device start byte not ack
<4>i2c_master_comb_read: I2C ERR: port 0 comb read error ================
<4>i2c_master_comb_read: I2C ERR: slave dev 0xe2 ================
<4>i2c_master_comb_read: I2C ERR: slave not exist or =============
<4>i2c_master_comb_read: I2C ERR: sub address not ack ================
<4>sdp_i2c_ioctl: i2c device start byte not ack
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0d)
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,0f)
<4>rfs_log_replay[599]: RFS_SUBLOG_COMMIT (0,8a,10)
<6>8139too Fast Ethernet driver 0.9.27
<4>PCI: enabling device 0000:00:0a.0 (0140 -> 0143)
<6>eth0: RealTek RTL8139 at 0x6000, 00:12:fb:b3:0d:d8, IRQ 12
<7>eth0: Identified 8139 chip type 'RTL-8100B/8139D'
<6>eth0: link down
<0>usb_fault: version 1.20
<6>usbcore: registered new driver usbfs
<6>usbcore: registered new driver hub
<6>ehci-s5h2x ehci-s5h2x.0: initializing S5H2XXX-SOC USB Controller
<6>ehci-s5h2x ehci-s5h2x.0: S5H2X On-chip EHCI Host controller
<6>ehci-s5h2x ehci-s5h2x.0: new USB bus registered, assigned bus number 1
<6>ehci-s5h2x ehci-s5h2x.0: s5h2x_ehci_setup success
<6>ehci-s5h2x ehci-s5h2x.0: irq 15, io mem 0x30070000
<6>ehci-s5h2x ehci-s5h2x.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
<6>ehci-s5h2x ehci-s5h2x.0: ehci-s5h2x probing completed.
<6>ehci-s5h2x ehci-s5h2x.1: initializing S5H2XXX-SOC USB Controller
<6>ehci-s5h2x ehci-s5h2x.1: S5H2X On-chip EHCI Host controller
<6>ehci-s5h2x ehci-s5h2x.1: new USB bus registered, assigned bus number 2
<6>ehci-s5h2x ehci-s5h2x.1: s5h2x_ehci_setup success
<6>ehci-s5h2x ehci-s5h2x.1: irq 17, io mem 0x30080000
<6>ehci-s5h2x ehci-s5h2x.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb2: configuration #1 chosen from 1 choice
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 1 port detected
<6>ehci-s5h2x ehci-s5h2x.1: ehci-s5h2x probing completed.
<6>ohci-s5h2x ohci-s5h2x.0: S5H2X On-chip OHCI Host controller
<6>ohci-s5h2x ohci-s5h2x.0: new USB bus registered, assigned bus number 3
<6>ohci-s5h2x ohci-s5h2x.0: irq 14, io mem 0x30078000
<6>usb usb3: configuration #1 chosen from 1 choice
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 1 port detected
<6>usb 1-1: new high speed USB device using ehci-s5h2x and address 2
<6>ohci-s5h2x ohci-s5h2x.1: S5H2X On-chip OHCI Host controller
<6>ohci-s5h2x ohci-s5h2x.1: new USB bus registered, assigned bus number 4
<6>ohci-s5h2x ohci-s5h2x.1: irq 16, io mem 0x30088000
<6>usb usb4: configuration #1 chosen from 1 choice
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 1 port detected
<6>usb 1-1: configuration #1 chosen from 1 choice
<6>Initializing USB Mass Storage driver...
<6>usb 2-1: new high speed USB device using ehci-s5h2x and address 2
<6>usb 2-1: configuration #1 chosen from 1 choice
<6>scsi0 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<6>usbcore: registered new driver usb-storage
<6>USB Mass Storage support registered.
<0>rtusb 2870 1.002(1.4.0.0) init --->
<7>
<0>
<0>=== pAd = d30a1000, size = 568816 ===
<0>
<0><-- RTMPAllocAdapterBlock, Status=0
<6>usbcore: registered new driver rt2870
<4>Symbol usb_register_driver is being used by a non-GPL module, which will not be allowed in the future
<4>Please see the file Documentation/feature-removal-schedule.txt in the kernel source tree for more details.
<4>Symbol usb_deregister is being used by a non-GPL module, which will not be allowed in the future
<4>Please see the file Documentation/feature-removal-schedule.txt in the kernel source tree for more details.
<0>rtusb 0.994 init ====>
<6>usbcore: registered new driver rt73
<5> Vendor: Model: CnMemory Rev: 1100
<5> Type: Direct-Access ANSI SCSI revision: 00
<5>SCSI device sda: 1981440 512-byte hdwr sectors (1014 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 43 00 00 00
<3>sda: assuming drive cache: write through
<5>SCSI device sda: 1981440 512-byte hdwr sectors (1014 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 43 00 00 00
<3>sda: assuming drive cache: write through
<6> sda: sda1
<5>sd 0:0:0:0: Attached scsi removable disk sda
<7>usb-storage: device scan complete
<7>Poller thread started for sda, PID = 401
<3>FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
<4><-- RTMPAllocTxRxRingMemory, Status=0
<7>1. Phy Mode = 5
<7>2. Phy Mode = 5
<7>#
<7>3. Phy Mode = 5
<7>MCS Set = ff ff 00 00 01
<7>The UUID Hex string is:<7>bc<7>32<7>9e<7>00<7>1d<7>d8<7>11<7>b2<7>86<7>01<7>00<7>12<7>fb<7>2d<7>63<7>00<7>
<7>The UUID ASCII string is:bc329e00-1dd8-11b2-8601-0012fb2d6300!
<4><==== RTMPInitialize, Status=0
<7>0x1300 = 00064300
<4>(1)th waiting.(fd=-2, len=0xfffffff7).
<4>(2)th waiting.(fd=-2, len=0xfffffff7).
<6>dummy_hcd dummy_hcd: USB Host+Gadget Emulator, driver 02 May 2005
<6>dummy_hcd dummy_hcd: Dummy host controller
<6>dummy_hcd dummy_hcd: new USB bus registered, assigned bus number 5
<6>usb usb5: configuration #1 chosen from 1 choice
<6>hub 5-0:1.0: USB hub found
<6>hub 5-0:1.0: 1 port detected
<7>dummy_udc dummy_udc: binding gadget driver 'g_file_storage'
<6>g_file_storage gadget: File-backed for SamyGO, version: 28 November 2005
<6>g_file_storage gadget: Number of LUNs=1
<6>g_file_storage gadget-lun0: ro=0, file: /mtd_rwarea/vusb.image
<7>dummy_hcd dummy_hcd: port status 0x00010101 has changes
<7>dummy_hcd dummy_hcd: port status 0x00010101 has changes
<7>dummy_hcd dummy_hcd: port status 0x00100503 has changes
<6>usb 5-1: new high speed USB device using dummy_hcd and address 2
<7>dummy_hcd dummy_hcd: port status 0x00100503 has changes
<7>dummy_udc dummy_udc: set_address = 2
<6>usb 5-1: configuration #1 chosen from 1 choice
<7>dummy_udc dummy_udc: enabled ep-a (ep1in-bulk) maxpacket 512
<7>dummy_udc dummy_udc: enabled ep-b (ep2out-bulk) maxpacket 512
<6>g_file_storage gadget: high speed config #1
<6>scsi1 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<5> Vendor: Linux Model: File-Stor Gadget Rev: 0302
<5> Type: Direct-Access ANSI SCSI revision: 02
<5>SCSI device sdb: 640 512-byte hdwr sectors (0 MB)
<7>dummy_hcd dummy_hcd: ep ep-a halted, urb c6dfb9c0
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 0f 00 00 00
<3>sdb: assuming drive cache: write through
<5>SCSI device sdb: 640 512-byte hdwr sectors (0 MB)
<7>dummy_hcd dummy_hcd: ep ep-a halted, urb c6dfb9c0
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 0f 00 00 00
<3>sdb: assuming drive cache: write through
<6> sdb: sdb1
<5>sd 1:0:0:0: Attached scsi disk sdb
<7>usb-storage: device scan complete
<3>FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
<3> CIFS VFS: Send error in SessSetup = -12
<4>(3)th waiting.(fd=-2, len=0xfffffff7).
<4>
<4>-(4)th waiting:(N:327278)--
<4>
<4> success=23, nonce=327278
<2>Success!! Authuld is completed as Success
<2>Executed
Re: HELP ?weak or no signal? when turning on TV
Posted: Sun Feb 21, 2010 11:43 am
by erdem_ua
everything looks good to my eye. Instead of trying to fix it, let Samsung service does their job. Before, I advice, revert all changes and firmware that you made.
Re: HELP ?weak or no signal? when turning on TV
Posted: Sun Feb 21, 2010 10:02 pm
by mattberlin
Thank's a lot for the feedback. I just wanted to check with you guys before contacting Samsung. I'll keep ya updated.
Get well into the upcoming week.