SliTaz Forum
You are not logged in.
Pages: 1
Booting in frugal install mode (GRUB on USB stick sdb1), after # 15 sec pause after[c]
sd 8:0:0:0: [sdb] Attached SCSI removable disk[/c]
then[c]
init[14106]: segfault at bf11eff0 ip b779b2f7 sp bf11eff4 error 6 in Id-2.14.1so[b7792000+20000]
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 3.2.53-slitaz #4
Call Trace:
[<c140c8ad>] ? panic+0x4d/0x13a
[<c102e66d>] ? do_exit+0x6f/0x5c9
[<c102eddb>] ? do_group_exit+0x5e/0x81
[<c1036360>] ? get_signal_to_deliver+0x3f8/0x414
[<c101bddf>] ? vmalloc_sync_all+0xeb/0xeb
[<c1002624>] ? do_signal+0x2f/0x828
[<c107d2c4>] ? print_vma_addr+0xa7/0xeb
[<c101bddf>] ? vmalloc_sync_all+0xeb/0xeb
[<c140c4a0>] ? bad_area+0x35/0x3a
[<c101bf90>] ? do_page_fault+0x1b1/0x32d
[<c102b6d7>] ? task_stopped_code+0x31/0x31
[<c101bddf>] ? vmalloc_sync_all+0xeb/0xeb
[<c10030da>] ? do_notify_resume+0x1e/0x5c
[<c1413bf4>] ? work_notifysig+0x13/0x1b
[<c1410000>] ? btrfs_log_inode+0x164/0x41b
[<c101bddf>] ? vmalloc_sync_all+0xeb/0xeb[/c]
EDIT : rolling 20140608 works fine
Offline
Downloaded again the ISO and re-installed the 4 rootfs#.gz and the kernel => same
Replaced rootfs4.gz with the one of the rolling 20140608 => works
Offline
I see "Down slitaz-boot-scripts (5.6.1) init fails to boot"
exactly 5.6.2 fixes kernel panic on core single rootfs.gz like in rolling-core.iso
if excess enter-key symbol will be deleted from 5.6.2
Posting twice about it - in my last replies, buy maybe due to my bad english nobody hears
Take a look on this
http://hg.slitaz.org/slitaz-boot-scripts/rev/79aea3c677ca#l1.45
One line deleted - two added
Really line ended by double fork || causes panic
why to touch kernel configs
Offline
Hi az_ua,
Author of these changes (Pascal Bellard) are silent. So, maybe it work for me 
Please, check this commit: http://hg.slitaz.org/slitaz-boot-scripts/rev/3b5dd12d6e46
My skill is not so high in the init scripts.
And wait for new package (5.6.3) in the http://cook.slitaz.org/ (it busy at the moment).
Offline
Problem solved with core-4in1 iso built using earlier build of kernel with init from 5.6.1 slitaz-boot-scripts.
This narrowed it down to kernel config change.
Search linux/stuff/linux-slitaz.config file log.
http://hg.slitaz.org/wok/rev/98da7130169f
Rebuild kernel reverting change.
http://hg.slitaz.org/wok/rev/d9b22c89c185
Tested with core,core-4in1 tazusb install to flash drive.
Add software,
[c]tazusb writefs lzma[/c]
[c]tazlito writeiso lzma[/c]
Both generated iso and new rootfs.gz on flash drive booted to desktop.
Check media locks up syslinux, Check memory doesn't work on tazlito generated iso.
Rolling isos built with changes on mirror.
Offline
Thanks for all your efforts, guys!
The Live-CD made of the latest rolling (2014.06.15-16:26:21) now boots to the desktop without problems, and so do tazlito-generated ISOs. But the CD still remains mounted after booting which causes problems with tazlito and wodim. I also noticed that after pushing the eject button the CD comes out of the drive as expected but the mount command still reports it as mounted ...
/dev/sr0 on /media/cdrom type iso9660 (ro,nosuid,nodev,noexec,relatime,user)
... shouldn't the eject signal trigger a umount before actually ejecting the CD? For the time being I have put a umount in local.sh which solves these problems.
Offline
P.S.: I was wrong in an earlier post a couple of days ago. With today's rolling I noticed that the CD only remains mounted when booted as Live, Core or GTKonly and not when booted as JustX, which means that PCManFM's "auto-mount" default setting is responsible for the mounted CD and the subsequent problems with wodim and tazlito.
Offline
@mojo - great job - you saved my time... I wanted to start to work on it on wednesday......
Offline
@kultex - thank you
@Darjeeling
With these settings live cd is not mounted unless the icon with the cd name in Places sidebar is clicked.
PcmanFM: Edit\Preferences\Volume Management
Uncheck all the boxes, tick "Change folder in the tab to Home Folder"
Click Close button
Disk in optical drive and inserted flash drive are not automounted
They appear as icons in Places sidebar
Click on icon to mount
Click up arrow to umount
There is a context menu to mount/unmount eject
Offline
Thanks Mojo. I've done all that and it works well. But since auto-mount is the default setting in PCManFM it would be good if applications that use wodim were to take care of the umount themselves. A few days ago someone has already put a umount in tazlito. Maybe the same can be done in burn-box, so the convenient PCManFM auto-mount can remain turned on?
Offline
@mojo
PcmanFM: Edit\Preferences\Volume Management
Uncheck all the boxes, tick "Change folder in the tab to Home Folder"
Click Close button
Thanks, now I can mount/unmount disks OK.
Offline
I hope it is possible to disable automount for optical drives only. It may be too much to expect users to open pcmanfm and click on the drive icon to mount removable drives if automount is turned off by default.
Disable automount of optical drive only for user tux:
Add to /etc/fstab: [c]/dev/sr0 /run/media/tux iso9660 user,ro,noauto 0 0[/c]
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]