• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  Hardware and U-Boot firmware / Hardware / Re: Poll: Sheeva Plug Power Supply failures - does the mains voltage matter? on: April 02, 2010, 01:11:24 PM
How about replacing the 'no failures' option with two:  'no failures and I run 120' and 'no failures and I run 240'?  Maybe then we can get a better handle on the total number of lo/hi voltage runners out there?

Hmm.  Although I've left this poll open, and thus the results may be subject to change, it surely appears that the PS failures that have been plaguing some forum members recently seem to only be affecting those Plugs being powered from 240V mains.  Perhaps one or more of the PS components are not up to the task of handling the higher voltage.

I wonder in 240V locales whether it might be worth powering the Plug through one of those small-wattage 240V-to-120V step-down transformers that they sell here in the US for tourists venturing overseas?  These small transformers are fairly cheap and easily found by googling for them.  Might be cheap insurance.  Just a thought.
2  Hardware and U-Boot firmware / U-Boot stuff / How to specify which USB drive to boot from? on: September 17, 2009, 10:55:20 AM
Hi again, all,

I'm about to get back into this after a bit of a break.  Currently my SheevaPlug MythTV system has a USB hub with two devices on it:  a 500 GB hard drive and a Hauppauge TV tuner.  (Originally I had my root filesystem on SD, but then it got corrupted when I inserted/removed USB while the system was on, and started running with the root on the hard drive.)

Since I plan to leave my system on 24/7 shortly, and would like the HDD to stay spun down most of the time (which it does automatically when not accessed for a few minutes), I'd like to migrate my root filesystem to a USB flash drive to be on the hub along with the HDD (now just to store videos) and the tuner.

While my system boots reliably when powered on, thanks to information provided by others in this forum, I'm curious what will happen when I add another storage device.  In particular, I'm wondering how I should set my boot parameters up to tell it *which* USB storage device I want it to pull the uImage from, and which partition holds the root filesystem.

In a 'grub' world one can use UUIDs to unambiguously specify which partition / filesystem is desired for the root, and I believe that a filesystem or partition's 'label' can also be used for disambiguation, but I don't recall seeing anywhere on this forum how either of these can be used in the SheevaPlug to specify the target of interest.

I suppose I could experimentally determine which port on my hub I should plug something into to have it always identified as, e.g., "usb 0:2", but I feel the cleaner solution is for it to be "position-independent".

Anyway, suggestions are welcome before I trudge forth on trial and error (hopefully not trashing my HDD in the process), probably this weekend.

Thanks,

Charles Green
3  Linux Stuff / Kernel / Re: 2.6.30 new release on: June 25, 2009, 06:41:25 PM
MythTV works with the HVR-1950 on this kernel / module set.  Just confirmed NTSC recording and playback with video + audio (I haven't tried QAM or ATSC yet, left as an exercise for others at least until I get the time to bend my 'if it ain't broke' rule and alter my working configuration).

Thanks yet again, cbxbiker61!

-Charles Green
4  Linux Stuff / Kernel / Re: [SOLVED] pvrusb2 driver for SheevaPlug kernel (MythTV) on: June 23, 2009, 07:59:12 PM
Solstice,

The primary guide for my setting this up was at http://www.isely.net/pvrusb2/pvrusb2.html.  That site might mention the HVR-950Q; I don't recall.  With respect to the 1950 firmware, I believe I either put it in /lib/firmware/ or /lib/firmware/<exact kernel version>/ as you probably did.

If by what you say you see below (MJPEG / MPEG4 vs. MPEG2) you're referring to what MythTV shows you as available in its setup, I seem to remember that I had to type in /dev/video0 on the MPEG2 selection (I saw that trick mentioned on some forum or board somewhere), after which it had no problem identifying the card, but I don't believe it was presented automatically as a choice the first time through, which may have led you to believe MythTV couldn't use it.  (I'm being vague as the system isn't up at the moment - I need more time to finish setting up a slave backend / frontend to really make use of it, so it's powered off until I get a chance to play around with it again.)

Hope this helps,

-Charles
5  General Category / Application ideas and development Q/A / Re: MythTV, anyone? on: June 11, 2009, 01:37:24 PM
I did eventually get everything straightened out, as did another member 'pushbx' who posted an excellent 'howto' accessible via the 'Success Stories' board.

