maemo.org - Talk
Page 4 of 5 « First 23 4 5
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP) (https://talk.maemo.org/showthread.php?t=93878)

Eno-Desu 2015-08-03 18:15
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Does someone remember Meego Rescue initrd? I can't find related files link since Meego is down and Tizen up.

The interesting thing was it was a kernel and initrd image loaded into ram over usb and the flasher tool. I don't know what the maximum size is that could be loaded like that but wouldn't it be nice to have the Debian-Installer that way? I was thinking about having keyboard and wifi support, and then install debian nativly without chroot on an empty (or in installer partioned) sd-card. Basically something like Debian-Netboot.

This isn't a request, nor do I know how-to myself. Just thinking about something nice and sharing that thought.

Edit, added some Debian things:
Quote:
Extract and modify the initrd.gz

Now we are ready to extract the initrd.gz, modify it and bring the changes back to an initrd.gz. We know that there are different ways to modify the initrd.gz file, like concatenating another .gz to it, but we like to know what we are doing and why things work like they do. Create a folder called "initrd" under our "netinstaller" folder. To this folder we will extract the contents of the initrd.gz from the Netinstaller.

Code:
mkdir ~/netinstaller/initrd
To extract the initrd.gz use the following command.

Code:
cd ~/netinstaller/initrd && zcat ~/netinstaller/cd/install.amd/initrd.gz | cpio -iv
Copy the extracted firmware to the extracted initrd

Now, after we extracted the initrd we can copy the firmware into it.

Code:
cp -Rpv ~/netinstaller/bnx2x/lib/firmware ~/netinstaller/initrd/lib
Copy the Preseed file to the extracted initrd

If you like to integrate a d-i Preseed file you can add it to the / (root) of the initrd. Please note that the Preseed file must be named preseed.cfg!

Code:
cp -v <yourpreseedfile> ~/netinstaller/initrd/preseed.cfg
Recreate the initrd.gz

After we made the changes in our initrd we have to recreate the initrd.gz

Code:
cd ~/netinstaller/initrd && find . -print0 | cpio -0 -H newc -ov | gzip -c > ~/netinstaller/cd/install.amd/initrd.gz
http://ftp.nl.debian.org/debian/dist...mages/netboot/

Android_808 2015-08-03 18:46
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
With regard to ti drivers, anyone know if "Xorg driver build (SUPPORT_XORG=1) not supported. " in the release notes means we can't use it with xorg (ie wayland only)?

Edit: Window system sections seems to drop X11 from v5.x onwards.

wicket 2015-08-04 01:26
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by Eno-Desu (Post 1478626)
Does someone remember Meego Rescue initrd? I can't find related files link since Meego is down and Tizen up.

The interesting thing was it was a kernel and initrd image loaded into ram over usb and the flasher tool. I don't know what the maximum size is that could be loaded like that but wouldn't it be nice to have the Debian-Installer that way? I was thinking about having keyboard and wifi support, and then install debian nativly without chroot on an empty (or in installer partioned) sd-card. Basically something like Debian-Netboot.

This isn't a request, nor do I know how-to myself. Just thinking about something nice and sharing that thought.

Edit, added some Debian things:


http://ftp.nl.debian.org/debian/dist...mages/netboot/
I can't say I remember MeeGo Rescue initrd.

I have actually thought about how I could make the installation more accessible to increase interest in the project. My main idea was to make install_debian.sh runnable on the N900 itself under Maemo, package it up and upload it to Extras. It would need to install a pre-built kernel but that would be trivial to provide.

The main show stopper is the incompatibility between Maemo's kernel and Debian's glibc which prevent on-device chroot. There are ways to work around this. sulu's patched glibc for EasyDebian is one option. Installing that might be problematic without a chroot. I would prefer to patch it in-place during the Debian installation process but that would require more work. Another option would be package a recent kernel (3.x/4.x) for Maemo, upload that to Extras and make it a dependency.

My main problem right now is lack of free time. As usual, any help would be welcomed.

wicket 2015-08-04 01:50
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by Android_808 (Post 1478628)
With regard to ti drivers, anyone know if "Xorg driver build (SUPPORT_XORG=1) not supported. " in the release notes means we can't use it with xorg (ie wayland only)?

Edit: Window system sections seems to drop X11 from v5.x onwards.
The X11 driver is available in Debian:

https://packages.debian.org/jessie/x...org-video-omap

It requires a kernel with DRM support (I will update the kernel build script for this at some stage).

What's not clear is what they mean by "not supported". Is it the building of the X11 driver that's not supported or is it that pre-built X11 drivers (like the one provided by Debian) are not compatible with the binary SGX drivers? It's probably the latter and that might explain why I couldn't get it to work.

Anyway, nicely spotted. It's something I missed. At some stage I'll try it again with v4 SGX drivers.

Android_808 2015-08-11 12:46
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Thought I'd share a little update on my work towards hildon on gtk3.

I finally tracked down a few (of the many) segfaults in libhildon meaning HildonFindToolbar now passes tests. get_allocation_size IIRC returns NULL so replaced with get_allocated_height. HildonPannableArea had lots of code relating to scrolling that I didn't feel was needed to I replaced it by inheriting GtkScrolledWindow. jump_to() was easier to sort out, scroll_to() would be 1 second fix if some of the private functions from gtkscrolledwindow and gtkadjustment were public. It still needs lots of work, especially theme/style wise.

Hildon-Desktop wise, I've made a little more progress. The menu file is actually loaded now which has fixed the inability to exit the menu. Unfortunately task switching is still broken. You can view task switcher but not select any running tasks.

Hildon-Home has some initial work done. Gtk3 port is done in as much as it runs but is still pretty unusable due to remaining issues in libhildon.

At some stage I might try to sort out a vid to demo the status and problems.

Today I've been cleaning up my source and have started to upload some of the projects to github (https://github.com/android-808?tab=repositories) So far libhildon, libhildondesktop and hildon-desktop are done but some other key bits (matchbox) I still need to go over. Please note that cairo, gtk, matchbox, clutter, mx etc are all completely new to me before starting this so I expect I may have made a few errors.

freemangordon 2015-08-11 15:17
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Android_808: Great! I wish I had some spare time to help you, but unfortunately I don't expect to have until maybe the mid of September :( (when I hopefully will update cssu-thumb as well as the other projects I have suspended)

Android_808 2015-08-11 21:35
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
There are quite a few extra hurdles to overcome before anyone else can build it due to the Mer packages for mce+dsme. I will try to give option of building against a mce based on cssu version at some stage.

I'm considering next stage at the moment, regarding clutter ui toolkit.
Option 1 is to stick with mx and fix it.
Option 2 is to follow libchamplain? (think thats right) who went back to tidy and update + cut down to only have the bits we need.
Option 3 is to follow the evolutionary route the forks, ie tidy>mx>st (gnome shell toolkit).

Last one is the only true upstream maintained option, so gonna give it a shot.

This was actually the reason for todays source upload. It was becoming a mess of quilt patches against cordia version. Gives me a clean, reproducable base to work with. There is one commit on hildon-desktop that needs sorting as it's a real hack to disable a chunk of dsme related code that needs if MER/ if MAEMO define to sort it out.

marmistrz 2015-09-07 11:55
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
What is N900 specific in these scripts? I'm about trying this out on my N950.

I've already done some kernel adaptation, see https://github.com/marmistrz/debian900

@Android_808: What if we started with Gnome3 shell instead and ran native N900 apps there? Maybe it'll be easier.

wicket 2015-09-07 23:21
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by marmistrz (Post 1481390)
What is N900 specific in these scripts? I'm about trying this out on my N950.

I've already done some kernel adaptation, see https://github.com/marmistrz/debian900
Apart from the kernel, other N900 specifics are the console and X11 keyboard layouts, possibly the WI-Fi firmware (you'll need to check this, I think the N950/N9 also uses TI firmware which is probably provided by the same package so you might be okay here), the device names for things like swap may be different, the touchscreen device and calibration in xorg.conf will be different, the wlan0 workaround might not be necessary, it might need different modules loaded in the initramfs, the device tree will be different, the U-Boot configuration script and the trigger that updates the the uInitrd image automatically won't be compatible (I'm assuming Ubiboot uses standard images for the kernel and initrd). Other than that, the rest is pretty generic.

The N950 is a beautiful device and I would have supported installation on it and on the N9 a long time ago if it wasn't such a dead-end platform. The kernel project was abandoned a long time ago and no effort was made to mainline the patches. As a result, you're stuck with using a 3-year-old kernel. Looking at the your kernel-n950.conf, you'll want to remove the OverlayFS support. Probably LXC too, some of the config option names have changed and some features will be missing entirely in that kernel. When I get some free time (won't be for a year) to put my full distro together, it will make substantial use of modern kernel features so unless someone bothers to bring the N9/N950 kernel into today's world, you can forget about it ever running on these devices.

marmistrz 2015-09-08 08:25
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by wicket (Post 1481503)
The N950 is a beautiful device and I would have supported installation on it and on the N9 a long time ago if it wasn't such a dead-end platform. The kernel project was abandoned a long time ago and no effort was made to mainline the patches. As a result, you're stuck with using a 3-year-old kernel. Looking at the your kernel-n950.conf, you'll want to remove the OverlayFS support. Probably LXC too, some of the config option names have changed and some features will be missing entirely in that kernel. When I get some free time (won't be for a year) to put my full distro together, it will make substantial use of modern kernel features so unless someone bothers to bring the N9/N950 kernel into today's world, you can forget about it ever running on these devices.
Hmmm... If the patches were properly sent upstream, wouldn't this mean we could use any (recent enough) mainline kernel on N9(50)?

If it's the case, I'll try to get in touch with the one who did the kernel upgrade job.

How modern kernel do we need? At least 4.0?

wicket 2015-09-08 16:13
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Well, yes. Mainline kernels are already bootable and very functional on the N900. The good news is that there is some of overlap between the N900 and the N9/N950 kernels, that means that there are patches that are needed for the N9/N950 which have already been mainlined by the N900 effort. You can compare the two project pages to get an idea:

https://wiki.merproject.org/wiki/N9_...update_project
http://elinux.org/N900

Good luck with your communication with the N9 kernel update project team. As I mentioned, the project appears to be all but abandoned. I hope don't sound too negative. I'd love to see upstreamed N9/N950 patches, it would respark my interest in the platform, put my N950 to good use and increase the reach and interest in mobile Debian.

The more modern the kernel, the better. N900 patches are being mainlined with each release. The cmt-speech driver for example went into 4.1. See here for the N900 changelog:

http://elinux.org/N900/Changelog

marmistrz 2015-09-09 08:18
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I've already gotten in touch with filippz (received a reply), I'll keep you updated.

marmistrz 2015-09-09 19:47
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Here's the reply from Filip. Anyone: do you have any ideas what to do with it? Pali (he was pinged by me): you work on the N900 kernel, maybe your experiences would be useful here.

Quote:
Originally Posted by Filip Matijević
Hi again,

regarding upstreaming my commits there are few major reasons why it didn't happen:

  • this kernel work was my first experience with kernel internals, pure C and git. Hence many commits are not up to linux kernel coding standards - they do work, but they can't be used "as is" for upstreaming
  • some of the drivers were part of the kernel, but seemed to be from different code base - depending on their usage they were modified, or rewritten based on original Nokia kernel. I guess replacing entire drivers is not something that would be upstreamed easy. For example CMT parts from n900 are different than those used on N9. N900 stuff got upstreamed (or is about to be), and I'm not really sure if it's the same HW, or there needs to be some N9/N950 specific stuff in there.
  • some hw can't be used without binary blobs from Harmattan (battery - BME, camera - lipomap3camd, and GPS as mentioned earlier). This forced me to do some nasty hacks (twl4030-madc seemed to be quite different and needed "old" stuff in order for BME to work, libomap3camd has trouble because v4l2_event has changed ABI...) This also would be difficult to upstream.
  • many of the stuff in there has no proper documentation (CMT, GPS...), hence it would be difficult to explain why some changes are needed. I guess saying: "It works that way", wouldn't be enough :)
  • Jolla used non LTS kernel as a base, maybe if we were on 3.4 LTS this would be a bit easier (AFAIK only "must have" reason for 3.0+ kernel was usage of systemd in Mer)
  • Kernel has shifted to device tree, but many of the stuff placed in board-rm680.c seem to be difficult do implement in such way - some of this would also require rewriting drivers

Sadly both of my N9's have stopped working (both developed problems with their CMT modules, one has since been destroyed in an attempt to fix it) I've moved to Android (and no, it's not working out for me:). This has reduced my interest in this project considerably, but I'm willing to help. At this point I'm thinking that we would need some kernel hacker that has good knowledge of kernel internals (and maybe even has connections with TI kernel guys and old Nokians that worked on N9) that would be willing to go trough my commits. Still I think that due to lack of documentation (MEIF requires signing NDA with Nokia, so does camera smiapp - together with bunch of "smiapp compatible" sensors that have quirks as they are not 100% compatible - contacting Toshiba, Sony for datasheets could be problematic...) current kernel state is probably best we can do.

It would be awesome if you succeed in getting some helping hands, but I'm under impression that N9/N950 didn't manage to attract "hardcore linux hackers" (at least not as much as N900 did) making it difficult (if not impossible) to find the "right people". In all this time I'm able to count all interested in N9 kernel on fingers of one hand :(

I've subscribed to TMO thread you linked, and I'll keep an eye on further progress!
About the state of the kernel:

Quote:
Originally Posted by Filip Matijević
Jolla guys did make first steps in making 3.5.3 bootable on N9, but after they moved onto their own HW they stopped developing N9 kernel further. I've made some progress since then, but biggest obstacle remains: problem of performance. It's believed to be due to rather hacky way wayland is implemented on top of closed source PVR binaries (https://github.com/nemomobile/ti-oma...-wayland-wsegl). Possible solutions would be to fix existing wayland implementation (https://twitter.com/hedayatvk was investigating that), or use PVR drivers for android (from LG Optimus Black P970, https://twitter.com/crazybulgarian was looking into that). There is also small possibility that Imagination makes open source driver (https://www.phoronix.com/scan.php?pa...R-Open-Chatter) but I wouldn't hold my breath on that one.

The only non function part of the kernel is GPS - and this will remain unchanged. GPS chip speaks MEIF instead of NMEA, and all the binary blobs for GPS (there seem to be a few of those) from Harmattan are tied to Qt4.
Filip's TMO nick is Filip.pz

marmistrz 2015-09-10 13:36
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Info from pali:

Quote:
Originally Posted by pali
Hello!

You can look at page http://elinux.org/N900 which track upstreaming
status for Nokia N900.

Process for upstreaming support for N9 or N900 should be similar or
quite same.

There are basically two big problems:

1) SGX graphics drivers and changes they need in mainline kernel

There is no open source userspace support for these TI/IM/SGX drivers
and this is enough reason that they will never be merged into mainline
kernel. Also now only KMS graphics drivers are accepted to mainline
kernel, so you those SGX kernel drivers (even they are GPLv2) will never
hit mainline kernel.

Just to note that *every* and *every* SGX chip needs different:
microcode, kernel driver and userspace driver.

Plus those SGX kernel drivers needs some changes (hacks!!) to mainline
kernel to make they work.

I would just say, ignore SGX driver in upstream process and keep them in
separate tree (with also changes to mainline kernel which are needed).


2) Quality of current Nokia/TI drivers which are in some production
Nokia kernels used on Nokia N9.

Lot of times quality is really bad and in that state drivers are not
accepted. You need to communicate with developers of specific kernel
trees what do they think about those drivers, what needed to be fixed,
changes and so, so maintainers can accept and merged them.

Plus whole OMAP and ARM code in kernel is converting to DeviceTree
structures (from old board code), so when you will try to mainline it,
you need to add support for DeviceTree (and probably remove old
platform_device board code which is obsolated).


3) First and important: Create table line on http://elinux.org/N900 and
decide which drivers are needed, which are already in upstream (but
in different name, etc) and which must be rewritten (e.g because
interface/subsystem was changed).

