SliTaz Forum

Problem booting an asus x201e

(18 posts) (3 voices)

• Started 11 years ago by christophe
• Latest reply from christophe
• This topic is not resolved

Tags:

No tags yet.

1. 

   christophe
   

   offline

   Member

   :(
   modprobe ok
   but ifconfig does not show any additional interface
   what am I missing ?

   Tx

   Posted 11 years ago #
2. 

   mojo
   

   offline

   Key Master

   Open a second terminal:
   tail -f /var/log/messages
   Google any errors you see while you modprobe the drivers.
   If the output of:
   ls /sys/class/net
   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.

   Posted 11 years ago #
3. 

   christophe
   

   offline

   Member

   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" :( :( )

   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

   Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.