Testing only starts on recovery

Kernels & Hardware, configuring network, installing services

Testing only starts on recovery

Postby noober1983 » 2017-08-26 03:03

Hi all.

I just installed Testing on an Acer Aspire E1 box. It works well. However it won't boot in 'normal' mode, only in recovery. If selected (or if I just let the GRUB timer go off) nothing will load, I get a black screen with a blinking cursor on the top left corner. I can boot in recovery mode and press Ctrl+D when prompted and X starts normally.

The only similar problem I found was this one: https://ubuntuforums.org/showthread.php?t=2120067. This doesn't seem to be my issue however; the radeon module is working, and I installed the following packages: radeontool, xserver-xorg-video-{amdgpu, radeon}, firmware-amd-graphics, and appropriate versions of headers for amd64 (I run kernel 4.12).

Is there anything I am missing? Any ideas?

Thanks a lot! Cheers!
Quid non intellegit aut tasceat aut discat.
noober1983
 
Posts: 53
Joined: 2012-04-03 00:12
Location: MX

Re: Testing only starts on recovery

Postby arochester » 2017-08-26 08:04

Are you sure about the required firmware?

This: http://www.linlap.com/acer_aspire_e1-571
says the Graphics chip is an Inter i915
"Something to be aware of: Debian is a core or source distribution. This means there are many Debian-based distributions. THEY ARE NOT DEBIAN."
arochester
 
Posts: 1029
Joined: 2010-12-07 19:55

Re: Testing only starts on recovery

Postby noober1983 » 2017-08-26 13:23

arochester wrote:Are you sure about the required firmware?

This: http://www.linlap.com/acer_aspire_e1-571
says the Graphics chip is an Inter i915

Not my model. I own an E1-421-0428, which is not listed on that site. This one has a Radeon 6320 HD card. I wasn't able to find a site in Enlgish for this model, but I found this one on Spanish: https://pcel.com/Acer-NX-M0ZAL-008-90971, just go to section "Gráficos" (I bought this box in Mexico). Thanks.
Quid non intellegit aut tasceat aut discat.
noober1983
 
Posts: 53
Joined: 2012-04-03 00:12
Location: MX

Re: Testing only starts on recovery

Postby noober1983 » 2017-09-02 17:08

Bump! Anybody? Please!
Quid non intellegit aut tasceat aut discat.
noober1983
 
Posts: 53
Joined: 2012-04-03 00:12
Location: MX

Re: Testing only starts on recovery

Postby GarryRicketson » 2017-09-02 18:26

What does 'lspci' show ?

Are you sure there is not just some problem with Debian testing that is causing
the problem ?
https://wiki.debian.org/DebianTesting
How to use Debian (next-stable) Testing

First thing is to assess the current state of testing. Have a look at the recent topics in the debian-testing mailing list archive and the Status/Testing Wiki-Page. Besides using these specific resources you can also use the general debian-user and debian-devel mailing lists, IRC channels #debian or #debian-next, and of course the debian bug tracker. You may also have a look at the DebianDesktopHowTo.
User avatar
GarryRicketson
 
Posts: 4206
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Testing only starts on recovery

Postby noober1983 » 2017-09-02 20:32

GarryRicketson wrote:What does 'lspci' show ?

Are you sure there is not just some problem with Debian testing that is causing
the problem ?
https://wiki.debian.org/DebianTesting
How to use Debian (next-stable) Testing

First thing is to assess the current state of testing. Have a look at the recent topics in the debian-testing mailing list archive and the Status/Testing Wiki-Page. Besides using these specific resources you can also use the general debian-user and debian-devel mailing lists, IRC channels #debian or #debian-next, and of course the debian bug tracker. You may also have a look at the DebianDesktopHowTo.


I will read the wiki and try to find my way through the mailing lists. However I successfully installed Testing on a newer laptop (Inspiron 15) and this one boots normally. I'll post updates on Monday since the laptop in question here is the one I use at the office.

Thanks a lot!
Quid non intellegit aut tasceat aut discat.
noober1983
 
Posts: 53
Joined: 2012-04-03 00:12
Location: MX

Re: Testing only starts on recovery

Postby GarryRicketson » 2017-09-02 20:37

