Re: A USB HDD is trouble outbreak in debian7.7

[kinneko]

Hi, all.

I think, the hardware of GLANTANK is obsolete.
The useful life of this product was end.
XScale can't get support of Intel and no one maintains that.

Intel XScale IOP Linux
http://xscaleiop.sourceforge.net/
http://sourceforge.net/projects/xscaleiop/files/

MAKAI is unrelated to NAS and ARM.
MAKAI is self-rebuildable LiveCD project.
MAKAI supports x86, ONLY.
It's Minimal system and not include NAS manager.

This problem seems to have 2 problems.
- XScale: The DMA function of XScale is not good. Intel failed to support it.
- Hard drive: There may be also a problem with function of a JBOD controller.


2015-01-06 9:43 GMT+09:00 Joel Rees :
> GLANTANK is a gigabit version of LANTANK. IO-DATA's child company
> Chousensha (Challenger) produced these in response to the Kurobako
> (with which some here may be familiar).
>
> http://ja.wikipedia.org/wiki/GLAN_Tank
> http://translate.google.co.jp/translate?hl=en&sl=ja&u=http://ja.wikipedia.org/wiki/GLAN_Tank&prev=search
>
> http://ja.wikipedia.org/wiki/LAN_Tank
> http://translate.google.co.jp/translate?hl=en&sl=ja&u=http://ja.wikipedia.org/wiki/GLAN_Tank&prev=search
>
> These are customizable NAS units, apparently running a customized
> debian (MAKAI -- MAKe Again ISO Image) internally.
>
> http://makai.sourceforge.jp/wiki/index.php?FrontPage
> http://translate.google.co.jp/translate?hl=en&sl=ja&u=http://ja.wikipedia.org/wiki/GLAN_Tank&prev=search
>
> LANTANK had an SH4 cpu, but the GLANTANK has an ARM (XScale).
>
> On Mon, Jan 5, 2015 at 9:22 AM, Jun Itou  wrote:
>> I managed debian 7 by the following constitution.
>>
>>   Body) I-O DATA GLANTANK 2.0TB (500GB * 4 RAID0, iop32x)
>>   USB1) I-O DATA HDZ-UES  2.0TB (500GB * 4 JBOD)
>>   USB2) I-O DATA HDZ-UES  1.0TB (250GB * 4 JBOD)
>>   USB3) I-O DATA HDZ-UES  1.0TB (250GB * 4 JBOD)
>>   USB4) I-O DATA HDW-UE   1.0TB (500GB * 2 JBOD)
>>
>> After making 7.7 from debian 7.6, malfunction occurred.
>>
>>   1) A sector error occurs when I do mount and becomes the lead only
>>   2) I fail in synchronization of the file system when I do fdisk
>>
>> I gave following tests to cut a problem into pieces.
>>
>>   1) I do operation same as GLANTANK in x64 environment whether it is a 
>> problem of the hardware.
>> -> Because the same problem occurs with both, it is not peculiar to 
>> hardware.
>>
>>   2) I confirm whether it is the problem of the HDD of USB1 - 4 with the 
>> test tool of the HDD maker.
>> -> Because the HDD of all passed a test, it is not a problem of USB1 - 4.
>>
>>   3) I do the same operation in Fedora whether it is a problem peculiar to 
>> debian.
>> -> Because it reappeared in Fedora, I conclude it to be a problem of 
>> kernel.
>>
>>   4) I change a version of kernel on debian and do the same operation.
>> -> 3.2.62   : It does not reappear
>>3.2.63 ~ : Reappear
>>3.18.0 ~ : Reappear
>>
>>   5) I report it to kernel.org and do the same operation after enforcement 
>> in the end run which there was of the answer.
>> -> Please refer to https://bugzilla.kernel.org/show_bug.cgi?id=89511.
>
> The summary here is that the GLANTANK seems not to like the
> SYNCHRONIZE CACHE command.
>
> 話をまとめると GLANTANK が SYNCHRONIZE CACHE の命令に応じないようです。
>
> https://bugzilla.kernel.org/show_bug.cgi?id=89511#c35
>
> Alan Stern says that the kernel should be able to handle this in 3.18
> or later, but Jun indicates that 3.18 does not handle it yet.
>
> スターン氏によると、カーネルの 3.18 なら対処できるであろう、ということでした。その反面、 JunItou の結果はそうではなかった。
>
>> It is to say that my USB HDD cannot support the change of this journal 
>> function in conclusion.
>> I make kernel latest or seem to but make a USB HDD a different one if I 
>> continue managing it by the present constitution.
>>
>> I knew that it was not developed debian 8 for GLANTANK by a document.
>> Because there is no help for it, I think to manage it without formating 
>> ext2, and using the journal function.
>>
>> ※In addition, one of file system is destroyed when an error happens as for 
>> this malfunction even once.
>>   I hope that it reappears and is not given a test with the contained HDD of 
>> important data.
>>
>> ※Because the funny grammar is machine translation; a pardon
>>
>> That's all.
>
> I'm thinking that the best place to fix this would be in the MAKAI
> community, but, as I check back in the Japanese list from last month,
> it looks like Jun has already tried contacting them. And that
> community seems to be an abandoned sourceforge.jp project, completely
> untouched since 2010. And the Makai project doesn't seem to have a
> place to post bugs.
>
> https://lists.debian.org/debian-japanese/2014/12/msg3.html
>
> 簡単に考えたら、 
> MAKAIのコミュニティに連絡した方が速い、かな？と思うけど、先月の日本のメールリスとを見直したら、もう、連絡されているのではないですか？それに、2010年からはプロジェクトが完全ほったらかしの様子ですね。さらに、バッグの窓口がなさそうです。
>
> it appears that last month I seem to have found something that made it
> look to me like the once-maintainer of MAKAI, kin-neko, has
> more-or-less washed his hands of a ten-year-old project tha

