Debian Install

[rolanaj]

Bruno what I did was

[root@localhost rolana]# mount /dev/hda8 /mnt/debian

[Bruno]

Bruno what I did was

<{POST_SNAPBACK}>

LOL . . . yep I did not know you named it "/mnt/debian" ( is okay though ) . . . . . . anyway, my answer crossed your post so is above your last one :PB) BrunoPS: If after you have a GUI you want to increase your screen-resolution . . . add the one you want here:

        SubSection "Display"                Depth          24                Modes        "HERE" "800x600" "640x480"        EndSubSectionEndSection

[rolanaj]

Ok I made the change, time to go check the results be right back

[Bruno]

Crossing fingers and knees . . . . Bruno

[rolanaj]

Still no luck, but it said that it was log /var/log/XFree86.0.log so I thought looking at the log would help so here it is

    NumberOfPlanes: 1        BitsPerPixel: 4        NumberOfBanks: 1        MemoryModel: 0        BankSize: 0        NumberOfImages: 0        RedMaskSize: 0        RedFieldPosition: 0        GreenMaskSize: 0        GreenFieldPosition: 0        BlueMaskSize: 0        BlueFieldPosition: 0        RsvdMaskSize: 0        RsvdFieldPosition: 0        DirectColorModeInfo: 0        PhysBasePtr: 0xd8000000        LinBytesPerScanLine: 264        BnkNumberOfImagePages: 0        LinNumberOfImagePages: 0        LinRedMaskSize: 0        LinRedFieldPosition: 0        LinGreenMaskSize: 0        LinGreenFieldPosition: 0        LinBlueMaskSize: 0        LinBlueFieldPosition: 0        LinRsvdMaskSize: 0        LinRsvdFieldPosition: 0        MaxPixelClock: 108500000>> made shorter by Bruno <<<<<<<        LinGreenMaskSize: 6        LinGreenFieldPosition: 5        LinBlueMaskSize: 5        LinBlueFieldPosition: 0        LinRsvdMaskSize: 0        LinRsvdFieldPosition: 0        MaxPixelClock: 229500000(II) VESA(0): Total Memory: 512 64KB banks (32768kB)(WW) VESA(0): config file hsync range 28-50kHz not within DDC hsync range 30-70kHz(WW) VESA(0): config file vrefresh range 43-75Hz not within DDC vrefresh range 50-160Hz(II) VESA(0): Generic Monitor: Using hsync range of 28.00-50.00 kHz(II) VESA(0): Generic Monitor: Using vrefresh range of 43.00-75.00 Hz(II) VESA(0): Not using built-in mode "1024x768" (width too large for virtual size)(--) VESA(0): Virtual size is 800x600 (pitch 800)(**) VESA(0): *Built-in mode "800x600"(**) VESA(0): *Built-in mode "640x480"(++) VESA(0): DPI set to (100, 100)(II) VESA(0): Attempting to use 72Hz refresh for mode "800x600" (115)(II) VESA(0): Attempting to use 73Hz refresh for mode "640x480" (112)(**) VESA(0): Using "Shadow Framebuffer"(II) Loading sub module "shadow"(II) LoadModule: "shadow"(II) Loading /usr/X11R6/lib/modules/libshadow.a(II) Module shadow: vendor="The XFree86 Project"        compiled for 4.3.0.1, module version = 1.0.0        ABI class: XFree86 ANSI C Emulation, version 0.2(II) Loading sub module "fb"(II) LoadModule: "fb"(II) Loading /usr/X11R6/lib/modules/libfb.a(II) Module fb: vendor="The XFree86 Project"        compiled for 4.3.0.1, module version = 1.0.0        ABI class: XFree86 ANSI C Emulation, version 0.2(--) Depth 24 pixmap format is 32 bpp(II) do I need RAC?  No, I don't.(II) resource ranges after preInit:        [0] -1  0       0xffe00000 - 0xffffffff (0x200000) MX[B](B)        [1] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)        [2] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]        [3] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]        [4] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]        [5] -1  0       0xe2011000 - 0xe20110ff (0x100) MX[B]        [6] -1  0       0xe2010000 - 0xe20100ff (0x100) MX[B]        [7] -1  0       0xe2000000 - 0xe200ffff (0x10000) MX[B]        [8] -1  0       0xd0000000 - 0xcfffffff (0x0) MX[B]O        [9] -1  0       0xd8000000 - 0xdfffffff (0x8000000) MX[B](B)        [10] -1 0       0xe0000000 - 0xe0ffffff (0x1000000) MX[B](B)        [11] 0  0       0x000a0000 - 0x000affff (0x10000) MS[B]        [12] 0  0       0x000b0000 - 0x000b7fff (0x8000) MS[B]        [13] 0  0       0x000b8000 - 0x000bffff (0x8000) MS[B]        [14] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[B]        [15] -1 0       0x00000000 - 0x000000ff (0x100) IX[B]        [16] -1 0       0x0000e800 - 0x0000e8ff (0x100) IX[B]        [17] -1 0       0x0000e400 - 0x0000e4ff (0x100) IX[B]        [18] -1 0       0x0000e000 - 0x0000e00f (0x10) IX[B]        [19] -1 0       0x0000dc00 - 0x0000dc1f (0x20) IX[B]        [20] -1 0       0x0000d800 - 0x0000d81f (0x20) IX[B]        [21] -1 0       0x0000d400 - 0x0000d41f (0x20) IX[B]        [22] -1 0       0x0000d000 - 0x0000d007 (0x8) IX[B]        [23] 0  0       0x000003b0 - 0x000003bb (0xc) IS[B]        [24] 0  0       0x000003c0 - 0x000003df (0x20) IS[B](II) Loading sub module "int10"(II) LoadModule: "int10"(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a(II) VESA(0): initializing int10(II) VESA(0): Primary V_BIOS segment is: 0xc000(II) VESA(0): VESA BIOS detected(II) VESA(0): VESA VBE Version 3.0(II) VESA(0): VESA VBE Total Mem: 32768 kB(II) VESA(0): VESA VBE OEM: NVidia(II) VESA(0): VESA VBE OEM Software Rev: 3.17(II) VESA(0): VESA VBE OEM Vendor: NVidia Corporation(II) VESA(0): VESA VBE OEM Product: NV10 Reference Board(II) VESA(0): VESA VBE OEM Product Rev: Chip Rev A1(II) VESA(0): virtual address = 0x4028a000,        physical address = 0xd8000000, size = 33554432(==) VESA(0): Default visual is TrueColor(==) VESA(0): Backing store disabled(**) Option "dpms"(**) VESA(0): DPMS enabled(==) RandR enabled(II) Setting vga for screen 0.(II) Initializing built-in extension MIT-SHM(II) Initializing built-in extension XInputExtension(II) Initializing built-in extension XTEST(II) Initializing built-in extension XKEYBOARD(II) Initializing built-in extension LBX(II) Initializing built-in extension XC-APPGROUP(II) Initializing built-in extension SECURITY(II) Initializing built-in extension XINERAMA(II) Initializing built-in extension XFree86-Bigfont(II) Initializing built-in extension RENDER(II) Initializing built-in extension RANDR(II) Keyboard "Generic Keyboard" handled by legacy driver(**) Option "Protocol" "ImPS/2"(**) Configured Mouse: Protocol: "ImPS/2"

