Re: On Bugs and Linux Quality

[Daniel Mons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Null Ack wrote:
| Linux needs to have less scatterbrain behaviour where half done things

I'll snip the post there, as that line contains the wording I am
interested in discussing.

One thing I find very common of people migrating to Linux is that they
treat "Linux" as a single entity, or single product.  Almost as if it
were a corporate being, ala Microsoft, Oracle, etc.

"Linux", as the name is used en mass, is not a single being.  It is a
collection of literally tens of thousands of programs, all working
together.  Indeed, no two Linux distros are alike, simply because the
people providing them choose different collections of software to forge
together to offer.

I make no apologies for saying this, but "Linux" will never be "less
scatterbrain" as you put it.  The distributed nature of the coding
processes that go into Linux may well be at times one of its weaknesses,
but on the whole it is also its single greatest asset.

As someone who is obviously new to "Linux", what you need to understand
is that the "Linux" community understand the distributed, evolving
nature of software far better than the slower moving proprietary world.
~ In software, the concept of "the perfect release" is simply impossible
to achieve - software is a process, not an object, and something that
moves and flows with the needs of its users over time.  To consider it a
single release, or one-off product is the wrong way to approach it.

Yes, there are tens of thousands of bugs in "Ubuntu".  Again, you need
to realise that this encompasses code written by tens of thousands of
human beings, from thousands of different companies, all working
together to release their code in a common pool for anyone to take from.
~ Unlike a lot of proprietary software that has a vested financial
interest in proclaiming how perfect it is on release (and then proceding
to release dozens of service packs and fixes anyway), "Linux" makes no
such claims.  Complete transparency and full discolsure is the name of
the game.

And what you also need to realise is that "Linux" is no better or worse
than proprietary counterparts.  I can assure you, Microsoft have just as
many bugs across their entire suite of software.  The difference is you
as the end user don't get to see their internal bug trackers.  To their
marketing departments and shareholders, admitting fault like that would
be financial suicide.  But just because it's not out there for all to
see, doesn't make it any less real.

Linux's distributed nature can be frustrating to people new to it.  But
again, you need to understand that despite the shortcomings of the
approach, it is the single biggest reason why Linux is alive and
thriving today.  I work in professional IT (as a Linux sysadmin and
systems architect), and time and time again hear the same cry from
people with little exposure to Linux: "They just need to stop making
dozens of distros and all work together to make one killer distro", or
"they need to stop making 5 different word processors and just make one
killer app".  What's obvious about this is that the people saying it are
grossly unaware of who "they" are, and how many people that encompasses.
~ More to the point, what constitutes "the perfect app"?  By whose
definition are we quantifying perfection?

"Linux" is a massive collection of small programs that each focus on
doing one thing well.  A Linux distro is one
individual's/group's/company's idea of which of these programs should be
tied together to make an operating system.  By virtue of the fact that
there are so many large-scale distros doing so well in the market
(RedHat, SuSE, Debian and Ubuntu are generally the "big 4" that people
talk about, with other popular ones like Fedora, CentOS, Gnetoo and
others close behind).  In a perfectly free market, if something is not
good enough it will disappear through obscurity and lack of interest.
So again, by virtue of all of these distros existing and being popular,
it means that they all have users who find them interesting and usable
for a whole gamut of reasons, personal and professional.

I understand your frustration.  You have used the product, found a bug,
and found that it was not fixed in a manner you considered timely.  As
an end-user, that is frustrating.  Speaking from the point of view of a
sysadmin who deals with literally thousands of machines on a daily
basis, I can tell you that this is not limited to the Linux world by any
means.  I personally find even more frustration when I'm forced to admin
proprietary software at great financial expense, and find the support no
better or more satisfying despite the enormous financial outlay.

I'm not trying to downplay your frustrations, but in my 11 years of free
software use, I've consistently found it faster to respond to known bugs
from both an acknowledgement point of view and a fix-delivery point of
view.  Additionally, I find it easier to get support for free software
from a wi

Re: Totally Out of Ideas on Fixing Network Bug

[Daniel Mons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Null Ack wrote:
| Jun 21 04:34:46 ppp kernel: [ 5493.104588] NETDEV WATCHDOG: eth0:
| transmit timed out
| Jun 21 04:34:46 ppp kernel: [ 5493.104738] eth0: Transmit timed out,
| status 0003, PHY status 786d, resetting...
| Jun 21 04:34:46 ppp kernel: [ 5493.105384] eth0: link up, 100Mbps,
| full-duplex, lpa 0x45E1

Here's a post on the Ubuntu forums from someone who had a similar
problem, also on Via Rhine II hardware:

http://ubuntuforums.org/archive/index.php/t-586044.html

It turns out an aggressive BIOS setting was causing the issue, and
choosing some safer options in-BIOS solved their problem.

- -Dan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIXe0deFJDv0P9Qb8RAmh+AJsGEkhkVAlGblPpTke7z24xLesRtACeLIeR
Mm3ul9lYVdRHIepWYfBiKRU=
=C/Z9
-END PGP SIGNATURE-

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

On Bugs and Linux Quality

[Null Ack]

I would like to respond to Dan's comments about Linux/Ubuntu quality. To not
dilute the discussion on my specific bug Ive moved it over here.

Like all of you, I share the enthusiasm for Linux and open source software.
To me, the greatest features are the ability to see the inner mechanisms of
the software, for not just security reasons ( which is a compelling reason
all in itself) but also for the ability to understand / change core
components. However it is vitally important we do not remain critical in a
constructive way to improve the software, or more importantly, improve the
user experience.

I disagree with the notion that one bug should not effect the global
perception of Ubuntu quality. The point is, for software to be generally
useful, an expected level of robustness and capability is generally expected
in core features. If a bug prevents this from happening then the software is
not generally useful, or at the very least, is not very usable without
protracted workarounds and other annoyances.

Ubuntu has a number of flawed approaches to release management and support.
For example, not updating the Nvidia 169.12 driver in Hardy. 169.12 has
numerous oopses and other bugs, and there subsequently has been three
revisions of the driver since. Not to mention the old driver revision does
not support new Nvidia cards that have been released. Or lets look at the
many, many other device driver fixes in the vanilla kernel tree that have
not been backported into Hardy's old kernel revision. Its wishful thinking
to somehow arbitarily declare that a release is "stable" and then hardly do
any device driver updates ongoing in the "support" phase. Clearly the word
support isnt actual support - I think its more driven by a lack of resources
to upgrade the baseline as is commonly done in Vista and Leopard.

Ubuntu has tens of thousands of bugs in the bug database. Reporting bugs
does not ensure that the bug is actually fixed or indeed investigated at
all. Of those that are, many of those are sent up stream where they again
sit like a statue and not seem to be resolved.

It doesnt take much of a look at say X for example, to see the countless
people complaining about X bugs that have not been fixed. Or, how X was
"released" and declared "stable" with a known blocker and other bugs that
could be argued to actually be blockers as well.

Lets look at what the insiders are saying. A kernel hacker recently said
"I'll typically read the linux-kernel list in 1000-email batches once every
few days and each time I will come across multiple bug reports which are one
to three days old and which nobody has done anything about! And sometimes I
*know* that the person who is responsible for that part of the kernel has
read the report" He continues on answering a question about the declining
quality of Linux "I used to think it was in decline, and I think that I
might think that it still is. I see so many regressions which we never fix.
Obviously we fix bugs as well as add them, but it is very hard to determine
what the overall result of this is.When I'm out and about I will very often
hear from people whose machines we broke in ways which I'd never heard about
before. I ask them to send a bug report (expecting that nothing will end up
being done about it) but they rarely do.So I don't know where we are and I
don't know what to do. All I can do is to encourage testers to report bugs
and to be persistent with them, and I continue to stick my thumb in
developers' ribs to get something done about them.I do think that it would
be nice to have a bugfix-only kernel release. One which is loudly publicised
and during which we encourage everyone to send us their bug reports and
we'll spend a couple of months doing nothing else but try to fix them. I
haven't pushed this much at all, but it would be interesting to try it once.
If it is beneficial, we can do it again some other time." His name is Andrew
Morton...

Linux needs to have less scatterbrain behaviour where half done things are
left and the chaos moves forward to the next semi complete feature. It needs
to consolidate and have a unified effort to really work on stability and bug
fixing.
-- 
ubuntu-au mailing list
ubuntu-au@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au

Re: Totally Out of Ideas on Fixing Network Bug

[Null Ack]

Hi Daniel. Thank you very much for your help on this problem.

I've trawled through all the logs, and I previously provided a relevant
section of the kernel log to the bug report:

Jun 21 04:34:46 ppp kernel: [ 5493.104588] NETDEV WATCHDOG: eth0: transmit
timed out
Jun 21 04:34:46 ppp kernel: [ 5493.104738] eth0: Transmit timed out, status
0003, PHY status 786d, resetting...
Jun 21 04:34:46 ppp kernel: [ 5493.105384] eth0: link up, 100Mbps,
full-duplex, lpa 0x45E1

Which then sets into a repeating pattern:

Jun 21 05:05:02 ppp kernel: [ 7308.203455] NETDEV WATCHDOG: eth0: transmit
timed out
Jun 21 05:05:02 ppp kernel: [ 7308.203606] eth0: Transmit timed out, status
1003, PHY status 786d, resetting...
Jun 21 05:05:02 ppp kernel: [ 7308.204254] eth0: link up, 100Mbps,
full-duplex, lpa 0x45E1
Jun 21 05:35:16 ppp kernel: [ 9121.303308] NETDEV WATCHDOG: eth0: transmit
timed out
Jun 21 05:35:16 ppp kernel: [ 9121.303457] eth0: Transmit timed out, status
1003, PHY status 786d, resetting...
Jun 21 05:35:16 ppp kernel: [ 9121.304106] eth0: link up, 100Mbps,
full-duplex, lpa 0x45E1

This occurs shortly before the first occurance in the kernel log:

Jun 21 04:29:46 ppp kernel: [ 5193.747505] irq 23: nobody cared (try booting
with the "irqpoll" option)
Jun 21 04:29:46 ppp kernel: [ 5193.747514] Pid: 0, comm: swapper Tainted:
P2.6.24-19-generic #1
Jun 21 04:29:46 ppp kernel: [ 5193.747516]
Jun 21 04:29:46 ppp kernel: [ 5193.747517] Call Trace:
Jun 21 04:29:46 ppp kernel: [ 5193.747519]  
[__report_bad_irq+0x1e/0x80] __report_bad_irq+0x1e/0x80
Jun 21 04:29:46 ppp kernel: [ 5193.747550]  [note_interrupt+0x2ad/0x2e0]
note_interrupt+0x2ad/0x2e0
Jun 21 04:29:46 ppp kernel: [ 5193.747562]  [handle_fasteoi_irq+0xa1/0x110]
handle_fasteoi_irq+0xa1/0x110
Jun 21 04:29:46 ppp kernel: [ 5193.747571]  [do_IRQ+0x7b/0x100]
do_IRQ+0x7b/0x100
Jun 21 04:29:46 ppp kernel: [ 5193.747577]  [ret_from_intr+0x0/0x0a]
ret_from_intr+0x0/0xa
Jun 21 04:29:46 ppp kernel: [ 5193.747583]  [pci_conf1_read+0x0/0x100]
pci_conf1_read+0x0/0x100
Jun 21 04:29:46 ppp kernel: [ 5193.747596]  [__do_softirq+0x60/0xe0]
__do_softirq+0x60/0xe0
Jun 21 04:29:46 ppp kernel: [ 5193.747609]  [call_softirq+0x1c/0x30]
call_softirq+0x1c/0x30
Jun 21 04:29:46 ppp kernel: [ 5193.747614]  [do_softirq+0x35/0x90]
do_softirq+0x35/0x90
Jun 21 04:29:46 ppp kernel: [ 5193.747618]  [irq_exit+0x88/0x90]
irq_exit+0x88/0x90
Jun 21 04:29:46 ppp kernel: [ 5193.747621]  [do_IRQ+0x80/0x100]
do_IRQ+0x80/0x100
Jun 21 04:29:46 ppp kernel: [ 5193.747624]  [default_idle+0x0/0x40]
default_idle+0x0/0x40
Jun 21 04:29:46 ppp kernel: [ 5193.747628]  [default_idle+0x0/0x40]
default_idle+0x0/0x40
Jun 21 04:29:46 ppp kernel: [ 5193.747630]  [ret_from_intr+0x0/0x0a]
ret_from_intr+0x0/0xa
Jun 21 04:29:46 ppp kernel: [ 5193.747633]  
[lapic_next_event+0x0/0x10] lapic_next_event+0x0/0x10
Jun 21 04:29:46 ppp kernel: [ 5193.747648]  [default_idle+0x29/0x40]
default_idle+0x29/0x40
Jun 21 04:29:46 ppp kernel: [ 5193.747654]  [cpu_idle+0x6f/0xc0]
cpu_idle+0x6f/0xc0
Jun 21 04:29:46 ppp kernel: [ 5193.747662]  [start_kernel+0x2c5/0x350]
start_kernel+0x2c5/0x350
Jun 21 04:29:46 ppp kernel: [ 5193.747670]
[x86_64_start_kernel+0x12e/0x140] _sinittext+0x12e/0x140
Jun 21 04:29:46 ppp kernel: [ 5193.747678]
Jun 21 04:29:46 ppp kernel: [ 5193.747679] handlers:
Jun 21 04:29:46 ppp kernel: [ 5193.747680] [usbcore:usb_hcd_irq+0x0/0x60]
(usb_hcd_irq+0x0/0x60 [usbcore])
Jun 21 04:29:46 ppp kernel: [ 5193.747702]
[via_rhine:rhine_interrupt+0x0/0x7f0] (rhine_interrupt+0x0/0x7f0
[via_rhine])
Jun 21 04:29:46 ppp kernel: [ 5193.747710] Disabling IRQ #23

As I said in the bug report comments, I am not using an Intel nic. My module
is the via-rhine. as per lspci

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
7c)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ed
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- 

Therefore:

[EMAIL PROTECTED]:~$ sudo rmmod via-rhine
[EMAIL PROTECTED]:~$ sudo modprobe via-rhine

I like the idea of a workaround :) I had one, where I manually added the
default gateway but that failed after another suggestion of hacking up the
aspci conf so I need to go back to the original conf to retest.

