You are not logged in.
Hello,
I tried to install Cooking and the 4 last Rollings on an ACER TravelMate 632XV; but for each try, I've had at boot
[c]
[Linux-bzImage, setup=0x3c00, size=0x2b4060]
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid:1, comm: swapper/0 not tainted 3.2.53-slitaz #4
Call Trace:
[<c13fc74d>] ? panic+0x4d/0x13a
[<c15a1a4e>] ? mount_block_root+0x1d8/0x1ec
[<c15a1b61>] ? mount_root+0x39/0x4d
[<c15a168c>] ? start_kernel+0x2c5/0x2c5
[<c15a1cb2>] ? prepare_namespace+0x13d/0x16d
[<c15a1789>] ? kernel_init+0xfd/0x102
[<c1404736>] ? kernel_thread_helper+0x6/0xd[/c]
I think the kernel needs a driver for my HD that is not builtin but built as module.
Cooking and Rolling run well in live or frugal mode and I can access to my HD.
I wanted add some drivers in the kernel but as well as with Cooking than with Rolling, it's not possible to compile the kernel, make meets an error.
Can a developer integrate the driver for old HD in the kernel for a next Rolling? Thanks.
my HD: IDE disk TOSHIBA MK2018GAP
Offline
can you attach the output of lsmod and dmesg from the live boot - I think maybe it is just necessary to load some modules at boot in rcS.conf or in grub - http://doc.slitaz.org/en:handbook:livecd - Slitaz Parameters
Offline
Hi kultex,
Thank you for answering. I don't have any problem with live; the kernel loads the driver and I can see my HD. I have problem with full installation. Installation with tazinst is OK, all files are correctly installed.
In menu.lst I tell to grub where to find the kernel; I believe I can also indicate to the kernel to load a module (in my case and only for the ACER, I need pata_ali). And here is the problem: to load the module the kernel needs to access to the HD and to access to the HD it needs pata_ali... You see what I mean?
Here are the output of lsmod and the dsmeg.log file (from frugal install)
Offline
I think you are right...
your dmesg is not complete - please run in terminal dmesg > dmesg.txt and attach it
Offline
Here it is.
Offline
Yesterday I downloaded cooking & could only install it from a .iso image, & had to use tasinst in a terminal, after making tazinst.rc file.
It wouldn't install from my live pendrive. The last message received was 'sh: Out of memory' - this on a machine with 1.5gb ram.(?!)
Just posting to let you know in case there is actually something amiss with the installer.
Otherwise, a great distro. ::thumbs up::
Edit: I used dd to create the live pendrive which worked perfectly as a live environment.
it has to do with this config part of the kernel - I think it is just stupid to check one by one, so I have to check, which ones are necessary - like I know - for CONFIG_PATA_NINJA32 m is ok - because its a PCMCIA IDE driver
The problem is I have no time now - perhaps somebody has time to check, what the drivers are needed...
#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=y
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_SVW=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
#
# PATA SFF controllers with BMDMA
#
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_ATP867X=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CS5535=m
CONFIG_PATA_CS5536=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT8213=m
CONFIG_PATA_IT821X=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not set
CONFIG_PATA_RDC=m
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SCH=m
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_TOSHIBA=m
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m
Offline
Concerning my own case, when I run Rolling in frugal install and open SpaceFM and view internal disks, I can see them as long as I don't [c]modprobe -r pata_ali[/c]
(removing other ata/pata_xxx modules has no effect)
But I suppose some other modules could be usefull for other HDs (ggg has problem with his HD too, see http://forum.slitaz.org/topic/not-detect-hard-drives)
I'm not competent enough to know what modules are essential; what I can do is to run 4.0 in frugal and see what modules were m/y or not set on it. It can give an idea, there is no access disks problem with 4.0
The problem is I have no time now
Don't worry. It's not really a priority. I'm just a little frustrated because I cannot test deeper rolling, but no precipitation; take your time and give us a stable 5.0 when ready.
Offline
This commit removed legacy IDE and PCI IDE chipset support for block devices which were compiled into the kernel.
This is the same commit where pata drivers went from not set to M.
http://hg.slitaz.org/wok/rev/db5b03f42dd9
linux/stuff/linux-slitaz.config Tue Jan 28 05:56:16 2014 +0000
#
-# Please see Documentation/ide/ide.txt for help/info on IDE drives
-#
-CONFIG_IDE_XFER_MODE=y
-CONFIG_IDE_TIMINGS=y
-CONFIG_IDE_ATAPI=y
-CONFIG_IDE_LEGACY=y
-# CONFIG_BLK_DEV_IDE_SATA is not set
-CONFIG_IDE_GD=y
-CONFIG_IDE_GD_ATA=y
-# CONFIG_IDE_GD_ATAPI is not set
-CONFIG_BLK_DEV_IDECS=m
-# CONFIG_BLK_DEV_DELKIN is not set
-CONFIG_BLK_DEV_IDECD=y
-CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
-# CONFIG_BLK_DEV_IDETAPE is not set
-# CONFIG_BLK_DEV_IDEACPI is not set
-# CONFIG_IDE_TASK_IOCTL is not set
-CONFIG_IDE_PROC_FS=y
-
-#
-# IDE chipset support/bugfixes
-#
-CONFIG_IDE_GENERIC=y
-# CONFIG_BLK_DEV_PLATFORM is not set
-CONFIG_BLK_DEV_CMD640=y
-# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
-# CONFIG_BLK_DEV_IDEPNP is not set
-CONFIG_BLK_DEV_IDEDMA_SFF=y
-
-#
-# PCI IDE chipsets support
-#
-CONFIG_BLK_DEV_IDEPCI=y
-CONFIG_IDEPCI_PCIBUS_ORDER=y
-# CONFIG_BLK_DEV_OFFBOARD is not set
-CONFIG_BLK_DEV_GENERIC=y
-# CONFIG_BLK_DEV_OPTI621 is not set
-CONFIG_BLK_DEV_RZ1000=y
-CONFIG_BLK_DEV_IDEDMA_PCI=y
-CONFIG_BLK_DEV_AEC62XX=y
-CONFIG_BLK_DEV_ALI15X3=y
-CONFIG_BLK_DEV_AMD74XX=y
-CONFIG_BLK_DEV_ATIIXP=y
-CONFIG_BLK_DEV_CMD64X=y
-CONFIG_BLK_DEV_TRIFLEX=y
-# CONFIG_BLK_DEV_CS5520 is not set
-CONFIG_BLK_DEV_CS5530=y
-CONFIG_BLK_DEV_CS5535=y
-CONFIG_BLK_DEV_CS5536=y
-CONFIG_BLK_DEV_HPT366=y
-CONFIG_BLK_DEV_JMICRON=y
-CONFIG_BLK_DEV_SC1200=y
-CONFIG_BLK_DEV_PIIX=y
-CONFIG_BLK_DEV_IT8172=y
-CONFIG_BLK_DEV_IT8213=y
-CONFIG_BLK_DEV_IT821X=y
-CONFIG_BLK_DEV_NS87415=y
-CONFIG_BLK_DEV_PDC202XX_OLD=y
-CONFIG_BLK_DEV_PDC202XX_NEW=y
-CONFIG_BLK_DEV_SVWKS=y
-CONFIG_BLK_DEV_SIIMAGE=y
-CONFIG_BLK_DEV_SIS5513=y
-CONFIG_BLK_DEV_SLC90E66=y
-CONFIG_BLK_DEV_TRM290=y
-CONFIG_BLK_DEV_VIA82CXXX=y
-CONFIG_BLK_DEV_TC86C001=y
-
-#
-# Other IDE chipsets support
-#
-
-#
-# Note: most of these also require special kernel boot parameters
-#
-CONFIG_BLK_DEV_4DRIVES=y
-CONFIG_BLK_DEV_ALI14XX=y
-CONFIG_BLK_DEV_DTC2278=y
-CONFIG_BLK_DEV_HT6560B=y
-CONFIG_BLK_DEV_QD65XX=y
-CONFIG_BLK_DEV_UMC8672=y
-CONFIG_BLK_DEV_IDEDMA=y
-
-#
Offline
yes I know this is my fault - but at the moment I cannot reconstruct, why I set them to m, because all the old attachments are gone - (I attached the config of 6 ? different distributions). We can set all of them to y, but I think its better to check before, which are realy necessary.
I can redo this in 10 days - not before
Offline
ok - found some time
Offline
ok - I took it from fedora and mint, thinking, when it works in fedora and mint, it should work also in SliTaz and it leaded into the smallest kernel - but ???
So I think we should try it with this config - mainly from Anitx - still the smallest and checking the drivers it looks ok
Mojo can you do it or should I ask Christophe?
1404 CONFIG_SATA_SIL24=y
1405 CONFIG_ATA_SFF=y
1406
1407 #
1408 # SFF controllers with custom DMA interface
1409 #
1410 CONFIG_PDC_ADMA=y
1411 CONFIG_SATA_QSTOR=y
1412 CONFIG_SATA_SX4=y
1413 CONFIG_ATA_BMDMA=y
1414
1415 #
1416 # SATA SFF controllers with BMDMA
1417 #
1418 CONFIG_ATA_PIIX=y
1419 CONFIG_SATA_MV=y
1420 CONFIG_SATA_NV=y
1421 CONFIG_SATA_PROMISE=y
1422 CONFIG_SATA_SIL=y
1423 CONFIG_SATA_SIS=y
1424 CONFIG_SATA_SVW=y
1425 CONFIG_SATA_ULI=y
1426 CONFIG_SATA_VIA=y
1427 CONFIG_SATA_VITESSE=y
1428
1429 #
1430 # PATA SFF controllers with BMDMA
1431 #
1432 CONFIG_PATA_ALI=y
1433 CONFIG_PATA_AMD=y
1434 CONFIG_PATA_ARTOP=y
1435 CONFIG_PATA_ATIIXP=y
1436 CONFIG_PATA_ATP867X=y
1437 CONFIG_PATA_CMD64X=m
1438 CONFIG_PATA_CS5520=m
1439 CONFIG_PATA_CS5530=m
1440 CONFIG_PATA_CS5535=m
1441 CONFIG_PATA_CS5536=m
1442 CONFIG_PATA_CYPRESS=m
1443 CONFIG_PATA_EFAR=m
1444 CONFIG_PATA_HPT366=m
1445 CONFIG_PATA_HPT37X=m
1446 CONFIG_PATA_HPT3X2N=m
1447 CONFIG_PATA_HPT3X3=m
1448 # CONFIG_PATA_HPT3X3_DMA is not set
1449 CONFIG_PATA_IT8213=m
1450 CONFIG_PATA_IT821X=y
1451 CONFIG_PATA_JMICRON=y
1452 CONFIG_PATA_MARVELL=y
1453 CONFIG_PATA_NETCELL=m
1454 CONFIG_PATA_NINJA32=m
1455 CONFIG_PATA_NS87415=m
1456 CONFIG_PATA_OLDPIIX=m
1457 CONFIG_PATA_OPTIDMA=m
1458 CONFIG_PATA_PDC2027X=m
1459 CONFIG_PATA_PDC_OLD=m
1460 # CONFIG_PATA_RADISYS is not set
1461 CONFIG_PATA_RDC=m
1462 # CONFIG_PATA_SC1200 is not set
1463 CONFIG_PATA_SCH=m
1464 CONFIG_PATA_SERVERWORKS=m
1465 CONFIG_PATA_SIL680=m
1466 CONFIG_PATA_SIS=y
1467 CONFIG_PATA_TOSHIBA=y
1468 CONFIG_PATA_TRIFLEX=m
1469 CONFIG_PATA_VIA=y
1470 CONFIG_PATA_WINBOND=m
1471
1472 #
1473 # PIO-only SFF controllers
1474 #
1475 CONFIG_PATA_CMD640_PCI=m
1476 CONFIG_PATA_ISAPNP=y
1477 CONFIG_PATA_MPIIX=y
1478 CONFIG_PATA_NS87410=m
1479 CONFIG_PATA_OPTI=m
1480 CONFIG_PATA_PCMCIA=m
1481 CONFIG_PATA_QDI=m
1482 # CONFIG_PATA_RZ1000=m
1483 CONFIG_PATA_WINBOND_VLB=m
1484
1485 #
1486 # Generic fallback / legacy drivers
1487 #
1488 CONFIG_PATA_ACPI=y
1489 CONFIG_ATA_GENERIC=y
Offline
@Ceel
The 3 driver modules loaded in the lsmod output you posted which enable the IDE controller are ata_generic pata_acpi pata_ali.
This kernel is compiled with CONFIG_ATA_GENERIC=y CONFIG_PATA_ACPI=y CONFIG_PATA_ALI=y in the kernel.
http://people.slitaz.org/~mojo/stuff/linux-3.2.53.tazpkg
Offline
@mojo,
Thanks, I test it right now.
...
Offline
... and it works for me now. Thanks again!
Still remains the problem when compiling the kernel. It could not come from a compatibility issue with gcc?
Offline
Just installed cooking via live pendrive to an SDHC card from the web, installed OK, BUT, it made the wrong entries in grub menu.lst & etc/fstab, I had to go back in & change them to (hd0,0) from (hd1,0), & there was no / entry in etc/fstab at all.
Hope this can be fixed before release of SliTaz 5.0.
(Really like the SliTaz Spider desktop wallpaper.)
All the best.
@fatmac
There's no need for a / entry in /etc/fstab, as the root= kernel cmdline option specifies this entry. It will be mounted as /dev/root in /, as can be seen in the /proc/mounts file.
As for installing to SDHC cards, I'm afraid that's an issue you'll have to deal with for as long as SliTaz will be using non-UUID names for boot settings. I'm not sure if Legacy GRUB supports booting with UUID, and specifying the root as UUID, but if it does, that certainly needs to be changed.
Offline
@necrophcodr
Thanks for the reply, sorry didn't look at the kernel line. As for SDHC cards, I'm OK with doing it for myself, just thought it might be good for others to have it done automatically.
All the best.
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]