Content-Type: text/plain
debian-user-digest Digest Volume 2013 : Issue 1552
Today's Topics:
Re: Soliciting hardware recommendati [ Stan Hoeppner <stan@hardwarefreak.c ]
Re: boot from USB and install debian [ ha <hiei.arhiva@gmail.com> ]
Re: boot from USB and install debian [ Brian <ad44@cityscape.co.uk> ]
Wireless Network Connection Unstable [ Rakitha Sanjeewa Beminiwattha <raki ]
Re: Wireless Network Connection Unst [ Andrei POPESCU <andreimpopescu@gmai ]
Printing in Jessie [ Frank Miles <fpm@u.washington.edu> ]
Re: Printing in Jessie [ Zenaan Harkness <zen@freedbms.net> ]
Wasted space in hard disk partitioni [ Stephen Powell <zlinuxman@wowway.co ]
Re: Wasted space in hard disk partit [ Stan Hoeppner <stan@hardwarefreak.c ]
Date: Mon, 16 Dec 2013 08:13:16 -0600
From: Stan Hoeppner <stan@hardwarefreak.com>
To: debian-user@lists.debian.org
Subject: Re: Soliciting hardware recommendations
Message-ID: <[🔎] 52AF0A7C.1020709@hardwarefreak.com">[🔎] 52AF0A7C.1020709@hardwarefreak.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On 12/15/2013 5:44 PM, Stephen Powell wrote:
> On Sun, 15 Dec 2013 15:07:33 -0500 (EST), Stan Hoeppner wrote:
>>
>> I was figuring you'd probably do the install from a USB stick and I
>> threw the DVD drive in as an afterthought. So yes, the ASUS burner
>> above would be perfect. Over 4,000 sold and a 5 egg rating. Can't get
>> any better than that.
>
> Good. I just ordered everything exactly as you recommended, except
> for the CD/DVD drive, for which I substituted the R/W model. To
> install Debian, I usually use the "netboot" installation image burned
> to a CD-R.
Cool. Make sure you partition the SSD so that your first, and all,
partitions start on a 4KB boundary. Many guides are available for your
favorite partitioning tool. Linux does all IO in 4KB pages including
filesystem and swap. If you don't align to 4KB you may get excessive
erase cycles on the SSD, lowering performance, and cell life. Most
folks seem to start the first SSD partition at sector 2048, which falls
immediately after the first 1MB of the device. 1,048,576/4,096=256. So
your first partition will start at 4KB "page 257", if you will. If you
create multiple partitions, make sure the size of each is evenly
divisible by 4096 bytes, or they won't be aligned.
>> If you decide to go this route and you run into any
>> trouble getting it going, don't hesitate to email me off list. I may
>> not respond quickly but I'll respond.
>
> That's a very generous offer. Thank you very much. I hope I won't
> need to take you up on that, but it's nice to know that I can if I need to.
It would be very poor form of me to recommend a bunch of parts and then
run away when problems arise during integration. :) This is a bit
different than recommending a model of TV or microwave...
> You know, I almost added an anti-static wrist strap to the order, but
> in the end decided not to. My basement is so humid, even in winter,
> that I doubted it would be a problem. However, my dehumidifier, which
> normally runs 9 or 10 months out of the year, is currently showing the
> relative humidity at 30% (and it's off, set for 50%), so maybe I'll
> get one anyway.
I'm a bit of a hypocrite here. I never use straps myself but always
recommend it to others. I've been doing computer work for a couple of
decades+, and I always do assy/repair on metal benches. Before I handle
a component I grab the bench, and while I'm working I keep a foot or
knee against a bench leg or the table top frame. It's simply 2nd
nature. And it negates the restriction of un/clipping a strap if I need
to leave the bench.
> Thanks again, "Santa".
Ho, ho, ho, you're welcome. :)
> This will be my first truly new system since
> 1994.
Wow, you should be in for a treat. Especially with that SSD. You're
going to need to watch your console closely. Even big operations will
complete before you hear the click from the Enter key. ;)
> I've been using other people's throw-aways and used systems
> since then. But nobody I know is throwing away 64-bit systems. Not
> yet anyway.
Maybe not throwing them away, but there are tons of decent used 64 bit
x86 boxen on Ebay. But even at those prices one can build a better
system for little more money, such as yours.
--
Stan
Date: Mon, 16 Dec 2013 15:25:56 +0100
From: ha <hiei.arhiva@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: boot from USB and install debian using grub2 and netinstall debian
iso image
Message-ID: <l8n29p$tbp$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 12/16/2013 12:45 PM, Brian wrote:
> On Mon 16 Dec 2013 at 09:40:17 +0100, ha wrote:
>
> [Snip]
>
>> So the question is:
>> 1. Did anybody managed to boot from USB and install debian using
>> grub2 and the netinstall debian image? (i.e. Is this possible? Does
>> netinstall support this?)
>
> Yes, using the hd-media kernel and initrd. Employing GRUB's loopback
> feature with a netinst ISO is not possible at present.
Can you please point me in the right direction?
>
>> 2. Did I miss something plain simple? (like, a boot parameter that
>> will mount the iso image to correct location; or link it; or
>> whatever)
>
> You'll be interested in the short discussion at
>
> http://lists.debian.org/debian-boot/2013/09/msg00094.html
>
> and its associated bug report at
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724931
>
>
Great, thanks.
But it seems as a dead end.
It would be helpful if you could share any knowledge you might have on
utilizing loop.ko module, mentioned in the bug report.
Date: Mon, 16 Dec 2013 16:02:30 +0000
From: Brian <ad44@cityscape.co.uk>
To: debian-user@lists.debian.org
Subject: Re: boot from USB and install debian using grub2 and netinstall
debian iso image
Message-ID: <[🔎] 20131216160230.GQ5433@copernicus.demon.co.uk">[🔎] 20131216160230.GQ5433@copernicus.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon 16 Dec 2013 at 15:25:56 +0100, ha wrote:
> On 12/16/2013 12:45 PM, Brian wrote:
> >
> >Yes, using the hd-media kernel and initrd. Employing GRUB's loopback
> >feature with a netinst ISO is not possible at present.
>
> Can you please point me in the right direction?
Working mainly from memory:
Obtain the hd-media from
http://ftp.debian.org/debian/dists/wheezy/main/installer-i386/current/images/
Put vmlinuz and initrd.gz in a directory of your choice.
In grub.cfg put
menuentry "debian-netinst-iso" {
linux /<DIR>/vmlinuz priority=low
initrd /<DIR>/initrd.gz
}
You may, of course, add installer options to the 'linux' line.
Put the netinst ISO in <DIR>.
Boot, select entry, scan devices to find the ISO.
> It would be helpful if you could share any knowledge you might have
> on utilizing loop.ko module, mentioned in the bug report.
If I did have any knowledge I've forgotten most of it. :) In the end I
decided booting from an isohybrid on a USB stick was far more convenient
than whatever I devised, which may have involved remastering the ISO.
Perhaps the bug report indicates a way forward.
Date: Mon, 16 Dec 2013 11:30:33 -0500
From: Rakitha Sanjeewa Beminiwattha <rakithab@gmail.com>
To: debian-user@lists.debian.org
Subject: Wireless Network Connection Unstable
Message-ID: <CAHhkf1zz0xujBg=7SsbX_qOgLr-BBG8Ss65P0rcw_wAsu+kJDw@mail.gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2ee18bec732404eda955d0
--047d7b2ee18bec732404eda955d0
Content-Type: text/plain; charset=ISO-8859-1
Hello,
I have an ASUS laptop with Intel Wireless-N module (iwlwifi driver). I'm
using Gnome network manager for networking. I'm experiencing following
issue with wireless internet connection and would like to know if any one
had faced same issues.
The internet connection loses sometime several times per day of use but I
can see the wireless connection is active. To recover from this I usually
turn OFF and ON the wireless connection from the gnome network manager.
Then there are occasions when this step will not restore the internet
connection. Then I have to unload and load the wireless module manually by
doing,
modprobe -r iwlwifi ; modprobe iwlwifi
I don't think this is not addressing to root of the problem, I'm doing it
just to reset what ever the issue with wireless connection and restore the
internet connection.
I appreciate if anyone can give me information to debug this issue or to
fix the problem. I can provide more information on request.
I recently switched to Debian distribution after using Ubuntu and I
remember I had the same issue while using Ubuntu too.
Rakitha Beminiwattha
--047d7b2ee18bec732404eda955d0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hello,</div><div>I have an ASUS laptop with Intel Wir=
eless-N module (iwlwifi driver). I'm using Gnome network manager for ne=
tworking. I'm experiencing following issue with wireless internet conne=
ction and would like to know if any one had faced same issues.</div>
<div><br></div><div>The internet connection loses sometime several times pe=
r day of use but I can see the wireless connection is active. To recover fr=
om this I usually turn OFF and ON the wireless connection from the gnome ne=
twork manager. Then there are occasions when this step will not restore the=
internet connection. Then I have to unload and load the wireless module ma=
nually by doing,</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0modprobe -r iwlwifi ; modprobe iwlw=
ifi</div><div>I don't think this is not addressing to root of the probl=
em, I'm doing it just to reset what ever the issue with wireless connec=
tion and restore the internet connection.</div>
<div><br></div><div>I appreciate if anyone can give me information to debug=
this issue or to fix the problem. I can provide more information on reques=
t.=A0</div><div><br></div><div>I recently switched to Debian distribution a=
fter using Ubuntu and I remember I had the same issue while using Ubuntu to=
o.=A0</div>
<div><br></div><div><br></div><br clear=3D"all"><div>Rakitha Beminiwattha<b=
r><br></div>
</div>
--047d7b2ee18bec732404eda955d0--
Date: Mon, 16 Dec 2013 22:56:23 +0200
From: Andrei POPESCU <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Wireless Network Connection Unstable
Message-ID: <[🔎] 20131216205623.GE3239@sid.nuvreauspam>
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="jn9znQ5OoOl0oegR"
Content-Disposition: inline
--jn9znQ5OoOl0oegR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Lu, 16 dec 13, 11:30:33, Rakitha Sanjeewa Beminiwattha wrote:
>=20
> I appreciate if anyone can give me information to debug this issue or to
> fix the problem. I can provide more information on request.
I would first try the most recent kernel and firmware. If you are using=20
Debian stable (you didn't say) the safest way would probably be to use=20
the kernel and firware-iwlwifi package from backports.
Other things to consider:
- how far are you from the access point?
- are other wireless devices working fine in similar conditions?
- do you have these issues also with other wireless access points?
Kind regards,
Andrei
--=20
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
--jn9znQ5OoOl0oegR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAEBCAAGBQJSr2j2AAoJEP/HhUTvIjQc+dgQAInsAiMPqN5N0ChzuQ9lnMHH
UMpAA6ZTKVPBlcUR9ijOkFfT/KHaBeibWYfSvdnGQxviA1lIhNARwH1+5Bno45Ui
fA+sHrK9/xEMIIfAURwC6L+uUFG+P/NI3vnNR+NlJwJp0KlU6DuRwBl6azobfSKn
phSCTSR25cJE4pbL1AdT2YmcbKlLfzBn1/2VwsaQsIOjByTamUazsCOj8cVgqYlL
dHIVF9bA99arlejKH+O+GWYFgO82U/iZ6WQej2EEOm9gy8R80ij5/UvVe/6e9rwE
O/GNHmfin/gdWKwxjBPw0Psf1INhTL6R47yFO4pJJNeiRqzspqZLrT+6tYiiFljl
+jWihy29d+0Qf1iRG6GDNqfTu1Eup9wtkAeFkiJI4+FHGZJkXZo00YPoef2q95+G
eUNDv741f9HBmKWIsdqEav7xxyg/HsTP/R/UW9f85Uun5LalqUzXh/9mgyE+nYW6
Mrs/gDS30sw1+HeEscCGrxCCq7TCFkj4M2nm5Gt0IT1GQDEWHbK+1bcNgxqmwLIK
UftgNmsrEXOcf3d7XHNUfWeMj+z5N5LCpNAJYxCe/9XRZ2f+8yJLWQ/3MOLARjUC
pg7F+kBcVLvDWMNl1YED0qYL6fgmNmWDg7AGbdiVsKLOGz7D1NlpO7NvTPqy+bw7
Q47F39av48VVwqpwDWH6
=6HSs
-----END PGP SIGNATURE-----
--jn9znQ5OoOl0oegR--
Date: Tue, 17 Dec 2013 00:33:02 +0000 (UTC)
From: Frank Miles <fpm@u.washington.edu>
To: debian-user@lists.debian.org
Subject: Printing in Jessie
Message-ID: <l8o63u$396$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
I'm having serious difficulty trying to print PDFs in Jessie.
Printing PDFs works from gimp (gutenprint), but evince just causes
blank pages. This is all with an old HPLJ5M (postscript)
network printer. Similarly I can telnet into the printer and have
random keystrokes print in Courier. Taking down my firewall
changes nothing. Several other applications (not just evince)
similarly generate blanks.
I've also installed (on the same machine) a virtual Wheezy via
KVM. Attempting to print from that also results in blank pages
though this should be through cups on the virtualized system to
the jet-direct card in the printer (bridged networking).
The cups web interface and <lpstat -tv> say everything is good.
My older system (this is a new machine) printed over the same
network without difficulty (wheezy and older).
I'm getting some hate mail from the system:
dbus[4399]: [system] Rejected send message, 2 matched rules; type="method_return",
+sender=":1.1" (uid=106 pid=4500 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error
+name="(unset)" requested_reply="0" destination=":1.35" (uid=1001 pid=3144 comm="/usr/bin/evince
+testfile.pdf ")
but so far my searching hasn't pulled up anything constructive
relevant to dbus, avahi-daemon, evince,...
Oh yes - this is with a 3.11 kernel, which I need to make the video
system work (Intel haswell, video is on-chip).
Any insights as to where I should look? Is this something that
jessie is doing to everyone, or is my configuration strangely mangled?
Thanks for any clues!
-Frank
Date: Tue, 17 Dec 2013 12:49:16 +1100
From: Zenaan Harkness <zen@freedbms.net>
To: debian-user@lists.debian.org
Subject: Re: Printing in Jessie
Message-ID: <[🔎] CAOsGNSSU4VJNGjjMkk4W1ZCiuaRiDDAyowKB+aUROayE2zPDMw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 12/17/13, Frank Miles <fpm@u.washington.edu> wrote:
> I'm having serious difficulty trying to print PDFs in Jessie.
> Any insights as to where I should look? Is this something that
> jessie is doing to everyone, or is my configuration strangely mangled?
Have you tried removing and re-adding the printer again (or simply add
new printer with a new id/name for the printer)?
Are you using gtklp,system-config-printer or some kde thing or something else?
Date: Mon, 16 Dec 2013 23:12:35 -0500 (EST)
From: Stephen Powell <zlinuxman@wowway.com>
To: debian-user <debian-user@lists.debian.org>
Subject: Wasted space in hard disk partitioning (was Soliciting Hardware
Recommendations)
Message-ID: <[🔎] 1588134292.17319.1387253555768.JavaMail.root@md01.wow.synacor.com">[🔎] 1588134292.17319.1387253555768.JavaMail.root@md01.wow.synacor.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
On Mon, 16 Dec 2013 08:13:16 -0600, Stan Hoeppner wrote:
>
> Cool. Make sure you partition the SSD so that your first, and all,
> partitions start on a 4KB boundary. Many guides are available for your
> favorite partitioning tool. Linux does all IO in 4KB pages including
> filesystem and swap. If you don't align to 4KB you may get excessive
> erase cycles on the SSD, lowering performance, and cell life. Most
> folks seem to start the first SSD partition at sector 2048, which falls
> immediately after the first 1MB of the device. 1,048,576/4,096=256. So
> your first partition will start at 4KB "page 257", if you will. If you
> create multiple partitions, make sure the size of each is evenly
> divisible by 4096 bytes, or they won't be aligned.
That's good to know. But I really don't have much control over this
when I partition using the Debian installer. When installing from
scratch on a system where I don't intend to keep anything from its
previous life, I delete all existing partitions using the Debian installer,
then create new partitions using the Debian installer. When I create
a new partition with the Debian installer, I generally specify the size
(typically in megabytes), the partition type (primary or logical), and,
if the size is less than the amount of free space, whether I want it at
the beginning of the free space or the end of the free space. Rounding
of sizes, boundary alignment, etc. is all controlled by the Debian installer
or the partitioning tools it uses (parted, generally). And I have no
control over that.
As an example, my existing disk partitions, created by the Debian installer,
look like this:
# parted /dev/i2o/hda unit s print free
Model: I2O Controller (i2o)
Disk /dev/i2o/hda: 286748672s
Sector size (logical/physical): 512B/512B
Partition table: msdos
Number Start End Size Type File system Flags
63s 2047s 1985s Free Space
1 2048s 194559s 192512s primary ext3 boot
194560s 196605s 2046s Free Space
2 196606s 162306302s 162109697s extended
5 196608s 17772543s 17575936s logical linux-swap(v1)
6 17774592s 56834047s 39059456s logical ext3
7 56836096s 64647167s 7811072s logical ext3
8 64647231s 162306302s 97659072s logical ext3
162306303s 286748671s 124442369s Free Space
#
As you can see, something, somewhere, has done a number on me. The only
boundary requirement is that the starting sector be a multiple of 8 to make
4096-byte boundaries. So why start the first partition at sector number
2048? The only intentional free space is the free space at the end of the
disk. The other free space entries were added by the partitioning program.
And for what purpose? This is not a GPT disk, so no BIOS boot partition
needs to be created for GRUB. (I'm not even using GRUB, I'm using LILO.
But the Debian installer would not have known what boot loader I planned
to use during the disk partitioning phase. It would, however, have known
that this is an MBR disk, not a GPT disk.) Furthermore, this is not a
UEFI-based system, so no EFI System partition (ESP) needs to be created
either. So why did the Debian installer leave these two free spaces before
and after my first partition? (Apparently, sectors 0-62 are considered part
of "meta data" and are therefore not included in the leading free space.)
Also, as you can see, the start of the next partition is not just one sector
number higher than the end of the previous partition. In the case of adjacent
logical partitions inside the extended partition, I realize that it must
leave room for an Extended Boot Record before each logical partition, but it
leaves way more room than that would require. Can you (or anyone) explain
why this wasted space has been built in?
--
.''`. Stephen Powell
: :' :
`. `'`
`-
Date: Tue, 17 Dec 2013 02:23:53 -0600
From: Stan Hoeppner <stan@hardwarefreak.com>
To: debian-user@lists.debian.org
Subject: Re: Wasted space in hard disk partitioning (was Soliciting Hardware
Recommendations)
Message-ID: <[🔎] 52B00A19.7060404@hardwarefreak.com">[🔎] 52B00A19.7060404@hardwarefreak.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On 12/16/2013 10:12 PM, Stephen Powell wrote:
> On Mon, 16 Dec 2013 08:13:16 -0600, Stan Hoeppner wrote:
>>
>> Cool. Make sure you partition the SSD so that your first, and all,
>> partitions start on a 4KB boundary. Many guides are available for your
>> favorite partitioning tool. Linux does all IO in 4KB pages including
>> filesystem and swap. If you don't align to 4KB you may get excessive
>> erase cycles on the SSD, lowering performance, and cell life. Most
>> folks seem to start the first SSD partition at sector 2048, which falls
>> immediately after the first 1MB of the device. 1,048,576/4,096=256. So
>> your first partition will start at 4KB "page 257", if you will. If you
>> create multiple partitions, make sure the size of each is evenly
>> divisible by 4096 bytes, or they won't be aligned.
>
> That's good to know. But I really don't have much control over this
> when I partition using the Debian installer.
...
Then boot a suitable live CD/DVD first and partition the SSD manually
with parted. E.g.
# parted
(parted) unit s
(parted) mkpart primary 2048 206847
(parted) set 1 boot on
(parted) mkpart primary linux-swap 206848 2303999
(parted) set 2 swap on
(parted) mkpart primary 2304000 212019199
(parted) quit
This should give you a 100 MB partition for /boot, a 1 GB partition for
swap, and a 100 GB partition for the root filesystem and everything
else. All should be 1 MB aligned if I did my math and
"off-by-one-starting-from-zero" correctly. With /boot and swap toggled
on, the installer should use these automatically. You should only need
to tell it which filesystem to format with, and to stick the root
filesystem and everything else on the 100GB partition.
Using the above you will have some unallocated free space at the end of
the device. This is GOOD to have with an SSD. The controller will
automatically use these unallocated cells for garbage collection and
wear leveling. This will further extend the life of all cells of the drive.
...
> As you can see, something, somewhere, has done a number on me. The only
> boundary requirement is that the starting sector be a multiple of 8 to make
> 4096-byte boundaries. So why start the first partition at sector number
> 2048?
...
The issue isn't simply with 4KB sector alignment, but also the erase
block size of the SSD. Some use 128KB, some 512KB, some 1MB. But they
don't tend to publish this information. By aligning to 1MB and making
all partitions divisible by 1MB, you guarantee you're aligned to the
erase block size. I won't go into any more detail on this as it's been
thoroughly covered by others. Google "erase block".
--
Stan