RE: Debian Installer - Problems Partitioning
On Thu, 2004-06-24 at 09:53, Whan Park wrote: > I have new 80gb hard disk from Ebay, After i put it in my comp my bios > did found it. > However when i tried partition it through FDISK i could not create the > disk. OK... > I also tried with third party programs such as partition magic and > partion manager 2004. However when ever I tried to initiate the > program it keep failing on error "Bad disk table" and invaild drive > specified" > > Is there any way I could fix my hard disk? > > Thanks > > Whan First of all: What kind of Computer are you using? It sounds to me as if it was just a regular PC. And that would definitely be the wrong question for a mailing list that carries alpha in its name :) Marc
Re: RE: Debian Installer - Problems Partitioning
How do you do. I was having problem with my hard disk and i was surffing around and found this site http://lists.debian.org/debian-alpha/2004/05/msg00180.html asking you question on partitioning his hard disk. I couldnt find any who can help me so I am seeking for your help. I have new 80gb hard disk from Ebay, After i put it in my comp my bios did found it. However when i tried partition it through FDISK i could not create the disk. I also tried with third party programs such as partition magic and partion manager 2004. However when ever I tried to initiate the program it keep failing on error "Bad disk table" and invaild drive specified" Is there any way I could fix my hard disk? Thanks Whan
Re: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
On Tue, Jun 08, 2004 at 09:35:56AM -0400, Dan M. MacNeil wrote: > I stutter: > > > It is my subjective experience that the security team is actually > > > pretty good about updating testing. For example the postgresql update > > > applied to both testing & stable. > Steve Langaek (post modern programer) writes: > > This would be very subjective indeed, because the > > security team does nothing to directly address > > security holes in testing. > If I were a diligent person, I'd look at this a bit more carefully (does > apt-get log???) , but here are a few random data points to muddy the > waters. > My various /etc/apt/sources.list files contain: > deb http://security.debian.org/ sarge/updates main contrib non-free The Packages list for main under sarge/updates lists a total of two source packages, and the versions of both provided from sarge/updates are older than the versions provided via woody/updates. > ...and when I get a notice from the security list: > http://lists.debian.org/debian-security-announce/ > the mentioned package is (always?) updated w/ a apt-get update/upgrade > It doesn't matter (much) to me if the package maintainer updates the > package or the security team. (However, I do seem to seem > "security.debian.org" flashing across the screen when I am updating > packages) The only thing the above sources.list entry will give you is periodic checking of the timestamp on the Packages file. As to whether the package maintainer or the security team updates the package, the issue is precisely that getting updated packages into testing in order to fix security bugs in as timely a manner as they are fixed in stable is often more effort than package maintainers are willing to invest. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
I stutter: > > It is my subjective experience that the security team is actually > > pretty good about updating testing. For example the postgresql update > > applied to both testing & stable. Steve Langaek (post modern programer) writes: > This would be very subjective indeed, because the > security team does nothing to directly address > security holes in testing. If I were a diligent person, I'd look at this a bit more carefully (does apt-get log???) , but here are a few random data points to muddy the waters. My various /etc/apt/sources.list files contain: deb http://security.debian.org/ sarge/updates main contrib non-free ...and when I get a notice from the security list: http://lists.debian.org/debian-security-announce/ the mentioned package is (always?) updated w/ a apt-get update/upgrade It doesn't matter (much) to me if the package maintainer updates the package or the security team. (However, I do seem to seem "security.debian.org" flashing across the screen when I am updating packages) >From the security announcement list (which everyone should subscribe to): [snip] Package: gallery Vulnerability : unauthenticated access Problem-Type : remote Debian-specific: no [snip] For the current stable distribution (woody), these problems have been fixed in version 1.2.5-8woody2. For the unstable distribution (sid), these problems have been fixed in version 1.4.3-pl2-1.
Re: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
On Mon, Jun 07, 2004 at 10:57:12PM -0400, Speakman, John H./Epidemiology-Biostatistics wrote: > There you go again (nod to the late Ronnie, not that I would have voted > for him). > As promised, after my success with the DL140, I popped a sarge CD into > my beloved old Alpha 4100s and the previously dormant StorageWorks 800 > array lit up like a Christmas tree for the first time for over a year. > It will be a couple of days before I can spend some more time on it, but > I was jubilant. Until you guys started bickering, hinting that it's > "not secure" or something. You guys need a good PR agent. Just > kidding. Or am I? PR agents usually have legal teams strapped to their backsides. Here in the Free Software community, I'd much rather tell it to you the way it is. The decision of whether to use sarge on your system is yours to make, my only interest is that it be an informed one. (FWIW, I run sarge or sid on all of my personal machines.) Cheers, -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Monday, June 07, 2004 9:51 PM > To: debian-alpha@lists.debian.org > Subject: Re: testing vs stable (was Re: broadcom drivers debian (was RE: > Debian Installer - Problems Partitioning)) > > On Mon, Jun 07, 2004 at 08:37:46PM -0400, Dan M. MacNeil wrote: > > http://www.nl.debian.org/security/faq#testing > > > Q: How is security handled for testing and unstable? > > > A: The short answer is: it's not. Testing and unstable are rapidly > moving > > targets and the security team does not have the resources needed to > > properly support those. If you want to have a secure (and stable) > server > > you are strongly encouraged to stay with stable. However, the security > > secretaries will try to fix problems in testing and unstable after > they > > are fixed in the stable release. > > > It is my subjective experience that the security team is actually > pretty > > good about updating testing. For example the postgresql update > applied to > > both testing & stable. > > This would be very subjective indeed, because the security team does > nothing to directly address security holes in testing. The most they do > is to document whether the bug affects testing. signature.asc Description: Digital signature
RE: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
There you go again (nod to the late Ronnie, not that I would have voted for him). As promised, after my success with the DL140, I popped a sarge CD into my beloved old Alpha 4100s and the previously dormant StorageWorks 800 array lit up like a Christmas tree for the first time for over a year. It will be a couple of days before I can spend some more time on it, but I was jubilant. Until you guys started bickering, hinting that it's "not secure" or something. You guys need a good PR agent. Just kidding. Or am I? Next I will put the dreaded DAC960s back and see if they work on sarge. More news soon. Best John -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 9:51 PM To: debian-alpha@lists.debian.org Subject: Re: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning)) On Mon, Jun 07, 2004 at 08:37:46PM -0400, Dan M. MacNeil wrote: > http://www.nl.debian.org/security/faq#testing > Q: How is security handled for testing and unstable? > A: The short answer is: it's not. Testing and unstable are rapidly moving > targets and the security team does not have the resources needed to > properly support those. If you want to have a secure (and stable) server > you are strongly encouraged to stay with stable. However, the security > secretaries will try to fix problems in testing and unstable after they > are fixed in the stable release. > It is my subjective experience that the security team is actually pretty > good about updating testing. For example the postgresql update applied to > both testing & stable. This would be very subjective indeed, because the security team does nothing to directly address security holes in testing. The most they do is to document whether the bug affects testing. -- Steve Langasek postmodern programmer = Please note that this e-mail and any files transmitted with it may be privileged, confidential, and protected from disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this communication or any of its attachments is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting this message, any attachments, and all copies and backups from your computer.
Re: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
On Mon, Jun 07, 2004 at 08:37:46PM -0400, Dan M. MacNeil wrote: > http://www.nl.debian.org/security/faq#testing > Q: How is security handled for testing and unstable? > A: The short answer is: it's not. Testing and unstable are rapidly moving > targets and the security team does not have the resources needed to > properly support those. If you want to have a secure (and stable) server > you are strongly encouraged to stay with stable. However, the security > secretaries will try to fix problems in testing and unstable after they > are fixed in the stable release. > It is my subjective experience that the security team is actually pretty > good about updating testing. For example the postgresql update applied to > both testing & stable. This would be very subjective indeed, because the security team does nothing to directly address security holes in testing. The most they do is to document whether the bug affects testing. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
x > The largest difference between stable and testing is that Debian > provides security updates for stable, and for testing you're on your http://www.nl.debian.org/security/faq#testing Q: How is security handled for testing and unstable? A: The short answer is: it's not. Testing and unstable are rapidly moving targets and the security team does not have the resources needed to properly support those. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable. However, the security secretaries will try to fix problems in testing and unstable after they are fixed in the stable release. It is my subjective experience that the security team is actually pretty good about updating testing. For example the postgresql update applied to both testing & stable. Also for major packages (apache, postfix, postgresql), the upstream people tend to be pretty good about Quality Assurance. Running on a closed (sys admin shell only) for things like email. Especially given that Sarge is likely to become stable soon, the new features (not having to dick around with compiling broadcom drivers separately) make it worth the "risk". I have heard people claim that "testing" is as stable as Redhat release...
RE: Debian Installer - Problems Partitioning
> > After creating a useful BSD disklabel and partition scheme, > > the d-i doesn't allow you do choose mount points outside of > > partman! It claims there's no root filesystem and puts you > > back into parman which can't see the partitions to select > > mount points for them!? > > Erm. This is quite peculiar; I can't think of any reason why partman > would be unable to see partitions that the kernel is able to > see. Where > did you download the version of the installer that you used here? I think it was downloaded from http://ftp.egr.msu.edu/debian/dists/testing/main/installer-alpha/ smime.p7s Description: S/MIME cryptographic signature
RE: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning)
Ah, absolutely, there are lots and lots of uses for sarge. But people like me (lazy, stupid, etc.) aren't looking for uses for sarge; we have production systems that they need to run on something and were hoping that something would be Debian. We have definite meanings for words like "testing" and are scared of them. In fact I would like, make that love, to run the whole shop on Debian (currently it's two flavors of Tru64 Unix, one of HP-UX, Windows and Debian, with the resulting sysadmin overhead) but not being "in the Debian community" we are maybe just not yet comfortable with the semantics. And maybe I am in the Debian community because I use Debian, I guess. But I think issues like this, still opaque to me after a couple of years of running Debian, are what's holding it back from wider acceptance. Sorry all for off-topic series of posts; I am on the point of selling off the Alphas (two 4100s and a huge Storageworks array; any offers?) but will first cook up an Alpha sarge CD and see if it magically brings everything to life. Thanks John -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 12:57 AM To: debian-alpha@lists.debian.org Subject: Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning) On Mon, Jun 07, 2004 at 12:39:04AM -0400, Speakman, John H./Epidemiology-Biostatistics wrote: > Actually, my own e-mail piqued my interest enough to go and try it on > a dl140. The sarge installer is sweet and detects the Broadcom. But > (maybe this is my ignorance about Debian) this is work; who wants to > run a production environment on something that isn't "stable"? Many people, to judge by anecdotal evidence within the Debian community. The largest difference between stable and testing is that Debian provides security updates for stable, and for testing you're on your own. If you can get past this hurdle, there are lots of uses sarge can be put to in the time leading up to its official release. -- Steve Langasek postmodern programmer = Please note that this e-mail and any files transmitted with it may be privileged, confidential, and protected from disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this communication or any of its attachments is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting this message, any attachments, and all copies and backups from your computer.
Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning)
On Mon, Jun 07, 2004 at 12:39:04AM -0400, Speakman, John H./Epidemiology-Biostatistics wrote: > Actually, my own e-mail piqued my interest enough to go and try it on > a dl140. The sarge installer is sweet and detects the Broadcom. But > (maybe this is my ignorance about Debian) this is work; who wants to > run a production environment on something that isn't "stable"? Many people, to judge by anecdotal evidence within the Debian community. The largest difference between stable and testing is that Debian provides security updates for stable, and for testing you're on your own. If you can get past this hurdle, there are lots of uses sarge can be put to in the time leading up to its official release. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
RE: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning)
Actually, my own e-mail piqued my interest enough to go and try it on a dl140.
The sarge installer is sweet and detects the Broadcom. But (maybe this is my
ignorance about Debian) this is work; who wants to run a production environment
on something that isn't "stable"?
John
-Original Message-
From: Dan M. MacNeil [mailto:[EMAIL PROTECTED]
Sent: Sun 6/6/2004 10:33 PM
To: Speakman, John H./Epidemiology-Biostatistics
Cc: Jim and Kelly Younkin; debian-alpha@lists.debian.org
Subject: broadcom drivers debian (was RE: Debian Installer - Problems
Partitioning)
> [linux]
> But expect to have problems there too, especially with the Broadcom
NICs
> that every new Intel box has these days.
The (intel) sarge installer auto-detects the broadcom drivers.
I had did apt-get update/upgrade and got a slightly newer kernel. The
network didn't come up until I put:
tg3
...into /etc/modules (for the reboot) and did:
insmod tg3
ifdown eth0
ifup eth0
On Sun, 6 Jun 2004, Speakman, John H./Epidemiology-Biostatistics wrote:
> Not to sound like a wet blanket, but if you have to have Linux I say
> give it up already and buy an Intel box, the more "standard" the
better.
> But expect to have problems there too, especially with the Broadcom
NICs
> that every new Intel box has these days.
>
> I spent six months, on and off, trying to get Linux, any Linux
(actually
> I never tried SuSE...hmm...), to behave itself with Alpha 4100s. I
> tried Debian and Red Hat, threw money away on new SCSI controllers,
> tried firmware upgrades, trolled the internet, gave up on having any
> kind of hardware RAID, all to no avail. I found lots of smart folks
who
> had teased the things into life but I'm just too dumb. At the very
> least you should ditch the DAC960s if they don't work after a week or
so
> of faffing around.
>
> With Intel I can get Debian running although I had to install an old
> fashioned 3Com NIC and if you have an eight-way box expect Debian only
> to be able to handle seven of them. I do think if you have to have
> Linux it should be Debian. Once you have accomplished the Herculean
> task of making Debian work, it will probably stay that way, unlike Red
> Hat. Plus on Intel you will need to hit "bf24" at the first prompt of
> the Debian CD (a non-2.4 kernel won't recognize your hardware, a 2.4
> will recognize everything but the Broadcom NIC).
>
> I hear rumors Debian 3.1 will have a new installer; if it provides a
> nicer way to incorporate new hardware drivers it could really change
the
> world for morons like me. I am pleased to see that HP are providing a
> free Debian-for-Dummies wrapper for Itanium
(http://hpde.linux.hp.com);
> I will be trying it on an eval soon. The one they did for Red Hat on
> Alpha wasn't perfect but got me halfway there. If you do try Red Hat
on
> Alpha you should use it.
>
> Best of luck
> John
>
> -Original Message-
> From: Jim and Kelly Younkin [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 05, 2004 7:36 PM
> To: debian-alpha@lists.debian.org
> Subject: RE: Debian Installer - Problems Partitioning
>
> Is there anything more I can do to get the necessary information for
> someone to be able to diagnosis the problem and suggest a solution?
>
> Should I try RedHat, or another flavor of Linux that supports Alpha?
>
> If I cannot get some version of Linux running on my Alpha by Tuesday I
> will have to order an Intel box. I have fallen way behind on this
> project.
>
> Thanks to all for you help.
>
> Jim
>
> -Original Message-
> From: Steve Langasek [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 05, 2004 3:39 PM
> To: debian-alpha@lists.debian.org
> Cc: Helge Kreutzmann; Jim and Kelly Younkin
> Subject: Re: Debian Installer - Problems Partitioning
> Importance: Low
>
> On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote:
> > Hello,
> > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin
wrote:
> >
broadcom drivers debian (was RE: Debian Installer - Problems Partitioning)
> [linux] > But expect to have problems there too, especially with the Broadcom NICs > that every new Intel box has these days. The (intel) sarge installer auto-detects the broadcom drivers. I had did apt-get update/upgrade and got a slightly newer kernel. The network didn't come up until I put: tg3 ...into /etc/modules (for the reboot) and did: insmod tg3 ifdown eth0 ifup eth0 On Sun, 6 Jun 2004, Speakman, John H./Epidemiology-Biostatistics wrote: > Not to sound like a wet blanket, but if you have to have Linux I say > give it up already and buy an Intel box, the more "standard" the better. > But expect to have problems there too, especially with the Broadcom NICs > that every new Intel box has these days. > > I spent six months, on and off, trying to get Linux, any Linux (actually > I never tried SuSE...hmm...), to behave itself with Alpha 4100s. I > tried Debian and Red Hat, threw money away on new SCSI controllers, > tried firmware upgrades, trolled the internet, gave up on having any > kind of hardware RAID, all to no avail. I found lots of smart folks who > had teased the things into life but I'm just too dumb. At the very > least you should ditch the DAC960s if they don't work after a week or so > of faffing around. > > With Intel I can get Debian running although I had to install an old > fashioned 3Com NIC and if you have an eight-way box expect Debian only > to be able to handle seven of them. I do think if you have to have > Linux it should be Debian. Once you have accomplished the Herculean > task of making Debian work, it will probably stay that way, unlike Red > Hat. Plus on Intel you will need to hit "bf24" at the first prompt of > the Debian CD (a non-2.4 kernel won't recognize your hardware, a 2.4 > will recognize everything but the Broadcom NIC). > > I hear rumors Debian 3.1 will have a new installer; if it provides a > nicer way to incorporate new hardware drivers it could really change the > world for morons like me. I am pleased to see that HP are providing a > free Debian-for-Dummies wrapper for Itanium (http://hpde.linux.hp.com); > I will be trying it on an eval soon. The one they did for Red Hat on > Alpha wasn't perfect but got me halfway there. If you do try Red Hat on > Alpha you should use it. > > Best of luck > John > > -Original Message- > From: Jim and Kelly Younkin [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 7:36 PM > To: debian-alpha@lists.debian.org > Subject: RE: Debian Installer - Problems Partitioning > > Is there anything more I can do to get the necessary information for > someone to be able to diagnosis the problem and suggest a solution? > > Should I try RedHat, or another flavor of Linux that supports Alpha? > > If I cannot get some version of Linux running on my Alpha by Tuesday I > will have to order an Intel box. I have fallen way behind on this > project. > > Thanks to all for you help. > > Jim > > -----Original Message----- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 3:39 PM > To: debian-alpha@lists.debian.org > Cc: Helge Kreutzmann; Jim and Kelly Younkin > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > Hello, > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > > I am ashamed to admit, but I *still* don't get how I am supposed to > run > > > FDISK so I can get to an FDISK prompt. > > > There is nothing to be ashamed of! > > > > ~# fdisk /dev/sda > > > /bin/sh: ~fdisk: not found > > > I don't know the PATH on this busybox. Try > > cd /sbin > > ./fdisk /dev/sda > > > and then (after partitioning) return to the installer. > > This will absolutely not work, you must use devfs-style paths to all > devices when running inside the debian installer. > > But this is an exercise in futility anyway -- if the disk could be seen > by the kernel, partman would've let him partition it to begin with. It > doesn't matter which partitioner he tries to use, he is *not* going to > be able to partition the disk until we figure out why the DAC960 module > won't load for him. > >
RE: Debian Installer - Problems Partitioning
On Sun, 6 Jun 2004, Jim and Kelly Younkin wrote: > > My point is that I have a purpose for which to use my Linux server and I > need to get on with that purpose. Been "faffing around" with this since > May 21st, and I need to move on. Thanks for sharing your experience > with RedHat, I will probably skip that nightmare and just buy the Intel > box. > If you're primary purpose is LTSP, take a look at http://www.k12ltsp.org/. KNOPPIX also has a terminal server. -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
John, Here I thought I was the only one feeling stupid with regard to Linux. I was able to purchase this Alphaserver used because the company only used M$ products and no longer had a need for it. Shame I could not get it to work though, now I have to shell out more $. My goal is to set up a server with internet access and LTSP so others with thin clients can access the internet from my server, using computers that require only minimal maintenance. My point is that I have a purpose for which to use my Linux server and I need to get on with that purpose. Been "faffing around" with this since May 21st, and I need to move on. Thanks for sharing your experience with RedHat, I will probably skip that nightmare and just buy the Intel box. The alternative is to use M$ Terminal Services (with or without Citrix), but this comes with some hefty client access licenses. So I would rather not. Thanks everyone for your help. And I wish you luck with your Alpha-Linux pursuits! Jim -Original Message- From: Speakman, John H./Epidemiology-Biostatistics [mailto:[EMAIL PROTECTED] Sent: Sunday, June 06, 2004 12:07 PM To: Jim and Kelly Younkin; debian-alpha@lists.debian.org Subject: RE: Debian Installer - Problems Partitioning Importance: Low Not to sound like a wet blanket, but if you have to have Linux I say give it up already and buy an Intel box, the more "standard" the better. But expect to have problems there too, especially with the Broadcom NICs that every new Intel box has these days. I spent six months, on and off, trying to get Linux, any Linux (actually I never tried SuSE...hmm...), to behave itself with Alpha 4100s. I tried Debian and Red Hat, threw money away on new SCSI controllers, tried firmware upgrades, trolled the internet, gave up on having any kind of hardware RAID, all to no avail. I found lots of smart folks who had teased the things into life but I'm just too dumb. At the very least you should ditch the DAC960s if they don't work after a week or so of faffing around. With Intel I can get Debian running although I had to install an old fashioned 3Com NIC and if you have an eight-way box expect Debian only to be able to handle seven of them. I do think if you have to have Linux it should be Debian. Once you have accomplished the Herculean task of making Debian work, it will probably stay that way, unlike Red Hat. Plus on Intel you will need to hit "bf24" at the first prompt of the Debian CD (a non-2.4 kernel won't recognize your hardware, a 2.4 will recognize everything but the Broadcom NIC). I hear rumors Debian 3.1 will have a new installer; if it provides a nicer way to incorporate new hardware drivers it could really change the world for morons like me. I am pleased to see that HP are providing a free Debian-for-Dummies wrapper for Itanium (http://hpde.linux.hp.com); I will be trying it on an eval soon. The one they did for Red Hat on Alpha wasn't perfect but got me halfway there. If you do try Red Hat on Alpha you should use it. Best of luck John -Original Message- From: Jim and Kelly Younkin [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 7:36 PM To: debian-alpha@lists.debian.org Subject: RE: Debian Installer - Problems Partitioning Is there anything more I can do to get the necessary information for someone to be able to diagnosis the problem and suggest a solution? Should I try RedHat, or another flavor of Linux that supports Alpha? If I cannot get some version of Linux running on my Alpha by Tuesday I will have to order an Intel box. I have fallen way behind on this project. Thanks to all for you help. Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 3:39 PM To: debian-alpha@lists.debian.org Cc: Helge Kreutzmann; Jim and Kelly Younkin Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > Hello, > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > I am ashamed to admit, but I *still* don't get how I am supposed to run > > FDISK so I can get to an FDISK prompt. > There is nothing to be ashamed of! > > ~# fdisk /dev/sda > > /bin/sh: ~fdisk: not found > I don't know the PATH on this busybox. Try > cd /sbin > ./fdisk /dev/sda > and then (after partitioning) return to the installer. This will absolutely not work, you must use devfs-style paths to all devices when running inside the debian installer. But this is an exercise in futility anyway -- if the disk could be seen by the kernel, partman would've let him partition it to begin with. It doesn't matter which partitioner he tries to use, he is *not* going to be able to partition the disk until we figure out why the DAC960 module won't load for him. -- Steve Langasek postmodern progra
RE: Debian Installer - Problems Partitioning
Well, note I say "if you have to have Linux". For me, Tru64 Unix works
like a dream on Alpha assuming of course you want to pay the big old
license fees. And Windows works... uh, predictably on Intel,
assuming... well, you know. And also I'm only comparing Debian with Red
Hat. Red Hat has a couple of problems. First, it's stuck on 7.2 on
Alpha, so you have to either maintain two different versions or stick on
7.2 for everything. Second, it's a big headache to maintain. RPM
doesn't manage dependencies, and managing them myself always seems to
lead me (being dumb as a box of rocks) down a blind alley of cascading
dependencies that end up in desperately trusting some not-quite-right
RPM ("well, I can't find 7.2, maybe 7.1 will do") that almost works but
doesn't and hours have flown past and it still doesn't work and, what's
more, I've now installed so many shady libraries from rpmfind that I've
probably compromised the system's integrity and broken something else
that I won't find out about until next week. The Debian dependency
manager takes care of all that stuff very nicely once the system is
running the way you want it. The challenge with Debian is making all
the hardware work in the first place; once you do, there is almost no
system administration to speak of. Caveat: of course, if you're not
lazy and stupid like me, you will probably do fine with Red Hat.
John
-Original Message-
From: Jiann-Ming Su [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 06, 2004 1:42 PM
To: debian-alpha@lists.debian.org
Subject: RE: Debian Installer - Problems Partitioning
On Sun, 6 Jun 2004, Speakman, John H./Epidemiology-Biostatistics wrote:
> I do think if you have to have Linux it should be Debian.
>
For someone who has had so much trouble with both Intel and Alpha, why
Debian?
--
Jiann-Ming Su
"Yeah, Lois, that'll be about as much fun as a lecture on
ontological empiricism." --Peter
Griffin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
=
Please note that this e-mail and any files transmitted with it may be
privileged, confidential, and protected from disclosure under
applicable law. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
reading, dissemination, distribution, copying, or other use of this
communication or any of its attachments is strictly prohibited. If
you have received this communication in error, please notify the
sender immediately by replying to this message and deleting this
message, any attachments, and all copies and backups from your
computer.
RE: Debian Installer - Problems Partitioning
On Sun, 6 Jun 2004, Speakman, John H./Epidemiology-Biostatistics wrote: > I do think if you have to have Linux it should be Debian. > For someone who has had so much trouble with both Intel and Alpha, why Debian? -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
Not to sound like a wet blanket, but if you have to have Linux I say give it up already and buy an Intel box, the more "standard" the better. But expect to have problems there too, especially with the Broadcom NICs that every new Intel box has these days. I spent six months, on and off, trying to get Linux, any Linux (actually I never tried SuSE...hmm...), to behave itself with Alpha 4100s. I tried Debian and Red Hat, threw money away on new SCSI controllers, tried firmware upgrades, trolled the internet, gave up on having any kind of hardware RAID, all to no avail. I found lots of smart folks who had teased the things into life but I'm just too dumb. At the very least you should ditch the DAC960s if they don't work after a week or so of faffing around. With Intel I can get Debian running although I had to install an old fashioned 3Com NIC and if you have an eight-way box expect Debian only to be able to handle seven of them. I do think if you have to have Linux it should be Debian. Once you have accomplished the Herculean task of making Debian work, it will probably stay that way, unlike Red Hat. Plus on Intel you will need to hit "bf24" at the first prompt of the Debian CD (a non-2.4 kernel won't recognize your hardware, a 2.4 will recognize everything but the Broadcom NIC). I hear rumors Debian 3.1 will have a new installer; if it provides a nicer way to incorporate new hardware drivers it could really change the world for morons like me. I am pleased to see that HP are providing a free Debian-for-Dummies wrapper for Itanium (http://hpde.linux.hp.com); I will be trying it on an eval soon. The one they did for Red Hat on Alpha wasn't perfect but got me halfway there. If you do try Red Hat on Alpha you should use it. Best of luck John -Original Message- From: Jim and Kelly Younkin [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 7:36 PM To: debian-alpha@lists.debian.org Subject: RE: Debian Installer - Problems Partitioning Is there anything more I can do to get the necessary information for someone to be able to diagnosis the problem and suggest a solution? Should I try RedHat, or another flavor of Linux that supports Alpha? If I cannot get some version of Linux running on my Alpha by Tuesday I will have to order an Intel box. I have fallen way behind on this project. Thanks to all for you help. Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 3:39 PM To: debian-alpha@lists.debian.org Cc: Helge Kreutzmann; Jim and Kelly Younkin Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > Hello, > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > I am ashamed to admit, but I *still* don't get how I am supposed to run > > FDISK so I can get to an FDISK prompt. > There is nothing to be ashamed of! > > ~# fdisk /dev/sda > > /bin/sh: ~fdisk: not found > I don't know the PATH on this busybox. Try > cd /sbin > ./fdisk /dev/sda > and then (after partitioning) return to the installer. This will absolutely not work, you must use devfs-style paths to all devices when running inside the debian installer. But this is an exercise in futility anyway -- if the disk could be seen by the kernel, partman would've let him partition it to begin with. It doesn't matter which partitioner he tries to use, he is *not* going to be able to partition the disk until we figure out why the DAC960 module won't load for him. -- Steve Langasek postmodern programmer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] = Please note that this e-mail and any files transmitted with it may be privileged, confidential, and protected from disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this communication or any of its attachments is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting this message, any attachments, and all copies and backups from your computer.
Re: Debian Installer - Problems Partitioning
Your whole problem is the DAC960 module not loading. And even if it did, the devices on the dac are not /dev/sda, etc but rather they are /dev/rd/c0d0, etc. I tried the sarge installer just for fun awhile back and had no luck with my dac960 raid arrays - I don't remember for sure, but i don't think I got the same failure to load the module error. But in any case - i ended up with no drives to partition. Installing onto dac960 raid arrays is a pain, but I have sucessfully done it with woody, after I manually created necessary entries in /dev (there is a script to do this). You can always temporarily plug a scsi drive onto the qlogic, install to that, then copy everything to the raid arrays, change your fstab entries, and install aboot to the first sector of the raid array. Been there, done that... Mike On Mon, May 31, 2004 at 04:45:43PM -0400, Jim and Kelly Younkin wrote: > When I boot from the CD to install Sarge it automatically loads the > Debian Installer. It prompts for language, and then begins. > > > > Problem #1: > > [?] Detect Network Hardware - > > Error while running 'modprobe -v DAC960' > > > > I press 'Continue". > > > > Problem #2: Let me describe. > > "Starting up the partitioner" brings me to a "Partition disks" main menu > with five choices. > > > > oFinish partitioning and write changes to disk > > oUndo changes to partitions > > oBlank > > oBlank > > oHelp on partitioning > > oGuided partitioning > > oConfigure the Logical Volume Manager > > > > After reading "Help on Partitioning" I choose "Guided Partitioning". I > now see a menu with one option "Manually edit partition table", so I > choose that option, which returns me to the main "Partition disks" menu. > I then try to "Configure the Logical Volume Manager" but it does not > allow me to complete any of the options (Volume Groups or Logical > Volumes) because "No usable physical volumes found". > > > > I believe I know how I want to partition my system but I do not know how > to proceed. The docs I read indicate that because I am booting from SRM > I must use FDISK, but I do not know how to find or run this program. > The Debian Installer does have an option to "Execute a Shell" which runs > "ash" using an editor called "nano". It explains that "the root file > system is a RAM disk". Also "the hard disk file systems are mounted on > '/target'". However, once there I do not know how to find or run FDISK. > > > > So what? > > > > Well I don't know if the first error I get is going to be a problem for > me or not. Since it mentions DAC960, I may have some problems with my > RAID storage devices. Since this has to do with storage, is it possible > that I cannot partition my drives until this is resolved? Are there > issues partitioning drives set up with RAID5? Should I partition > *before* I run the Debian Installer? If so, how do I do this? > > > > Thanks again for your infinite Linux wisdom! > > > > Jim > > > > My system: > > AlphaServer 800 5/400 > > 256MB RAM (128MB in each bank) > > Alphabios: v5.69 > > SRM: v5.4-113 > > Mylex DAC960 RAID Controller > > - Bank 0 (2007MB) > > - Bank 1 (8182MB) > > QLogic ISP SCSI Controller for CD-ROM > > >
RE: Debian Installer - Problems Partitioning
On Sat, 5 Jun 2004, Jim and Kelly Younkin wrote: > > Should I try RedHat, or another flavor of Linux that supports Alpha? > What are you going to be using this system for? The only thing RH7.2 doesn't have over debian is the ability to install and upgrade with apt. Otherwise, I'm sure RH7.2 should work well on your system. -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
# uname -a Linux (none) 2.4.25-1-generic #2 Wed Apr 14 19:38:35 EST 2004 alpha unknown Also, regarding the spelling and case, you are correct it should be DAC960; I double checked. # modprobe DAC960 modprobe: failed to load module DAC960 The original error also had a -v, so I tried that as well... # modprobe -v DAC960 modprobe: failed to load module DAC960 -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 9:06 PM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 09:01:48PM -0400, Jim and Kelly Younkin wrote: > I used JIGDO to download 13 ISO images from > http://gluck.debian.org/cdimage/testing/cd/jigdo-area/alpha/ > Not sure how to use the ISO to determine a) what "d-i" it is using, or > what version of kernel. I thought I was using 2.6, but I could be > wrong. It's not 2.6, there is no 2.6 support yet in the installer on alpha. If all else fails, booting it and running "uname -a" from console 2 should give you this answer. > I tried the modprobe you suggested, and here's what it said... > # modprobe mdac960 > insmod: mdac960.o: no module by that name found > modprobe: failed to load module mdac960 Please check the spelling of the module name. Case counts. -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 8:06 PM > To: debian-alpha@lists.debian.org > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 07:35:44PM -0400, Jim and Kelly Younkin wrote: > > Is there anything more I can do to get the necessary information for > > someone to be able to diagnosis the problem and suggest a solution? > > At a start, you might try running 'modprobe DAC960' from console #2, to > see if you get anything more useful out of it that way (instead of just > "Error loading 'DAC960'"). > > I've checked and the DAC960 module doesn't take any options, so I can't > propose anything in that regard. > > Can you confirm which version of the d-i (sarge) boot images you're > using? It may be worth trying an image with a different kernel than the > one you've used so far; i.e., if you're using 2.4.25 right now, try > 2.4.26, or vice versa. > > > Should I try RedHat, or another flavor of Linux that supports Alpha? > > > If I cannot get some version of Linux running on my Alpha by Tuesday I > > will have to order an Intel box. I have fallen way behind on this > > project. > > If you have a pressing need to get this box booting, you may well want > to give Red Hat a try here, as I can't promise any quick fixes for what > seems to be a kernel problem on your hardware. > > -- > Steve Langasek > postmodern programmer > > > -Original Message- > > From: Steve Langasek [mailto:[EMAIL PROTECTED] > > Sent: Saturday, June 05, 2004 3:39 PM > > To: debian-alpha@lists.debian.org > > Cc: Helge Kreutzmann; Jim and Kelly Younkin > > Subject: Re: Debian Installer - Problems Partitioning > > Importance: Low > > > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > > Hello, > > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin > wrote: > > > > I am ashamed to admit, but I *still* don't get how I am supposed > to > > run > > > > FDISK so I can get to an FDISK prompt. > > > > > There is nothing to be ashamed of! > > > > > > ~# fdisk /dev/sda > > > > /bin/sh: ~fdisk: not found > > > > > I don't know the PATH on this busybox. Try > > > cd /sbin > > > ./fdisk /dev/sda > > > > > and then (after partitioning) return to the installer. > > > > This will absolutely not work, you must use devfs-style paths to all > > devices when running inside the debian installer. > > > > But this is an exercise in futility anyway -- if the disk could be > seen > > by the kernel, partman would've let him partition it to begin with. > It > > doesn't matter which partitioner he tries to use, he is *not* going to > > be able to partition the disk until we figure out why the DAC960 > module > > won't load for him. > > > > -- > > Steve Langasek > > postmodern programmer > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Debian Installer - Problems Partitioning
# uname -a Linux (none) 2.4.25-1-generic #2 Wed Apr 14 19:38:35 EST 2004 alpha unknown Also, regarding the spelling and case, you are correct it should be DAC960; I double checked. # modprobe DAC960 modprobe: failed to load module DAC960 The original error also had a -v, so I tried that as well... # modprobe -v DAC960 modprobe: failed to load module DAC960 -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 9:06 PM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 09:01:48PM -0400, Jim and Kelly Younkin wrote: > I used JIGDO to download 13 ISO images from > http://gluck.debian.org/cdimage/testing/cd/jigdo-area/alpha/ > Not sure how to use the ISO to determine a) what "d-i" it is using, or > what version of kernel. I thought I was using 2.6, but I could be > wrong. It's not 2.6, there is no 2.6 support yet in the installer on alpha. If all else fails, booting it and running "uname -a" from console 2 should give you this answer. > I tried the modprobe you suggested, and here's what it said... > # modprobe mdac960 > insmod: mdac960.o: no module by that name found > modprobe: failed to load module mdac960 Please check the spelling of the module name. Case counts. -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 8:06 PM > To: debian-alpha@lists.debian.org > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 07:35:44PM -0400, Jim and Kelly Younkin wrote: > > Is there anything more I can do to get the necessary information for > > someone to be able to diagnosis the problem and suggest a solution? > > At a start, you might try running 'modprobe DAC960' from console #2, to > see if you get anything more useful out of it that way (instead of just > "Error loading 'DAC960'"). > > I've checked and the DAC960 module doesn't take any options, so I can't > propose anything in that regard. > > Can you confirm which version of the d-i (sarge) boot images you're > using? It may be worth trying an image with a different kernel than the > one you've used so far; i.e., if you're using 2.4.25 right now, try > 2.4.26, or vice versa. > > > Should I try RedHat, or another flavor of Linux that supports Alpha? > > > If I cannot get some version of Linux running on my Alpha by Tuesday I > > will have to order an Intel box. I have fallen way behind on this > > project. > > If you have a pressing need to get this box booting, you may well want > to give Red Hat a try here, as I can't promise any quick fixes for what > seems to be a kernel problem on your hardware. > > -- > Steve Langasek > postmodern programmer > > > -Original Message- > > From: Steve Langasek [mailto:[EMAIL PROTECTED] > > Sent: Saturday, June 05, 2004 3:39 PM > > To: debian-alpha@lists.debian.org > > Cc: Helge Kreutzmann; Jim and Kelly Younkin > > Subject: Re: Debian Installer - Problems Partitioning > > Importance: Low > > > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > > Hello, > > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin > wrote: > > > > I am ashamed to admit, but I *still* don't get how I am supposed > to > > run > > > > FDISK so I can get to an FDISK prompt. > > > > > There is nothing to be ashamed of! > > > > > > ~# fdisk /dev/sda > > > > /bin/sh: ~fdisk: not found > > > > > I don't know the PATH on this busybox. Try > > > cd /sbin > > > ./fdisk /dev/sda > > > > > and then (after partitioning) return to the installer. > > > > This will absolutely not work, you must use devfs-style paths to all > > devices when running inside the debian installer. > > > > But this is an exercise in futility anyway -- if the disk could be > seen > > by the kernel, partman would've let him partition it to begin with. > It > > doesn't matter which partitioner he tries to use, he is *not* going to > > be able to partition the disk until we figure out why the DAC960 > module > > won't load for him. > > > > -- > > Steve Langasek > > postmodern programmer > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer - Problems Partitioning
On Sat, Jun 05, 2004 at 09:01:48PM -0400, Jim and Kelly Younkin wrote: > I used JIGDO to download 13 ISO images from > http://gluck.debian.org/cdimage/testing/cd/jigdo-area/alpha/ > Not sure how to use the ISO to determine a) what "d-i" it is using, or > what version of kernel. I thought I was using 2.6, but I could be > wrong. It's not 2.6, there is no 2.6 support yet in the installer on alpha. If all else fails, booting it and running "uname -a" from console 2 should give you this answer. > I tried the modprobe you suggested, and here's what it said... > # modprobe mdac960 > insmod: mdac960.o: no module by that name found > modprobe: failed to load module mdac960 Please check the spelling of the module name. Case counts. -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 8:06 PM > To: debian-alpha@lists.debian.org > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 07:35:44PM -0400, Jim and Kelly Younkin wrote: > > Is there anything more I can do to get the necessary information for > > someone to be able to diagnosis the problem and suggest a solution? > > At a start, you might try running 'modprobe DAC960' from console #2, to > see if you get anything more useful out of it that way (instead of just > "Error loading 'DAC960'"). > > I've checked and the DAC960 module doesn't take any options, so I can't > propose anything in that regard. > > Can you confirm which version of the d-i (sarge) boot images you're > using? It may be worth trying an image with a different kernel than the > one you've used so far; i.e., if you're using 2.4.25 right now, try > 2.4.26, or vice versa. > > > Should I try RedHat, or another flavor of Linux that supports Alpha? > > > If I cannot get some version of Linux running on my Alpha by Tuesday I > > will have to order an Intel box. I have fallen way behind on this > > project. > > If you have a pressing need to get this box booting, you may well want > to give Red Hat a try here, as I can't promise any quick fixes for what > seems to be a kernel problem on your hardware. > > -- > Steve Langasek > postmodern programmer > > > -Original Message- > > From: Steve Langasek [mailto:[EMAIL PROTECTED] > > Sent: Saturday, June 05, 2004 3:39 PM > > To: debian-alpha@lists.debian.org > > Cc: Helge Kreutzmann; Jim and Kelly Younkin > > Subject: Re: Debian Installer - Problems Partitioning > > Importance: Low > > > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > > Hello, > > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin > wrote: > > > > I am ashamed to admit, but I *still* don't get how I am supposed > to > > run > > > > FDISK so I can get to an FDISK prompt. > > > > > There is nothing to be ashamed of! > > > > > > ~# fdisk /dev/sda > > > > /bin/sh: ~fdisk: not found > > > > > I don't know the PATH on this busybox. Try > > > cd /sbin > > > ./fdisk /dev/sda > > > > > and then (after partitioning) return to the installer. > > > > This will absolutely not work, you must use devfs-style paths to all > > devices when running inside the debian installer. > > > > But this is an exercise in futility anyway -- if the disk could be > seen > > by the kernel, partman would've let him partition it to begin with. > It > > doesn't matter which partitioner he tries to use, he is *not* going to > > be able to partition the disk until we figure out why the DAC960 > module > > won't load for him. > > > > -- > > Steve Langasek > > postmodern programmer > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
RE: Debian Installer - Problems Partitioning
I used JIGDO to download 13 ISO images from http://gluck.debian.org/cdimage/testing/cd/jigdo-area/alpha/ Not sure how to use the ISO to determine a) what "d-i" it is using, or what version of kernel. I thought I was using 2.6, but I could be wrong. I tried the modprobe you suggested, and here's what it said... # modprobe mdac960 insmod: mdac960.o: no module by that name found modprobe: failed to load module mdac960 Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 8:06 PM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 07:35:44PM -0400, Jim and Kelly Younkin wrote: > Is there anything more I can do to get the necessary information for > someone to be able to diagnosis the problem and suggest a solution? At a start, you might try running 'modprobe DAC960' from console #2, to see if you get anything more useful out of it that way (instead of just "Error loading 'DAC960'"). I've checked and the DAC960 module doesn't take any options, so I can't propose anything in that regard. Can you confirm which version of the d-i (sarge) boot images you're using? It may be worth trying an image with a different kernel than the one you've used so far; i.e., if you're using 2.4.25 right now, try 2.4.26, or vice versa. > Should I try RedHat, or another flavor of Linux that supports Alpha? > If I cannot get some version of Linux running on my Alpha by Tuesday I > will have to order an Intel box. I have fallen way behind on this > project. If you have a pressing need to get this box booting, you may well want to give Red Hat a try here, as I can't promise any quick fixes for what seems to be a kernel problem on your hardware. -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 3:39 PM > To: debian-alpha@lists.debian.org > Cc: Helge Kreutzmann; Jim and Kelly Younkin > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > Hello, > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > > I am ashamed to admit, but I *still* don't get how I am supposed to > run > > > FDISK so I can get to an FDISK prompt. > > > There is nothing to be ashamed of! > > > > ~# fdisk /dev/sda > > > /bin/sh: ~fdisk: not found > > > I don't know the PATH on this busybox. Try > > cd /sbin > > ./fdisk /dev/sda > > > and then (after partitioning) return to the installer. > > This will absolutely not work, you must use devfs-style paths to all > devices when running inside the debian installer. > > But this is an exercise in futility anyway -- if the disk could be seen > by the kernel, partman would've let him partition it to begin with. It > doesn't matter which partitioner he tries to use, he is *not* going to > be able to partition the disk until we figure out why the DAC960 module > won't load for him. > > -- > Steve Langasek > postmodern programmer > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Debian Installer - Problems Partitioning
I used JIGDO to download 13 ISO images from http://gluck.debian.org/cdimage/testing/cd/jigdo-area/alpha/ Not sure how to use the ISO to determine a) what "d-i" it is using, or what version of kernel. I thought I was using 2.6, but I could be wrong. I tried the modprobe you suggested, and here's what it said... # modprobe mdac960 insmod: mdac960.o: no module by that name found modprobe: failed to load module mdac960 Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 8:06 PM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 07:35:44PM -0400, Jim and Kelly Younkin wrote: > Is there anything more I can do to get the necessary information for > someone to be able to diagnosis the problem and suggest a solution? At a start, you might try running 'modprobe DAC960' from console #2, to see if you get anything more useful out of it that way (instead of just "Error loading 'DAC960'"). I've checked and the DAC960 module doesn't take any options, so I can't propose anything in that regard. Can you confirm which version of the d-i (sarge) boot images you're using? It may be worth trying an image with a different kernel than the one you've used so far; i.e., if you're using 2.4.25 right now, try 2.4.26, or vice versa. > Should I try RedHat, or another flavor of Linux that supports Alpha? > If I cannot get some version of Linux running on my Alpha by Tuesday I > will have to order an Intel box. I have fallen way behind on this > project. If you have a pressing need to get this box booting, you may well want to give Red Hat a try here, as I can't promise any quick fixes for what seems to be a kernel problem on your hardware. -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 3:39 PM > To: debian-alpha@lists.debian.org > Cc: Helge Kreutzmann; Jim and Kelly Younkin > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > Hello, > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > > I am ashamed to admit, but I *still* don't get how I am supposed to > run > > > FDISK so I can get to an FDISK prompt. > > > There is nothing to be ashamed of! > > > > ~# fdisk /dev/sda > > > /bin/sh: ~fdisk: not found > > > I don't know the PATH on this busybox. Try > > cd /sbin > > ./fdisk /dev/sda > > > and then (after partitioning) return to the installer. > > This will absolutely not work, you must use devfs-style paths to all > devices when running inside the debian installer. > > But this is an exercise in futility anyway -- if the disk could be seen > by the kernel, partman would've let him partition it to begin with. It > doesn't matter which partitioner he tries to use, he is *not* going to > be able to partition the disk until we figure out why the DAC960 module > won't load for him. > > -- > Steve Langasek > postmodern programmer > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer - Problems Partitioning
On Sat, Jun 05, 2004 at 07:35:44PM -0400, Jim and Kelly Younkin wrote: > Is there anything more I can do to get the necessary information for > someone to be able to diagnosis the problem and suggest a solution? At a start, you might try running 'modprobe DAC960' from console #2, to see if you get anything more useful out of it that way (instead of just "Error loading 'DAC960'"). I've checked and the DAC960 module doesn't take any options, so I can't propose anything in that regard. Can you confirm which version of the d-i (sarge) boot images you're using? It may be worth trying an image with a different kernel than the one you've used so far; i.e., if you're using 2.4.25 right now, try 2.4.26, or vice versa. > Should I try RedHat, or another flavor of Linux that supports Alpha? > If I cannot get some version of Linux running on my Alpha by Tuesday I > will have to order an Intel box. I have fallen way behind on this > project. If you have a pressing need to get this box booting, you may well want to give Red Hat a try here, as I can't promise any quick fixes for what seems to be a kernel problem on your hardware. -- Steve Langasek postmodern programmer > -Original Message- > From: Steve Langasek [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 05, 2004 3:39 PM > To: debian-alpha@lists.debian.org > Cc: Helge Kreutzmann; Jim and Kelly Younkin > Subject: Re: Debian Installer - Problems Partitioning > Importance: Low > > On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > > Hello, > > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > > I am ashamed to admit, but I *still* don't get how I am supposed to > run > > > FDISK so I can get to an FDISK prompt. > > > There is nothing to be ashamed of! > > > > ~# fdisk /dev/sda > > > /bin/sh: ~fdisk: not found > > > I don't know the PATH on this busybox. Try > > cd /sbin > > ./fdisk /dev/sda > > > and then (after partitioning) return to the installer. > > This will absolutely not work, you must use devfs-style paths to all > devices when running inside the debian installer. > > But this is an exercise in futility anyway -- if the disk could be seen > by the kernel, partman would've let him partition it to begin with. It > doesn't matter which partitioner he tries to use, he is *not* going to > be able to partition the disk until we figure out why the DAC960 module > won't load for him. > > -- > Steve Langasek > postmodern programmer > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Debian Installer - Problems Partitioning
On Wed, Jun 02, 2004 at 10:11:26AM -0400, Cernese, Dan wrote: > To answer my own question, you can 'shell' out of the installer, > run fdisk (which only has ext2 listed, however, not ext3), but > finding the drive pathname isn't so easy > fdisk /dev/hda --doesn't work, > fdisk /dev/discs/disc0/disc > After creating a useful BSD disklabel and partition scheme, > the d-i doesn't allow you do choose mount points outside of > partman! It claims there's no root filesystem and puts you > back into parman which can't see the partitions to select > mount points for them!? Erm. This is quite peculiar; I can't think of any reason why partman would be unable to see partitions that the kernel is able to see. Where did you download the version of the installer that you used here? -- Steve Langasek postmodern programmer > > -Original Message- > > From: Cernese, Dan [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 02, 2004 9:48 AM > > To: debian-alpha@lists.debian.org > > Subject: RE: Debian Installer - Problems Partitioning > > > > I'm in the middle of dealing with this same issue, I cannot > > figure out how to partition my IDE drive in a DS20L (that has > > no floppy; only a CD and an IDE drive). Using SRM... > > > > I started with sarge/testing's netboot installer (both minimal > > and base-system CD images), but learned the hard way it couldn't > > partition the disk. > > > > I used the woody installer and it can autorun fdisk, I create > > the partition table and reboot with the newest installer and > > it (partman?) can't deal with the BSD partition table, there > > doesn't even appear to be a way to skip it. > > > > What to do to get a sarge install? > > > > > > > -Original Message- > > > From: Cameron Patrick [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, June 02, 2004 3:24 AM > > > To: debian-alpha@lists.debian.org > > > Subject: Re: Debian Installer - Problems Partitioning > > > > > > Jiann-Ming Su wrote: > > > > > > | I thought Debian's installer used cfdisk. For more info in > > > partitioning > > > | with fdisk: > > > | > > > | http://www.tldp.org/HOWTO/Partition/partition-5.html > > > > > > If by "Debian's installer" you mean "boot floppies on i386" then > > > that's true. It's never been used on alpha -- boot-floppies used > > > straight fdisk, and debian-installer uses partman (as it > > does on most > > > other architectures). > > > > > > (boot-floppies is the name of the installer used in woody > > and previous > > > distributions. debian-installer is the new installer that will be > > > used in sarge.) > > > > > > Cameron. > > > > > signature.asc Description: Digital signature
Re: Debian Installer - Problems Partitioning
On Wed, Jun 02, 2004 at 09:48:41AM -0400, Cernese, Dan wrote: > I'm in the middle of dealing with this same issue, I cannot > figure out how to partition my IDE drive in a DS20L (that has > no floppy; only a CD and an IDE drive). Using SRM... > I started with sarge/testing's netboot installer (both minimal > and base-system CD images), but learned the hard way it couldn't > partition the disk. > I used the woody installer and it can autorun fdisk, I create > the partition table and reboot with the newest installer and > it (partman?) can't deal with the BSD partition table, there > doesn't even appear to be a way to skip it. partman not only should be able to handle BSD disklabels, it also knows that these should be the default partition table types on alpha. What exactly do you see when partman runs? Are you trying to use autopartitioning or not? Does it show the disk(s) as being present and selectable? If you switch to console #2, what do you get as output of "ls /dev/discs/"? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
RE: Debian Installer - Problems Partitioning
Is there anything more I can do to get the necessary information for someone to be able to diagnosis the problem and suggest a solution? Should I try RedHat, or another flavor of Linux that supports Alpha? If I cannot get some version of Linux running on my Alpha by Tuesday I will have to order an Intel box. I have fallen way behind on this project. Thanks to all for you help. Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 3:39 PM To: debian-alpha@lists.debian.org Cc: Helge Kreutzmann; Jim and Kelly Younkin Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > Hello, > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > I am ashamed to admit, but I *still* don't get how I am supposed to run > > FDISK so I can get to an FDISK prompt. > There is nothing to be ashamed of! > > ~# fdisk /dev/sda > > /bin/sh: ~fdisk: not found > I don't know the PATH on this busybox. Try > cd /sbin > ./fdisk /dev/sda > and then (after partitioning) return to the installer. This will absolutely not work, you must use devfs-style paths to all devices when running inside the debian installer. But this is an exercise in futility anyway -- if the disk could be seen by the kernel, partman would've let him partition it to begin with. It doesn't matter which partitioner he tries to use, he is *not* going to be able to partition the disk until we figure out why the DAC960 module won't load for him. -- Steve Langasek postmodern programmer
Re: Debian Installer - Problems Partitioning
On Sat, Jun 05, 2004 at 06:36:34PM +0200, Helge Kreutzmann wrote: > Hello, > On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > > I am ashamed to admit, but I *still* don't get how I am supposed to run > > FDISK so I can get to an FDISK prompt. > There is nothing to be ashamed of! > > ~# fdisk /dev/sda > > /bin/sh: ~fdisk: not found > I don't know the PATH on this busybox. Try > cd /sbin > ./fdisk /dev/sda > and then (after partitioning) return to the installer. This will absolutely not work, you must use devfs-style paths to all devices when running inside the debian installer. But this is an exercise in futility anyway -- if the disk could be seen by the kernel, partman would've let him partition it to begin with. It doesn't matter which partitioner he tries to use, he is *not* going to be able to partition the disk until we figure out why the DAC960 module won't load for him. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
RE: Debian Installer - Problems Partitioning
Thanks for the encouragement. How do I find the PATH? I changed the directory to /sbin and typed what you said. /sbin # ./fdisk /dev/sda /bin/sh: ./fdisk: not found I assume I will find fdisk elsewhere? I tried 'find / -name "fdisk"' but nothing was returned. Jim -Original Message- From: Helge Kreutzmann [mailto:[EMAIL PROTECTED] Sent: Saturday, June 05, 2004 12:37 PM To: Jim and Kelly Younkin Cc: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low Hello, On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > I am ashamed to admit, but I *still* don't get how I am supposed to run > FDISK so I can get to an FDISK prompt. There is nothing to be ashamed of! > ~# fdisk /dev/sda > /bin/sh: ~fdisk: not found I don't know the PATH on this busybox. Try cd /sbin ./fdisk /dev/sda and then (after partitioning) return to the installer. Greetings Helge -- Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferredgpg-key: finger [EMAIL PROTECTED] 64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm Help keep free software "libre": http://www.freepatents.org/
Re: Debian Installer - Problems Partitioning
Hello, On Sat, Jun 05, 2004 at 12:10:33PM -0400, Jim and Kelly Younkin wrote: > I am ashamed to admit, but I *still* don't get how I am supposed to run > FDISK so I can get to an FDISK prompt. There is nothing to be ashamed of! > ~# fdisk /dev/sda > /bin/sh: ~fdisk: not found I don't know the PATH on this busybox. Try cd /sbin ./fdisk /dev/sda and then (after partitioning) return to the installer. Greetings Helge -- Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferredgpg-key: finger [EMAIL PROTECTED] 64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm Help keep free software "libre": http://www.freepatents.org/ pgpP3gODDy6i8.pgp Description: PGP signature
RE: Debian Installer - Problems Partitioning
I am ashamed to admit, but I *still* don't get how I am supposed to run FDISK so I can get to an FDISK prompt. When I boot the computer I come to an SRM prompt. SRM does not know about FDISK, nor can I seem to get to a shell. So I: >>>boot dka400 -fl 0 which boots from the CD, which starts the Debian Installer. After entering responses to language and keyboard, detect h/w, (where I get the DAC960 error) etc., I am taken to Partman which tells me I cannot partition. From here I can shell out to a prompt "BusyBox v1.00-pre10 (ash)". ~# fdisk /dev/sda /bin/sh: ~fdisk: not found So you see, I do not know *how* to run fdisk. Jim -Original Message- From: Jiann-Ming Su [mailto:[EMAIL PROTECTED] Sent: Friday, June 04, 2004 11:15 PM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning On Mon, 31 May 2004, Jim and Kelly Younkin wrote: > > I believe I know how I want to partition my system but I do not know how > to proceed. The docs I read indicate that because I am booting from SRM > I must use FDISK, but I do not know how to find or run this program. > The Debian Installer does have an option to "Execute a Shell" which runs > "ash" using an editor called "nano". It explains that "the root file > system is a RAM disk". Also "the hard disk file systems are mounted on > '/target'". However, once there I do not know how to find or run FDISK. > After reinstalling after a disk failure, I think I see what you are running into. When you run fdisk, you'll have to run it in BSD mode for Alpha systems. You can enter BSD mode (if fdisk didn't do so automatically) with "b" at the fdisk prompt. The HOWTO should explain how to use fdisk. The difference I have found with BSD mode is you have to explicitly tell where each partition starts and ends. In DOS mode, it'll sequentially start the next partition at the end of the previous one. Also for Alpha, leave the first sector blank for aboot. That is, start your first partition with sector 2. If you don't use BSD disk labels, aboot will not install. IIRC, RedHat 7.2's installer took care of a lot of this. -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer - Problems Partitioning
On Mon, 31 May 2004, Jim and Kelly Younkin wrote: > > I believe I know how I want to partition my system but I do not know how > to proceed. The docs I read indicate that because I am booting from SRM > I must use FDISK, but I do not know how to find or run this program. > The Debian Installer does have an option to "Execute a Shell" which runs > "ash" using an editor called "nano". It explains that "the root file > system is a RAM disk". Also "the hard disk file systems are mounted on > '/target'". However, once there I do not know how to find or run FDISK. > After reinstalling after a disk failure, I think I see what you are running into. When you run fdisk, you'll have to run it in BSD mode for Alpha systems. You can enter BSD mode (if fdisk didn't do so automatically) with "b" at the fdisk prompt. The HOWTO should explain how to use fdisk. The difference I have found with BSD mode is you have to explicitly tell where each partition starts and ends. In DOS mode, it'll sequentially start the next partition at the end of the previous one. Also for Alpha, leave the first sector blank for aboot. That is, start your first partition with sector 2. If you don't use BSD disk labels, aboot will not install. IIRC, RedHat 7.2's installer took care of a lot of this. -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
On Wed, 2 Jun 2004, Cernese, Dan wrote: > Aah, I tried this route. Unfortunately, the woody e100 driver is > so unstable as to hit continualy transmit timeouts which prevent a > useful upgrade. Maybe I'll stick a tulip card in just to do the > upgrade. > Is your card not compatible with the eepro100 driver? -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
To answer my own question, you can 'shell' out of the installer, run fdisk (which only has ext2 listed, however, not ext3), but finding the drive pathname isn't so easy fdisk /dev/hda --doesn't work, fdisk /dev/discs/disc0/disc After creating a useful BSD disklabel and partition scheme, the d-i doesn't allow you do choose mount points outside of partman! It claims there's no root filesystem and puts you back into parman which can't see the partitions to select mount points for them!? > -Original Message- > From: Cernese, Dan [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 02, 2004 9:48 AM > To: debian-alpha@lists.debian.org > Subject: RE: Debian Installer - Problems Partitioning > > I'm in the middle of dealing with this same issue, I cannot > figure out how to partition my IDE drive in a DS20L (that has > no floppy; only a CD and an IDE drive). Using SRM... > > I started with sarge/testing's netboot installer (both minimal > and base-system CD images), but learned the hard way it couldn't > partition the disk. > > I used the woody installer and it can autorun fdisk, I create > the partition table and reboot with the newest installer and > it (partman?) can't deal with the BSD partition table, there > doesn't even appear to be a way to skip it. > > What to do to get a sarge install? > > > > -Original Message- > > From: Cameron Patrick [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 02, 2004 3:24 AM > > To: debian-alpha@lists.debian.org > > Subject: Re: Debian Installer - Problems Partitioning > > > > Jiann-Ming Su wrote: > > > > | I thought Debian's installer used cfdisk. For more info in > > partitioning > > | with fdisk: > > | > > | http://www.tldp.org/HOWTO/Partition/partition-5.html > > > > If by "Debian's installer" you mean "boot floppies on i386" then > > that's true. It's never been used on alpha -- boot-floppies used > > straight fdisk, and debian-installer uses partman (as it > does on most > > other architectures). > > > > (boot-floppies is the name of the installer used in woody > and previous > > distributions. debian-installer is the new installer that will be > > used in sarge.) > > > > Cameron. > > > smime.p7s Description: S/MIME cryptographic signature
RE: Debian Installer - Problems Partitioning
Aah, I tried this route. Unfortunately, the woody e100 driver is so unstable as to hit continualy transmit timeouts which prevent a useful upgrade. Maybe I'll stick a tulip card in just to do the upgrade. sigh. > -Original Message- > From: Jiann-Ming Su [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 01, 2004 12:28 AM > To: debian-alpha@lists.debian.org > Subject: Re: Debian Installer - Problems Partitioning > > I assume you are using Beta 4... take a look at the errata: > > http://www.debian.org/devel/debian-installer/errata > > Your best bet is probably to install a minimal Woody and do an > "apt-get dist-upgrade". You'd probably want to make your > /etc/apt/preferences look like: > > Package: * > Pin: release a=testing > Pin-Priority: 750 > > Package: * > Pin: release a=unstable > Pin-Priority: 650 > > Package: * > Pin: release a=stable > Pin-Priority: 600 > > Package: * > Pin: release a=experimental > Pin-Priority: 500 > > > -- > Jiann-Ming Su > "Yeah, Lois, that'll be about as much fun as a lecture on > ontological empiricism." > --Peter Griffin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > smime.p7s Description: S/MIME cryptographic signature
RE: Debian Installer - Problems Partitioning
I'm in the middle of dealing with this same issue, I cannot figure out how to partition my IDE drive in a DS20L (that has no floppy; only a CD and an IDE drive). Using SRM... I started with sarge/testing's netboot installer (both minimal and base-system CD images), but learned the hard way it couldn't partition the disk. I used the woody installer and it can autorun fdisk, I create the partition table and reboot with the newest installer and it (partman?) can't deal with the BSD partition table, there doesn't even appear to be a way to skip it. What to do to get a sarge install? > -Original Message- > From: Cameron Patrick [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 02, 2004 3:24 AM > To: debian-alpha@lists.debian.org > Subject: Re: Debian Installer - Problems Partitioning > > Jiann-Ming Su wrote: > > | I thought Debian's installer used cfdisk. For more info in > partitioning > | with fdisk: > | > | http://www.tldp.org/HOWTO/Partition/partition-5.html > > If by "Debian's installer" you mean "boot floppies on i386" then > that's true. It's never been used on alpha -- boot-floppies used > straight fdisk, and debian-installer uses partman (as it does on most > other architectures). > > (boot-floppies is the name of the installer used in woody and previous > distributions. debian-installer is the new installer that will be > used in sarge.) > > Cameron. > smime.p7s Description: S/MIME cryptographic signature
Re: Debian Installer - Problems Partitioning
On Wed, Jun 02, 2004 at 03:23:58PM +0800, Cameron Patrick wrote: > Jiann-Ming Su wrote: > > | I thought Debian's installer used cfdisk. For more info in partitioning > | with fdisk: > | > | http://www.tldp.org/HOWTO/Partition/partition-5.html > > If by "Debian's installer" you mean "boot floppies on i386" then > that's true. It's never been used on alpha -- boot-floppies used > straight fdisk, and debian-installer uses partman (as it does on most > other architectures). In fact, if you are on Alpha, you cfdisk will *not* work for the disk that SRM is booting from. It *will* work if you are using AlphaBIOS/MILO, IIRC. -- John > > (boot-floppies is the name of the installer used in woody and previous > distributions. debian-installer is the new installer that will be > used in sarge.) > > Cameron.
Re: Debian Installer - Problems Partitioning
Jiann-Ming Su wrote: | I thought Debian's installer used cfdisk. For more info in partitioning | with fdisk: | | http://www.tldp.org/HOWTO/Partition/partition-5.html If by "Debian's installer" you mean "boot floppies on i386" then that's true. It's never been used on alpha -- boot-floppies used straight fdisk, and debian-installer uses partman (as it does on most other architectures). (boot-floppies is the name of the installer used in woody and previous distributions. debian-installer is the new installer that will be used in sarge.) Cameron. signature.asc Description: Digital signature
RE: Debian Installer - Problems Partitioning
On Tue, 1 Jun 2004, Jim and Kelly Younkin wrote: > The only driver I have that I see a problem with in the errata is the > QLogicISP. Not sure this is even a problem, since it does successfully > use the CD-ROM drive. > > If someone could just explain how to partition my drives within the > installer, or outside the installer program, I would prefer trying that > first. > I thought Debian's installer used cfdisk. For more info in partitioning with fdisk: http://www.tldp.org/HOWTO/Partition/partition-5.html -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
When the error pops up on the screen, and I read terminal 4, it has: Jun 1 02:19:16 (none) user.notice hw-detect: Error loading 'DAC960' All the preceding messages are syslog.warn messages referring to klogd: Then I press "Continue"...and quickly switch consoles and pause the screen. I will type just the text of the DEBUG: messages... ...[not sure how many messages slipped thru before I could pause screen] install debootstrap-udeb, dependency from base-installer search for package resolving created-fstab, dependency from base installer package chroot doesn't exist search for package resolving libparted1.6-0, dependency from partconf-find-partitions install partconf-find-partitions, dependency from aboot-installer search for package resolving kernel-installer, dependency from nobootloader install parted-udeb, dependency from nobootloader search for package resolving bootable-system, dependency from prebaseconfig menu item 'partman' selected configure partman, status: 2 configure harddrive-detection, status: 0 virtual package harddrive-detection search for package resolving harddrive-detection, dependency from partman search for package resolving mounted-partitions, dependency from base-installer install debootstrap-udeb, dependency from base-installer search for package resolving created-fstab, dependency from base-installer package chroot doesn't exist (ignored) search for package resolving libparted1.6-0, dependency from partconf-find-partitions install partconf-find-partitions, dependency from aboot installer search for package resolving kernel-installer, dependency from nobootloader install parted-udeb, dependency from nobootloader search for package resolving bootable-system, dependency from prebaseconfig Next I got some daemon.info messages that look like they are starting or scheduling processes. HTH..thanks! Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 2:09 AM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Mon, May 31, 2004 at 04:45:43PM -0400, Jim and Kelly Younkin wrote: > When I boot from the CD to install Sarge it automatically loads the > Debian Installer. It prompts for language, and then begins. > Problem #1: > [?] Detect Network Hardware - > Error while running 'modprobe -v DAC960' Knowing that your drives are on a DAC960 controller, this is a problem. > I press 'Continue". > Problem #2: Let me describe. > "Starting up the partitioner" brings me to a "Partition disks" main menu > with five choices. > oFinish partitioning and write changes to disk > > oUndo changes to partitions > > oBlank > > oBlank > > oHelp on partitioning > > oGuided partitioning > > oConfigure the Logical Volume Manager This confirms that, without the DAC960 driver correctly loaded, d-i was not able to find any disks that you could partition. Can you send the output from terminal 4 (ALT-F4) within the installer, immediately after the error about the module loading? -- Steve Langasek postmodern programmer
RE: Debian Installer - Problems Partitioning
The only driver I have that I see a problem with in the errata is the QLogicISP. Not sure this is even a problem, since it does successfully use the CD-ROM drive. If someone could just explain how to partition my drives within the installer, or outside the installer program, I would prefer trying that first. Jim -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 2:02 AM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning Importance: Low On Mon, May 31, 2004 at 11:12:21PM -0500, Jiann-Ming Su wrote: > I assume you are using Beta 4... take a look at the errata: > http://www.debian.org/devel/debian-installer/errata > Your best bet is probably to install a minimal Woody and do an > "apt-get dist-upgrade". Er, questionable, unless you know for sure the driver in question is supported by the woody installer? -- Steve Langasek postmodern programmer
Re: Debian Installer - Problems Partitioning
On Mon, May 31, 2004 at 04:45:43PM -0400, Jim and Kelly Younkin wrote: > When I boot from the CD to install Sarge it automatically loads the > Debian Installer. It prompts for language, and then begins. > Problem #1: > [?] Detect Network Hardware - > Error while running 'modprobe -v DAC960' Knowing that your drives are on a DAC960 controller, this is a problem. > I press 'Continue". > Problem #2: Let me describe. > "Starting up the partitioner" brings me to a "Partition disks" main menu > with five choices. > oFinish partitioning and write changes to disk > > oUndo changes to partitions > > oBlank > > oBlank > > oHelp on partitioning > > oGuided partitioning > > oConfigure the Logical Volume Manager This confirms that, without the DAC960 driver correctly loaded, d-i was not able to find any disks that you could partition. Can you send the output from terminal 4 (ALT-F4) within the installer, immediately after the error about the module loading? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Debian Installer - Problems Partitioning
On Mon, May 31, 2004 at 11:12:21PM -0500, Jiann-Ming Su wrote: > I assume you are using Beta 4... take a look at the errata: > http://www.debian.org/devel/debian-installer/errata > Your best bet is probably to install a minimal Woody and do an > "apt-get dist-upgrade". Er, questionable, unless you know for sure the driver in question is supported by the woody installer? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
RE: Debian Installer - Problems Partitioning
Thanks Jiann-Ming, but the only reason I am using Sarge is because of kernel problems when installing Woody. Is there an option to install Sarge without the Beta 4 Installer? Is there an option to install Woody with the newest kernel? Help, I seem to be looping. Jim -Original Message- From: Jiann-Ming Su [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 12:12 AM To: debian-alpha@lists.debian.org Subject: Re: Debian Installer - Problems Partitioning I assume you are using Beta 4... take a look at the errata: http://www.debian.org/devel/debian-installer/errata Your best bet is probably to install a minimal Woody and do an "apt-get dist-upgrade". You'd probably want to make your /etc/apt/preferences look like: Package: * Pin: release a=testing Pin-Priority: 750 Package: * Pin: release a=unstable Pin-Priority: 650 Package: * Pin: release a=stable Pin-Priority: 600 Package: * Pin: release a=experimental Pin-Priority: 500 -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer - Problems Partitioning
I assume you are using Beta 4... take a look at the errata: http://www.debian.org/devel/debian-installer/errata Your best bet is probably to install a minimal Woody and do an "apt-get dist-upgrade". You'd probably want to make your /etc/apt/preferences look like: Package: * Pin: release a=testing Pin-Priority: 750 Package: * Pin: release a=unstable Pin-Priority: 650 Package: * Pin: release a=stable Pin-Priority: 600 Package: * Pin: release a=experimental Pin-Priority: 500 -- Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin
RE: Debian Installer - Problems Partitioning
I found by pressing alt-f2 I could get to a shell with a prompt of ~# I entered fdisk and discovered it recognized the command. I believe, since I am using SCSI that I must format /dev/sda and /dev/sdb, but when I enter fdisk /dev/sda (or sdb) it replies with “Unable to open device /dev/sda”. I also tried with /dev/sda1, since that should be the first partition on sda, with the same result. Is there another command that releases the disk for formatting? Are there any good primers on using FDISK? Everything I read says this is for EXPERTS ONLY, so what am I doing here? Is there a better way to set up these partitions? Jim -Original Message- From: Conny Enström [mailto:[EMAIL PROTECTED] Sent: Monday, May 31, 2004 6:55 PM To: Jim and Kelly Younkin Subject: Re: Debian Installer - Problems Partitioning - Original Message - From: Jim and Kelly Younkin To: debian-alpha@lists.debian.org Sent: Monday, May 31, 2004 9:45 PM Subject: Debian Installer - Problems Partitioning When I boot from the CD to install Sarge it automatically loads the Debian Installer. It prompts for language, and then begins. Problem #1: [?] Detect Network Hardware – Error while running ‘modprobe –v DAC960’ I press ‘Continue”… Problem #2: Let me describe… “Starting up the partitioner” brings me to a “Partition disks” main menu with five choices… o Finish partitioning and write changes to disk o Undo changes to partitions o Blank o Blank o Help on partitioning o Guided partitioning o Configure the Logical Volume Manager After reading “Help on Partitioning” I choose “Guided Partitioning”. I now see a menu with one option “Manually edit partition table”, so I choose that option, which returns me to the main “Partition disks” menu. I then try to “Configure the Logical Volume Manager” but it does not allow me to complete any of the options (Volume Groups or Logical Volumes) because “No usable physical volumes found”. I believe I know how I want to partition my system but I do not know how to proceed. The docs I read indicate that because I am booting from SRM I must use FDISK, but I do not know how to find or run this program. The Debian Installer does have an option to “Execute a Shell” which runs “ash” using an editor called “nano”. It explains that “the root file system is a RAM disk”. Also “the hard disk file systems are mounted on ‘/target’”. However, once there I do not know how to find or run FDISK. So what? Well I don’t know if the first error I get is going to be a problem for me or not. Since it mentions DAC960, I may have some problems with my RAID storage devices. Since this has to do with storage, is it possible that I cannot partition my drives until this is resolved? Are there issues partitioning drives set up with RAID5? Should I partition *before* I run the Debian Installer? If so, how do I do this? Thanks again for your infinite Linux wisdom! Jim My system: AlphaServer 800 5/400 256MB RAM (128MB in each bank) Alphabios: v5.69 SRM: v5.4-113 Mylex DAC960 RAID Controller - Bank 0 (2007MB) - Bank 1 (8182MB) QLogic ISP SCSI Controller for CD-ROM A first step is to create a BSD disklabel on the disk. This may help: http://alum.wpi.edu/~tfraser/Stories/alphalinux.html
RE: Debian Installer - Problems Partitioning
Conny, Please forgive me for asking a stupid question. The instructions show how to create a BSD disklabel from a prompt like this: Command (m for help): I am at the main menu of the Debian Installer, how do I enter this command? The author, I believe, assumes you are already running FDISK, but I do not know how to run the FDISK program from within the Debian Installer. Jim -Original Message- From: Conny Enström [mailto:[EMAIL PROTECTED] Sent: Monday, May 31, 2004 6:55 PM To: Jim and Kelly Younkin Subject: Re: Debian Installer - Problems Partitioning - Original Message - From: Jim and Kelly Younkin To: debian-alpha@lists.debian.org Sent: Monday, May 31, 2004 9:45 PM Subject: Debian Installer - Problems Partitioning When I boot from the CD to install Sarge it automatically loads the Debian Installer. It prompts for language, and then begins. Problem #1: [?] Detect Network Hardware – Error while running ‘modprobe –v DAC960’ I press ‘Continue”… Problem #2: Let me describe… “Starting up the partitioner” brings me to a “Partition disks” main menu with five choices… o Finish partitioning and write changes to disk o Undo changes to partitions o Blank o Blank o Help on partitioning o Guided partitioning o Configure the Logical Volume Manager After reading “Help on Partitioning” I choose “Guided Partitioning”. I now see a menu with one option “Manually edit partition table”, so I choose that option, which returns me to the main “Partition disks” menu. I then try to “Configure the Logical Volume Manager” but it does not allow me to complete any of the options (Volume Groups or Logical Volumes) because “No usable physical volumes found”. I believe I know how I want to partition my system but I do not know how to proceed. The docs I read indicate that because I am booting from SRM I must use FDISK, but I do not know how to find or run this program. The Debian Installer does have an option to “Execute a Shell” which runs “ash” using an editor called “nano”. It explains that “the root file system is a RAM disk”. Also “the hard disk file systems are mounted on ‘/target’”. However, once there I do not know how to find or run FDISK. So what? Well I don’t know if the first error I get is going to be a problem for me or not. Since it mentions DAC960, I may have some problems with my RAID storage devices. Since this has to do with storage, is it possible that I cannot partition my drives until this is resolved? Are there issues partitioning drives set up with RAID5? Should I partition *before* I run the Debian Installer? If so, how do I do this? Thanks again for your infinite Linux wisdom! Jim My system: AlphaServer 800 5/400 256MB RAM (128MB in each bank) Alphabios: v5.69 SRM: v5.4-113 Mylex DAC960 RAID Controller - Bank 0 (2007MB) - Bank 1 (8182MB) QLogic ISP SCSI Controller for CD-ROM A first step is to create a BSD disklabel on the disk. This may help: http://alum.wpi.edu/~tfraser/Stories/alphalinux.html