Will test your suggestions, thanks
-- 
ubuntu-au mailing list
ubuntu-au@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au

Re: Totally Out of Ideas on Fixing Network Bug

[Daniel Mons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Null Ack wrote:
| Gday everyone :)
|
| So Im having alot of problems with loosing eth0 connectivity after a
| period of time. I'm trying to be an advocate for Ubuntu, but it's hard
| when a major bug makes the experience painful. I'm desperate to fix this
| problem. I have various things up on the lanuchpad bug report at:
|
| https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/111282
|
| Many thanks for any help.
|

"dmesg" is a program that prints out errors/information directly from
the kernel to the screen.

After this bug happens, could you please collect the output of dmesg,
and past the last dozen lines or so to the mailing list.

There appears to be a known issue with the Intel 82573L only being able
to be detected at boot time.  It also appears that when waking from
sleep, the device is not properly initialised.  This is not specific to
Ubuntu either - it is a kernel level issue (thus it affects all Linux
distros).  Fixing these sorts of issues require someone with more
intimate knowledge of both the hardware and the kernel.  Intel
themselves are quite excellent with their contribution to kernel code,
and I would assume they will issue a fix shortly.

In the meantime, the suggested workaround is to do a complete module reload

sudo /etc/init.d/networking stop
sudo rmmod e1000
sudo depmod e1000
sudo modprobe e1000
sudo /etc/init.d/networking start

