Norhtec MicroClient Jr DX and Slackware 13, can't boot
in [Slackware]
|
Prev: libgtk-1.2.so.0
Next: All aTTers unite,lets all offer up some kinds words & applogizesto rob cypher in the sprit of a experiment. rob said that if he gets 5 applogizeshe'll forever stop posting cross threads on ATT.lets all here see if he'sa man of his word or n
From: Tinfoil Hat on 24 Feb 2010 06:31 Hi all, Any experience with this hardware? http://www.norhtec.com/products/mcjrdx/ According with http://members.shaw.ca/dan.mckay/Slackroclient.html it should work fine with Slackware 13. I've installed Slackware 13 on a CF card, with the huge.s kernel. The preboot setup correctly identifies the card as secondary master, with its make and model. These are mi CF partitions: /dev/[h|s]dx1 / ext4 /dev/[h|s]dx2 swap /dev/[h|s]dx3 /var ext4 /dev/[h|s]dx4 /home ext4 Yet when I try to boot it says Kernel Panic... .... VFS: cannot open root device "1601" or unknown block(22,1) VFS: unable to mount root fs on unknown block(22,8) I've tried to put into /etc/fstab and /etc/lilo.conf either /dev/hdc1 or /dev/sdc1, but it always panics with the above message. I've also tried to use an initrd with the ext4 modules, but nothing changes. Aren't those modules already included in huge.s anyways? Any hint about what could go wrong?
From: Henrik Carlqvist on 24 Feb 2010 14:01 Tinfoil Hat <nope(a)than.ks> wrote: > I've installed Slackware 13 on a CF card, with the huge.s kernel. > The preboot setup correctly identifies the card as secondary master, > with its make and model. > > These are mi CF partitions: > /dev/[h|s]dx1 / ext4 > /dev/[h|s]dx2 swap > /dev/[h|s]dx3 /var ext4 > /dev/[h|s]dx4 /home ext4 The key here is to know the device names at boot. Instead of guessing among /dev/hda1, /dev/sda1, /dev/hdc1 or /dev/whatever it might help to look at the written text during boot. Usually you will see some text about a disk controller being found and a disk connected to that controller. There you will also see information about detected partitions. Here is an example from a machine with Slackware 12.0 I booted a few days ago: -8<--------------------------------------------------------- Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot 0000:00:07.1 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1 ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: ST3320620A, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: LG CD-ROM CRD-8522B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 512KiB hda: 625142448 sectors (320072 MB) w/16384KiB Cache, CHS=38913/255/63, UDMA(100)hda: cache flushes supported hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9 hda10 > hdc: ATAPI 48X CD-ROM drive, 128kB Cache, DMA -8<--------------------------------------------------------- Above you can see that the machine has a VIA IDE controller and a Seagate disk (ST3320620A) connected to that controller. The disk has partitions named hda1 to hda10. > cannot open root device "1601" or unknown block(22,1) Block(22,1) means that it failed to use /dev/hdc1, probably because your root partition is on some device. > VFS: unable to mount root fs on unknown block(22,8) Did you try to mount your root partition from /dev/hdc8? > I've tried to put into /etc/fstab and /etc/lilo.conf either /dev/hdc1 or > /dev/sdc1, but it always panics with the above message. Scsi drives get their names in another way than ide drives. You usually don't have any /dev/sdc unless you also have /dev/sda and /dev/sdb. > I've also tried to use an initrd with the ext4 modules, but nothing > changes. Aren't those modules already included in huge.s anyways? Huge.s is meant to include everything you might need to boot. > Any hint about what could go wrong? You are most likely trying to mount the wrong device name for your root partition. If I would give yet another guess I would suggest that you try to mount /dev/sda1 as your root file system. However, it would be better to read the bootup messages to get the right value without guessing. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Tinfoil Hat on 24 Feb 2010 13:48 Tinfoil Hat, on 02/24/2010 12:31 PM, wrote: > Hi all, > > Any experience with this hardware? > http://www.norhtec.com/products/mcjrdx/ Just for the record, it also goes by the name eBox-3300 for some vendors. http://www.compactpc.com.tw/ebox-3300.htm Anyone using it with Slackware 13?
From: Danno on 24 Feb 2010 16:07 Tinfoil Hat wrote: > Hi all, > > Any experience with this hardware? > http://www.norhtec.com/products/mcjrdx/ > > According with > http://members.shaw.ca/dan.mckay/Slackroclient.html > it should work fine with Slackware 13. <snip> > Any hint about what could go wrong? From the above link : Although I had little difficulty with this, an email from Falk R. says that he had to rebuild a kernel to include pata_RDC statically in his kernel (not as a module) before he had access to the IDE interface. RDC PATA support kernel options is under -> Device Drivers -> Serial ATA (prod) and Parallel ATA (experimental) drivers -> RDC PATA support There are, apparently, more than one version of the IDE controller for this silicon in these boxes, with the more recent versions giving Slack13.0 users grief. Further in that webpage, on installing Slack12.2, you'll see that the stock kernel had to be patched and built to disable DMA. My guess would be that with Slack13.0, you'd have to configure the kernel with pata_RDC statically built, and disable DMA with a lilo append option (TMK, append options won't work with modules). It also says to use a small DOS partition as the first primary partition of the CF card. Did you try that? I doubt it matters, but who can say? The BIOS settings are also very important with this box. You absolutely must have the OnBoard IDE operate Mode set to "Native", as the webpage states. If all else fails, try a Slack12.2 install with the eBox3300 patches. I notice that you have defined a partition on your CF card for swap. I have always avoided this, with any flash product, as I was under the impression that the extreme number of rewrites would wear out that particular partition very quickly quickly. -- Slackware 12.2, 2.6.27.7, Core i7 920, GeForce 8400 GS RLU #272755
From: Tinfoil Hat on 26 Feb 2010 06:18
Tinfoil Hat, on 02/24/2010 12:31 PM, wrote: > Hi all, > > Any experience with this hardware? > http://www.norhtec.com/products/mcjrdx/ Thanks for the answers. I've tried another trick: boot from USB stick. At first I tried with the instructions at ftp://ftp.slackware.com/pub/slackware/slackware-13.0/usb-and-pxe-installers/README_USB.TXT but it still wouldn't boot. The boot was successful after recreating the USB stick with this script: http://connie.slackware.com/~alien/tools/usbimg2disk.sh Now the mistery thickens. If I boot from USB, in /dev/disk/ I can see the USB stick, but no trace of the CF card. If I create in the same way a bootable CF, it still boots fine, but /dev/disk doesn't even exist and fdisk -l can't see any volume. dmesg and /var/log/messages don't show any ide-related line at all. It baffles me that it can read the CF and boot from it, and then not see it. If it could see and mount the CF, I could proceed with a network install. I will try Danno's advice, but I've never tampered with kernel or modules before. I'll go ahead and google, but if you have some neat link I would really appreciate it. Thanks. |