Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
DEC Alpha - boot partitions : SRM/aboot [workaround found]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Sat Aug 01, 2015 6:22 pm    Post subject: DEC Alpha - boot partitions : SRM/aboot [workaround found] Reply with quote

I'm trying to install Gentoo on an Alpha Personal Work Station 433au (Miata). The hardware is fine, boots and runs OpenVMS (8.3,) Debian (old no longer supported,) and OpenBSD 5.7 (current release.) I downloaded the Jan 3 2015 ISO for Alpha and burned it to a CD. Added an extra SCSI drive to my disc tower, and booted from the CD.

First problem: The boot runs fine until it tries to mount the source CD, which fails. Apparently there's a driver missing from the CD configuration. Solved that by plugging in an external CD drive to the USB port, and putting a second copy of the CD into that drive. (You can't boot SRM from USB. But the CD boot image is able to find and mount the USB drive once it gets running.)

Handbook for Alpha works fine until I get to the disk partitioning. It says (correctly) that the SRM console firmware needs aboot installed in the first track of the disk, and that the drive must be partitioned on an OSF/BSD disklabel rather than a DOS partition table. The instructions say to run "fdisk /dev/sda" (in my case /dev/sdd but that shouldn't matter.) Of course the drive already had a DOS partition table. It seems that fdisk can't delete that. Typing a "b" as directed by the handbook tries to create an "embedded BSD label" on disk partition 3. Trouble is, that will only let me assign boundaries within partition 3. So I went back and defined DOS partition 3 to include all of the disk. Created the BSD label on partition 3, assigned a, b, and c partitions as recommended. Wrote the labels to the disk, exited fdisk. No good, you can't create the file systems on those partitions because the OS only sees the disk as a single partition. Tried rebooting from scratch and it still looks the same.

So I used dd to blank out the first few sectors. Started "fdisk -tbsd -c=nondos /dev/sdd" hoping it would let me create the BSD disklabel. No such luck. It does come up without writing a DOS partition table, but when you give the "b" command it aborts.

Then I tried booting OpenBSD, and had it initialize a BSD disklabel on the drive ("disklabel -i /dev/sd3c") and then I partitioned the swap, root, and whole disk partitions as a, b, and c respectively. It looked right to disklabel and to sfdisk on OpenBSD.

Went back to the Gentoo CD boot, and it still doesn't see those partitions on the drive. The CD version of fdisk complains that the disklabel is absent or corrupt.

I've tried several sequences of steps, and reset the first few sectors of the drive to all zeros several times. Nothing works. The Handbook is no help, because the sequence of steps given there are not possible in this version of fdisk. You can't issue the "b" command on an uninitialized disk. It simply won't accept that.

I suspect that the sequence of steps given farther down the page, for the ARC console management firmware rather than SRM, are probably correct for ARC. But when I tried them, they still can't be used with SRM because you get to the point where aboot will be written to the drive and the installer can't do it. It complains that the label is corrupt or invalid.

I've tried Google, I've searched the forums, I've even asked on the Gentoo IRC (where there was no one who knew anything about the Alpha processor, apparently.) I'm sure this can be done, but not with the version of fdisk that is included on that CD image.

Can anyone offer clarification of the missing/scrambled instructions?


Last edited by Altivo on Wed Aug 12, 2015 2:42 am; edited 1 time in total
Back to top
View user's profile Send private message
Keruskerfuerst
Advocate
Advocate


Joined: 01 Feb 2006
Posts: 2288
Location: near Augsburg, Germany

PostPosted: Sun Aug 02, 2015 6:02 am    Post subject: Reply with quote

Can you post a detailed hardwareinfo of your computer?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7550
Location: Goose Creek SC

PostPosted: Sun Aug 02, 2015 6:13 am    Post subject: Reply with quote

Have no alpha cpu's but:
fdisk /dev/sdd
enter m
I see only
Quote:
Create a new label
g create a new empty GPT partition table
G create a new empty SGI (IRIX) partition table
o create a new empty DOS partition table
s create a new empty Sun partition table
Suggesting at least my version of fdisk has lost the ability to create a bsd label. parted or gparted will still create a bsd disk label.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Sun Aug 02, 2015 11:57 am    Post subject: Reply with quote

Keruskerfuerst wrote:
Can you post a detailed hardwareinfo of your computer?


I'm sure there are no hardware issues. Specs follow. The only modification from what DEC originally delivered is the addition of a memory stick to expand the original 512MB to 1024MB of RAM.

Digital Personal Workstation 433au
1024MB RAM, 433MHz clock, Alpha EV56 cpu
QLogic SCSI controller (PCI)
DEC 10/100MHz NIC (PCI builtin)
Elsa Gloria Synergy VGA, Permedia 2 chipset (PCI)
No ISA cards
Internal IDE CDROM (Toshiba)
Internal floppy drive
SRM BIOS (I don't have the version number at hand, but it is the latest for this machine)
Two serial ports, DEC VT220 terminal attached to /dev/ttyS0 as console
Two USB ports, Yamaha CDROM unit connected to one of them
PS/2 mouse and keyboard attached
VGA monitor on the Elsa VGA port

There is no internal hard drive, the bays are empty. Hard drives are in a separate external unit connected to the QLogic controller. External tower is hot-pluggable, contains four Seagate Cheetah drives. The fourth is the target for Gentoo (/dev/sdd) and the others have working installations of OpenVMS 8.3 (/dev/sda,) Debian 4.0 "etch" (/dev/sdb,) OpenBSD 5.7 (/dev/sdc.) The OpenBSD was just installed from internal CD last week, with no difficulty.

Here is /proc/cpuinfo:
----------------------------------
cpu : Alpha
cpu model : EV56
cpu variation : 7
cpu revision : 0
cpu serial number :
system type : Miata
system variation : 0
system revision : 0
system serial number : NI84006951
cycle frequency [Hz] : 433235087 est.
timer frequency [Hz] : 1024.00
page size [bytes] : 8192
phys. address bits : 40
max. addr. space # : 127
BogoMIPS : 848.52
kernel unaligned acc : 0 (pc=0,va=0)
user unaligned acc : 0 (pc=0,va=0)
platform string : Digital Personal WorkStation 433au
cpus detected : 1
cpus active : 1
cpu active mask : 0000000000000001
L1 Icache : 8K, 1-way, 32b line
L1 Dcache : 8K, 1-way, 32b line
L2 cache : 96K, 3-way, 64b line
L3 cache : n/a
-------------------------------------------------------------------

Here is dmesg from the Gentoo livecd boot-up:
------------------------------------------------------------------
[ 0.000000] Linux version 3.17.7-gentoo (root@monolith) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.5, pie-0.5.5) ) #1 SMP Sat Jan 3 22:52:42 UTC 2015
[ 0.000000] Booting GENERIC on Miata using machine vector Miata from SRM
[ 0.000000] Major Options: SMP LEGACY_START VERBOSE_MCHECK MAGIC_SYSRQ
[ 0.000000] Command line: root=/dev/ram0 init=/linuxrc dokeymap looptype=squashfs loop=/image.squashfs console=ttyS0 cdroot
[ 0.000000] memcluster 0, usage 1, start 0, end 236
[ 0.000000] memcluster 1, usage 0, start 236, end 131071
[ 0.000000] memcluster 2, usage 1, start 131071, end 131072
[ 0.000000] freeing pages 236:384
[ 0.000000] freeing pages 1344:131071
[ 0.000000] reserving pages 1344:1346
[ 0.000000] Initial ramdisk at: 0xfffffc003f924000 (4973264 bytes)
[ 0.000000] pci: cia revision 1 (pyxis)
[ 0.000000] SMP: 1 CPUs probed -- cpu_present_mask = 1
[ 0.000000] On node 0 totalpages: 131071
[ 0.000000] free_area_init_node: node 0, pgdat fffffc0000a1c0c0, node_mem_map fffffc0000a84000
[ 0.000000] DMA zone: 896 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 131071 pages, LIFO batch:15
[ 0.000000] PERCPU: Embedded 5 pages/cpu @fffffc000118c000 s9856 r8192 d22912 u40960
[ 0.000000] pcpu-alloc: s9856 r8192 d22912 u40960 alloc=5*8192
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130175
[ 0.000000] Kernel command line: root=/dev/ram0 init=/linuxrc dokeymap looptype=squashfs loop=/image.squashfs console=ttyS0 cdroot
[ 0.000000] PID hash table entries: 4096 (order: 2, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 1048576 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 524288 bytes)
[ 0.000000] Sorting __ex_table...
[ 0.000000] Memory: 1025296K/1048568K available (5137K kernel code, 416K rwdata, 1436K rodata, 424K init, 174K bss, 23272K reserved)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=1.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.000000] NR_IRQS:128
[ 0.000000] HWRPB cycle frequency bogus. Estimated 433235087 Hz
[ 0.002929] Console: colour VGA+ 80x25
[ 0.029296] console [ttyS0] enabled
[ 0.030273] Calibrating delay loop... 848.52 BogoMIPS (lpj=414208)
[ 0.041015] pid_max: default: 32768 minimum: 301
[ 0.041992] Mount-cache hash table entries: 2048 (order: 1, 16384 bytes)
[ 0.042968] Mountpoint-cache hash table entries: 2048 (order: 1, 16384 bytes)
[ 0.046874] SMP mode deactivated.
[ 0.050781] Brought up 1 CPUs
[ 0.052734] SMP: Total of 1 processors activated (853.77 BogoMIPS).
[ 0.055664] devtmpfs: initialized
[ 0.061523] NET: Registered protocol family 16
[ 0.064453] EISA bus registered
[ 0.065429] pci: passed tb register update test
[ 0.066406] pci: passed sg loopback i/o read test
[ 0.068359] pci: passed pte write cache snoop test
[ 0.069335] pci: failed valid tag invalid pte reload test (mcheck; workaround available)
[ 0.070312] pci: passed pci machine check test
[ 0.071289] pci: tbia workaround enabled
[ 0.072265] PCI host bridge to bus 0000:00
[ 0.073242] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 0.074218] pci_bus 0000:00: root bus resource [mem 0x00000000-0x7fffffff]
[ 0.075195] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[ 0.076171] pci 0000:00:03.0: [1011:0019] type 00 class 0x020000
[ 0.076171] pci 0000:00:03.0: reg 0x10: [io 0x9000-0x907f]
[ 0.076171] pci 0000:00:03.0: reg 0x14: [mem 0x81151000-0x8115107f]
[ 0.077148] pci 0000:00:03.0: reg 0x30: [mem 0x81100000-0x8113ffff pref]
[ 0.077148] pci 0000:00:07.0: [1080:c693] type 00 class 0x060100
[ 0.078124] pci 0000:00:07.1: [1080:c693] type 00 class 0x010180
[ 0.078124] pci 0000:00:07.1: reg 0x10: [io 0x01f0-0x01f7]
[ 0.078124] pci 0000:00:07.1: reg 0x14: [io 0x03f4-0x03f7]
[ 0.078124] pci 0000:00:07.1: reg 0x20: [io 0x90a0-0x90af]
[ 0.078124] pci 0000:00:07.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
[ 0.080078] pci 0000:00:07.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
[ 0.081054] pci 0000:00:07.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
[ 0.083007] pci 0000:00:07.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
[ 0.083984] pci 0000:00:07.2: [1080:c693] type 00 class 0x010100
[ 0.083984] pci 0000:00:07.2: reg 0x10: [io 0x0170-0x0177]
[ 0.083984] pci 0000:00:07.2: reg 0x14: [io 0x0374-0x0377]
[ 0.084960] pci 0000:00:07.2: reg 0x20: [mem 0x81140000-0x8114ffff]
[ 0.084960] pci 0000:00:07.2: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
[ 0.085937] pci 0000:00:07.2: legacy IDE quirk: reg 0x14: [io 0x03f6]
[ 0.086914] pci 0000:00:07.2: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
[ 0.087890] pci 0000:00:07.2: legacy IDE quirk: reg 0x1c: [io 0x0376]
[ 0.089843] pci 0000:00:07.3: [1080:c693] type 00 class 0x0c0310
[ 0.089843] pci 0000:00:07.3: reg 0x10: [mem 0x81150000-0x81150fff]
[ 0.090820] pci 0000:00:14.0: [1011:0024] type 01 class 0x060400
[ 0.090820] pci: enabling save/restore of SRM state
[ 0.091796] pci 0000:00:14.0: bridge configuration invalid ([bus 01-00]), reconfiguring
[ 0.093749] pci 0000:01:04.0: [1077:1020] type 00 class 0x010000
[ 0.093749] pci 0000:01:04.0: reg 0x10: [io 0x8000-0x80ff]
[ 0.093749] pci 0000:01:04.0: reg 0x14: [mem 0x81040000-0x81040fff]
[ 0.093749] pci 0000:01:04.0: reg 0x30: [mem 0x81030000-0x8103ffff pref]
[ 0.094726] pci 0000:01:09.0: [104c:3d07] type 00 class 0x030000
[ 0.094726] pci 0000:01:09.0: reg 0x10: [mem 0x81000000-0x8101ffff]
[ 0.094726] pci 0000:01:09.0: reg 0x14: [mem 0x80800000-0x80ffffff]
[ 0.094726] pci 0000:01:09.0: reg 0x18: [mem 0x80000000-0x807fffff]
[ 0.094726] pci 0000:01:09.0: reg 0x30: [mem 0x81020000-0x8102ffff pref]
[ 0.095703] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 0.095703] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01
[ 0.095703] pci 0000:00:14.0: BAR 8: assigned [mem 0x09000000-0x0a3fffff]
[ 0.096679] pci 0000:00:03.0: BAR 6: assigned [mem 0x0a400000-0x0a43ffff pref]
[ 0.097656] pci 0000:00:07.2: BAR 4: assigned [mem 0x0a440000-0x0a44ffff]
[ 0.098632] pci 0000:00:07.3: BAR 0: assigned [mem 0x0a450000-0x0a450fff]
[ 0.099609] pci 0000:00:14.0: BAR 7: assigned [io 0x8000-0x8fff]
[ 0.100585] pci 0000:00:03.0: BAR 0: assigned [io 0x9000-0x907f]
[ 0.101562] pci 0000:00:03.0: BAR 1: assigned [mem 0x0a451000-0x0a45107f]
[ 0.102539] pci 0000:00:07.1: BAR 4: assigned [io 0x9080-0x908f]
[ 0.103515] pci 0000:01:09.0: BAR 1: assigned [mem 0x09000000-0x097fffff]
[ 0.104492] pci 0000:01:09.0: BAR 2: assigned [mem 0x09800000-0x09ffffff]
[ 0.106445] pci 0000:01:09.0: BAR 0: assigned [mem 0x0a000000-0x0a01ffff]
[ 0.107421] pci 0000:01:04.0: BAR 6: assigned [mem 0x0a020000-0x0a02ffff pref]
[ 0.108398] pci 0000:01:09.0: BAR 6: assigned [mem 0x0a030000-0x0a03ffff pref]
[ 0.109374] pci 0000:01:04.0: BAR 1: assigned [mem 0x0a040000-0x0a040fff]
[ 0.110351] pci 0000:01:04.0: BAR 0: assigned [io 0x8000-0x80ff]
[ 0.111328] pci 0000:00:14.0: PCI bridge to [bus 01]
[ 0.112304] pci 0000:00:14.0: bridge window [io 0x8000-0x8fff]
[ 0.113281] pci 0000:00:14.0: bridge window [mem 0x09000000-0x0a3fffff]
[ 0.114257] pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
[ 0.114257] pci_bus 0000:00: resource 5 [mem 0x00000000-0x7fffffff]
[ 0.114257] pci_bus 0000:01: resource 0 [io 0x8000-0x8fff]
[ 0.114257] pci_bus 0000:01: resource 1 [mem 0x09000000-0x0a3fffff]
[ 0.115234] SMC37c669 Super I/O Controller found @ 0x0000000000000370
[ 0.140624] vgaarb: setting as boot device: PCI:0000:01:09.0
[ 0.140624] vgaarb: device added: PCI:0000:01:09.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.141601] vgaarb: loaded
[ 0.142578] vgaarb: bridge control possible 0000:01:09.0
[ 0.144531] SCSI subsystem initialized
[ 0.147460] libata version 3.00 loaded.
[ 0.148437] usbcore: registered new interface driver usbfs
[ 0.149413] usbcore: registered new interface driver hub
[ 0.150390] usbcore: registered new device driver usb
[ 0.208984] NET: Registered protocol family 2
[ 0.211913] TCP established hash table entries: 8192 (order: 3, 65536 bytes)
[ 0.213867] TCP bind hash table entries: 8192 (order: 4, 131072 bytes)
[ 0.214843] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.216796] TCP: reno registered
[ 0.217773] UDP hash table entries: 512 (order: 1, 16384 bytes)
[ 0.218749] UDP-Lite hash table entries: 512 (order: 1, 16384 bytes)
[ 0.220703] NET: Registered protocol family 1
[ 0.221679] PCI: CLS 64 bytes, default 64
[ 0.222656] Unpacking initramfs...
[ 8.000972] random: nonblocking pool is initialized
[ 8.218745] Freeing initrd memory: 4856K (fffffc003f924000 - fffffc003fde2000)
[ 8.222652] futex hash table entries: 256 (order: 1, 16384 bytes)
[ 8.226558] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 8.227534] msgmni has been set to 2012
[ 8.233394] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[ 8.234370] io scheduler noop registered
[ 8.235347] io scheduler deadline registered (default)
[ 8.236323] io scheduler cfq registered
[ 8.238277] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 8.240230] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 8.242183] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[ 8.247066] rtc: SRM (post-2000) epoch (2000) detected
[ 8.248042] Real Time Clock Driver v1.12b
[ 8.259761] Console: switching to colour frame buffer device 80x30
[ 8.263667] fb0: TVP4020 frame buffer device, memory = 8192K
[ 8.265620] isapnp: Scanning for PnP cards...
[ 8.616206] isapnp: No Plug & Play device found
[ 8.619136] Floppy drive(s): fd0 is 2.88M
[ 8.633784] loop: module loaded
[ 8.634761] Loading iSCSI transport class v2.0-870.
[ 8.637690] qla1280: QLA1040 found on PCI bus 1, dev 4
[ 8.645503] FDC 0 is a post-1991 82077
[ 9.432612] scsi(0:0): Resetting SCSI BUS
[ 12.437493] scsi host0: QLogic QLA1040 PCI to SCSI Host Adapter
Firmware version: 7.65.06, Driver version 3.27.1
[ 12.441399] scsi 0:0:0:0: Direct-Access SEAGATE ST336607LC 0007 PQ: 0 ANSI: 3
[ 12.443353] scsi(0:0:0:0): Sync: period 10, offset 12, Wide, Tagged queuing: depth 31
[ 12.451165] scsi 0:0:1:0: Direct-Access SEAGATE ST336607LC 0007 PQ: 0 ANSI: 3
[ 12.453118] scsi(0:0:1:0): Sync: period 10, offset 12, Wide, Tagged queuing: depth 31
[ 12.461907] scsi 0:0:2:0: Direct-Access SEAGATE ST336607LC DS09 PQ: 0 ANSI: 3
[ 12.463860] scsi(0:0:2:0): Sync: period 10, offset 12, Wide, Tagged queuing: depth 31
[ 12.473626] scsi 0:0:3:0: Direct-Access SEAGATE ST318452LC 2213 PQ: 0 ANSI: 3
[ 12.475579] scsi(0:0:3:0): Sync: period 10, offset 12, Wide, Tagged queuing: depth 31
[ 14.328117] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 14.332023] sd 0:0:0:0: [sda] 71687372 512-byte logical blocks: (36.7 GB/34.1 GiB)
[ 14.333000] sd 0:0:1:0: [sdb] 71687372 512-byte logical blocks: (36.7 GB/34.1 GiB)
[ 14.333977] sd 0:0:0:0: [sda] Write Protect is off
[ 14.334953] sd 0:0:0:0: [sda] Mode Sense: ab 00 10 08
[ 14.335930] sd 0:0:1:0: [sdb] Write Protect is off
[ 14.336906] sd 0:0:1:0: [sdb] Mode Sense: ab 00 10 08
[ 14.337883] sd 0:0:3:0: [sdd] 35566478 512-byte logical blocks: (18.2 GB/16.9 GiB)
[ 14.338859] sd 0:0:2:0: [sdc] 71132959 512-byte logical blocks: (36.4 GB/33.9 GiB)
[ 14.339836] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 14.340812] sd 0:0:3:0: [sdd] Write Protect is off
[ 14.341789] sd 0:0:3:0: [sdd] Mode Sense: a3 00 10 08
[ 14.343742] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 14.345695] sd 0:0:3:0: [sdd] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 14.347648] sd 0:0:2:0: [sdc] Write Protect is off
[ 14.348625] sd 0:0:2:0: [sdc] Mode Sense: ab 00 10 08
[ 14.350578] sd 0:0:1:0: Attached scsi generic sg1 type 0
[ 14.356437] sd 0:0:2:0: Attached scsi generic sg2 type 0
[ 14.359367] sd 0:0:3:0: Attached scsi generic sg3 type 0
[ 14.362297] PCI: Setting latency timer of device 0000:00:07.1 to 64
[ 14.371086] sd 0:0:2:0: [sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 14.374016] sdb: sdb1 sdb2 sdb3 sdb4
[ 14.375969] sda: unknown partition table
[ 14.386711] scsi host1: pata_cypress
[ 14.390617] sdd: sdd3 < sdd5 sdd6 sdd7 >
[ 14.393547] sd 0:0:0:0: [sda] Attached SCSI disk
[ 14.400383] scsi host2: pata_cypress
[ 14.402336] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0x9080 irq 14
[ 14.404289] ata2: DUMMY
[ 14.406242] Linux Tulip driver version 1.1.15 (Feb 27, 2007)
[ 14.411125] tulip0: EEPROM default media type Autosense
[ 14.412101] tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block
[ 14.413078] tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block
[ 14.414055] tulip0: Index #2 - Media 10base2 (#1) described by a 21142 Serial PHY (2) block
[ 14.415031] tulip0: Index #3 - Media AUI (#2) described by a 21142 Serial PHY (2) block
[ 14.416008] tulip0: Index #4 - Media MII (#11) described by a 21142 MII PHY (3) block
[ 14.421867] tulip0: MII transceiver #5 config 0000 status 7849 advertising 01e1
[ 14.428703] net eth0: Digital DS21142/43 Tulip rev 48 at MMIO 0xa451000, 00:00:f8:76:38:78, IRQ 24
[ 14.430656] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 14.431633] ehci-pci: EHCI PCI platform driver
[ 14.433586] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 14.434562] ohci-pci: OHCI PCI platform driver
[ 14.435539] ohci-pci 0000:00:07.3: OHCI PCI host controller
[ 14.436516] ohci-pci 0000:00:07.3: new USB bus registered, assigned bus number 1
[ 14.437492] ohci-pci 0000:00:07.3: irq 10, io mem 0x0a450000
[ 14.439445] sd 0:0:1:0: [sdb] Attached SCSI disk
[ 14.440422] sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11
[ 14.447258] sd 0:0:3:0: [sdd] Attached SCSI disk
[ 14.458976] sd 0:0:2:0: [sdc] Attached SCSI disk
[ 14.495109] hub 1-0:1.0: USB hub found
[ 14.496086] hub 1-0:1.0: 2 ports detected
[ 14.499016] uhci_hcd: USB Universal Host Controller Interface driver
[ 14.505851] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 14.507805] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 14.510734] mousedev: PS/2 mouse device common for all mice
[ 14.513664] platform eisa.0: Probing EISA bus 0
[ 14.518547] usbcore: registered new interface driver usbhid
[ 14.519523] usbhid: USB HID core driver
[ 14.520500] TCP: cubic registered
[ 14.521476] NET: Registered protocol family 17
[ 14.523430] 8021q: 802.1Q VLAN Support v1.8
[ 14.524406] Key type dns_resolver registered
[ 14.590812] Freeing unused kernel memory: 424K (fffffc000097e000 - fffffc00009e8000)
[ 14.793937] input: AT Raw Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 14.861320] usb 1-2: new full-speed USB device number 2 using ohci-pci
[ 16.327140] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input2
[ 21.777332] scsi: <fdomain> Detection failed (no card)
[ 21.822254] GDT-HA: Storage RAID Controller Driver. Version: 3.05
[ 22.040027] qlogicfas: no cards were found, please specify I/O address and IRQ using iobase= and irq= options
[ 22.740222] sym53c416.c: Version 1.0.0-ac
[ 22.875964] Fusion MPT base driver 3.04.20
[ 22.875964] Copyright (c) 1999-2008 LSI Corporation
[ 22.958972] Fusion MPT SPI Host driver 3.04.20
[ 23.003894] Fusion MPT FC Host driver 3.04.20
[ 23.051746] Fusion MPT SAS Host driver 3.04.20
[ 23.097644] 3ware Storage Controller device driver for Linux v1.26.02.003.
[ 23.142566] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
[ 23.236316] HP CISS Driver (v 3.6.26)
[ 23.433581] Adaptec aacraid driver 1.2-0[30300]-ms
[ 23.520495] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
[ 23.529284] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
[ 23.616198] megasas: 06.803.01.00-rc1 Mon. Mar. 10 17:00:00 PDT 2014
[ 23.714831] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.07.00.08-k.
[ 23.854479] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
[ 24.184557] usb-storage 1-2:1.0: USB Mass Storage device detected
[ 24.188464] scsi host3: usb-storage 1-2:1.0
[ 24.189440] usbcore: registered new interface driver usb-storage
[ 25.200182] scsi 3:0:0:0: CD-ROM YAMAHA CRW-F1E 1.0f PQ: 0 ANSI: 2
[ 25.235338] sr 3:0:0:0: [sr0] scsi3-mmc drive: 44x/44x writer cd/rw xa/form2 cdda tray
[ 25.235338] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 25.237291] sr 3:0:0:0: Attached scsi CD-ROM sr0
[ 25.238268] sr 3:0:0:0: Attached scsi generic sg4 type 5
[ 25.572252] device-mapper: uevent: version 1.0.3
[ 25.573229] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[ 25.980455] md: raid0 personality registered for level 0
[ 26.023424] md: raid1 personality registered for level 1
[ 26.066392] xor: measuring software checksum speed
[ 26.076158] 8regs : 475.136 MB/sec
[ 26.085924] 32regs : 729.088 MB/sec
[ 26.095689] alpha : 876.544 MB/sec
[ 26.105455] alpha prefetch: 770.048 MB/sec
[ 26.105455] xor: using function: alpha (876.544 MB/sec)
[ 26.136705] raid6: int64x1 160 MB/s
[ 26.153306] raid6: int64x2 232 MB/s
[ 26.169908] raid6: int64x4 264 MB/s
[ 26.186510] raid6: int64x8 212 MB/s
[ 26.186510] raid6: using algorithm int64x4 (264 MB/s)
[ 26.186510] raid6: using intx1 recovery algorithm
[ 26.205064] md: raid6 personality registered for level 6
[ 26.205064] md: raid5 personality registered for level 5
[ 26.205064] md: raid4 personality registered for level 4
[ 26.371080] md: raid10 personality registered for level 10
[ 26.411119] md: linear personality registered for level -1
[ 26.845689] JFS: nTxBlock = 4025, nTxLock = 32205
[ 26.942369] RPC: Registered named UNIX socket transport module.
[ 26.942369] RPC: Registered udp transport module.
[ 26.942369] RPC: Registered tcp transport module.
[ 26.942369] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 27.173814] fuse init (API version 7.23)
[ 27.247056] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[ 27.247056] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 27.291978] pps_core: LinuxPPS API ver. 1 registered
[ 27.291978] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 27.295884] PTP clock support registered
[ 33.027326] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 33.042951] ISO 9660 Extensions: RRIP_1991A
[ 149.892501] systemd-udevd[9763]: starting version 216
[ 151.756758] tulip 0000:00:03.0 enp0s3: renamed from eth0
[ 151.767500] systemd-udevd[9776]: renamed network interface eth0 to enp0s3
[ 158.383707] end_request: I/O error, dev fd0, sector 0
[ 158.383707] floppy: error -5 while reading block 0
[ 173.652254] warning: process `hwsetup' used the deprecated sysctl system call with 1.23.
[ 196.162008] NET: Registered protocol family 10
[ 205.773332] net enp0s3: Setting half-duplex based on MII#5 link partner capability of 0021
-----------------------------------------------------------------


Last edited by Altivo on Sat Aug 15, 2015 9:34 am; edited 1 time in total
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Sun Aug 02, 2015 12:15 pm    Post subject: Reply with quote

DONAHUE wrote:
Have no alpha cpu's but:
fdisk /dev/sdd
enter m
I see only
Quote:
Create a new label
g create a new empty GPT partition table
G create a new empty SGI (IRIX) partition table
o create a new empty DOS partition table
s create a new empty Sun partition table
Suggesting at least my version of fdisk has lost the ability to create a bsd label. parted or gparted will still create a bsd disk label.


Yes, that's what the fdisk in the LiveCD shows. Here's the version information.

#fdisk -v
fdisk from util-linux 2.24.1

This fdisk clearly does not understand a root BSD disklabel. It is capable of embedding a BSD label into a DOS partition, but will not read or write one for the whole drive. It cannot read the partition tables on the other three drives, all of which are working correctly.

BTW, the OpenBSD drive (/dev/sdc) is recognized by the Gentoo LiveCD and the BSD partitions are individually mountable as /dev/sdc1 through /dev/sdc11, so Gentoo itself is able to read and process the BSD label. Apparently the fdisk utility being included on the LiveCD has been changed upstream so that it lost the BSD capability.

I considered using gparted on another machine to set up the drive, and I may have to do that, but it will be messy as my other running boxes have no SCSI interface. I'll have to pull another Alpha out of storage (DS10, big thing in two cabinets) or put a SCSI card into an Intel box.

The LiveCD system doesn't seem to be able to emerge gparted ("emerge command not found") so that is apparently not a solution. As I said in the original message, I tried initializing and partitioning the drive on OpenBSD, but that wasn't successful. I may try that again. The Debian installation doesn't have gparted installed and I'm not sure the packages for Lenny are still available.

I went to gparted.org to look at the manual there, and though they hint that gparted will install other partition formats in place of the MSDOS table, they give no details at all. Not very helpful.
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Sun Aug 02, 2015 3:38 pm    Post subject: Reply with quote

Current status: restoring the tar backup I made of the original failed install.

I rebooted to OpenBSD, and erased the first few blocks of the drive:

Code:
# dd bs=1024 if=/dev/zero of=/dev/sd3a count=8

Then I used disklabel to generate a new label and then edit it to the desired partitions:

Code:
# disklabel -Ac sd3
# disklabel -E sd3

Wrote the revised label to the drive. Rebooted with the Gentoo LiveCD.

Did NOT let fdisk touch the drive again. I think this is essential. The fdisk program will rewrite a DOS partition table, destroying the BSD setup.

Initialized the 3 partitions. (Do not touch /dev/sdd3, as that is the BSD c: partition that covers the entire disk.)

Code:
# mkswap /dev/sdd1
# mkfs.ext2 /dev/sdd2
# mkfs.ext3 /dev/sdd4

I am now restoring my backup to save going through the configuration and kernel build again. I'll chroot to the new setup and see if I can install the aboot bootstrap and boot from it.

Will report results in a couple of hours.

It looks to me as if a different fdisk or else a separate program like disklabel must be added to the LiveCD. Also, the instructions in the Alpha version of the Handbook need clarification. The instruction part I can possibly help with.
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Sun Aug 02, 2015 5:12 pm    Post subject: Reply with quote

Much, much closer, but still not successful.

All steps completed, through configuring and installing the aboot loader. (Yes, I altered the swriteboot and abootconf commands to get the correct drive /dev/sdd and partition 2, which should be equivalent to BSD partition b, right?)

    Digital Personal WorkStation 433au
    Console V7.2-1 Mar 6 2000 14:47:02
    >>>boot dka3
    ...
    reading 163 blocks from dka300.3.0.1004.0
    bootstrap code read in
    base = 1d8000, image start = 0, image_bytes = 14600
    initializing HWRPB at 2000
    initializing page table at 1ca000
    initializing machine state
    setting affinity to the primary CPU
    jumping to the bootstrap code
    aboot: Linux/Alpha SRM bootstrap loader version 1.0_pre20040408
    aboot: switching to OSF/1 PALcode version 1.22
    aboot: booting from device 'SCSI 0 1004 0 3 300 0 0'
    aboot: valid disklabel found: 16 partitions.
    Welcome to aboot 1.0_pre20040408
    Commands:
    [menu here]
    aboot>


Clearly we are on the right device, the disklabel is valid and readable, and the setup seems correct. Using the menu to query the boot options or the contents of the current partition produces this:

    aboot: don't know how to mount partition 2 (filesystem type 17)
    Partition 2 is invalid. Please specify another with 'p'
    aboot>


There are only 4 actual partitions defined. Partition 1 (a) gives the same message but with filesystem type 1 (swap.) This is correct. Partition 3 (c) gives the same message but with filesystem type 0 (unused.) This is correct. Partition 4 (d) gives the same message with filesystem type 17 again.

In the OpenBSD system, I set the disklabel to have file type "ext2fs" for partitions 2 and 4. Partition 2 is /boot and partition 4 is the root /. Evidently, OpenBSD used code 17 for those, when I think it should be 8. So now I have to figure out how to change just that value in the BSD disklabel. I can't use fdisk, we've pretty much established that it will corrupt the label. I may be able to use OpenBSD, but I don't yet know what value to insert for file system type to get the desired code. I pray I don't have to use some raw disk editor to make the change when I'm this close to being operational.

Suggestions welcome. I'm still researching.
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Sun Aug 02, 2015 10:06 pm    Post subject: Reply with quote

Successful boot at last!

This is not a suitable workaround to recommend in general, though. It's a massive, ugly kludge. Something needs fixing. A lot of things, I think.

What I had to do to get the disklabel functional was create it on an OpenBSD system, define my partitions as desired, and tell OpenBSD that the partition type for the root and boot partitions was "MSDOS". I had to read the /usr/include/sys/disklabel.h file on OpenBSD to figure out that this would place a value of 8 into the FS_TYPE field for the partition. Abortive experiments with fdisk while trying to get this working showed that 8 is apparently interpreted as "ext2" by Gentoo and aboot. With that change, aboot is able to find the /boot directory, and the /etc/aboot.conf file, and it can load a kernel and boot.

Most people, even the rare ones who are running Alpha hardware, are not going to have OpenBSD handy to create this disklabel. It is very clear that the fdisk utility included in the Alpha LiveCD configuration is (for whatever reason) unable to deal properly or even benignly with BSD disk labels.

As an experienced technical writer (now retired) I will be glad to volunteer to rewrite relevant sections of the Alpha Handbook to make this all clearer, but first a replacement for fdisk must be found so that correct instructions can be determined for those who have an SRM console. In case there is any doubt, SRM is generally much preferred over ARC. The SRM firmware allows some primitive debugging, interactive booting, and will boot many different systems and devices. ARC was really designed just to boot Windows NT, with very little interaction from the user. Unfortunately, many of the later Alpha workstations that sold for lower prices were designed primarily to run 64-bit Windows NT and came with the ARC loader. (Loader is what it really is, not a true console command shell.) That's why systems like Gentoo should support both SRM and ARC.

I can't say whether the ARC instructions in the Handbook are correct. They may well be. Both of my Alpha systems have SRM, however, and the Handbook instructions as they now stand are not usable to get Gentoo installed for SRM.

Thanks to the folks here who tried to help. I don't know where to escalate this issue. I guess it could be called a "bug" though, so should it be a bug report?
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Wed Aug 05, 2015 12:11 pm    Post subject: Reply with quote

Footnote, in case anyone is paying attention.

The version of fdisk included on the 20150103 Alpha LiveCD is 2.24. This version is brain-dead when it comes to BSD disk labels, and therefore cannot be used to initialize disks for booting on the Alpha with SRM console.

The version of fdisk included in Debian 4.0 (obselete stable, "etch") is 2.12r. This version is capable of reading and writing a proper BSD root label. In fact, the copy of fdisk included in my working Alpha install of Debian runs correctly under Gentoo 4.0.5 and can be used there.

Somewhere between 2.12 and 2.24, fdisk has been lobotomized. I have no idea whether this was intentional, or accidental, but it needs to be repaired. And at least for the Alpha, an older, functional version of fdisk is essential.
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 376

PostPosted: Fri Aug 07, 2015 2:25 am    Post subject: Reply with quote

Wow, you've gone through a lot to get Gentoo installed on your alpha. I'm impressed. :)

It's disappointing that people on IRC weren't able to direct you to the #gentoo-alpha IRC channel. Join us there.

I'll do some research and see if I can figure out what happened to fdisk.
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Fri Aug 07, 2015 10:12 am    Post subject: Reply with quote

Thanks for letting me know that someone is listening. I think the real disappointment for me is the realization that this was released eight months ago and no one had caught the problem yet. That suggests that no one is doing new installations on Alpha hardware. And that news is indeed sad.

I have so far been unable to create a working kernel, too. I guess I need to start another thread on that. After several attempts I finally was able to get configurations to compile and link, but they either lock up without error message or arrive at a kernel panic when trying to boot.

Fortunately I was able to copy the preconfigured kernel from the installation media and I'm up and running with that. It's about 30% bigger than I need, and lacks a couple of features I would like, but at least it's functional. The worst flaw is its apparent inability to activate the framebuffer consoles properly on my Elsa Gloria Synergy graphics card. OpenVMS, OpenBSD, and Debian all do this successfully, so the hardware is not a problem. The card is a Permedia 2 chip set, and was sold by DEC for these workstations with the Miata motherboard config.
Back to top
View user's profile Send private message
mattst88
Developer
Developer


Joined: 28 Oct 2004
Posts: 376

PostPosted: Wed Aug 19, 2015 5:42 am    Post subject: Reply with quote

I dug in the util-linux git tree, and indeed a bunch of code changed in fdisk between v2.22 and v2.23. I emailed util-linux@vger.kernel.org and asked, and here was (my quoted message and) the reply from the developer:

Quote:
On Thu, Aug 06, 2015 at 07:34:40PM -0700, Matt Turner wrote:
> I'm not able to figure out how to make a BSD disklabel in fdisk since v2.23.
>
> Gentoo's installation guide describes the process of partitioning a
> disk for SRM/Alpha [1]. How should one do this now?
>
> With my distro's util-linux-2.25 I don't see any option that resembles
> BSD disklabels -- I see only
>
> Create a new label
> g create a new empty GPT partition table
> G create a new empty SGI (IRIX) partition table
> o create a new empty DOS partition table
> s create a new empty Sun partition table
>
> What am I missing?

You have to create a DOS (MBR) label first, and then there is

DOS (MBR)
a toggle a bootable flag
b edit nested BSD disklabel
c toggle the dos compatibility flag


For example:

# fdisk /dev/sdc
...
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-1023999, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-1023999, default 1023999):

Created a new partition 1 of type 'Linux' and of size 499 MiB.
...
Command (m for help): t <----!!!
Partition type (type L to list all types): a5
Changed type of partition 'Linux' to 'FreeBSD'.
...
Command (m for help): b <----!!!
The device /dev/sdc1 does not contain BSD disklabel.

Do you want to create a BSD disklabel? [Y]es/[N]o: y
...
Command (m for help): p
...
Slice Start End Sectors Size Type Fsize Bsize Cpg
c 2048 1023999 1021952 499M unused 0 0 0
d 0 1023059 1023060 499.6M unused 0 0 0


Could you give that a try?

Looks less intuitive than before...
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Wed Aug 19, 2015 11:41 am    Post subject: Reply with quote

Not only is it less intuitive, I'm not sure it will work. If I understand what they are doing, I suspect that aboot will reject the drive. I tried something similar, but it's been a couple of weeks and I didn't keep the notes.

Yes, I can test this out. I'll have to swap another drive into the machine and see if I can initialize and then boot from it.

I'll post results here, it may take a day or so.
_________________
Have patience with me, I'm only half-baked.
--Altivo
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Thu Aug 20, 2015 1:39 pm    Post subject: Reply with quote

Short answer:

This recommended procedure does not work.

Longer answer:

First, it is necessary to make sure that the suggested single "DOS" partition of type a5 (FreeBSD) gets written to the disk before you exit. On the first attempt, I did exactly what the instructions said, then created my desired BSD paritions, used "w" to write the label followed by "q" to exit fdisk.

The embedded BSD label was written, but the DOS partition table was not. Even after a reboot, both Gentoo and fdisk insisted that the disk had no label and was unpartitioned.

Second attempt, I used "w" to write the DOS partition information after creating the whole disk partition of type FreeBSD. Then I restarted fdisk (it exits and re-syncs after the "w" command at that level) and went to make my BSD partitions. Used "w" from within the BSD submenu, then "r" to return to the DOS level, and "q" to quit. Result: Even after a reboot, Gentoo sees only one partition, /dev/sdc1. This means it is not possible to initialize the file systems on the individual BSD partitions and will not be possible to mount them. Neither OpenBSD nor Debian is able to see these "embedded" partitions, and I assume they must be a FreeBSD analog for the DOS "extended" partition trick. FreeBSD might see them, but the tools I have available do not recognize them. This is not going to work with SRM/aboot if it doesn't work in Gentoo or OpenBSD.

My guess is that somewhere along the road, someone thought that FreeBSD==BSD but this is not always true. I had never heard of this "embedded" disklabel concept, and my old BSD UNIX manuals don't recognize it either. The label required must follow the OSF/1 standard, which was in turn drawn from (I think) BSD 3 or 4. Aboot was based on boot technology originally created to boot OSF/1 on the Alpha, and the firmware in these machines was designed to boot OSF/1 as an option. (OSF/1 went on to become HPUX and Tru64 UNIX, as I understand it.)

While I have a spare disk installed, I'm going to try something else and will report back on the results. But I still conclude that the current version of fdisk is damaged and unusable for our purposes when DEC/Compaq/HP Alpha hardware is involved.
_________________
Have patience with me, I'm only half-baked.
--Altivo
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Thu Aug 20, 2015 3:18 pm    Post subject: Reply with quote

So, I wanted to try a Sun disklabel to see whether it would work. It didn't. Gentoo doesn't see the partitions on that either.

Then I tried the GPT disklabel, but couldn't find a way to align that with the BSD structure either, though Gentoo does see the partitions in that one.

Finally I went back to Debian 4.0 "etch" and initialized the drive following the exact instructions in the Gentoo Handbook for Alpha. This is fdisk version 2.12r, and it works exactly as described in the Handbook. I initialized the ext2 (for /boot) and ext3 (for root) file systems on the appropriate partitions, and made the swap partition, ignoring the third partition which is that BSD oddity, a whole disk partition that overlaps all others.

Then I used Debian to copy the contents of my working boot and root partitions over to the new drive.

Rebooted Gentoo, and used swriteboot to put the aboot program in the boot sectors of the new drive.

Then I shut down and booted from the new drive. This works perfectly, and the new running system is a clone of what I had on my working drive.

Again the conclusion: Older versions of fdisk do successfully create a disklabel that can be used by Gentoo, Debian, and the Alpha SRM/aboot bootstrap. The current version of fdisk is not capable of this operation. An "embedded" BSD label does not work with either Gentoo or SRM/aboot.
_________________
Have patience with me, I'm only half-baked.
--Altivo
Back to top
View user's profile Send private message
alphahere
n00b
n00b


Joined: 09 Sep 2015
Posts: 1

PostPosted: Wed Sep 09, 2015 11:12 pm    Post subject: Reply with quote

Installation notes on Alpha - COMPAQ Professional Workstation XP1000

I can confirm what the previous poster noted: Creation of bsd disklabel as recommended in the previous posts in a partition (/dev/sda1) is not recognized by linux. fdisk is unable to create a bsd disklabel for the entire drive (/dev/sda).

A quick work around is the following

# parted
(parted) mktable bsd
(parted) q

parted is on the installation CD and will make a correct bsd disklabel for the whole disk. Then I used fdisk to partition the disk. "fdisk" did see the bsd disklabel created with "parted". This work well. The was done on a drive without any partition table. One probably could use parted for the whole drive but I prefer fdisk.

Repeat the current version of fdisk on the installation CD does not make the correct BSD disklabel for installation or disk setup. However, one can use parted to create the BSD disklabel and then use fdisk. Hopefully fdisk will be fixed.

So far everything is working well and compiled and installed kernel 4.2 without any problems expect one small change.

https://lkml.org/lkml/2012/11/11/183

Hope this helps someone that is trying to install gentoo on dec alpha hardware.
Back to top
View user's profile Send private message
Maquis196
n00b
n00b


Joined: 02 Apr 2003
Posts: 58
Location: London

PostPosted: Mon Apr 04, 2016 10:58 am    Post subject: Reply with quote

I never ran into these issues when i installed gentoo on my alpha sometime a year ago. The only issue I have is with Xorg server. Anyone here able to run X on their alpha out of interest?

I've since been trying to get debian 5 installed without too much luck I might add. Still, good to see Kernel 4 running on Alpha!
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Mon Apr 04, 2016 3:56 pm    Post subject: Reply with quote

The aboot issues only affect hardware models that require SRM console for booting. Machines that were originally intended to boot Windows NT will, presumably, install Gentoo successfully.
_________________
Have patience with me, I'm only half-baked.
--Altivo
Back to top
View user's profile Send private message
Ivan The Viking
n00b
n00b


Joined: 14 Apr 2003
Posts: 71
Location: Connecticut, USA

PostPosted: Mon Dec 19, 2016 9:58 pm    Post subject: Reply with quote

Strange as hell this problem you have on archaic hardware I happen to love!

I did an reinstall on my ev56 LX164 alpha about a year ago and didn't run into any issues making the BSD disk label and partitions with the liveCD I had for the machine using fdisk. I think the disc was from 2012 or so?
Parted seems to be a lackluster replacement at best.

Granted this SRM and Alpha stuff is becoming niche knowledge, but the livecd should work.

I'll check the latest iso and confirm I too see the shoddy behavior.

Btw, 4.8 kernels work just fine on the LX164 as well, they just take forever to compile!
Back to top
View user's profile Send private message
Altivo
n00b
n00b


Joined: 01 Aug 2015
Posts: 49
Location: Northern Illinois

PostPosted: Mon Dec 19, 2016 10:55 pm    Post subject: Reply with quote

A LiveCD from 2012 is probably fine. This problem was introduced somewhere later than that, evidently when fdisk was revised by someone who did not understand the nature of the BSD disk label. Note too, that this thread dates back more than a year and a formal problem report was filed, so the most recent LiveCD may in fact have the problem fixed. I haven't checked that.
_________________
Have patience with me, I'm only half-baked.
--Altivo
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum