Just do a google of Gutsy daily live, will take you right to it.

On Sat, 2007-10-06 at 17:07 +0000, Cristian wrote:
> Thanks for the reply!,
> Yes, it has the VIA K8T800Pro chipset.
> I was wondering where did you downloaded the daily build of the 7.10 live cd??
> i would like to try it in my system.
> 
> Cristian
> 
> ----- Original Message ----
> From: wpshooter <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Saturday, October 6, 2007 1:04:33 PM
> Subject: Re: [Bug 99757] Re: still getting /bin/sh: can't access tty error
> 
> Christian:
> 
>     I just noticed that your ASUS system apparently is a VIA chipset.  If
> memory serves me correct, my MSI motherboard has a VIA chipset.
> 
> On Sat, 2007-10-06 at 03:52 +0000, Cristian wrote:
> > I am having the same error with 7.10 Beta Desktop CD (amd64 version)
> > When booting from the Desktop CD, after i choose the first option in the 
> > boot menu, 
> > it shows the ubuntu logo and the loading bar,  and after a while it would 
> > show
> > the famous busybox console with "can't access tty" message.
> > I tried the solutions proposed for 7.04 (loading piix) but none of them 
> > worked.
> > This is my hardware configuration:
> > 
> > Motherboard: Asus A8V Deluxe (Chipset: VIA K8T800Pro / VIA VT8237)
> > Amd64 3000+ (S939)
> > sda (sata): WDC WD800JD-00JNC0, 05.01C05, max UDMA/133
> > hda: LITE-ON DVDRW SHW-160P6S
> > hdb: SONY CD-ROM CDU5215
> > Video: ATI Radeon 9600
> > 
> > If you need more information just ask ;)
> > Regards!
> >     Cristian
> >
> 
> -- 
> still getting /bin/sh: can't access tty error
> https://bugs.launchpad.net/bugs/99757
> You received this bug notification because you are a direct subscriber
> of the bug.
> 
> 
> 
>        
> ____________________________________________________________________________________
> Need a vacation? Get great deals
> to amazing places on Yahoo! Travel.
> http://travel.yahoo.com/
>

-- 
still getting /bin/sh: can't access tty error
https://bugs.launchpad.net/bugs/99757
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to