By cursor what I mean is a flashing underscore line. I tried reinstalling grub2 using super grub. At first I didn't think anything happened, but now I'm getting more then a blinking cursor. The screen now says #floppy0: no floppy controllers found # r8169 0000:03:00.0 eth0: link up # Ipv6: ADDCONF(NETDEV_CHANGE): eth0: link becomes ready.
I tried to record the script that show before this screen and it looks like there is a lot loading, but I saw one place in the script that had a red FAILED and it looks like it says #failed to start load kernel modules It would probably be easier to reinstall, but I'm trying to learn linux. Any more suggestions? On Wed, Dec 13, 2017 at 11:34 AM, Ionel Mugurel Ciobîcă < i.m.ciob...@gmail.com> wrote: > On 13-12-2017, at 19h 55'54", Pascal Hambourg wrote about "Re: please > help! debian won't boot" > > Le 13/12/2017 à 10:54, Ionel Mugurel Ciobîcă a écrit : > > >On 13-12-2017, at 01h 41'15", Jason Brenkus wrote about "please help! > debian won't boot" > > >>I am a novice to linux, and I'm in over my head. I'm not sure what went > > >>wrong or went. I am running Jessie. On startup the pc begins to load > and > > >>then goes to a screen with nothing but a cursor. Then nothing happens > no > > >>matter how long i wait. If i boot in to recover mode i get a screen > that > > >>says #IPv6: ADDRCONF (NETDEV_CHANGE): eth0: link becomes ready. And no > > >>amount of waiting changes it. I had trouble getting the correct > drivers for > > >>my gpu which is a amd radeon r9 270 i believe. The last thing i did > before > > >>the system didn't boot was install a mining program. > > > > > >Not knowing that is wrong I would reinstall grub. > > > > IMO it would be a total waste of time. What makes you think that GRUB is > > broken ? > > When you do not know too much about what is the status of the system > anything may be a total waste of time. > > In the past when using Lilo I got this kind of behaviour. Instead of > loading the kernel, just after BIOS I would ket a blinking cursor. > > > >It is important to know if the system stops before or after > > >loading the kernel, etc. > > > > We already know. The above message happens when the ethernet interface is > > activated, which means that the kernel was loaded and started, the > initramfs > > was loaded and did its job and the init system started its tasks. > > Then you know more than me. I will say then that X config is broken. > > What induced me in error was the word cursor. For me that was in tty1 > a blinking underscore line. What Jason may have meant was an X shape > mouse, for example. > > Ionel > >
