Hi Pete
(the 'varying a bit) referred to those flexi PCBs. On some bits of HW they are east to replace/refit; on some, it's 50/50 whether you damage things irreparably).
FWIW I have ended up remaking the external DAC hard-wiring mod onto a second Joggler. This one has continued to boot & re-flash OK; I have just installed the latest PnP III onto it. The 'set USB to external DAC' script, which just creates a new /etc/asound.conf, works fine. So it looks like my mods to the first Jogger were unconnected to the problem, & it was just coincidental that it happend at the same time.
I'm guessing the MMC memory is a bit screwed, as discussed earlier. I'll stick to booting Linux Mint or whatever form a pendrive on that one.
Cheers, Jon N
Reflashing and/or EFI chip revisited
Re: Reflashing and/or EFI chip revisited
Good news Jon.
It wouldn't hurt any to reformat the MMC memory on the nonbooting Joggler and check it as your USB stick is booting from the EFI boot flash anyways.
Unrelated and goofing a bit yesterday with the 3rd and 4th documented USB taps inside of the Joggler noticed an odd thing yesterday. I use one Joggler with the external USB sound card. That said I didn't really like using the side USB port so added the two USB connections and went out the back of the Joggler with them. That said noticed that if I plugged the USB sound card directly to the 2.0 port it didn't work like it does on the side USB port. I put a small little mini hub and it was recognized and I was able to plug in the USB sound card into the mini hub. This was all about just changing the footprint a bit as I have this joggler connected to the master bedroom MM center and it makes for cleaner wiring.
It wouldn't hurt any to reformat the MMC memory on the nonbooting Joggler and check it as your USB stick is booting from the EFI boot flash anyways.
Unrelated and goofing a bit yesterday with the 3rd and 4th documented USB taps inside of the Joggler noticed an odd thing yesterday. I use one Joggler with the external USB sound card. That said I didn't really like using the side USB port so added the two USB connections and went out the back of the Joggler with them. That said noticed that if I plugged the USB sound card directly to the 2.0 port it didn't work like it does on the side USB port. I put a small little mini hub and it was recognized and I was able to plug in the USB sound card into the mini hub. This was all about just changing the footprint a bit as I have this joggler connected to the master bedroom MM center and it makes for cleaner wiring.
- Pete
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Auto mater
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Auto mater
Re: Reflashing and/or EFI chip revisited
Hi Pete
Yes, I am going to play with the MMC memory on the non-booting Joggler at some point. I did so, a little, a while ago, but will try again in anger next time. I used 'badblocks' to check for errors IIRC, but there are probably other linux facilities for testing such memory.
Re. USB modes and the internal points, you probably know this but according to:
http://www.jogglerwiki.com/wiki/Additional_USB_Ports
some of the 'extra' ports are USB 1.1 and USB 2.0 capable, some only USB 2.0. My DAC is USB 1.1 (I wonder if they all are? Haven't checked) and so I used what I think of as the 'third' port, listed as TP137 & TP 138.
I did wonder if I would have to modify the 'run from USB' script (ie. change /etc/asound.conf) to match, but it doesn't seem so. I guess if I had also installed a second USB socket on the side, and connected that to a DAC as well, I'd have to do so. I started to look at what USB devices were reported (/sys/bus/usb/devices, from memory), but haven't wandered down that road too far as yet.
Cheers, Jon N
Yes, I am going to play with the MMC memory on the non-booting Joggler at some point. I did so, a little, a while ago, but will try again in anger next time. I used 'badblocks' to check for errors IIRC, but there are probably other linux facilities for testing such memory.
Re. USB modes and the internal points, you probably know this but according to:
http://www.jogglerwiki.com/wiki/Additional_USB_Ports
some of the 'extra' ports are USB 1.1 and USB 2.0 capable, some only USB 2.0. My DAC is USB 1.1 (I wonder if they all are? Haven't checked) and so I used what I think of as the 'third' port, listed as TP137 & TP 138.
I did wonder if I would have to modify the 'run from USB' script (ie. change /etc/asound.conf) to match, but it doesn't seem so. I guess if I had also installed a second USB socket on the side, and connected that to a DAC as well, I'd have to do so. I started to look at what USB devices were reported (/sys/bus/usb/devices, from memory), but haven't wandered down that road too far as yet.
Cheers, Jon N
Re: Reflashing and/or EFI chip revisited
Yeah here my soundcard was a 2.0 USB sound card and it was connected to the USB port inside. That said it wouldn't come up until I put a hub into place. Ran into issue though because it seems that it started to stutter on the radio broadcasts. Must be the little hub (it saids its a 2.0 hub). I connected to the side port and all was fine. I am using the same port though on another Joggler to boot up via USB stick which doesn't make sense to me.
So I am currently tapped in to: TP139 and TP140 for the 2.0 hub.
So I am currently tapped in to: TP139 and TP140 for the 2.0 hub.
- Pete
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Auto mater
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens
Auto mater