Re: HTML viewer

[Emil Oppeln-Bronikowski]

w3m, links or elinks. With w3m being the most pager-like. 
-- 
Łażę gdzieś, pisząc ten e-mail na telefonie. 

HTML viewer

[Frank]

I am looking for a simple HTML viewer I can use under MC to read HTML 
docs. I have Dillo installed but even it seems overkill for what I need. 
Does anyone have suggestions ?


Thanks


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54ab32e...@videotron.ca

Re: A USB HDD is trouble outbreak in debian7.7

[Joel Rees]

GLANTANK is a gigabit version of LANTANK. IO-DATA's child company
Chousensha (Challenger) produced these in response to the Kurobako
(with which some here may be familiar).

http://ja.wikipedia.org/wiki/GLAN_Tank
http://translate.google.co.jp/translate?hl=en&sl=ja&u=http://ja.wikipedia.org/wiki/GLAN_Tank&prev=search

http://ja.wikipedia.org/wiki/LAN_Tank
http://translate.google.co.jp/translate?hl=en&sl=ja&u=http://ja.wikipedia.org/wiki/GLAN_Tank&prev=search

These are customizable NAS units, apparently running a customized
debian (MAKAI -- MAKe Again ISO Image) internally.

http://makai.sourceforge.jp/wiki/index.php?FrontPage
http://translate.google.co.jp/translate?hl=en&sl=ja&u=http://ja.wikipedia.org/wiki/GLAN_Tank&prev=search

LANTANK had an SH4 cpu, but the GLANTANK has an ARM (XScale).