Thanks all.
Quote:
Originally Posted by pali
I think all hackers who hacking n900 kernel know all these information,
so for them it is not needed...

>
>> 3) First and important: Create table line on http://elinux.org/N900 and
>> decide which drivers are needed, which are already in upstream (but
>> in different name, etc) and which must be rewritten (e.g because
>> interface/subsystem was changed).
>
> You mean that we should combine the N900 & N9 efforts together?
>

Rather create new wiki page (on elinux.org). Please not add N9 info into
N900 page as we want to have that page clean...
Any other kernel hackers here? :)

I think it's a good idea to create the elinux.org page for N9, indicating what is already upstreamed, what has to be done (issues for each of the commits, etc.), which parts need binary blobs (we'd have to reverse engineer them or use them)

When it comes to the coding style, maybe I could fix a commit or two.

One more thing: (@filip.pz) BME has been reverse engineered.

marmistrz 2015-09-10 13:36
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
@Everyone: Any thoughts?

marmistrz 2015-09-26 19:45
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
For people not watching the Upstreaming Force: crossposting: http://talk.maemo.org/showpost.php?p...4&postcount=45

marmistrz 2015-11-21 16:14
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Feature request: could you add the possibility of installing kernel only to debian900, without removing all the fs?

When I have time to devote to the N950 kernel upstreaming, I'll probably test >1 kernels, so I don't want to kill my internal memory with write cycles.

