You are not logged in.
Pages: 1
Hello guys!
I have some problem installing and booting Bunsenlabs Linux on my netbook, here's my story:
I have an Acer Cloudbook AO1-431-C2YR, updated BIOS v1.11
I found these guides:
(1) https://wiki.archlinux.org/index.php/Acer_Cloudbook
(2) https://forums.bunsenlabs.org/viewtopic.php?id=2200
(3) https://github.com/tmlbl/acer-cloudbook-11-bunsenlabs
and using these parameters
edd=off noapic modprobe.blacklist=pinctrl_cherryview
i'm able to install and boot any distro i tried (Elementary, Mint, Lubuntu, Ubuntu Mate) except my beloved BL..
I'm able to install the os (same step as guide 2 and 3) but after the kernel boot there is only a black screen.
I'm able to access the LIVE version of the os if i add "vga=788" with the others parameters, like this:
vga=788 edd=off noapic modprobe.blacklist=pinctrl_cherryview
but, again, this is only working for the live os, and the 800x600 grub resolution is keep in the live desktop although my real resolution is 1366x768.
I'm installing BL from an USB, i tried burning an ISO, i tried DD, i tried with the UEFI, i tried with the Legacy BIOS, i tried installing debian netiso +nonfree firmware then using the Bunsenlabs script and it works fine but after the needed reboot same thing happens: grub, edit parameters, kernel loading, black screen.
The behavior is the same as the other distro if i don't use the "modprobe.blacklist=pinctrl_cherryview" parameters, and since the live version is not starting if not in "vga=xxx" i suspect is a graphic issue.
The lastest BIOS update is labeled as "Updates CPU microcode and VGA BIOS/GOP driver" and i belive the guides are not using the lastest update as i do.
But it's just a guess here...
There's something i can do to find what's going on?
Thanks for helping and sorry for my English.
Last edited by Dag_01 (2016-11-19 21:30:00)
Offline
Try adding this kernel command line parameter:
nomodeset
Probably best to remove vga=788 when you test this.
Offline
Hi Head_on_a_Stick!
Thanks for reading my problem.
I tested the "nomodeset" parameter multiple times in multiple ways but it's not working.
I will continue my investigation...
EDIT:
I just realized all the distro i tried were Ubuntu based and all are working fine.
Debian without gui is also booting fine.
Debian with gui or BL iso can be installed but not booting.
Debian Stretch cannot be installed at all.
Firmware/Driver/Kernel differences?
Should i post this to the debian forum?
Last edited by Dag_01 (2016-11-19 21:41:05)
Offline
Hi Head_on_a_Stick!
Thanks for reading my problem.I tested the "nomodeset" parameter multiple times in multiple ways but it's not working.
I will continue my investigation...EDIT:
I just realized all the distro i tried were Ubuntu based and all are working fine.
Debian without gui is also booting fine.
Debian with gui or BL iso can be installed but not booting.
Debian Stretch cannot be installed at all.Firmware/Driver/Kernel differences?
Should i post this to the debian forum?
Hi Dag! Question if you boot into the BL console ( I believe you can, from what I can gather from your statement) can you start the gui with the startx command?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Hi Horizon_Brave, thanks for helping!
I used my live USB to boot in BL console using the "single" kernel parameter.
Then "startx" and black screen.
I bet is something gui/graphic related haha
Should i repeat the test with the installed os?
Offline
EDIT:
I just realized all the distro i tried were Ubuntu based and all are working fine.
Debian without gui is also booting fine.
Debian with gui or BL iso can be installed but not booting.
Debian Stretch cannot be installed at all.Firmware/Driver/Kernel differences?
Should i post this to the debian forum?
yes and yes.
i think it is likely to have something to do with kernel versions and how they support the (presumably intel?) graphics.
i'm sure this is also possible to solve via command line, so do the normal install, ignore the gui, and fix the issue (use a newer, backported kernel?) via commandline.
Offline
Should i post this to the debian forum?
Only in respect of the pure Debian installation attempt, please do not post BL support queries on forums.debian.net
Offline
i'm sure this is also possible to solve via command line, so do the normal install, ignore the gui, and fix the issue (use a newer, backported kernel?) via commandline.
Thanks ohnonot!
Installed fresh BL, booted in "single" mode, added debian backports..
apt-get -t jessie-backports install linux-image-amd64 linux-base
apt-get -t jessie-backports install xserver-xorg-video-intel libegl1-mesa libgl1-mesa-glx libgl1-mesa-dri
apt-get -t jessie-backports install firmware-misc-nonfree
"linux-base" was a requirement for "linux-image-amd64" (kernel 4.7.0-0.bpo.1 something something).
I don't know if i need all the xserver and mesa stuff, but since i'm on intel graphic...
Copied some packages from here https://forums.bunsenlabs.org/viewtopic.php?id=1185
"firmware-misc-nonfree" just in case.
Rebooted... and now i get a kernel panic:
Kernel Panic - Not syncing: Attempted to kill init! exitcode=0x00000009
I'm dying inside.
Offline
Not sure if this will help, but after having installed BL normally on one of my laptops, it happens occasionally that instead of the login screen I see an apparently unresponsive black screen. If I use Ctrl-Alt-F1 to switch to TTY1 and then, without even logging in, immediately use Ctrl-Alt-F7 to switch back to graphical, the login screen usually appears and I can use my system as normal. Occasionally I have to repeat the process a couple of times. In my experience this usually solves the problem for several weeks. I really don't know if it's the same problem or if this "solution" will work, but I thought I'd mention it just in case.
Last edited by photonucleon (2016-11-21 23:48:29)
The servant lifted off a kind of ottoman a long peacock-blue drapery, rather of the nature of a domino, on the front of which was emblazoned a large golden sun, and which was splashed here and there with flaming stars and crescents. “You’re to be dressed as Thursday, sir,” said the valet somewhat affably.
Offline
Hi photonucleon!
Thanks for the suggestion, i just tried that combination in a live usb image of BL but didn't work.
Offline
Not sure why it'd be all that bad an idea to ask on Debian forums. No biggie, although HOAS knows of which he speaks. Guess it's poss you could receive a less than warm welcome for using a Debian base distro.
Not a big fan of Deb forum and many more experienced nixers expressed the same to me when 1st starting out with gnu/Linux. Love Debian, one of the oldest/best distributions ever and know there's many awesome folks among the community too.
Seems like Debforum has been taken over (to an extent)by frothing at the mouth Debian fanboi's, often found they have no idea what they're talking about.
Lol ... sowwie, end off semi-offtopic rant. A good trick to learn is google search modifiers. You can search a given site or online resource for specific keywords using them. An example of telling da mighty goog that you want to confine your search to Debian forum would be as follows.
site:forums.debian.net/ "Acer Cloudbook AO1-431-C2YR" +"black screen"
That's just an example, enclosing it in quotes tells goog you only want that exact string of words and the + is just like saying I also want this word, or these words included in the search too.
That search above might not yield best results, though might. You may have to play around with the wording and parameters a bit but if there's discussions on Deb forum about your model pc and you can refine it with additional stuff to zero in on relevant threads. Then google will find it for you.
Update: Sheesh did a few searches via modifier, pickings related to cloudbooks seem to be slim on the Debian forum. Though search modifiers can be used to zero in on an entire web search basis too. This isn't a good example but search modifiers really can come in handy in my experience. Often times much better to use than a given sites own integrated search functions. Plus just good to know and learn about in general I think anyway.
Here's a couple of searches that may help you figure things out.
1. link
2. link
Last edited by BLizgreat! (2016-11-22 13:42:33)
Offline
Not sure why it'd be all that bad an idea to ask on Debian forums.
@dasein usually links this post to transgressors:
http://forums.debian.net/viewtopic.php? … 15#p542283
Remember folks, BunseLabs != Debian, please don't post support requests for this distribution over at forums.debian.net
@OP: I think perhaps you should try another distribution, I recommend Arch for newer hardware.
Offline
Geez for such an awesome distro Debian sure is turning a blind eye to what's happening on their forum huh ? Ouch ... Don't doubt there's still a metric tonne of really knowledgeable and good natured types among the Debian community. Think they've mostly all conceded the Deb forum to the fanboi's and trolls though ... sad.
Last edited by BLizgreat! (2016-11-22 23:28:12)
Offline
ohnonot wrote:i'm sure this is also possible to solve via command line, so do the normal install, ignore the gui, and fix the issue (use a newer, backported kernel?) via commandline.
Thanks ohnonot!
Installed fresh BL, booted in "single" mode, added debian backports..apt-get -t jessie-backports install linux-image-amd64 linux-base apt-get -t jessie-backports install xserver-xorg-video-intel libegl1-mesa libgl1-mesa-glx libgl1-mesa-dri apt-get -t jessie-backports install firmware-misc-nonfree
"linux-base" was a requirement for "linux-image-amd64" (kernel 4.7.0-0.bpo.1 something something).
I don't know if i need all the xserver and mesa stuff, but since i'm on intel graphic...
Copied some packages from here https://forums.bunsenlabs.org/viewtopic.php?id=1185
"firmware-misc-nonfree" just in case.Rebooted... and now i get a kernel panic:
Kernel Panic - Not syncing: Attempted to kill init! exitcode=0x00000009
I'm dying inside.
when you're in the middle of troubleshooting it is prudent to also look at the output of commands and supply that output here.
and your statement "Copied some packages from here" is very vague. what do you mean? copied .debs and installed them? which .debs, i don't see any in this thread?
have you followed the kernel backporting thread on these forums?
we need more information to be able to help you.
please also include the output of
lspci -k
uname -rv
Offline
Pages: 1