[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
howtos:hardware:arm:qemu_support_in_slackware_arm [2018/11/30 22:52 (UTC)] – [QEMU Network Settings] mralk3howtos:hardware:arm:qemu_support_in_slackware_arm [2018/11/30 22:57 (UTC)] – [Boot Slackware ARM with QEMU] mralk3
Line 255: Line 255:
 <note important>You may need to edit the /etc/resolv.conf file on the host.  Add in the IP addresses of your preferred primary and secondary name server(s) since you are not receiving these IP addresses by other means.  The name server is 192.168.1.1 (or the default gateway) in this tutorial</note> <note important>You may need to edit the /etc/resolv.conf file on the host.  Add in the IP addresses of your preferred primary and secondary name server(s) since you are not receiving these IP addresses by other means.  The name server is 192.168.1.1 (or the default gateway) in this tutorial</note>
  
-Modify the launcher helper scripts once you are certain your host has the appropriate network settings.  Pay close attention to the **$NETTYPE** variable.  Details about how to use this variable are documented in both the **installer_launch** and **disk_launch** helper scripts.  Edit the **$MACADDR** variable if you are running more than one Slackware ARM guest in QEMU at once.+Modify the launcher helper scripts once you are certain your host has the appropriate network settings.  Pay close attention to the **$NETTYPE** variable.  Details about how to use this variable are documented in both the **installer_launch** and **disk_launch** helper scripts.  Edit the **$MACADDR** variable for each QEMU instance if you are running more than one Slackware ARM guest at once.
 ===== Install Slackware ARM ===== ===== Install Slackware ARM =====
  
Line 319: Line 319:
 ===== Boot Slackware ARM with QEMU ===== ===== Boot Slackware ARM with QEMU =====
  
-**Work in Progress** +Congratulations for making it this far!  The next step is booting into your fresh installation of Slackware ARM.  Locate the **disk_launch** helper script in /export/armhost and modify it to fit your needs.
- +
-For making it this far, congratulations!  The next step is booting into your fresh installation of Slackwarearm-current.  Locate the **disk_launch** helper script in /export/armhost and modify it to fit your needs.+
  
 <code> <code>
Line 335: Line 333:
   * **NETTYPE** - network configuration, NAT mode or bridged mode   * **NETTYPE** - network configuration, NAT mode or bridged mode
  
-The **disk_launch** script can be found online, [[http://ftp.arm.slackware.com/slackwarearm/boardsupport/qemu/slackwarearm-current/helper-scripts/disk_launch|here]].+The **disk_launch** script for Slackwarearm-current can be found online, [[http://ftp.arm.slackware.com/slackwarearm/boardsupport/qemu/slackwarearm-current/helper-scripts/disk_launch|here]].
  
 The first boot will take quite a while.  This is due to the fact that Slackware will generate the font cache for the first time.  Start up QEMU by executing the disk_launch script. The first boot will take quite a while.  This is due to the fact that Slackware will generate the font cache for the first time.  Start up QEMU by executing the disk_launch script.
Line 343: Line 341:
 </code> </code>
  
 +Assuming all is well, you can begin using Slackware ARM just as you would any other Slackware installation.
 ===== Slackware ARM Graphical User Interface ===== ===== Slackware ARM Graphical User Interface =====
  
 howtos:hardware:arm:qemu_support_in_slackware_arm ()