Re: X 4.1.0 Hints for french PowerBook users...
Hi,
I support the idea of using command (apple) key instead of the alt key on
the mac keyboard (or if you use a mac keyboard on a pc.) One more reason is
that 'alt' is primarely labeled 'option' in the mac parlance and that should
be its major task: generating special chars. I wonder how many apps that
would break though (the ones that use option-command-something would
definitely suffer the change.)
Talking about keyboard mapping, I used a couple of powerbooks in the past
under macos 9/X, and as you probably know these laptops have a fn key.
On the MacOS, Apple uses the Fn key + F1-F12 to generate a function key
event. This, I think, is pretty stupid: how many times do you change the
screen luminosity vs. doing cut/paste in an app just to mention one example.
Still on the powerbook running macos, you can get hit enter by using
fn+return and enter has its own key on the right of command-right (note:
enter is different than return on the mac.) I wish they would have been put
an option/alt key instead of the single enter key. On MacOS, I was using a
utility that remapped the keyboard just like I wanted it to be (I guess I
was not the only one annoyed by this.)
How is it done under Linux/XF86? Is there any 'easy' way to change the
mapping of your keyboard without recompiling the kernel or whatever?
Thanks for your info,
Laurent
on 9/3/01 2:08 PM, Florent Pillet at [EMAIL PROTECTED] wrote:
> on 3/09/01 19:28, Tuomas Kuosmanen at [EMAIL PROTECTED] wrote:
>
>> This has the effect of making []{} etc to work. However, it disables ALT
>> for me (though I tried it on the finnish/swedish keymap) - thus you
>> cannot Ctrl-Alt-Backspace to kill the X server, nor can you use Alt for
>> anything (alt-drag to move windows for example on many window managers)
>>
>> Tuomas
>
> Interesting.
>
> I'm not an expert with this keyboard configuration yet. Since xkb setting
> files seem to be under-documented, I'm trying to make my way through them.
> I'm trying to find a fix for this. The default X mappings for Mac keyboards
> are not perfect since I think ALT is misused (the Command key should be used
> instead). Therefore, I wonder if it would not be more appropriate to use the
> Command key as "Alt_L" and leave the Alt key for what it is really used
> under MacOS, that is access additional characters on the various keys.
Re: Difficulty installing woody OR potato on Beige G3
On Mon, Sep 03, 2001 at 07:47:25PM -0800, Ethan Benson wrote: > i reccommend netboot. keeping macos around is impossible without > keeping all that useless, harmful cruft as well. > > http://www.alaska.net/~erbenson/doc/netboot.html Well, uh, that's great, Ethan, but this is a _beige_ (OldWorld) G3, and so netboot is more or less impossible, given its craptacular OF support, right? In any case, I was able to get the base distribution installed via the potato boot-floppies, leaving only the problem with the potato ofpath not liking the beige 266's hardware tree. If I know which partition my root is (/dev/hda2), could anybody maybe just tell me what the appropriate goop to pass to nvsetenv is? Barring that, anyone have a handy binary for ofpath that groks beige G3-land (in case your memory needs refreshing, this particular problem last cropped up in a similar thread in January -- I do try to use the archives)? I'll poke around, but I'd sorta like to get this finished. Thanks again for all the help. Forrest -- . . . the self-reflecting image of a narcotized mind . . . ozymandias G desiderata [EMAIL PROTECTED] desperate, deathless (415)558-9064http://www.aoaioxxysz.com/ ::AOAIOXXYSZ::
Re: Troubles with Potato/Woody on iBook 2001
Laurent de Segur <[EMAIL PROTECTED]> writes: Hi, > - I built the kernel the debian way (make-kpkg yadi yada...) That dosen't work for me. > - I DO use 'video=atyfb video=ofonly' in the append string. With the 2.2.* kernel only use video=ofonly. With the 2.4 kernel the other string is no problem. > When the iBook restarts, I still get the Do-QUIESCE message. Linux boots > (supposedly as I hear the disk) but the OF screen is blocking the view > kinda. That's the video string. > Switching to linux-2.2.18 which I got from somewhere else works. It's just > not fair! Upgrade to 2.4. But not 2.4.8 from woody. The right one is from ben's page. It's down in the moment. But there is a mirror at http://www.ppckernel.org. Upgrade your kernel and your mouse is working. :-) (I had a lot of problems with that. bye Thorsten
Re: Startup disk ruined my booting setup
On Mon, 3 Sep 2001, Individual . . wrote: > I opened the Startup Disk control pane, didnt touch anything, just > opened it to have a look out of sheer boredom, and now it boots > straight into macos, though the option key thing still works. > > I tried running ybin, but it didnt change anything. You probably have "nonvram" in your yaboot.conf file. This option prevents ybin from resetting the boot-device variable that Startup Disk changed. Remove that line from /etc/yaboot.conf and then run ybin. You can also fix this problem by zapping your PRAM. Hold down cmd-opt-p-r at startup until the machine has chimed twice. As long as your bootstrap partition is the first bootable volume, the menu will be restored.
Startup disk ruined my booting setup
I had things set up quite nicely: turn on the power, and im presented with a black screen and "m for macos, l for linux". Defualt was macos after 10seconds. Or, I could hold down option key and get icons for the different OSs. I opened the Startup Disk control pane, didnt touch anything, just opened it to have a look out of sheer boredom, and now it boots straight into macos, though the option key thing still works. I tried running ybin, but it didnt change anything. Suggestions? PS. Thank you for replying to my previous posts, sorry for not thanking you personally (you know who you are!).
Re: Difficulty installing woody OR potato on Beige G3
On Mon, Sep 03, 2001 at 08:36:16PM -0700, ozymandias G desiderata wrote: > On Mon, Sep 03, 2001 at 07:24:02PM -0800, Ethan Benson wrote: > > > > e) Enter mac-fdisk, and here's where the fun begins. If I do an 'i' > > > to reinitialize the partition table and then immediately do a 'w' > > > to write the new partition table, everything's cool. As soon as I > > > try to create any partitions, though, any attempts to write the > > > changed partition table thereafter cause an exception that reads > > > "Unable to handle kernel NULL pointer at virtual address". At this > > > point both woody and potato chunder. > > > > just reboot, the partititon table will be fine. bug benh to fix the > > partition table reread ioctl. > > Well, yeah, I'd noticed that the partition table was written just > fine, when I booted from a MacOS install CD and reinitialized the disk > preparatory to giving everything yet another try. The only problem > with this strategy is I don't know _how_ I'm to reboot once I've nuked > the partition tables for the entire disk. Keep a MacOS partition > around until I'm done with the installation? Install from the potato > boot floppies? I guess I'll give the latter a try. > > Thanks for your help. i reccommend netboot. keeping macos around is impossible without keeping all that useless, harmful cruft as well. http://www.alaska.net/~erbenson/doc/netboot.html -- Ethan Benson http://www.alaska.net/~erbenson/ pgp4aAvLdvF8x.pgp Description: PGP signature
Re: Difficulty installing woody OR potato on Beige G3
On Mon, Sep 03, 2001 at 07:24:02PM -0800, Ethan Benson wrote: > > e) Enter mac-fdisk, and here's where the fun begins. If I do an 'i' > > to reinitialize the partition table and then immediately do a 'w' > > to write the new partition table, everything's cool. As soon as I > > try to create any partitions, though, any attempts to write the > > changed partition table thereafter cause an exception that reads > > "Unable to handle kernel NULL pointer at virtual address". At this > > point both woody and potato chunder. > > just reboot, the partititon table will be fine. bug benh to fix the > partition table reread ioctl. Well, yeah, I'd noticed that the partition table was written just fine, when I booted from a MacOS install CD and reinitialized the disk preparatory to giving everything yet another try. The only problem with this strategy is I don't know _how_ I'm to reboot once I've nuked the partition tables for the entire disk. Keep a MacOS partition around until I'm done with the installation? Install from the potato boot floppies? I guess I'll give the latter a try. Thanks for your help. Forrest -- . . . the self-reflecting image of a narcotized mind . . . ozymandias G desiderata [EMAIL PROTECTED] desperate, deathless (415)558-9064http://www.aoaioxxysz.com/ ::AOAIOXXYSZ::
Re: Difficulty installing woody OR potato on Beige G3
On Mon, Sep 03, 2001 at 08:07:21PM -0700, ozymandias G desiderata wrote: > > It seems that whether I try to do an HD install or install from > floppy, I'm equally screwed. Let me outline my two scenarios of > screwage, after which I will throw myself upon the mercy of the forum: > > 1) Floppy install: > > Well, this one is pretty simple, really. The HFS boot floppy works > jim-dandy, but the ramdisk image on root.bin refuses to read and > causes an oops. That's because it's currently corrupted, right? I its trunicated yes, about 5k or so is missing from the end. gzip wont' like that. > admit I haven't tried the potato version of the floppy images, largely > because of Ethan's insistence that we'd all rather die lingering, > painful deaths than deal with the potato boot floppies at this late > date. they aren't quite that bad, but i have lost all patience for people who screw up and botch thier install by ignoring the fing manual. woody b-f make it significantly more difficult to screw up and then play dumb. > e) Enter mac-fdisk, and here's where the fun begins. If I do an 'i' > to reinitialize the partition table and then immediately do a 'w' > to write the new partition table, everything's cool. As soon as I > try to create any partitions, though, any attempts to write the > changed partition table thereafter cause an exception that reads > "Unable to handle kernel NULL pointer at virtual address". At this > point both woody and potato chunder. just reboot, the partititon table will be fine. bug benh to fix the partition table reread ioctl. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpQ8DvhD59Ut.pgp Description: PGP signature
Re: Kernel Drivers in PPC build: where are they?
On Mon, Sep 03, 2001 at 11:00:50PM -0400, Bill Carini wrote: > On Mon, 03 Sep 2001 21:37:06 Ethan Benson wrote: > > > > > > you must not put kernels on the bootstrap partition. the bootstrap > > partition must be exactly 800K and be type Apple_Bootstrap, it must > > not be mounted anywhere at any time. > > > > Oh, then the advice that I read somewhere is wrong: it was suggested > that you > might want to size the bootstrap partition somewhat larger in order to > accomodate > possible future bloat. i can assure you that i WILL NOT allow yaboot/ybin to become anywhere near that bloated. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpBKlKwyefC1.pgp Description: PGP signature
Re: Kernel Drivers in PPC build: where are they?
On Mon, 03 Sep 2001 21:37:06 Ethan Benson wrote: > > > you must not put kernels on the bootstrap partition. the bootstrap > partition must be exactly 800K and be type Apple_Bootstrap, it must > not be mounted anywhere at any time. > Oh, then the advice that I read somewhere is wrong: it was suggested that you might want to size the bootstrap partition somewhat larger in order to accomodate possible future bloat. --Bill Carini
Difficulty installing woody OR potato on Beige G3
It seems that whether I try to do an HD install or install from floppy, I'm equally screwed. Let me outline my two scenarios of screwage, after which I will throw myself upon the mercy of the forum: 1) Floppy install: Well, this one is pretty simple, really. The HFS boot floppy works jim-dandy, but the ramdisk image on root.bin refuses to read and causes an oops. That's because it's currently corrupted, right? I admit I haven't tried the potato version of the floppy images, largely because of Ethan's insistence that we'd all rather die lingering, painful deaths than deal with the potato boot floppies at this late date. 2) HD install: a) Download BootX, the kernel, and the compressed ramdisk image. b) Use BootX to load up the kernel (either at next reboot or after MacOS loading finishes, doesn't affect the outcome). c) Read the, uh, skeletal release notes for woody. d) Ignore the keyboard configuration step because it causes the installer to eat flaming death. e) Enter mac-fdisk, and here's where the fun begins. If I do an 'i' to reinitialize the partition table and then immediately do a 'w' to write the new partition table, everything's cool. As soon as I try to create any partitions, though, any attempts to write the changed partition table thereafter cause an exception that reads "Unable to handle kernel NULL pointer at virtual address". At this point both woody and potato chunder. I've been attempting to install this particular system several times over the last couple months as I've had time, and I'm getting really frustrated. Does anything obvious suggest itself to you? Obviously, since it's an Oldworld Mac, I can't boot from CD, and unless someone sorts out the woody root.bin for FD images, I can't do an install with those either. Is there some sort of hardware nastiness that could be causing this? yours, Forrest -- . . . the self-reflecting image of a narcotized mind . . . ozymandias G desiderata [EMAIL PROTECTED] desperate, deathless (415)558-9064http://www.aoaioxxysz.com/ ::AOAIOXXYSZ::
Re: debian-powerpc: yaboot & ybin bug ???
On Tue, Sep 04, 2001 at 11:53:44AM +1000, Brendan J Simon wrote: > I found a bug in ybin. > I added a "default=" statement at the top of my /etc/yaboot.conf. was the label a label for a linux kerenl entry? default=macos will not work. for that you need defaultos=macos > I then did a "ybin -v" and everything went fine. ybin unfortunatly can't check everything. > I rebooted and yaboot barfed because there was a syntax error in the > yaboot.conf. please send your yaboot.conf. > I could not reboot to my old system easily. I had to boot off the CD > which was a pain because I had to search the web to find the right OF > commands and right kernel parameters to pass to the kernel (ie. > video=ofonly). not true at the yaboot boot: prompt: hd:3,/boot/vmlinux root=/dev/hda3 ro > There are two solutions to avoid this and improve yaboot and ybin. > > 1) ybin (or something) should check the yaboot.conf to make sure it is > valid before writing it to the bootstrap partition. that requires a significant rewrite of its parsing code, the only /bin/sh alternative i can come up with has as many deficiencies as the current code, that leaves rewriting ybin in C, which i may do eventually, but not for awhile. > 2) yaboot should just ignore any lines with errors on it. This way I > still would have had a menu pop up and be able to reboot to one of my > other configurations. yaboot already ignores bogus lines, i haven't been able to trigger an error like yours in a long time, i need to see your yaboot.conf. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpkSsrGSXfPD.pgp Description: PGP signature
Re: Troubles with Potato/Woody on iBook 2001
On Mon, Sep 03, 2001 at 05:41:56PM -0700, Laurent de Segur wrote: > > The problem is still here. Reading debian docs for half a day didn't solve > anything :-( - I learned a lot more about various policies though... > > Here is what I do: > - I built the kernel the debian way (make-kpkg yadi yada...) > - The kernel image I get in /boot after the kernel successfully built and > installed is vmlinux-2.2.19. This image, I copy to my bootstrap partition > (hfs) where yaboot resides. wrong, kernels must never be on HFS filesystems. resize your bootstrap partition to 800K to prevent you from doing this in the future. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpxGBf50fqNX.pgp Description: PGP signature
xine 0.5.2 and performance
I guess this question is more for Michel Daenzer, but i'll field it to the rest of the list: In april, Michel posted deb's for xine-4.0.01. video plays very nice, and audio stays in sync pretty well. I stole siggi's debification of xine-ui and xine-libs 0.5.2 and rebuilt them ( heh, i'm impatient: i want to watch movies on a flight tomorrow :> ) but now sound plays really badly. my main question is how can xine-4.0.01 be so much faster than xine-0.5.2, considering that there have allegedly been big performance improvements in xine since 4.0.01 ... or maybe there haven't been any improvements after all. Michel: did you just use the stock compiler optimizations when you built your xine debs ? thanks ==rob -- Rob Latham: linux A-Team Bethlehem, PA USA EAE8 DE90 85BB 526F 3181 1FCF 51C4 B6CB 08CC 0897
debian-powerpc: yaboot & ybin bug ???
I found a bug in ybin. I added a "default=" statement at the top of my /etc/yaboot.conf. I then did a "ybin -v" and everything went fine. I rebooted and yaboot barfed because there was a syntax error in the yaboot.conf. I could not reboot to my old system easily. I had to boot off the CD which was a pain because I had to search the web to find the right OF commands and right kernel parameters to pass to the kernel (ie. video=ofonly). There are two solutions to avoid this and improve yaboot and ybin. 1) ybin (or something) should check the yaboot.conf to make sure it is valid before writing it to the bootstrap partition. 2) yaboot should just ignore any lines with errors on it. This way I still would have had a menu pop up and be able to reboot to one of my other configurations. Maybe some of these have already been implemented. I'm using ybin version 1.2.4 and yaboot version ??? (not sure without rebooting). It's all part of the debian yaboot/testing package which I think is version 1.2.3-1.2.4-1 . Regards, Brendan Simon.
Re: Kernel Drivers in PPC build: where are they?
On Mon, Sep 03, 2001 at 06:01:14PM -0700, Laurent de Segur wrote: > on 9/3/01 5:48 PM, Ethan Benson at [EMAIL PROTECTED] wrote: > > > > > the kernel is not stored on teh bootstrap partition, its stored on > > your ext2 / partition or your ext2 /boot partition. never on teh > > bootstrap partition. > > > > > Are you sure? That's big news to me! I need to readjust here (and I need a > drink too :-) um, yes im sure, i do maintain the powerpc bootloader stuff afterall. > If what you say is correct, then I have always misunderstood this and > probably got confused since the days of BootX where you needed to store your > kernel in the hfs partition (where bootx was residing.) Now that you are bootx is only for oldworld crap. newworlds cannot and must not use it. > saying that, I kinda understand why nowhere it was mentioned to copy the > kernel image to the bootstrap partition. Indulge me, but please confirm > this. Thanks, you must not put kernels on the bootstrap partition. the bootstrap partition must be exactly 800K and be type Apple_Bootstrap, it must not be mounted anywhere at any time. -- Ethan Benson http://www.alaska.net/~erbenson/ pgp3KPkZD4XVD.pgp Description: PGP signature
Re: Troubles with Potato/Woody on iBook 2001
on 9/2/01 11:34 PM, Arrigo Benedetti at [EMAIL PROTECTED] wrote: >> Rebooting with the original 2.2.18 works fine. On the iBook 2001, I have to >> set "video=ofonly" to get video at boot time. Is this related? It seems that >> the OS is still loading but I can't see it. >> > > Yes, I got the Do-QUIESCE message until I started giving the "video=ofonly" > argument to the kernel. You can put append "video=ofonly" in yaboot.conf as > you would do with lilo.conf on x86 linux. > Hi again, The problem is still here. Reading debian docs for half a day didn't solve anything :-( - I learned a lot more about various policies though... Here is what I do: - I built the kernel the debian way (make-kpkg yadi yada...) - The kernel image I get in /boot after the kernel successfully built and installed is vmlinux-2.2.19. This image, I copy to my bootstrap partition (hfs) where yaboot resides. - I reboot with the yaboot.conf pointing to the new image. - I DO use 'video=atyfb video=ofonly' in the append string. When the iBook restarts, I still get the Do-QUIESCE message. Linux boots (supposedly as I hear the disk) but the OF screen is blocking the view kinda. Switching to linux-2.2.18 which I got from somewhere else works. It's just not fair! What's wrong with my procedure? Did I forget to tell set a flag when building the kernel, like don't call quiesce or something (shouldn't it be yaboot who calls quiesce anyway)? I am running out of ideas... Can someone help plase? Thanks a lot, Laurent
Re: Kernel Drivers in PPC build: where are they?
on 9/3/01 5:48 PM, Ethan Benson at [EMAIL PROTECTED] wrote: > > the kernel is not stored on teh bootstrap partition, its stored on > your ext2 / partition or your ext2 /boot partition. never on teh > bootstrap partition. > Are you sure? That's big news to me! I need to readjust here (and I need a drink too :-) If what you say is correct, then I have always misunderstood this and probably got confused since the days of BootX where you needed to store your kernel in the hfs partition (where bootx was residing.) Now that you are saying that, I kinda understand why nowhere it was mentioned to copy the kernel image to the bootstrap partition. Indulge me, but please confirm this. Thanks, Laurent
Re: Kernel Drivers in PPC build: where are they?
On Mon, Sep 03, 2001 at 09:54:30AM -0700, Laurent de Segur wrote: > > Is the loading mechanism for kernel modules supported on the PPC platform? > Can I compile my kernel without a specific module then compile the driver > and store it in /lib/modules// or am I better off compiling > as a big monolithic kernel? My problem is understanding where the kernel modules work fine on powerpc. (unless your taking i386 modules and expecting them to work on powerpc) > image stored on the bootstrap partition (vmlinux) kicks in the root > partition and can see the drivers if it can see them at all on it. the kernel is not stored on teh bootstrap partition, its stored on your ext2 / partition or your ext2 /boot partition. never on teh bootstrap partition. > I was looking at the PowerPC installation disk for debian. I noticed that > there is a file in there called drivers.tar.gz. What am I supposed to do > with this file? Should I leave it in the bootstrap dir uncompressed next to > yaboot and vmlinux files? Decompress it and move it in the /lib/modules/ dir > in my root partition? Puzzled. the installation system will use it to install the kernel drivers. you should not extract it yourself. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpouCfkxpaoA.pgp Description: PGP signature
Netgear Card in Installer
I'm attempting to migrate from LinuxPPC. I would like to install from network since I have a very local mirror. However, my beige G3's onboard ethernet is having compatibility issues with my campus network, so I need to use my Netgear FA311. Unfortunately, the National Semiconductor drivers aren't in the install kernel/ramdisk. I have natsemi.o from my 2.2.19 LinuxPPC modules directory, but trying to insmod it is met with half a dozen unresolved symbol errors. I was able to succesfully insmod pci-scan.o, the only module on which natsemi.o seems to depend on my old system. What else do I need to do to use the FA311 in the installer? Thanks, -- Brian "A man who wants to lead the Email: [EMAIL PROTECTED] orchestra must turn his back Web: http://www.personal.psu.edu/bhv1/ on the crowd." -- Max Lucado
Re: Kernel Drivers in PPC build: where are they?
Hi Laurent, On Mon, Sep 03, 2001 at 09:54:30AM -0700, Laurent de Segur wrote: > ... I still like the machine better > though, so it's worse the extra efforts ;-) If you mean worth instead of worse - so most of us do so, I think ;-) > Is the loading mechanism for kernel modules supported on the PPC platform? Read /Documentation/kmod.txt in the kernel-sources ;-) Eventually you're interested in and so on > Can I compile my kernel without a specific module then compile the driver > and store it in /lib/modules// or am I better off compiling > as a big monolithic kernel? Why you want compile a lonley kernel and by a second effort any driver (is that the way to do in x86, you mentioned above?) I mean, AFAIK you decide compiling drivers in the kernel _or_compile it as module ... - am I wrong or misunderstanding your willing? > My problem is understanding where the kernel > image stored on the bootstrap partition (vmlinux) kicks in the root > partition and can see the drivers if it can see them at all on it. > > I was looking at the PowerPC installation disk for debian. I noticed that > there is a file in there called drivers.tar.gz. What am I supposed to do > with this file? Why don't let the installation do this and compile your own kernel after you installed from a working system? > Should I leave it in the bootstrap dir uncompressed next to > yaboot and vmlinux files? Decompress it and move it in the /lib/modules/ dir > in my root partition? Puzzled. Hmmm ;-/ . So AFAIK (and did) you have to compile the kernel (with debian ) the following way (as root): cd /usr/src/linux (or whereever the kernel-sources are) make config (or make menuconfig or make xconfig - last recommended if it works on your install) make-kpkg kernel_image cd .. dpkg -i kernel-image* This should install the vmlinux in /boot and links /vmlinux to it and install all the drivers you choosen as module in /lib/modules/2.*.* . Hope that helps Cheers -- mfg Georg Koss mailto: [EMAIL PROTECTED]
Re: X 4.1.0 Hints for french PowerBook users...
on 3/09/01 19:28, Tuomas Kuosmanen at [EMAIL PROTECTED] wrote:
> This has the effect of making []{} etc to work. However, it disables ALT
> for me (though I tried it on the finnish/swedish keymap) - thus you
> cannot Ctrl-Alt-Backspace to kill the X server, nor can you use Alt for
> anything (alt-drag to move windows for example on many window managers)
>
> Tuomas
Interesting.
I'm not an expert with this keyboard configuration yet. Since xkb setting
files seem to be under-documented, I'm trying to make my way through them.
I'm trying to find a fix for this. The default X mappings for Mac keyboards
are not perfect since I think ALT is misused (the Command key should be used
instead). Therefore, I wonder if it would not be more appropriate to use the
Command key as "Alt_L" and leave the Alt key for what it is really used
under MacOS, that is access additional characters on the various keys.
--
Florent Pillet, Code Segment [EMAIL PROTECTED]
PGP Key: D13C 6DD7 D0E2 7891 4AF9 0111 9514 4753 02F1 4D6D
Re: downgrade sid to woody?
Kevin van Haaren <[EMAIL PROTECTED]> writes: > I messed up my machine a couple of times running unstable (huh, > wonder why they call it that 8-) anyway I want to downgrade to just > woody. I dug through the apt-get and dselect man pages and didn't > see a way to do this. Is it enough to remove the unstable > references in sources.list and run upgrade? or will that leave some > of the unstable packages in place? Apt won't install older packages unless you use its "pinning" feature. See apt_preferences(5). Be sure to use a downgradable priority (i.e. >= 1000). Note that downgrading is not supported in the Debian system, although it should work for most packages. This question is more suitable for -user, by the way.
Re: Kernel Drivers in PPC build: where are they?
Laurent de Segur <[EMAIL PROTECTED]> writes: > Is the loading mechanism for kernel modules supported on the PPC platform? Of course. > Can I compile my kernel without a specific module then compile the > driver and store it in /lib/modules// or am I better > off compiling as a big monolithic kernel? You can compile modules separately after building the kernel, yes. The best way to build kernels is to use kernel-package. Do "apt-get install fakeroot kernel-package", then view the file /usr/share/doc/kernel-package/README.gz. > My problem is understanding where the kernel image stored on the > bootstrap partition (vmlinux) kicks in the root partition and can > see the drivers if it can see them at all on it. By "bootstrap partition", I'm assuming you mean a separate /boot filesystem. Kernels shouldn't be stored on the Apple_Bootstrap partition, AIUI. The answer to what I think your question is: you can't compile your filesystem or disk drivers as modules¹; they need to be part of the kernel so it can mount the root file system (containing /lib) and get the rest of the modules. > I was looking at the PowerPC installation disk for debian. I noticed > that there is a file in there called drivers.tar.gz. What am I > supposed to do with this file? Should I leave it in the bootstrap > dir uncompressed next to yaboot and vmlinux files? Decompress it and > move it in the /lib/modules/ dir in my root partition? drivers.tar.gz is for the debian boot-floppies. During the installation, you'll be prompted for the path to it. Unless you're doing some sort of manual installation, you shouldn't need to do anything with it yourself. ¹Without an initrd, anyways...
Re: downgrade sid to woody?
Hi Kevin, On Mon, Sep 03, 2001 at 08:08:04AM -0500, Kevin van Haaren wrote: > . Is it enough to remove the unstable references > in sources.list and run upgrade? No >...or will that leave some of the > unstable packages in place? AFAIK all of them. APT uses the newest versions it can get, as I experienced lots of times in the past jumping between woody and potato and, more seldom, sid and woody. I'd a similar problem in the past and found no practicable solution :-(. The only thing I found was the command dpkg -i --force-downgrade with the result it comments the installation of the woody-version of the package but dpkg -s gave the version of sid further on. So, for short I'm not really shure even if this worked in my case downgrading just a package from sid to woody. With the former problem downgrading the whole from sid to woody I did a new installation of my system (56k-modem :=((( ). Hope anybody else has better hints.( ;-) ) Cheers -- mfg Georg Koss mailto: [EMAIL PROTECTED]
Re: divx
> Hello everybody > I just want to play divx on debian, because i don't like to play it > on mac os 9 > i just wait your answer. I am using mplayer (mplayer.sourceforge.net) with the ffmpeg divx codec, and it works really well. Check the mplayer README for the URL to ffmpeg. Cheers. James Tyson --- Samizdat New Media Solutions
Re: adaptec 2906 scsi card
crisbill wrote: > > I wrote to the list on August 18 reporting problems getting debian to > boot/install on a G4 mac (Subject:boot problems on g4). I should have > mentioned that I had installed an Adaptec 2906 SCSI card in the machine. > > As I reported, booting got stuck with the kernel from Woody after the md > driver message from the kernel. > > With the kernel from the Potato dist, I got no further than "Booting..." > > I tried some 2.4 kernels and got into the Woody installer that was > current at the time, but couldn't get past the Install Kernel and > Modules stage: the installer reported "Bad address Bad file descriptor". > (The log said that "set_loop couldn't create a loop device" for my > installation medium). > > Anyway, I ended up yanking out the card and then had no trouble > installing potato r.3 from a downloaded sourceforge debian-imac archive. > The Adaptec 2906 is a cheaper card without a BIOS. I'm curious if you've tried to boot the system with the card in it, with no devices connected to the card, since you've successfully installed potato. You might try the mac specific version of one of the aic7xxx cards a http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1270950154
Kernel Drivers in PPC build: where are they?
Hi, Sorry if this questions looks strange, even stupid. I tried digging the FAQ/Installation to get some answers for that, but it would seem that PowerPC specific materials don't come out easily from the docs, at least that is how I feel coming from the x86 side. I still like the machine better though, so it's worse the extra efforts ;-) Is the loading mechanism for kernel modules supported on the PPC platform? Can I compile my kernel without a specific module then compile the driver and store it in /lib/modules// or am I better off compiling as a big monolithic kernel? My problem is understanding where the kernel image stored on the bootstrap partition (vmlinux) kicks in the root partition and can see the drivers if it can see them at all on it. I was looking at the PowerPC installation disk for debian. I noticed that there is a file in there called drivers.tar.gz. What am I supposed to do with this file? Should I leave it in the bootstrap dir uncompressed next to yaboot and vmlinux files? Decompress it and move it in the /lib/modules/ dir in my root partition? Puzzled. Thanks for your help in advance. Laurent
Re: divx
On Montag, 3. September 2001 09:13 Michel Le Cocq wrote: > Hello everybody > I just want to play divx on debian, because i don't like to play it > on mac os 9 > i just wait your answer. What do you expect from us? Do you want to know what programs you can use? Or what? If it's this them download xmps and the codecs. Search at google for divx-codecs. There I found the right ones for xmps and it runs fine! Björn -- http://www.bbinternet.de
Re: downgrade sid to woody?
On Mon, 2001-09-03 at 16:08, Kevin van Haaren wrote: > I messed up my machine a couple of times running unstable (huh, > wonder why they call it that 8-) anyway I want to downgrade to just > woody. I dug through the apt-get and dselect man pages and didn't > see a way to do this. Is it enough to remove the unstable references > in sources.list and run upgrade? or will that leave some of the > unstable packages in place? IANADD*, so I am not In The Know(tm) on this, but I assume apt and dselect work by comparing package versions. So just changing the stuff in sources.list probably puts you up in the situation where upgrading the system makes apt think "Hmm, he already has newer stuff installed than what I see on the ftp site..". So I guess one would need to have something like dist-downgrade, but I have no clue if that is possible. Maybe someone In The Know(tm) would know better? Tuomas * IANADD = I Am Not A Debian Developer :o) -- :: :: Tuomas Kuosmanen :: Art Director, Ximian :: :: :: :: [EMAIL PROTECTED] :: www.ximian.com :: ::
Re: X 4.1.0 Hints for french PowerBook users...
On Sun, 2001-09-02 at 14:53, Florent Pillet wrote:
>
> After struggling with X keyboard configurations for a while, I finally found
> a way to get access to {, }, [ and ] under X on a FRENCH PowerBook keyboard.
>
> There is a problem with the standard key mappings under X 4.1.0 (I'm running
> unstable), you should modify the file:
>
> /usr/lib/X11/xkb/symbols/macintosh/fr
>
> and just after this line:
>
> name[Group1]= "FR-1";
>
> add:
>
> key {
> symbols[Group1] = [ Mode_switch, Multi_key ],
> virtualMods = AltGr
> };
This has the effect of making []{} etc to work. However, it disables ALT
for me (though I tried it on the finnish/swedish keymap) - thus you
cannot Ctrl-Alt-Backspace to kill the X server, nor can you use Alt for
anything (alt-drag to move windows for example on many window managers)
Tuomas
--
:: :: Tuomas Kuosmanen :: Art Director, Ximian :: ::
:: :: [EMAIL PROTECTED] :: www.ximian.com :: ::
adaptec 2906 scsi card
I wrote to the list on August 18 reporting problems getting debian to boot/install on a G4 mac (Subject:boot problems on g4). I should have mentioned that I had installed an Adaptec 2906 SCSI card in the machine. As I reported, booting got stuck with the kernel from Woody after the md driver message from the kernel. With the kernel from the Potato dist, I got no further than "Booting..." I tried some 2.4 kernels and got into the Woody installer that was current at the time, but couldn't get past the Install Kernel and Modules stage: the installer reported "Bad address Bad file descriptor". (The log said that "set_loop couldn't create a loop device" for my installation medium). Anyway, I ended up yanking out the card and then had no trouble installing potato r.3 from a downloaded sourceforge debian-imac archive. The Adaptec 2906 is a cheaper card without a BIOS. Can someone suggest a compatible card? --Bill Carini
Re: XMMS + Ogg = hiss?
On Sat, 1 Sep 2001, Derrik Pates wrote: > infrastructure, you're only adding kernel bloat, that's all. It adds > _zero_ functionality soundwise. yeah. someone had suggested turning them on to me, and when i did things started working. i didnt know why (since they had been broken for months on end), since there werent any modules that cooincided with powerpc hardware, but it must just have been good timing with a kernel & xmms in sid that fixed things. there was a patch for 2.4.0 iirc, but that didnt work when i tried it. plus, it was 2.4.0 :) john -- john wood systems administrator, gmo inc
downgrade sid to woody?
I messed up my machine a couple of times running unstable (huh, wonder why they call it that 8-) anyway I want to downgrade to just woody. I dug through the apt-get and dselect man pages and didn't see a way to do this. Is it enough to remove the unstable references in sources.list and run upgrade? or will that leave some of the unstable packages in place? Thanks, Kevin
Re: Problems Mounting HFS on Mac & Linux
>Is there a MacOS driver partition on the disk? If not, you will have to >use a >third party MacOS utility to install a driver - I do not know if Drive >Setup is >capable of installing drivers without initializing the entire disk. >Tom You may only install a driver on the first partition without erase the entire drive, there is a option "install driver". But only if DriveSetup can see the first partition. Tschau Frank Escher
divx
Hello everybody I just want to play divx on debian, because i don't like to play it on mac os 9 i just wait your answer. Michel --
Re: Troubles with Potato/Woody on iBook 2001
Laurent de Segur <[EMAIL PROTECTED]> writes: > Hi all, > > This message describes some problems I've ran into while installing a Debian > distr (2.2r3 + update stable) on a new iBook 2001 (P29 aka Marble). > > First it seems that the kernel that ships on the CD is a pre 2.2.18 and > won't boot on this machine. So I got a 2.2.18 from Suse (god forbids!) just > to use with yaboot during installation. > Strange, I did not have any problems booting the kernel on the 2.2r3 cdrom on my new iBook. > After I was done with the installation, I downloaded the 2.2.19. More > exactly, I updated the stable (potato) on top of a freshly installed 2.2r3 > and then moved the vmlinux kernel from / to my bootstrap partition where > yaboot is located, then changed the yaboot.conf file to point to the new > kernel. > > The result when I reboot is a white screen with Do-QUIESCE finishedbooting > hanging (it seems to continue booting, I just can't see it.) > > Rebooting with the original 2.2.18 works fine. On the iBook 2001, I have to > set "video=ofonly" to get video at boot time. Is this related? It seems that > the OS is still loading but I can't see it. > Yes, I got the Do-QUIESCE message until I started giving the "video=ofonly" argument to the kernel. You can put append "video=ofonly" in yaboot.conf as you would do with lilo.conf on x86 linux. > > Next, I updated to the testing release (woody) on the linux partition and > leaving 2.2.18 in the bootstrap partition to start with yaboot, the keyboard > is mapped totally wrong just after loading the USB drivers from the linux > partition it seems (I type when booting and keys are ok until usb is > detected and loaded.) Note: the internal keyboard on the iBook is USB. > If you search the archives you willl find hints on this. > After installing woody, I noticed that the /lib/modules dir still doesn't > contain a 2.4 subdir in there, only a 2.2.19 (part of the potato update.) So > no drivers from 2.4 can be loaded. Is this intented to be that way on a PPC > machine? It would seem that doing a woody update on a potato update would > get me the modules for 2.4 in my linux partition, right? > Did you get the 2.4 from http://penguinppc.org/~benh/ ? Please note that this link is temporarily down at the moment. Good luck! -Arrigo