Again, if you could do that, check if network connectivity resumes, and
if it does, collect the output of "dmesg".

If the workaround works for you, you can turn it into a script to run on
demand.  While it's not ideal, it might get you working in the short
term until a kernel level fix finds its way downstream into Ubuntu.

Again, please don't judge the overall quality of either Ubuntu or Linux
in general on this one issue.  Linux supports quite literally tens of
thousands of devices perfectly.  Those that aren't working are not swept
under the rug either.  Linux is very much about full disclosure.  The
fact that you've already reported the bug is an excellent first step
(indeed, far more than most people do), and will aide Ubuntu and other
distros in finding what's at fault, and beginning the task of fixing the
problem.

- -Dan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIXW7LeFJDv0P9Qb8RAiEMAJ9otXk41xSQIb0bq4Y8QRP1fO2HpQCgge5n
o1rUSzL8NPflMRyvmRUslq8=
=wwA1
-END PGP SIGNATURE-

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

Re: Totally Out of Ideas on Fixing Network Bug

[Null Ack]

Thanks Dave. Its a desktop on a static private IP. The machine is set not to
sleep. All of these details and all of my attempts at resolution are in the
bug notes  https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/111282 on
launchpad. It was orignally another persons bug that I confirmed and it
appears while symptoms are the same cause is different. I refuse to give up
but its not looking hopeful for me as I have exhausted all avenues I can
think of short of paying for professional help which I assume would be
$. :( Im a professional myself (albeit somewhat new to Linux
specifically) so theres some pride / ego here too!
-- 
ubuntu-au mailing list
ubuntu-au@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au

Re: Totally Out of Ideas on Fixing Network Bug

[Dave Hall]

On Sat, 2008-06-21 at 14:15 +1000, Null Ack wrote:
> Gday everyone :)
> 
> So Im having alot of problems with loosing eth0 connectivity after a
> period of time. I'm trying to be an advocate for Ubuntu, but it's hard
> when a major bug makes the experience painful. I'm desperate to fix
> this problem. I have various things up on the lanuchpad bug report at:
> 
> https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/111282
> 
> Many thanks for any help.

