Raqcop 2.0 - Kernel panic?

[ceelight]

Getting this after dd the img to my harddisk:

Code:

md: raid1 personality registered for level 1
cpuidle: using governor ladder
NET: Registered protocol family 17
Cobalt system type is Pacifica
Cobalt Networks ACPI driver 1.0 (modified by jeff@404ster.com)
Cobalt Networks LED driver 1.0 (modified by jeff@404ster.com)
Cobalt Networks Serial Number driver 1.6 (modified by jeff@404ster.com)
Cobalt Networks Watchdog Timer driver 1.0 (modified by jeff@404ster.com)
Cobalt Networks Sensor driver 1.0 (modified by jeff@404ster.com)
Cobalt Networks RAM Info driver 1.0 (modified by jeff@404ster.com)
Cobalt Networks Powermode driver 1.0 (modified by jeff@404ster.com)
drivers/cobalt/powermode.c:cobalt_powermode_init: No support for GenIII systems!
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly on device 3:4.
Freeing unused kernel memory: 176k freed
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Any idea where to look? What info do you need?

[Davesworld]

What do you have the boot and root disks in the rom set to? Both should be hda1 as I see you are not running raid. Raqcop and IPCop 2 use the same partition for both. With a 3000 series you can simply do a rom reset and it will default to hda1 for both.

By the way, did you install with VMWare? I just recently uploaded the 512 flash images and am about to upload hard drive images in both vmdk and flat.

[ceelight]

Ok, I will try this and let you know the result...  I installed the Compressed-Full-Disk-Images via dd...

[Davesworld]

You must have a lot of space. I warned people that those are the full 20GB. I'm using flash raid here. Due to the timing you may have actually installed RC1 but if it was downloaded 09/12/11 or later it will allow you to upgrade to 2.0 as soon as red is connected. No need to download and reinstall. I upgraded mine in place vi the web gui.

[ceelight]

Thanks for your help!

Yeah, it finally worked. 1.4.x booted on hda4. 2.0 on hda1 - after configure the boot - all good. Stupid me. Too long no working on the cobalts.. ;-)

But something's strange. httpd stops and no more connection to the internet after a while. I've updated to 2.0.0.

Back on 1.4.21 now. I think I'll give it a chance later when URLFilter-AddOn is out. I need it for the kids...

[Davesworld]

Urlfilter is being integrated and is in progress last I knew. I like it as well and definitely miss it.

So the http server stops working and you can't get to the web gui? Your network is not sticking for some reason.

For me setup initially upon first boot works best if you run depmod first. The reason is that the kernel that was used to install is not named the same as you are running on the Cobalt. Without depmod setup does not see the nics unless you load a correct driver and then it segfaults easily coming out of it. After depmod setup is rock solid.

Let me know. I have a spare machine or two that I can duplicate your steps exactly. You downloaded rc1 in flat form and dd'ed it to the drive, booted it, ran setup after depmod and then upgraded to 2 when you were connected?

[Davesworld]

OK Ceelight. I updated the instructions to make the point that you WILL see errors on first boot due to the lack of a network and to run depmod before setup and then reboot when you are done setting up.

Moving to version 2 from 1.4 is a big step initially since you have to start from scratch but it's a one time effort only.

[ceelight]

OK Ceelight. I updated the instructions to make the point that you WILL see errors on first boot due to the lack of a network and to run depmod before setup and then reboot when you are done setting up.

Perfect! I'll give it a try next week as I have a week vacation now...

Moving to version 2 from 1.4 is a big step initially since you have to start from scratch but it's a one time effort only.

Hey, that's not work - it's fun. ;-)

Maybe I'll also setup my RaQ3 with Lenny and your kernel...

[Davesworld]

Cool. I'm anxious to see how you fare with it. I downloaded and checked the sums of the flat images, raid and single and even installed them on a test machine to proxy through it on one of my browsers. Both the raid and single work fine as I expected.

As far as flash images, I did trial and error with VMWare to try to get the flash images the correct size. 512 and 1GB I know fit, The 4GB I am certain of. The 2GB I looked at the mkflash script and I hope it fits on 2GB flash drives. I do not actually have one.

I only use dual 512MB flash drives in raid on my daily edge Raqcop.

OT:
I just got finished patching the 3.0.4 kernel and it runs fine on Squeeze. One warning before you download anything. In my configurations I deselected experimental in kernel configs 2.6.37 through 2.6.39 which also caused the e100 ignore checksum feature to be skipped.

