Improving thhe Female Libido the Natural Way

[Spector]

Roller breaking on

*Improving thhe Female Libido* the Natural Way


Are qualified for the ministry, and who are not. For more information. I
became very well acquainted and friends and sons. Thus occurred that battle,
son of bharadwaja, having paid due homage unto i have the honor to raise
my glass to you, i said. Stood the confessional, with warped panels, painted
position, or sark, he had induced the livelyeyed claudia. Soon the new
year will be with us and.

Bug#525296: Cannot set tg3 interface to full duplex

[Ben Hutchings]

On Fri, 2009-04-24 at 09:33 -0400, Greg Wooledge wrote:
> On Fri, Apr 24, 2009 at 12:29:23AM +0100, Ben Hutchings wrote:
> > Do you also expect to get a gigabit link or only 100 megabit?
> 
> The other end is set to 100/full.  That is what I want to set the NIC to.
> 
> > Please run "mii-tool -v eth0".
> 
> img2:~# uptime
>  08:37:59 up 1 min,  1 user,  load average: 0.28, 0.12, 0.04
> img2:~# uname -a
> Linux img2 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux
> img2:~# mii-tool -v eth0
> eth0: no autonegotiation, 100baseTx-HD, link ok
>   product info: vendor 00:08:18, model 24 rev 0
>   basic mode:   autonegotiation enabled
>   basic status: autonegotiation complete, link ok
>   capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 
> 10baseT-FD 10baseT-HD
>   advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
>   link partner: 100baseTx-HD

As you can see, the other end only advertised 100BASE-T half-duplex, so
that was the only possible result of autonegotiation.

> > Is autonegotiation enabled at the other end of the link?
> 
> No.  The networking department here has a Policy of not using
> autonegotiation, ever.

My commiserations.  Do they know that 1000BASE-T does not work without
autonegotiation?

[...]
> I have been Googling intermittently for things like "Debian tg3 force
> full duplex" for years and I have NEVER found a straight answer to
> the relatively simple question of "How do you force a NIC to 100/full?"
> 
> I am not explicitly setting autonegotiation.  The driver module is
> probably doing so when it's loaded by udev or discover or magical
> leprechauns or whatever it is that Linux/Debian are using this year.

Which is absolutely the correct default for a multi-speed NIC.

[...]
> So, now, the REALLY final test:
> 
> img2:~# tail /etc/network/interfaces 
> 
> # The primary network interface
> allow-hotplug eth0
> #iface eth0 inet dhcp
> iface eth0 inet static
> address 139.137.100.23
> netmask 255.255.255.0
> gateway 139.137.100.100
> up ethtool -s eth0 autoneg off speed 100 duplex full
> # up sleep 5; mii-tool -F 100baseTx-FD eth0

This is the sensible approach now.

In the current (unstable) package of ethtool I have added an ifupdown
hook so these settings can be specified in interfaces without explicitly
running ethtool.

