Re: Nvidia Geforce GT 520

[Umarzuki Mochlis]

2012/1/25 Arno - 
>
> I wish to install Debian 6.0.3. (64 bit) on my PC. I have a Nvidia Geforce GT 
> 520, which is not on the Debian Hardware compatibility list. I'm a new user 
> and not familiar with Debian. I would be very grateful if you could give me 
> clear, step by step instructions. The messages published about this topic are 
> not understandable for a noviced like me. Sorry.
>
> Thank you so much!
>
try sgfxi
after stopping gdm3 with below command as root

/etc/init.d/gdm3 stop

while connecting to the internet, from terminal, use below commands:

cd /usr/local/bin
wget -Nc smxi.org/sgfxi
chmod +x sgfxi
sgfxi


--
Regards,

Umarzuki Mochlis
http://debmal.my


--
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/CAHW9mbxapQC1hpq39MyRufRjaVrnTQ=gw=p3uclj9bzvlwv...@mail.gmail.com

Wheezy. Weekly build 23-Jan-2012. "No kernel modules were found" during install.

[Leonid Korostyshevski]

Hello, list!

Trying to install weekly build subj from USB stick. An image in use is
'debian-testing-i386-DVD-1.iso'. Boot and installer's start are fine but
next step shows a message: "No kernel modules were found... mismatch kernel
version... etc.". Have no possibility to install from netinstall daily
build. Please, advise what should be done as a workaround? Or, probably,
another solution?

Appreciated,
LK

Re: icedove 8.0-2 not opening http links in browser

[Alberto Fuentes]

On 24/01/12 22:01, MRH wrote:

And I just checked that in Thunderbird 9 at work - the same (attachment
tab is empty), but the links work there.


So its not related... good to know :)
ill keep looking for a solution and post it when find it

greets!
aL


--
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/4f1fba6d.8020...@qindel.com

Re: ALSA instead of pulseaudio on new sid

[Lorenzo Sutton]

On 25/01/2012 03:07, Scott Ferguson wrote:

On 25/01/12 12:37, John Hasler wrote:

Scott writes:

You'll discover the minor pain of learning Pulse is a very profitable
investment.


For those of us who are not audiophiles and have very simple audio
needs, what does Pulse add?


Hi John, a common misconception.

Jackd is for audiophiles (compromising audiophiles)[*1].


...



[*1] Audiophiles use electrostatic speakers, Class A amplifiers, and
shun the crudities of "digital" sound (apparently).


They also sleep with a 78 rpm turntable under their pillow, include 
crackle and pops when they speak and keep a constant background noise 
source switched on. Not to mention the magnetic tape baths they take 
periodically. :)



--
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/4f1fc63e.6050...@gmail.com

Re: Free software

[Lorenzo Sutton]

On 25/01/2012 10:42, Stayvoid wrote:

Hello!

I want to install Debian.
Does it contain any non-free software? How to check it?

Is there a way to use Debian without non-free software?



http://people.debian.org/~bap/dfsg-faq.html




King regards.





--
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/4f1fd048.1030...@gmail.com

Re: ALSA instead of pulseaudio on new sid - now [OT] serious audiophiles

[Scott Ferguson]

On 25/01/12 20:07, Lorenzo Sutton wrote:
> On 25/01/2012 03:07, Scott Ferguson wrote:
>> On 25/01/12 12:37, John Hasler wrote:
>>> Scott writes:



> 
>> 
>> [*1] Audiophiles use electrostatic speakers, Class A amplifiers,
>> and shun the crudities of "digital" sound (apparently).
> 
> They also sleep with a 78 rpm turntable

Belt driven of course, and the needle has to have been handmade by
Tasmanian twin brothers - who committed suicide with their wives. (I
swear I'm not making that up - the Garrott brothers).

> under their pillow, include crackle and pops when they speak and keep
> a constant background noise source switched on.

But it must be a white noise source - none of that cheap pink rubbish.

> Not to mention the magnetic tape baths they take periodically. :)
> 
> 

I know someone like that he washes his records in the sink, can't be
trusted near milk crates (stores LPs in them) and has a specially
designed lounge room for music. Cork tiled ceiling, heavy carpets,
padded chairs, felt curtains, and the sound equipment sits on concrete
blocks (poured on-site), and no other furniture or fitting in there. In
Summer you can hear mosquitos and flies being killed by the speakers -
in Winter there's no need for a fire, the amp keeps everything toasty.
Completely over-the-top (*cough*Rick*cough*)... but beautiful, smooth,
rich sound.

-- 
Iceweasel/Firefox extensions for finding answers to Debian questions:-
https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/

NOTE: new update available for Debian Buttons
(New button for querying Debian Developer Package):-
https://addons.mozilla.org/en-US/firefox/addon/debian-buttons/


-- 
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/4f1fd115.9010...@gmail.com

Re: Nvidia Geforce GT 520

[richard]

On Wed, 25 Jan 2012 08:41:21 +0100
Arno -  wrote:

> I wish to install Debian 6.0.3. (64 bit) on my PC. I have a Nvidia Geforce
> GT 520, which is not on the Debian Hardware compatibility list. I'm a new
> user and not familiar with Debian. I would be very grateful if you could
> give me clear, step by step instructions. The messages published about this
> topic are not understandable for a noviced like me. Sorry.
> 
>
 Thank you so much!


As I said Arno the Nvidia version 290 IS the correct driver for the  GT520
I USE ONE.

You can either do several ways, from your earlier post you have download the 
proprietary Nvidia driver.

this is easy to install BUT you will need to install it each time the kernel is
upgraded.
AND it will not install with the Xserver running, you have to turn gdm and X off

If you want to install it the debian way read this:-
http://wiki.debian.org/NvidiaGraphicsDrivers

If you want to install the nvidia way  read this lifted from:-
Debian - NVIDIA drivers quick and easy tutorial about how to install NVIDIA 
drivers as simply as possible.

Prerequisites:

As a starting point, download the latest stable drivers.

Then you’ll need to install a few packages :

$ sudo apt-get install build-essential linux-headers-$(uname -r)
Debian Sarge users have to replace linux-headers with kernel-headers.


Installation:

First you’ll need to kill the X server. You can do that by switching to console
#3 : press CTRL-ALT-F3 simultaneously.

Once there, log in with your username and password.

Stop the graphical login manager :

$ sudo /etc/init.d/gdm3 stop
Then install the drivers :
$  cd 
$ sudo sh Nvidia-linux-x86_64-209.10.run
and follow the installation process.
:-

But remember each time the kernel is upgraded to do the same again.

Is that plain enough ???

-- 
Best wishes / 73
Richard Bown

e-mail: rich...@g8jvm.com   or   richard.b...@blueyonder.co.uk

nil carborundum a illegitemis
##
Ham Call G8JVM . OS Fedora FC16 x86_64 on a Dell Insiron N5030 laptop
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs mins )
QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W & 3 cms:5W
##
 


--
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/20120125095321.2bab8...@lappy.g8jvm.com

Blank screen at boot with kernel 3.1

[Rémi Moyen]

Hello,

I'm installing Debian on a new computer and although the install of
stable version works fine, after upgrade to testing I am unable to
boot on the 3.1 kernel. There is no X on the machine (for the moment)
and I get a blank screen a few seconds after boot. I suspect a problem
with the graphics card (NVidia GTX 570) and nouveau, but couldn't find
a workaround.

Here are the details. Sorry, that's a bit long, but I wanted to put
all I can here. Also, note that I'm not in front of the machine right
now, so I'm typing this from memory and some notes, and cannot test
stuff until tonight...

I've bought myself a new computer and want to install a Debian/testing
on it. I burnt a CD with the latest stable to start with (I was not
quite sure how to get a testing CD and anyway I've had years of
upgrading various Debian so I was quite confident the stable ->
testing upgrade would work fine). The installation with the CD works
perfectly, I can use the graphic installer and I install the
"standard" system (no graphical environment at that point).

After reboot, I get a working Debian/stable with kernel 2.6.32 (I
think). First thing I do is to change sources.list to add the contrib
& non-free repos as well as the testing ones (main, contrib &
non-free). Update, full-upgrade: almost everything seems to be
updated, as expected, including installing a kernel 3.1.0. No error
messages, except one warning when the kernel is upgraded about
potentially missing firmwares for my network card (realtek) and
nouveau. For nouveau, these are the same warnings as described here,
for example: http://forums.linuxmint.com/viewtopic.php?f=185&t=83587.

Now, this is only a warning, but after this, whenever an upgrade step
rebuilds the initrd, I get warnings about missing firmware for
realtek. Only for realtek, nothing about nouveau here. So I install
the firmware-realtek package, and lo and behold, the warning disappear
when initrd is rebuilt. Because I never get warnings about nouveau
while generating initrd, I don't know whether these missing firmware I
was warned about are really missing...

Are these firmwares really useful? I couldn't find anyone on the web
saying so, all I find are messages where people ask about it. They
don't seem to be anywhere in any Debian package (even in non-free).

OK, so now I get what I think should be a working up-to-date testing
system. Rebooting on the 2.6.32 kernel works again perfectly. But
rebooting on the 3.1 kernel starts to boot (it prints at least the
"waiting for udev to be populated" message) and then all I get is a
blank screen. Some messages get displayed before, but so fast that I
have no hope to even catch a glimpse of a word. The screen flickers
when it becomes black, at about the time where in the 2.6 kernel the
screen resolution changes, so I guess this is the step that fails.
With the blank screen, I can't do anything. Keyboard seems dead (at
least "Caps Lock" doesn't respond, although "Num Lock" does). The
machine is still alive and can be logged-on remotely, but that's all.
I didn't see anything strange in syslog or dmesg, but I might have
missed something.

I stress here the fact that I am only working in console. No X server
has been installed yet, and certainly no display manager (so when
booting, it stays in console). I will install an X server later but I
feel that I should fix problems one at a time... (actually, I did a
first install with the graphic environment as well and things didn't
work better, so I started again a fresh install without it, to better
isolate problems)

>From searching on the web, it looks like a KMS or nouveau problem. I
have tried blacklisting nouveau (by adding a custom file containing
"blacklist nouveau" in /etc/modprobe.d), but this doesn't change
anything. I tried also installing the nvidia driver (since I want to
install it ultimately anyway), by installing the nvidia-glx package.
It installs OK, build the 3.1 DKMS kernel module without errors, but
still get the same error when booting. It does install an X server at
that stage (which is expected) but this server is normally not started
at boot, so I'm still only dealing with console. I also tried to put
"nomodeline" in the boot parameters (/etc/default/grub, then
update-grub) but again, this doesn't change anything.

So I'm stuck with a working 2.6.32 kernel, and a broken (and unusable,
at that point) 3.1 kernel.

As a last resort, I wanted to try and install the nvidia module on the
2.6 kernel (thinking that I could stay with that one for some time,
assuming later versions of the 3.1 kernel will work better that the
current one...), but trying to do so requires the kernel headers,
which in turns requires an older version of gcc, and one thing causing
another, aptitude would basically downgrade most of my system back to
stable, which is not what I want (I mean, if I wanted a stable system,
I would have stuck with it from the start).

So, does anyone have an idea of what is causing the problem,

Re: Blank screen at boot with kernel 3.1

[richard]

On Wed, 25 Jan 2012 09:56:15 +
Rémi Moyen  wrote:

> Hello,
> 
> I'm installing Debian on a new computer and although the install of
> stable version works fine, after upgrade to testing I am unable to
> boot on the 3.1 kernel. There is no X on the machine (for the moment)
> and I get a blank screen a few seconds after boot. I suspect a problem
> with the graphics card (NVidia GTX 570) and nouveau, but couldn't find
> a workaround.
> 
> Here are the details. Sorry, that's a bit long, but I wanted to put
> all I can here. Also, note that I'm not in front of the machine right
> now, so I'm typing this from memory and some notes, and cannot test
> stuff until tonight...
> 
> I've bought myself a new computer and want to install a Debian/testing
> on it. I burnt a CD with the latest stable to start with (I was not
> quite sure how to get a testing CD and anyway I've had years of
> upgrading various Debian so I was quite confident the stable ->
> testing upgrade would work fine). The installation with the CD works
> perfectly, I can use the graphic installer and I install the
> "standard" system (no graphical environment at that point).
> 
> After reboot, I get a working Debian/stable with kernel 2.6.32 (I
> think). First thing I do is to change sources.list to add the contrib
> & non-free repos as well as the testing ones (main, contrib &
> non-free). Update, full-upgrade: almost everything seems to be
> updated, as expected, including installing a kernel 3.1.0. No error
> messages, except one warning when the kernel is upgraded about
> potentially missing firmwares for my network card (realtek) and
> nouveau. For nouveau, these are the same warnings as described here,
> for example: http://forums.linuxmint.com/viewtopic.php?f=185&t=83587.
> 
> Now, this is only a warning, but after this, whenever an upgrade step
> rebuilds the initrd, I get warnings about missing firmware for
> realtek. Only for realtek, nothing about nouveau here. So I install
> the firmware-realtek package, and lo and behold, the warning disappear
> when initrd is rebuilt. Because I never get warnings about nouveau
> while generating initrd, I don't know whether these missing firmware I
> was warned about are really missing...
> 
> Are these firmwares really useful? I couldn't find anyone on the web
> saying so, all I find are messages where people ask about it. They
> don't seem to be anywhere in any Debian package (even in non-free).
> 
> OK, so now I get what I think should be a working up-to-date testing
> system. Rebooting on the 2.6.32 kernel works again perfectly. But
> rebooting on the 3.1 kernel starts to boot (it prints at least the
> "waiting for udev to be populated" message) and then all I get is a
> blank screen. Some messages get displayed before, but so fast that I
> have no hope to even catch a glimpse of a word. The screen flickers
> when it becomes black, at about the time where in the 2.6 kernel the
> screen resolution changes, so I guess this is the step that fails.
> With the blank screen, I can't do anything. Keyboard seems dead (at
> least "Caps Lock" doesn't respond, although "Num Lock" does). The
> machine is still alive and can be logged-on remotely, but that's all.
> I didn't see anything strange in syslog or dmesg, but I might have
> missed something.
> 
> I stress here the fact that I am only working in console. No X server
> has been installed yet, and certainly no display manager (so when
> booting, it stays in console). I will install an X server later but I
> feel that I should fix problems one at a time... (actually, I did a
> first install with the graphic environment as well and things didn't
> work better, so I started again a fresh install without it, to better
> isolate problems)
> 
> >From searching on the web, it looks like a KMS or nouveau problem. I
> have tried blacklisting nouveau (by adding a custom file containing
> "blacklist nouveau" in /etc/modprobe.d), but this doesn't change
> anything. I tried also installing the nvidia driver (since I want to
> install it ultimately anyway), by installing the nvidia-glx package.
> It installs OK, build the 3.1 DKMS kernel module without errors, but
> still get the same error when booting. It does install an X server at
> that stage (which is expected) but this server is normally not started
> at boot, so I'm still only dealing with console. I also tried to put
> "nomodeline" in the boot parameters (/etc/default/grub, then
> update-grub) but again, this doesn't change anything.
> 
> So I'm stuck with a working 2.6.32 kernel, and a broken (and unusable,
> at that point) 3.1 kernel.
> 
> As a last resort, I wanted to try and install the nvidia module on the
> 2.6 kernel (thinking that I could stay with that one for some time,
> assuming later versions of the 3.1 kernel will work better that the
> current one...), but trying to do so requires the kernel headers,
> which in turns requires an older version of gcc, and one thing causing
> another, aptitude

Re: Nvidia Geforce GT 520

[Alberto Luaces]

richard writes:

> If you want to install it the debian way read this:-
> http://wiki.debian.org/NvidiaGraphicsDrivers
>
> If you want to install the nvidia way  read this lifted from:-
> Debian - NVIDIA drivers quick and easy tutorial about how to install NVIDIA 
> drivers as simply as possible.

Hi Richard,

I don't know why they still call this the 'Debian way'. Nowadays you can
just use

apt-get install nvidia-glx

as root, and that's it. No need to compile kernel modules or having to
update them every kernel update, the package already uses DKMS for this.

-- 
Alberto


-- 
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/87fwf4gjye@eps142.cdf.udc.es

Re: Free software

[Stayvoid]

> The main branch is only free software...
Are you sure about that?
How to check that?
Where can I look through the package's license?


King regards.


-- 
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/cak5fs_hx3guksoqkqbn-3d+qqezce6wt8+-3iftnrvuunwl...@mail.gmail.com

Re: Free software

[Julien Claassen]

Hi!
  Yes you can exclude all non-free software. If you install Debian, I don't 
know, where it will be, but I'm very sure, that excluding non-free software is 
the default. Later on you can decide, what you want. You can always edit

/etc/apt/sources/list
  There you might see lines - roughly - like this:
deb http://ftp.de.debian.org/debian squeeze main contrib non-free
  It was my personal choice to also add the "contrib" and "non-free" branches. 
The main branch is only free software, same goes- I think - for the contrib 
branch.

  Kind regards
 Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

==  Find my music at  ==
http://juliencoder.de/nama/music.html
.
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)


--
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/alpine.deb.2.00.1201251051110.19...@flower.world.net

Re: Blank screen at boot with kernel 3.1

[Alberto Luaces]

Rémi Moyen writes:

> OK, so now I get what I think should be a working up-to-date testing
> system. Rebooting on the 2.6.32 kernel works again perfectly. But
> rebooting on the 3.1 kernel starts to boot (it prints at least the
> "waiting for udev to be populated" message) and then all I get is a
> blank screen. Some messages get displayed before, but so fast that I
> have no hope to even catch a glimpse of a word. The screen flickers
> when it becomes black, at about the time where in the 2.6 kernel the
> screen resolution changes, so I guess this is the step that fails.
> With the blank screen, I can't do anything. Keyboard seems dead (at
> least "Caps Lock" doesn't respond, although "Num Lock" does). The
> machine is still alive and can be logged-on remotely, but that's all.
> I didn't see anything strange in syslog or dmesg, but I might have
> missed something.
>
> I stress here the fact that I am only working in console. No X server
> has been installed yet, and certainly no display manager (so when
> booting, it stays in console). I will install an X server later but I
> feel that I should fix problems one at a time... (actually, I did a
> first install with the graphic environment as well and things didn't
> work better, so I started again a fresh install without it, to better
> isolate problems)

If you are not running or have X installed, you can uninstall nouveau
and nvidia-glx packages.

Since you can access the machine from a network connection, watch for
errors in the logs with the «dmesg» command.

-- 
Alberto


-- 
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/87bopsgjr3@eps142.cdf.udc.es

Kernel Compiling from scratch

[Syed Hasan Atizaz]

Hello
I like to know where can i get the information in detail for compiling
kernel, loading modules and installing programs from scratch. i never
did it before. I installed virtual box recently and looking to play
with it.
Thank you
Syed Hasan Atizaz


-- 
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/CANPPWQRv4d34tW7bkg-OhAEukp_gZ3cs8btC_ktz=kfenjg...@mail.gmail.com

Re: Nvidia Geforce GT 520

[richard]

On Wed, 25 Jan 2012 11:22:49 +0100
Alberto Luaces  wrote:

> richard writes:
> 
> > If you want to install it the debian way read this:-
> > http://wiki.debian.org/NvidiaGraphicsDrivers
> >
> > If you want to install the nvidia way  read this lifted from:-
> > Debian - NVIDIA drivers quick and easy tutorial about how to install NVIDIA
> > drivers as simply as possible.
> 
> Hi Richard,
> 
> I don't know why they still call this the 'Debian way'. Nowadays you can
> just use
> 
> apt-get install nvidia-glx
> 
> as root, and that's it. No need to compile kernel modules or having to
> update them every kernel update, the package already uses DKMS for this.
> 

I posted that  as Arno has little understanding of how things work, It woolly
but understandable for  newbies, I hope.
He has mailed me direct saying he does not understand the postings.
I'm also guess he has some old books probably dating from Debian 5 :)

-- 
Best wishes / 73
Richard Bown

e-mail: rich...@g8jvm.com   or   richard.b...@blueyonder.co.uk

nil carborundum a illegitemis
##
Ham Call G8JVM . OS Fedora FC16 x86_64 on a Dell Insiron N5030 laptop
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs mins )
QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W & 3 cms:5W
##
 


-- 
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/20120125104354.55887...@lappy.g8jvm.com

Re: Free software

[Julien Claassen]

Hello!
  Yes I am sure about the main branch. One of the main ideas of Debian was to 
be a distribution of free-software only. I don't know, if they already 
introduced the non-free branch with the first version, but that's precisely, 
why it is there as a seperate branch, to make sure, that people, like 
yourself, can choose.
  I think you can find interfaces on debian.org to search the package database 
and info about specific packages. I have rarely used those though, since I 
could always use my own system for all the research necessary.

  Kind regards
  Julien

=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!

==  Find my music at  ==
http://juliencoder.de/nama/music.html
.
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)


--
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/alpine.deb.2.00.1201251125140.19...@flower.world.net

Re: Free software

[Andreas Rönnquist]

On Wed, 25 Jan 2012 13:24:03 +0300
Stayvoid  wrote:

> > The main branch is only free software...
> Are you sure about that?
> How to check that?
> Where can I look through the package's license?
> 

Its policy [1] - 
"Every package in main must comply with the DFSG (Debian Free Software
Guidelines). "
See [2].
If a package not complying to this is found in main, It should be
reported as a bug.

best regards
/Andreas

[1] - http://www.debian.org/doc/debian-policy/ch-archive.html#s-main
[2] - http://www.debian.org/social_contract#guidelines


signature.asc
Description: PGP signature

Re: Free software

[Scott Ferguson]

On 25/01/12 21:24, Stayvoid wrote:
>> The main branch is only free software...

There are three repositories - you need "main" to build an OS
Main is all libre
Additionally you may select "contrib" and "non-free".


> Are you sure about that?

Debian has a legal test:-
http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines#debian-legal_tests_for_DFSG_compliance

Please read the Debian Social Contract on the main site:-
debian.org

Where a lot people have spent a lot of time preparing answers to your
questions :-)

You can read more about Debian's Free Software policies:-
http://www.spi-inc.org/

> How to check that?

Use a script:-
http://romanrm.ru/en/librian

> Where can I look through the package's license?

Select the package here:-
http://packages.debian.org/search?

By clicking on the version of the package you're interested in you'll be
taken to a page which will have a link on the right-hand side for the
license information.

> 
> 
> King regards.
> 
> 
By default the installer selects the libre (main) repository - if you so
desire you may select additional repositories.

Debian is about choices.

Cheers

-- 
Iceweasel/Firefox extensions for finding answers to Debian questions:-
https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/

NOTE: new update available for Debian Buttons
(New button for querying Debian Developer Package):-
https://addons.mozilla.org/en-US/firefox/addon/debian-buttons/


-- 
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/4f1fde49.7060...@gmail.com

Re: Kernel Compiling from scratch

[Jon Dowland]

On 25/01/12 10:40, Syed Hasan Atizaz wrote:

I like to know where can i get the information in detail for compiling
kernel, loading modules and installing programs from scratch. i never
did it before. I installed virtual box recently and looking to play
with it.


Download the kernel sources from http://kernel.org/

Ensure you have the "build-essential" package installed.

unpack, CD into the directory and type 'make help' for more information.

Tip: copy your running kernel's config to save time reconfiguring:

(from within the unpacked source directory)

cp /boot/$(uname -r)/config .config

Building takes a long time, a powerful machine and using multiple 
threads recommended.



--
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/4f1fe497.5000...@debian.org

Re: System hangs due to NFS share

[Chris Davies]

Sylvain  wrote:
> I have an NFS share mounted on my Debian testing computer with default
> mount options. It works fine but as soon as my computer loses network
> access or the NAS is disconnected or shut down, the system becomes
> unstable:

I would recommend a number of things to review.

1. If the contents of the NFS share are fundamental to your system
working, you need to consider whether you can either improve the network
access or change the sharing mechanism to something that's less reliant
on the network. (rsync local copies, etc.) Basically, there's no point
trying to rely on something that's unreliable.

2. If you have something in your PATH, such as /usr/local/bin, on the
NFS share, consider whether you can have the PATH referencing only local
directories, but within one of those local directories use a collection
of symlinks to point to the corresponding programs on the NFS share.

i.e., if /mnt/share/bin is (part of) the NFS share, and you have that
directory in your PATH, change it so that your PATH no longer references
the directory but instead references, say, /usr/local/bin. And then
within /usr/local/bin run this command (once, or each time you mount
the NFS share, or hourly, etc.):

cd /usr/local/bin && ln -fs /mnt/share/bin/* .

IME this will help prevent your shell locking up if the NFS mount hangs.

3. Consider whether you can use the automounter (autofs) instead of a
fixed mount in /etc/fstab. (The automounter will unmount the filesystem
when it's not in use, and remount it automatically on demand.) This will
reduce - but not remove - the likelihood of the filesystem being mounted
when the network disappears.

4. Change the mount options to include "hard" (not soft) and "intr".

5. Next time, try using umount -l (lazy umount) to umount the filesystem
when it's already gone. Not perfect, but usually works for me.

Chris


-- 
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/5215v8x2k2@news.roaima.co.uk

Re: Free software

[Brad Rogers]

On Wed, 25 Jan 2012 12:42:24 +0300
Stayvoid  wrote:

Hello Stayvoid,

> I want to install Debian.
> Does it contain any non-free software? How to check it?

The main Debian repos have three sections;  Main, Contrib & Non-free.

> Is there a way to use Debian without non-free software?

Don't use the Non-free section.  IIRC, a default install sets up only
Main.  Contrib and Non-free have to be specifically added by the user.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
It's not your heart, it's your bank I want to break
It's Yer Money - Wonder Stuff


signature.asc
Description: PGP signature

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

(I made a mistake and answered to the posters individually instead of
the list, so I'll post my answers here again. Sorry for that!)

Le 25 janvier 2012 10:20, richard  a écrit :

>> I'm installing Debian on a new computer and although the install of
>> stable version works fine, after upgrade to testing I am unable to
>> boot on the 3.1 kernel. There is no X on the machine (for the moment)
>> and I get a blank screen a few seconds after boot. I suspect a problem
>> with the graphics card (NVidia GTX 570) and nouveau, but couldn't find
>> a workaround.

> Remi try first blacklisting nouveau
> /etc/modprobe.d/
> HTH

I tried that already, I added a new file in there containing only one
 line "blacklist nouveau". It didn't work. Do I need to do something
 special after creating this file? (regenerate something, add it
 somewhere else to make sure it is used...)

 Note also that installing the nvidia-glx adds a file in
 /etc/modprobe.d that blacklists nouveau, and I still get the problem
 with the nvidia-glx package installed.

 So blacklisting nouveau in /etc/modprobe.d doesn't seem to be enough.
-- 
Rémi Moyen


--
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/CAOBzH+=nxms73jvcoxe1mn70i++1rtucy6aejuxa+en3xd7...@mail.gmail.com

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

(again, I mistakenly answered Alberto directly instead of the list, so
I repost our exchanges here. Sorry...)

Le 25 janvier 2012 10:27, Alberto Luaces  a écrit :

> If you are not running or have X installed, you can uninstall nouveau
> and nvidia-glx packages.

Yes, I agree. I installed nvidia-glx only because everything else I
 could think of was failing... But as I said, even before installing
 it, it didn't work. Moreover, ultimately I want a X server, so at one
 point in the future I'll want to install it anyway. But un-installing
 it doesn't change anything to my boot problem, unfortunately.

 As for nouveau, I've also thought about uninstalling it, the problem
 is that it seems to come from the kernel itself. At one point (sorry,
 I can't remember exactly when in all my tries...) I had a
 libdrm-nouveau1a package installed, but uninstalling it didn't change
 anything. No other package contains nouveau in its name, and the only
 files on the disk that do are the kernel modules (one per kernel, 2.6
 and 3.1). So I don't see what else I could try uninstalling.

 The nouveau.ko kernel module seems to be provided by the kernel
 package itself (at least, this is what dpkg -S tells me), so I don't
 see how I can uninstall nouveau without uninstalling the kernel.

 (one way could be to compile my own kernel only to disable nouveau in
 it, but I would rather avoid having to do this as this would increase
 the maintenance burden -- not hugely, but I don't feel this should be
 needed...)

> Since you can access the machine from a network connection, watch for
> errors in the logs with the «dmesg» command.

Tried that also, and as I said, I don't see any suspicious messages
 there. Now, I don't claim that there are no error messages at all, but
 I couldn't find any message that truly seemed to indicate a problem,
 and some googling with the few messages that slightly bothered me
 didn't turn up anything useful. I might have missed the important one
 (actually, I should have made a copy of dmesg to post it as well,
 sorry...).





And in another mail, Alberto suggested:
> If the module is brought by the kernel, you can avoid loading it by
 > blacklisting it in the system configuration:
 >
 > http://wiki.debian.org/KernelModuleBlacklisting

Hmm, I already added the /etc/modprobe.d file, but I didn't run depmod
nor update-initramfs. I'll try that. Will depmod affect the
non-running 3.1 kernel even if I launch it from running the 2.6
kernel?

Also, what changes are supposed to be made by depmod (i.e. is there a
way I can check that it has effectively done what it should)? Same
question for update-initramfs, how can I check that the generated
initrd is OK (and will it update the initrd for the 3.1 kernel and not
only the 2.6 one)?

Thanks!
-- 
Rémi Moyen


--
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/CAOBzH+=wBzujTPDyk+HpmimHc+8N5bGaAvjnQmZfB53JJkh=a...@mail.gmail.com

Re: boot failure

[Pierre Frenkiel]

On Tue, 24 Jan 2012, Pierre Frenkiel wrote:


 But may-be /etc/modprobe/options is used at kernel upgrade to create
 the initrd image. That would explain why the same error occured with
 my 2 kernels.


   Running dpkg-reconfigure, I checked that this is true
   Remains the question "how /etc/modprobe.d/options was corrupted"
   May-be after a power failure, but I thought that this couldn't
   happen with a ext4 file system.

--
Pierre Frenkiel


--
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/alpine.deb.2.00.1201251331220.8...@pfr2.frenkiel-hure.net

Re: Free software

[Nate Bargmann]

* On 2012 25 Jan 03:43 -0600, Stayvoid wrote:
> Hello!
> 
> I want to install Debian.
> Does it contain any non-free software? How to check it?
> 
> Is there a way to use Debian without non-free software?

The default is the way.  That said, you may find that depending on your
hardware that the experience will be less than satisfactory.  Some
hardware, particularly that found on laptops and various integrated
systems, will require firmware blobs found in the firmware-linux-nonfree
package to enable things like wireless, sound, and video capabilities.
I'm not saying that it's not possible to run with only Free Software but
be aware of any limitations when you do.  Nor am I advocating for
non-free software, just noting reality as it exists.

Also, be aware that certain GNU documentation is not found in the main
section due to its license being judged as too restrictive per the DFSG.

- Nate >>

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us


-- 
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/20120125131128.ge5...@n0nb.us

Re: Free software

[Alex Mestiashvili]

On 01/25/2012 10:42 AM, Stayvoid wrote:
> Hello!
>
> I want to install Debian.
> Does it contain any non-free software? How to check it?
>   
vrms - Virtual Richard M. Stallman
 can help you .
> Is there a way to use Debian without non-free software?
>
>   
sure , non-free part of repository is not Debian , even if Debian
community support it .
> King regards.
>
>
>   

But the biggest problem here is hardware :) , here you can't do much ,
all kinds of firmwares-nightmares are usually not free .

Best regards ,
Alex

NIC transferring twice its max rate

[Rob Owens]

I've got an onboard NIC, supposedly 100Mb.  I've been doing a dd over
ssh for the last hour, and iftop tells me that I'm transmitting at a
steady 186Mb, while receiving about 1.2Mb.

I read up a bit on full duplex, and as I understand it full duplex means
the NIC would be capable of transmitting a theoretical max of 100Mb
while simultaneously receiving 100Mb.  My card seems to be transmitting
at nearly double its theoretical max.

Is this possible, or is iftop lying to me?

I've got gigabit networking between the two computers, and the second
computer has gigabit ethernet.

-Rob


-- 
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/20120125143939.ga3...@aurora.owens.net

Re: Setting up horde3 on Debian Squeeze

[Arnt Karlsen]

On Wed, 18 Jan 2012 19:32:58 +0100, Csanyi wrote in message 
<87ipk8n9np.fsf@debian-asztal.excito>:

> Arnt Karlsen  writes:
> 
> > On Wed, 18 Jan 2012 06:59:06 +0100, Csanyi wrote in message 
> > <87boq1d00l.fsf@debian-asztal.excito>:
> >
> >> Knut Esztermann  writes:
> >> 
> >> > Csanyi Pal schrieb am 16.01.2012 um 21:58:
> >> >> I'm trying to setup horde3 on my home server, that running
> >> >> Debian GNU/Linux Squeeze.
> >> >> I'm following instructions from
> >> >> /usr/share/doc/horde3/README.Debian.gz
> >> 
> >> >> Now when I trying to open this webpage from my desktop machine
> >> >> on the LAN behind the server on which have installed and setup
> >> >> horde3, I get error message:
> >> >> Not Found
> >> >> The requested URL /login.php was not found on this server.
> >> >> Apache/2.2.16 (Debian) Server at 192.168.10.1 Port 80
> >> >> Why can't I open the Horde3 webpage to setup it further?
> >> >
> >> > It seems as if apache looks for login.php in the web root, not in
> >> > the horde directory (should be /horde3/login.php). Try changing
> >> > the 'webroot' setting in /etc/horde/horde3/registry.php to
> >> > '/horde3'.
> >> 
> >> I edited the file so:
> >> $this->applications['horde'] = array(
> >> 'fileroot' => '/usr/share/horde3/lib' . '/..',
> >> //'webroot' => _detect_webroot(),
> >> 'webroot' => '/horde3',
> >> 'initial_page' => 'login.php',
> >> 'name' => _("Horde"),
> >> 'status' => 'active',
> >> 'templates' => '/usr/share/horde3/lib' . '/../templates',
> >> 'provides' => 'horde',
> >> );
> >> 
> >> and try to open the webpage http://192.168.10.1/horde3/
> >> but never get it opened. Iceweasel webbrowser says in the status
> >> line something like: Waiting for 192.168.10.1...
> >> 
> >> In the address field of the Iceweasel browser there is:
> >> http://192.168.10.1/horde3/login.php?Horde=8qrg5u0qi8tq5s5nkequ0uk3c5
> 
> > ..you did restart the server services?
> 
> I did run
> sudo /etc/init.d/apache2 restart
> 
> to restart my Apache2 server. Is that what do you mean?
> 

..yes.  (I usually do that as root, rather than go the sudo route.)


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
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/20120125151542.414c3...@nb6.lan

Re: Blank screen at boot with kernel 3.1

[Brian]

On Wed 25 Jan 2012 at 09:56:15 +, Rémi Moyen wrote:

> OK, so now I get what I think should be a working up-to-date testing
> system. Rebooting on the 2.6.32 kernel works again perfectly. But
> rebooting on the 3.1 kernel starts to boot (it prints at least the
> "waiting for udev to be populated" message) and then all I get is a
> blank screen. Some messages get displayed before, but so fast that I
> have no hope to even catch a glimpse of a word. The screen flickers
> when it becomes black, at about the time where in the 2.6 kernel the
> screen resolution changes, so I guess this is the step that fails.
> With the blank screen, I can't do anything. Keyboard seems dead (at
> least "Caps Lock" doesn't respond, although "Num Lock" does). The
> machine is still alive and can be logged-on remotely, but that's all.
> I didn't see anything strange in syslog or dmesg, but I might have
> missed something.

The Squeeze kernel is happy to use nouveau with your card so you
would expect the Wheezy one to be equally content. Testing also
produces a visible display, which surely it wouldn't if there was no
video driver to work with. Comparing dmesg for both boots may show
differences. Look for 'drm' and 'nouveau'. Post both if you so wish.

This dead keyboard: does it not respond to CTRL-ALT-DEL?

And is the final screen really blank? In the past day or so Wheezy
installs a getty which clears the screen before displaying a login
prompt. That's a long shot because I cannot see you missing it and
you were very detailed in describing your observations.


-- 
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/20120125143617.GS17235@desktop

Re: NIC transferring twice its max rate

[Rob Owens]

On Wed, Jan 25, 2012 at 09:39:40AM -0500, Rob Owens wrote:
> I've got an onboard NIC, supposedly 100Mb.  I've been doing a dd over
> ssh for the last hour, and iftop tells me that I'm transmitting at a
> steady 186Mb, while receiving about 1.2Mb.
> 
> I read up a bit on full duplex, and as I understand it full duplex means
> the NIC would be capable of transmitting a theoretical max of 100Mb
> while simultaneously receiving 100Mb.  My card seems to be transmitting
> at nearly double its theoretical max.
> 
> Is this possible, or is iftop lying to me?
> 
> I've got gigabit networking between the two computers, and the second
> computer has gigabit ethernet.
> 
I just ran iftop on the second computer, and it reports receiving at a
rate of 92Mb.  So apparently iftop is lying to me, at least on one of
the computers.

I guess I'll find out which one is telling the truth (if any) based on
how long it takes for this 160GB transfer.

-Rob


-- 
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/20120125151514.ga4...@aurora.owens.net

Re: System hangs due to NFS share

[Tom H]

On Tue, Jan 24, 2012 at 12:50 PM, Sylvain  wrote:
> On 24. 01. 12 09:28, Tom H wrote:
>> On 24/01/12 18:50, Sylvain wrote:
>>>
>>> I tried to SIGKILL the [nfsiod] process but it didn't get killed. I
>>> also tried to kill the various rpcbind processes but it didn't change
>>> anything.
>>>
>>> I also tried autofs as Scott suggested, but the same problem occured
>>> when I unplugged the network cable (most of the system hangs, can't
>>> reboot nor halt). Here's how I configured autofs:
>>>
>>> /etc/auto.misc:
>>> bazinga -retry=1,rw,hard,size=8192,wsize=8192
>>> 192.168.2.77:/DataVolume/Public
>>>
>>> /etc/auto.master:
>>> /misc   /etc/auto.misc --timeout 20
>>>
>>> Here's what I found in the syslog:
>>>
 Jan 23 22:59:17 cid kernel: [  510.944160] nfs: server 192.168.2.77 not
 responding, still trying
 Jan 23 23:01:22 cid kernel: [  635.616161] nfs: server 192.168.2.77 not
 responding, still trying
 Jan 23 23:01:46 cid sm-notify[841]: DNS resolution of Bazinga.local
 failed; retrying later
 Jan 23 23:03:51 cid sm-notify[841]: DNS resolution of Bazinga.local
 failed; retrying later
 Jan 23 23:05:56 cid sm-notify[841]: DNS resolution of Bazinga.local
 failed; retrying later
 Jan 23 23:07:56 cid sm-notify[841]: Unable to notify Bazinga.local,
 giving up
>>>
>>> I'm not sure why it's trying to resolve the "bazinga.local" name, and
>>> even when it gave up with the resolution, it didn't unfreeze anything.
>>> Also nfs seems to be still trying to reach the server (the cable was
>>> unplugged at 22:56).
>>
>> It's avahi that's trying to resolve "Bazinga" through "Bazinga.local".
>>
>> Is Bazinga the hostname of 192.168.2.77?
>>
>> Did ifs quit after avahi failed?
>
> No, nfs didn't quit after avahi failed (the nfsiod process is still here).
> Also I don't know the hostname of 192.168.2.77, because it's just a NAS box
> on which I don't have any control.

Too bad x2.

Your indirect map uses "/misc/bazinga" as a mount point. Doesn't
Bazinga/bazinga mean anything to you?

Do you have a reference to Bazinga in "/var/lib/nfs/sm*/"?

