I have an ASUS netbook (EEEPC 1005P) which is running openSuSE 12.1 (I tried 12.2 but it was far too slow). The spec is an intel Atom CPU, 1 GB RAM, 250 GB hard drive and a very basic BIOS.
After using it for nearly two years it suddenly stopped booting altogether. The boot sequence would stop after the hard drive partitions were mounted and declared clean, and the machine would hang indefinitely in this state.
By chance I tried to boot it once with an ethernet cable plugged in, which was connected to an active hub. The machine booted without difficulty, although no further messages were displayed on the screen after the mounting of the hard disk partitions (normally I get quite a long list of messages on the screen before the booting process is complete).
This is repeatable: the machine never boots unless the cable is plugged in. When it is hanging I can plug the cable in whenever I want and it then proceeds to complete the boot. I tried to get ASUS to explain this, but they refuse to discuss a machine not running the original windows with which it was factory installed. I tried to look into the BIOS, thinking that there might be a “boot on LAN only” option that was accidentally triggered, but the BIOS is so basic that I have no control over anything of importance and anyway I could see no boot on LAN option. I have not been able to find an updated BIOS, either.
Has anyone come across something like this? Is there anything I can do to avoid having to plug a live ethernet cable into the machine every time I want to boot it?
I as well observe this kind of problem from time to time.
I have a desktop (core i5-2500) running under openSUSE 12.1 64bit.
Some times I unplugged the ethernet cable connecting the PC to the ADSL modem,
and this kind of hanging occurred.
Sometimes not.
In the end I think that LibreOffice is most suspicious:
The hanging at startup in a repeatable way occurred, when I had any LibreOffice running with a text document
at the preceding shutdown.
What helps for me on such a hanging:
Ctrl-Alt-F1, to get to a root console. Enter root password. Then say “shutdown -h now”.
The next boot usually works.
>
>I have an ASUS netbook (EEEPC 1005P) which is running openSuSE 12.1 (I
>tried 12.2 but it was far too slow). The spec is an intel Atom CPU, 1 GB
>RAM, 250 GB hard drive and a very basic BIOS.
>
>After using it for nearly two years it suddenly stopped booting
>altogether. The boot sequence would stop after the hard drive partitions
>were mounted and declared clean, and the machine would hang indefinitely
>in this state.
>
>By chance I tried to boot it once with an ethernet cable plugged in,
>which was connected to an active hub. The machine booted without
>difficulty, although no further messages were displayed on the screen
>after the mounting of the hard disk partitions (normally I get quite a
>long list of messages on the screen before the booting process is
>complete).
>
>This is repeatable: the machine never boots unless the cable is plugged
>in. When it is hanging I can plug the cable in whenever I want and it
>then proceeds to complete the boot. I tried to get ASUS to explain this,
>but they refuse to discuss a machine not running the original windows
>with which it was factory installed. I tried to look into the BIOS,
>thinking that there might be a “boot on LAN only” option that was
>accidentally triggered, but the BIOS is so basic that I have no control
>over anything of importance and anyway I could see no boot on LAN
>option. I have not been able to find an updated BIOS, either.
>
>Has anyone come across something like this? Is there anything I can do
>to avoid having to plug a live ethernet cable into the machine every
>time I want to boot it?
>
>Thanks,
>
>Abe
Well my first suggestion is to look at /var/bootlog, after a boot stall
then plugged in the Ethernet cable. A lot to read through but likely to
point to the issue.
On 2013-01-02 00:56, ratzi wrote:
> In the end I think that LibreOffice is most suspicious:
> The hanging at startup in a repeatable way occurred, when I had any
> LibreOffice running with a text document
> at the preceding shutdown.
But by the time libreoffice has a chance to look, the system is already
booted. I don’t understand. Unless you consider login to the desktop
(automatic or manual) as part of the boot.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
If I wait for half an hour (my core i5-2500 is quite fast though …)
then the background picture of the desktop shows up,
but no App (like Okular, Dolphin, Firefox, and libreOffice) loads.
That’s the time that I press Ctrl-Alt-F1, login as root, and ‘shutdown -h now’.
Which kills the KDE session, so that it will still try to restore the erronious session (I’m convinced it’s something like described above) . I suggest you create a new user, login as that user and see if that user suffers from the phenomenon.
On 2013-01-06 22:56, ratzi wrote:
>
> robin_listas;2516083 Wrote:
>> On 2013-01-02 00:56, ratzi wrote:
>>> In the end I think that LibreOffice is most suspicious:
>>> The hanging at startup in a repeatable way occurred, when I had any
>>> LibreOffice running with a text document
>>> at the preceding shutdown.
>>
>> But by the time libreoffice has a chance to look, the system is already
>> booted. I don’t understand. Unless you consider login to the desktop
>> (automatic or manual) as part of the boot.
>
> Hm, it should have been booted, in principle yes.
>
> But it hangs while it shows the KDE icon.
At that point, the machine is completely booted. That point in the
sequence is the session initialization sequence, not the boot sequence.
> If I wait for half an hour (my core i5-2500 is quite fast though …)
> then the background picture of the desktop shows up,
> but no App (like Okular, Dolphin, Firefox, and libreOffice) loads.
So, the KDE initialization hangs, not boot.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
I was a bit reluctant to follow your advice, and rather took the stance to observe the behaviour of the installed openSUSE 12.1 a bit,
because all members of my family would cry out, if I would change the behaviour/permissions/name of the standard (non-root !!) user,
logged in by default after boot without requiring a password (because our PC isn’t accessible by the public).
At least the last 12 times of booting, the hanging during startup didn’t occur.
But I observed that until then - at shutdown - I repeatedly (at least 3 times) got crash reports for the (KDE) plasma desktop
It is not needed to change all to a new user he is only for testing.
If the new user works ok then the problem is in the KDE config files somewhere.
In that case log into the system as root in a terminal and in the preferred user’s home directory rename the ~/.kde4 directory then restart and log back in as the preferred user. That will cause the ~/.kde4 directory to be recreated with default settings. You would then need to arrange the desktop as you like again.
I have the same issue with 12.2 and ACER Laptop: my SuSE 12.2 boots only when connetect to the LAN.
If I boot with disconnected ethernet cable, the boot freezes as soon as the green splashscreen is displayed.
Trying to use ctrl-alt-F1 to open a root shell does not work, the PC is completely freezed.
I already tryed to change LAN start from boot time / hotplug to manually, but it does not resolve.
This evening I will now try to shutdown -h now and reboot, and check the bootlog.
On Thu 10 Jan 2013 03:06:01 PM CST, paolosena wrote:
Hi,
I have the same issue with 12.2 and ACER Laptop: my SuSE 12.2 boots
only when connetect to the LAN.
If I boot with disconnected ethernet cable, the boot freezes as soon as
the green splashscreen is displayed.
Trying to use ctrl-alt-F1 to open a root shell does not work, the PC is
completely freezed.
I already tryed to change LAN start from boot time / hotplug to
manually, but it does not resolve.
This evening I will now try to shutdown -h now and reboot, and check
the bootlog.
Anyone else with this issue?
Best Regards,
Paolo
Hi
After the system boots with the cable installed, install and run the
commands;
zypper in systemd-analyze
systemd-analyze blame
Then post the output.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 2:04, 3 users, load average: 0.13, 0.14, 0.14
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
I was a bit reluctant to follow your advice, and rather took the stance to observe the behaviour of the installed openSUSE 12.1 a bit,
because all members of my family would cry out, if I would change the behaviour/permissions/name of the standard (non-root !!) user,
logged in by default after boot without requiring a password (because our PC isn’t accessible by the public).
At least the last 12 times of booting, the hanging during startup didn’t occur.[/QUOTE]
These were good hints.
Thank you both very much!
Mike
On my system zypper cannot find a provider of systemd-analyze.
Regarding other questions asked and suggestions made on this thread:
#2: yes, the hold up is after grub, and yes I did press esc - which is how I know that the boot process gets stuck after mounting the hard drives and declaring them clean.
#3: there was no LibreOffice running, but I did verify this, shut down and restarted. Unfortunately this did not sort it out.
#5: I have just booted the machine and waited deliberately a few minutes before plugging in the ethernet cable. As expected, the system only finished booting after the cable was plugged in. Here is a part of my /var/log/messages surrounding the time when I plugged in the cable. Please note the two areas very near the end that I enclosed with asterisks.
I hope this make sense to someone - I can’t understand from it what the problem is.
Abe
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Found user 'avahi' (UID 104) and group 'avahi' (GID 105).
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Successfully dropped root privileges.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: avahi-daemon 0.6.30 starting up.
Jan 10 22:37:43 eeelinux /usr/sbin/cron[840]: (CRON) INFO (running with inotify support)
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Loading service file /etc/avahi/services/sftp-ssh.service.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Loading service file /etc/avahi/services/ssh.service.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Loading service file /etc/avahi/services/udisks.service.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Network interface enumeration completed.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Registering HINFO record with values 'I686'/'LINUX'.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Server startup complete. Host name is eeelinux.local. Local service cookie is 1932251952.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Service "eeelinux" (/etc/avahi/services/udisks.service) successfully established.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Service "eeelinux" (/etc/avahi/services/ssh.service) successfully established.
Jan 10 22:37:43 eeelinux avahi-daemon[841]: Service "eeelinux" (/etc/avahi/services/sftp-ssh.service) successfully established.
Jan 10 22:37:43 eeelinux systemd-logind[748]: New seat seat0.
Jan 10 22:37:43 eeelinux dbus[847]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jan 10 22:37:43 eeelinux dbus-daemon[847]: dbus[847]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jan 10 22:37:43 eeelinux polkitd[851]: started daemon version 0.102 using authority implementation `local' version `0.102'
Jan 10 22:37:43 eeelinux dbus[847]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 10 22:37:43 eeelinux dbus-daemon[847]: dbus[847]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 10 22:37:43 eeelinux dbus-daemon[847]: dbus[847]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Jan 10 22:37:43 eeelinux dbus[847]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> ModemManager (version 0.5) starting...
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> ModemManager (version 0.5) starting...
Jan 10 22:37:43 eeelinux dbus-daemon[847]: dbus[847]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Jan 10 22:37:43 eeelinux dbus[847]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin SimTech
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin SimTech
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Option
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Option
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Linktop
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Linktop
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Generic
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Generic
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Novatel
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Novatel
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin X22X
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin X22X
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Sierra
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Sierra
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Option High-Speed
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Option High-Speed
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Ericsson MBM
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Ericsson MBM
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin AnyData
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin AnyData
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin MotoC
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin MotoC
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Wavecom
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Wavecom
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Samsung
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Samsung
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Nokia
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Nokia
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin ZTE
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin ZTE
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Gobi
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Gobi
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Huawei
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Huawei
Jan 10 22:37:43 eeelinux kernel: 17.751197] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 10 22:37:43 eeelinux modem-manager[855]: <info> Loaded plugin Longcheer
Jan 10 22:37:43 eeelinux dbus-daemon[847]: modem-manager[855]: <info> Loaded plugin Longcheer
Jan 10 22:37:43 eeelinux dbus[847]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Jan 10 22:37:43 eeelinux dbus-daemon[847]: dbus[847]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Jan 10 22:37:43 eeelinux kernel: 17.792375] atl1c 0000:01:00.0: irq 46 for MSI/MSI-X
Jan 10 22:37:43 eeelinux dbus-daemon[847]: dbus[847]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jan 10 22:37:43 eeelinux dbus[847]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
***********************
Jan 10 22:37:43 eeelinux kernel: 17.853137] ADDRCONF(NETDEV_UP): eth0: link is not ready
***********************
an 10 22:37:43 eeelinux kernel: 17.863034] NET: Registered protocol family 17
Jan 10 22:38:31 eeelinux kernel: 65.624177] usb 3-1: USB disconnect, device number 2
Jan 10 22:38:33 eeelinux kernel: 67.104132] usb 3-1: new low speed USB device number 3 using uhci_hcd
Jan 10 22:38:33 eeelinux kernel: 67.278918] usb 3-1: New USB device found, idVendor=093a, idProduct=2510
Jan 10 22:38:33 eeelinux kernel: 67.278932] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 10 22:38:33 eeelinux kernel: 67.278942] usb 3-1: Product: USB OPTICAL MOUSE
Jan 10 22:38:33 eeelinux kernel: 67.278950] usb 3-1: Manufacturer: PIXART
Jan 10 22:38:33 eeelinux mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1"
Jan 10 22:38:33 eeelinux kernel: 67.307609] input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input14
Jan 10 22:38:33 eeelinux kernel: 67.308493] generic-usb 0003:093A:2510.0002: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.1-1/input0
Jan 10 22:38:33 eeelinux mtp-probe: bus: 3, device: 3 was not an MTP device
Jan 10 22:39:33 eeelinux kernel: 127.376190] usb 3-1: USB disconnect, device number 3
Jan 10 22:39:35 eeelinux kernel: 129.104125] usb 3-1: new low speed USB device number 4 using uhci_hcd
Jan 10 22:39:35 eeelinux kernel: 129.278728] usb 3-1: New USB device found, idVendor=093a, idProduct=2510
Jan 10 22:39:35 eeelinux kernel: 129.278742] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 10 22:39:35 eeelinux kernel: 129.278752] usb 3-1: Product: USB OPTICAL MOUSE
Jan 10 22:39:35 eeelinux kernel: 129.278760] usb 3-1: Manufacturer: PIXART
Jan 10 22:39:35 eeelinux mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1"
Jan 10 22:39:35 eeelinux kernel: 129.306762] input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input15
Jan 10 22:39:35 eeelinux kernel: 129.307313] generic-usb 0003:093A:2510.0003: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.1-1/input0
Jan 10 22:39:35 eeelinux mtp-probe: bus: 3, device: 4 was not an MTP device
Jan 10 22:40:35 eeelinux kernel: 189.376204] usb 3-1: USB disconnect, device number 4
Jan 10 22:40:37 eeelinux kernel: 191.104129] usb 3-1: new low speed USB device number 5 using uhci_hcd
Jan 10 22:40:37 eeelinux kernel: 191.278538] usb 3-1: New USB device found, idVendor=093a, idProduct=2510
Jan 10 22:40:37 eeelinux kernel: 191.278552] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 10 22:40:37 eeelinux kernel: 191.278562] usb 3-1: Product: USB OPTICAL MOUSE
Jan 10 22:40:37 eeelinux kernel: 191.278570] usb 3-1: Manufacturer: PIXART
Jan 10 22:40:37 eeelinux mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1"
Jan 10 22:40:37 eeelinux kernel: 191.306574] input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input16
Jan 10 22:40:37 eeelinux kernel: 191.307122] generic-usb 0003:093A:2510.0004: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.1-1/input0
Jan 10 22:40:37 eeelinux mtp-probe: bus: 3, device: 5 was not an MTP device
***********************
Jan 10 22:41:21 eeelinux kernel: 235.156612] atl1c 0000:01:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
***********************
Jan 10 22:41:21 eeelinux kernel: 235.157198] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan 10 22:41:21 eeelinux dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jan 10 22:41:21 eeelinux dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jan 10 22:41:21 eeelinux dhclient: All rights reserved.
Jan 10 22:41:21 eeelinux dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jan 10 22:41:21 eeelinux dhclient:
Jan 10 22:41:21 eeelinux dhclient: Listening on LPF/eth0/20:cf:30:4d:0e:c3
Jan 10 22:41:21 eeelinux dhclient: Sending on LPF/eth0/20:cf:30:4d:0e:c3
Jan 10 22:41:21 eeelinux dhclient: Sending on Socket/fallback
Jan 10 22:41:21 eeelinux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Jan 10 22:41:21 eeelinux dhclient: DHCPOFFER from 192.168.1.1
Jan 10 22:41:22 eeelinux avahi-daemon[841]: Registering new address record for fe80::22cf:30ff:fe4d:ec3 on eth0.*.
Jan 10 22:41:26 eeelinux dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 10 22:41:26 eeelinux dhclient: DHCPACK from 192.168.1.1
Jan 10 22:41:26 eeelinux dhclient: bound to 192.168.1.102 -- renewal in 40731 seconds.
On 2013-01-11 00:46, naimab wrote:
> #5: I have just booted the machine and waited deliberately a few
> minutes before plugging in the ethernet cable. As expected, the system
> only finished booting after the cable was plugged in. Here is a part of
> my /var/log/messages surrounding the time when I plugged in the cable.
> Please note the two areas very near the end that I enclosed with
> asterisks.
>
> I hope this make sense to someone - I can’t understand from it what the
> problem is.
Me neither… except that it is waiting for the network to connect.
> Code:
> --------------------
>
> Jan 10 22:37:43 eeelinux avahi-daemon[841]: Found user ‘avahi’ (UID 104) and group ‘avahi’ (GID 105).
…
> Jan 10 22:37:43 eeelinux dbus[847]: [system] Successfully activated service ‘fi.w1.wpa_supplicant1’
>
> ***********************
> Jan 10 22:37:43 eeelinux kernel: 17.853137] ADDRCONF(NETDEV_UP): eth0: link is not ready
> ***********************
>
> an 10 22:37:43 eeelinux kernel: 17.863034] NET: Registered protocol family 17
Here is a 1 minute holdup.
> Jan 10 22:38:31 eeelinux kernel: 65.624177] usb 3-1: USB disconnect, device number 2
> Jan 10 22:38:33 eeelinux kernel: 67.104132] usb 3-1: new low speed USB device number 3 using uhci_hcd
…
2 minutes!
> Jan 10 22:40:37 eeelinux mtp-probe: bus: 3, device: 5 was not an MTP device
>
> ***********************
> Jan 10 22:41:21 eeelinux kernel: 235.156612] atl1c 0000:01:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
> ***********************
>
> Jan 10 22:41:21 eeelinux kernel: 235.157198] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
and now it continues.
> Jan 10 22:41:21 eeelinux dhclient: Internet Systems Consortium DHCP Client 4.2.2
> --------------------
Weird indeed. Something in the network configuration, perhaps the eth0
device is defined as “mandatory”.
Could be that?
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
On 01/11/2013 06:16 PM, naimab wrote:
>
> Excuse my ignorance - how do I check whether eth0 is mandatory and how
> do I change it if it is?
To my knowledge, the only way that eth0 might be mandatory is if you are forcing
the mount of some network file system such as NFS or SMB. Check /etc/fstab for
such settings. If you have them, ass the “nofail” option.
