newbie installation problems: to charles
Hi charles, had the same problem i guess. what did i do to to resove it? a f t e r installation of bf24, woody asks you to log in. so log in as root. then do: apt-get install xserver-xfree86 and, after that to prevent that you only can log in with gdm: apt-get install kdm (or xdm) follow the questions in the (blue boxes on the konsole-screen and you will see your graphic interface appear, after you command something like 'startx' as root. thid all possibly on the following constraint: that you, as i did during the installation of bf24, a fine kernel, installed the debian security updates as well. it seems that installing these sec. updates blockades Xwindows to appear to install in taskel. good luck ps jan gave you allready a sound advice, zso it seems to me. but: maybe the advantage of my words is the ude of (almost aumatic) get-apt. goodluck, however, steef Date: Sat, 04 Oct 2003 09:35:09 +0200 To: Charles Forelle [EMAIL PROTECTED] CC: debian-us [EMAIL PROTECTED] On Sat, 2003-10-04 at 08:19, Charles Forelle wrote: Hello all, I'm in the midst of my first ever installation of Debian and I'm having trouble with the graphical interface. I've completed the process (installing the bf2.4 flavor with only desktop environment picked in tasksel -- I chose not to run dselect yet). The install complete with a text log-in prompt. I can login OK, both as the normal user I created and as root. But when I reboot, I get a message right after the login prompt appears that says: I cannot start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem? My choices: Yes or No. I pick Yes and get a blank gray box. My only choice is EXIT, which I pick. Then it says: Would you like me to try to run the X configuration program? Note that you will need the root password for this. I pick Yes and give the root password. Then I get: I will now try to restart the X server again. I pick OK, and after a second or two pause, I'm back to the original I cannot start the X server... message, whence I end up in an endless loop. Help! I'm totally flummoxed. Does anyone have a sense of what's gone wrong? With thanks, Charles. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Installation Problems
On Fri, Feb 14, 2003 at 10:18:16AM -0600, Craig Jackson wrote: On Fri, 2003-02-14 at 09:40, Rowland Fellows wrote: I am able to install 3.0 successfully from the disk images I've downloaded from Oregon State. However, once installed, the system goes directly into a login screen from which I cannot login into root. How to I get the system to boot in such a way that I can log in as root? You want to login to X as root? That's nearly[1] always a bad idea. Use sudo or su as Craig suggested. Log in as a regular user and su. If you didn't create a regular user during the install, it would be easy to ssh from another computer as root. Failing that, start Linux in single user mode by typing single after linux when lilo first starts. Or hit ctrl+alt+f1 to get to a VT. [1] As far as I can tell, it's never a good idea, but I bet someone will reply with some good reason to do it. -- Rob Weir [EMAIL PROTECTED] http://ertius.org/ msg30920/pgp0.pgp Description: PGP signature
Re: Newbie Installation Problems
On Fri, Feb 14, 2003 at 09:47:04PM -0800, Paul Johnson wrote: Fun fact: Today is Oregon Day. On this day in 1859, Oregon became the US's 33rd state, the result of the Vote at Champoeg, in which two Canadians wanted dead or alive tipped the vote from 49/50 to 51/50 in favor of becoming a US state instead of a Canadian province. Retrospectively, this is considered the worst thing to happen to Oregon as it leaves the international boundary on the wrong side of the state, something that has left us completely defenseless against political and migratory abuse by California (everybody stop moving here, Oregon's full now, not that anybody was welcome to begin with). Please take your tripe elsewhere. In the U.S. people are free to move from state to state without restriction. Get over it. Replace Californian with nigger/jew/whop/chink/irish/injun/wetback/etc. and see how palatable your xenophobia becomes. More people move to California in any given year than Oregon and California is similarly defenseless against these migrations. Since this is largely an economic decision, the solution lies in: (1) make Oregon a prohibitively expensive place to live; and (2) make Oregon a prohibitively expensive place to do business. If you succeed in both of those, I'm sure migrations will dwindle to a trickle. Of course, it might make Oregon a less desirable place to live for the natives as well. -- echo gra.fcw@2ztr eryyvZ .T pveR | rot13 | reverse -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Installation Problems
On Sat, Feb 15, 2003 at 11:57:03AM -0800, Eric G. Miller wrote: On Fri, Feb 14, 2003 at 09:47:04PM -0800, Paul Johnson wrote: Fun fact: Today is Oregon Day. On this day in 1859, Oregon became the US's 33rd state, the result of the Vote at Champoeg, in which two Canadians wanted dead or alive tipped the vote from 49/50 to 51/50 in favor of becoming a US state instead of a Canadian province. Retrospectively, this is considered the worst thing to happen to Oregon as it leaves the international boundary on the wrong side of the state, something that has left us completely defenseless against political and migratory abuse by California (everybody stop moving here, Oregon's full now, not that anybody was welcome to begin with). Please take your tripe elsewhere. In the U.S. people are free to move from state to state without restriction. Get over it. Replace Californian with nigger/jew/whop/chink/irish/injun/wetback/etc. and see how palatable your xenophobia becomes. More people move to California in any given year than Oregon and California is similarly defenseless against these migrations. Since this is largely an economic decision, the solution lies in: (1) make Oregon a prohibitively expensive place to live; and (2) make Oregon a prohibitively expensive place to do business. If you succeed in both of those, I'm sure migrations will dwindle to a trickle. Of course, it might make Oregon a less desirable place to live for the natives as well. -- Thank you very much. You are my new hero of the day. I was getting a little tired at the californian bashing as well. Ethnocentrism has little place in an otherwise noble organization such as this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Newbie Installation Problems
I am able to install 3.0 successfully from the disk images I've downloaded from Oregon State. However, once installed, the system goes directly into a login screen from which I cannot login into root. How to I get the system to boot in such a way that I can log in as root? Rowland Fellows 112 Feather Falls Circle Folsom, CA 95630 (916) 987-1670 (916) 768-9394 cell (707) 276-0849 fax [EMAIL PROTECTED]
Re: Newbie Installation Problems
On Fri, 2003-02-14 at 09:40, Rowland Fellows wrote: I am able to install 3.0 successfully from the disk images I've downloaded from Oregon State. However, once installed, the system goes directly into a login screen from which I cannot login into root. How to I get the system to boot in such a way that I can log in as root? Rowland Fellows 112 Feather Falls Circle Folsom, CA 95630 (916) 987-1670 (916) 768-9394 cell (707) 276-0849 fax [EMAIL PROTECTED] Log in as a regular user and su. If you didn't create a regular user during the install, it would be easy to ssh from another computer as root. Failing that, start Linux in single user mode by typing single after linux when lilo first starts. -- Craig Jackson [EMAIL PROTECTED] Wildnet Group L.L.C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Installation Problems
On Fri, Feb 14, 2003 at 07:25:14AM -0800, Rowland Fellows wrote: However, once installed, the system goes directly into a login screen from which I cannot login into root. What happens when you try and login as root? [on console] by default you can login as root on console or by ssh [as long as sshd is running]. hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Installation Problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Freitag, 14. Februar 2003 16:25 schrieb Rowland Fellows: I am able to install 3.0 successfully from the disk images I've downloaded from Oregon State. However, once installed, the system goes directly into a login screen from which I cannot login into root. How to I get the system to boot in such a way that I can log in as root? Hi, Is it a graphical login? If yes try hitting CTRL-ALT-F1, so you get an text login screen. There you should be able to login as root. (if you dont forgot your root password ;o) Robert -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+TTZAILH3kR/OabQRAjeZAKCSd1+pX7lUn+F78yarGUvKnrTxwwCeNc1H ixWaGciLGvR6xrMf6m/r57M= =Jwsy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Installation Problems
If I understand your problem correctly, this might help: log in with regular user name su (enter root's password) cat /etc/gdm/gdm.conf Look through the list for 'AllowRoot=_' If it says 'false', run an editor and change it to 'true'. Then save. Alex Rowland Fellows wrote: I am able to install 3.0 successfully from the disk images I've downloaded from Oregon State. However, once installed, the system goes directly into a login screen from which I cannot login into root. How to I get the system to boot in such a way that I can log in as root? Rowland Fellows 112 Feather Falls Circle Folsom, CA 95630 (916) 987-1670 (916) 768-9394 cell (707) 276-0849 fax [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Installation Problems
On Fri, Feb 14, 2003 at 07:25:14AM -0800, Rowland Fellows wrote: I am able to install 3.0 successfully from the disk images I've downloaded from Oregon State. Fun fact: Today is Oregon Day. On this day in 1859, Oregon became the US's 33rd state, the result of the Vote at Champoeg, in which two Canadians wanted dead or alive tipped the vote from 49/50 to 51/50 in favor of becoming a US state instead of a Canadian province. Retrospectively, this is considered the worst thing to happen to Oregon as it leaves the international boundary on the wrong side of the state, something that has left us completely defenseless against political and migratory abuse by California (everybody stop moving here, Oregon's full now, not that anybody was welcome to begin with). However, once installed, the system goes directly into a login screen from which I cannot login into root. How to I get the system to boot in such a way that I can log in as root? Do not log in as root. Use su instead. If you have to run something graphical as root, as a normal user type xhost +local:localhost, then run the command as root using su. Don't log in as root. -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Oregonian. `. `'` `- Oregon. We're the anti-California. msg30868/pgp0.pgp Description: PGP signature
Re: Newbie: Installation problems
I'm no expert on this either but try these settings: /dev/hdn -instead of n you select b, c or d Why so? go here: http://www.debian.de/releases/slink/i386/install and look in section 4.3 maybe this helps On 7 May 1999 16:38:36 +0200, Sudhir P [EMAIL PROTECTED] wrote: Hi, Please excuse me for the wide distribution. And do excuse me for not being able to give the exact technical terms in the following. I have tried to explain the situation to the best extent that I can (now). My present set up: -- I have an i586 system in which I have dos, linux (Redhat and Debian) installed (after lot of goof-ups and struggles, being a novice that I am). The partition details are as follows /dev/hda1 - DOS /dev/hda2 - Linux partition (I suppose, I am not very confortable with this naming convention, so please excuse me) /dev/hda5 - RedHat Linux (kernel - 2.0.36) /dev/hda6 - Swap space (common to both Redhat and Debian) /dev/hda7 - Debian Linux (kernel - 2.0.36) The MBR contains the LILO. My lilo.conf in /dev/hda5 (Redhat) contains details of the setup, and the details about Debian kernel (being present in /dev/hda7, boot-label=debian). I am assuming that this is where it is taking information from when I type debian at my lilo prompt, the kernel being loaded from /dev/hda7. Dos (Windows-95) and Redhat are fully operational. There is some problem with debian however. I am not able to go beyond the base-kernel installation. I have configured in the kernel to support cd-roms with the common CD-ROMs option that is available for CD-ROM device drivers. There is a part of the installation where u have to give details about the access medium (default being /dev/cdrom). When I accept this as my default or even type in /dev/cdrom, it is reported as an error. It says that it is unable to find the device (even though installation is going on from the device). If I go to another virtual-terminal and try: mount /dev/cdrom, it gives an error message stating that there is no entry in the /etc/fstab. If I make an entry in the same, and issue mount /dev/cdroom, an error message stating that the kernel doesn't support this filesystem (iso9660) is issued. I am unable to go beyond this. No packages are being installed as I haven't been able to specify /dev/cdrom as my source. I hope that I have explained the situation clearly enough. In case you require more details, please mail me. Thanks in advance. Regards, Sudhir.P -- When you hit rock bottom, there is no way, but, up. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Newbie: Installation problems
On %M 0, Sudhir P wrote Hi, Please excuse me for the wide distribution. And do excuse me for not being able to give the exact technical terms in the following. I have tried to explain the situation to the best extent that I can (now). My present set up: -- I have an i586 system in which I have dos, linux (Redhat and Debian) installed (after lot of goof-ups and struggles, being a novice that I am). The partition details are as follows /dev/hda1 - DOS /dev/hda2 - Linux partition (I suppose, I am not very confortable with this naming convention, so please excuse me) /dev/hda5 - RedHat Linux (kernel - 2.0.36) /dev/hda6 - Swap space (common to both Redhat and Debian) /dev/hda7 - Debian Linux (kernel - 2.0.36) The MBR contains the LILO. My lilo.conf in /dev/hda5 (Redhat) contains details of the setup, and the details about Debian kernel (being present in /dev/hda7, boot-label=debian). I am assuming that this is where it is taking information from when I type debian at my lilo prompt, the kernel being loaded from /dev/hda7. Dos (Windows-95) and Redhat are fully operational. There is some problem with debian however. I am not able to go beyond the base-kernel installation. I have configured in the kernel to support cd-roms with the common CD-ROMs option that is available for CD-ROM device drivers. There is a part of the installation where u have to give details about the access medium (default being /dev/cdrom). When I accept this as my default or even type in /dev/cdrom, it is reported as an error. It says that it is unable to find the device (even though installation is going on from the device). If I go to another virtual-terminal and try: mount /dev/cdrom, it gives an error message stating that there is no entry in the /etc/fstab. If I make an entry in the same, and issue mount /dev/cdroom, an error message stating that the kernel doesn't support this filesystem (iso9660) is issued. I am unable to go beyond this. No packages are being installed as I haven't been able to specify /dev/cdrom as my source. There are several things you should check: - Does /dev/cdrom actually exist? - Is it a symlink pointing to your CDROM drive (e.g., - /dev/hdb)? - Is isofs module loaded? Can you load it with 'modprobe isofs'? - Is your entry for /dev/cdrom in /etc/fstab correct? It should look something like /dev/cdrom /cdrom iso9660 defaults,ro 0 0 - Does the mount point listed in /etc/fstab (/cdrom, in the example above) exist (and is it a directory)? - Can you mount /dev/cdrom now, after checking the above? - If so, *and* you were able to load the isofs module manually, then either add 'isofs' to /etc/modules, or install kerneld. Hope this helps, John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] Oh - I - you know - my job is to fear everything. - Bill Gates in Denmark
Newbie: Installation problems
Hi, Please excuse me for the wide distribution. And do excuse me for not being able to give the exact technical terms in the following. I have tried to explain the situation to the best extent that I can (now). My present set up: -- I have an i586 system in which I have dos, linux (Redhat and Debian) installed (after lot of goof-ups and struggles, being a novice that I am). The partition details are as follows /dev/hda1 - DOS /dev/hda2 - Linux partition (I suppose, I am not very confortable with this naming convention, so please excuse me) /dev/hda5 - RedHat Linux (kernel - 2.0.36) /dev/hda6 - Swap space (common to both Redhat and Debian) /dev/hda7 - Debian Linux (kernel - 2.0.36) The MBR contains the LILO. My lilo.conf in /dev/hda5 (Redhat) contains details of the setup, and the details about Debian kernel (being present in /dev/hda7, boot-label=debian). I am assuming that this is where it is taking information from when I type debian at my lilo prompt, the kernel being loaded from /dev/hda7. Dos (Windows-95) and Redhat are fully operational. There is some problem with debian however. I am not able to go beyond the base-kernel installation. I have configured in the kernel to support cd-roms with the common CD-ROMs option that is available for CD-ROM device drivers. There is a part of the installation where u have to give details about the access medium (default being /dev/cdrom). When I accept this as my default or even type in /dev/cdrom, it is reported as an error. It says that it is unable to find the device (even though installation is going on from the device). If I go to another virtual-terminal and try: mount /dev/cdrom, it gives an error message stating that there is no entry in the /etc/fstab. If I make an entry in the same, and issue mount /dev/cdroom, an error message stating that the kernel doesn't support this filesystem (iso9660) is issued. I am unable to go beyond this. No packages are being installed as I haven't been able to specify /dev/cdrom as my source. I hope that I have explained the situation clearly enough. In case you require more details, please mail me. Thanks in advance. Regards, Sudhir.P -- When you hit rock bottom, there is no way, but, up.
Re: Newbie: Installation problems
Sudhir P wrote: Hi, Please excuse me for the wide distribution. And do excuse me for not being able to give the exact technical terms in the following. I have tried to explain the situation to the best extent that I can (now). My present set up: -- I have an i586 system in which I have dos, linux (Redhat and Debian) installed (after lot of goof-ups and struggles, being a novice that I am). The partition details are as follows /dev/hda1 - DOS /dev/hda2 - Linux partition (I suppose, I am not very confortable with this naming convention, so please excuse me) /dev/hda5 - RedHat Linux (kernel - 2.0.36) /dev/hda6 - Swap space (common to both Redhat and Debian) /dev/hda7 - Debian Linux (kernel - 2.0.36) The MBR contains the LILO. My lilo.conf in /dev/hda5 (Redhat) contains details of the setup, and the details about Debian kernel (being present in /dev/hda7, boot-label=debian). I am assuming that this is where it is taking information from when I type debian at my lilo prompt, the kernel being loaded from /dev/hda7. Dos (Windows-95) and Redhat are fully operational. There is some problem with debian however. I am not able to go beyond the base-kernel installation. I have configured in the kernel to support cd-roms with the common CD-ROMs option that is available for CD-ROM device drivers. There is a part of the installation where u have to give details about the access medium (default being /dev/cdrom). When I accept this as my default or even type in /dev/cdrom, it is reported as an error. It says that it is unable to find the device (even though installation is going on from the device). If I go to another virtual-terminal and try: mount /dev/cdrom, it gives an error message stating that there is no entry in the /etc/fstab. If I make an entry in the same, and issue mount /dev/cdroom, an error message stating that the kernel doesn't support this filesystem (iso9660) is issued. I am unable to go beyond this. No packages are being installed as I haven't been able to specify /dev/cdrom as my source. I hope that I have explained the situation clearly enough. In case you require more details, please mail me. It appeares that you did not install the cd rom (or if its ATPI type) when you installed the first time. In either case the situation is resolved by recompiling the kernel to support the necessary files systems and hardware. You should be able to get a modem running or if you have a direct internet connection ; use dselect to install the necessary applications for recompiling the kernel. Read the Kernel HOWTO in directory /usr/docs. That is where all/most of the docummentation for Debian is stored. Good Luck!!begin:vcard n:Foster;John x-mozilla-html:FALSE url:http://www.advance-computing.com org:AdVance-Computing Systems;WHQ version:2.1 email;internet:[EMAIL PROTECTED] title:Owner note:We Build Multi-Processor Computers adr;quoted-printable:;;Stonetrail Drive=0D=0ASuite A;Plano;Texas;75023-7223;USA x-mozilla-cpt:;22240 fn:John Foster end:vcard
Re: Newbie: Installation problems
On a i586 system, your cdrom is probably connected to the second IDE controller and it will be on /dev/hdc or less likely /dev/hdd. Try using that during the installation. /dev/cdrom is usually a link that points to /dev/hdc or /dev/hdd. If Redhat works, boot into Redhat and look at /etc/fstab. See if there is a line mentioning the cdrom. You can even send your redhat fstab. Hi, Please excuse me for the wide distribution. And do excuse me for not being able to give the exact technical terms in the following. I have tried to explain the situation to the best extent that I can (now). My present set up: -- I have an i586 system in which I have dos, linux (Redhat and Debian) installed (after lot of goof-ups and struggles, being a novice that I am). The partition details are as follows /dev/hda1 - DOS /dev/hda2 - Linux partition (I suppose, I am not very confortable with this naming convention, so please excuse me) /dev/hda5 - RedHat Linux (kernel - 2.0.36) /dev/hda6 - Swap space (common to both Redhat and Debian) /dev/hda7 - Debian Linux (kernel - 2.0.36) The MBR contains the LILO. My lilo.conf in /dev/hda5 (Redhat) contains details of the setup, and the details about Debian kernel (being present in /dev/hda7, boot-label=debian). I am assuming that this is where it is taking information from when I type debian at my lilo prompt, the kernel being loaded from /dev/hda7. Dos (Windows-95) and Redhat are fully operational. There is some problem with debian however. I am not able to go beyond the base-kernel installation. I have configured in the kernel to support cd-roms with the common CD-ROMs option that is available for CD-ROM device drivers. There is a part of the installation where u have to give details about the access medium (default being /dev/cdrom). When I accept this as my default or even type in /dev/cdrom, it is reported as an error. It says that it is unable to find the device (even though installation is going on from the device). If I go to another virtual-terminal and try: mount /dev/cdrom, it gives an error message stating that there is no entry in the /etc/fstab. If I make an entry in the same, and issue mount /dev/cdroom, an error message stating that the kernel doesn't support this filesystem (iso9660) is issued. I am unable to go beyond this. No packages are being installed as I haven't been able to specify /dev/cdrom as my source. I hope that I have explained the situation clearly enough. In case you require more details, please mail me. Thanks in advance. Regards, Sudhir.P -- When you hit rock bottom, there is no way, but, up. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Newbie installation problems
Wondering if someone could help me.I'm trying to change over from Win 95 to Debian, which would be fine if I could actually get the latter installed. I'm using a Cheapbytes CD, and BIOS is set up to boot from the CD drive. I press ENTER at the boot prompt, and a lot of technical info flashes past on the screen, before everything comes to a complete halt. No bootlog, since I can't actually get that far, so excuse my vague explanations! I did manage to write down what was on screen at the time: Ramdisk driver initialized: 16 ramdisks of 4096K size loop: registered device at major 7 hda: SAMSUNG VG34323A (4.32GB) gq033, 4124MB w/496KB cache, VHS=525/255/63 hdb: CD-ROM 24x/AKOx, ATAP CDROM drive hdc: WdC AC31000H, 1033MB w/128KB cache, CHS=2100/16/63 hdd: M1614TA, 1040MB w/64KB cache, CHS=2114/16/63 ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14 ide1 at 0x170-0x177, 0x3f6 on irq 15 Floppy drive(s): fd0 is 1.44M FDC is a post-1991 82077 md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 At which point everything just stops. No reboot, no error message. I left it for 10 minutes one time, and nothing happened. My setup is: AMD K6 2 300 Samsung 4.32 GB IDE HD Western digital 1GB IDE HD (that I want to put Debian on) M1614TA IGB IDE HD Philips 24x CDROM Soundblaster clone Cirrus Logic 5436 PCI display adapter Samsung Syncmaster 3 monitor No SCSI cards/HDs, and I don't have any of the hardware mentioned in the boot help options. I checked the Linux Hardware Compatability FAQ, and I don't seem to have any hardware that could cause a problem as far as I know. What am I missing? Why does it stop straight after the md driver line? It's probably something really obvious that I'm overlooking...I'd be really grateful for any help.
Re: Newbie installation problems
Hello Rebecca: I am not a 100% certain but I think there are some problems with the cheap bytes distribution. If you can, create a boot floppy. The tools should be in the tools section of the CD you have. hint rawrite2. I have installed cheap bytes using a floppy and the provided CD. Boot from floppy Peter Rebecca Naylor wrote: Wondering if someone could help me.I'm trying to change over from Win 95 to Debian, which would be fine if I could actually get the latter installed. I'm using a Cheapbytes CD, and BIOS is set up to boot from the CD drive. I press ENTER at the boot prompt, and a lot of technical info flashes past on the screen, before everything comes to a complete halt. No bootlog, since I can't actually get that far, so excuse my vague explanations! I did manage to write down what was on screen at the time: Ramdisk driver initialized: 16 ramdisks of 4096K size loop: registered device at major 7 hda: SAMSUNG VG34323A (4.32GB) gq033, 4124MB w/496KB cache, VHS=525/255/63 hdb: CD-ROM 24x/AKOx, ATAP CDROM drive hdc: WdC AC31000H, 1033MB w/128KB cache, CHS=2100/16/63 hdd: M1614TA, 1040MB w/64KB cache, CHS=2114/16/63 ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14 ide1 at 0x170-0x177, 0x3f6 on irq 15 Floppy drive(s): fd0 is 1.44M FDC is a post-1991 82077 md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 At which point everything just stops. No reboot, no error message. I left it for 10 minutes one time, and nothing happened. My setup is: AMD K6 2 300 Samsung 4.32 GB IDE HD Western digital 1GB IDE HD (that I want to put Debian on) M1614TA IGB IDE HD Philips 24x CDROM Soundblaster clone Cirrus Logic 5436 PCI display adapter Samsung Syncmaster 3 monitor No SCSI cards/HDs, and I don't have any of the hardware mentioned in the boot help options. I checked the Linux Hardware Compatability FAQ, and I don't seem to have any hardware that could cause a problem as far as I know. What am I missing? Why does it stop straight after the md driver line? It's probably something really obvious that I'm overlooking...I'd be really grateful for any help. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null begin: vcard fn: Peter Iannarelli n: Iannarelli;Peter org:GenX Internet Laboratories Inc. adr:20 Madison Ave.;;;Toronto;Ontario;M5R 2S1;Canada email;internet: [EMAIL PROTECTED] title: Engineer tel;work: 1+ 416 929 1885 tel;fax:1+ 416 929 1056 note: Unix/Linux Support x-mozilla-cpt: ;0 x-mozilla-html: FALSE version:2.1 end:vcard
Re: Newbie installation problems
Hi Rebecca; I am a newbie too, I am also switching from W95 to Debian. I installed Debian from a floppy set and its smooth -- no problem at all or alternatively if you like, you can install it from your hard disk. Files to get if from floppy: (asumming your floppy is 3.5 1.44M at drive A:) 1. rawrite2.exe (a dos program for writing Debian image files to floppies) 2. resc1440.bin (boot / setup disk can be created by using the rawrite2.exe) 3. drv1440.bin (driver image) 4. base14-1.bin to base14-5.bin (base/core program files) 5. install.txt (or the Html page at http://www.debian.org/2.0/install.html) Files to get if installed from hard disk (which is also suitable for you to copy your files from your Cheapbyte CD) 1. resc1440.bin (in case you need to write a boot floppy) 2. drv1440.bin 3. base2_0.tgz (core program files) 4. root.bin 3.loadlin.exe 4. install.bat 5. linux 6.install.txt or install.html All the above files or information can be obtained in http://www.debian.org/2.0/install.html#Installation Enjoy Rebecca Naylor wrote: Wondering if someone could help me.I'm trying to change over from Win 95 to Debian, which would be fine if I could actually get the latter installed. I'm using a Cheapbytes CD, and BIOS is set up to boot from the CD drive. I press ENTER at the boot prompt, and a lot of technical info flashes past on the screen, before everything comes to a complete halt. No bootlog, since I can't actually get that far, so excuse my vague explanations! I did manage to write down what was on screen at the time: Ramdisk driver initialized: 16 ramdisks of 4096K size loop: registered device at major 7 hda: SAMSUNG VG34323A (4.32GB) gq033, 4124MB w/496KB cache, VHS=525/255/63 hdb: CD-ROM 24x/AKOx, ATAP CDROM drive hdc: WdC AC31000H, 1033MB w/128KB cache, CHS=2100/16/63 hdd: M1614TA, 1040MB w/64KB cache, CHS=2114/16/63 ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14 ide1 at 0x170-0x177, 0x3f6 on irq 15 Floppy drive(s): fd0 is 1.44M FDC is a post-1991 82077 md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 At which point everything just stops. No reboot, no error message. I left it for 10 minutes one time, and nothing happened. My setup is: AMD K6 2 300 Samsung 4.32 GB IDE HD Western digital 1GB IDE HD (that I want to put Debian on) M1614TA IGB IDE HD Philips 24x CDROM Soundblaster clone Cirrus Logic 5436 PCI display adapter Samsung Syncmaster 3 monitor No SCSI cards/HDs, and I don't have any of the hardware mentioned in the boot help options. I checked the Linux Hardware Compatability FAQ, and I don't seem to have any hardware that could cause a problem as far as I know. What am I missing? Why does it stop straight after the md driver line? It's probably something really obvious that I'm overlooking...I'd be really grateful for any help. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