(**) Option "CorePointer"(**) Configured Mouse: Core Pointer(**) Option "Device" "dev/psaux"(EE) xf86OpenSerial: Cannot open device dev/psaux No such file or directory.(EE) Configured Mouse: cannot open input device(EE) PreInit failed for input device "Configured Mouse"(II) UnloadModule: "mouse"(WW) No core pointer registeredNo core pointerFatal server error:failed to initialize core devicesWhen reporting a problem related to a server crash, please sendthe full server output, not just the last messages.This can be found in the log file "/var/log/XFree86.0.log".Please report problems to submit@bugs.debian.org.[root@localhost log]#

[rolanaj]

Wow sorry hadn't realized how big that was, don't know if it will be helpful or not either

[Bruno]

RolanaCan you check again . . . I think you forgot a slash at "/dev/psaux" . . . see your output:

(**) Configured Mouse: Core Pointer(**) Option "Device" "dev/psaux"(EE) xf86OpenSerial: Cannot open device dev/psaux No such file or directory.

So

# cat /mnt/debian/etc/X11/XF86Config-4

and please check . . Bruno

[rolanaj]

That would be it ok I will try again

[rolanaj]

Section "InputDevice"        Identifier      "Configured Mouse"        Driver          "mouse"        Option          "CorePointer"        Option          "Device"                "/dev/psaux"        Option          "Protocol"              "ImPS/2"        Option          "Emulate3Buttons"       "true"        Option          "ZAxisMapping"          "4 5"EndSection