wicket 2015-11-21 18:36
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by marmistrz (Post 1489050)
Feature request: could you add the possibility of installing kernel only to debian900, without removing all the fs?

When I have time to devote to the N950 kernel upstreaming, I'll probably test >1 kernels, so I don't want to kill my internal memory with write cycles.
This is something that I've wanted to do for a while now as to test a new kernel I would often find myself manually mounting the file systems, copying over the kernel and modules and then I'd chroot into it in order to generate U-Boot compatible kernel and initrd images. It's a bit of a pain when it can be easily automated.

Sadly, I've no free time available in the coming months to do any work on this project.

NIK510 2015-11-29 10:04
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Thanks a lot for this project, really cool to have debian on my N900!
I am curious can you connect USB devices?

Android_808 2015-12-21 22:23
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quick update on GTK3. Will start a dedicated thread at some stage.

Been cleaning up the test suite and examples lately to help track down a few issues and to make the build output easier to follow. It is down to hildon-pannable-area-tuning-example (segfaults because I ripped out a lot of HildonPannableArea) and hildon-button-example (gtk_button_set_alignment IIRC) being the only files to generate warnings.

With regard to actual source files, HildonCaption, HildonButton, HildonPannableArea and hildon-main are still causing warnings.

I have some changes not yet commited to github (inc some of the examples fixes unfortunately), mainly due to HILDON_SIZE_HALFSCREEN_WIDTH and HILDON_SIZE_FULLSCREEN_WIDTH not being handled the same in GTK3. These helpers are probably going to have to be removed, and the height definitions need some work to prevent a warning being spewed out by HildonAppMenu (amongst others).

