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. [Bug 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
2. [Bug 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
3. [Bug 282] New: microSD Problem
([EMAIL PROTECTED])
4. [Bug 282] New: microSD Problem
([EMAIL PROTECTED])
5. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
6. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
7. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
8. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
9. [Bug 283] New: portmap-5-26-r0-do_unpack
([EMAIL PROTECTED])
10. [Bug 283] New: portmap-5-26-r0-do_unpack
([EMAIL PROTECTED])
11. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
12. [Bug 283] portmap-5-26-r0-do_unpack
([EMAIL PROTECTED])
13. [Bug 283] portmap-5-26-r0-do_unpack
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256
------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 12:38 -------
I tried to run cu several times after issuing stty -F /dev/ttySAC0 crtscts, and
now I get garbled output from the modem. After several lines it still hangs.
Examples:
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
d Interpreter re
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
OK
OK
OK
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
OK
AT[6~
EAT-Command Interpreter ready
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
d Interpreter ready
I also tried picocom, which didn't react after "Terminal ready", until I pressed
a key:
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ picocom -b 115200 -f h -p o -d 8 -i -r -l /dev/ttySAC0
picocom v1.4
port is : /dev/ttySAC0
flowcontrol : RTS/CTS
baudrate is : 115200
parity is : odd
databits are : 8
escape is : C-a
noinit is : yes
noreset is : yes
nolock is : yes
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv
Terminal ready
AT-Command
Interateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterater
ERROR
OK
OK
OK
... and so forth until C-a C-x. Any suggestions?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256
------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 12:38 -------
I tried to run cu several times after issuing stty -F /dev/ttySAC0 crtscts, and
now I get garbled output from the modem. After several lines it still hangs.
Examples:
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
d Interpreter re
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
OK
OK
OK
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
OK
AT[6~
EAT-Command Interpreter ready
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
d Interpreter ready
I also tried picocom, which didn't react after "Terminal ready", until I pressed
a key:
[EMAIL PROTECTED]:~$ echo 1 > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ picocom -b 115200 -f h -p o -d 8 -i -r -l /dev/ttySAC0
picocom v1.4
port is : /dev/ttySAC0
flowcontrol : RTS/CTS
baudrate is : 115200
parity is : odd
databits are : 8
escape is : C-a
noinit is : yes
noreset is : yes
nolock is : yes
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv
Terminal ready
AT-Command
Interateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterateraterater
ERROR
OK
OK
OK
... and so forth until C-a C-x. Any suggestions?
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=282
Summary: microSD Problem
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
- SD card : RiDATA 512 MBãApacer 512 MB
- kernel version number : Linux fic-gta01 2.6.20.1-moko8 #1 PREEMPT Fri Mar 2
21:16:25 CET 2007 armv4tl unknown
- hardware revision : GTA01B_V3
When I used the microSD of other vendor, it displayed:
mmcblk0: error 2 transferring data
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs error (device mmcblk0): ext2_readdir: bad page in #2
[EMAIL PROTECTED]:~$s3c2410-sdi s3c2410-sdi: mci_setup_data() transfer stillin
progress.
mmcblk0: error 3 transferring data
end_request: I/O error, dev mmcblk0, sector 12
Buffer I/O error on device mmcblk0, logical block 6
lost page write due to I/O error on mmcblk0
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=282
Summary: microSD Problem
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
- SD card : RiDATA 512 MBãApacer 512 MB
- kernel version number : Linux fic-gta01 2.6.20.1-moko8 #1 PREEMPT Fri Mar 2
21:16:25 CET 2007 armv4tl unknown
- hardware revision : GTA01B_V3
When I used the microSD of other vendor, it displayed:
mmcblk0: error 2 transferring data
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs error (device mmcblk0): ext2_readdir: bad page in #2
[EMAIL PROTECTED]:~$s3c2410-sdi s3c2410-sdi: mci_setup_data() transfer stillin
progress.
mmcblk0: error 3 transferring data
end_request: I/O error, dev mmcblk0, sector 12
Buffer I/O error on device mmcblk0, logical block 6
lost page write due to I/O error on mmcblk0
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 16:42 -------
To fix the BSWP vs. HWSWP setting problem I'm in contact with Ben Dooks. He's
thinking about the best integration of it.
I will open a new bug about the 8bit kdrive problem.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 16:42 -------
To fix the BSWP vs. HWSWP setting problem I'm in contact with Ben Dooks. He's
thinking about the best integration of it.
I will open a new bug about the 8bit kdrive problem.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 16:52 -------
Seems to be a better idea let the info in this bug.
Starting kdrive with 8bit gives the following error:
can't get colormap: Invalid argument
The errors occurs due to an failed ioctl: (hw/kdrive/fbdev/fbdev.c:770)
k = ioctl (priv->fd, FBIOGETCMAP, &cmap);
if (k < 0)
{
perror ("can't get colormap");
return;
FBIOGETCMAP is the ioctl to get the color map from the framebuffer driver.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 16:52 -------
Seems to be a better idea let the info in this bug.
Starting kdrive with 8bit gives the following error:
can't get colormap: Invalid argument
The errors occurs due to an failed ioctl: (hw/kdrive/fbdev/fbdev.c:770)
k = ioctl (priv->fd, FBIOGETCMAP, &cmap);
if (k < 0)
{
perror ("can't get colormap");
return;
FBIOGETCMAP is the ioctl to get the color map from the framebuffer driver.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=283
Summary: portmap-5-26-r0-do_unpack
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: autobuilds
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The package failed to build at 20070316230006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=283
Summary: portmap-5-26-r0-do_unpack
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: autobuilds
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The package failed to build at 20070316230006
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=192
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=204
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=232
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=248
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=283
------- Additional Comments From [EMAIL PROTECTED] 2007-03-17 10:01 -------
I just deleted portmap* from my sources directory and ran bitbake -crebuild
portmap. It was downloaded, unpacked and built just fine. Maybe you have a
broken download of the source tarball?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=283
------- Additional Comments From [EMAIL PROTECTED] 2007-03-17 10:01 -------
I just deleted portmap* from my sources directory and ran bitbake -crebuild
portmap. It was downloaded, unpacked and built just fine. Maybe you have a
broken download of the source tarball?
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
