larch-7 testing

gradgrind · 2009-12-08 14:16:07

I've uploaded a new larch package, with some quite radical internal changes. The design should be nearly complete now, it needs testing though (please read the Quick Start documentation, this has changed). Feedback welcome.

ammon · 2009-12-14 23:47:29

Could you post larch7-testing pkgbuild in AUR?
More people will test it that way.

gradgrind · 2009-12-15 08:44:48

I'm afraid that my PKGBUILDs are rather non-standard at the moment, so they can't be put in AUR so easily. I'll put it on my TODO list.

farvardin · 2009-12-15 20:50:26

It's working better than before, it could begin to build the image (I"m using latest larch from the repos).

But at the end:

#Testing for necessary packages and kernel modules
#Beginning to build larch medium files
>rm -rf /.larch/cd && mkdir -p /.larch/cd/{boot,larch}
@0
>cp -f /boot/vmlinuz26 /.larch/cd/boot/larch.kernel
@0
>echo 'vmlinuz26' > /.larch/cd/larch/kernelname
@0
#Generating system.sqf
>/sbin/mksquashfs '/' '/.larch/system.sqf' -e boot dev mnt media proc sys tmp .livesys .larch var/log var/tmp var/lock var/cache/pacman/pkg usr/lib/locale
:-Parallel mksquashfs: Using 1 processor
:-Creating 4.0 filesystem on /.larch/system.sqf, block size 131072.
:-Cannot stat dir/file //home/esclinux/.gvfs because Permission denied, ignoring
:-Exportable Squashfs 4.0 filesystem, data block size 131072
:-compressed data, compressed metadata, compressed fragments
:-duplicates are removed
:-Filesystem size 693984.45 Kbytes (677.72 Mbytes)
:-Inode table size 1311827 bytes (1281.08 Kbytes)
:-Directory table size 1372525 bytes (1340.36 Kbytes)
:-Number of duplicate files found 12283
:-Number of inodes 137236
:-Number of files 108667
:-Number of fragments 7122
:-Number of symbolic links  14539
:-Number of device nodes 8
:-Number of fifo nodes 0
:-Number of socket nodes 2
:-Number of directories 14020
:-Number of ids (unique uids + gids) 17
:-Number of uids 9
:-root (0)
:-esclinux (1003)
:-vboxadd (121)
:-policykit (102)
:-dbus (81)
:-unknown (1000)
:-hal (82)
:-gdm (120)
:-nobody (99)
:-Number of gids 13
:-root (0)
:-users (100)
:-disk (6)
:-ftp (11)
:-bin (1)
:-locate (21)
:-tty (5)
:-policykit (102)
:-dbus (81)
:-games (50)
:-unknown (1000)
:-hal (82)
:-gdm (101)
@0
>chmod oga-x /.larch/system.sqf
@0
>mv /.larch/system.sqf /.larch/cd/larch
@0
#Generating larch overlay
>cp /etc/inittab /.larch/tmp/overlay/etc/inittab.larchsave
:-cp: cannot create regular file `/.larch/tmp/overlay/etc/inittab.larchsave': No such file or directory
@1
>cp /etc/inittab/etc/inittab /.larch/tmp/overlay/etc/inittab/etc
:-cp: cannot stat `/etc/inittab/etc/inittab': Not a directory
@1
>sed -i 's|/etc/rc.sysinit|/etc/rc.larch.sysinit|' /.larch/tmp/overlay/etc/inittab
:-sed: can't read /.larch/tmp/overlay/etc/inittab: No such file or directory
@2
>sed -i 's|/etc/rc.shutdown|/etc/rc.larch.shutdown|' /.larch/tmp/overlay/etc/inittab
:-sed: can't read /.larch/tmp/overlay/etc/inittab: No such file or directory
@2
#Generating larch initcpio
>sed 's|___aufs___|_aufs|g' </etc/mkinitcpio.conf.larch0 >/.larch/tmp/overlay/etc/mkinitcpio.conf.larch
:-bash: /.larch/tmp/overlay/etc/mkinitcpio.conf.larch: No such file or directory
@1
>mkdir -p /.larch/tmp/overlay/etc/mkinitcpio.d
@0
>cp /etc/mkinitcpio.d/kernel26.preset /.larch/tmp/overlay/etc/mkinitcpio.d/kernel26.preset.larchsave
@0
>sed 's|___|kernel26|' </etc/mkinitcpio.d/larch.preset0 >/.larch/tmp/overlay/etc/mkinitcpio.d/larch.preset
@0
>cp /.larch/tmp/overlay/etc/mkinitcpio.d/larch.preset /.larch/tmp/overlay/etc/mkinitcpio.d/kernel26.preset
@0
>mkinitcpio -k 2.6.31-ARCH -c /.larch/tmp/overlay/etc/mkinitcpio.conf.larch -g /.larch/cd/boot/larch.img
:-config file '/.larch/tmp/overlay/etc/mkinitcpio.conf.larch' cannot be found, aborting...
@1