Someone suggested using different options including "soft"; I
wouldn't. I'd try "mount/umount" without any options as a test.


--
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/CAOdo=Swv7QcONuktkeb5G7zSGf4OfivoM=hy-b_ylhyhimq...@mail.gmail.com

Re: Kernel Compiling from scratch

[Syed Hasan Atizaz]

isnt it suppose to be

/boot/config-$(uname -r) .config ?
plus what type of configuration it stores ? just curious.

On Wed, Jan 25, 2012 at 8:22 PM,   wrote:
> The best tutorial I have found describing the Debian way to compile the
> kernel is Steve Powell's pae:
>
> http://users.wowway.com/~zlinuxman/Kernel.htm
>
> There are lots of others, just google around, but be wary of older pages
> and read Steve's page first.
>
> I have no idea how using virtual box may affect/complicate the process.
>
> Keith Ostertag
>
>
>> Hello
>> I like to know where can i get the information in detail for compiling
>> kernel, loading modules and installing programs from scratch. i never
>> did it before. I installed virtual box recently and looking to play
>> with it.
>> Thank you
>> Syed Hasan Atizaz
>>
>
>


-- 
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/canppwqtn2cjtrfbmdn2cjsav+ljctzxtywt7fxu4wuw9arq...@mail.gmail.com

Re: boot failure

[Marc Auslander]

Pierre Frenkiel  writes:

> On Tue, 24 Jan 2012, Pierre Frenkiel wrote:
>
>Remains the question "how /etc/modprobe.d/options was corrupted"
>May-be after a power failure, but I thought that this couldn't
>happen with a ext4 file system.
>

The default/normal configuration of ext4 journals only metadata.
This means that file system integrity is guaranteed but individual
file content can be corrupted by a power failure or other hard crash.

To update files that must be correct, one can write a new version,
sync, and then use mv to replace the old with the new version.  Since
mv is a metadata operation, it is guaranteed to either have happened
or not after crash recovery.

The journal_data option provides full protection, but I suspect it is
not a practical solution for normal usage.


-- 
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/87d3a7erxq@aptiva.optonline.net

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

Le 25 janvier 2012 14:36, Brian  a écrit :
> On Wed 25 Jan 2012 at 09:56:15 +, Rémi Moyen wrote:
>
>> OK, so now I get what I think should be a working up-to-date testing
>> system. Rebooting on the 2.6.32 kernel works again perfectly. But
>> rebooting on the 3.1 kernel starts to boot (it prints at least the
>> "waiting for udev to be populated" message) and then all I get is a
>> blank screen. Some messages get displayed before, but so fast that I
>> have no hope to even catch a glimpse of a word. The screen flickers
>> when it becomes black, at about the time where in the 2.6 kernel the
>> screen resolution changes, so I guess this is the step that fails.
>> With the blank screen, I can't do anything. Keyboard seems dead (at
>> least "Caps Lock" doesn't respond, although "Num Lock" does). The
>> machine is still alive and can be logged-on remotely, but that's all.
>> I didn't see anything strange in syslog or dmesg, but I might have
>> missed something.
>
> The Squeeze kernel is happy to use nouveau with your card so you
> would expect the Wheezy one to be equally content. Testing also
> produces a visible display, which surely it wouldn't if there was no
> video driver to work with.

Well, I'm guessing that at the early stage of the boot some very crude
driver is used and things fail when the kernel tries to load/use
something more complicated. Kernel 3.1 can display something but only
using the "big" characters at startup (something like 80x25, I would
guess). Kernel 2.6 switches to smaller characters very early in the
boot sequence and I am guessing that this is when attempting that that
the kernel 3.1 fails. But that's just a guess and doesn't really help
me...

Also, I noticed that when I did a first install with graphical
environment, X was working with the 2.6 kernel (obviously not with the
3.1...) and the xorg.0.log was saying something along the lines of
"searching a driver for your card, trying (in this order) nouveau, nv,
vesa" (not the exact messages, but that was the gist of it). Then
error messages about not being able to load nouveau (with the 2.6
kernel, again, so why was it not working there?), same errors for nv
(which was normal because at that point I had not installed the
xserver-xorg-video-nv package so I was not expecting X to be able to
use it) and finally doing some stuff with vesa (it might have been
trying something with "fb", vesafb or the like before?). Then when
logging in Gnome for the first time, I got another error saying more
or less "cannot use all the fancy graphic stuff because you're not
using the right drivers" (I'm rephrasing, you can guess...).

What I'm concluding from this is that even with the working 2.6
kernel, somehow nouveau wasn't properly working in X. Installing the
nvidia module didn't work as I have the DKMS issue where I can only
build the 3.1 module (so I cannot test the nvidia module with the 2.6
kernel). Now, this was about X, so I didn't mention it in my first
message, because it could be caused by something else (for example a
problem with the xserver-xorg-video packages, not with the kernel).

But I'm just saying that it might be that even the 2.6 kernel isn't so
happy with nouveau and my card...

> Comparing dmesg for both boots may show
> differences. Look for 'drm' and 'nouveau'. Post both if you so wish.

Yep, will do that tonight. Why drm, btw? I did notice that this was
associated with nouveau in a number of messages, but is there a
specific module for it? If yes, would blacklist/uninstall nouveau be
enough or should I also try to do something about this drm stuff?

> This dead keyboard: does it not respond to CTRL-ALT-DEL?

No. Only NumLock seems to have a visible effect (the led switches
on/off). Any other combination I tried does nothing. I didn't try the
magic SysRq combinations, mostly because I don't know them, but also
because I don't remember if they are supposed to be activated in the
standard Debian kernels...

The system does seem to properly respond to a hard-reset (i.e. by
pressing the reset button on the computer case), because at the next
boot it doesn't complain of badly unmounted file system (which it does
if I turn off the power by pressing the "on" button for 5 s.). But
that doesn't bring any more information than knowing that I can
remotely login. The machine seems alive and well, excepted for the
display/keyboard.

> And is the final screen really blank? In the past day or so Wheezy
> installs a getty which clears the screen before displaying a login
> prompt. That's a long shot because I cannot see you missing it and
> you were very detailed in describing your observations.

There is definitely no login prompt, nor anything bigger than a single
character. There may be a cursor in the top-left corner (and that
would indicate that the graphic is not totally botched...), but I'm
99.999...% sure that there isn't (I'm not saying 100% because I'm not
sitting in from of the machine right now, but if pushed to it I would

Re: Kernel Compiling from scratch

[keitho]

The best tutorial I have found describing the Debian way to compile the
kernel is Steve Powell's pae:

http://users.wowway.com/~zlinuxman/Kernel.htm

There are lots of others, just google around, but be wary of older pages
and read Steve's page first.

I have no idea how using virtual box may affect/complicate the process.

Keith Ostertag


> Hello
> I like to know where can i get the information in detail for compiling
> kernel, loading modules and installing programs from scratch. i never
> did it before. I installed virtual box recently and looking to play
> with it.
> Thank you
> Syed Hasan Atizaz
>



--
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/7278650b4c21fe19146b5dcf6cb2ef70.squir...@webmail.strucktower.com

Re: SGE (grid-engine-*) versus open grid scheduler

[francis picabia]

On Thu, Dec 8, 2011 at 4:04 PM, francis picabia  wrote:
>
> On Thu, Dec 8, 2011 at 2:23 PM, Camaleón  wrote:
>>
>> On Wed, 07 Dec 2011 12:08:55 -0400, francis picabia wrote:
>>
>> > Maybe this isn't the best list to discuss grid cluster software, but
>> > I'll see...
>>
>> JFYI, there is also:
>>
>>
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gridengine-devel
>
>
> Thank you for the response.
>
> Very good to see this mailing list.
> I saw a reference at one package site to that, but thought
> perhaps it was for internal use only.  It didn't appear on a list
> of Debian mailing lists I saw.  I'll join.

