Bug#726838: mplayer depends upon old libavutil under unstable
Package: mplayer
Severity: important
Dear Maintainer,
mplayer under unstable for loongson-2f depends upon libavutil51, which
is no longer present under unstable. It also depends upon some other
packages, which are not installable given the lack of libavutil51.
It looks like mplayer needs to be kept up to date against other media packages.
See below:
% aptitude install mplayer
The following NEW packages will be installed:
mplayer{b}
0 packages upgraded, 1 newly installed, 0 to remove and 10 not upgraded.
Need to get 2,654 kB of archives. After unpacking 5,129 kB will be used.
The following packages have unmet dependencies:
mplayer : Depends: libavcodec53 (= 5:0.8-2~) but it is not installable. or
libavcodec-extra-53 (= 5:0.8-2~) but it is not
installable.
Depends: libavformat53 (= 5:0.8-2~) but it is not installable.
Depends: libavutil51 (= 5:0.8-2~) which is a virtual package.
Depends: libsmbclient (= 3.0.24) but it is not going to
be installed.
Depends: libx264-123 but it is not installable.
Depends: libxvmc1 but it is not going to be installed.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (750, 'unstable'), (700, 'experimental')
Architecture: mipsel (mips64)
Kernel: Linux 3.10-3-loongson-2f
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mplayer depends on:
ii libaa1 1.4p5-41
ii libasound2 1.0.27.2-2
pn libavcodec53 | libavcodec-extra-53 none
pn libavformat53 none
pn libavutil51 none
ii libbluray1 1:0.4.0-1
ii libbz2-1.0 1.0.6-5
ii libc6 2.17-93
ii libcaca00.99.beta18-1
ii libcdparanoia0 3.10.2+debian-11
ii libdca0 0.0.5-6
ii libdirectfb-1.2-9 1.2.10.0-5
ii libdvdnav4 4.2.0+20130225-3
ii libdvdread4 4.2.0+20130219-2
ii libenca01.15-1
ii libesd0 0.2.41-11
ii libfaad22.7-8
ii libfontconfig1 2.10.2-2
ii libfreetype62.4.9-1.1
ii libfribidi0 0.19.5-2
ii libgcc1 1:4.8.1-10
ii libgif4 4.1.6-10
ii libgl1-mesa-glx [libgl1]9.1.7-1
ii libjack0 [libjack-0.116]1:0.121.3+20120418git75e3e20b-2.1
ii libjpeg88d-1
ii liblircclient0 0.9.0~pre1-1
ii liblzo2-2 2.06-1.2
ii libmp3lame0 3.99.5+repack1-3
ii libmpeg2-4 0.5.1-5
ii libncurses5 5.9+20130608-1
ii libogg0 1.3.1-1
ii libopenal1 1:1.14-4
ii libpng12-0 1.2.49-5
ii libpostproc52 6:0.git20120821-4
ii libpulse0 4.0-6+b1
ii libsdl1.2debian 1.2.15-7
pn libsmbclientnone
ii libspeex1 1.2~rc1-7
ii libstdc++6 4.8.1-10
ii libswscale2 6:9.10-1
ii libtheora0 1.1.1+dfsg.1-3.1
ii libtinfo5 5.9+20130608-1
ii libx11-62:1.6.2-1
pn libx264-123 none
ii libxext62:1.3.2-1
ii libxinerama12:1.1.3-1
ii libxv1 2:1.0.9-1
ii libxvidcore42:1.3.2-9
pn libxvmc1none
ii libxxf86dga12:1.1.4-1
ii libxxf86vm1 1:1.1.3-1
ii zlib1g 1:1.2.8.dfsg-1
mplayer recommends no packages.
Versions of packages mplayer suggests:
ii bzip2 1.0.6-5
ii fontconfig 2.10.2-2
ii fonts-freefont-ttf [ttf-freefont] 20120503-1
pn mplayer-docnone
ii netselect 0.3.ds1-25
ii ttf-freefont 20120503-1
--
Javier.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726839: xserver-xorg-video-sis depends on old xorg-video-abi-12 under unstable
Package: xserver-xorg-video-sis Severity: important Dear Maintainer, On loongson-2f mini-pc, which uses SIS video card, it's not possible to upgrade Xorg packages ata all, given xserver-xorg-video-sis depends on an old xorg-video-abi-12, which is no longer provided by upgradable Xorg packages. For this fuloong mini-pc it's important to keep SIS video driver up to date as long with the rest of Xorg packages. See next: The following packages have unmet dependencies: xserver-xorg-video-sis : Depends: xorg-video-abi-12 which is a virtual package. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jul 23 2011 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2125744 Sep 12 18:41 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:08.0 VGA compatible controller [0300]: Silicon Integrated Systems [SiS] 315PRO PCI/AGP VGA Display Adapter [1039:0325] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 24 -rw-r--r-- 1 root root 74 Oct 19 11:44 05-flags.conf -rw-r--r-- 1 root root 1278 Jun 19 2011 10-evdev.conf -rw-r--r-- 1 root root 377 Jun 19 2011 10-quirks.conf -rw-r--r-- 1 root root 79 Oct 19 11:46 20-card.conf -rw-r--r-- 1 root root 113 Oct 19 11:51 50-vmmouse.conf -rw-r--r-- 1 root root 666 Oct 19 11:51 60-files.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.10-3-loongson-2f (debian-ker...@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) ) #1 Debian 3.10.11-1 (2013-09-10) Xorg X server log files on system: -- -rw-r--r-- 1 root root 37934 Oct 19 11:56 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 30327.457] X.Org X Server 1.12.4 Release Date: 2012-08-27 [ 30327.457] X Protocol Version 11, Revision 0 [ 30327.457] Build Operating System: Linux 3.2.0-4-loongson-2e mips Debian [ 30327.457] Current Operating System: Linux mini-1 3.10-3-loongson-2f #1 Debian 3.10.11-1 (2013-09-10) mips64 [ 30327.457] Kernel command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 ro video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6a EC_VER=undefined machtype=lemote-fuloong-2f-box rd_start=0x8400 rd_size=0xb497e7 [ 30327.458] Build Date: 12 September 2013 10:55:55PM [ 30327.458] xorg-server 2:1.12.4-6.2+b2 (mipsel Build Daemon (eysler) buildd_mipsel-eys...@buildd.debian.org) [ 30327.458] Current version of pixman: 0.30.2 [ 30327.458]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 30327.458] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 30327.458] (==) Log file: /var/log/Xorg.0.log, Time: Sat Oct 19 11:55:56 2013 [ 30327.461] (==) Using config directory: /etc/X11/xorg.conf.d [ 30327.461] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 30327.467] (==) No Layout section. Using the first Screen section. [ 30327.467] (==) No screen section available. Using defaults. [ 30327.467] (**) |--Screen Default Screen Section (0) [ 30327.467] (**) | |--Monitor default monitor [ 30327.469] (==) No device specified for screen Default Screen Section. Using the first device section listed. [ 30327.469] (**) | |--Device Card0 [ 30327.469] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 30327.469] (==) Automatically adding devices [ 30327.469] (==) Automatically enabling devices [ 30327.469] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 30327.469]Entry deleted from font path. [ 30327.470] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [ 30327.470]Entry deleted from font path. [ 30327.470] (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi:unscaled, /usr/share/fonts/X11/75dpi:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /usr/share/fonts/truetype/msttcorefonts, /usr/share/fonts/truetype/freefont, /usr/share/fonts/truetype/ttf-bitstream-vera, /usr/share/fonts/truetype/ttf-dejavu, /usr/share/fonts/truetype/ttf-liberation, /usr/share/fonts/type1/gsfonts, /usr/share/fonts/type1/mathml, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 30327.470] (==) ModulePath set to
Bug#724233: iceweasel crashes with illegal instruction when accessing javascript gmail web page.
I also got gdb log, and it shows the same failure: [Thread 0x655ff490 (LWP 23275) exited] [New Thread 0x655ff490 (LWP 23336)] [New Thread 0x5bcff490 (LWP 23337)] [New Thread 0x5b1ff490 (LWP 23358)] [New Thread 0x572ff490 (LWP 23381)] [New Thread 0x569ff490 (LWP 23398)] [New Thread 0x530ff490 (LWP 23444)] [Thread 0x5e5ff490 (LWP 23311) exited] [New Thread 0x526ff490 (LWP 23447)] Program received signal SIGILL, Illegal instruction. 0x77ded48c in __sqrt_finite () from /lib/mipsel-linux-gnu/loongson2f/libm.so.6 The back trace couldn't find the culprit: (gdb) bt #0 0x77ded48c in __sqrt_finite () from /lib/mipsel-linux-gnu/loongson2f/libm.so.6 #1 0x778b3868 in lookup (x=optimized out, f=optimized out, this=optimized out) at /build/iceweasel-AksY7a/iceweasel-24.0/js/src/jsmath.h:44 #2 js_math_sqrt (cx=0x6616c220, argc=optimized out, vp=0x718a71f8) at /build/iceweasel-AksY7a/iceweasel-24.0/js/src/jsmath.cpp:766 #3 0x77757d24 in CallJSNative (args=..., native=optimized out, cx=optimized out) at ../../../js/src/jscntxtinlines.h:321 ... #38 0x76935544 in nsWindow::OnMotionNotifyEvent (this=0x6ebdbb50, aEvent=0x718d28c0) at /build/iceweasel-AksY7a/iceweasel-24.0/widget/gtk2/nsWindow.cpp:2558 #39 0x76935610 in motion_notify_event_cb (widget=optimized out, event=0x718d28c0) at /build/iceweasel-AksY7a/iceweasel-24.0/widget/gtk2/nsWindow.cpp:5208 #40 0x7488646c in ?? () from /usr/lib/mipsel-linux-gnu/libgtk-x11-2.0.so.0 warning: GDB can't find the start of the function at 0x7488646a. GDB is unable to find the start of the function at 0x7488646a and thus can't determine the size of that function's stack frame. This means that GDB may be unable to access that stack frame, or the frames below it. This problem is most likely caused by an invalid program counter or stack pointer. However, if you think GDB should simply search farther back from 0x7488646a for code which looks like the beginning of a function, you can increase the range of the search using the `set heuristic-fence-post' command. Attached goes the full gdb output. -- Javier. GNU gdb (GDB) 7.6 (Debian 7.6-5) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as mipsel-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/iceweasel/iceweasel...Reading symbols from /usr/lib/debug/usr/lib/iceweasel/iceweasel...done. done. (gdb) run Starting program: /usr/lib/iceweasel/iceweasel [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/mipsel-linux-gnu/loongson2f/libthread_db.so.1. [New Thread 0x73caf490 (LWP 23226)] [Thread 0x73caf490 (LWP 23226) exited] (process:22477): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed [New Thread 0x73caf490 (LWP 23237)] [New Thread 0x720ff490 (LWP 23240)] [New Thread 0x716ff490 (LWP 23243)] [New Thread 0x70eff490 (LWP 23244)] [New Thread 0x706ff490 (LWP 23245)] [New Thread 0x6fbab490 (LWP 23246)] [New Thread 0x6eaff490 (LWP 23259)] [New Thread 0x6e2ff490 (LWP 23260)] [New Thread 0x6d9ff490 (LWP 23261)] [New Thread 0x6811f490 (LWP 23266)] [New Thread 0x676ff490 (LWP 23267)] [New Thread 0x66eff490 (LWP 23268)] [New Thread 0x660ff490 (LWP 23274)] [New Thread 0x655ff490 (LWP 23275)] [Thread 0x676ff490 (LWP 23267) exited] [New Thread 0x64dff490 (LWP 23278)] [New Thread 0x676ff490 (LWP 23281)] [New Thread 0x634ff490 (LWP 23291)] [New Thread 0x62cff490 (LWP 23292)] [New Thread 0x623ff490 (LWP 23293)] [New Thread 0x618f3490 (LWP 23299)] [New Thread 0x610f3490 (LWP 23300)] [New Thread 0x608f3490 (LWP 23301)] [New Thread 0x5faff490 (LWP 23306)] [New Thread 0x5efff490 (LWP 23309)] [New Thread 0x600db490 (LWP 23310)] [New Thread 0x5e5ff490 (LWP 23311)] [New Thread 0x5ddff490 (LWP 23312)] [New Thread 0x5d5ff490 (LWP 23322)] [New Thread 0x5cdff490 (LWP 23326)] [Thread 0x655ff490 (LWP 23275) exited] [New Thread 0x655ff490 (LWP 23336)] [New Thread 0x5bcff490 (LWP 23337)] [New Thread 0x5b1ff490 (LWP 23358)] [New Thread 0x572ff490 (LWP 23381)] [New Thread 0x569ff490 (LWP 23398)] [New Thread 0x530ff490 (LWP 23444)] [Thread 0x5e5ff490 (LWP 23311) exited] [New Thread 0x526ff490 (LWP 23447)] Program received signal SIGILL, Illegal instruction. 0x77ded48c in __sqrt_finite () from /lib/mipsel-linux-gnu/loongson2f/libm.so.6 (gdb) bt #0 0x77ded48c in __sqrt_finite () from /lib/mipsel-linux-gnu/loongson2f/libm.so.6 #1 0x778b3868 in lookup (x=optimized out, f=optimized out, this=optimized out) at /build/iceweasel-AksY7a/iceweasel-24.0/js/src/jsmath.h:44 #2 js_math_sqrt (cx=0x6616c220, argc=optimized out, vp=0x718a71f8) at /build/iceweasel-AksY7a/iceweasel-24.0/js/src/jsmath.cpp:766 #3 0x77757d24 in CallJSNative (args=..., native=optimized
Bug#721469: [rxvt-unicode] perl update to 5.18, requires change on tabbed.
Package: rxvt-unicode
Version: 9.18-2+b1
Well, it happens that for perl 5.18:
https://metacpan.org/module/RJBS/perl-5.18.0/pod/perldelta.pod#qw-...-can-no-longer-be-used-as-parentheses
So, on:
/usr/lib/urxvt/perl/tabbed
Where it says:
for my $hook qw(start destroy key_press property_notify) {
It must say instead:
for my $hook (qw(start destroy key_press property_notify)) {
And that avoids the failure preventing the tabs to be used:
urxvt: perl hook 0 evaluation error: /usr/lib/urxvt/perl/tabbed:
syntax error at /usr/lib/urxvt/perl/tabbed line 406, near $hook
qw(start destroy key_press property_notify)
syntax error at /usr/lib/urxvt/perl/tabbed line 426, near }
}
An easy fis, :-)
--
Javier.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711585: [linux-image-3.9-1-loongson-2f] linux 3.9.4-1 for loongson-2f doesn't halt/reboot/suspend-disk.
Still failing with latest 3.10-1 linux image... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708812: [Aptitude-devel] Bug#708812: [aptitude] aptitude segfaults upon being called.
On Tue, Jun 18, 2013 at 5:22 PM, Axel Beckert a...@debian.org wrote: ... Was that today's upgrade on Wheezy or on Sid? (Or asked the other way round: Does this bug affect Stable or Unstable?) On unstable (sid). -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708812: [Aptitude-devel] Bug#708812: [aptitude] aptitude segfaults upon being called.
On Tue, Jun 18, 2013 at 5:14 PM, Axel Beckert a...@debian.org wrote: ... Any chance to figure out which dependencies of aptitude were upgraded during that run? The backtrace wasn't as helpful as expected. (Yeah, I know it's late for that question, but maybe either aptitude's, apt's or dpkg's logs are still there and can answer that question.) I'm afraid not, sorry... There was one other person reporting the same issue, perhaps he might be able to provide logs on that particular run. -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711585: [linux-image-3.9-1-loongson-2f] linux 3.9.4-1 for loongson-2f doesn't halt/reboot/suspend-disk.
Package: linux-image-3.9-1-loongson-2f Version: 3.9.4-1 Severity: Important When rebooting, halting or suspending to disk on a mini-pc with loongson-2f, it just hangs, printing a weird trace. Fortunately dmessage kept such trace: Jun 7 23:34:30 mini-1 kernel: [2.18] EXT4-fs (sda6): write access will be enabled during recovery Jun 7 23:34:30 mini-1 kernel: [2.908000] EXT4-fs (sda6): orphan cleanup on readonly fs Jun 7 23:34:30 mini-1 kernel: [2.908000] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 888392 Jun 7 23:34:30 mini-1 kernel: [2.924000] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 889643 Jun 7 23:34:30 mini-1 kernel: [2.924000] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 904421 Jun 7 23:34:30 mini-1 kernel: [2.936000] EXT4-fs (sda6): 3 orphan inodes deleted Jun 7 23:34:30 mini-1 kernel: [2.94] EXT4-fs (sda6): recovery complete Jun 7 23:34:30 mini-1 kernel: [3.072000] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) Jun 7 23:34:30 mini-1 kernel: [3.076000] VFS: Mounted root (ext4 filesystem) readonly on device 8:6. Jun 7 23:34:30 mini-1 kernel: [3.076000] Freeing unused kernel memory: 320k freed Jun 7 23:34:30 mini-1 kernel: [6.764000] cpufreq: Loongson-2F CPU frequency driver. Jun 7 23:34:30 mini-1 kernel: [6.812000] CPU 0 Unable to handle kernel paging request at virtual address c00106c8, epc == 8051f1c4, ra == 8051d36c Jun 7 23:34:30 mini-1 kernel: [6.816000] Oops[#1]: Jun 7 23:34:30 mini-1 kernel: [6.816000] Cpu 0 Jun 7 23:34:30 mini-1 kernel: [6.816000] $ 0 : cfff c00106c8 Jun 7 23:34:30 mini-1 kernel: [6.816000] $ 4 : 9800be421000 807b Jun 7 23:34:30 mini-1 kernel: [6.816000] $ 8 : 98000136e798 Jun 7 23:34:30 mini-1 kernel: [6.816000] $12 : 8047d688 803192e8 Jun 7 23:34:30 mini-1 kernel: [6.816000] $16 : 9800be421000 8081cc40 8081cc30 806f90b8 Jun 7 23:34:30 mini-1 kernel: [6.816000] $20 : 9800be764000 9800be6afe70 771b8000 4000 Jun 7 23:34:30 mini-1 kernel: [6.816000] $24 : 770c7ce4 Jun 7 23:34:30 mini-1 kernel: [6.816000] $28 : 9800be6ac000 9800be6afd50 00afc978 8051d36c Jun 7 23:34:30 mini-1 kernel: [6.816000] Hi: e147d0b6 Jun 7 23:34:30 mini-1 kernel: [6.816000] Lo: 748f7125 Jun 7 23:34:30 mini-1 kernel: [6.816000] epc : 8051f1c4 dev_uevent+0xe0/0x1a0 Jun 7 23:34:30 mini-1 kernel: [6.816000] Not tainted Jun 7 23:34:30 mini-1 kernel: [6.816000] ra: 8051d36c show_uevent+0xdc/0x178 Jun 7 23:34:30 mini-1 kernel: [6.816000] Status: 100044e3 KX SX UX KERNEL EXL IE Jun 7 23:34:30 mini-1 kernel: [6.816000] Cause : 10008008 Jun 7 23:34:30 mini-1 kernel: [6.816000] BadVA : c00106c8 Jun 7 23:34:30 mini-1 kernel: [6.816000] PrId : 6303 (ICT Loongson-2) Jun 7 23:34:30 mini-1 kernel: [6.816000] Modules linked in: usb_common Jun 7 23:34:30 mini-1 kernel: [6.816000] Process udevd (pid: 246, threadinfo=9800be6ac000, task=9800be67a6b8, tls=771fc2c0) Jun 7 23:34:30 mini-1 kernel: [6.816000] Stack : 8081cc40 806f90b8 9800be421000 Jun 7 23:34:30 mini-1 kernel: [6.816000] 8081cc40 8051d36c 9800be342980 80867818 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be0f5550 8081cc40 806f90b8 9800be3429a0 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be6afe70 8051dac0 00afc978 802c6778 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be342980 80387a04 9800be6afe70 Jun 7 23:34:30 mini-1 kernel: [6.816000] 770785e0 4000 9800be75cec0 771b8000 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be6afe70 770785e0 Jun 7 23:34:30 mini-1 kernel: [6.816000] 7f8e97d8 803190c0 0003 9800be75cec0 Jun 7 23:34:30 mini-1 kernel: [6.816000] 771b8000 000a 80319338 Jun 7 23:34:30 mini-1 kernel: [6.816000] 4000 000a Jun 7 23:34:30 mini-1 kernel: [6.816000] ... Jun 7 23:34:30 mini-1 kernel: [6.816000] Call Trace: Jun 7 23:34:30 mini-1 kernel: [6.816000] [8051f1c4] dev_uevent+0xe0/0x1a0 Jun 7 23:34:30 mini-1 kernel: [6.816000] [8051d36c] show_uevent+0xdc/0x178 Jun 7 23:34:30 mini-1 kernel: [
Bug#710852: [linux-image-3.8-2-loongson-2f] usb ethernet adapter MosChip MCS7830 hangs after working fine for a while
Package: src:linux Version: 3.8.13-1 Severity: important Tags: upstream On loongson-2f mini-pc running under unstable, I upgraded the linux image from old linux-image-3.2.0-4-loongson-2f to newer linux-image-3.8-2-loongson-2f. I use this mini-pc as a gateway 24/7, so it is to be up all the time. However after the upgrade, the MosChip MCS7830 ethernet usb adaptor starts working great after booting, but after a while (haven't identified how much), it stops working, with no message about it. I can do ifdown, but I can't complete ifup successfully given the DHCP process doesn't get response from the DHCP server (provider), given the usb device is hanging. Attempting to modprobe -r usbnet, doesn't work, the module is reported busy, even fails to remove with -f. The only work around is to reboot. As I need the gateway up at all times, I'm going back to old 3.2.0-4 version. However the idea is to keep the machine running with more up to date kernels... -- Package-specific info: ** Version: Linux version 3.8-2-loongson-2f (debian-ker...@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-3) ) #1 Debian 3.8.13-1 ** Command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 ro video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Kernel log: [1.964000] ata1.00: 312581808 sectors, multi 16: LBA48 [1.976000] ata1.00: configured for UDMA/100 [1.976000] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM160HI HH10 PQ: 0 ANSI: 5 [1.98] ata2: port disabled--ignoring [1.98] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) [1.984000] sd 0:0:0:0: [sda] Write Protect is off [1.984000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.984000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.148000] sda: sda1 sda2 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 [2.152000] sd 0:0:0:0: [sda] Attached SCSI disk [2.152000] PM: Hibernation image partition 8:5 present [2.152000] PM: Looking for hibernation image. [2.152000] PM: Image not found (code -22) [2.152000] PM: Hibernation image not present or could not be loaded. [2.152000] registered taskstats version 1 [2.156000] /build/buildd-linux_3.8.13-1-mipsel-XrCEF3/linux-3.8.13/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [2.176000] EXT4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities [2.176000] EXT4-fs (sda6): couldn't mount as ext2 due to feature incompatibilities [2.208000] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [2.208000] VFS: Mounted root (ext4 filesystem) readonly on device 8:6. [2.212000] Freeing unused kernel memory: 288k freed [5.332000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [5.364000] rtc0: alarms up to one day, 114 bytes nvram [5.412000] cpufreq: Loongson-2F CPU frequency driver. [5.56] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [5.576000] r8169 :00:06.0 (unregistered net_device): not PCI Express [5.60] usbcore: registered new interface driver usbfs [5.608000] r8169 :00:06.0 eth0: RTL8169sc/8110sc at 0x900050072000, 00:23:9e:00:04:b6, XID 1800 IRQ 36 [5.612000] r8169 :00:06.0 eth0: jumbo features [frames: 7152 bytes, tx checksumming: ok] [5.624000] usbcore: registered new interface driver hub [5.652000] usbcore: registered new device driver usb [5.684000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [5.70] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [5.704000] ohci_hcd :00:0e.4: setting latency timer to 64 [5.704000] ohci_hcd :00:0e.4: OHCI Host Controller [5.712000] ehci-pci: EHCI PCI platform driver [5.724000] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 1 [5.74] ohci_hcd :00:0e.4: irq 11, io mem 0x5007 [5.836000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [5.84] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.844000] usb usb1: Product: OHCI Host Controller [5.848000] usb usb1: Manufacturer: Linux 3.8-2-loongson-2f ohci_hcd [5.852000] usb usb1: SerialNumber: :00:0e.4 [5.864000] hub 1-0:1.0: USB hub found [5.868000] hub 1-0:1.0: 4 ports detected [5.872000] ehci-pci :00:0e.5: setting latency timer to 64 [5.876000] ehci-pci :00:0e.5: EHCI Host Controller [5.912000] ehci-pci :00:0e.5: new USB bus registered, assigned bus number 2 [5.92] ehci-pci :00:0e.5: irq 11, io mem 0x50071000 [5.944000] ehci-pci :00:0e.5: USB 0.0 started, EHCI 1.00 [5.96] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [5.964000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.968000] usb usb2: Product: EHCI Host Controller [
Bug#710852: [linux-image-3.8-2-loongson-2f] usb ethernet adapter MosChip MCS7830 hangs after working fine for a while
Additional info... The beginnign of the kernel log, not reported before, shows: Jun 2 09:00:20 mini-0 kernel: [55560.272000] UDP: bad checksum. From 213.157.218.54:0 to 186.176.90.47:0 ulen 1430 Jun 2 09:55:57 mini-0 kernel: [58896.588000] UDP: bad checksum. From 218.95.142.2:0 to 186.176.90.47:0 ulen 1430 Jun 2 11:22:06 mini-0 kernel: [64065.68] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:44352 ulen 170 Jun 2 14:16:34 mini-0 kernel: [74533.544000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:49396 ulen 136 Jun 2 14:16:40 mini-0 kernel: [74539.976000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:47340 ulen 187 Jun 2 14:17:02 mini-0 kernel: [74561.496000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:52383 ulen 154 Jun 2 14:34:16 mini-0 kernel: [75596.068000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:33701 ulen 126 Jun 2 16:26:34 mini-0 kernel: [82334.04] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:54904 ulen 125 Jun 2 16:43:35 mini-0 kernel: [83355.312000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:52201 ulen 282 Jun 2 16:57:04 mini-0 kernel: [84163.824000] [ cut here ] Jun 2 16:57:04 mini-0 kernel: [84163.824000] WARNING: at /build/buildd-linux_3.8.13-1-mipsel-XrCEF3/linux-3.8.13/net/sched/sch_generic.c:254 dev_watchdog+0x180/0x2b0() Jun 2 16:57:04 mini-0 kernel: [84163.824000] NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out Jun 2 16:57:04 mini-0 kernel: [84163.828000] Modules linked in: cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave nfsd auth_rpcgss nfs_acl nfs lockd dns_resolver fscache sunrpc ipt_MASQUERADE ipt_REJECT xt_tcpudp xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables autofs4 loop fuse snd_cs5535audio snd_ac97_codec snd_pcm_oss snd_mixer_oss mcs7830 usbnet snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq r8169 rtc_cmos snd_seq_device mii ehci_pci snd_timer ohci_hcd ehci_hcd snd loongson2_cpufreq usbcore soundcore usb_common ac97_bus Jun 2 16:57:04 mini-0 kernel: [84163.84] Call Trace: Jun 2 16:57:04 mini-0 kernel: [84163.84] [8068e5fc] dump_stack+0x8/0x40 Jun 2 16:57:04 mini-0 kernel: [84163.84] [80229680] warn_slowpath_common+0x78/0xa4 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [80229754] warn_slowpath_fmt+0x38/0x50 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [805c8240] dev_watchdog+0x180/0x2b0 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [80238018] call_timer_fn+0x84/0x164 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [80239110] run_timer_softirq+0x20c/0x2a4 Jun 2 16:57:04 mini-0 kernel: [84163.848000] [80231c18] __do_softirq+0x124/0x288 Jun 2 16:57:04 mini-0 kernel: [84163.848000] [80231e48] do_softirq+0x44/0x68 Jun 2 16:57:04 mini-0 kernel: [84163.848000] [802320ac] irq_exit+0x4c/0xcc Jun 2 16:57:04 mini-0 kernel: [84163.852000] [8020419c] ret_from_irq+0x0/0x4 Jun 2 16:57:04 mini-0 kernel: [84163.852000] [80477288] arch_local_irq_save+0x0/0x28 Jun 2 16:57:04 mini-0 kernel: [84163.852000] [802963f4] rcu_idle_exit+0x1c/0xb4 Jun 2 16:57:04 mini-0 kernel: [84163.852000] [80206560] cpu_idle+0x68/0x80 Jun 2 16:57:04 mini-0 kernel: [84163.856000] [80868a6c] start_kernel+0x470/0x49c Jun 2 16:57:04 mini-0 kernel: [84163.856000] Jun 2 16:57:04 mini-0 kernel: [84163.856000] ---[ end trace 18e9d7175962fe44 ]--- Jun 2 17:28:23 mini-0 kernel: [0.00] Initializing cgroup subsys cpuset Jun 2 17:28:23 mini-0 kernel: [0.00] Initializing cgroup subsys cpu Jun 2 17:28:23 mini-0 kernel: [0.00] Linux version 3.8-2-loongson-2f (debian-ker...@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-3) ) #1 Debian 3.8.13-1 Perhaps the important part is the netdev watchdog. I performed several pings to external URLs to see if I had external connection, but none of the pings was responded back, all packets were reported lost. That's how I realized the network device was hanging, or no longer working... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708812: [aptitude] aptitude segfaults upon being called.
On 5/18/13, Daniel Hartwig mand...@gmail.com wrote: On 19/05/2013 1:09 AM, Javier Vasquez j.e.vasque...@gmail.com wrote: ... Please install aptitude-dbg and send a stack trace from gdb. ... OK, attached goes the gdb back trace... It's pretty short though. Notice I moved to experimental to see if that would change anything, but it's exactly the sme thing. This gdb back trace is then on the experimental version... Thanks, -- Javier. GNU gdb (GDB) 7.6-debian Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as mipsel-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/aptitude-curses...Reading symbols from /usr/lib/debug/.build-id/d6/b5136d6ff3c09467908c6d693c872beb69d729.debug...done. done. (gdb) run Starting program: /usr/bin/aptitude-curses [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/mipsel-linux-gnu/loongson2f/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x00418c20 in _PROCEDURE_LINKAGE_TABLE_ () Backtrace stopped: frame did not save the PC (gdb) quit A debugging session is active. Inferior 1 [process 23270] will be killed. Quit anyway? (y or n)
Bug#708812: [aptitude] aptitude segfaults upon being called.
Package: aptitude Version: 0.6.8.2-1 Architecture: mipsel After Today's (2013/05/18) aptitude safe-upgrade, aptitude segfaults upon calling it. I'm attaching the strace log when calling aptitude. Seems like apt-get still works, though aptitude ncurses UI is really missed, and I'm used to aptitude already, :-) I'm running on mipsel architecture for on a loongson-2f mini-pc. Thanks, -- Javier. aptitude.log Description: Binary data
Bug#708812: [aptitude] aptitude segfaults upon being called.
I've also tried the newer version under experimental: 0.6.9.1-1 And that doesn't help. -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708812: [Aptitude-devel] Bug#708812: [aptitude] aptitude segfaults upon being called.
What version of libapt-pkg4.12 and apt? 0.9.8.1 Pending still the other request... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
It does actually work, a bit slower than the anhen 17 version, but I'm glad it works on plain debian... I'll keep using this new then. Seems like the bug can finally be closed, :-) Thanks, Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696646: icedtea-7-plugin not loading applets (mipsel loongson-2f).
It looks like the newer version of icedtea7-plugin on unstable from Today's upgrade (1.3.1-2), now works in the sites it wasn't working before. BTW, it's now the default alternative, since I was going to change from icedtea6-plugin to icedtea7-plugin, but to my surprise icedtea7-plugin was already the automatic selection, which is is more than OK to me, since now it's working, :-) So this bug can be closed. If anyother upgrade breaks things, then I'll file a different bug... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696646: icedtea-7-plugin not loading applets (mipsel loongson-2f).
Package: icedtea-7-plugin Version: 1.3.1-1 Severity: important Dear Maintainer, Some time back icedtea-7-plugin was working correctly, however when moving to the latest1.3.1-1 version, also some time back, bank account applets no longer load. I had to revert to icedtea-6-plugin so I can access my bank accounts which depend upon java applets. Weird thing, everything was working before, :-( Any ways, I've seen bugs relates to update-alternatives, but so far everything points to java7, and even so, the icedtea-6-plugin still works while icedtea-7-plugin doesn't: % ls -l /etc/alternatives/ | 'grep' 'java-6' lrwxrwxrwx 1 root root 66 Dec 24 13:54 mozilla-javaplugin.so - /usr/lib/jvm/java-6-openjdk-mipsel/jre/lib/mipsel/IcedTeaPlugin.so % ls -l /etc/alternatives/ | 'grep' 'java-7' lrwxrwxrwx 1 root root 51 Dec 24 12:23 appletviewer - /usr/lib/jvm/java-7-openjdk-mipsel/bin/appletviewer* lrwxrwxrwx 1 root root 61 Dec 24 12:23 appletviewer.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/appletviewer.1.gz lrwxrwxrwx 1 root root 47 Dec 24 12:27 extcheck - /usr/lib/jvm/java-7-openjdk-mipsel/bin/extcheck* lrwxrwxrwx 1 root root 57 Dec 24 12:27 extcheck.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/extcheck.1.gz lrwxrwxrwx 1 root root 43 Dec 24 12:28 idlj - /usr/lib/jvm/java-7-openjdk-mipsel/bin/idlj* lrwxrwxrwx 1 root root 53 Dec 24 12:28 idlj.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/idlj.1.gz lrwxrwxrwx 1 root root 57 Dec 24 12:20 itweb-settings - /usr/lib/jvm/java-7-openjdk-mipsel/jre/bin/itweb-settings* lrwxrwxrwx 1 root root 67 Dec 24 12:20 itweb-settings.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/jre/man/man1/itweb-settings.1.gz lrwxrwxrwx 1 root root 42 Nov 24 15:25 jar - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jar* lrwxrwxrwx 1 root root 52 Nov 24 15:25 jar.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jar.1.gz lrwxrwxrwx 1 root root 48 Nov 24 15:26 jarsigner - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jarsigner* lrwxrwxrwx 1 root root 58 Nov 24 15:26 jarsigner.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jarsigner.1.gz lrwxrwxrwx 1 root root 47 Nov 24 15:23 java - /usr/lib/jvm/java-7-openjdk-mipsel/jre/bin/java* lrwxrwxrwx 1 root root 57 Nov 24 15:23 java.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/jre/man/man1/java.1.gz lrwxrwxrwx 1 root root 44 Nov 24 15:25 javac - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javac* lrwxrwxrwx 1 root root 54 Nov 24 15:25 javac.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javac.1.gz lrwxrwxrwx 1 root root 46 Nov 24 15:26 javadoc - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javadoc* lrwxrwxrwx 1 root root 56 Nov 24 15:26 javadoc.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javadoc.1.gz lrwxrwxrwx 1 root root 44 Nov 24 15:27 javah - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javah* lrwxrwxrwx 1 root root 54 Nov 24 15:27 javah.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javah.1.gz lrwxrwxrwx 1 root root 44 Dec 24 12:29 javap - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javap* lrwxrwxrwx 1 root root 54 Dec 24 12:29 javap.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javap.1.gz lrwxrwxrwx 1 root root 49 Nov 24 15:27 javaws - /usr/lib/jvm/java-7-openjdk-mipsel/jre/bin/javaws* lrwxrwxrwx 1 root root 59 Nov 24 15:27 javaws.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/jre/man/man1/javaws.1.gz lrwxrwxrwx 1 root root 47 Dec 24 12:28 jconsole - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jconsole* lrwxrwxrwx 1 root root 57 Dec 24 12:28 jconsole.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jconsole.1.gz lrwxrwxrwx 1 root root 42 Dec 24 12:29 jdb - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jdb* lrwxrwxrwx 1 root root 52 Dec 24 12:29 jdb.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jdb.1.gz lrwxrwxrwx 1 root root 48 Dec 24 12:30 jexec - /usr/lib/jvm/java-7-openjdk-mipsel/jre/lib/jexec* lrwxrwxrwx 1 root root 53 Dec 24 12:30 jexec-binfmt - /usr/lib/jvm/java-7-openjdk-mipsel/jre/lib/jar.binfmt lrwxrwxrwx 1 root root 43 Dec 24 12:27 jhat - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jhat* lrwxrwxrwx 1 root root 53 Dec 24 12:27 jhat.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jhat.1.gz lrwxrwxrwx 1 root root 44 Dec 24 12:30 jinfo - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jinfo* lrwxrwxrwx 1 root root 54 Dec 24 12:30 jinfo.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jinfo.1.gz lrwxrwxrwx 1 root root 43 Dec 24 12:30 jmap - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jmap* lrwxrwxrwx 1 root root 53 Dec 24 12:30 jmap.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jmap.1.gz lrwxrwxrwx 1 root root 42 Dec 24 12:30 jps - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jps* lrwxrwxrwx 1 root root 52 Dec 24 12:30 jps.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jps.1.gz lrwxrwxrwx 1 root root 49 Dec 24 12:31 jrunscript - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jrunscript* lrwxrwxrwx 1 root root 59 Dec 24 12:31 jrunscript.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jrunscript.1.gz lrwxrwxrwx 1 root root 48 Dec 24
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
On Sat, Nov 3, 2012 at 11:18 AM, Steven Chamberlain ste...@pyro.eu.orgwrote: ... You might like to try iceweasel/10.0.10esr-1 on loongson-2f. ... I did it when I notice the new version available. And I tried it once more a few minutes back, given your comment. Unfortunately it's still hanging on me under gmail account. So to me it's behaving the same, even though it might have become a little more stable, :-( So I had to revert to anheng old 9.0.1-1loongson... Sorry for the bad news. -- Javier.
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
On Sat, Nov 3, 2012 at 3:29 PM, Steven Chamberlain ste...@pyro.eu.orgwrote: ... did you also update the xulrunner-10.0 package to 10.0.10esr-1? The relevant change might have been in that package rather than in the 'iceweasel' package. ... iceweasel 10 doesn't install without xulrunner 10... So yes, when updating iceweasel I also updated xulrunner, :-) So again, sorry for still bad news from me... Thanks, -- Javier.
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
The new unstable version still doesn't help. Currently on mipsel:
iceweasel 10.0.6esr-2
xulrunner-10.0 10.0.6esr-2
Iceweasel keeps hanging on gmail web interface on new 10.0.6esr-2
debian release. I got strace now, though I'll see how to provide
attachment later. For now, I'll point out that strace indicates
iceweasel reaches an infinite invalid argument loop:
gettimeofday({1344794173, 223105}, NULL) = 0
gettimeofday({1344794173, 366012}, NULL) = 0
gettimeofday({1344794173, 367223}, NULL) = 0
gettimeofday({1344794173, 377720}, NULL) = 0
gettimeofday({1344794173, 400642}, NULL) = 0
gettimeofday({1344794173, 416226}, NULL) = 0
gettimeofday({1344794173, 417000}, NULL) = 0
gettimeofday({1344794173, 420493}, NULL) = 0
gettimeofday({1344794173, 421108}, NULL) = 0
gettimeofday({1344794173, 422545}, NULL) = 0
gettimeofday({1344794173, 423126}, NULL) = 0
gettimeofday({1344794173, 428157}, NULL) = 0
gettimeofday({1344794173, 428844}, NULL) = 0
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
madvise(0x63fae000, 4096, MADV_DONTNEED) = -1 EINVAL (Invalid argument)
Iceweasle keeps there hanging until it's killed, with the same EINVAL madvise...
--
Javier.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
Had to gzip the strace output in order to be able to attach the file... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
Package: iceweasel Version: 10.0.5esr-2 Severity: important Notice dependency on xulrunner version 10.0.5esr-2... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: mipsel (mips64) Kernel: Linux 3.2.0-3-loongson-2f Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash +++ I own lemote mini-pcs with loongson-2f cpu (mipsel), and the official iceweasel hasn't ever worked out for me when accessing for example gmail account, even less bank accounts. I use debian mipsel unstable only... So far to be able to browse such pages, I'm using anheng testing repository (they don't provide unstable), and their iceweasel really works, but it's outdated. Not sure if they apply any special patches other than compiling specifically for loongson-2f... Their repo is: deb http://www.anheng.com.cn/loongson2f/testing ./ http://www.anheng.com.cn/loongson2f/testing/iceweasel/iceweasel9/iceweasel_9.0.1-1loongson_mipsel.deb http://www.anheng.com.cn/loongson2f/testing/iceweasel/iceweasel9/xulrunner-9.0_9.0.1-1loongson_mipsel.deb http://www.anheng.com.cn/loongson2f/testing/iceweasel/iceweasel9/libmozjs9d_9.0.1-1loongson_mipsel.deb I think now debian advertises support for loongson-2f, thus, I believe supporting official debian version of firefox is important. Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
Forgot to mention that what happens is that iceweasel just freezees, with no other option than killing the application. When running through command line from terminal, there's absolutely no error message, nothing. It used to be that one could login, and after a few seconds iceweasel would freeze. As of now I can even get to enter the login page of gmail, just freezes when getting there... The behavior has persisted since there was iceweasel 8 I believe, all the way through 9, and now 10... Remember I use unstable, and have tried experimental to see if things improve, :-) -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
On 5/19/12, Jonathan Nieder jrnie...@gmail.com wrote: Hi again, Jonathan Nieder wrote: Javier Vasquez wrote: MemTotal: 514432 kB SwapTotal: 2096408 kB [...] [ 92.796017] PM: Need to copy 66237 pages [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: 64647 [ 92.796017] PM: Not enough free memory [ 92.796017] PM: Error -12 creating hibernation image Yeah, that looks broken. Ping. Do you still have access to a system reproducing this bug? Are you still interested in pursuing it? If not, that's fine, but please do let us know so we can plan accordingly. Thanks, Jonathan I don't have access to the laptop. I hoped I could set my hands on it, but I haven't... So, if later on I face the same problems, and you close this one, I'll file a different one, :-) BTW, if I recall correctly setting to 0 /sys/power/image_size helped prevent the issue... Thanks, Javier. -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636170: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
After a couple of upgrades (two have ahppened) on linux-image (without version change), now I'm getting the connections I was missing. As I said the linux-image package has been upgrade twice, but still keeping same version, so I couldn't notice what change unfortunately, so if you look at packages versions, they're still the same: % aptitude search '~i' | 'grep' inux-image i linux-image-2.6-loongson-2f - Linux for Loongson 2F (dummy package) i linux-image-2.6.39-2-loongson-2 - Linux 2.6.39 for Loongson 2F i A linux-image-3.0.0-1-loongson-2f - Linux 3.0.0 for Loongson 2F i linux-image-loongson-2f - Linux for Loongson 2F (meta-package) Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640418: Does not use an initrd on mipsel/loongson-2f systems
Hi, I'm an user, not a dev, but I own a lemote mini-pc, not the laptop, and the linux kernel for loongson-2f can be loaded through initrd. Actually that's the way archloong does it. This doesn't have anything to do to the ability to boot with grub. Actually archloong does not support grub (neither any other bootloader on top of pmon) at all for lemote products... Even when gNewSense has been able to make grub work, not sure if only for laptops, or mini-pcs included, on debian this is broken for mini-pcs, when trying to load the initrd the machine just goes to limbo. So I'd suggest not to depend upon grub to make decisions about the kernel or initrd... That said, I think using an initrd should be no problem, given that other distros are using it. But this ability should not depend upont grub. Whether because grub is broken, or because people wan to still use the pmon bootloader, or because enabling pmon as a backup when things go wrong with grub, people should still be able to load the initrd, or to use an ext4 root FS. Notice also that to get ext4 support for root, there's no need for initrd either. It could be gotten by providing direct native support in the kernel. This sounds like the safest, cause then mounting the root FS will work no matter something else is broken, like loading the initrd or booting through grub... In the case of archloong, the dev decided to support initrd, and still ext4 is compiled directly within the kernel, not as a module, and it doesn't have problems having root FS being ext4... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636170: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
One clarification on the msn connection issue. I can connect on the gateway. I can not connect on the boxes connected to the gateway, :-) So this to re-enforce the idea it's something in the forwarding, or filtering provided by iptables which seems broken... Just in case this was not clear... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636417: linux-image-3.0.0-1-loongson-2f: loongson-2f linux kernel in stock compiled with ipv6 as module, which conflicts with procps
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Tags: ipv6 *** Please type your report below this line *** The loongson-2f stock kernel on debian comes with ipv6 compiled as a module. However that's not expected by procps. See: /usr/share/doc/procps/README.Debian ... ipv6 sysctl keys Modern Debian kernel packages have the IPv6 module compiled in by default. This means that the /proc/sys/net/ipv6 directory exists when the procps startup script runs. However if you make your own kernel then you may make ipv6 a module and get a race condition between the netbase and procps startup scripts. This is because netbase, by default, causes ipv6 module to be loaded but they don't (and cannot) depend on each-other. The solution is to either: - Not put ipv6 keys into /etc/sysctl.d/* or /etc/sysctl.conf - Compile the ipv6 module into the kernel - Load the module early by putting ipv6 into /etc/modules - Make a init script dependency by adding netbase to the Required-Start line in /etc/init.d/procps ... Tha clearly states the debian stock kernels should have no problem given that they come with ipv6 built inside. However loongson-2f stock kernels don't comply with this. This causes failures like: error: net.ipv6.bindv6only is an unknown key Work around is really simple, just to add ipv6 into /etc/modules, however that shouldn't be the case for stock kernels according to procps documentation, and also a bug filed for that purpose last year (closed already): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507788 Any ways, just the loongson-2f kernel not being compliant with procps suppositions, :-) Thanks, Javier. -- Package-specific info: ** Version: Linux version 3.0.0-1-loongson-2f (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 Mon Jul 25 21:17:28 UTC 2011 ** Command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Not tainted ** Kernel log: [2.088000] PM: Hibernation image partition 8:5 present [2.088000] PM: Looking for hibernation image. [2.092000] PM: Image not found (code -22) [2.092000] PM: Hibernation image not present or could not be loaded. [2.092000] registered taskstats version 1 [2.092000] /build/buildd-linux-2.6_3.0.0-1-mipsel-TFQf1R/linux-2.6-3.0.0/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [2.096000] Initializing network drop monitor service [2.12] EXT3-fs: barriers not enabled [2.128000] kjournald starting. Commit interval 5 seconds [2.128000] EXT3-fs (sda6): mounted filesystem with ordered data mode [2.128000] VFS: Mounted root (ext3 filesystem) readonly on device 8:6. [2.132000] Freeing unused kernel memory: 240k freed [4.312000] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [4.312000] r8169 :00:06.0: (unregistered net_device): no PCI Express capability [4.312000] r8169 :00:06.0: eth0: RTL8169sc/8110sc at 0x900050072000, 00:23:9e:00:0f:62, XID 1800 IRQ 36 [4.48] cpufreq: Loongson-2F CPU frequency driver. [4.54] usbcore: registered new interface driver usbfs [4.556000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [4.604000] usbcore: registered new interface driver hub [4.612000] rtc0: alarms up to one day, 114 bytes nvram [4.644000] usbcore: registered new device driver usb [4.688000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [4.744000] PCI: Setting latency timer of device :00:0e.5 to 64 [4.744000] ehci_hcd :00:0e.5: EHCI Host Controller [4.776000] ehci_hcd :00:0e.5: new USB bus registered, assigned bus number 1 [4.828000] ehci_hcd :00:0e.5: irq 11, io mem 0x50071000 [4.848000] ehci_hcd :00:0e.5: USB 0.0 started, EHCI 1.00 [4.888000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [4.892000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.896000] usb usb1: Product: EHCI Host Controller [4.90] usb usb1: Manufacturer: Linux 3.0.0-1-loongson-2f ehci_hcd [4.904000] usb usb1: SerialNumber: :00:0e.5 [4.924000] hub 1-0:1.0: USB hub found [4.944000] hub 1-0:1.0: 4 ports detected [4.996000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [5.004000] PCI: Enabling device :00:0e.4 ( - 0002) [5.036000] PCI: Setting latency timer of device :00:0e.4 to 64 [5.036000] ohci_hcd :00:0e.4: OHCI Host Controller [5.044000] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 2 [5.064000] ohci_hcd :00:0e.4: irq 11, io mem 0x5007 [5.156000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [5.16] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.164000] usb usb2: Product: OHCI Host Controller [
Bug#636170: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
Package: linux-2.6 Version: 3.0.0-1 Severity: important *** Please type your report below this line *** I'm using a lemote mini-pc as my gateway through simple iptables configuration. I use debian unstable. With yesterday upgrade which updated linux kernel to 3.0.0-1 and iptables as well, my gateway broke. % cat /var/log/aptitude ... [UPGRADE] iptables 1.4.11.1-3 - 1.4.12-1 ... [UPGRADE] linux-image-loongson-2f 2.6.39+35.1 - 3.0.0+39 ... What got broken is some connection from internal boxes connected to the gateway to some outside places external to the gateway. For example, trying to upgrade again Today from the gateway had no problem at all. However trying to upgrade from an internal box was hard, both in the sense that getting the headers took way longer than in the gateway, and that when the time came for safe-upgrade and after downloading the packages, apt-listbugs just failed indicating it couldn't connect to extract the bug information. To get to upgrade on the internal boxes, the apt-listbugs part of the process was canceled. I also connect to a msn account through pidgin. But since the upgrade until I installed back 2.6.39-2 linux kernel, I could NOT connect at all to msn. To get msn workign back, I just had to install old prior working kernel 2.6.39-2. The prior confirms to me that actually the problem was not with iptables, since I didn't have to even try downgrading it. Just by installing 2.6.39-2 linux kernel version for loongson-2f worked out great. Notice that there are several changes in the kernel config files (under boot) between 2.6.39-2 and 3.0.0-1, however I couldn't appreciate any significant variation that could have affected the iptables behavior. My iptables script that is under: /etc/network/if-up.d/00_gateway It's pretty simple: ++ # delete all existing rules and clean up. iptables -P INPUT ACCEPT iptables -P FORWARD ACCEPT iptables -P OUTPUT ACCEPT iptables -F iptables -t nat -F iptables -t mangle -F iptables -X # Always accept loopback traffic iptables -A INPUT -i lo -j ACCEPT # Allow established connections, and those not coming from the outside iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -m state --state NEW ! -i ppp0 -j ACCEPT iptables -A FORWARD -m state --state ESTABLISHED,RELATED -i ppp0 -o eth0 -j ACCEPT # Allow outgoing connections from the LAN side. iptables -A FORWARD -i eth0 -o ppp0 -j ACCEPT # Masquerade. iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE # Don't forward from the outside to the inside. iptables -A FORWARD -i ppp0 -o ppp0 -j REJECT ++ That's it, pretty simple as well... Also I'm using an usb NIC to connect outside the gateway through ppp: /etc/network/interfaces ++ auto lo iface lo inet loopback # The internal LAN on embedded NIC auto eth0 iface eth0 inet static pre-up /sbin/ethtool -K eth0 rx off post-up /sbin/ethtool -K eth0 rx off address 192.168.2.1 netmask 255.255.255.0 network 192.168.2.0 broadcast 192.168.2.255 # The external LAN USB NIC auto eth1 iface eth1 inet manual ## The dsl-provider through PPPoE auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth1 up # line maintained by pppoeconf provider dsl-provider post-down /sbin/ifconfig eth1 down ++ I didn't have the post-up command before for the built-in NIC, but one of my initial thoughs was that perhaps one of the changes was related to that, but in reality it was not the issue. One needs to disable hardware crc sum calculation on the realtek built-in card otherwise the NIC transports wrong packages... Again this seems not to be the issue though, since the setting (/sbin/ethtool -K eth0 rx off) is working out in the prior kernel, and has no observed effect in the current one. So I can't really use at this moment linux kernel 3.0.0-1 on my gateway. My work around was to use prior one 2.6.39-2 still present on testing, and with the work around the problems go away, :-) Not sure what changes in the linux kernel for loongson-2f cause the new misbehavior, but it's sure the kernel is the one preventing my connections from internal boxes connected to my gateway... % aptitude search '~i' | 'grep' linux-image u linux-image-2.6-loongson-2f - Linux for Loongson 2F (dummy package) i linux-image-2.6.39-2-loongson-2 - Linux 2.6.39 for Loongson 2F i A linux-image-3.0.0-1-loongson-2f - Linux 3.0.0 for Loongson 2F i linux-image-loongson-2f - Linux for Loongson 2F (meta-package) Any help to get the kernel work properly with iptables for a gateway will be most appreciated... Thanks, Javier. -- Package-specific info: ** Model information system type : lemote-fuloong-2f-box cpu model : ICT Loongson-2 V0.3 FPU V0.1 ** PCI devices: 00:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10) Subsystem:
Bug#636170: Fwd: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
Just an upgrade. When trying to install the prior 2.6.39-2 kernel I tried a kernel package that was not necessary. After fixing that, the look fro kernel packages installed look this way: % aptitude search '~i' | 'grep' linux-image i linux-image-2.6-loongson-2f - Linux for Loongson 2F (dummy package) i linux-image-2.6.39-2-loongson-2 - Linux 2.6.39 for Loongson 2F i A linux-image-3.0.0-1-loongson-2f - Linux 3.0.0 for Loongson 2F i linux-image-loongson-2f - Linux for Loongson 2F (meta-package) This doesn't affect at all, what has been exposed. Actually with that little mess my 2.6.39-2 kernel was working correctly... Thanks, -- Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636095: linux-image-3.0.0-1-loongson-2f: loongson-2f should have ext4 built-in support and not as a module
Package: linux-2.6 Version: 3.0.0-1 Severity: normal *** Please type your report below this line *** I have 2 lemote mini-pcs, and for both I have separate partitions for boot and root. boot needs to be ext3, given that's what pmon boot loader supports. However root can be whatever filesystem linux supports. Now problem is the lonngson-2f kernel comes without initrd, and the one generated by initramfs-tools doesn't work. So whatever FS is used needs to be built inside the kernel itself and not compiled as a module. ext3 is built inside the kernel, however ext4 is not: % 'grep' -i ext3 /boot/config-3.0.0-1-loongson-2f CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y % 'grep' -i ext4 /boot/config-3.0.0-1-loongson-2f CONFIG_EXT4_FS=m CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set I've used ext4 as the FS for root en several systems, including x86-64 and x86-32. Moreover I also tried using archloong (arch linux side attempt for loongson), which had ext4 built inside the kernel, and I had no problems whatsoever with it. So current configuration inhibits ext4 FS to be used as the root one, and I really see no reason not to have it built in. Please reconsider having ext4 built inside the kernel at least for loongson-2f one. Thanks, Javier. -- Package-specific info: ** Version: Linux version 3.0.0-1-loongson-2f (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 Mon Jul 25 21:17:28 UTC 2011 ** Command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Not tainted ** Kernel log: [ 2.10] PM: Hibernation image partition 8:5 present [ 2.10] PM: Looking for hibernation image. [ 2.104000] PM: Image not found (code -22) [ 2.104000] PM: Hibernation image not present or could not be loaded. [ 2.104000] registered taskstats version 1 [ 2.104000] /build/buildd-linux-2.6_3.0.0-1-mipsel-TFQf1R/linux-2.6-3.0.0/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 2.108000] Initializing network drop monitor service [ 2.132000] EXT3-fs: barriers not enabled [ 2.14] kjournald starting. Commit interval 5 seconds [ 2.14] EXT3-fs (sda6): mounted filesystem with ordered data mode [ 2.14] VFS: Mounted root (ext3 filesystem) readonly on device 8:6. [ 2.144000] Freeing unused kernel memory: 240k freed [ 4.292000] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 4.30] r8169 :00:06.0: (unregistered net_device): no PCI Express capability [ 4.308000] r8169 :00:06.0: eth0: RTL8169sc/8110sc at 0x900050072000, 00:23:9e:00:0f:62, XID 1800 IRQ 36 [ 4.492000] cpufreq: Loongson-2F CPU frequency driver. [ 4.508000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 4.528000] rtc0: alarms up to one day, 114 bytes nvram [ 4.584000] usbcore: registered new interface driver usbfs [ 4.676000] usbcore: registered new interface driver hub [ 4.72] usbcore: registered new device driver usb [ 4.744000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.824000] PCI: Setting latency timer of device :00:0e.5 to 64 [ 4.824000] ehci_hcd :00:0e.5: EHCI Host Controller [ 4.828000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 4.852000] ehci_hcd :00:0e.5: new USB bus registered, assigned bus number 1 [ 4.90] ehci_hcd :00:0e.5: irq 11, io mem 0x50071000 [ 4.92] ehci_hcd :00:0e.5: USB 0.0 started, EHCI 1.00 [ 4.932000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 4.936000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.94] usb usb1: Product: EHCI Host Controller [ 4.944000] usb usb1: Manufacturer: Linux 3.0.0-1-loongson-2f ehci_hcd [ 4.948000] usb usb1: SerialNumber: :00:0e.5 [ 4.96] hub 1-0:1.0: USB hub found [ 4.976000] hub 1-0:1.0: 4 ports detected [ 4.988000] PCI: Enabling device :00:0e.4 ( - 0002) [ 5.004000] PCI: Setting latency timer of device :00:0e.4 to 64 [ 5.004000] ohci_hcd :00:0e.4: OHCI Host Controller [ 5.02] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 2 [ 5.028000] ohci_hcd :00:0e.4: irq 11, io mem 0x5007 [ 5.12] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 5.124000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.128000] usb usb2: Product: OHCI Host Controller [ 5.132000] usb usb2: Manufacturer: Linux 3.0.0-1-loongson-2f ohci_hcd [ 5.136000] usb usb2: SerialNumber: :00:0e.4 [ 5.144000] hub 2-0:1.0: USB hub found [ 5.148000] hub 2-0:1.0: 4 ports detected [ 5.40] PCI: Setting latency timer of device
Bug#615609: [loongson-dev] Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
On Sun, Mar 27, 2011 at 7:42 PM, wu zhangjin wuzhang...@gmail.com wrote: Hi, Javier Thanks very much for your report. I don't have such a USB to reproduce the problem, hope the folks from Lemote can work on it. thanks! Regards, Wu Zhangjin Any sugestions on how to try debugging this? -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615609: [loongson-dev] Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
1) try this NIC with another machine (non-Loongson); Done, it works well on x86_32 and x86_64 (both intel). I've also tried: acpi=noirq usbcore.autosuspend=-1 Which in the past have been able to solve other serial usb issues, but none worked out... 2) try another kind of NIC on this machine (e.g. there are MosChip mcs7830 based USB NICs which also support true USB 2.0 speeds, or if USB 1.1 with 12 mbit is enough, then Davicom dm9601 can be an option). I'll look for them. I acquired another one to try, but at the end it was based upon the same chipset, so also the same driver, so it didn't help. I'll look in the web... As for trying different module parameters you mentioned earlier, usbnet and asix do not have any tunables, but ehci_hcd does have some, you can check them out with sudo modinfo ehci_hcd. Thanks a lot Roman, I'll investigate as soon as possible. I'd like a work around before going to buy something else, so this will be my first step, :-) So far no luck, but I'll keep trying, and if anyone gets to find something, please let me know... Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620582: libgcj-common: /usr/bin/rebuild-gcj-db line 92 evaluating for 4.4 version when it should be 4.5
Package: libgcj-common Version: 1:4.4.5-6 Severity: important *** Please type your report below this line *** I'm using debian unstable under a loongson-2f mini-pc (mipsel arch), and currently libreoffice-gcj can't be upgraded to 1:3.3.1-1 unless /usr/bin/rebuild-gcj-db line 92 gets fixed, so far it evaluates for version 4.4, but it should be evaluating for version 4.5, since it then if present executes version 4.5. Problem is that if the system doesn't include version 4.5, and it does include version 4.4, as it's evaluating for 4.4 the script fails... So upgrading libreoffice-gcj fails eventually in a different place. But any ways it should evaluate for the version it executes... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: mipsel (mips64) Kernel: Linux 2.6.38-2-loongson-2f Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgcj-common depends on: ii python2.6.6-12 interactive high-level object-orie libgcj-common recommends no packages. libgcj-common suggests no packages. -- no debconf information Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
Just to let you know the problem is still present under 2.6.37-2 debian kernel and 2.6.38-1 debian kernel... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
Package: linux-2.6 Version: 2.6.37-1 File: linux-image-2.6.37-1-loongson-2 Severity: important Tags: upstream *** Please type your report below this line *** I have a lemote mini-pc loongson-2f, and when hooking an external usb NIC, the trendenet TU2-ET100, after disabling the inner NIC (realtek), then the device starts working nice for a while and then all of a sudden it just halts, and doing ifdown/ifup combination several times doesn't seem to be able to bring it up. I believe this problem is not exclusive to debian given that I've tried the gnew-sense 2.6.37 kernel, and another one from anheng, and none seems to work for this. Perhaps it exposes a HW problem, such the one for the inner NIC which can't handle checksums, and the CPU needs to deal with them (/sbin/ethtool -K eth0 rx off), but if it's a HW problem there might be a way to work around it (such as some usb-net or asix modules parameters). I'm not aware of any known problem related to this, so the first suspect is a kernel problem associated to the usb-net or the asix modules, which are the ones loaded for this external USB device. Perhaps for lemote HW there are some specific compile options required, and maybe missing, :-) Please notice the kernel was loaded with debug boot parameter, and even by doing so, the kernel log only shows the following associated to this problem: [ 68.076000] usb 1-1: new high speed USB device using ehci_hcd and address 4 [ 68.22] usb 1-1: New USB device found, idVendor=0b95, idProduct=7720 [ 68.22] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 68.22] usb 1-1: Product: AX88772 [ 68.22] usb 1-1: Manufacturer: ASIX Elec. Corp. [ 68.22] usb 1-1: SerialNumber: 01 [ 69.164000] asix 1-1:1.0: eth1: register 'asix' at usb-:00:0e.5-1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:08:1c:5f [ 69.164000] usbcore: registered new interface driver asix [ 173.484000] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 173.62] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 184.12] eth1: no IPv6 routers present [ 593.268000] ehci_hcd :00:0e.5: force halt; handshake 900050071014 4000 - -145 [ 593.268000] ehci_hcd :00:0e.5: can't reschedule qh 9800bc2d5200, err -145 [ 593.268000] ehci_hcd :00:0e.5: force halt; handshake 900050071014 4000 4000 - -145 [ 593.268000] ehci_hcd :00:0e.5: HC died; cleaning up [ 593.272000] usb 1-1: USB disconnect, address 4 [ 593.28] asix 1-1:1.0: eth1: unregister 'asix' usb-:00:0e.5-1, ASIX AX88772 USB 2.0 Ethernet While this is still a problem, the mini-pc is of not much usage to me, given that its aimed to work as a two NICs gateway (and light server for couple of light services). The ineer NIC is working now after the work around for the checksum (inner NIC can handle the checks), but I'm still missing the external usb NIC to work... Below is additional information... -- Package-specific info: ** Version: Linux version 2.6.37-1-loongson-2f (Debian 2.6.37-1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-2) ) #1 Wed Feb 16 17:37:56 UTC 2011 ** Command line: console=tty no_auto_cmd root=/dev/sda6 resume=/dev/sda5 debug PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Not tainted ** Kernel log: [5.288000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [5.292000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.296000] usb usb2: Product: OHCI Host Controller [5.30] usb usb2: Manufacturer: Linux 2.6.37-1-loongson-2f ohci_hcd [5.304000] usb usb2: SerialNumber: :00:0e.4 [5.312000] hub 2-0:1.0: USB hub found [5.316000] hub 2-0:1.0: 4 ports detected [5.596000] PCI: Setting latency timer of device :00:0e.3 to 64 [5.68] usbcore: registered new interface driver usbserial [5.688000] USB Serial support registered for generic [5.716000] usb 2-3: new low speed USB device using ohci_hcd and address 2 [5.944000] usb 2-3: New USB device found, idVendor=04d9, idProduct=1702 [5.952000] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.956000] usb 2-3: Product: USB Keyboard [5.96] usb 2-3: Manufacturer: [6.272000] usb 2-4: new low speed USB device using ohci_hcd and address 3 [6.496000] usb 2-4: New USB device found, idVendor=0458, idProduct=003a [6.50] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.504000] usb 2-4: Product: Optical Mouse [6.508000] usb 2-4: Manufacturer: Genius [6.612000] input: USB Keyboard as /devices/pci:00/:00:0e.4/usb2/2-3/2-3:1.0/input/input0 [6.628000] generic-usb 0003:04D9:1702.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-:00:0e.4-3/input0 [6.652000] usbcore: registered new interface driver usbserial_generic [6.656000] usbserial: USB Serial Driver core [6.684000] input: USB Keyboard
Bug#614127: confirmed on allmachines: painfull
... Some additional information from the original submitter (Javier Vasquez) is required before this can be done. Javier, do you have console-setup installed on your machine? If yes, then what is the version of the package xkb-data and what happens if you run setupcon on the console? Anton Zinoviev P.S. I hope tomorow I will be able to upload a fixed version of console-setup. Yes, and actually that's what I tried first... As I'm at work, I don't have the mini-pc available with me. Let me answer when I'm back at home... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614127: confirmed on allmachines: painfull
On Wed, Feb 23, 2011 at 1:37 PM, Javier Vasquez j.e.vasque...@gmail.com wrote: ... Some additional information from the original submitter (Javier Vasquez) is required before this can be done. Javier, do you have console-setup installed on your machine? If yes, then what is the version of the package xkb-data and what happens if you run setupcon on the console? Anton Zinoviev P.S. I hope tomorow I will be able to upload a fixed version of console-setup. Yes, and actually that's what I tried first... As I'm at work, I don't have the mini-pc available with me. Let me answer when I'm back at home... Thanks, -- Javier. Package: console-setup Version: 1.69 Package: xkb-data Version: 2.1-1 -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614127: confirmed on allmachines: painfull
On Wed, Feb 23, 2011 at 10:50 PM, Anton Zinoviev an...@lml.bas.bg wrote: reassign 614127 console-setup severity 614127 normal forcemerge 614550 614127 thanks On Wed, Feb 23, 2011 at 09:35:42PM -0600, Javier Vasquez wrote: Package: console-setup Version: 1.69 Package: xkb-data Version: 2.1-1 So, the you have version 2.1-1 of xkb-data too. I am reassigning the bug correspondingly. I am lowering the severity becase this version of xkb-data has not entered unstable yet. On Wed, Feb 23, 2011 at 10:09:23PM -0600, Javier Vasquez wrote: It fails: % dpkg-reconfigure console-setup Bad number of antecedents at /usr/bin/ckbcomp line 2571, RULES line 372. Line 2571 indicates: 2571 @antecedent_patterns == @antecedents 2572 or die Bad number of antecedents; And line 372: 372 'parenlef' = '0028', # Is this recognised by X ? (speling error) This was actualy line 372 of /usr/share/X11/xkb/rules/base: 372 htcdream us de it = %l(htcdream) I don't even know how to interpret this line. It looks like an error. It seems line 369 already does what was intended (the value of $htcdreamlayouts is us it de): 369 htcdream $htcdreamlayouts = %l(htcdream) I'll report this. For now my recommendation is to remove line 372 from /usr/share/X11/xkb/rules/base. It is related to the micro-keyboard of the HTC Dream mobile device which doesn't support Debian. Anton Zinoviev Hi Anton, as the answer was to you directly my 2nd answer which hadn't reached you apparently shows that I found the issue with the errors, though with my limited knowledge I think there shouldn't be any issues... So your provided file worked fine with a couple of things worth mentioning. I'm copying in here... +++ Found the issue with the failure, but I don't like the solution, :-) One of the things keyboard-configuration doesn't ask, is whether there are alternative languages to the primary ones, so one of my trials (when dpkg-reconfigure keyboard-configuration didn't help out) was to set /etc/default/keyboard by hand, and I used the same configuration I use for X: XKBMODEL=pc105 XKBLAYOUT=latam,us XKBVARIANT= XKBOPTIONS=lv3:ralt_switch,grp:alt_shift_toggle Apparently console-setup didn't like something from the previous. But using what keyboard-configuration limits by default doesn't make console-setup to fail: XKBMODEL=pc105 XKBLAYOUT=latam XKBVARIANT= XKBOPTIONS=lv3:ralt_switch,terminate:ctrl_alt_bksp Is this configuration meant for X as well? So is it true then that alternative languages support is not supported? If so for X (that's where sometimes I use us layout) I'll keep setting the keyboard layout on xorg.conf as I have kept so far though the xorg changes to eliminate xorg.conf and keyboard and mouse config in ther, :-) For console, well just the native keybord language layout is OK for me, :-) The other problem is that once one runs dpkg-reconfigure keyboard-configuration and then also dpkg-reconfigure console-setup the console does not change at all. The layout keeps at its default (us) no matter how many times those things are run. The changes ONLY take effect after reboot, or probably (something I found by looking at the reboot messages) by doing sudo invoke-rc.d keyboard-setup start, or perhaps sudo setupcon -k. It'd be nice if both dpkg-reconfigure keyboard-configuration and dpkg-reconfigure console-setup provide a clue to perform any of the prior instructions so that the console changes configuration without needing a reboot, :-) Other than those two issues I can live with, the configuration was kept after reboot, which was the original bug, :-) My concern is that in my mind the solutions requires a bit of shining, but I can live with it actually, :-) +++ Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
On Tue, Feb 22, 2011 at 1:19 PM, Aurelien Jarno aurel...@aurel32.net wrote: On Mon, Feb 21, 2011 at 02:01:16PM -0800, Vagrant Cascadian wrote: ... So, it really was the VGA driver the one making qemu -enable-kvm not to work. IMHO, it's most probably a duplicate of #614169. Might be, but 614169 doesn't talk about making qemu -enble-kvm unusable. It indicates a warning message is all there is to it, not wrong functionality, neither that -vga std or -vga vmware break qemu -enable-kvm, which is what I'm experiencing. However I don't know much about the inner details of qemu to have a better opinion, :-) -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614127: keyboard layout doesn't keep after reboot
On Mon, Feb 21, 2011 at 12:22 AM, Christian PERRIER bubu...@debian.org wrote: Quoting Javier Vasquez (j.e.vasque...@gmail.com): ... Well, no change in console-data is likely to have triggerred this. The package is completely stalled and the last change (in wheezy) was adding a keymap for Kazakhno change to any debconf stuff and the way the default keymap is handled. OK, prhaps the next update of the package, :-)... PS: try dpkg-reconfigure keyboard-configuration. *this* is the console-setup component that deals with this stuff. Forgot to mentioned I did that already, and didn't work. BTW, it looked like the configuration for X, :-)... Any ways it didn't help out... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
On Sun, Feb 20, 2011 at 12:39 PM, Vagrant Cascadian vagr...@freegeek.org wrote: On Sun, Feb 20, 2011 at 11:24:16AM -0600, Javier Vasquez wrote: ... i know you've tried a variety of commandline options, but what about just using the defaults with -enable-kvm? If I don't specify cpu it doesn't work, the only NIC that works is rtl8139, and with the virtio drivers then the virtio NIC as well. At the beginning I didn't require to use virtio scsi storage for disks, but now it's a must, otherwise, as I indicated before, the guest just freezes with high cpu utilization. In other words, little room I see to make more variations on the parameters to the qemu command line, and for sure defaults don't work for this XP image, which is a HP-COE one. BTW. ... do you have other hardware you can test with? -enable-kvm seems to work for me on i386, at least. Unfortunately not, :-( are you able to boot a different OS? i've only tested with Debian/GNU Linux or Debian/GNU kFreeBSD. You mean guest OS? Nope I haven't tried other guests, and can't run on different host either any ways, :-) live well, vagrant Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
On Mon, Feb 21, 2011 at 11:29 AM, Javier Vasquez j.e.vasque...@gmail.com wrote: On Sun, Feb 20, 2011 at 12:39 PM, Vagrant Cascadian vagr...@freegeek.org wrote: On Sun, Feb 20, 2011 at 11:24:16AM -0600, Javier Vasquez wrote: ... i know you've tried a variety of commandline options, but what about just using the defaults with -enable-kvm? In other words, little room I see to make more variations on the parameters to the qemu command line, and for sure defaults don't work ... Hmm, found the issue, :-) If I do not specify VGA driver at all, meaning I do not use vga=std or vga=vmware, things work as expected needing no change in any other parameter. So, it really was the VGA driver the one making qemu -enable-kvm not to work. As it was mentioned it was not the issue, I got insisting on other things like the virtio drivers, cpu, driver, sound driver, etc... But the suggestion of using defaults helped, since it entitled me to challenge the VGA driver... Any ways, the cyrrus driver used by default is really bad. It provides just too few configurations, an the max resolution I can get is 1280x1024 @ 16 bits color depth. Not only that is bad, but also I can't use a resolution at least proportional to the one in the host (1920x1200) so that I can expand it proportionally to the available space... So now, at least I can work with qemu-kvm again, but with very poor VGA driver. BTW, I'm wondering why there's no such a driver that auto configures resolution keeping high color depth, like virtualbox' one... So one just resizes the guest screen, and the resolution gets automatically adjusted as with NX as well, the the font can get adjusted for the common size, :-) Any ways, I still see a bug in here, by not supporting -vga std, neither -vga vmware, but I'd say the bug is no longer that severe, and it can be renamed (no idea how to do any of those things), :-)... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614127: keyboard layout doesn't keep after reboot
On Sun, Feb 20, 2011 at 7:20 AM, Christian PERRIER bubu...@debian.org wrote: Quoting Javier Vasquez (j.e.vasque...@gmail.com): ... You indeed should use console-setup. console-data is no longer installed by default on Debian and we'll probably try to get rid of it during the squeeze-wheezey release cycle. So, there are few chances that this bug is investigated, indeed. FYI, dpkg-reconfigure console-setup does not offer any configuration associated to the keyboard layout. That's why dpkg-reconfigure console-data had to be tried instead... BTW, it was working before the last upgrade, :-) Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
Subject: qemu -enable-kvm freezes Package: qemu Version: 0.14.0+dfsg-2 Justification: renders package unusable Severity: grave *** Please type your report below this line *** On an amd64 laptop (debian unstable) I've been using qemu with the following arguments (with windows XP guest): ARGS_GEN=-enable-kvm -drive file=$1,if=virtio -boot order=c -m 512 -rtc base=localtime ARGS_NET=-net nic -net tap,ifname=tap0,script=no,downscript=no ARGS_BIOS0=-smbios file=/home/vasqueja/.qemu_kvm/bios_bin/smbios_type_0.bin ARGS_BIOS1=-smbios file=/home/vasqueja/.qemu_kvm/bios_bin/smbios_type_1.bin ARGS_VGA=-vga std ARGS_AUDIO=-soundhw ac97 ARGS_USB=-usb -usbdevice tablet ARGS_CPU=-cpu athlon ARGS_NIC=-net nic,model=virtio qemu $ARGS_GEN $ARGS_NET $ARGS_BIOS0 $ARGS_BIOS1 $ARGS_VGA $ARGS_AUDIO $ARGS_USB $ARGS_CPU $ARGS_NIC Where $1 is provided as the qcow2 windows XP image. And it just with no action at all. As I was getting the following verbose print outs: qemu: pci_add_option_rom: failed to find romfile vgabios-stdvga.bin qemu: virtio_ioport_write: unexpected address 0x13 value 0x1 Initially I thought it was because I was using virtio driver for IO storage and NIC, then I changed that to use just plane -hda $1 and NIC model rtl8139 which work, but are necessary, since without the virtio NIC the guest will eventually freeze will the CPU consuming 100%... However by not using virtio drivers, the phenomena still shows up. Then I tried just removing the STD vga driver, and instead using the vmware (already installed in the guest) driver, and combinations of virtio drivers and vga ones, and nothing seems to work. I'm filing this against qemu package then, since not sure about the origin, but it seems not possible to load the guest client... The laptop is HP compaq 8510w... Notice as I'm using nouveau xorg driver version 1:0.0.16+git20101210+8bb8231-2, I can only use linux-image 2.6.37-1 (unstable default) and can't try the 2.6.32, so I can't test the kvm modules on older kernel... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu depends on: ii qemu-system0.14.0+dfsg-2 QEMU full system emulation binarie ii qemu-user 0.14.0+dfsg-2 QEMU user mode emulation binaries ii qemu-utils 0.14.0+dfsg-2 QEMU utilities qemu recommends no packages. Versions of packages qemu suggests: pn qemu-user-static none (no description available) -- no debconf information % uname -a Linux jvasquez14 2.6.37-1-amd64 #1 SMP Tue Feb 15 17:43:38 UTC 2011 x86_64 GNU/Linux Thanks -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614127: keyboard layout doesn't keep after reboot
Package: console-data Version: 2:1.10-9 Severity: important I have debian unstable running on a lemote mini-pc (loongson-2f cpu), and the console keyboard was working OK until Today that I made an upgrade... With currnt version of console data (already provided) and kbd (1.15.2-2), I have to perform after reboot dpkg-reconfigure console-data so that I can use the latin amerecan layout. The layout always coming out after reset is us... I tried using console-tools instead of kbd, but that doesn't change a bit, and the font size I like is not supported by console-tools. So this seems more like a console-data issue, given that by performing dpkg-reconfigure console-data I get the right layout I want, though it's tedious to keep doing this everytime after reboot... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: mipsel (mips64) Kernel: Linux 2.6.37-1-loongson-2f Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-data depends on: ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy Versions of packages console-data recommends: ii console-common0.7.85 basic infrastructure for text cons ii kbd 1.15.2-2 Linux console font and keytable ut Versions of packages console-data suggests: pn unicode-data none (no description available) -- debconf information: console-data/keymap/template/layout: console-data/keymap/family: qwerty console-keymaps-amiga/keymap: console-keymaps-at/keymap: console-keymaps-usb/keymap: console-keymaps-acorn/keymap: console-data/keymap/powerpcadb: console-keymaps-sun/keymap: console-data/keymap/template/variant: console-data/keymap/ignored: console-keymaps-dec/keymap: * console-data/keymap/full: la-latin1 console-keymaps-atari/keymap: console-keymaps-mac/keymap: console-data/keymap/template/keymap: * console-data/keymap/policy: Select keymap from full list console-data/bootmap-md5sum: 278e4b1dbfbae65f4688b0988dabbbda % uname -a Linux mini-1 2.6.37-1-loongson-2f #1 Wed Feb 16 17:37:56 UTC 2011 mips64 GNU/Linux Thanks -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598562: evolution-mapi can't be installed
Well, there are several dependencies upon experimental, but they can be overcome, :-) The problem about libgtkhtml-editor0 and libgtkhtml3.14-19 are to be fixed though. I had to edit 3 files: /var/lib/apt/lists/mirror_debian_dists_unstable_main_binary-amd64_Packages /var/lib/dpkg/status /var/lib/dpkg/available Look in those for the dependencies for evolution-mapi, and in all of them where it said = 1:3.30.2 for those 2 packages, I just used instead = 3.30.2, since the latest version for those 2 packages is 3.30.3-1 even higher than the one required, this solves the issue... It might be that 1: was just a typo... Once you modify those files, you can install it without problems, except by the fact you'll have to solve dependencies coming from experimental, which is not a big deal any ways... I have it installed, but haven't tested it yet... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
An additional detail is that apparently: echo 0 /sys/power/image_size Makes things work... I haven't tested enough to confirm though, neither I would know what exahustive kind of test would be required, but from couple of trials, it seems to work. Thanks to Ben Livengood who e-mailed me to try this... I still don't understand why the issue given that /sys/power/image_size controls the image size to be restored (best effort to try to keep it as small as indicated, though if not possible it'll be bigger). By default it's set to 500 MB... What is not clear to me if this setting helps as it seems, is why if the size is limited to 500 MB or a bit more, that would represent a problem given the swap space available? Now if the logic to apply is different, like as the RAM is 512 MB, perhaps it doesn't fit into 500 MB limit, which might be the case, but the documentation indicates it's best effort, meaning it can get bigger if it's not possible to make it fit, and even if a bit bigger, then there's plenty of swap in comparison. Any ways, with those questions at hand, then even if 500 MB is the default value for linux, why not making it 0 the default for debian? As I see it 0 doesn't hurt, and it's the more secure value, since it will always tend to minimize the image sizze to be restored, which in turns might also accelerate resume time... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588552: evolution-alarm-notify does not start automaticly anymore
Well, I'm using latest debian unstable evolution package, 2.30.3-1, though I don't use gnome, just plain fluxbox, and I still don't get evolution-alarm-notify loaded when starting evolution. Given that I have enabled show reminder, and the alarms on Personal and Birthdays..., I would expect the process to be launched automatically. But that's not happening... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588552: [Evolution] Bug#588552: evolution-alarm-notify does not start automaticly anymore
/etc/xdg/autostart/evolution-alarm-notify.desktop has: OnlyShowIn=GNOME;XFCE; so it won't start on other DE. If you remove that line, does it work? (in fact it'd be better to add it to your .local/etc/xdg/autostart). I removed the line from global /etc/xdg/autostart/evolution-alarm-notify.desktop, and then closed evolution and started it again. But unfortunately evolution-alarm-notify didn't get started automatically. So just removing that line didn't work out, :-( -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588552: [Evolution] Bug#588552: evolution-alarm-notify does not start automaticly anymore
BTW, by starting evolution-alarm-notify manually after evolution has been loaded, it seems to launch the alarms on time, as far as I know... -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588552: [Evolution] Bug#588552: Bug#588552: evolution-alarm-notify does not start automaticly anymore
OK, so evolution-alarm-notify can no longer be launched from evolution itself... Sad, :-( Any ways, good to know. Do you think it's best to start evolution-alarm-notify before evolution, or after? Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590817: evolution-mapi: Package is uninstallable, please update to 0.30.x
Hi, I think the latest evolution-mapi is 0.30.3, at least according to: http://ftp.acc.umu.se/pub/GNOME/sources/evolution-mapi/0.30 Under AUR for archLinux, I can see it depends upon openchange 0.9: http://aur.archlinux.org/packages/evolution-mapi/evolution-mapi/PKGBUILD And I see that openchange 0.9 is already the latest version upstream: http://www.openchange.org/index.php?option=com_phocadownloadview=categoryid=1:releases And it's already used in archLinux AUR as upstream version: http://aur.archlinux.org/packages/openchange/openchange/PKGBUILD So if there was a need for openchange 0.9 to be released, it already have. If there was a need for a different openchange version, I think that's not necessary with openchange 0.9... So perhaps now it can be uipgraded to 0.30.3, :-) -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
Answering to myself, :-) The keys file generated automatically, when starting fluxbox with no ~/.fluxbox directory present seems to work OK, as it was suggested previously. I just couldn't use the old ~/.fluxbox/keys since it got it overrided witht the /etc/X11/fluxbox/keys... Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
OK to me. Thanks... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
One more thing missing (didn't notice before). I can't resize any window application at all from the left/right bottom corners with left mouse. Is there any particular configuration for that? Attaching keys configuration file copied from /etc/X11/fluxbox, andmodified so that alt-left alt-right is all nedded to move to prev/next work spaces (desktops)... keys Description: Binary data
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
Package: fluxbox Version: 1.1.1+git20100807.0cc08f9-1 Severity: serious The recent upgraded fluxbox on unstable does not allow moving window applications inside a window desktop through pressing left mouse button and moving the window around. It's still possible to use the middle button, which is not present on every mouse, but the behaviour is different than the left button, since the application window is hidden, leaving just the application bar, and the movement is more limited than with left button. % uname -a Linux jvasquez14 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
Reporting back that: OnTitlebar Mouse1 :StartMoving Actually fixed the issue. So it was a matter of changing the configuration file as mentioned. Perhaps this can be closed then as a user configuration issue. As mentioned fixing /etc/X11/fluxbox/keys doesn't fix ~/.fluxbox/keys, but a key learning for users might be to always compare configuration files against global ones when upgrades happen. Thanks for quick response... Javier. On 8/13/10, Paul Tagliamonte paul...@ubuntu.com wrote: retitle: Fluxbox's upstrem changes break old configuration files thanks Just going to reset the title to something more descriptive of what the issue is Thanks, Paul On Fri, Aug 13, 2010 at 4:21 PM, Paul Tagliamonte paul...@ubuntu.com wrote: Confirmed This happens because in 1.1.1 release, this was default behavior. Upstream decided to change this for the next release. To keep behavior standard, I patched the default config file to enable left click dragging. This does not carry over into the ~/.fluxbox/keys file, even though this option is in /etc/X11/fluxbox. One fix is to remove the .fluxbox directory and restart fluxbox. This is not acceptable for people who have very complex setups, but then again, if they have complex setups, they should be able to set this manually. -Paul On Fri, Aug 13, 2010 at 4:09 PM, Paul Tagliamonte paul...@ubuntu.com wrote: severity: important justification: alt + move should still work, and middle click ( emulated by left + right ) thanks The more I think about this, the more I think this is a migration issue for old packages. Retagging to important. -Paul On Fri, Aug 13, 2010 at 4:00 PM, Paul Tagliamonte paul...@ubuntu.com wrote: Hey Javier, Were you running fluxbox before? This could be due to a small issue with the git tree. This should not affect anyone just installing. Try adding this to your keys file OnTitlebar Mouse1 :StartMoving Please do follow up with this -Paul On Fri, Aug 13, 2010 at 3:38 PM, Javier Vasquez j.e.vasque...@gmail.com wrote: Package: fluxbox Version: 1.1.1+git20100807.0cc08f9-1 Severity: serious The recent upgraded fluxbox on unstable does not allow moving window applications inside a window desktop through pressing left mouse button and moving the window around. It's still possible to use the middle button, which is not present on every mouse, but the behaviour is different than the left button, since the application window is hidden, leaving just the application bar, and the movement is more limited than with left button. % uname -a Linux jvasquez14 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux -- #define sizeof(x) rand() :wq -- #define sizeof(x) rand() :wq -- #define sizeof(x) rand() :wq -- #define sizeof(x) rand() :wq -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
Package: linux-image-2.6.32-5-686 Version: 2.6.32-17 Severity: important I have debian unstable installed on a laptop Dell Inspiron 600m, with pentium M processor at 1.6 GHz: % cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 9 model name : Intel(R) Pentium(R) M processor 1600MHz stepping: 5 cpu MHz : 1600.000 cache size : 1024 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 tm pbe up bts est tm2 bogomips: 3189.09 clflush size: 64 cache_alignment : 64 address sizes : 32 bits physical, 32 bits virtual power management: The laptop includes 512 MB of RAM, and a partition with 2 GB of swap: % cat /proc/meminfo MemTotal: 514432 kB MemFree: 100192 kB Buffers: 21396 kB Cached: 152088 kB SwapCached:0 kB Active: 240888 kB Inactive: 141424 kB Active(anon): 162184 kB Inactive(anon):47256 kB Active(file): 78704 kB Inactive(file):94168 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 514432 kB LowFree: 100192 kB SwapTotal: 2096408 kB SwapFree:2096396 kB Dirty: 4 kB Writeback: 0 kB AnonPages:208828 kB Mapped:40536 kB Shmem: 612 kB Slab: 10976 kB SReclaimable: 4584 kB SUnreclaim: 6392 kB KernelStack: 984 kB PageTables: 1464 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit: 2353624 kB Committed_AS: 362324 kB VmallocTotal: 504128 kB VmallocUsed: 18188 kB VmallocChunk: 473956 kB HardwareCorrupted: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 4096 kB DirectMap4k: 290488 kB DirectMap4M: 233472 kB A brief from the meminfo: MemTotal: 514432 kB SwapTotal: 2096408 kB Most of the time when trying to perform a kernel suspend to disk, whether by using acpitool -S, which is my preferred method, or by directly writing disk into /sys/power/state, the suspend is attempted, but it fails and the machine returns to state priot to attempt... When looking at dmesg: [ 90.737713] Freezing user space processes ... (elapsed 0.00 seconds) done. [ 90.752182] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 90.766427] PM: Preallocating image memory... done (allocated 61556 pages) [ 90.817030] PM: Allocated 246224 kbytes in 0.03 seconds (8207.46 MB/s) [ 90.831363] Suspending console(s) (use no_console_suspend to debug) [ 90.847537] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 90.849254] parport_pc 00:0c: disabled [ 90.850417] serial 00:0b: disabled [ 90.972175] ipw2100 :02:03.0: PCI INT A disabled [ 92.656557] tg3 :02:00.0: PME# enabled [ 92.656568] pci :00:1e.0: wake-up capability enabled by ACPI [ 92.779840] Intel ICH Modem :00:1f.6: PCI INT B disabled [ 92.792231] Intel ICH :00:1f.5: PCI INT B disabled [ 92.792380] ata_piix :00:1f.1: PCI INT A disabled [ 92.795306] ACPI: Preparing to enter system sleep state S4 [ 92.795583] PM: Saving platform NVS memory [ 92.795672] Disabling non-boot CPUs ... [ 92.795783] PM: Creating hibernation image: [ 92.796017] PM: Need to copy 66237 pages [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: 64647 [ 92.796017] PM: Not enough free memory [ 92.796017] PM: Error -12 creating hibernation image [ 92.796716] ACPI: Waking up from system sleep state S4 The important part of the dmesg section above is: [ 92.796017] PM: Need to copy 66237 pages [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: 64647 [ 92.796017] PM: Not enough free memory [ 92.796017] PM: Error -12 creating hibernation image According to the kernel, there's a need of 67261 pages, when there are available only 64647. This is pretty weird, given that RAM size is only 512 MB, while swap partition is 2 GB, 4 times bigger, so there should be no issue. This kernel suspend to disk has always worked for me on this laptop, under debian unstable, and under other distros, like arch gnu/linux. I stopped using debian for a while and then recently installed debian unstable again, which came with linux-image-2.6.32-5-686, and since then it hasn't worked. There's an exception... Prior to current version (2.6.32-17) there was one which after which current one came after upgrade, which seemde to have fixed the issue, but as soon as I performed an upgrade and got current one, the issue cam back again. So there was a particular
Bug#494460: grub-pc: update-grub unable to generate a graphical gfxterm menu
On Sat, Aug 9, 2008 at 1:04 PM, Robert Millan [EMAIL PROTECTED] wrote:
On Sat, Aug 09, 2008 at 10:49:12AM -0600, Familia Vasquez-Vivas wrote:
Package: grub-pc
Version: 1.96+20080724-6
Severity: normal
The update-grub script evaluates `font_path` in order to determine
whether GRUB_FONT_PATH can be set to its output. However font_path
doesn't seem to be excutable... Therefore, although $GRUB_TERMINAL
originally came with the nice gfxterm setting, it gets reverted to
console, and there's no longer graphical menu, :(...
It was working nice to me before, not sure what happened...
font_path is a shell function, declared in update-grub_lib. Please describe
the symptoms of your problem before jumping into conclussions.
What is it exactly that you observed?
update-grub works just fine, except that I no longer get in grub.cfg
the gfxterm stuff (so I no longer get splash image menu). This
happens only in all my i686 boxes, not in the amd64 one... I modified
update-grub several times to identify where the problem was (with my
own debug hooks)... Just before case ${GRUB_TERMINAL} in I included
' echo \${GRUB_TERMINAL} - ${GRUB_TERMINAL} ', and I got
gfxterm. I did exactly the same after that piece of code and I got
console... So I thought that was the issue. To my surprise, this
doesn't seem the case for amd64.
I'm sorry for jumping into conclusions too soon, but after this little
debug I thought that was the issue...
So I'll try a bit further and see if there's a difference in
update-grub that's causing i686 version not to provide me with the
nice graphical menu, :)...
--
Robert Millan
Thanks,
--
Javier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494460: grub-pc: update-grub unable to generate a graphical gfxterm menu
On Sat, Aug 9, 2008 at 2:31 PM, Javier Vasquez [EMAIL PROTECTED] wrote:
On Sat, Aug 9, 2008 at 1:04 PM, Robert Millan [EMAIL PROTECTED] wrote:
On Sat, Aug 09, 2008 at 10:49:12AM -0600, Familia Vasquez-Vivas wrote:
Package: grub-pc
Version: 1.96+20080724-6
Severity: normal
The update-grub script evaluates `font_path` in order to determine
whether GRUB_FONT_PATH can be set to its output. However font_path
doesn't seem to be excutable... Therefore, although $GRUB_TERMINAL
originally came with the nice gfxterm setting, it gets reverted to
console, and there's no longer graphical menu, :(...
It was working nice to me before, not sure what happened...
font_path is a shell function, declared in update-grub_lib. Please describe
the symptoms of your problem before jumping into conclussions.
What is it exactly that you observed?
update-grub works just fine, except that I no longer get in grub.cfg
the gfxterm stuff (so I no longer get splash image menu). This
happens only in all my i686 boxes, not in the amd64 one... I modified
update-grub several times to identify where the problem was (with my
own debug hooks)... Just before case ${GRUB_TERMINAL} in I included
' echo \${GRUB_TERMINAL} - ${GRUB_TERMINAL} ', and I got
gfxterm. I did exactly the same after that piece of code and I got
console... So I thought that was the issue. To my surprise, this
doesn't seem the case for amd64.
I'm sorry for jumping into conclusions too soon, but after this little
debug I thought that was the issue...
So I'll try a bit further and see if there's a difference in
update-grub that's causing i686 version not to provide me with the
nice graphical menu, :)...
--
Robert Millan
Thanks,
--
Javier
Actually I think my conclusions are not that wrong... With the
following modifications to update-grub:
echo \${GRUB_TERMINAL} before evaluating font_path == ${GRUB_TERMINAL}
case ${GRUB_TERMINAL} in
gfxterm)
echo Next line is output of \`font_path\`:
echo `font_path`
if path=`font_path` ; then
GRUB_FONT_PATH=${path}
else
# fallback to console
GRUB_TERMINAL=console
fi
;;
esac
echo \${GRUB_TERMINAL} after evaluating font_path == ${GRUB_TERMINAL}
I get:
# update-grub
${GRUB_TERMINAL} before evaluating font_path == gfxterm
Next line is output of `font_path`:
${GRUB_TERMINAL} after evaluating font_path == console
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.26-1-686
Found initrd image: /boot/initrd.img-2.6.26-1-686
Found linux image: /boot/vmlinuz-2.6.25-2-686
Found initrd image: /boot/initrd.img-2.6.25-2-686
done
So you can actually that it's font_path returning NOTHING the
problem... I thought because NOT being executable, but it might be
something else, but actually font_path returning nothings is causing
the problem. Again this affects all i686 boxes, but not the only
amd64 I have. For the amd64 I get with the same modifications:
# update-grub
${GRUB_TERMINAL} before evaluating font_path == gfxterm
Next line includes `font_path` output:
/usr/share/grub/ascii.pff
${GRUB_TERMINAL} after evaluating font_path == gfxterm
Updating /boot/grub/grub.cfg ...
Found Debian background: debian-blueish-wallpaper-640x480.tga
Found linux image: /boot/vmlinuz-2.6.26-1-amd64
Found initrd image: /boot/initrd.img-2.6.26-1-amd64
Found linux image: /boot/vmlinuz-2.6.25-2-amd64
Found initrd image: /boot/initrd.img-2.6.25-2-amd64
done
And there's a difference in here, since for i686:
# ls /usr/share/grub/
#
So the /usr/share/grub directory is empty, while for amd64 I get:
# ls /usr/share/grub/
ascii.pff unicode.pff
So this might be the problem then... I think this is the further I
can go, it might be that the i686 debian package just didn't include
the /usr/share/grub stuff, and that'd be pretty much it, :)
I hope that's the problem, maybe a quick one to fix...
--
Javier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494460: grub-pc: update-grub unable to generate a graphical gfxterm menu
On Sat, Aug 9, 2008 at 5:01 PM, Felix Zielcke [EMAIL PROTECTED] wrote: tag 494460 pending retitle 494460 i386 builds are missing fonts thanks Am Samstag, den 09.08.2008, 16:44 -0600 schrieb Javier Vasquez: And there's a difference in here, since for i686: # ls /usr/share/grub/ # See 494473 The reason is that the unifont-bin package doestn't provide anymore the file we use to generate the fonts for GRUB. The new upload for lenny will build-depend on the old version, so hopefully all buildds will then use the lenny version to build the packages. OK, however neither of my boxes (amd64 nor i686) have unifont nor unifont-bin installed (they are not dependencies for grub-pc or grub-common). BTW, on the amd64, I don't have /usr/share/unifont path, as a result that I don't have unifont/unifont-bin installed, and I still have for amd64: % ls /usr/share/grub/ ascii.pff unicode.pff Both the i386 and the amd64 packages seem to have the same versions: http://packages.debian.org/sid/grub-pc Package: grub-pc (1.96+20080724-6) http://packages.debian.org/sid/grub-common amd64 1.96+20080724-6 i386 1.96+20080724-6 So the reason might just be that things are done differently for these 2 architectures, and the bug is i386 exclusive, :)... I'm mentioning this out of my ignorance, since I still don't get how things still work for one architecture and not the other, given that both have the same versions, and both are not depending upon unifont* which I don't have installed in any architecture... So my only guess is that they do things very different then, :). So the clue is then to wait for a new update which would fix things then, I guess? Thanks, -- Javier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
