Re: [Om2008.8 - testing] - alsa: No soundcards found...
On Wed, Sep 17, 2008 at 7:04 PM, Benedikt Schindler [EMAIL PROTECTED] wrote: how could i check, if my system is realy booting the right kernel? Does the info here help you? http://wiki.openmoko.org/wiki/FAQ#How_do_I_find_out_what_image_versions_are_in_use_on_the_phone.3F HTH Ed. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: (om2008.8-update)(gta02) qpe hogs 80% of cpu, kills battery
Thanks - that is useful (although I agree I've seen it in earlier
posts, I wasn't running Qtopia then, so this is useful) :-)
Cheers
Ed.
On Wed, Sep 17, 2008 at 9:29 PM, Yaroslav Halchenko
[EMAIL PROTECTED] wrote:
if you have lots of files on your /media/card -- then you are doomed to
wait for qpe to finish scanning them on start
or just edit Storage.conf which is I believe under
/opt/Qtopia/etc/default
and say that your /media/card has nothing interesting for qtopia ;-)
PS more details could be found in earlier posts on the lists
On Wed, 17 Sep 2008, Tom Yates wrote:
On Wed, 17 Sep 2008, Edgar D' Souza wrote:
On Wed, Sep 17, 2008 at 5:21 PM, Tom Yates [EMAIL PROTECTED] wrote:
[pid 1724] stat64(/home/root/.config/Trolltech.conf,
{st_mode=S_IFREG|0600, st_size=4470, ...}) = 0
[pid 1724]
stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xbefaed98) = -1 ENOENT (No such file or directory)
[pid 1724]
stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf, 0xa385f8)
= -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0xbefaed98)
= -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0x4cd618) =
-1 ENOENT (No such file or directory)
Hope you won't mind a possibly silly question, but: is your Qtopia
rootfs on SDcard or on NAND flash?
NAND flash, as is /home/root. i have the SDcard mounted on /media/card,
and i only keep audio tracks and OSM tiles on it.
--
.-.
=-- /v\ =
Keep in touch// \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User^^-^^[17]
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
GPRS in FDOM
I am trying the FDOM images. Is there a GUI to configure GPRS? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Thursday 18 September 2008, Armin ranjbar wrote: On Wed, 17 Sep 2008 21:29:53 +0100 Al Johnson [EMAIL PROTECTED] wrote: I can understand your point now , this is my problem : VERY bad sound quality using Headset under Qtopia and openmoko mediaplayer , lots of Strange noises , echoes , and totally unlistenable quality . you know what is strange about it ? using Mplayer sound quality is Nearly perfect ( except for lack of bass , which is not very important ) , any idea ?! is this the issue with pulse audio and or soundserver ? Thanks. This sort of question is _much_ more likely to get a useful answer. I've not looked into this directly, but IIRC there were reports of pulseaudio doing sample rate conversion on almost everything that was played, munching CPU in the process and not necessarily leaving enough for smooth decode of the media file. The media player in 2007.2 was apparently affected by this, but if patched to use alsa directly it was fine. I can't verify this as I had gstreamer errors with the mp3 I tried it with. I think pulseaudio has been dropped from 2008.8 and FSO because of this. I don't know what the situation is with qtopia, but if you run top while playing a file you should see if anything's hogging CPU. I suggest you search the list archives for the original reports on this issue as they probably contain details I've forgotten or got wrong ;-) mplayer by default plays directly through alsa so isn't affected by the sound server issues. That you say sound is nearly perfect in this case shows the hardware limitation isn't really the issue. I haven't looked closely at the whole media playback issue so I don't know what the best solution is. If you're lucky someone who does might read this, but you may be better off reposting with a more appropriate subject line. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
help please with autologin on debian/xfce
i installed debian after getting my freerunner, but want it to autologin under xfce as a least-privileged user on startup i installed xfce and followed all the instructions under http://wiki.openmoko.org/wiki/Debian#Running_X_as_normal_user but it still logs in as root are those instructions completely correct? there's a couple of things there that don't look 100% correct/are written badly thanks ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] GPRS not functioning in M3
Am Thursday 18 September 2008 03:05:01 schrieb Dylan Semler: Has anyone else had their GPRS stop working since flashing FSO M3. It was working for me in M2. I've filed a bug about it[1] but no action so far. [1] http://trac.freesmartphone.org/ticket/140 I see this line here: ogsmd.pdp INFO configuring ppp for user 'x' w/ password 'x' I doubt that's correct for T-Mobile. Please try again with for user and password. MS2 did not care for user and password settings, MS3 does care :) -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Thursday 18 September 2008, Armin ranjbar wrote: On Thu, 18 Sep 2008 10:50:03 +0100 Al Johnson [EMAIL PROTECTED] wrote: Thanks. This sort of question is _much_ more likely to get a useful answer. I've not looked into this directly, but IIRC there were reports of pulseaudio doing sample rate conversion on almost everything that was played, munching CPU in the process and not necessarily leaving enough for smooth decode of the media file. The media player in 2007.2 was apparently affected by this, but if patched to use alsa directly it was fine. I can't verify this as I had gstreamer errors with the mp3 I tried it with. I think pulseaudio has been dropped from 2008.8 and FSO because of this. I don't know what the situation is with qtopia, but if you run top while playing a file you should see if anything's hogging CPU. I suggest you search the list archives for the original reports on this issue as they probably contain details I've forgotten or got wrong ;-) mplayer by default plays directly through alsa so isn't affected by the sound server issues. That you say sound is nearly perfect in this case shows the hardware limitation isn't really the issue. I haven't looked closely at the whole media playback issue so I don't know what the best solution is. If you're lucky someone who does might read this, but you may be better off reposting with a more appropriate subject line. Already filed a bug on this : http://docs.openmoko.org/trac/ticket/1956 You probably won't get much response to that bug report, first because it lacks sufficient detail, and second because it's against 2007.2 which is now more or less unsupported by Openmoko. For improved bug reporting see the links below. I thought the policy was supposed to be linked from the front page of the bug tracker, but it seems not to be. Details like exact version numbers and the repositories the packages came from are important for duplicating your bug and working out why it doesn't happen for someone else. http://wiki.openmoko.org/wiki/Bug_Filing_Policy http://www.mail-archive.com/devel%40lists.openmoko.org/msg01462.html 2007.2 is being converted to use the FSO interfaces to make the 'Stable Hybrid Release' (SHR). So far there is no release image for this project, but they may have more ideas on this. the Mplayer on om2008 is directly connected to OSS not alsa, when i -ao alsa it becomes 'very sensible' to loads , audio stop and resumes even after each characters into terminals , strange ... Have you had a look at CPU load? Is this repeatable? This is different to the bug report. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] GPRS not functioning in M3
On Thu, Sep 18, 2008 at 5:40 AM, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote: Am Thursday 18 September 2008 03:05:01 schrieb Dylan Semler: Has anyone else had their GPRS stop working since flashing FSO M3. It was working for me in M2. I've filed a bug about it[1] but no action so far. [1] http://trac.freesmartphone.org/ticket/140 I see this line here: ogsmd.pdp INFO configuring ppp for user 'x' w/ password 'x' I doubt that's correct for T-Mobile. Please try again with for user and password. MS2 did not care for user and password settings, MS3 does care :) I updated the mdbus command to: mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN but I appear to have the same result. -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[fso m3] vibrate over and over
I installed FSO milstone III on my FR, and left it on my desk at home. When I came home, I noticed it was vibrating, over and over. I had at least one missed call, I can't find a call log, so it may have been more. The phone kept vibrating until I had unlocked zhone (1224) and clicked reject, several times. Would have been virating most of the day. Is this a known bug? I tried to access the trak to check but http://www.freesmartphone.org appears to be down for me. Regards ~ matt ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [fso m3] vibrate over and over
When I first read that subject line I thought it was porn spam :p On Thursday 18 September 2008 09:22:19 Matt wrote: I installed FSO milstone III on my FR, and left it on my desk at home. When I came home, I noticed it was vibrating, over and over. I had at least one missed call, I can't find a call log, so it may have been more. The phone kept vibrating until I had unlocked zhone (1224) and clicked reject, several times. Would have been virating most of the day. Is this a known bug? I tried to access the trak to check but http://www.freesmartphone.org appears to be down for me. Regards ~ matt ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [fso m3] vibrate over and over
Matt wrote: I installed FSO milstone III on my FR, and left it on my desk at home. When I came home, I noticed it was vibrating, over and over. I had at least one missed call, I can't find a call log, so it may have been more. The phone kept vibrating until I had unlocked zhone (1224) and clicked reject, several times. Would have been virating most of the day. Is this a known bug? I had the same thing happen yesterday with zhone in Debian. I made a test call, didn't answer it, and the only way to make the phone stop vibrating was to reboot it--multiple clicks of the reject button had no effect. Jim ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
Tom Yates wrote: i experimented yesterday with turning on the hardware echo cancellation, and that worked for one call (allowed me to increase Speaker Playback Volume to 117) but then things went back to being very echoey. so unless i'm willing to have a minicom session at the beginning of every call, that's not usable right now; i'll have to wait until the AT%N0187 is integrated into qtopia's call-handling logic. So do you think that calling that AT command before of doing/answering a call would improve the sound quality? If it is, I guess this could be done quite easily in the code... So if I find some free time, I'll try it! -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
Armin ranjbar wrote: the Mplayer on om2008 is directly connected to OSS not alsa, when i -ao alsa it becomes 'very sensible' to loads , audio stop and resumes even after each characters into terminals , strange ... That's true... Using the oss output is really better here too. -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [fso m3] vibrate over and over
Jim Ancona wrote: Matt wrote: I installed FSO milstone III on my FR, and left it on my desk at home. When I came home, I noticed it was vibrating, over and over. I had at least one missed call, I can't find a call log, so it may have been more. The phone kept vibrating until I had unlocked zhone (1224) and clicked reject, several times. Would have been virating most of the day. Is this a known bug? I had the same thing happen yesterday with zhone in Debian. I made a test call, didn't answer it, and the only way to make the phone stop vibrating was to reboot it--multiple clicks of the reject button had no effect. Echoing a 0 in the files in /sys/class/leds/neo1973\:vibrator/ should fix this issue without rebooting (edit both delay_on, delay_off and brightness)... -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: fso-testing feed out of sync
-stacy wrote: edje is out of sync with e/illume and friends: libedje0_0.9.9.043+cvs20080802-r0_armv4t.ipk edje-utils_0.9.9.043+cvs20080802-r0_armv4t.ipk edje-viewer_0.0.0+svnr35984-r1_armv4t.ipk illume_0.0+svnr35984-r13_armv4t.ipk e-wm_0.16.999.043+svnr35984-r11_armv4t.ipk This causes e to fail to start and thus xserver-nodm doesn't complete. I was able to build my own edje packages, but no matter what I did I could not convince opkg to install them instead of the ones in the repository (I think I could learn to hate opkg); I finally just unpacked them by hand and copied the files into place. My FSO-testing is now working again. -stacy fso-testing is still broken. Out of desparation I have flashed the latest fso-testing image from downloads.freesmartphone.org. x.log still shows enlightenment: symbol lookup error: enlightenment: undefined symbol: edje_scale_set Any chance you could make the relevant ipks available please? I can't get the build system to work on my ubuntu box. Thanks, Richard -- View this message in context: http://n2.nabble.com/fso-testing-feed-out-of-sync-tp1095478p1098567.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: fso-testing feed out of sync
Michael 'Mickey' Lauer wrote: Am Thursday 18 September 2008 17:47:12 schrieb Richard Cooke: Any chance you could make the relevant ipks available please? I can't get the build system to work on my ubuntu box. How can we help to fix that? Did you file a bug report? -- :M: I have not filed a bug report up until now as I was not sure that the breakage was not due to my installation of non-standard e packages. Now I have the same problem having flashed the whole image I will do so. -- View this message in context: http://n2.nabble.com/fso-testing-feed-out-of-sync-tp1095478p1098776.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Thursday 18 September 2008, Marco Trevisan (Treviño) wrote: Tom Yates wrote: i experimented yesterday with turning on the hardware echo cancellation, and that worked for one call (allowed me to increase Speaker Playback Volume to 117) but then things went back to being very echoey. so unless i'm willing to have a minicom session at the beginning of every call, that's not usable right now; i'll have to wait until the AT%N0187 is integrated into qtopia's call-handling logic. So do you think that calling that AT command before of doing/answering a call would improve the sound quality? If it is, I guess this could be done quite easily in the code... So if I find some free time, I'll try it! It was persistent over 2 calls when I tried it in FSO, but it certainly shouldn't do any harm. I used mickeyterm to enable and disable it mid call to check that call to call variability wasn't playing a part. It may also be worth trying some of the other settings. From the hardware list post: 0083 Short AEC is active 0283 Long AEC is active 028B Long AEC -6 dB is active 0293 Long AEC -12 dB is active 029B Long AEC -18 dB is active 0105 Noise reduction is active 0125 Noise reduction -6 dB is active 0145 Noise reduction -12 dB is active 0165 Noise reduction -18 dB is active 0187 Both AEC and Noise reduction are active 0001 AEC and Noise reduction are unactivated These are bitmasked. From LSB upward the usage appears to be: LSB - always true AEC (short or long) NR -6dB on AEC -12dB on AEC -6dB on NR -12dB on NR AEC (short or long) NR Long AEC So far AFAIK only 0001 (nothing) and 0187 (short AEC and NR) have been tried. What does Long AEC do? Or -XdB for AEC and NR? Do other combinations than those listed work? Does 0387 give us Long AEC and NR? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: kernel panic on the second boot from the sd
I've been having the identical problem with an 8Gb sandisk SDHC. Is the original poster seeing this with the 512MB card that comes with the phone, or a different one? (I've not seen this behavior with the original card.) I don't have a fix yet but I think I can explain what's going on here. The problem is that sometimes when Linux tries to access the sd card, the card isn't ready yet and the first read doesn't get any data. After the first successful read in a session everything's gravy and you can read/write all you want, but in some circumstances software gives up at the first error so you never get a chance to try again. For instance if that first access is attempting to get the partition table and fails, then the kernel is going to think no partitions exist. In the case with the kernel panic on boot, the unknown-block (179,2) is exactly the same numbers I get and (I assume) it's trying to either access block 179 of partition 2, or a partition starting at block 179 (the first block of partition 2?) and get sector 2 of it. In any case what is going on here is that uboot can read the card correctly and it loaded the kernel from the small 8 MB space in partition 1, but when the kernel turns around to load the root file system from partition 2, the reads don't work and the kernel thinks there isn't anything there. The fact that the kernel got loaded at all doesn't prove the kernel can access the card, because uboot did that work. The kernel doesn't try to access the card until it looks for the root file system, at which point it panics when the read fails. You phrased the subject very specifically that it happens on second boot from sd. You could mean you can boot once and it is ok, but not a second time. However, the other way to read that phrase, and the way I'm interpreting your meaning because it describes the problem I'm having and I think we're having the same problem, is that you always have to try twice to boot, once getting nowhere and the second time getting to kernel panic. I don't know if you managed to catch what is on the screen the first time you try to boot because it flashes very quickly before disappearing, but I rebooted over and over to read it: what happens (at least on my phone) is the first time you try to boot *uboot itself* fails to read the sd and can't find the boot partition. It drops me back to the NAND uboot menu automatcially. On the *second* try after that, it loads the kernel correctly. This makes me think that the first attempt from uboot somehow warmed up the card so that it was read the second time uboot accessed it. This is not really a boot problem but a problem the partition table. When I first tried my card, I was able to partition it and put Debian on it. The next time I booted my phone (from flash) I couldn't access the card at all. Sometimes I had mmcblk0 only, other times I had mmcblk0p1 and p2. Sometimes I could mount them and sometimes not. But I found in this thread on kernel trap someone with a similar problem had a voodoo workaround: http://kerneltrap.org/mailarchive/openmoko-community/2008/7/23/2653864/thread#mid-2653864 Most of what he was doing for the voodoo was irrelevant, but I noticed that he did fdisk -l /dev/mmcblk0 several times (with different, illogical results each time). He was doing that to see when the card showed up; I suspected that rather than just telling you the card was showing up, it actually was the part of the voodoo that caused the card to work! Basically I think what he was doing was triggering a read from block 0 of the card over and over, until finally it gets a successful read. As I said, once you get 1 successful read, you can read/write all you want after that. Let me show you a log of what it looked like on my phone when I did this. First, I list /dev; notice how only mmcblk0 shows up, not p1 or p2: login as: root [EMAIL PROTECTED]'s password: [EMAIL PROTECTED]:~# ls /dev mmcblk0 ram14 usbmon0 mtd0ram15 usbmon1 I removed lines from the ls listing for brevity; note just though that mtd0 follows mmcblk0, where is p1 and p2? Now I run fdisk over and over, watch as the output changes: First run, nothing: [EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 Second run, finds it but finds no partitions: [EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes 4 heads, 16 sectors/track, 242560 cylinders Units = cylinders of 64 * 512 = 32768 bytes Disk /dev/mmcblk0 doesn't contain a valid partition table Third run, jackpot! [EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes 4 heads, 16 sectors/track, 242560 cylinders Units = cylinders of 64 * 512 = 32768 bytes Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 2457832 83 Linux /dev/mmcblk0p2 246 242560 7754080 83 Linux But /dev/mmcblk0p1 and p2
Re: kernel panic on the second boot from the sd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | The problem is that sometimes when Linux tries to access the sd card, | the card isn't ready yet and the first read doesn't get any data. After | the first successful read in a session everything's gravy and you can | read/write all you want, but in some circumstances software gives up at | the first error so you never get a chance to try again. For instance if | that first access is attempting to get the partition table and fails, | then the kernel is going to think no partitions exist. In the case with | the kernel panic on boot, the unknown-block (179,2) is exactly the | same numbers I get and (I assume) it's trying to either access block 179 | of partition 2, or a partition starting at block 179 (the first block of | partition 2?) and get sector 2 of it. In any case what is going on here No, these are the device numbers, where 179 is the mmc block devices. It's basically saying that the second partition of that device doesn't exist. These would always be the numbers you see if you ask to boot from mmcblk0p2 regardless of what the problem is. I think you're right about the card not being ready somehow and timing out though. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjSsPQACgkQOjLpvpq7dMrA8wCghGAD0+c7RWR9uPGtn+7JEkWu 1EAAn0pO2FV9B03xbxBAPGm3IR1+ESpT =cxox -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [fso m3] vibrate over and over
I had at least one missed call, I can't find a call log, so it may have
been more.
numbers are in zhone.log.
i hacked an ugly script extracting those numbers -- but if you reboot,
zhone.log is created fom scratch (still want to do it in python, but the
documentation is ... sparse and hard to find).
the script puts out date, time and number
#!/bin/bash
LINES=`grep CALL STATUS /tmp/zhone.log | grep incoming`
declare -a LINE
LINE=(`echo $LINES`)
#echo [EMAIL PROTECTED]
echo CALLS
for (( i=0;i[EMAIL PROTECTED];i++ )); do
if [ $(($i%21)) = 0 ]; then
echo ${LINE[$i]} ${LINE[$((i+1))]} : `echo ${LINE[$(($i+12))]}
| cut -f2 -d' -`
fi
done
echo DONE
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
2007.2: openmoko-messages segfault
hi! I've been using 2007.2 pretty much the whole time since I got the phone (tried, qtopia debian but 2007.2 was most suitable for me). Today I got a SMS and tried to openmoko-messages to read the message and got this: [EMAIL PROTECTED]:~# openmoko-messages (openmoko-messages:1698): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height -11 Got path /org/gnome/evolution/dataserver/calendar/filehome_root__evolution_memos_local_system for new calendar (openmoko-messages:1698): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height -11 (openmoko-messages:1698): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height -11 (openmoko-messages:1698): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height -11 (openmoko-messages:1698): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height -11 (openmoko-messages:1698): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height -11 Segmentation fault [EMAIL PROTECTED]:~# Anyone sharing the same experience? Any tips how to get over this? r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [EMAIL PROTECTED] gone?
sparky mat wrote: I am not able to find the FSO binaries/repository at shr.bearstech.com. Instead, I see that SHR binaries are present. I tried them out and there are (many) issues. There is a shr-devel mailing list on which you can discuss those issues if you have an interest in getting them resolved. Just wondering why FSO builds were removed from here. This was my preferred build/repository. FSO official feeds are now at downloads.freesmartphone.org - Mickey was supposed to send an email announcement, but that hasn't happened yet. He did blog about it, but that's not really an announcement: http://www.vanille-media.de/site/index.php/2008/09/18/staugstin-braunschweig-berlin-taipei/ So shr.bearstech.com is now used for the purpose which it's name proclaims - its' the feeds for the SHR distro. -- Rod ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: What packages have cu and socat?
Hi, i use OE to build package and i upload socat package here. You may try it on. http://cs1.cs.nyu.edu/~wcy203/socat_1.3.2.1-r1_armv4t.opk --erin W.Kenworthy wrote: Unfortunately, I need the OM2008.8 pkg. I installed uucp and it doesnt contain cu. minicom doesnt work (or I have not hit on the right settings - doesnt seem to be documented anywhere!), cant find cu/socat ... [...] On Wed, 2008-09-17 at 11:01 +1000, Neil Caldwell wrote: 2008/9/17 W.Kenworthy [EMAIL PROTECTED]: What packages have cu and socat? BillK ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: What packages have cu and socat?
Erin Yueh wrote: Hi, i use OE to build package and i upload socat package here. You may try it on. http://cs1.cs.nyu.edu/~wcy203/socat_1.3.2.1-r1_armv4t.opk Since you work at Openmoko, why didn't you just add socat to the task-openmoko-feed bitbake recipe, and then re-run the openmoko autobuilder to update the feed? Why would someone with an @openmoko.com address be putting pre-built packages anywhere other than in the official openmoko feeds? -- Rod ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: What packages have cu and socat?
Erin Yueh wrote: Rod Whitby wrote: Erin Yueh wrote: Hi, i use OE to build package and i upload socat package here. You may try it on. http://cs1.cs.nyu.edu/~wcy203/socat_1.3.2.1-r1_armv4t.opk Since you work at Openmoko, why didn't you just add socat to the task-openmoko-feed bitbake recipe, and then re-run the openmoko autobuilder to update the feed? Why would someone with an @openmoko.com address be putting pre-built packages anywhere other than in the official openmoko feeds? -- Rod mmh. yeah, we do have this recipe in OE, but i don't have this permission to add it to repository. I would cc this email to our distro team. Julian, Does Openmoko build the 'task-openmoko-feed' recipe and publish that to the official feeds? Who should community members contact if they have a recipe which already builds fine from the org.openmoko.dev git repository, and they just want that package added to task-openmoko-feed so that it automatically appears in the official feeds? -- Rod ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
