[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-09-20 Thread gumptravels
** Changed in: wireless-tools (Ubuntu)
   Status: New => Confirmed

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-09-20 Thread gumptravels
Maybe if all the bug reporters try the nomination feature we can get
this looked at, or maybe someone needs to look up the maintainer info
and try and get someone working/looking at this bug.

But for now, maybe people can nominate this for hardy... I didn't see an
option for intrepid in the list it gave me.. so not sure if it only
shows a list of "remaining" versions that haven't already been nominated
for the bug.

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-09-20 Thread gumptravels
add maintainer to it

** Changed in: ifupdown (Ubuntu)
 Assignee: (unassigned) => Scott James Remnant (scott)

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-09-20 Thread gumptravels
add maintainer to bug

** Changed in: wireless-tools (Ubuntu)
 Assignee: (unassigned) => Scott James Remnant (scott)

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-09-21 Thread gumptravels
Its a bug, if you read more of the bug reports, you'll see that things
actually don't work, and actually are a regression from older versions.

Specifically, DHCP doesn't work on virtual ethernet interfaces (such as
eth0:0), and if DHCP is on the parent interface (eth0), that when you
stop the DHCP client/tools, it takes down the parent interface along
with all/any virtual interfaces.

Tyler.

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-06-09 Thread gumptravels
Using Hardy updated to latest updates as of today, 32-bit, on a Quad
Xeon machine with an Intel 10/100 2-port NIC, the following
/etc/network/interfaces still causes such errors:

/etc/network/interfaces:
auto eth1 eth1:0 eth1:1
iface eth1 inet static
address 192.168.0.109
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255

iface eth1:0 inet static
   address 192.168.10.109
   netmask 255.255.255.0
   network 192.168.10.0
   broadcast 192.168.10.255

iface eth1:1 inet dhcp

# /etc/init.d/networking restart
 * Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.eth1:1.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Bind socket to interface: No such device
Failed to bring up eth1:1.
   ...done.

eth1  Link encap:Ethernet  HWaddr 00:02:a5:5c:d9:35  
  inet addr:192.168.0.109  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::202:a5ff:fe5c:d935/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:607 errors:0 dropped:0 overruns:0 frame:0
  TX packets:437 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:55066 (53.7 KB)  TX bytes:66634 (65.0 KB)

eth1:0Link encap:Ethernet  HWaddr 00:02:a5:5c:d9:35  
  inet addr:192.168.10.109  Bcast:192.168.10.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


It does however work with the non-dhcp virtual interface, which I couldn't get 
working until I figured out to put all the virtual devices on the same 'auto' 
line as their parent device, many examples on the net (debian docs) don't 
include that little note.

# uname -a
Linux www 2.6.13-15.18-smp #1 SMP Tue Oct 2 17:36:20 UTC 2007 i686 i686 i386 
GNU/Linux

Other note: I removed the wireless-tools package (which also took
ubuntu-minimal package with it), it didn't make any difference.

Other note2: So to sum up, it works for me with static virtual
interfaces, but not dhcp interfaces.  Writing this note right now, makes
me think that you may not be able use dhcp on virtual interfaces since
the mac address would be the same as all the other virtual interfaces on
that same parent, and the same as the parent itself.  However, allowing
DHCP on a virtual interface still makes sense, as long as its the only
virtual interfaces using dhcp, and the parent is not using dhcp.
Otherwise, I guess one could make sure to use the parent device as the
dhcp interface, and then static virtual interfaces for the rest, not
sure if this is by design or not.

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias

2008-06-09 Thread gumptravels
I decided to try my theory of using dhcp on the parent interface only.
It works and sends out dhcp requests as expected, if it doesn't get any
responses, the virtual interfaces have to wait for it to be backgrounded
before they are brought up (not a big deal.. 10-15 seconds or something
I think), but the downside, is that if you ifdown eth1 (the parent
interface with dhcp on it), you down all of the virtual interfaces.

I'm guessing the downing of all virtual interfaces is intentional.. and
makes sense, however, this limits us to not being able to shutdown the
dhcp side of the nic without killing the rest of the virtual interfaces.
If the dhcp could run on a virtual interface (assuming the parent and
the other virtual interfaces are not using dhcp, since the mac address
is shared), one could ifup/ifdown the dhcp virtual interface without
affecting the parent or other virtual interfaces on the card.