Ok, the 'lspci' command should show for sure what drivers it actually has.
It might not be the same as it is on the site that shows the specs.
User avatar
GarryRicketson
 
Posts: 4206
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Testing only starts on recovery

Postby stevepusser » 2017-09-02 21:24

Or install inxi and give us the output of

Code: Select all
inxi -F


I find that gives a less techy, verbose yet even more informative (where it counts) output than the "lsXXX" commands.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: AzPainter 2.1.0, Pale Moon 27.4.2, Liquorix kernel 4.12-6, mpv 0.26.0, Kodi 17.3, 0ad 0.0.22, Mesa 13.0.6
User avatar
stevepusser
 
Posts: 8690
Joined: 2009-10-06 05:53

Re: Testing only starts on recovery

Postby noober1983 » 2017-09-04 17:19

Hi all.

This is the output of inxi -Fxxx:
Code: Select all
System:    Host: baldrick Kernel: 4.12.0-1-amd64 x86_64 bits: 64 gcc: 6.4.0
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) info: xfce4-panel dm: lightdm
           Distro: Debian GNU/Linux buster/sid
Machine:   Device: laptop System: Acer product: Aspire E1-421 v: V1.04
           Mobo: Acer model: EA40_BZ
           UEFI [Legacy]: Insyde v: V1.04 date: 05/02/2012
Battery    BAT1: charge: 34.8 Wh 100.0% condition: 34.8/47.5 Wh (73%)
           volts: 12.2/10.8
           model: SAMSUNG AS10D73 Li-ion serial: 2374 status: Full cycles: 0
CPU:       Dual core AMD E-450 APU with Radeon HD Graphics (-MCP-)
           arch: Bobcat rev.0 cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4a ssse3 svm) bmips: 6587
           clock speeds: min/max: 825/1650 MHz 1: 1650 MHz 2: 1650 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320]
           bus-ID: 00:01.0 chip-ID: 1002:9806
           Display Server: x11 (X.Org 1.19.3 )
           drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.10hz
           OpenGL: renderer: Gallium 0.4 on AMD PALM (DRM 2.50.0 / 4.12.0-1-amd64, LLVM 3.9.1)
           version: 3.3 Mesa 13.0.6 (compat-v: 3.0) Direct Render: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
           driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1022:780d
           Card-2 Advanced Micro Devices [AMD/ATI] Wrestler HDMI Audio
           driver: snd_hda_intel bus-ID: 00:01.1 chip-ID: 1002:1314
           Sound: Advanced Linux Sound Architecture v: k4.12.0-1-amd64
Network:   Card-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet
           driver: atl1c v: 1.0.1.1-NAPI port: 2000
           bus-ID: 01:00.0 chip-ID: 1969:1083
           IF: enp1s0 state: down mac: 04:7d:7b:e1:16:f2
           Card-2: Qualcomm Atheros AR9485 Wireless Network Adapter
           driver: ath9k bus-ID: 02:00.0 chip-ID: 168c:0032
           IF: wlp2s0 state: up mac: 74:e5:43:4c:62:ab
Drives:    HDD Total Size: 500.1GB (3.4% used)
           ID-1: /dev/sda model: ST500LT012 size: 500.1GB serial: S0V04CWA
Partition: ID-1: / size: 28G used: 8.1G (32%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 427G used: 4.2G (2%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 4.00GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 93.8C mobo: N/A gpu: 95.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 164 Uptime: 2 days Memory: 1105.1/3681.1MB
           Init: systemd v: 234 runlevel: 5 Gcc sys: 7.2.0 alt: 6
           Client: Shell (bash 4.4.121 running in xfce4-terminal) inxi: 2.3.34

This is the output of lspci -vv|grep -i vga:
Code: Select all
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] (prog-if 00 [VGA controller])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
   Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

I googled the error above but nothing useful came up; there are reports of this error on machines that crash under Ubuntu, but nothing else.
Quid non intellegit aut tasceat aut discat.
noober1983
 
Posts: 53
Joined: 2012-04-03 00:12
Location: MX


Return to System configuration

Who is online

Users browsing this forum: No registered users and 11 guests

fashionable
cron