I can confirm this mailing list is only for developers use.  I've queried it
and Debian developers directly and they do not answer email.

It looks like the better list is "open source grid engine users",
which is outside of Debian.

http://gridengine.org/mailman/listinfo/users

It is a strange situation when Oracle makes their free grid engine commercial,
and another company (Univa) hires the bulk of Sun's former grid engine
developers,
again selling a commercial product.  That leaves us with only the open source
alternative.  But I can't find out what Debian is doing with its
package.  I simply want
to adopt a solution with a path going into the future, what ever that
is.  I don't
want the equivalent of deploying Sun/Oracle Java JDK from Debian
package and watch
it evaporate.


--
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/ca+akb6hdrbsc9h+6r3fetsnpdu7fhgtwe8-vsr5ptd-_f1r...@mail.gmail.com

Re: Blank screen at boot with kernel 3.1

[richard]

On Wed, 25 Jan 2012 15:33:19 +
Rémi Moyen  wrote:
< Gurt big snip>

OK different approach.
You can identify if its kernel 3 problem or not by booting up off a live cd.
Download a Fedora FC16 live CD..
Yes I said Fedora, I've found the hard way that Debian is a bit fussy with
graphics card drivers.
My main machine has a ATI card built in which run fine on Fedora on
gnome-shell, gdm3,
Even after much attempts to configure it would only half work.I had to buy a
Nvidia card to run gnome-shell normally.
FC16 live CD will go straight in to gnome-shell , not in fallback mode as
long as your card can manage acceleration..
I strongly suspect it will run. Gnome-shell,gdm3, has the word "activities" in
the top left hand corner.

If/when that runs properly you will know where the problem is, whether is
debian or kernel3/gnome3.

HTH

-- 
Best wishes / 73
Richard Bown

e-mail: rich...@g8jvm.com   or   richard.b...@blueyonder.co.uk

nil carborundum a illegitemis
##
Ham Call G8JVM . OS Fedora FC16 x86_64 on a Dell Insiron N5030 laptop
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs mins )
QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W & 3 cms:5W
##
 


--
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/20120125160707.24ff9...@lappy.g8jvm.com

Re: Blank screen at boot with kernel 3.1

[Sven Joachim]

On 2012-01-25 16:33 +0100, Rémi Moyen wrote:

> Well, I'm guessing that at the early stage of the boot some very crude
> driver is used and things fail when the kernel tries to load/use
> something more complicated. Kernel 3.1 can display something but only
> using the "big" characters at startup (something like 80x25, I would
> guess).

This is the standard text mode which you get when you don't load a
framebuffer driver such as vesafb or nouveaufb (the latter is part of
the nouveau.ko kernel module).

> Kernel 2.6 switches to smaller characters very early in the
> boot sequence and I am guessing that this is when attempting that that
> the kernel 3.1 fails. But that's just a guess and doesn't really help
> me...
>
> Also, I noticed that when I did a first install with graphical
> environment, X was working with the 2.6 kernel (obviously not with the
> 3.1...) and the xorg.0.log was saying something along the lines of
> "searching a driver for your card, trying (in this order) nouveau, nv,
> vesa" (not the exact messages, but that was the gist of it). Then
> error messages about not being able to load nouveau (with the 2.6
> kernel, again, so why was it not working there?),

I assume because the card is not supported by the nouveau module
in the Squeeze kernel.  IIRC, you need Linux 2.6.38 at least.

> same errors for nv
> (which was normal because at that point I had not installed the
> xserver-xorg-video-nv package so I was not expecting X to be able to
> use it)

Would have been useless anyway, nv does not support your card.

> and finally doing some stuff with vesa (it might have been
> trying something with "fb", vesafb or the like before?). Then when
> logging in Gnome for the first time, I got another error saying more
> or less "cannot use all the fancy graphic stuff because you're not
> using the right drivers" (I'm rephrasing, you can guess...).

You have to use either the NVidia blob or nouveau with a kernel >= 3.2
and libgl1-mesa-dri package >= 7.11.1-1.

> Yep, will do that tonight. Why drm, btw? I did notice that this was
> associated with nouveau in a number of messages, but is there a
> specific module for it? If yes, would blacklist/uninstall nouveau be
> enough or should I also try to do something about this drm stuff?

If you want to make sure nouveau does not do anything harmful (or
useful) ever, boot with the "nomodeset" kernel parameter.

Sven


-- 
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/87sjj3wyt6@turtle.gmx.de

Re: boot failure

[Pierre Frenkiel]

On Wed, 25 Jan 2012, Marc Auslander wrote:


To update files that must be correct, one can write a new version,
sync, and then use mv to replace the old with the new version.


  The only way to easily do that seems to always call any editor via a script
  doing that.


The journal_data option provides full protection, but I suspect it is
not a practical solution for normal usage.


  Do you mean the "data=journal" mount option ?
  According the documentation, that seems a way to overcome this problem.

  And what about a file like /etc/modprobe.d/options, and all
  other config files which were never edited ?

--
Pierre Frenkiel


--
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/alpine.deb.2.00.1201251730390.11...@pfr2.frenkiel-hure.net

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

Le 25 janvier 2012 16:07, richard  a écrit :

> OK different approach.
> You can identify if its kernel 3 problem or not by booting up off a live cd.
> Download a Fedora FC16 live CD..

Good point. If I don't find another way to tweak the install, I'll try that.
-- 
Rémi Moyen


--
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/CAOBzH+m0ng0iN_pyLZfKYsSL6wkOe+VUFx7wjZe0H=oqq46...@mail.gmail.com

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

Le 25 janvier 2012 16:07, Sven Joachim  a écrit :
> On 2012-01-25 16:33 +0100, Rémi Moyen wrote:
>
>> Well, I'm guessing that at the early stage of the boot some very crude
>> driver is used and things fail when the kernel tries to load/use
>> something more complicated. Kernel 3.1 can display something but only
>> using the "big" characters at startup (something like 80x25, I would
>> guess).
>
> This is the standard text mode which you get when you don't load a
> framebuffer driver such as vesafb or nouveaufb (the latter is part of
> the nouveau.ko kernel module).

This is what I suspected, yes. Up to that point, I don't think
anything can really go wrong!

>> Kernel 2.6 switches to smaller characters very early in the
>> boot sequence and I am guessing that this is when attempting that that
>> the kernel 3.1 fails. But that's just a guess and doesn't really help
>> me...
>>
>> Also, I noticed that when I did a first install with graphical
>> environment, X was working with the 2.6 kernel (obviously not with the
>> 3.1...) and the xorg.0.log was saying something along the lines of
>> "searching a driver for your card, trying (in this order) nouveau, nv,
>> vesa" (not the exact messages, but that was the gist of it). Then
>> error messages about not being able to load nouveau (with the 2.6
>> kernel, again, so why was it not working there?),
>
> I assume because the card is not supported by the nouveau module
> in the Squeeze kernel.  IIRC, you need Linux 2.6.38 at least.

Might be, yes. The kernel is 2.6.32, I think (at least, the
kernel-image package in stable is 2.6.32, so I think this is the one I
have). So that might explain why the nouveau driver is not properly
used with the stable kernel.

I am also guessing, based on this (why didn't I think about that
earlier?) that in the 3.1 kernel, my card is supposed to be supported
by nouveau, hence it tries to use it (and this causes all my problems)
whereas in 2.6.32 it doesn't even try to use nouveau and falls back to
vesafb or something like it, hence it still manages to display
something. Does this makes sense, or is this gibberish?

>> same errors for nv
>> (which was normal because at that point I had not installed the
>> xserver-xorg-video-nv package so I was not expecting X to be able to
>> use it)
>
> Would have been useless anyway, nv does not support your card.

OK. That would avoid me even trying it :-)

> You have to use either the NVidia blob or nouveau with a kernel >= 3.2
> and libgl1-mesa-dri package >= 7.11.1-1.

Hmm... Why do you say 3.2? Is there something specific that was added
in nouveau in 3.2? Support for my card, I guess? Where did you find
this information?

Kernel 3.2 seems to be still in unstable, I'd rather not install
something from there if I can avoid it. But that is worth trying, at
least!

Also, it should be working with the nvidia stuff, but apparently it
doesn't. I understand that to use the nvidia stuff I need to somehow
deactivate nouveau, but neither the blacklist in modprobe.d nor using
nomodelist in the boot options did the trick...

> If you want to make sure nouveau does not do anything harmful (or
> useful) ever, boot with the "nomodeset" kernel parameter.

I tried that, but it didn't change anything. OK, maybe I did it wrong?
Let me try to summarize what I've learned/guessed here:

* To blacklist nouveau, there needs to be a "blacklist nouveau" line
somewhere in a file in /etc/modprobe.d. The nvidia DKMS package does
this (or I did that manually), but apparently this is not enough. I've
yet to try running depmod -ae and regenerating the initrd afterwards,
could not doing it be a reason why nouveau is not properly
blacklisted?

* To completely disable nouveau, I should pass nomodeset to the
kernel. I tried doing this by modifying the GRUB_CMDLINE_LINUX_DEFAULT
(or GRUB_CMDLINE_LINUX) in /etc/default/grub and then running
update-grub, this does not seem to work (then rebooting). Is it the
right way to set this parameter?

Thanks for your help!
-- 
Rémi Moyen


--
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/CAOBzH+=ZTJ+FQ-YdZcG9iQ-F7FAMPn=xkvpc7d3egyfrwjw...@mail.gmail.com

Re: NIC transferring twice its max rate

[Allan Wind]

On 2012-01-25 09:39:40, Rob Owens wrote:
> I've got an onboard NIC, supposedly 100Mb.  I've been doing a dd over
> ssh for the last hour, and iftop tells me that I'm transmitting at a
> steady 186Mb, while receiving about 1.2Mb.

Perhaps you have compression enabled for ssh?


/Allan
-- 
Allan Wind
Life Integrity, LLC



-- 
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/20120125170349.gt15...@lifeintegrity.com

Re: Blank screen at boot with kernel 3.1

[Sven Joachim]

On 2012-01-25 18:04 +0100, Rémi Moyen wrote:

> I am also guessing, based on this (why didn't I think about that
> earlier?) that in the 3.1 kernel, my card is supposed to be supported
> by nouveau, hence it tries to use it (and this causes all my problems)
> whereas in 2.6.32 it doesn't even try to use nouveau and falls back to
> vesafb or something like it, hence it still manages to display
> something. Does this makes sense, or is this gibberish?

It makes sense, but since you seem to have the problem even with
"nomodeset", it might not actually be the cause.

>> You have to use either the NVidia blob or nouveau with a kernel >= 3.2
>> and libgl1-mesa-dri package >= 7.11.1-1.
>
> Hmm... Why do you say 3.2? Is there something specific that was added
> in nouveau in 3.2? Support for my card, I guess?

No, but earlier kernels had acceleration disabled for your card.

> Where did you find this information?

On upstream's wiki¹ there is a link to the relevant kernel commit².

> Kernel 3.2 seems to be still in unstable, I'd rather not install
> something from there if I can avoid it.

No, 3.2 has been in testing for six days, 3.1 is not supported anymore.
And yesterday's upload to unstable fixed a local root exploit³, so it's
really time to upgrade.

>> If you want to make sure nouveau does not do anything harmful (or
>> useful) ever, boot with the "nomodeset" kernel parameter.
>
> I tried that, but it didn't change anything. OK, maybe I did it wrong?
>
> * To blacklist nouveau, there needs to be a "blacklist nouveau" line
> somewhere in a file in /etc/modprobe.d. The nvidia DKMS package does
> this (or I did that manually), but apparently this is not enough.

It is enough to prevent udev from loading the module, but X will still
try to load it if you don't specify a different driver in xorg.xonf.

> I've yet to try running depmod -ae and regenerating the initrd
> afterwards, could not doing it be a reason why nouveau is not properly
> blacklisted?

