Raspberry Pi Using Raspbian As TV Tuner

Hi guys,

I'm new to the forum and the first problem appeared, hope u guys can help me out!


Just changed my system from Windows to Linux and have some issues to get my Wifi Stick
Fritz! WLAN USB N v 2 working.

1. I downloaded the newest drivers for Win64-Bit from the AVM Homepage.
2. Started ndiswrapper Selected the fwlan64.inf -> Clicked on install.
3. Error Message appears :
modprobe: FATAL: Module ndiswrapper not found
4. Uninstalled ndiswrapper (thought probably and older version could fix this was reading on some Ubuntu Forum cause i couldnt find anything for Ziron)

Any help appreciated!

Thank you so much!

Edit: Some more info

System Log:

Quote:
stani-System-Product-Name kernel: [ 2085.487551] usb 2-1.6: USB disconnect, device number 13
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.452762] usb 2-1.6: new high-speed USB device number 14 using ehci-pci
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.549669] usb 2-1.6: New USB device found, idVendor=057c, idProduct=8501
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.549674] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.549677] usb 2-1.6: Product: FRITZ!WLAN USB Stick N v2
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.549680] usb 2-1.6: Manufacturer: AVM Berlin
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.549682] usb 2-1.6: SerialNumber: 246511430F18
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.624607] usb 2-1.6: reset high-speed USB device number 14 using ehci-pci
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.719007] ieee80211 phy4: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.756314] ieee80211 phy4: rt2x00usb_vendor_request: Error - Vendor Request 0x09 failed for offset 0x0000 with error -32
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.756320] ieee80211 phy4: rt2x00lib_probe_dev: Error - Failed to allocate device
Feb 12 16:34:23 stani-System-Product-Name kernel: [ 2086.756349] rt2800usb: probe of 2-1.6:1.0 failed with error -32
Feb 12 16:34:23 stani-System-Product-Name mtp-probe: checking bus 2, device 14: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6"
Feb 12 16:34:23 stani-System-Product-Name mtp-probe: bus: 2, device: 14 was not an MTP device
Feb 12 16:34:24 stani-System-Product-Name usb_modeswitch: switched to 057c:ffffffff on 002/013
uname -a

Quote:
Linux stani-System-Product-Name 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
stani@stani-System-Product-Name:~$
lsusb
Quote:
Bus 002 Device 006: ID 0b05:179c ASUSTek Computer, Inc.
Bus 002 Device 014: ID 057c:8501 AVM GmbH
Bus 002 Device 004: ID 1ea7:1005
Bus 002 Device 003: ID 046d:c326 Logitech, Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hello - This is my first interaction with Linux. I recently purchased a Raspberry Pi 2 and am running the full version of Raspbian. I intend to use the Pi as my PLEX media server however I have been unsuccessful in mounting my NAS. I've read a number of guides on how to accomplish this but have been striking out on all accounts. I was hoping someone could help me with what information I should be adding.

NAS - Synology Diskstation DS212j - 192.168.5.195
Linux device - Raspberry Pi 2 - Raspbian - 192.168.5.186
Router - D-Link DIR-655 - 192.168.5.1

I've been accessing the Pi via ssh on my MacBook PRO - 192.168.5.188

Thanks for any assistance you can provide.

Hi all

I need help with the above topic as i have followed the instructions on the FTDI website but have had no luck in getting my device to communicate with my machine. dmesg reports it has found the device at ttyusb0 and recognises it as a FTDI device, but when i scan my ports with my program it does not detect it. the program is Tuner Studio and my device is a Megasquirt EFI controller.

thanks,

Hello guys!

First thing to be said is, that I am not native English speaker and I hope my english will be sufficient for this problem.

I am trying to make some kind of thin client from my Raspberry Pi 2.
I put Raspbian Wheezy distribution inside.

After I tried different clients (rdesktop, remmina, xrdp) I found FreeRDP, that looks like what I was looking for.

