Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #163885 > unrolled thread

Install ok, boot fail

Back to article view | Back to linux.debian.user

Contents

  Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-05 15:10 +0100
    Re: Install ok, boot fail debian@semioptimal.net - 2016-02-05 15:30 +0100
      Re: Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-06 11:50 +0100
        Re: Install ok, boot fail "computer.enthusiastic" <computer.enthusiastic@gmail.com> - 2016-02-06 17:10 +0100
          Re: Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-08 00:20 +0100
    Re: Install ok, boot fail Brian <ad44@cityscape.co.uk> - 2016-02-05 17:10 +0100
      Re: Install ok, boot fail Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-02-06 00:30 +0100
        Re: Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-06 12:40 +0100
          Re: Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-08 13:30 +0100
            Re: Install ok, boot fail Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-02-08 22:10 +0100
              Re: Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-08 22:40 +0100
            Re: Install ok, boot fail arian <debian@semioptimal.net> - 2016-02-09 17:50 +0100
              Re: Install ok, boot fail Fabrizio Carrai <fabrizio.carrai@gmail.com> - 2016-02-09 19:10 +0100

#163885 — Install ok, boot fail

[Multipart message — attachments visible in raw view] — view raw

Hello all,
I'm using a single board computer where I'm trying to install Debian 8.3.

The boot from USB was fine, and so the whole installation process. The
target SATA HD has been partitioned by the installer and nothing was
remaining of old installation.

Then, at the boot time, nothing happen. After the BIOS messages the screen
remain black (no messages at all).

I temporary move the disk to another computer and then I was able to boot
the fresh Debian installation (that confirmed that the installation was ok).

Any idea on the problem or how I could investigate on ?
Thanks for any help

-- 
*Fabrizio*

[toc] | [next] | [standalone]

#163886

[Multipart message — attachments visible in raw view] — view raw

Hi Fabrizio,

> I'm using a single board computer
you need to be more specific. What Computer? As you're saying BIOS and later on other computer this sounds like i386 or amd64. But is it
- EFI64
- EFI32
- actually BIOS?

other than that:
boot settings correct?

I've seen HP EFI32/64 craptops that just did not run grub but whatever windows loader they could come up with.

Regards, Arian

[toc] | [prev] | [next] | [standalone]

#163893

[Multipart message — attachments visible in raw view] — view raw

I'm using an ADLINk Nanox-tx, The Bios ia an American Megatrends A1.2
The BIOS reports that EMT64 is supported.
Boot settings are coorect. I took care to set the HD as first device, but
with no joy.

The system succesfully boot the installation ISO from USB, so I also tried
to put the HD in an USB interface adapter but again without results.

I started installing the Debian AMD64 bit version. Thought that this was
the problen, I did another installation with the i386 distro, but still
without results.

>>"I've seen HP EFI32/64 craptops that just did not run grub but whatever
windows loader they could come up with."

That looks to be a similar case: Windows was ok.

Thanks!

Fabrizio


2016-02-05 15:20 GMT+01:00 <debian@semioptimal.net>:

> Hi Fabrizio,
>
> > I'm using a single board computer
> you need to be more specific. What Computer? As you're saying BIOS and
> later on other computer this sounds like i386 or amd64. But is it
> - EFI64
> - EFI32
> - actually BIOS?
>
> other than that:
> boot settings correct?
>
> I've seen HP EFI32/64 craptops that just did not run grub but whatever
> windows loader they could come up with.
>
> Regards, Arian
>
>


-- 
*Fabrizio*

[toc] | [prev] | [next] | [standalone]

#163901

[Multipart message — attachments visible in raw view] — view raw

​Hi Fabrizio,
​

2016-02-06 11:39 GMT+01:00 Fabrizio Carrai <fabrizio.carrai@gmail.com>:

>
> The system succesfully boot the installation ISO from USB, so I also tried
> to put the HD in an USB interface adapter but again without results.
>


​What is the name of Debian installation ISO image you have used ?​

[toc] | [prev] | [next] | [standalone]

#163926

[Multipart message — attachments visible in raw view] — view raw

I tried the stable debian 8.3 netinst, both 64 and 32 bits versions.

F.
Il 06 feb 2016 5:06 PM, "computer.enthusiastic" <
computer.enthusiastic@gmail.com> ha scritto:

> ​Hi Fabrizio,
> ​
>
> 2016-02-06 11:39 GMT+01:00 Fabrizio Carrai <fabrizio.carrai@gmail.com>:
>
>>
>> The system succesfully boot the installation ISO from USB, so I also
>> tried to put the HD in an USB interface adapter but again without results.
>>
>
>
> ​What is the name of Debian installation ISO image you have used ?​
>
>

[toc] | [prev] | [next] | [standalone]

#163887

On Fri 05 Feb 2016 at 15:05:27 +0100, Fabrizio Carrai wrote:

> Hello all,
> I'm using a single board computer where I'm trying to install Debian 8.3.
> 
> The boot from USB was fine, and so the whole installation process. The
> target SATA HD has been partitioned by the installer and nothing was
> remaining of old installation.
> 
> Then, at the boot time, nothing happen. After the BIOS messages the screen
> remain black (no messages at all).
> 
> I temporary move the disk to another computer and then I was able to boot
> the fresh Debian installation (that confirmed that the installation was ok).

The other computer likely has a graphics card which (for whatever reason)
can handle what is given to it.

> Any idea on the problem or how I could investigate on ?

Can you reboot the single board computer with CTRL-ALT-DEL and get back
to the GRUB menu?

At the GRUB menu edit the "linux" line and add "nomodeset" to the end of
it. Boot with F10.

[toc] | [prev] | [next] | [standalone]

#163890

Brian a écrit :
> On Fri 05 Feb 2016 at 15:05:27 +0100, Fabrizio Carrai wrote:
> 
>> Then, at the boot time, nothing happen. After the BIOS messages the screen
>> remain black (no messages at all).
>>
>> I temporary move the disk to another computer and then I was able to boot
>> the fresh Debian installation (that confirmed that the installation was ok).
> 
> The other computer likely has a graphics card which (for whatever reason)
> can handle what is given to it.
> 
>> Any idea on the problem or how I could investigate on ?
> 
> Can you reboot the single board computer with CTRL-ALT-DEL and get back
> to the GRUB menu?

IIUC, the GRUB menu is not even displayed.
However you may be correct about a graphics mode issue, but in GRUB, not
the kernel. I have seen it on a couple of machines/graphic cards.

Boot the system on the other machine or chroot from the installer or any
live system.
Edit /etc/default/grub to uncomment GRUB_TERMINAL=console.
Run update-grub to regenerate the grub config file.
Try to boot again on the single board.

[toc] | [prev] | [next] | [standalone]

#163897

[Multipart message — attachments visible in raw view] — view raw

Pascal,
you understood correctly: the GRUB is not even shown. Indeed it would be a
problen, but now is secondary.
If the GRUB could continue the process (after the timeout), even showing
nothing, that could be temporary acceptable. The problem is that it looks
like that GRUB stuck the PC.

I'm convincing that the problem is the GRUB. I tried to boot from a Super
Grub 2, but it stucks as well.

I'm going to work with the GRUB_TERMINAL=console setting.

Thanks

F.


2016-02-06 0:23 GMT+01:00 Pascal Hambourg <pascal@plouf.fr.eu.org>:

> Brian a écrit :
> > On Fri 05 Feb 2016 at 15:05:27 +0100, Fabrizio Carrai wrote:
> >
> >> Then, at the boot time, nothing happen. After the BIOS messages the
> screen
> >> remain black (no messages at all).
> >>
> >> I temporary move the disk to another computer and then I was able to
> boot
> >> the fresh Debian installation (that confirmed that the installation was
> ok).
> >
> > The other computer likely has a graphics card which (for whatever reason)
> > can handle what is given to it.
> >
> >> Any idea on the problem or how I could investigate on ?
> >
> > Can you reboot the single board computer with CTRL-ALT-DEL and get back
> > to the GRUB menu?
>
> IIUC, the GRUB menu is not even displayed.
> However you may be correct about a graphics mode issue, but in GRUB, not
> the kernel. I have seen it on a couple of machines/graphic cards.
>
> Boot the system on the other machine or chroot from the installer or any
> live system.
> Edit /etc/default/grub to uncomment GRUB_TERMINAL=console.
> Run update-grub to regenerate the grub config file.
> Try to boot again on the single board.
>
>


-- 
*Fabrizio*

[toc] | [prev] | [next] | [standalone]

#163939

[Multipart message — attachments visible in raw view] — view raw

Yes! The GRUB_TERMINAL=console setting works...at least I moved forward.Now
I can access and edit the GRUB menu.

Now the last messages visible on the screen are:

Unable to read GCT!
VBT signature missing

Then the screen slowly turns white. The problem seems to be in the video
interface integrated in the Atom E6xx. I tryed several linux command option
like video=640x480 but without effects...

Any suggestions ?

Thanks
F.


2016-02-06 12:31 GMT+01:00 Fabrizio Carrai <fabrizio.carrai@gmail.com>:

> Pascal,
> you understood correctly: the GRUB is not even shown. Indeed it would be a
> problen, but now is secondary.
> If the GRUB could continue the process (after the timeout), even showing
> nothing, that could be temporary acceptable. The problem is that it looks
> like that GRUB stuck the PC.
>
> I'm convincing that the problem is the GRUB. I tried to boot from a Super
> Grub 2, but it stucks as well.
>
> I'm going to work with the GRUB_TERMINAL=console setting.
>
> Thanks
>
> F.
>
>
> 2016-02-06 0:23 GMT+01:00 Pascal Hambourg <pascal@plouf.fr.eu.org>:
>
>> Brian a écrit :
>> > On Fri 05 Feb 2016 at 15:05:27 +0100, Fabrizio Carrai wrote:
>> >
>> >> Then, at the boot time, nothing happen. After the BIOS messages the
>> screen
>> >> remain black (no messages at all).
>> >>
>> >> I temporary move the disk to another computer and then I was able to
>> boot
>> >> the fresh Debian installation (that confirmed that the installation
>> was ok).
>> >
>> > The other computer likely has a graphics card which (for whatever
>> reason)
>> > can handle what is given to it.
>> >
>> >> Any idea on the problem or how I could investigate on ?
>> >
>> > Can you reboot the single board computer with CTRL-ALT-DEL and get back
>> > to the GRUB menu?
>>
>> IIUC, the GRUB menu is not even displayed.
>> However you may be correct about a graphics mode issue, but in GRUB, not
>> the kernel. I have seen it on a couple of machines/graphic cards.
>>
>> Boot the system on the other machine or chroot from the installer or any
>> live system.
>> Edit /etc/default/grub to uncomment GRUB_TERMINAL=console.
>> Run update-grub to regenerate the grub config file.
>> Try to boot again on the single board.
>>
>>
>
>
> --
> *Fabrizio*
>



-- 
*Fabrizio*

[toc] | [prev] | [next] | [standalone]

#163956

Fabrizio Carrai a écrit :
> Yes! The GRUB_TERMINAL=console setting works...at least I moved forward.Now
> I can access and edit the GRUB menu.

Note that it may still be possible to use the graphic terminal but with
specific graphics mode selected in /etc/default/grub.

> Now the last messages visible on the screen are:
> 
> Unable to read GCT!
> VBT signature missing
> 
> Then the screen slowly turns white. The problem seems to be in the video
> interface integrated in the Atom E6xx. I tryed several linux command option
> like video=640x480 but without effects...

I have never seen this.
Did you try the "nomodeset" option ?
Does it happen if you boot in recovery mode from GRUB ?

[toc] | [prev] | [next] | [standalone]

#163958

[Multipart message — attachments visible in raw view] — view raw

2016-02-08 22:00 GMT+01:00 Pascal Hambourg <pascal@plouf.fr.eu.org>:

> Fabrizio Carrai a écrit :
> > Yes! The GRUB_TERMINAL=console setting works...at least I moved
> forward.Now
> > I can access and edit the GRUB menu.
>
> Note that it may still be possible to use the graphic terminal but with
> specific graphics mode selected in /etc/default/grub.
>
> > Now the last messages visible on the screen are:
> >
> > Unable to read GCT!
> > VBT signature missing
> >
> > Then the screen slowly turns white. The problem seems to be in the video
> > interface integrated in the Atom E6xx. I tryed several linux command
> option
> > like video=640x480 but without effects...
>
> I have never seen this.
> Did you try the "nomodeset" option ?
> Does it happen if you boot in recovery mode from GRUB ?
>
>
Sorry, I found the "video=" option in a web page an I thought it was
standard, now I don't think so...
Yes, I tried the "nomodeset".

I did most of the tests editing the main Debian boot option from GRUB, the
boot in the recovery mode ends in the same way.

-- 
*Fabrizio*

[toc] | [prev] | [next] | [standalone]

#163996

[Multipart message — attachments visible in raw view] — view raw

Hi,
> Then the screen slowly turns white. The problem seems to be in the video interface integrated in the Atom E6xx. 

yes, that's your problem, it's not actually an intel gpu but powervr IP with an extremely crappy driver situation. Do you need display output your task? otherwise I'd scrap it and rely on ssh.

Search terms that may be more helpful than e600/gma600: gma500 (same IP at halve clock), poulsbo (codename)

[toc] | [prev] | [next] | [standalone]

#163999

[Multipart message — attachments visible in raw view] — view raw

Indeed, I don't need to use the monitor, but it is useful to login, to
configure the system and to interact just in case of network interface
unavailability. I will search for the term and driver you suggests.

By the way, to push the Debian developers: with LINUX MINT the system works
perfectly...!

Fabrizio

2016-02-09 17:46 GMT+01:00 arian <debian@semioptimal.net>:

> Hi,
> > Then the screen slowly turns white. The problem seems to be in the video
> interface integrated in the Atom E6xx.
>
> yes, that's your problem, it's not actually an intel gpu but powervr IP
> with an extremely crappy driver situation. Do you need display output your
> task? otherwise I'd scrap it and rely on ssh.
>
> Search terms that may be more helpful than e600/gma600: gma500 (same IP at
> halve clock), poulsbo (codename)
>
>


-- 
*Fabrizio*

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web