SliTaz SliTaz Forum

You are not logged in.

#1 2013-01-17 00:26:50

christophe
Member
Registered: 2011-04-17
Posts: 432

Problem booting an asus x201e

I cant boot slitaz 4 on that machine (from a live usb) I always get a black screen

The last message i am seeing is (i think, but it is so fast)

* loading module intel-agp

then i hear the disk being accessed for a short while

ctrl atl F1 does not bring up a console

and adding option screen=text on grub line does not bring me to text

in fact the only thing i could do is bring up the command under limited "core" boot choice

System spec: intel celeron b847, 4GB ram

From ubuntu i get this:

christophe@christophe-X201EP:~$ lspci

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)

00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)

00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)

00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)

00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)

00:1c.1 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 2 (rev c4)

00:1c.3 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 4 (rev c4)

00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)

00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)

00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)

00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)

02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

03:00.0 Ethernet controller: Atheros Communications Inc. AR8162 Fast Ethernet (rev 10)

christophe@christophe-X201EP:~$

Any hint ? or is the processor to recent to be supported properly by slitaz ?

Offline

#2 2013-01-22 12:10:35

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

reading this post http://forum.slitaz.org/topic/installer-cant-find-partitions-eee-pc-900a

and the comments from domcox,

Could my problem be related to GPT ?

the disk use a gpt scheme

I was under the impression slitaz4 would boot from the USB, it does but there is a problem later, the last thing is see is the disk being accessed, could this be tied to gpt ?

any hint ?

Offline

#3 2013-01-22 15:29:48

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Problem booting an asus x201e

It could be drm module frame buffer acceleration which kicks in before xorg starts.

[c]nomodeset[/c] turns it off

Tab the core menu choice

Add [c]nomodeset[/c] after autologin

Enter

Offline

#4 2013-01-22 16:50:08

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

Thanks.

I tried to force (successively) modeset, nomodeset, i915.modeset=0, and i915.modeset=1,

with no success sad

Does it help to know that the only thing which booted "as expected" was the core kernel ?

(but then of course i am stuck with something i cant use....)

Is there any other flavor that would be worth it to try to tackle the issue ?

Offline

#5 2013-01-22 18:13:59

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Problem booting an asus x201e

The kernel (linux-2.6.37.tazpkg) refered as linux on a package.list is the same regardless of which flavor you boot the slitaz-4.0 core 4-in-1 into.

If your having xorg problems core,gtk+,and justx all include xorg and will fail.

Your system should boot to a login prompt choosing base flavor which has no xorg-server.

Offline

#6 2013-01-22 21:57:47

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

okay,

base boot until login prompt and i can login as root

just-x does not go anywhere except black screen after * loading module intel-agp

But i can see it still accesses the disk

i checked that that processor was announced late in 2011

Could it be though that intel-agp would be outdated for that specific proc ?

or that the problem is tied to GPT (since i can hear it tries to access the disk)

or any other hint ?

Offline

#7 2013-03-15 02:35:57

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

@ Mojo:

Just checked the embedded graphic is  HD 2000 based

Could there be a driver issue here ? either needing some new driver or a different option at kernel building time ? Thanks.

(disappointed that slitaz still does not work on that machine)

Offline

#8 2013-04-04 22:28:13

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

@ mojo

You were almost right

I made progress thanks to this post

http://forum.slitaz.org/topic/new-pc-and-black-screen-at-boot

So nomodeset has to be added BEFORE autologin, and i have to add screen = text at the end

then I log in as tux in text mode, and I run startx

i get the graphical interface (i cannot see the mouse, pointer but there is some pointer as i can open the application menu) and i can open from the menu a terminal

in which i will run openbox

At this point everything looks familiar, the cursor is visible (i think i still have a keyboard problem, the keyboard was setup properly at boot time as i can check from the console when logging in; however after startx in the sakura terminal i have a US keyboard).

Neither the wifi nor the ethernet adapter get recognized however, they are Atheros chips

~$ lspci | grep Atheros

02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

03:00.0 Ethernet controller: Atheros Communications Inc. AR8162 Fast Ethernet (rev 10)

~$

Any suggestion on how to proceed ? To solve both the network and graphical issues.

[this is a hd2000 based Celeron, so i would think this problem should be fairly common on the recent laptops]

Thanks

Offline

#9 2013-04-06 17:10:26

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Re: Problem booting an asus x201e

@ Christophe,

Trick of the day : when you use the screen=text option, don't ask you anymore if you must place nomodeset before or after autologin, replace autologin with nomodeset...

Offline

#10 2013-04-06 20:30:42

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

ok thanks, will try that, I still have some other issues...

Have you been able to make it work on the HD3000 ? is this on a mobile processor ?

I have an i3 which is hd3000 based and works flowlessy (from what i remember, I do not have enough time to work on it at this time)

Offline

#11 2013-04-06 20:55:07

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Re: Problem booting an asus x201e

