Re: [Cooker] Problem network install using network.img
Frederik Himpe <[EMAIL PROTECTED]> writes:
[...]
> - There seems to be wrong with the locale settings, every time I start
> one of the Mandrake tools, I got this output from perl:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = "en_GB:en",
> LC_ALL = (unset),
> LC_PAPER = "fr_BE",
> LC_ADDRESS = "fr_BE",
> LC_MONETARY = "fr_BE",
> LC_NUMERIC = "fr_BE",
> LC_TELEPHONE = "fr_BE",
> LC_MESSAGES = "en_GB",
> LC_COLLATE = "en_GB",
> LC_IDENTIFICATION = "fr_BE",
> LC_MEASUREMENT = "fr_BE",
> LC_CTYPE = "en_GB",
> LC_TIME = "en_GB",
> LC_NAME = "fr_BE",
> LANG = "en_GB"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> Strange, because I cannot remember having chosen French somewhere (I did
> choose Belgium as country however). So I have no French locales installed:
I do have a bug (forgetting to install the locales-xx package
when the country doesn't pertain to the same locale as the
language), fixing it right now.
> # rpm -qa *locales*
> locales-en-2.3.1.4-3mdk
> locales-nl-2.3.1.4-3mdk
Installing locales-fr or changing the locales settings with
localedrake should fix the problem :).
--
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] Problem network install using network.img
On Thu, Feb 13, 2003 at 12:00:42PM +0100, Pixel wrote:
> Frederik Himpe <[EMAIL PROTECTED]> writes:
>
> > When the module 8139too for the network card is loaded, a message
> > appears in the kernel log tot it "is an enhanced 8139+ chip. Use the
> > "8139cp" driver for improved performance and stability".
> >
> > Is there some way to use this driver instead of the 8139too driver?
> > Maybe the network.img can be changed to try first the 8139cp driver, and
> > if it does not work, use the 8139too driver?
>
> to test: boot with "expert", and choose 8139cp.
>
> if it works: give me the output of "lspcidrake -v" so that we change
> the default from 8139too to 8139cp
I've tried it with 8139cp, and it works flawlessly!
Here's the requested output:
$ lspcidrake -v
unknown : unknown (1002/cab2//) [BRIDGE_HOST]
unknown : unknown (1002/7010//) [BRIDGE_PCI]
trident : Acer Laboratories Inc. [ALi]|M5451 PCI South Bridge
Audio [MULTIMEDIA_AUDIO] (vendor:10b9 device:5451 subv:0e11 subd:0056)
unknown : Acer Laboratories Inc. [ALi]|M1533 PCI to ISA Bridge
[Aladdin IV] [BRIDGE_ISA] (vendor:10b9 device:1533)
yenta_socket: Texas Instruments|PCI4410 PC card Cardbus Controller
[BRIDGE_CARDBUS] (vendor:104c device:ac41 subv:8c00 subd:)
ohci1394: Texas Instruments|PCI4410 OHCI-Lynx IEEE 1394
Controller [SERIAL_FIREWIRE] (vendor:104c device:8017 subv:0e11
subd:0056)
8139too : Realtek|RTL-8139 [NETWORK_ETHERNET] (vendor:10ec
device:8139 subv:0e11 subd:0056)
Hsf:www.linmodems.org: Conexant|HSF 56k HSFi Modem [COMMUNICATION_OTHER]
(vendor:14f1 device:2f00 subv:0e11 subd:8d89)
unknown : Acer Laboratories Inc. [ALi]|M5229 IDE [STORAGE_IDE]
(vendor:10b9 device:5229)
unknown : Acer Laboratories Inc. [ALi]|M7101 PMU [BRIDGE_OTHER]
(vendor:10b9 device:7101)
usb-ohci: NEC|USB [SERIAL_USB] (vendor:1033 device:0035
subv:0e11 subd:0056)
usb-ohci: NEC|USB [SERIAL_USB] (vendor:1033 device:0035
subv:0e11 subd:0056)
ehci-hcd: NEC Corporation|PCI to USB Enhanced Host Controller
[SERIAL_USB] (vendor:1033 device:00e0 subv:0e11 subd:0056)
unknown : unknown (1002/4337/0e11/0056) [DISPLAY_VGA]
unknown : Linux 2.4.21pre4-6mdk ehci-hcd|NEC Corporation USB 2.0
[Hub|Root Hub] (vendor: device:)
unknown : Unknown|USB OHCI Root Hub [Hub|Root Hub] (vendor:
device:)
unknown : Unknown|USB OHCI Root Hub [Hub|Root Hub] (vendor:
device:)
unknown : B16_b_02|USB-PS/2 Optical Mouse [Human Interface
Devices|Boot Interface Subclass|Mouse] (vendor:046d device:c025)
Install went very well for a beta. I like the new theme very much,
it looks fantastic. Only issues I encountered are the fact that I could
not resize the NTFS partition to less than 16 GB, although there's only
about 2 or 3 GB in use and I have defragmented it before the Mandrake
install. Hmm, while I'm writing this, I notice that trying to view the
contents of the NTFFS partition (with ls) does not work, ls just
hangs...
Othere strange things I noticed:
- I used a static IP to do the install. After installation, I noticed
that it had enabled dhcp. If I checked the network settings in mcc, I
saw that the correct static IP was saved, but the dhcp-checkbox was
checked.
- The hostname is set to localhost.
- There seems to be wrong with the locale settings, every time I start
one of the Mandrake tools, I got this output from perl:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_GB:en",
LC_ALL = (unset),
LC_PAPER = "fr_BE",
LC_ADDRESS = "fr_BE",
LC_MONETARY = "fr_BE",
LC_NUMERIC = "fr_BE",
LC_TELEPHONE = "fr_BE",
LC_MESSAGES = "en_GB",
LC_COLLATE = "en_GB",
LC_IDENTIFICATION = "fr_BE",
LC_MEASUREMENT = "fr_BE",
LC_CTYPE = "en_GB",
LC_TIME = "en_GB",
LC_NAME = "fr_BE",
LANG = "en_GB"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Strange, because I cannot remember having chosen French somewhere (I did
choose Belgium as country however). So I have no French locales installed:
# rpm -qa *locales*
locales-en-2.3.1.4-3mdk
locales-nl-2.3.1.4-3mdk
I think these are all the problems I encountered. Nice work!
Frederik Himpe
Re: [Cooker] Problem network install using network.img
On Thu, Feb 13, 2003 at 02:22:31PM +0100, Frederik Himpe wrote: > On do, 2003-02-13 at 13:08, Pixel wrote: > > Frederik Himpe <[EMAIL PROTECTED]> writes: > > > > > On do, 2003-02-13 at 12:00, Pixel wrote: > [...] > > > > to test: boot with "expert", and choose 8139cp. > > > > > > It seems this driver is not included on network.img (feb 12 2003 > > > 01:34:06)... > > > > oops, adding it. > > That's great, thank you! I will test it and let you know the results as > soon as it hits the mirrors. Aarghh! I just reinstalled the windows that came with this laptop, and it has also a slow download (upload is fast though). So it seems it has nothing to do with the driver :-( My apologies, I should have tried this first... Frederik Himpe
Re: [Cooker] Problem network install using network.img
On do, 2003-02-13 at 13:08, Pixel wrote: > Frederik Himpe <[EMAIL PROTECTED]> writes: > > > On do, 2003-02-13 at 12:00, Pixel wrote: [...] > > > to test: boot with "expert", and choose 8139cp. > > > > It seems this driver is not included on network.img (feb 12 2003 > > 01:34:06)... > > oops, adding it. That's great, thank you! I will test it and let you know the results as soon as it hits the mirrors. Frederik
Re: [Cooker] Problem network install using network.img
Frederik Himpe <[EMAIL PROTECTED]> writes: > On do, 2003-02-13 at 12:00, Pixel wrote: > > Frederik Himpe <[EMAIL PROTECTED]> writes: > > > > > When the module 8139too for the network card is loaded, a message > > > appears in the kernel log tot it "is an enhanced 8139+ chip. Use the > > > "8139cp" driver for improved performance and stability". > > > > > > Is there some way to use this driver instead of the 8139too driver? > > > Maybe the network.img can be changed to try first the 8139cp driver, and > > > if it does not work, use the 8139too driver? > > > > to test: boot with "expert", and choose 8139cp. > > It seems this driver is not included on network.img (feb 12 2003 > 01:34:06)... oops, adding it.
Re: [Cooker] Problem network install using network.img
On do, 2003-02-13 at 12:00, Pixel wrote: > Frederik Himpe <[EMAIL PROTECTED]> writes: > > > When the module 8139too for the network card is loaded, a message > > appears in the kernel log tot it "is an enhanced 8139+ chip. Use the > > "8139cp" driver for improved performance and stability". > > > > Is there some way to use this driver instead of the 8139too driver? > > Maybe the network.img can be changed to try first the 8139cp driver, and > > if it does not work, use the 8139too driver? > > to test: boot with "expert", and choose 8139cp. It seems this driver is not included on network.img (feb 12 2003 01:34:06)... Frederik Himpe
Re: [Cooker] Problem network install using network.img
On do, 2003-02-13 at 11:41, rcc wrote: > On 13 Feb 2003 11:24:56 +0100 > Frederik Himpe <[EMAIL PROTECTED]> wrote: > > > I'm trying to install Cooker on a Compaq EVO n1020v laptop using > > network.img. The network card is recognised, but it works awfully slow > > (it lasts more than half an hour to download the 13 MB > > mdkinst_stage2.bz2, while it should achieve around 400 KB/s). > > This may be unrelated but on my laptop (not a Compaq) download of > stage2 with network install is terribly slow when the Auto-Doze feature > is enabled in bios (CPU/16, timeout 8 sec). I only found it because I > pushed a key on the keyboard which made the progress bar jump. Turning > Doze off for install and it works pretty neat. Seems a good idea, but I have no such an option in the Bios. Pressing all those special keys on the keyboard does not make a difference either. Frederik Himpe
Re: [Cooker] Problem network install using network.img
Frederik Himpe <[EMAIL PROTECTED]> writes: > When the module 8139too for the network card is loaded, a message > appears in the kernel log tot it "is an enhanced 8139+ chip. Use the > "8139cp" driver for improved performance and stability". > > Is there some way to use this driver instead of the 8139too driver? > Maybe the network.img can be changed to try first the 8139cp driver, and > if it does not work, use the 8139too driver? to test: boot with "expert", and choose 8139cp. if it works: give me the output of "lspcidrake -v" so that we change the default from 8139too to 8139cp
Re: [Cooker] Problem network install using network.img
On 13 Feb 2003 11:24:56 +0100 Frederik Himpe <[EMAIL PROTECTED]> wrote: > I'm trying to install Cooker on a Compaq EVO n1020v laptop using > network.img. The network card is recognised, but it works awfully slow > (it lasts more than half an hour to download the 13 MB > mdkinst_stage2.bz2, while it should achieve around 400 KB/s). This may be unrelated but on my laptop (not a Compaq) download of stage2 with network install is terribly slow when the Auto-Doze feature is enabled in bios (CPU/16, timeout 8 sec). I only found it because I pushed a key on the keyboard which made the progress bar jump. Turning Doze off for install and it works pretty neat. - Mark