Are you using Network Manager?  If so have you tried clicking on the
icon and selecting the network again after your laptop wakes up?

Cheers

Dave


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

Re: Optus Wireless

[Dave Hall]

On Sat, 2008-06-21 at 18:38 +1000, Jetjoint wrote:
> Hey guys,
> 
> First post here.
> Does anyone use an Optus Wireless Broadband USB Modem on Ubuntu? I am 
> looking at getting one and just wondering how easy it is to set up? Any 
> links to pages that might help?

If it is the Huawei E220, I am using a VF branded version and it works
great.  Avoid the E169 (as shipped by 3 and others?) it needs some hacks
to udev to make it work properly.

If you want to use the E220 with Network Manager you need to hack a
couple of config files, then it works well.  Let me know if you need the
files.

Cheers

Dave


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

Re: eee pc wireless died after latest update

[Dave Hall]

On Sat, 2008-06-21 at 18:35 +1000, Mark M Lambert wrote:
> On Sat, 21 Jun 2008 13:26:11 +1000, "James Takac" <[EMAIL PROTECTED]>
> said:
> > Hi Guys
> > 
> > Just did the latest upgrade on my epc and lost wireless capability.
> > Worked 
> > fine in gutsy before the update though. I was using the ndiswrapper. Just 
> > checked to see if a new kernel has been installed and it has, i.e.
> > 2.6.22.15. 
> > Works fine when booting into previous kernel so my Q is does anyone know
> > how 
> > to get the eee pc's wifi going in the new kernel using ndiswrapper or do
> > I 
> > need to look at the mad wifi drivers?
> > 
> > James
> 
> I've always used the madwifi drivers and they work fine for me, but have
> to recompile/reinstall after any kernel upgrade.