After the setup and network configuration of my Raspbian I updated repositories and installed freerdp through
Quote:
sudo apt-get update
sudo apt-get install freerdp
Their wiki says that there are 2 forms of commands. The newer one (through /PARAMETER) and older one (through -PARAMETER)
https://github.com/FreeRDP/FreeRDP/w...dLineInterface

How do I get new commands to work? I thought that apt-get install freerdp would bring me the newest version. My version is 1.0.1 and I am not sure if it is the newest version.

I need to run my rdp client from shell, that is why I refused to use remmina.

I hope i explained my problem weell enough.

Thank you for any suggestions.

Hi.
This is the first time I need to do this. New to Linux... :-)

I need to have two Ethernet connections in my laptop working. Its Ethernet RJ-45 jack works fine. I had to get a new Trendnet USB/Ethernet adapter for the second connection. After I connected it for the first time to my laptop having Fedora 15, I get:

[root@Brcm-AP brcmapac]# tail -f /var/log/messages
Mar 17 05:31:57 Brcm-AP dbus: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 17 05:36:58 Brcm-AP kernel: [11429.615508] TCP lp registered
Mar 17 05:42:35 Brcm-AP kernel: [11766.773200] composite sync not supported
Mar 17 05:46:17 Brcm-AP dbus: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Mar 17 05:46:17 Brcm-AP dbus: [system] Successfully activated service 'net.reactivated.Fprint'
Mar 17 05:46:48 Brcm-AP dbus: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 17 05:46:48 Brcm-AP dbus: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mar 17 06:04:07 Brcm-AP kernel: [13058.324180] composite sync not supported
Mar 17 06:04:49 Brcm-AP dbus: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Mar 17 06:04:49 Brcm-AP dbus: [system] Successfully activated service 'net.reactivated.Fprint'
Mar 17 06:06:07 Brcm-AP kernel: [13177.798536] usb 1-5: USB disconnect, address 4
Mar 17 06:06:10 Brcm-AP kernel: [13181.511109] usb 1-5: new high speed USB device using ehci_hcd and address 5
Mar 17 06:06:10 Brcm-AP kernel: [13181.630296] usb 1-5: New USB device found, idVendor=0b95, idProduct=1790
Mar 17 06:06:10 Brcm-AP kernel: [13181.630304] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 17 06:06:10 Brcm-AP kernel: [13181.630311] usb 1-5: Product: AX88179
Mar 17 06:06:10 Brcm-AP kernel: [13181.630316] usb 1-5: Manufacturer: ASIX Elec. Corp.
Mar 17 06:06:10 Brcm-AP kernel: [13181.630320] usb 1-5: SerialNumber: 0000000000103C
Mar 17 06:06:10 Brcm-AP mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Mar 17 06:06:10 Brcm-AP mtp-probe: bus: 1, device: 5 was not an MTP device
Mar 17 06:09:07 Brcm-AP dbus: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Mar 17 06:09:07 Brcm-AP dbus: [system] Successfully activated service 'org.freedesktop.PackageKit'

the output does detect the new USB adapter "Product: AX88179, Manufacturer: ASIX Elec Corp.".

The list of interfaces seen:

[root@Brcm-AP brcmapac]# ifconfig
em1 Link encap:Ethernet HWaddr 00:18:8B:B6:97:4D
inet addr:10.10.138.24 Bcast:10.10.139.255 Mask:255.255.254.0
inet6 addr: fe80::218:8bff:feb6:974d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32846 errors:0 dropped:12285 overruns:0 frame:12
TX packets:15532 errors:0 dropped:0 overruns:0 carrier:0
collisions:5185 txqueuelen:1000
RX bytes:35819763 (34.1 MiB) TX bytes:1346684 (1.2 MiB)
Interrupt:18

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1008 errors:0 dropped:0 overruns:0 frame:0
TX packets:1008 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:78668 (76.8 KiB) TX bytes:78668 (76.8 KiB)

wlan0 Link encap:Ethernet HWaddr 00:1A:92:9FA:A3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


The first connection is em1 and working fine, but I never see a second ethx interface. I figured I'm missing the driver for it. So, I went to the read me file from the cd, where these files a
- asix.h
- ax88179_178a.c
- Makefile
- readme

The readme instructions for Linux say: you need the kernel sources installed on the machine. Make sure the version of the running kernel must match the installed kernel sources.

1. What are kernel sources and how I can download them for this installation? Please, keep in mind I do not know Linux. This is my first time doing more than just the very basics.
The instructions are called "ASIX AX88179_178A USB 3.0/2.0 Gigabit Ethernet Network Adapter Driver Compilation & Configuration on Linux."

My kernel is 2.6.38.6-26.rc1.fc15.i686.PAE

I have no idea how to start.
Thank you!!!

I have a USB fax modem, and it logs the following errors when turned on.

I know it is impossible to know for sure, but think it is hardware related? Any chance to salvage?

Also, what are the steps to start troubleshooting?

Thanks

Code:

Jan 17 14:38:26 devserver kernel: generic-usb 0003:0461:4D0F.0066: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1a.0-1.2/input0
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 24 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/all, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 25 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/all, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 26 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:41 devserver kernel: usb 3-1: new full speed USB device number 27 using xhci_hcd
Jan 17 14:38:41 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:42 devserver kernel: usb 3-1: device descriptor read/8, error -71
Jan 17 14:38:42 devserver kernel: hub 3-0:1.0: unable to enumerate USB device on port 1

I'm using a Western Digital My Book Live DUO network drive with 2x2Tb HD's in RAID 1 configuration. The devices uses Linux GNU to manage the RAID array.
At some point after a reboot the UI returns this error:

"Data volume failed to mount Contact tech support"

I have very little linux knowledge, and trying to get the RAID error fixed so I can access and backup my data on another drive.

Here's the info I have managed to pull so far from the drive via SSH:


dmesg

Code:

login as: root
root@192.168.1.55's password:
Linux LTFileServer 2.6.32.11-svn70860 #1 Thu May 17 13:32:51 PDT 2012 ppc
Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.

LTFileServer:~# dmesg
4bffd1800.sata: DMA CFG = 0x00000001
dma_register_interrupt register irq (25)
irq: irq 27 on host /interrupt-controller0 mapped to virtual irq 27
ata4294967295: sata_dwc_port_start: setting burst size in DBTSR: 0x00100010
sata-dwc 4bffd1800.sata: **** GEN II speed rate negotiated
scsi1 : sata-dwc
ata2: SATA max UDMA/133 irq 27
Found: SST 39LF040
4fff80000.nor_flash: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Creating 2 MTD partitions on "4fff80000.nor_flash":
0x000000000000-0x000000020000 : "3genv"
0x000000020000-0x000000080000 : "u-boot"
ndfc 4fff80000.ndfc: failed to get memory
ndfc: probe of 4fff80000.ndfc failed with error -5
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
PPC 4xx OCP EMAC driver, version 3.54
mal0: descriptor-memory = ocm
irq: irq 6 on host /interrupt-controller2 mapped to virtual irq 24
irq: irq 7 on host /interrupt-controller2 mapped to virtual irq 29
irq: irq 3 on host /interrupt-controller2 mapped to virtual irq 31
irq: irq 4 on host /interrupt-controller2 mapped to virtual irq 32
irq: irq 5 on host /interrupt-controller2 mapped to virtual irq 33
irq: irq 8 on host /interrupt-controller2 mapped to virtual irq 34
irq: irq 12 on host /interrupt-controller2 mapped to virtual irq 35
MAL: Enabled Interrupt Coal TxCnt: 1 RxCnt: 8
                            TxTimer: 0 RxTimer: 10000
