Re: [arch-general] Weird issue with Google Talk/Hangout plugin
Hmmm just discovered some additional info about this issue. It seems that it only happens when I use the LTS kernel. When I boot into the main linux kernel, the issue mysteriously goes away. Anyone have any ideas what might be happening here? What module in the kernel might have an impact on video? Thanks, DR On 03/06/2013 02:23 PM, David Rosenstrauch wrote: I'm having a weird issue with the Google Talk plugin (https://aur.archlinux.org/packages/google-talkplugin/) distorting all my video images - both the ones of me coming in from my camera, and the ones coming in from others across the Net. See http://www.darose.net/GoogleHangWeirdness.png for an example. Anyone have any idea what's going on here and/or how to fix? This seems to be a recent issue - i.e., probably caused by some package upgrade within the past week or so. I'm running google-talkplugin 3.14.17.0-1 with firefox 19.0-1. But I don't think the issue is caused by the plugin itself. (Or by firefox, since I see the same problem when I use Google chromium browser.) I was running an older version of the plugin - which had been working fine for weeks - when I started experiencing the issue. I upgraded to the latest version in an attempt to work around the problem, but it didn't clear it up. So as I said, I don't think the plugin itself is the cause of the problem - since 2 different versions of the plugin are experiencing the issue, and the issue popped up out of the blue after things had been working fine for quite a while. Any assistance anyone might be able to lend here would be much appreciated! Thanks, DR
Re: [arch-general] Cannot chroot '/bin/bash': No such file or directory
On Thu, Mar 7, 2013 at 10:30 PM, David C. Rankin < drankina...@suddenlinkmail.com> wrote: > On 03/06/2013 08:24 PM, Ross Hamblin wrote: > # cd /mnt > # chroot /mnt > chroot: failed to run command `/bin/bash`: No such file or directory > > For some reason it is like the system has no ability to find anything. > The > install cd is a pre /lib change cd, so that may be the issue. I have > downloaded > the latest install cd and will try again. > > Thank you again Ross. > > Any other suggestions welcomed. Well, that error usually happens, at least to me, when the dynamic loader is unable to solve the shared dependencies of bash, hence the suggestion to use busybox: it is statically linked, so it doesn't suffer of that problem. In my machine the dynamic loader is `/usr/lib/ld-linux.so.2` but the reference to it is `/lib/ld-linux.so.2`. It works because of the `/lib` -> `usr/lib` symbolic link. I'd bet that the cause of your problem is that this link is missing. If If the symbolic link in /lib is correct, it also may happen because the `/etc/ld.so.cache` file is corrupted. You can rebuild it using `chroot /mnt /usr/bin/ldconfig` or maybe `ldconfig -r /mnt` (untested). That can work because `ldconfig` is (obviously) a statically linked program. HTH Rodrigo
Re: [arch-general] Cannot chroot '/bin/bash': No such file or directory
On 03/06/2013 08:24 PM, Ross Hamblin wrote: > It's been a while now but ISTR this message when chroot from 32 bit host > and 64 bit target, or maybe it was vice versa. > > HTH > Ross. It does. It has to be something that simple. However, checking, I have booted with the i686 install medium. The box is an older dell P4, so the i686 is correct and matches the system installed. The install disk /bin/bash date is May 7, 2011. The /bin/bash on /dev/sda6 at /mnt/usr/bin/bash (after mount of the system / at /mnt) is January 26, 2013. Attempting the chroot again on fresh reboot gives the same failure: # cd /mnt # chroot /mnt chroot: failed to run command `/bin/bash`: No such file or directory For some reason it is like the system has no ability to find anything. The install cd is a pre /lib change cd, so that may be the issue. I have downloaded the latest install cd and will try again. Thank you again Ross. Any other suggestions welcomed. -- David C. Rankin, J.D.,P.E.
[arch-general] nouveau or kernel which one ?
Hi for the last 3 kernels i have been getting errors and hangs that ultimately end in a completely frozen system this is the error that appears in the in the log Mar 07 11:00:43 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 4 Get 0xfc Put 0xf8 IbGet 0x01fe IbPut 0x01ff State 0xc0040022 (err: MEM_FAULT) Push 0x00400040 Mar 07 11:45:27 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x002002893c Put 0x0020029774 IbGet 0x035a IbPut 0x035b State 0x80004861 (err: INVALID_CMD) Push 0x00400040 Mar 07 11:54:36 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 4 Get 0xfc Put 0xf8 IbGet 0x0237 IbPut 0x0238 State 0xc0040022 (err: MEM_FAULT) Push 0x00400040 Mar 07 12:00:14 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x002002bd20 Put 0x002002bd80 IbGet 0x02ff IbPut 0x0300 State 0xc020 (err: MEM_FAULT) Push 0x00400040 Mar 07 12:16:33 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x002002d538 Put 0x002002d554 IbGet 0x0243 IbPut 0x0244 State 0x8314 (err: INVALID_CMD) Push 0x00400040 Mar 07 12:21:09 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020035140 Put 0x002003af14 IbGet 0x0362 IbPut 0x0365 State 0x80004861 (err: INVALID_CMD) Push 0x00400040 Mar 07 12:25:06 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020030ad4 Put 0x0020030b8c IbGet 0x01bc IbPut 0x01bf State 0xc020 (err: MEM_FAULT) Push 0x00400040 Mar 07 12:25:42 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020037348 Put 0x0020037e78 IbGet 0x035a IbPut 0x035b State 0xc0004861 (err: MEM_FAULT) Push 0x00400040 Mar 07 13:02:36 7-of-9 kernel: delay: estimated 192, actual 0 Mar 07 13:04:22 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 4 Get 0x00200d4984 Put 0x00200d4d1c IbGet 0x0250 IbPut 0x0251 State 0x8000745c (err: INVALID_CMD) Push 0x00400040 Mar 07 13:04:22 7-of-9 kernel: nouveau E[ PGRAPH][:01:00.0] DATA_ERROR INVALID_BITFIELD Mar 07 13:04:22 7-of-9 kernel: nouveau [ PGRAPH][:01:00.0] DATA_ERROR Mar 07 13:04:22 7-of-9 kernel: nouveau E[ PGRAPH][:01:00.0] ch 4 [0x003f96e000] subc 3 class 0x8597 mthd 0x1458 data 0x Mar 07 13:04:22 7-of-9 kernel: nouveau E[ PFB][:01:00.0] trapped read at 0x00 on channel 0x0003f96e PFIFO/PFIFO_READ/PUSHBUF reason: PT_NOT_PRESENT Mar 07 13:11:59 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] DMA_PUSHER - Ch 2 Get 0x0020008fe4 Put 0x0020008ff8 IbGet 0x0327 IbPut 0x0329 State 0x8064 (err: INVALID_CMD) Push 0x00400040 Mar 07 13:11:59 7-of-9 kernel: nouveau [ PFIFO][:01:00.0] CACHE_ERROR - Ch 2/0 Mthd 0x0060 Data 0x at present running KDE 4.10.1 kernel 3.7.10-1 4Gb ram currently running with 2.56Gib free memory video card is a GeForce GT220 @1Gb memory. Twin monitors USB external sound card (onboard card is pants) New install middle of January Thanks Pete . -- Linux 7-of-9 3.7.10-1-ARCH #1 SMP PREEMPT Thu Feb 28 09:50:17 CET 2013 x86_64 GNU/Linux
Re: [arch-general] Cannot chroot '/bin/bash': No such file or directory
On Thu, Mar 7, 2013 at 4:02 AM, Sean Greenslade wrote: > On Wed, Mar 6, 2013 at 8:32 PM, David C. Rankin > wrote: > > Guys, > > > > Attempting to fix the test box that updating left unable to boot, I > cannot > > chroot to fix the system. I've booted from the install medium and done > the > > normal mount of the existing system under /mnt: > > > > mount /dev/sda6 /mnt > > mount /dev/sda5 /mnt/home > > mount /dev/sda8 /mnt/boot > > mount -o bind /dev /mnt/dev > > mount -t proc none /mnt/proc > > mount -t sysfs none /mnt/sys > > > > All files appear in their proper place under /mnt. However, attempting > to > > create the chroot fails: > > > > cd /mnt > > chroot /mnt /bin/bash > > > > chroot: failed to run command '/bin/bash': No such file or directory > > > > /bin/bash is in the new location /usr/bin/bash (moved from /bin/bash > by the > > update) with with a proper symlink in /mnt/bin/bash pointing to > ../usr/bin/bash > > > > This if the first time I've ever had difficulty chrooting a system. I > suspect > > that this is caused by the last update that pulled in systemd which left > the > > system unbootable. Anyone know what could be causing the chroot failure? > I've > > tried explicitly pointing the chroot to ./usr/bin/bash, etc... and tried > it > > without any executable specified. Regardless, I get the same "No such > file or > > directory". > > > > Thanks in advance for any help or link you can provide. > > > > -- > > David C. Rankin, J.D.,P.E. > > I had this issue once. It was on a system that had corruption on its > root drive due to power failures. The error can be very misleading; in > my case the file existed and yet the chroot still failed. I ended up > wiping that system, but the most likely conclusion I could come to was > that some very important system .so's got corrupted. If you have > busybox installed, try chrooting into busybox's sh. If that works and > the bash executable really does exist despite that error, I'm afraid > you may have a quite the thrashed system on your hands. > And if you don't have busybox installed, you can copy the `busybox` binary to, say, /mnt/tmp and then `chroot mnt /tmp/busybox`. Rodrigo.
Re: [arch-general] Forced to run fsck manually on unattended system
On Thu, Mar 7, 2013 at 6:06 AM, edd_smith wrote: > For what it's worth I'm using SSDs and I've found that a journalled file > system (ext3/4) struggled a bit more with sudden power outages, but this is > all emperical. A filesystem without journalling just doesn't know anything went wrong, and silently loses data.
Re: [arch-general] Forced to run fsck manually on unattended system
I have found a way around my problem of freezing on startup. The startup script is called from /etc/rc.d/functions You simply find the section where the fsck command is called and edit the flags to remove -a and add -y. I understand that my data may end up getting a little frazzled, but hopefully turning off disk caching with hdparm (this is a low performance system anyway) should sort things out. For what it's worth I'm using SSDs and I've found that a journalled file system (ext3/4) struggled a bit more with sudden power outages, but this is all emperical. Many thanks for all your suggestions. -- View this message in context: http://archlinux.2023198.n4.nabble.com/Forced-to-run-fsck-manually-on-unattended-system-tp4684861p4684978.html Sent from the arch general mailing list archive at Nabble.com.
Re: [arch-general] Broadcom B43 problems
Hi I have the dame wireless chipset and it "works" on my Archlinux setup (64bits, GNOME, b43-firmware and network manager). I sa y "works" because i can use the wireless connection but the connection is slow. What does dmesg says after a connection try? Cordialement, Julien Pecqueur -- http://julienpecqueur.net Le 6 mars 2013 22:59, "Magnus Therning" a écrit : > I have seen some indications that my Broadcom B43 *ought* to work with > the kernel's b43 driver, but I've never managed to get it working on > my own. I'd love to be able to switch away from the broadcom-wl > package is possible. > > Using a kernel from a few days ago, 3.7.9 and the b43-firmware > package from AUR I only get as far as connecting to my router (at > least that's what NetworkManager says), but then I can't actually > connect to any site. If I then bring down the network and then bring > it back up again the connection to the router will fail > (NetworkManager keeps asking for the password). > > Any suggestions on what might be causing this, and what I should try > next? > > /M > > % lspci -nn|grep Broadcom > 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g > LP-PHY [14e4:4315] (rev 01) > > Wireless network uses WPA2 > > -- > Magnus Therning OpenPGP: 0xAB4DFBA4 > email: mag...@therning.org jabber: mag...@therning.org > twitter: magthe http://therning.org/magnus > > I invented the term Object-Oriented, and I can tell you I did not have > C++ in mind. > -- Alan Kay >