On Mon, Jan 5, 2015 at 9:22 AM, Jun Itou  wrote:
> I managed debian 7 by the following constitution.
>
>   Body) I-O DATA GLANTANK 2.0TB (500GB * 4 RAID0, iop32x)
>   USB1) I-O DATA HDZ-UES  2.0TB (500GB * 4 JBOD)
>   USB2) I-O DATA HDZ-UES  1.0TB (250GB * 4 JBOD)
>   USB3) I-O DATA HDZ-UES  1.0TB (250GB * 4 JBOD)
>   USB4) I-O DATA HDW-UE   1.0TB (500GB * 2 JBOD)
>
> After making 7.7 from debian 7.6, malfunction occurred.
>
>   1) A sector error occurs when I do mount and becomes the lead only
>   2) I fail in synchronization of the file system when I do fdisk
>
> I gave following tests to cut a problem into pieces.
>
>   1) I do operation same as GLANTANK in x64 environment whether it is a 
> problem of the hardware.
> -> Because the same problem occurs with both, it is not peculiar to 
> hardware.
>
>   2) I confirm whether it is the problem of the HDD of USB1 - 4 with the test 
> tool of the HDD maker.
> -> Because the HDD of all passed a test, it is not a problem of USB1 - 4.
>
>   3) I do the same operation in Fedora whether it is a problem peculiar to 
> debian.
> -> Because it reappeared in Fedora, I conclude it to be a problem of 
> kernel.
>
>   4) I change a version of kernel on debian and do the same operation.
> -> 3.2.62   : It does not reappear
>3.2.63 ~ : Reappear
>3.18.0 ~ : Reappear
>
>   5) I report it to kernel.org and do the same operation after enforcement in 
> the end run which there was of the answer.
> -> Please refer to https://bugzilla.kernel.org/show_bug.cgi?id=89511.

The summary here is that the GLANTANK seems not to like the
SYNCHRONIZE CACHE command.

話をまとめると GLANTANK が SYNCHRONIZE CACHE の命令に応じないようです。

https://bugzilla.kernel.org/show_bug.cgi?id=89511#c35

Alan Stern says that the kernel should be able to handle this in 3.18
or later, but Jun indicates that 3.18 does not handle it yet.

スターン氏によると、カーネルの 3.18 なら対処できるであろう、ということでした。その反面、 JunItou の結果はそうではなかった。

> It is to say that my USB HDD cannot support the change of this journal 
> function in conclusion.
> I make kernel latest or seem to but make a USB HDD a different one if I 
> continue managing it by the present constitution.
>
> I knew that it was not developed debian 8 for GLANTANK by a document.
> Because there is no help for it, I think to manage it without formating ext2, 
> and using the journal function.
>
> ※In addition, one of file system is destroyed when an error happens as for 
> this malfunction even once.
>   I hope that it reappears and is not given a test with the contained HDD of 
> important data.
>
> ※Because the funny grammar is machine translation; a pardon
>
> That's all.

I'm thinking that the best place to fix this would be in the MAKAI
community, but, as I check back in the Japanese list from last month,
it looks like Jun has already tried contacting them. And that
community seems to be an abandoned sourceforge.jp project, completely
untouched since 2010. And the Makai project doesn't seem to have a
place to post bugs.

https://lists.debian.org/debian-japanese/2014/12/msg3.html

簡単に考えたら、 
MAKAIのコミュニティに連絡した方が速い、かな？と思うけど、先月の日本のメールリスとを見直したら、もう、連絡されているのではないですか？それに、2010年からはプロジェクトが完全ほったらかしの様子ですね。さらに、バッグの窓口がなさそうです。

it appears that last month I seem to have found something that made it
look to me like the once-maintainer of MAKAI, kin-neko, has
more-or-less washed his hands of a ten-year-old project that never
developed a self-sustaining community. I don't remember where I found
that, however.

先月の投稿に、僕がどこかで見つけた情報のため、 MAKAI管理者の kinneko
は十年前の世界の遺跡のように、手放しの姿勢となっているように思いました。コミュニティが成立できなかったためでしょう。ただし、その情報はどこで手に入れたかは覚えていません。

Anybody here in user, arm, or embedded (or d-japanese) have a suggestion?

Joel Rees

Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAAr43iOLR5ibR-VFQE4gx9afV3gWMm+kHT=suesylrvd1gm...@mail.gmail.com

Re: Late authentication

[Gary Dale]

On 05/01/15 04:40 PM, Andrei POPESCU wrote:

On Du, 04 ian 15, 17:02:12, August Karlstrom wrote:

I run Debian Wheezy with a simple window manager (Blackbox). If I remember
correctly, in Ubuntu some applications like Synaptic and Update Manager ask
for sudo password only when/if needed.

How do I configure the system so I can launch for instance Update Manager as
normal user, check if there are any updates available and then provide the
sudo password only if the system is to be updated? As Far as I understand
the authentication is handled by Polkit.

Not sure about Update Manager, but both apt(-get) and aptitude require
root privileges to update their information about packages available in
the repositories (which is required to determine if any updates are
available).

One possible way around it would be to do the update via something like
cron-apt, apticron, unattended-upgrades, etc. Those tools also do inform
you if updates are available ;)

Kind regards,
Andrei
For a while I was getting a notice every morning that there were updates 
waiting. I gather that this was something that was being tested in 
Jessie then removed. Anyway, having apt-get update run as cron job as 
root certainly does the trick and KDE (at least) shows a notification 
when updates are available.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54ab0faa.4060...@torfree.net

Re: Late authentication

[Andrei POPESCU]

On Du, 04 ian 15, 17:02:12, August Karlstrom wrote:
> I run Debian Wheezy with a simple window manager (Blackbox). If I remember
> correctly, in Ubuntu some applications like Synaptic and Update Manager ask
> for sudo password only when/if needed.
> 
> How do I configure the system so I can launch for instance Update Manager as
> normal user, check if there are any updates available and then provide the
> sudo password only if the system is to be updated? As Far as I understand
> the authentication is handled by Polkit.

Not sure about Update Manager, but both apt(-get) and aptitude require 
root privileges to update their information about packages available in 
the repositories (which is required to determine if any updates are 
available).

One possible way around it would be to do the update via something like
cron-apt, apticron, unattended-upgrades, etc. Those tools also do inform 
you if updates are available ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Late authentication

[Bob Proulx]

August Karlstrom wrote:
> I run Debian Wheezy with a simple window manager (Blackbox). If I remember
> correctly, in Ubuntu some applications like Synaptic and Update Manager ask
> for sudo password only when/if needed.
> 
> How do I configure the system so I can launch for instance Update Manager as
> normal user, check if there are any updates available and then provide the
> sudo password only if the system is to be updated? As Far as I understand
> the authentication is handled by Polkit.

That is really harder to do than it sounds.  The problem is that you
don't know if you need root until you need it and not before.  So you
don't know if you need to use sudo until it is too late.

Just an idea...

It would probably be possible to run apt-get --simulate and see what
it wants to do.  If it doesn't want to upgrade anything then stop
there and do nothing.  But if the simulation wants to upgrade
something then fire it for effect with sudo as a second pass.

Bob


signature.asc
Description: Digital signature

Re: apache fastcgi trouble with Apache/2.2.22

[Jochen Spieker]

Hi Bob,

I am sending this to both the list and your mail address in case you are
not subscribed.

Bob:
> 
> Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that 
> RewriteRule directive is forbidden: /usr/lib/cgi-bin/php55-cgi

You already posted about a (suspected) other problem with the exact same
error message. My reply is here:

https://lists.debian.org/debian-user/2015/01/msg00106.html
| AFAICT, this error is completely unrelated to PHP. My guess would be
| that Apache doesn't read your .htaccess file and your settings aren't
| applied. Since you appear to have access to the Apache configuration,
| you should just add the directives from the .htaccess file to the
| appropriate VirtualHost section.

Does this help you?

J.
-- 
Watching television is more hip than actually speaking to anyone.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: multiple versions of python

[Boruch Baum]

Thanks, Stanley!


On 01/04/2015 10:32 AM, Stanley C. Kitching wrote:
> 
> 
>> 
>> 1] Can I have multiple versions of python simultaneously?
>> 
> 
>   yes
> 
>   Using Debian Wheezy I have 3 python versions installed
> 
> # ls -1 /usr/lib | grep python | grep -v lib
> 
> python
> python2.6
> python2.7
> python3
> python3.2
> 
> python  is python2.7
> python3 is python3.2
>   
> ===
> 
>> 2] Is there a way to specify that one package 
>> use a non-default version of python ? 
>> 
> 
>   yes
> 
>   Use the specific python version name
>   when starting your program
> 
> pythonX.Y /path/to/zProgram.py
> 
>   For example, I have a small program
>   that only prints the current python version
>   that it has been started with  
> 
>   $ python $p/amisc/version.py
> 
>   python version  2.7.3
> 
>   $ python2.6 $p/amisc/version.py
> 
>   python version  2.6.8
>  
>   $ python2.7 $p/amisc/version.py
> 
>   python version  2.7.3
> 
>   $ python3 $p/amisc/version.py
> 
>   python version  3.2.3
> 
>   $ python3.2 $p/amisc/version.py
> 
>   python version  3.2.3
> 
> 
>   Using the name python is the same 
>   as using the name python2.7
> 
> python2.7 is the default version
> 
>   Using the name python3 is the same
>   as using the name python3.2
> 
> ===
> 
>> 3] Is this a quick, straightforward install ? 
>> 
> 
>   yes
> 
>   Use the Debian package manager
>   to install the different python versions
> 
>   # sudo apt-get install python
> 
>   # sudo apt-get install python3
> 
>   If you start your python programs
>   using specific python version names
>   nothing else should be necessary 
> 
> 


-- 
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54aaba4d.4000...@gmx.com

apache fastcgi trouble with Apache/2.2.22

[Bob]

Dear list,

has anyone successfully run fastcgi with Apache/2.2.22 on debian wheezy ?
I need your kind help to make it working..

I have already the required modules running namely [ actions alias fastcgi ]
I also have the following wrapper script with execute permission 
/usr/lib/cgi-bin/php55-cgi


#!/bin/bash
PHP_FCGI_CHILDREN=10
export PHP_FCGI_CHILDREN
PHP_FCGI_MAX_REQUESTS=5000
export PHP_FCGI_MAX_REQUESTS
exec /usr/local/bin/php-5.5.20/bin/php-cgi -c 
/usr/local/bin/php-5.5.20/lib/php.ini 

``

Now If I place the below at .htaccess


Options +FollowSymLinks +SymLinksIfOwnerMatch +ExecCGI

RewriteEngine On


SetHandler application/x-httpd-php5


``

I get error as 

`
Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that 
RewriteRule directive is forbidden: /usr/lib/cgi-bin/php55-cgi

`

Placing same at vhost throws same error though rewrite module is loaded... Have 
I missed anything ?
Kindly suggest.

Thanks


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150105153200.357f2...@shiva.selfip.org

Kernel panic and shutdown

[Eric Offermann]

I have an i7-3612Qe system that has been giving kernel panics when running a 
custom video streaming application pretty consistently after a couple minutes.  
After the kernel panic, the machine reboots.  When I turn off turbo mode in the 
BIOS, the panics happen less frequently.  Other BIOS settings are all default, 
no overclocking or anything fancy.



-Can be reproduced by running streaming application using ~250% CPU, temps are 
a little high, they float around 68-71 degrees

-sysbench runs fine with 8 threads, throttles CPU up to ~800%, no kernel 
panics, temps remain below 70 degrees

-MemTest did not report any errors

-Intel Processor Diagnotic tool passed

-Tried swapping RAM

-Reproducible on multiple machines, not just a single processor (possibly 
eliminates it being a bad single proc)



-Able to mitigate most of the kernel panics and reboots by disabling Turbo mode 
(this is unacceptable, just including this for debugging purposes)

-Also able to mitigate kernel panics and reboots by changing the cpu frequency 
sacling_governor to conservative, from ondemand.  Conservative should 
"gracefully increase and decreases the CPU speed rather than jumping to max 
speed the moment there is any load on the CPU" 
(https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt)



Here is what I could copy down from the kernel panic on the monitor, sometimes 
the messages vary slightly, bu the TSC and PROCESSOR messages are almost always 
the same.



[Hardware Error]:  TSC 6e496d96062

[Hardware Error]:  PROCESSOR 0:306a9 TIME 1418929330 SOCKET 0 APIC 3 microcode 
12

[Hardware Error]:  Run the above through 'mcelog --ascii'

[Hardware Error]:  CPU 0: Machine Check Exception: 5 Bank 4: b2100402

[Hardware Error]:  RIP !INEXACT! 10: {intel_idle+0xb9/0x119}