It is buildable on its own on Debian if anyone really wants to have a play. Stacked windows and some notifications won't work as intended (they need hildon-desktop/matchbox). You'll also get several styling/font errors as I've not started to look at that fully yet.

marmistrz 2015-12-28 09:24
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Does DebiaN900 use some kind of preinit script on N900? For example to kick the watchdog, etc. We'll need such a thing on N950 but maybe there's no need to reinvent the wheel :)

marmistrz 2016-06-29 11:30
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
wicket: not polling github anymore, better to discuss it here.

there are lots of problems with running your script under Arch.

We don't have qemu-debootstrap here, it is advised to symlink it: http://unix.stackexchange.com/questi...-in-arch-linux

So I did it, then debootstrap fails on: mount: Bad exec format

Some search yielded I need to add the --foreign parameter. Did it, now debootstrapping fails because of missing /mnt/etc/hosts.

Do you have any ideas?

wicket 2016-07-03 18:16
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Sorry for neglecting this thread but my time has freed up for the moment so I'll be doing some more work on this.

Meanwhile, I snapped up this beauty which should speed up development. It's been sitting in the UK for a few months but it will be personally delivered to me this Tuesday. :)

I want to again thank all of those who offered me an N900 but I really did not want to accept a donation whilst I wasn't sure how much time I would be able to commit to the project.