Thankfully this bug/design is not hindering roll-out, and is more of an
observation showing usability issues.

Regards,
Tyler.

-- 
'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
https://bugs.launchpad.net/bugs/123773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 106821] Re: smartmontools/smartctl does not work on SATA drives on Linux Kernel 2.6.20-15.27

2008-02-08 Thread gumptravels
Okay, I tried the server kernel on the system with the nforce3 chipset
(storage2 machine), and it still produces the following output and does
not work:

[EMAIL PROTECTED]:~# smartctl --device=ata -s on /dev/sda
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
Error SMART Status command failed
Please get assistance from http://smartmontools.sourceforge.net/
Register values returned from SMART Status command are:
CMD=0x50
FR =0x00
NS =0x00
SC =0x00
CL =0x00
CH =0x00
SEL=0x00
A mandatory SMART command failed: exiting. To continue, add one or more '-T 
permissive' options.

So it seems it may be chipset related... are there any fixes that can be
backported to feisty?

Hardware report as follows:
[EMAIL PROTECTED]:~# lspci
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev 
a2)
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) 
(rev a2)
00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) 
(rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge 
(rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address 
Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM 
Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL [Radeon 
8500 LE]
02:06.0 Ethernet controller: Intel Corporation 82543GC Gigabit Ethernet 
Controller (Copper) (rev 02)

[EMAIL PROTECTED]:~# uname -a
Linux storage2 2.6.20-16-server #2 SMP Fri Feb 1 03:10:48 UTC 2008 i686 
GNU/Linux

[EMAIL PROTECTED]:~# cat /proc/cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 15
model   : 12
model name  : AMD Athlon(tm) 64 Processor 3000+
stepping: 0
cpu MHz : 1000.000

-- 
smartmontools/smartctl does not work on SATA drives on Linux Kernel 2.6.20-15.27
https://bugs.launchpad.net/bugs/106821
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 106821] Re: smartmontools/smartctl does not work on SATA drives on Linux Kernel 2.6.20-15.27

2008-02-08 Thread gumptravels
This bug is still current on some systems, I just updated to the
following kernel on two feisty systems, and one works, and one still
does not.

Linux storage2 2.6.20-16-generic #2 SMP Fri Feb 1 02:59:08 UTC 2008 i686
GNU/Linux

The 'storage2' machine is using an nforce3 chipset as follows:

00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller
(v2.5) (rev a2)

The other system with the 'server' kernel seems to work (different sata
controller also):

Linux blacktower 2.6.20-16-server #2 SMP Fri Feb 1 03:10:48 UTC 2008
i686 GNU/Linux

The 'blacktower' is running an nforce2 chipset with the following sata
PCI card:

01:08.0 Mass storage controller: Promise Technology, Inc.
PDC20518/PDC40518 (SATAII 150 TX4) (rev 02)

Either the generic kernel does not seem to work with smart still, or its
chipset related..

I will try installing the server kernel on the storage2 machine and try
to get back to this thread.. but for now, either the generic kernel is
still a problem, or there is a chipset related problem.

-- 
smartmontools/smartctl does not work on SATA drives on Linux Kernel 2.6.20-15.27
https://bugs.launchpad.net/bugs/106821
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 18720] Re: smartmontools doesn't work with SATA disks

2008-02-08 Thread gumptravels
Smartmontools 5.37 does not 'cure' this problem on all systems (feisty
here currently), even 5.36 works on one of my systems (promise sata
controller), but not on my other system (nforce3 CK8S chipset).  It
seems there still needs to be some kernel patches in this area, or some
backported kernel patches, if its been fixed upstream already.

-- 
smartmontools doesn't work with SATA disks
https://bugs.launchpad.net/bugs/18720
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 106821] Re: smartmontools/smartctl does not work on SATA drives on Linux Kernel 2.6.20-15.27

2008-02-08 Thread gumptravels
I tried installing a backport of smartmontools 5.37, but it has the same
issue.

The 'blacktower' system works even with 5.36 however.. so I don't think
its smartmontools related, and still a kernel issue that may need a
backported fix if its been fixed upstream already.

-- 
smartmontools/smartctl does not work on SATA drives on Linux Kernel 2.6.20-15.27
https://bugs.launchpad.net/bugs/106821
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs