Debian Configuration :: BCM4313 802.11bgn Doesn't Work In Jessie
Mar 27, 2016
Debian configurating, so I try to use wifi adapter, but it doesn't work. I have installed Debian Jessie from netinst CD. To reach perfect speed no options were selected. After I installed xfce4 and xfce4-goodies.I follow some different instructions and no dice. Wicd show me no avalable wifi connections. used Ubuntu 14, Ubuntu 12, etc. and I didn't have any problems with wi-fi connections. Some outputs of comands...
I'm trying out a Jessie install and have noticed VNC doesn't work as well as it used to. I often install a desktop environment on a headless machine, disable *dm, and use vnc4server to create a desktop session if I want to use a GUI. When I try to do the same on Jessie, I run into problems.
Using Gnome, all I get is the generic "Oops something went wrong" error. Looking at .xsession-errors, there are some errors that hint at the problem.
Code: Select allXsession: X session started for ryan at Mon Dec 29 06:07:30 CST 2014 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8
Some possibly related bugs: [URL] ...
The same thing seems to happen with Cinnamon. Since I doubt a fix for the above issue will make it into Jessie, I tried XFCE. However, that doesn't work correctly either. When running XFCE via VNC something is misreporting the version of xrandr as 1.1 instead of 1.4. Since xfsettingsd appears to want version 1.2+, many things are broken.
This post on the Ubuntu forums suggests the issue might be fixed in xfsettingsd version 4.11: [URL] .....
Is there a better way of getting a remote desktop in Jessie that I'm overlooking?
I recently install a Debian 8.0 Jessie on a Laptop Dell latitude E6540 with gnome 3.14+3. But the problem is that it doesn't recongnize my multimedia buttons, I tried some methods but I didn't get results.
On Jessie (cups 1.7.5): I first tried the standard Brother driver from here: [URL] ....It didn't work at all. When I print, Cups tells me that the job has been completed, even though nothing has been done. Sometimes I also got the error "job canceled, filter failed", but I can't reproduce this error...
The foomatic/ptouch driver for the QL550 prints like it did before, but doesn't cut the lables automatically like it used to in wheezy. (I'm using the same printing file/picture as in wheezy and also the same configuration.)
I have an Atheros wireless USB dongle that will connect to my Wifi network just fine in Gnome but in KDE doesn't. I've read through the http://wiki.debian.org/WiFi/HowToUse and have installed all packages and tried all methods noted there but still can't get the wlan0 to work at all in KDE. Is wireless in KDE & Debian Squeeze useless?
So, as per Arch Linux's wiki, I tried to make some optimisations to the intel driver through setting it up in Xorg.conf (or as advised by that wiki article, in '/etc/X11/xorg.conf.d/20-intel.conf' ), but I've ran into trouble enabling DRI3. Here's my current config file:
So far everything works fine, I haven't seen any noticeable tearing, nor did I had any problems with any graphics-intensive programs I run, but there's a slight problem with the DRI3 part as indicated by Xorg's logs:
Code: Select all[ 26.556] (II) Loading sub module "dri2" [ 26.556] (II) LoadModule: "dri2" [ 26.556] (II) Module "dri2" already built-in [ 26.556] (==) Depth 24 pixmap format is 32 bpp [ 26.616] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend [ 26.616] (==) intel(0): Backing store enabled
First of all it still mentions the DRI2 driver, is this supposed to happen, or did something go wrong? Also it complains that it cannot find a file, which I can't figure out which package it belongs to, and taking a quick search around the interwebs hasn't produced anything useful...
The IGP is the CPU, which is actually a i5-4460... which according to Wikipedia it has a HD Graphics 4600 GPU.
My net-book is working properly with Debian squeeze 2-6-32-5-686, only the wlan does not work. After typing lsusb I have got the message: lsusb : Bus 002 Device 002 : ID 160a:3184 VIA Technologies, Inc. VIA VNT-6656 [WiFi 802.11b/g USB Dongle]
So I obtained the driver package : VT6656_Linux_src_v1.19_12_x86. I followed the instructions ( make install... ) - but the result is only a lot of error messages. Mayby I am using the wrong driver package for the squeeze kernel - I don't know.
i created a second instance of postfix.It isn' t the first time that i made this procedure but with debian i had a lot of problem.I think that the problem is chroot configuration of postfix .In the first i had two problem smtp “fatal: unknown service: smtp/tcp” and the second instance was enable to make nslookup of domain.I copied the necessary file in /var/spool/postfix-second-instace and i solved the errors.Now the problem is that there aren't error in log file but connect to xxx.xxx.net[yyy.nn.yyy.yyy]:25: Connection timed out for all connection. and the email are all in defer directory and the second instance doesn' t send emails.
I have Debian Squeeze x64 on ThinkPad T61p with standard 2.6.32-5-amd64 kernel. thinkpad_acpi loaded as module, suspend to RAM works fine from menu in KDE as well as by closing the lid, however machine doesn't appear to react on pressing Fn+F4 which should put it to sleep as well. I've read through thinkpad_acpi documentation and asked Google but so far can't find the solution. Can anyone, point me in correct direction?
last week while I was using ssh to the computer1 inside a NAT as usual, I made another tunnel from the computer1 that I was connecting to, to another computer2 inside that NAT (ssh 192.168.1.130) and after making some changes in computer2 I typed reboot. The computer2 rebooted but the tunnel totally hung and I had to kill it in my laptop. Since that day I haven't been able to ssh to the computer1 as I am used to.
Here is some more information:
debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/une/.ssh/id_rsa
I have recently bought a branded Onda MT835UP USB broadband modem. The hardware comes with its own drivers/GUI for linux, however I'd rather use the Debian-provided NetworkManager+modemmanager packages.
A few details:
- I'm using debian unstable, - latest NetworkManager 0.8.2-3 from experimental - latest modemmanager 0.4+git$foo from testing - latest usb_modeswitch[_data] from experimental
It seems like ifconfig used to show which DNS servers were being addressed, but something has changed, I need to know whether I am referencing what I think I am... I have search this forum, googled, and come up empty... did the metrics go away with 8.2? Was I dreaming at 7.5?
I have a relative fresh install of jessie in which I face a high cpu usage of java (top shows about 165% CPU and 12% MEM). The problem occurs right after booting the computer. These values stay constantly high for days if I leave the box running. This happens even if the computer is just sitting there without doing anything.
I have to kill java to go back to normal. So, when I do a Code: Select allkillall -KILL java the problem goes away. After that it doesn't reappear and I can use all apps installed without a problem.
Currently I am based on openjdk Code: Select allupdate-alternatives --display java java - auto mode link currently points to /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java - priority 1071 slave java.1.gz: /usr/lib/jvm/java-7-openjdk-amd64/jre/man/man1/java.1.gz Current 'best' version is '/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java'.
But I have also tried the SUN version with the same result.
Where to look to find more information on what exactly java app is using so much resources and how I can solve it? I guess I could just put somewhere in rc.d a kill java command and forget about it but I would really like to find out whats going on...
When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.
I am having trouble using touch pad in jessie. My touch pad was ok when it's in wheezy but after i updated to jessie, i can't really get used to it.
I don't know whether i setting it up wrongly, sometimes, my touchpad will keep dragging, without releasing. And if I click the bottom right of the touch pad, it's not right click; instead i have to use two fingers.
etc. So how can i change to back to a more traditional usage? Also, do jessie have a setting like ubuntu saying disable touch pad while typing?
After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
A few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.
umount My passport fdisk -l (to see device name) mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4 dmesg | tail [ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found [ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through
After changing my video cards from gigabyte HD5450 and saphire X550 to two saphire r7 240s one of my debian installs no longer supports rotating the monitors either with 'Monitor Settings' or xrandr. The only difference between these 2 Jessie installs is that one was upgraded and the other one was fresh. The problem is with the upgraded one. On the fresh installed debian I just put the ati proprietary driver so I won't do further testing on it but xrandr was working fine on it before that.
I tried going over the ATIHowTo [URL] .... and everything looks good. Tried purging the non free firmware and reinstalling. I verified the version numbers of libxrandr2 and kernel of both installs. It is either some scrap left over from wheezy or a configuration file I am not aware of.
So what actually happens is xrandr does not say anything, blanks out all windows on the screen with only their background color and title bar showing, changes the lxpanel to its background pattern except for 2 blanked out boxes almost to the right of the screen( I have 10 tray icons there before it blanks), activates the screen I wanted to rotate with the proper rotation. On my main screen I can't click on anything. On the rotated screen I can right click and I get my openbox right click menu like I do on my main monitor before the command but when I try to run something nothing happens. The only way I can get out of this situation is to go to ctrl-alt-f1, log in as root and type 'service lightdm restart'.
Both of these monitors are connected to the primary video card, an ati r7 240 saphire. The main one is on vga and the other one is on DVI. I also have another monitor connected to HDMI but it's not being used. I have yet another monitor connected to the VGA of the secondary GPU I don't think it's a problem is it? I tried not using 'xrandr --setprovideroutputsource 1 0' and it still did the same thing.
I tried just launching openbox with no LXDE and it did the same thing.
Also another strange thing is when I stop the lightdm service and try to 'startx' or 'xinit' my screens go blank; numlock, control-alt-delete and control-alt-f1 do nothing and the only thing I can do is an emergency REISUB. I didn't configure this install to use startx or xinit yet but should it really lock up my system?
On the affected system my script looks like this (I already did this step by step and the 'rotate left' line is causing the problem):
I am using Jessie with XFCE and I tried to write a service which executes a script to change my wallpaper. When I try to start the service with systemctl start wallpaper.service it fails and I get the outout below from systemctl status wallpaper.service
I don't think it to be a permissions issue, they are -rw- r-- r--
This service is called by a timer that goes off daily. Below is wallpaper.service