Quote:
Originally Posted by NIK510 (Post 1490098)
I am curious can you connect USB devices?
Not yet. Host mode via debugfs is work in progress:

http://thread.gmane.org/gmane.linux..../focus=2133266

Quote:
Originally Posted by marmistrz (Post 1492789)
Does DebiaN900 use some kind of preinit script on N900? For example to kick the watchdog, etc. We'll need such a thing on N950 but maybe there's no need to reinvent the wheel :)
There's no special preinit script. It's pure Debian.

Quote:
Originally Posted by marmistrz (Post 1508639)
wicket: not polling github anymore, better to discuss it here.

there are lots of problems with running your script under Arch.

We don't have qemu-debootstrap here, it is advised to symlink it: http://unix.stackexchange.com/questi...-in-arch-linux

So I did it, then debootstrap fails on: mount: Bad exec format

Some search yielded I need to add the --foreign parameter. Did it, now debootstrapping fails because of missing /mnt/etc/hosts.

Do you have any ideas?
Please see my responses on the issue tracker. You need qemu-arm-static and then you can register the ARM executable binary format.

marmistrz 2016-07-05 13:21
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
What currently blocks us from supporting installation on the eMMC? I have a spare N900 to experiment on but no spare uSD atm.

wicket 2016-07-05 15:29
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I've pushed several commits to GitHub. The notable changes are that a new script debug mode is now supported which provides verbose output, the default kernel has been updated to 4.7-rc4 from Pali's repo and the kernel is now installed as a deb file.