This is the most reliable way of doing it.  Hopefully Intrepid will
include the madwifi driver with the support for the atheros chipset the
eee pc uses.  The wiki docs make it pretty easy -
https://help.ubuntu.com/community/EeePC

btw it is worth installing the netbook remix on an eee pc with hardy :)

Cheers

Dave


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

Re: DHCPD3 "No subnet declaration for eth0 (0.0.0.0)" - SOLVED

[Karl Goetz]

On Sat, 2008-06-21 at 03:46 -0700, Slawek Drabot wrote:
> "I dont see an 'auto eth0' line here. does it come up?
> kk"
> 
> you got it: it wasn't. Didn't like the gateway address. Mind you, that was no 
> where near the error message I received from ifup
> 
> wouldn't it be nice to have an error message from DHCPD to the effect of: 
> DHCPD failed as eth0 is not up. eth0 is not up because you screwed up the 
> gateway address???
> 

well, it told you that it couldnt bind for the ip eth0 was on (0.0.0.0).
it doesnt know/care that eth0 is down, it just knows the ip isnt what it
wanted.
kk

> 
>   
-- 
Karl Goetz,
Debian user / Ubuntu contributor / gNewSense contributor
http://www.kgoetz.id.au


signature.asc
Description: This is a digitally signed message part
-- 
ubuntu-au mailing list
ubuntu-au@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au

