"tty" missing from busybox in feisty BETA

Bug #99843 reported by BullCreek
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: busybox-initramfs

I have an averatec c3500 tablet pc I've been testing feisty on. The previous herd builds worked fine, but when I go to install the BETA, booting the CD-ROM, I get the following error during initramfs initialization:

BusyBox:

/bin/sh: can't access tty; job control turned off

I'm assuming maybe the version of BusyBox got upgraded, and /bin/tty or /usr/bin/tty didn't get included in the list of static binaries. I hope someone can fix this before release - as I plan on using the old tablet as a CarPC and feisty herd 5 was running really well on it!

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Could you please retest with a daily build from http://cdimage.ubuntu.com/ ? There have been some fixes after BETA and I would like to know if you still have this problem. Thanks in advance!

Changed in busybox:
assignee: nobody → thotz
Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

The error message "/bin/sh: can't access tty; job control turned off" isn't a bug in itself (FYI it is printed because Busybox can't obtain a controlling terminal because it is running on /dev/console).

The reason why you've got this message is because something in the kernel boot has failed. Normally when this happens (without the splash screen), a kernel error will be printed just before the BusyBox: line.

Can you boot the Beta CD in 'recovery mode' and see if any error messages are printed? If they're printed, can you write them down and attach to this bug report, or if possible take a digital photo of the screen, and attach that. Thanks,

Changed in linux-source-2.6.20:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
BullCreek (jeff-openenergy) wrote : Re: [Bug 99843] Re: "tty" missing from busybox in feisty BETA

Well after I got home this afternoon, I started downloading a daily build to test,
but I also accidentally happened to boot the laptop in question with the BETA disc
still in, and it worked this time. I thought - what's different??? Turns out I had moved
the laptop and unplugged the ethernet cable. Without the ethernet cable plugged
in, it boots the BETA CD fine. With it plugged in, I get the error previously mentioned.
I've tried it six times with and without, and it seems to be consistent. The NIC
chip in the laptop I believe is the SIS900 if that helps.

when the daily build finishes downloading, I will try it and report back findings.

----- Original Message -----
From: "Phillip Lougher" <email address hidden>
To: <email address hidden>
Sent: Monday, April 2, 2007 8:37:40 AM (GMT-0600) US/Central
Subject: [Bug 99843] Re: "tty" missing from busybox in feisty BETA

The error message "/bin/sh: can't access tty; job control turned off"
isn't a bug in itself (FYI it is printed because Busybox can't obtain a
controlling terminal because it is running on /dev/console).

The reason why you've got this message is because something in the
kernel boot has failed. Normally when this happens (without the splash
screen), a kernel error will be printed just before the BusyBox: line.

Can you boot the Beta CD in 'recovery mode' and see if any error
messages are printed? If they're printed, can you write them down and
attach to this bug report, or if possible take a digital photo of the
screen, and attach that. Thanks,

** Changed in: linux-source-2.6.20 (Ubuntu)
   Importance: Undecided => Medium
       Status: Unconfirmed => Needs Info

--
"tty" missing from busybox in feisty BETA
https://bugs.launchpad.net/bugs/99843
You received this bug notification because you are a direct subscriber
of the bug.

Changed in linux-source-2.6.20:
assignee: thotz → nobody
assignee: nobody → phillip-lougher
Revision history for this message
BullCreek (jeff-openenergy) wrote :

FWIW, the April 2 daily build boots fine from CD whether the network is plugged in or not - so I guess this bug is fixed.

Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

There has been a couple of bug fixes to some ethernet drivers (Sky2) since Beta. These have probably fixed your problem.

Thanks for getting back, we can mark this as closed.

Changed in linux-source-2.6.20:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.