Re: [lfs-support] Booting into LFS chapter 9.2
On 11/28/12 14:45, Kaleb van Ingen Schenau wrote: Hello, I'm having trouble booting into the new LFS partition (or harddisk in my case). I've set up the GRUB as descriped in the book, the only changes i've put into the grub.cfg is that i had to change the hd0,2 to hd1,1 and i changed the root partition to sdb1 to match my setup up. (ill just list my setup quick) sda1 (linux host OS) sdb1 (/ (this is where i installed all the folders such as ,dev , srv, usr, etc, and the list goes on) sdb2 (my 100mb boot partition) sdb3 (1GB swap) Now i reboot after unmounting $LFS and i get the grub menu as expected and intended. i press enter to start the boot, the comes up with a massive list of things i can only imagine are steps to boot into LFS and it freezes with a error or Kernel panic: [2.396063] No filesystem could mount root, tried: ext3 vfat msdos iso9660 [2.398121] Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (8.17) then i get a litte list of something i cant make head or tails out of and then finishes with atkbd serio0: Sprurious ACK on isa0060/serio0. some program might be trying to acces hardware directly. Any thoughts? regards, Kaleb DId you compile the drivers for the harddrivecontroller into the kernel (not as a module)? Groet, Thomas -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Booting into LFS chapter 9.2
I'm not a 100% sure which drivers i need, luckily i have snapshots before every major step in the book (I'm running LFS on a virtual machine), so i've just gone back to before compiling the kernel and have configured to install all possible harddrive drivers to see how that works out. I must add that im trying to boot off a partition that isn't currently set a a bootable partition in FDISK on the host OS, could this be relevent to the errors I'm getting? On sdb i have a bootable 100mb partition that doesn't contain anything because /boot is set to be mounted with all the other folders in / . It seems to be able to read the grub file as configured in the .cfg but it's just stalling at the mounting of the root partition. I'll let you know if installing extra drivers helped me or has set me back further. regards, Kaleb -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] next step wireless
On Tuesday 27 November 2012 11:09:33 Dave wrote:
I only have WiFi with WEP encryption here, can the WICD pkg and DHCP
alone handle this connect?
Good morning Dave,
Well, as I told you yesterday, yes. From my notes taken during build:
You will need
Wireless Tools, BLFS Book § 15
wpa_supplicant BLFS Book § 15
Supplicant is intended to handle WPA encryptions. However, it
understands
also other protocols, like WEP. See the informations in wikipedia,
https://wiki.archlinux.org/index.php/WPA_supplicant
dhcpcd BLFS Book § 14
Wireless Drivers: depending on your laptop. I have a thinkpad with iwl3945
card. Depending on your kernel, you need to activate the intree driver
directly, in my case iwlwifi, www.intellinuxwireless.org.
Microcode Images. (http://intellinuxwireless.org )
Py2cairo, BLFS Book § 13, needed by PyGTK
PyGObject BLFS Book $ 13
PyGTK, BLFS Book § 13 needed by WICD
You should configure /etc/wpa_supplicant.conf, see wikipedia link above.
network={
ssid=mywireless_ssid
psk=secretpassphrase
# Additional parameters (proto, key_mgmt, etc.)
proto=WEP WPA
}
I wrote a little script wlan0_Home, which I placed in /etc/rc.d/init.d, that
calls supplicant and dhcpcd:
--
# /etc/rc.d/init.d/wlan0_Home
/usr/local/sbin/wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0 -Dwext
/sbin/dhcpcd wlan0
--
and finally, you write the scripts
/etc/sysconfig/ifconfig.wlan0:
---
ONBOOT=no
IFACE=wlan0
SERVICE=dhcpcd
DHCP_START=wlan0 -t 20
DHCP_STOP=-k
and
/etc/sysconfig/network-devices/ifconfig.wlan0/dhclient:
ONBOOT=no
SERVICE=dhclient
DHCP_START=wlan0 -t 20
DHCP_STOP=-k
# Set PRINTIP=yes to have the script print
# the DHCP assigned IP address
PRINTIP=no
# Set PRINTALL=yes to print the DHCP assigned values for
# IP, SM, DG, and 1st NS. This requires PRINTIP=yes.
PRINTALL=no
-
ONBOOT=no is needed to be able to start WICD
The last two scripts taken, slighty modifyed, from the BLFS Book.
I hope these notes will help you in some way to put your wifi connection to
work. The business is not as difficult as it may seem. Good luck !
Edgar
--
Dr.-Ing. Edgar Alwers edgaralw...@gmx.de
GPG Key ID:AD5C6F70
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] (no subject)
thanks for answering. Date: Sat, 24 Nov 2012 20:46:35 + From: zarniwh...@ntlworld.com To: lfs-support@linuxfromscratch.org Subject: Re: [lfs-support] (no subject) On Sat, Nov 24, 2012 at 07:55:17PM +, Tobias Linus Seidler wrote: Hello. I downloaded and decompressed the packages with wget as instructed in the lfs book. Within the host-system and as lfs-user I created and cd-ed into the binutils-build folder and executed the ../binutils-2.22/configure --prefix=/tools --with-sysro command. Then I executed 'make' put terminal reported there was no make file in the current directory. Inspection of the previous commands output told me about some error that a c compiler on the host system was missing: Please advise me. For a C compiler, download one from your host distro. After (or before) that, please look at Host System Requirements in the Preface (page 16 of the PDF). To be honest, if you have no experience of compiling, I don't think you will be ready for LFS. Besides when I copy multiline commands out of your pdf terminal interpretes each single line on its one which of course doesn't work. Can I do something about that? Paste or copy the whole line, ensuring that any '\' is the last character. Most people don't use the PDF, and paste from the html version in their browser to a term. Of course, that does assume you are using a desktop environment which doesn't want to maximize an application to full-screen. I'm also not sure why you would decompress the packages - any adequate version of tar will cope with all the various forms of compression, provided the decompressors have been installed [ see posts from the last 24 hours for which versions of tar are adequate, in the archives if you weren't subscribed ]. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Booting into LFS chapter 9.2
On Wed, Nov 28, 2012 at 03:44:31PM +0100, Kaleb van Ingen Schenau wrote: I'm not a 100% sure which drivers i need, luckily i have snapshots before every major step in the book (I'm running LFS on a virtual machine), so i've just gone back to before compiling the kernel and have configured to install all possible harddrive drivers to see how that works out. This is where LiveCDs (and distro initrds) might be helpful - lsmod on the host system can show which modules are loaded. OTOH, ISTR someone mentioned that knoppix LiveCDs build most things in. I must add that im trying to boot off a partition that isn't currently set a a bootable partition in FDISK on the host OS, could this be relevent to the errors I'm getting? No. Marking a partition as bootable should not be needed in linux. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] next step wireless
On Wed, 28 Nov 2012 16:22:01 +0100
Dr.-Ing. Edgar Alwers edgaralw...@gmx.de wrote:
You should configure /etc/wpa_supplicant.conf, see wikipedia link
above. network={
ssid=mywireless_ssid
psk=secretpassphrase
# Additional parameters (proto, key_mgmt, etc.)
proto=WEP WPA
}
Note that wpa_supplicant can also handle WPA and WPA2 all by itself,
regardless of hardware capabilities.
You can use wpa_gui, present in the wpa_gui directory of wpa_supplicant
to interactively configure the link parameters. Wpa_gui is not built by
default, it requires qt.
--
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] next step wireless
On 11/27/2012 05:15 PM, Dave wrote: Dr.-Ing. Edgar Alwers wrote: On Tuesday 27 November 2012 11:09:33 Dave wrote: I only have WiFi with WEP encryption here, can the WICD pkg and DHCP alone handle this connect? You will need some other packages, like wpa_supplicant, but the answer is yes. It is late here, and I am tired, but I can come back to the issue if you need advice. I am working with WICD and DHCP. If you're just using WEP, then you don't really need anything other than wireless_tools. Of course you also want dhcpcd if you're connecting via dhcp, but that's actually separate from the wireless settings. Just install wireless_tools (see BLFS) and type iwconfig [wlan0] essid [SSIDof_your_router] enc [encryption_key] before bringing up your network connection - and maybe add that to your network startup script. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] next step wireless
On Wednesday 28 November 2012 14:48:05 Chris Staub wrote: If you're just using WEP, then you don't really need anything other than wireless_tools. Of course you also want dhcpcd if you're connecting via dhcp, but that's actually separate from the wireless settings. Just install wireless_tools (see BLFS) and type iwconfig [wlan0] essid [SSIDof_your_router] enc [encryption_key] before bringing up your network connection - and maybe add that to your network startup script. I am using wpa, so I was generalising wep and wpa, that is the reason for supplicant. You are right, your instructions are OK for a communication. However, Dave wanted to use WICD, what gives more elasticity in running in different places with different encryptions. I hope, I am not wrong. To my experience, WICD is a great tool. Edgar -- Dr.-Ing. Edgar Alwers edgaralw...@gmx.de GPG Key ID:AD5C6F70 -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
