Re: [Cooker] cdrom.img
Stéphane Teletchéa <[EMAIL PROTECTED]> writes: > How can i reproduce cdrom.img with my own kernel (does drakx allows me to do > that ?) the easiest solution is to use blank.img (from images/README) blank.img: install with a home-made kernel : you need to copy this image on a floppy, then copy the kernel as a file named "vmlinuz" on the floppy (be careful, modules support is disabled so please include all needed network card drivers and everything in your kernel)
Re: [Cooker] cdrom.img
Stéphane Teletchéa <[EMAIL PROTECTED]> writes: > How can i reproduce cdrom.img with my own kernel (does drakx allows me to do > that ?) > Thanks in advance, Stef the easiest is to build your own monolithic kernel (e.g. without modules) and to put it on "blank.img"-made floppy. -- Guillaume Cottenceau - http://www.frozen-bubble.org/
Re: [Cooker] cdrom.img and resolution (beta3)
Stefan Siegel <[EMAIL PROTECTED]> writes:
> Hello,
>
> this morning I asked a friend of mine who never installed linux so far
> to install the 7.1 beta3 on my box (I plugged my external scsi disk
> (an excahne disk with nothing usefull on it)). He tried to install it
> with cdrom.img which I made under my working linux ...
>
> * Frist problems arised, as the CD-Rom was not recognized by the
> installer. He got a message saying there were no linux mandrake on
> that cd-rom (so far so bad - the beta3 was in the drive), but by
> pressing ok (the only button available), he got "initializing
> cd-rom" which failed, as DrakX thaught there were no mandrake cd-rom
> in the drive ... :-(
>
> It figured out correctlt that I have an adaptec card and also found my
> 2 cd-rom drives ...
>
> on 3rd try we switched to the second drive (a cd burner) and used
> scd1 instead of scd0 which worked fine ... so my freind went on.
>
> * At the end of the install he choose the correct monitor fron the list
> (instead of "svga ...") and ended up with a very poor resolution of
> 640x400 as he had no resolution or graphics card alternatives ...
> His only comment "Windows is able of presentig a better resolution, so
> why using linux ..." => please ask the user which resolution he wants
> even if he choosed automatic install ...
>
> * BTW why is kcmlaptop installed on a normal pc (not a laptop) ???
it shouldn't
>
> --
> _
> Tschüss und bis demnächst/à bientôt, _|_|_
>(") *
> Stefan /v\ /
> /( )X Penguin Powered!
> ++(m-m)--+
> | Stefan Siegel | http://www.student.uni-kl.de/~siegel/ |
> | Kurt-Schumacher-Str. 34 / App. 144 | mailto:[EMAIL PROTECTED]|
> | D-67663 Kaiserslautern | PGP Public Key: |
> | Tel.: +49-631-18269| finger -l [EMAIL PROTECTED] |
> ++---+
Re: [Cooker] cdrom.img and such.. what I did..
Bobby Dowling <[EMAIL PROTECTED]> writes: > Well, that is my kernel version ...wonder why ata/66 wasn't enabled without me > recompiling? what is the type of your card ? -- MandrakeSoft Inchttp://www.mandrakesoft.com In travel.--Chmouel
Re: [Cooker] cdrom.img and such.. what I did..
On Mon, 08 May 2000, you wrote: > Bobby Dowling wrote: > > > Well, I am not sure what kernel version you are talking about. When I > > installed my ata/66 controllers and drives were recognized and ready for use, > > though to actually get ata/66 I had to specify that option in the kernel. Btw, > > I did not install a 'new' kernel. I installed whatever kernel installed with > > 7.1 b2. > > kernel version -2.2.15-1mdk Well, that is my kernel version ...wonder why ata/66 wasn't enabled without me recompiling? Bobby Dowling
Re: [Cooker] cdrom.img and such.. what I did..
Bobby Dowling wrote: > Well, I am not sure what kernel version you are talking about. When I > installed my ata/66 controllers and drives were recognized and ready for use, > though to actually get ata/66 I had to specify that option in the kernel. Btw, > I did not install a 'new' kernel. I installed whatever kernel installed with > 7.1 b2. kernel version -2.2.15-1mdk
Re: [Cooker] cdrom.img and such.. what I did..
Well, I am not sure what kernel version you are talking about. When I installed my ata/66 controllers and drives were recognized and ready for use, though to actually get ata/66 I had to specify that option in the kernel. Btw, I did not install a 'new' kernel. I installed whatever kernel installed with 7.1 b2. You are correct about getting atapi writers to work. On Mon, 08 May 2000, you wrote: > Bobby Dowling wrote: > > > Not true ...I had to recompile to get ata/66 support ...also I had to > > include scsi support and then create /dev/scd* links before my writer would > > work ...unless there is something i don't know about getting it to work > > without scsi emulation > > > > True. I installed the new kernel and it immediately recognizes my ata/66 > controller and drives. Didn't have to set anything. As for as setting the > IDE-CD burner working, it's well documented and there have been numerous > messages explaining the procedure. > > > > > > On Sun, 07 May 2000, you wrote: > > > ramses <[EMAIL PROTECTED]> writes: > > > > > > > Next I recompiled the kernel and enabled my > > > > promise controller support under block devices, > > > > and I also enabled use UDMA as default, > > > > saved information and compiled. Did the proper > > > > steps, rebooted and I had ata/66 support. > > > > > > why ? the kernel should be compiled with ATA/66 builtins. > > > > > > -- > > > MandrakeSoft Inchttp://www.mandrakesoft.com > > > In travel.--Chmouel > > -- > > Bobby Dowling -- Bobby Dowling
Re: [Cooker] cdrom.img and such.. what I did..
Bobby Dowling wrote: > Not true ...I had to recompile to get ata/66 support ...also I had to > include scsi support and then create /dev/scd* links before my writer would > work ...unless there is something i don't know about getting it to work > without scsi emulation > True. I installed the new kernel and it immediately recognizes my ata/66 controller and drives. Didn't have to set anything. As for as setting the IDE-CD burner working, it's well documented and there have been numerous messages explaining the procedure. > > On Sun, 07 May 2000, you wrote: > > ramses <[EMAIL PROTECTED]> writes: > > > > > Next I recompiled the kernel and enabled my > > > promise controller support under block devices, > > > and I also enabled use UDMA as default, > > > saved information and compiled. Did the proper > > > steps, rebooted and I had ata/66 support. > > > > why ? the kernel should be compiled with ATA/66 builtins. > > > > -- > > MandrakeSoft Inchttp://www.mandrakesoft.com > > In travel.--Chmouel > -- > Bobby Dowling
Re: [Cooker] cdrom.img and such.. what I did..
Not true ...I had to recompile to get ata/66 support ...also I had to include scsi support and then create /dev/scd* links before my writer would work ...unless there is something i don't know about getting it to work without scsi emulation On Sun, 07 May 2000, you wrote: > ramses <[EMAIL PROTECTED]> writes: > > > Next I recompiled the kernel and enabled my > > promise controller support under block devices, > > and I also enabled use UDMA as default, > > saved information and compiled. Did the proper > > steps, rebooted and I had ata/66 support. > > why ? the kernel should be compiled with ATA/66 builtins. > > -- > MandrakeSoft Inchttp://www.mandrakesoft.com > In travel.--Chmouel -- Bobby Dowling
Re: [Cooker] cdrom.img and such.. what I did..
At 04:30 PM 5/7/00 +0200, Chmouel Boudjnah wrote: >ramses <[EMAIL PROTECTED]> writes: > >> Next I recompiled the kernel and enabled my >> promise controller support under block devices, >> and I also enabled use UDMA as default, >> saved information and compiled. Did the proper >> steps, rebooted and I had ata/66 support. > >why ? the kernel should be compiled with ATA/66 builtins. > It's not. After the install via text mode (because of the issues with the graphical installer using the new cdrom.img), UDMA was not enabled by defualt. I was getting like 4.5 mb/sec on the 64mb test using hdparm -itT /dev/hde... after enabling UDMA and promise controller under block devices in kernel and recompiling I am not getting around 28mb/sec on the 64mb test.
Re: [Cooker] cdrom.img and such.. what I did..
ramses <[EMAIL PROTECTED]> writes: > Next I recompiled the kernel and enabled my > promise controller support under block devices, > and I also enabled use UDMA as default, > saved information and compiled. Did the proper > steps, rebooted and I had ata/66 support. why ? the kernel should be compiled with ATA/66 builtins. -- MandrakeSoft Inchttp://www.mandrakesoft.com In travel.--Chmouel
Re: [Cooker] cdrom.img and such.. what I did..
ramses <[EMAIL PROTECTED]> writes: [...] > There are some issues with the text install, when you get > to partitions, it has a set number of dirs you can make.. > so I couldn't make a /root directory, so I just used a > larger partition size for / so I could have room for /root > as well. ok, added /root
Re: [Cooker] cdrom.img and such.. what I did..
For anyone out there having problems installing Mandrake 7.1 beta because of the ata/66 glitch, here are some suggestions. First off I downloaded the cdrom.img file from the following location: ftp://ftp.mandrakesoft.com/pub/pixel/cdrom.img Once you have done this, I placed the Mandrake 7.1 beta cdrom (by the way I am using beta 2) in my wifes computer (win98 se) and went to my computer and selected open for the mandrake cd, went to dosutils, and the ran rawritewin and chose the download path to the source of the cdrom.img file, inserted a blank floppy, then clicked on write. After this had completed I put the floppy in my computer and the mandrake 7.1 beta 2 in my cdrom drive. Booted off the floppy, when the install screen came up I selected F1 so I could get to the boot prompt menu and then typed text so I would get a text install (there is something wrong with the graphical install, but you can try it -- the video was all screwed up). There are some issues with the text install, when you get to partitions, it has a set number of dirs you can make.. so I couldn't make a /root directory, so I just used a larger partition size for / so I could have room for /root as well. It will not install the second cdrom that is available for download. After the installation had complete I used DrakRPM to install the rest of the packages I needed. Using this method I got Xfree86 4.0 setup on my GeForce DDR at 1600x1200 with 32 bit color depth. I had to use XFdrake, and change the card to a DDR in order for it to let me use 32 bit, otherwise it would just let me use 16 bit.. I also edited the XF86Config-4 and XF86Config to make sure my default color depth used 32 bit.. Next I recompiled the kernel and enabled my promise controller support under block devices, and I also enabled use UDMA as default, saved information and compiled. Did the proper steps, rebooted and I had ata/66 support. hdparm -itT /dev/hde reported 145mb/sec for 128mb test, and 64mb was 28 mb/sec.
Re: [Cooker] cdrom.img problems
I have went to several mirrors, and all the cdrom.img files I have found do not work properly. The one I got from Pixels directory on ftp.mandrakesoft worked, but you could not install graphically (which takes a lot of powerful tools away from you), and the text mode did not install second cdrom (stops ay 75% of install and goes to post install). I checked the mirror on tucows (the cdrom.img file from the cooker dir) and it can not detect my IDE CDROM properly. So still a lot of issues on the installation it seems. Is there a cdrom.img that works (Pixel noted there was from cooker, but exactly which FTP site??) Thanks
Re: [Cooker] cdrom.img file
I usually just look at the dates ... - Original Message - From: "ramses" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 06, 2000 5:28 PM Subject: Re: [Cooker] cdrom.img file > At 11:59 PM 5/6/00 +0200, you wrote: > >ramses <[EMAIL PROTECTED]> writes: > > > >> Greetings, > >> > >> I downloaded the new cdrom.img file to get around the bug in the > >> two beta's (not being able to install on a ata/66) drive. The > >> cdrom.img file will not work for a graphical install and on the > >> text install there are a couple of issues. First you can not > >> make a partition /root, second it does not ask for the 2nd > >> cdrom to install the rest of the components that are included > >> with that cd. So any plans for an updated cdrom.img > >> file that works correctly? > > > >you have to download the new cooker... > > > > hehe, what is the "new cooker"?? and where can I get it.. how big is it? > darn it.. > >
Re: [Cooker] cdrom.img file
Where can I download the latest cooker and be sure it is the absolute latest ...live in texas, usa, btw Thanks, Bobby - Original Message - From: "Pixel" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 06, 2000 4:59 PM Subject: Re: [Cooker] cdrom.img file > ramses <[EMAIL PROTECTED]> writes: > > > Greetings, > > > > I downloaded the new cdrom.img file to get around the bug in the > > two beta's (not being able to install on a ata/66) drive. The > > cdrom.img file will not work for a graphical install and on the > > text install there are a couple of issues. First you can not > > make a partition /root, second it does not ask for the 2nd > > cdrom to install the rest of the components that are included > > with that cd. So any plans for an updated cdrom.img > > file that works correctly? > > you have to download the new cooker... > >
Re: [Cooker] cdrom.img file
At 11:59 PM 5/6/00 +0200, you wrote: >ramses <[EMAIL PROTECTED]> writes: > >> Greetings, >> >> I downloaded the new cdrom.img file to get around the bug in the >> two beta's (not being able to install on a ata/66) drive. The >> cdrom.img file will not work for a graphical install and on the >> text install there are a couple of issues. First you can not >> make a partition /root, second it does not ask for the 2nd >> cdrom to install the rest of the components that are included >> with that cd. So any plans for an updated cdrom.img >> file that works correctly? > >you have to download the new cooker... > hehe, what is the "new cooker"?? and where can I get it.. how big is it? darn it..
Re: [Cooker] cdrom.img file
ramses <[EMAIL PROTECTED]> writes: > Greetings, > > I downloaded the new cdrom.img file to get around the bug in the > two beta's (not being able to install on a ata/66) drive. The > cdrom.img file will not work for a graphical install and on the > text install there are a couple of issues. First you can not > make a partition /root, second it does not ask for the 2nd > cdrom to install the rest of the components that are included > with that cd. So any plans for an updated cdrom.img > file that works correctly? you have to download the new cooker...
Re: [Cooker] cdrom.img file
Greetings, I downloaded the new cdrom.img file to get around the bug in the two beta's (not being able to install on a ata/66) drive. The cdrom.img file will not work for a graphical install and on the text install there are a couple of issues. First you can not make a partition /root, second it does not ask for the 2nd cdrom to install the rest of the components that are included with that cd. So any plans for an updated cdrom.img file that works correctly?
Re: [Cooker] cdrom.img
Pixel wrote: > ptah <[EMAIL PROTECTED]> writes: > > > Where can I get this latest chdrom.img file that will work with > > ata/66? Thanks. > > on any mandrake devel mirror. as of 11:04 the hd,img is still messed up i can not use it, it says modprobe ide failed or something like that in the console. -DarkWlf
Re: [Cooker] cdrom.img
ptah <[EMAIL PROTECTED]> writes: > Where can I get this latest chdrom.img file that will work with > ata/66? Thanks. on any mandrake devel mirror.
Re: [Cooker] cdrom.img
Where can I get this latest chdrom.img file that will work with ata/66? Thanks.
