| View previous topic :: View next topic |
| Author |
Message |
rush_ad
l33t
Joined: 22 Jul 2004
Posts: 863
Location: New Jersey, USA
|
 Posted: Tue Jun 14, 2005 1:57 am Post subject: |
 |
|
| RoadRunn wrote: | | rush_ad wrote: | | only problem now is that i cannot test 64-bit iso in vmware. i tried many 64-bit ditro iso in vmware but it only boots 32-bit distros. so i guess i'm back to wasting CDs. |
I played around with qemu today. From their docs they say they can emulate x64. And it does boot from ISO's. I'm upgrading to the 0.70 version now and see what's up |
this is what i found
"Current QEMU limitations:
* No SSE/MMX support (yet).
* No x86-64 support.
* IPC syscalls are missing.
* The x86 segment limits and access rights are not tested at every memory access (yet). Hopefully, very few OSes seem to rely on that for normal use.
* On non x86 host CPUs, doubles are used instead of the non standard 10 byte long doubles of x86 for floating point emulation to get maximum performances. " |
|
| Back to top |
|
 |
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Tue Jun 14, 2005 2:04 am Post subject: |
|
|
| rush_ad wrote: | | RoadRunn wrote: | | rush_ad wrote: | | only problem now is that i cannot test 64-bit iso in vmware. i tried many 64-bit ditro iso in vmware but it only boots 32-bit distros. so i guess i'm back to wasting CDs. |
I played around with qemu today. From their docs they say they can emulate x64. And it does boot from ISO's. I'm upgrading to the 0.70 version now and see what's up |
this is what i found
"Current QEMU limitations:
* No SSE/MMX support (yet).
* No x86-64 support.
* IPC syscalls are missing.
* The x86 segment limits and access rights are not tested at every memory access (yet). Hopefully, very few OSes seem to rely on that for normal use.
* On non x86 host CPUs, doubles are used instead of the non standard 10 byte long doubles of x86 for floating point emulation to get maximum performances. " |
I guess we have conflicting information....
http://fabrice.bellard.free.fr/qemu/status.html
System emulation is there...not sure what the difference is between system and user emu |
|
| Back to top |
|
|
rush_ad
l33t
Joined: 22 Jul 2004
Posts: 863
Location: New Jersey, USA
|
| Posted: Tue Jun 14, 2005 2:08 am Post subject: |
|
|
| i guess i dont know how to interprete information given. but now that i see 64-bit is supported, i have to find out how to test iso using qemu |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Tue Jun 14, 2005 2:32 am Post subject: |
|
|
| rush_ad wrote: | | i guess i dont know how to interprete information given. but now that i see 64-bit is supported, i have to find out how to test iso using qemu |
Well i am booting off the x64 minimal livecd (stock gentoo). It's booting but slow. As soon as it comes up i'll see if it's running a 64 bit kernel....
first run 'qemu-img test.img 1G' this creates a 1GB "hard drive" named test.img
then run 'qemu-system-x86_64 -cdrom livecd.iso -boot d test.img' this will boot the emulator, using livecd.iso as the cdrom and trying to boot off that cdrom before the hard drive. |
|
| Back to top |
|
|
rush_ad
l33t
Joined: 22 Jul 2004
Posts: 863
Location: New Jersey, USA
|
| Posted: Tue Jun 14, 2005 2:36 am Post subject: |
|
|
| alright. thanks. i will try that out once i finish making amd64 live cd. |
|
| Back to top |
|
|
rush_ad
l33t
Joined: 22 Jul 2004
Posts: 863
Location: New Jersey, USA
|
| Posted: Tue Jun 14, 2005 3:31 am Post subject: |
|
|
| Quote: | first run 'qemu-img test.img 1G' this creates a 1GB "hard drive" named test.img
then run 'qemu-system-x86_64 -cdrom livecd.iso -boot d test.img' this will boot the emulator, using livecd.iso as the cdrom and trying to boot off that cdrom before the hard drive. |
nop not working. qemu-system-x86_64, no commnad found. seems like doesnt work on amd64. what you found probably means that you can try out 64-bit iso on a 32-bit host system, i think. |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Tue Jun 14, 2005 3:52 am Post subject: |
|
|
| rush_ad wrote: | | Quote: | first run 'qemu-img test.img 1G' this creates a 1GB "hard drive" named test.img
then run 'qemu-system-x86_64 -cdrom livecd.iso -boot d test.img' this will boot the emulator, using livecd.iso as the cdrom and trying to boot off that cdrom before the hard drive. |
nop not working. qemu-system-x86_64, no commnad found. seems like doesnt work on amd64. what you found probably means that you can try out 64-bit iso on a 32-bit host system, i think. |
Are you using qemu 0.70? It's marked as unstable (USE="~x86"). 0.61 is the latest stable and does not have x86_64. |
|
| Back to top |
|
|
rush_ad
l33t
Joined: 22 Jul 2004
Posts: 863
Location: New Jersey, USA
|
| Posted: Tue Jun 14, 2005 11:34 am Post subject: |
|
|
i'm going to be out for a week or so. cant get anything done over this time.
last time i booted my cd i got kernel panic of some sort. not sure what it meant. i will post everything once i come back. |
|
| Back to top |
|
|
echo6
Guru
Joined: 04 Jan 2003
Posts: 587
|
| Posted: Tue Jun 14, 2005 6:15 pm Post subject: |
|
|
| rush_ad wrote: | | only problem now is that i cannot test 64-bit iso in vmware. i tried many 64-bit ditro iso in vmware but it only boots 32-bit distros. so i guess i'm back to wasting CDs. |
VMWare should emulate its host, at least the latest versions do! I think from v4 4558 IIRC. |
|
| Back to top |
|
|
echo6
Guru
Joined: 04 Jan 2003
Posts: 587
|
| Posted: Tue Jun 14, 2005 6:17 pm Post subject: |
|
|
| RoadRunn wrote: | | echo6 wrote: | | Is this grub error normal? |
Nope that shouldn't happen. Try to emerge grub and see what errors it comes with. That command was just 'emerge grub > /dev/null' so try an emerge -av grub and see if it still bombs. |
That worked, no errors!! |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Tue Jun 14, 2005 6:25 pm Post subject: |
|
|
| echo6 wrote: | | RoadRunn wrote: | | echo6 wrote: | | Is this grub error normal? |
Nope that shouldn't happen. Try to emerge grub and see what errors it comes with. That command was just 'emerge grub > /dev/null' so try an emerge -av grub and see if it still bombs. |
That worked, no errors!! |
Hmm. don't know why it bombed durring install. At least it's installed now. |
|
| Back to top |
|
|
echo6
Guru
Joined: 04 Jan 2003
Posts: 587
|
| Posted: Tue Jun 14, 2005 9:02 pm Post subject: |
|
|
| RoadRunn wrote: | | Hmm. don't know why it bombed durring install. At least it's installed now. |
Anyway the script can redirect errors to a log so it can be checked..seems strange. |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Tue Jun 14, 2005 9:22 pm Post subject: |
|
|
| echo6 wrote: | | RoadRunn wrote: | | Hmm. don't know why it bombed durring install. At least it's installed now. |
Anyway the script can redirect errors to a log so it can be checked..seems strange. |
Well i was wanting to keep the screen clean that's why i was redirecting a few things to /dev/null. I guess i could redirect everything to a log file so fi there was a problem we can go back to the log. |
|
| Back to top |
|
|
echo6
Guru
Joined: 04 Jan 2003
Posts: 587
|
| Posted: Wed Jun 15, 2005 6:25 am Post subject: |
|
|
Another useful utility is eix, makes searching the portage database more efficient.
Also, there is a way to startx in a chroot environment but I can't quite recall how, any ideas? |
|
| Back to top |
|
|
bebebebeben
n00b
Joined: 26 May 2005
Posts: 5
|
| Posted: Wed Jun 15, 2005 3:40 pm Post subject: |
|
|
anyone can give out a link for the iso of this cd.. any kind of link
a torrent is is also ok cuz I cant go into the tracker site and start a download there? |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Wed Jun 15, 2005 4:45 pm Post subject: |
|
|
| bebebebeben wrote: | anyone can give out a link for the iso of this cd.. any kind of link
a torrent is is also ok cuz I cant go into the tracker site and start a download there? |
If you are talking about my ISO you can grap the torrent at http://tracker.roadrunn.com Right now it looks as if my server is the only seeder so might be a bit slow but it's there. My cable connection was down earlier but it is back up now. |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Wed Jun 15, 2005 4:46 pm Post subject: |
|
|
| echo6 wrote: | Another useful utility is eix, makes searching the portage database more efficient.
Also, there is a way to startx in a chroot environment but I can't quite recall how, any ideas? |
Well if you are chroot'ed then all X links should also point inside the chroot environment. I have always built my livecd's via SSH so starting X was not something I thought about trying. |
|
| Back to top |
|
|
echo6
Guru
Joined: 04 Jan 2003
Posts: 587
|
| Posted: Wed Jun 15, 2005 6:47 pm Post subject: |
|
|
Speaking of ssh  Likewise I do many of my Gentoo installs over ssh. I haven't had time to get around your scripts yet so I'm not sure how I can resume the remaster process from another shell session. I'm thinking of using the screen app which allows you to detach the shell session login from another shell and resume it..IYSWIM!? In any case, some good clear step by step guides on using the scripts would be useful, and possibly also a guide to installing a base system i.e. which emerges are required. Of course for a base system you need to consider which packages constitute a base system. In either case perhaps a further script or config file which contains the base system might be useful, allowing the user to add and edit what they require. |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Wed Jun 15, 2005 7:02 pm Post subject: |
|
|
| echo6 wrote: | | Speaking of ssh Likewise I do many of my Gentoo installs over ssh. I haven't had time to get around your scripts yet so I'm not sure how I can resume the remaster process from another shell session. I'm thinking of using the screen app which allows you to detach the shell session login from another shell and resume it..IYSWIM!? In any case, some good clear step by step guides on using the scripts would be useful, and possibly also a guide to installing a base system i.e. which emerges are required. Of course for a base system you need to consider which packages constitute a base system. In either case perhaps a further script or config file which contains the base system might be useful, allowing the user to add and edit what they require. |
Yes I do most of my stuff in a screen session when I know it will take longer than what I want (depending on what kind of mood I am in). For instance my seeding for the livecd iso is done inside a screen session, so I can reconnect to it and see what the current bandwidth is. I use it as follows:
screen -S <name> - create screen session with <name>
screen -ls - list all known screen sessions and their state
screen -x <name> - reconnect to a screen session named <name>
I hav scripted as much as possible in my scripts. I stopped where I though a package was "optional" based on what kind of LiceCD you were building. If there are other packages that are required for ANY livecd I'll surly add them, but I don't want to fice someone into a package unless it is required. CD/ISO size is still first priority. |
|
| Back to top |
|
|
thomasa88
Tux's lil' helper
Joined: 13 Apr 2005
Posts: 143
Location: Sweden
|
| Posted: Thu Jun 16, 2005 8:41 am Post subject: |
|
|
how do I get the X-env to autologin?
_________________
- thomasa88 |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Thu Jun 16, 2005 1:20 pm Post subject: |
|
|
| thomasa88 wrote: | | how do I get the X-env to autologin? |
You can add xdm to the default runlevel. Then modify rc.conf to use gdm as your display manager. And finally in /etc/X11/gdm/gdm.conf modify the following lines:
| Code: |
[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=true
AutomaticLogin=<username>
|
FYI, I was never able to get root ro autologin to gdm. I'm pretty sure that's a security feature that I never looked into getting around. |
|
| Back to top |
|
|
thomasa88
Tux's lil' helper
Joined: 13 Apr 2005
Posts: 143
Location: Sweden
|
| Posted: Thu Jun 16, 2005 1:57 pm Post subject: |
|
|
thx, but I should have mentioned I wanted it for kdm (dont want whole gnome:P)
but after some searching I found
| Code: |
/usr/kde/3.4/share/config/kdm/kdmrc
|
and then edit from line 532
| Code: |
# Core config for 1st local display
[X-:0-Core]
# The VT the X-server should run on. Better use ServerVTs.
# Default is 0
#ServerVT=7
# Enable automatic login. USE WITH EXTREME CARE!
# Default is false
AutoLoginEnable=true
# The user to log in automatically. NEVER specify root!
# Default is ""
AutoLoginUser=thotoo
# The password for the user to log in automatically. This is NOT required
# unless the user is logged into a NIS or Kerberos domain. If you use this
# option, you should "chmod 600 kdmrc" for obvious reasons.
# Default is ""
#AutoLoginPass=secret!
|
_________________
- thomasa88 |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Thu Jun 16, 2005 2:46 pm Post subject: |
|
|
| thomasa88 wrote: | thx, but I should have mentioned I wanted it for kdm (dont want whole gnome:P)
but after some searching I found
| Code: |
/usr/kde/3.4/share/config/kdm/kdmrc
|
and then edit from line 532
| Code: |
# Core config for 1st local display
[X-:0-Core]
# The VT the X-server should run on. Better use ServerVTs.
# Default is 0
#ServerVT=7
# Enable automatic login. USE WITH EXTREME CARE!
# Default is false
AutoLoginEnable=true
# The user to log in automatically. NEVER specify root!
# Default is ""
AutoLoginUser=thotoo
# The password for the user to log in automatically. This is NOT required
# unless the user is logged into a NIS or Kerberos domain. If you use this
# option, you should "chmod 600 kdmrc" for obvious reasons.
# Default is ""
#AutoLoginPass=secret!
|
|
Kewl, glad you found it. I was all KDE while gnome was it it's 2.4-2.6 stage. Since it went 2.8 and now 2.10 IMHO it is better in resource management/usage than the last time I played with KDE. |
|
| Back to top |
|
|
Match
Tux's lil' helper
Joined: 22 Mar 2004
Posts: 117
Location: England
|
| Posted: Thu Jun 16, 2005 8:36 pm Post subject: |
|
|
Hi there,
First off, thanks so much for the hard work you've put into this. Hearing how you've gone about setting things up inspired me to create my own LiveCD. I've got so far - GRUB works, everything boots all fine until I get these lines:
| Code: | VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 232k freed
Kernel panic - not syncing: no init found. Try passing init=option to kernel |
My GRUB config file is identical to yours, minus the video parameter. The only thing I can think of is that linuxrc contains a line that makes reference to /sbin/init - but there isn't an sbin directory on the LiveCD. Any ideas what the problem could be?
_________________
O_o |
|
| Back to top |
|
|
RoadRunn
Apprentice
Joined: 10 Jun 2004
Posts: 162
|
| Posted: Thu Jun 16, 2005 9:27 pm Post subject: |
|
|
| Match wrote: | Hi there,
First off, thanks so much for the hard work you've put into this. Hearing how you've gone about setting things up inspired me to create my own LiveCD. I've got so far - GRUB works, everything boots all fine until I get these lines:
| Code: | VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 232k freed
Kernel panic - not syncing: no init found. Try passing init=option to kernel |
My GRUB config file is identical to yours, minus the video parameter. The only thing I can think of is that linuxrc contains a line that makes reference to /sbin/init - but there isn't an sbin directory on the LiveCD. Any ideas what the problem could be? |
I'm thinking that the initrd is not there or missing a few things. Also if the kernel config does not contain support for squashfs, tmpfs, ram device, and ide-cdrom support, the linuxrc script will bail. The first thing I do when grub boots but the kernel can finish is the following:
Print out the linuxrc script of possible or some way that you can refer to it.
When you get the grub menu, edit the line so that the only thing in the kernel line that will be executed is:
| Code: | | kernel (cd)/boot/vmlinuz root=/dev/ram0 |
That will load the kernel and dump you to an sh prompt.
Then you can execute line by line what is in the linuxrc file (without the > /dev/null) to see which step is failing. If you know which device your cdrom is, you can skip all the begining stuff, mount your cdrom device to /cdrom, and start with all the other mount commands in linuxrc. |
|
| Back to top |
|
|
|
Unsupported Software