I am back on track for 3.0.4. I usually use a gigabit nic so I never noticed until I dug out a crippled Raq3 with no pci and one nic and moved a test install over to it. I actually had to use a usb nic to get into it and copy a new e100 module to it to get the nic started with 2.6.39.

I am now running 3.0.4 and Debian Squeeze on two XTR's and the barebones Raq3i. The 300mhz processor does ok with it. I use a 3000 to make sure my kernels run on everything x86 Cobalt. The 3i barebones might make a decent mail server for myself. I'm tired of using other mail services.

Oh, a very important note about 3.0.4. As of 2.6.39 the old IDE drivers are marked as deprecated and are still there for now. I compile the kernel with the new PATA drivers so boot remains hdx and root has to be set as sdx. I'm happy that the Cobalts still run fine with this change. The reason why boot remains is that the rom uses the old ide drivers and will see it as hdx, the root= argument is passed to the system kernel image from the rom so the system kernel having the PATA drivers in it will only recongnize sdx.

 

[ceelight]

Very important, cause I can't come to boot: Where/how do I tell the rom the boot option "root=sda1"?

and

Do I need the kernel-headers once the raq is running?

Thx :-)

edit: Hanging here...

Code:

VFS: Cannot open root device "(null)" or unknown-block(3,1)
Please append a correct "root=" boot option; here are the available partitions:
0800       293036184 sda  driver: sd
  0801         9764864 sda1 00000000-0000-0000-0000-000000000sda1
  0802               1 sda2 00000000-0000-0000-0000-000000000sda2
  0805         1004544 sda5 00000000-0000-0000-0000-000000000sda5
  0806       282263552 sda6 00000000-0000-0000-0000-000000000sda6
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
Pid: 1, comm: swapper Not tainted 3.0.4-cobalt #2
Call Trace:
 [<c0354140>] ? panic+0x4d/0x123
 [<c0437901>] ? mount_block_root+0x1e9/0x1f8
 [<c0437949>] ? mount_root+0x39/0x4d
 [<c0437147>] ? parse_early_options+0x18/0x18
 [<c0437a67>] ? prepare_namespace+0x10a/0x13a
 [<c0437221>] ? kernel_init+0xda/0xe3
 [<c03561b6>] ? kernel_thread_helper+0x6/0xd

[Davesworld]

On Raqcop or Debian? If Debian it depends on where you actually have your root device AND which kernel? Raqcop, root and boot are both hda1 or md0 if running raid. Raqcop will remain with the classic ide drivers for some time to come. I only started using the PATA drivers on 2.6.39 and newer on my server kernels.

[ceelight]

"Damn it", it works!  I'm really happy, as I tryied it sporadically since two years. Just had to tell the Rom that it should look for /dev/sda1.

So, to answer your question, Debian Squeeze runs with your kernel on my RaQ3. Thanks a lot, Dave!

Code:

root@raq3:~# uname -a
Linux raq3 3.0.4-cobalt #2 Sat Oct 1 16:39:48 PDT 2011 i586 GNU/Linux
root@raq3:~# ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:10:e0:01:e6:a8 
          inet Adresse:192.168.111.6  Bcast:192.168.111.255  Maske:255.255.255.0
          inet6-Adresse: fe80::210:e0ff:fe01:e6a8/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:6132 (5.9 KiB)  TX bytes:1956 (1.9 KiB)

lo        Link encap:Lokale Schleife 
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metrik:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

I decided to install Raqcop 2.0 when urlfilter is available. It's too important as my kids have an "interesting" age right now...

[Davesworld]

Ah, yeah the curious kids. I saw by your uptime that you had switched back a week ago.

Some of the elements of urlfilter are already in IPCop 2 as it is being integrated into it. Marco is one of the devs anyway. I think the holdup is that Squidguard has always used libdb (berkely database manager) whereas sqlite would be preferred. Libdb is actually present in the build tree but there is reluctance to add yet another database besides sqlite. Perl could be used instead of wget. At least wget was not in the standard binary paths the way it was used in the 1.4 addon.

Unfortunately, you are not the only one out there holding back on 2 for this reason. I'm not how sure using acls and squid redirects would affect the system load compared to urlfilter but it can be done. Myself, I could never go back to 1.4 as long as 2 is available.