|
|
RE: Ubuntu 8.04 LTS boot problems - File system is NOT clean: msg#03712ubuntu-users
Hi All, Thanks for the great work you are doing, I really enjoy this list and have learned a lot from it. I am running VMware ESx 3i on a dell PE2850 server, I have about 5 Linux vms running on this. I had a system crash yesterday morning and had some problems getting it up and running again, it freezed on boot. This is my main email server and also nfs server. After booting from cd and running fsck the server booted up fine. But I would like to schedule reboot over the weekend to see if it boots fine. Can you please assist me with this error, I am not sure yet what exactly happened. Here is the output from my log: (any help would be great) Reiserfs super block in block 16 on 0x807 of format 3.6 with standard journal Blocks (total/free): 3289296/2906825 by 4096 bytes File system is NOT clean Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal Blocks (total/free): 39321072/19976457 by 4096 bytes File system is NOT clean Reiserfs super block in block 16 on 0x807 of format 3.6 with standard journal Blocks (total/free): 3289296/2906825 by 4096 bytes File system is NOT clean Paul Send ubuntu-users mailing list submissions to ubuntu-users@xxxxxxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-users or, via email, send a message with subject or body 'help' to ubuntu-users-request@xxxxxxxxxxxxxxxx You can reach the person managing the list at ubuntu-users-owner@xxxxxxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of ubuntu-users digest..." Today's Topics: 1. Re: WICD (Shannon McMackin) 2. Re: procmail filter for mailinglist (Derek Broughton) 3. Re: Dual-boot setup still not working... (Derek Broughton) 4. Re: Customise or Remaster ubuntu 9.04 jaunty from an image file (NoOp) 5. Re: File system locked on upgrade (Derek Broughton) 6. Re: WICD (NoOp) 7. Re: drivers/net/usb/asix - Re: WS-UL220G USB 2.0 Gigabit Ethernet Adapter in Dell Inspiron 700m laptop (Zenaan Harkness) ---------------------------------------------------------------------- Message: 1 Date: Thu, 16 Jul 2009 22:18:23 -0400 From: Shannon McMackin <smcmackin@xxxxxxxxx> Subject: Re: WICD To: ubuntu-users@xxxxxxxxxxxxxxxx Message-ID: <h3on1f$1fh$1@xxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 07/16/2009 07:23 PM, Karl F. Larsen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Fred Roller wrote: >> On Thu, 2009-07-16 at 16:51 -0600, Karl F. Larsen wrote: >>> Not on my Jaunty. It fumbles around and says it can't find it. >>> How do I >>> add the universe repository? maybe man apt-get? >> gksu gedit /etc/apt/source.list >> >> uncomment the two lines that look like: >> >> # deb http://us.archive.ubuntu.com/ubuntu/ jaunty universe >> # deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty universe >> >> so they look like >> >> deb http://us.archive.ubuntu.com/ubuntu/ jaunty universe >> deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty universe >> >> and save. >> >> then run: >> >> sudo apt-get update >> >> when complete run >> >> sudo apt-get install wicd >> > > Thank you, Thank you, that got it. I wonder why wicd is so difficult to > get? It should be a normal thing on new Ubuntu versions. > > > 73 Karl > > > - -- > > Karl F. Larsen, AKA K5DI > Linux User > #450462 http://counter.li.org. > Key ID = 3951B48D > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKX7ZcNuSIOjlRtI0RApg0AJ9qdTUnSD7adxHGnQgt8kuEECZleQCfazOd > XSH0cupzVglAWkOYguPbuew= > =dSdS > -----END PGP SIGNATURE----- > It's not that it isn't normal, it's not the standard. Everything that isn't standard in Ubuntu or things that are maintained by the community are in the universe repo. If it were an option to install WICD, then it would be in the std repo. ------------------------------ Message: 2 Date: Thu, 16 Jul 2009 23:06:22 -0300 From: Derek Broughton <derek@xxxxxxxxxxxxxx> Subject: Re: procmail filter for mailinglist To: ubuntu-users@xxxxxxxxxxxxxxxx Message-ID: <ut25j6-rqm.ln1@xxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="US-ASCII" Siggy Brentrup wrote: > On Wed, Jul 15, 2009 at 23:26 -0300, Derek Broughton wrote: >> Siggy Brentrup wrote: > >> > Never put this in your .procmailrc: by crafting a Sender: >> > xxxx-bounces@xxxxxxxxxx in a malicious message anybody can create >> > a maildir on your system, from now on any mail carrying this header >> > will be delivered to list.xxxx/ without you even noticing :) >> >> WTP? I fail to see how that's an issue. I don't use procmail, but I >> _do_ >> filter mail into essentially random maildirs. If it's spam, or any >> other malicious content, it's just sitting there in a folder - it's >> _never_ >> unnoticed. It will show up as New mail. > > Not with my MUA, it only checks mailboxes declared in .muttrc. Citing > it's author: "All mail clients suck. This one just sucks less." -me, > circa 1995 Well, many other clients have learned to suck less in the following 14 years, and even mutt does IMAP these days - which is why it doesn't matter whether mail gets directed to a brand new folder, the IMAP server still shows it. >> > Most if not all MTAs handle .forward. >> >> Absolutely, but not fetchmail itself. > > It's no MTA, no MDA, it's a mess <duck/>. No, I agree with you - but the OP was complaining that fetchmail ignored his .forward - and I was just trying to explain why (and yes, I use fetchmail too). -- derek ------------------------------ Message: 3 Date: Thu, 16 Jul 2009 23:03:05 -0300 From: Derek Broughton <derek@xxxxxxxxxxxxxx> Subject: Re: Dual-boot setup still not working... To: ubuntu-users@xxxxxxxxxxxxxxxx Message-ID: <pn25j6-rqm.ln1@xxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="US-ASCII" Victor Padro wrote: > On Thu, Jul 16, 2009 at 4:30 PM, J Bickhard<jbickhard@xxxxxxxxx> wrote: >> On Thu, Jul 16, 2009 at 2:47 PM, Karl F. Larsen<klarsen1@xxxxxxxxx> >> wrote: >>> >>> >>>>> # grub-install --root-directory=/mnt /dev/sda >>> >>> This I think is wrong. I need to look at man grub but I do not think >>> you can use grub-install unless your actually on the root directory. In >>> anycase I will try it and see what happens. Karl, you're an idiot. Of course you're wrong, again. >> What does Man do? > > man shows you the manual for certain package: > man apt > man apache2 > man sudo > etc > > in this case: > man grub In this case, "man grub-install" -- derek ------------------------------ Message: 4 Date: Thu, 16 Jul 2009 19:21:11 -0700 From: NoOp <glgxg@xxxxxxxxxxxxx> Subject: Re: Customise or Remaster ubuntu 9.04 jaunty from an image file To: ubuntu-users@xxxxxxxxxxxxxxxx Message-ID: <h3on6o$1v7$1@xxxxxxxxxxxxx> Content-Type: text/plain; charset=UTF-8 On 07/16/2009 12:25 PM, DIPIN KRISHNA wrote: > Customise or Remaster ubuntu 9.04 jaunty from an image > file<http://blog.dipinkrishna.info/2009/07/customise-or-remaster-ubuntu-904-jaunty.html> > > See > Customise or Remaster ubuntu 9.04 jaunty from an image > file<http://blog.dipinkrishna.info/2009/07/customise-or-remaster-ubuntu-904-jaunty.html> > > Dipin Krishna > > Thanks & well done. @David Curtis: you might want to check out Dipin's other linux tips: http://blog.dipinkrishna.info/ ------------------------------ Message: 5 Date: Thu, 16 Jul 2009 23:09:42 -0300 From: Derek Broughton <derek@xxxxxxxxxxxxxx> Subject: Re: File system locked on upgrade To: ubuntu-users@xxxxxxxxxxxxxxxx Message-ID: <6435j6-rqm.ln1@xxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="US-ASCII" David S Angulo wrote: > On Thu, Jul 16, 2009 at 2:26 PM, Derek Broughton<derek@xxxxxxxxxxxxxx> > wrote: >> Why are you still using ext2? It really isn't smart, and it's so easy to >> add a journal and turn it into ext3 (see tune2fs). Then if you manage to >> turn off the machine without properly shutting down, it'll be able to >> recover properly. >> -- >> derek >> > > I read the man page for tune2fs. I don't see what this or fsck have > to do with my failed upgrade, and I don't know what you're suggesting > I do with tune2fs. I see to add a journal I should do > > tune2fs -j > > Is that it? WIll that make it ext3? Will I need to change > /etc/fstab? Yes, yes, and yes. > Will I need to change anything else? No. > How will that help my read-only status? It won't do a thing to help _this_ time, but it will make it far less likely to happen again in the future. -- derek ------------------------------ Message: 6 Date: Thu, 16 Jul 2009 19:29:47 -0700 From: NoOp <glgxg@xxxxxxxxxxxxx> Subject: Re: WICD To: ubuntu-users@xxxxxxxxxxxxxxxx Message-ID: <h3onms$2nu$1@xxxxxxxxxxxxx> Content-Type: text/plain; charset=UTF-8 On 07/16/2009 05:50 PM, Karl F. Larsen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > NoOp wrote: >> On 07/16/2009 04:35 PM, Jay Daniels wrote: >>> On Thu, 2009-07-16 at 18:44 -0400, Fred Roller wrote: >>>> On Thu, 2009-07-16 at 16:10 -0600, Karl F. Larsen wrote: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> I recall you must have the right repository installed before you can >>>>> get wicd. I just put Jaunty on my old Sony laptop for some testing but I >>>>> just HATE Network Manager! >>>>> >>>>> Does anyone recall how to get wicd? >>>>> >>>>> 73 Karl >>>>> >>>>> - -- >>>> Installing Wicd in Ubuntu >>>> If you are using Ubuntu 9.04 (Jaunty), Wicd 1.5.9 is in the universe >>>> repository, so a simple sudo apt-get install wicd will do it. If you >>>> want the latest version of Wicd when it comes out, though, you'll need >>>> to add the Wicd repository. Jaunty users who need to download the Wicd >>>> deb package can grab it from Ubuntu's Universe repository. >>>> >>>> from: http://wicd.sourceforge.net/download.php >>>> >>> It never states where the wicd repository is located nor how to connect >>> with Hardy or how to add the repository key? >>> >>> Very confusing statements on that page. hey, want the latest version? >>> Get it from hidden repository which we are not going to tell you about. >>> >> >> You need the secret handshake... >> http://apt.wicd.net/dists/ >> https://launchpad.net/ubuntu/+source/wicd/+publishinghistory >> >> BTW: for Karl - you might want to take your remember pills :-) >> http://wicd.sourceforge.net/moinmoin >> <http://wicd.sourceforge.net/moinmoin/Wicd_on_Ubuntu> >> Wicd on Ubuntu (last edited 2009-05-26 12:54:58 by KarlLarsen) >> >> >> >> > You might just try to fix it. I do not even pretend to know how to do > many things, but by god I know wicd is so much better than the other it > is worth getting. > What on earth are you on today? Your initial post: > I recall you must have the right repository installed before you can > get wicd. I just put Jaunty on my old Sony laptop for some testing but I > just HATE Network Manager! > > Does anyone recall how to get wicd? You made a big fuss about wicd a few months ago and wrote the friggin wiki page that I pointed you to. And as an aside, either fix your newfound GnuPG signature so that it is actually a sig, or eliminate it. 15 lines of added noise is as bad as those that post their company confidentiality nonsense to the list. ------------------------------ Message: 7 Date: Fri, 17 Jul 2009 12:32:54 +1000 From: Zenaan Harkness <zen@xxxxxxxxxxxx> Subject: Re: drivers/net/usb/asix - Re: WS-UL220G USB 2.0 Gigabit Ethernet Adapter in Dell Inspiron 700m laptop To: linux-net@xxxxxxxxxxxxxxx, ubuntu-users <ubuntu-users@xxxxxxxxxxxxxxxx> Cc: dhollis@xxxxxxxxxxxxxx, dbrownell@xxxxxxxxxxxxxxxxxxxxx Message-ID: <20090717023254.GA12636@xxxxxxxxxxxx> Content-Type: text/plain; charset=us-ascii Bump. Please let me know if there is anything else I can do to narrow down why this device is not working for me. Thanks Zenaan On Sat, Jul 11, 2009 at 04:01:23AM +1000, Zenaan Harkness wrote: > I have a number of WS-UL220G USB 2.0 Ethernet adapters, new. I have > tested with two of them, see below. > > Testing in Dell Inspiron 700m laptop, a few years old, with two USB 2.0 > ports - tested in both ports. > > Kernel module is "asix" it appears. > > I'm running Ubuntu 8.04. I've tested (tonight) this device on the > following kernels: > vmlinuz-2.6.24-19-generic > vmlinuz-2.6.24-23-generic > vmlinuz-2.6.24-24-generic > > The manufacturer advertises Linux support. > > Related URLS, chipset/ controller device manufacturer page: > http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71 > > I thought I made one of these devices work about a month or two ago, > when they first arrived, with simple/ standard config/ setup, as with > any other network device. Now I have failed to make either the original > device I tested with, or another one fresh out of its packet, to work. > > > Here's my session, after a fresh reboot: > > # connect cat5 to internal device: > > $ cat /etc/network/interfaces > auto lo > iface lo inet loopback > > iface eth2 inet static > address 172.22.22.62 > netmask 255.255.255.0 > metric 29 > > iface eth0 inet static > address 172.22.22.61 > netmask 255.255.255.0 > gateway 172.22.22.2 > metric 0 > > $ ifconfig > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1498 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1498 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:77578 (75.7 KB) TX bytes:77578 (75.7 KB) > > $ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > > # modprobe asix > > # lsmod|grep asix > asix 18304 0 > usbnet 20232 1 asix > mii 6400 3 asix,usbnet,b44 > usbcore 146412 7 > asix,usbnet,hsfusbcd2,hsfosspec,ehci_hcd,uhci_hcd > > # ifup eth0 > > # ifconfig > eth0 Link encap:Ethernet HWaddr 00:0f:1f:b2:c3:44 > inet addr:172.22.22.61 Bcast:172.22.22.255 Mask:255.255.255.0 > inet6 addr: fe80::20f:1fff:feb2:c344/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:252 (252.0 B) TX bytes:2631 (2.5 KB) > Interrupt:10 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1473 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1473 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:73688 (71.9 KB) TX bytes:73688 (71.9 KB) > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 172.22.22.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 > 0.0.0.0 172.22.22.2 0.0.0.0 UG 0 0 0 eth0 > > > # syslog entries for above activities: > Jul 11 03:04:18 ip61zen kernel: [ 342.207112] ADDRCONF(NETDEV_UP): eth0: > link is not ready > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Joining mDNS multicast group on > interface eth0.IPv4 with address 172.22.22.61. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: New relevant interface eth0.IPv4 > for mDNS. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Registering new address record > for 172.22.22.61 on eth0.IPv4. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Withdrawing address record for > 172.22.22.61 on eth0. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Leaving mDNS multicast group on > interface eth0.IPv4 with address 172.22.22.61. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Interface eth0.IPv4 no longer > relevant for mDNS. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Joining mDNS multicast group on > interface eth0.IPv4 with address 172.22.22.61. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: New relevant interface eth0.IPv4 > for mDNS. > Jul 11 03:04:18 ip61zen avahi-daemon[5068]: Registering new address record > for 172.22.22.61 on eth0.IPv4. > Jul 11 03:04:18 ip61zen postfix/master[5826]: reload configuration > /etc/postfix > Jul 11 03:04:22 ip61zen kernel: [ 343.368131] b44: eth0: Link is up at 10 > Mbps, half duplex. > Jul 11 03:04:22 ip61zen kernel: [ 343.368142] b44: eth0: Flow control is off > for TX and off for RX. > Jul 11 03:04:22 ip61zen kernel: [ 343.373190] ADDRCONF(NETDEV_CHANGE): eth0: > link becomes ready > Jul 11 03:04:24 ip61zen avahi-daemon[5068]: Registering new address record > for fe80::20f:1fff:feb2:c344 on eth0.*. > Jul 11 03:04:28 ip61zen ntpdate[8520]: no server suitable for synchronization > found > Jul 11 03:04:33 ip61zen kernel: [ 344.815162] eth0: no IPv6 routers present > > > # ping 172.22.22.2 > PING 172.22.22.2 (172.22.22.2) 56(84) bytes of data. > 64 bytes from 172.22.22.2: icmp_seq=1 ttl=64 time=0.480 ms > 64 bytes from 172.22.22.2: icmp_seq=2 ttl=64 time=0.460 ms > 64 bytes from 172.22.22.2: icmp_seq=3 ttl=64 time=0.454 ms > > --- 172.22.22.2 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2000ms > rtt min/avg/max/mdev = 0.454/0.464/0.480/0.027 ms > > > All is clearly well with internal eth device. Now for external "asix" device: > > # ifdown eth0 > > # syslog: > Jul 11 03:08:38 ip61zen postfix/master[5826]: reload configuration > /etc/postfix > Jul 11 03:08:38 ip61zen avahi-daemon[5068]: Interface eth0.IPv4 no longer > relevant for mDNS. > Jul 11 03:08:38 ip61zen avahi-daemon[5068]: Leaving mDNS multicast group on > interface eth0.IPv4 with address 172.22.22.61. > Jul 11 03:08:38 ip61zen avahi-daemon[5068]: Withdrawing address record for > fe80::20f:1fff:feb2:c344 on eth0. > Jul 11 03:08:38 ip61zen avahi-daemon[5068]: Withdrawing address record for > 172.22.22.61 on eth0. > > # ifconfig > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1473 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1473 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:73688 (71.9 KB) TX bytes:73688 (71.9 KB) > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > > # disconnect cat5 from internal dev > > # connect asix/ usb 2 gige dev: > > # ifconfig > eth2 Link encap:Ethernet HWaddr 00:0e:c6:87:9b:3c > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1473 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1473 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:73688 (71.9 KB) TX bytes:73688 (71.9 KB) > > # syslog: > Jul 11 03:10:35 ip61zen kernel: [ 395.460971] usb 4-1: new high speed USB > device using ehci_hcd and address 2 > Jul 11 03:10:35 ip61zen kernel: [ 395.606195] usb 4-1: configuration #1 > chosen from 1 choice > Jul 11 03:10:35 ip61zen NetworkManager: <debug> [1247245835.564443] > nm_hal_device_added(): New device added (hal udi is > '/org/freedesktop/Hal/devices/usb_device_b95_1780_009988'). > Jul 11 03:10:35 ip61zen NetworkManager: <debug> [1247245835.692066] > nm_hal_device_added(): New device added (hal udi is > '/org/freedesktop/Hal/devices/usb_device_b95_1780_009988_if0'). > Jul 11 03:10:36 ip61zen kernel: [ 396.732266] eth2: register 'asix' at > usb-0000:00:1d.7-1, ASIX AX88178 USB 2.0 Ethernet, 00:0e:c6:87:9b:3c > Jul 11 03:10:36 ip61zen NetworkManager: <debug> [1247245836.389099] > nm_hal_device_added(): New device added (hal udi is > '/org/freedesktop/Hal/devices/net_00_0e_c6_87_9b_3c'). > Jul 11 03:10:36 ip61zen kernel: [ 148.796558] eth2: link down > Jul 11 03:10:36 ip61zen kernel: [ 148.801263] ADDRCONF(NETDEV_UP): eth2: > link is not ready > > > # ifup eth2 > > # ifconfig > eth2 Link encap:Ethernet HWaddr 00:0e:c6:87:9b:3c > inet addr:172.22.22.62 Bcast:172.22.22.255 Mask:255.255.255.0 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1475 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1475 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:73864 (72.1 KB) TX bytes:73864 (72.1 KB) > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 172.22.22.0 0.0.0.0 255.255.255.0 U 29 0 0 eth2 > 169.254.0.0 0.0.0.0 255.255.0.0 U 29 0 0 eth2 > > # syslog: > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Joining mDNS multicast group on > interface eth2.IPv4 with address 172.22.22.62. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: New relevant interface eth2.IPv4 > for mDNS. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Registering new address record > for 172.22.22.62 on eth2.IPv4. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Withdrawing address record for > 172.22.22.62 on eth2. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Leaving mDNS multicast group on > interface eth2.IPv4 with address 172.22.22.62. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Interface eth2.IPv4 no longer > relevant for mDNS. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Joining mDNS multicast group on > interface eth2.IPv4 with address 172.22.22.62. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: New relevant interface eth2.IPv4 > for mDNS. > Jul 11 03:11:44 ip61zen avahi-daemon[5068]: Registering new address record > for 172.22.22.62 on eth2.IPv4. > Jul 11 03:11:44 ip61zen postfix/master[5826]: reload configuration > /etc/postfix > Jul 11 03:12:04 ip61zen ntpdate[9283]: can't find host ntp.ubuntu.com > Jul 11 03:12:04 ip61zen ntpdate[9283]: no servers can be used, exiting > > > # connect cat5 to asix device: > > # syslog: > Jul 11 03:13:10 ip61zen kernel: [ 562.760197] ADDRCONF(NETDEV_CHANGE): eth2: > link becomes ready > Jul 11 03:13:10 ip61zen kernel: [ 562.763641] eth2: link up, 10Mbps, > half-duplex, lpa 0x0021 > Jul 11 03:13:12 ip61zen avahi-daemon[5068]: Registering new address record > for fe80::20e:c6ff:fe87:9b3c on eth2.*. > Jul 11 03:13:21 ip61zen kernel: [ 574.288501] eth2: no IPv6 routers present > > # ping 172.22.22.2 > PING 172.22.22.2 (172.22.22.2) 56(84) bytes of data. > From 172.22.22.62 icmp_seq=2 Destination Host Unreachable > From 172.22.22.62 icmp_seq=3 Destination Host Unreachable > From 172.22.22.62 icmp_seq=4 Destination Host Unreachable > > --- 172.22.22.2 ping statistics --- > 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms > , pipe 3 > > # route add default gw 172.22.22.2 > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 172.22.22.0 0.0.0.0 255.255.255.0 U 29 0 0 eth2 > 169.254.0.0 0.0.0.0 255.255.0.0 U 29 0 0 eth2 > 0.0.0.0 172.22.22.2 0.0.0.0 UG 0 0 0 eth2 > > # ping 172.22.22.2 > PING 172.22.22.2 (172.22.22.2) 56(84) bytes of data. > From 172.22.22.62 icmp_seq=1 Destination Host Unreachable > From 172.22.22.62 icmp_seq=2 Destination Host Unreachable > From 172.22.22.62 icmp_seq=3 Destination Host Unreachable > > --- 172.22.22.2 ping statistics --- > 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3004ms > , pipe 4 > > > BTW, the cat5 cable is connected in all cases to a hub (10MBit 4/5 port > DLink), it is a straight-through, not a cross-over cable. I've tried two > different cat5 patch leads with the above procedure. I've tried also the > hubs "uplink" (crossover) port. > > I've tried two brand new asix devices: > USB2.0 GIGABIT LAN DELPHI G > Gigabit USB 2.0 Ethernet Adapter > WS-UL220G > > Any testing avenues appreciated. > > TIA > Zenaan > > -- > Homepage: www.SoulSound.net -- Free Australia: www.UPMART.org > Please respect the confidentiality of this email as sensibly warranted. > > -- > ubuntu-users mailing list > ubuntu-users@xxxxxxxxxxxxxxxx > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users -- Homepage: www.SoulSound.net -- Free Australia: www.UPMART.org Please respect the confidentiality of this email as sensibly warranted. ------------------------------ -- ubuntu-users mailing list ubuntu-users@xxxxxxxxxxxxxxxx Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users End of ubuntu-users Digest, Vol 59, Issue 188 ********************************************* -- ubuntu-users mailing list ubuntu-users@xxxxxxxxxxxxxxxx Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
|
|
||||||||||||||||||||||||||
| News | Mail Home | sitemap | FAQ | advertise |