Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Openmoko Bug #2056: /etc/resolv.conf is empty on first boot
(Openmoko Public Trac)
2. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
3. Re: Openmoko Bug #2055: cancel
projects.openmoko.org/projects/aodv-mad personal project
(Openmoko Public Trac)
4. Re: Openmoko Bug #2056: /etc/resolv.conf is empty on first
boot (Openmoko Public Trac)
5. Re: Openmoko Bug #2056: /etc/resolv.conf is empty on first
boot (Openmoko Public Trac)
6. Re: Openmoko Bug #2056: /etc/resolv.conf is empty on first
boot (Openmoko Public Trac)
7. Re: Openmoko Bug #1595: GTA02 - uboot 1.3.2rc2 terminal
s3ser0 doesn't work apparently (Openmoko Public Trac)
8. Re: Openmoko Bug #1595: GTA02 - uboot 1.3.2rc2 terminal
s3ser0 doesn't work apparently (Openmoko Public Trac)
--- Begin Message ---
#2056: /etc/resolv.conf is empty on first boot
-----------------------------+----------------------------------------------
Reporter: rwhitby | Owner: raster
Type: defect | Status: new
Priority: normal | Milestone:
Component: Network Manager | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
-----------------------------+----------------------------------------------
Scenario:
Flash a new ASU or FSO distribution, and connect to it via USB networking
(since it's a GTA01, so there is no wireless, and GPRS and Bluetooth don't
connect to anything out of the box).
Type "opkg update". If /etc/resolv.conf had sensible contents it would
work. However, /etc/resolv.conf is empty, so it doesn't.
This has been mentioned countless times on many OM mailing lists, but it
seems that no-one has ever officially reported it as a bug.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2056>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by nelg):
tested with: uImage-gta02-g291a9d50_mwester-stable.bin, 2.6.24mw-g291a9d50
with qtextended-4.4.1-gta02-rootfs-release-10022309.jffs2
Still get wsod on resume, but this is still a 2.6.24 kernel, so no
surprise.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:29>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2055: cancel projects.openmoko.org/projects/aodv-mad personal project
-------------------------------+--------------------------------------------
Reporter: javiroman | Owner: openmoko-devel
Type: task | Status: closed
Priority: normal | Milestone:
Component: host utilities | Version:
Severity: normal | Resolution: invalid
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------------+--------------------------------------------
Changes (by zecke):
* status: new => closed
* resolution: => invalid
Comment:
Please use https://admin-trac.openmoko.org/trac. Good luck. I will close
this bug as invalid here, please file it at the above mentioned
bugtracker!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2055#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2056: /etc/resolv.conf is empty on first boot
--------------------------------+-------------------------------------------
Reporter: rwhitby | Owner: raster
Type: defect | Status: new
Priority: normal | Milestone:
Component: Network Manager | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------------+-------------------------------------------
Comment(by newkirk):
A simple fix, provided resolvconf is installed and managing
/etc/resolv.conf, (This appears to be the case with 2007/2008/ASU/FDOM,
but not Raster's image, uncertain about others) is to add this line to
/etc/network/interfaces in the 'usb0' stanza:
up echo 'nameserver a.b.c.d' | resolvconf -a usb0
Clearly the actual destination nameserver's IP is a separate point for
potential debate, but the previous standard was the IP of the desktop to
which usb0 leads, 192.168.0.200 by current default. Another reasonable
choice would be opendns.org or another free publicly-accessible caching
DNS service.
Also best to put 'usb*' near the end of /etc/resolvconf/interface-order
just above '*' complete wildcard entry, though it will be caught by that
wildcard if not explicitly listed.
Also clearly, if one network interface's "standard" config utilizes
resolvconf to manage nameservers, ALL need to do so or problems ensue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2056#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2056: /etc/resolv.conf is empty on first boot
------------------------+---------------------------------------------------
Reporter: rwhitby | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* owner: raster => julian_chu
* component: Network Manager => Distro
Comment:
The other side of the story is
[http://git.openmoko.org/?p=openmoko.git;a=commitdiff;h=4b593b0879640de084fa8f8936417fffb8ac9d46
this]. usb0 adds a default route and when you add a DNS entry to any kind
of name resolving will take a while until it times out. This was a big hit
for assassin as it added a huge (several seconds) delay to have a opkg
update fail. My assumption was 192.168.0.200 as nameserver is wrong most
of the time anyway and added complication (koen did a similar fix in OE)
and that with wlan one would have dhcp most of the time anyway.
Any ideas how to make both sides happy? Have a default DNS server but
still fail fast in case usb0 is not routed to the world?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2056#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2056: /etc/resolv.conf is empty on first boot
------------------------+---------------------------------------------------
Reporter: rwhitby | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* owner: raster => julian_chu
* component: Network Manager => Distro
Comment:
The other side of the story is
[http://git.openmoko.org/?p=openmoko.git;a=commitdiff;h=4b593b0879640de084fa8f8936417fffb8ac9d46
this]. usb0 adds a default route and when you add a DNS entry to any kind
of name resolving will take a while until it times out. This was a big hit
for assassin as it added a huge (several seconds) delay to have a opkg
update fail. My assumption was 192.168.0.200 as nameserver is wrong most
of the time anyway and added complication (koen did a similar fix in OE)
and that with wlan one would have dhcp most of the time anyway.
Any ideas how to make both sides happy? Have a default DNS server but
still fail fast in case usb0 is not routed to the world?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2056#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1595: GTA02 - uboot 1.3.2rc2 terminal s3ser0 doesn't work apparently
---------------------------------+------------------------------------------
Reporter: frances.albanese | Owner: laforge
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: System Software | Version: GTA02v6
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------------+------------------------------------------
Changes (by laforge):
* owner: openmoko-kernel => laforge
* status: new => assigned
Comment:
the problem consists of two parts
1) the hardware flow control is not handled in software since neither
CONFIG_HWFLOW are set,
nor is the autobaud-enable-check for a GTA02 board working (explicitly
checking for GTA02v1 and
GTA02v2, but not any later versions
2) the serial init function is not called, since it is only called for the
console device.
the serial_reinit_all() call in common/cmd_terminal.c was commented out
I'm working on a solution
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1595#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1595: GTA02 - uboot 1.3.2rc2 terminal s3ser0 doesn't work apparently
---------------------------------+------------------------------------------
Reporter: frances.albanese | Owner: laforge
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: System Software | Version: GTA02v6
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------------+------------------------------------------
Comment(by laforge):
the attached fix fixes the problem. please apply this to the u-boot stable
(and other) branches.
I will work with u-boot mainline to get a similar fix accepted (since
cmd_terminal.c is in mainline).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1595#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
