hamed hosseini:
>
> i have
>
> PCI: 8086:0085 Intel Corporation Centrino Advanced-N 6205
>
> but Squeeze dont support this pci and i want install this driver from here
>
> http://intellinuxwireless.org/?n=Downloads
I have no idea whether your card is actually support
hamed hosseini wrote:
hi
i want install iwlwifi driver in debian 6.0.4, what i am must to do?
i have
PCI: 8086:0085 Intel Corporation Centrino Advanced-N 6205
but Squeeze dont support this pci and i want install this driver from here
http://intellinuxwireless.org/?n=Downloads
*6005 Images
hamed hosseini wrote:
hi
i want install iwlwifi driver in debian 6.0.4, what i am must to do?
i have
PCI: 8086:0085 Intel Corporation Centrino Advanced-N 6205
but Squeeze dont support this pci and i want install this driver from here
http://intellinuxwireless.org/?n=Downloads
*6005 Images
hi
i want install iwlwifi driver in debian 6.0.4, what i am must to do?
i have
PCI: 8086:0085 Intel Corporation Centrino Advanced-N 6205
but Squeeze dont support this pci and i want install this driver from here
http://intellinuxwireless.org/?n=Downloads
*6005 Images – for Intel Centrino
ontinue using
Debian :)
I wish you luck.
Best regards,
Eduardo.
--- Em sáb, 14/4/12, Stephen Powell escreveu:
> De: Stephen Powell
> Assunto: Re: Trouble with Nvidia driver
> Para: debian-user@lists.debian.org
> Data: Sábado, 14 de Abril de 2012, 8:57
> On Sat, 14 Apr 2012 03:27:06 -0
;
>
> - I had memtest86+ run for a long time, and no ram errors were reported.
>
> But Bob's guess that perhaps it is not a driver-related problem
> may be correct. Today I finally decided to try Nvidia installer,
> and had the newest driver installed. And - unfortunatel
;
> - I had memtest86+ run for a long time, and no ram errors were
> reported.
>
> But Bob's guess that perhaps it is not a driver-related problem may be
> correct. Today I finally decided to try Nvidia installer, and had the
> newest driver installed. And - unfort
27;s guess that perhaps it is not a driver-related problem may be correct.
Today I finally decided to try Nvidia installer, and had the newest driver
installed. And - unfortunately - the system continues to freeze. Therefore, the
cause must lie somewhere else (if it is not a bug).
I'll keep
G86[GeForce 8400 GS] (rev a1)
>
> I have a system with the same graphics chip and it is working fine for
> me at 1600x1200 with the default driver. I am a little embarrassed to
> say that after looking at the /var/log/Xorg.0.log file I am not sure
> which driver it is actually using.
Eduardo Bearzoti wrote:
> Video card (lspci output):
> nvidia Corporation G86[GeForce 8400 GS] (rev a1)
I have a system with the same graphics chip and it is working fine for
me at 1600x1200 with the default driver. I am a little embarrassed to
say that after looking at the /var/log/Xorg
ps, I first tried to install the free driver "noveau", as
suggested. The problem remained. Then I followed the steps to
install the non-free Nvidia drivers, using the Debian driver packages
(non-free APT sources). These steps were:
1) install the module kernel, using the packages "mo
On Wed, 11 Apr 2012 17:08:02 -0400, Allington wrote in message
:
> Hello,
>
> I am looking for specific catalyst driver versions for my ATI graphics
> card. Each driver has it's varying performance affect on linux with
> some newer versions actually degrading performance fo
On Wed, 11 Apr 2012 17:08:02 -0400, Allington Pippin wrote:
> Hello,
Hi, please, no html formatted posts, thank :-)
> I am looking for specific catalyst driver versions for my ATI graphics
> card. Each driver has it's varying performance affect on linux with some
> newer
Hello,
I am looking for specific catalyst driver versions for my ATI graphics
card. Each driver has it's varying performance affect on linux with some
newer versions actually degrading performance for my 5970. I would like to
have some options if the one I choose isn't functioning w
specific hard disk layout or hardware but it can also help here.
> The diff is here: http://pastebin.com/L4YXTmJh
>
> I would be very grateful if you'd take a look.
I'll do, but that goes beyond my knowledge :-)
There are many differences between the two boot logs, that'
either, for some reason. The easiest way (which will allow you to read the screen) would be slowing the kernel output messages, I would start from there.I am running the latest packages in both kernel series, and the 3.1series does not have the problem.Are you using any special kernel module that
; shell, but I am unsure how to proceed from here. I guess the problem
>> > could be a faulty driver that I need to disable, but I know of no
>> > (efficient) way to find out which one. Ideally, I would load one
>> > driver at a time, and see when the problem occurs.
>&
shell, but I am unsure how to proceed from here. I guess the problem
> > could be a faulty driver that I need to disable, but I know of no
> > (efficient) way to find out which one. Ideally, I would load one driver
> > at a time, and see when the problem occurs.
> >
>
On Fri, Mar 30, 2012 at 12:08:30AM +0200, Arnt Karlsen wrote:
> On Wed, 28 Mar 2012 11:07:15 +0200, Lars wrote in message
> <20120328090715.ga4...@starfish.lan>:
>
> > Hi all
> >
> > When upgrading kernel series 3.1.0 to series 3.2.0, suddenly my system
> > won't boot. It hangs with the message
to drop into the initramfs debug
> shell, but I am unsure how to proceed from here. I guess the problem
> could be a faulty driver that I need to disable, but I know of no
> (efficient) way to find out which one. Ideally, I would load one
> driver at a time, and see when the problem occu
right?
> I read the manual and found out how to drop into the initramfs debug
> shell, but I am unsure how to proceed from here. I guess the problem
> could be a faulty driver that I need to disable, but I know of no
> (efficient) way to find out which one. Ideally, I would load on
oblem
could be a faulty driver that I need to disable, but I know of no
(efficient) way to find out which one. Ideally, I would load one
driver at a time, and see when the problem occurs.
Can anyone help? Or am I completely off track with this problem?
I am running the latest packages in both k
Hi, ( not sure at all if this is going to help )
Look at this:
{ from:
http://www.kernel.org/doc/Documentation/sound/alsa/ALSAConfiguration.txt
}
{
Module snd-opl3sa2
--
Module for Yamaha OPL3-SA2/SA3 sound cards.
isapnp - ISA PnP detection - 0 = disable, 1 = e
oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
Unfortunately no noticable change has happened.
Soundcard does not produce any sound.
Driver is loaded (with or without the changes to /etc/modprobe.d/aliases).
I checked with alsamixer
Hi, have you been here:
http://www.alsa-project.org/main/index.php/Matrix:Module-opl3-sa2
hth, --Jasper.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f63923d.50
34.511445] snd-opl3sa2-pnpbios 01:01.00: disabled
[ 34.511482] snd-opl3sa2-pnpbios: probe of 01:01.00 failed with error -2
[ 34.515095] snd-opl3sa2-cpnp 01:01.00: activated
It seems that snd-opl3sa2 driver is trying to be used but unsuccesful
soundcard does not work. Is this chip supported under so
On Fri, 10 Feb 2012 22:02:04 +0100, albcares wrote:
> cari corrispondenti,
(...)
This is the English mailing list so better if you write in English to
reach a wider audience. You can also try the Italian user list:
http://lists.debian.org/debian-italian/
Greetings,
--
Camaleón
--
To UNSU
Good time of the day, Stefan.
You worte:
>Do you have any idea where else should I ask my question for higher
>chances of obtaining an answer?
No. May to try to contact manufacturer?
>Simply put, the problem is that my Dell Inspiron N5010 (15R) is
>overheating on Linux with very low CPU usage,
I did not understand exactly for the things You are fighting w/ but if
You are concerned on CPU too hot - I suggest to check if the modules
are loaded (not only installed on Your system) - so it was w/ mine
inspiron until I set it manually to be loaded.
Thank you for your reply,
The drivers are
On 30/01/12 23:26, Ramon Hofer wrote:
> On Mon, 30 Jan 2012 23:05:07 +1100, Scott Ferguson wrote:
>
>> On 30/01/12 22:50, Ramon Hofer wrote:
>>> On Mon, 30 Jan 2012 22:03:24 +1100, Scott Ferguson wrote:
>>>
On 30/01/12 20:48, Ramon Hofer wrote:
> On Mon, 30 Jan 2012 13:03:09 +1100, Scott
wrote:
>>>>
>>>>> On 29/01/12 23:12, Ramon Hofer wrote:
>>>>>> Hi all
>>>>>>
>>>>>> I'm trying to configure a Soundgraph 15c2:0038 display. In Ubuntu
>>>>>> which I had running befo
te:
>>>>> Hi all
>>>>>
>>>>> I'm trying to configure a Soundgraph 15c2:0038 display. In Ubuntu
>>>>> which I had running before on that PC it was very easy to get the
>>>>> display working: Install lcdproc and change the driv
7;m trying to configure a Soundgraph 15c2:0038 display. In Ubuntu
>>>> which I had running before on that PC it was very easy to get the
>>>> display working: Install lcdproc and change the driver in /etc/
>>>> LCDd.conf to imonlcd.
>>>> Unfortunately this
running before on that PC it was very easy to get the display
>>> working: Install lcdproc and change the driver in /etc/ LCDd.conf to
>>> imonlcd.
>>> Unfortunately this isn't possible in squeeze because this driver isn't
>>> available.
>>
&g
t; working: Install lcdproc and change the driver in /etc/ LCDd.conf to
>> imonlcd.
>> Unfortunately this isn't possible in squeeze because this driver isn't
>> available.
>
>
>
>
>> Best regards
>> Ramon
>>
>>
>>
&
t; working: Install lcdproc and change the driver in /etc/ LCDd.conf to
>> imonlcd.
>> Unfortunately this isn't possible in squeeze because this driver isn't
>> available.
>
> # apt-get install lcdproc
> http://packages.debian.org/squeeze/lcdproc pool/main/l/
On 29/01/12 23:12, Ramon Hofer wrote:
> Hi all
>
> I'm trying to configure a Soundgraph 15c2:0038 display.
> In Ubuntu which I had running before on that PC it was very easy to get
> the display working: Install lcdproc and change the driver in /etc/
> LCDd.conf to imonlc
Hi all
I'm trying to configure a Soundgraph 15c2:0038 display.
In Ubuntu which I had running before on that PC it was very easy to get
the display working: Install lcdproc and change the driver in /etc/
LCDd.conf to imonlcd.
Unfortunately this isn't possible in squeeze because this dr
On Sun, 29 Jan 2012 11:58:22 +0200, Andrei Popescu wrote:
> On Du, 29 ian 12, 09:37:36, Ramon Hofer wrote:
>> >
>> > Hmm, you must be running amd64, 3.1.0 is not available on i386. But
>> > anyway, if I understand correctly, it's too much effort to support
>> > more than one kernel version in bac
On Du, 29 ian 12, 09:37:36, Ramon Hofer wrote:
> >
> > Hmm, you must be running amd64, 3.1.0 is not available on i386. But
> > anyway, if I understand correctly, it's too much effort to support more
> > than one kernel version in backports, so it is likely to disappear soon.
> >
> > For nvidia-gl
On Sun, 29 Jan 2012 01:28:19 +0200, Andrei Popescu wrote:
> On Sb, 28 ian 12, 10:20:58, Ramon Hofer wrote:
>>
>> If I get you right I should install linux-image-3.2.0-0.bpo.1-amd64?
>> But there are other packages too like linux-image-amd64 which installs
>> the extra package linux-image-3.1.0-0.
On Sat, 28 Jan 2012 22:16:04 +0100, didier gaumet wrote:
> Le Sat, 28 Jan 2012 10:20:58 + (UTC), Ramon Hofer
> a écrit :
>
> [...]
>> I have added "deb http://backports.debian.org/debian-backports squeeze-
>> backports main" to my /etc/apt/sources.list
>
> "deb http://backports.debian.org/d
On Sb, 28 ian 12, 10:20:58, Ramon Hofer wrote:
>
> If I get you right I should install linux-image-3.2.0-0.bpo.1-amd64?
> But there are other packages too like linux-image-amd64 which installs
> the extra package linux-image-3.1.0-0.bpo.1-amd64. Here are all the
> possibilies I have:
Hmm, you m
Le Sat, 28 Jan 2012 10:20:58 + (UTC),
Ramon Hofer a écrit :
[...]
> I have added "deb http://backports.debian.org/debian-backports
> squeeze- backports main" to my /etc/apt/sources.list
"deb http://backports.debian.org/debian-backports squeeze- backports
main non-free" would be better
[...]
On Fri, 27 Jan 2012 23:00:49 +0200, Andrei Popescu wrote:
> On Vi, 27 ian 12, 20:39:06, Ramon Hofer wrote:
>>
>> The linux-image-amd64 package from squeeze backports installs linux-
>> image-3.1.0-0.bpo.1-amd64.
>> Is 2.6.29 the better choice than 3.1?
>
> I don't know, I can only tell you that
On Fri, 27 Jan 2012 23:14:43 +0200, Andrei Popescu wrote:
> On Vi, 27 ian 12, 23:00:49, Andrei Popescu wrote:
>>
>> I don't know, I can only tell you that 2.6.29 from squeeze-backports
>> doesn't work with nvidia-glx from squeeze, you need both from
>> backports, but in the meantime 2.6.29 got re
On Vi, 27 ian 12, 23:00:49, Andrei Popescu wrote:
>
> I don't know, I can only tell you that 2.6.29 from squeeze-backports
> doesn't work with nvidia-glx from squeeze, you need both from backports,
> but in the meantime 2.6.29 got replaced with 3.2 I didn't get the chance
> to test it (3.1 is n
On Vi, 27 ian 12, 20:39:06, Ramon Hofer wrote:
>
> The linux-image-amd64 package from squeeze backports installs linux-
> image-3.1.0-0.bpo.1-amd64.
> Is 2.6.29 the better choice than 3.1?
I don't know, I can only tell you that 2.6.29 from squeeze-backports
doesn't work with nvidia-glx from sque
x-image-amd64 package from squeeze-backports
>> kernel without changing nvidia-glx (version 195.36.31-6)?
>>
>> Or will I have to compile the nvidia driver?
>
> 2.6.29 would work only with nvidia-glx from backports, didn't get the
> chance to try 3.2 yet.
The li
a-glx (version 195.36.31-6)?
>
> Or will I have to compile the nvidia driver?
2.6.29 would work only with nvidia-glx from backports, didn't get the
chance to try 3.2 yet.
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/
Hi all
I have some problems with the ir-remote of my htpc.
That's why I want to install a newer kernel.
Can I install the linux-image-amd64 package from squeeze-backports kernel
without changing nvidia-glx (version 195.36.31-6)?
Or will I have to compile the nvidia driver?
Best regards
l_laptop
>-> intel_ips (apparently needed by my laptop's "5 Series/3400 Series
>Chipset Thermal Subsystem")
>-> radeon (the free GPU driver; my video card is a HD 5470)
I did not understand exactly for the things You are fighting w/ but if
You are concerned on CPU too h
On 01/22/2012 01:25 PM, M Stefan wrote:
Hello,
I have been struggling with my overheating laptop issue for a while,
and I can't seem to fix it on Debian. My laptop does not overheat on
Windows, so this is not a hardware issue. After checking my driver
support on http://kmuto.jp/debia
Hello,
I have been struggling with my overheating laptop issue for a while,
and I can't seem to fix it on Debian. My laptop does not overheat on
Windows, so this is not a hardware issue. After checking my driver
support on http://kmuto.jp/debian/hcl/index.rhtml, I have noticed
that my
On 16/01/12 21:14, Curt wrote:
> Yes, I verified in the kernel logs (/var/log/kern.log--thanks for that
> tip) : I was using 2.6.32-39 before; after the upgrade I'm using
> 2.6.32-39squeeze1.
According to the changelog, there has indeed been no other changes
between those versions.
I'm *sure* I
On 2012-01-16, Sven Joachim wrote:
>
>> dpkg.log says :
>>
>> upgrade linux-image-2.6.32-5-amd64 2.6.32-39 2.6.32-39squeeze1
>>
>> So there has been no version upgrade, apparently, and therefore the mystery
>> remains as to why the r8169 kernel driver works
ntains the package version corresponding to the kernel.
> dpkg.log says :
>
> upgrade linux-image-2.6.32-5-amd64 2.6.32-39 2.6.32-39squeeze1
>
> So there has been no version upgrade, apparently, and therefore the mystery
> remains as to why the r8169 kernel driver works correctly
s using before the upgrade?
dpkg.log says :
upgrade linux-image-2.6.32-5-amd64 2.6.32-39 2.6.32-39squeeze1
So there has been no version upgrade, apparently, and therefore the mystery
remains as to why the r8169 kernel driver works correctly now when it wasn't
working correct
On 2012-01-16 19:20 +0100, Curt wrote:
> On 2012-01-16, Sven Joachim wrote:
>
>>> I don't know where to look to find out what kernel version I was using
>>> before.
>>
>> /var/log/dpkg.log would be the best place.
>
> I don't have that file on my system.
That's a bit unfortunate. Did you delib
On 2012-01-16, Sven Joachim wrote:
>> I don't know where to look to find out what kernel version I was using
>> before.
>
> /var/log/dpkg.log would be the best place.
I don't have that file on my system.
>> In /var/lib/dpkg/status-old it says:
>>
>> Package: linux-image-2.6-amd64
>
> This is j
On 2012-01-16 18:46 +0100, Curt wrote:
> On 2012-01-16, Sven Joachim wrote:
>>>
>>> I think a (prior) point release upgrade fixed it, not this security upgrade,
>>> but the security upgrade is built on top of the point release.
>>
>> According to debian/changelog, 2.6.32-36 was the last version i
On 2012-01-16, Sven Joachim wrote:
>>
>> I think a (prior) point release upgrade fixed it, not this security upgrade,
>> but the security upgrade is built on top of the point release.
>
> According to debian/changelog, 2.6.32-36 was the last version in which
> major changes were made to r8169, and
On 2012-01-16 17:14 +0100, Jon Dowland wrote:
> On Mon, Jan 16, 2012 at 03:50:39PM +, Curt wrote:
>> Did they fix the r8169, or was it all a bad dream?
>>
>> (I looked at the debian security advisory for the kernel upgrade, dated
>> 15 January, but it says nothing about the matter).
>
> I thin
On Mon, Jan 16, 2012 at 03:50:39PM +, Curt wrote:
> Did they fix the r8169, or was it all a bad dream?
>
> (I looked at the debian security advisory for the kernel upgrade, dated
> 15 January, but it says nothing about the matter).
I think a (prior) point release upgrade fixed it, not this sec
Got a kernel upgrade today from the security repository. I had
previously installed the Realtek proprietary driver (r8168) for my
network card, because the kernel module in squeeze was very problematic
(frequent disconnections, diminished throughput, etc...)
(curty@einstein:~$ uname -a
Linux
I'm using Debian Squeeze (new to linux) with the ATI fglrx-driver installed
along with pm-utils.
Sometimes, when my computer comes back up from suspend mode, it just hangs at
gdm login screen. When I kill the xsession (ctrl + alt + f1), it goes into
console mode. After login to console
brent 802.11N PCI wireless adapter card
>> into a fresh wheezy install. I guess I am confused about which firmware
>> and driver to use.
>>
>> When I do a ifup wlan0 I get the follwing error mesage:
>>
>> phy0 -> rt2800pci_mcu_status: Error - MCU request fail
ent 802.11N PCI wireless adapter card
> into a fresh wheezy install. I guess I am confused about which firmware
> and driver to use.
>
> When I do a ifup wlan0 I get the follwing error mesage:
>
> phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from
>
On 29/12/11 08:57 PM, kei...@strucktower.com wrote:
I am attempting to install a Sabrent 802.11N PCI wireless adapter card
into a fresh wheezy install. I guess I am confused about which firmware
and driver to use.
When I do a ifup wlan0 I get the follwing error mesage:
phy0
I am attempting to install a Sabrent 802.11N PCI wireless adapter card
into a fresh wheezy install. I guess I am confused about which firmware
and driver to use.
When I do a ifup wlan0 I get the follwing error mesage:
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response f
Camaleón writes:
> On Fri, 23 Dec 2011 13:40:03 +0100, Csanyi Pal wrote:
>
>> Camaleón writes:
>
> (...)
>
Searching with Google using keywords 'evdev scroll wheel' gives to me
no answer for this. Thanks!
>>>
>>> Yep, there is not much information on the matter or at least I was
>>> un
On Fri, 23 Dec 2011 13:40:03 +0100, Csanyi Pal wrote:
> Camaleón writes:
(...)
>>> Searching with Google using keywords 'evdev scroll wheel' gives to me
>>> no answer for this. Thanks!
>>
>> Yep, there is not much information on the matter or at least I was
>> unable to find a clear way to conf
On Fri, 16 Dec 2011 20:36:34 +, Andrew Wood wrote:
> Is there a Debian package which provides a driver for eGalax touchscreen
> controllers? The driver is available from the manufactuer here
> http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm
If there is such driver I
On Sat, 17 Dec 2011 01:05:07 -0500, Sushil Mantri wrote:
> I need the driver for broadcom bcm5754.
You ethernet card should be supported by "tg3.ko" module. What's the
ouput of "lspci -nn"?
> I found the source in debian repository, but compiling it has bee
Hi,
I need the driver for broadcom bcm5754. I found the source in debian
repository, but compiling it has been painful. Can i get a debian
package for the driver?
Thanks,
Sushil
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Is there a Debian package which provides a driver for eGalax touchscreen
controllers? The driver is available from the manufactuer here
http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm
but Im concerned that if I install that I will have problems with future
kernel updates. Is
Hi
I've manage to get the proprietary ATI Radeon driver running on this Gigabyte
mobo with the integrated
HD4250, and todays build of wheezy, 12,12,2011
There is still a problem with info boxes when the mouse pointer is hovered over
being distorted
to a trapeziod shape and the settings
[dropping CC to the bug, at least for now]
On Du, 04 dec 11, 23:24:48, lina wrote:
> Sincerely looking for advice about following error:
Hi Lina,
We are glad to help, but it is not easy to do so via e-mail. It is very
important that:
- you are patient :)
- you describe your problem as accuratel
On 2011-12-04, lina wrote:
> Sincerely looking for advice about following error:
>
> more Xorg.0.log | grep WW
>
UUOM
;-)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debi
tching Device section for instance
>> (BusID PCI:0@1:0:1) found
>> [ 16137.250] (WW) fglrx(0): board is an unknown third party board,
>> chipset is supported
>
>
> What Brand and model video card is this? What version of the propriatary
> driver? Does X actually load? c
C ID 1002:675F:: in control file
> [ 16136.200] (WW) fglrx: No matching Device section for instance
> (BusID PCI:0@1:0:1) found
> [ 16137.250] (WW) fglrx(0): board is an unknown third party board,
> chipset is supported
>
What Brand and model video card is this? What version of the propr
Sincerely looking for advice about following error:
more Xorg.0.log | grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 16136.164] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 16136.195] (WW) Falling back to old probe method for fglrx
[ 16136
the latest udev (175-2) removes
> > blacklist.conf, I put it back again.
> > What I find if I don't blacklist nouveau is that the nvidia
> > driver gives an error when starting X.
> >
> > Hugo
> >
>
> When I first installed Squeeze, my nVidia GeForce
at I find if I don't blacklist nouveau is that the nvidia
> driver gives an error when starting X.
>
> Hugo
>
When I first installed Squeeze, my nVidia GeForce 8400 GS worked perfectly with
nouveau. I later switched to nVidia drivers to get the cube going and no
problem th
Ralf Mardorf wrote:
On Fri, 2011-11-25 at 12:16 +, Richard wrote
the FLOSS nouveau driver doesn't work
with old Nvidia cards, even if it's claimed that it should work.
I've come to the conclusion the nouveau driver doesn't work with new nvidia
cards as well, as I
Forwarded Message
From: Richard
Date: Fri, 25 Nov 2011 13:01:45 +
On Fri, 25 Nov 2011 13:58:00 +0100
Ralf Mardorf wrote:
> On Fri, 2011-11-25 at 12:16 +, Richard wrote
> > > the FLOSS nouveau driver doesn't work
> > > with old Nvidia cards, ev
On Fri, 2011-11-25 at 12:16 +, Richard wrote
> > the FLOSS nouveau driver doesn't work
> > with old Nvidia cards, even if it's claimed that it should work.
> I've come to the conclusion the nouveau driver doesn't work with new nvidia
> cards as well, as
On Fri, 2011-11-25 at 12:16 +, Richard wrote
> > the FLOSS nouveau driver doesn't work
> > with old Nvidia cards, even if it's claimed that it should work.
> I've come to the conclusion the nouveau driver doesn't work with new nvidia
> cards as well, as
nux-headers installed?
>
> Half OT:
> Since Nov 5 I kick installing the driver to 3.0.7-rt20. Perhaps I try
> again this weekend. For the kernel-rt there's an additional issue, since
> 3 system calls from the rt patch need an additional patch, an illegal
> patch, that change the li
On Thu, 2011-11-24 at 19:01 +, Richard wrote:
> [snip] It wont build from the /usr/src/nvidia direcory, as it wants
> the kernel config file. [snip]
Please post the output of the log file. Are the linux-headers installed?
Half OT:
Since Nov 5 I kick installing the driver to 3.0.
Hi I'm starting to get more that a bit hacked off.
The gnome shell requires with the onboard radeon graphics card the ATI driver
to run normally,
however the ATI proprietary driver is unstable on kernel 3.0 and 3.1.
So I've gone the Nvidia route, there is only one slot width on the mo
On Lu, 21 nov 11, 12:33:42, Richard wrote:
> Hi,
> I'm pretty sure this isn't a gnome problem as it effects xfce as well.
>
> The display with the fglrx module is unstable when changing desktops it
> breaks up,
> starting and video causes it to crash and you get returned to the login pane
> DKMS
Hi,
I'm pretty sure this isn't a gnome problem as it effects xfce as well.
The display with the fglrx module is unstable when changing desktops it breaks
up,
starting and video causes it to crash and you get returned to the login pane
DKMS will not build the fglrx modules downloaded from the repo
On Wed, 09 Nov 2011 14:45:06 -0600, Kjetil brinchmann Halvorsen wrote:
> Hola!
Hi! :-P
> I have debian Wheezy 64 bit installed, and just installed the new skype
> for 64bit debian.
AFAIK, there is no such a version. Skype only provides 32-bits binaries
for linux.
> It works OK, but it cannot
On a HP Pavilion dv7-4151sg the camera is connected internally to the USB bus.
In this case it is listed in the output of the command
lsusb -v
as "USB Camera" or "Webcam" or "Camera Sensor". I've tested the camera with
guvcview.
--
Best regards,
Jörg-Volker.
--
To UNSUBSCRIBE, email to debian
Hola!
I have debian Wheezy 64 bit installed, and just installed the new
skype for 64bit debian.
It works OK, but it cannot access my camera --- it can receive video,
but not send. Then I tried to start Cheese,
which worked earlier when I had 32 bit linux on this same machine, but
no says it cannot
On Sat 29 Oct 2011 at 11:37:37 +0100, Raf Czlonka wrote:
> Main advantage - you're not keeping your passphrase in clear text on your
> filesystem.
> PSK is precomputed from a passphrase for a specific SSID and passphrase
> cannot be quantified from it.
What difference does that make? A file which
On Fri, Oct 28, 2011 at 06:22:00PM BST, Brian wrote:
> > You don't, for simple setup that is indeed enough.
> > If you have several wireless networks you can keep your interfaces file
> > tidy and organised, not to mention that roaming mode won't work without
> > wpa_supplicant.conf file.
>
> Yes,
his.
> allow-hotplug eth1
> iface eth1 inet dhcp
> # wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
> wpa-debug-level 3
> wpa-driver wext
> wpa-ssid "gojo1985"
> wpa-psk e0609ee9b0f20c1393f815c9c11759f41ca4b3f078146e842ad48ab692097f5d
Ok, but will need altering if roam
On Fri, 28 Oct 2011 14:54:38 -0700
kei...@strucktower.com wrote:
> Thanks Brian-
>
> I installed ifplugd. Still, the wireless does not work if I unplug the
> Ethernet,
assuming you have ifplugd + guessnet
edit * /etc/default/ifplugd *
INTERFACES="eth0 wlan0"
HOTPLUG_INTERFACES=""
#ARGS="-q -f
1401 - 1500 of 4990 matches
Mail list logo
