Menu
▾
▴
linux-apus-user
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(177) |
Jun
(100) |
Jul
(56) |
Aug
(143) |
Sep
(366) |
Oct
(142) |
Nov
(221) |
Dec
(56) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(364) |
Feb
(705) |
Mar
(185) |
Apr
(267) |
May
(238) |
Jun
(59) |
Jul
(22) |
Aug
(47) |
Sep
(42) |
Oct
(54) |
Nov
(72) |
Dec
(42) |
| 2002 |
Jan
(32) |
Feb
(130) |
Mar
(77) |
Apr
(23) |
May
(15) |
Jun
(17) |
Jul
(31) |
Aug
(38) |
Sep
(61) |
Oct
(35) |
Nov
(36) |
Dec
(42) |
| 2003 |
Jan
(57) |
Feb
(13) |
Mar
(31) |
Apr
(28) |
May
(4) |
Jun
(22) |
Jul
(22) |
Aug
(5) |
Sep
|
Oct
(5) |
Nov
(9) |
Dec
(37) |
| 2004 |
Jan
(7) |
Feb
(11) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
(3) |
Oct
(3) |
Nov
(1) |
Dec
(6) |
| 2006 |
Jan
(18) |
Feb
(8) |
Mar
|
Apr
|
May
(14) |
Jun
(1) |
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andreas <an...@po...> - 2003-01-05 22:06:53
|
Hello Lio Am 05-Jan-03 schrieb Lio: > Hi All, > I use gdm as default login screen but I can not log in as root from this > screen IIRC this is how it should be. You should never login as root!! > but I do not know how to switch to console mode. What are the keys ? ctrl+alt+F1 or whatever Fx you like to switch from X to a console. alt+F7 or F6 to switch back to X. > I use kernel 2.4.13 and installed its modules 2.4.13-20011030, and rename > the folder from 2.4.13-20011030 to 2.4.13. Now at boot screen, I get after > calculating modules depencies messages telling me "dep.mod... is not owned > by root" Do you have to care about this ? No idea, but I guess you copied them from an affs partition as a normal user? So chown them to root. > I would like to know which gfx driver should I take for a pixel64 gfx card > (cirrus logic GD5429) ? > Regards > Lio -- Best wishes, Andi |
|
From: Lio <ls...@ma...> - 2003-01-05 21:11:05
|
Hi All, I use gdm as default login screen but I can not log in as root from this screen but I do not know how to switch to console mode. What are the keys ? I use kernel 2.4.13 and installed its modules 2.4.13-20011030, and rename the folder from 2.4.13-20011030 to 2.4.13. Now at boot screen, I get after calculating modules depencies messages telling me "dep.mod... is not owned by root" Do you have to care about this ? I would like to know which gfx driver should I take for a pixel64 gfx card (cirrus logic GD5429) ? Regards Lio -- Amiga, THE computer they could not kill... Message generated on A1200T+BPPC+BVPPC |
|
From: David J. <jo...@co...> - 2003-01-05 18:05:03
|
Hi, I have been unable to get sound working correctly on my woody system. I am running KDE2, but get an error message on booting. The message says, " error while initialising the sound driver, device /dev/dsp can't be opened, no such device" I have been informed that I need to "modprobe dmasound_paula", without much extra explanation. I've typed this into bash but sound still isn't working on my system. If anyone can help, I need some comprehensive instuctions on what I need to do. My woody system works ok and I have managed to set up X and a working apache webserver with php and mysql support, but am unable to suss out this sound problem. With a bit more info I know I can sort this out. Any help is appreciated. Regards Dave |
|
From: David J. <jo...@co...> - 2003-01-05 18:05:00
|
Hi, I recently found my amiga ffs which is linked to /mnt/amiga had become corrupted. I reformated the partition on the miggy side only to find Woody still sees all the files that where present before the reformat. I can view the files, see the pics even though on the miigy side the partion is blank. Also new files i add on the miggy side are now not visible. This problem seems to be totally impossible, but true. How can I unmount /mnt/amiga and start a fresh with a blank partition. Any help would be great. Regards Dave |
|
From: Geert U. <ge...@li...> - 2003-01-05 09:10:16
|
On 5 Jan 2003, Kulwant Bhogal wrote:
> I think these funny format disks of mine are the reason for the non
> detection. I suddenly discovered that there are many more menu selections in
> the Linux Installer and discovered a menu item called "List Partitions" (or
> something like that) and this is what it returned:
So now you saw the `Launch shell' entry as well? :-)
> Partitions list
>
> The following partitions have been detected:
>
> Device Mounted On Type
> /dev/sda1 --Not mounted-- FFS
> /dev/sda2 --Not mounted-- FFS
> /dev/sda3 --Not mounted-- FFS
> /dev/sda4 --Not mounted-- FFS
> /dev/sda5 --Not mounted-- FFS
> /dev/sda6 --Not mounted-- FFS
> /dev/sda7 --Not mounted-- FFS
>
> Disk /dev/sdb has no partitons defined
> Disk /dev/sdc has no partitions defined
Aha, so it could be a problem with the partitioning support. Were these disks
partitioned under AmigaOS using HDToolBox? If yes, chances are high that the
Amiga RDB (Rigid Disk Block) support doesn't handle 4096-byte blocks yet.
> /dev/sdd1 --Not mounted-- FFS
> /dev/sdd2 --Not mounted-- FFS
> /dev/sdd3 --Not mounted-- FFS
> /dev/sdd4 --Not mounted-- FFS
> /dev/sdd5 --Not mounted-- FFS
>
> /dev/hda1 --Not mounted-- FFS
> /dev/hda2 --Not mounted-- FFS
> /dev/hda3 --Not mounted-- FFS
>
> where:
>
> sda is a Compaq 18Gb with a 512 blocksize
> sdb is a Seagate Baracudda 4.8Gb with a 4096 blocksize
> sdc is a Seagate Baracudda 4.8Gb with a 4096 blocksize
> sdd is a Compaq 9Gb with a 512blocksize and
> hda is a Connor 420Mb with a 512 blocksize
>
> And all of the disks have a number of partitions each.
>
> sdc is the drive I have set up the Linux partitions on.
>
> All the SCSI drives are second hand and the Seagates came with the 4096
> blocksize and no Amiga program has been able to low level format them with a
> 512 blocksize. Only a Seagate tool (which runs on PC only) is available for
> this job apparently.
Just thinking of somethings:
1. Is there a jumper on the drive to choose the blocksize?
2. Does Linux recognize the blocksize during disk probing? E.g. for my disks
it says
| SCSI device sda: 8910423 512-byte hdwr sectors (4562 MB)
| SCSI device sdb: 6281856 512-byte hdwr sectors (3216 MB)
during startup.
> Given that the only spare space I have is on the 18Gb Compaq drive, is it
> safe to set up the Linux partitions on this drive? I don't want to risk
> anything because I remember that Shapeshifter (Macintosh Emulator) destoyed
> some partitions trying to initialise a Mac partition on a >4Gb disk of mine
> once.
Should be safe. I never managed to corrupt my AmigaOS partitions from within
Linux. I know others did, but that was due to bugs in the linux AFFS support,
which were solved a long time ago.
> I am running OS3.9 but suspect that the patches to handle >4Gb disks are not
> active once Linux is booted?
Linux has its own support for disks, which handles the >4 GB case just fine.
Don't know about the Amiga partitioning support, though.
BTW, since your Compaq is much larger than 4 GB, what does
`cat /proc/partitions' say?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Kulwant B. <kul...@bt...> - 2003-01-05 00:49:52
|
Hello, I think these funny format disks of mine are the reason for the non detection. I suddenly discovered that there are many more menu selections in the Linux Installer and discovered a menu item called "List Partitions" (or something like that) and this is what it returned: Partitions list The following partitions have been detected: Device Mounted On Type /dev/sda1 --Not mounted-- FFS /dev/sda2 --Not mounted-- FFS /dev/sda3 --Not mounted-- FFS /dev/sda4 --Not mounted-- FFS /dev/sda5 --Not mounted-- FFS /dev/sda6 --Not mounted-- FFS /dev/sda7 --Not mounted-- FFS Disk /dev/sdb has no partitons defined Disk /dev/sdc has no partitions defined /dev/sdd1 --Not mounted-- FFS /dev/sdd2 --Not mounted-- FFS /dev/sdd3 --Not mounted-- FFS /dev/sdd4 --Not mounted-- FFS /dev/sdd5 --Not mounted-- FFS /dev/hda1 --Not mounted-- FFS /dev/hda2 --Not mounted-- FFS /dev/hda3 --Not mounted-- FFS where: sda is a Compaq 18Gb with a 512 blocksize sdb is a Seagate Baracudda 4.8Gb with a 4096 blocksize sdc is a Seagate Baracudda 4.8Gb with a 4096 blocksize sdd is a Compaq 9Gb with a 512blocksize and hda is a Connor 420Mb with a 512 blocksize And all of the disks have a number of partitions each. sdc is the drive I have set up the Linux partitions on. All the SCSI drives are second hand and the Seagates came with the 4096 blocksize and no Amiga program has been able to low level format them with a 512 blocksize. Only a Seagate tool (which runs on PC only) is available for this job apparently. Given that the only spare space I have is on the 18Gb Compaq drive, is it safe to set up the Linux partitions on this drive? I don't want to risk anything because I remember that Shapeshifter (Macintosh Emulator) destoyed some partitions trying to initialise a Mac partition on a >4Gb disk of mine once. I am running OS3.9 but suspect that the patches to handle >4Gb disks are not active once Linux is booted? Kind regards, Kulwant |
|
From: Andreas <an...@po...> - 2003-01-04 17:41:46
|
Hello Bj=F6rn Am 04-Jan-03 schrieb Bj=F6rn Johansson: > I need a dvd device ( /dev/dvd ). > I assume I need to use mknod. > How do I do this? There's an ongoing discussion on debian-powerpc starting with this http:/= /lists.debian.org/debian-powerpc/2003/debian-powerpc-200301/msg00023.html post. --=20 Best wishes, Andi |
|
From: Robert J. <rob...@st...> - 2003-01-04 17:14:03
|
On Sat, 4 Jan 2003, [UNKNOWN] Bj=F6rn Johansson wrote:
> I need a dvd device ( /dev/dvd ).
> I assume I need to use mknod.
I think "ln -s /dev/hdX /dev/dvd" is enough, where hdX is your DVD-ROM
player. Lycka till! :-)
Robert Johansson * gu...@ha... * +46 (0)7 39 8000 39
In pursuit of a M.Sc. in Computer Science
|
|
From: Björn J. <kh...@te...> - 2003-01-03 23:31:54
|
Hi! I need a dvd device ( /dev/dvd ). I assume I need to use mknod. How do I do this? -- Bj=F6rn Johansson "Debian rocks!!" |
|
From: Kulwant B. <kul...@bt...> - 2003-01-03 18:55:22
|
Hello Geert, >> Can you try opening a shell (it's in the installer menu), and manually >> format and mount the partition(s) under /target? After that you can >> close the shell and skip the initialisation and mounting steps in the >> installer. That worked for me. I could not find shell in the installer menu.... I would also still need the syntax of the format command too... Regards, Kulwant |
|
From: Kulwant B. <kul...@bt...> - 2003-01-03 14:16:29
|
Hello Geert/All, > I actually saw similar things with the Debian installer on mipsel. The > installer never saw any formatted partitions. > Can you try opening a shell (it's in the installer menu), and manually > format and mount the partition(s) under /target? After that you can close > the shell and skip the initialisation and mounting steps in the > installer. That worked for me. Ok, I can try this, what is the syntax of the command to use and where can I find more information on shell commands (e.g. a manual)? I tried a web search but found only info on the most common ones and even the more comprehensive ones (like http://www.ss64.com/bash/) don't include any info on format! >> Does LINUX only support HDs with 512 bytes per sector and if so does >> anyone know of an Amiga low level format program that actually works >> (i.e. can reformat a HD with 4096 bytes per sector to 512 bytes per >> sector?). If LINUX can initialize a 4096 bytes per sector HD/partition >> then what am I doing wrong? What do I need to do to get the installation >> program to detect the partitions? > Sorry, I don't know. I once got a Mac SCSI hard disk with 488 (??) bytes > per sector, and that didn't work. Ho hum. This may be my stumbling block - although I can see a screenshot of a Mandrake installation which shows a partition with a 4096 blocksize (at ). This however may be what LINUX can do to a partition with a 512 block size and not what it can do with a 4096 block size. The Amiga has this problem - it can create partitions of any block size from 512 to 16384 (in steps of powers of two) but it can only do this if the original block size is 512. If the drive has a native block size of 4096, then this becomes the smallest block size for all partitions on the drive under AmigaOS. Where can I find more information on what the LINUX requirements are with regard to hard disk block size? Are are there any LINUX commands for low level formatting hard drives with new block sizes? Regards, Kulwant |
|
From: Geert U. <ge...@li...> - 2003-01-03 09:23:25
|
On 3 Jan 2003, Kulwant Bhogal wrote:
> Many thanks for your pointer. I got the Debian installer system to run using the
> following bootstrap command (after setting up my partitions using the Amiga
> OS3.9 HDToolbox program):
>
> bootstrap --apus -k /apus/linux.bin -r /apus/root.bin root=/dev/ram nobats
> 60nsram video =pm2fb:mode:1024x768-60
>
> (if you see italics where the "/" forwardslashes should be in the above line then you need to
> turn off text styles in your email program).
>
> However, after successfully decompressing the image file and starting the
> installation program where I can successfully select the language and keyboard, I cannot
> specify the swap partition or initialise any partitions because the LINUX installer
> program says there is a problem:
>
> No ext2 partitions that had not already been mounted were detected
> <continue>
>
> I suspect that this is due to my earlier mentioned question about a hard
> disk with a 4096 byte sector size instead of the more usual 512 byte sector
> size.
I actually saw similar things with the Debian installer on mipsel. The
installer never saw any formatted partitions.
Can you try opening a shell (it's in the installer menu), and manually format
and mount the partition(s) under /target? After that you can close the shell
and skip the initialisation and mounting steps in the installer. That worked
for me.
> Does LINUX only support HDs with 512 bytes per sector and if so does anyone
> know of an Amiga low level format program that actually works (i.e. can
> reformat a HD with 4096 bytes per sector to 512 bytes per sector?). If LINUX
> can initialize a 4096 bytes per sector HD/partition then what am I doing
> wrong? What do I need to do to get the installation program to detect the
> partitions?
Sorry, I don't know. I once got a Mac SCSI hard disk with 488 (??) bytes per
sector, and that didn't work.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Kulwant B. <kul...@bt...> - 2003-01-03 02:50:27
|
Hello Geert, Many thanks for your pointer. I got the Debian installer system to run using the following bootstrap command (after setting up my partitions using the Amiga OS3.9 HDToolbox program): bootstrap --apus -k /apus/linux.bin -r /apus/root.bin root=/dev/ram nobats 60nsram video =pm2fb:mode:1024x768-60 (if you see italics where the "/" forwardslashes should be in the above line then you need to turn off text styles in your email program). However, after successfully decompressing the image file and starting the installation program where I can successfully select the language and keyboard, I cannot specify the swap partition or initialise any partitions because the LINUX installer program says there is a problem: No ext2 partitions that had not already been mounted were detected <continue> I suspect that this is due to my earlier mentioned question about a hard disk with a 4096 byte sector size instead of the more usual 512 byte sector size. I even tried: # bootstrap --apus -k /apus/linux.bin -r /apus/root.bin root=/dev/sdc1 nobats 60nsram video =pm2fb:mode:1024x768-60 where sdc1 is the first partition on the third scsi HD on my system that I had already setup to be my LINUX root partition with an partition type id of 0x4c4e5800. sdc2 was supposed to be the swap partition (0x53575000). Does LINUX only support HDs with 512 bytes per sector and if so does anyone know of an Amiga low level format program that actually works (i.e. can reformat a HD with 4096 bytes per sector to 512 bytes per sector?). If LINUX can initialize a 4096 bytes per sector HD/partition then what am I doing wrong? What do I need to do to get the installation program to detect the partitions? All the other Amiga partitions (FFS) are visible under the mount menu item but they obviously cannot be mounted until the root has been mounted. Any help from anybody much appreciated. Kind regards, Kulwant Re: Your e-mail (31/12/2002) > On 31 Dec 2002, Kulwant Bhogal wrote: >> I've got the "PowerPC installation Guide - APUS (Amiga PowerUp System)" >> by Sven Luther <lu...@de...> v1.0 24 Feb 2000 (which I guess is a >> little old) and I found it incomplete and somewhat lacking. >> e.g. it tells me to use: >> >> # bootstrap --apus -k apus/linux.bin -r apus/images-1.44/root.bin >> root=/dev/ram >> to launch the Debian installer system and then goes onto say: >> >> After installation, to launch Debian, use: >> >> # bootstrap --apus -k apus/linux.bin root=/dev/sda3 >> >> without saying anything about how to actually carry out the >> installation!! > That guide tells about the APUS-specific things only. For a guide about > the Debian part (which is the same across all architectures supported by > Debian), check out http://www.debian.org/. > Gr{oetje,eeting}s, > Geert > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- > ge...@li... > In personal conversations with technical people, I call myself a hacker. > But when I'm talking to journalists I just say "programmer" or something > like that. -- Linus Torvalds > |
|
From: Kulwant B. <kul...@bt...> - 2003-01-01 01:17:58
|
and a peaceful one (well there's always hoping!). Kind regards, Kulwant |
|
From: Geert U. <ge...@li...> - 2002-12-31 08:46:01
|
On 31 Dec 2002, Kulwant Bhogal wrote: > I've got the "PowerPC installation Guide - APUS (Amiga PowerUp System)" by > Sven Luther <lu...@de...> v1.0 24 Feb 2000 (which I guess is a little > old) and I found it incomplete and somewhat lacking. > e.g. it tells me to use: > > # bootstrap --apus -k apus/linux.bin -r apus/images-1.44/root.bin root=/dev/ram > > to launch the Debian installer system and then goes onto say: > > After installation, to launch Debian, use: > > # bootstrap --apus -k apus/linux.bin root=/dev/sda3 > > without saying anything about how to actually carry out the installation!! That guide tells about the APUS-specific things only. For a guide about the Debian part (which is the same across all architectures supported by Debian), check out http://www.debian.org/. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
|
From: Geert U. <ge...@li...> - 2002-12-31 08:42:10
|
On Mon, 30 Dec 2002, Limer wrote:
> >> If I put my WB in 1280x1024 (16bits) and launch bootstrap, I got in error
> >> message saying not enough chip Ram, so I have to go back to 1152x900. No
> >> chance to have a 1280x1024 WB and launch boot strap without having to
> >> reboot with no startup-sequence ?
> >
> > Why do you want to boot with a wb in these resolutions? To tune the
> > console resolution? Then better use the kernel parameter. But I guess you
> > want to tune the resolution of gdm, which will not work, X is not
> > interested at all on which res your wb was in, as always, it's using
> > XF86Config to determine which resolution to use.
>
> Nothing to do with Linux here, I just want to have a WB at 1280x1024 and not
> want to reboot without startup-sequence in order to launch bootstrap.
> I downloaded amiga-lilo, maybe I could solve this.
AFAIK Amiga-Lilo boots Linux/m68k kernels only.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Kulwant B. <kul...@bt...> - 2002-12-31 00:29:43
|
Hello all,
I am a total Linux newbie. I've never seen Linux running on any machine let
alone an Amiga so I'm probably at a disadvantage. But that isn't going to
stop me trying.
I've got a broadband connection so don't mind big downloads. I'd rather not
spend any money (cause I spent it all on my BlizzPPC and BVision) so any
options for doing things on the cheap (i.e. downloading instead of buying)
are preferred.
My question is kinda obvious for a newbie I guess -
Is there a idiot's guide to setting up Linux on an Amiga.
i.e. one that includes:
1. A list of files I need to download (and where to download them from)
2. Step by Step instructions on what to do with (or how to install) the downloaded files.
I've got the "PowerPC installation Guide - APUS (Amiga PowerUp System)" by
Sven Luther <lu...@de...> v1.0 24 Feb 2000 (which I guess is a little
old) and I found it incomplete and somewhat lacking.
e.g. it tells me to use:
# bootstrap --apus -k apus/linux.bin -r apus/images-1.44/root.bin root=/dev/ram
to launch the Debian installer system and then goes onto say:
After installation, to launch Debian, use:
# bootstrap --apus -k apus/linux.bin root=/dev/sda3
without saying anything about how to actually carry out the installation!!
I've downloaded all the files I could find under the files link from the ftp
server and uncompressed the lzh files onto my hard disk. The first command locks up my machine (I've tried the kernel options to use
my BVision and nobats) so am not sure what to try next.
My system is exclusively SCSI (after the 20Gb IDE attached to the Elbox
Flyer went AWOL). In addition to the other SCSI HDs on the system, I have two 4.8Gb Seagate Barracudas attached to the
BlizzardPPC onboard SCSI which unfortunately have a sector size of 4096
bytes instead of the more usual 512. Will this prevent me from using two
partitions from them as
Linux Partitions? I have been unable to find an Amiga tool capable of low
level reformatting them with a 512 byte sector size and don't really want to
buy a PC SCSI card just so that I can borrow someone's PC to reformat them
with the Seagate tool - because I don't know anyone with a SCSI equipped PC.
Can I actually install Linux onto my system, or do I need to add a cheap IDE
to the onboard IDE port to do it (I currently have my first IDE (a Connor
420Mb) for my A1200 attached to get rid of the boot delay)?
That's all for now :-)
Many thanks for putting up with my inane questions.
Kind regards,
Kulwant
|
|
From: Limer <ls...@ma...> - 2002-12-30 22:19:50
|
> >> Hi All, >> Now that X is working, I installed a brand new system with gdm as default >> session manager. But now I can not type my password to enter because the >> keyboard layout is absolutely wrong. So I decided to install a base >> system on another partition to access this partition and change this >> behavior. > > Wew, sounds very complicated to me. > >> The >> question is from where gdm is taking the keyboard layout ? > > From XF86Config.. As everything which is X. But, nevermind, I didn't > manage either to get a session manager working here.. (but it may have > been some fault on my end). Keyboard layout was very screwed too. Now I'm > a happy user of startx.. ;) I just did what the apus FAQ mentioned about wrong keyboard layout and everything is allright now. > > So, if you want to try and fix the keyboard layout, alter the right > XF86Config (on the right partition, as you now seem to have multiple > installations on one disk) according to the one which you had yesterday or > so where you still had a working system (if you forgot how it was, look at > the "InputDevice" section correspondig to "Generic Keyboard" on the > XF86Config file which you posted some days ago on this list). But only > alter the keyboard stuff, don't screw up the video driver or the mouse > again.. ;) > >> If I put my WB in 1280x1024 (16bits) and launch bootstrap, I got in error >> message saying not enough chip Ram, so I have to go back to 1152x900. No >> chance to have a 1280x1024 WB and launch boot strap without having to >> reboot with no startup-sequence ? > > Why do you want to boot with a wb in these resolutions? To tune the > console resolution? Then better use the kernel parameter. But I guess you > want to tune the resolution of gdm, which will not work, X is not > interested at all on which res your wb was in, as always, it's using > XF86Config to determine which resolution to use. > Nothing to do with Linux here, I just want to have a WB at 1280x1024 and not want to reboot without startup-sequence in order to launch bootstrap. I downloaded amiga-lilo, maybe I could solve this. Lio |
|
From: Andreas <an...@po...> - 2002-12-29 23:13:02
|
Hello Limer Am 29-Dez-02 schrieb Limer: > Hi All, > Now that X is working, I installed a brand new system with gdm as default > session manager. But now I can not type my password to enter because the > keyboard layout is absolutely wrong. So I decided to install a base system > on another partition to access this partition and change this behavior. Wew, sounds very complicated to me. > The > question is from where gdm is taking the keyboard layout ? From XF86Config.. As everything which is X. But, nevermind, I didn't manage either to get a session manager working here.. (but it may have been some fault on my end). Keyboard layout was very screwed too. Now I'm a happy user of startx.. ;) So, if you want to try and fix the keyboard layout, alter the right XF86Config (on the right partition, as you now seem to have multiple installations on one disk) according to the one which you had yesterday or so where you still had a working system (if you forgot how it was, look at the "InputDevice" section correspondig to "Generic Keyboard" on the XF86Config file which you posted some days ago on this list). But only alter the keyboard stuff, don't screw up the video driver or the mouse again.. ;) > If I put my WB in 1280x1024 (16bits) and launch bootstrap, I got in error > message saying not enough chip Ram, so I have to go back to 1152x900. No > chance to have a 1280x1024 WB and launch boot strap without having to > reboot with no startup-sequence ? Why do you want to boot with a wb in these resolutions? To tune the console resolution? Then better use the kernel parameter. But I guess you want to tune the resolution of gdm, which will not work, X is not interested at all on which res your wb was in, as always, it's using XF86Config to determine which resolution to use. -- Best wishes, Andi |
|
From: Andreas <an...@po...> - 2002-12-29 23:02:33
|
Hello Limer Am 29-Dez-02 schrieb Limer: >>>> No idea. Normally, it should use the resolution you provide on the >>>> bootstrap line as a kernel parameter. Does it use this one or does it >>>> use something else? Maybe your monitor has some troubles synchronising. >>> >>> no resolution is given when I launch bootstrap, only video=pm2fb: >> >> So maybe you try to provide one. >> > > Ok now I specified video=pm2fb:1024x768-118 but still got 3 switching > screens after the command "starting X display manager : xdm". Maybe it is > because I installed only the base system and X, nothing else. Oh, I thought you were referring to console. No, X resolution is managed by XF86Config. It may be well possible that there is some screen switching with glint, I just don't remember (I am using fbdev since it glint isn't stable on cybervisionppc). [ snip ] >>> Fatal server error: >>> failed to initialize core devices >> >> No wonder it doesn't work.. ;) >> >> Please replace your "InputDevice" Section in your XF86Config with the >> following snipplet: >> >> Section "InputDevice" >> Identifier "Configured Mouse" >> Driver "mouse" >> Option "CorePointer" >> Option "Device" "/dev/amigamouse" >> Option "Protocol" "BusMouse" >> EndSection >> > > Dammed it is WORKING Great!! (did not include the 2 lines below though)! Huh, 2 lines? Only one. But don't worry.. ;) > Thank you > so much. You're welcome! > I got an ugly screen with only twm. Now I should look how to > install KDE and the rest. Or gnome.. But IIRC, if you selected X in tasksel, hasn't it already installed all the gnome and kde stuff?? That's why I wrote about the step-by-step installation using aptitude. > Again thanks I really appreciate your help. > I have a logitech mouseman with a roll, 3rd and 4th buttons. Is there > another option to fully use this mouse ? Hmm, using serial bus? Well, I have no idea about this, theoretically it should be working, but I don't have any experience with that. I would suggest you ask this question on deb...@li... or deb...@li... , they should know about that (subscribe via http://www.debian.org/MailingLists/subscribe). Or browse the archive first at http://lists.debian.org/ . -- Best wishes, Andi |
|
From: Limer <ls...@ma...> - 2002-12-29 22:25:14
|
Hi All, Now that X is working, I installed a brand new system with gdm as default session manager. But now I can not type my password to enter because the keyboard layout is absolutely wrong. So I decided to install a base system on another partition to access this partition and change this behavior. The question is from where gdm is taking the keyboard layout ? If I put my WB in 1280x1024 (16bits) and launch bootstrap, I got in error message saying not enough chip Ram, so I have to go back to 1152x900. No chance to have a 1280x1024 WB and launch boot strap without having to reboot with no startup-sequence ? Thanks in advance Lio |
|
From: Limer <ls...@ma...> - 2002-12-29 01:52:05
|
>>> No idea. Normally, it should use the resolution you provide on the >>> bootstrap line as a kernel parameter. Does it use this one or does it >>> use something else? Maybe your monitor has some troubles synchronising. >> >> no resolution is given when I launch bootstrap, only video=pm2fb: > > So maybe you try to provide one. > Ok now I specified video=pm2fb:1024x768-118 but still got 3 switching screens after the command "starting X display manager : xdm". Maybe it is because I installed only the base system and X, nothing else. > [ snip first part of XF86Config ] > >> (**) Option "Protocol" "ImPS/2" >> (**) Configured Mouse: Protocol: "ImPS/2" > > You are using the wrong protocol. > >> (**) Option "CorePointer" >> (**) Configured Mouse: Core Pointer >> (**) Option "Device" "/dev/input/mice" > > You are using the wrong device. > >> (EE) xf86OpenSerial: Cannot open device /dev/input/mice >> No such device. >> (EE) Configured Mouse: cannot open input device >> (EE) PreInit failed for input device "Configured Mouse" >> (II) UnloadModule: "mouse" >> (WW) No core pointer registered >> No core pointer >> >> Fatal server error: >> failed to initialize core devices > > No wonder it doesn't work.. ;) > > Please replace your "InputDevice" Section in your XF86Config with the > following snipplet: > > Section "InputDevice" > Identifier "Configured Mouse" > Driver "mouse" > Option "CorePointer" > Option "Device" "/dev/amigamouse" > Option "Protocol" "BusMouse" > EndSection > Dammed it is WORKING (did not include the 2 lines below though)! Thank you so much. I got an ugly screen with only twm. Now I should look how to install KDE and the rest. Again thanks I really appreciate your help. I have a logitech mouseman with a roll, 3rd and 4th buttons. Is there another option to fully use this mouse ? > > PS: add > > Option "NoInt10" > > to your "Device" section (that's where you put the glint and BusID stuff > in), you don't need it (it may only cause problems). > Regards Lio |
|
From: Andreas <an...@po...> - 2002-12-28 11:24:30
|
Hello Limer
Am 28-Dez-02 schrieb Limer:
>
>> No idea. Normally, it should use the resolution you provide on the
>> bootstrap line as a kernel parameter. Does it use this one or does it use
>> something else? Maybe your monitor has some troubles synchronising.
>
> no resolution is given when I launch bootstrap, only video=pm2fb:
So maybe you try to provide one.
[ snip ext3 stuff ]
>> Forget tasksel, it's like catching a mouse with an elephant. Download
>> x-window-system by
>>
>> apt-get install x-window-system
>
> I just configured my connection and after running this command, I get a
> message saying I already have the latest version installed.
The better.
>> or using aptitude. Afterwards, download some gnome stuff (if you like).
>> Aptitude will be of great help here!
>>
>
>> I think you have to provide the BusID here using
>>
>> BusID "PCI:0:1:0"
>>
>> Just put it at the end of the "Device" section above (of course before
>> EndSection).
>>
>
> Ok I did that and still I get fatal error as you can see below, but it is
> something to do with "core devices" (no idea whats this now)
The problems is about your mouse. Your XF86Config seems to be pretty fscked
up, how did you do that?
[ snip first part of XF86Config ]
> (**) Option "Protocol" "ImPS/2"
> (**) Configured Mouse: Protocol: "ImPS/2"
You are using the wrong protocol.
> (**) Option "CorePointer"
> (**) Configured Mouse: Core Pointer
> (**) Option "Device" "/dev/input/mice"
You are using the wrong device.
> (EE) xf86OpenSerial: Cannot open device /dev/input/mice
> No such device.
> (EE) Configured Mouse: cannot open input device
> (EE) PreInit failed for input device "Configured Mouse"
> (II) UnloadModule: "mouse"
> (WW) No core pointer registered
> No core pointer
>
> Fatal server error:
> failed to initialize core devices
No wonder it doesn't work.. ;)
Please replace your "InputDevice" Section in your XF86Config with the following
snipplet:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/amigamouse"
Option "Protocol" "BusMouse"
EndSection
PS: add
Option "NoInt10"
to your "Device" section (that's where you put the glint and BusID stuff in),
you don't need it (it may only cause problems).
--
Best wishes,
Andi
|
|
From: Limer <ls...@ma...> - 2002-12-28 00:34:15
|
> No idea. Normally, it should use the resolution you provide on the > bootstrap line as a kernel parameter. Does it use this one or does it u= se > something else? Maybe your monitor has some troubles synchronising. no resolution is given when I launch bootstrap, only video=3Dpm2fb: >> After reading some docs I found how to get an ext3 partition by using >> mke2fs -j /dev/... but can I do that on my boot partition without loos= ing >> everything ? > = > Hmm, IIRC this should be possible. Please read the article on > http://www.debianplanet.org/node.php?id=3D627 . It will provide you wit= h > some useful information about the switch (no, it is NOT about Ellen.. ;= ) > ). > = >> I succeed with the floppy : -o size=3D1760 was too much I restart the >> installation but after the base system, I choose only X with tasksel. > = > Forget tasksel, it's like catching a mouse with an elephant. Download > x-window-system by > = > apt-get install x-window-system I just configured my connection and after running this command, I get a message saying I already have the latest version installed. > = > or using aptitude. Afterwards, download some gnome stuff (if you like).= > Aptitude will be of great help here! > = > I think you have to provide the BusID here using > = > BusID "PCI:0:1:0" > = > Just put it at the end of the "Device" section above (of course before > EndSection). > = Ok I did that and still I get fatal error as you can see below, but it is= something to do with "core devices" (no idea whats this now) Thanks anyway for your help = Lio Build Operating System: Linux 2.4.18-powerpc-smp ppc [ELF] = Module Loader present (=3D=3D) Log file: "/var/log/XFree86.0.log", Time: Sat Dec 28 01:11:53 20= 02 (=3D=3D) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "Generic Video Card" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "macintosh" (**) XKB: model: "macintosh" (**) Option "XkbLayout" "fr" (**) XKB: layout: "fr" (=3D=3D) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/= usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/f= onts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi" (=3D=3D) RgbPath set to "/usr/X11R6/lib/X11/rgb" (=3D=3D) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:01:0: chip 104c,3d07 card e4e4,e4e4 rev 01 class 03,80,00 hd= r 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleare= d) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (--) PCI: (0:1:0) Texas Instruments Permedia 2 rev 1, Mem @ 0xef000000/17= , 0xe0000000/23, 0xe1000000/23, BIOS @ 0xe2000000/16 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [3] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xe2000000 - 0xe200ffff (0x10000) MX[B](B) [1] -1 0 0xe1000000 - 0xe17fffff (0x800000) MX[B](B) [2] -1 0 0xe0000000 - 0xe07fffff (0x800000) MX[B](B) [3] -1 0 0xef000000 - 0xef01ffff (0x20000) MX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xe2000000 - 0xe200ffff (0x10000) MX[B](B) [1] -1 0 0xe1000000 - 0xe17fffff (0x800000) MX[B](B) [2] -1 0 0xe0000000 - 0xe07fffff (0x800000) MX[B](B) [3] -1 0 0xef000000 - 0xef01ffff (0x20000) MX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [3] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) All system resource ranges: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0 0xe2000000 - 0xe200ffff (0x10000) MX[B](B) [3] -1 0 0xe1000000 - 0xe17fffff (0x800000) MX[B](B) [4] -1 0 0xe0000000 - 0xe07fffff (0x800000) MX[B](B) [5] -1 0 0xef000000 - 0xef01ffff (0x20000) MX[B](B) [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Server Extension, version 0.1 (II) LoadModule: "bitmap" (II) Reloading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Loading font Bitmap (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Server Extension, version 0.1 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XFree86-DRI (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension FontCache (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.1.9 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font FreeType (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Server Extension, version 0.1 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Reloading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Loading extension GLX (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/libint10.a (II) Module int10: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: "pex5" (II) Loading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Module pex5: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension X3D-PEX (II) LoadModule: "record" (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: "speedo" (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a (II) Module speedo: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Speedo (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: "xie" (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: "glint" (II) Loading /usr/X11R6/lib/modules/drivers/glint_drv.o (II) Module glint: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) GLINT: driver for 3Dlabs chipsets: gamma, ti_pm2, ti_pm, pm3, pm2v, pm2, pm, 300sx, 500tx, mx, delta (--) Chipset ti_pm2 found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0 0xe2000000 - 0xe200ffff (0x10000) MX[B](B) [3] -1 0 0xe1000000 - 0xe17fffff (0x800000) MX[B](B) [4] -1 0 0xe0000000 - 0xe07fffff (0x800000) MX[B](B) [5] -1 0 0xef000000 - 0xef01ffff (0x20000) MX[B](B) [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) resource ranges after probing: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0 0xe2000000 - 0xe200ffff (0x10000) MX[B](B) [3] -1 0 0xe1000000 - 0xe17fffff (0x800000) MX[B](B) [4] -1 0 0xe0000000 - 0xe07fffff (0x800000) MX[B](B) [5] -1 0 0xef000000 - 0xef01ffff (0x20000) MX[B](B) [6] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [7] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [8] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [9] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [10] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [11] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [12] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) GLINT(0): Depth 24, (--) framebuffer bpp 32 (=3D=3D) GLINT(0): RGB weight 888 (=3D=3D) GLINT(0): Default visual is TrueColor (=3D=3D) GLINT(0): Using gamma correction (1.0, 1.0, 1.0) (**) GLINT(0): Option "UseFBDev" "true" (=3D=3D) GLINT(0): Using HW cursor (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a (II) Module fbdevhw: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 0.0.2 ABI class: XFree86 Video Driver, version 0.4 (**) GLINT(0): Using Linux framebuffer device (--) GLINT(0): Chipset: "ti_pm2" (--) GLINT(0): Linear framebuffer at 0xE1000000 (--) GLINT(0): MMIO registers at 0xEF010000 (--) GLINT(0): VideoRAM: 8192 kByte (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (--) GLINT(0): FIFO Size is 256 DWORDS (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/libint10.a (II) GLINT(0): Initializing int10 (EE) GLINT(0): Cannot read V_BIOS (5) (=3D=3D) GLINT(0): Min pixel clock is 16 MHz (--) GLINT(0): Max pixel clock is 110 MHz (II) GLINT(0): Generic Monitor: Using hsync range of 30.00-86.00 kHz (II) GLINT(0): Generic Monitor: Using vrefresh range of 55.00-160.00 Hz (II) GLINT(0): Clock range: 16.25 to 110.00 MHz (II) GLINT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1792x1344" (insufficient memory fo= r mode) (II) GLINT(0): Not using default mode "1792x1344" (insufficient memory fo= r mode) (II) GLINT(0): Not using default mode "1856x1392" (insufficient memory fo= r mode) (II) GLINT(0): Not using default mode "1856x1392" (insufficient memory fo= r mode) (II) GLINT(0): Not using default mode "1920x1440" (insufficient memory fo= r mode) (II) GLINT(0): Not using default mode "1920x1440" (insufficient memory fo= r mode) (II) GLINT(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan) (--) GLINT(0): Virtual size is 1024x768 (pitch 1024) (**) GLINT(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (II) GLINT(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 = 772 808 +hsync +vsync (**) GLINT(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) GLINT(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 = 631 +hsync +vsync (**) GLINT(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) GLINT(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 5= 09 +hsync -hsync +vsync -vsync (++) GLINT(0): DPI set to (100, 100) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.1 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.4 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor=3D"The XFree86 Project" compiled for 4.1.0.1, module version =3D 1.2.0 ABI class: XFree86 Video Driver, version 0.4 (II) GLINT(0): I2C bus "DDC" initialized. (II) GLINT(0): I2C bus "Video" initialized. (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xe1000000 - 0xe17fffff (0x800000) MX[B] [1] 0 0 0xe0000000 - 0xe07fffff (0x800000) MX[B] [2] 0 0 0xef000000 - 0xef01ffff (0x20000) MX[B] [3] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [4] -1 0 0x00000000 - 0x00000000 (0x1) MX[B] [5] -1 0 0xe2000000 - 0xe200ffff (0x10000) MX[B](B) [6] -1 0 0xe1000000 - 0xe17fffff (0x800000) MX[B](B) [7] -1 0 0xe0000000 - 0xe07fffff (0x800000) MX[B](B) [8] -1 0 0xef000000 - 0xef01ffff (0x20000) MX[B](B) [9] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [10] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [11] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [13] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [14] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprD) [15] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprD) (II) GLINT(0): I2C device "DDC:ddc2" registered. (II) GLINT(0): I2C device "DDC:ddc2" removed. (II) GLINT(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Offscreen Pixmaps Driver provided WriteBitmap replacement Driver provided WritePixmap replacement Setting up tile and stipple cache: 32 128x128 slots 10 256x256 slots (=3D=3D) GLINT(0): Backing store disabled (=3D=3D) GLINT(0): Silken mouse enabled (**) Option "dpms" (**) GLINT(0): DPMS enabled (II) GLINT(0): direct rendering disabled (II) GLINT(0): Initializing Xv driver rev. 4 (II) GLINT(0): Xv frontend scaler enabled (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 PEXExtensionInit: Couldn't open default PEX font file Roman_M (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/input/mice" (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. (EE) Configured Mouse: cannot open input device (EE) PreInit failed for input device "Configured Mouse" (II) UnloadModule: "mouse" (WW) No core pointer registered No core pointer Fatal server error: failed to initialize core devices |
|
From: Michel <mi...@da...> - 2002-12-27 18:05:08
|
On Mon, 2002-12-23 at 20:06, Krystian Bacławski wrote: > > I'm using 2.4.18 kernel and I experience a few problems with it. It's > quite stable but try to install xserver 4.x.x and you will start running > through the minefields :) I've lost one ext2 partition and two reiserfs > because of xserver 4.1.0 running on 2.4.18. I found out that this version > causes data corruption while writing to harddisk. Xserver 4.2.1 is a bit > better it doesn't cause data coruuption while writing to "/" partition, > but sometimes it trashes swap partition (what randomly crashes programs) > and after a xserver's restart every(!) program ends with "segmentation > fault" error. The X server can't really do that, sounds rather like a kernel or hardware problem. Besides, I wouldn't recommend ReiserFS, not even on i386. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
45 messages has been excluded from this view by a project administrator.
