Cobalt Thread

Additional operating system/hardware discussion (Windows, Linux, *BSD and others)
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Thu Jan 26, 2017 12:44 pm

spiroyster wrote:Does anyone have the BlueQuartz source code for Qube3? All the links seem dead :(.

http://bluequartz.org/

It would be nice put a Qube3 to some practical use, such as NAS or something. It doesn't have gigbit ethernet and only supports UW SCSI (or ATA33) though. Would there be any work arounds for this? One PCI :roll: hmmm...

Could you make something out of Debian 7 and Linux kernel v3.2.x? Dave Studeman - the guy behind Raqcop (sadly no longer active now planning for a new domain) had a Cobalt patch for Linux kernel v3.2.5 which worked until v3.2.63. With some reordering I was able to make it work with v3.2.65 and I assume it could still work (again with some reordering) just today (2017-01-27) successfully tested RaQ 4r (w/K6-2), RaQ XTR (w/PIII) and Qube 3 (w/K6-2+) systems with the latest Debian 7 kernel (v3.2.84 - successfully patched with the patch for v3.2.65) (i386 has long term support until end of May 2018!).
Last edited by johnnym on Fri Jan 27, 2017 9:41 am, edited 1 time in total.
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
uunix
Donor
Donor
Posts: 1808
Joined: Sun Mar 27, 2011 12:48 pm
Location: Stourbridge / England / UK

Re: Cobalt Thread

Unread postby uunix » Thu Jan 26, 2017 12:46 pm

I have been pondering this of late:
http://www.ebay.co.uk/itm/SUN-COBALT-QUBE-3-Pro-Plus-Boxed-with-PSU-Excellent-condition-/132066684172?hash=item1ebfc9ad0c:g:-yAAAOSwxp9W8X05
SUN Qube 3, not the MIPs variant, AMD K6 I think.

There is one £10 cheaper with no PSU.
-----------------------------------------------------------------------
Hey Ho! Pip & Dandy!
:Octane2: :O2: :Indigo: :Indy:
-----------------------------------------------------------------------

User avatar
Titox
Posts: 265
Joined: Tue Aug 14, 2007 12:13 am
Location: Spain

Re: Cobalt Thread

Unread postby Titox » Thu Jan 26, 2017 12:47 pm

johnnym wrote:
spiroyster wrote:Does anyone have the BlueQuartz source code for Qube3? All the links seem dead :(.

http://bluequartz.org/

It would be nice put a Qube3 to some practical use, such as NAS or something. It doesn't have gigbit ethernet and only supports UW SCSI (or ATA33) though. Would there be any work arounds for this? One PCI :roll: hmmm...

Could you make something out of Debian 7 and Linux kernel v3.2.x? Dave Studeman - the guy behind Raqcop (sadly no longer active :( ) had a Cobalt patch for Linux kernel v3.2.5 which worked until v3.2.63. With some reordering I was able to make it work with v3.2.65 and I assume it could still work (again with some reordering) with the latest Debian 7 kernel (i386 has long term support until end of May 2018!).

Dave is still active at the IPCop forums: http://www.ipcop-forum.de/forum/viewtopic.php?f=62&t=32596
I also have used RaQCop!
Alberto (Between the TV and the sofa)
:Fuel: :Octane2: :1600SW: :O2: :O2: :1600SW: :Indigo:
http://www.f3b.es
http://unixverse.blogspot.com

User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Fri Jan 27, 2017 8:58 am

Titox wrote:[...]
Dave is still active at the IPCop forums: http://www.ipcop-forum.de/forum/viewtopic.php?f=62&t=32596

Thanks for the pointer, I was already afraid his work was lost. Good to read that he wants to continue working on RaQCop. Also interesting is that he seems to be successful in using a nearly vanilla Linux kernel with his RaQs, although some Cobalt specific functionality is lost.

Titox wrote:I also have used RaQCop!

Well, it could be that I've first heard about RaQCop from your website actually! The link to RaQCop on the linked article looks "used" when I returned to the article just now. :)

Titox wrote:[...]
BTW this is under my desk at the moment:
xtr.jpeg

I haven't seen a detailed picture of an XTR tray yet on the web and I also don't have a single one in my XTR. So would you mind posting one or more - if you like - photos from one of your XTR trays so we can have a look?
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
Titox
Posts: 265
Joined: Tue Aug 14, 2007 12:13 am
Location: Spain

Re: Cobalt Thread

Unread postby Titox » Sun Jan 29, 2017 5:43 am

johnnym wrote:I haven't seen a detailed picture of an XTR tray yet on the web and I also don't have a single one in my XTR. So would you mind posting one or more - if you like - photos from one of your XTR trays so we can have a look?


Of course:
DSC_8385.JPG

DSC_8381.JPG

DSC_8379.JPG

DSC_8378.JPG
Alberto (Between the TV and the sofa)
:Fuel: :Octane2: :1600SW: :O2: :O2: :1600SW: :Indigo:
http://www.f3b.es
http://unixverse.blogspot.com

User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Mon Jan 30, 2017 1:58 am

Titox wrote:
johnnym wrote:I haven't seen a detailed picture of an XTR tray yet on the web and I also don't have a single one in my XTR. So would you mind posting one or more - if you like - photos from one of your XTR trays so we can have a look?


Of course:

Thanks for sharing those detailed photos. I haven't seen those trays on Ebay, yet, IIRC.

According to the RaQ XTR data sheet, it was the first server (appliance) to use four 3.5" HDDs in a front-accessible manner in one rack unit. So if correct, a real first of its kind.

The mechanism of the front panel is also quite interesting, because it allows for a display, buttons and info LEDs but does not hinder access to the disks because in can be folded out of the way. Well, it might not look as clean as an Xserve G4 front panel, but you also don't have to look into a manual to decrypt the LED signals.

During searching for the data sheet I also stumbled upon this very detailed description of the RaQ XTR I didn't know yet - perhaps useful for other RaQ XTR owners, too - if not already widely known.
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
spiroyster
Donor
Donor
Posts: 145
Joined: Thu May 03, 2012 8:24 am
Location: Somerset, UK

Re: Cobalt Thread

Unread postby spiroyster » Tue Jan 31, 2017 12:10 am

Titox wrote:
spiroyster wrote:Does anyone have the BlueQuartz source code for Qube3? All the links seem dead :(.

http://bluequartz.org/

It would be nice put a Qube3 to some practical use, such as NAS or something. It doesn't have gigbit ethernet and only supports UW SCSI (or ATA33) though. Would there be any work arounds for this? One PCI :roll: hmmm...

I have a backup of bluequrtz.org somewhere in my hard disks. I wll look for it and upload, but it will take some time.

To install bluequartz in a RaQ/Qube you need OSOffice Strongbolt. Unfortunately the OSOffice project/company is died so you have to look for the iso elsewhere.

That would be appreciated, certainly in no rush.

johnnym wrote:just today (2017-01-27) successfully tested RaQ 4r (w/K6-2), RaQ XTR (w/PIII) and Qube 3 (w/K6-2+) systems with the latest Debian 7 kernel (v3.2.84 - successfully patched with the patch for v3.2.65) (i386 has long term support until end of May 2018!).

:)
Excellent stuff! How does it boot? Entire kernel/bootloader etc in the ROM, or is it strapped somehow? I wish I was more versed with 'embedded' type thingy ma jigs.

wrt BlueQuartz.org. It seems to have morphed into BlueOnyx.it and it still being actively developed. :)

User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Wed Feb 01, 2017 3:16 am

spiroyster wrote:
johnnym wrote:just today (2017-01-27) successfully tested RaQ 4r (w/K6-2), RaQ XTR (w/PIII) and Qube 3 (w/K6-2+) systems with the latest Debian 7 kernel (v3.2.84 - successfully patched with the patch for v3.2.65) (i386 has long term support until end of May 2018!).

:)
Excellent stuff! How does it boot? Entire kernel/bootloader etc in the ROM, or is it strapped somehow?

I've set this up about two years ago and it just worked a few days ago. I'm currently not at home, so cannot check all the details of the setup again, so I try to use my notes and recall the missing details. I'll update/correct things when I'm back home.

Before I start: I use the Cobalt machines diskless. For x86 Cobalts you need to have a recent or the latest firmware (v2.10.3 from SourceForge) that supports the needed bfx n n boot mode, where the kernel and the root file system is downloaded/accessed via network (NFS in this case). As per the README in romutils-1.0.tar.bz2 "The paged layout is used by the RaQ 3, RaQ 4, Qube 3, and RaQ XTR. The flat layout is only used by the RaQ 550."

When using bfx n n, the firmware starts an embedded Linux kernel 2.4.x, which downloads the kernel (named "vmlinux.bz2" - a bzip2 compressed vmlinux binary (no bzImage!), no external initrd and not bigger than 2097152 Bytes in total!) that should actually be used, from an NFS mount (from "/boot" in "/nfsroot-x86" on the NFS server that is provided via DHCP/BOOTP). Then it starts this kernel (maybe via a similar method than kexec). As the 2.4.x kernel determines the kernel command line for the loaded kernel which is not (always) suitable, I use an embedded Linux kernel command line which suits my needs. This command line makes sure that the Linux kernel does an IP auto-configuration and finds its NFS root file system via DHCP/BOOTP.
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
spiroyster
Donor
Donor
Posts: 145
Joined: Thu May 03, 2012 8:24 am
Location: Somerset, UK

Re: Cobalt Thread

Unread postby spiroyster » Wed Feb 01, 2017 3:30 am

Many thanks johnnym! I've some motivation to dig out my Qub3 and give this a go now. :)

Gul-Dukat
Posts: 7
Joined: Fri Feb 10, 2017 4:55 pm

Re: Cobalt Thread

Unread postby Gul-Dukat » Fri Feb 10, 2017 5:02 pm

Cool thread guys.
Glad to see cobalt raq's still being used and more impressively kept up to date.

Some of the other web pages have dropped off the interweb in recent years.
Only one Ive still managed to find with semi-recent info is

http://lookass.ch/?id=4&area=lst&kat1=Hardware&kat2=SUN%20Cobalt%20Raq

WOuld be keen to get a hold of the 3.2.5 patch you refer to johnnym. If you could make available that would be very appreciated.

Cheers

User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Sat Feb 11, 2017 2:22 am

Gul-Dukat wrote:Cool thread guys.
Glad to see cobalt raq's still being used and more impressively kept up to date.

What Cobalt machines are you using?

Gul-Dukat wrote:WOuld be keen to get a hold of the 3.2.5 patch you refer to johnnym. If you could make available that would be very appreciated.

I hope this is OK for Dave Studeman. For now I've uploaded:
...to pastebin.

I also compiled a small guide for patching and compiling Linux kernel v3.2.84 for Cobalt Networks x86 machines in Debian Wheezy. This will go into a new post to this thread.
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Sat Feb 11, 2017 2:26 am

Patching and compiling Linux kernel v3.2.84 for Cobalt Networks x86 machines (on Debian Wheezy)

  • bind mount needed pseudo file systems ("/proc", "/sys", "/dev/pts" and "/run") into the NFS root file system for the Cobalt x86 machine
  • chroot into the NFS root file system
  • if not already done, install build-essential, linux-source-3.2 and firmware-linux
  • download the v3.2.65 cobalt patch (credits go to Russell Coker, Tim Hockins, Jeff Walter and especially to Dave Studeman for making the Cobalt patches work on Linux v3.2 (and later), I just did some reordering for making the v3.2.5 patch apply to the v3.2.65 Linux kernel)
  • download the v3.2.84 kernel config for diskless operation (this is based on Dave Studeman's config for the Debian Wheezy kernel but changed to support diskless operation (i.e. drivers for built-in NICs are compiled into the kernel and booting from NFS root FS is activated, too))
  • the resulting Linux kernel v3.2.84 runs on:
    • RaQ 4(r)
    • RaQ XTR
    • Qube 3
    ...other Cobalt x86 machines are untested as I have the listed machines only, but I assume that it should at least also run on a RaQ 3 without modification.

Patching the v3.2.84 Linux kernel sources with the patch for v3.2.65

Code: Select all

user@host:/usr/src/linux-source-3.2$ patch -p1 < ../linux-cobalt-3.2.65.patch
patching file Makefile
Hunk #1 succeeded at 214 (offset -40 lines).
patching file arch/x86/Makefile
Hunk #1 succeeded at 157 (offset 3 lines).
Hunk #2 succeeded at 191 (offset 4 lines).
patching file arch/x86/configs/raq3_defconfig
patching file arch/x86/configs/raq4_defconfig
patching file arch/x86/configs/raq550_defconfig
patching file arch/x86/configs/raqxtr_defconfig
patching file arch/x86/include/asm/setup.h
patching file arch/x86/kernel/Makefile
patching file arch/x86/kernel/cobalt.c
patching file arch/x86/kernel/head_32.S
patching file arch/x86/kernel/nmi.c
patching file arch/x86/kernel/reboot.c
Hunk #2 succeeded at 614 (offset 58 lines).
Hunk #3 succeeded at 692 with fuzz 1 (offset 58 lines).
Hunk #4 succeeded at 747 (offset 64 lines).
patching file drivers/Kconfig
patching file drivers/Makefile
patching file drivers/char/misc.c
patching file drivers/char/nvram.c
patching file drivers/cobalt/Kconfig
patching file drivers/cobalt/Makefile
patching file drivers/cobalt/README
patching file drivers/cobalt/acpi.c
patching file drivers/cobalt/fans.c
patching file drivers/cobalt/i2c.c
patching file drivers/cobalt/init.c
patching file drivers/cobalt/lcd.c
patching file drivers/cobalt/led.c
patching file drivers/cobalt/net.c
patching file drivers/cobalt/powermode.c
patching file drivers/cobalt/raminfo.c
patching file drivers/cobalt/ruler.c
patching file drivers/cobalt/sensors.c
patching file drivers/cobalt/serialnum.c
patching file drivers/cobalt/systype.c
patching file drivers/cobalt/wdt.c
patching file drivers/net/ethernet/intel/Kconfig
patching file drivers/net/ethernet/intel/e100.c
Hunk #3 succeeded at 3127 (offset 19 lines).
patching file include/cobalt/acpi.h
patching file include/cobalt/cobalt.h
patching file include/cobalt/i2c.h
patching file include/cobalt/lcd.h
patching file include/cobalt/led.h
patching file include/cobalt/misc.h
patching file include/cobalt/net.h
patching file include/cobalt/nvram.h
patching file include/cobalt/powermode.h
patching file include/cobalt/ruler.h
patching file include/cobalt/sensors.h
patching file include/cobalt/serialnum.h
patching file include/cobalt/superio.h
patching file include/cobalt/systype.h
patching file include/cobalt/wdt.h
patching file include/linux/reboot.h
patching file init/main.c


Configuration and compilation

Code: Select all

user@host:/usr/src/linux-source-3.2$ cp ~/linux-cobalt-3.2.84-diskless.config .config
user@host:/usr/src/linux-source-3.2$ make CROSS_COMPILE=i686-unknown-linux-gnu- ARCH=i386 oldconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
*
* Restart config...
*
*
* Security options
*
Enable access key retention support (KEYS) [Y/?] y
  ENCRYPTED KEYS (ENCRYPTED_KEYS) [N/m/y/?] n
  Enable the /proc/keys file by which keys may be viewed (KEYS_DEBUG_PROC_KEYS) [N/y/?] n
Restrict unprivileged access to the kernel syslog (SECURITY_DMESG_RESTRICT) [N/y/?] n
Restrict unprivileged use of performance events (SECURITY_PERF_EVENTS_RESTRICT) [N/y/?] (NEW)
Enable different security models (SECURITY) [N/y/?] n
Enable the securityfs filesystem (SECURITYFS) [N/y/?] n
Default security module
> 1. Unix Discretionary Access Controls (DEFAULT_SECURITY_DAC)
choice[1]: 1
#
# configuration written to .config
#

user@host:/usr/src/linux-source-3.2$ make CROSS_COMPILE=i686-unknown-linux-gnu- ARCH=i386 menuconfig

user@host:/usr/src/linux-source-3.2$ time make-kpkg -j 2 --revision='1' kernel_image kernel_headers modules_image
[...]
real   16m30.247s
user   25m13.647s
sys   2m25.013s

I compiled the kernel on an AMD Athlon X2 BE-2350.

Extracting vmlinux from vmlinuz and creating bzip2 compressed file (needed by x86 Cobalt machines)

Code: Select all

user@host:/usr/src/linux-source-3.2$ sudo dpkg -i ../linux-image-3.2.84-cobalt_1_i386.deb
user@host:/usr/src/linux-source-3.2$ cd ~
user@host:~$ /usr/src/linux-source-3.2/scripts/extract-vmlinux /boot/vmlinuz-3.2.84-cobalt > ~/vmlinux
user@host:~$ bzip2 -c -9 vmlinux > vmlinux.bz2
user@host:~$ sudo mv vmlinux vmlinux.bz2 /boot
user@host:~$ sudo su -
root@host:~# cd /boot
root@host:/boot# ln -s vmlinux vmlinux-3.2.84-cobalt
root@host:/boot# ln -s vmlinux.bz2 vmlinux.bz2-3.2.84-cobalt
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

Gul-Dukat
Posts: 7
Joined: Fri Feb 10, 2017 4:55 pm

Re: Cobalt Thread

Unread postby Gul-Dukat » Sat Feb 11, 2017 2:58 am

johnnym wrote:What Cobalt machines are you using?


I have two/three Raq's. Two working Raq4's and one dead Raq3. (getting that to work is a future project, PSU is dead, but I think its more troubled, as I recall trying one of the Raq4 PSU's on it and not much happened on the console....)

I have historically used these units for DVB purposes. In recent times, i"ve swapped the DVB-T PCI card for a DVB-S PCI card as they are great for multicast streaming to my local LAN the entire mux (pid 8192). Then the PC's or STB's can "select" the tv channels they would like from the multicast stream.

My renewed drive to update this was to support some newer USB and other DVB hardware. And, well my desktop Xeon mainboard went boom and the wife wont let me replace it. I dont have anything else in the house which can accept a PCI card these days. Ive mostly got laptops or raspberry pi's etc.

johnnym wrote:I hope this is OK for Dave Studeman. For now I've uploaded:
  • the original Linux kernel v3.2.5 cobalt patch
  • the v3.2.65 cobalt patch (applies up to v3.2.84 and possibly beyond)
  • my config for v3.2.84 (enabling diskless operation, for booting from disk you first need to compile in some on-disk file system drivers!)
...to pastebin.

I also compiled a small guide for patching and compiling Linux kernel v3.2.84 for Cobalt Networks x86 machines in Debian Wheezy. This will go into a new post to this thread.


Thanks. Heaps.......To all who have contributed in the past and now. Keeping good hardware like this alive is fun.

I will give it a go this evening.

User avatar
johnnym
Donor
Donor
Posts: 196
Joined: Sun Sep 04, 2016 9:53 pm

Re: Cobalt Thread

Unread postby johnnym » Sat Feb 11, 2017 4:23 am

Gul-Dukat wrote:
johnnym wrote:What Cobalt machines are you using?


I have two/three Raq's. Two working Raq4's and one dead Raq3. (getting that to work is a future project, PSU is dead, but I think its more troubled, as I recall trying one of the Raq4 PSU's on it and not much happened on the console....)

Did the display of the RaQ 3 show the first row black and the second row blank? If yes, the firmware might be broken (see http://forums.nekochan.net/viewtopic.php?f=1&t=16730589&start=255#p7396780).

Gul-Dukat wrote:I have historically used these units for DVB purposes. In recent times, i"ve swapped the DVB-T PCI card for a DVB-S PCI card as they are great for multicast streaming to my local LAN the entire mux (pid 8192). Then the PC's or STB's can "select" the tv channels they would like from the multicast stream.

Wow, didn't knew the K6-2s (do you have K6-2s, K6-2+s or even K6-III(+)s?) were/are that capable.

Gul-Dukat wrote:And, well my desktop Xeon mainboard went boom and the wife wont let me replace it. I dont have anything else in the house which can accept a PCI card these days. Ive mostly got laptops or raspberry pi's etc.

Too bad that your Xeon machine is dead. But I assume each of your remaining machines is still faster in kernel compilation than your RaQs. I think you can also do the compilation in any Debian Wheezy for i386 installation (e.g in a virtual machine).

Gul-Dukat wrote:Keeping good hardware like this alive is fun.

Indeed! :D
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

Gul-Dukat
Posts: 7
Joined: Fri Feb 10, 2017 4:55 pm

Re: Cobalt Thread

Unread postby Gul-Dukat » Sat Feb 11, 2017 4:39 am

Gul-Dukat wrote:I will give it a go this evening.


I've not used linux-source-3.2 but rather I have decompressed the raw kernel source code file.

Code: Select all

65663948 Nov 20 09:56 linux-3.2.84.tar.xz


I Seem to have hit a few differences:

Code: Select all

cobaltDVB:/usr/src/linux# patch -p1 < ../linux-cobalt-3.2.65.patch
patching file Makefile
patching file arch/x86/Makefile
Hunk #1 succeeded at 157 (offset 3 lines).
Hunk #2 succeeded at 191 (offset 4 lines).
patching file arch/x86/configs/raq3_defconfig
patching file arch/x86/configs/raq4_defconfig
patching file arch/x86/configs/raq550_defconfig
patching file arch/x86/configs/raqxtr_defconfig
patching file arch/x86/include/asm/setup.h
patching file arch/x86/kernel/Makefile
Hunk #1 FAILED at 94.
[b]1 out of 1 hunk FAILED -- saving rejects to file arch/x86/kernel/Makefile.rej[/b]
patching file arch/x86/kernel/cobalt.c
patching file arch/x86/kernel/head_32.S
patching file arch/x86/kernel/nmi.c
patching file arch/x86/kernel/reboot.c
Hunk #2 succeeded at 614 (offset 58 lines).
Hunk #3 succeeded at 692 with fuzz 1 (offset 58 lines).
Hunk #4 succeeded at 747 (offset 64 lines).
patching file drivers/Kconfig
patching file drivers/Makefile
patching file drivers/char/misc.c
patching file drivers/char/nvram.c
patching file drivers/cobalt/Kconfig
patching file drivers/cobalt/Makefile
patching file drivers/cobalt/README
patching file drivers/cobalt/acpi.c
patching file drivers/cobalt/fans.c
patching file drivers/cobalt/i2c.c
patching file drivers/cobalt/init.c
patching file drivers/cobalt/lcd.c
patching file drivers/cobalt/led.c
patching file drivers/cobalt/net.c
patching file drivers/cobalt/powermode.c
patching file drivers/cobalt/raminfo.c
patching file drivers/cobalt/ruler.c
patching file drivers/cobalt/sensors.c
patching file drivers/cobalt/serialnum.c
patching file drivers/cobalt/systype.c
patching file drivers/cobalt/wdt.c
patching file drivers/net/ethernet/intel/Kconfig
patching file drivers/net/ethernet/intel/e100.c
patching file include/cobalt/acpi.h
patching file include/cobalt/cobalt.h
patching file include/cobalt/i2c.h
patching file include/cobalt/lcd.h
patching file include/cobalt/led.h
patching file include/cobalt/misc.h
patching file include/cobalt/net.h
patching file include/cobalt/nvram.h
patching file include/cobalt/powermode.h
patching file include/cobalt/ruler.h
patching file include/cobalt/sensors.h
patching file include/cobalt/serialnum.h
patching file include/cobalt/superio.h
patching file include/cobalt/systype.h
patching file include/cobalt/wdt.h
patching file include/linux/reboot.h
patching file init/main.c
[b]patch unexpectedly ends in middle of line[/b]
Hunk #2 succeeded at 741 with fuzz 2.


file arch/x86/kernel/Makefile.rej

Code: Select all

cobaltDVB:/usr/src/linux# cat arch/x86/kernel/Makefile.rej
--- arch/x86/kernel/Makefile    2012-02-06 09:47:00.000000000 -0800
+++ arch/x86/kernel/Makefile    2012-02-06 21:34:59.000000000 -0800
@@ -94,6 +94,8 @@
 microcode-$(CONFIG_MICROCODE_INTEL)    += microcode_intel.o
 microcode-$(CONFIG_MICROCODE_AMD)      += microcode_amd.o
 microcode-$(CONFIG_MICROCODE_XEN)      += microcode_xen.o
+obj-$(CONFIG_COBALT_RAQ)       += cobalt.o
+
 obj-$(CONFIG_MICROCODE)                        += microcode.o

 obj-$(CONFIG_X86_CHECK_BIOS_CORRUPTION) += check.o


I'll have a go at editing the patch file to adjust for the microcode_intel/amd difference to the standard microcode.o ....

stay tuned :)


Return to “Miscellaneous Operating Systems/Hardware”

Who is online

Users browsing this forum: RobhG and 1 guest