Yes it is on a mobile processor and yes it works on HD3000 adding nomodeset and screen=text options at boot (SliTaz 4.0 but not installed, LiveCD/USB and frugal install).

I have to log as root and type commands

# mkdir /home/tux/.config/slitaz

# cp /etc/slitaz/applications.conf /home/tux/.config/slitaz

# slim

as well as with Live than frugal on this computer (Fujitsu Siemens Lifebook S752)

(http://forum.slitaz.org/topic/unable-to-do-a-frugal-install-of-slitaz-40)

Offline

#12 2013-04-06 21:40:26

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

by the way my proc is not a i3 but a celeron g530 and not a mobile processor, obviously. Sorry.

Thanks.

I will try if my problem on the laptop is similar to yours (for the graphics). I still have to find a solution for the Atheros network adapter though.

Offline

#13 2013-04-07 15:21:14

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Problem booting an asus x201e

@christophe

[c]lspci -nn | grep Atheros[/c]

Offline

#14 2013-04-07 21:07:26

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

~$ lspci -nn |grep Ath

02:00.0 Network controller [0280]: Atheros Communications Inc. AR9485 Wireless Network Adapter [168c:0032] (rev 01)

03:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR8162 Fast Ethernet [1969:1090] (rev 10)

~$

tx for your hints

Offline

#15 2013-04-08 18:31:57

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Problem booting an asus x201e

02:00.0 Network controller [0280]: Atheros Communications Inc. AR9485 Wireless Network Adapter [168c:0032] (rev 01)

[c]# modprobe ath9k[/c]

[c]# echo "168c 0032" >> /sys/bus/pci/drivers/ath9k/new_id[/c]

03:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR8162 Fast Ethernet [1969:1090] (rev 10)

atlxx-compat-2.6.37.tazpkg => http://www.mediafire.com/?78uu0xnqx06z84s

[c]# tazpkg install atlxx-compat-2.6.37.tazpkg[/c]

[c]# modprobe alx[/c]

Offline

#16 2013-04-13 01:18:45

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

sad

modprobe ok

but ifconfig does not show any additional interface

what am I missing ?

Tx

Offline

#17 2013-04-13 01:41:06

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Problem booting an asus x201e

Open a second terminal:

[c]tail -f /var/log/messages[/c]

Google any errors you see while you modprobe the drivers.

If the output of:

[c]ls /sys/class/net[/c]

show no additional alias for network interfaces after modprobe and echo new_id then you will have to compile compat-wireless on Slitaz-4.0 yourself. If that doesn't work your out of luck because ath9k and athxx drivers(atheros) are only available with compat-wireless unlike most the others (ralink,realtek,broadcom,etc.) which have an alternative driver available from the manufacturer.

Offline

#18 2013-04-13 03:45:24

christophe
Member
Registered: 2011-04-17
Posts: 432

Re: Problem booting an asus x201e

i see a bunch of these:

Apr 13 03:15:31 (none) daemon.err udevd[1883]: error binding udev control socket

Apr 13 03:15:31 (none) daemon.err udevd[1884]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Apr 13 03:15:31 (none) daemon.err udevd[1884]: bind failed: Address already in use

Apr 13 03:15:31 (none) user.info kernel: cfg80211: Calling CRDA to update world regulatory domain

Apr 13 03:15:31 (none) daemon.err udevd[1884]: error binding udev control socket

Apr 13 03:15:31 (none) daemon.err udevd[1885]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

Apr 13 03:15:31 (none) daemon.err udevd[1885]: bind failed: Address already in use

Apr 13 03:15:31 (none) daemon.err udevd[1885]: error binding udev control socket

Apr 13 03:15:31 (none) daemon.err udevd[1887]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

note the calling CRDA in the middle of the mess

I take all these messages as not being real issues though, am I right ?

ls /sys/class/net

does not show any  additional alias for network interfaces after modprobe and echo new_id

I can recompile compat-wireless, where do I get the source code ? is it on a slitaz server ?

I have already installed the development toolchain on a disk.

-------------------------------------------------------

I am having a bunch of other issues though, as i mentionned.

I have to boot with nomodeset and screen=text

then login as tux and startx

but I get a graphical interfact with openbox not started i have to start it manually from sakura

The sakura terminal has a us keyboard; if i redefine the keyboard as french then tazusbwritefs and reboot, then the graphical interface will start, EXCEPT THERE IS no lxpanel, and left/right clicks wont work so I cannot rightclick to start a sakura terminal to start openbox (and lxpanel); so I had to revert to the previous rootfs.gz, and i am stuck with that US keyboard (uncomfortable, and it does not support the "pipe" sad sad )

Any suggestion for that one too ?

I also see the infamous MTTR message at shutdown time (and at other time also, if i do not follow that complex startup procedure i mentionned...)

---------------------------------

The support for that machine looks horrible, I know. At least I can hope other could benefit from that experience if we can solve this.

Thanks

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]