[-- Attachment #1: Type: text/plain, Size: 1774 bytes --] Hi, I'm trying to install 9legacy on a ThinkPad X60. I'm running 9front on another machine, but I would like to explore 9legacy (or vanilla Plan 9) more thoroughly. I've managed to serve 9legacy from a USB drive, however, any changes are obviously lost whenever I reboot. I don't receive any install prompt on boot to install the OS to the internal hard drive. It recognises disks sdB0 and sdB1, but I'm only asked whether to start a terminal or cpu kernel or to do it manually. I've seen in various places (like here <https://0x783czar.files.wordpress.com/2012/05/1-install-boot.jpg>) that booting from CD gives an option to install from CD. Terminal option (default selection) works, cpu doesn't and I couldn't find any useful information to even attempt it manually. Would it be wise to boot a terminal kernel and dd the image from the USB over to the hard drive? This may be outright ludicrous, so please excuse my naiveness. I've also tried to boot it from a CD, but I always get stuck at the 'Boot from:' prompt after receiving the following error, so I don't even get to a startup menu: [...] disks: sdC0 trying sdC0...dosinit: can't open #S/sdC0/9fat dosinit #S/sdC0/9fat failed Here it seems to only recognise the internal hard drive (sdC0). I've encountered the same problem when installing vanilla Plan 9 from Bell Labs, but none of the suggestions in the Plan 9 troubleshooting guide work. Has anyone encountered similar problems before or any ideas for how I could resolve this issue? Thank you! --yakku ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M24592fa76ae34908a64fcc8f Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 7505 bytes --]
I think I can help you, but right now is a bad moment, maybe nag me over the weekend in private mail? I am running 9front on a T61 I acquired specifically, but I did actually install 9legacy and your problem seems familiar enough that I can at least compare notes with you. Lucio. PS: your message landed in SPAM, I'm not sure why GMail felt it ought to do that. On 1/20/22, yakkuliste@vusra.com <yakkuliste@vusra.com> wrote: > Hi, I'm trying to install 9legacy on a ThinkPad X60. I'm running 9front on > another machine, but I would like to explore 9legacy (or vanilla Plan 9) > more thoroughly. > > I've managed to serve 9legacy from a USB drive, however, any changes are > obviously lost whenever I reboot. I don't receive any install prompt on boot > to install the OS to the internal hard drive. It recognises disks sdB0 and > sdB1, but I'm only asked whether to start a terminal or cpu kernel or to do > it manually. I've seen in various places (like here > <https://0x783czar.files.wordpress.com/2012/05/1-install-boot.jpg>) that > booting from CD gives an option to install from CD. Terminal option (default > selection) works, cpu doesn't and I couldn't find any useful information to > even attempt it manually. Would it be wise to boot a terminal kernel and dd > the image from the USB over to the hard drive? This may be outright > ludicrous, so please excuse my naiveness. > > I've also tried to boot it from a CD, but I always get stuck at the 'Boot > from:' prompt after receiving the following error, so I don't even get to a > startup menu: > > [...] > disks: sdC0 > trying sdC0...dosinit: can't open #S/sdC0/9fat > dosinit #S/sdC0/9fat failed > Here it seems to only recognise the internal hard drive (sdC0). I've > encountered the same problem when installing vanilla Plan 9 from Bell Labs, > but none of the suggestions in the Plan 9 troubleshooting guide work. > > Has anyone encountered similar problems before or any ideas for how I could > resolve this issue? Thank you! > > --yakku -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Ma03f2e0f63147be5b230c6d8 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> I've also tried to boot it from a CD, but I always get stuck at the 'Boot from:' prompt Try sdC0!cdboot!9pcflop.gz And local!/boot/bzroot for the root filesystem prompt. If your hard drive is configured in AHCI mode by the BIOS, it should be seen as sdE0. If it's in ATA compatibility mode, it should be sdC0 and the CD might be seen as sdD0. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M7d3acb4b97fc1d07b04a2a58 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --] Thanks Lucio & Richard. I've tried to boot via CD again (mind it's from a USB CD drive in case that makes any difference), but so far no success: PBSR...0000 F5FD 0000 00B2 Plan 9 from Bell Labspcirouting: PCI.0.31.2 at pin 2 link 96 irq 11 disk loader cpu0: 1662Mhz GenuineIntel P6 (cpuid: AX 0x06EC DX 0xBFE9FBFF) ELCR: 0800 497M memory: 497M kernel data, 0M user, 18M swap found partition #S/sdC0/data 0 123,091,920 disks: sdC0 trying sdC0...dosinit: can't open #S/sdC0/9fat dosinit #S/sdC0/9fat failed Boot from: sdC0!cdboot!9pcflop.gz dosinit: can't open #S/sdC0/cdboot dosinit #S/sdC0/cdboot failed Boot from: sdD0!cdboot!9pcflop.gz dosinit: can't open #S/sdD0/cdboot dosinit #S/sdD0/cdboot failed Boot from: local!/boot/bzroot can't open partition #S/local//boot/bzroot Boot from: local!boot/bzroot can't open partition #S/local/boot/bzroot ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Mb8683148f4648b349adb5e06 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 2080 bytes --]
> I've tried to boot via CD again (mind it's from a USB CD drive > in case that makes any difference) Yes, that makes a difference. It may appear as sdB0 or sdB1. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M55a257ec05c874c88956ab89 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 456 bytes --] On Friday, 21 January 2022, at 1:21 PM, Richard Miller wrote: > It may appear as sdB0 or sdB1. Sorry that doesn't seem to work either. I've tried sdB0, sdB1, sdC0, sdC1, sdD0, sdD1, sdE0, sdE1 . . . but the issue persists. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Mb4ea931e91ba25677d2bb074 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 1057 bytes --]
> Sorry that doesn't seem to work either. I've tried sdB0, sdB1, > sdC0, sdC1, sdD0, sdD1, sdE0, sdE1 . . . but the issue persists. That appears to be a dead end. To answer your earlier question, you could use dd (or pump(1)) to copy the usb image to your hard drive, if you're happy to sacrifice all the existing partitions on the hard drive. Or, for more control over the final configuration, you could create an empty fossil partition on the hard drive and copy the usb filesystem contents to it, using mkfs | mkext or replica/pull. Alternatively, I have an experimental 4e/9legacy installer which runs from a usb flash drive instead of a cdrom. It's been used successfully on an X230 and an X60s. If you get in touch with me off-list, I can give you a copy and some instructions. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M4fcaebc812cb6735b5e11144 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
The following works on 9front: Escape to an rc shell by typing !rc at the boot prompt. Then type ls '#S' This will list all devices the storage device, sd(3), sees which includes CD/DVD, ATA, SATA, and SCSI drives. You can also run cat '#S/sdctl' which will give you more information about the controllers. See: http://man.postnix.pw/plan_9/3/sd On Fri, Jan 21, 2022 at 8:34 AM yakkuliste via 9fans <9fans@9fans.net> wrote: > > On Friday, 21 January 2022, at 1:21 PM, Richard Miller wrote: > > It may appear as sdB0 or sdB1. > > > Sorry that doesn't seem to work either. I've tried sdB0, sdB1, > sdC0, sdC1, sdD0, sdD1, sdE0, sdE1 . . . but the issue persists. > 9fans / 9fans / see discussions + participants + delivery options Permalink ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Maf260023febf546d4b14232a Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Hello Yakku - I couldn't reply to the email you sent me off-list. The returned error was "User unknown in virtual mailbox table" -- Richard ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M6db08da236580ae316905718 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 762 bytes --] On Friday, 21 January 2022, at 2:02 PM, Thaddeus Woskowiak wrote: > Escape to an rc shell by typing !rc at the boot prompt. Thanks for the pointer Thaddeus. I've tried, but it doesn't work at boot prompt in 9legacy. It only works in parts of the install script. On Friday, 21 January 2022, at 2:01 PM, Richard Miller wrote: > I can give you a copy and some instructions. Thank you very much Richard, as per off-list email, it worked a treat on the X60s. Let's see if we can scrub up the X60 and get it going there as well. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M6b5fb4562e239ca53ffbaf24 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 1436 bytes --]
On Sat, Jan 22, 2022 at 10:32 AM yakkuliste via 9fans <9fans@9fans.net> wrote: > > On Friday, 21 January 2022, at 2:02 PM, Thaddeus Woskowiak wrote: > > Escape to an rc shell by typing !rc at the boot prompt. > > > Thanks for the pointer Thaddeus. I've tried, but it doesn't work at boot prompt in 9legacy. It only works in parts of the install script. Hmmmm. That is disappointing. I don't have a 9legacy install at the moment, but can someone confirm if !rc was inherited from plan 9 or unique to 9front? ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Me3c18ab38d5b71b86d587b82 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --] why not mount the .iso and scrap the project... worked for me and @#m is always a good prefix to try... its all in code boyz (& girlz...)... all in code... and boot it off your game machine? there are a myriad of games machines now... and most of them work quite successfully... a lot of them were built in countries around the world.... /c:2022(i think???) On Sat, Jan 22, 2022 at 4:08 PM Thaddeus Woskowiak <tswoskowiak@gmail.com> wrote: > On Sat, Jan 22, 2022 at 10:32 AM yakkuliste via 9fans <9fans@9fans.net> > wrote: > > > > On Friday, 21 January 2022, at 2:02 PM, Thaddeus Woskowiak wrote: > > > > Escape to an rc shell by typing !rc at the boot prompt. > > > > > > Thanks for the pointer Thaddeus. I've tried, but it doesn't work at boot > prompt in 9legacy. It only works in parts of the install script. > > Hmmmm. That is disappointing. I don't have a 9legacy install at the > moment, but can someone confirm if !rc was inherited from plan 9 or > unique to 9front? ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Mc51fb080099b22b36a6c1db6 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 2605 bytes --]
> On 22 Jan 2022, at 17:08, Thaddeus Woskowiak <tswoskowiak@gmail.com> wrote: > > On Sat, Jan 22, 2022 at 10:32 AM yakkuliste via 9fans <9fans@9fans.net> wrote: >> >> On Friday, 21 January 2022, at 2:02 PM, Thaddeus Woskowiak wrote: >> >> Escape to an rc shell by typing !rc at the boot prompt. >> >> >> Thanks for the pointer Thaddeus. I've tried, but it doesn't work at boot prompt in 9legacy. It only works in parts of the install script. > > Hmmmm. That is disappointing. I don't have a 9legacy install at the > moment, but can someone confirm if !rc was inherited from plan 9 or > unique to 9front? !rc (and the rest of the boot) is one of the first things implemented uniquely by 9front. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M90addd59e061df80dcb40db9 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> !rc (and the rest of the boot) is one of the first things implemented uniquely by 9front. I think there's a little bit of confusion about different stages of booting. The 9boot program loads the kernel. The original Plan 9 9boot is driven by configuration variables in a plan9.ini file. Cinap's rewritten 9boot adds the capability of interactively changing configuration variables from the console before loading the kernel. That's really useful, especially when experimenting with new kernels or new hardware. But 9boot does not contain a shell or a built-in file system, so it doesn't allow you to type !rc and get an interactive shell. Once the kernel is loaded, the first thing it does is to execute the command /boot/boot from a small root filesystem which is built into the kernel. The main job of /boot/boot is to attach to the real root filesystem (on a local device or from a network server) and execute /$cputype/init to start the system. Historically the usual case is for /boot/boot to be a specialised program built from C source in /sys/src/9/boot. But it has always been possible to configure a kernel with a shell script as /boot/boot - see for example /sys/lib/sysconfig/ppc/boot for the PowerPC, or /sys/src/9/bcm/bootwifi.rc for a Raspberry Pi accessing its root file server via wifi. So, using a shell script as /boot/boot is not unique to 9front. But with 9front, it has become the default. This means there's always a shell inside the kernel, along with a few commands, ready to use interactively when !rc is invoked - after the kernel is loaded, but before the final root filesystem is attached. The kernel on the 9legacy install CD doesn't have a shell script as /boot/boot with the ability to invoke !rc. Perhaps it should. But that wouldn't have helped in this case. Yakku was stuck at the 'Boot from' prompt within /9boot, unable to find a kernel to boot. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M3a252d01292986d2f6699d46 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 2715 bytes --] hello mein names ist __insert name here___ this is not a 9front mailing list ps: this is ... when it was setup there was no 9front 9front is a breakaway republic designed to initially enhance P.8.72... pps: the problem with break-away republic is that they may initially have the best of intentions but soon realise that they may not have the resources... a bit like my friend sam... /c:2022Jan23 On Sun, Jan 23, 2022 at 10:44 AM Richard Miller <9fans@hamnavoe.com> wrote: > > !rc (and the rest of the boot) is one of the first things implemented > uniquely by 9front. > > I think there's a little bit of confusion about different stages of > booting. > > The 9boot program loads the kernel. The original Plan 9 9boot is driven > by configuration variables in a plan9.ini file. Cinap's rewritten 9boot > adds the capability of interactively changing configuration variables from > the console before loading the kernel. That's really useful, especially > when experimenting with new kernels or new hardware. But 9boot does not > contain a shell or a built-in file system, so it doesn't allow you to > type !rc and get an interactive shell. > > Once the kernel is loaded, the first thing it does is to execute the > command /boot/boot from a small root filesystem which is built into the > kernel. The main job of /boot/boot is to attach to the real root filesystem > (on a local device or from a network server) and execute /$cputype/init to > start the system. Historically the usual case is for /boot/boot to > be a specialised program built from C source in /sys/src/9/boot. But it > has always been possible to configure a kernel with a shell script as > /boot/boot - see for example /sys/lib/sysconfig/ppc/boot for the PowerPC, > or /sys/src/9/bcm/bootwifi.rc for a Raspberry Pi accessing its root file > server via wifi. > > So, using a shell script as /boot/boot is not unique to 9front. But > with 9front, it has become the default. This means there's always a > shell inside the kernel, along with a few commands, ready to use > interactively when !rc is invoked - after the kernel is loaded, but > before the final root filesystem is attached. > > The kernel on the 9legacy install CD doesn't have a shell script as > /boot/boot with the ability to invoke !rc. Perhaps it should. But that > wouldn't have helped in this case. Yakku was stuck at the 'Boot from' > prompt within /9boot, unable to find a kernel to boot. > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-Mc331e608a02e4f563305aea1 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 4162 bytes --]
On Sun, Jan 23, 2022 at 5:44 AM Richard Miller <9fans@hamnavoe.com> wrote: > > !rc (and the rest of the boot) is one of the first things implemented uniquely by 9front. > > I think there's a little bit of confusion about different stages of booting. > > The 9boot program loads the kernel. The original Plan 9 9boot is driven > by configuration variables in a plan9.ini file. Cinap's rewritten 9boot > adds the capability of interactively changing configuration variables from > the console before loading the kernel. That's really useful, especially > when experimenting with new kernels or new hardware. But 9boot does not > contain a shell or a built-in file system, so it doesn't allow you to > type !rc and get an interactive shell. > > Once the kernel is loaded, the first thing it does is to execute the > command /boot/boot from a small root filesystem which is built into the > kernel. The main job of /boot/boot is to attach to the real root filesystem > (on a local device or from a network server) and execute /$cputype/init to > start the system. Historically the usual case is for /boot/boot to > be a specialised program built from C source in /sys/src/9/boot. But it > has always been possible to configure a kernel with a shell script as > /boot/boot - see for example /sys/lib/sysconfig/ppc/boot for the PowerPC, > or /sys/src/9/bcm/bootwifi.rc for a Raspberry Pi accessing its root file > server via wifi. > > So, using a shell script as /boot/boot is not unique to 9front. But > with 9front, it has become the default. This means there's always a > shell inside the kernel, along with a few commands, ready to use > interactively when !rc is invoked - after the kernel is loaded, but > before the final root filesystem is attached. > > The kernel on the 9legacy install CD doesn't have a shell script as > /boot/boot with the ability to invoke !rc. Perhaps it should. But that > wouldn't have helped in this case. Yakku was stuck at the 'Boot from' > prompt within /9boot, unable to find a kernel to boot. > Richard, Thank you for the detailed explanation. I misread the part about no kernel and thought we made it to the boot prompt and could not figure out the disk name. Mea culpa. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M63efb6f310bdb085365dc15f Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
On 1/23/22, Conor Williams <conor.williams@gmail.com> wrote: > hello mein names ist __insert name here___ > > this is not a 9front mailing list It isn't, but unless *all* 9front users and fans (need not be one homogenous group) choose to stop using this list, I have no objection to assisting them or learn from them. I don't think I'm alone in this. > ps: this is ... > when it was setup there was no 9front > 9front is a breakaway republic designed to initially enhance P.8.72... > pps: the problem with break-away republic is that they may initially > have the best of intentions but soon realise that they may not > have the resources... a bit like my friend sam... /c:2022Jan23 > Thank you for the history lesson and the political savvy. Can we get on with the main topic, now? Lucio. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M8bfaf1be667b87e0bfef7fb5 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
On Mon, 24 Jan 2022, Lucio De Re wrote: > Date: Mon, 24 Jan 2022 05:23:26 +0200 > From: Lucio De Re <lucio.dere@gmail.com> > Reply-To: 9fans <9fans@9fans.net> > To: 9fans <9fans@9fans.net> > Subject: Re: [9fans] Problems installing 9legacy on bare metal (Thinkpad X60) > > On 1/23/22, Conor Williams <conor.williams@gmail.com> wrote: >> hello mein names ist __insert name here___ >> >> this is not a 9front mailing list > It isn't, but unless *all* 9front users and fans (need not be one > homogenous group) choose to stop using this list, I have no objection > to assisting them or learn from them. I don't think I'm alone in this. > >> ps: this is ... >> when it was setup there was no 9front >> 9front is a breakaway republic designed to initially enhance P.8.72... >> pps: the problem with break-away republic is that they may initially >> have the best of intentions but soon realise that they may not >> have the resources... a bit like my friend sam... /c:2022Jan23 >> > Thank you for the history lesson and the political savvy. Can we get > on with the main topic, now? > > Lucio. You are aware that you are talking to the most stupidly writen bot in the history of the _I've_no_life_some_one_pay_me_attention_please_ retards? There is an episode of South Park when some poor kid get all exited because one person makes him a friend on facebook. You made some really lonely sad piece of Mr. Hankey happy today. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M207c983dbe2bd679ace6fd68 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
On 1/24/22, adr <adr@sdf.org> wrote: > > You are aware that you are talking to the most stupidly writen bot > in the history of the _I've_no_life_some_one_pay_me_attention_please_ > retards? > > There is an episode of South Park when some poor kid get > all exited because one person makes him a friend on facebook. You > made some really lonely sad piece of Mr. Hankey happy today. > We add happiness where we can, I guess. Machines have a right to the occasional belly laugh too. Plus, maybe there are Noddy points one scores against the day AIs come for us? Lucio :-) ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M4bbabef6c854036b4c3e3b01 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --] Richard has been very forthcoming off-list in trying to get 9legacy working on my machines. But there are still a few things that aren't quite working, so let's bring this thread up to speed. On the X60s, Plan 9 now runs on bare metal but I can't establish an ethernet connection. Even when I run ipconfig and ndb/dns manually after boot, it doesn't solve the issue, because there is an issue with the mp table. cat /dev/kmesg [...] #l0: i82573: 1Gbps port 0xEE000000 irq 11: 0016d3b8c206 mpintrenable: multiple botch irq11, tbdf 5000000, lo 00000049, n 00000049 mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc030000 irq 11 intrenable: couldn't enable irq 11, tbdf 0xC030000 for ether1 wpi: [...] #l1: [...] mpintrenable: multiple botch irq11, tbdf 5000000, lo 00000049, n 00000049 mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc00ef00 irq 11 intrenable: couldn't enable irq 11, tbdf 0xC0EF000 for usbehci [...] init: starting /bin/rc ipconfig: no success with DHCP ndb/dns: can't read my ip address It takes ages to start rc due to the latter two entries. I've tried the BIOS in AHCI, but that returns only more errors, so I have it run in IDE compatibility mode again. The hardware works fine together under OpenBSD, so it can't be an incompatibility issue there. I understand that the MP table may be broken, so I'm wondering whether there is a way of fixing it or whether I would just need to update the BIOS 2.14>2.19 (which would mean buying an X6 Ultrabase with optical drive) and the problem would be solved. On the X60, I can't partition the disk during installation. [partdisk] keeps failing. Again, mpintrenable has not been very kind to me. As above, it cannot enable irq 11 for usbuhci and iahci and can't seem to recognise the hard drive (sdE0): sdE0: retry blk 0 sdE0: retry blk 0 sdE0: retry blk 0 sdE0: retry blk 0 sdE0: retry blk 0 sdE0: bad disk ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M26b0929a71ed3df775db1000 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription [-- Attachment #2: Type: text/html, Size: 3330 bytes --]