[Hardware Error]:  TSC 148c99828a0

[Hardware Error]:  PROCESSOR 0:306a9 TIME 1418929330 SOCKET 0 APIC 3 microcode 
12

[Hardware Error]:  Run the above through 'mcelog --ascii'

[Hardware Error]:  Some CPUs didn't answer in synchronization

[Hardware Error]:  Machine check:  Processor context corrupt

Kernel panic - not synching: Fatal machine check on current CPU

Pid: 0, comm: swapper/3 Tained: P  M   0 3.2.0-4-amd64 #1 Debian 3.2.51-1

Call Trace: ...



Also, here is a post from superuser on some suggestions that I tried: cpu - 
Kernel Panic from overheating? - Super 
User



Here is my discussion on intel where someone recommended I post to the debian 
list https://communities.intel.com/thread/58372?sr=stream



I am looking to actually debug and fix this, but not finding a lot out there.  
Any ideas for what to try next?

Re: Late authentication

[August Karlstrom]

On 2015-01-04 17:30, August Karlstrom wrote:

I run Debian Wheezy with a simple window manager (Blackbox). If I
remember correctly, in Ubuntu some applications like Synaptic and Update
Manager ask for sudo password only when/if needed.

How do I configure the system so I can launch for instance Update
Manager as normal user, check if there are any updates available and
then provide the sudo password only if the system is to be updated? As
Far as I understand the authentication is handled by Polkit.


I tried adding the file 
/var/lib/polkit-1/localauthority/50-local.d/test.pkla with the content 
below (and restarting X) but it made no difference; update-manager still 
asks for root password when launched.


$ sudo cat /var/lib/polkit-1/localauthority/50-local.d/test.pkla
[test]
Identity=unix-group:sudo
Action=org.debian.apt.update-cache
ResultActive=yes


-- August


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/m8e1rj$dmn$1...@speranza.aioe.org

from: a perez

[a perez]

Good afternoon Debian



http://airportgateway.in/blue.php?party=yakgeb2ywf8





a perez


Sent from my iPhone


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/897c-bb00-4e73-b593-e269451cb...@terra.com.br

Re: Jumbo frame Debian Wheezy.

[Muhammad Yousuf Khan]

Thanks for the reply yes you are correct. i assume and find out the same. i
could to change the MTU of the local LAN. then i added 4x1Gb intel  LAN on
the same system and it was working as expected. that shows limit was with
the Hardware.

Thanks,
Yousuf

On Mon, Jan 5, 2015 at 4:14 PM, Alexis  wrote:

>
> Muhammad Yousuf Khan writes:
>
> > i am trying to enable jumbo frame on Debian wheezy however nothing
> > works.
> >
> > i ran a command "ifconfig eth0 mtu 9000"
> >
> > and receive "invalid argument"
> >
> > then i edit /etc/network/interfaces and added "mtu 9000"
> > when i ifdown and ifup eth0
> > it shows the same error "invalid argument"
> >
> > Please help.
>
> It might be that your Ethernet adaptor doesn't support an MTU of
> 9000. For example, the maximum MTU of the adaptor in my laptop is 6122;
> attempts to set the MTU to a larger value than that produces the
> "SIOCSIFMTU: Invalid argument" error.
>
>
> Alexis.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: https://lists.debian.org/87y4phqy2k@gmail.com
>
>

Re: Jumbo frame Debian Wheezy.

[Alexis]

Muhammad Yousuf Khan writes:

> i am trying to enable jumbo frame on Debian wheezy however nothing
> works.
>
> i ran a command "ifconfig eth0 mtu 9000"
>
> and receive "invalid argument"
>
> then i edit /etc/network/interfaces and added "mtu 9000"
> when i ifdown and ifup eth0
> it shows the same error "invalid argument"
>
> Please help.

It might be that your Ethernet adaptor doesn't support an MTU of
9000. For example, the maximum MTU of the adaptor in my laptop is 6122;
attempts to set the MTU to a larger value than that produces the
"SIOCSIFMTU: Invalid argument" error.


Alexis.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87y4phqy2k@gmail.com