Re: DHCPD3 "No subnet declaration for eth0 (0.0.0.0)" - SOLVED

[Slawek Drabot]

"I dont see an 'auto eth0' line here. does it come up?
kk"

you got it: it wasn't. Didn't like the gateway address. Mind you, that was no 
where near the error message I received from ifup

wouldn't it be nice to have an error message from DHCPD to the effect of: DHCPD 
failed as eth0 is not up. eth0 is not up because you screwed up the gateway 
address???


  

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

Re: DHCPD3 "No subnet declaration for eth0 (0.0.0.0)"

[Karl Goetz]

On Sat, 2008-06-21 at 01:22 -0700, Slawek Drabot wrote:
> set up a DHCPD on Ubuntu 8.04 and all was working well until I rebooted. Now 
> DHCPD does not come up and above error is found in /var/log/daemon.log
> 

trim

> 
> /etc/ltsp/dhcpd.conf
> #
> # Default LTSP dhcpd.conf config file.
> #
> 
> #log-facility local7;
> 
> authoritative;
> 
> subnet 192.168.2.0 netmask 255.255.255.0 {
> range 192.168.2.2 192.168.2.5;
> option domain-name "*";
> option domain-name-servers 192.168.1.254;
> option broadcast-address 192.168.1.255;
> option routers 192.168.1.1;

Sure you want your router on a different network?

> #next-server 192.168.2.1;
> #get-lease-hostnames true;
> #option subnet-mask 255.255.255.0;
> option root-path "/opt/ltsp/i386";
> if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
> filename "/ltsp/i386/pxelinux.0";
> } else {
> filename "/ltsp/i386/nbi.img";
> }
> }
> 
> 
> /etc/network/interfaces
> auto lo
> iface lo inet loopback
> 
> 
> iface wlan0 inet dhcp
> wireless-key 
> wireless-essid 
> 
> auto wlan0
> 
> iface eth0 inet static
> address 192.168.2.1
> netmask 255.255.255.0
> network 192.168.2.0
> broadcast 192.168.2.255
> 