This looks better ok I will try again

[Bruno]

Looks like the rest of the log was okay . . . so I bet it will work okay now Bruno

[Bruno]

Rolana .. I have to close down for the night . . . . now imagine you still do not get a GUI . . try this:First back up that file

# cp  /mnt/debian/etc/X11/XF86Config-4  /mnt/debian/etc/X11/XF86Config-4-Backup

Then have a look in the Mandriva /etc/X11/xorg.conf file and compare the "Monitor" section to the Debian XF86Config file . . the stuff to concentrate on are the parts in REDThis is from your Debian XF86Config-4 file:

Section "Monitor" <<== do not touch !!        Identifier      "Generic Monitor" <<== do not touch !!      HorizSync      28-50        VertRefresh    43-75        Option          "DPMS"EndSection

Bruno

[rolanaj]

Well I actually got the Gui and managed to switch it to Kde with the tips finotti had posted. So far so good. I can not get kppp to open though

[rolanaj]

I checked out of curiousity to see what was in my Mandrake XF86Config-4 file and it had HorizSync 30-70 and VertRefresh 50-160 so should I change that in debian or leave well enough alone?

[Bruno]

Hi RolanaIs that a version of Mandrake that still uses the XF86Config-4 and not yet the xorg.conf ? If so you can rely on those HorizSync 30-70 and VertRefresh 50-160 and adapt the Debian one ( but make a backup of the old file first just to be on the safe side ) Bruno

[rolanaj]

Bruno i is Mandrake 10.1 and it has xorg.conf so I will leave Debian alone. Thank you and everyone else for all your help. Another question, when I select kppp from the menu it just doesn't open and when I type it in a command centre I get an error

Xlib: connection to ":0.0" refused by serverXlib: No protocol specifiedkppp: cannot connect to X server :0.0debian:/home/rolana#

any ideas anyone

[BarryB]

Try (in terminal) kdesu Kppp

[rolanaj]

Thanks BarryB that got me a little farther it opened kppp with an error

 /etc/resolv.conf is missing or can't be read ask your system administrator to create this file (can be empty) with appropriate read and write permissions

What would be appropriate read and write permissions?

[BarryB]

you should be able to create it in root(su)as in " mkdir /etc/resolv.conf " in a terminal minus the " "

[finotti]

you should be able to create it in root(su)as in " mkdir /etc/resolv.conf " in a terminal  minus the " "

<{POST_SNAPBACK}>

Hmm... Isn't resolv.conf a *file*? If you use mkdir it will create a directory... On the other hand,

touch /etc/resolv.conf

