Re: please help! debian won't boot
On 13-12-2017, at 23h 02'29", Jason Brenkus wrote about "Re: please help! debian won't boot" > 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 :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? > Not more that what already was discussed. It looks like your Debian boots fine. Try to access a console with Ctrl-Alt-Fn, where n=2-6, or with Shift-Fn, if Ctrl-Alt-Fn doesn't work. Then login at the console and check the logs. If you have another computer you can try to ping or even ssh into this Debian box. You can check your router and try to identify from the dhcp clients list which one can be your Debian box. If you have no other computers and you can't get into any console, try to boot with a live disk, mount the harddrive and check the logs for clues on what went wrong. My best guess at the moment is that your kdm/gdm/xdm and X11 cannot start due to a faulty xorg.conf file. All those messages that disappeared are still there. You can get back to it with Ctrl-Alt-F1 or Shift-F1. Ionel
Re: please help! debian won't boot
Jason Brenkus composed on 2017-12-13 23:02 (UTC-0800): > 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 :03:00.0 eth0: link up > # Ipv6: ADDCONF(NETDEV_CHANGE): eth0: link becomes ready. Did you try keying in Ctrl-Alt-F2 after seeing nothing more? > 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? What did you mean when you wrote "recover mode"? Was that a Grub menu choice? Were there any other menu choices available, such as prior kernel? You could try appending to the main grub selection "plymouth.enable=0', and/or removing any cmdline options mentioning modeset, quiet, splash, gfxmode, vga and/or video. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: please help! debian won't boot
When you downloaded what you used to install debian, did the file have a .torrent on the end of it? If not you may have better luck by using a bittorrent client and downloading the torrent form of the file. Reason is integrity checks get done as you download and it could be you got a bad download using another form of download file. Another suggestion I would make since you may have some pretty far out hardware is to download the image that starts with firmware- and ends with .torrent. It should also have x86 somewhere in the name of the image to match as closely as possible your hardware. Good luck. On Wed, 13 Dec 2017, Jason Brenkus wrote: Date: Thu, 14 Dec 2017 02:02:29 From: Jason Brenkus <jasonbren...@gmail.com> To: Ionel Mugurel Ciob?c? <i.m.ciob...@gmail.com>, debian-user@lists.debian.org Subject: Re: please help! debian won't boot Resent-Date: Thu, 14 Dec 2017 07:02:48 + (UTC) Resent-From: debian-user@lists.debian.org 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 :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 --
Re: please help! debian won't boot
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 :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 > >
Re: please help! debian won't boot
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
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 ? 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.
Re: please help! debian won't boot
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. Hi, Not knowing that is wrong I would reinstall grub. Boot with a live disk or with the install disk and reinstall grub. If you need help with all the steps please ask. But also try to capture the last two lines or so when the system is booting before it gets to the blank screen. It is important to know if the system stops before or after loading the kernel, etc. Good luck. Ionel P.S. I took the liberty to correct debain into debian.
