@kultex
here it is
(pure iso, usb-flash-boot, live mode)

SliTaz Cooking 20140216
(48 posts) (15 voices)-
Posted 11 years ago #
-
regarding the agpgart_sis module
if you look in lsmod - it seems that the module in agpgart is renamed to sis_agp
check how it is called in 4.0
if it is like this, this has to be changed in tazhw
and regarding to your harddisk - it may be a problem of new kernel
I need also dmesg and lsmod from 4.0 and lspci
but I have no time before the weekend to deal with it
Posted 11 years ago # -
@kultex
here they are
note:I'm booting Sz4 from a customized live-Cd, my internal Hdd is only
storage.(ext2).Posted 11 years ago # -
ok - the sis-ide drivers are not in the kernel - we have to add
CONFIG_BLK_DEV_SIS5513=m
I will check next weekend, if we are missing some other drivers
and can you check on 4.0 if tazhw is also telling about missing agpgart_sis
Posted 11 years ago # -
Hi kultex
First of all thank you that you have found the error.
and no, no missing agpgart_sis module in 4.0 (tazhw)
-----------------------------------------------------
not to confuse you and maybe completely irrelevant
could it be that it is named "agpgart-sis" in 4.0 ?
(found in the dmesg-file)
-----------------------------------------------------
again,many thanks...I can hardly wait till next release.Posted 11 years ago # -
it is not irrelevant - but it is the same also in cooking - agpgart-sis is done in both versions by udev
so I have no ideay, why tazhw is crying in cooking....
Posted 11 years ago # -
@mojo,
NTFS signature is missing --> change ntfs-3g to #ntfs-3g
Thanks mojo; it works correctly now.
Posted 11 years ago # -
- Bug in tazpkg (look at sizes)?
root@slitaz:/home/tux# tazpkg depends udevil
udev (220.0K)
util-linux-blkid (468.0K)
glibc-base (4.1M)
util-linux-uuid (68.0K)
ncursesw (ndisc6)
ncurses-common (116.0K)
pciids (240.0K)
usbids (200.0K)
acl (python-dev)
attr (fbff)
kmod (mindi)
zlib (224.0K)
liblzma (yacpi)
glib (tahoe-lafs)
pcre (500.0K)
libffi (libfirefox)
libxml2 (python-magic)
elfutils (856.0K)
root@slitaz:/home/tux#
Already seen with SliTaz 4.0 - Bug in TazPanel
Search for a package in TazPanel (ie: midori)
Posted 11 years ago # - Bug in tazpkg (look at sizes)?
-
@ sixofeight
can you try new rolling, if your harddrive is now available? pata_sis.ko.xz was added to modules list
Posted 11 years ago # -
yep..Hdd is detected
tazhw same issue:
root@slitaz:/home/tux# tazhw detected-modulesDetected PCI and USB modules
===============================================
agpgart_sis
ohci_hcd
ohci_hcd
pata_sis
snd_intel8x0
ohci_hcd
ohci_hcd
ehci_hcd
nouveau
===============================================root@slitaz:/home/tux# tazhw detect-pci
Detected PCI devices Kernel modules
===============================================
! Missing module : agpgart_sis
* Builtin module : ohci_hcd
> Module in use : pata_sis
> Module in use : snd_intel8x0
* Builtin module : ohci_hcd
* Builtin module : ehci_hcd
> Module in use : nouveau
===============================================
I'm still in trouble with SpaceFm:
boot from usb (live mode)-> remove usb->empty folder /media/SliTaz core-4in1
I can't delete that folder (owner tux) not as tux and not as root.
also all the "do it as root" rightclick options won't work.They are asking
for the PW but doing nothing.Posted 11 years ago # -
@sixofeight
the ! Missing module : agpgart_sis will not disapear, as long as somedody looks into tazhw - at the moment i have no time. But it is no problem, because agpgart_sis is loaded by udev, so the error is only, that tazhw is reporting this non existing error...
the spacefm troubles -
you should eject the stick before you remove the stick
and all the "do it as root" options are not working, because of spacefm needs bash - I think, when you install bash, it will work (did not test it) - my solution is to add a spacefm root desktopentry in /usr/share/applications - it is attached - just remove the .txt
Posted 11 years ago # -
@kultex
It seems that progress is being made, at least for me..;-)
Thank youPosted 11 years ago # -
ERROR DURING COMPILING KERNEL
Make returns the following error when compiling the kernel:
make[2]: *** [drivers/block/loop.o] Error 1
make[1]: *** [drivers/block] Error 2
make: *** [drivers] Error 2Compiling modules is OK; it seems that all the missing modules are built and installed. I'm going to do a new iso for Cooking so I'll be able to connect to the internet and can continue to test cooking.
Posted 11 years ago # -
Hi,
3 QUESTIONS
- Can I consider, running Cooking, that after an update the system is same that Rolling?
- Would it be possible with next Rolling/Cooking to have a graphical utility that just would show the state of the memory: total/free/used Mem/Swap in real time (like Info System in stable)? This would be very usefull (for me :-) ) when working on a system with few RAM.
- Running as well as Cooking than Rolling, can someone explain me why the Task Manager indicates more free memory than the
free
command?
Thanks
Posted 11 years ago # -
@Ceel
I'm pretty sure the Task Manager reports the same as the free command. But look for the +/- buffers selection, not the 'Mem' selection.
Posted 11 years ago #
Reply »
You must log in to post.