I dont see an 'auto eth0' line here. does it come up?
kk

> --
> 
> strangely enough, I can get dhcpd to listen on wlan0, but clearly I want that 
> to be eth0.
> 
> Any help appreciated.
> 
-- 
Karl Goetz,
Debian user / Ubuntu contributor / gNewSense contributor
http://www.kgoetz.id.au


signature.asc
Description: This is a digitally signed message part
-- 
ubuntu-au mailing list
ubuntu-au@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au

Optus Wireless

[Jetjoint]

Hey guys,

First post here.
Does anyone use an Optus Wireless Broadband USB Modem on Ubuntu? I am 
looking at getting one and just wondering how easy it is to set up? Any 
links to pages that might help?

Thanks for any info

Jetjoint

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

Re: eee pc wireless died after latest update

[Mark M Lambert]

On Sat, 21 Jun 2008 13:26:11 +1000, "James Takac" <[EMAIL PROTECTED]>
said:
> Hi Guys
> 
> Just did the latest upgrade on my epc and lost wireless capability.
> Worked 
> fine in gutsy before the update though. I was using the ndiswrapper. Just 
> checked to see if a new kernel has been installed and it has, i.e.
> 2.6.22.15. 
> Works fine when booting into previous kernel so my Q is does anyone know
> how 
> to get the eee pc's wifi going in the new kernel using ndiswrapper or do
> I 
> need to look at the mad wifi drivers?
> 
> James

I've always used the madwifi drivers and they work fine for me, but have
to recompile/reinstall after any kernel upgrade.

Cheers
Mark

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

DHCPD3 "No subnet declaration for eth0 (0.0.0.0)"

[Slawek Drabot]

set up a DHCPD on Ubuntu 8.04 and all was working well until I rebooted. Now 
DHCPD does not come up and above error is found in /var/log/daemon.log


files:
-
/etc/default/dhcp3-server
# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/dhcp3-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES=eth0


/etc/ltsp/dhcpd.conf
#
# Default LTSP dhcpd.conf config file.
#

#log-facility local7;

authoritative;

subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.2 192.168.2.5;
option domain-name "*";
option domain-name-servers 192.168.1.254;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
#next-server 192.168.2.1;
#get-lease-hostnames true;
#option subnet-mask 255.255.255.0;
option root-path "/opt/ltsp/i386";
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
} else {
filename "/ltsp/i386/nbi.img";
}
}


/etc/network/interfaces
auto lo
iface lo inet loopback


iface wlan0 inet dhcp
wireless-key 
wireless-essid 

auto wlan0

iface eth0 inet static
address 192.168.2.1
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255

--

strangely enough, I can get dhcpd to listen on wlan0, but clearly I want that 
to be eth0.

Any help appreciated.



  

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

Re: eee pc wireless died after latest update

[Gilles Gravier]

I'm using Eee Ubuntu and haven't had the slightest problem with any update.

Gilles.

James Takac wrote:

Hi Guys

Just did the latest upgrade on my epc and lost wireless capability. Worked 
fine in gutsy before the update though. I was using the ndiswrapper. Just 
checked to see if a new kernel has been installed and it has, i.e. 2.6.22.15. 
Works fine when booting into previous kernel so my Q is does anyone know how 
to get the eee pc's wifi going in the new kernel using ndiswrapper or do I 
need to look at the mad wifi drivers?


James

  


--
/*Gilles Gravier*/ *=* [EMAIL PROTECTED] 
ICQ : *77488526* 
 * || *MSN 
Messenger : [EMAIL PROTECTED] *
*Skype : ggravier * || *Y! : ggravier 
 || AOL : gillesgravier 

PGP Key ID : *0x8DE6D026* 


"Chastity is its own punishment." (/Solomon Short/) [/David Gerrold/]
"De toutes les aberrations sexuelles, la chasteté est la plus 
aberrante." [Anatole France]


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