Only if you have added the module to the initramfs yourself, which is
unlikely.  If you see the message "INIT: version 2.88 booting" in text
mode, your initramfs does not load it.

> * To completely disable nouveau, I should pass nomodeset to the
> kernel. I tried doing this by modifying the GRUB_CMDLINE_LINUX_DEFAULT
> (or GRUB_CMDLINE_LINUX) in /etc/default/grub and then running
> update-grub, this does not seem to work (then rebooting). Is it the
> right way to set this parameter?

If you want to set it permanently, yes.

Sven


¹ http://nouveau.freedesktop.org/wiki/InstallDRM#Firmware
¹ 
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=80859760daa01fb38497aa6326a32a16489d8c97
³ http://lwn.net/Articles/476684/


-- 
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/87boprwt44@turtle.gmx.de

Re: issue with mdadm and mirroring drives

[Joey L]

Okay..I am telling all in this email -:)

My configuration is as such:
/dev/md0 = /dev/sdc1 and /dev/sdd1
/dev/md1 = /dev/sda1 and /dev/sb1

My swap partitions are not part of the array or mirror  at all -
they are just regular partitions - they are:
/dev/sdc2 and /dev/sdd2.

When I boot the system with all drives in, I get the superflous error.

So the only way to boot is only to put in /dev/sdc alone and boot.
when i get to a linux prompt, I insert the second drive into the system /dev/sdd

To sync them, /dev/sdd has already failed, so i run
sfdisk -d /dev/sdc | sfdisk /dev/sdd
** i get an error that nothing has changed - so I run it with the
--force command to get the partitions identical like:
sfdisk -d /dev/sdc | sfdisk --force /dev/sdd

Once that is successful - i run mdadm --manage /dev/md0 --add /dev/sdd1

And the sync process starts, and when it is done yesterday, I ran this
and got these errors:


root@rider:~# grub-install --recheck --no-floppy /dev/sdc
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
Installation finished. No error reported.
root@rider:~# grub-install --recheck --no-floppy /dev/sdd
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
error: superfluous RAID member (2 found).
Installation finished. No error reported.
root@rider:~# grub-install --recheck --no-floppy /dev/sdc


My blkid is :
root@rider:~# blkid
/dev/md0: UUID="611258bc-4ace-4779-b44d-73ba1949f7db" TYPE="ext4"
/dev/sdb1: UUID="98d6db12-5b96-8cb7-25d3-d6abaab9ab86" LABEL="rider:1"
TYPE="linux_raid_member"
/dev/sda1: UUID="98d6db12-5b96-8cb7-25d3-d6abaab9ab86" LABEL="rider:1"
TYPE="linux_raid_member"
/dev/md1: UUID="70e605e3-7dbb-412e-9b0a-c212bf9d8592" TYPE="ext4"
/dev/sdc1: UUID="f696d568-1f42-26e3-42f0-a70a68e284a7"
LABEL="debian:0" TYPE="linux_raid_member"
/dev/sdc2: UUID="ba64d9c2-8e76-4545-8d64-7fc0adcc3b17" TYPE="swap"
/dev/sdd1: UUID="f696d568-1f42-26e3-42f0-a70a68e284a7"
LABEL="debian:0" TYPE="linux_raid_member"
/dev/sdd2: UUID="bdacec9f-1b12-44db-8562-d572a7117790" TYPE="swap"


My parted -l is:


Model: ATA ST31000340AS (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType File system  Flags
 1  32.3kB  1000GB  1000GB  primary  ext3 raid


Model: ATA ST31000340AS (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType File system  Flags
 1  32.3kB  1000GB  1000GB  primary  ext3 raid


Model: ATA ST31000340AS (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType File system Flags
 1  1049kB  996GB   996GB   primary  ext3raid
 2  996GB   1000GB  4204MB  primary  linux-swap(v1)


Model: ATA ST31000528AS (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType File system Flags
 1  1049kB  996GB   996GB   primary  ext4raid
 2  996GB   1000GB  4204MB  primary  linux-swap(v1)


Warning: Unable to open /dev/fd0 read-write (Read-only file system).  /dev/fd0
has been opened read-only.

Error: /dev/fd0: unrecognised disk label

Model: Linux Software RAID Array (md)
Disk /dev/md0: 996GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  EndSize   File system  Flags
 1  0.00B  996GB  996GB  ext4


Model: Linux Software RAID Array (md)
Disk /dev/md1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End SizeFile system  Flags
 1  0.00B  1000GB  1000GB  ext4



And /proc/mdadm.conf is :

root@rider:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda1[2] sdb1[1]
  976758841 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sdd1[2] sdc1[1]
  972654456 blocks super 1.2 [2/2] [UU]

unused devices: 

When I run the status on mdadm, i get this :

root@rider:~# mdadm --misc --detail --brief /dev/md?*
ARRAY /dev/md0 metadata=1.2 name=debian:0
UUID=f696d568:1f4226e3:42f0a70a:68e284a7
ARRAY /dev/md1 metadata=1.2 name=rider:1
UUID=98d6db12:5b968cb7:25d3d6ab:aab9ab86


Also my grub boot lines are :


### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian
--class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(md/0)'
search --no-floppy --fs-uuid --set 611258bc-4ace-4779-b44d-73ba1949f7db
echo'Loading Linux 2.6.32-5-amd64 ...'
linux   /boot/vmlinuz-2.6.32-5-amd64
root=UUI

Re: NIC transferring twice its max rate

[Rob Owens]

On Wed, Jan 25, 2012 at 12:03:49PM -0500, Allan Wind wrote:
> On 2012-01-25 09:39:40, Rob Owens wrote:
> > I've got an onboard NIC, supposedly 100Mb.  I've been doing a dd over
> > ssh for the last hour, and iftop tells me that I'm transmitting at a
> > steady 186Mb, while receiving about 1.2Mb.
> 
> Perhaps you have compression enabled for ssh?
> 
Perhaps, but I think iftop should tell me how much data was sent over
the NIC, regardless of what that data might look like uncompressed.

Anyway, I started iftop partway through my transfer, and it reports that
I transferred a total of 244GB.  But I know based on the filesize (a
disk image file) that I only transferred 160GB.

I guess I'll report it as a bug.

-Rob


-- 
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/20120125181824.ga5...@aurora.owens.net

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

Le 25 janvier 2012 18:10, Sven Joachim  a écrit :
> On 2012-01-25 18:04 +0100, Rémi Moyen wrote:
>
>> I am also guessing, based on this (why didn't I think about that
>> earlier?) that in the 3.1 kernel, my card is supposed to be supported
>> by nouveau, hence it tries to use it (and this causes all my problems)
>> whereas in 2.6.32 it doesn't even try to use nouveau and falls back to
>> vesafb or something like it, hence it still manages to display
>> something. Does this makes sense, or is this gibberish?
>
> It makes sense, but since you seem to have the problem even with
> "nomodeset", it might not actually be the cause.

OK, actually... it does seem to work now!

What I did is, I booted with the 3.1 kernel, remotely logged in,
checked that nouveau was blacklisted (by an nvidia-smthg file in
/etc/modprobe.d), ran depmod & update-initramfs, then rebooted. At
that point, I still had the problem. dmseg was however indicating that
it was loading the nvidia module, and there was absolutely not a
single line implying that nouveau was used in anyway.

Then I tried again to pass nomodeset to the kernel, and... it worked!
The system boots correctly, I get my login prompt, it says it is using
the nvidia module. I am now installing X to see if that works as well,
but I am reasonably hopeful now!

I could swear that I did try the nomodeset option, especially since
another computer in the house had a similar problem that required a
similar solution (it was a Fedora and for some reason it requires a
rdblacklist=nouveau option in addition to the nomodeset). Well, either
I somehow mistyped that the first time, or maybe some of the other
manipulations (such as installing nvidia, blacklisting nouveau,
running depmod...) were needed in addition to that parameter?

Anyway, I seem to have a running system, so the problem seems solved.

Many thanks for spending some time helping me to get there!

>> Where did you find this information?
>
> On upstream's wikią there is a link to the relevant kernel commit˛.

OK, thanks for the info.

>> Kernel 3.2 seems to be still in unstable, I'd rather not install
>> something from there if I can avoid it.
>
> No, 3.2 has been in testing for six days, 3.1 is not supported anymore.

But linux-image-am64 still seems to be in version 3.1 and depends from
linux-image-3.1.0-1-amd64? I don't want to nominally install the 3.2
kernel, I only want the latest one, so I think I'll stick to
linux-image-amd64 and wait until that updates to 3.2. Should be quite
soon, I guess.

>> * To blacklist nouveau, there needs to be a "blacklist nouveau" line
>> somewhere in a file in /etc/modprobe.d. The nvidia DKMS package does
>> this (or I did that manually), but apparently this is not enough.
>
> It is enough to prevent udev from loading the module, but X will still
> try to load it if you don't specify a different driver in xorg.xonf.

Good point. I guess though that now that I have added nomodeset,
nouveau will not be available to X, so it shouldn't even try to load
it?

>> I've yet to try running depmod -ae and regenerating the initrd
>> afterwards, could not doing it be a reason why nouveau is not properly
>> blacklisted?
>
> Only if you have added the module to the initramfs yourself, which is
> unlikely.  If you see the message "INIT: version 2.88 booting" in text
> mode, your initramfs does not load it.

I certainly have not added it myself. However I don't remember seeing
the message. But on the other hand, some text was flashing on the
screen, much too fast for me to read it. Maybe that was in there?

>> * To completely disable nouveau, I should pass nomodeset to the
>> kernel. I tried doing this by modifying the GRUB_CMDLINE_LINUX_DEFAULT
>> (or GRUB_CMDLINE_LINUX) in /etc/default/grub and then running
>> update-grub, this does not seem to work (then rebooting). Is it the
>> right way to set this parameter?
>
> If you want to set it permanently, yes.

Well, since it does not really seem to work with the nvidia module
anyway, I don't see any point in keeping it.

Again, thanks for your help! (and to everybody else who helped)
-- 
Rémi Moyen


--
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/caobzh+mb0_5dvs-je9jndqi_uezurj_mt1uwr7btqgmos+d...@mail.gmail.com

Re: Blank screen at boot with kernel 3.1

[Sven Joachim]

On 2012-01-25 20:38 +0100, Rémi Moyen wrote:

> Le 25 janvier 2012 18:10, Sven Joachim  a écrit :
>> On 2012-01-25 18:04 +0100, Rémi Moyen wrote:
>
>>> Kernel 3.2 seems to be still in unstable, I'd rather not install
>>> something from there if I can avoid it.
>>
>> No, 3.2 has been in testing for six days, 3.1 is not supported anymore.
>
> But linux-image-am64 still seems to be in version 3.1 and depends from
> linux-image-3.1.0-1-amd64?

The metapackage has not yet migrated, it seems.  But 3.1 really is not
supported anymore, neither by Debian nor by upstream.

> I don't want to nominally install the 3.2
> kernel, I only want the latest one, so I think I'll stick to
> linux-image-amd64 and wait until that updates to 3.2. Should be quite
> soon, I guess.

As long as you don't have untrusted users on your system, a local root
exploit might not scare you much.  And since you're willing to use a
proprietary kernel module for which nobody knows what nasty things it
might do, security probably does not really matter.

>>> * To blacklist nouveau, there needs to be a "blacklist nouveau" line
>>> somewhere in a file in /etc/modprobe.d. The nvidia DKMS package does
>>> this (or I did that manually), but apparently this is not enough.
>>
>> It is enough to prevent udev from loading the module, but X will still
>> try to load it if you don't specify a different driver in xorg.xonf.
>
> Good point. I guess though that now that I have added nomodeset,
> nouveau will not be available to X, so it shouldn't even try to load
> it?

X does not know about that parameter, so it will try to load nouveau
unless you specify a driver in xorg.conf.  But

a) you have to specify the nvidia driver anyway if you want to use it;

b) the only ill effect would be an error message in Xorg's log.

Sven


-- 
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/87wr8fv913@turtle.gmx.de

Re: Kernel Compiling from scratch

[Syed Hasan Atizaz]

I am able to compile the kernel for i386, however no initial ram disk
image is created, i did with the help of mkinitramfs though it was
empty, still unable to boot.

On Wed, Jan 25, 2012 at 8:27 PM, Syed Hasan Atizaz
 wrote:
> isnt it suppose to be
>
> /boot/config-$(uname -r) .config ?
> plus what type of configuration it stores ? just curious.
>
> On Wed, Jan 25, 2012 at 8:22 PM,   wrote:
>> The best tutorial I have found describing the Debian way to compile the
>> kernel is Steve Powell's pae:
>>
>> http://users.wowway.com/~zlinuxman/Kernel.htm
>>
>> There are lots of others, just google around, but be wary of older pages
>> and read Steve's page first.
>>
>> I have no idea how using virtual box may affect/complicate the process.
>>
>> Keith Ostertag
>>
>>
>>> Hello
>>> I like to know where can i get the information in detail for compiling
>>> kernel, loading modules and installing programs from scratch. i never
>>> did it before. I installed virtual box recently and looking to play
>>> with it.
>>> Thank you
>>> Syed Hasan Atizaz
>>>
>>
>>


--
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/canppwqtzmydpyiuxujpj5dvee+cv7xgmw0jngsrtc9octys...@mail.gmail.com

Re: Setting up horde3 on Debian Squeeze

[Csanyi Pal]

Arnt Karlsen  writes:

> On Wed, 18 Jan 2012 19:32:58 +0100, Csanyi wrote in message 
> <87ipk8n9np.fsf@debian-asztal.excito>:
>
>> Arnt Karlsen  writes:
>> 
>> > On Wed, 18 Jan 2012 06:59:06 +0100, Csanyi wrote in message 
>> > <87boq1d00l.fsf@debian-asztal.excito>:
>> >
>> >> Knut Esztermann  writes:
>> >> 
>> >> > Csanyi Pal schrieb am 16.01.2012 um 21:58:
>> >> >> I'm trying to setup horde3 on my home server, that running
>> >> >> Debian GNU/Linux Squeeze.
>> >> >> I'm following instructions from
>> >> >> /usr/share/doc/horde3/README.Debian.gz
>> >> 
>> >> >> Now when I trying to open this webpage from my desktop machine
>> >> >> on the LAN behind the server on which have installed and setup
>> >> >> horde3, I get error message:
>> >> >> Not Found
>> >> >> The requested URL /login.php was not found on this server.
>> >> >> Apache/2.2.16 (Debian) Server at 192.168.10.1 Port 80
>> >> >> Why can't I open the Horde3 webpage to setup it further?
>> >> >
>> >> > It seems as if apache looks for login.php in the web root, not in
>> >> > the horde directory (should be /horde3/login.php). Try changing
>> >> > the 'webroot' setting in /etc/horde/horde3/registry.php to
>> >> > '/horde3'.
>> >> 
>> >> I edited the file so:
>> >> $this->applications['horde'] = array(
>> >> 'fileroot' => '/usr/share/horde3/lib' . '/..',
>> >> //'webroot' => _detect_webroot(),
>> >> 'webroot' => '/horde3',
>> >> 'initial_page' => 'login.php',
>> >> 'name' => _("Horde"),
>> >> 'status' => 'active',
>> >> 'templates' => '/usr/share/horde3/lib' . '/../templates',
>> >> 'provides' => 'horde',
>> >> );
>> >> 
>> >> and try to open the webpage http://192.168.10.1/horde3/
>> >> but never get it opened. Iceweasel webbrowser says in the status
>> >> line something like: Waiting for 192.168.10.1...
>> >> 
>> >> In the address field of the Iceweasel browser there is:
>> >> http://192.168.10.1/horde3/login.php?Horde=8qrg5u0qi8tq5s5nkequ0uk3c5
>> 
>> > ..you did restart the server services?
>> 
>> I did run
>> sudo /etc/init.d/apache2 restart
>> 
>> to restart my Apache2 server. Is that what do you mean?
>> 
>
> ..yes.  (I usually do that as root, rather than go the sudo route.)

Well, it seems to me that Horde3 on Debian Squeeze is unusable, isn't?

-- 
Regards from Pal


-- 
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/87boprpkfl.fsf@debian-asztal.excito

KVM virtualisation

[James Allsopp]

Hi,
I'm having trouble building a kvm virtual machine, The script I'm using 
to build this is:

#!/bin/bash
virt-install \
--connect qemu:///system \
-n deb1 \
-r 512 \
--vcpus=1 \
--os-variant=debiansqueeze \
--accelerate \
-v \
-c /var/lib/libvirt/images/debian-6.0.3-amd64-netinst.iso \
-w bridge:br0 \
--vnc \
--disk path=/var/lib/libvirt/images/debiantest.img,size=4


but when I run I get the following error, I've tried to debug this 
afterwards;


awaiian:/home/ja/vm_kvm# ./kvmInstall


Starting install...
Allocating 'debiantest.img'  | 4.0 GB 
00:00
Creating domain...   |0 B 
00:00

Cannot open display:
Run 'virt-viewer --help' to see a full list of available command line 
options

Domain installation does not appear to have been
 successful.  If it was, you can restart your domain
 by running 'virsh start deb1'; otherwise, please
 restart your installation.
Hawaiian:/home/ja/vm_kvm# virsh start deb1
error: failed to get domain 'deb1'
error: Unknown failure

Hawaiian:/home/ja/vm_kvm# virsh
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
   'quit' to quit

virsh # nodeinfo
CPU model:   x86_64
CPU(s):  2
CPU frequency:   2000 MHz
CPU socket(s):   1
Core(s) per socket:  2
Thread(s) per core:  1
NUMA cell(s):1
Memory size: 4061292 kB

virsh # list --al
error: command 'list' doesn't support option --al
virsh # list --all
 Id Name State
--

virsh # net-list --all
Name State  Autostart
-
vboxnet0 inactive   no autostart

virsh # net-edit default
error: failed to get network 'default'
error: Unknown failure

virsh # quit

Hawaiian:/home/ja/vm_kvm# virsh
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
   'quit' to quit

virsh # net-autostart default
error: failed to get network 'default'
error: Unknown failure



If anyone can offer me any help on how to fix this I'd be really grateful,

James


--
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/4f2062b3.8030...@googlemail.com

Re: issue with mdadm and mirroring drives

[tv.deb...@googlemail.com]

25/01/2012 19:16, Joey L wrote:

In-line reply ;

> Okay..I am telling all in this email -:)
> 
> My configuration is as such:
> /dev/md0 = /dev/sdc1 and /dev/sdd1
> /dev/md1 = /dev/sda1 and /dev/sb1
> 
> My swap partitions are not part of the array or mirror  at all -
> they are just regular partitions - they are:
> /dev/sdc2 and /dev/sdd2.

Any particular reason do do that ? If you want your system/applications
to carry on working if a disk fails you need the swap on raid1 too.

> 
> When I boot the system with all drives in, I get the superflous error.
> 
> So the only way to boot is only to put in /dev/sdc alone and boot.
> when i get to a linux prompt, I insert the second drive into the system 
> /dev/sdd
> 
> To sync them, /dev/sdd has already failed, so i run
> sfdisk -d /dev/sdc | sfdisk /dev/sdd
> ** i get an error that nothing has changed - so I run it with the
> --force command to get the partitions identical like:
> sfdisk -d /dev/sdc | sfdisk --force /dev/sdd

Why do you do that ? You are forcing the partitioning of the first disk
onto the second, this could work at raid creation time but isn't the
proper procedure to re-add a failed member to an array. You don't have
to "sync" the data and even less the disk partitioning manually prior to
re-adding it to the raid. mdadm will handle the resync.

> 
> Once that is successful - i run mdadm --manage /dev/md0 --add /dev/sdd1
> 
> And the sync process starts, and when it is done yesterday, I ran this
> and got these errors:
> 
> 
> root@rider:~# grub-install --recheck --no-floppy /dev/sdc
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> Installation finished. No error reported.
> root@rider:~# grub-install --recheck --no-floppy /dev/sdd
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> Installation finished. No error reported.
> root@rider:~# grub-install --recheck --no-floppy /dev/sdc
> 
> 
[cut]
> 
> 
> My parted -l is:
> 
> 
> Model: ATA ST31000340AS (scsi)
> Disk /dev/sda: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> 
> Number  Start   End SizeType File system  Flags
>  1  32.3kB  1000GB  1000GB  primary  ext3 raid
> 
> 
> Model: ATA ST31000340AS (scsi)
> Disk /dev/sdb: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> 
> Number  Start   End SizeType File system  Flags
>  1  32.3kB  1000GB  1000GB  primary  ext3 raid
> 
> 
> Model: ATA ST31000340AS (scsi)
> Disk /dev/sdc: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> 
> Number  Start   End SizeType File system Flags
>  1  1049kB  996GB   996GB   primary  ext3raid
>  2  996GB   1000GB  4204MB  primary  linux-swap(v1)
> 
> 
> Model: ATA ST31000528AS (scsi)
> Disk /dev/sdd: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> 
> Number  Start   End SizeType File system Flags
>  1  1049kB  996GB   996GB   primary  ext4raid
>  2  996GB   1000GB  4204MB  primary  linux-swap(v1)
> 

Why do you have file-systems on your partitions ? Only the "md" raid
devices should be formatted with a file-system, not the underlying
partitions !
I would be curious to know what "fsck" says about your md devices (fsck
/dev/md0 for example) ?



> Warning: Unable to open /dev/fd0 read-write (Read-only file system).  /dev/fd0
> has been opened read-only.
> 
> Error: /dev/fd0: unrecognised disk label
> 
> Model: Linux Software RAID Array (md)
> Disk /dev/md0: 996GB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
> 
> Number  Start  EndSize   File system  Flags
>  1  0.00B  996GB  996GB  ext4
> 
> 
> Model: Linux Software RAID Array (md)
> Disk /dev/md1: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
> 
> Number  Start  End SizeFile system  Flags
>  1  0.00B  1000GB  1000GB  ext4
> 
> 
> 
[cut]
> 
> 
> 
> I am currently terrified to reboot my box --- any help would be appriciated -
> 
> I have NOT run the command "update-initramfs -u -k all  "  and do not
> know if i should.
> 
> 
> thanks
> mjh

You seem to be walking in the dark awaiting to hit the next pole ;-) .
Updating the initrd won't solve file-system or raid inconsistencies, it
would only be necessary if the content of mdadm.conf had changed.

I am starting to think that you have much lower level problems. When you
created this system, where the disks "clean", or did you use "sfdisk"
over existing formatted partitions ? Where the disks used in a raid
before ? If this is the case you should consider backing up and
recreatin

Re: Wheezy. Weekly build 23-Jan-2012. "No kernel modules were found" during install.

[Jan Harnisch]

Same problem here. After receiving the error, at first it seems possible 
to continue the installation (as long as one doesn't need the network 
card). However when entering partman, there seems to be no way to assign 
a mountpoint to any partition.

The only workaround I found so far is this one:
www.linuxquestions.org/questions/debian-26/wheezy-netinst-iso-installation-problem-921825/
Best regards

Jan


--
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/4f208227.9000...@bnhof.de

Re: Blank screen at boot with kernel 3.1

[Tom H]

On Wed, Jan 25, 2012 at 3:09 PM, Sven Joachim  wrote:
> On 2012-01-25 20:38 +0100, Rémi Moyen wrote:
>> Le 25 janvier 2012 18:10, Sven Joachim  a écrit :
>>> On 2012-01-25 18:04 +0100, Rémi Moyen wrote:

 Kernel 3.2 seems to be still in unstable, I'd rather not install
 something from there if I can avoid it.
>>>
>>> No, 3.2 has been in testing for six days, 3.1 is not supported anymore.
>>
>> But linux-image-am64 still seems to be in version 3.1 and depends from
>> linux-image-3.1.0-1-amd64?
>
> The metapackage has not yet migrated, it seems. But 3.1 really is not
> supported anymore, neither by Debian nor by upstream.

This can't be. I installed a testing box and upgraded it to unstable
today and I have both 3.1 and 3.2 installed - and they're both still
available in the repos.

# tune2fs -l /dev/sda2 | grep created
Filesystem created:   Wed Jan 25 03:35:13 2012
#
# aptitude search linux-image -F '%p %t %v %V'
linux-image
   
linux-image-2.6-486
unstable3.2+42
linux-image-2.6-686
unstable3.2+42
linux-image-2.6-686-bigmem
unstable3.2+42
linux-image-2.6-686-pae
unstable3.2+42
linux-image-2.6-amd64
unstable3.2+42
linux-image-3.1.0-1-486
testing 3.1.8-2
linux-image-3.1.0-1-686-pae
testing3.1.8-23.1.8-2
linux-image-3.1.0-1-686-pae-dbg
testing 3.1.8-2
linux-image-3.1.0-1-amd64
testing 3.1.8-2
linux-image-3.2.0-1-486
unstable3.2.1-2
linux-image-3.2.0-1-686-pae
unstable   3.2.1-23.2.1-2
linux-image-3.2.0-1-686-pae-dbg
unstable3.2.1-2
linux-image-3.2.0-1-amd64
unstable3.2.1-2
linux-image-486
unstable3.2+42
linux-image-686
unstable3.2+42
linux-image-686-bigmem
unstable3.2+42
linux-image-686-pae
unstable3.2+42
linux-image-amd64
unstable3.2+42


--
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/CAOdo=sxvp2psz_mdrk1iwvykf2sjguddlfbwbx6aqxj3v1e...@mail.gmail.com

Re: NIC transferring twice its max rate

[Chris Davies]

Rob Owens  wrote:
> I've got an onboard NIC, supposedly 100Mb.
> [...]
> I've got gigabit networking between the two computers

So do you have 1Gb or 100Mb connectivity?
CHris


-- 
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/fce6v8xtjj@news.roaima.co.uk

duplicity backups are unidirectional? : local_directory -> remote_host

[Evuraan]

duplicity full [options] source_directory target_url


Duplicity  enters  restore  mode if it sees  the "URL"  before  the
local  directory. - this sorta sucks as this mandates the "source" to
be a local directory - means I can backup "this" machine's stuff
elsewhere using duplicity. If i wanted to go the other way, ie, backup
that remote machines' folder onto this machine using duplicity, it
FAILS.

$ duplicity full scp://user@host1//etc/xml  /tmp/aa
Command line error: --full option cannot be used when restoring or verifying


otoh, rdiff-backup

rdiff-backup [options]  
Where both  and  can be local or remote - yay! - but
lack of encryption and stuff is making it less desired for me.


Any suggestions?


Many thanks in advance!


-- 
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/CA+jJSoTvYo-R2RBo1--DdsEg+RNsyj=3gavuehsjpdlxgd5...@mail.gmail.com

Re: Kernel Compiling from scratch

[Stephen Powell]

On Wed, 25 Jan 2012 15:21:46 -0500 (EST), Syed Hasan Atizaz wrote:
> 
> I am able to compile the kernel for i386, however no initial ram disk
> image is created, i did with the help of mkinitramfs though it was
> empty, still unable to boot.

Did you use the --initrd option when you invoked make-kpkg?
The initial ram disk image is not created until the kernel image
package is installed, but if you did not use the --initrd option
when you invoked make-kpkg then when you install the kernel image
package an initial ram disk image will not be created.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/155064544.705050.1327534682602.javamail.r...@md01.wow.synacor.com

Re: Blank screen at boot with kernel 3.1

[Rémi Moyen]

Le 25 janvier 2012 20:09, Sven Joachim  a écrit :

>> I don't want to nominally install the 3.2
>> kernel, I only want the latest one, so I think I'll stick to
>> linux-image-amd64 and wait until that updates to 3.2. Should be quite
>> soon, I guess.
>
> As long as you don't have untrusted users on your system, a local root
> exploit might not scare you much.  And since you're willing to use a
> proprietary kernel module for which nobody knows what nasty things it
> might do, security probably does not really matter.

Well, let's say that the first thing I did after installing kdm was to
enable auto-login on my user, so yes, local security is not really a
concern for me (anyway, it's a home computer and anyone that could get
to a login screen would be physically sitting in front of it, so they
could boot on whatever live CD they'd like. So again, local security
is definitely not a concern for me).

> X does not know about that parameter, so it will try to load nouveau
> unless you specify a driver in xorg.conf.  But
>
> a) you have to specify the nvidia driver anyway if you want to use it;
>
> b) the only ill effect would be an error message in Xorg's log.

You are right, on both counts. The X installation went fine, except
that I had to write a minimal xorg.conf file to force it to use the
nvidia module (a). And yes, I also get an error message (actually, a
warning) in the log (b).

But the system seems to be working perfectly, so now I'm just left to
copy my files and fine tune the install.

Thanks again for the help!
-- 
Rémi Moyen


--
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/CAOBzH+k3e4RAmmvQF5nTgmGijopbcb=rxuf7mqfhvra3trg...@mail.gmail.com

Fwd: Mr. Geissert "Need Some Help" Debian GNU/Linux unstable "Sid" - Official Snapshot amd64 LIVE/NETINST Binary 20090704-21:29

[Raphael Geissert]

--  Forwarded Message  --

Subject: Mr. Geissert "Need Some Help" Debian GNU/Linux unstable "Sid" - 
Official Snapshot amd64 LIVE/NETINST Binary 20090704-21:29
Date: Wednesday 25 January 2012, 17:08:36
From: maujhsn <1037302...@gmail.com>
To: geiss...@debian.org

I downloaded this verson of lenny!

Debian GNU/Linux unstable "Sid" - Official Snapshot amd64 LIVE/NETINST
Binary 20090704-21:29

I realized that this CD that I downloaded has not bene authenticated by me!

When I go to "etc/apt/sources.list" I get this list of repositories:


deb http://ftp.us.debian.org/debian/ sid main contrib non-free

# Custom repositories
deb http://www.debian-multimedia.org/ sid main
deb http://www.debian-multimedia.org/ testing main
deb http://live.debian.net/debian/ ./

When I boot into the CD I go directly to "LIVE"!

What directory & folder will show me the MD5SUM so that I can verify
this CD with gpg or the --keyserver?
Thanks,

M J

-
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


-- 
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/201201251806.06858.geiss...@debian.org

Re: issue with mdadm and mirroring drives

[Tom H]

On Wed, Jan 25, 2012 at 5:35 PM, tv.deb...@googlemail.com
 wrote:
> 25/01/2012 19:16, Joey L wrote:


>> Okay..I am telling all in this email -:)
>>
>> My configuration is as such:
>> /dev/md0 = /dev/sdc1 and /dev/sdd1
>> /dev/md1 = /dev/sda1 and /dev/sb1
>>
>> My swap partitions are not part of the array or mirror  at all -
>> they are just regular partitions - they are:
>> /dev/sdc2 and /dev/sdd2.
>
> Any particular reason do do that ? If you want your system/applications
> to carry on working if a disk fails you need the swap on raid1 too.

+1


>> When I boot the system with all drives in, I get the superflous error.
>>
>> So the only way to boot is only to put in /dev/sdc alone and boot.
>> when i get to a linux prompt, I insert the second drive into the system 
>> /dev/sdd
>>
>> To sync them, /dev/sdd has already failed, so i run
>> sfdisk -d /dev/sdc | sfdisk /dev/sdd
>> ** i get an error that nothing has changed - so I run it with the
>> --force command to get the partitions identical like:
>> sfdisk -d /dev/sdc | sfdisk --force /dev/sdd
>
> Why do you do that ? You are forcing the partitioning of the first disk
> onto the second, this could work at raid creation time but isn't the
> proper procedure to re-add a failed member to an array. You don't have
> to "sync" the data and even less the disk partitioning manually prior to
> re-adding it to the raid. mdadm will handle the resync.

It's unorthodox but it's a replacement of zeroing the superblock with
mdadm before adding the partition back to into the array.


>> Once that is successful - i run mdadm --manage /dev/md0 --add /dev/sdd1
>>
>> And the sync process starts, and when it is done yesterday, I ran this
>> and got these errors:
>>
>> root@rider:~# grub-install --recheck --no-floppy /dev/sdc
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> Installation finished. No error reported.
>> root@rider:~# grub-install --recheck --no-floppy /dev/sdd
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> error: superfluous RAID member (2 found).
>> Installation finished. No error reported.

There are a few bugs on b.d.o that correspond to this error but none
that fit your case, AFAICT. "grub-install" does say "Installation
finished. No error reported."

You could check whether grub's OK via bootinfoscript (although the
only real test'll be a reboot...).

http://sourceforge.net/projects/bootinfoscript/


>> My parted -l is:
>>
>> Disk /dev/sda: 1000GB
>> Number  Start   End     Size    Type     File system  Flags
>>  1      32.3kB  1000GB  1000GB  primary  ext3         raid
>>
>> Disk /dev/sdb: 1000GB
>> Number  Start   End     Size    Type     File system  Flags
>>  1      32.3kB  1000GB  1000GB  primary  ext3         raid
>>
>> Disk /dev/sdc: 1000GB
>> Number  Start   End     Size    Type     File system     Flags
>>  1      1049kB  996GB   996GB   primary  ext3            raid
>>  2      996GB   1000GB  4204MB  primary  linux-swap(v1)
>>
>> Disk /dev/sdd: 1000GB
>> Number  Start   End     Size    Type     File system     Flags
>>  1      1049kB  996GB   996GB   primary  ext4            raid
>>  2      996GB   1000GB  4204MB  primary  linux-swap(v1)
>
> Why do you have file-systems on your partitions ? Only the "md" raid
> devices should be formatted with a file-system, not the underlying
> partitions !

sdc1 is ext3 and sdd1 is ext4; somehow.


--
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/CAOdo=szbcqu8tasyn1_ycn2+huzkkth4hm2smqh5m+iecb+...@mail.gmail.com

Re: duplicity backups are unidirectional? : local_directory -> remote_host

[Andrew Reid]

[About remote back-ups w/ duplicity vs. rdiff-backup]

  I am unfamiliar with duplicity, but use rdiff-backup regularly,
as well an rsync/rsnapshot combination.

  One thing that I like to do is to separate the remote transport
from the actual back-up process -- there can be performance penalties
for this, but it gives you better control.

  For instance, since you mentioned encryption, for your first
scenario, you could make an sshfs mount of the remote filesystem 
on the back-up host, and then run duplicity (or another tool) in
local-to-local mode.
  The performance penalty arises because the back-up tool now
has to scan the source file system for changes over the 
network link, rather than running a daemon at the far end
to scan it locally.  Depending on the speed of your link
and the size of your filesystem, this may or may not be
a problem. 

  I do this in production (with rdiff-backup, not duplicity) with 
a machine that actually backs up from a remote to a different 
remote -- the "source" remote is a read-only NFS mount, which
therefore appears local, and the "target" remote is an iSCSI 
target on a storage appliance, which also appears local.  
The performance penalty is real, but it works for me.

-- A.
--
Andrew Reid / rei...@bellatlantic.net


-- 
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/201201252345.50383.rei...@bellatlantic.net

Re: Blank screen at boot with kernel 3.1

[Sven Joachim]

On 2012-01-25 23:51 +0100, Tom H wrote:

> On Wed, Jan 25, 2012 at 3:09 PM, Sven Joachim  wrote:
>>
>> The metapackage has not yet migrated, it seems. But 3.1 really is not
>> supported anymore, neither by Debian nor by upstream.
>
> This can't be. I installed a testing box and upgraded it to unstable
> today and I have both 3.1 and 3.2 installed - and they're both still
> available in the repos.

3.1 kernels may still be available, but that does mean they are
supported.  There is a local root exploit that will not be fixed in the
3.1 series, move on to 3.2 already!

Sven


-- 
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/87pqe7vu2e@turtle.gmx.de