By installing the kernel as a deb file, it's now much easier to test new kernels. Installation of the deb file will append the device tree to the kernel image and create the U-Boot image automatically. Creation of the initrd images is triggered automatically after the kernel has been installed. This means that you now just need to copy the deb file over and install it (and don't forget to update U-Boot!). Deb files for headers, dbg and libc dev are also built. You'll need to make sure that your build system can build deb files!

I've just noticed a regression with the 4.7-rc4 kernel in that the mouse cursor movement is inverted on the Y axis so I may revert the default kernel to an earlier version.

Quote:
Originally Posted by marmistrz (Post 1509028)
What currently blocks us from supporting installation on the eMMC? I have a spare N900 to experiment on but no spare uSD atm.
Nothing really, however I've not tested it.

marmistrz 2016-07-05 16:15
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I tried. By while partitioning I forgot about the hardcoded partition ids in Maemo, which rendered Maemo unbootable.

Is there any other way to fix it than by undoing the partitioning and reinstalling Debian?

My partitioning:

/dev/mmcblk0p1
/dev/mmcblk0p4
/dev/mmcblk0p2
/dev/mmcblk0p3

I'd need to move p4 to the end of the disk

wicket 2016-07-05 18:38
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by marmistrz (Post 1509040)
I tried. By while partitioning I forgot about the hardcoded partition ids in Maemo, which rendered Maemo unbootable.

Is there any other way to fix it than by undoing the partitioning and reinstalling Debian?

My partitioning:

/dev/mmcblk0p1
/dev/mmcblk0p4
/dev/mmcblk0p2
/dev/mmcblk0p3

I'd need to move p4 to the end of the disk
You've not made it clear what it is you've done exactly. I don't understand how you've got the partitioning in that order, partition managers like fdisk and parted will number the partitions in the correct order. If you've not got a bootable OS, don't you need to reflash?

marmistrz 2016-07-05 20:08
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I used the MeeGo rescue initrd. I stripped the mmcblk0p4 to 10 GB. I created an ext4 partition in the remaining spaced. It was given the id mmcblk0p4.

I installed Debian with the script (old version) to the newly created ext4 partition.
Now I'm booting Maemo with U-Boot, all I get is a black screen.

I guess that If mmcblk0p4 were removed, Maemo'd boot back again.

pythoneye2 2016-07-06 01:29
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I have debian900 booting from emmc. So it is possible ;)
If i remember correctly the only "problem" was the numbering change depending on whether a sd card is in the device or not.

emmc becomes
/dev/mmcblk0 without sdcard
/dev/mmcblk1 with sdcard in device