MAL v2 /plb/mcmal, 1 TX channels, 1 RX channels
RGMII /plb/opb/emac-rgmii@ef601500 initialized with MDIO support
TAH /plb/opb/emac-tah@ef601350 initialized
irq: irq 16 on host /interrupt-controller2 mapped to virtual irq 36
irq: irq 20 on host /interrupt-controller2 mapped to virtual irq 37
/plb/opb/emac-rgmii@ef601500: input 0 in RGMII mode
bcm54610_init: before 0x2c8c, after 0x2c8c
bcm54610_init: before 0x0d41, 0x0200; after 0x0d41, 0x0200
eth0: EMAC-0 /plb/opb/ethernet@ef600c00, MAC 00:90:a9:b7:10:66
eth0: found BCM54610 Gigabit Ethernet PHY (0x01)
Intel(R) Gigabit Ethernet Network Driver - version 1.3.16-k2
Copyright (c) 2007-2009 Intel Corporation.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Fusion MPT base driver 3.04.12
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.12
input: rst_button as /devices/virtual/input/input0
i2c /dev entries driver
irq: irq 2 on host /interrupt-controller0 mapped to virtual irq 38
ibm-iic 4ef600700.i2c: using standard (100 kHz) mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
Registered led device: a3g_led
irq: irq 20 on host /interrupt-controller0 mapped to virtual irq 39
AMCC 4xx PKA v0.1 @0x04_00114000 size 16384 IRQ 39
Initializing PKA...
PKA Driver Successfully Initialized
Reading pvr value = 12c41c82
irq: irq 29 on host /interrupt-controller0 mapped to virtual irq 40
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
apm82181-adma: Probing AMCC APM82181 ADMA engines...
ata2.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 1/32)
irq: irq 13 on host /interrupt-controller0 mapped to virtual irq 41
AMCC(R) APM82181 ADMA Engine found [1]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
apm82181 adma1: allocated 512 descriptor slots
irq: irq 14 on host /interrupt-controller0 mapped to virtual irq 42
AMCC(R) APM82181 ADMA Engine found [2]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata1.00: ATA-8: WDC WD20EARX-00PASB0, 27.0CR.7, max UDMA/133
ata1.00: 3907209168 sectors, multi 0: LBA48
ata2.00: configured for UDMA/133
apm82181 adma2: allocated 512 descriptor slots
irq: irq 15 on host /interrupt-controller0 mapped to virtual irq 43
AMCC(R) APM82181 ADMA Engine found [3]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
apm82181 adma3: allocated 512 descriptor slots
oprofile: using timer interrupt.
Macsec proc interface Initiliazed
Registered Macsec Interface
IPv4 over IPv4 tunneling driver
ata1.00: configured for UDMA/133
blk_queue_max_hw_segments: set to minimum 1
scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 27.0 PQ: 0 ANSI: 5
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
sd 0:0:0:0: [sda] 3907209168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: Attached scsi generic sg0 type 0
blk_queue_max_hw_segments: set to minimum 1
scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
NET: Registered protocol family 17
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg1 type 0
 sda:
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
 sdb: sdb1 sdb2 sdb3 sdb4
 sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] Attached SCSI disk
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: invalid raid superblock magic on sdb3
md: sdb3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb4
md: sdb4 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda3
md: sda3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda4
md: sda4 does not have a valid v0.90 superblock, not importing!
md: Scanned 8 and added 4 devices.
md: autorun ...
md: considering sda2 ...
md:  adding sda2 ...
md:  adding sda1 ...
md:  adding sdb2 ...
md:  adding sdb1 ...
md: created md0
md: bind<sdb1>
md: bind<sdb2>
md: bind<sda1>
md: bind<sda2>
md: running: <sda2><sda1><sdb2><sdb1>
md0: WARNING: sda2 appears to be on the same physical disk as sda1.
md0: WARNING: sdb2 appears to be on the same physical disk as sdb1.
True protection against single-disk failure might be compromised.
raid1: raid set md0 active with 4 out of 4 mirrors
md0: detected capacity change from 0 to 2047803392
md: ... autorun DONE.
 md0: unknown partition table
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 9:0.
Freeing unused kernel memory: 448k init
Disable EMAC EMI Fix
eth0: link is up, 1000 FDX, pause enabled
eth0: no IPv6 routers present
md: md2 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 512741376
md: md3 stopped.
md: bind<sdb4>
md: bind<sda4>
raid1: raid set md3 active with 1 out of 2 mirrors
md3: detected capacity change from 0 to 1995774484480
md: recovery of RAID array md3
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 2048k window, over a total of 1948998520 blocks.
md: resuming recovery of md3 from checkpoint.
 md3: unknown partition table
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev md3.
 md2: unknown partition table