Thanks!

-Charles Green
6  Linux Stuff / Kernel / Re: [SOLVED] Internal error: Oops: 5 from 2.6.22.18 #1 on: June 11, 2009, 01:33:10 PM
My "solution" was simply to go with a newer kernel, which I needed anyway for the modules to support the hardware I have since added.

Thanks,

Charles
7  Linux Stuff / Kernel / [SOLVED] Re: pvrusb2 driver for SheevaPlug kernel (MythTV) on: June 11, 2009, 01:21:47 PM
Not sure what the problem with the kernel was, but eventually I found the time to grab a 'git' snapshot from Marvell and pounded it with "config/make" cycles until it  submitted.

-Charles Green
8  Linux Stuff / Kernel / Re: Anyone able to upload firmware via USB with their kernel? on: June 11, 2009, 01:15:02 PM
All,

Thanks for the responses!  I was using a kernel provided elsewhere as I was trying to make some sort of progress while busy with other things, so I'm not 100% certain how it was configured.

More recently, however, I found the time to grab a 'git' snapshot from Marvell, reconfigure to add the necessary modules, rebuilt, repeated the cycle a few times, and finally got everything recognized and working.

Thanks again!

-Charles
9  Linux Stuff / Kernel / Request for upcoming 2.6.30 on: June 11, 2009, 01:08:47 PM
It sounds like the "official" 2.6.30 kernel is imminent:

    http://thread.gmane.org/gmane.linux.kernel/849020

Cbxbiker61, would it be possible to get the following modules added to support the Hauppauge HVR-1950 MPEG3 USB tuner?  (I believe a few of them are already there.)

    s5h1411
    tda18271
    tda8290
    tuner
    cx25840
    pvrusb2
    dvb_core
    cx2341x
    v4l2_common
    videodev
    v4l1_compat
    tveeprom

Thanks!

-Charles Green
10  General Category / Success stories / HVR-1950 working on SheevaPlug with MythTV on: June 10, 2009, 04:19:36 AM
Hi, all,