I "solved" it via 2 different uboot entrys.
But i guess you need just one.

marmistrz 2016-07-06 08:35
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
My uboot was more fubar than I thought, reflashed.

I can't build the kernel with the latest git version:
Code:
  LD      drivers/video/fbdev/omap2/built-in.o
  LD      drivers/video/fbdev/built-in.o
  LD      drivers/video/built-in.o
  LD      drivers/built-in.o
make[1]: *** [deb-pkg] Error 2
make: *** [deb-pkg] Error 2
/edit: the real cause was earlier on:

Code:
  CC      fs/nls/nls_base.o
In file included from include/linux/spinlock.h:81:0,
                from include/linux/seqlock.h:35,
                from include/linux/time.h:5,
                from include/linux/stat.h:18,
                from include/linux/module.h:10,
                from fs/nls/nls_base.c:11:
include/linux/spinlock_types.h:76:1: internal compiler error: Segmentation fault
 } spinlock_t;
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[4]: *** [fs/nls/nls_base.o] Error 1
make[3]: *** [fs/nls] Error 2
make[2]: *** [fs] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC      drivers/iommu/omap-iommu.o
I guess I'll have to build the kernel on my Arch/GCC6.1 and resume the debootstrap on my Linux Mint.

/edit2: the script should check for dpkg, installed it on my Arch, let's see what happens next.
/edit3: The packaging fails:
Code:
parsechangelog/debian: warning:    debian/changelog(l2): found eof where expected first heading
parsechangelog/debian: error: fatal error occurred while parsing debian/changelog
dpkg-gencontrol: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255
make[1]: *** [scripts/package/Makefile:94: deb-pkg] Error 255

Fallingwater 2016-07-07 10:36
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Hi. I've dug my N900 back out because I'm interested in running a Pi-Hole household ad-blocker on it, as per this thread.

Pi-hole is meant for a Raspberry Pi, but will work on vanilla Debian - I currently have it running on an old Asus EeePC 701 running textmode Debian.

Consequently, I need Debian running on the N900. Importantly, I don't care about Maemo at all - I'll do a MMC backup for nostalgia's sake, but I don't actually need the device to perform as a smartphone anymore, so I can wipe its contents completely and repartition from scratch. All I need is for the operating system to run and connect to my wi-fi, then I can control it via ssh and download what I need from the Debian repos and pi-hole.

I have some relatively vague memories about tinkering on the N900, but it's been several years since I've done anything on it and I don't really remember the technicalities. Is a step-by-step guide to install DebiaN900 available? I've checked the readme but it assumes knowledge I don't really have; specifically, is there any way to avoid cross-compilation, perhaps using precompiled kernels?

And thanks for the efforts, I wasn't expecting to see the most recent update to be yesterday!

marmistrz 2016-07-11 10:43
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Ok, I used the old version of DebiaN900 to setup Debian on my spare N900. There's one problem. U-Boot doesn't show the entries

I can choose between: attachboot, eMMC boot, SD boot, etc. I don't get the menu as on the photo here: http://i.imgur.com/5HKgggR.jpg

The generated configure-uboot.sh was:
http://paste.ubuntu.com/19067425/

I changed EXT_CARD to INT_CARD, but the problem persists.

The package is: u-boot-flasher

wicket 2016-07-15 23:31
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by Fallingwater (Post 1509158)
Hi. I've dug my N900 back out because I'm interested in running a Pi-Hole household ad-blocker on it, as per this thread.

Pi-hole is meant for a Raspberry Pi, but will work on vanilla Debian - I currently have it running on an old Asus EeePC 701 running textmode Debian.

Consequently, I need Debian running on the N900. Importantly, I don't care about Maemo at all - I'll do a MMC backup for nostalgia's sake, but I don't actually need the device to perform as a smartphone anymore, so I can wipe its contents completely and repartition from scratch. All I need is for the operating system to run and connect to my wi-fi, then I can control it via ssh and download what I need from the Debian repos and pi-hole.

I have some relatively vague memories about tinkering on the N900, but it's been several years since I've done anything on it and I don't really remember the technicalities. Is a step-by-step guide to install DebiaN900 available? I've checked the readme but it assumes knowledge I don't really have; specifically, is there any way to avoid cross-compilation, perhaps using precompiled kernels?