In the manual it just said to point the installation folder to /, I don't want any preset or profile, I just want to build a live cd from a current installation.

Last edited by farvardin (2009-12-15 20:56:16)

gradgrind · 2009-12-16 13:25:30

I'll have a look at that - thanks for the report.

gradgrind · 2009-12-17 09:37:26

I hope, farvardin, larch-7.0.107, which I've just uploaded, will fix this.

ig0r · 2009-12-18 19:59:09

Hello, I have packages which provide kernel modules, and when larchify I recive next message
"WARNING:
You seem to have installed a package containing modules
which aren't compatible with your kernel (see log).
Please check that this won't cause problems.
Maybe you need the corresponding package for your kernel?
Continue building?"

and when I press Ok larch is exit.

farvardin · 2009-12-19 10:32:02

I have this message too, but it doesn't prevent larch to continue. I have both 2.6.29 and 2.6.31 modules, I don't know why and I'm not sure if it's safe to delete the /lib/modules/2.6.29-ARCH folder: (I suppose it is, but I wonder why it's still there)

ls /lib/modules/
2.6.29-ARCH 2.6.31-ARCH

Now the generation of the image is going to the end but it doesn't create the iso file. When I switch to the "prepare medium" tab, it's crashing, saying "Unknown widget: :nodevice". (I don't have any cdrom into my drive, I run it from a virtual machine in virtualbox and I just want an iso), and "Bad gui command line:
!:nodevice.set [true]" before exiting larch. (I can't select the other tab)

the console give me this result after the crash:
GUI: Traceback (most recent call last):
File "/usr/bin/quip", line 981, in new_line
self._methodcall(line[1:])
File "/usr/bin/quip", line 1041, in _methodcall
cmd = getattr(wo, m)
AttributeError: 'NoneType' object has no attribute 'set'

Here is the complete log of the process:
http://pastebin.archlinux.fr/371523

Is it possible to create an iso from the command line? In the larch 7 docs there is a reference to a "create-iso" script, but I can't find it.
Here is what I got from the larchify generation:

ls -alh /.larch/cd/larch/
total 696M
drwxr-xr-x 2 root root 4.0K Dec 23 17:36 .
drwxr-xr-x 3 root root 4.0K Dec 23 17:36 ..
-rw-r--r-- 1 root root 10 Dec 23 16:58 kernelname
-rw------- 1 root root 604K Dec 23 17:36 mods.sqf
-rw------- 1 root root 695M Dec 23 17:30 system.sqf

ls -alh /.larch/tmp/boot/
total 5.6M
drwxr-xr-x 2 root root 4.0K Dec 23 17:35 .
drwxr-xr-x 3 root root 4.0K Dec 23 17:36 ..
-rw-r--r-- 1 root root 3.8M Dec 23 17:36 larch.img
-rw-r--r-- 1 root root 1.8M Dec 23 16:58 larch.kernel

Last edited by farvardin (2009-12-19 10:34:29)

gradgrind · 2009-12-19 19:16:44

Hi farvardin,

You can safely remove the old kernel modules - they are from virtualbox. As to the crash, that is really strange. I can't find any trace of ':nodevice' in the source code - are you really using the latest larch and uipi (and not something you perhaps installed earlier)?

It should be possible to produce an iso from the command line: see http://larch.berlios.de/doc7/larch_console.html.

Hi ig0r,
Without some sort of error message it's difficult to trace the problem. If you didn't run larch from a terminal, you could try that.

ig0r · 2009-12-20 08:40:05

gradgrind wrote:

Hi ig0r,
Without some sort of error message it's difficult to trace the problem. If you didn't run larch from a terminal, you could try that.

I have no message in terminal, but after messaage "Continue building?" I recive "Couldn't find kernel modules", I found in sources my error.

/opt/apps/larch/modules/build.py
301: if not ui.confirmDialog(_("WARNING:\n"
302: " You seem to have installed a package containing modules\n"
303: "which aren't compatible with your kernel (see log).\n"
304: "Please check that this won't cause problems.\n"
305: "Maybe you need the corresponding package for your kernel?\n"
306: "\n Continue building?")):
307: return False
308:
309: if not self.kversion:
310: fatal_error(_("Couldn't find kernel modules"))
311: return False

gradgrind · 2009-12-20 09:39:58

Hi ig0r,

I think you'll need to tidy up your /lib/modules directory so that only modules for the installed kernel are present - and ensure you only have one kernel installed.

ig0r · 2009-12-20 15:33:17

gradgrind wrote:

Hi ig0r,
I think you'll need to tidy up your /lib/modules directory so that only modules for the installed kernel are present - and ensure you only have one kernel installed.

I have one kernel, but I have not "lib/modules/%s/build" % kv (line 273 of /opt/apps/larch/modules/build.py), and self.kversion = None (as defined at line 271 of /opt/apps/larch/modules/build.py)
====
% sudo chroot /home/larchbuild/
# ls /lib/modules
2.6.32-ARCH
# ls /lib/modules/2.6.32-ARCH
kernel modules.alias.bin modules.dep modules.ieee1394map modules.isapnpmap modules.order modules.seriomap modules.symbols.bin updates
modules.alias modules.ccwmap modules.dep.bin modules.inputmap modules.ofmap modules.pcimap modules.symbols modules.usbmap
====

Last edited by ig0r (2009-12-20 18:52:13)

firecat53 · 2009-12-20 20:24:18

Thanks for the great work! Couple of questions/requests:

1. On x86_64, even when I select the archtitecture type to i686, it still downloads x86_64 packages. I actually created a new mirrorlist in a different location so I wouldn't forget to change my regular mirrorlist back to x86_64 and accidentally bork my system It'd be nice to have a way to automatically handle this for cross-architecture builds.

2. How can you turn off the auto-login feature and just go back to the regular virtual terminal username and password login?

3. I have a 4GB partition I'm using for larch, and df -h shows:
Filesystem Size Used Avail Use% Mounted on
aufs 1.2G 1.1G 133M 90% /
tmpfs 1.2G 1.1G 133M 90% /.livesys
/dev/sdb2 4.5G 1.5G 2.8G 35% /.livesys/medium
none 1012M 204k 1012M 1% /dev
none 1012M 0 1012M 0% /dev/shm

How can I get more of that free 2.8G available for /home and /var?

Thanks!
Scott

Last edited by firecat53 (2009-12-20 20:24:29)

farvardin · 2009-12-21 00:52:19

I'm using the official larch repo, so larch and uipi are up to date (I'm using larch-7.0.107)
I'll try again, maybe with a blank cdrom in my drive.

I found the "create-iso" script, which wasn't in the path. I couldn't use my .img files for using with it, so I'll try soon to generate the whole thing again.

gradgrind · 2009-12-21 08:57:55

ig0r:

That may be a change in kernel 2.6.32 - you might need to install kernel26-headers.

firecat53:

1) I'll think about that - it's difficult for me to work on an x86_64 version because I'm not running it.