To get the Hauppauge MPEG-2 USB tuner running on the SheevaPlug, I grabbed the 'git' snapshot from the Marvell repository as described elsewhere here, took 'cbxbiker61's config file from the -rc8 version of his most excellent kernel series (renaming it .config and replacing the repository's .config file with it), then 'make menuconfig'ed it to add the necessary support as described on isely.net.

While watching "live" TV (actually recording to a local file on a USB drive attached to the 'plug with the tuner via USB 2.0 hub and simultaneously playing it back from a frontend on a different machine), after 5 minutes the load average hovers around 0.22, so I don't anticipate any major issues with usability as a backend.

I've passed the information along to cbxbiker61 so hopefully this will be included in the next generally-available kernel, but if you're in a position to configure your own kernel, the following additional modules are being incorporated when the device is plugged in:

Module                  Size  Used by
s5h1411                 9856  1
tda18271               34808  2
tda8290                13884  2
tuner                  21036  1
cx25840                27716  1
pvrusb2               140728  0
dvb_core               88108  1 pvrusb2
cx2341x                13740  1 pvrusb2
v4l2_common            15096  4 tuner,cx25840,pvrusb2,cx2341x
videodev               34408  4 tuner,cx25840,pvrusb2,v4l2_common
v4l1_compat            16104  2 pvrusb2,videodev
tveeprom               11144  1 pvrusb2

I'm now able to do NTSC (analog) recording; haven't attempted digital yet (I have an antenna in my attic for ATSC, and there are a few clear-QAM channels on our cable service), but I plan to give that a shot after a "standard" kernel comes out with this support.

Enjoy,

Charles
11  Linux Stuff / General Linux questions / Re: Getting Started with the cross compiler on: June 05, 2009, 10:49:56 AM
Hi,

I don't use the cross-compiler, but I'm guessing in your case (especially since you are explicitly 'pathing' to 'gcc') that you need to add /home/gcc/arm-none-linux-gnueabi/bin to your $PATH?

This assumes that the directory actually contains 'cc1'...

Hope this helps,

Charles
12  Linux Stuff / Kernel / [SOLVED] Anyone able to upload firmware via USB with their kernel? on: May 27, 2009, 04:28:25 AM
Hi all,

I'm attempting to get the Hauppauge HVR-1950 USB tuner running on the SheevaPlug.  This works fine on my Intel-based Ubuntu systems, but plugging it into the SheevaPlug all I see in the kernel log is two lines announcing the USB device itself.  I've put the three .fw files it requires into /lib/firmware, but there's no evidence that the request for them is getting through the USB driver, or whatever mechanism is used, to 'udev'.

Here's what the SheevaPlug shows:

usb 1-1.3: new high speed USB device using orion-ehci and address 5
usb 1-1.3: configuration #1 chosen from 1 choice

Here's what my Intel 'hardy' system shows:

[ 2282.660029] usb 1-8: new high speed USB device using ehci_hcd and address 4
[ 2282.797228] usb 1-8: configuration #1 chosen from 1 choice
[ 2282.952304] usbcore: registered new interface driver pvrusb2
[ 2282.952311] pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
[ 2282.952314] pvrusb2: Debug mask is 31 (0x1f)
[ 2283.948095] usb 1-8: firmware: requesting v4l-pvrusb2-73xxx-01.fw
...

And here's what my Intel 'jaunty' system shows:

[  593.490018] usb 1-4: new high speed USB device using ehci_hcd and address 2
[  593.644339] usb 1-4: configuration #1 chosen from 1 choice
[  593.698637] Linux video capture interface: v2.00
[  593.763880] usbcore: registered new interface driver pvrusb2
[  593.763905] pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
[  593.763910] pvrusb2: Debug mask is 31 (0x1f)
[  594.760164] usb 1-4: firmware: requesting v4l-pvrusb2-73xxx-01.fw
...

(The extra "Linux video capture interface" message in this case appears to be coming from videodev.ko)

Looking for 'firmware' on the forums here, the only references I see are to the SheevaPlug firmware itself, so it occurred to me that perhaps no one else is (yet) making use of any USB devices which require firmware downloads.  Does anyone know if the USB subsystem on the SheevaPlug supports this, or if there are any other impediments?

Thanks,

Charles Green
13  Linux Stuff / Kernel / Re: pvrusb2 driver for SheevaPlug kernel (MythTV) on: May 24, 2009, 05:33:50 PM
[Update:  I see my Intel Linux 'hardy' MythTV box has a 'firmware_helper' executable in /lib/udev, whereas the 'jaunty' SheevaPlug and Intel box have a 'firmware.sh' script in /lib/udev.]

OK, after losing my /usr filesystem (note to self:  apparently unplugging a USB hub from the SheevaPlug can cause corruption of an SD card) I re-established my Sheeva distribution on the external USB drive which I got in anticipation of getting this last piece to the MythTV puzzle working.  With a kernel provided by 'pushbx' that incorporates the 'pvrusb2' driver (not as a module), and the necessary firmware in /lib/firmware, here's what I see when I plug in the HVR-1950:

Code:
usb 1-1.3: new high speed USB device using orion-ehci and address 5
usb 1-1.3: configuration #1 chosen from 1 choice

This looks to me to be the same as the kernel without the driver.  Hmm...

Next I thought that perhaps the firmware wasn't being found, so I renamed it on my Intel 'hardy' MythTV box (on which I have successfully used the tuner) to see what would happen if it's not found, and plugged it in there.  I got:

Code:
[347747.808029] usb 1-8: new high speed USB device using ehci_hcd and address 17
[347747.945182] usb 1-8: configuration #1 chosen from 1 choice
[347748.944111] usb 1-8: firmware: requesting v4l-pvrusb2-73xxx-01.fw
[347748.951269] pvrusb2: ***WARNING*** Device fx2 controller firmware seems to be missing.
[347748.951274] pvrusb2: Did you install the pvrusb2 firmware files in their proper location?
[347748.951277] pvrusb2: request_firmware unable to locate fx2 controller file v4l-pvrusb2-73xxx-01.fw
[347748.951280] pvrusb2: Failure uploading firmware1
[347748.951283] pvrusb2: Device initialization was not successful.
[347748.951286] pvrusb2: Giving up since device microcontroller firmware appears to be missing.

My understanding is that 'udev' handles loading of the firmware, and that's certainly running on the SheevaPlug.

I also tried this on a basic 'jaunty' install on a third computer, and noticed a new "third line" which is missing from the Sheeva (in the following case, firmware was present, and lines after obvious success are deleted); the following also looks identical to the 'success' case on my Hardy MythTV box, with the exception of the new third line, which is apparently specific to Jaunty:

Code:
[  593.490018] usb 1-4: new high speed USB device using ehci_hcd and address 2
[  593.644339] usb 1-4: configuration #1 chosen from 1 choice
[  593.698637] Linux video capture interface: v2.00
[  593.763880] usbcore: registered new interface driver pvrusb2
[  593.763905] pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
[  593.763910] pvrusb2: Debug mask is 31 (0x1f)
[  594.760164] usb 1-4: firmware: requesting v4l-pvrusb2-73xxx-01.fw
[  594.781660] pvrusb2: Device microcontroller firmware (re)loaded; it should now reset and reconnect.
[  596.328962] usb 1-4: USB disconnect, address 2
[  596.329440] pvrusb2: Device being rendered inoperable
[  596.600019] usb 1-4: new high speed USB device using ehci_hcd and address 3
[  596.759694] usb 1-4: configuration #1 chosen from 1 choice
[  596.842134] cx25840' 1-0044: cx25843-24 found @ 0x88 (pvrusb2_a)
[  596.912732] tuner' 1-0042: chip found @ 0x84 (pvrusb2_a)
[  596.937121] tveeprom 1-00a2: Hauppauge model 75111, rev C3E9, serial# 5371386
...

So perhaps the next thing we should see on the SheevaPlug is "Linux video capture interface: v2.00"?  A quick 'grep -l' on the Intel Jaunty system reveals this line is somewhere in videodev.ko, so if that driver is compiled into the kernel I'm now running, I would expect to see that message, right?  (Interestingly, 'grep -l' against the SheevaPlug kernel doesn't seem to be very fruitful, even the word 'video' didn't match...)  Also, given that the 'videodev' module was present in the 2.6.30-rc4 image provided by 'cbxbiker61', I would have thought this third line might have shown up there, even without the additional drivers specific to the HVR-1950.

Here's the output of 'udevmonitor', or 'udevadm monitor', on the SheevaPlug:

Code:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1243272711.974440] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4 (usb)
KERNEL[1243272711.974573] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0 (usb)
KERNEL[1243272711.974672] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep81 (usb_endpoint)
KERNEL[1243272711.974768] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep84 (usb_endpoint)
KERNEL[1243272711.974862] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep88 (usb_endpoint)
KERNEL[1243272711.974956] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep01 (usb_endpoint)
KERNEL[1243272711.975051] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep02 (usb_endpoint)
KERNEL[1243272711.975145] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep86 (usb_endpoint)
KERNEL[1243272711.975238] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/usb_device/usbdev1.6 (usb_device)
KERNEL[1243272711.975330] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/usb_endpoint/usbdev1.6_ep00 (usb_endpoint)
UDEV  [1243272711.976139] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4 (usb)
UDEV  [1243272711.989564] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0 (usb)
UDEV  [1243272711.995778] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/usb_device/usbdev1.6 (usb_device)
UDEV  [1243272712.008812] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep88 (usb_endpoint)
UDEV  [1243272712.014952] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep84 (usb_endpoint)
UDEV  [1243272712.039559] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/usb_endpoint/usbdev1.6_ep00 (usb_endpoint)
UDEV  [1243272712.041717] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep86 (usb_endpoint)
UDEV  [1243272712.042514] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep02 (usb_endpoint)
UDEV  [1243272712.043252] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep01 (usb_endpoint)
UDEV  [1243272712.046061] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.0/usb_endpoint/usbdev1.6_ep81 (usb_endpoint)

And on the basic Jaunty, non-MythTV system:

Code:
monitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent

UEVENT[1243281061.483320] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4 (usb)
UDEV  [1243281061.488216] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4 (usb)
UEVENT[1243281061.489453] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0 (usb)
UEVENT[1243281061.489493] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep81 (usb_endpoint)
UEVENT[1243281061.489526] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep84 (usb_endpoint)
UEVENT[1243281061.489553] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep88 (usb_endpoint)
UEVENT[1243281061.489579] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep01 (usb_endpoint)
UEVENT[1243281061.489604] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep02 (usb_endpoint)
UEVENT[1243281061.489628] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep86 (usb_endpoint)
UEVENT[1243281061.489652] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/usb_endpoint/usbdev1.2_ep00 (usb_endpoint)
UDEV  [1243281061.496395] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/usb_endpoint/usbdev1.2_ep00 (usb_endpoint)
UEVENT[1243281061.527453] add      /module/tveeprom (module)
UEVENT[1243281061.529937] add      /module/v4l1_compat (module)
UDEV  [1243281061.530909] add      /module/tveeprom (module)
UEVENT[1243281061.537592] add      /module/videodev (module)
UEVENT[1243281061.537633] add      /class/video4linux (class)
UDEV  [1243281061.538136] add      /module/v4l1_compat (module)
UEVENT[1243281061.543161] add      /module/v4l2_common (module)
UDEV  [1243281061.544996] add      /module/videodev (module)
UDEV  [1243281061.547085] add      /class/video4linux (class)
UDEV  [1243281061.549125] add      /module/v4l2_common (module)
UEVENT[1243281061.554578] add      /module/cx2341x (module)
UDEV  [1243281061.556455] add      /module/cx2341x (module)
UEVENT[1243281061.573547] add      /module/dvb_core (module)
UEVENT[1243281061.573586] add      /class/dvb (class)
UDEV  [1243281061.575452] add      /module/dvb_core (module)
UDEV  [1243281061.577523] add      /class/dvb (class)
UEVENT[1243281061.597762] add      /module/pvrusb2 (module)
UDEV  [1243281061.599338] add      /module/pvrusb2 (module)
UEVENT[1243281061.600171] add      /class/pvrusb2 (class)
UDEV  [1243281061.601841] add      /class/pvrusb2 (class)
UEVENT[1243281061.602813] add      /bus/usb/drivers/pvrusb2 (drivers)
UDEV  [1243281061.606976] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0 (usb)
UDEV  [1243281061.610596] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep81 (usb_endpoint)
UDEV  [1243281061.613178] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep84 (usb_endpoint)
UDEV  [1243281061.615698] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep88 (usb_endpoint)
UDEV  [1243281061.618224] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep01 (usb_endpoint)
UDEV  [1243281061.620833] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep02 (usb_endpoint)
UDEV  [1243281061.623392] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep86 (usb_endpoint)
UDEV  [1243281061.625689] add      /bus/usb/drivers/pvrusb2 (drivers)
UEVENT[1243281062.599177] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/firmware/1-4 (firmware)
UEVENT[1243281062.615874] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/firmware/1-4 (firmware)
UDEV  [1243281062.617431] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/firmware/1-4 (firmware)
UDEV  [1243281062.618775] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/firmware/1-4 (firmware)
UEVENT[1243281064.168606] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep81 (usb_endpoint)
UEVENT[1243281064.168801] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep84 (usb_endpoint)
UEVENT[1243281064.168863] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep88 (usb_endpoint)
UEVENT[1243281064.168891] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep01 (usb_endpoint)
UEVENT[1243281064.168915] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep02 (usb_endpoint)
UEVENT[1243281064.168941] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep86 (usb_endpoint)
UEVENT[1243281064.168972] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0 (usb)
UEVENT[1243281064.168998] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/usb_endpoint/usbdev1.2_ep00 (usb_endpoint)
UEVENT[1243281064.169035] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4 (usb)
UDEV  [1243281064.171654] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep81 (usb_endpoint)
UDEV  [1243281064.174444] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep84 (usb_endpoint)
UDEV  [1243281064.177230] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep88 (usb_endpoint)
UDEV  [1243281064.180085] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep01 (usb_endpoint)
UDEV  [1243281064.182852] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep02 (usb_endpoint)
UDEV  [1243281064.185641] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.2_ep86 (usb_endpoint)
UDEV  [1243281064.189859] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0 (usb)
UDEV  [1243281064.192676] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4/usb_endpoint/usbdev1.2_ep00 (usb_endpoint)
UDEV  [1243281064.197221] remove   /devices/pci0000:00/0000:00:10.3/usb1/1-4 (usb)
UEVENT[1243281064.598614] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4 (usb)
UEVENT[1243281064.599521] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0 (usb)
UDEV  [1243281064.607728] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4 (usb)
UEVENT[1243281064.609733] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep81 (usb_endpoint)
UEVENT[1243281064.609782] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep84 (usb_endpoint)
UEVENT[1243281064.609808] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep88 (usb_endpoint)
UEVENT[1243281064.609833] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep01 (usb_endpoint)
UEVENT[1243281064.609858] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep02 (usb_endpoint)
UEVENT[1243281064.609882] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep86 (usb_endpoint)
UEVENT[1243281064.609906] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/usb_endpoint/usbdev1.3_ep00 (usb_endpoint)
UDEV  [1243281064.614873] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0 (usb)
UDEV  [1243281064.620415] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep81 (usb_endpoint)
UDEV  [1243281064.623460] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep84 (usb_endpoint)
UDEV  [1243281064.626507] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep88 (usb_endpoint)
UEVENT[1243281064.630150] add      /module/cx25840 (module)
UEVENT[1243281064.630193] add      /bus/i2c/drivers/cx25840' (drivers)
UEVENT[1243281064.630215] add      /bus/i2c/drivers/cx25840 (drivers)
UDEV  [1243281064.635420] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep01 (usb_endpoint)
UDEV  [1243281064.638459] add      /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:1.0/usb_endpoint/usbdev1.3_ep02

Any thoughts on why the Intel Ubuntu system announces the request for firmware and the SheevaPlug system doesn't?  I see that the firmware request log line is tagged 'usb' rather than 'pvrusb2', so presumably the pvrusb2 driver isn't even involved yet at this point??

Thanks for any suggestions,

Charles
14  Hardware and U-Boot firmware / Hardware / Corrupt SD partition table after unplugging USB? on: May 22, 2009, 04:17:14 AM
Hi,

I've had a pretty stable system for a number of weeks; using the delivered root filesystem I've put my '/usr' on an SD card, added swap, installed/built software including MythTV backend, and installed a couple of kernels.

Yesterday I installed a monolithic kernel including 'pvrusb2' driver to check out a USB tuner for MythTV.  Plugging in the tuner reported a couple of USB device lines in the kernel log, but no messages about loading firmware, etc.  So I decided to unplug it (couple more lines), and unplug the USB hub (which I've been using with no problems) to plug the tuner in directly.  I noticed several lines, including a couple about the flash (mmcblk0p1), thought "That's weird", plugged the USB tuner directly into the unit, saw the same two USB kernel log lines, and decided the USB hub wasn't interfering with the tuner getting its firmware via udev or whatever.

However, I've proceeded to continue to see more complaints about mmcblk0p1, tried rebooting, and e2fsck told me it couldn't make sense of the /usr filesystem.  What I've gathered from the following is that the partition table on the SD card may be corrupted; hope hope hope that if I simply re-'fdisk' it with the identical parameters I used to begin with, the /usr/ filesystem itself will still be there, else I guess I'll be restarting from near ground zero (perhaps this time putting the root filesystem on the new USB hard drive I just got).

Has anyone else experienced any relationship between unplugging USB devices and losing data on the SD card?  Any 'success stories' on easily recovering?  I've seen a few notes about flash corruption, both onboard and SD, but didn't notice any correlation with USB devices.  (I also had the serial console cable operational at the time, since I'd just had to change boot parameters for the new kernel, and I've seen references to that causing various types of instability, though again not flash corruption per se.)

Thanks,

Charles

Code:
* Checking file systems...
fsck 1.41.4 (27-Jan-2009)
fsck.ext3: No such file or directory while trying to open /dev/mmcblk0p1
/dev/mmcblk0p1:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Seek to 1014479360:Invalid argument
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
fsck died with exit status 9
   ...fail!
 * File system check failed.
A log is being saved in /var/log/fsck/checkfs if that location is writable.
Please repair the file system manually.
 * A maintenance shell will now be started.
CONTROL-D will terminate this shell and resume system boot.
Give root password for maintenance
(or type Control-D to continue):
Login incorrect.
Give root password for maintenance
(or type Control-D to continue):
bash: no job control in this shell
bash: groups: command not found
bash: dircolors: command not found
root@debian:~# fsck
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext3: No such file or directory while trying to open /dev/mmcblk0p1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Seek to 1014479360:Invalid argument
root@debian:~# e2fsck -b 8193 /dev/mmcblk0p1
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: No such file or directory while trying to open /dev/mmcblk0p1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
15  Linux Stuff / Kernel / Re: pvrusb2 driver for SheevaPlug kernel (MythTV) on: May 20, 2009, 05:46:05 PM
OK, after trying a few strategies on a different Ubuntu system I finally succeeded in upgrading the kernel on my existing 'hardy' MythTV box to 2.6.28-11-generic.  I then extracted the firmware from the CD using the instructions and script from isley.net, plugged in the HVR-1950, et viola:
Code:
May 20 20:01:58 ubuntu kernel: [ 1172.204064] usb 1-8: new high speed USB device using ehci_hcd and address 4
May 20 20:01:58 ubuntu kernel: [ 1172.345370] usb 1-8: configuration #1 chosen from 1 choice
May 20 20:01:58 ubuntu kernel: [ 1172.459375] usbcore: registered new interface driver pvrusb2
May 20 20:01:59 ubuntu kernel: [ 1172.460605] pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
May 20 20:01:59 ubuntu kernel: [ 1172.460614] pvrusb2: Debug mask is 31 (0x1f)
May 20 20:01:59 ubuntu kernel: [ 1173.456176] usb 1-8: firmware: requesting v4l-pvrusb2-73xxx-01.fw
May 20 20:01:59 ubuntu kernel: [ 1173.459936] pvrusb2: Device microcontroller firmware (re)loaded; it should now reset and reconnect.
May 20 20:02:00 ubuntu kernel: [ 1173.491686] usb 1-8: USB disconnect, address 4
May 20 20:02:00 ubuntu kernel: [ 1173.492618] pvrusb2: Device being rendered inoperable
May 20 20:02:01 ubuntu kernel: [ 1175.244029] usb 1-8: new high speed USB device using ehci_hcd and address 5
May 20 20:02:01 ubuntu kernel: [ 1175.385634] usb 1-8: configuration #1 chosen from 1 choice
May 20 20:02:02 ubuntu kernel: [ 1175.531722] tuner' 2-0042: chip found @ 0x84 (pvrusb2_a)
May 20 20:02:02 ubuntu kernel: [ 1175.552932] cx25840' 2-0044: cx25843-24 found @ 0x88 (pvrusb2_a)
May 20 20:02:02 ubuntu kernel: [ 1175.574172] tveeprom 2-00a2: Hauppauge model 75111, rev C3E9, serial# 5371386
May 20 20:02:02 ubuntu kernel: [ 1175.574178] tveeprom 2-00a2: MAC address is 00-0D-FE-51-F5-FA
May 20 20:02:02 ubuntu kernel: [ 1175.574181] tveeprom 2-00a2: tuner model is Philips 18271_8295 (idx 149, type 54)
May 20 20:02:02 ubuntu kernel: [ 1175.574185] tveeprom 2-00a2: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
May 20 20:02:02 ubuntu kernel: [ 1175.574188] tveeprom 2-00a2: audio processor is CX25843 (idx 37)
May 20 20:02:02 ubuntu kernel: [ 1175.574191] tveeprom 2-00a2: decoder processor is CX25843 (idx 30)
May 20 20:02:02 ubuntu kernel: [ 1175.574194] tveeprom 2-00a2: has radio, has IR receiver, has IR transmitter
May 20 20:02:02 ubuntu kernel: [ 1175.574202] pvrusb2: Supported video standard(s) reported available in hardware: PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB
May 20 20:02:02 ubuntu kernel: [ 1175.574207] pvrusb2: Mapping standards mask=0x300b700 (PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB)
May 20 20:02:02 ubuntu kernel: [ 1175.574211] pvrusb2: Setting up 6 unique standard(s)
May 20 20:02:02 ubuntu kernel: [ 1175.574215] pvrusb2: Set up standard idx=0 name=PAL-M
May 20 20:02:02 ubuntu kernel: [ 1175.574219] pvrusb2: Set up standard idx=1 name=PAL-N
May 20 20:02:02 ubuntu kernel: [ 1175.574222] pvrusb2: Set up standard idx=2 name=PAL-Nc
May 20 20:02:02 ubuntu kernel: [ 1175.574225] pvrusb2: Set up standard idx=3 name=NTSC-M
May 20 20:02:02 ubuntu kernel: [ 1175.574228] pvrusb2: Set up standard idx=4 name=NTSC-Mj
May 20 20:02:02 ubuntu kernel: [ 1175.574231] pvrusb2: Set up standard idx=5 name=NTSC-Mk
May 20 20:02:02 ubuntu kernel: [ 1175.574235] pvrusb2: Initial video standard (determined by device type): NTSC-M
May 20 20:02:02 ubuntu kernel: [ 1175.574246] pvrusb2: Device initialization completed successfully.
May 20 20:02:02 ubuntu kernel: [ 1175.574350] pvrusb2: registered device video2 [mpeg]
May 20 20:02:02 ubuntu kernel: [ 1175.574359] DVB: registering new adapter (pvrusb2-dvb)
May 20 20:02:02 ubuntu kernel: [ 1175.601255] cx25840' 2-0044: firmware: requesting v4l-cx25840.fw
May 20 20:02:04 ubuntu kernel: [ 1177.867104] cx25840' 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
May 20 20:02:04 ubuntu kernel: [ 1177.984545] tda829x 2-0042: setting tuner address to 60
May 20 20:02:04 ubuntu kernel: [ 1178.030929] tda18271 2-0060: creating new instance
May 20 20:02:04 ubuntu kernel: [ 1178.065612] TDA18271HD/C1 detected @ 2-0060
May 20 20:02:05 ubuntu kernel: [ 1179.232655] tda829x 2-0042: type set to tda8295+18271
May 20 20:02:09 ubuntu kernel: [ 1182.590891] cx25840' 2-0044: Video signal:              present
May 20 20:02:09 ubuntu kernel: [ 1182.590896] cx25840' 2-0044: Detected format:           NTSC-M
May 20 20:02:09 ubuntu kernel: [ 1182.590899] cx25840' 2-0044: Specified standard:        NTSC-M
May 20 20:02:09 ubuntu kernel: [ 1182.590902] cx25840' 2-0044: Specified video input:     Composite 7
May 20 20:02:09 ubuntu kernel: [ 1182.590905] cx25840' 2-0044: Specified audioclock freq: 48000 Hz
May 20 20:02:09 ubuntu kernel: [ 1182.598049] cx25840' 2-0044: Detected audio mode:       forced mode
May 20 20:02:09 ubuntu kernel: [ 1182.598057] cx25840' 2-0044: Detected audio standard:   forced audio standard
May 20 20:02:09 ubuntu kernel: [ 1182.598062] cx25840' 2-0044: Audio muted:               no
May 20 20:02:09 ubuntu kernel: [ 1182.598066] cx25840' 2-0044: Audio microcontroller:     stopped
May 20 20:02:09 ubuntu kernel: [ 1182.598071] cx25840' 2-0044: Configured audio standard: automatic detection
May 20 20:02:09 ubuntu kernel: [ 1182.598076] cx25840' 2-0044: Configured audio system:   BTSC
May 20 20:02:09 ubuntu kernel: [ 1182.598080] cx25840' 2-0044: Specified audio input:     External
May 20 20:02:09 ubuntu kernel: [ 1182.598086] cx25840' 2-0044: Preferred audio mode:      stereo
May 20 20:02:11 ubuntu kernel: [ 1184.981530] DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
May 20 20:02:11 ubuntu kernel: [ 1184.983409] tda829x 2-0042: type set to tda8295
May 20 20:02:11 ubuntu kernel: [ 1185.040806] tda18271 2-0060: attaching existing instance
I then went into mythtv-setup, selected the new tuner as an 'MPEG-2 card', scanned for channels, brought the backend up again, and simultaneously recorded two programs on my two tuners to confirm that it worked.

A check with 'lsmod' shows the following modules being used:

pvrusb2
dvb_core
cx2341x
tveeprom
v4l2_common
videodev
v4l1_compat

Again, the last three are being supplied in the kernels supplied by 'cbxbiker61' (thanks again!), so if anyone can post a kernel including these additional modules, I'll be happy to give it a whirl and finish my writeup.

Thanks,

Charles Green
Pages: [1] 2