creates an empty file. (I don't know if it will solve the problem. This file usually contains DNS info, right?)Best,LuisEDIT: I think that the proper permissions are given with

chmod 644 /etc/resolv.conf

Edited June 30, 2005 by finotti

[BarryB]

Ahhh....good point Luis...thanks for jumping in.... ..but shouldn't the dns info be popluated when she connects?

[finotti]

Ahhh....good point Luis...thanks for jumping in.... ..but shouldn't the dns info be popluated when she connects?

<{POST_SNAPBACK}>

You're right! I remember creating one once, but it was for a static IP... Luis

[Bruno]

Indeed the /etc/resolv.conf is a file that holds the name of your ISP and the primary and secondary DNS number of your ISP . . . . Basically it are just 3 lines, example:

    search nameisp.com    nameserver 208.14.152.1    nameserver 208.14.152.2

( first line can be "domain nameisp.com" too . . . so long ago I had dial-up )But I think it is easier ( and has more chance to be accurate ) if you just copy it over from one of your other distros . . . because every other distro you have and that is already configured to dial in to the net will have that file and you can use it one on one in Debian. Bruno

[rolanaj]

Well I guess I should have read all these replies first, I did as BarryB said and indeed got a directory and needed a file, couldn't remember how to create an empty file as root so created one as user changed permissions, changed owner and changed group moved it to /etc as root - as user has no permission to write to /etc. When that still didnt work because ppp couldn't find the passwords I thought maybe I should check with someone if I should maybe just copy the file from Mandrake to Debian and I guess that answers that. Thanks for all the help sooner or later some of this has got to sink in and I will remember it. I did copy my tips for linux explorers over to debian so I have some help there

[rolanaj]

so does this look like it might work?

[rolana:~]$ suPassword:[root@localhost rolana]# cp /etc/resolv.conf /mnt/debian/etc/resolv.confcp: overwrite `/mnt/debian/etc/resolv.conf'? y

[Bruno]

Yep that should do the trick . . . . . . still curious what it looks like though Bruno

[rolanaj]

[root@localhost rolana]# cat /mnt/debian/etc/resolv.confdomain nb.sympatico.ca          #kppp temp entrynameserver 198.164.30.2 # ppp temp entrynameserver 198.164.4.2 # ppp temp entrynameserver 198.164.30.2 #kppp temp entrynameserver 198.164.4.2  #kppp temp entry[root@localhost rolana]#

[Bruno]

WOOOW !! . . . . . 4 DNS numbers . . . that must be a rich IISP . . LOLThanks Bruno

[rolanaj]

Well I am posting from Debian After I copied the /etc/resolv.conf file over it still wouldn't connect so I went to the doc files because I always seem to need something there to setup kppp. I went to /usr/share/doc/kppp/readme.debian and this is what it said

In order to actually use kppp you must first be a part of the "dip" group.This is the standard for using ppp in general with Debian.  If you are not amember of this group, you will not be able to run pppd or setup connections.Furthermore, kppp requires that the ppp daemon be run with the "noauth"option.  However, pppd's default setting, in /etc/ppp/options, is "auth",and for security reasons it should remain so.  To work around this problem,uncomment "noauth" in /etc/ppp/peers/kppp-options.  You should then be ableto connect.Note that if "noauth" is uncommented, a setting of "noauth" in/etc/ppp/options will conflict with kppp. Note also that uncommenting"noauth" opens the possibility that other malicious members of the "dip"group could now potentially abuse the ppp daemon with the "noauth" option.

So I went to /etc/ppp/peers/kppp-options and removed the # in front of noauth and here I am. I had to use kdesu kppp to open up kppp because I have no idea how to add myself to a group called dip (i never imaged I would want to belong to a group called dip ever) Edited June 30, 2005 by rolanaj

[rolanaj]

Just a couple more things Debian does not see the windows partition or any other. During install not only are you able to force Debian to use lilo you can tell it to continue without a bootloader which I did. Could this explain why it doesn't see windows?

[Bruno]

That is great Rolana !! . . . Good work !! . . . Now the DIP group . . . . . . . . please show me

# cat /etc/group

And we will fix that first . . . . . . and after we can fix the need to use kdesu too BrunoPS:Your second question, instead of the /mnt directory, Debian uses /media . . . . maybe there is /media/win_c ??