2) That's all in the profile. You could possibly delete the whole rootoverlay directory - it depends what you want to achieve. Have a look in there, especially root/.bash_profile and etc/inittab.

3) larch runs in tmpfs. If you want to use the boot medium to store data you need to remount it 'rw' (the default is 'ro') and perhaps use symlinks from var and home.

farvardin:

Good luck!

Skullcrasher · 2009-12-22 19:12:06

I guess I just found the tool, what I was looking for. But as I know it is only usable for building i686 systems.
I would need a x64 version, so is there still one or still in planning? Or is it possible to use the i686 to make a install cd with x64 packages etc.?

Cheers Skullcrasher

gradgrind · 2009-12-26 10:19:00

It should be possible to use it on a 64-bit system, but it will need a few tweaks. The packages themselves are no problem as they are all 'any' architecture at present, but some of the paths (repositories, etc) may need adjusting. If you are using the larch-setup script you can change these lines at the beginning:

-------------------------------------------
sysarch="$( uname -m )"
if [ "${sysarch}" != "x86_64" ]; then
sysarch="i686"
fi
-------------------------------------------

to

-------------------------------------------
sysarch="i686"
-------------------------------------------

(that is correct, I haven't set up a specifically x86_64 repository).

Sharn · 2009-12-26 20:49:52

Hey gradgrind - having a small issue with larch-7. I've gotten all the way to Prepare Medium, but when I try to "Choose" a partition, it shows only "None" - there are no partitions listed. I'm trying to install to a new USB drive, recognised as /dev/sdc.

THIRD EDIT:
Totally repartitioned the drive and now it appears to be working, so feel free to skip reading the rest of this post

SECOND EDIT:
Nevermind, removed the drive and put it back and larch recognised it this time. However, now I get:

:-Warning: given size (1016) exceeds max allowable size (1015)
:-
:-sfdisk: bad input

^^^ from the log. Going to try reformatting the drive..

EDIT: in the log it shows this several time (for every time I've clicked Choose, I'm sure):

>sfdisk -uM -l
:-
:-Disk /dev/sda: 4998 cylinders, 255 heads, 63 sectors/track
:-Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
:-
:-Device Boot Start   End    MiB    #blocks   Id  System
:-/dev/sda1   *     0+   101-   102-    104422   83  Linux
:-/dev/sda2       101+   360-   259-    265072+  82  Linux swap / Solaris
:-/dev/sda3       360+ 39205- 38845-  39776940   83  Linux
:-/dev/sda4         0      -      0          0    0  Empty
:-
:-Disk /dev/sdb: 30515 cylinders, 255 heads, 63 sectors/track
:-Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
:-
:-Device Boot Start   End    MiB    #blocks   Id  System
:-/dev/sdb1         0+ 239366- 239367- 245111706   83  Linux
:-/dev/sdb2         0      -      0          0    0  Empty
:-/dev/sdb3         0      -      0          0    0  Empty
:-/dev/sdb4         0      -      0          0    0  Empty
@0

Last edited by Sharn (2009-12-26 21:06:42)

firecat53 · 2009-12-30 03:04:31

Has anyone had any luck getting intel (i915) KMS modesetting to work in a larch install? I just created a larch install from scratch with the new 2.6.32 kernel in core, and although the news says that intel KMS is enabled by default, I can't get it to work either by doing nothing (is it default?) or by adding i915.modeset=1 to the grub boot line. Is there anything different about the way that larch boots up that changes how we enable KMS?

THanks!
Scott

gradgrind · 2009-12-30 11:37:42

I can't think of anything that could be different. I've done most of the testing in virtualbox so I wouldn't normally notice any KMS problems. Does this work in a non-larch system? Can anyone else confirm this?

farvardin · 2009-12-30 13:34:00

I got the same error as ig0r, and tried several time until I re-read this thread. Maybe the error message is not clean enough : "Couldn't find kernel modules" and could say "Couldn't find kernel modules and / or headers", or even "... have you installed the latest kernel26-headers" ? Strange enough it was working in the previous kernel version, so I suppose it was already installed for the previous one but not automatically upgraded?

But for now... It's working again for larchify, I could generate a working .iso ! Thank you for your support Gradgrind!

Btw I tried again with a blank cdrom in my real drive (I'm doing all stuffs from virtualbox), and this time the "prepare medium" tab didn't crash. If I remove it, when starting larch this operation is not possible (crash), so I think it's a bug because I didn't mean to write it to a cdrom, just to create an iso on my system. If I try with a virtual cdrom, it crashes as well.

firecat53 · 2009-12-31 06:59:29

Well, I got a normal hard drive install with an intel 82854 graphic card to boot with 'late start' KMS by default, with the stock kernel and driver from the repo (early start wouldn't work). Neither the install on the flash drive, with the same kernel/driver, or the larch install will use KMS at all (early or late). Weird. I don't know enough about the boot sequence to know if booting from a flash drive would affect the setting of KMS somehow. Any ideas?

Scott

gradgrind · 2009-12-31 16:03:44

farvardin wrote:

I got the same error as ig0r, and tried several time until I re-read this thread. Maybe the error message is not clean enough : "Couldn't find kernel modules" and could say "Couldn't find kernel modules and / or headers", or even "... have you installed the latest kernel26-headers" ? Strange enough it was working in the previous kernel version, so I suppose it was already installed for the previous one but not automatically upgraded?

The reason for this is that the kernel packaging has changed with 2.6.32. larch uses something that is now no longer present in the kernel package to detect the installed kernel. The message was reasonable until this change. When I have a bit of time I'll change the way larch handles this so that it is no longer necessary to install the headers package.

farvardin wrote:

Btw I tried again with a blank cdrom in my real drive (I'm doing all stuffs from virtualbox), and this time the "prepare medium" tab didn't crash. If I remove it, when starting larch this operation is not possible (crash), so I think it's a bug because I didn't mean to write it to a cdrom, just to create an iso on my system. If I try with a virtual cdrom, it crashes as well.

This is very strange - larch shouldn't care whether a cdrom is present or not. Is anyone else getting this behaviour?

gradgrind · 2009-12-31 16:08:03

firecat53 wrote:

Well, I got a normal hard drive install with an intel 82854 graphic card to boot with 'late start' KMS by default, with the stock kernel and driver from the repo (early start wouldn't work). Neither the install on the flash drive, with the same kernel/driver, or the larch install will use KMS at all (early or late). Weird. I don't know enough about the boot sequence to know if booting from a flash drive would affect the setting of KMS somehow. Any ideas?
Scott

Maybe you should post on the mailing list or somewhere more appropriate on the forum, as this seems not directly larch related - you might get more feedback.

firecat53 · 2009-12-31 17:31:42

That's what I was starting to think, too -- didn't want to double post until I was sure no one else was having the problem with larch. THanks

Scott

Arch Linux

#51 2009-12-08 14:16:07

Re: larch-7 testing

#52 2009-12-14 23:47:29

Re: larch-7 testing

#53 2009-12-15 08:44:48

Re: larch-7 testing

#54 2009-12-15 20:50:26

Re: larch-7 testing

#55 2009-12-16 13:25:30

Re: larch-7 testing

#56 2009-12-17 09:37:26

Re: larch-7 testing

#57 2009-12-18 19:59:09

Re: larch-7 testing

#58 2009-12-19 10:32:02

Re: larch-7 testing

#59 2009-12-19 19:16:44

Re: larch-7 testing

#60 2009-12-20 08:40:05

Re: larch-7 testing

#61 2009-12-20 09:39:58

Re: larch-7 testing

#62 2009-12-20 15:33:17

Re: larch-7 testing

#63 2009-12-20 20:24:18

Re: larch-7 testing

#64 2009-12-21 00:52:19

Re: larch-7 testing

#65 2009-12-21 08:57:55

Re: larch-7 testing

#66 2009-12-22 19:12:06

Re: larch-7 testing

#67 2009-12-26 10:19:00

Re: larch-7 testing

#68 2009-12-26 20:49:52

Re: larch-7 testing

#69 2009-12-30 03:04:31

Re: larch-7 testing

#70 2009-12-30 11:37:42

Re: larch-7 testing

#71 2009-12-30 13:34:00

Re: larch-7 testing

#72 2009-12-31 06:59:29

Re: larch-7 testing

#73 2009-12-31 16:03:44

Re: larch-7 testing

#74 2009-12-31 16:08:03

Re: larch-7 testing

#75 2009-12-31 17:31:42

Re: larch-7 testing

Board footer