[SOLVED] Can't log into squeeze after updating yesterday

helai · 07-10-2009, 07:15 PM

system: debian squeeze

Yesterday,after I have run dist-upgrade then reboot my computer ,it stop at the logging while the screen has the sentences just like

Code:

*****
intel8x0_measure_ac97_clock measured 52292 usecs
intel8x0 clocking to 48000
done

but no errors showed on screen
who can help me tell me how to figure it out

after I click ctrl-c it still can go through,and the next sentence is "setting the system clock", then it log into the system,but next time it still stop at this step
here is my sys log

Code:

Jul 11 07:06:34 localhost kernel: [   11.974191] ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 17
Jul 11 07:06:34 localhost kernel: [   12.130806] input: ImPS/2 Generic Wheel Mouse as /class/input/input4
Jul 11 07:06:34 localhost kernel: [   12.198700] parport_pc 00:0a: reported by Plug and Play ACPI
Jul 11 07:06:34 localhost kernel: [   12.198700] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
Jul 11 07:06:34 localhost kernel: [   12.471514] intel8x0_measure_ac97_clock: measured 51353 usecs
Jul 11 07:06:34 localhost kernel: [   12.471584] intel8x0: clocking to 48000
Jul 11 07:06:34 localhost kernel: [   21.188294] Adding 1951856k swap on /dev/sda5.  Priority:-1 extents:1 across:1951856k
Jul 11 07:06:34 localhost kernel: [   21.657618] EXT3 FS on sda7, internal journal
Jul 11 07:06:34 localhost kernel: [   21.921078] loop: module loaded
Jul 11 07:06:34 localhost kernel: [   21.997805] w83627hf: Found W83627THF chip at 0x290
Jul 11 07:06:34 localhost kernel: [   21.997805] w83627hf w83627hf.656: Reading VID from GPIO5
Jul 11 07:06:34 localhost kernel: [   22.053802] p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
Jul 11 07:06:34 localhost kernel: [   23.199554] fuse init (API version 7.9)

mark_alfred · 07-12-2009, 11:07 AM

Try logging into the single user maintenance account (an option to do this should be given at the initial grub screen, just before the computer attempts to boot into the system). From here, you'll be able to sign in as root user*, and, hopefully, also be able to fix things. Here, you might be able to try running the command "apt-get -f install" ("-f" being for "fix broken"). Another command that may help is "fsck". Sometimes this can fix things. Also, if you're connected to the internet, try running "apt-get update" followed by "apt-get safe-upgrade" followed by "apt-get full-upgrade" (or, if you've been using aptitude, then stick with that via "aptitude update", etc).

If you're not connected to the internet, sometimes you can connect with the command "pppoeconf", or, if using dial-up, "pon" (disconnecting is "poff -a").

See http://www.linux.com/archive/feature/48910 for more information on what to try when apt-get fails.

_________
*assuming that the root user is activated on your system -- uh, if it's not, as is the case in an Ubuntu-like set up, then I'm not really sure. Maybe the maintenance mode can be accessed by a regular user, if sudo is set up for this.

later edit: I just noticed that you indeed can log into your system. I initially thought you weren't able to. So, there's likely no need to worry about using the single user maintenance mode. Anyway, after logging in, feel free to try some of the recommendations I gave above (except "fsck", this won't be possible after a regular log in).

vharishankar · 07-12-2009, 11:11 AM

I recently had a problem where boot was hanging at a particular point but continued after nearly 100 seconds. I was totally frustrated by it but I discovered that udev was the culprit thanks to some very useful advice on this forum by farslayer.

Did you check your udev rules and see if there are any conflicts there?

Check all the files in
/etc/udev/rules.d/

And see if any device is mentioned twice.

helai · 07-13-2009, 08:21 AM

To mark_alfred:
My problem is not the failure of the "apt-get" it just that after I "dist-upgrade" my squeeze OS ,then the os stop log into the OS while it stoped after the sentence"intel8x0 clocking to 48000 done" in the screen

To harishankar:
here is my file under folder,I didn't find the duplicated files

Code:

lenovo@debian:/etc/udev/rules.d$ ls
025_libgphoto2.rules     z60_hplip.rules
025_logitechmouse.rules  z60_kpartx.rules
56-hpmud_support.rules   z60_libpisock9.rules
65_dmsetup.rules         z60_libsane-extras.rules
70-persistent-cd.rules   z60_libsane.rules
70-persistent-net.rules  z60_xen-backend.rules
85_dmraid.rules          z60_xserver-xorg-input-wacom.rules

Thanks all
Helai

helai · 07-14-2009, 07:31 AM

still need help!

when booting which command control the "setting the system clock"
helai

mark_alfred · 07-14-2009, 11:30 PM

I don't have a clue. But, from my /var/log/syslog, I get the following:

Quote:

Jul 14 16:26:53 debian kernel: [ 3.736637] rtc_cmos 00:0c: setting system clock to 2009-07-14 20:26:19 UTC (1247603179)

So, I did a search of package descriptions for the term "cmos", and came up with libsmbios2, which is installed on my system.

Disclaimer: the above is most definitely just a shot in the dark.

helai · 07-15-2009, 06:25 PM

the problem still there,but anyway thanks

helai · 07-16-2009, 07:52 AM

solved:

after I put the option "quiet" attached the sentence of " kernel /vmlinuz-2.6.26-2-686 root=/dev/sda7 ro quiet" in the file /boot/grub/menu.lst,then when booting the OS hangs when screen shows message" waiting for /dev to be fully populated...done"
after google the INTERNET, I find it was caused by the sentence "CONCURRENCY=shell" which I put it in the file /etc/default/rcS long before by following which optimization instruction.

so remove it and go through anyway.