Re: (Trouble at booting) Re: problema al bootear
Paul Scott wrote: Antonio Rodriguez wrote: On Mon, Dec 12, 2005 at 06:02:37AM -0300, Gabriel wrote: Levi Sandoval wrote: /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 8 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 16 seconds for /sys/block/hda/dev to show up Device /sys/block/hda/dev seems to be down. Debuggin opportunity, type ^D to continue /bin/dash: can't access tty; job control turned off # Same problem here, with the difference that I don't have any windows running, is pure debian, one hard disk. After upgrading and immediate reboot, the kernel is unable to find some /dev/*something and suggests 'Control + D'. I found easier to just reboot with image 2.6.13.* and wait for another image to come. Hmm. I am surprised that not many have reported the same. Same fix here. I hope someone explains this. Paul Scott The explanation is a bug in yaird (see |Bug#343042). unfortunately i don't have a backup kernel so i started a new thread to get some help Andrei | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
(Trouble at booting) Re: problema al bootear
On Mon, Dec 12, 2005 at 06:02:37AM -0300, Gabriel wrote: Levi Sandoval wrote: /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 1 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 2 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 4 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 8 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 16 seconds for /sys/block/hda/dev to show up Device /sys/block/hda/dev seems to be down. Debuggin opportunity, type ^D to continue /bin/dash: can't access tty; job control turned off # Same problem here, with the difference that I don't have any windows running, is pure debian, one hard disk. After upgrading and immediate reboot, the kernel is unable to find some /dev/*something and suggests 'Control + D'. I found easier to just reboot with image 2.6.13.* and wait for another image to come. Hmm. I am surprised that not many have reported the same. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (Trouble at booting) Re: problema al bootear
Antonio Rodriguez wrote: On Mon, Dec 12, 2005 at 06:02:37AM -0300, Gabriel wrote: Levi Sandoval wrote: /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 1 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 2 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 4 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 8 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 16 seconds for /sys/block/hda/dev to show up Device /sys/block/hda/dev seems to be down. Debuggin opportunity, type ^D to continue /bin/dash: can't access tty; job control turned off # Same problem here, with the difference that I don't have any windows running, is pure debian, one hard disk. After upgrading and immediate reboot, the kernel is unable to find some /dev/*something and suggests 'Control + D'. I found easier to just reboot with image 2.6.13.* and wait for another image to come. Hmm. I am surprised that not many have reported the same. Same problem here. Just did most of the current sid updates. New kernel: 2.6.14-2-k7 Googling doesn't give any help. Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (Trouble at booting) Re: problema al bootear
On 12 Dec 2005, Paul Scott wrote: Antonio Rodriguez wrote: On Mon, Dec 12, 2005 at 06:02:37AM -0300, Gabriel wrote: Levi Sandoval wrote: /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 1 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 2 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 4 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 8 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 16 seconds for /sys/block/hda/dev to show up Device /sys/block/hda/dev seems to be down. Debuggin opportunity, type ^D to continue /bin/dash: can't access tty; job control turned off # Same problem here, with the difference that I don't have any windows running, is pure debian, one hard disk. After upgrading and immediate reboot, the kernel is unable to find some /dev/*something and suggests 'Control + D'. I found easier to just reboot with image 2.6.13.* and wait for another image to come. Hmm. I am surprised that not many have reported the same. Same problem here. Just did most of the current sid updates. New kernel: 2.6.14-2-k7 Googling doesn't give any help. Paul Scott Apologies for a me-too, but I've just had the same experience, both here on my desktop and also on my laptop (Thinkpad R50e). I thought it might have been something to do with needing udev, which I don't use. Rashly, I installed it on my laptop and the consequence was that it removed hotplug and now I shall have to reinstall everything in order to get my wireless connection to work (don't ask why, long story). A bad day at the races. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Fwd: Re: (Trouble at booting) Re: problema al bootear]
Oops!, I didn't send this to the list. Paul Anthony Campbell wrote: On 12 Dec 2005, Paul Scott wrote: Antonio Rodriguez wrote: On Mon, Dec 12, 2005 at 06:02:37AM -0300, Gabriel wrote: Levi Sandoval wrote: Waiting: 8 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 16 seconds for /sys/block/hda/dev to show up Device /sys/block/hda/dev seems to be down. Debuggin opportunity, type ^D to continue /bin/dash: can't access tty; job control turned off # Same problem here, with the difference that I don't have any windows running, is pure debian, one hard disk. After upgrading and immediate reboot, the kernel is unable to find some /dev/*something and suggests 'Control + D'. I found easier to just reboot with image 2.6.13.* and wait for another image to come. Hmm. I am surprised that not many have reported the same. Same problem here. Just did most of the current sid updates. New kernel: 2.6.14-2-k7 Googling doesn't give any help. Paul Scott Apologies for a me-too, but I've just had the same experience, both here on my desktop and also on my laptop (Thinkpad R50e). I will try going back to the previous kernel to eliminate that variable. I thought it might have been something to do with needing udev, which I don't use. Rashly, I installed it on my laptop and the consequence was that it removed hotplug and now I shall have to reinstall everything in order to get my wireless connection to work (don't ask why, long story). I will start a new thread on that. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (Trouble at booting) Re: problema al bootear
Antonio Rodriguez wrote: On Mon, Dec 12, 2005 at 06:02:37AM -0300, Gabriel wrote: Levi Sandoval wrote: /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 8 seconds for /sys/block/hda/dev to show up /bin/cat: /sys/block/hda/dev: No such file or directory Waiting: 16 seconds for /sys/block/hda/dev to show up Device /sys/block/hda/dev seems to be down. Debuggin opportunity, type ^D to continue /bin/dash: can't access tty; job control turned off # Same problem here, with the difference that I don't have any windows running, is pure debian, one hard disk. After upgrading and immediate reboot, the kernel is unable to find some /dev/*something and suggests 'Control + D'. I found easier to just reboot with image 2.6.13.* and wait for another image to come. Hmm. I am surprised that not many have reported the same. Same fix here. I hope someone explains this. Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
