Content-Type: text/plain
debian-user-digest Digest Volume 2015 : Issue 1449
Today's Topics:
Re: AP support for wl driver [ Stuart Longland <
stuartl@longlandcl ]
Re: OT Re: POP3 was: Re: command not [ Bob Bernstein <
poobah@ruptured-duck ]
Re: Attempt to Move Root [ David Baron <
d_baron@012.net.il> ]
Re: Attempt to Move Root [ Stephen Powell <
zlinuxman@wowway.co ]
kernel panic at Jessie shutdown [ "Elmer E. Dow" <
elmeredow@att.net> ]
Re: AP support for wl driver [ Himanshu Shekhar <
irm2015006@iiita. ]
Re: Intel 82576 Gigabit on Debian 7 [ David Christensen <
dpchrist@holgerd ]
Re: Intel 82576 Gigabit on Debian 7 [ David Christensen <
dpchrist@holgerd ]
Re: Attempt to Move Root [ David Christensen <
dpchrist@holgerd ]
Re: Intel 82576 Gigabit on Debian 7 [ David Christensen <
dpchrist@holgerd ]
Date: Mon, 21 Dec 2015 06:28:07 +1000
From: Stuart Longland <
stuartl@longlandclan.id.au>
To:
debian-user@lists.debian.orgSubject: Re: AP support for wl driver
Message-ID: <
[🔎] 56770F57.6050400@longlandclan.id.au" class="removed-link" href="">
[🔎] 56770F57.6050400@longlandclan.id.au>
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature";
boundary="bPJ46MDLoKNLnU7qMUjwMEgf2GfKuMXnU"
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bPJ46MDLoKNLnU7qMUjwMEgf2GfKuMXnU
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 20/12/15 19:32, Gene Heskett wrote:
>> > Thanks Stuart! I have made several attempts and almost scanned the
>> > Broadcom driver download page. No support email.
>> > They have 64 bit driver for Linux available for download. I tried,
>> > following the README file, and compilation failed with errors.
>> > Bad experience with Broadcom.
>> >
> Exactly that caused me to blacklist & leave it on the shelf or pegboard=
,=20
> anthing with a broadcom radio in it. I don't buy headches if I can help=
=20
> it.
Likewise. I have one machine with a Broadcom WIFI chip, that's the
MacBook I'm typing this email on:
> RC=3D0 vk4msl-mb stuartl $ lspci -vnn | grep Network
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4322 802.11a=
/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
That one, is compatible with the 'b43' driver in the Linux kernel, and
after a few ritual sacrifices, *does* work. It does however frequently
drop its link (dhclient soon fixes it), and even on MacOS X, misbehaves.
I've never tried HostAP with this particular device.
I don't blame the 'b43' developers for this. They have done an
excellent job to get it working to the level they have. Their work has
been almost entirely the result of clean-room reverse engineering.
It shouldn't be that way though.
Himanshu, if your chip is supported by one of the drivers listed here:
https://wireless.wiki.kernel.org/en/users/drivers. If one of those is
compatible, then you've got a chance.
Otherwise your only option is begging and grovelling to Broadcom, or
voting with your wallet and buying something else. Given the level of
contempt Broadcom has shown the Linux community historically, I
generally find it easier to avoid them and go with someone like Atheros
or Intel, who actively develop their drivers in the Linux mainline kernel=
=2E
If I wanted a proprietary binary soup I'd use Windows.
--=20
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--bPJ46MDLoKNLnU7qMUjwMEgf2GfKuMXnU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdw9YAAoJEE36GRQQveO3vgUP/3RSZOddp2Wc0RbJc5n3dOBJ
/grGl60mwr8A0bL5pj9rT359JpOCCNPRonIYDidKWSHBg+6XjH1KcFx3B1KZSWNq
uyGfgb+/we8jdr2sH5zLRmPBnTc2xKSUVNoDxyKfefzFBP84my+/DNBs3C+TDZCi
bWeMsB700qibDMUCwolu+2q2PLLCzvkF56SapIgfgaufwUdLwuVyF+gXqLEXe9Jv
oEaGM8c5PKCNY2JY4T2+jKLPa+9T4shj8b+M94HbNYflw1dtTM8d5QnlD0HjWMYU
HlOApmkSteLSU3iWLF/x/5HoqPdZyEPLzWgnZK4SsV8KpLZflmT78PHht3NeeEWl
hBB1o4/rn7ne5Yl5niM1ZxKjHTO6jFUU2QD0Z5ZpfbLCWpga0cHdEwE+ixRZxZXR
boU7Z5idHlvlD69+KF5IkQqlj7kWoN+37Q6d1xV5TiFVCiqzirzz4XS58CYADysr
9YCWagliQd90qslQ5ps8WCxo7B7zr6abugOaG7ywtSZ2J8S6ZKzqSYztmaj2p4Bp
P1tGvt0ADwxB+SpsDMkIr8fV4SJmHoRFm1q2z2vVqbt8jPOX3VSuRWGDkPouOmRa
vWHGkjtPUdzUDpmIsMnwrMjBDtqT41tPse8k8jK3jBSs4yLlBPhUWlEJjSbyItlO
YWOyeCaLvu720iLIf6Sh
=qgdJ
-----END PGP SIGNATURE-----
--bPJ46MDLoKNLnU7qMUjwMEgf2GfKuMXnU--
Date: Sun, 20 Dec 2015 15:40:54 -0500 (EST)
From: Bob Bernstein <
poobah@ruptured-duck.com>
To: Debian User List <
debian-user@lists.debian.org>
Subject: Re: OT Re: POP3 was: Re: command not found [SOLVED]
Message-ID: <
[🔎] nycvar.QRO.7.75.65.1512201531510.31215@qrovna.ybpnyqbznva" class="removed-link" href="">
[🔎] nycvar.QRO.7.75.65.1512201531510.31215@qrovna.ybpnyqbznva>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Sun, 20 Dec 2015, Bob Holtzman wrote:
> When I had to put down my old guy and best friend "Num Nutz" I
> cried more than I did at my mother's funeral....so I know the
> feeling.
Yes. Some may want to complain that this exchange is OT, but I
submit that this Christmas week, with the world seemingly more
ready to fly apart at the seams than it is has within my memory,
and I turned seventy one last month, is exactly the time for at
least a passing nod to our shared concerns of humanity and
death.
Come the New Year (God Willing and the creek don't rise)
there'll be plenty of time to get back to our old cranky
individualistic ways. Right now 'tho there is a strong feeling
abroad in the land, as they used to say, that either we stick
together, or hang separately...
--
Bob Bernstein
Date: Sun, 20 Dec 2015 22:51:22 +0200
From: David Baron <
d_baron@012.net.il>
To:
debian-user@lists.debian.orgSubject: Re: Attempt to Move Root
Message-id: <
[🔎] 2198108.1GosprtllU@dovidhalevi" class="removed-link" href="">
[🔎] 2198108.1GosprtllU@dovidhalevi>
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7Bit
On Sunday 20 December 2015 13:18:09 Stephen Powell wrote:
> On Sun, 20 Dec 2015 05:58:47 -0500 (EST), David Baron wrote:
> > OK, mounted newrootpartition newroot
> > Did a cp -x / newroot
> > Successful so far, elementary
> >
> > Edited newroot/etc/fstab and newroot/etc/lilo.conf to point root to
> > newrootpartition (by uuid)
> >
> > mount --bind /dev newroot/dev
> > mount --bind /proc newroot/proc
> > as instructed in various posts, to enable lilo to run.
> >
> > chroot newroot
> > lilo ...
> >
> > Looked successful. Umounted everything and reboot.
> >
> > Get boot menu (congratulations !?).
> > Chose the kernel.
> >
> > Now got that lvm not ready business.. I usually get this once and then
> > normally boot up. Now getting it over and again. BTW, if I control/C a few
> > times, I end up inside initramfs>.
> >
> > Put up the live DVD, regenerated the initramfs, but ... no change.
> > Put up the live DVD, mounted the old root partition, went through the
> > lilo
> > process and back up.
> >
> > So ... how do I do this??
>
> I have several thoughts.
>
> First of all, the right way to copy the root filesystem under these
> conditions is
>
> cp -a -x /. newroot
>
> That period after the forward slash is important!
>
> Second, make sure that the initial RAM filesystem contains everything needed
> to initialize a logical volume. If you make a logical volume the root
> filesystem in the Debian installer, the Debian installer *should* do
> whatever is necessary to make sure that everything needed to mount a
> logical volume gets included in the initial RAM filesystem. I've never
> tried to do this, so I can't give you a list of what files will be needed.
> You can examine an existing inital RAM filesystem to see what files are
> included by using lsinitramfs.
>
> Third, although it is possible to make a logical volume the root filesystem,
> /boot must not be part of this filesystem. It must be a separate partition
> on a physical volume. (Furthermore, it must be a separate partition that
> is accessible via the BIOS.) The same goes for the boot sector. (The
> "boot" configuration record in /etc/lilo.conf.) Usually, this is the first
> sector on the /boot partition or else the master boot record. And if it is
> not the master boot record, then a generic MBR boot loader program must be
> installed in the MBR and the /boot partition must be on that physical disk,
> and it must be marked active in the partition table (and all other
> partitions marked inactive). Finally, make sure that the BIOS is actually
> booting from this physical disk.
>
> Although the specific subject of using an LVM2 logical volume as the root
> filesystem is not specifically covered, you may find some useful lilo
> tidbits on my lilo web page:
>
>
http://www.stevesdebianstuff.org/lilo.htm>
> Finally, make sure that there are no duplicate UUIDs in the system that
> might confuse the kernel during boot.
Thanks for the detailed explanation!
I am not now using logical volumes. (When I did in the past, boot was indeed
separate.) Do not need the layer of complication and unless one is careful to
leave unallocated areas, the whole thing becomes locked up anyway.
I did not know about the /. so will definitely try it this way.
The first time I did this, moving from the tiny partition to the old IDE
partition, I did not do any of this. I did the copy, edited the files in situ
(old root), ran lilo and it booted up. But ... the old root was still active
because the newroot files were not the edited copies (i.e., old fstab). So
once I fixed that, it simply played, no fuss, no muss.
So ... do I need the chroot and the binds and all this at all?
Date: Sun, 20 Dec 2015 16:39:10 -0500 (EST)
From: Stephen Powell <
zlinuxman@wowway.com>
To:
debian-user@lists.debian.orgSubject: Re: Attempt to Move Root
Message-ID: <
[🔎] 1107424864.99304802.1450647550137.JavaMail.zimbra@wowway.com" class="removed-link" href="">
[🔎] 1107424864.99304802.1450647550137.JavaMail.zimbra@wowway.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
On Sun, 20 Dec 2015 15:51:22 -0500 (EST), David Baron wrote:
>
> So ... do I need the chroot and the binds and all this at all?
That's the recommended way. Make sure that the edited copies of
/etc/lilo.conf, /etc/fstab, and /etc/initramfs-tools/conf.d/resume,
in the chrooted environment, all make sense for the new setup,
especially the "boot" and "root" configuration file records in
/etc/lilo.conf. /etc/initramfs-tools/conf.d/resume must specify
the UUID of the swap partition.
I have another web page that may be helpful to you. It shows an
example of copying a root file system for a virtual machine running
under z/VM in the s390x environment. That is not your situation,
of course; but portions of it are applicable to your environment.
You may be able to separate the wheat from the chaff and figure out
what applies to your situation and what doesn't. Then again, it may
only confuse you. So I give you the link with some hesitation.
The parts that apply are the copying of the file system(s), and
setting up the chroot environment. I hope it does more good than
harm. Here it is:
http://www.stevesdebianstuff.org/diag250.htm The s390x environment uses a boot loader called zIPL, not LILO; but
zIPL's design is similar to LILO in that it does not understand the
structure of a Linux file system. It simply reads a predetermined
list of blocks from the file system at boot time.
Also note that /boot must not use the btrfs filesystem. This is an
undocumented restriction for both zIPL and LILO. I recommend ext2
for /boot. (If the partition size is small enough, you pretty much have
to use ext2. ext3 and ext4 require a journal, and that in turn requires
a certain minimum partition size.) Good luck.
Date: Sun, 20 Dec 2015 16:48:19 -0600
From: "Elmer E. Dow" <
elmeredow@att.net>
To:
debian-user@lists.debian.orgSubject: kernel panic at Jessie shutdown
Message-ID: <
[🔎] 56773033.4020709@att.net" class="removed-link" href="">
[🔎] 56773033.4020709@att.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I installed Debian LXDE 8.2 (Jessie) on an IBM R40 laptop (2897-54U, 1.3
Centrino processor, 256 meg memory) using the netinst CD. The LAN port
is broken, so I used a USB to RJ45 adapter. Installation went fine, but
when I clicked logout, then shutdown, it went into kernel panic, giving
the following messages:
[ 222.710760] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000009
[ 222.710760]
[ 222.713883] Kernel offset: 0x0 from 0xc0000000 (relocation range:
0xc0000000 - 0xd075ffff)
[ 222.713883] drm_kms_helper: panic occurred, switching back to text
console
[ 222.713883] ---[end kernel panic - not syncing: Attempted to kill
init! exitcode:0x00000009
[ 222.713883]
Then it failed to shutdown, so I had to press the power button to shut
it down. It continues to do that.
Any suggestion as to what's the cause and what's the solution? I had
been running Squeeze before this Jessie installation.
Please cc me as I am not subscribed.
elmer
Date: Mon, 21 Dec 2015 08:31:43 +0530
From: Himanshu Shekhar <
irm2015006@iiita.ac.in>
To: Debian-user <
debian-user@lists.debian.org>
Subject: Re: AP support for wl driver
Message-ID: <CANy4JShX4rd4R5dAA3E-iJ=FUDZLwo8uQAAenHRjsqG7hOn=
-g@mail.gmail.com>
Content-Type: multipart/alternative; boundary=001a11c165e8a44a1805275fb6e5
--001a11c165e8a44a1805275fb6e5
Content-Type: text/plain; charset=UTF-8
On Mon, Dec 21, 2015 at 1:58 AM, Stuart Longland <
stuartl@longlandclan.id.au> wrote:
>
> > RC=0 vk4msl-mb stuartl $ lspci -vnn | grep Network
> > 03:00.0 Network controller [0280]: Broadcom Corporation BCM4322
> 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
>
> That one, is compatible with the 'b43' driver in the Linux kernel, and
> after a few ritual sacrifices, *does* work. It does however frequently
> drop its link (dhclient soon fixes it), and even on MacOS X, misbehaves.
>
> I've never tried HostAP with this particular device.
>
Please make a try once. We would be pleased to have your experiences. I
would suggest to use the hotspotd program (depends on hostapd, dnsmasq).
It's the simplest I've known, but not in Debian repos. A Google search
would pop it up.
>
> I don't blame the 'b43' developers for this. They have done an
> excellent job to get it working to the level they have. Their work has
> been almost entirely the result of clean-room reverse engineering.
>
> It shouldn't be that way though.
>
I understand the pain for a proprietary software manufacturer to spend time
and money on a free project with no monetary return.
However, one should not make a software that locks the capabilities of the
hardware, making the device function in a non-appreciable manner.
>
> Himanshu, if your chip is supported by one of the drivers listed here:
>
https://wireless.wiki.kernel.org/en/users/drivers. If one of those is
> compatible, then you've got a chance.
>
Yup! That's the 'wl' driver. I've been using it right from the first day I
installed Debian.
I began with 'broadcom-sta-dkms' package but later switched to
'bcmwl-kernel-source' from Ubuntu repos.
Also, changing the regulatory allowed me to make use of certain disabled
channels and make better use of the device.
However, it is the hotspot disappointing me, which I need everyday badly
and have to depend on other people as my roommate which not at all gives a
good feeling.
>
> Otherwise your only option is begging and grovelling to Broadcom, or
> voting with your wallet and buying something else. Given the level of
> contempt Broadcom has shown the Linux community historically, I
> generally find it easier to avoid them and go with someone like Atheros
> or Intel, who actively develop their drivers in the Linux mainline kernel.
>
> That's the biggest mistake I ever did. Perhaps, one should focus more on
wireless and driver support than any other thing while purchasing a laptop.
The laptop came with Ubuntu preinstalled, making me believe that Linux
would function perfectly on it. Misconception indeed!
If I wanted a proprietary binary soup I'd use Windows.
>
I downloaded the Windows driver, but ndis suports drivers made for Windows
XP only.
Walking through the Windows driver made me discover multiple ".hex" files
with no idea on how to use them.
> --
> Stuart Longland (aka Redhatter, VK4MSL)
>
> I haven't lost my mind...
> ...it's backed up on a tape somewhere.
>
Not at all, you seem to be a perfectly sound man :P
Regards
Himanshu Shekhar
--001a11c165e8a44a1805275fb6e5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Dec 21, 2015 at 1:58 AM, Stuart Longland <span dir=3D"ltr"><<a href="">=3D"mailto:
stuartl@longlandclan.id.au" target=3D"_blank">
stuartl@longlandcl=
an.id.au</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><br>
> RC=3D0 vk4msl-mb stuartl $ lspci -vnn | grep Network<br>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4322 802.11=
a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)<br>
<br>
That one, is compatible with the 'b43' driver in the Linux kernel, =
and<br>
after a few ritual sacrifices, *does* work.=C2=A0 It does however frequentl=
y<br>
drop its link (dhclient soon fixes it), and even on MacOS X, misbehaves.<br=
>
<br>
I've never tried HostAP with this particular device.<br></blockquote><d=
iv><br></div><div>Please make a try once. We would be pleased to have your =
experiences. I would suggest to use the hotspotd program (depends on hostap=
d, dnsmasq). It's the simplest I've known, but not in Debian repos.=
A Google search would pop it up.=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-col=
or:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
I don't blame the 'b43' developers for this.=C2=A0 They have do=
ne an<br>
excellent job to get it working to the level they have.=C2=A0 Their work ha=
s<br>
been almost entirely the result of clean-room reverse engineering.<br>
<br>
It shouldn't be that way though.<br></blockquote><div><br></div><div>I =
understand the pain for a proprietary software manufacturer to spend time a=
nd money on a free project with no monetary return.</div><div>However, _one_ =
should not make a software that locks the capabilities of the hardware, mak=
ing the device function in a non-appreciable manner.</div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
Himanshu, if your chip is supported by one of the drivers listed here:<br>
<a href="" target="_blank" class="removed-link" href="">https://wireless.wiki.kernel.org/en/users/drivers" rel=3D"norefe=
rrer" target=3D"_blank">
https://wireless.wiki.kernel.org/en/users/drivers</=
a>.=C2=A0 If one of those is<br>
compatible, then you've got a chance.<br></blockquote><div><br></div><d=
iv>Yup! That's the 'wl' driver. I've been using it right fr=
om the first day I installed Debian.</div><div>I began with 'broadcom-s=
ta-dkms' package but later switched to 'bcmwl-kernel-source' fr=
om Ubuntu repos.=C2=A0</div><div>Also, changing the regulatory allowed me t=
o make use of certain disabled channels and make better use of the device.<=
/div><div>However, it is the hotspot disappointing me, which I need everyda=
y badly and have to depend on other people as my roommate which not at all =
gives a good feeling.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,2=
04,204);border-left-style:solid;padding-left:1ex">
<br>
Otherwise your only option is begging and grovelling to Broadcom, or<br>
voting with your wallet and buying something else.=C2=A0 Given the level of=
<br>
contempt Broadcom has shown the Linux community historically, I<br>
generally find it easier to avoid them and go with someone like Atheros<br>
or Intel, who actively develop their drivers in the Linux mainline kernel.<=
br>
<br></blockquote><div>That's the biggest mistake I ever did. Perhaps, o=
ne should focus more on wireless and driver support than any other thing wh=
ile purchasing a laptop.</div><div>The laptop came with Ubuntu preinstalled=
, making me believe that Linux would function perfectly on it. Misconceptio=
n indeed!=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
If I wanted a proprietary binary soup I'd use Windows.<br></blockquote>=
<div><br></div><div><div>I downloaded the Windows driver, but ndis suports =
drivers made for Windows XP only.</div><div>Walking through the Windows dri=
ver made me discover multiple ".hex" files with no idea on how to=
use them.</div></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex">
<span>--<br>
Stuart Longland (aka Redhatter, VK4MSL)<br>
<br>
</span><div><div>I haven't lost my mind...<br>
=C2=A0 ...it's backed up on a tape somewhere.<br></div></div></blockquo=
te><div><br></div><div>Not at all, you seem to be a perfectly sound man :P<=
/div><div><br></div><div>Regards</div><div>Himanshu Shekhar =C2=A0</div></d=
iv><br></div></div>
--001a11c165e8a44a1805275fb6e5--
Date: Sun, 20 Dec 2015 23:58:28 -0800
From: David Christensen <
dpchrist@holgerdanske.com>
To:
debian-user@lists.debian.orgSubject: Re: Intel 82576 Gigabit on Debian 7 slow speed.
Message-ID: <
[🔎] 5677B124.8060503@holgerdanske.com" class="removed-link" href="">
[🔎] 5677B124.8060503@holgerdanske.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 12/20/2015 08:36 AM, Mimiko wrote:
> If LUKS you mean Linux Unified Key Setup, then I don't use [it].
Okay.
> The HDD's are connected thru SuperMicro SAS RAID AOC-USASLP-L8i
> (PCI-E).
http://www.supermicro.com.tr/AOC-USASLP-L8i.cfm.htmSo, one RAID card, eight SAS channels, and one 2 TB and one 1 TB drive
per channel (?).
Are you using any hardware RAID or JBOD capabilities under Wheezy?
> All disks are in an enclosure.
External enclosure? That card is for drives within in the same
enclosure as the card.
Where do the drives get power?
> This card works at SATA2 speed, although disks can handle SATA3.
What is the make/ model of the drives?
> Also SSD's are new Intel disk which have SATA3, but motherboard
> supports only SATA2. SSD's a connected to motheboard directly.
Try disconnecting the RAID card and drives, and benchmarking just the SSD's.
> There is only 18RAM available as of budget.
Do you know if your amount of RAM is too much, too little, or just right?
> Enabled [AES-NI in CMOS setup] - and no effect.
Since you are not running encrypted drives, AES-NI won't help you there.
But, it should help with SSL.
> Some [CMOS settings[ are default, some are changed based on my
> readings in Internet.
Okay, so long as you understand each.
> zpool create -f -m none -o ashift=12 zfspool raidz2
> wwn-0x50000xxxxxxxxxxx ..... (all disks).
What does ZFS report for the size of the pool?
> [bug reports/ feature requests] will take a longer time than I will
> start to use drbd. If no one fired a request, or it wasn't
> implemented yet, then ZFS on Linux thinks it is not useful, I think.
Okay.
> I'm open to suggestions to optimize file system and keep the needs.
When you ran Windows:
1. Which version of Windows?
2. Were the hardware and and CMOS settings identical to what they are
with Wheezy?
3. Did you use the AOC-USASLP-L8i RAID hardware capabilities? If so,
how did you configure it?
4. Did you use any software RAID, Windows dynamic disks, etc.? If so,
what software and how did you configure it?
David
Date: Mon, 21 Dec 2015 00:24:56 -0800
From: David Christensen <
dpchrist@holgerdanske.com>
To:
debian-user@lists.debian.orgSubject: Re: Intel 82576 Gigabit on Debian 7 slow speed.
Message-ID: <
[🔎] 5677B758.4070105@holgerdanske.com" class="removed-link" href="">
[🔎] 5677B758.4070105@holgerdanske.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 12/19/2015 07:24 PM, David Christensen wrote:
> I ran iperf ... ~950 MB/s.
^^^^
Oops -- make that 950 Mbps.
On 12/20/2015 09:13 AM, Mimiko wrote:
> I've tested using iperf the file server to the windows server and I've
> got 400Mbits.
Something is wrong.
> The other linux server got 600Mbits.
Something is wrong, too.
> Also I've tested
> iperf between windows server and another same type supermicro with
> hyper-v and got around 650Mbits.
The hypervisor adds another layer, but I would still expect it to be
900+ Mbps. Something is wrong, three.
Do you have a laptop or desktop (or two) with Gigabit that you can use
for testing?
Download a live CD image, burn two discs/ USB flash drives, and try again:
https://www.debian.org/CD/live/ debian-live-8.2.0-amd64-standard.iso
> I've tested samba speed from windows to other linux server. It gives
> 90MB/s at read from that server and 70MB/s of write. 2 times of the file
> server with problem.
>
> Using smbclient:
> From file server to other liux box - 48MB/s
> from othe linux box to file server - 65MB/s
>
> This is what I could test more.
Both Ethernet and RAID need to be running well before Samba can run well.
You have 24 GB of drives for RAID. How many file systems(s), and what
size each, do you need?
Are you able to move services off the Wheezy Samba server so you can
take drastic measures?
David
Date: Mon, 21 Dec 2015 00:50:43 -0800
From: David Christensen <
dpchrist@holgerdanske.com>
To:
debian-user@lists.debian.orgSubject: Re: Attempt to Move Root
Message-ID: <
[🔎] 5677BD63.9000102@holgerdanske.com" class="removed-link" href="">
[🔎] 5677BD63.9000102@holgerdanske.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 12/20/2015 02:58 AM, David Baron wrote:
> So ... how do I do this??
On 12/20/2015 03:36 AM, David Baron wrote:
> my goal is to remove and older 80gig IDE disk from the system
Debian version?
What drive is root on? How is the drive partitioned? RAID? LVM? LUKS?
Other? What is the file system type? How big?
Where do you want to move root?
What else is on the same drive as root? Boot? Swap? Do you want to
move these? Where?
David
Date: Mon, 21 Dec 2015 00:56:55 -0800
From: David Christensen <
dpchrist@holgerdanske.com>
To:
debian-user@lists.debian.orgSubject: Re: Intel 82576 Gigabit on Debian 7 slow speed.
Message-ID: <
[🔎] 5677BED7.9040403@holgerdanske.com" class="removed-link" href="">
[🔎] 5677BED7.9040403@holgerdanske.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 12/21/2015 12:24 AM, David Christensen wrote:
> Download a live CD image, burn two discs/ USB flash drives, and try again:
>
>
https://www.debian.org/CD/live/>
> debian-live-8.2.0-amd64-standard.iso
I just realized that the live disc might not have iperf...
Perhaps Knoppix:
http://knopper.net/knoppix/index-en.htmlBut the best solution I've found is installing and running Debian on USB
flash drives in computers that are "new enough". USB flash drives are
cheap, they work well enough for light use, and they are very useful for
troubleshooting. Get two, set one up with a fresh install of Jessie,
install iperf and whatever other tools you like, save the raw image,
clone it to the second drive, and use those for testing.
David