And thanks for the efforts, I wasn't expecting to see the most recent update to be yesterday!
I'm not familiar with Pi-hole but I see no reason why it shouldn't work. As long as you are running a Debian based distro on your PC (Debian, Ubuntu, Mint, etc.), it's fairly straight forward to set up. Not a lot of prior knowledge is required, you just need to make sure that all of the dependencies have been installed. If you still have problems, I could provide you with a precompiled kernel deb package.

Quote:
Originally Posted by marmistrz (Post 1509401)
Ok, I used the old version of DebiaN900 to setup Debian on my spare N900. There's one problem. U-Boot doesn't show the entries

I can choose between: attachboot, eMMC boot, SD boot, etc. I don't get the menu as on the photo here: http://i.imgur.com/5HKgggR.jpg

The generated configure-uboot.sh was:
http://paste.ubuntu.com/19067425/

I changed EXT_CARD to INT_CARD, but the problem persists.

The package is: u-boot-flasher
It looks like you are running some other bootloader there. Make sure that Pali's U-Boot has been installed from the Extras repository and that no other bootloaders are installed which may interfere with it.

marmistrz 2016-07-16 06:52
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by wicket (Post 1509754)
It looks like you are running some other bootloader there. Make sure that Pali's U-Boot has been installed from the Extras repository and that no other bootloaders are installed which may interfere with it.
Which package should that be?

As for the following error:
Code:
parsechangelog/debian: warning:    debian/changelog(l2): found eof where expected first heading parsechangelog/debian: error: fatal error occurred while parsing debian/changelog dpkg-gencontrol: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255 make[1]: *** [scripts/package/Makefile:94: deb-pkg] Error 255
a patch is awaiting in an upstream kernel (mailing list reference: today).
I'll make a workaround in debian900 anyway soon

marmistrz 2016-07-27 13:29
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I tried installing Gnome Shell just to see how fast/slow it's running. I get a black screen at the GDM launch.

Do you have an idea how to debug it?

wicket 2016-07-27 18:45
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
I'd start by checking /var/log/Xorg.0.log for errors.

sulu 2016-07-28 07:18
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Does gdm3 even run without hw acceleration?
I thought it doesn't. But even then, it should display its enormously helpful message: "Oh no! Something has gone wrong"
Maybe it needs a UHD screen to do that.

marmistrz 2016-07-28 07:25
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by wicket (Post 1511002)
I'd start by checking /var/log/Xorg.0.log for errors.
I mean, how can I access the logs?

Quote:
Originally Posted by sulu (Post 1511036)
Does gdm3 even run without hw acceleration?
I thought it doesn't. But even then, it should display its enormously helpful message: "Oh no! Something has gone wrong"
Maybe it needs a UHD screen to do that.
I guess something happens at the stderr. But still I see no way to read it while I'm stuck at the black screen.

sulu 2016-07-28 07:58
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by marmistrz (Post 1511037)
I mean, how can I access the logs?
I believe there is no way to change to a different tty due to the N900's limited keyboard. Afair the key combination to change ttys can be changed in the kernel config, which might be worth considering.

Anyway, if you have Maemo installed in parallel you can access the logs from there.
If you already have network up when the blackscreen appears, you can ssh into the N900.
If everything else fails, take the µSD card out of the device and check the logs on a different computer.
If you installed DebiaN900 on your internal emmc, install another instance of it on a µSD card (WITHOUT Gnome ;), Lxde with slim works fine), boot from there and check the logs on the emmc.

wicket 2016-07-28 14:45
Re: DebiaN900 - A set of scripts to facilitate the installation of native Debian (WIP)
 
Quote:
Originally Posted by sulu (Post 1511040)
I believe there is no way to change to a different tty due to the N900's limited keyboard. Afair the key combination to change ttys can be changed in the kernel config, which might be worth considering.
The default keyboard configuration uses Fn+VolumeUp and Fn+VolumeDown to change pseudo TTYs.


All times are GMT. The time now is 11:39.
Page 4 of 5 « First 23 4 5
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8