Visualizzazione Stampabile
-
Report di sistema...
Salve a tutti,
sono nuovo del forum... e sto aspettando un MR5000... :)
Nel frattempo, c'è qualcuno che avendolo giÃ* in casa puo' postare l'output del comando 'dmesg' dopo il collegamento in telnet al MR5000 in modo
da vedere un po' le caratteristiche del sistema HW e SW... ?
Grazie
Un saluto a tutti... :wink:
-
Re: Report di sistema...
/ # dmesg
, set sh = 0x5, get sh = 0x5, 4bit
[usb1_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb1_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb1_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb1_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
[usb2_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb2_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb2_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb2_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb2_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
ehci_hcd ehci_hcd: EHCI Host Controller
ehci_hcd ehci_hcd: new USB bus registered, assigned bus number 1
ehci_hcd ehci_hcd: irq 2, io mem 0xb8013000
ehci_hcd ehci_hcd: park 0
ehci_hcd ehci_hcd: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub : individual port power switching
hub : individual port over-current protection
[cfyeh] set PPE = 0
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
[usb_param] setting for mars
Setting for MARS-B
[usb_param] set port two for host!
[usb1_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb1_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb1_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb1_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb1_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
[usb2_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb2_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb2_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb2_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb2_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
ohci_hcd ohci_hcd: OHCI Host Controller
ohci_hcd ohci_hcd: new USB bus registered, assigned bus number 2
ohci_hcd ohci_hcd: irq 2, io mem 0xb8013400
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hub : no power switching (usb 1.0)
hub : no over-current protection
usb 1-1: new high speed USB device using ehci_hcd and address 2
This is the current time: PowerUP_Done!!!
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
hub : ganged power switching
hub : global over-current protection
usb 1-1.1: new high speed USB device using ehci_hcd and address 3
###################################################################
[cfyeh-test] usb_set_configuration(1454)
Don't support this usb device or don't insert correct module yet!!!
bus_id 1-1.1:1.0 (config #1, interface 0)
###################################################################
ufsd: no version for "struct_module" found: kernel tainted.
ufsd: module license 'Commercial product' taints kernel.
ufsd: driver loaded at c011c000 built on Aug 11 2009 19:56:40
UFSD version 7.07 (Aug 11 2009, 19:40:46)
NTFS read/write support included
$Id: ufsdvfs.c,v 1.228 2009/08/11 15:37:17 shura Exp $ (LBD=ON)
usb 1-1.2: new high speed USB device using ehci_hcd and address 4
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb 1-1.4: new high speed USB device using ehci_hcd and address 5
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
ieee80211_crypt: registered algorithm 'NULL'
ieee80211_crypt: registered algorithm 'CCMP'
Algorithmics/MIPS FPU Emulator v1.5
save exit: isCheckpointed 1
ieee80211_crypt: registered algorithm 'TKIP'
ieee80211_crypt: registered algorithm 'WEP'
Vendor: Maxtor Model: OneTouch Rev: 0122
Type: Direct-Access ANSI SCSI revision: 04
Vendor: Generic Model: STORAGE DEVICE Rev: 9451
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: assuming drive cache: write through
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: assuming drive cache: write through
/dev/scsi/host2/bus0/target0/lun0: p1
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Attached scsi removable disk sdc at scsi3, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi3, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Linux kernel driver for RTL8192 based WLAN cards
Copyright (c) 2007-2008, Realsil Wlan
try_to_free_pages: free 812
1. start remap DVR zone...
fastmode is 100...
map_done is 1284...
map_fail is 0...
==>ep_num:4, in_ep_num:1, out_ep_num:3
==>RtInPipes:3
==>RtOutPipes:4 6 13
==>txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD, MGNT, HIGH, BEACON:
1 1 0 0 2 2 2 2 2
try_to_free_pages: free 32
1. start remap DVR zone...
remap: reinitialize swap area...
fastmode is 100...
map_done is 19...
map_fail is 0...
CustomerID = 0x 0
BoardType = 0x 1
RF_Type = 0x 0
Dot11d_Init()
usbcore: registered new driver rtl819xSU
rtl819xSU: --->FirmwareDownload92S()
Using FW_SOURCE_HEADER_FILE
rtl819xSU:signature:8192, version:903e, size:30, imemsize:8808, sram size:b708
rtl819xSU:--->FirmwareDownloadCode()
rtl819xSU:--->FirmwareCheckReady(): LoadStaus(1),
rtl819xSU:<---FirmwareCheckReady(): LoadFWStatus(1), rtStatus(0)
rtl819xSU:--->FirmwareDownloadCode()
rtl819xSU:--->FirmwareCheckReady(): LoadStaus(2),
rtl819xSU:-->FirmwareEnableCPU()
rtl819xSU:IMEM Ready after CPU has refilled.
rtl819xSU:<--FirmwareEnableCPU(): rtStatus(0x0)
rtl819xSU:<---FirmwareCheckReady(): LoadFWStatus(2), rtStatus(0)
rtl819xSU:--->FirmwareDownloadCode()
rtl819xSU:--->FirmwareCheckReady(): LoadStaus(3),
rtl819xSU:DMEM code download success, CPUStatus(0x3f)
rtl819xSU:Polling Load Firmware ready, CPUStatus(ff)
rtl819xSU:FirmwareCheckReady(): Current RCR settings(0x157e20e)
rtl819xSU:FirmwareCheckReady(): Current TCR settings(2ff)
rtl819xSU:<---FirmwareCheckReady(): LoadFWStatus(3), rtStatus(0)
rtl819xSU:Firmware Download Success!!
rtl8192SU_HalUsbRxAggr8192SUsb: Enable RxAggregation +++++
rtl8192SU_adapter_start-9092: RCR = 8377f00e
rtl8192SU_adapter_start-9095: RCR = 8777f00e
rtl8192_phy_QueryRFReg(): rf_pathmap=3 eRFPath=0
rtl8192_phy_QueryRFReg(): rf_pathmap=3 eRFPath=1
rtl8192_rx_isr-2326: netif_wake_queue(dev)
smbd: page allocation failure. order:3, mode:0x20
rtl8192_rx_isr():can,t alloc skb
===>ieee80211_start_scan()
rtl819xSU:Setting SW wep key
Linking with VIVO,channel:3, qos:0, myHT:1, networkHT:0, mode:6 cur_net.flags:0x
406
=====>rtl8192SU_link_change 1
<=====rtl8192SU_link_change 2
===>ieee80211_associate_procedure_wq(), chan:3
==========>rtl819su_HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
rtl819xSU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
rtl819xSU:<==SetBWModeCallback8192SUsbWorkItem()
=================>ieee80211_authentication_req():auth->algorithm is 0
rtl819xSU:rtl8192_qos_association_resp: network->flags = 2,0
rtl819xSU:qos active process with associate response received
Associated successfully
============>normal associate
Using G rates:108
Successfully associated, ht not enabled(0, 0)
=====>rtl8192SU_link_change 1
=============>ARFR0+rate_index*4:0xfff
<=====rtl8192SU_link_change 2
dm_check_edca_turbo():iot peer is 0x0:unknown, bssid:00:14:78:63:84:2d
========>dm_check_edca_turbo()up link
===>DHCP Protocol start tx DHCP pkt src port:68, dest port:67!!
===>DHCP Protocol start tx DHCP pkt src port:68, dest port:67!!
save exit: isCheckpointed 1
========>dm_check_edca_turbo()down link
========>dm_check_edca_turbo()up link
/ #
ecco fatto! ma tu ci capisci qualcosa?
-
Re: Report di sistema...
yes :)
il dmesg praticamente è un print del file log di sistema che sta sotto /var/log/messages.
Hanno una lunghezza prestabilita e appena viene superata il file messages diventa messages.1 ... ecc... e un nuovo messages viene creato.
Sarebbe stato meglio avere un dmesg dopo un reboot del dispositivo, ma .... mi sono dimenticato di chiederlo :)
Mi serviva sapere quanta RAM e che processore(dovrebbe essere il mips) monta l'MR5000 ...
Ciao e grazie
-
Re: Report di sistema...
mi pare di averlo acceso apposta ma ho qualche dubbio, però, se lo desideri, lo rifaccio avendo cura di accenderlo al momento. :)
-
Re: Report di sistema...
Si grazie se puoi, cosi vediamo al boot cosa elenca il linux mentre carica... :wink:
P.S. devi spegnere togliendo la spina; spegnendo dal telecomando penso non sia sufficiente.
-
Re: Report di sistema...
Venus login: root
Password:
warning: cannot change to home directory
BusyBox v1.1.3 (2010.03.10-14:41+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ # dmesg
obe failed
save exit: isCheckpointed 1
[usb_param] setting for mars
Setting for MARS-B
[usb_param] set port two for host!
[usb1_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb1_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb1_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb1_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb1_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
[usb2_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb2_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb2_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb2_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb2_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
ehci_hcd ehci_hcd: EHCI Host Controller
ehci_hcd ehci_hcd: new USB bus registered, assigned bus number 1
ehci_hcd ehci_hcd: irq 2, io mem 0xb8013000
ehci_hcd ehci_hcd: park 0
ehci_hcd ehci_hcd: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub : individual port power switching
hub : individual port over-current protection
[cfyeh] set PPE = 0
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
[usb_param] setting for mars
Setting for MARS-B
[usb_param] set port two for host!
[usb1_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb1_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb1_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb1_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb1_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
[usb2_param] usbphy reg 32, set sh = 0x5, get sh = 0x5, 4bit
[usb2_param] usbphy reg 35, set src = 0x7, get src = 0x7, 3bit
[usb2_param] usbphy reg 36, set senh = 0xd, get senh = 0xd, 4bit
[usb2_param] usbphy reg 32, set sen = 0x8, get sen = 0x8, 4bit
[usb2_param] usbphy reg 33, set dr = 0x0, get dr = 0x0, 3bit
ohci_hcd ohci_hcd: OHCI Host Controller
ohci_hcd ohci_hcd: new USB bus registered, assigned bus number 2
ohci_hcd ohci_hcd: irq 2, io mem 0xb8013400
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hub : no power switching (usb 1.0)
hub : no over-current protection
usb 1-1: new high speed USB device using ehci_hcd and address 2
This is the current time: PowerUP_Done!!!
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
hub : ganged power switching
hub : global over-current protection
usb 1-1.1: new high speed USB device using ehci_hcd and address 3
###################################################################
[cfyeh-test] usb_set_configuration(1454)
Don't support this usb device or don't insert correct module yet!!!
bus_id 1-1.1:1.0 (config #1, interface 0)
###################################################################
ufsd: no version for "struct_module" found: kernel tainted.
ufsd: module license 'Commercial product' taints kernel.
ufsd: driver loaded at c011c000 built on Aug 11 2009 19:56:40
UFSD version 7.07 (Aug 11 2009, 19:40:46)
NTFS read/write support included
$Id: ufsdvfs.c,v 1.228 2009/08/11 15:37:17 shura Exp $ (LBD=ON)
usb 1-1.2: new high speed USB device using ehci_hcd and address 4
Algorithmics/MIPS FPU Emulator v1.5
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb 1-1.4: new high speed USB device using ehci_hcd and address 5
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
save exit: isCheckpointed 1
ieee80211_crypt: registered algorithm 'NULL'
ieee80211_crypt: registered algorithm 'CCMP'
ieee80211_crypt: registered algorithm 'TKIP'
ieee80211_crypt: registered algorithm 'WEP'
Linux kernel driver for RTL8192 based WLAN cards
Copyright (c) 2007-2008, Realsil Wlan
try_to_free_pages: free 809
1. start remap DVR zone...
Vendor: Maxtor Model: OneTouch Rev: 0122
Type: Direct-Access ANSI SCSI revision: 04
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: assuming drive cache: write through
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: assuming drive cache: write through
/dev/scsi/host2/bus0/target0/lun0:<5> Vendor: Generic Model: STORAGE DEVICE
Rev: 9451
Type: Direct-Access ANSI SCSI revision: 00
fastmode is 100...
map_done is 1427...
map_fail is 0...
==>ep_num:4, in_ep_num:1, out_ep_num:3
==>RtInPipes:3
==>RtOutPipes:4 6 13
==>txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD, MGNT, HIGH, BEACON:
1 1 0 0 2 2 2 2 2
try_to_free_pages: free 0
1. start remap DVR zone...
fastmode is 100...
map_done is 0...
map_fail is 0...
CustomerID = 0x 0
BoardType = 0x 1
RF_Type = 0x 0
Dot11d_Init()
usbcore: registered new driver rtl819xSU
rtl819xSU: --->FirmwareDownload92S()
Using FW_SOURCE_HEADER_FILE
rtl819xSU:signature:8192, version:903e, size:30, imemsize:8808, sram size:b708
rtl819xSU:--->FirmwareDownloadCode()
rtl819xSU:--->FirmwareCheckReady(): LoadStaus(1),
rtl819xSU:<---FirmwareCheckReady(): LoadFWStatus(1), rtStatus(0)
rtl819xSU:--->FirmwareDownloadCode()
rtl819xSU:--->FirmwareCheckReady(): LoadStaus(2),
rtl819xSU:-->FirmwareEnableCPU()
rtl819xSU:IMEM Ready after CPU has refilled.
rtl819xSU:<--FirmwareEnableCPU(): rtStatus(0x0)
rtl819xSU:<---FirmwareCheckReady(): LoadFWStatus(2), rtStatus(0)
rtl819xSU:--->FirmwareDownloadCode()
rtl819xSU:--->FirmwareCheckReady(): LoadStaus(3),
rtl819xSU:DMEM code download success, CPUStatus(0x3f)
rtl819xSU:Polling Load Firmware ready, CPUStatus(ff)
rtl819xSU:FirmwareCheckReady(): Current RCR settings(0x157e20e)
rtl819xSU:FirmwareCheckReady(): Current TCR settings(2ff)
rtl819xSU:<---FirmwareCheckReady(): LoadFWStatus(3), rtStatus(0)
rtl819xSU:Firmware Download Success!!
rtl8192SU_HalUsbRxAggr8192SUsb: Enable RxAggregation +++++
rtl8192SU_adapter_start-9092: RCR = 8377f00e
rtl8192SU_adapter_start-9095: RCR = 8777f00e
rtl8192_phy_QueryRFReg(): rf_pathmap=3 eRFPath=0
rtl8192_phy_QueryRFReg(): rf_pathmap=3 eRFPath=1
===>ieee80211_start_scan()
iwlist: page allocation failure. order:3, mode:0x20
rtl8192_rx_isr():can,t alloc skb
p1
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Attached scsi removable disk sdc at scsi3, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi3, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
rtl819xSU:Setting SW wep key
Linking with VIVO,channel:3, qos:0, myHT:1, networkHT:0, mode:6 cur_net.flags:0x
406
=====>rtl8192SU_link_change 1
<=====rtl8192SU_link_change 2
===>ieee80211_associate_procedure_wq(), chan:3
==========>rtl819su_HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
rtl819xSU:==>SetBWModeCallback8192SUsbWorkItem() Switch to 20MHz bandwidth
rtl819xSU:<==SetBWModeCallback8192SUsbWorkItem()
=================>ieee80211_authentication_req():auth->algorithm is 0
rtl819xSU:rtl8192_qos_association_resp: network->flags = 2,0
rtl819xSU:qos active process with associate response received
Associated successfully
============>normal associate
Using G rates:108
Successfully associated, ht not enabled(0, 0)
=====>rtl8192SU_link_change 1
=============>ARFR0+rate_index*4:0xfff
<=====rtl8192SU_link_change 2
dm_check_edca_turbo():iot peer is 0x0:unknown, bssid:00:14:78:63:84:2d
========>dm_check_edca_turbo()up link
===>DHCP Protocol start tx DHCP pkt src port:68, dest port:67!!
===>DHCP Protocol start tx DHCP pkt src port:68, dest port:67!!
save exit: isCheckpointed 1
/ #
non posso collegarmi e poi accendere, devo fare il contrario altrimenti non riesco ad entrare via wifi quindi niente boot. non ho sottomano un cavo di rete.
non ho controllato se è uguale all'atro.
forse può aiutarci Galerio
-
Re: Report di sistema...
ok! ... va bene lo stesso.... :) dal log di prima infatti avevo visto che accedevi con la usb wifi...
tanto appena arriva il mio lo metto sotto torchio :eheh:
Volevo cominciare a studiare un po' come è strutturato il kernel e le configurazioni in modo da poter aggiungere qualche cosa di utile o altri dispositivi esterni,
magari attaccati all'usb :)
Ciao e grazie....
Buona serata...
-
Re: Report di sistema...
non sapevo si potesse anche da usb, sono alle prime armi, devo acceder sempre con l'ip?
-
Re: Report di sistema...
no, l'usb quella con l'attacco tipo B (quella più quadrata) fa' vedere l'hardisk interno dell'MR, come un disco esterno se lo si attacca ad un PC.
Le altre due USB, connettore tipo A, sono per aggiungere all'MR altri dispositivi, tipo usb key o HD esterni o usb wifi o webcam... ecc...
Ciao :)
-
Re: Report di sistema...
eheh forse non mi sono spiegato. l'uso delle usb lo conosco bene. Mi chiedevo se si potesse accedere all'mr5000 tramite telnet da usb B. era questo il mio dubbio :)