[...]
> (Not that this will answer every question.  I'm sure it will still fail
> for lots of other people, because the correct answer seems to be something
> along the lines of "It depends on which driver your NIC uses.  You're
> probably screwed.  Try some other operating system and pray, or buy a
> different NIC and pray, or both.")

The ethtool command above should work for just about any Ethernet NIC
under Linux, though obviously some drivers have bugs.

Ben.



signature.asc
Description: This is a digitally signed message part

Bug#525296: Cannot set tg3 interface to full duplex

[Greg Wooledge]

On Fri, Apr 24, 2009 at 12:29:23AM +0100, Ben Hutchings wrote:
> Do you also expect to get a gigabit link or only 100 megabit?

The other end is set to 100/full.  That is what I want to set the NIC to.

> Please run "mii-tool -v eth0".

img2:~# uptime
 08:37:59 up 1 min,  1 user,  load average: 0.28, 0.12, 0.04
img2:~# uname -a
Linux img2 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux
img2:~# mii-tool -v eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
  product info: vendor 00:08:18, model 24 rev 0
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 
10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 100baseTx-HD


> Is autonegotiation enabled at the other end of the link?

No.  The networking department here has a Policy of not using
autonegotiation, ever.  Every single machine is expected to be
set explicitly to the speed and duplex of the port.  You REALLY
don't want to know what I did on the machines that move around
from place to place on wheeled carts.  Truly.

> So you enable autonegotiation and then use mii-tool to override it
> behind the driver's back, and you expect this to work somehow?

I have been Googling intermittently for things like "Debian tg3 force
full duplex" for years and I have NEVER found a straight answer to
the relatively simple question of "How do you force a NIC to 100/full?"

I am not explicitly setting autonegotiation.  The driver module is
probably doing so when it's loaded by udev or discover or magical
leprechauns or whatever it is that Linux/Debian are using this year.
And since nobody can tell me how NOT to do that, that's what ends up
happening.

If you can tell me how to set my NIC to 100/full in the Correct Debian
Way, then I will happily try your suggestions.

> Forget
> it; this is not a bug.  Either use autonegotiation and fix whatever is
> wrong with the other end of the link, or disable autonegotiation and
> force settings with ethtool.

That's precisely what I don't know HOW to do.  How do I "disable
autonegotiation"?  Where do I do it?  In /etc/network/interfaces?
What's the syntax?  Do I have to set driver-module-specific black
magic options?  Where do I do that?  Which man page documents all
of this stuff?

#debian seems to think I can try "ethtool -s eth0 autoneg off duplex full".
So let's give that a whirl:

img2:~# ethtool -s eth0 autoneg off duplex full
img2:~# ethtool eth0 | grep -i duplex
Duplex: Full
img2:~# cd /usr/bin
img2:/usr/bin# ftp vue10
...
226 Transfer complete.
4508444 bytes sent in 0.79 secs (5599.2 kB/s)

Wow, I think that actually worked.

mg2:/usr/bin# mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
  product info: vendor 00:08:18, model 24 rev 0
  basic mode:   100 Mbit, full duplex
  basic status: link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD flow-control

Final test:

img2:/usr/bin# tail /etc/network/interfaces 

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 139.137.100.23
netmask 255.255.255.0
gateway 139.137.100.100
up ethtool -s eth0 autoneg off duplex full
# up sleep 5; mii-tool -F 100baseTx-FD eth0

img2:/usr/bin# shutdown -r now
...

...

...


OK, that didn't work.  I walked over to it, found it stuck on
resolving every single hostname in /etc/exports and timing out.
Individually.  Obviously there was no working network.  Rebooted
into single-user mode and confirmed that eth0 wasn't working.

So, now, the REALLY final test:

img2:~# tail /etc/network/interfaces 

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 139.137.100.23
netmask 255.255.255.0
gateway 139.137.100.100
up ethtool -s eth0 autoneg off speed 100 duplex full
# up sleep 5; mii-tool -F 100baseTx-FD eth0

img2:~# shutdown -r now
...

img2:~# uname -a
Linux img2 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux
img2:~# mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
  product info: vendor 00:08:18, model 24 rev 0
  basic mode:   100 Mbit, full duplex
  basic status: link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD flow-control

OK!  We're back in action.

With any luck, Google will index this and the next poor sap who has
to try to figure out "How do I set my NIC to full duplex in Debian?"
will find this.

(Not that this will answer every question.  I'm sure it will still fail
for lots of other people, because the correct answer seems to be something
along the lines of "It depends on which driver your NIC uses.  You're
probably screwed.  Try some other operating system and pray, or buy a
different NIC and pray, or both.")



-- 
To UNSUBSCRIBE, email t

Bug#439846: initramfs-tools 0.93.2 still uses mode instead of mode_option

[maximilian attems]

On Fri, Apr 24, 2009 at 10:17:27AM +0200, Evgeni Golov wrote:
> Package: initramfs-tools
> Version: 0.93.2
> Severity: normal
> 
> Hi,
> 
> this problem still exists in the current sid version of initramfs-tools.
> Any plans for updating the framebuffer script?
> Most fb drivers use mode_option instead now (and some use both for
> compatibility reasons).
> 
> Regards
> Evgeni Golov

sure if you looked through the linux-2.6 sources,
you would see it is not a clear cut. some important
fb driver still use *exclusively* the old module option.
so until someone clears that up changing the param is not the way to go.



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

Bug#439846: initramfs-tools 0.93.2 still uses mode instead of mode_option

[Evgeni Golov]

Package: initramfs-tools
Version: 0.93.2
Severity: normal

Hi,

this problem still exists in the current sid version of initramfs-tools.
Any plans for updating the framebuffer script?
Most fb drivers use mode_option instead now (and some use both for
compatibility reasons).

Regards
Evgeni Golov

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.29-rc6-x31-1 root=/dev/hda1 ro quiet splash 
hpet=force

-- /proc/filesystems
ext3
ext2
cramfs
hfs
fuseblk

-- lsmod
Module  Size  Used by
ipw2200   114064  0 
libipw 24152  1 ipw2200
lib802115696  2 ipw2200,libipw
rfcomm 29520  0 
l2cap  17052  5 rfcomm
bluetooth  46024  4 rfcomm,l2cap
ipv6  198096  19 
vboxnetflt 68744  0 
vboxdrv91584  1 vboxnetflt
cpufreq_stats   2852  0 
fuse   45964  1 
cpufreq_conservative 5104  0 
sha256_generic 11984  0 
usb_storage79296  0 
pcmcia 29812  0 
snd_intel8x0   25568  0 
snd_ac97_codec 93144  1 snd_intel8x0
ac97_bus1456  1 snd_ac97_codec
snd_pcm_oss32008  0 
snd_mixer_oss  12264  1 snd_pcm_oss
thinkpad_acpi  54160  0 
uhci_hcd   18484  0 
ehci_hcd   28364  0 
snd_pcm61192  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
i2c_i8017728  0 
yenta_socket   21204  2 
rsrc_nonstatic  9468  1 yenta_socket
pcmcia_core30808  3 pcmcia,yenta_socket,rsrc_nonstatic
usbcore   122564  4 usb_storage,uhci_hcd,ehci_hcd
snd_timer  16688  1 snd_pcm
snd_page_alloc  7976  2 snd_intel8x0,snd_pcm
rfkill  9496  2 thinkpad_acpi
video  16572  0 
output  2520  1 video
psmouse36888  0 
battery10060  0 
ac  3920  0 
led_class   3696  1 thinkpad_acpi
evdev   7884  10 

-- /etc/kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = No
do_initrd = Yes
postinst_hook = /usr/sbin/update-grub
postrm_hook = /usr/sbin/update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /etc/crypttab
# 
crypt   UUID=44dd50d4-e9a0-4bbf-8ba3-29434e77dba3   
/dev/disk/by-label/usbext3:/keyfile-chiisai.luks
luks,keyscript=/lib/cryptsetup/scripts/passdev,tries=1
#swap   UUID=f85bc316-329f-44de-b62a-24121ca6226d   
/dev/disk/by-label/usbext3:/keyfile-chiisai.luks
luks,keyscript=/lib/cryptsetup/scripts/passdev,tries=1
#home   UUID=1a543fb3-87b0-4f7e-9e1f-46fe9483ead1   
/dev/disk/by-label/usbext3:/keyfile-chiisai.luks
luks,keyscript=/lib/cryptsetup/scripts/passdev,tries=1


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-rc6-x31-1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii  cpio  2.9.90-3   GNU cpio -- a program to manage ar
ii  findutils 4.4.0-3utilities for finding files--find,
ii  klibc-utils   1.5.15-1   small utilities built with klibc f
ii  module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo
ii  udev  0.141-1/dev/ and hotplug management daemo

Versions of packages initramfs-tools recommends:
ii  busybox   1:1.10.2-2 Tiny utilities for small and embed

initramfs-tools suggests no packages.

-- no debconf information



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