Adding 500544k swap on /dev/md2.  Priority:-1 extents:1 across:500544k
ufsd: bad vermagic: kernel tainted.
Disabling lock debugging due to kernel taint
ufsd: module license 'unspecified' taints kernel.
ufsd: driver 8.5 (NTFS4LINUX_U85_014_S[2011-09-15-11:41:06]) LBD=ON with delayalloc with ioctl loaded at d4490000
NTFS read/write support included
Big endian platform
Hfs+/HfsX read/write support included
Built_for__WD_APM_82181_2011-08-09_sec

svc: failed to register lockdv1 RPC service (errno 97).
md: cannot remove active disk sda1 from md0 ...
md: cannot remove active disk sda2 from md0 ...
md: cannot remove active disk sdb1 from md0 ...
md: cannot remove active disk sdb2 from md0 ...
Calling led_set_blink with value x
usbco  registered new interface driver usbfs
usbco  registered new interface driver hub
usbco  registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
dwc_otg: version 2.60a 22-NOV-2006
dwc_otg: Shared Tx FIFO mode
dwc_otg: Using DMA mode
dwc_otg dwc_otg.0: DWC OTG Controller
dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1
dwc_otg dwc_otg.0: irq 28, io mem 0x00000000
dwc_otg: Init: Port Power? op_state=1
dwc_otg: Init: Power Port (0)
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DWC OTG Controller
usb usb1: Manufacturer: Linux 2.6.32.11-svn70860 dwc_otg_hcd
usb usb1: SerialNumber: dwc_otg.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
md: md3: recovery done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda4
 disk 1, wo:0, o:1, dev:sdb4
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
usb 1-1: new high speed USB device using dwc_otg and address 2
usb 1-1: New USB device found, idVendor=0781, idProduct=5581
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: Ultra
usb 1-1: Manufacturer: SanDisk
usb 1-1: SerialNumber: 4C530123091014123423
usb 1-1: configuration #1 chosen from 1 choice
usbco  registered new interface driver libusual
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbco  registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:0:0: [sdc] 62566488 512-byte logical blocks: (32.0 GB/29.8 GiB)
usb-storage: device scan complete
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
md: cannot remove active disk sda1 from md0 ...
md: cannot remove active disk sda2 from md0 ...
md: cannot remove active disk sdb1 from md0 ...
md: cannot remove active disk sdb2 from md0 ...
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
LTFileServer:~#
LTFileServer:~#

mount

Code:

LTFileServer:~# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime,barrier=1)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=5M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=5M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
tmpfs on /tmp type tmpfs (rw,size=100M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/DataVolume/cache on /CacheVolume type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/sdc1 on /var/media/Ultra type vfat (rw,utf8,errors=continue,fmask=013,dmask=002,uid=99,gid=1000)
LTFileServer:~#
LTFileServer:~#

parted -l

Code:

LTFileServer:~# parted -l
Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system     Name     Flags
 3      15.7MB  528MB   513MB   linux-swap(v1)  primary  raid
 1      528MB   2576MB  2048MB  ext3            primary  raid
 2      2576MB  4624MB  2048MB  ext3            primary  raid
 4      4624MB  2000GB  1996GB                  primary  raid


Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system     Name     Flags
 3      15.7MB  528MB   513MB   linux-swap(v1)  primary  raid
 1      528MB   2576MB  2048MB  ext3            primary  raid
 2      2576MB  4624MB  2048MB  ext3            primary  raid
 4      4624MB  2000GB  1996GB                  primary  raid


Model: SanDisk Ultra (scsi)
Disk /dev/sdc: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      11.2MB  32.0GB  32.0GB  primary  fat32        lba


Model: Unknown (unknown)
Disk /dev/md0: 2048MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2048MB  2048MB  ext3


Model: Unknown (unknown)
Disk /dev/md2: 513MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system     Flags
 1      0.00B  513MB  513MB  linux-swap(v1)


Error: /dev/md3: unrecognised disk label

LTFileServer:~#
LTFileServer:~#
LTFileServer:~#

From what I have managed to put together by reading left and right the RAID 1 is md0 made from sda and sdb (Hard drives)
And the problem seems to be something on the superblock being corrupted. but if I try to use fsck command to attempt to fix it it...

Code:

LTFileServer:~# fsck /dev/md0
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/md0 is mounted.

WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Do you really want to continue (y/n)? no

check aborted.
LTFileServer:~#

All help and advise is really welcome.

Hi I am not a complete Linux newbie, but I have a challenge that is new to me.

I am wanting to be able to connect to a linux box (Raspberry Pi running Debian) via ssh directly from a single computer. I want to be able to plug in a ethernet cable from a laptop to the Raspberry Pi so that I can configure it via ssh or a webpage.

I have had a few pieces of hardware, routers, printers etc that allow this sort of connection for configuration, I just would like to know how it is done.

My question is how do I set up the /etc/interfaces file to allow the Raspberry Pi to be found by the laptop.

Once configured I would want the Raspberry Pi to obtain its IP address via DHCP when connected to a network.

Any suggestions, ideas would be appreciated.

I am new to drivers development under linux kernel. After starting with the simple examples from the book Linux Device Drivers v3, I realised that the block driver API has been totally changed since the kernel 2.6.31 or maybe later versions, and I couldn't find any documentation about the new API and how to use it. There are just some few comments in the source code.

After struggling for one month I almost had something working but few parts are missing or I misunderstood something.

Here is the situation :

After fetching the request with blk_fetch_request(q), I use the macro __rq_for_each_bio for handling the full request
To transfer the segments one by one I use the macro bio_for_each_segment(bvec, bio, i) that loops over all the segments in a bio

My question is :

I need to do some DMA from/to my device (the dma engine is within the device), that's why I need some address that I could use it to DMA from/to
Which buffer should I use ? for the moment I use the buffer returned by char *buffer=bio_data(bio), Does "buffer" corresponds to the physical buffer that I can use for DMA
How to end the request in this case ? using __blk_end_request_cur(req, 0) ? or using __blk_end_request(req, 0, bytes) ?

If you don't have an answer to any of these questions, where can I find a useful documentation for the new API of the block device drivers.

Hi.


I'm using smstools3 and Sony Ericsson Phones to send SMS. My system did work well with 4 phones, now I want to connect 20.
The issue is that each phone generates two ttyACMXX devices using cdc_acm driver, and for limitations the driver supports up to 32 ACM devices

Code:

Aug 31 09:51:19 smsgw kernel: cdc_acm 2-2:1.1: ttyACM31: USB ACM device
Aug 31 09:51:19 smsgw kernel: cdc_acm 2-2:1.3: ttyACM32: USB ACM device
Aug 31 09:51:19 smsgw kernel: usbco  registered new driver cdc_acm
Aug 31 09:51:19 smsgw kernel: drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
Aug 31 09:51:19 smsgw kernel: usbco  registered new driver cdc_ether
Aug 31 09:51:19 smsgw kernel: usb 2-2: unsupported MDLM descriptors
Aug 31 09:52:01 smsgw kernel: cdc_acm 3-1:1.0: no more free acm devices

From the ttyACM devices created by the driver I only use the first one..

So I was wondering if it is possible to remove a ttyACM from /sys/class/tty/ttyACM1

I tried unlink /dev/ttyACM1, but it persist as a device on /sys/class/tty/

The devices are removed if I disconnect the phone, So I think would be possible also that the driver only create one ttyACM device..

Please guide me...

Thanks in advance.