Activity log for bug #127927

Date Who What changed Old value New value Message
2007-07-24 12:02:05 errenay bug added bug
2007-07-25 07:25:31 errenay description System: Acer Aspire 5920G (Centrino 2 Duo 7300, 2 GB RAM, chipset Intel 965G, GeForce 8600 M GT with 256 MB, 160 GB SATA), system on HDD: Vista Premium 32 bit, trying to install: Kubuntu 7.10 (Gutsy, Tribe 3) LiveCD 64 bit. Without kernel options quiet splash -- and in safe graphics mode I could see the messages. First BusyBox... /bin/sh: can't access tty; job terminated was without any previous warning. I have used code modprobe ata_piix exit It has helped a little. However, there was another error: cp unable to open '/root/var/log' no such file or directory Begin: Running /scripts/init-boyyom mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init And that's all... I have tried modprobe piix modprobe ide_generic but it doesn't help. I'm too green to know what I should do next. But I hope it helps somebody to understand this problem. Thank you in advance for your help. I have the same problem with Kubuntu 7.04 LiveCD, please see: http://ubuntuforums.org/showthread.php?t=415009&highlight=can%27t+access+tty&page=26 System: Acer Aspire 5920G (Centrino 2 Duo 7300, 2 GB RAM, chipset Intel 965G, GeForce 8600 M GT with 256 MB, 160 GB SATA), system on HDD: Vista Premium 32 bit, trying to install: Kubuntu 7.10 (Gutsy, Tribe 3) LiveCD 64 bit. Problem: LiveCD couldn't even start desktop system. Without kernel options quiet splash -- and in safe graphics mode I could see the messages. First BusyBox... /bin/sh: can't access tty; job terminated was without any previous warning. I have used code modprobe ata_piix exit It has helped a little. However, there was another error: cp unable to open '/root/var/log' no such file or directory Begin: Running /scripts/init-boyyom mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init And that's all... I have tried modprobe piix modprobe ide_generic but it doesn't help. I'm too green to know what I should do next. But I hope it helps somebody to understand this problem. Thank you in advance for your help. I have the same problem with Kubuntu 7.04 LiveCD, please see: http://ubuntuforums.org/showthread.php?t=415009&highlight=can%27t+access+tty&page=26
2007-07-25 07:25:31 errenay title [Gutsy Kubuntu 7.10 LiveCD} /bin/sh: can't access tty; job control turned off [Gutsy Tribe 3 Kubuntu 7.10 LiveCD] /bin/sh: can't access tty; job control turned off
2007-07-25 07:26:20 errenay description System: Acer Aspire 5920G (Centrino 2 Duo 7300, 2 GB RAM, chipset Intel 965G, GeForce 8600 M GT with 256 MB, 160 GB SATA), system on HDD: Vista Premium 32 bit, trying to install: Kubuntu 7.10 (Gutsy, Tribe 3) LiveCD 64 bit. Problem: LiveCD couldn't even start desktop system. Without kernel options quiet splash -- and in safe graphics mode I could see the messages. First BusyBox... /bin/sh: can't access tty; job terminated was without any previous warning. I have used code modprobe ata_piix exit It has helped a little. However, there was another error: cp unable to open '/root/var/log' no such file or directory Begin: Running /scripts/init-boyyom mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init And that's all... I have tried modprobe piix modprobe ide_generic but it doesn't help. I'm too green to know what I should do next. But I hope it helps somebody to understand this problem. Thank you in advance for your help. I have the same problem with Kubuntu 7.04 LiveCD, please see: http://ubuntuforums.org/showthread.php?t=415009&highlight=can%27t+access+tty&page=26 System: Acer Aspire 5920G (Centrino 2 Duo 7300, 2 GB RAM, chipset Intel 965G, GeForce 8600 M GT with 256 MB, 160 GB SATA), system on HDD: Vista Premium 32 bit, trying to install: Kubuntu 7.10 (Gutsy, Tribe 3) LiveCD 64 bit. Problem: LiveCD couldn't even start desktop system. Without kernel options quiet splash -- and in safe graphics mode I could see the messages. First BusyBox... /bin/sh: can't access tty; job control turned off was without any previous warning. I have used code modprobe ata_piix exit It has helped a little. However, there was another error: cp unable to open '/root/var/log' no such file or directory Begin: Running /scripts/init-boyyom mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init And that's all... I have tried modprobe piix modprobe ide_generic but it doesn't help. I'm too green to know what I should do next. But I hope it helps somebody to understand this problem. Thank you in advance for your help. I have the same problem with Kubuntu 7.04 LiveCD, please see: http://ubuntuforums.org/showthread.php?t=415009&highlight=can%27t+access+tty&page=26
2007-08-01 06:04:59 Paul Dufresne None: statusexplanation
2007-08-01 06:11:55 Paul Dufresne casper: status New Incomplete
2007-08-01 06:11:55 Paul Dufresne casper: assignee dufresnep
2007-08-01 06:11:55 Paul Dufresne casper: statusexplanation Hi! Thank you for taking time to report this bug and help us make Ubuntu become better. It took me a while to realize that you were able to type commands after the message "can't access tty, job control turned off". It is important to understand that this message come for many many different errors. I have actually open a new bug about this message: bug #129612. Rather than typing 'modprobe ata_piix; exit' I would suggest you type: cat /var/log/casper.log and looks for error message. (Actually, the real error message have probably be shown on screen, just a bit before the "can't access tty, job control turned off") This is the real problem that need to be fixed and caused busybox (just a shell to type commands) to be called because the system was not able to continue loading normally.
2007-08-04 16:25:10 Paul Dufresne title [Gutsy Tribe 3 Kubuntu 7.10 LiveCD] /bin/sh: can't access tty; job control turned off [Gutsy Tribe 3 Kubuntu 7.10 LiveCD 64b] need all_generic_ide kernel option for system to boot
2007-08-09 07:45:20 errenay bug added attachment 'uname.log' (uname.log)
2007-08-09 07:45:51 errenay bug added attachment 'dmesg.log' (dmesg.log)
2007-08-09 07:46:35 errenay bug added attachment 'lspci-vvnn.log' (lspci-vvnn.log)
2007-08-09 22:57:42 Paul Dufresne casper: status Incomplete Confirmed
2007-08-09 22:57:42 Paul Dufresne casper: assignee dufresnep ubuntu-kernel-team
2007-08-09 22:57:42 Paul Dufresne casper: statusexplanation Hi! Thank you for taking time to report this bug and help us make Ubuntu become better. It took me a while to realize that you were able to type commands after the message "can't access tty, job control turned off". It is important to understand that this message come for many many different errors. I have actually open a new bug about this message: bug #129612. Rather than typing 'modprobe ata_piix; exit' I would suggest you type: cat /var/log/casper.log and looks for error message. (Actually, the real error message have probably be shown on screen, just a bit before the "can't access tty, job control turned off") This is the real problem that need to be fixed and caused busybox (just a shell to type commands) to be called because the system was not able to continue loading normally. Thanks for all these information. Moving bug from Casper to linux-source-2.6.22 (kernel). That is sad that we don't have a clear error message before busybox command prompt show up. I have personally observed that the system seems FOR ME, to write the 'uncompressing linux kernel' on text mode while graphical mode is set, so that some unreadable lines show up on the top (I recognize the dots and vmlinuz word because I have seen that on other/older distributions even if almost completely unreadable). So I believe first kernel messages are lost while in graphical mode, just before it switch to text mode. Confirming bug, letting a kernel developer to take a look and decide which move need to be made next.
2007-08-17 00:27:36 Brian Murray linux-source-2.6.22: status Confirmed Triaged
2007-08-17 00:27:36 Brian Murray linux-source-2.6.22: assignee ubuntu-kernel-team brian-murray
2007-08-17 00:27:36 Brian Murray linux-source-2.6.22: statusexplanation Thanks for all these information. Moving bug from Casper to linux-source-2.6.22 (kernel). That is sad that we don't have a clear error message before busybox command prompt show up. I have personally observed that the system seems FOR ME, to write the 'uncompressing linux kernel' on text mode while graphical mode is set, so that some unreadable lines show up on the top (I recognize the dots and vmlinuz word because I have seen that on other/older distributions even if almost completely unreadable). So I believe first kernel messages are lost while in graphical mode, just before it switch to text mode. Confirming bug, letting a kernel developer to take a look and decide which move need to be made next. Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 127163 and is being marked as such. Feel free to submit any future bugs you may find.
2007-08-17 00:27:47 Brian Murray marked as duplicate 127163
2007-08-17 00:29:31 Brian Murray linux-source-2.6.22: assignee brian-murray
2007-08-17 00:29:31 Brian Murray linux-source-2.6.22: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 127163 and is being marked as such. Feel free to submit any future bugs you may find.